Tobias Willi
08/23/2024, 11:55 AMCesar Santos
08/23/2024, 11:56 AMDanton Bertuol
08/23/2024, 12:05 PMChristopher Daniel
08/23/2024, 12:06 PM1.0.0
to 0.2.5
to support normalization.
Without changing proxy If there is a way to achieve it also - I am okay with it.
Please assist.Nimrod Rosen
08/23/2024, 12:16 PMDamir G
08/23/2024, 12:40 PMTobias Willi
08/23/2024, 12:54 PMOla Smaha
08/23/2024, 1:06 PMVlad Ivanyk
08/23/2024, 1:20 PMTobias Willi
08/23/2024, 1:26 PMkapa.ai
08/23/2024, 1:31 PMabctl local uninstall
followed by abctl local install
. This resolved the 504 issue when creating connectors. Here are the steps they followed: 1. Run kubectl get po -n airbyte-abctl
2. Identify any pods with status pending and "check" in the name 3. Describe pod kubectl describe po -n airbyte-abctl [pending-pod-name]
4. Confirm if there are logs showing insufficient resourcing If you're using Airbyte Cloud, you might need to allow inbound traffic from Airbyte IPs as mentioned in the [Airbyte documentation](https://docs.airbyte.com/integrations/sources/mysql#step-4-airbyte-cloud-only-allow-inbound-traffic-from-airbyte-ips). If the issue persists, it would be helpful to provide more details about your setup such as the Airbyte version, source name/version, destination name/version, and any relevant logs. This will help in diagnosing the problem more accurately.Rahul Singh
08/23/2024, 1:32 PMAnanth Kumar
08/23/2024, 3:09 PMThành Đặng Minh
08/23/2024, 3:17 PMEric Park
08/23/2024, 4:14 PMkapa.ai
08/23/2024, 4:14 PMairbyteUrl
in the values.yaml
file without deleting and recreating the namespace. You can do this by using the helm upgrade
command which updates the existing deployment with the new values specified in the values.yaml
file. Here is an example of how you can do this: bash helm upgrade \ --namespace airbyte \ --values ./values.yaml \ --install airbyte-enterprise \ airbyte/airbyte
In this command, replace ./values.yaml
with the path to your values.yaml
file. This command will apply the new configuration to your existing Airbyte deployment in the specified namespace. Please note that you should be careful when changing the airbyteUrl
as it is used in various places in your configuration. For instance, one user reported an issue where removing the global.airbyteUrl
from the values.yaml
configuration and manually changing the value of the INTERNAL_API_HOST
environment variable in the airbyte-airbyte-env
config map to remove the http://
prefix helped fix a sync job failure issue after an upgrade ([source](https://github.com/airbytehq/airbyte/issues/38854)). Sources: - [Customizing your Deployment](https://docs.airbyte.com/enterprise-setup/implementation-guide#customizing-your-deployment) - [Configure your Deployment](https://docs.airbyte.com/enterprise-setup/implementation-guide#step-2-configure-your-deployment) - [Github Issue 38854](https://github.com/airbytehq/airbyte/issues/38854)Eric Park
08/23/2024, 4:16 PMAnanth Kumar
08/23/2024, 5:44 PMAnanth Kumar
08/24/2024, 2:20 AMYoav Ben Ishai
08/24/2024, 6:10 AMJack Tse
08/24/2024, 10:26 AMTúlio Lima
08/24/2024, 2:51 PMIshan Anilbhai Koradiya
08/24/2024, 4:17 PMAditya Gupta
08/24/2024, 8:27 PMSlackbot
08/24/2024, 8:47 PMChristopher Daniel
08/24/2024, 11:51 PMTúlio Lima
08/25/2024, 1:20 AMTúlio Lima
08/25/2024, 1:33 AMTúlio Lima
08/25/2024, 2:52 AMTúlio Lima
08/25/2024, 2:54 AM