Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release pipelines use cluster-1, rather than topgun gke cluster #195

Closed
cirocosta opened this issue Nov 1, 2019 · 2 comments
Closed

release pipelines use cluster-1, rather than topgun gke cluster #195

cirocosta opened this issue Nov 1, 2019 · 2 comments
Labels

Comments

@cirocosta
Copy link
Member

cirocosta commented Nov 1, 2019

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)

@jomsie
Copy link

jomsie commented Nov 1, 2019

Wow, so the new GKE cluster is not being used by anything? Good snag for sure!

@github-actions
Copy link

This issue has had no activity for a while. It has been labeled stale, and will be closed in one week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants