prebootstrapcommand in machinepool / managed machinepool

[kholisrag]

/kind feature

Describe the solution you'd like
a preBootstrapCommand feature like that eksctl have, maybe both in unmanaged node / managed node. its greate feature for all of us I believe

Anything else you would like to add:
for our case, we need to mount the instance store of aws ec2 instance and be able to use it in hostPath of PersistentVolume

[randomvariable]

For EC2, you can do that already in KubeadmConfigTemplate and KubeadmControlPlane under preKubeadmCommands.

[kholisrag]

@randomvariable if we use eks and unmanaged node we can do that? can you elaborate more how to do it?

[randomvariable]

Sorry, I misread this. This is indeed a missing feature.

/priority critical-urgent

[richardcase]

I'll pick up this as part of my work on launchtemplates as it touches that area for machine pools (managed/unmanaged):

/assign
/lifecycle active

[richardcase]

Will include this along with #2854 instead of the launch templates change.

[richardcase]

Moving miletone

/milestone v1.2.0

[sedefsavas]

We may need to take this into account during Launch Templates design: #3024

[sedefsavas]

Since this is not only relevant to MachinePools, we need to come up with a generic solution for all Machines as @richardcase pointed.

This is blocking enabling clusterctl upgrade tests, which will help to catch conversion related issues, so adding release-blocking tag.

[cnmcavoy]

Interested in this functionality and trying to understand where it is at...given that #2854 was closed in preference to #2965 and neither addressed the missing bootstrapping features for this issue.

Is working on this issue blocked on #3024 being merged? What work remains before a PR could be submitted to add this functionality?

[richardcase]

@cnmcavoy - its being some separately. Theres only a small amount of work to do...will get it finished in the next few days.

[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

[richardcase]

/remove-lifecycle stale

[richardcase]

/milestone v1.6.0

[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

[Skarlso]

I believe this will be handled by #3757

[richardcase]

I believe this will be handled by #3757

Yes it will. My change was stopped in favour of #3757

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.