Skip to content

feat: support scheduling fields in kruise helmHooks and kruise-game#162

Open
ylhyh wants to merge 2 commits intoopenkruise:masterfrom
ylhyh:master
Open

feat: support scheduling fields in kruise helmHooks and kruise-game#162
ylhyh wants to merge 2 commits intoopenkruise:masterfrom
ylhyh:master

Conversation

@ylhyh
Copy link

@ylhyh ylhyh commented Jan 9, 2026

Changes involve:

  • Updating versions/kruise-game/next/values.yaml in charts/kruise-game to include the new fields.
  • Updating versions/kruise-game/next/templates/manager.yaml in charts/kruise-game to consume these values.
  • Updating versions/kruise/next/values.yaml in charts/kruise to include a section for hook scheduling (under helmHooks section).
  • Updating the finalizer job templates in versions/kruise/next/templates/pre_delete_hook_job.yaml to consume these values.

Which issue(s) this PR fixes:
Fixes #161

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • I have bumped the chart version according to versioning
    FYI, just commited to the "next" folder
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.

Changes are automatically published when merged to master. They are not published on branches.

Changes involve:
- Updating `versions/kruise-game/next/values.yaml` in `charts/kruise-game` to include the new fields.
- Updating `versions/kruise-game/next/templates/manager.yaml` in `charts/kruise-game` to consume these values.
- Updating `versions/kruise/next/values.yaml` in `charts/kruise` to include a section for hook scheduling (under `helmHooks` section).
- Updating the finalizer job templates in `versions/kruise/next/templates/pre_delete_hook_job.yaml` to consume these values.
@kruise-bot kruise-bot requested review from furykerry and zmberg January 9, 2026 03:54
@kruise-bot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign furykerry for approval by writing /assign @furykerry in a comment. For more information see:The Kubernetes 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

@kruise-bot
Copy link

Welcome @ylhyh! It looks like this is your first PR to openkruise/charts 🎉

@furykerry
Copy link
Member

can you also change the kruise-rollout chart ?

@ylhyh
Copy link
Author

ylhyh commented Jan 9, 2026

can you also change the kruise-rollout chart ?

Done. I have added nodeAffinity and nodeSelector support while keeping the existing podAntiAffinity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Support custom scheduling (nodeSelector, tolerations, affinity) in kruise-game and kruise helmHooks

3 participants