Add basic scheduling automation
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 6
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 18
Description
Ref: https://github.com/rancher/fleet/issues/3726
Basic case:
- Configure basic sheduling
- 1 ds cluster with labels pointing to scheduling only updates when time permits, while other 2 ds clusters are inmidiately updated upon webhook push
Considerations:
- Maybe easier to automate when experimental flags are off:
extraEnv:
- name: EXPERIMENTAL_SCHEDULES
value: 'true'
- May need update when UI upgrade is available for this
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced Fleet issue 3726 and the repository's existing end-to-end scenarios. Reproduce the basic case with EXPERIMENTAL_SCHEDULES enabled: one labeled downstream cluster should update only when scheduled, while two others update immediately from a webhook; done means these behaviors are automated and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100