@kapa.ai Getting error when selecting Airbyte source connector as Postgres Cannot read properties of undefined (reading 'split')

This error seems to be a known issue with certain versions of the Postgres source connector in Airbyte. It was reported in the Github issues [#46346](https://github.com/airbytehq/airbyte/issues/46346) and [#46681](https://github.com/airbytehq/airbyte/issues/46681). The error occurs when editing or creating a source using the Postgres connector. The issue was reported to be fixed in the Postgres connector version 3.6.22 and above. You can try updating your Postgres connector to the latest version. If you're using Airbyte Open Source, you might need to restart your cluster for the changes to take effect. If the issue persists, you might want to check the version of your Airbyte platform and Postgres. According to the [Airbyte documentation](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting#version-requirements), you should be using Airbyte platform version

v0.58.0

or newer and Postgres v9.3.x or above for non-CDC workflows and Postgres v10 or above for CDC workflows. If you're still facing issues, it would be best to report this on the Airbyte Github issues page or the Airbyte forum for further assistance.

@kapa.ai I am using Airbyte Open Source through helm repo. How can i upgrade my Postgres Connector in K8s? How should I restart the cluster?

A message from kapa.ai

To upgrade your Postgres connector in Airbyte deployed on Kubernetes, you can follow these steps: 1. Access the Airbyte UI and navigate to the Admin page. 2. On the Admin page, select the 'Sources' tab. 3. Find the Postgres source connector in the list and click on the 'Upgrade' button if an upgrade is available. After upgrading the connector, you might need to restart your Airbyte deployment for the changes to take effect. If you're using Helm for deployment, you can use the

helm upgrade

command to upgrade your Airbyte deployment. Here's an example command:

bash helm upgrade --install <RELEASE-NAME> airbyte/airbyte --values <VALUE.YAML> --version <HELM-APP-VERSION>

Replace

<RELEASE-NAME>

,

<VALUE.YAML>

, and

<HELM-APP-VERSION>

with your specific release name, values file, and Helm app version respectively. Please note that the upgrade process might take a few minutes. After the upgrade, Helm will print a message showing how to port-forward Airbyte. This process is described in the [Airbyte documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-k8s-using-helm). If you're still facing issues, it would be best to report this on the Airbyte Github issues page or the Airbyte forum for further assistance.

@kapa.ai Updating the source connectors from Airbyte UI, I was able to setup the source. But I have another concern, since I have deployed the Airbyte through K8s helm charts. When accessing the web app UI of airbyte, it is not asking me for user credentials. It is directly going to workspaces. even when opened through private congnito window.

A message from kapa.ai

The behavior you're experiencing is expected for the open-source version of Airbyte when deployed on Kubernetes. As per the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm), the Airbyte Kubernetes Community Edition does not support basic authentication by default. If you need to secure your Airbyte instance with authentication, you might consider adding a reverse proxy in front of Airbyte that handles authentication. This could be a service like Nginx, Apache, or a cloud provider's API Gateway. For more advanced authentication features, you might want to consider using the Airbyte Cloud version or the Self-Managed Enterprise version, which come with built-in authentication based on the email provided at setup and a generated password, as described in the [Authentication documentation](https://docs.airbyte.com/deploying-airbyte/integrations/authentication). Remember to always secure your data and only allow trusted individuals to access your Airbyte instance.

@kapa.ai I have enabled the auth feature through values.yaml i want to know the how to get the Airbyte console user credentials of my server running on k8s

A message from kapa.ai

Airbyte comes with built-in authentication based on the email provided at setup and a generated password. If you need to view your password and you are running Airbyte through

abctl

, you can run the following command:

bash abctl local credentials

This should output something similar to:

bash {     "password": "password",     "client-id": "client_id",     "client-secret": "client_secret"   }

If you have deployed to your own Kubernetes cluster using Helm, then you can view your credentials by running the following command:

bash kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml

This will return something similar to:

bash apiVersion: v1   data:     instance-admin-client-id: Y2Q1ZTc4ZWEtMzkwNy00ZThmLWE1ZWMtMjIyNGVhZTFiYzcw     instance-admin-client-secret: cmhvQkhCODlMRmh1REdXMWt3REpHZTJMaUd3N3c2MjU=     instance-admin-password: d0V2bklvZEo1QUNHQnpPRWxrOWNSeHdFUGpJMWVzMWg=   kind: Secret   metadata:     creationTimestamp: "2024-07-31T04:22:54Z"     name: airbyte-auth-secrets     namespace: airbyte-abctl     resourceVersion: "600"     uid: f47170eb-f739-4e58-9013-b7afb3ac336a   type: Opaque

These values are base64 encoded, to decode your password run the following command:

bash echo 'cmhvQkhCODlMRmh1REdXMWt3REpHZTJMaUd3N3c2MjU=' | base64 -d

This information is based on the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/integrations/authentication).

@kapa.ai Which info to be used to login using Airbyte Console

A message from kapa.ai

To log in to the Airbyte console, you will need the email and password that were generated during the setup process. If you have enabled authentication and are running Airbyte on Kubernetes, you can retrieve the credentials by running the following command:

bash kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml

This will return something similar to:

bash apiVersion: v1   data:     instance-admin-client-id: Y2Q1ZTc4ZWEtMzkwNy00ZThmLWE1ZWMtMjIyNGVhZTFiYzcw     instance-admin-client-secret: cmhvQkhCODlMRmh1REdXMWt3REpHZTJMaUd3N3c2MjU=     instance-admin-password: d0V2bklvZEo1QUNHQnpPRWxrOWNSeHdFUGpJMWVzMWg=   kind: Secret   metadata:     creationTimestamp: "2024-07-31T04:22:54Z"     name: airbyte-auth-secrets     namespace: airbyte-abctl     resourceVersion: "600"     uid: f47170eb-f739-4e58-9013-b7afb3ac336a   type: Opaque

These values are base64 encoded. To decode your password, run the following command:

bash echo 'd0V2bklvZEo1QUNHQnpPRWxrOWNSeHdFUGpJMWVzMWg=' | base64 -d

Replace

'd0V2bklvZEo1QUNHQnpPRWxrOWNSeHdFUGpJMWVzMWg='

with the

instance-admin-password

value from your secret. The decoded value is the password you can use to log in to the Airbyte console. The email should be the one you provided during the setup process. If you don't remember the email, you can set a new one using the

abctl

tool with the following command:

bash abctl local credentials --email <[[email protected]]>

Replace

<[[email protected]]>

with your email address. This information is based on the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/integrations/authentication).

@kapa.ai is AWS DocumentDB Cluster connector supported in Airbyte?

A message from kapa.ai

New message text here

@kapa.ai I am getting error when setting up any source connector, I am running airbyte on AWS EKS with m5.2xlarge node. An unexpected error occurred. Please report this if the issue persists. (HTTP 500)

A message from kapa.ai

Based on the information provided in the knowledge sources, it appears that you're experiencing a common issue with Airbyte deployments on Kubernetes. This error can occur due to various reasons, but there are a few potential solutions we can explore: 1. Resource Constraints: Even though you're using an m5.2xlarge node, which has substantial resources, there might still be resource allocation issues. As mentioned in a [GitHub issue comment](https://github.com/airbytehq/airbyte/issues/42404), increasing CPU and memory allocated to Docker resolved a similar issue for some users. You might want to check your resource allocation and potentially increase it. 2. Configuration Issues: There could be a configuration problem with your deployment. As noted in another [GitHub issue](https://github.com/airbytehq/airbyte/issues/38180), some users experienced this error after upgrading Airbyte. Make sure your configuration is correct and compatible with your current Airbyte version. 3. Database Connection: The error might be related to database connectivity. As seen in a [forum post](https://discuss.airbyte.io/t/2129), there were instances where the bootloader service couldn't connect to the Airbyte database. Ensure that your database configurations are correct and that the necessary ports are open. 4. Version Compatibility: Ensure that you're using compatible versions of Airbyte and its components. As mentioned in a [GitHub issue](https://github.com/airbytehq/airbyte/issues/38282), updating to the latest version resolved the issue for some users. To troubleshoot this issue: 1. Check your Airbyte logs for more detailed error messages. 2. Verify your resource allocations and increase them if necessary. 3. Double-check your configuration, especially database connection settings. 4. Consider updating to the latest stable version of Airbyte if you're not already using it. If the issue persists after trying these steps, it would be helpful to gather more detailed logs and report the issue on the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte/issues) or the Airbyte community forum for further assistance.