No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

are you setting a `provider` on your Kubernetes resources?
if not, you'll need to set a `KUBECONFIG` to talk to your kubernetes cluster

yes, using
```
import { clusterProvider } from '../../gcp/gke';

const tn = "testtest";
export const t = new k8s.core.v1.Namespace(tn, {
  metadata: {
      name: tn,
  }
}, {
  provider: clusterProvider,
});```

and the clusterProvider is created by
```export const kubeconfig = pulumi
  .all([cluster.name, cluster.endpoint, cluster.masterAuth])
  .apply(([name, endpoint, masterAuth]) =&gt; {
    const context = `${gcp.config.project}_${gcp.config.zone}_${name}`;
    return `apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ${masterAuth.clusterCaCertificate}
    server: https://${endpoint}
  name: ${context}
contexts:
- context:
    cluster: ${context}
    user: ${context}
  name: ${context}
current-context: ${context}
kind: Config
preferences: {}
users:
- name: ${context}
  user:
    auth-provider:
      config:
        cmd-args: config config-helper --format=json
        cmd-path: gcloud
        expiry-key: '{.credential.token_expiry}'
        token-key: '{.credential.access_token}'
      name: gcp
`;
  });

export const clusterProvider = new k8s.Provider(clusterName, {
    kubeconfig: kubeconfig,
});```

I guess the diff between local and gitlab ci is that i have gcloud setup locally and in gitlab ci its just using the pulumi image as base

the kubeconfig will need to have a token etc, if that isn't valid (it may be your google creds arent valid for the cluster?) it'll error like it is

but its setting the token from the above code snippet? I just followed the gcp tutorial you guys provide

how are you setting in gitlab? does a `gcloud` command work correctly before your `pulumi up` ?

i highly doubt it because its just using a plain pulumi image, but i can try
```image:
  name: pulumi/pulumi
  entrypoint:
    - '/usr/bin/env'
    - 'PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'

stages:
  - infrastructure-update

pulumi:
  stage: infrastructure-update
  variables:
    PULUMI_STACK: nickjn92/pulumi-fleet/lab
  script:
    - npm ci
    - pulumi stack select $PULUMI_STACK
    - pulumi up --yes
  only:
  - main```

where are you setting `GOOGLE_CREDENTIALS` ?

i verified that its there by just doing an echo before the pulumi cmd

it's been a long while since I've used gitlab I'm afraid, but essentially my best guess is that the kubeconfig isn't getting the right creds

Thanks for all the help,  it was as you hinted a gcloud issue. Just doing
```  script:
    - npm ci
    - echo $GOOGLE_CREDENTIALS &gt; /tmp/creds.json
    - gcloud auth activate-service-account --key-file=/tmp/creds.json
    - pulumi stack select $PULUMI_STACK
    - pulumi up --yes```
Got it to work :slightly_smiling_face:
Thanks again :+1: