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

Introduce machineDeployments #990

Closed
wants to merge 1 commit into from

Conversation

enxebre
Copy link
Member

@enxebre enxebre commented Jan 4, 2019

This introduces support for machineDeployments.
Deployments rely on sets to allow among other things to roll pool of workers to new types of instances

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 4, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: enxebre
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: flaper87

If they are not already assigned, you can assign the PR to them by writing /assign @flaper87 in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@enxebre
Copy link
Member Author

enxebre commented Jan 4, 2019

@enxebre enxebre force-pushed the machine-deployments branch from c93cf08 to 7e968d9 Compare January 4, 2019 11:19
Copy link
Member

@ingvagabund ingvagabund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So basically you are saying machine deployment is 1:1 replacement for machine set? This is just the first step? Have you tried to actually run rolling update? E.g. to change AMI?

@@ -43,10 +46,13 @@ func MachineSets(config *types.InstallConfig, pool *types.MachinePool, role, use
return nil, errors.Wrap(err, "failed to create provider")
}
name := fmt.Sprintf("%s-%s-%s", clustername, pool.Name, az)
mset := clusterapi.MachineSet{
maxSurge := intstr.FromInt(1)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe put a short comment here "Rolling machines one by one"

@ingvagabund
Copy link
Member

@enxebre enxebre force-pushed the machine-deployments branch from 7e968d9 to 9e62aa2 Compare January 4, 2019 11:49
@dgoodwin
Copy link
Contributor

dgoodwin commented Jan 4, 2019

Is this planned to go in for 4.0? If so we will adjust Hive to maintain MachineDeployments instead of MachineSets post-install.

// MachineSets returns a list of machinesets for a machinepool.
func MachineSets(config *types.InstallConfig, pool *types.MachinePool, role, userDataSecret string) ([]clusterapi.MachineSet, error) {
// MachineDeployments returns a list of machinedeployments for a machinepool.
func MachineDeployments(config *types.InstallConfig, pool *types.MachinePool, role, userDataSecret string) ([]clusterapi.MachineDeployment, error) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hive shares this function to maintain post-install, the changes here look fine from my POV.

@crawford
Copy link
Contributor

crawford commented Jan 4, 2019

/hold

There must be a commit message for something as invasive as this. Please follow our contribution guide and add a thorough description of what this does and (more importantly) why this needs to change.

@openshift-ci-robot openshift-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jan 4, 2019
@enxebre enxebre force-pushed the machine-deployments branch from 9e62aa2 to a2df547 Compare January 18, 2019 08:16
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 18, 2019
@openshift-ci-robot
Copy link
Contributor

@enxebre: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws a2df547 link /test e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@enxebre
Copy link
Member Author

enxebre commented Feb 6, 2019

closing for now, I'll reopen when relevant

@enxebre enxebre closed this Feb 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants