Astro Private Cloud (APC) 2.0 restructures, renames, and removes several Helm values. This page outlines each change, its user impact, and migration steps.
If you are upgrading from APC 1.x, the changes below represent the incremental differences from 1.x to 2.0. If you are upgrading from 0.37.x directly to 2.0, the 1.0 breaking changes also apply.
In APC 2.0, scattered global.* boolean flags are reorganized into domain-grouped structures with a consistent .enabled pattern. This improves consistency and makes the configuration schema easier to extend.
values.yaml overrides that use the old key paths, causing values to fall back to chart defaults.Run the appropriate migration script before upgrading. The scripts are in the bin/ folder of the Astronomer Helm chart repository on the release-2.0 branch:
bin/migrate-helm-chart-values-1x-to-2x.pybin/migrate-helm-chart-values-037x-to-2x.pyIn addition to the global.* feature flags, the APC API configuration flags under astronomer.houston.config.deployments have also been restructured into domain-grouped nested paths. The migration scripts handle these automatically.
All paths above are relative to astronomer.houston.config.deployments.
values.yaml overrides that use the old key paths under astronomer.houston.config.deployments, causing values to fall back to APC API defaults.Run the appropriate migration script before upgrading. The scripts handle both global.* and astronomer.houston.config.deployments.* key restructuring.
This change was introduced in APC 1.0. If you are upgrading from 1.x, Fluentd was already replaced and no action is needed.
APC 2.0 uses Vector for log collection instead of Fluentd. The migration script renames the top-level fluentd key to vector, preserving resource requests and limits.
If you have custom Fluentd configuration:
This change was introduced in APC 1.0. If you are upgrading from 1.x, Kibana was already removed.
APC 2.0 no longer includes Kibana. The migration script deletes the top-level kibana section.
kibana.<BASEDOMAIN> endpoint is no longer available after upgrade.If you rely on Kibana for log viewing, set up an alternative log viewing solution (such as Grafana with Loki, or direct Elasticsearch queries) before upgrading.
This change was introduced in APC 1.0. If you are upgrading from 1.x, the blackbox exporter was already removed.
APC 2.0 no longer includes the Prometheus blackbox exporter. The migration script deletes the top-level prometheus-blackbox-exporter section.
If you rely on blackbox probing for uptime monitoring of platform services, that monitoring will stop after the upgrade.
Set up alternative uptime monitoring before upgrading if you depend on blackbox exporter probes.
This change was introduced in APC 1.0. If you are upgrading from 1.x, the port was already changed.
The default PgBouncer service port changes from 5432 to 6543 to avoid conflict with the PostgreSQL default port.
External services or scripts connecting to PgBouncer on port 5432 will fail to connect after the upgrade.
Update any external services, connection strings, or scripts that reference the PgBouncer port. If you need to keep port 5432, set global.pgbouncer.servicePort: "5432" in your override file after migration.
This change was introduced in APC 1.0. If you are upgrading from 1.x, this key was already renamed.
The PgBouncer configuration key global.pgbouncer.krb5ConfSecretName is renamed to global.pgbouncer.secretName. The migration script handles this automatically.
The underlying Kubernetes Secret is unchanged — only the Helm values key name changes.
Verify that the value carried over correctly after migration.
This change was introduced in APC 1.0. If you are upgrading from 1.x, JetStream is already enabled.
In 0.37.x, global.nats.jetStream.enabled defaults to false. In 2.x, it defaults to true.
JetStream requires persistent storage. Ensure your cluster has a storage class available for JetStream volumes.
Verify that your cluster supports persistent volumes for NATS JetStream. If you need to keep JetStream disabled, set global.nats.jetStream.enabled: false in your override file after migration.
APC 2.0 removes the following keys. If you are upgrading from 1.x, 1.0 already removed them.
The migration script adds the following keys with default values if they aren’t already present. Review each key and override the default if it doesn’t match your environment.