Skip to content
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

Improve windows logs when it comes to iptables #1939

Open
manuelbuil opened this issue Apr 12, 2024 · 0 comments
Open

Improve windows logs when it comes to iptables #1939

manuelbuil opened this issue Apr 12, 2024 · 0 comments
Assignees

Comments

@manuelbuil
Copy link
Collaborator

Expected Behavior

Current Behavior

We see the following logs:

I0412 09:55:06.903005    4612 main.go:567] Starting flannel in iptables mode
W0412 09:55:06.903005    4612 iptables_windows.go:39] unimplemented
W0412 09:55:06.903005    4612 main.go:530] no subnet found for key: FLANNEL_IPV6_NETWORK in file: /run/flannel/subnet.env
W0412 09:55:06.903005    4612 main.go:530] no subnet found for key: FLANNEL_IPV6_SUBNET in file: /run/flannel/subnet.env
W0412 09:55:06.903005    4612 iptables_windows.go:50] unimplemented
I0412 09:55:06.903005    4612 kube.go:476] Creating the node lease for IPv4. This is the n.Spec.PodCIDRs: [10.42.2.0/24]

which could be considered alarming by users when reading unimplemented or reading iptables mode even if they are in Windows

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

  • Flannel version:
  • Backend used (e.g. vxlan or udp):
  • Etcd version:
  • Kubernetes version (if used):
  • Operating System and version:
  • Link to your project (optional):
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants