Repository navigation
feat: add krater staging records, proxied to alastor - #17
Merged
Merged
Conversation
octoDNS planpatchworklabs.org.cloudflare
Summary: Creates=2, Updates=1, Deletes=0, Existing=29, Meta=False Planned against |
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
Krater staging runs on weft behind alastor's edge (patchworklabsorg/infra#32). This adds its two names, proxied A records to alastor (129.213.163.213), the same as
quilt-staging:krater-staging: the portal. Sign-in through Weave staging.krater-staging-storage: its S3 storage (SeaweedFS).The storage name is proxied on purpose. Staging stores small gallery screenshots, and Krater Compute (large checkpoints) is off. Cloudflare caps a request body at 100 MB. The comment says to turn the proxy off, or to use small multipart parts, before Compute needs more. No cache or Rocket Loader rule may apply to that name, because they break S3 signatures.
Order
Merge after alastor has the Krater staging edge routes (lock bump in jaspermayone/infra). Before that, both names return 404 from Traefik.
Test plan