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
runtimecfg: Add node-ip subcommand #57
Conversation
Moved the implementation from openshift/machine-config-operator#1564 |
/hold Need to test a full deployment with the accompanying change in MCO that moves to use it. |
Need to add the retry on failure functionality from openshift/machine-config-operator#1601 to prevent a regression |
/lgtm |
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.
This failed in my local testing:
Apr 16 18:23:31 master-0.ostest.test.metalkube.org podman[1899]: time="2020-04-16T18:23:31Z" level=info msg="Parsed Virtual IP fd2e:6f44:5dd8:c956::5"
Apr 16 18:23:31 master-0.ostest.test.metalkube.org podman[1899]: time="2020-04-16T18:23:31Z" level=fatal msg="error in node-ip set: protocol not supported\n"
I'm trying again with some more logging added to see if I can figure out where the error is actually coming from.
The binary works when copied to my IPv6 env:
|
node-ip is a subcommand that allows the user to see which IP should the node use in cases of multiple interface and multiple address nodes. This is useful to prevent cases where Container Runtime related services bind to an interface that is not reachable in the control plane. It has two subcommands: * show: Takes one or more Virtual IPs of the control plane and it gives you one eligible IP on stdout. * set: Takes one or more Virtual IPs of the control plane and sets systemd service configuration for services like CRI-O or Kubelet that need to bind to the control plane. In the process of making the commit, and to make runtimecfg less of a monolith, I split its subcommands to separate files.
verified to work on both masters and workers. |
/retest |
/hold cancel |
/retest |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bcrochet, celebdor, cybertron 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
node-ip is a subcommand that allows the user to see which IP should the
node use in cases of multiple interface and multiple address nodes. This
is useful to prevent cases where Container Runtime related services bind
to an interface that is not reachable in the control plane.
It has two subcommands:
show: Takes one or more Virtual IPs of the control plane and it gives
you one eligible IP on stdout.
set: Takes one or more Virtual IPs of the control plane and sets
systemd service configuration for services like CRI-O or Kubelet that
need to bind to the control plane.
In the process of making the commit, and to make runtimecfg less of a
monolith, I split its subcommands to separate files.