fix: update debug skip probes annotation to be Kubernetes valid annotation#9831
Merged
ChrisGe4 merged 1 commit intoGoogleContainerTools:mainfrom Jun 12, 2025
Merged
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
ChrisGe4
approved these changes
Jun 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #8962
Description
Current implementation of Skaffold uses annotation that is not valid on Kubernetes. Valid annotation can have at most one
/in it. According to Kubernetes docs: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/#syntax-and-character-setUser facing changes (remove if N/A)
User will have to use now annotation:
instead of
Fortunately, nothing should change for users as they weren't able to use this feature now, because of Kubernetes validation, which prevented them from using it