revert(cloudflared): do not publish the kube-apiserver at k8s.riotpiao.com

#88 added a tunnel rule mapping k8s.riotpiao.com to the in-cluster apiserver. Its own comment warned that without a Cloudflare Access application in front, every scanner on the internet reaches the apiserver, and no Access application exists. ArgoCD applied the rule before the exposure could be stopped, so the live ConfigMap was patched and cloudflared restarted to drop it. All paths now return 404. This commit removes the rule from the source so it cannot return. The hostname keeps its DNS record and returns the tunnel's 404 fallback. That is deliberate: publish it again only together with an Access policy.
2026-11-04 06:03:55 +08:00
1 changed files with 5 additions and 0 deletions
@@ -14,6 +14,11 @@ resources:
  # v0.5.22+, published only on CUDA 13, and CUDA 13 dropped Volta kernels. The model
  # instead runs the implementation it ships (joint_schema_model.py) in fp16 on one V100.
  - clef-serve.yaml
+  # coder = Qwen3-Coder-30B-A3B-Instruct, 4-bit GPTQ, TP=2 at 262,144 tokens. It serves
+  # both `coder` and `reasoning`, so poimen-memory needs a host change only, never a
+  # model-name change. reasoning.yaml below can be dropped once that host change lands.
+  - coder.yaml
+  - reasoning.yaml
  # Stable client-facing name for the chat model. poimen-memory points at this Service,
  # so the vLLM -> candle-vllm handoff is a selector edit here and no client change.
  - reasoning-long-service.yaml