Skip to content
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.

When using GKE workload identity setting the defaultProject in the datasource configuration has no effect #278

Closed
wilhelmi opened this issue Sep 9, 2020 · 1 comment · Fixed by #332
Labels
duplicate This issue or pull request already exists
Milestone

Comments

@wilhelmi
Copy link

wilhelmi commented Sep 9, 2020

Bug Report

Expected Behavior

The ability to set the default project to something other than project running the GKE cluster.

Actual Behavior

The BigQuery connection is only established within the project hosting the GKE cluster

Steps to Reproduce the Problem

  1. Deploy into a GKE cluster via Workload Identity in project-a
  2. Configure the datasource:
apiVersion: 1

datasources:
- name: audit-logs
  type: doitintl-bigquery-datasource
  access: proxy
  isDefault: true
  jsonData:
       authenticationType: gce
       defaultProject: project-b
       processingLocation: US
  version: 2
  readOnly: false
  1. When exploring the datasource the only project that can be selected in the query window is project-a

Specifications

  • Version: latest
  • Platform: GKE
  • Grafana Version: 7.1.5
@ofir5300 ofir5300 modified the milestone: 2.0.2 Mar 25, 2021
@codeblooded
Copy link

I believe this is actually the same issue as #317. I do not think it is specific to workload identity. I have witnessed the same behavior running on App Engine Flex. There appears to be a problem with persisting the default project when using the system service account.

@ofir5300 ofir5300 added the duplicate This issue or pull request already exists label Apr 26, 2021
@ofir5300 ofir5300 added this to the 2.0.2 milestone May 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants