Skip to content

fix(milo-integration): stop shipping ActivityPolicies to infra clusters #46

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
scotwells merged 1 commit into from
Jun 17, 2026
Merged

fix(milo-integration): stop shipping ActivityPolicies to infra clusters #46

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
13 changes: 6 additions & 7 deletions config/components/milo-integration/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,13 +17,12 @@ kind: Component
# `infra.datum.net/inject-datum-control-plane-trust-bundle: ""` so that
# trust-manager populates the trust bundle ConfigMap.
#
# This component also installs the inventory ActivityPolicy resources
# (config/milo) onto the Milo control plane. The policies only make sense
# where the Activity system runs, so they ship with the Milo integration
# rather than the self-contained dev overlay.

components:
- ../../milo
# This component contains only the controller's Milo-wiring patches. The
# inventory ActivityPolicy resources are NOT installed here: they require the
# activity.miloapis.com CRDs served only by the Milo control plane's
# activity-system apiserver, and this component is consumed by the infra
# cluster (which has no such CRDs). The policies live in config/milo and are
# applied directly to the Milo control plane by a dedicated Flux Kustomization.

patches:
# Remove the base Secret-based webhook-cert volume and volumeMount so we
Expand Down