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

Proposal: New rule for kubernetes clusters on Azure CNI #189

Open
tspearconquest opened this issue Aug 20, 2022 · 0 comments
Open

Proposal: New rule for kubernetes clusters on Azure CNI #189

tspearconquest opened this issue Aug 20, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@tspearconquest
Copy link

tspearconquest commented Aug 20, 2022

According to the Microsoft Docs for Azure CNI, when configuring a cluster to use Azure CNI, you need to create 2 subnets in your virtual network, and assign one to the cluster via vnet_subnet_id, and the other to the in-cluster service network via service_cidr.

It is a mistake to configure a cluster with only 1 subnet that and then configure a smaller CIDR block from that same subnet as the service_cidr, however tflint does not currently highlight this issue and azure does not generate an error or warning message.

Configuring a single subnet for a cluster with Azure CNI will work only under a limited (and diminishing) set of circumstances, and it is not supported by Microsoft. Since service_cidr is only set at cluster creation, and cannot be changed afterward, it would be great if this issue can be highlighted by tflint.

@wata727 wata727 added the enhancement New feature or request label Aug 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants