-
Notifications
You must be signed in to change notification settings - Fork 525
[GEP-28] make gardenadm-up SCENARIO=connect
deploys a Gardener locally
#12471
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
Conversation
/assign |
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.
Thanks for the next increment towards GEP-28. This makes it look easy to add the Garden to the gardenadm
setup :-) .
/lgtm
/approve
LGTM label has been added. Git tree hash: 34829c1b9d89d5262e6a01de103200bb6b04e032
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ScheererJ The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The virtual cluster is currently not accessible because `make kind-up` does not map the needed ports to the host machine. Eventually, this will resolve automatically once progress on gardener#11958 continues. Nevertheless, a component running inside the machine pods (i.e., inside the automous shoot cluster) should still be able to communicate to the virtual cluster (via cluster-internal communication).
482fa27
to
eec8687
Compare
/lgtm |
LGTM label has been added. Git tree hash: 0cd2f683eea0ca0cbbe6efa4a13cc3e62c17d188
|
How to categorize this PR?
/area ipcei
/kind enhancement
What this PR does / why we need it:
In preparation for
gardenadm connect
, this PR introduces a new scenario formake gardenadm-up
. It deploysgardener-operator
and aGarden
resource (which brings up a Gardener). This Gardener deployment can be later used to connect autonomous shoot clusters to.Which issue(s) this PR fixes:
Part of #2906
Special notes for your reviewer:
/cc @ScheererJ
The virtual cluster is currently not accessible because
make kind-up
does not map the needed ports to the host machine. Eventually, this will resolve automatically once progress on #11958 continues.Nevertheless, a component running inside the machine pods (i.e., inside the automous shoot cluster) should still be able to communicate to the virtual cluster (via cluster-internal communication).
Release note: