can not get kube-apiserver from kube-dash
Bug #1712230 reported by
jazeltq
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
In Progress
|
Undecided
|
jazeltq |
Bug Description
Right now, if we disable tls, the kube-dashboard pod may be scheduled to
minion, and the there is no args to point out where is the kube-apiserver.
So access ui will be fault. We should add them
Changed in magnum: | |
assignee: | nobody → jazeltq (jazeltq-k) |
status: | New → In Progress |
To post a comment you must log in.
Just for tracking the info and discussion on https:/ /review. openstack. org/#/c/ 491663/ :-
I too checked, the issue is only with --tls-disabled.
With tls-disabled --apiserver-host argument need to be passed, me neither know about auto discover, attaching kubectl log for dashboard with apiserver-host and without apiserver-host:-
with apiserver-host and tls-disabled:- k8-vc5zg2qymq- 0-jpvbtet27xsw- kube-master- tok35nrnl64w ~]$ kubectl logs --namespace kube-system kubernetes- dashboard- 3203831700- vbp2f /10.254. 0.1:443 k8-vc5zg2qymq- 0-jpvbtet27xsw- kube-master- tok35nrnl64w ~]$ kubectl describe po --namespace kube-system kubernetes- dashboard- 3203831700- vbp2f dashboard- 3203831700- vbp2f 0-kgkosjcptyzi- kube-minion- nlyae2xbfbvq/ 10.0.0. 11 dashboard hash=3203831700 kubernetes- dashboard- 3203831700 dashboard: //be274fc94a344 e1a2be792a376f5 95012e043b17897 12572ac40a294e2 a59070 google_ containers/ kubernetes- dashboard- amd64:v1. 5.1 pullable: //gcr.io/ google_ containers/ kubernetes- dashboard- amd64@sha256: 46a09eb9c611e62 5e7de3fcf325cf7 8e629d002e57dc8 0348e9b06383382 06b5 :9090/ delay=30s timeout=30s period=10s #success=1 #failure=3 var/run/ secrets/ kubernetes. io/serviceaccou nt from default-token-zqthp (ro) token-zqthp: master: Equal:NoSchedul e dashboard- 3203831700- vbp2f to k8-dseyedlnyv- 0-kgkosjcptyzi- kube-minion- nlyae2xbfbvq 0-kgkosjcptyzi- kube-minion- nlyae2xbfbvq} spec.containers {kubernetes- dashboard} Normal Pulling pulling image "gcr.io/ google_ containers/ kubernetes- dashboard- amd64:v1. 5.1" 0-kgkosjcptyzi- kube-minion- nlyae2xbfbvq} Warning MissingClusterDNS kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy. 0-kgkosjcptyzi- kube-minion- nlyae2xbfbvq} spec.containers {kubernetes- dashboard} Normal Pulled Successfully pulled image "gcr.io/ google_ containers/ kubernetes- dashboard- amd64:. ..
[fedora@
Using HTTP port: 9090
Creating API server client for https:/
Successful initial request to the apiserver, version: v1.5.3
Creating in-cluster Heapster client
Using service account token for csrf signing
[fedora@
Name: kubernetes-
Namespace: kube-system
Node: k8-dseyedlnyv-
Start Time: Wed, 16 Aug 2017 12:59:41 +0000
Labels: app=kubernetes-
pod-template-
Status: Running
IP: 10.100.54.2
Controllers: ReplicaSet/
Containers:
kubernetes-
Container ID: docker:
Image: gcr.io/
Image ID: docker-
Port: 9090/TCP
State: Running
Started: Wed, 16 Aug 2017 13:00:36 +0000
Ready: True
Restart Count: 0
Liveness: http-get http://
Volume Mounts:
/
Environment Variables: <none>
Conditions:
Type Status
Initialized True
Ready True
PodScheduled True
Volumes:
default-
Type: Secret (a volume populated by a Secret)
SecretName: default-token-zqthp
QoS Class: BestEffort
Tolerations: dedicated=
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
3m 3m 1 {default-scheduler } Normal Scheduled Successfully assigned kubernetes-
2m 2m 1 {kubelet k8-dseyedlnyv-
2m 2m 2 {kubelet k8-dseyedlnyv-
2m 2m 1 {kubelet k8-dseyedlnyv-