[jira] [Comment Edited] (BIGTOP-3242) Instructions on configuring kubectl for local k8s cluster

["YoungWoo Kim (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950683#comment-16950683 ] 

YoungWoo Kim edited comment on BIGTOP-3242 at 10/14/19 3:11 AM:
----------------------------------------------------------------

I'll add simple instructions into README.md for configuring kubectl.....

```
k8s-1$ mkdir -p ~/.kube
k8s-1$ sudo cp /etc/kubernetes/admin.conf .kube/config
k8s-1$ sudo chown -R vagrant:vagrant .kube

k8s-1$ kubectl cluster-info

Kubernetes master is running at https://172.17.8.101:6443
coredns is running at https://172.17.8.101:6443/api/v1/namespaces/kube-system/services/coredns:dns/proxy
kubernetes-dashboard is running at https://172.17.8.101:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
```


was (Author: warwithin):
I'll add simple instructions into README.md for configuring kubectl.....

> Instructions on configuring kubectl for local k8s cluster
> ---------------------------------------------------------
>
>                 Key: BIGTOP-3242
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3242
>             Project: Bigtop
>          Issue Type: Sub-task
>            Reporter: YoungWoo Kim
>            Priority: Major
>
> If you up your local k8s cluster via kubespray, you need to configure kubectl to hacking k8s cluster.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)