Task

As an engineer working on RHDH, I want to understand as best as possible how the backstage k8s plugins's use of the k8s typescript sdk so that new plugins interfacing with k8s employ community endorsed methodologies.

Background

During Gabe Montero's initial dive into the backstage k8s plugin code, he discovered that while it uses the k8s typescript library, it did NOT use the 'makeApiClient' API, and in fact had implemented its own REST client for interfacing with the k8s REST API.

Then, in the community plugins, he noticed a mixture of 

• plugins typically with a UI element using the k8s pluging
• catalog entity provide plugins using the k8s sdk directly, including makeApiClient

Dependencies and Blockers

No QE or Doc impacts

Acceptance Criteria

Performing due diligence research on what is available in the git histories for the backstage k8s plugin(including code, documentation, and any past blog posts or the like), cross referencing with the k8s typescript SDK to confirm what was and was not available at the times of k8s plugin development, produced a google doc with findings and inferences from what was and was not documented..