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

Implement mechanism for copying types related to provider specific config from Gardener #254

Open
Tracked by #112
akgalwas opened this issue Jun 5, 2024 · 0 comments
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

@akgalwas
Copy link
Contributor

akgalwas commented Jun 5, 2024

Description

In the current implementation of AWS, GCP, and OpenStack provider specific config is directly using dependencies to Gardener repositories. For Azure the provider specific config uses type that is copied from the Provisioner. We need to have consistent solution.

Idea:

  • we can fetch the types from the Gardener repos to the KIM's source code at build time

Reasons
There is a problem with direct use of the Azure Gardener Extension's dependency. It requires client-go version that conflicts with requirements defined in Infrastructure Provider's go.mod. The only way would be to fix Azure Gardener Extension's go.mod that seems to be not feasible.

@akgalwas akgalwas 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 5, 2024
@akgalwas akgalwas changed the title Implement mechanism for copying the types from Gardener Implement mechanism for copying types related to provider specific config from Gardener Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to 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.
Projects
None yet
Development

No branches or pull requests

1 participant