Extend log-level commands to support managed clusters #365
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.
Extended all log-level commands
(set, show, unset)
to support managed clusters as requested in issue #41. Added optional parameters--namespace, --clusterName, and --clusterType
to enable log level management in both ClusterAPI and SveltosCluster managed clusters usingclusterproxy.GetKubernetesClient
. Maintains full backward compatibility with existing management cluster functionality.I first created the test cluster and then ran the actual deployment.
Examples of testing
Some new unit tests passsing:
Management Cluster Tests (Backward Compatibility):
Managed cluster tests
For managed clusters