We don't currently have a way to do this. Consider this custom resource that is the parent:
apiVersion: v1alpha1
kind: WebApp
metadata:
name: intance-x
spec:
env: dev
Suppose we want to deploy n number of these webapps to a single cluster - each into their own namespace. Suppose we shove this resource into operator-builder...
We don't currently have a way to do this. Consider this custom resource that is the parent:
Suppose we want to deploy n number of these webapps to a single cluster - each into their own namespace. Suppose we shove this resource into operator-builder...
So, given the WebApp resource above, this would produce a namespace with name
webapp-instance-x
.And if a WebApp with name
instance-y
was created the result would be a namespace calledwebapp-instance-y
.