Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate config map additional-root-apps #86

Merged
merged 2 commits into from
Jan 8, 2025
Merged

Conversation

simu
Copy link
Member

@simu simu commented Dec 18, 2024

This PR extends the component to generate the config map additional-root-apps which Steward reads to determine what additional ArgoCD AppProject and Application resources to bootstrap.

The config map must always be present, but the value of field teams can be an empty JSON list.

The list of teams in the config map should never contain the team owning the cluster, since that team keeps the "default" root app named root and the default app project named syn.

Additionally, we don't want to generate a root app and app project for teams which are listed in the parameter but which don't have any component instances assigned.

The full feature requires a version of Steward which includes projectsyn/steward#158

Checklist

  • The PR has a meaningful title. It will be used to auto-generate the
    changelog.
    The PR has a meaningful description that sums up the change. It will be
    linked in the changelog.
  • PR contains a single logical change (to build a better changelog).
  • Update the documentation.
  • Categorize the PR by adding one of the labels:
    bug, enhancement, documentation, change, breaking, dependency
    as they show up in the changelog.
  • Link this PR to related issues or PRs.

@simu simu added enhancement New feature or request bump:minor labels Dec 18, 2024
Copy link

github-actions bot commented Dec 18, 2024

No bump labels present

🛠️ Auto tagging disabled

@simu simu changed the title Feat/additional root apps Generate config map additional-root-apps Dec 18, 2024
@simu simu force-pushed the feat/additional-root-apps branch 3 times, most recently from c361f3d to 077af4f Compare December 20, 2024 16:09
@simu simu requested a review from a team December 24, 2024 09:04
@simu simu marked this pull request as ready for review December 24, 2024 09:04
@simu
Copy link
Member Author

simu commented Dec 24, 2024

See projectsyn/documentation#182 for documentation

@simu simu force-pushed the feat/additional-root-apps branch from 077af4f to 3022570 Compare December 24, 2024 09:06
@simu simu force-pushed the feat/additional-root-apps branch 2 times, most recently from 20491ad to 8d505f2 Compare December 31, 2024 13:33
@simu simu removed the bump:minor label Jan 8, 2025
We use `syn-teams.libsonnet` to get the list of non-owner teams for
which we need to generate additional root apps in Steward.

Please note that this implementation will only create root apps for
teams who are assigned to at least one application that's present in
the cluster.
@simu simu force-pushed the feat/additional-root-apps branch from 8d505f2 to 27647ba Compare January 8, 2025 09:08
The list of teams in the config map should never contain the team owning
the cluster, since that team keeps the "default" root app named `root`
and the default app project named `syn`.

Additionally, we don't want to generate a root app and app project for
teams which are listed in the parameter but which don't have any
component instances assigned.

The test case is setup to have a structure in parameter `syn` which
covers the cases outlined above.

Rendered from template version: main (98d16f)
@simu simu force-pushed the feat/additional-root-apps branch from 27647ba to 45f6c10 Compare January 8, 2025 09:09
@simu simu merged commit e351a7d into master Jan 8, 2025
9 checks passed
@simu simu deleted the feat/additional-root-apps branch January 8, 2025 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants