You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i want to overwrite the behavior where i want to accept annotations added by other ways to resources managed by kapp-controller and so added following config in a yaml file along with other resource definitions packed as a imgpkg.
But kapp-controller still tries to remove the extra annotations added which will be rejected by our custom opa controller.
<> annotations/labels <> cannot be deleted
Can you please let me now if i am doing something wrong and also if there is any way i can overwrite the default rebaserules globally and not in individual apps.
The text was updated successfully, but these errors were encountered:
(Also, apologies for not being able to reply for a while, you can always reach out on the carvel slack channel for queries)
renuy
added
discussion
This issue is not a bug or feature and a conversation is needed to find an appropriate resolution
and removed
carvel triage
This issue has not yet been reviewed for validity
labels
Jan 2, 2024
I see that kapp has a default rebase rule for annotations as follows
Be specific about annotations to be applied
type: remove
resourceMatchers:
type: copy
sources: [new]
resourceMatchers:
i want to overwrite the behavior where i want to accept annotations added by other ways to resources managed by kapp-controller and so added following config in a yaml file along with other resource definitions packed as a imgpkg.
apiVersion: kapp.k14s.io/v1alpha1
kind: Config
rebaseRules:
type: copy
sources: [existing, new]
resourceMatchers:
But kapp-controller still tries to remove the extra annotations added which will be rejected by our custom opa controller.
<> annotations/labels <> cannot be deleted
Can you please let me now if i am doing something wrong and also if there is any way i can overwrite the default rebaserules globally and not in individual apps.
The text was updated successfully, but these errors were encountered: