Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operator prevents passing extraArgs helm value #17

Open
auberta2 opened this issue Sep 15, 2020 · 3 comments
Open

Operator prevents passing extraArgs helm value #17

auberta2 opened this issue Sep 15, 2020 · 3 comments

Comments

@auberta2
Copy link

auberta2 commented Sep 15, 2020

I am facing a situation where I wanted to spin up CertManager resource to install your underlying helm chart with some specific extraArgs values like hereunder :

apiVersion: operator.cert-manager.io/v1alpha1
kind: CertManager
metadata:
  name: cert-manager
  namespace: openshift-operators
spec:
  extraArgs:
    - --dns01-recursive-nameservers-only
    - --dns01-recursive-nameservers=8.8.8.8:53,1.1.1.1:53

However, the extraArgs value is being ignored when the helm chart is being released because of the overrideValues for extraArgs[0] at the end of your watches.yaml file.

What would be your recommendation to easily pass such extra args to the cert-manager controller ?

@dustinmm80
Copy link

dustinmm80 commented Jul 7, 2021

We are also running into this issue trying to generate certificates for GitLab. Without the --dns01-recursive-nameservers flag we are are unable to use this operator in OpenShift.

@itewk
Copy link

itewk commented Jan 11, 2022

anyone find any workaround to this?

@gebhardtr
Copy link

In case anyone else ends up here from a related search: unsupportedConfigOverrides:

apiVersion: operator.openshift.io/v1alpha1
kind: CertManager
metadata:
  name: cluster
spec:
  managementState: "Managed"
  unsupportedConfigOverrides:
    controller:
      args:
        - "--dns01-recursive-nameservers=1.1.1.1:53"
        - "--dns01-recursive-nameservers-only"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants