-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
token recognition error in kustomization on valid CRD #4646
Comments
mloiseleur
changed the title
kustomize-controller token recognition error on valid CRD
token recognition error in kustomization on valid CRD
Mar 4, 2024
Hey @mloiseleur I can't reproduce this with Kubernetes upstream v1.29.3 PR here fluxcd/kustomize-controller#1124 |
It's annoying and no surprising at the same time : this test is like the strange things section in the issue description. There is two possible difference between config of this issue and your PR.
since I cannot commit in your PR, I tried option 2 in fluxcd/kustomize-controller#1125 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When applying infrastructure components yaml from AWS provider of Cluster API, flux kustomization fails with this error message:
error message
Strange things, this yaml section works fine:
it seems it's only for this specific
/spec/versions/0/schema/openAPIV3Schema/properties/spec/properties/version/x-kubernetes-validations
fieldSteps to reproduce
Just add this YAML in a kustomization file, and it throws parser token error.
Expected behavior
A YAML accepted by kubernetes client should also be accepted by Flux.
Screenshots and recordings
No response
OS / Distro
Kubernetes
Flux version
v2.2.3
Flux check
Additional context
It's possible to workaround this issue by removing this field with a json patch:
Code of Conduct
The text was updated successfully, but these errors were encountered: