Let's look at some basic kubectl output options.
Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).
We can start with:
kubectl get no
| FROM alpine:3.11 AS build | |
| ARG CHANNEL=unstable | |
| ARG VERSION=0.99.1-127 | |
| ARG ARCH=amd64 | |
| RUN mkdir /build | |
| WORKDIR /build | |
| RUN apk add --no-cache curl tar |
| Fireup all our nodes. | |
| I could find information about this only which was odd. The tutorial is nice if you are setting up some static site ala the early 00's. | |
| So this is some notes on creating a cluster by hang which will feed into the creation of a puppet / ansible / chef / shell / slat script | |
| to do the main part of creating the cluster. | |
| I note also many clients do not support redis in cluster mode WTF? | |
| Open up this in a browser | |
| https://redis.io/commands/cluster-slots |
| # use ImageMagick convert | |
| # the order is important. the density argument applies to input.pdf and resize and rotate to output.pdf | |
| convert -density 90 input.pdf -rotate 0.5 -attenuate 0.2 +noise Multiplicative -colorspace Gray output.pdf |
Network namespaces create isolated network stacks, including network devices, IP addresses, routing tables, rules , ... This separation is crucial for containerization.
Network namespaces also contain network devices that can live exactly on one network namespace:
physical network device can live in exactly one network namespace. When a network namespace is freed (i.e., when the last