Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

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

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

Description

/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-priority needs-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

        AltStyle によって変換されたページ (->オリジナル) /