-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 CAPD: add env var to allow using remote Docker engines #8177
Conversation
Signed-off-by: Stefan Büringer [email protected]
/assign @fabriziopandini |
/assign @killianmuldoon |
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.
/lgtm
Like you mentioned, would be good to get an overall guide about how to set this up in documentation once the whole thing is ready - looking forward to seeing it in action 🙂
LGTM label has been added. Git tree hash: 57181e7f8b2c1080f586dcdd4afd6bac713bb413
|
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
This PR allows running CAPD with a remote Docker engine by setting the CAPD_DOCKER_HOST env var.
This covers parts of #5634, although not on a per-cluster basis, just for the entire CAPD controller.
The remote engine can be used by setting the env var in either tilt-settings.yaml or as env var before running clusterctl init or in an IDE run configuration for an e2e test:
I'll follow-up with documentation once #8135 is ready
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #