Helm 3 is storing description of it's releases in secrets. You can simply find them via
$ kubectl get secrets
NAME TYPE DATA AGE
sh.helm.release.v1.wordpress.v1 helm.sh/release.v1 1 1h
If you want to get more info about the secret, you can try to describe the secret
$ kubectl describe secret sh.helm.release.v1.wordpress.v1
| $subnet = '10.224.0' | |
| (1..254) | foreach { | |
| $ip = "$subnet.$_" | |
| $props = @{ | |
| 'IP' = $ip ; | |
| 'Name' = (Resolve-DnsName $ip -ErrorAction SilentlyContinue | select -ExpandProperty NameHost) ; | |
| 'Response' = (Test-Connection $ip -Quiet -Count 1) | |
| } | |
| $obj = New-Object -TypeName psobject -Property $props | |
| Write-Output $obj |
This guide will enable systemd to run as normal under WSL 2. This will enable services like microk8s, docker and many more to just work during a WSL session. Note: this was tested on Windows 10 Build 2004, running Ubuntu 20.04 LTS in WSL 2.
To enable systemd under WSL we require a tool called systemd-genie
Copy the contents of install-sg.sh to a new file /tmp/install-sg.sh:
cd /tmp
| version: '2' | |
| services: | |
| plex: | |
| image: linuxserver/plex | |
| container_name: plex | |
| volumes: | |
| - /path/to/plex/config:/config | |
| - /path/to/plex/Movies:/data/movies | |
| - /path/to/plex/Shows:/data/tvshows | |
| - /path/to/plex/transcode:/data/transcode |
| sudo dpkg --add-architecture i386 | |
| sudo apt update | |
| sudo apt-get install libtool-bin cmake libproxy-dev uuid-dev liblzo2-dev autoconf automake bash bison \ | |
| bzip2 diffutils file flex m4 g++ gawk groff-base libncurses5-dev libtool libslang2 make patch perl pkg-config shtool \ | |
| subversion tar texinfo zlib1g zlib1g-dev git gettext libexpat1-dev libssl-dev cvs gperf unzip \ | |
| python libxml-parser-perl gcc-multilib gconf-editor libxml2-dev g++-multilib gitk libncurses5 mtd-utils \ | |
| libncurses5-dev libvorbis-dev git autopoint autogen sed build-essential intltool libglib2.0-dev \ |
| #define WIN32_LEAN_AND_MEAN | |
| #include <Windows.h> | |
| #include <TlHelp32.h> | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <ctype.h> | |
| #include <string.h> | |
| #define printerr(e) (fprintf(stderr, e)) |
| #requires -Version 6 | |
| function Get-BranchName | |
| { | |
| $currentPath = Get-Location | |
| while ($true) | |
| { | |
| try | |
| { |
| # escape=` | |
| # Image with NET CORE installation to extract executables for final image | |
| FROM microsoft/aspnetcore:2.0.0-nanoserver As CoreBuild | |
| # Middleware image used to extract ASP.NET core module | |
| From microsoft/iis as WindowsBuild | |
| SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'Continue'; $verbosePreference='Continue';"] | |
| # Installing NET CORE webhosting in middleware image so latest module and configuration schema is extracted for final image | |
| ADD https://download.microsoft.com/download/B/1/D/B1D7D5BF-3920-47AA-94BD-7A6E48822F18/DotNetCore.2.0.0-WindowsHosting.exe ".\hosting.exe" |
Yes - you can create a Kubernetes cluster with Raspberry Pis with the default operating system Raspbian. Carry on using all the tools and packages you're used to with the officially-supported OS.