Fix for - Generate policy fails if trigger resource name exceed 58 characters #1631
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.
Signed-off-by: NoSkillGirl singhpooja240393@gmail.com
Related issue
closes #1624
What type of PR is this
Proposed changes
The issue was due to the label
kyverno.io/generated-by
which is a combination of source resource kind-namespace-name. The character count exceeds 63 chars if the name or namespace have more number of characters.To resolve this issue label
kyverno.io/generated-by
is separated in three labels:kyverno.io/generated-by-kind
kyverno.io/generated-by-namespace
kyverno.io/generated-by-name
Checklist