ns cloud-creds gcp executable helper to generate a short-lived Niteshift OIDC token, which Google
exchanges for access credentials.
On the Niteshift side, the integration is configured with an entry in the environment’s committed
settings.yaml. Set one workload identity provider using its project number.
Add serviceAccountEmail only if the workload will impersonate a service account:
settings.yaml
https://iam.googleapis.com/ followed
by the provider path. For the example above, run:
iss
and aud. Map google.subject from assertion.sub and restrict the provider to the exact
inspected environment-specific sub with an attribute condition. Trusting only the issuer and
audience does not restrict access to your Niteshift environment.
For an existing pool, create its provider with the following command. Replace the project, pool,
and provider placeholders with the values from settings.yaml, and the claim placeholders with
the exact inspected values:
sub:
roles/iam.workloadIdentityUser on the selected service account and grant
resource permissions to that service account. Avoid pool-wide wildcard grants. Google’s Workload
Identity Federation guide
covers provider setup and both access methods.