-
Notifications
You must be signed in to change notification settings - Fork 6
Move the provisionStart to the placement for better organization #79
Copy link
Copy link
Open
Labels
cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.help wantedExtra attention is neededExtra attention is neededneeds-priorityIndicates a PR lacks a label and requires one.Indicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.Indicates an issue or PR lacks a label and requires one.
Description
Activity
Metadata
Metadata
Assignees
Labels
cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.help wantedExtra attention is neededExtra attention is neededneeds-priorityIndicates a PR lacks a label and requires one.Indicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.Indicates an issue or PR lacks a label and requires one.
What would you like to be cleaned:
placement and provisionStart are highly coupled today, if we start the provisioning, we have the start time, then we'll have the placement.
So maybe a better way is to merge them together and make it a pointer. Storing them in the cache could lead to data loss like Pod restarted, but it's still fine since we can get them from the nodeClaim anyway.
Why is this needed: