Skip to content
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

Allow AWS securityGroupOverrides #9268

Open
ethanchowell opened this issue Dec 4, 2024 · 2 comments · May be fixed by #9429
Open

Allow AWS securityGroupOverrides #9268

ethanchowell opened this issue Dec 4, 2024 · 2 comments · May be fixed by #9429

Comments

@ethanchowell
Copy link

In our environment, we're not allowed to create new security groups which essentially forces us into the UPI model even though we have permissions to do everything else the installer needs. Using the UPI model makes things difficult because we then have to break apart the documented cloudformation to separate out actions based on IAM roles we have to assume.

I've been able to generate the capi manifests from the installer and patch those to get a working deployment using the securityGroupOverrides, but being able to handle this purely through the install-config would significantly simplify things and make OpenShift a more viable solution for our environments.

@ethanchowell ethanchowell linked a pull request Feb 3, 2025 that will close this issue
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2025
@ethanchowell
Copy link
Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants