NowChess/GitOps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: NCI-12 kargo #364

Merged
Janis merged 1 commits from feat-kargo-tour into main 2026-06-15 22:17:33 +02:00
Conversation 4 Commits 1 Files Changed 2
+35
shosho996 commented 2026-06-10 10:10:10 +02:00
Owner
Copy Link
Copy Source
No description provided.
shosho996 added 1 commit 2026-06-10 10:10:11 +02:00
feat: kargo
Delete PR Branch On Close / delete-branch (pull_request) Successful in 6s
Details
6ffa1c2778
lq64 commented 2026-06-10 10:12:14 +02:00
Owner
Copy Link
Copy Source

What was done right

  • ncs-warehouse.yaml — new tournament Warehouse added, identical config to all other services (same interval, SemVer, strictSemvers, discoveryLimit, correct image
    path ghcr.io/now-chess/now-chess-systems/tournament)
  • ncs-stage.yaml — tournament added as a freight origin in the staging stage with direct: true and requiredSoakTime: 5m0s, consistent with the other services

What's missing

The two production stages (eu-central-1-prod and htwg-1-prod) are not updated. Every other service is listed in all three stages. The PR only adds tournament to
the staging stage.

The production stages pull from staging, and each service needs to be explicitly listed there too. Without that, tournament images will be validated in staging but
never promoted to production.

Also worth checking: htwg-1-prod uses an architecture-specific tag suffix "-x86_v2" for some services — tournament would need the same treatment if it's deployed
there.

Short answer: The warehouse is correct, staging is correct, but the two production stage entries for tournament are missing.

What was done right - ncs-warehouse.yaml — new tournament Warehouse added, identical config to all other services (same interval, SemVer, strictSemvers, discoveryLimit, correct image path ghcr.io/now-chess/now-chess-systems/tournament) - ncs-stage.yaml — tournament added as a freight origin in the staging stage with direct: true and requiredSoakTime: 5m0s, consistent with the other services --- What's missing The two production stages (eu-central-1-prod and htwg-1-prod) are not updated. Every other service is listed in all three stages. The PR only adds tournament to the staging stage. The production stages pull from staging, and each service needs to be explicitly listed there too. Without that, tournament images will be validated in staging but never promoted to production. Also worth checking: htwg-1-prod uses an architecture-specific tag suffix "-x86_v2" for some services — tournament would need the same treatment if it's deployed there. --- Short answer: The warehouse is correct, staging is correct, but the two production stage entries for tournament are missing.
shosho996 commented 2026-06-10 10:17:56 +02:00
Author
Owner
Copy Link
Copy Source

What was done right

  • ncs-warehouse.yaml — new tournament Warehouse added, identical config to all other services (same interval, SemVer, strictSemvers, discoveryLimit, correct image
    path ghcr.io/now-chess/now-chess-systems/tournament)
  • ncs-stage.yaml — tournament added as a freight origin in the staging stage with direct: true and requiredSoakTime: 5m0s, consistent with the other services

What's missing

The two production stages (eu-central-1-prod and htwg-1-prod) are not updated. Every other service is listed in all three stages. The PR only adds tournament to
the staging stage.

The production stages pull from staging, and each service needs to be explicitly listed there too. Without that, tournament images will be validated in staging but
never promoted to production.

Also worth checking: htwg-1-prod uses an architecture-specific tag suffix "-x86_v2" for some services — tournament would need the same treatment if it's deployed
there.

Short answer: The warehouse is correct, staging is correct, but the two production stage entries for tournament are missing.

its already there (claudius said)
Bruda schreib claude antwort dazu

> What was done right > > - ncs-warehouse.yaml — new tournament Warehouse added, identical config to all other services (same interval, SemVer, strictSemvers, discoveryLimit, correct image > path ghcr.io/now-chess/now-chess-systems/tournament) > - ncs-stage.yaml — tournament added as a freight origin in the staging stage with direct: true and requiredSoakTime: 5m0s, consistent with the other services > > --- > What's missing > > The two production stages (eu-central-1-prod and htwg-1-prod) are not updated. Every other service is listed in all three stages. The PR only adds tournament to > the staging stage. > > The production stages pull from staging, and each service needs to be explicitly listed there too. Without that, tournament images will be validated in staging but > never promoted to production. > > Also worth checking: htwg-1-prod uses an architecture-specific tag suffix "-x86_v2" for some services — tournament would need the same treatment if it's deployed > there. > > --- > Short answer: The warehouse is correct, staging is correct, but the two production stage entries for tournament are missing. its already there (claudius said) Bruda schreib claude antwort dazu
lq64 commented 2026-06-10 10:19:13 +02:00
Owner
Copy Link
Copy Source

What was done right

  • ncs-warehouse.yaml — new tournament Warehouse added, identical config to all other services (same interval, SemVer, strictSemvers, discoveryLimit, correct image
    path ghcr.io/now-chess/now-chess-systems/tournament)
  • ncs-stage.yaml — tournament added as a freight origin in the staging stage with direct: true and requiredSoakTime: 5m0s, consistent with the other services

What's missing

The two production stages (eu-central-1-prod and htwg-1-prod) are not updated. Every other service is listed in all three stages. The PR only adds tournament to
the staging stage.

The production stages pull from staging, and each service needs to be explicitly listed there too. Without that, tournament images will be validated in staging but
never promoted to production.

Also worth checking: htwg-1-prod uses an architecture-specific tag suffix "-x86_v2" for some services — tournament would need the same treatment if it's deployed
there.

Short answer: The warehouse is correct, staging is correct, but the two production stage entries for tournament are missing.

its already there (claudius said)
Bruda schreib claude antwort dazu

Bruda schreib claude s antwort dazu

> > What was done right > > > > - ncs-warehouse.yaml — new tournament Warehouse added, identical config to all other services (same interval, SemVer, strictSemvers, discoveryLimit, correct image > > path ghcr.io/now-chess/now-chess-systems/tournament) > > - ncs-stage.yaml — tournament added as a freight origin in the staging stage with direct: true and requiredSoakTime: 5m0s, consistent with the other services > > > > --- > > What's missing > > > > The two production stages (eu-central-1-prod and htwg-1-prod) are not updated. Every other service is listed in all three stages. The PR only adds tournament to > > the staging stage. > > > > The production stages pull from staging, and each service needs to be explicitly listed there too. Without that, tournament images will be validated in staging but > > never promoted to production. > > > > Also worth checking: htwg-1-prod uses an architecture-specific tag suffix "-x86_v2" for some services — tournament would need the same treatment if it's deployed > > there. > > > > --- > > Short answer: The warehouse is correct, staging is correct, but the two production stage entries for tournament are missing. > > its already there (claudius said) > Bruda schreib claude antwort dazu > Bruda schreib claude s antwort dazu
lq64 commented 2026-06-10 10:27:29 +02:00
Owner
Copy Link
Copy Source

In ncs-stage.yaml fehlen die tournament-Einträge in den beiden Production-Stages:

  • eu-central-1-prod
  • htwg-1-prod

Das sind die zwei Blöcke die ergänzt werden müssen.

✻ Worked for 4s

Was machen die beide blöcke, die hinzugefügt wurden?

● Die zwei Blöcke die bereits da sind:

  1. Warehouse-Definition (ncs-warehouse.yaml):
    Sagt Kargo: "Schau alle 5 Minuten nach neuen Images von ghcr.io/now-chess/now-chess-systems/tournament — wenn ein neues SemVer-Tag auftaucht, erstelle ein
    Freight-Objekt."

  2. Staging-Stage-Eintrag (ncs-stage.yaml):
    Sagt Kargo: "Wenn ein neues Tournament-Freight da ist, deploye es direkt nach Staging — aber warte danach 5 Minuten bevor du es als bereit für Production
    markierst."

Was fehlt sind die Produktions-Einträge, die sagen würden: "Wenn das Tournament-Freight in Staging validiert wurde, deploye es auch nach Production."

✻ Baked for 5s

wie würde der fix dazu aussehen?

● Fetch(https://git.janis-eccarius.de/NowChess/GitOps/raw/branch/main/kargo-projects/nowchess/ncs-stage.yaml)
⎿  Received 5.2KB (200 OK)

● In ncs-stage.yaml müssen in beiden Production-Stages jeweils dieser Block ergänzt werden — direkt neben den anderen Warehouse-Einträgen:

In eu-central-1-prod:
- origin:
kind: Warehouse
name: tournament
sources:
direct: false
stages:
- staging

In htwg-1-prod:
- origin:
kind: Warehouse
name: tournament
sources:
direct: false
stages:
- staging

Identisch zu allen anderen Services — direct: false bedeutet "nicht direkt vom Image-Registry, sondern erst nachdem Staging es validiert hat".

In ncs-stage.yaml fehlen die tournament-Einträge in den beiden Production-Stages: - eu-central-1-prod - htwg-1-prod Das sind die zwei Blöcke die ergänzt werden müssen. ✻ Worked for 4s > Was machen die beide blöcke, die hinzugefügt wurden? ● Die zwei Blöcke die bereits da sind: 1. Warehouse-Definition (ncs-warehouse.yaml): Sagt Kargo: "Schau alle 5 Minuten nach neuen Images von ghcr.io/now-chess/now-chess-systems/tournament — wenn ein neues SemVer-Tag auftaucht, erstelle ein Freight-Objekt." 2. Staging-Stage-Eintrag (ncs-stage.yaml): Sagt Kargo: "Wenn ein neues Tournament-Freight da ist, deploye es direkt nach Staging — aber warte danach 5 Minuten bevor du es als bereit für Production markierst." Was fehlt sind die Produktions-Einträge, die sagen würden: "Wenn das Tournament-Freight in Staging validiert wurde, deploye es auch nach Production." ✻ Baked for 5s > wie würde der fix dazu aussehen? ● Fetch(https://git.janis-eccarius.de/NowChess/GitOps/raw/branch/main/kargo-projects/nowchess/ncs-stage.yaml) ⎿  Received 5.2KB (200 OK) ● In ncs-stage.yaml müssen in beiden Production-Stages jeweils dieser Block ergänzt werden — direkt neben den anderen Warehouse-Einträgen: In eu-central-1-prod: - origin: kind: Warehouse name: tournament sources: direct: false stages: - staging In htwg-1-prod: - origin: kind: Warehouse name: tournament sources: direct: false stages: - staging Identisch zu allen anderen Services — direct: false bedeutet "nicht direkt vom Image-Registry, sondern erst nachdem Staging es validiert hat".
Janis merged commit b546313e79 into main 2026-06-15 22:17:33 +02:00
Janis deleted branch feat-kargo-tour 2026-06-15 22:17:33 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Janis (Janis) lq64 (Leon Hermann) shosho996 (Shahd Lala) svc.kargo svc.teamcity
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: NowChess/GitOps#364
Delete Branch "feat-kargo-tour"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?