We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v4.3.0
您好,在使用sealos 4.3.0版本部署k8s环境时遇到了coredns必须要连接公网才能让组件访问速度正常的情况,否则在服务器断开公网链接后再访问k8s应用时就比较慢,链接到公网就又变快了【k8s版本v1.27.5和calico 3.26.1以及k8s版本v1.24和calico 3.24.1 这两个组合都复现了此种情况】,请见附件,麻烦帮忙看下,谢谢,期待回复
No response
- Sealos version:4.3.0 - Containerd version:v1.7.15 - Kubernetes version:1.27.5 - Operating system:ubuntu 20.04.6 LTS - Runtime environment:Containerd - Cluster size: single - Additional information:
The text was updated successfully, but these errors were encountered:
This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.
Sorry, something went wrong.
No branches or pull requests
Sealos Version
v4.3.0
How to reproduce the bug?
您好,在使用sealos 4.3.0版本部署k8s环境时遇到了coredns必须要连接公网才能让组件访问速度正常的情况,否则在服务器断开公网链接后再访问k8s应用时就比较慢,链接到公网就又变快了【k8s版本v1.27.5和calico 3.26.1以及k8s版本v1.24和calico 3.24.1 这两个组合都复现了此种情况】,请见附件,麻烦帮忙看下,谢谢,期待回复
What is the expected behavior?
What do you see instead?
No response
Operating environment
Additional information
No response
The text was updated successfully, but these errors were encountered: