Kyma Environment Broker must integrate with Infrastructure Manager

kyma-project / control-plane

A flexible and easy way to manage Kyma Runtimes

Apache License 2.0

17 stars 113 forks source link

Kyma Environment Broker must integrate with Infrastructure Manager #3060

Open akgalwas opened 1 year ago

akgalwas commented 1 year ago

Description

In order to provide support for dynamic kubeconfigs in the Control Plane, KEB must integrate with the Cluster Inventory.

Reasons

In the current architecture, KEB takes kubeconfig from the Provisioner, and creates a secret. The kubeconfig returned by the Provisioner is static, and should be no longer used by other components. Cluster Inventory is a new component that is responsible for dynamic kubeconfig management. KEB must delegate the task of kubeconfig secret creation to the Cluster Inventory by creating cluster CR.

Acceptance criteria

[ ] KEB must create Cluster CR containing the following data:
- shoot name
- secret name
[ ] Cluster CR must contain the same set of labels as defined here
[ ] KEB generates RuntimeID, instead of using the one generated by the Provisioner
[ ] Cluster CR name contains RuntimeID
[ ] The functionality in KEB is enabled by a feature flag

akgalwas commented 1 year ago

The exact structure of the CR will be defined in this issue: https://github.com/kyma-project/cluster-inventory/issues/9 .

kyma-bot commented 10 months ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

After 60d of inactivity, lifecycle/stale is applied
After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot commented 10 months ago

This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

After 60d of inactivity, lifecycle/stale is applied
After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

Reopen this issue or PR with /reopen
Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

kyma-bot commented 10 months ago

@kyma-bot: Closing this issue.

In response to [this](https://github.com/kyma-project/control-plane/issues/3060#issuecomment-1817878103): >This issue or PR has been automatically closed due to the lack of activity. >Thank you for your contributions. > >This bot triages issues and PRs according to the following rules: >- After 60d of inactivity, `lifecycle/stale` is applied >- After 7d of inactivity since `lifecycle/stale` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle stale` > >If you think that I work incorrectly, kindly [raise an issue](https://github.com/kyma-project/test-infra/issues/new/choose) with the problem. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.