You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that some versions of kubectl prior to 1.16.0 can fail if the kubectl scale command is run for a role that did not have a specific replicas value set.
We should ensure that even if the initial CoherenceCluster does not specify a replicas value that it is deflated in any CoherenceRoles that are created.
The text was updated successfully, but these errors were encountered:
* Issue #368 - ensure that roles always have a replica value
* Issue #368 - amend scale to zero test role to not have a replica count
* Issue #368 - test modification
It seems that some versions of
kubectl
prior to 1.16.0 can fail if thekubectl scale
command is run for a role that did not have a specificreplicas
value set.We should ensure that even if the initial
CoherenceCluster
does not specify areplicas
value that it is deflated in anyCoherenceRole
s that are created.The text was updated successfully, but these errors were encountered: