Update windows-support.adoc with access entry considerations #924
Conversation
add consideration for access entries type
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
| --policy-arn {arn-aws}iam::aws:policy/AmazonEKSVPCResourceController | ||
| ---- | ||
| . Create a file named [.replaceable]`vpc-resource-controller-configmap.yaml` with the following contents. | ||
| . If the VPC CNI *is not* installed as an Amazon EKS Add-on: |
There was a problem hiding this comment.
VPC CNI is is always installed for networking in k8s. This command just enable Windows-ipam inside VPC resource controller.
Rephrase the statement to, enable IPAM for Windows nodes in VPC resource controller using following ConfigMap.
There was a problem hiding this comment.
I think it matters if it's installed as a managed add-on or regular, right?
if it's a managed add-on, they need to configure the add-on
if it's regular, they can just update the config
does that make sense?
There was a problem hiding this comment.
CNI for Windows is different from Linux. Windows CNI is shipped in AMIs. It is not installed via addon.
2 participants
add consideration for access entries type