prep 2026.9.11 release + PagerDuty EU service region - #94
Merged
Merged
Conversation
Self-hosted instances in the EU need their PagerDuty integration pointed at the EU OAuth and REST endpoints. The integration already had client id/secret values but hardcoded the US endpoints, so an EU-registered app could not complete OAuth. Adds three optional values to the existing integrations.pagerduty block, carried in the per-integration secret alongside the credentials so all of PagerDuty's config stays in one place and reaches pods through the secretRef that is already wired up. Nothing new is needed in the configmap. All three default to "", which the app's read_pagerduty_url treats as "use the US default" (.presence || default) -- so existing installs are unaffected. Note the app-side support landed in d169b865 (2026-09-10) and is NOT in the 2026.8.13 image this chart pins. These values render correctly but stay inert until the app image bump.
Bumps the opslevel app image to the dcdcb288 build (digest verified against ECR; all five tags on that build resolve to the same manifest, and the digest is what actually runs since the helper renders repo:tag@digest). This build contains d169b865, so the PagerDuty EU region values added in this branch take effect on merge rather than staying inert. opssight is left on f9a8f4b: its newest build has not been tagged selfhosted-production-*, and opssight routinely lags a release anyway -- 2026.5.20 shipped a February build.
jasonopslevel
changed the title
andrewstillv15
approved these changes
Sep 11, 2026
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
2 participants
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.
Two commits: the PagerDuty EU values, and the release bump that makes them take effect.
PagerDuty EU region
Three optional values on the existing
integrations.pagerdutyblock:They ride in the per-integration secret next to the credentials, so they reach pods via the
secretRefthat's already wired up. All three default to"", which the app'sread_pagerduty_url(.presence || default) turns back into the US endpoints — no change for existing installs.Release bump
selfhosted-prod-8de7ca42-1786633441selfhosted-prod-dcdcb288fcdcc48cc6c7fb862b19a2770c0e342csha256:cd44c821…sha256:41956ab4…repo:tag@digest.d169b865(verified via merge-base), so the PagerDuty values above are live on merge.Review notes
f9a8f4b— its newest build has noselfhosted-production-*tag. Tag it and I'll add it. (opssight routinely lags: 2026.5.20 shipped a February build.)2026.9.11assumes we release today — past releases set version to the release date, not the build date. Change it if this lands another day.usAppClientIdis a misleading name for the EU case; renaming is breaking, so left alone.