This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
[release/4][BACKPORT] [auto-bump][chart] kube-oidc-proxy-0.3.0 #1420
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.
This is a backport of the following PR:
#1418
What type of PR is this?
Feature
What this PR does/ why we need it:
Bump kube-oidc-proxy to 0.3.0
Which issue(s) this PR fixes:
https://jira.d2iq.com/browse/D2IQ-82948
Special notes for your reviewer:
I tried to add to the chart things/changes that were introduced upstream since our last bump (to 0.2.0 in 1b9a4b392d13fa66f395eb854b57c962ca015969). I assume that the 0.2.0 bump did the same.
Tested with: mesosphere/kommander#1389 and manually with k20 - 1655a43c773009fb9d97cb940d7758d9370156b3, and latest konvoy (also manually).
The manual test consisted of launching the cluster, confirming that 0.3.0 was deployed, obtaining the token, and logging into the cluster and listing pods using it.
Does this PR introduce a user-facing change?:
Checklist