KIND runs Kubernetes cluster in Docker, and leverages Docker networking for all the network features: port mapping, IPv6, containers connectivity, etc.
KIND uses a docker user defined network.
It creates a bridge named kind
KIND runs Kubernetes cluster in Docker, and leverages Docker networking for all the network features: port mapping, IPv6, containers connectivity, etc.
KIND uses a docker user defined network.
It creates a bridge named kind
| KataContainers | |
| - image coupled with kernel | |
| - light vm layer | |
| - can run in nested virturalization environments if hardware supports and you can enable it in bios (ex. only bare metal EC2 instances, limits many cloud providers) | |
| - slower startup time | |
| - OCI compliant | |
| - previously known as ClearContainers by Intel | |
| gvisor | |
| - kernel implemented in userspace |
| # GitLab multi-arch docker build template | |
| # https://badgateway.qc.to/multi-architecture-docker-builds | |
| variables: | |
| CI_IMAGE: $DOCKER_HUB_USER/$CI_PROJECT_NAME | |
| before_script: | |
| - docker login -u $DOCKER_HUB_USER -p $DOCKER_HUB_TOKEN | |
| - docker run --rm --privileged multiarch/qemu-user-static --reset -p yes | |
| - docker buildx create --use |
| provider "google" { | |
| project = var.google_project_id | |
| region = var.region | |
| zone = var.az | |
| } | |
| resource "google_compute_instance" "k3s_master_instance" { | |
| name = "k3s-master" | |
| machine_type = "n1-standard-1" | |
| tags = ["k3s", "k3s-master", "http-server", "https-server"] |
| # https://www.outcoldsolutions.com/docs/monitoring-kubernetes/v4/audit/ | |
| apiVersion: audit.k8s.io/v1 | |
| kind: Policy | |
| rules: | |
| # Do not log from kube-system accounts | |
| - level: None | |
| userGroups: | |
| - system:serviceaccounts:kube-system | |
| - level: None | |
| users: |
There a times when you need to build something from the nix unstable channel. For example the master contains a new package you need, but the next nixpkgs release is somewhere in the future, and you need this package now. In this guide I want to show how to install packages from unstable by using nix-env. Furthermore I hope to give a basic understanding of the channels concept.
A channel is a set of expressions which includes severall build, installation and configuration instructions for packages, services and the system itself. The repository normaly used here is nixpkgs. It is developed at https://github.com/NixOS/nixpkgs.
The unstable channel is a copy of the NixOS/nixpkgs master. It is pulled from github once in a while and will be available from a mirror under https://nixos.org/channels/nixpkgs-unstable. Since NixOS uses half-anual released stable channels, some changes (especially new f
| package main | |
| import ( | |
| "bytes" | |
| admissionregistrationv1 "k8s.io/api/admissionregistration/v1" | |
| metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | |
| "k8s.io/client-go/kubernetes" | |
| "os" | |
| ctrl "sigs.k8s.io/controller-runtime" | |
| ) |
| package main | |
| import ( | |
| "bytes" | |
| cryptorand "crypto/rand" | |
| "crypto/rsa" | |
| "crypto/x509" | |
| "crypto/x509/pkix" | |
| "encoding/pem" | |
| "fmt" |
| name: issue-greeter | |
| on: | |
| issues: | |
| types: [opened] | |
| jobs: | |
| my-job: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: my-step | |
| env: |
| name: hello-world | |
| on: push | |
| jobs: | |
| my-job: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: my-step | |
| run: echo "Hello World!" |