✨ Use live Kubernetes API data in Release app instead of mock

[jasonBirchall]

User Need

As a developer using the Release app
I want to see the actual deployed state from the Kubernetes API
so that I can trust the app reflects real-world environments

---

What’s Needed

• Replace stubbed/mock responses with live KubeAPI data
• Confirm this works for at least one live environment
• Backend logic gracefully handles no/partial data
• Code is committed to ken/kubeclient branch or equivalent
• repo name is correctly mapped - eg Whitehall maps to Whiitehall-admin

---

Acceptance Criteria

• Everything in What’s Needed is delivered.
• Any changes during delivery are reflected in this story.
• Impacted users have been informed appropriately (e.g. change logs, Slack, docs).
• We document the next steps of downstream services using this data as their source of truth. - moved to a sub-task
• We deliver this to the community by demoing the finished Release app at techfortnightly. - will move to the sub-task

---

User Comms Plan (if applicable)

---

Assumptions (optional)

• Cluster has consistent labelling/versioning we can surface in the UI.

---

Risks & Mitigation (optional)

• Risk: API call fails and surfaces bad data.
  Mitigation: Add robust error handling in separate ticket.

---

Notes

Use existing branch: https://github.com/alphagov/release/tree/use-k8s-info
Build atop the existing mocked framework already wired into the UI.
Connects to #1980

[jasonBirchall]

Blocked by #2236, but work can run in parallel.

[kentsanggds]

I reached out to @ChrisBAshton on this and he made the following comment after I showed him an early demo of the page with the EKS information -

---

Maybe What version of my app is configured where?, or even Where is my code? 😄
The “github versions” thing is only ever temporarily useful I think - to show that a deployment is in progress. Once the deployment is on EKS, we don’t really care about what’s on GitHub
My ideal would be some sort of visual like:

Integration: [v266]
Staging: [v255] (GitHub is now set to v266. Progressing EKS...)
Production: [v255]

---

I'll update the layout based on his comments, but it seems like it is useful to show the Github version if there is a discrepancy between whats running on the cluster and what the latest version is on Github.

[jasonBirchall]

[pre-planning] we've decided the best path forward is to manually map difficult labels and names to expected names whitehall: whitehall-admin. We then need to decide what the frontend should look like, and @ChrisBAshton will be consulted.

[kentsanggds]

Seems that licensify isn't running on the apps namespace, so introduce a config file in Release app to point the app at the licensify namespace.

Also it appears that the assumer role doesn't have access to the licensify namespace so update the role bindings and service account