feat(examples & workflows): Draft PR for adding prometheus-3 example#330
Open
SerbaC6 wants to merge 2 commits into
Open
feat(examples & workflows): Draft PR for adding prometheus-3 example#330SerbaC6 wants to merge 2 commits into
SerbaC6 wants to merge 2 commits into
Conversation
razvand
requested changes
May 9, 2026
razvand
left a comment
razvand
left a comment
Contributor
There was a problem hiding this comment.
Where is the Kraftfile for your example? Add the version number in the directory name.
Use your proper name in the commit message. Use Serban Ciumacencu, not SerbaC6.
Use a single commit. A commit is a unit of contribution. It can't reference a pull request, it can't be something thought of as draft. A commit is NOT a history of your struggles. A commit is an atomic contribution. Think of that when you create a commit. See instructions here and use the model of commits in the commit history.
SerbaC6
force-pushed
the
serbanc/prometheus
branch
from
9e3a7db to
f6c70e6
Compare
Add a Prometheus 3.x example for Unikraft deployment based on Alpine Linux.
The example includes:
- Dockerfile: builds a minimal image using the Prometheus package pulled
directly from the official Alpine Linux repositories
- Kraftfile: defines the Unikraft deployment specification, including the
runtime, erofs filesystem packaging, and startup command flags
- prometheus.yml: provides the base scraping configuration, intervals,
and static target definitions for the Prometheus instance
- README.md: provides deployment instructions and configuration details
The directory is explicitly named prometheus-3 rather than latest to
track the current 3.x package provided by Alpine Linux, future-proofing
the example against breaking changes in subsequent major releases.
Signed-off-by: Serban Ciumacencu <serbaciumacencu@gmail.com>
Introduce two GitHub Actions workflows to continuously test the
prometheus-3 example against Unikraft Cloud environments.
Workflows added:
- example-prometheus-3-staging.yaml: targets the staging environment
- example-prometheus-3-stable.yaml: targets the stable environment
Each workflow is triggered on push and pull request to paths under
prometheus-3/, as well as on a weekday schedule (Mon-Fri at 15:00 UTC).
Both use kraftkit@staging to build and deploy the example via
kraft cloud deploy, start the instance, assert the endpoint is
reachable with curl, and unconditionally tear down the instance and
image on completion.
Signed-off-by: Serban Ciumacencu <serbaciumacencu@gmail.com>
SerbaC6
force-pushed
the
serbanc/prometheus
branch
from
f6c70e6 to
5994f55
Compare
SerbaC6
changed the title
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
3 participants
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.
No description provided.