upload
CI/CD (dev on branch, prod on tag) / build-and-deploy (push) Successful in 4m7s

This commit is contained in:
Tom Chien (IQ-AS)
2026-11-18 18:41:41 +08:00
parent b554c90e03
commit 5fe2ecd757
6 changed files with 100 additions and 103 deletions
+4 -3
View File
@@ -27,13 +27,14 @@ export default function Home() {
id="lab"
eyebrow="The Lab"
title="A Kubernetes lab on a Mac mini"
lead="Kubernetes comes from Docker Desktop on my Mac mini. A host-level Nginx accepts traffic on port 80 and hands it to the cluster's ingress controller, which routes each application hostname to the right service. Harbor and Gitea sit outside the cluster and are reached directly on their own ports. Everything below is hosted on that one machine, including this site."
lead="Kubernetes comes from Docker Desktop on my Mac mini. A host-level Nginx accepts traffic on port 80 and hands it to the cluster's ingress controller, which routes each application hostname to the right service. Harbor and Gitea run in the same cluster, but each is exposed by its own LoadBalancer service on a host port, so they skip the ingress. Everything below is hosted on that one machine, including this site."
>
<div>
<SubHeading title="How a request reaches a pod">
DNS is managed at GoDaddy. Application traffic passes through the host Nginx and the
cluster ingress before landing on a pod. Harbor and Gitea are not behind the ingress;
they are served directly on their own ports.
cluster ingress before landing on a pod. Harbor and Gitea are pods in the cluster too,
but each is exposed by its own LoadBalancer service on :8080 and :3001, so they are not
behind the ingress.
</SubHeading>
<RequestFlow />
</div>