so yes that works great, but its a pain in the but...
# generale
early-intern-90238
11/21/2019, 1:24 AMso yes that works great, but its a pain in the butt to do it that way...
w
white-balloon-205
11/21/2019, 1:28 AM
What would you want to be able to do here? (Or how would you expect refresh to work?)
e
early-intern-90238
11/21/2019, 1:30 AMI am typing up a GitHub issue...what I would like to be able to do is a force an update to resource property by name.
early-intern-90238
11/21/2019, 1:31 AMso if I have a kubeconfig i need updated from a infra-cluster microstack as example, and i need all my other microstacks to update their stack with the new one from that one, I can run a command to easily do that...
early-intern-90238
11/21/2019, 1:33 AMthe issue is that when the nodes get replaced, the deployments go away...so when you run an update it has incorrect state...and if you try to refresh to correct it, it doesn't have the ability to connect to the new node
early-intern-90238
11/21/2019, 1:35 AMits not a super common scenario...but if you modify something on your cluster like say update the release channel and you use microstack you will be in this situation...
early-intern-90238
11/21/2019, 1:44 AM