Repository navigation
chore(gcp): match the repo to the live event settings - #2988
Merged
Merged
Conversation
On 2026-11-19 these values were set on the live event tenant to keep portal logins and Guacamole sessions available under event load. This change puts the same values in the chart, the GCP capacity profile and the RDP settings. - Portal liveness uses a TCP check. Readiness keeps /health/ with a 5 s timeout. - The portal BackendConfig needs 5 failed health checks in a row, not 2. - Guacamole frees a session with no open connection after 15 minutes. - p300 portal: 68 to 100 replicas and 6 web workers. - p300 guacd: 48 to 72 replicas. - RDP sessions do not use the graphics pipeline, so they use 16-bit color.
On 2026-11-19 at p300 load, OpenFGA checks that took longer than 1.5 s failed closed. The Guacamole authority renewal then answered "denied" and ended live sessions at 19:57 and 20:42 UTC. The OpenFGA pods used about 0.24 CPU, so load was not the cause. These values were set on the live event tenant: - OpenFGA runtime server replicas: 4 (was 2), at 20:03 UTC. - Portal OPENFGA_TIMEOUT_MS: 5000 (was the default 1500), at 21:00 UTC. Add an openfga section to the GCP capacity profile. p300 gets 4 replicas and 5000 ms. Other tiers keep 2 replicas and 1500 ms. The profile emits the replicas as openfga.replicas, which the bootstrap merges into the Helm values without replacing the identity keys. It emits the timeout through runtimeEnv into the platform-runtime ConfigMap. desired_state() lists both. Add OPENFGA_TIMEOUT_MS to the capacity runtime keys and regenerate the published contract.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
These values run on the live event tenant since 2026-11-19. They kept portal logins and Guacamole sessions available under event load. This PR puts the same values in the repo.
http(initial delay 60 s, period 30 s, timeout 5 s, 3 failures)platform/charts/shifter/templates/web-deployment.yaml/health/, timeout 5 s (was 1 s)platform/charts/shifter/templates/web-deployment.yamlunhealthyThreshold5 (was 2)platform/charts/shifter/values.yamlAPI_SESSION_TIMEOUTplatform/charts/shifter/templates/guacamole-client-deployment.yamlshifter/installation/capacity_profiles_gcp.pyshifter/installation/capacity_profiles_gcp.pyshifter/installation/capacity_profiles_gcp.py"disable-gfx": "true"shifter/shifter_platform/mission_control/_guacamole_connection_params.pyshifter/installation/capacity_profiles_gcp.pyOPENFGA_TIMEOUT_MS(live 21:00 UTC)shifter/installation/capacity_profiles_gcp.py,shifter/installation/runtime_inventory_gcp.pyNotes
replicasvalues also change to 68 and 48. The profile invariant requiresreplicasto equal the autoscaling minimum.capacity_profiles_gcp.pydoes not apply to p300 now, and a comment says so.test_chart_contract.pyare regenerated. The render diff contains only the probe, BackendConfig andAPI_SESSION_TIMEOUTchanges.docs/technical/architecture.mdnow states the 15-minute Guacamole session limit.openfgasection. p300 gets 4 replicas and 5000 ms. Other tiers keep 2 replicas and 1500 ms.openfga.replicas. The bootstrap merges it into the Helm values with_merge_capacity_values, which keeps the identity keys fromgcp_native_identity.py. The timeout goes throughruntimeEnvinto theplatform-runtimeConfigMap.OPENFGA_TIMEOUT_MSis now a capacity runtime key, and the published contract is regenerated.Verification
shifter/installation:test_capacity_profiles_gcp.py,test_runtime_inventory.pyandtest_contract.pypass.platform/charts/shifter/tests/test_chart_contract.pyandtest_openfga_rollout.pypass.helm lintpasses.tests/mission_control/test_guacamole_identity.pypasses, with a new test fordisable-gfx.ruff checkandruff format --checkpass on the changed Python files.bigrae-config contract checkpasses.test_gcp_bundle.pypasses, with the new tests for the p300 OpenFGA values and the defaults of the other tiers.