Test Cluster Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 22: | Line 22: | ||
The current Test cluster dashboard token is: | The current Test cluster dashboard token is: | ||
eyJhbGciOiJSUzI1NiIsImtpZCI6Iml3aDAxeDEtNkkxWnNQSHViMEszTlBDSnROcGk4MGY0MURiZFpaQ3dwQjgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Ims4ZGFzaC1zYS10b2tlbi02eGs3NSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrOGRhc2gtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhZTgzZDM0MC1hMWY0LTQ2ZGQtOWJhMi1mZjI0NDRmNzdhMTYiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDprOGRhc2gtc2EifQ.Ap6DbLKX-eyaN2boWLkxsAWZJTx954uk63AjAF4o001kRdVzVzo2g8OazoNlALy-rlnH1kE3CN50YofdBG5onbuB9TOUdWwuAAnesY1ZzCOmP0R3C_uVypTC4n6nhVsENawmIsB-kJXQDXS5TSu14vG6kxpVUuJjTrh7_2lV0Cm1L5D9RhxMN8mw53k3pLUBZwcJnnYKRnq7a44cJb2hoDWhQoUYbQLO42ZynZCpnCBU4Ap5SCsFmxEJ6qWGBCEehzkyp9gDmmFsFYfudq_2kDmQsflaK9PNfRURYtc5EoslDhSDYONx6oMX2cMy7hWG062Z-7FLF20RAGyrBeRZ5g | |||
=== Storage === | === Storage === | ||
Revision as of 19:59, 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:
eyJhbGciOiJSUzI1NiIsImtpZCI6Iml3aDAxeDEtNkkxWnNQSHViMEszTlBDSnROcGk4MGY0MURiZFpaQ3dwQjgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Ims4ZGFzaC1zYS10b2tlbi02eGs3NSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrOGRhc2gtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhZTgzZDM0MC1hMWY0LTQ2ZGQtOWJhMi1mZjI0NDRmNzdhMTYiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDprOGRhc2gtc2EifQ.Ap6DbLKX-eyaN2boWLkxsAWZJTx954uk63AjAF4o001kRdVzVzo2g8OazoNlALy-rlnH1kE3CN50YofdBG5onbuB9TOUdWwuAAnesY1ZzCOmP0R3C_uVypTC4n6nhVsENawmIsB-kJXQDXS5TSu14vG6kxpVUuJjTrh7_2lV0Cm1L5D9RhxMN8mw53k3pLUBZwcJnnYKRnq7a44cJb2hoDWhQoUYbQLO42ZynZCpnCBU4Ap5SCsFmxEJ6qWGBCEehzkyp9gDmmFsFYfudq_2kDmQsflaK9PNfRURYtc5EoslDhSDYONx6oMX2cMy7hWG062Z-7FLF20RAGyrBeRZ5g
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.
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.
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`