-
Notifications
You must be signed in to change notification settings - Fork 4k
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
refactor gce.RegenerateMigInstancesCache() to use Instance.List #6955
Conversation
Hi @damikag. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
for _, err := range errors { | ||
func (c *cachingMigInfoProvider) isMigInCreatingOrDeletingInstanceState(mig Mig) bool { | ||
migRef := mig.GceRef() | ||
state, found := c.cache.GetMigInstancesState(migRef) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't thought about this before, but we need a better name for this. Maybe MigInstancesCount or MigInstancesStateCount? Because now, when I read below state[cloudprovider.InstanceCreating] it reads as state[state] and doesn't parse well in my head. It can be a separate PR though.
func groupInstancesToMigs(instances []GceInstance) map[GceRef][]GceInstance { | ||
migToInstances := map[GceRef][]GceInstance{} | ||
for _, instance := range instances { | ||
if _, found := migToInstances[instance.Igm]; found { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
igm can be an empty GceRef, or a non-existent GceRef how do we want to handle that?
func createIgmRef(gceInstance *gce.Instance, loggingQuota *klogx.Quota) GceRef { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We update cache only for the migs that are known and simply ignore instances from empty GceRefs or non-existent GceRefs. Did you notice any issue with that?
95c4ee6
to
22f6e7e
Compare
201869c
to
8ea6aec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks good, minor comments. Thank you for the extensive unit tests!
} | ||
return updateErr | ||
} | ||
|
||
migs := c.migLister.GetMigs() | ||
errors := make([]error, len(migs)) | ||
workqueue.ParallelizeUntil(context.Background(), c.concurrentGceRefreshes, len(migs), func(piece int) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be skipped if bulkGceMigInstancesListingEnabled=true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. We are doing the same thing in different ways.
…or listing MIG instances
8ea6aec
to
8971a29
Compare
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bskiba, damikag, x13n The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
refactor gce.RegenerateMigInstancesCache() to use Instance.List API
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR refactor the RegenerateMigInstancesCache() to use Instance.List API when fetching MIG instances.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: