Open codefromthecrypt opened 11 months ago
Some context here, for upstream kubernetes scheduler plugins, we general use context for three things, IIRC
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
What would you like to be added:
We should consider if context parameters should exist on plugin callbacks before formalizing the SDK.
Notes :
Why is this needed:
End users should comment directly what they want, so we can verify the expectation will work in TinyGo.
Completion requirements:
The completion of this issue depends one the decision:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.