-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Updating ConfigMap always fail due to "_example" modified error #8211
Comments
I reproduce it easily. |
Ok, found it |
Ugh, sorry for missing this. My first version checked for this but I lost that in rewriting it to a go tool. My bad 👼 |
… spaces Fixes knative#8211 in serving
Mainly I think it's because we're using two different yaml parsers :| which is always inviting trouble in subtle differences :) |
Hello, I am running into this issue while trying to configure the domain as described here:
How do I proceed forward? |
Did you update your serving? |
I am using the vision 0.15 as documented on the knative docs site. Since this is fairly new, I am sure I am not using the latest version. Which version should I be upgrading to? |
The same problem appears on
|
The same problem appears with |
I am on 1.7.2 and I can't figure out how to get around this issue. Whats the actual resolution here? I am trying to modify the ingress class and I cannot, not even if by deleting and recreating from the configMap. I'm not sure what it thinks I changed. EDIT: ok, turns out a few weeks ago when I was messing with this I must have modified the initial config, and when I went to apply it from scratch it created the configMap before it created the validating webhook, therefore it was already "modified" from the example but I thought it was only my newer modifications that were breaking thing. I pulled the right example block from the upstream and fixed the issue. |
For anyone having this issue, this snippet can help yo redo your example checksum in case you need it:
|
While trying to update staging, I realized that there was a testing setting on config-defaults that was applied manually, so I tried to restore the original _example config but I ended up in: knative/serving#8211 This seems something very brittle to rely on, the webhook validator can potentially reject the config if we add new (real) values etc.. It never happened in the past, but I stumbled upon it so I'd vote for removing the problem entirely to be safe. Simply stripping the _example settings works, since the checksum value stored in the annotation is not validated anymore. I think that it is way better to avoid _example, we have always checked upstream docs for new settings, it shouldn't be a big problem. Also those examples can be consulted in the yaml files shipped by old knative releases on github, so easily retrievable. Bug: T368359 Change-Id: I558ed01eb44bf230e61fdf14cc8537ac941618a0
Description
validation failed: "_example" modified, you likely wanted to create an unindented configuration
._example
field, but it fails even though non-_example
block field with correct indent.In what area(s)?
/area API
What version of Knative?
Build on top of 4aedf5f
Expected Behavior
should work.
Actual Behavior
Steps to Reproduce the Problem
or
and add a new config in non-
_example
block field with correct indent.The text was updated successfully, but these errors were encountered: