Open indiealexh opened 1 year ago
I think you should be able to use any namespace. However given cert-manager was installed by RedHat operator, perhaps it does something to prevent other installations in the same namespace?
Did you install the RedHat or the Community cert-manager marketplace offering?
Did you install the RedHat or the Community cert-manager marketplace offering?
It was labeled as community, but seeing as how it comes from a red hat mirror I don't know how community it actually is.
Is there a way to get more logs out to understand why it died?
@indiealexh Is cert-manager really installed in the openshift-operators
namespace in your OpenShift cluster? It seems a bit strange. In our OpenShift cluster this namespace typically contains operators (for operators). So cert-manager-operator (an operator provisioning cert-manager) would be installed there, but not cert-manager.
/priority awaiting-more-evidence
@indiealexh Is cert-manager really installed in the
openshift-operators
namespace in your OpenShift cluster?
Yes, it was the default location suggested by the Openshift UI.
Cert Manager Instance:
Cert Manager Operator Subscription
Thanks! Yes, it seems like OpenShift recommends openshift-operators
namespace for cluster-scoped operators, ref. OpenShift docs.
Are you able to reproduce the trust-manager installation issue? To me, it seems like Helm is bugging out here. Maybe you can add the I see you already did. 🤔 --debug
flag to the Helm command to get more output?
Which version of Helm are you using?
I am attempting to install trust-manager into openshift with an existing cert-manager install that was installed via the operator hub.
Despite already having cert-manager, so I need to deploy an instance into a cert-manager namespace like the docs state, or should I be able to use the one I have?