-
Notifications
You must be signed in to change notification settings - Fork 295
CREATE_FAILED AWS::EFS::MountTarget Subnet0MountTarget mount target already exists in this AZ #208
Comments
@nicerobot Thanks for re-creating this! Revisiting my comment on the former issue coreos/coreos-kubernetes#802 (comment); |
@mumoshu I have provided an EFS Id of an existing resource that is already mounted on the subnets in which I'm placing k8s. What I want is simply to be able to specify the EFS Id and have a flag to indicate that it doesn't need to mount the subnets (alternatively, somehow check before creation if EFS is mounted to the needed subnets). |
@nicerobot Ah, so if you had the flag to cancel creating mount targets, the EFS will still be mounted successfully via |
@mumoshu Hmmm ... 🤷♂️ |
@nicerobot Thanks for replying! Please forgive me if I had gotten too deep in my previous comment. I'm open for questions/discussions to resolve your issue anyways. AFAIK:
So:
If so, could you try going ahead with removing If that works, I guess the flag added to kube-aws as you've suggested makes sense to me. |
@mumoshu So i just uncommented It makes sense again. I already have all the AZs mounted for the EFS volume which is why I needed the flag to ignore the mount. I was confusing myself with subnet references instead of thinking of AZs. Anyway, I can try again with the removing of the mount from the template again. When I did that before, the cluster wouldn't start because of the |
@nicerobot Thanks for the info again 👍 AFAIK a kube-aws cluster won't fail to start because of errors in Also, could you manually update mount targets from e.g. the AWS console to include the subnets created via kube-aws after |
@mumoshu 👍 Will do. It's starting now. Also, the |
@mumoshu Ok, indeed, the cluster seems fine. The
So, to fix that error, I have to add the kube-aws subnets to EFS mount targets but we have that volume mounted across other hosts across AZs on different subnets. And it only allows one subnet per AZ. So it seems like we can't even use this volume with k8s? |
@nicerobot Thanks for the info! |
@mumoshu Thanks. No worries. I can make due without EFS for the time being. And we might be transitioning to tectonic once install supports targeting an existing VPC where I'm hopeful this'll already be available ;-) |
@nicerobot Hi, deployments to existing subnets is experimentally supported since v0.9.4-rc.1 released today. subnets:
- name: SubnetWithEFS
availabilityZone: ...
id: subnet-...
worker:
subnets:
- name: SubnetWithEFS Please be sure that you've properly associated the existing subnet with the EFS like we've discussed above. |
@mumoshu Nice. Thanks. I've tried it but something seems to be failing on the controller.
Though I'm not so sure it's due to the new config. I've reverted to the prior |
@mumoshu So i reverted to
|
Hi @nicerobot thanks for the feedback!
|
@mumoshu Yep. I run Original:
vs new subnets feature:
|
@nicerobot Thanks again for the feedback! Excuse me if I've missed writing documentation for that but:
|
@mumoshu Thanks. No worries. Good information. I'll Make those updates and try again this weekend (I hope). |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Following the docs and customizing
cluster.yaml
, i reachIf i specify my existing elasticFileSystemId which is already in use and allocated to the subnets I'm specifying for the AWS-native auto-scaling:
It appears that
kube-aws
is attempting to mount the subnets to my existing EFS which causes it to fail:I've removed the following from
stack-template.json
:But maybe there should be another flag that asks whether to mount.
The text was updated successfully, but these errors were encountered: