-
Notifications
You must be signed in to change notification settings - Fork 183
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
Deactivate kubernetes.io in override labels #533
Comments
“Deprecate” means “tell people that they ought to switch”. The point where we turn off the old thing has another name, such as “deactivate”. |
oh, thanks for the explanation! We'll actually be warning folks that they need to switch when we make a new release with the changes in the PR. Will do it today. I've changed the issue title and description to capture your feedback! Thank you so much once again! |
one basic question(sorry if it's not right place): Can we override error to scan yaml file? |
It was suggested that we give folks 6 months before we deactivate the old override labels with
kubernetes.io
annotation.We now support both
kubernetes.io
andkubeaudit.io
but once kubernetes v 1.28 is released, we'll fully deactivate the old labelsThe text was updated successfully, but these errors were encountered: