mirror of
https://github.com/puppetmaster/typhoon.git
synced 2025-07-24 21:51:34 +02:00
Add heapster, dashboard, and CLUO addons
This commit is contained in:
@ -1,6 +1,29 @@
|
||||
# Container Linux Update Operator
|
||||
|
||||
More aptly named "Container Linux Reboot Coordinator".
|
||||
The [Container Linux Update Operator](https://github.com/coreos/container-linux-update-operator) (i.e. CLUO) coordinates reboots of auto-updating Container Linux nodes so that one node reboots at a time and nodes are drained before reboot. CLUO enables the auto-update behavior Container Linux clusters are known for, but does so in a Kubernetes native way.
|
||||
|
||||
## Create
|
||||
|
||||
Create the `update-operator` deployment and `update-agent` DaemonSet.
|
||||
|
||||
```sh
|
||||
kubectl apply -f addons/cluo -R
|
||||
```
|
||||
|
||||
## Usage
|
||||
|
||||
`update-agent` runs as a DaemonSet and annotates a node when `update-engine.service` indiates an update has been installed and a reboot is needed. It also adds additional labels and annotations to nodes.
|
||||
|
||||
```
|
||||
$ kubectl get nodes --show-labels
|
||||
...
|
||||
container-linux-update.v1.coreos.com/group=stable
|
||||
container-linux-update.v1.coreos.com/version=1465.6.0
|
||||
```
|
||||
|
||||
`update-operator` ensures one node reboots at a time and that pods are drained prior to reboot.
|
||||
|
||||
!!! note ""
|
||||
CLUO replaces `locksmithd` reboot coordination. The `update_engine` systemd unit on hosts still performs the Container Linux update check, download, and install to the inactive partition.
|
||||
|
||||
|
||||
!!! bug "In Progress"
|
||||
These docs haven't been completed yet.
|
||||
|
@ -1,4 +1,24 @@
|
||||
# Kubernetes Dashboard
|
||||
|
||||
!!! bug "In Progress"
|
||||
These docs haven't been completed yet.
|
||||
The Kubernetes [Dashboard](https://github.com/kubernetes/dashboard) provides a web UI to manage a Kubernetes cluster for those who prefer an alternative to `kubectl`.
|
||||
|
||||
## Create
|
||||
|
||||
Create the dashboard deployment and service.
|
||||
|
||||
```
|
||||
kubectl apply -f addons/dashboard -R
|
||||
```
|
||||
|
||||
## Access
|
||||
|
||||
Use `kubectl` to authenticate to the apiserver and create a local port forward to the remote port on the dashboard pod.
|
||||
|
||||
```sh
|
||||
kubectl get pods -n kube-system
|
||||
kubectl port-forward POD [LOCAL_PORT:]REMOTE_PORT
|
||||
kubectl port-forward kubernetes-dashboard-id 9090 -n kube-system
|
||||
```
|
||||
|
||||
!!! tip
|
||||
If you'd like to expose the Dashboard via Ingress and add authentication, use a suitable OAuth2 proxy sidecar and pick your favorite OAuth2 provider.
|
||||
|
@ -1,4 +1,19 @@
|
||||
# Heapster
|
||||
|
||||
!!! bug "In Progress"
|
||||
These docs haven't been moved over yet.
|
||||
[Heapster](https://kubernetes.io/docs/user-guide/monitoring/) collects data from apiservers and kubelets and exposes it through a REST API. This API powers the `kubectl top` command and Kubernetes dashbard graphs.
|
||||
|
||||
## Create
|
||||
|
||||
```sh
|
||||
kubectl apply -f addons/heapster -R
|
||||
```
|
||||
|
||||
## Usage
|
||||
|
||||
Allow heapster to run for a few minutes, then check CPU and memory usage.
|
||||
|
||||
```sh
|
||||
kubectl top node
|
||||
kubectl top pod
|
||||
```
|
||||
|
||||
|
Reference in New Issue
Block a user