-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
✨ Add externallyManagedReplicaCount field to MachinePool #5685
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -60,6 +60,13 @@ type MachinePoolSpec struct { | |
// FailureDomains is the list of failure domains this MachinePool should be attached to. | ||
// +optional | ||
FailureDomains []string `json:"failureDomains,omitempty"` | ||
|
||
// Whether the Replicas value is externally managed. This is useful when | ||
// the infrastructure is a managed machine pool, or if the cluster-autoscaler is scaling | ||
// the underlying cloud infrastructure directly outside of cluster-api. Set this to true | ||
// if you wish the replica count to be managed outside of cluster-api. Defaults to false. | ||
// +optional | ||
ExternallyManagedReplicaCount *bool `json:"externallyManagedReplicaCount,omitempty"` | ||
Comment on lines
+64
to
+69
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this field used anywhere? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It will be used to signal to the infrastructure provider that it is responsible for managing the |
||
} | ||
|
||
// ANCHOR_END: MachinePoolSpec | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we document this property and the (expected) behavior of infra providers in the book (https://cluster-api.sigs.k8s.io/developer/architecture/controllers/machine-pool.html#infrastructure-provider)?
I assume this logic in the core MachinePool controller won't change when ExternallyManagedReplicaCount is set?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I will definitely update the book. And also yes, the logic you mention does not change.