Add the v0.5 release post - #39
Open
dennis-upbound wants to merge 4 commits into
Open
dennis-upbound wants to merge 4 commits into
dennis-upbound wants to merge 4 commits into
Conversation
Covers the three headline changes: the fleet gateway becoming an Envoy AI Gateway, fleet telemetry under one metric vocabulary, and Civo as a cluster source. Each section leads with the problem rather than the feature, and the telemetry one explains why normalising at collection is the only option open to us when the engine is the user's choice. Left as a draft, so it renders on the preview deployment but stays out of production until the release ships and the telemetry docs publish. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Dennis Ramdass <dennis@upbound.io>
It was a clause in a list of odds and ends, which undersold it: the interesting part isn't that the floor on spec.replicas went away, it's that dropping the floor alone would have left a parked deployment reporting permanently not ready. Zero takes its own path so a parked deployment reads as parked, which is what makes it safe for an autoscaler to do unattended. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Dennis Ramdass <dennis@upbound.io>
Ran the docs' vale ai-tells rules over it, which the v0.4 post passes clean. Eight hits: a three-item title and a three-verb description, two more verb tricolons, an em-dash standing in for a comma, a run of clipped parallel sentences, 'ships' for 'comes with', and a 'given that' doing the work of 'when'. The title drops to two items like v0.4's, with Civo carried by the description and its own section. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Dennis Ramdass <dennis@upbound.io>
The field is out of MetricMapping: nothing read it, and it asked every mapping author to declare something a dashboard query decides for itself. The post's two-field explanation becomes one, and the part worth keeping - that Modelplane leaves combining a deployment's replicas to your backend, because a scrape of one replica is one batch - stands on its own. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Dennis Ramdass <dennis@upbound.io>
This branch was successfully deployed
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
1 participant
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.
Description of your changes
The release post for v0.5, covering the three headline changes: the fleet gateway becoming an Envoy AI Gateway, fleet telemetry under one metric vocabulary, and Civo as a cluster source.
It follows the v0.4 post's shape — problem first in each section, prose rather than bullets, a worked YAML example where the API is the point. It's about a third shorter than v0.4 (1,065 words against 1,537).
The telemetry section carries the most rationale, because that's where the design needs explaining: Modelplane can't normalise metric names by picking an engine, since the engine is the user's choice, so it normalises at collection instead.
fromUnitandacrossReplicaseach get a short paragraph for the same reason — both encode something a dashboard would otherwise guess.Opened as a draft (
draft: true), so it renders on the Vercel preview but stays out of production, the RSS feed and the sitemap. Two things to flip before it goes live:draft: false, anddateset to the actual release date.There's no
coverimage — v0.4 and the other posts have one underpublic/blog/<slug>/cover.png, so this needs artwork before it ships.I ran
node scripts/validate-posts.mjs(8 posts, all good) and a fullnpm run buildlocally; both pass.🤖 Generated with Claude Code