When you run a newer version of abctl and use the command abctl local install to upgrade or reinstall Airbyte, your existing configuration (including values and secrets) is generally maintained from your previous installation. The documentation does not explicitly state that you must always re-provide your values.yaml or secrets.yaml files for every upgrade or reinstallation. However, if you want to change or customize your configuration, you should provide the updated files using the --values and --secret flags. If you do not provide these files, abctl will use the configuration already present in your local Kubernetes cluster. This means your previous settings are preserved unless you explicitly override them by supplying new files during the install or upgrade process. This behavior is consistent with how Helm-based installations typically work, where existing secrets and values persist unless replaced. If you are migrating from Docker Compose or setting up a new instance, you must provide the values and secrets files. For upgrades or re-installs, providing them is only necessary if you want to change the configuration or if your environment has lost the previous settings for some reason (e.g., a clean environment or deleted secrets) [Install and manage local Airbyte instances](
https://docs.airbyte.com/platform/next/deploying-airbyte/abctl#install-and-manage-local-airbyte-instances). In summary: - For routine upgrades with abctl, you do not need to re-provide values/secrets files unless you want to change the configuration. - Your settings are maintained across local installs unless you explicitly override them.