What Info is available inside KeptnTask?

[agardnerIT]

What information from a Deployment is available to access inside the KeptnTask and how do I use it?

Imagine I annotate my Deployment with foo: bar and want to notify an external tool to do something with bar "things". For this I need access to the Deployment annotations inside the KeptnTask. Is this possible and if so, how?

[thschue]

At the moment, it’s only the app name, workload name and the corresponding versions. Do you think we should only pass over the workload/app annotations and labels additionally or do you need more things there?

[agardnerIT]

I'm trying to integrate the lifecycle toolkit with external systems. For example, if we had the ability described here I could pass in a list of URLs. Then (assuming this in an API) have the KLT create synthetic tests during a pre-deployment check - for each API endpoint and "name, label or tag" them (depending on what the 3rd party synth tool allows).

From there I can trigger those synthetic checks automatically in a KLT post-deployment task and rollback if the endpoints weren't responding as expected.

---

I would like to query a third party API for "open issues" and prevent a deployment if there's a currently open issue OR post-deployment, call the API after X minutes and trigger a rollback if the 3rd party tool did have an alert.

---

Query a third party security tool and if "issues" or "vulnerabilities" (terms used loosely) are detected, prevent teh deployment.

---

---

All of these boil down to relying on more than just the appname, workload name and version being available in the task. However, it seems that (italic items are already possible):

• Deployment labels
• Deployment annotations
• appname
• workload name
• version
• environment variables
• secrets
• configmaps

Would solve most of these usecases. I'm eager for others to input too in case I've missed something that wouldnt' be covered by adding support for labels and annotations....