fix: removed failing propagation. will add it later
Deploy k8s Bootstrap / Pulumi Preview (pull_request) Successful in 33s
Deploy k8s Bootstrap / Bootstrap k3s Cluster (pull_request) Has been skipped
Deploy Proxmox Infra / Pulumi Preview (pull_request) Successful in 42s
Deploy Proxmox Infra / Pulumi Deploy (pull_request) Has been skipped

This commit is contained in:
2026-05-30 19:53:04 +02:00
parent 980e24c606
commit 5ac4cb592c
@@ -85,31 +85,3 @@ jobs:
cloud-url: ${{ secrets.PULUMI_BACKEND_URL }} cloud-url: ${{ secrets.PULUMI_BACKEND_URL }}
env: env:
PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }} PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}
# Propagate kubeconfig to the downstream stacks so their next deploy picks it up
- name: Propagate kubeconfig to k8s-infra
run: |
echo "${{ secrets.K8S_INFRA_DEV_YAML }}" | base64 -d > k8s-infra/Pulumi.dev.yaml
cd k8s-infra && npm install
KUBECONFIG=$(cd ../k8s-bootstrap && pulumi stack output kubeconfig --show-secrets \
--cloud-url "${{ secrets.PULUMI_BACKEND_URL }}" -s dev)
pulumi config set --secret kubeconfig "$KUBECONFIG" \
--cloud-url "${{ secrets.PULUMI_BACKEND_URL }}" -s dev
# Re-encode updated config for the secret (update manually in Gitea after first run)
base64 -w 0 Pulumi.dev.yaml
working-directory: .
env:
PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}
- name: Propagate kubeconfig to k8s-apps
run: |
echo "${{ secrets.K8S_APPS_DEV_YAML }}" | base64 -d > k8s-apps/Pulumi.dev.yaml
cd k8s-apps && npm install
KUBECONFIG=$(cd ../k8s-bootstrap && pulumi stack output kubeconfig --show-secrets \
--cloud-url "${{ secrets.PULUMI_BACKEND_URL }}" -s dev)
pulumi config set --secret kubeconfig "$KUBECONFIG" \
--cloud-url "${{ secrets.PULUMI_BACKEND_URL }}" -s dev
base64 -w 0 Pulumi.dev.yaml
working-directory: .
env:
PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}