Skip to content

Conversation

@Hounddog
Copy link

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.

Hounddog and others added 2 commits October 21, 2022 10:17
Co-authored-by: Johan Cornelissen <johan1252@gmail.com>
Co-authored-by: Johan Cornelissen <johan1252@gmail.com>
@Hounddog
Copy link
Author

Hounddog commented Oct 21, 2022

Thank you for the Review. I have seen that i missed removing the resultdir flag and the corefile pattern.
Removed these lines from the help

@holyspectral
Copy link
Contributor

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?

@Hounddog
Copy link
Author

Hounddog commented Nov 4, 2022

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

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

Successfully merging this pull request may close these issues.

4 participants