replicatedhq
Feature request: Split base to three categories
Expected behavior
Split base automatically into three categories to avoid race condition when creating multiple resources sets in the same cluster, e.g. one for dev, another for test and etc.
singleton
The resource is unique in a cluster and hold a dedicated name that should not be prefixed or suffixed. For example CustomResourceDefinition
cluster-scope
Resources not belong to any namespace, e.g. ClusterRole, ClusterRoleBinding, Namespace.
The only way to create multiple instance of such resources is applying name suffix or prefix.
namespace-scope
Resources created in specified namespace and multiple instances with the same name can co-exists in the cluster by allocating into different namespaces.
Actual behavior
All resources in a single base directory.
Information
- Ship version: 0.37.1
- Docker version: N/A
- Command line run: N/A
Steps to reproduce the behavior
N/A
This is an interesting request -- thank you! The different levels of namespace/cluster scoping definitely make sense to me. I know there's all kinds of Transformer tweaks and fixes that are in flux over in github.com/kubernetes-sigs/kustomoize. We'll keep an eye on the Kustomize issue as well and keep thinking about the best way to address. this.
