Skip to content

deploy: enable internal qualified WasmEdge IRC canary #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
r33drichards merged 1 commit into from
Sep 8, 2026
Merged

deploy: enable internal qualified WasmEdge IRC canary #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions clusters/kopf-k3s/inspircd/deployment.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,12 @@ metadata:
app.kubernetes.io/name: inspircd-wasi
app.kubernetes.io/part-of: inspircd-wasi-experiment
annotations:
inspircd.trycua.ai/status: "disabled pending separately approved versioned runtime activation"
inspircd.trycua.ai/status: "internal loopback-only canary; validate IRC through port-forward"
spec:
# Keep the rendered canary inert until the runtime and OCI digest gates pass.
replicas: 0
replicas: 1
minReadySeconds: 30
strategy:
type: Recreate
selector:
matchLabels:
app.kubernetes.io/name: inspircd-wasi
Expand All @@ -27,7 +29,7 @@ spec:
type: RuntimeDefault
containers:
- name: inspircd
# The deployment remains at zero replicas until its runtime gates pass.
# Immutable artifact qualified against the dedicated handler.
image: ghcr.io/trycua/inspircd@sha256:2239672f9e721b2f61fedb1a0c229863c576e092010bd1444f69d6637598af9d
imagePullPolicy: IfNotPresent
args: ["--nofork", "--config", "/irc/inspircd.conf"]
Expand Down
Loading