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.

Sign up for GitHub

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

Jump to bottom

Kube: optional update_policy parameter at cluster creation #293

Merged
merged 2 commits into from
Aug 30, 2022
Merged

Kube: optional update_policy parameter at cluster creation #293

merged 2 commits into from
Aug 30, 2022

Conversation

matprig
Copy link
Contributor

@matprig matprig commented Aug 26, 2022

optional update_policy parameter at cluster creation, APIV6 was updated

no exception thrown at cluster creation when specifying the update_policy parameter

scraly
scraly requested changes Aug 30, 2022
View reviewed changes
Copy link
Collaborator

@scraly scraly left a comment

Choose a reason for hiding this comment

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

Perfect, thanks :-)

Just one typo found in the documentation (a ' after the list of possible value)
image

Thanks

@scraly scraly added the v0.20 label Aug 30, 2022
@scraly scraly changed the title optional update_policy parameter at cluster creation Kube: optional update_policy parameter at cluster creation Aug 30, 2022
scraly
scraly approved these changes Aug 30, 2022
View reviewed changes
Copy link
Collaborator

@scraly scraly left a comment

Choose a reason for hiding this comment

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

Thanks, acceptance tests are working, everything is OK :-)

@scraly scraly merged commit 1910509 into ovh:master Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@scraly scraly scraly approved these changes

Assignees
No one assigned
Labels
v0.20
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@matprig @scraly