This message was deleted.
# generals
sparse-intern-71089
02/21/2023, 3:25 PMThis message was deleted.
b
billowy-army-68599
02/21/2023, 4:02 PM
Are you installing components into the cluster with Pulumi?
d
dry-keyboard-94795
02/21/2023, 4:24 PMit'd be
USE_GKE_GCLOUD_AUTH_PLUGIN: 'false'install_componentsv1.1.0 Copy code
- uses: 'google-github-actions/setup-gcloud@v1.1.0'
name: Setup gcloud SDK
with:
install_components: 'gke-gcloud-auth-plugin'b
billowy-army-68599
02/21/2023, 4:25 PM
sorry no, are using the kubernetes provider with pulumi?
d
dry-keyboard-94795
02/21/2023, 4:25 PMYes
dry-keyboard-94795
02/21/2023, 4:27 PMWent through the process of getting gke auth working already when GH Runners updated gcloud a couple of months ago
b
billowy-army-68599
02/21/2023, 4:32 PM
how do you build your gke provider?
d
dry-keyboard-94795
02/21/2023, 4:32 PM2 stacks, one uses a generated kubeconfig with the new gke-auth-plugin explicitly based off the cluster being made.
The other uses get-credentials, with gke-auth-plugin being implicit.
b
billowy-army-68599
02/21/2023, 4:36 PM
okay, have you run a successful update since you made those chances? The issue here is that the provider itself is stored in state., This error:
Copy code
Diagnostics:
kubernetes:core/v1:ConfigMap (log4j):
error: failed to initialize discovery client: The gcp auth plugin has been removed.
Please use the "gke-gcloud-auth-plugin" kubectl/client-go credential plugin instead.
See <https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke> for further detailsbillowy-army-68599
02/21/2023, 4:37 PM
it’s difficult to prescribe a fix here because i don’t have code to look at, but essentially you’ll need to make sure your provider instantiation is correct and is using the correct plugin
i
incalculable-potato-82285
02/21/2023, 4:39 PMYes, we‘re installing components.
So the fix would be to update the kubernetes provider with correct plugin?
b
billowy-army-68599
02/21/2023, 4:48 PM
yes, when i saw provider, i mean the provider code.
i
incalculable-potato-82285
02/21/2023, 4:56 PMOkay I‘ll check the code and will provide more information tomorrow
incalculable-potato-82285
02/22/2023, 8:16 AMSo basically we`re generating the kubernetes provider like this:
Copy code
export function GetK8sProvider(): k8s.Provider {
const k8sStackName= config.require("k8s-stack");
const k8sStack = new pulumi.StackReference(k8sStackName);
const kubeconfig = k8sStack.getOutput("kubeconfig");
const k8sProvider = new k8s.Provider("provider", {
kubeconfig: kubeconfig,
});
return k8sProvider;
}incalculable-potato-82285
02/22/2023, 8:17 AMInteressting thing is, if we do a "pulumi up" on the local machine, everything works fine - just in GitHub Action we run into the above Error
incalculable-potato-82285
02/22/2023, 8:20 AMhttps://github.com/pulumi/examples/blob/d11f2289a3418ad905ee43fa5dfc0104267ac1c9/gcp-ts-gke/cluster.ts#L75 i think i found the solution here - we`re not passing the command: gke-gcloud-auth-plugin to the kubeconfig
👍 1
incalculable-potato-82285
02/22/2023, 4:52 PM@billowy-army-68599 Thanks a lot again! You´re Hint helped a lot and we got the action running again!
🎉 1
5 Views