Skip to content

GKE install guide: gaps found by a clean-project install (Ingress first-sync delay, chart deps, desktop feed env, release pins, first-admin host, deny backend 502) #492

Closed

Description

@miyaontherelay

Found by layered-infra-ops while following docs/gcp-install on a clean GCP project for the live proof of the GKE edge hardening (#477, #487). None is caused by those PRs. The install succeeded with the workarounds below.

  1. The Ingress took 16 minutes to get an address. Its first sync failed with Translation failed ... no BackendConfig for service port exists for all four Services, although the BackendConfigs were created in the same Helm revision and the Service annotations were correct. It healed by itself on a later sync. The guide's Ingress check should say this can take 15 to 20 minutes and name that event as harmless if it does not repeat.
  2. Building the chart from source needs helm dependency build charts/sessions-pipeline before charts/agent-relay. Without it the read API and workers are not rendered. (Applies when installing from a checkout instead of the released .tgz.)
  3. managed-values.json can crash-loop relay-control. With desktop_feed_bucket_name set, the Terraform output sets the desktop-feed storage env without a signer, and relay-control exits with SELFHOST_DESKTOP_FEED_SIGNER and SELFHOST_DESKTOP_FEED_STORAGE must be set together. Workaround used: relay-control.extraEnv: []. Either the output should only carry the storage env once a signer is configured, or the guide should say what to set.
  4. Release pins. SERVICES_IMAGE, PSQL_IMAGE and the release .tgz name in the guide point at agent-relay-2026.11.16 (chart 0.7.54), not the chart being installed. Expected while the guide pins that release; it needs updating when the pin moves.
  5. first-admin.sh assumes https://api.$DOMAIN. With four flat hostnames (not api.<domain>) it calls the wrong host. It also assumes Secret Manager.
  6. The edge-deny backend returns 502, not 403 or 404. It has no endpoints by design, so a path routed to it gets a 502 from the load balancer when no Cloud Armor policy is attached. Worth one line in the guide so nobody reads the 502 as an outage.

Related: #487 already adds cloudresourcemanager.googleapis.com to the guide's API list and the node service account note for organizations that forbid the default one.

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

Metadata

Metadata

Assignees

No one assigned

    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