-
Notifications
You must be signed in to change notification settings - Fork 17
Collect logs context switch #3
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
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Johan Cornelissen <johan1252@gmail.com>
Co-authored-by: Johan Cornelissen <johan1252@gmail.com>
|
Thank you for the Review. I have seen that i missed removing the resultdir flag and the corefile pattern. |
|
Hi @Hounddog, thanks for contributing. Can you elaborate more about your use case where you can't use environment variables to specify release and namespace? |
|
I have no reason for this. My only concern here is that smartcheck has a similar script and uses parameters instead of environment variables. I personally also feel that i am more flexible with parameters to change them as required |
It is required for us to set the context in the logs to select which cluster should be used.
I have removed the need to use Environment variables and instead provide parameters. (Similar to smartcheck implementation)
I have implemented a context switch to switch between prod and staging Kubernetes cluster.
The Readme has been updated to Reflect the changes.
I was able to use this locally to provide logs to your support team.