Skip to content

CAPM3 (capm3-system namespace pods) should not be running among workloads #940

@tuminoid

Description

@tuminoid

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:

  • CAPM3 version: any/latest
  • Environment (metal3-dev-env or other): any

/kind bug
/kind documentation
/assign @lentzi90

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.kind/documentationCategorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.

Type

No type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions