Skip to content

Support for GCP control plane, single/dual cluster#208

Open
nelsonjr wants to merge 1 commit intomainfrom
nelson/nav-gcp-2
Open

Support for GCP control plane, single/dual cluster#208
nelsonjr wants to merge 1 commit intomainfrom
nelson/nav-gcp-2

Conversation

@nelsonjr
Copy link

Update Helm charts to support intra- and dual-cluster on GCP.

@aviator-app
Copy link
Contributor

aviator-app bot commented Jan 22, 2026

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

Comment on lines +133 to +140
5. `helm install` the Control Plane module

cd charts/controlplane
helm upgrade --install unionai-controlplane . \
--namespace union-cp \
--create-namespace \
--values your-values.yaml \
--timeout 15m
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we mention also cert-manager or similar functionality to be available on the cluster for creating certs and also note regarding the racy behavior where the scylladb webhook takes a long time to come up which requires the user the run this command multiple times. May be a note also to check the logs for the scylla webhook.

Longer term we can probably add some delay in bringing up the services until scylla is up if its enabled in the values file or separate scylla installation step so that services can up with that dependency being available.

Also in general a infra/dependency verification tool could be helpful before we run this step to make sure things all dependencies can be met.
Another option is each service checks for its depdencies to be available before coming up. Whichever option we choose may be good to mention the dependency here

Comment on lines +161 to +165
queue-78f8fb75f4-22qp8 1/1 Running 0 33h
run-scheduler-54667b6d96-w5z8p 1/1 Running 0 33h
scylla-dc1-rack1-0 4/4 Running 0 33h
scylla-dc1-rack1-1 4/4 Running 0 33h
scylla-dc1-rack1-2 4/4 Running 0 33h
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also a note that queue service crashloops until scylla rack pods are up

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May be name this as values.gcp.dataplane.selfhosted-intercluster.yaml and keep the old file aswell. We can may be take out the commonalities into a separate file and just override intercluster.yaml separately which only contains the loadbalancer annotation section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants