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
A little bit before getting concourse/concourse#4643 in, we got a cluster (topgun) created in GKE, having node pools that make more sense than before (high cpu, with autoscaling set).
It turns out that we never changed the cluster that k8s-topgun target in the release pipelines though.
As a result, we're now with the clusters, while in practice, we could have just one.
Thanks!
(not necessarily related, but could be done together w/ concourse/prod#36)
The text was updated successfully, but these errors were encountered:
Hey,
A little bit before getting concourse/concourse#4643 in, we got a cluster (
topgun
) created in GKE, having node pools that make more sense than before (high cpu, with autoscaling set).It turns out that we never changed the cluster that k8s-topgun target in the release pipelines though.
As a result, we're now with the clusters, while in practice, we could have just one.
Thanks!
(not necessarily related, but could be done together w/ concourse/prod#36)
The text was updated successfully, but these errors were encountered: