Allow unstructured schema for the ProxyDefaults CRD #495
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.
Prior to
apiextensions.k8s.io/v1
, structured schema was optional for CRD spec, but now it is required. Sinceconfig
field can have arbitrary keys, we need to tell Kubernetes to allow that explicitly now that we've upgraded fromv1beta1
tov1
.Changes proposed in this PR:
x-kubernetes-preserve-unknown-fields
totrue
for theconfig
field inProxyDefaults
How I've tested this PR:
by running acceptance tests
How I expect reviewers to test this PR:
code review (acceptance tests in hashicorp/consul-helm#921)
Checklist: