Skip to content
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

Separate config and options specific code for node from start #16268

Closed

Conversation

smarterclayton
Copy link
Contributor

First refactoring towards separating out the code that launches
networking from the code that launches the kubelet. Ensures that node
options (the part that converts nodeconfig to kubelet config) is
completely separate from how processes are started.

@deads2k

@openshift-merge-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 10, 2017
@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 10, 2017
First refactoring towards separating out the code that launches
networking from the code that launches the kubelet. Ensures that node
options (the part that converts nodeconfig to kubelet config) is
completely separate from how processes are started.
@smarterclayton
Copy link
Contributor Author

/retest

@smarterclayton
Copy link
Contributor Author

Will just continue in #16269

openshift-merge-robot added a commit that referenced this pull request Sep 16, 2017
Automatic merge from submit-queue (batch tested with PRs 16269, 13282, 16386)

Split networking out from node initialization into its own package

Node and networking are now completely independent initialization paths.

Builds off of #16268, only second commit is new

@deads2k second step towards removing the need for node to be tied together
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants