Skip to content

Finish phasing out Kubernetes channels #3327

Closed

Description

For #3200, completed through PRs #3205 and #3214, we simplified the Kubernetes deployment process and eliminated the concept of "channels" which encapsulated different sets of services but were all deployed to the same cluster.

One lingering artifact of the previous setup is that services deployed to the production cluster are still segmented between prod.yaml and test.yaml under ci/channels. prod.yaml is now hardcoded into the deployment workflows and is the only "channel" that matters now, but test.yaml still contains definitions of several test instances that are deployed to the same cluster but currently unmanaged by the deployment process. These test instances are useful when deploying new versions of Metabase or the GTFS RT archiver

Work to be done

  • Merge -test instances into prod.yaml and finish deprecating the concept of channels
  • Reconcile the current state of the cluster against the new declared state
  • Test deploying a change to one of the test instances and verify that the PR workflow is smooth and correct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions