Changes required for running Gardener in the mini-lab. #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a prerequisite step for developing the migration to the Gardener Operator with out current deployment role. This allows spinning up the Gardener in the mini-lab.
gardener_virtual_api_server_public_portis required in order to access the virtual garden api server in the mini-lab where KinD is mapping port 4443 from the outside to 443gardener_virtual_api_replicasis just to save up some resources in the KinD cluster because I already saw that a kube-apiserver pod was not scheduled due to node limitsReferences #360.