Skip to content

Allow modification to Ports section for FixedIP addition #2393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sachinphogat opened this issue Jan 24, 2025 · 4 comments
Open

Allow modification to Ports section for FixedIP addition #2393

sachinphogat opened this issue Jan 24, 2025 · 4 comments
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.

Comments

@sachinphogat
Copy link

sachinphogat commented Jan 24, 2025

/kind feature

Describe the solution you'd like
Allow addition of FixedIP post openstackmachine creation. This will help implement external IPAM solution. Post OpenstackMachine is created, I have developed external validating webhook to block OpenstackServer creation so that IPAM system will add FixedIP to openstack machine and validating webhook will let OpenstackServer to be created.

We need to allow modification to Ports spec for FixedIP addition post creation.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 24, 2025
@EmilienM
Copy link
Contributor

The OpenStackMachine is immutable, I don't think we can do that, right @mdbooth ?

@sachinphogat
Copy link
Author

Can we enhance by allowing this through validating webhook?

@mdbooth
Copy link
Contributor

mdbooth commented Jan 27, 2025

@sachinphogat As @EmilienM says machines are immutable, but this is more about 'we don't modify them after they've been created'. However, I think it could be valid, e.g. to use a lifecycle hook which prevents creation until external actors have had an opportunity to modify the object.

Can you do me a favour? Please can you start a conversation in #cluster-api slack about this and gather some ways others have achieved it and link that conversation here? I have a feeling it should involve lifecycle hooks rather than a mutating webhook, but I haven't done enough reading about how they are implemented to be sure.

I think this is a valid and interesting use case. Thanks!

@k8s-triage-robot
Copy link

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

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

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
Status: Inbox
Development

No branches or pull requests

5 participants