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

Support for networks with disabled port security #1758

Open
hellt opened this issue Jan 11, 2024 · 2 comments
Open

Support for networks with disabled port security #1758

hellt opened this issue Jan 11, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale.

Comments

@hellt
Copy link

hellt commented Jan 11, 2024

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:

      cloudProviderSpec:
        image: "nesc-baseimages-debian-11-latest"
        flavor: ea.008-0024
        network: k8s-net-20e4f34
        subnet: k8s-subnet-b4aa25e
        securityGroups: []
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

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

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 11, 2024
@kubermatic-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

@kubermatic-bot kubermatic-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale.
Projects
None yet
Development

No branches or pull requests

2 participants