This repository was archived by the owner on Dec 4, 2024. It is now read-only.
[auto-bump][chart] kube-oidc-proxy-0.3.1#1462
Open
d2iq-dispatch wants to merge 2 commits intomasterfrom
Open
Conversation
Contributor
|
This repo has @mesosphere-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@mesosphere-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 type of PR is this?
Chore
What this PR does/ why we need it:
Updates charts definitions where
Ingressobjects were using deprecatedextensions/v1beta1ornetworking.k8s.io/v1API versions that were removed from k8s 1.22. Updated charts:Which issue(s) this PR fixes:
https://jira.d2iq.com/browse/D2IQ-81723
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist