Skip to content

Support configuring custom k8s node port range in security groups #5617

@Algeran

Description

@Algeran

/kind feature

Describe the solution you'd like
As a Service Consumer I want to be able to properly configure custom k8s node port range in AWSCluster

Anything else you would like to add:
Currently, controller bootstraps security groups with rules for default k8s node port range and it's not possible to change the behaviour.

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions