Make KOS able to handle resources without namespaces #1114
Closed
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.
Sometimes customers need to deploy resources that are cluster-scoped, which do not have namespaces. Currently these resources result in a
kubectl get <kind> <name> -n
command being sent, which is invalid because the namespace argument-n
must have a value.This PR fixes this issue by filtering out the resources that are cluster-scoped. When we have cluster-scoped resources, we exclude them from the KOS and do not show them to the customer. Instead we note them down in the task log, and tell the customer that those are not checked against.
Assuming we are using this YAML which deploys a cluster-scoped resource:
Before
After