[CLOUDP-333407] Remove subcommand kubectl mongodb debug
#293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
There are two ways to collect diagnostic information from customers enviornments. Either we can ask them to run
kubectl mongodb debug
or we can ask them to runpublic/support/mdb_operator_diagnostic_data.sh
script.From the field we got to know that people prefer .sh over the binary, that's why it looks like we have been providing the .sh file to the users. And because of that having
kubectl mongodb debug
just confuses us as to, which one should be provided to the users. That's why this commit removes that subcommand.Proof of Work
Build the binary and make sure that
debug
subcommand has been removed.I tried to verify if we ever documented this, to make sure if we will have to change the docs or not. And it looks like this subcommand was not documented https://www.mongodb.com/docs/kubernetes/current/plugin-reference/. So we will not have to create/push release notes for this.
Checklist