134
edits
Equipment/Blanton/Kubernetes: Difference between revisions
From London Hackspace Wiki
→Accessing the cluster
Mich181189 (talk | contribs) (→Accessing the cluster: Tested on macOS as well) |
Mich181189 (talk | contribs) |
||
| Line 44: | Line 44: | ||
'''Currently (useful) access is limited to those in the Admins ldap group'''. After a bit more testing though, I'd like to create a members namespace for members to play in. | '''Currently (useful) access is limited to those in the Admins ldap group'''. After a bit more testing though, I'd like to create a members namespace for members to play in. | ||
First, go get kubectl (preferably version 1.22 | First, go get kubectl (preferably version 1.22 which, at the time of writing this, is the version the cluster runs) https://kubernetes.io/docs/tasks/tools/ | ||
Now go get the binary for your OS from https://github.com/londonhackspace/kube-auth-handler/releases/ and put it somewhere on your PATH as <code>ldap-kube-auth</code> (or on Windows <code>ldap-kube-auth.exe</code> - you might just want to put it next to kubectl and run it from that directory, at least to get going) | Now go get the binary for your OS from https://github.com/londonhackspace/kube-auth-handler/releases/ and put it somewhere on your PATH as <code>ldap-kube-auth</code> (or on Windows <code>ldap-kube-auth.exe</code> - you might just want to put it next to kubectl and run it from that directory, at least to get going) | ||
| Line 50: | Line 50: | ||
Other filenames and paths would work, but you'll need to modify the config file below in that case. | Other filenames and paths would work, but you'll need to modify the config file below in that case. | ||
Now stick the following in $HOME/.kube/config (if you already have a config in there, you'll need to merge them) | Now stick the following in $HOME/.kube/config (if you already have a config in there, you'll need to merge them, or put it somewhere else and use the KUBE_CONFIG environment variable) | ||
<pre> | <pre> | ||
