-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Track Deployed Artifacts #98
Comments
All tools eventually have to send real api object requests to the apiserver, so I’m not sure if that’s too strong of a requirement for the tools to spit out those. For the tools that simply template and then apply, it’s trivial. Helm also has a way to output the “released” resources in YAML form. |
Some more ideas: Add a list of deployed For Helm, populate this via helm get It looks like this is the best way to parse YAML files currently: |
Here's a functioning yaml parsing snippet: |
cc @nkubala this is the issue I was referring to yesterday |
Opening an issue to get some discussion started on how skaffold can keep track of what it's deploying through the various deployers we support (helm, kubectl apply, ksonnet, etc.).
Tracking these artifacts can help with things like #94 and deletion cases.
For kubectl, we know the manifest paths so we could parse those YAMLs and apply labels, or build a label selector?
For helm, we know the release names so we can query them with helm list or something similar.
The text was updated successfully, but these errors were encountered: