-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add enhancements to easily output manifests for GitOps #488
Comments
Is this a realistic scenario for someone using this enhancement?
|
👋 Hey @jpelletier1, yes I think so assuming this person will use a tool we plan to support here. We are targeting Argo-specific stuff here first, but would certainly entertain other tools to add support for later. |
That's great, thanks Luke! Reason why I ask: We're looking to enable Insights to be more developer-friendly. For example, giving developers an easy way to get metrics, logs, cost, state about their apps from a single location. I could see reckoner being a nice OSS way to make it easy for developers to get their apps deployed, and then leverage Insights as a way to collect/gather all the info they need about their apps. At least, that's the vision :) Having Reckoner used at the beginning stages of that process could be neat. |
While looking into using tools like ArgoCD or Flux, we realized that the current
reckoner template
command could be used to generate a set of manifests that are monitored by a gitops tool. There are several things that might make that process easier:manifests/<RELEASE NAME>
- This would ideally be configurableSome pitfalls/gotchas to watch out for:
Helm template flags that will need to be passed:
The text was updated successfully, but these errors were encountered: