Value Statement

Currently the global hub offers a non Kubernetes API that can be used to list all the managed clusters. This API includes the URL of the API server of each cluster in the following field:

"spec": {
    "managedClusterClientConfigs": [
      {
        "url": "https://cluster-99.example.com:6443"
      }
    ],
    ...
}

But clients may want to use that information to connect to that API server and start to deploy workloads. That is the case for the O-RAN O2 IMS project that we are starting to work on. In addition to the URL we will need also the authentication details required to connect to that URL. It would be ideal to have an additional field containing the "kubeconfig" that should be used to connect:

"spec": {
    "managedClusterClientConfigs": [
      {
        "url": "https://cluster-99.example.com:6443"
        "kubeconfig": "..."
      }
    ],
    ...
}

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.