Open r3k2 opened 3 years ago
@rsoika @sapkra @marner2 @pierreozoux Hello im stuck on this, anyone have any idea? I notice Address is empty. we using a load balancer on digital ocean could this be the cause that we need extra step?
ok I figure it out... this tutorial says to follow the ingress nginx already installed and such I did but what it does not say is that we need to link this jitsi role to "nginx class" so it picks it up:
metadata:
name: jitsi
namespace: jitsi
annotations:
kubernetes.io/ingress.class: "nginx" <-------------- THIS!!!
cert-manager.io/cluster-issuer: "letsencrypt-prod"
now is working and I am getting an ip on the jitsi role:
kubectl get ingress -n jitsi ░▒▓ ✔ at do-nyc3-jitsirocketchat ⎈ at 16:32:38
NAME CLASS HOSTS ADDRESS PORTS AGE
jitsi <none> vid1.example.com 159.xx.xx.xx 80, 443 22h
please update the steps so others wont get confused
@r3k2 you can update it also :) and help with your experience :)
@pierreozoux sure, I dont use github to much for PR's anymore just gitlab/sourcehut etc but I will see if I can do a PR later this evening.
@pierreozoux thanks for you feedback. I just updated the documentation according to your imput. Please make a short review:
Hello I been banging my head trying to get this to work. I have installed ingress-nginx following this since I am using digital ocean https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes After this is working I removed the echo1 and echo2 that it was used for testing.. I installed the kustomize from here following with details the examples.
when I do a kubectl describe certificate -A it shows the cert created. but I have two problems that may be related.
on the describe ingress
I changed the secret to get another cert from tls-jitsi to tls-prod-jitsi but still same issue.. also there is a missing backend error in that output...
any tips? Thanks