[WIP][Feature]Configuraion support for kubernetes-client/c

[ityuhui]

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

c/kubernetes/config 

and some source files

c/kubernetes/config/kube_config.h
c/kubernetes/config/kube_config.c

to hold the utility functions.

What methods should we support at least ?

• Basic Auth (username/password)
• X509 Client certificate
• Bearer tokens
• encryption/TLS

[brendandburns]

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.

[ityuhui]

Status updated on Aug 21, 2020

1. Support GCP, Azure, AWS by plugin library (the plugin framework and OIDC plugin are Implemented by PR [Configuration] Authentication plugin #26)

2. Support exec following the specification https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuration (Implemented by PR [Configuration] Support exec for kubeconfig #12)

3. Support load_k8s_config_in_cluster for

• Bearer tokens ( Implemented by PR [Configuration]Support bearer tokens in cluster #10)

4. Support load_k8s_config_out_of_cluster for

• Bearer tokens
• X509 Client certificate ( Implemented by PR [Configuration]Support X509 client certificate in kube config file #9)

[ityuhui]

SSL client authentication is implemented by #7

[ityuhui]

X509 client certificate in kube config file is supported by the PR #9

[ityuhui]

Configuration of service token and CA in cluster is supported by the PR #10

[ityuhui]

exec (https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuration) is supported by the PR #12

[ityuhui]

auth provider plugin framework and OIDC plugin are implemented by the PR #26

[ityuhui]

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.

[fejta-bot]

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

[ityuhui]

/remove-lifecycle stale

Use this ticket to trace the current status of configuration support.

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.