Mayowa Ibitola
09/02/2023, 12:47 AMkapa.ai
09/02/2023, 12:48 AM0.39.37-alpha, Airbyte has revisited helm charts structure and separated all components of Airbyte into their own independent charts. This allows developers to test a single component without deploying Airbyte as a whole and upgrading a single component at a time. In most cases, the upgrade from an older monolith chart to a new one should go without any issue. However, if you've configured custom logging or specified custom configuration of DB or Logging, you need to follow specific instructions [source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm). If you're using external DB secrets, you need to provide them in values.yaml under the global.database section in the following format: yaml database: secretName: "myOctaviaSecret" secretValue: "postgresql-password" host: "<http://example.com|example.com>" port: "5432" And then upgrade the chart by running: bash helm upgrade -f path/to/values.yaml %release_name% airbyte/airbyte [source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm) If you're looking to upgrade your Airbyte deployment, you can follow the guide [here](https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-k8s-0270-alpha-and-above). Please note that you need to turn off Airbyte fully and delete the existing Airbyte Kubernetes volumes. Make sure you have already exported your data as this command is going to delete your data in Kubernetes, and you may lose your Airbyte configurations [source](https://docs.airbyte.com/operator-guides/upgrading-airbyte). Lastly, if you're looking to keep a customizable version of the Helm charts in your own deployment repo, you can use helm dependency update and alter the Chart.yaml in Airbyte to point to all local copies of the dependencies [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1677611656145969). I hope this helps! If you have any more questions, feel free to ask.Mayowa Ibitola
09/02/2023, 12:52 AMkapa.ai
09/02/2023, 12:52 AMkapa.ai
09/02/2023, 12:53 AM/api/v1/deployment/export and /api/v1/deployment/import endpoints, please note that these endpoints have been removed and are no longer available [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1671577788883009). I hope this helps! If you have any more questions, feel free to ask.Mayowa Ibitola
09/02/2023, 1:10 AM0.38.3 and the version of helm is 0.48.5 @kapa.ai
what's the best way to migrate, export and import configurations, and connect to a cloudsql dbkapa.ai
09/02/2023, 1:10 AMkapa.ai
09/02/2023, 1:11 AM0.48.5 as per your question). 3. Import Configurations to Helm Deployment: Use the Octavia CLI tool to import your configurations into the new Helm deployment. Again, the exact command will depend on your specific setup and requirements. 4. Connect to CloudSQL DB: To connect Airbyte to a CloudSQL database, you would typically provide the connection details in the values.yaml file under the global.database section. However, the exact details might vary depending on your specific setup and requirements. Please note that this is a high-level overview and the exact steps might vary depending on your specific setup and requirements. Always ensure you have a backup of your data before performing any operations that could potentially modify or delete it. If you encounter any issues during this process, don't hesitate to ask for help. The Airbyte community is always here to assist you.Mayowa Ibitola
09/02/2023, 1:14 AMkapa.ai
09/02/2023, 1:14 AMkapa.ai
09/02/2023, 1:14 AMoctavia init command. This command will create the necessary directories and files for your project. bash octavia init This will output something like: bash 🐙 - Octavia is targetting your Airbyte instance running at <http://localhost:8000> on workspace 36ddb450-66e4-4988-91bf-67279eed5098. 🐙 - Project is not yet initialized. 🔨 - Initializing the project. ✅ - Created the following directories: sources, destinations, connections. ✅ - Created API HTTP headers file in api_http_headers.yaml [source](https://airbyte.com/tutorials/version-control-airbyte-configurations) 3. Import Configurations: After initializing the Octavia project, you can import all existing resources (sources, destinations, connections) on your Airbyte instance to manage them with Octavia CLI using the octavia import all command. bash octavia import all [source](https://docs.airbyte.com/cli-documentation) Please note that you need to replace <http://localhost:8000> with the actual URL of your Airbyte instance running on Kubernetes. Also, the workspace ID should be replaced with the actual workspace ID of your Airbyte instance. Remember to edit any secret values that exist in these configuration files as secrets are not imported. You can edit the configuration files and run octavia apply to continue managing them with Octavia CLI [source](https://docs.airbyte.com/cli-documentation). I hope this helps! If you have any more questions, feel free to ask.Mayowa Ibitola
09/03/2023, 11:56 AMkapa.ai
09/03/2023, 11:56 AMkapa.ai
09/03/2023, 11:56 AMoctavia import all command to retrieve all sources, destinations, and connection configurations from your Airbyte instance. bash octavia import all [source](https://airbyte.com/tutorials/version-control-airbyte-configurations) This command will retrieve all sources, destinations, and connection configurations. You can then commit this to a Git repository. Please note that the exact command may vary depending on your specific setup and requirements. Always ensure you have a backup of your data before performing any operations that could potentially modify or delete it. If you encounter any issues during this process, don't hesitate to ask for help. The Airbyte community is always here to assist you.Mayowa Ibitola
09/03/2023, 11:58 AMkapa.ai
09/03/2023, 11:58 AMkapa.ai
09/03/2023, 11:58 AM