You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we are in dualStack mode, metrics and kube-dns services are all SingleStack. We can manually change that but I think it makes more sense if both were dualStack automatically
Steps To Reproduce:
Installed K3s:
Deploy k3s in dualStack mode and check the ipFamilyPolicy: in metrics-server and kube-dns services
Expected behavior:
Services have an ipv4 and an ipv6 address when deployed in dualStack mode
Actual behavior:
Services only have on IP address when deployed in dualStack mode
Additional context / logs:
The text was updated successfully, but these errors were encountered:
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
This bug is covered by a bigger bug: rancher/rke2#4772
When we are in dualStack mode, metrics and kube-dns services are all SingleStack. We can manually change that but I think it makes more sense if both were dualStack automatically
Steps To Reproduce:
Deploy k3s in dualStack mode and check the
ipFamilyPolicy:
in metrics-server and kube-dns servicesExpected behavior:
Services have an ipv4 and an ipv6 address when deployed in dualStack mode
Actual behavior:
Services only have on IP address when deployed in dualStack mode
Additional context / logs:
The text was updated successfully, but these errors were encountered: