[stable/aws-s3-proxy]: Support k8s 1.19 Ingress #481
Merged
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
Ingress of
aws-s3-proxy
only supportnetworking.k8s.io/v1beta1
andextensions/v1beta1
, so it cannot be deployed over k8s 1.22 versions. (networking.k8s.io/v1
is supported starting with k8s 1.19.)https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122
So, add if-else statements to support
networking.k8s.io/v1
apiVersion. This change is compatible to k8s 1.19 under version, so don't worry :)Checklist
[stable/mychartname]
)