Test Cluster Configuration

From WilliamsNet Wiki
Revision as of 23:29, 7 August 2019 by DrEdWilliams (talk | contribs)
Jump to navigation Jump to search

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
Dynamic Provisioning k8s-admin (k8s-admin wiki)
Harbor Registry k8s-admin <variable> harbor-dev.williams.localnet

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) require a special client configuration.

Kubernetes Node Join Command

kubeadm join 10.0.0.10:6443 --token iq8lyx.uidbp3lpnlztn5am \
    --discovery-token-ca-cert-hash sha256:e77c81af2e5eec04f2cb11ae69e74a6f5575e22e8d475fab266486292fea9c8a \
    --ignore-preflight-errors Swap --node-name=`hostname -s`