-
Notifications
You must be signed in to change notification settings - Fork 44
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
feat(k8s): add WaitForPool & WaitForClusterPools helper methods #312
Conversation
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.
Okay, so I have a different approach:
WaitForNodesReadyRequest
with either aClusterID
or aPoolID
and aRegion
WaitForNodesReady
which will:- check the status of the pool and the targetsize == current node count if poolID is not empty
- chech the status of each pool and current node count of cluster == sum of pool target size is clusterID is not empty
- fail if both are empty
@QuentinBrosse @jerome-quere any thoughts?
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.
* `WaitForNodesReadyRequest` with either a `ClusterID` or a `PoolID` and a `Region`
I prefer 2 methods (eg. WaitForCluserNodesReady
and WaitForPoolNodesReady
)
@Sh4d1 @QuentinBrosse : thanks for your comments. I will try to have a look asap. |
just to be sure, |
@debovema Since the implementation of pool ready will be to check if target size == current_node_count and the status == ready, I guess you can
I think both implementation are quite the same in term of performance. Maybe opt for the first one since you can in fact reuse the |
For this one, I am not yet as familiar as you with the Scaleway API but why do we need to provide a PoolID and a Region in the request ? It means that a PoolID is not unique across region right ? But what if we provide directly a |
This method won't be implemented no? |
749fb92
to
9993d74
Compare
9993d74
to
343a194
Compare
343a194
to
7f87ab9
Compare
4932a2d
to
676bae7
Compare
dfd9f6c
to
eee3cd4
Compare
5913497
to
34b1b50
Compare
34b1b50
to
63c7850
Compare
dc79d73
to
c74a509
Compare
fc9f601
to
334b376
Compare
f44c438
to
02a4f06
Compare
02a4f06
to
36a09eb
Compare
LGTM |
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.
LGTM
Requirement of https://github.com/terraform-providers/terraform-provider-scaleway/pull/393