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

Add a test for 'Change log level on the fly without restart ' #12522

Open
denis-tingaikin opened this issue Nov 5, 2024 · 1 comment
Open
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@denis-tingaikin
Copy link
Member

TODO:

  1. Add a new README.md file into the features suite: https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/features
  2. Add a step to change log level for the nsmgr/fforwarder via sginal (just use kubectl exec for the nsm app in the nsm-system namespace, note: SIGUSR1, SIGUSR2 should be used).
  3. Make sure that logs level is changing (kubectl logs --since=1m can be used).
  4. Contribute the example.
@arp-est
Copy link
Contributor

arp-est commented Nov 29, 2024

Hi, I've two prs for this,
#12572
and networkservicemesh/integration-k8s-kind#1043,
In the second pr, since I'm fiddling with the forwarder daemonset in the tc, to ensure the loglevel is not TRACE,
I've added the test to the 'WithRunningTestsSynchronously' part, to make sure that it does not interfere with the other test runs.

Please review when you have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
Status: Todo
Development

No branches or pull requests

3 participants