You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: