We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It will be useful if we can pass on the ingress operator the secretName on config.yaml.
secretName
config.yaml
At the moment it only creates a new cert from cert issuer like the cert-manager provider.
cert-manager
We have a case where we are using only wildcard domain and we have to edit manually each Ingress to use the same secretName like an example below.
apiVersion: openfaas.com/v1alpha2 kind: FunctionIngress metadata: name: nodeinfo namespace: openfaas spec: domain: "nodeinfo.myfaas.club" function: "nodeinfo" ingressType: "nginx" tls: enabled: true secretName: same-cert-secret
If it is a workaround like to automate this bit, it will very useful to know.
What do you think about it?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It will be useful if we can pass on the ingress operator the
secretName
onconfig.yaml
.At the moment it only creates a new cert from cert issuer like the
cert-manager
provider.We have a case where we are using only wildcard domain and we have to edit manually each Ingress to use the same
secretName
like an example below.If it is a workaround like to automate this bit, it will very useful to know.
What do you think about it?
The text was updated successfully, but these errors were encountered: