Update pinned bitnami charts in values.yaml #1900
Merged
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
andresmgot
approved these changes
Jul 29, 2020
andresmgot
reviewed
Jul 29, 2020
| @@ -646,7 +646,7 @@ authProxy: | |||
| image: | |||
| registry: docker.io | |||
| repository: bitnami/oauth2-proxy | |||
| tag: 5.1.0-debian-10-r24 | |||
| tag: 5.1.1-debian-10-r58 | |||
There was a problem hiding this comment.
BTW, can you give a try to 6.x?
There was a problem hiding this comment.
6.x requires option changes in our chart. I'll try to do that today separately.
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.
Description of the change
Updates the bitnami charts in the values.yaml to their latest versions.
Benefits
Some providers delete older tags (odd?) breaking chart deployments without manual configuration.
Possible drawbacks
See if CI passes without issue.
Additional information
Longer term, we should not pin these in our Kubeapps main branch, but pin them to the current latest when releasing the Kubeapps chart.