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

Update machine-controller to v1.4.2 and add additional OpenStack field #572

Merged
merged 2 commits into from
Jul 11, 2019

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Jul 11, 2019

What this PR does / why we need it:

This PR updates machine-controller to v1.4.2 and adds an optional OpenStack field nodeVolumeAttachLimit.

Does this PR introduce a user-facing change?:

Update machine-controller to v1.4.2
Add `nodeVolumeAttachLimit` optional field to OpenStack worker spec

/assign @kron4eg

@xmudrii xmudrii requested a review from kron4eg July 11, 2019 08:33
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 11, 2019
@@ -67,6 +67,8 @@ output "kubeone_workers" {
# Otherwise, the rootDisk will be on ephemeral storage and its size will
# be derived from the flavor
rootDiskSizeGB = 50
# Optional: limit how much volumes can be attached to a node
Copy link
Member Author

Choose a reason for hiding this comment

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

I haven't found a comment for this field in machine-controller examples, but I assumed it from the field name. Is this comment correct?

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

@kron4eg kron4eg left a comment

Choose a reason for hiding this comment

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

/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 11, 2019
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 83b64f42e00db6ac77f1229176ef21e29c9abd01

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

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

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 11, 2019
@kron4eg
Copy link
Member

kron4eg commented Jul 11, 2019

/hold

needs to be tested manually on azure

@kubermatic-bot kubermatic-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 11, 2019
@kubermatic-bot kubermatic-bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 11, 2019
@kron4eg
Copy link
Member

kron4eg commented Jul 11, 2019

/hold cancel
/lgtm

@kubermatic-bot kubermatic-bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Jul 11, 2019
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 8f5cd109a3ada8aa932f2684a90bd9338bb92d1a

@kubermatic-bot kubermatic-bot merged commit c9591bf into master Jul 11, 2019
@kubermatic-bot kubermatic-bot deleted the mc-1.4.2 branch July 11, 2019 10:59
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. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants