good morning team I am deploying with helm and my...
# all-things-deployment
w
good morning team I am deploying with helm and my own values.yaml datahub inside GCP’s GKE, I want to enable the manage access token, inside the values .yaml I have this configuration and it generates the following error, can you help me?
Copy code
global:        
  datahub:
    metadata_service_authentication:
      enabled: true
      systemClientId: "__datahub_system"
      systemClientSecret:
        secretRef: "datahub-auth-secrets"
        secretKey: "token_service_signing_key"
      tokenService:
        signingKey:
          secretRef: "datahub-auth-secrets"
          secretKey: "token_service_signing_key"
        salt:
          secretRef: "datahub-auth-secrets"
          secretKey: "token_service_salt"
        # Set to false if you'd like to provide your own auth secrets
      provisionSecrets: 
        enabled: true
        autoGenerate: true
        annotations: {}
i have this mistake with this configuration Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: Secret “datahub-auth-secrets” in namespace “default” exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key “app.kubernetes.io/managed-by”: must be set to “Helm”; annotation validation error: missing key “meta.helm.sh/release-name”: must be set to “datahub”; annotation validation error: missing key “meta.helm.sh/release-namespace”: must be set to “default”
r
Hi - this may not be directly related to DataHub so we might not have the best answer. However, seems like some of the resources already exists - could you delete team and install again? this thread might be helpful ; https://stackoverflow.com/questions/62964532/helm-not-creating-the-resources
w
hello team I was validating this possible solution and others, but I get the same error, I have the following file valúes.yaml, with which in the flag that enables the token generates the error and when I disable it within the yaml datahub yaml works without problem, I am setting it within GKE add them secrets (datahub-auth-secrets) within the Cluster and are saved without problem.
Copy code
datahub-frontend:
    enabled: true
    service:
      type: LoadBalancer
      annotations:
        <http://cloud.google.com/neg|cloud.google.com/neg>: '{"ingress": true}'
        <http://networking.gke.io/load-balancer-type|networking.gke.io/load-balancer-type>: "Internal"
    extraVolumes:
      - name: datahub-users
        secret:
          defaultMode: 0444
          secretName:  datahub-users-secret
    extraVolumeMounts:
      - name: datahub-users
        mountPath: /datahub-frontend/conf/user.props
        subPath: user.props
    extraEnvs:
      - name: AUTH_OIDC_ENABLED
        value: "true"
      - name: AUTH_OIDC_CLIENT_ID
        value: #CAMBIAR
      - name: AUTH_OIDC_CLIENT_SECRET #CAMBIAR
        value: 
      - name: AUTH_OIDC_DISCOVERY_URI
        value: 
      - name: AUTH_OIDC_BASE_URL
        value: #CAMBIAR
      - name: AUTH_OIDC_SCOPE
        value:
      - name: AUTH_OIDC_USER_NAME_CLAIM
        value:
      - name: AUTH_OIDC_USER_NAME_CLAIM_REGEX
        value: 
acryl-datahub-actions:
  enabled: true
  resources:
    limits:
      memory: 1024Mi
    requests:
      cpu: 300m
      memory: 256Mi
datahub-gms:
  service:
    type: ClusterIP

global:
  datahub:
    sql:
      datasource:
        host:  #CAMBIAR
        url:  #CAMBIAR
        hostForMysqlClient: #CAMBIAR
        port: "3306"
        driver: "com.mysql.jdbc.Driver"
        username: root
        password:
          secretRef: mysql-secrets
          secretKey: mysql-root-password
    
    metadata_service_authentication:
      enabled: true
      systemClientId: "__datahub_system"
      systemClientSecret:
        secretRef: "datahub-auth-secrets"
        secretKey: "system_client_secret"
      provisionSecrets:
        enabled: true
inside metadata_service_authentication when I set enabled: false it works but when I set enabled: true it generates the following error
Copy code
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: Secret "datahub-auth-secrets" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>": must be set to "Helm"; annotation validation error: missing key "<http://meta.helm.sh/release-name|meta.helm.sh/release-name>": must be set to "datahub"; annotation validation error: missing key "<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>": must be set to "default"