简体   繁体   English

如何在不重新启动集群的情况下使用 Fargate 在 AWS EKS 中传播 DNS 主机名(网络更改)和/或角色更改?

[英]How to Propagate DNS Hostnames (Network Changes), and/or Role Changes Inside AWS EKS using Fargate without Relaunching the Cluster?

As the title suggests, I am unable to propagate Role, or any "Network" changes (AKA: Changing VPC DNS hostname flag to "Enabled" without deleting the entire cluster and relaunching.正如标题所示,我无法传播角色或任何“网络”更改(又名:将 VPC DNS 主机名标志更改为“已启用”,而无需删除整个集群并重新启动。


Usually in order to propagate these changes in EC2 or normal EKS (without fargate) I simply restart the server or node, respectively. 通常为了在 EC2 或普通 EKS(没有 Fargate)中传播这些更改,我只需分别重新启动服务器或节点。 With Fargate, this is not possible considering one doesn't have access to the underlying nodes. 使用 Fargate,考虑到无法访问底层节点,这是不可能的。 Is there a certain way to send commands to the node itself, or at least force a restart on the node in order to make these changes? 是否有某种方法可以向节点本身发送命令,或者至少强制重启节点以进行这些更改? Any help would be greatly appreciated! 任何帮助将不胜感激! Thanks 谢谢

Is there a certain way to send commands to the node itself, or at least force a restart on the node in order to make these changes?

You can try kubectl rollout restart deployment <name> to redeploy pods, which will cause Fargate to re-allocate your pods.您可以尝试kubectl rollout restart deployment <name>重新部署 pod,这将导致 Fargate 重新分配您的 pod。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM