Resource Status - Deployment status

[bmesfin24]

• Query the status from Config Sync
• The kpt repo has some design notes that'll help

[vedantthapa]

@seanpoulter-foci
My proposal for this was to use the kubernetes plugin in backstage and then surface kubernetes components as part of an entity. Before I take it on, just wanted to confirm if you guys already explored this route?

[seanpoulter-foci]

It's an interesting idea. It supports customResources but I haven't found where we'd be able to write a status query for the Claims or other resources.

[vedantthapa]

@seanpoulter-foci

Yeah! This is how it'd look like in practice (ignore the permission error for pods) -

Some details regarding the setup -

• It uses a k8s service account and some custom RBAC to authenticate and make requests.
• It prints out the entire Status field of the claim. If required, we can probably write individual resource status to the claim's status so there's visibility into underlying resources.
• It is tagged to a Resource entity so only claims specific to that entity should show up on the page.
• feat: add annotation and label for k8s plugin #400 contains the changes for a claim and it's catalog-info.

Do you think this fits the use-case? / If we can build something custom on the frontend using this to surface the status?

This was really low-effort so if you think it doesn't fit the use-case here, I'm totally cool to discard it.

Big thanks @ssubedir for helping me set this up.
cc: @sleepycat, @tcaky