Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I followed this tutorial: https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes
And it worked at first, I set it up for one domain I have, and also for a subdomain, all seems good. I needed, though, to add another domain and it doe snot seem to work. after following the tutorial, what I did is to go to the ingress for my websites and do like this:
code
annotations:
kubernetes.io/ingress.class: nginx
cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
tls:
- hosts:
- mydomain.com
- hello.mydomain.com
- my-SECOND-domain.com
- smething.my-SECOND-domain.com
secretName: hello-kubernetes-tls
but in the ingress_nginx_svc.yaml I have:
code
metadata:
annotations:
service.beta.kubernetes.io/do-loadbalancer-enable-proxy-protocol: 'true'
service.beta.kubernetes.io/do-loadbalancer-hostname: "mydomain.com"
Now I have my DNS records pointing to the external IP but for the my-SECOND-domain.com entries, when navigating to the page, I have an invalid certificate, chrome tells me that is using: FAKE acme certificate, while for the other domain the certificate is valid
009fd274aeae48f2bfbda6ef568676
Cloudstream Apk
Ruz
Ruz
Edward Sitarski
ebeecroft
dashan
34bcef38725b4e6eb5224ae028f17e
markatango
gouskova
Andrew J Montanus