1.106 update #2577
Merged
1.106 update #2577
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chipzoller
approved these changes
Sep 10, 2023
|
Hey team, any quick way to automate this process? |
|
It's on my to-do list, actually. Shouldn't be too difficult. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
update kubecost.yaml and chart.yaml to 1.106.0
Does this PR rely on any other PRs?
no
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Useful for users that prefer the flat manifest or cloning the default develop branch
What risks are associated with merging this PR? What is required to fully test this PR?
None
How was this PR tested?
helm template kubecost \ --repo https://kubecost.github.io/cost-analyzer cost-analyzer \ -n kubecost \ >cost-analyzer-helm-chart/kubecost.yamlHave you made an update to documentation? If so, please provide the corresponding PR.