-
Notifications
You must be signed in to change notification settings - Fork 67
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
Is GCP config connector actively used or should be cleaned up (Requests 620m CPU) #2186
Comments
Using this query, I conclude that we are using config connector still. The question then becomes if we should, or if we should migrate to using terraform.
|
We should definitely move off to using terraform for everything. I don’t think we use it on any new clusters. |
damianavila
moved this to Needs Shaping / Refinement
in DEPRECATED Engineering and Product Backlog
Feb 15, 2023
Closing as dupe of #1046 |
github-project-automation
bot
moved this from Needs Shaping / Refinement
to Complete
in DEPRECATED Engineering and Product Backlog
Jun 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looking at GCP node pools, i see two core node pool pods in the GCP GKE cluster in the
two-eye-two-see
project, while only one would have been needed unless we requested 620m CPU from the config connector. So, is cnfig connector stuff used still, or was it something we experimented with and stopped using?Related
The text was updated successfully, but these errors were encountered: