Ok, I have a few big blockers unfortunately and could really use some guidance on these. I’ve mentioned some of these previously but I’ll list them here with the context that I’ve gathered while digging… 1. GCP (GKE) Kube cluster is currently recreated every time I run pulumi up a. I am attempting to understand the diff in order to remove anything that changes and causes it to recreate b. On the second and subsequent runs, the oauth scopes appear to be deleted - could this cause it? or is this normal and just sending me the wrong direction?

~ nodeConfig: {
          ~ oauthScopes: [
              - [0]: "<https://www.googleapis.com/auth/monitoring>"
              - [1]: "<https://www.googleapis.com/auth/logging.write>"
            ]
        }

2. I’m trying to generate a kubeconfig and use that to create a provider for my gke cluster however every time I get an error for line 5 in the yaml.

error: rpc error: code = Unknown desc = failed to parse kubeconfig: yaml: line 5: found character that cannot start any token

Code is like this:

func generateKubeconfig(clusterEndpoint pulumi.StringOutput, clusterName pulumi.StringOutput,
	clusterMasterAuth container.ClusterMasterAuthOutput) pulumi.StringOutput {
	context := pulumi.Sprintf("dimo_%s", clusterName)
	clusterCaCertificate := clusterMasterAuth.ClusterCaCertificate().Elem()
	fmt.Printf("(gen config) clusterCaCertificate: %v", clusterCaCertificate)
	fmt.Printf("(gen config) clusterEndpoint: %v", clusterEndpoint)

	return pulumi.Sprintf(`apiVersion: v1
clusters:
- cluster:
		certificate-authority-data: %v
		server: <https://%v>
	name: %s
contexts:
- context:
    cluster: %s
    user: %s
  name: %s
current-context: %s
kind: Config
preferences: {}
users:
- name: %s
  user:
    exec:
      apiVersion: <http://client.authentication.k8s.io/v1beta1|client.authentication.k8s.io/v1beta1>
      command: gke-gcloud-auth-plugin
      installHint: Install gke-gcloud-auth-plugin for use with kubectl by following
        <https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke>
      provideClusterInfo: true
`, clusterCaCertificate, clusterEndpoint, context, context, context, context, context, context)
}

You can see the full context here: https://github.com/phutchins/dimo-node/blob/main/infrastructure/k8s_provider_gke.go

Hi. Your

name

field does not belong to server section.

It belongs to the cluster section. That should be in the right place. I compare it to my actual kube/config and it looks right (in the code at least, and even in the logs from what I can tell).

@kind-fireman-33438 That’s indeed very odd! So the random

\t

character was in the Kubeconfig, which in turn was used to create an explicit provider, is that right?