/kind feature
Describe the solution you'd like
In the current flow we always reconcile again when a state is completed. In some cases this is due to a waiting time we have anyway, in other cases that wouldn't be necessary.
Something that is independent but also makes the above-mentioned point worse: We call GetServer always at the beginning of the loop - independent of whether that is necessary.
We should evaluate how we can reduce the API calls in the most efficient way. Is it by not reconciling again -but just immediately going to the next states when possible? Is it by calling GetServer only when the provisioning really requires it?
Anything else you would like to add:
In some cases we might be able to omit a GetServer call by fetching information via ssh instead of HCloud API. That's something we can keep in mind while developing a solution for this.
/kind feature
Describe the solution you'd like
In the current flow we always reconcile again when a state is completed. In some cases this is due to a waiting time we have anyway, in other cases that wouldn't be necessary.
Something that is independent but also makes the above-mentioned point worse: We call GetServer always at the beginning of the loop - independent of whether that is necessary.
We should evaluate how we can reduce the API calls in the most efficient way. Is it by not reconciling again -but just immediately going to the next states when possible? Is it by calling GetServer only when the provisioning really requires it?
Anything else you would like to add:
In some cases we might be able to omit a GetServer call by fetching information via ssh instead of HCloud API. That's something we can keep in mind while developing a solution for this.