new namespaces gets dynamically added to schedule and fails validation #9139
Replies: 2 comments 1 reply
Expected behavior..
If you added NS, velero won't remove them or ignore them.. you specified velero to backup a non existing NS, velero will tell you about its non-existence. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We have set the includenamespaces to * and when it detects the new ns it appends to the included namespaces leading to
Validation errors:
Invalid included/excluded namespace lists: includes list must either contain '*' only, or a non-empty list of items
Environment: staging
Even if we dont pass the field includeNamespaces, its taking default to * and later on adding the new ns created
Velero version (use velero version): v1.16.1
Can someone help
Obseration:
Manually added namespaces are not being removed automatically, even if those namespaces no longer exist. However, for namespaces created after the schedule was patched or created, Velero seems to automatically handle both additions and deletions.
I have a EKS cluster with version 1.31
Can anyone please suggest how can we handle this?
this is our schedule
When new namespace comes up
Namespaces:
Included: *, new-ns
All reactions