Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

values.yaml - set default connect inject init cpu resource limits to null, backport to 1.0.x #2021

Closed

Conversation

david-yu
Copy link
Contributor

@david-yu david-yu commented Mar 15, 2023

Changes proposed in this PR:

How I've tested this PR:

How I expect reviewers to test this PR:

Checklist:

  • Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)

…`null` to increase service registration times (hashicorp#2008)

* Update values.yaml
@david-yu david-yu changed the title Helm: 1.0.x backport of 2008 helm: 1.0.x backport of 2008 Mar 15, 2023
@david-yu david-yu added the pr/no-backport signals that a PR will not contain a backport label label Mar 15, 2023
@david-yu david-yu changed the title helm: 1.0.x backport of 2008 values.yaml - set default connect inject init cpu resource limits to null, backport to 1.0.x Mar 15, 2023
@david-yu david-yu added the pr/no-changelog PR does not need a corresponding .changelog entry label Mar 15, 2023
@david-yu
Copy link
Contributor Author

Will close on wrong branch

@david-yu david-yu closed this Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport signals that a PR will not contain a backport label pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant