-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add flavor to run Gardener in the mini-lab #202
Conversation
I am trying to do this in order to develop an automation for migrating to the Gardener Operator.
Started with the provider-local and had to build it locally upfront. But I found the network setup too opinionated for our use-case to just reach the goal of having a running control plane. Therefore, I went for the power dns and backup s3 extension from @robertvolkmann. Seed now reconciles to 100%, but two things have to be done:
|
@@ -12,3 +12,4 @@ requirements.yaml | |||
.extra_vars.yaml | |||
sonic-vs.img | |||
*.bak | |||
.ansible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ansible caches git clones here, which are happening in the Gardener role.
11683db
to
1c12183
Compare
Description
I am trying to do this in order to develop an automation for migrating our Gardener deployment from metal-roles to the Gardener Operator. This PR prepares for it by allowing to deploy the Gardener Control Plane through the existing automation.
I did not take care of any shoot deployments for now. This would be a stretch goal. For the sole purpose of developing the Operator migration, this implementation should be sufficient.
Depends on:
References: