Skip to content

[Request]: kargo #6697

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

Open
7 tasks done
BWagenerGenerali opened this issue Apr 8, 2025 · 0 comments · May be fixed by #6735
Open
7 tasks done

[Request]: kargo #6697

BWagenerGenerali opened this issue Apr 8, 2025 · 0 comments · May be fixed by #6735
Labels
package-request requesting new package

Comments

@BWagenerGenerali
Copy link
Contributor

Prerequisites

  • I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

  • Non-GUI tool
  • Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 500 stars and/or 150 forks)
  • English interface (or at least English documentation)
  • Latest stable version
  • Full version (i.e. not a trial version)
  • Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name

kargo

Description

Kargo is a next-generation continuous delivery and application lifecycle orchestration platform for Kubernetes. It builds upon GitOps principles and integrates with existing technologies, like Argo CD, to streamline and automate the progressive rollout of changes across the many stages of an application's lifecycle.

Homepage

https://kargo.io

Download Link(s)

https://github.com/akuity/kargo/releases

Some Indication of Popularity/Repute

  • ~2.2k stars
  • ~190 forks
@BWagenerGenerali BWagenerGenerali added the package-request requesting new package label Apr 8, 2025
@jack-mil jack-mil linked a pull request Apr 17, 2025 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package-request requesting new package
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant