|
|
|
@ -18,11 +18,9 @@ certain threshold. Run `python3 contrib/inventory_builder/inventory.py help` hel
|
|
|
|
|
|
|
|
|
|
Example inventory generator usage:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
cp -r inventory/sample inventory/mycluster
|
|
|
|
|
declare -a IPS=(10.10.1.3 10.10.1.4 10.10.1.5)
|
|
|
|
|
CONFIG_FILE=inventory/mycluster/hosts.ini python3 contrib/inventory_builder/inventory.py ${IPS[@]}
|
|
|
|
|
```
|
|
|
|
|
cp -r inventory/sample inventory/mycluster
|
|
|
|
|
declare -a IPS=(10.10.1.3 10.10.1.4 10.10.1.5)
|
|
|
|
|
CONFIG_FILE=inventory/mycluster/hosts.ini python3 contrib/inventory_builder/inventory.py ${IPS[@]}
|
|
|
|
|
|
|
|
|
|
Starting custom deployment
|
|
|
|
|
--------------------------
|
|
|
|
@ -30,12 +28,10 @@ Starting custom deployment
|
|
|
|
|
Once you have an inventory, you may want to customize deployment data vars
|
|
|
|
|
and start the deployment:
|
|
|
|
|
|
|
|
|
|
**IMPORTANT: Edit my_inventory/groups_vars/*.yaml to override data vars**
|
|
|
|
|
**IMPORTANT**: Edit my\_inventory/groups\_vars/\*.yaml to override data vars:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
ansible-playbook -i inventory/mycluster/hosts.ini cluster.yml -b -v \
|
|
|
|
|
--private-key=~/.ssh/private_key
|
|
|
|
|
```
|
|
|
|
|
ansible-playbook -i inventory/mycluster/hosts.ini cluster.yml -b -v \
|
|
|
|
|
--private-key=~/.ssh/private_key
|
|
|
|
|
|
|
|
|
|
See more details in the [ansible guide](ansible.md).
|
|
|
|
|
|
|
|
|
@ -44,18 +40,18 @@ Adding nodes
|
|
|
|
|
|
|
|
|
|
You may want to add **worker** nodes to your existing cluster. This can be done by re-running the `cluster.yml` playbook, or you can target the bare minimum needed to get kubelet installed on the worker and talking to your masters. This is especially helpful when doing something like autoscaling your clusters.
|
|
|
|
|
|
|
|
|
|
- Add the new worker node to your inventory under kube-node (or utilize a [dynamic inventory](https://docs.ansible.com/ansible/intro_dynamic_inventory.html)).
|
|
|
|
|
- Run the ansible-playbook command, substituting `scale.yml` for `cluster.yml`:
|
|
|
|
|
```
|
|
|
|
|
ansible-playbook -i inventory/mycluster/hosts.ini scale.yml -b -v \
|
|
|
|
|
--private-key=~/.ssh/private_key
|
|
|
|
|
```
|
|
|
|
|
- Add the new worker node to your inventory under kube-node (or utilize a [dynamic inventory](https://docs.ansible.com/ansible/intro_dynamic_inventory.html)).
|
|
|
|
|
- Run the ansible-playbook command, substituting `scale.yml` for `cluster.yml`:
|
|
|
|
|
|
|
|
|
|
ansible-playbook -i inventory/mycluster/hosts.ini scale.yml -b -v \
|
|
|
|
|
--private-key=~/.ssh/private_key
|
|
|
|
|
|
|
|
|
|
Connecting to Kubernetes
|
|
|
|
|
------------------------
|
|
|
|
|
|
|
|
|
|
By default, Kubespray configures kube-master hosts with insecure access to
|
|
|
|
|
kube-apiserver via port 8080. A kubeconfig file is not necessary in this case,
|
|
|
|
|
because kubectl will use http://localhost:8080 to connect. The kubeconfig files
|
|
|
|
|
because kubectl will use <http://localhost:8080> to connect. The kubeconfig files
|
|
|
|
|
generated will point to localhost (on kube-masters) and kube-node hosts will
|
|
|
|
|
connect either to a localhost nginx proxy or to a loadbalancer if configured.
|
|
|
|
|
More details on this process are in the [HA guide](ha-mode.md).
|
|
|
|
@ -77,29 +73,33 @@ Accessing Kubernetes Dashboard
|
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
|
|
As of kubernetes-dashboard v1.7.x:
|
|
|
|
|
* New login options that use apiserver auth proxying of token/basic/kubeconfig by default
|
|
|
|
|
* Requires RBAC in authorization_modes
|
|
|
|
|
* Only serves over https
|
|
|
|
|
* No longer available at https://first_master:6443/ui until apiserver is updated with the https proxy URL
|
|
|
|
|
|
|
|
|
|
- New login options that use apiserver auth proxying of token/basic/kubeconfig by default
|
|
|
|
|
- Requires RBAC in authorization\_modes
|
|
|
|
|
- Only serves over https
|
|
|
|
|
- No longer available at <https://first_master:6443/ui> until apiserver is updated with the https proxy URL
|
|
|
|
|
|
|
|
|
|
If the variable `dashboard_enabled` is set (default is true), then you can access the Kubernetes Dashboard at the following URL, You will be prompted for credentials:
|
|
|
|
|
https://first_master:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login
|
|
|
|
|
<https://first_master:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login>
|
|
|
|
|
|
|
|
|
|
Or you can run 'kubectl proxy' from your local machine to access dashboard in your browser from:
|
|
|
|
|
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login
|
|
|
|
|
<http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login>
|
|
|
|
|
|
|
|
|
|
It is recommended to access dashboard from behind a gateway (like Ingress Controller) that enforces an authentication token. Details and other access options here: https://github.com/kubernetes/dashboard/wiki/Accessing-Dashboard---1.7.X-and-above
|
|
|
|
|
It is recommended to access dashboard from behind a gateway (like Ingress Controller) that enforces an authentication token. Details and other access options here: <https://github.com/kubernetes/dashboard/wiki/Accessing-Dashboard---1.7.X-and-above>
|
|
|
|
|
|
|
|
|
|
Accessing Kubernetes API
|
|
|
|
|
------------------------
|
|
|
|
|
|
|
|
|
|
The main client of Kubernetes is `kubectl`. It is installed on each kube-master
|
|
|
|
|
host and can optionally be configured on your ansible host by setting
|
|
|
|
|
`kubeconfig_localhost: true` in the configuration. If enabled, kubectl and
|
|
|
|
|
admin.conf will appear in the artifacts/ directory after deployment. You can
|
|
|
|
|
see a list of nodes by running the following commands:
|
|
|
|
|
`kubectl_localhost: true` and `kubeconfig_localhost: true` in the configuration:
|
|
|
|
|
|
|
|
|
|
cd artifacts/
|
|
|
|
|
./kubectl --kubeconfig admin.conf get nodes
|
|
|
|
|
- If `kubectl_localhost` enabled, `kubectl` will download onto `/usr/local/bin/` and setup with bash completion. A helper script `inventory/mycluster/artifacts/kubectl.sh` also created for setup with below `admin.conf`.
|
|
|
|
|
- If `kubeconfig_localhost` enabled `admin.conf` will appear in the `inventory/mycluster/artifacts/` directory after deployment.
|
|
|
|
|
|
|
|
|
|
If desired, copy kubectl to your bin dir and admin.conf to ~/.kube/config.
|
|
|
|
|
You can see a list of nodes by running the following commands:
|
|
|
|
|
|
|
|
|
|
cd inventory/mycluster/artifacts
|
|
|
|
|
./kubectl.sh get nodes
|
|
|
|
|
|
|
|
|
|
If desired, copy admin.conf to ~/.kube/config.
|
|
|
|
|