Can we setup BASIC_AUTH_PROXY_TIMEOUT in kubernete...
# replication-ask-ai
s
Can we setup BASIC_AUTH_PROXY_TIMEOUT in kubernetes deployment of airbyte.?
k
Yes, you can set up
BASIC_AUTH_PROXY_TIMEOUT
in a Kubernetes deployment of Airbyte. This is done by modifying the
values.yaml
file in your Helm Charts. The
BASIC_AUTH_PROXY_TIMEOUT
environment variable defines the proxy timeout time for requests to the Airbyte Server. Here is an example of how you might set it:
Copy code
yaml env:   BASIC_AUTH_PROXY_TIMEOUT: "600"
Please note that the value for
BASIC_AUTH_PROXY_TIMEOUT
should be set in seconds. This is mainly used for dynamic discover when creating a connection (S3, JDBC, etc) that takes a long time. For more information on configuring Airbyte in Kubernetes deployments, you can refer to the [official documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte).
s
@kapa.ai I just ran a helm upgrade on airbyte, Now i am getting this error for airbyte-connector-builder-server pod:
Copy code
Failed to pull image "airbyte/connector-atelier-server:0.50.31": rpc error: code = NotFound desc = failed to pull and unpack image "<http://docker.io/airbyte/connector-atelier-server:0.50.31|docker.io/airbyte/connector-atelier-server:0.50.31>": failed to resolve reference "<http://docker.io/airbyte/connector-atelier-server:0.50.31|docker.io/airbyte/connector-atelier-server:0.50.31>": <http://docker.io/airbyte/connector-atelier-server:0.50.31|docker.io/airbyte/connector-atelier-server:0.50.31>: not found
k
New message text here
s
@kapa.ai I have set these global env vars using helm but still i don’t see airbyte asking for password when try to login:
Copy code
BASIC_AUTH_PROXY_TIMEOUT: 600
BASIC_AUTH_USERNAME: "airbyte"
BASIC_AUTH_PASSWORD: "password"
k
A message from kapa.ai
Based on the information provided in the extracts, it seems like you're trying to set up basic authentication for Airbyte using environment variables. However, these environment variables (
BASIC_AUTH_USERNAME
,
BASIC_AUTH_PASSWORD
,
BASIC_AUTH_PROXY_TIMEOUT
) are specific to Airbyte and not Airflow. In Airbyte, you can modify the
BASIC_AUTH_USERNAME
and
BASIC_AUTH_PASSWORD
in the
.env
file to set up basic authentication. If you want to disable basic authentication, you can set these values to empty strings ("") as mentioned in the [Airbyte documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte). If you're trying to set up authentication for Airflow, you would need to follow the specific instructions for Airflow. Unfortunately, the provided extracts do not contain information on how to set up authentication for Airflow. If you're still having issues with Airbyte authentication, make sure that the
.env
file is correctly set up and that the Airbyte services are restarted after modifying the environment variables. If the problem persists, I would recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io) or [Slack](https://airbytehq.slack.com) for more assistance.
A message from kapa.ai
New message text here