ansible / ansible/eda-server-operator
minikube login url missing
- Dominant language
- Jinja
- Stars
- 45
- Forks
- 41
- Avg merge
- 2d
- Merged PRs (30d)
- 1
Description
minikube service list
|----------------------------|--------------------------------------------------------|--------------|---------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|----------------------------|--------------------------------------------------------|--------------|---------------------------|
| ansible-awx | ansible-awx-postgres-15 | No node port | |
| ansible-awx | ansible-awx-service | http/80 | http://192.168.49.2:32550 |
| ansible-awx | awx-operator-controller-manager-metrics-service | No node port | |
| default | kubernetes | No node port | |
| eda-server-operator-system | eda-server-operator-controller-manager-metrics-service | No node port | |
| ingress-nginx | ingress-nginx-controller | http/80 | http://192.168.49.2:31512 |
| | | https/443 | http://192.168.49.2:31678 |
| ingress-nginx | ingress-nginx-controller-admission | No node port | |
| kube-system | kube-dns | No node port | |
|----------------------------|--------------------------------------------------------|--------------|---------------------------|
minikube service -n eda-server-operator-system eda-server-operator-controller-manager-metrics-service --url
😿 service eda-server-operator-system/eda-server-operator-controller-manager-metrics-service has no node port
❗ Services [eda-server-operator-system/eda-server-operator-controller-manager-metrics-service] have type "ClusterIP" not meant to be exposed, however for local development minikube allows you to access this !
minikube service -n eda-server-operator-system eda-server-operator-controller-manager-metrics-service --url
😿 service eda-server-operator-system/eda-server-operator-controller-manager-metrics-service has no node port
❗ Services [eda-server-operator-system/eda-server-operator-controller-manager-metrics-service] have type "ClusterIP" not meant to be exposed, however for local development minikube allows you to access this !
[novaprime@HPE-5CG2165SG6 ~]$ minikube service -n eda-server-operator-system eda-server-operator-controller-manager-metrics-service
|----------------------------|--------------------------------------------------------|-------------|--------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|----------------------------|--------------------------------------------------------|-------------|--------------|
| eda-server-operator-system | eda-server-operator-controller-manager-metrics-service | | No node port |
|----------------------------|--------------------------------------------------------|-------------|--------------|
😿 service eda-server-operator-system/eda-server-operator-controller-manager-metrics-service has no node port
❗ Services [eda-server-operator-system/eda-server-operator-controller-manager-metrics-service] have type "ClusterIP" not meant to be exposed, however for local development minikube allows you to access this !
🏃 Starting tunnel for service eda-server-operator-controller-manager-metrics-service.
|----------------------------|--------------------------------------------------------|-------------|------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|----------------------------|--------------------------------------------------------|-------------|------------------------|
| eda-server-operator-system | eda-server-operator-controller-manager-metrics-service | | http://127.0.0.1:35739 |
|----------------------------|--------------------------------------------------------|-------------|------------------------|
🎉 Opening service eda-server-operator-system/eda-server-operator-controller-manager-metrics-service in default browser...
/usr/bin/xdg-open: line 881: www-browser: command not found
/usr/bin/xdg-open: line 881: links2: command not found
/usr/bin/xdg-open: line 881: elinks: command not found
/usr/bin/xdg-open: line 881: links: command not found
Looking up 127.0.0.1:35739
Making HTTP connection to 127.0.0.1:35739
Sending HTTP request.
when i login to 127.0.0.1:35739 , i get unauthorized, what am i missing?
Contributor guide
Research direction
Start by reproducing the shown `minikube service ... --url` and `minikube service ...` commands for the ClusterIP metrics service, then inspect the resulting tunnel URL and unauthorized response. Determine whether the missing login URL or authentication behavior is in the operator or Minikube; done means the expected access behavior and any required credentials or configuration are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100