Update Helm chart with correct Istio gateway and DNS config - #1
Merged
Conversation
Set gateway to istio-system/base-gateway-public and add the external-dns.alpha.kubernetes.io/target annotation to the VirtualService, matching the existing apollo-frontend production configuration. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jason-rodri
approved these changes
May 28, 2026
jdieter
approved these changes
May 28, 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.
Summary
istio-system/base-gateway-public(was placeholderdefault-gateway)external-dns.alpha.kubernetes.io/target: ingress.build.resf.organnotation to VirtualServiceBoth values match the existing
apollo-frontend-http-prod-vsVirtualService currently routingerrata.build.resf.orgin theapollo-frontendnamespace.Deployment Plan
Step 1 — Deploy without VirtualService
Deploy the new frontend alongside the old one, with the VirtualService disabled to avoid two VirtualServices competing for the same host:
Step 2 — Verify via port-forward
Open
http://localhost:8086and confirm the site loads and static assets render.Step 3 — Switch traffic
Delete the old VirtualService and enable ours in a single upgrade:
Step 4 — Verify production
Confirm
https://errata.build.resf.orgloads correctly — advisory list, detail pages, filters, RSS feed.Step 5 — Clean up old deployment
After confirming the new frontend is stable:
Rollback
If something goes wrong after Step 3:
The old deployment and service are still running until Step 5, so restoring the backed-up VirtualService returns traffic to the original frontend immediately.
Backup files (saved in
tmp/before deployment):tmp/apollo-frontend-vs-backup.yaml— public VirtualService for errata.build.resf.orgtmp/apollo-frontend-internal-vs-backup.yaml— internal service mesh VirtualServicetmp/apollo-frontend-metrics-vs-backup.yaml— metrics VirtualService