https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> how do i set authentication in gke ...
# replication-ask-ai
a
@kapa.ai how do i set authentication in gke installation?
k
To manage Airbyte authentication on a GKE (Kubernetes) installation, you work with Kubernetes Secrets and your 
values.yaml
used by Helm/`abctl`. ### 1. Find or change the default admin credentials When deployed on Kubernetes (including GKE), Airbyte stores the instance admin credentials in the 
airbyte-auth-secrets
Secret:
Copy code
bash kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml
You’ll see base64‑encoded values like:
Copy code
yaml data:   instance-admin-client-id: ...   instance-admin-client-secret: ...   instance-admin-password: ...
Decode, for example, the password:
Copy code
bash echo 'BASE64_PASSWORD' | base64 -d
[[Auth integration](https://docs.airbyte.com/platform/deploying-airbyte/integrations/authentication)] To set your own password (and optional client id/secret), create or update that Secret:
Copy code
yaml apiVersion: v1 kind: Secret metadata:   name: airbyte-auth-secrets type: Opaque stringData:   instance-admin-password: <your-password>   # instance-admin-client-id: <optional-client-id>   # instance-admin-client-secret: <optional-client-secret>
Apply it:
Copy code
bash kubectl apply -f secret.yaml -n <YOUR_NAMESPACE>
You may need to restart the 
airbyte-server
pod for it to take effect. [[Auth integration](https://docs.airbyte.com/platform/deploying-airbyte/integrations/authentication)] ### 2. Turn authentication off (optional) If you already front Airbyte with your own SSO/proxy and want to disable built‑in auth, add this to your 
values.yaml
before (re)deploying:
Copy code
yaml global:   auth:     enabled: false
Then redeploy with Helm or:
Copy code
bash abctl local install --values ./values.yaml
[[Auth integration](https://docs.airbyte.com/platform/deploying-airbyte/integrations/authentication)] ### 3. Cookie security options (if needed) In the same 
values.yaml
, under 
global.auth
you can adjust cookie behavior:
Copy code
yaml global:   auth:     cookieSecureSetting: "false"      # only if you are NOT using HTTPS     cookieSameSiteSetting: "None"     # if you need cross-site cookies
[[Auth integration](https://docs.airbyte.com/platform/deploying-airbyte/integrations/authentication)] These are the authentication controls documented for Kubernetes/GKE installs; there isn’t additional GKE‑specific auth configuration in the provided sources.
a
@kapa.ai can't i run "abctl local credentials"?
k
A message from kapa.ai
You generally wouldn’t use 
abctl local credentials
for a GKE installation. 
abctl local credentials
is meant for Airbyte that was installed locally via 
abctl
into a kind cluster (the default 
abctl local install
flow). In that case, it prints or updates the local instance’s email/password and client credentials. [[abctl install/manage](https://docs.airbyte.com/platform/deploying-airbyte/abctl#install-and-manage-local-airbyte-instances)] For a Kubernetes deployment you manage yourself (like GKE, using Helm), the docs say to get or control credentials via the 
airbyte-auth-secrets
Secret instead: - View credentials:
Copy code
bash   kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml
- Set your own password (and optional client id/secret) by creating/updating that Secret:
Copy code
yaml   apiVersion: v1   kind: Secret   metadata:     name: airbyte-auth-secrets   type: Opaque   stringData:     instance-admin-password: <your-password>     # instance-admin-client-id: <optional-client-id>     # instance-admin-client-secret: <optional-client-secret>
Then:
Copy code
bash   kubectl apply -f secret.yaml -n <YOUR_NAMESPACE>
You may need to restart the 
airbyte-server
pod. [[Auth integration](https://docs.airbyte.com/platform/deploying-airbyte/integrations/authentication)] The knowledge sources don’t mention using 
abctl local credentials
against a remote GKE cluster, only for local 
abctl
installations, so I can’t confirm that as a supported workflow.
6 Views
Open in Slack
PreviousNext
Powered by