Skip to content

Migrate Kubelet --experimental-allowed-unsafe-sysctls to kubelet.config.k8s.io or remove the flag #61669

Closed
@mtaufen

Description

Flag name: experimental-allowed-unsafe-sysctls

Help text:

Comma-separated whitelist of unsafe sysctls or unsafe sysctl patterns (ending in *). Use these at your own risk.


This is part of migrating the Kubelet command-line to a Kubernetes-style API.

The --experimental-allowed-unsafe-sysctls flag should either be migrated to the Kubelet's kubelet.config.k8s.io
API group, or simply removed from the Kubelet.

If this could be considered an instance-specific flag, or a descriptor of local topology
managed by the Kubelet, see: #61647.

If this flag is only registered in os-specific builds, see: #61649.

As --experimental-allowed-unsafe-sysctls is an alpha/experimental flag, the feature it configures must either be
feature-gated, or graduated from alpha/experimental status prior to the migration.

@sig-node-pr-reviews @sig-node-api-reviews

/assign @mtaufen
/sig node
/kind feature
/priority important-soon
/milestone v1.11
/status approved-for-milestone

Metadata

Labels

kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/nodeCategorizes an issue or PR as relevant to SIG Node.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions