-
Notifications
You must be signed in to change notification settings - Fork 5
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
externalTrafficPolicy/enum must NOT have duplicate items on 1.0.61 #21
Comments
@bcha, good finding Looks like the schema for version 1.29.4 has duplicate entries, which is not the case for the least 1.30.0
I will investigate and let you know further. |
rubenhak
added a commit
that referenced
this issue
Jul 14, 2024
@bcha, this is fixed in the latest release v1.0.62.
|
Closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Getting curious
..externalTrafficPolicy/enum must NOT have duplicate items (items ## 2 and 3 are identical)
errors suddenly. Noticed this with our applications running kubevious in CI/CD and I can replicate this locally as well.This seems to be somehow related to the latest release 1.0.61 and the --k8s-version parameter.
These seem to happen with pretty much any kind of deployment.yaml. We first ran into these with our own huge manifests, but in this example I just used something simple I copypasted from k8s docs:
With 1.0.60:
With 1.0.61:
With 1.0.61 I get success if I leave out --k8s-version:
The text was updated successfully, but these errors were encountered: