Skip to content

Files

Latest commit

41b2978 · Dec 18, 2024

History

History

cluster

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Dec 18, 2024
Sep 19, 2024
Feb 1, 2023
Feb 1, 2023
Apr 4, 2022
Aug 12, 2021
Mar 17, 2023
Aug 12, 2021
Sep 18, 2024
Sep 18, 2024
Sep 16, 2019
Nov 19, 2021
Nov 19, 2021

Add a new component to the release

  1. Create the component, such that no other components depend on it. (If it fails, you can debug without worrying about breaking production.)

  2. PR: Add the component to the BUILD file, and send a PR for this. (Example: #822).

  3. Wait until Container Registry has a date-versioned image for the component.

    • e.g. #822 -> tabulator image with versionv20220210-v0.0.121-16-g5bceb0c
  4. PR: Create a configuration <component>.yaml file under cluster/canary, referencing the image version all components are using in production (so the autobumper can catch it).

  5. Bind the service account(s) for the component in the testgrid-canary namespace:

    NAMESPACE=testgrid-canary
    PROJECT=<project>
    COMPONENT=<component name>
    SERVICE_ACCOUNT=<service account to bind to>
    gcloud iam service-accounts add-iam-policy-binding   --project=$PROJECT   --role=roles/iam.workloadIdentityUser   --member=serviceAccount:k8s-testgrid.svc.id.goog[$NAMESPACE/$COMPONENT]   $SERVICE_ACCOUNT
    
  6. PR: Create <component>.yaml under cluster/prod.

  7. Bind the service account(s) for the component in the testgrid namespace:

    NAMESPACE=testgrid
    PROJECT=<project>
    COMPONENT=<component name>
    SERVICE_ACCOUNT=<service account to bind to>
    gcloud iam service-accounts add-iam-policy-binding   --project=$PROJECT   --role=roles/iam.workloadIdentityUser   --member=serviceAccount:k8s-testgrid.svc.id.goog[$NAMESPACE/$COMPONENT]   $SERVICE_ACCOUNT