search

lsst-sqre / strimzi-registry-operator

A Kubernetes Operator for running the Confluent Schema Registry with a Strimzi-based Kafka cluster
MIT License
79 stars 16 forks source link

Operator deployed always in the `default` namespace #94

Closed darkwings closed 1 year ago

darkwings commented 1 year ago

I'm trying to deploy the operator in a dedicated namespace but, either via helm or Kustomize, the operator is installed in the default namespace.

Helm

With helm, I tried

helm install lsstsqre/strimzi-registry-operator --name ssr --set clusterNamespace=kafka,clusterName=my-cluster

Kustomize

With Kustomize I tried to follow the instructions of the README and apply the patch but the operator is always deployed in the default namespace, not in the one I want.

This was my process. I created a patch folder in which I added kustomization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - github.com/lsst-sqre/strimzi-registry-operator.git//manifests?ref=0.5.0

patches:
  - strimzi-registry-operator-deployment.yaml

and strimzi-registry-operator-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: strimzi-registry-operator
spec:
  template:
    spec:
      containers:
        - name: operator
          env:
            - name: SSR_CLUSTER_NAME
              value: my-cluster
            - name: SSR_NAMESPACE
              value: kafka

Then I apply the configuration with the command

kctl apply -k patch