Skip to content

fix: deploy-relay-and-fix-issues#82

Merged
sirily11 merged 2 commits into
mainfrom
k8s
Jun 3, 2026
Merged

fix: deploy-relay-and-fix-issues#82
sirily11 merged 2 commits into
mainfrom
k8s

Conversation

@autopilot-project-manager

Copy link
Copy Markdown
Contributor

Deployed the relay server to a new cluster, updated configuration files, and made SNI adjustments to resolve DNS issues.

Changes

  • Deployed the relay server to a new cluster.
  • Updated configuration files.
  • Made SNI adjustments to resolve DNS issues.
  • Fixed version drift in the health service by updating Go files and the Dockerfile.
  • Updated release builds to include the VERSION variable.
  • Resolved a specific error in a Swift file to prevent overflow in the reconnect attempt counter.
  • No further code changes are needed, but package builds can confirm successful compilation.

sirily11 and others added 2 commits June 3, 2026 18:01
…stname

Rework the relay k8s manifests for the new cross-region microk8s cluster and
move the public endpoint to a Universal-SSL-covered hostname.

- Deployment+HPA -> DaemonSet: one pod per node == one per region, auto-extends
  as regional nodes join; HPA dropped (DaemonSets scale with nodes, not CPU).
- Ingress: ingressClassName `public` (Traefik), drop cert-manager issuer, the
  `tls:` block, and all `nginx.ingress.kubernetes.io/*` annotations. Cloudflare
  terminates TLS (Full mode); Traefik handles `/ws` natively.
- Pin image to ghcr.io/rxtech-lab/rxcode-relay:v1.14.0 (latest git release).
- Move endpoint relay.code.rxlab.app -> relaycode.rxlab.app. The 3-level name
  was not covered by the `*.rxlab.app` Universal SSL wildcard (one label only),
  so the CF edge served no cert and rejected every client TLS handshake. The
  1-level name is covered for free. Updated ingress host, website relays.json,
  and the desktop RelayPresetCatalog fallback.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The /healthz `version` was a hardcoded "0.2.0" literal in health.go, decoupled
from the image's release tag, so it drifted (deployed v1.14.0 still self-reported
0.2.0).

- main.go: add `var version = "dev"`, overridable via -ldflags -X main.version.
- health.go: report `version` instead of the literal.
- Dockerfile: ARG VERSION=dev + -ldflags "-X main.version=${VERSION}".
- relay-deploy.yaml: pass build-args VERSION=${{ github.ref_name }} on release.

Verified: ldflags build reports the stamped tag, plain build reports "dev".
Takes effect on the next release build.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
rxcode Ready Ready Preview, Comment Jun 3, 2026 10:07am

Request Review

@sirily11 sirily11 changed the title deploy-relay-and-fix-issues fix: deploy-relay-and-fix-issues Jun 3, 2026
@autopilot-project-manager autopilot-project-manager Bot added the bug Something isn't working label Jun 3, 2026
@sirily11 sirily11 enabled auto-merge (squash) June 3, 2026 10:13
@sirily11 sirily11 merged commit da4e8c9 into main Jun 3, 2026
14 checks passed
@sirily11 sirily11 deleted the k8s branch June 3, 2026 10:26
@sirily11

sirily11 commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.14.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

bug Something isn't working released

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant