You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For my homelab I'm setting up a K3S cluster on a few Raspberry Pi's.
have the nginx-ingress installed
have the cert-manager installed
have a working example where I deploy a basic 'hello world' website with Letsencrypt certificates
Since I would like a more graphical overview of everything regarding resources and such, the dashboard seemed a next logical step
This seems to create 3 pods (web, api and metrics-scraper) What I can't seem to figure out here is how to configure an ingress so I can access the web-interface.
To be honest it might be that I am mixing up a few things. In my search on the internet I originally deployed with another version (2.XX something) where I had to apply a separate ingress-nginx, RBAC service account, .... This lead me to the login page but I was never able to activate the Letsencrypt certificates. I must say here that the previous deploys never generated 3 pods (so the api and scraper never showed up)
If my understanding is correct it seems that now in the version I try to deploy all those settings are gathered into 1 single yaml file. So first of all is that correct?
And then if it is can somebody shed some light on what to change in that yaml so that upon the deploy, the letsencrypt cluster-issuer kicks in, does his certificate magic and nginx-ingress is created.
Currently if I go to the webaddress I have the certificates, but a 503 Service Temporarily Unavailable. I can link that to a ssl passthrough setting in my nginx-ingress config (a config which I might no longer need if the above assumption is correct)
If not I would be glad to share the ingress config, but I'll leave it out for now to limit clutter.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
New to Kubernetes so bear with me :-)
For my homelab I'm setting up a K3S cluster on a few Raspberry Pi's.
have the nginx-ingress installed
have the cert-manager installed
have a working example where I deploy a basic 'hello world' website with Letsencrypt certificates
Since I would like a more graphical overview of everything regarding resources and such, the dashboard seemed a next logical step
Deployed it with:
This seems to create 3 pods (web, api and metrics-scraper) What I can't seem to figure out here is how to configure an ingress so I can access the web-interface.
To be honest it might be that I am mixing up a few things. In my search on the internet I originally deployed with another version (2.XX something) where I had to apply a separate ingress-nginx, RBAC service account, .... This lead me to the login page but I was never able to activate the Letsencrypt certificates. I must say here that the previous deploys never generated 3 pods (so the api and scraper never showed up)
If my understanding is correct it seems that now in the version I try to deploy all those settings are gathered into 1 single yaml file. So first of all is that correct?
And then if it is can somebody shed some light on what to change in that yaml so that upon the deploy, the letsencrypt cluster-issuer kicks in, does his certificate magic and nginx-ingress is created.
Currently if I go to the webaddress I have the certificates, but a 503 Service Temporarily Unavailable. I can link that to a ssl passthrough setting in my nginx-ingress config (a config which I might no longer need if the above assumption is correct)
If not I would be glad to share the ingress config, but I'll leave it out for now to limit clutter.
Thanks in advance for the read and help.
regards,
Koen
Beta Was this translation helpful? Give feedback.
All reactions