The code and data behind xeiaso.net
chore(k8s): remove legacy Civo deployment logic (#1056)
- Remove entire deploy job from GitHub Actions workflow
- Remove Civo CLI installation and configuration steps
- Remove CIVO_TOKEN secret reference
- Add editor's note to hello-again-k8s blog post indicating historical context
- Clean slate for implementing new deployment strategy in future PR
Resolves: XE-5
+10
-40
+1
-40
.github/workflows/earthly.yml
+1
-40
.github/workflows/earthly.yml
···
50
50
patreon-saasproxy.tags=ghcr.io/xe/site/patreon-saasproxy:latest
51
51
xesite.tags=ghcr.io/xe/site/bin:latest
52
52
53
-
deploy:
54
-
name: "Deploy xesite"
55
-
needs: build
56
-
runs-on: alrest-xe-site
57
-
if: github.ref == 'refs/heads/main'
58
-
permissions:
59
-
contents: read
60
-
61
-
steps:
62
-
- uses: actions/checkout@v4
63
-
- uses: dorny/paths-filter@v3
64
-
id: changes
65
-
with:
66
-
filters: |
67
-
src:
68
-
- 'cmd/**/*.go'
69
-
- 'internal/**/*.go'
70
-
- 'pb/*'
71
-
- 'pb/**/*'
72
-
- 'go.mod'
73
-
- 'go.sum'
74
-
- 'docker/*'
75
-
- "docker-bake.hcl"
76
-
- 'manifest/**/*.yaml'
77
-
- uses: azure/setup-kubectl@v4
78
-
if: steps.changes.outputs.src == 'true'
79
-
- name: Save Civo kubeconfig
80
-
if: steps.changes.outputs.src == 'true'
81
-
run: |
82
-
curl -sL https://civo.com/get | sudo sh
83
-
civo apikey add default $CIVO_TOKEN
84
-
civo apikey current default
85
-
civo kubernetes config --region phx1 aeacus --save --switch
86
-
env:
87
-
CIVO_TOKEN: ${{ secrets.CIVO_TOKEN }}
88
-
- name: "Deploy"
89
-
if: steps.changes.outputs.src == 'true'
90
-
run: |
91
-
kubectl apply -k manifest
92
-
kubectl rollout restart -n default deploy/xesite
53
+
+9
lume/src/blog/2024/hello-again-k8s.mdx
+9
lume/src/blog/2024/hello-again-k8s.mdx
···
15
15
- civo
16
16
---
17
17
18
+
import Admonition from "../../_components/Admonition.jsx";
19
+
20
+
<Admonition type="note" title="Editor's note (2025-11-01)">
21
+
This blog post describes the initial migration of my website to Civo Kubernetes.
22
+
Since this was written, the site has been migrated from Civo to Vultr Kubernetes Engine.
23
+
The deployment details and provider-specific information in this post are historical
24
+
and no longer reflect the current setup.
25
+
</Admonition>
26
+
18
27
[Previously on Xesite](/blog/k8s-pondering-2020-12-31/):
19
28
20
29
> I think I made a mistake when I decided to put my cards into Kubernetes for my personal setup. It made sense at the time (I was trying to learn Kubernetes and I am cursed into learning by doing), however I don't think it is really the best choice available for my needs.