-
Notifications
You must be signed in to change notification settings - Fork 278
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
Calico pollutes the rke2-win logs #4722
Comments
Not really seeing this much verbosity in the logs on reproduction - maybe it was more prevalent on k3s. ##Environment Details Infrastructure
Node(s) CPU architecture, OS, and version:
Cluster Configuration:
Config.yaml:
Not Reproducible
Results: $ sudo journalctl --no-pager | grep -i calico
VS $ sudo INSTALL_RKE2_COMMIT=302b2915ff5013cb3f566c455cfdefe54a0e8882 INSTALL_RKE2_EXEC=server ./install-rke2.sh
$ sudo journalctl --no-pager | grep -i calico
PS C:\Users\Administrator> get-eventlog -logname System -Source "rke2"
PS C:\Users\Administrator> get-eventlog -logname System -Source "calico"
|
@manuelbuil unless you can offer comment I'm going to just close the related issues for this linked back here. |
You were looking at logs in Windows agent right? You did not see a lot of logs before the PR? |
Better sample of windows agent logging noise below BeforeFix$ get-eventlog -logname Application -source 'rke2' | select-object -Property TimeWritten,ReplacementStrings | format-table -wrap
AfterFix$ get-eventlog -logname Application -source 'rke2' | select-object -Property TimeWritten,ReplacementStrings | format-table -wrap
|
Environmental Info:
RKE2 Version:
Windows
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
Calico starts right after we start the different kubernetes components (e.g. kubelet). As a consequence, it takes a bit until everything is ready for Calico to start correctly. We are starting calico as par of an infinite loop and thus, we get ~20 times the same log:
Steps To Reproduce:
Install rke2 windows with calico as the CNI plugin
Expected behavior:
See a couple of times the same log
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered: