CAPM3 (capm3-system namespace pods) should not be running among workloads #940
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
triage/accepted
Indicates an issue is ready to be actively worked on.
What steps did you take and what happened:
As discussed in metal3-sec group related to metal3-io/baremetal-operator#1241 CAPM3/IPAM (capm3-system namespace) should not be running among user workloads, but with k8s controlplane or infra nodes.
What did you expect to happen:
CAPM3/IPAM (capm3-system) is running on controlplane or in infra nodes, not among regular workload. These should be sensible default value, and documentation should be available to explain the options.
Environment:
/kind bug
/kind documentation
/assign @lentzi90
The text was updated successfully, but these errors were encountered: