mayadata-io / mayadata-io/oep-e2e

Not able to figure cluster information from the names

Open
#711 2 comments 0 reactions 1 assignee View on GitHub

@harshshekhar15 is already working on this.

Since Jun 22, 2020.

blocker future
Dominant language
Python
Stars
6
Forks
10
PR merge metrics
No merged PRs in 30d

Description

*** System restart required ***
Last login: Mon Jun 22 10:50:52 2020 from 49.37.202.34
oep@rack2:~$ 
oep@rack2:~$ kubectl get no
NAME              STATUS   ROLES               AGE   VERSION
rancher3-master   Ready    controlplane,etcd   84d   v1.15.9
rancher3-node1    Ready    worker              84d   v1.15.9
rancher3-node2    Ready    worker              84d   v1.15.9
rancher3-node3    Ready    worker              84d   v1.15.9
oep@rack2:~$ 
oep@rack2:~$ export KUBECONFIG=~/.kube/cluster2_config
oep@rack2:~$ kubectl get no
NAME                 STATUS   ROLES               AGE   VERSION
oep-rancher-master   Ready    controlplane,etcd   65d   v1.15.11
oep-rancher-node1    Ready    worker              65d   v1.15.11
oep-rancher-node2    Ready    worker              65d   v1.15.11
oep-rancher-node3    Ready    worker              65d   v1.15.11
oep-rancher-node4    Ready    worker              65d   v1.15.11
oep-rancher-node5    Ready    worker              65d   v1.15.11
oep@rack2:~$ 
oep@rack2:~$ export KUBECONFIG=~/.kube/cluster3_config
oep@rack2:~$ 
oep@rack2:~$ 
oep@rack2:~$ kubectl get no
NAME                 STATUS   ROLES               AGE   VERSION
rancher-c3-master    Ready    controlplane,etcd   40d   v1.15.11
rancher-c3-worker1   Ready    worker              40d   v1.15.11
rancher-c3-worker2   Ready    worker              40d   v1.15.11
rancher-c3-worker3   Ready    worker              40d   v1.15.11
rancher-c3-worker4   Ready    worker              40d   v1.15.11
rancher-c3-worker5   Ready    worker              40d   v1.15.11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.