SecurityGroup does not have Rules for IPv6

[modzilla99]

/kind bug

What steps did you take and what happened:
IPv6 connectivity is impossible with IPv6 when using the CAPI managed SecurityGroups. The only allowed traffic is egress.

What did you expect to happen:
Allow all the ports that are allowed in v4 land on v6. (10250, 2379, 2380...) At the very least if I enable all node to node communication, IPv6 should be allowed as well.

Anything else you would like to add:
Anything helping the use of IPv6 is very welcome. (Dual-Stack Network creation and SubnetPool use for example)

Environment:

• Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): v0.12.3
• Cluster-API version: v1.10.1
• OpenStack version: Victoria
• Kubernetes version (use kubectl version): v1.33.0

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale