Use explicit security context #545
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
When we switch to 1.4, we should also start to use an explicit security context. This is recommended by the capi book.
See kubernetes-sigs/cluster-api#7831 for details on how cluster-api does it.
/kind feature
The text was updated successfully, but these errors were encountered: