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

Cert Manager needs to be updated. IngressClassName incompatibility. #253

Open
mehmetaydogduu opened this issue Jan 6, 2024 · 2 comments

Comments

@mehmetaydogduu
Copy link

I lost whole day with that. Certs aren't work because auto created ingress by cert-manager is not functional. Old annotation kubernetes.io/ingress.class doesn't work anymore. According to the docs, The field ingressClassName was added in cert-manager 1.12., so we need to upgrade to at least 1.12 to get rid of the issue.

MicroK8S 1.28.3:
microk8s kubectl cert-manager version

Client Version: util.Version{GitVersion:"v1.12.7", GitCommit:"6d7629ba42b946978e3baaa75348c851f7ef9134", GitTreeState:"", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: &versionchecker.Version{Detected:"v1.8.0", Sources:map[string]string{"crdLabelVersion":"v1.8.0"}}

As we can see MicroK8S Addon doesn't have ingressClassName property. HTTP01 check is failing.

@cnu80
Copy link

cnu80 commented Jan 14, 2024

Please update cert-manager. With this version, it is not possible to use an onprem acme like step-ca. The option: caBundle is missing.

@cnu80
Copy link

cnu80 commented Jan 17, 2024

I tested cert-manager with the official installation instruction and microk8s. I used the helm option and configured an acme issuer with my onprem acme ca. (step-ca).

My configuration:

  • single node microk8s v1.28
  • cert-manager v1.13.3
  • step-ca

nginx-ingress with tls is working out of the box.

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

2 participants