Test Cluster Configuration: Difference between revisions

From WilliamsNet Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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.
The Development cluster is deployed using [[K3s - Kubernetes Simplified]].
 
These packages form the basic functionality of the development cluster.  The packages need to preserve the IP address assignments.  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.
Scripts & config files are checked into gitlab under the Kubernetes group project listed.
Line 6: Line 8:
|-
|-
! activity !! gitlab !! script/procedures/config !! IP !! hostname(s)
! activity !! gitlab !! script/procedures/config !! IP !! hostname(s)
|-
| K8Dash Dashboard || k8s-admin || || 10.0.0.200 ||
|-
|-
| NVIDIA device plugin || || https://github.com/NVIDIA/k8s-device-plugin || ||
| NVIDIA device plugin || || https://github.com/NVIDIA/k8s-device-plugin || ||
|-
|
|-
|
|}
|}


Line 22: Line 22:
The current Test cluster dashboard token is:
The current Test cluster dashboard token is:


  eyJhbGciOiJSUzI1NiIsImtpZCI6IjFvRzRMZWFiR0hXSVUybmc0dU5OYnhrOVBuaUJUS0VmUG9lV0RGVGZ0Y00ifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Ims4ZGFzaC1zYS10b2tlbi1tZndtaCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrOGRhc2gtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhMjI5YWY5Zi1hNGIxLTRjYTAtYjBkMi03OTQyYjU1OWQ0ZDAiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDprOGRhc2gtc2EifQ.oQM_X8HyHa7kYHLp2b8yCYrPR7kSiJlSx1iOgnn2CNub8cT3TIrgU4LI4vOUPxCy1JaJ2mjHf1ZibupzO9FofuYv8iTFVFWIl5lV9cB1XQ7ungNaMCnrCuSZR1QrAhmEEO0070wcvL8xo2xb6q1ZOs_Hx9bv4MWn9KjAYu3AmDv1Z-jqLeWijE9mTuKJyZ5t9yFwTiF5EuHeLI1QpS80F534qVqkiouvP3_FMV9k1Z95raD3Q2JakzOZCb67tfPXq7jxOGsA19h9BpKL98qj0H8iv97cHvlBzAM9Q5Ljx8k9VIJzv4Q-r9CU5SzEHN1E7A2i3Ro5tL57Q_2Rrz39kQ
  eyJhbGciOiJSUzI1NiIsImtpZCI6IktfVTJCLU9xVG1zRmVOTWF5dTBZcWNSWlVzQ2t0RlFaS0o4VEFmcUl2VE0ifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Ims4ZGFzaC1zYS10b2tlbi16czJkNCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrOGRhc2gtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiIzYzg5OGUyMC0wNGFmLTQ5YTItYWJmYS01MTcwOGE5OGYxMTUiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDprOGRhc2gtc2EifQ.dkxXHdHFrwJ2krjd3krFHFM5aAMLIRvDH8cFv9TzaCRgolnlC-xI12rfLXnyig-WKWdjzJSUr-_bh60CRmzONBzXWg9NEY_LYJRIKszkGOGADFPNuCn-ugbfq5LqvEh5H2LWsnzWx49YUQeHNeVjipRKl9xLSqvmK2UfmvffJYFoxcnuky4xC-X4qv8aYzXSF9D9hPR7NYd8XdFv3NZsPOOkhwjBpKZi20FEKLeuNNJq88Xdewh1mGLkCyeZuSFpNV_eawOJSO4A2NpT5hCmzleq4XDBNMZUlgALpTqhNd5kGJnke6xt8WIt2EP3HarRkq1wLLu5TIR5oB2xQ2qR8w


=== Storage ===
=== 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.
The test cluster does not (by default) have any required filesystems, but systems that require access to both the development filesystem ('''/work''') and the production filesystem ('''/shared''') can mount them via NFS as appropriate.
 
=== Kubernetes Node Join Command ===


<pre>
There is a test ceph cluster hosted on pro5 that is available through the rook installation, but (at this time) no filesystems are hosted on that cluster.
kubeadm join 10.0.0.168:6443 --token t1a0n9.3ct5og3va5q3kdbo \
    --discovery-token-ca-cert-hash sha256:7bcbe8b669241607c18c7cf1ca7a96d9de64be02d9df734b0fca46c4efd419cb \
    --ignore-preflight-errors Swap --node-name=`hostname -s`
</pre>

Latest revision as of 22:44, 15 August 2021

The Development cluster is deployed using K3s - Kubernetes Simplified.

These packages form the basic functionality of the development cluster. The packages need to preserve the IP address assignments. 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)
K8Dash Dashboard k8s-admin 10.0.0.200
NVIDIA device plugin https://github.com/NVIDIA/k8s-device-plugin

Dashboard Token[edit]

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: 

eyJhbGciOiJSUzI1NiIsImtpZCI6IktfVTJCLU9xVG1zRmVOTWF5dTBZcWNSWlVzQ2t0RlFaS0o4VEFmcUl2VE0ifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Ims4ZGFzaC1zYS10b2tlbi16czJkNCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrOGRhc2gtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiIzYzg5OGUyMC0wNGFmLTQ5YTItYWJmYS01MTcwOGE5OGYxMTUiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDprOGRhc2gtc2EifQ.dkxXHdHFrwJ2krjd3krFHFM5aAMLIRvDH8cFv9TzaCRgolnlC-xI12rfLXnyig-WKWdjzJSUr-_bh60CRmzONBzXWg9NEY_LYJRIKszkGOGADFPNuCn-ugbfq5LqvEh5H2LWsnzWx49YUQeHNeVjipRKl9xLSqvmK2UfmvffJYFoxcnuky4xC-X4qv8aYzXSF9D9hPR7NYd8XdFv3NZsPOOkhwjBpKZi20FEKLeuNNJq88Xdewh1mGLkCyeZuSFpNV_eawOJSO4A2NpT5hCmzleq4XDBNMZUlgALpTqhNd5kGJnke6xt8WIt2EP3HarRkq1wLLu5TIR5oB2xQ2qR8w

Storage[edit]

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

There is a test ceph cluster hosted on pro5 that is available through the rook installation, but (at this time) no filesystems are hosted on that cluster.

Retrieved from "http://wiki.williams-net.org/index.php?title=Test_Cluster_Configuration&oldid=504"