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 9: | Line 9: | ||
| NVIDIA device plugin || || https://github.com/NVIDIA/k8s-device-plugin || || | | NVIDIA device plugin || || https://github.com/NVIDIA/k8s-device-plugin || || | ||
|- | |- | ||
| | |||
|- | |- | ||
| | | | ||
|} | |} | ||
| Line 25: | Line 25: | ||
=== 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''') | 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 === | === Kubernetes Node Join Command === | ||
<pre> | <pre> | ||
kubeadm join 10. | kubeadm join 10.1.0.15:6443 --token n7izvj.jxymbbusm0vjrpn6 \ | ||
--discovery-token-ca-cert-hash sha256: | --discovery-token-ca-cert-hash sha256:7b63bd488b5b630f7a0153a748b6b979dc41e8391a3751ae941cdfa08ec89385 \ | ||
--ignore-preflight-errors Swap --node-name=`hostname -s` | --ignore-preflight-errors Swap --node-name=`hostname -s` | ||
</pre> | </pre> | ||
Revision as of 05:14, 11 July 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:
eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJjbHVzdGVycm9sZS1hZ2dyZWdhdGlvbi1jb250cm9sbGVyLXRva2VuLTQ4Z3ZjIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImNsdXN0ZXJyb2xlLWFnZ3JlZ2F0aW9uLWNvbnRyb2xsZXIiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiI3ZDAyNTEwZC01ZjRmLTRjMzMtYTFiZC1jNGVlZWVmNzk1Y2UiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZS1zeXN0ZW06Y2x1c3RlcnJvbGUtYWdncmVnYXRpb24tY29udHJvbGxlciJ9.Tym2gkN7amyRMSAAx8oD4T57bhkB2hNCkNwKrFFsc7-K53x2m_WjKMdfm4xX09-z9F_kFH2OKVae7yDcNVpZRjbJP0zfKm3n7IdfSPoOTN1Nu-y-EOVmgsQL8ix2dAaoY_GFtOyKAdj7RV9qo-NX__s1mGLXV_FSjpVjP6dh6Hcz3AL4pBIRZB-bQppNTOzyt19wR7sUMewBORwTe2CqsRMZ6TCmoXTNs4jJDgQdann5hiPQvGITPXs_mZBCo0tm6CKc8TjRNjaPqqVWp1rh9qRn7OTteE0Ey3LNFG4Q30NivRQW_Kxy_Ht-JwDseDLKfAYNrfMTYDSEctbkvwLqmg
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.1.0.15:6443 --token n7izvj.jxymbbusm0vjrpn6 \
--discovery-token-ca-cert-hash sha256:7b63bd488b5b630f7a0153a748b6b979dc41e8391a3751ae941cdfa08ec89385 \
--ignore-preflight-errors Swap --node-name=`hostname -s`