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

Extend Provisioner to support the configuration of seeds within the same region as the shoot has #3441

Closed
3 tasks
tobiscr opened this issue May 29, 2024 · 2 comments
Assignees

Comments

@tobiscr
Copy link
Contributor

tobiscr commented May 29, 2024

Description

As part of EPIC kyma-project/kyma#18182, we are going to offer customers the option request a shoot and seed in the same region.

This requires a modification of the Provisioner logic to be able to

  • Receive the information that seed and shoot should be in the same region (will be an additional boolean flag)
  • Set the proper fields in the Shoot-spec for Gardener (label-selectors for seeds)

AC:

  • Provisioner contract gets extended to support also a boolean-field which indicates whether seed and shoot have to be in the same region
  • If this field is set, the Shoot-spec includes the required configuration (label-selectors for seed) to enforce that the shoot will only be created if a corresponding seed exists
  • Failure cases during the shoot provisioning (e.g. shoot hangs forever in Pending state) are detected and returned as failure to KEB.

Reasons

Enforce seed and shoot in same region to improve latency and address security related concerns.

Attachments

Relates to
kyma-project/kyma#18182

@tobiscr
Copy link
Contributor Author

tobiscr commented May 29, 2024

PR for this feature: #3440

@tobiscr
Copy link
Contributor Author

tobiscr commented Sep 26, 2024

will be handled by KIM only.. closing this as it's duplicate of kyma-project/infrastructure-manager#241

@tobiscr tobiscr closed this as completed Sep 26, 2024
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

2 participants