[CPDEV-93171] - do not export kubernetes resources by default #553
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.
Description
Exported kubernetes objects in
backup
procedure are not used inrestore
procedure, but they take a lot of time to export (especially in big clusters). They can be helpful only for some manual changes, but they do not needed by default.Additionally now user can't skip kubernetes resources export in
procedure.yaml
, because it's not allowed in json schema. He can only skip whole task.And finally user can't export only specific resource because of the same reason. For example the following configuration is restricted:
Fixes # (issue)
Solution
backup_plan.kubernetes
not to load kubernetes resources by default;Test Cases
TestCase 1: default behavior
Test Configuration:
Steps:
Results:
TestCase 2: specific not-namespaced resource
Test Configuration:
Steps:
Results:
TestCase 3: specific namespaced resource (loaded for all namespaces)
Test Configuration:
Steps:
Results:
Checklist
Unit tests
Indicate new or changed unit tests and what they do, if any.