Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| kubernetes_install_on_fedora [2018/04/09 09:37] – [From the script] rpjday | kubernetes_install_on_fedora [2018/04/09 10:15] (current) – [cluster/get-kube-binaries.sh] rpjday | ||
|---|---|---|---|
| Line 33: | Line 33: | ||
| ===== download_kube_binaries ===== | ===== download_kube_binaries ===== | ||
| + | |||
| + | ==== Overview ==== | ||
| This function call does two things: | This function call does two things: | ||
| Line 40: | Line 42: | ||
| ==== download_kube_binaries() ==== | ==== download_kube_binaries() ==== | ||
| + | |||
| + | This just turns around and calls a script for the download and extraction: | ||
| < | < | ||
| + | # Use the script from inside the Kubernetes tarball to fetch the client and | ||
| + | # server binaries (if not included in kubernetes.tar.gz). | ||
| function download_kube_binaries { | function download_kube_binaries { | ||
| ( | ( | ||
| Line 56: | Line 62: | ||
| ==== cluster/ | ==== cluster/ | ||
| - | The server tarball is downloaded and simply left under '' | + | === kubernetes-server-linux-amd64.tar.gz === |
| + | |||
| + | As you can see, the server tarball is downloaded and simply left under '' | ||
| < | < | ||
| Line 64: | Line 72: | ||
| </ | </ | ||
| - | On the other client, the client tarball is downloaded under '' | + | so you can easily do that manually. |
| + | |||
| + | === kubernetes-client-linux-amd64.tar.gz === | ||
| + | |||
| + | Unlike the server tarball, the client tarball is not only downloaded under '' | ||
| < | < | ||
| Line 73: | Line 85: | ||
| </ | </ | ||
| - | What happens: | + | The client tarball consists of the single executable '' |
| + | |||
| + | < | ||
| + | $ tar tvf kubernetes-client-linux-amd64.tar.gz | ||
| + | drwxr-xr-x root/ | ||
| + | drwxr-xr-x root/ | ||
| + | drwxr-xr-x root/ | ||
| + | -rwxr-xr-x root/ | ||
| + | $ | ||
| + | </ | ||
| + | |||
| + | which will be " | ||
| + | |||
| + | Here's the '' | ||
| < | < | ||
| Line 92: | Line 117: | ||
| </ | </ | ||
| - | The client tarball consists | + | In short, from the '' |
| + | |||
| + | < | ||
| + | $ mkdir -p platforms/linux/ | ||
| + | $ tar xvf ../ | ||
| + | > --strip-components 3 \ | ||
| + | > -C platforms/linux/amd64 | ||
| + | $ | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | $ tree platforms | ||
| + | platforms | ||
| + | └── linux | ||
| + | └── amd64 | ||
| + | └── | ||
| + | $ | ||
| + | </ | ||
| + | |||
| + | Finally, make sure you can find '' | ||
| + | |||
| + | < | ||
| + | PATH=$PATH:/ | ||
| + | </ | ||
| ===== create_cluster ===== | ===== create_cluster ===== | ||
| + | |||
| + | ==== Overview ==== | ||
| + | |||
| + | This function kicks off a new cluster: | ||
| + | |||
| + | < | ||
| + | function create_cluster { | ||
| + | if [[ -n " | ||
| + | exit 0 | ||
| + | fi | ||
| + | echo " | ||
| + | ( | ||
| + | cd kubernetes | ||
| + | ./ | ||
| + | echo " | ||
| + | if [[ ": | ||
| + | echo "You may want to add this directory to your PATH in \$HOME/ | ||
| + | fi | ||
| + | |||
| + | echo " | ||
| + | ) | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | You might want to add the '' | ||
| + | |||
| + | < | ||
| + | PATH=$PATH:/ | ||
| + | </ | ||
| + | ==== create_cluster() ==== | ||
| + | |||
| + | This function calls the underlying script '' | ||
| + | |||
| + | < | ||
| + | function create_cluster { | ||
| + | if [[ -n " | ||
| + | exit 0 | ||
| + | fi | ||
| + | echo " | ||
| + | ( | ||
| + | cd kubernetes | ||
| + | ./ | ||
| + | echo " | ||
| + | if [[ ": | ||
| + | echo "You may want to add this directory to your PATH in \$HOME/ | ||
| + | fi | ||
| + | |||
| + | echo " | ||
| + | ) | ||
| + | } | ||
| + | </ | ||