Probably I didn't explain myself correctly.

I'm happy to add withKubeConfig(String) if this method delivers the functionality to provide the .kube/config content as a String. After your minor elaboration, this is what I now understand you're requesting (as opposed to withKubeConfig("/home/user/.kube/config") which is what I won't add unless someone really makes a case for this).

However, you still haven't elaborated on your use case. It's my understanding that you would be running this in a build automation tool and passing the content of .kube/config by retrieving it from a secret. If this is the case, note that helm-java is actually leveraging helm libs under the covers, and it's likely that you can pass a lot of information using variables such as: HELM_KUBEAPISERVER, HELM_KUBECAFILE, HELM_KUBETOKEN, and so on).

official kubernetes java client.

I wouldn't use the Official Kubernetes Java Client as an example of API-friendly when you get horrible things such as:

V1PodList list = api.listPodForAllNamespaces(null, null, null, null, null, null, null, null, null);

Especially when you can use the Fabric8 Kubernetes Client that provides completely fluent interfaces 😉

PodList podList = client.pods().inAnyNamespace().list();

Allow providing kubeconfig from String #52

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions