Deploy ECK to a Single Namespace


I would like to deploy ECK within a single namespace, but it is not clear to me how to do so after reading

Not sure exactly how to specify thoes options. Can someone give me a quick example?


@nobound you can set them as args or env vars in the operator stateful set. For example here:

Thanks for the reply.

Does it mean I should not use the

I should just customize the template yaml file to deploy the ECK. Right?

I follow the instructions ( to generate yaml file for namespace operator that manages resources in a given namespace. NAMESPACE=test MANAGED_NAMESPACE=test make generate-namespace > namespace.yaml

Is that right?


Does it mean I should not use the

The easiest way would be to use that, but edit the args first. Sorry for the confusion, I was just linking the template as an example of where the args are in the all-in-one. So around line 3024 in the all-in-one you can add them either as args or environment variables. Does that make help?

Thanks for the clarification.
I sort of figure out what you meant as I am poking around those configuration templates.

@Anya_Sabo I found my way here in search of the same thing. I'm a bit confused by the terminology in the docs. Is it possible to deploy everything(ECK and CRDs) within a single namespace? Working on a huge multi-tenant system and I'm limited to what I can deploy in my namespace.

@supermancc03 I think (not tested in a while) this is possible but requires some tweaking.
Basically you can change the ClusterRole and ClusterRoleBinding from the all-in-one manifests to their corresponding Role and RoleBinding translations, with your desired namespace.
Then, you can patch the operator StatefulSet manifest to be deployed in the desired namespace. Also make sure the --namespaces flag of the operator cmd matches the namespace you want the operator to work with (probably the same it's deployed in).

However, you can only deploy the CRDs cluster-wide, AFAIK it is not possible to limit a CustomResourceDefinition resource to a particular namespace. And it looks it's not going to be supported anytime soon.

I understand this feels a bit hacky. I'm opening an issue to track this so we can come up with an easier way to generate your own flavor of the manifests:

1 Like