-
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
Case convention inconsistent in Knative Serving config maps #7300
Comments
ugh, that ship has sailed probably... otherwise it's a long and painful migration. :| |
I wonder if now that we have the nice config map parsing library in pkg we could make this change in a backwards compatible way without a completely unreasonable amount of pain 🤔. It's only going to worse if we don't so I vote we bite the bullet, fwiw. Hyphens ftw ;). |
Another alternative is @markusthoemmes proposal to switch to CRDs. Care to link that? |
This issue is stale because it has been open for 90 days with no |
/lifecycle frozen Ping @markusthoemmes for link |
#8114 here's the other issue. |
I think #8114 is probably the best chance to resolve this issue. /area API /close |
@evankanderson: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I think for the 1.0 efforts we should do this and keeping the backwards compatible /reopen |
@dprotaso: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Part of knative/serving#7300 Majority of serving uses lowercase-hyphens - ie. some-property over someProperty This changes the leader election config map parsing to support formats and to prioritize the lowercase-hyphen case
Part of knative/serving#7300 Majority of serving uses lowercase-hyphens - ie. some-property over someProperty This changes the leader election config map parsing to support formats and to prioritize the lowercase-hyphen case
I've just filled a similar issue to track label and annotation names as well - #12103 I think, those two should be done in synchronization to lower the migration pain for end users. |
I think all the config maps are sorted and the documentation was the last remaining bit |
Some config maps have keys using camel-case, some have kebab-case. The majority of the config maps use camel-case at this point. All of this should probably be unified.
camel-case used in these config maps:
Expected Behavior
All config maps using the same notation.
Actual Behavior
Some config maps using a different notation than others.
Steps to Reproduce the Problem
The text was updated successfully, but these errors were encountered: