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

How to add new plugin into helm chart #807

Open
3 of 4 tasks
Lyon77 opened this issue Oct 1, 2024 · 1 comment
Open
3 of 4 tasks

How to add new plugin into helm chart #807

Lyon77 opened this issue Oct 1, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Lyon77
Copy link

Lyon77 commented Oct 1, 2024

Area

  • Scheduler
  • Controller
  • Helm Chart
  • Documents

Other components

No response

What happened?

This isn't as much of a bug as is it a clarification on steps required to add a new plugin to the helm chart.

I am trying to create a fork of this project which creates a modification of the preemption toleration pkg code to fit my use case. In order for the newly created plugin to be a part of the image, what do I need to do? Do I just need to create the new plugin the the pkg folder, add the new preemption args to the register.go file, and enable my plugin in the manfiest helm chart values file?

Or do I need to do something in the manifest folder or elsewhere so to make the helm chart aware of the new plugin?

Thanks.

What did you expect to happen?

I'm just looking for way to add a new plugin to the helm chart.

How can we reproduce it (as minimally and precisely as possible)?

No response

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Scheduler Plugins version

@Lyon77 Lyon77 added the kind/bug Categorizes issue or PR as related to a bug. label Oct 1, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants