-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle kubeconfig contents or path in provider #1255
Conversation
Previously, we only handled the contents of a kubeconfig as configuration for the k8s provivder. This change now additionally supports passing in the path to a kubeconfig. An error is only returned if both of these options fail to load a valid k8s configuration.
Love it! |
Is it possible to also support a |
This change fixes that as well. Tested with the following: import * as k8s from "@pulumi/kubernetes";
import * as eks from "@pulumi/eks";
const cluster = new eks.Cluster("test", {
providerCredentialOpts: {profileName: process.env.AWS_PROFILE},
});
const provider = new k8s.Provider("test", {kubeconfig: cluster.kubeconfig})
new k8s.core.v1.Namespace("test", undefined, {provider})
|
Proposed changes
Previously, we only handled the contents of a kubeconfig
as configuration for the k8s provivder. This change now
additionally supports passing in the path to a kubeconfig.
An error is only returned if both of these options fail to
load a valid k8s configuration.
Related issues (optional)
Fix #1252