-
Notifications
You must be signed in to change notification settings - Fork 124
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
Support for networks with disabled port security #1758
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. /close |
@kubermatic-bot: Closing this issue. In response to this:
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. |
I have a network with the disabled port security. On such a network one can not (and doesn't want) to apply any security groups.
When I manually create the instance on a network like this I remove the default security group for instance to spawn.
With machine controller spec like this it seems it still tries to apply the default security group because nova can't create the instance with an error that port-security should be enabled when adding security groups:
The text was updated successfully, but these errors were encountered: