cleanup: unexport kubernetes.Client method #1973
Merged
+22
−30
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.
Signed-off-by: Jason Hall [email protected]
The method is only used inside the package, and we shouldn't recommend folks depend on it, so let's unexport it.
The method encapsulates trying to create a k8s client from local environment config, and if one can't be found, it falls back to creating an in-cluster k8s client. This is used by both the policy controller, which uses the in-cluster config, and
cosign generate-key-pair k8s://ns/secret-name
, which may use a regular user config, or if run in a K8s cluster, would use the in-cluster config. As the policy controller moves out to its own repo we might want to consider just having it assume the in-cluster config.This change also collapses three methods into one, for simplicity.
Release Note