Conversation
5c89425 to
a486681
Compare
8c51972 to
6801f70
Compare
Release plan
|
b439d58 to
99a2ec7
Compare
9a47f86 to
2926d6f
Compare
| ## Prerequisites | ||
|
|
||
| - Your application must be deployed on GKE | ||
| - You must deploy this from an infrastructure repo (e.g., `dataservices-infra`, `webservices-infra`) |
There was a problem hiding this comment.
Implicit pre-requisite: ESO-related CRDs must be installed.
There was a problem hiding this comment.
My assumption is that this is all covered by standard onboarding of GKE applications.
There was a problem hiding this comment.
If you are implementing in a non-shared cluster, CRDs need to be added. E.g. I needed to add ESO CRDs in airflow-gke (for an implementation unrelated to this module).
mikaeld
left a comment
There was a problem hiding this comment.
What use cases do we have for this at the moment besides employee exits? Any GKE event consumers?
See:
https://mozilla-hub.atlassian.net/browse/DENG-8700 in particular makes sense for me to run via https://github.com/mozilla/dataservices-infra/tree/main/airflow-gke, which is a nonstandard GKE deployment but GKE nonetheless. STMO would also make sense as GKE if it was built from scratch as there is a GKE component to that pipeline, but for ease of transition I've elected to keep a serverless component. Really the GKE interface is not GKE-specific but we're trying to be opinionated as a platform on how to use the primitives we provide. |
Description
Tested in V1 via https://github.com/mozilla-services/cloudops-infra/pull/6775/changes and https://github.com/mozilla/sandbox-infra/pull/872/changes for GKE and v2 Cloud Function modes. My plan is to have user-facing docs in Mana point at the module README.
Related Tickets & Documents