config-tool support for multiple -connect-to parameters for get|set|unset|import|diagnostic|activate
For activate:
Supporting multiple -connect-to parameters is useful in the case of a repair when force-pushing and force-activating a topology to some nodes, instead of doing node by node.
For get|set|unset:
Supporting multiple -connect-to parameters allows the caller to pass all the known nodes of the cluster, and config-tool will pick one to fetch the topology. These commands can be run with some nodes down so supporting multiple values allows to pass all known pods in the CLI in a cloud env.
For import:
Same for activate: allows tp import a cluster config to several nodes at once
For diagnostic:
Same as get|set : diag command can be run over a cluster where some nodes are down, so it needs to support a complete set of pods and will detect the ones reachable
All these use cases are not only for cloud but for normal deployments, but they are really valuable on a cloud env.
config-tool
support for multiple-connect-to
parameters for get|set|unset|import|diagnostic|activateFor activate:
Supporting multiple
-connect-to
parameters is useful in the case of a repair when force-pushing and force-activating a topology to some nodes, instead of doing node by node.For get|set|unset:
Supporting multiple
-connect-to
parameters allows the caller to pass all the known nodes of the cluster, and config-tool will pick one to fetch the topology. These commands can be run with some nodes down so supporting multiple values allows to pass all known pods in the CLI in a cloud env.For import:
Same for activate: allows tp import a cluster config to several nodes at once
For diagnostic:
Same as get|set : diag command can be run over a cluster where some nodes are down, so it needs to support a complete set of pods and will detect the ones reachable
All these use cases are not only for cloud but for normal deployments, but they are really valuable on a cloud env.
config-tool.sh diagnostic -connect-to localhost -output-format json
Enables an easier processing of diagnotic output.
For Kube Operator, these fields are relevant:
manualInterventionRequired
readyForTopologyChange
Example for a node in diagnostic mode
Example for an activated node
Example for a node in repair mode
Example when restart is required
Examples when config is locked
Example commit failure: