Support startup taint

[sylr]

Is your feature request related to a problem?/Why is this needed

I'd like the aws-ebs-csi-driver to implement a startup taint mechanism.

/feature

Describe the solution you'd like in detail

When you are dealing with clusters where nodes come and go often we want to ensure that those new nodes have all the required components before the actual workloads are started.

Cilium for example recommends that all nodes spawned in a cluster be added the taint node.cilium.io/agent-not-ready=true:NoExecute. The cilium agent, which is a required component in a cilium based cluster, tolerates that taint and, upon startup completion of the agent, removes the taint on the node so that the workload can be started with a network stack up and running.

When I start new nodes in a EKS / Karpenter / Cilium based cluster, it happens that workloads requiring mounting an EBS volume starts before the aws-ebs-csi-driver and the workloads enter a backoff loop which can be long.

I'd like to prevent that by adding a new startup taint to my new nodes, e.g.: ebs.csi.aws.com/agent-not-ready=true:NoExecute and I would like that this taint be removed upon aws-ebs-csi-driver startup completion.

[torredil]

/kind feature

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[olemarkus]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sylr]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ConnorJC3]

/remove-lifecycle stale

[torredil]

Thanks for the request, this feature will be available in 1.19.
/close

[k8s-ci-robot]

@torredil: Closing this issue.

In response to this:

Thanks for the request, this feature will be available in 1.19.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.