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

Missing support other kind of source in additional firewall rules #252

Open
g-iannelli opened this issue Feb 15, 2023 · 1 comment
Open

Comments

@g-iannelli
Copy link
Contributor

g-iannelli commented Feb 15, 2023

As now It's supported only the "single IPv4 address" as source of the additional firewall rules in Spec.Kubernetes.NodePool.AdditionalFirewallRule, please add the missing one from the following list:

  • A single IPv4 address. You must use the /32 prefix length. For example, 203.0.113.1/32.
  • A single IPv6 address. You must use the /128 prefix length. For example, 2001:db8:2345:1a00::123/128.
  • A range of IPv4 addresses, in CIDR block notation. For example, 203.0.113.0/24.
  • A range of IPv6 addresses, in CIDR block notation. For example, 2001:db8:2345:1a00::/64.
  • The ID of a prefix list. For example, pl-1234abc1234abc123. For more information, see Prefix lists in the Amazon VPC User Guide.
  • The ID of a security group (referred to here as the specified security group). For example, the current security group, a security group from the same VPC, or a security group for a peered VPC. This allows traffic based on the private IP addresses of the resources associated with the specified security group. This does not add rules from the specified security group to the current security group.

Ref: AWS docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants