#!/bin/bash
# Helmリポジトリを追加
helm repo add tailscale https://pkgs.tailscale.com/helmcharts
helm repo update
# まずnamespaceを作成
kubectl create namespace tailscale
# Secretをtailscale namespaceに作成
kubectl apply -f tailscale-oauth.yaml
helm install tailscale-operator tailscale/tailscale-operator \
--namespace=tailscale \
--set-string oauth.clientSecretName=operator-oauth
検索
Hey you there, reading this whole wondering what next to do with your #homelab. It's a great weekend to setup a #forgejo instance for yourself then we it to mirror some #git repos, and store some #helm charts in it for your home #Kubernetes, setup repo webhooks to automate things with #Ansible, etc. It's useful, free, fully #opensource, and very well maintained!
https://forgejo.org/
But why?
Trying to decide if I want to commit to writing and publishing a #helm chart for the #EnvKey API server. #Kubernetes
Putting special characters like @ at the beginning of a key in #YAML is a no-no. Fortunately, there's a way around this with a bit of unicode magic on a double-quoted scalar. #Kubernetes #helm
These get converted to @jupyterlab/extensionmanager-extension and @jupyterlab/jupyterlab-telemetry in this example:
I did a thing. I had #Longhorn deployed out of band with kubectl + git reference. I wrote a script to "convert" the Longhorn deployment to a #helm release, upgrading it back to a proper Longhorn release in the process. (Obviously, use this entirely at your own risk!) #kubernetes #rancher #storage
https://gist.github.com/vwbusguy/494a1fca6ed72557ef7bc58a6803149c
Looking for a #yaml diff tool that spits out valid yaml but only including the parts where there are differences between the two. I have some helm chart values yaml files that have gotten unnecessarily verbose. #Programming #kubernetes #helm

