-
Notifications
You must be signed in to change notification settings - Fork 136
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
[EBS CSI Driver] It is not compatible with Windows Managed Node Group #390
Comments
This issue has been automatically marked as stale because it has been open 30 days |
Has anyone looked into the provided example? This is issue still not answered either triaged to be removed. |
and what do the logs from the EBS CSI driver pod show you? |
I will shortly in the net couple of days. Thanks for looking into this @bryantbiggs |
@bryantbiggs thanks for your patience :) Regarding ebs csi driver logs, they are not for
From the above description we can say that the issue appears to be related to the Amazon VPC CNI plugin failing to obtain the private IPv4 address for the Windows pod running the EBS CSI driver. Questions1.- I spoke to @wellsiau-aws about this issue and he pointed me out to this list of prerequisites https://github.com/kubernetes-sigs/aws-ebs-csi-driver/tree/master/examples/kubernetes/windows. Looking at the 4 points, I have my doubts on point 2 and 3. Do I need to add them in the provider
2.- Looking at https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html. I am wondering if https://docs.aws.amazon.com/eks/latest/userguide/csi-iam-role.html is configured correctly by the current configuration or is there something else we need to add for Windows Managed Nodes.
3.- I tried to look at the terraform code here https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/blob/main/main.tf to understand what is happening under the scenes but there is not reference to ebs csi driver. Where should we look at the code for troubleshooting? 4.- Has anyone tried to run the *.tf files I provided? The issue is easy to reproduce locally I believe. Resources statusFinally, I'm attaching a snapshot of all resource created and status
|
I would re-visit your configurations, theres a number of mis-configurations. For example:
|
Thanks @bryantbiggs for your reply
Nope! Where can I find the accepted inputs for There is not reference to them either https://registry.terraform.io/modules/aws-ia/eks-blueprints-addon/aws/latest?tab=inputs neither https://aws-ia.github.io/terraform-aws-eks-blueprints-addons/main/ OK, I guess I can do something like this https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/3e9e5a13e7afee42d4b64874ba5adf73f329ff30/patterns/karpenter/main.tf#L117 Then adding tolerations like https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/charts/aws-ebs-csi-driver/values.yaml#L276-L281 Can you confirm my suggestion please?
Which docs please? Gotcha I need to enable this section https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/charts/aws-ebs-csi-driver/values.yaml#L384 using the same approach I explained above |
I'm closing this issue it was solved by using node selectors only for Node Pools I want to use EBS CSI driver
|
Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the
examples/*
directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by runningterraform init && terraform apply
without any further changes.If your request is for a new feature, please use the
Feature request
template.Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]: 1.15.1
Terraform version:
Terraform v1.6.6 on linux_amd64
Terraform v1.6.6 on linux_amd64
Reproduction Code [Required]
Considerations:
Steps to reproduce the behavior:
main.tf
provider.tf
Expected behaviour
EBS CSI Driver is deployed correctly
Actual behaviour
EBS CSI Driver is NOT deployed
Terminal Output Screenshot(s)
Additional context
eks_managed_node_groups
>mg_windows
section the ebs csi driver is deployed correctly.WINDOWS_CORE_2022_x86_64
ami type but it didn't work.The text was updated successfully, but these errors were encountered: