Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Problem:
When you create a k8s node_pool a default security group is created but:
You can't manage this security group
You can't change the name of this security group
You can't associate a security created previously with your node pool
Today you have only one solution:
Create one security group with the namge "kubernetes + Cluster ID before node pool creation"
This security group will automatically associate with your node pool after creation (Explicit dependency mandatory to create security group before node pool)
Hello,
Community Note
Description
Problem: When you create a k8s node_pool a default security group is created but:
Today you have only one solution:
Documentation: https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/secure-cluster-with-private-network/#how-can-i-access-my-cluster-via-my-nodes-public-ips-for-specific-use-cases
Can you add the security_group management inside "scaleway_k8s_pool" resource ?
Use cases example:
New or Affected Resource(s)
Potential Terraform Configuration
Association example with existing security group:
Default security group with basic switch to activate smtp feature:
Additional rule: If "security_group_id" is defined, "default_security_group" block is ignored.
Thank you and don't hesitate if you have question.
Regards,