mak3r

Explicitly kill all k3s containers at system shutdown

Put the file in /etc/systemd/system/shutdown-k3s.service and then enable the service using

systemctl enable shutdown-k3s.service

Also note that this service name shutdown-k3s must not start with k3s-, otherwise the k3s-killall.sh script would also try to stop this service and cause problems.

• Copied from this github issue k3s-io/k3s#2400 (comment)

mak3r

apiVersion: v1
kind: Namespace
metadata:
  name: kiosk
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kiosk
  namespace: kiosk

mak3r

kubectl get secret -n cattle-system tls-rancher -o jsonpath='{.data.tls\.crt}' | base64 -d | sha256sum | cut -d" " -f 1

mak3r

#!/bin/sh

for f in $(ls -1); do 
  pushd $f; 
  
  echo -e "\n\n******" >> ~/dev/remotes.txt;
  echo $f >> ~/dev/remotes.txt;
  echo "******" >> ~/dev/remotes.txt;
  git remote show origin >> ~/dev/remotes.txt 2>&1; 
  popd; 

mak3r

Install a standard k3s configuration

• Run the command below to install a standard k3s configuration into the /etc/rancher/k3s directory.
• This will set the kubeconfig permissions bits and setup to overwrite the install users ~/.kube/config file with the k3s kubeconfig
• The user executing the script must have sudo privileges

Usage

1. Install the config file

• curl -sfL https://gist.github.com/mak3r/5e53406d303f46aa3c31af1cc792fe42/raw/install-k3s-config.sh | sh -

mak3r

#!/bin/sh -x

usage() {
        echo "Usage:"
        echo "$0 <url to .xz image> <device e.g. /dev/sda>"
        echo ""
        echo "Warning: Make sure you pass the device you really want to overwrite."
        echo "\tit will get wiped."
}

mak3r

#!/bin/bash

for i in $(brew list --formula); do which $i | xargs file  |  grep x86 ; done

for i in $(brew list --cask); do which $i | xargs file  |  grep x86 ; done

mak3r

#cloud-config
rancheros:
  install:
    # An http://, https://, or tftp:// URL to load as the base configuration
    # for this configuration. This configuration can include any install 
    # directives or OEM configuration. The resulting merged configuration
    # will be read by the installer and all content of the merged config will
    # be stored in /oem/99_custom.yaml in the created image.
    # configURL: http://example.com/machine-cloud-config
    # Turn on verbose logging for the installation process

mak3r

{ "text": "Hello" }

mak3r

#!/bin/bash

shopt -s expand_aliases
alias echo='echo -e'

# fake server-url
RANCHER_SERVER=https://your_rancher_server.com
ROLEFLAGS=""
CLUSTER_CREATE_TYPE=
DOCKER="DOCKER"