-
Notifications
You must be signed in to change notification settings - Fork 37
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
kustomize example not working #13
Comments
@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:
now is working and I am getting an ip on the jitsi role:
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
The text was updated successfully, but these errors were encountered: