stackfeed/k8s-ops repository overview

⁠stackfeed/k8s-ops⁠ cloud tools docker image

Docker image which bundles cloud automation software used for operating kubernetes. Apart from that the container bundles lots of useful tools to provide you a ready-to-go container workstation without need to install anything on your host machine.

⁠Tools

List of software bundled into this container:

• Terraform⁠ - infrastructure managment which works with almost any cloud provider
• Terragrunt⁠ - a thin terraform wrapper-tool which meant to make experience smoother when working with multiple terraform stages and environments
• KOPS⁠ - the easiest way to get a production grade Kubernetes cluster up and running
• kubectl⁠ - kubernetes CLI tool
• Helm⁠ - the package manager for Kubernetes
• Helmfile⁠ - is a declarative spec for deploying helm charts
• AWS CLI⁠ - AWS CLI tool (available in AWS container flavour)
• Heptio Ark⁠ - is an utility for managing disaster recovery, specifically for your Kubernetes cluster resources and persistent volumes (available in AWS container flavour).

⁠k8s-ops for AWS

⁠Usage

This container uses fixuid⁠ a go binary to change Docker container user/group and file permissions at runtime. That's why it's recommended to run as unprivileged user matching your host UID, GID.

Typical workstation container initialization looks like:

docker run -ti --name myproject -u $(id -u):$(id -g) -v /some/path:/code -w /code stackfeed/k8s-ops:aws

Here above we create a container and name it myproject, provide UID/GID of the host system and also we can pass any volumes which might be required.

⁠Stopping/starting the k8s-ops tools container

docker stop myproject
docker start myproject

⁠Getting the console

To get any number of consoles running you can simply exec into the running container as simple as this:

docker exec -ti myproject zsh

also note that if you want to get fancy colors and proper terminal width and height you have to enhance the docker exec by providing additional options:

docker exec -ti --env COLUMNS=`tput cols` --env LINES=`tput lines` myproject zsh

But better make yourself an alias: alias deti="docker exec -ti --env COLUMNS=tput cols --env LINES=tput lines"

⁠Volumes

Here are a few best practices. When working on the workstation almost any application makes use of the home directory. Tools bundled into this container are no exception, for example kubectl uses ~/.kube directory and helm uses ~/.helm.

In case if you recreate container to update the tools all the configuration will be lost!

That's why the first rule is to always pre-createa a volume for the container user home. The second rule is not to forget to pass volumes with the code.

⁠Best practice example

# create volume to store home directory files
docker volume create myproject-home

# we admit that the code we work with is in ~/code, so we keep this in when we initate the container
docker run -ti --name myproject --hostname myproject -u $(id -u):$(id -g) -v myproject-home:/home/fixuid -v ~/code:/home/fixuid/code stackfeed/k8s-ops:aws