Test Cluster Configuration: Difference between revisions
Jump to navigation
Jump to search
DrEdWilliams (talk | contribs) mNo edit summary |
DrEdWilliams (talk | contribs) mNo edit summary |
||
| Line 30: | Line 30: | ||
<pre> | <pre> | ||
kubeadm join 10. | kubeadm join 10.0.0.168:6443 --token t1a0n9.3ct5og3va5q3kdbo \ | ||
--discovery-token-ca-cert-hash sha256: | --discovery-token-ca-cert-hash sha256:7bcbe8b669241607c18c7cf1ca7a96d9de64be02d9df734b0fca46c4efd419cb \ | ||
--ignore-preflight-errors Swap --node-name=`hostname -s` | --ignore-preflight-errors Swap --node-name=`hostname -s` | ||
</pre> | </pre> | ||
Revision as of 20:14, 1 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 -n kube-system describe secrets \
`kubectl -n kube-system get secrets | awk '/clusterrole-aggregation-controller/ {print $1}'` \
| awk '/token:/ {print $2}'
The current Test cluster dashboard token is:
eyJhbGciOiJSUzI1NiIsImtpZCI6IlBjNE8zRlZuVTZNQndrSFBmWVFRVjQxTUJhaTZWMmpUdkYyRnZRZ1MxWXMifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJjbHVzdGVycm9sZS1hZ2dyZWdhdGlvbi1jb250cm9sbGVyLXRva2VuLTZ4bnBwIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImNsdXN0ZXJyb2xlLWFnZ3JlZ2F0aW9uLWNvbnRyb2xsZXIiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhNjIxMDU0OC0zOTZiLTRiOGMtOWYyNS03MGJhMGIwYmI4MDgiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZS1zeXN0ZW06Y2x1c3RlcnJvbGUtYWdncmVnYXRpb24tY29udHJvbGxlciJ9.VVC436n71IiZO2MBoHbtRMyiUkdExGKqxb5H1Ln7NZ22_9OXoEkT-r5XEEwWVb5TMNHpZnFR0LBVimPI1Ek0W6GCfIwkYi1E99xXkgSo9hpxpueZf0o7N7CsBuPYCDdJz0-U1siq7CauAp3xa08BfWVbvs-791zCiVg3KSC5vRzA0oyktsGF6YTyBfICxhQZtVYiP9zg9DiPgFsJ4-NHXi2OTOwnUCgLq78jWptZqnQ_64aKdWMGJ6VvfHOY55LPlzQzT4fzpiGNLM5IcICor79fPZj-iDZmEKnuA_GnldSD0Xd89lLXx0ZVTQWrMKfGfnoV5ASUd3FJgMSj3NsB8g
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.168:6443 --token t1a0n9.3ct5og3va5q3kdbo \
--discovery-token-ca-cert-hash sha256:7bcbe8b669241607c18c7cf1ca7a96d9de64be02d9df734b0fca46c4efd419cb \
--ignore-preflight-errors Swap --node-name=`hostname -s`