Repository navigation
Reach bazelflare through its edge-TLS front door - #8693
Merged
Merged
Conversation
danlapid
force-pushed
the
dlapid/bazelflare-edge-tls
branch
from
November 19, 2026 21:40
aa46dc8 to
946d0b5
Compare
bazelflare has a second Spectrum app, remote.workers-runtime-playground .cloudflareworkers.com, which terminates TLS at Cloudflare's edge with ALPN h2 (edge_alpn_protocols) and presents the zone's publicly trusted certificate, so Bazel's default trust store verifies it and the private CA pin goes away. The old hostname keeps serving the pinned private CA for clients that haven't moved yet, and build/bazelflare/ca.pem stays for them: edgeworker's v8.py hands it to siso. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
danlapid
force-pushed
the
dlapid/bazelflare-edge-tls
branch
from
November 19, 2026 21:41
946d0b5 to
47ae01e
Compare
danlapid
marked this pull request as ready for review
November 19, 2026 23:16
There was a problem hiding this comment.
✅ Approved — Small, consistent .bazelrc change with no issues found.
The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.
✅ All checks passed
📋 Code reviewer: ✅ LGTM
The remote executor host and credential helper host key match, and no stale references to the old hostname or the removed TLS certificate flag remain.
Reviewed commit: 47ae01e0
mar-cf
approved these changes
Nov 19, 2026
fhanau
approved these changes
Nov 19, 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
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.
bazelflare now has two front doors on the same Worker:
bazelflare.workers-runtime-playground.cloudflareworkers.com:8980: Spectrumtls: off, the Worker terminates TLS with the private CA that clients pin (build/bazelflare/ca.pem). Unchanged, for clients that haven't moved.remote.workers-runtime-playground.cloudflareworkers.com:8980: Spectrum terminates TLS at the edge with ALPN h2 (edge_alpn_protocols), presenting the zone's publicly trusted certificate.The Worker tells them apart by the connection's first byte (a TLS ClientHello vs the h2c preface). This moves workerd to the second one and drops the pin, so it can merge any time without breaking anyone.
build/bazelflare/ca.pemstays until the old app retires: edgeworker'sv8.pypasses it to siso asRBE_tls_ca_cert.🤖 Generated with Claude Code