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.

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

KIM should create clusters for all hyperscalers #206

Closed
3 tasks done
Tracked by #112
Disper opened this issue May 10, 2024 · 1 comment
Closed
3 tasks done
Tracked by #112

KIM should create clusters for all hyperscalers #206

Disper opened this issue May 10, 2024 · 1 comment
Assignees

Comments

@Disper
Copy link
Member

Disper commented May 10, 2024

Description

KIM should react on newly created Runtime CRs, and apply Shoot resources on Gardener cluster.

AC:

  • KIM is able to produce working Shoot-Specs for AWS, Azure, GCP, and SAP Converged Cloud
  • Shoot-Spec is tested with Gardener and a Kubernetes cluster was successfully provisioned by Gardener
  • Automated tests are implemented which verify the generate Shoot-Specs with a provided Shoot-Spec template
  • Consider if shoot.Spec.Provider.Workers[] should be migrated or always defaulted by KIM - migrating that will assure that we will not trigger any change on gardener side - AC was from the time we wanted to have more rigid defaults but later we decided that we will rely on KEB.
@akgalwas
Copy link
Contributor

akgalwas commented May 22, 2024

Workplan

  • Implement MVP
  • Implement remaining hyperscalers:
    • GCP
    • SAP Converged Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants