Deploy nebula operator with ArgoCD

[robcinko]

Hi,

we want to deploy nebula operator with CD tool ArgoCD, but we have a problem with specify k8s namespace. In values.yaml file we cant define namespace. Do you have any suggestions how to solve this problem ?

Thank you

[wey-gu]

@MegaByte875 could you plz help advise on this?

[robcinko]

Maybe it can be solved by edit {{ .Values.namespace | default .Release.Namespace }} in _helpers.tpl file.

[wey-gu]

Did you try changing the metadata.namespace from its CRD as follow?

apiVersion: apps.nebula-graph.io/v1alpha1
kind: NebulaCluster
metadata:
  name: nebula
  namespace: default # <-----------
spec:
  graphd:

[robcinko]

Yes, but this what you send is for nebula-cluster for which we can set namespace.
We have a problem with nebula-operator because the only way how to deploy operator is with Helm. This Helm chart is imported into ArgoCD tool and only changes we can do are in values.yaml file, but in this file namespace is not templated :(

[wey-gu]

If I understood it correctly, you need the nebula-operator(control plan of nebulacluster, the operator itself) to be running on any namespace other than the default nebula-operator-system, right?

If that is the case, the equivalent call of --namespace in helm CLI in ArgoCD will do the job.

$ helm install nebula-operator nebula-operator/nebula-operator --namespace=nebula-operator-system --version=${chart_version}

ref:

• https://github.com/vesoft-inc/nebula-operator/blob/master/doc/user/install_guide.md
• https://github.com/vesoft-inc/nebula-operator/blob/master/doc/user/nebula_cluster_helm_guide.md

[MegaByte875]

@robcinko The yaml below is argocd applicaton, the field 'namespace' is specified for deploy the chart

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: sealed-secrets
  namespace: argocd
spec:
  project: default
  source:
    chart: sealed-secrets
    repoURL: https://bitnami-labs.github.io/sealed-secrets
    targetRevision: 1.16.1
    helm:
      releaseName: sealed-secrets
  destination:
    server: "https://kubernetes.default.svc"
    namespace: kubeseal

[robcinko]

Thank you @wey-gu @MegaByte875 I'm going to try it :)

[MegaByte875]

I will close the issue, please re-open it if you have other questions.