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
#!/bin/sh | |
jdk=/usr/java/jdk1.8.0_05 | |
jre=$jdk/jre | |
alternatives \ | |
--install /usr/bin/java java $jre/bin/java 180005 \ | |
--slave /usr/lib/jvm/jre jre $jre \ | |
--slave /usr/bin/keytool keytool $jre/bin/keytool \ | |
--slave /usr/bin/orbd orbd $jre/bin/orbd \ |
nbproject |
# Sample Nginx config with sane caching settings for modern web development | |
# | |
# Motivation: | |
# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools. | |
# These tools automatically deactivate all sorts of caching for you, so you always have a fresh | |
# and juicy version of your assets available. | |
# At some point, however, you want to show your work to testers, your boss or your client. | |
# After you implemented and deployed their feedback, they reload the testing page – and report | |
# the exact same issues as before! What happened? Of course, they did not have developer tools | |
# open, and of course, they did not empty their caches before navigating to your site. |
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