-
Notifications
You must be signed in to change notification settings - Fork 130
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
Support Private IP for Hetzner Cloud #1579
Support Private IP for Hetzner Cloud #1579
Conversation
Signed-off-by: Moath Qasim <moad.qassem@gmail.com>
Signed-off-by: Moath Qasim <moad.qassem@gmail.com>
Signed-off-by: Moath Qasim <moad.qassem@gmail.com>
This should also somewhat solve kubermatic/operating-system-manager#230 |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, moadqassem 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 |
LGTM label has been added. Git tree hash: 9c29e61eb5764703c363beba2ffca565e8ff33a7
|
* support private ip for hetzner cloud Signed-off-by: Moath Qasim <moad.qassem@gmail.com> * document hetzner ips assignment Signed-off-by: Moath Qasim <moad.qassem@gmail.com> * fix linting Signed-off-by: Moath Qasim <moad.qassem@gmail.com> --------- Signed-off-by: Moath Qasim <moad.qassem@gmail.com>
What this PR does / why we need it:
This PR adds support for disabling the allocation and assignment of public IPv4 and IPv6 by default. Two new fields are introduced(
assignPublicIPv4
andassignPublicIPv6
) when set, the values are gonna be set and propagated to the hetzner vms. If those are not set, the default behaviour is assigning public IPs.Which issue(s) this PR fixes:
Fixes #
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: