Test Cluster Configuration: Difference between revisions

From WilliamsNet Wiki
Jump to navigation Jump to search
mNo edit summary
Line 30: Line 30:


<pre>
<pre>
kubeadm join 10.0.0.168:6443 --token t1a0n9.3ct5og3va5q3kdbo \
kubeadm join 10.0.0.189:6443 --token eqgxme.uvyfullc4bqk9i8c \
     --discovery-token-ca-cert-hash sha256:7bcbe8b669241607c18c7cf1ca7a96d9de64be02d9df734b0fca46c4efd419cb \
     --discovery-token-ca-cert-hash sha256:31a1f3b9db02971e3c78176bcae74f15afa09e6e2a7df687ecc44654eb31a154 \
     --ignore-preflight-errors Swap --node-name=`hostname -s`
     --ignore-preflight-errors Swap --node-name=`hostname -s`
</pre>
</pre>

Revision as of 17:52, 8 August 2020

These packages can be installed as needed to provide functionality for the test cluster. It is expected that the Test Cluster will be destroyed and re-created as needed to test configurations and processes/procedures.

Scripts & config files are checked into gitlab under the Kubernetes group project listed.

activity gitlab script/procedures/config IP hostname(s)
NVIDIA device plugin https://github.com/NVIDIA/k8s-device-plugin

Dashboard Token

Obtain the current dashboard token with this command:

kubectl describe secrets \
  `kubectl get secrets | awk '/k8dash-sa/ {print $1}'` \
  | awk '/token:/ {print $2}'

The current Test cluster dashboard token is:

eyJhbGciOiJSUzI1NiIsImtpZCI6IjFvRzRMZWFiR0hXSVUybmc0dU5OYnhrOVBuaUJUS0VmUG9lV0RGVGZ0Y00ifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Ims4ZGFzaC1zYS10b2tlbi1tZndtaCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrOGRhc2gtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhMjI5YWY5Zi1hNGIxLTRjYTAtYjBkMi03OTQyYjU1OWQ0ZDAiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDprOGRhc2gtc2EifQ.oQM_X8HyHa7kYHLp2b8yCYrPR7kSiJlSx1iOgnn2CNub8cT3TIrgU4LI4vOUPxCy1JaJ2mjHf1ZibupzO9FofuYv8iTFVFWIl5lV9cB1XQ7ungNaMCnrCuSZR1QrAhmEEO0070wcvL8xo2xb6q1ZOs_Hx9bv4MWn9KjAYu3AmDv1Z-jqLeWijE9mTuKJyZ5t9yFwTiF5EuHeLI1QpS80F534qVqkiouvP3_FMV9k1Z95raD3Q2JakzOZCb67tfPXq7jxOGsA19h9BpKL98qj0H8iv97cHvlBzAM9Q5Ljx8k9VIJzv4Q-r9CU5SzEHN1E7A2i3Ro5tL57Q_2Rrz39kQ

Storage

The test cluster does not (by default) have any required filesystems, but systems that require access to both the development filesystem (/workspace) and the production filesystem (/shared) can mount them via ceph or NFS as appropriate.

Kubernetes Node Join Command

kubeadm join 10.0.0.189:6443 --token eqgxme.uvyfullc4bqk9i8c \
    --discovery-token-ca-cert-hash sha256:31a1f3b9db02971e3c78176bcae74f15afa09e6e2a7df687ecc44654eb31a154 \
    --ignore-preflight-errors Swap --node-name=`hostname -s`