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
{{ message }}
This repository was archived by the owner on Apr 25, 2024. It is now read-only.
At the moment it is possible to define cluster scoped resources in a template and a TemplateInstance in a namespace that deploys these resources. This can lead to problematic behavior, since two templateinstances in two different namespaces that would point to the same template (which is allowed and encouraged) would override the clusterresource of each other and is basically currently the result of some kind of undefined behavior.
Hence, we should restrict and check during deployment of a TemplateInstance if a given resource is namespaced or cluster scoped and let the TemplateInstance fail if it is a cluster scoped resource.
The text was updated successfully, but these errors were encountered:
FabianKramm
changed the title
TemplateInstance: ensure only namespaced resources can be deployed
TemplateInstance: fail if non namespaced scope resource should be deployed
Feb 14, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment it is possible to define cluster scoped resources in a template and a TemplateInstance in a namespace that deploys these resources. This can lead to problematic behavior, since two templateinstances in two different namespaces that would point to the same template (which is allowed and encouraged) would override the clusterresource of each other and is basically currently the result of some kind of undefined behavior.
Hence, we should restrict and check during deployment of a TemplateInstance if a given resource is namespaced or cluster scoped and let the TemplateInstance fail if it is a cluster scoped resource.
The text was updated successfully, but these errors were encountered: