The motivation for this gist comes from an interest in reproducing issues observed using multus on talos metal.
Here we will attempt to re-create the symptom in as simple of an environment as possible to then pursue support as needed.
In this gist we will attempt to capture the prominent steps in building an RK1 TPI2 Talos K8s Cluster for use with the github.com/ContainerCraft/Kargo kubevirt platform.
If you try this and achieve success imaging your RK1 compute modules with the un-merged talos rk1 fork please report your success on this rfe issue: github.com/siderolabs/talos/issues/8187
The pulumi-go-provider
is a framework for building Go-based providers for Pulumi. It is currently in active development, and breaking changes are expected. The library is designed to be flexible yet simple, and it comes in four main parts:
Provider Interface: The core abstraction for a Pulumi Provider.
Middleware Layers: Built on top of the Provider interface for features like token dispatch and schema generation.
Testing Framework: Located in the integration
folder for unit and integration tests.
Infer Layer: Generates full providers from Go types and methods. It's the quickest way to start building a provider.
Cheat Sheet Main Function Example
apiVersion: argoproj.io/v1alpha1 | |
kind: Application | |
metadata: | |
name: argocd | |
spec: | |
destination: | |
name: '' | |
namespace: argocd | |
server: 'https://kubernetes.default.svc' | |
project: default |
cat <<EOF > Dockerfile && docker build -t registry .
FROM --platform=x86_64 cgr.dev/chainguard/go:latest-glibc as build
RUN CGO_ENABLED=0 GOBIN=/home/nonroot go install github.com/google/go-containerregistry/cmd/registry@latest
FROM --platform=x86_64 cgr.dev/chainguard/static:latest