fix(uptime-kuma): label the Application as platform tier - #81
Merged
Merged
Conversation
Kuma is operator tooling beside the observability stack. The public homelab page renders stack tiles only for platform-tier apps, so the workload label hid it. Signed-off-by: Pragalva Sapkota <sapkotapragalva@gmail.com>
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.
What
One label:
devata.pragalva.me/tier: workloadbecomesplatformon the Uptime Kuma Application. README sentence explaining the choice.Why
The snapshot publisher already emits Kuma with its tier. The portfolio's homelab page builds stack tiles from platform-tier apps only, so Kuma was in the GitOps panel but missing from the stack row. Kuma is operator tooling beside Grafana and Alertmanager, which is what the platform tier means here.
After merge
The next hourly snapshot publish carries the new tier and the homelab page picks it up on its next fetch. No cluster behaviour changes.