Skip to content

Fix/cherryservers context#9367

Open
YASWANTH28840 wants to merge 4 commits intokubernetes:masterfrom
YASWANTH28840:fix/cherryservers-context
Open

Fix/cherryservers context#9367
YASWANTH28840 wants to merge 4 commits intokubernetes:masterfrom
YASWANTH28840:fix/cherryservers-context

Conversation

@YASWANTH28840
Copy link

Replace placeholder context.TODO() calls with context.Background() in the
CherryServers cloud provider manager.

Changes:

  • getCherryServer calls
  • listCherryServers calls
  • createNode calls
  • request calls
  • listCherryPlans calls

These are synchronous API calls that should use a root context rather than
a placeholder TODO context. This improves code clarity and ensures proper
context lifecycle management.

/kind cleanup

…erClient

Replace placeholder context.TODO() calls with context.Background() in the
CapacityBufferClient methods. These are synchronous API calls that should
use a root context rather than a placeholder TODO context.

This improves code clarity and ensures proper context lifecycle management:
- ListResourceQuotas
- GetPodTemplate
- UpdateCapacityBuffer
- CreatePodTemplate
- UpdatePodTemplate
- GetScaleObject
- GetPodFromCapacityBuffer

Co-authored-by: Yaswanth Majety <63487431+YASWANTH28840@users.noreply.github.com>
Replace placeholder context.TODO() calls with context.Background() in:
- balancer/main.go
- balancer/pkg/client/informers/externalversions/balancer.x-k8s.io/v1alpha1/balancer.go
- balancer/pkg/controller/controller.go
- cluster-autoscaler/capacitybuffer/translators/pod_template_translator.go
- cluster-autoscaler/capacitybuffer/translators/scalable_objects_translator.go

These are synchronous API calls that should use a root context rather
than a placeholder TODO context. This improves code clarity.

Co-authored-by: Yaswanth Majety <63487431+YASWANTH28840@users.noreply.github.com>
Capitalize the first letter of comments in AliCloud SDK files to comply
with Go code style guidelines. Comments should start with an uppercase letter
or begin with the exported identifier they describe.

Files:
- cluster-autoscaler/cloudprovider/alicloud/alibaba-cloud-sdk-go/sdk/auth/roa_signature_composer.go
- cluster-autoscaler/cloudprovider/alicloud/alibaba-cloud-sdk-go/sdk/auth/rpc_signature_composer.go
- cluster-autoscaler/cloudprovider/alicloud/alibaba-cloud-sdk-go/sdk/client.go

Co-authored-by: Yaswanth Majety <63487431+YASWANTH28840@users.noreply.github.com>
Replace placeholder context.TODO() calls with context.Background() in the
CherryServers cloud provider manager. These are synchronous API calls that
should use a root context rather than a placeholder TODO context.

Changes in cherry_manager_rest.go:
- getCherryServer calls
- listCherryServers calls
- createNode calls
- request calls
- listCherryPlans calls

Co-authored-by: Yaswanth Majety <63487431+YASWANTH28840@users.noreply.github.com>
@k8s-ci-robot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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.

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/needs-area area/balancer needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 17, 2026
@k8s-ci-robot
Copy link
Contributor

Hi @YASWANTH28840. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: YASWANTH28840
Once this PR has been reviewed and has the lgtm label, please assign aleksandra-malinowska, kgolab for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added area/provider/alicloud Issues or PRs related to the AliCloud cloud provider implementation size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed do-not-merge/needs-area labels Mar 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/balancer area/cluster-autoscaler area/provider/alicloud Issues or PRs related to the AliCloud cloud provider implementation cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants