stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 1 Releases Wiki Activity
Files
8e7ce55542fea7fabb0e31cb3721357af1a42a8d
git.stella-ops.org/deploy
History
master 5ce40d2eeb feat: Initialize Zastava Webhook service with TLS and Authority authentication 
- Added Program.cs to set up the web application with Serilog for logging, health check endpoints, and a placeholder admission endpoint.
- Configured Kestrel server to use TLS 1.3 and handle client certificates appropriately.
- Created StellaOps.Zastava.Webhook.csproj with necessary dependencies including Serilog and Polly.
- Documented tasks in TASKS.md for the Zastava Webhook project, outlining current work and exit criteria for each task.
2025-10-19 18:36:22 +03:00
..
compose
feat: Initialize Zastava Webhook service with TLS and Authority authentication
2025-10-19 18:36:22 +03:00
helm/stellaops
feat: Initialize Zastava Webhook service with TLS and Authority authentication
2025-10-19 18:36:22 +03:00
releases
up
2025-10-19 10:38:55 +03:00
tools
feat: Initialize Zastava Webhook service with TLS and Authority authentication
2025-10-19 18:36:22 +03:00
README.md
up
2025-10-19 10:38:55 +03:00

README.md

Deployment Profiles

This directory contains deterministic deployment bundles for the core Stella Ops stack. All manifests reference immutable image digests and map 1:1 to the release manifests stored under deploy/releases/.

Structure

  • releases/ – canonical release manifests (edge, stable, airgap) used to source image digests.
  • compose/ – Docker Compose bundles for dev/stage/airgap targets plus .env seed files.
  • helm/stellaops/ – multi-profile Helm chart with values files for dev/stage/airgap.
  • tools/validate-profiles.sh – helper that runs docker compose config and helm lint/template for every profile.

Workflow

  1. Update or add a release manifest under releases/ with the new digests.
  2. Mirror the digests into the Compose and Helm profiles that correspond to that channel.
  3. Run deploy/tools/validate-profiles.sh (requires Docker CLI and Helm) to ensure the bundles lint and template cleanly.
  4. Commit the change alongside any documentation updates (e.g. install guide cross-links).

Maintaining the digest linkage keeps offline/air-gapped installs reproducible and avoids tag drift between environments.