Skip to content
This repository was archived by the owner on Jun 29, 2022. It is now read-only.

packet/nodes: switch back to baremetal_0 as default node type#642

Merged
iaguis merged 1 commit intomasterfrom
iaguis/revert-packet-type
Jun 19, 2020
Merged

packet/nodes: switch back to baremetal_0 as default node type#642
iaguis merged 1 commit intomasterfrom
iaguis/revert-packet-type

Conversation

@iaguis
Copy link
Contributor

@iaguis iaguis commented Jun 18, 2020

Otherwise upgrading from v0.1.0 will cause all nodes to be recreated.

@iaguis iaguis requested review from johananl and surajssd as code owners June 18, 2020 17:33
Otherwise upgrading from v0.1.0 will cause all nodes to be recreated.
@iaguis iaguis force-pushed the iaguis/revert-packet-type branch from aa856d7 to 9b6a966 Compare June 18, 2020 17:45
Copy link
Member

@surajssd surajssd left a comment

Choose a reason for hiding this comment

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

LGTM.

@iaguis iaguis merged commit 461abbf into master Jun 19, 2020
@iaguis iaguis deleted the iaguis/revert-packet-type branch June 19, 2020 08:31
@invidian
Copy link
Member

I think this PR was not necessary. Instead, users wishing to not migrate their worker pools to new type should define the value explicitly and we should recommend users to re-create the pools.

@iaguis
Copy link
Contributor Author

iaguis commented Jun 22, 2020

I think this PR was not necessary. Instead, users wishing to not migrate their worker pools to new type should define the value explicitly and we should recommend users to re-create the pools.

That's a fair point. We could update this and mention in the release notes the change and recommend to define explicitly the instance type if using the default one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants