Open WK-Haneeth opened 1 week ago
Did you try http://kubero.localhost:80 ? 404 is at least an Nginx answer.
The debug looks very empty tough.
In case you are not running on a local host, point the DNS to the clusters public ip, and change the ingresss to this Domain.
Did you try http://kubero.localhost:80 ? 404 is at least an Nginx answer.
The debug looks very empty tough.
In case you are not running on a local host, point the DNS to the clusters public ip, and change the ingresss to this Domain.
Thank you for the quick reply, I am not running on localhost, it's a VM that I had set-up on a Proxmox Node and I just sshed into it. I just wanted to quickly try Kubero myself because the demo you had for it was read-only. Can I ask what you meant by changing the ingress to the domain?
Ingress works kind like an Apache Vhost.
So you will need a Domain pointing to your 172.16.xx.xx ip so the ingress can match the app. The ingress is configured in Kubero's CRD.
’’’ kubectl -n kubero kuberoes kubero ’’’
Find kubero.localhost and change it to your domain.
Add a DNS entry:
’’’ *.mydomain.com A 600 172.16.xx.xx ’’’
The wildcard comes handy when provisioning you apps.
/Written in my mobile phone 😬
Which component(s) is affected?
No response
Describe the bug
Installed kubectl and kind on a fresh VM, and followed the "Quickstart" guide from docs.kubero.dev, installed the binary through the installation script.
Followed the defaults from
kubero install
and passed my github token when asked for, the installation successfully finished but when I try to access the WebUI it results in an nginx 404.Any help is appreciated, thank you for your timeQ
Steps to reproduce
kubectl
&kind
to set kubero on a local machinecurl -fsSL get.kubero.dev | bash
kubero install
and verify that both the prerequisites are present and detected.Expected behavior
A Login page upon connection
Screenshots
Additional information
No response
Debug information