search

metal3-io / baremetal-operator

Bare metal host provisioning integration for Kubernetes
Apache License 2.0
567 stars 246 forks source link

BMO pods are running among workloads #1262

Open tuminoid opened 1 year ago

tuminoid commented 1 year ago

What steps did you take and what happened: As discussed in metal3-sec group related to https://github.com/metal3-io/baremetal-operator/pull/1241 BMO (Ironic) should not be running among user workloads, but with k8s controlplane or infra nodes.

What did you expect to happen: BMO/Ironic 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 @zaneb

Rozzii commented 1 year ago

/triage accepted

metal3-io-bot commented 1 year ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Rozzii commented 1 year ago

Would be welcomed I will move this to frozen, no need to always remove the stale /lifecycle frozen

metal3-io-bot commented 10 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Rozzii commented 10 months ago

/remove-lifecycle stale

metal3-io-bot commented 7 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

tuminoid commented 7 months ago

/remove-lifecycle stale

tuminoid commented 6 months ago

/lifecycle frozen