Fall back to rudimentary login handlers if the clients are absent #771
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.
This will make Kopf runnable in the majority of cases even with no
pykube-ng
andkubernetes
client libraries installed. This was not a problem till recently, but thenpykube-ng
was removed from the implicit dependencies (#655), so users get frustrated by "unauthenticated" or "ran out of credentials" errors (#349 #187, partially solved in #770).Two extra functions are added to the public interface:
kopf.login_with_kubeconfig()
kopf.login_with_service_account()
They can only read the rudimentary (but usually sufficient) data and pass them to the API requests "as is", with no post-processing or interpretation (or token rotation, or whatever the client libraries can provide).
To avoid running too many login handlers at startup, the rudimentary login handlers are added strictly when the client libraries are absent, not always. This can be overridden with custom login handlers calling these functions (as documented).
TODOs: