Open pbochynski opened 6 months ago
the static bootstrap token created at the provisioning is extremely short living. (~5min)
As we discussed we should not use static token. I think TokenRequest api would be the best. KEB can call it directly (without provisioner / infrastructure manager in the middle) using own Kubeconfig. That would be quick and easy solution.
POCs: 1) create a technical user in BTP and with BTP CLI create Kyma instance and Kyma binding 2) create a technical user in BTP and create btpOperator instance and then with clientCredential create Kyma instance and Kyma binding
FWIW, in order to address https://github.com/kyma-project/kyma/issues/18092 in our project we have come up with a script that
The human user has to be a cluster admin in order to be able to create the service account though.
Next steps should be discussed with @pbochynski @PK85 @piotrmiskiewicz.
@PK85, @tobiscr, @pbochynski wouldnt' this gardener's feature offer an alternative, shortcut solution? https://github.com/gardener/gardener/blob/master/docs/usage/shoot_access.md#shootsadminkubeconfig-subresource
Another meeting with CIS team needed
We had a meeting again, and we agreed to implement MVP with Service Bindings. The MVP proposal is already to CIS team, awaiting timelines
MVP proposal, awaiting for CIS team: https://wiki.one.int.sap/wiki/display/kyma/Kyma+Environment+Service+Binding+-+MVP+proposal
Description Provide a service binding for Kyma Runtime instance. The binding should contain all the information to connect to the runtime (KUBECONFIG or all the information required to build a KUBECONFIG). The binding request can create TokenRequest and return the token in the binding.
Reasons Users can create Kyma Runtime instances with API or BTP CLI. But the instance cannot be accessed without user being authenticated (OIDC flow). Therefore any automation flow that involves provisioning Kyma and deploying any workload there cannot be easily implemented. The only way to do that is to use custom OIDC provider, but that option is not easy to set up and use.
Attachments Other way to achieve the automation would be https://github.com/kyma-project/kyma/issues/18305