can not get kube-apiserver from kube-dash

Bug #1712230 reported by jazeltq
6
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
Revision history for this message
yatin (yatinkarel) wrote :
Download full text (4.8 KiB)

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:-
[fedora@k8-vc5zg2qymq-0-jpvbtet27xsw-kube-master-tok35nrnl64w ~]$ kubectl logs --namespace kube-system kubernetes-dashboard-3203831700-vbp2f
Using HTTP port: 9090
Creating API server client for https://10.254.0.1:443
Successful initial request to the apiserver, version: v1.5.3
Creating in-cluster Heapster client
Using service account token for csrf signing
[fedora@k8-vc5zg2qymq-0-jpvbtet27xsw-kube-master-tok35nrnl64w ~]$ kubectl describe po --namespace kube-system kubernetes-dashboard-3203831700-vbp2f
Name: kubernetes-dashboard-3203831700-vbp2f
Namespace: kube-system
Node: k8-dseyedlnyv-0-kgkosjcptyzi-kube-minion-nlyae2xbfbvq/10.0.0.11
Start Time: Wed, 16 Aug 2017 12:59:41 +0000
Labels: app=kubernetes-dashboard
  pod-template-hash=3203831700
Status: Running
IP: 10.100.54.2
Controllers: ReplicaSet/kubernetes-dashboard-3203831700
Containers:
  kubernetes-dashboard:
    Container ID: docker://be274fc94a344e1a2be792a376f595012e043b1789712572ac40a294e2a59070
    Image: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.1
    Image ID: docker-pullable://gcr.io/google_containers/kubernetes-dashboard-amd64@sha256:46a09eb9c611e625e7de3fcf325cf78e629d002e57dc80348e9b0638338206b5
    Port: 9090/TCP
    State: Running
      Started: Wed, 16 Aug 2017 13:00:36 +0000
    Ready: True
    Restart Count: 0
    Liveness: http-get http://:9090/ delay=30s timeout=30s period=10s #success=1 #failure=3
    Volume Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-zqthp (ro)
    Environment Variables: <none>
Conditions:
  Type Status
  Initialized True
  Ready True
  PodScheduled True
Volumes:
  default-token-zqthp:
    Type: Secret (a volume populated by a Secret)
    SecretName: default-token-zqthp
QoS Class: BestEffort
Tolerations: dedicated=master:Equal:NoSchedule
Events:
  FirstSeen LastSeen Count From SubObjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  3m 3m 1 {default-scheduler } Normal Scheduled Successfully assigned kubernetes-dashboard-3203831700-vbp2f to k8-dseyedlnyv-0-kgkosjcptyzi-kube-minion-nlyae2xbfbvq
  2m 2m 1 {kubelet k8-dseyedlnyv-0-kgkosjcptyzi-kube-minion-nlyae2xbfbvq} spec.containers{kubernetes-dashboard} Normal Pulling pulling image "gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.1"
  2m 2m 2 {kubelet k8-dseyedlnyv-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.
  2m 2m 1 {kubelet k8-dseyedlnyv-0-kgkosjcptyzi-kube-minion-nlyae2xbfbvq} spec.containers{kubernetes-dashboard} Normal Pulled Successfully pulled image "gcr.io/google_containers/kubernetes-dashboard-amd64:...

Read more...

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/494770
Reason: https://docs.openstack.org/doc-contrib-guide/writing-style/code-conventions.html

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.