Skip to content

fix: scope OCI kube-proxy config to the control plane #119

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
syscod3 merged 1 commit into from
Sep 21, 2026
Merged

fix: scope OCI kube-proxy config to the control plane #119

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
9 changes: 4 additions & 5 deletions omni/cluster-templates/oci-lab.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,8 @@ talos:
# upward and no `--allowed-dir` flag is needed. `status` now works without it.
patches:
- file: patches/cni-none.yaml
- file: patches/disable-kube-proxy.yaml
# allow-scheduling.yaml deliberately NOT applied: oci-lab's control plane
# stays dedicated (only the worker takes workloads).
# talos-1.14-compat.yaml contains SecurityProfileConfig, which Talos 1.13
# does not register. Add it only when versions.yaml moves oci-lab to 1.14.
# OCI keeps its control plane dedicated; the KubeProxyConfig patch is scoped
# to that role below because Talos 1.14 does not accept it on workers.
- file: patches/oci-lab-inline-manifests.yaml
---
# omnictl requires ControlPlane and Workers as SEPARATE documents. They were
Expand All @@ -28,6 +25,8 @@ patches:
# field workers not found in type models.Cluster
# So this template was never syncable in that form.
kind: ControlPlane
patches:
- file: patches/disable-kube-proxy.yaml
machineClass:
name: oci-cp
size: 1
Expand Down
Loading