Kops: When we should use --cloudonly flag?
A lot of people when doing kops rolling-update they add --cloudonly flag.
The only description of that flag we can find in manual page is:
--cloudonly [Perform rolling update without confirming progress with k8s]
When we should use it and vice versa? And why it is even called cloudonly?
Aracki
👍1
All 2 comments
cloudonly means that rolling update is not calling kubernetes api and verify kubernetes cluster status between the instance upgrade. Instead it will call only cloudprovider apis, for instance AWS apis to do the upgrade. If you are using things with cloudonly flag, its not draining nodes at all either.
In normal situations that k8s api is up and running you should not use cloudonly flag with rolling update
zetaab
on 3 Sep 2019
👍3
Thanks 馃憤
Aracki
on 5 Sep 2019
Was this page helpful?
0 / 5 - 0 ratings
Related issues
lnformer
路
3Comments
DocValerian
路
4Comments
RXminuS
路
5Comments
georgebuckerfield
路
4Comments
endejoli
路
4Comments
Most helpful comment
cloudonly means that rolling update is not calling kubernetes api and verify kubernetes cluster status between the instance upgrade. Instead it will call only cloudprovider apis, for instance AWS apis to do the upgrade. If you are using things with cloudonly flag, its not draining nodes at all either.
In normal situations that k8s api is up and running you should not use cloudonly flag with rolling update