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
[ISSUE-35] Be more resilient against unexpected cluster specs
Fixes#35
When deserializing clusters discovered in the MCC instance, try
each one independently rather than in bulk, and keep the ones
that succeed instead of throwing them all out if just one fails.
Also, this implicitly ignores clusters that do not yet have any
nodes, presumably because they have just been provisioned and
nodes haven't been created yet. This is because those clusters
will not have a `providerStatus` object which contains information
required to generate kubeconfig files, such as the
`apiServerCertificate`.
0 commit comments