Closed ityuhui closed 3 years ago
We should definitely also support exec
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuration
and probably clouds (GCP, Azure, AWS) auth.
Ideally we can make it pluggable so that people can dynamically register new authentication methods.
Status updated on Aug 21, 2020
Support GCP, Azure, AWS by plugin library (the plugin framework and OIDC plugin are Implemented by PR https://github.com/kubernetes-client/c/pull/26)
Support exec
following the specification https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuration (Implemented by PR https://github.com/kubernetes-client/c/pull/12)
Support load_k8s_config_in_cluster for
Support load_k8s_config_out_of_cluster for
SSL client authentication is implemented by https://github.com/kubernetes-client/c/pull/7
X509 client certificate in kube config file is supported by the PR https://github.com/kubernetes-client/c/pull/9
Configuration of service token and CA in cluster is supported by the PR https://github.com/kubernetes-client/c/pull/10
exec (https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuration) is supported by the PR #12
auth provider plugin framework and OIDC plugin are implemented by the PR https://github.com/kubernetes-client/c/pull/26
Considering most of configuration cases are supported, I will suspend this task from now.
If other authentication method (e.g. AWS, Azure, GCP) is needed, I can continue by demand. And PR is welcome.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
Use this ticket to trace the current status of configuration support.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-contributor-experience at kubernetes/community. /close
@fejta-bot: Closing this issue.
Hi @brendandburns
In order to meet the requirement of client bronze requirements , I begin to implement the configuration utility now.
My design is adding a directory "config" under the directory kubernetes
and some source files
to hold the utility functions.
What methods should we support at least ?