Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate from GardenerCluster CR to KIM #251

Closed
Tracked by #112
Disper opened this issue Jun 3, 2024 · 1 comment
Closed
Tracked by #112

Migrate from GardenerCluster CR to KIM #251

Disper opened this issue Jun 3, 2024 · 1 comment
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Disper
Copy link
Member

Disper commented Jun 3, 2024

Description

  • KEB should no longer create Gardener ClusterCRs
  • KIM should create those CR
  • (optional) Either now, or in a separate ticket change the name to a more meaningful name like Kubeconfig

Reasons

  • KEB should no longer create Gardener Cluster CRs
  • Gardener Cluster CR name is confusing in the current architecture as it is only responsible for managing kubeconfig secrets

Attachments
See #187 for ideas
@Disper Disper added kind/feature Categorizes issue or PR as related to a new feature. area/control-plane Related to all activities around Kyma Control Plane labels Jun 3, 2024
@Disper Disper mentioned this issue Jun 3, 2024
Open
70 tasks
@tobiscr
Copy link
Contributor

tobiscr commented Jul 25, 2024

Duplicate of #282

@tobiscr tobiscr marked this as a duplicate of #282 Jul 25, 2024
@tobiscr tobiscr closed this as completed Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Disper @tobiscr