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

Configurable OpenStack SecurityGroups #389

Open
elenz97 opened this issue Feb 2, 2022 · 2 comments
Open

Configurable OpenStack SecurityGroups #389

elenz97 opened this issue Feb 2, 2022 · 2 comments
Labels
area/networking Networking related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/openstack OpenStack platform/infrastructure

Comments

@elenz97
Copy link
Contributor

elenz97 commented Feb 2, 2022

How to categorize this issue?

/area networking
/kind enhancement
/platform openstack

What would you like to be added:

A configuration option to specify custom OpenStack SecurityGroups using this extension.
From what i know, customizing OpenStack SecurityGroups should only be possible by specifying the desired configuration in the templates inside ./pkg/internal/infrastructure/templates.
As of now, the rules specified in main.tpl.tf are static and use openstack_networking_secgroup_v2.cluster.[id|name] to bind to the desired cluster.

Why is this needed:

Apparently, the OpenStack SecurityGroups that are deployed via this extension cannot be configured externally, as they are statically baked into the template - Please correct me if i'm wrong on this. However, the default rules created are undesirable in production use-cases, since they enable all TCP/UDP traffic from/to any network source.

I'd be glad on getting any hint to support the above using this extension. If there is a chance of implementing this in a reasonable way, i'd also be ready to prepare a PR for it.


Since the project seems to be transitioning off of the usage of Terraform (#362), the implementation of this doesn't have to be in form of extending the existing templates. This might rather be seen as a good occasion to migrate logic into a go package using the gophercloud SDK instead.

@elenz97 elenz97 added the kind/enhancement Enhancement, improvement, extension label Feb 2, 2022
@gardener-robot gardener-robot added area/networking Networking related platform/openstack OpenStack platform/infrastructure labels Feb 2, 2022
@elenz97
Copy link
Contributor Author

elenz97 commented May 11, 2022

Hello, could anyone give me an update on the above?

@gardener-robot
Copy link

@SvenMW Command /add is not available to you but only to a Maintainer, Member, Author.

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 9, 2022
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking Networking related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/openstack OpenStack platform/infrastructure
Projects
None yet
Development

No branches or pull requests

2 participants