koordinator-sh/yarn-copilot

[proposal] use source.Channel to handle yarn node requested update event

Open

#49 opened on Nov 15, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (9 forks)auto 404
area/yarn-operatorgood first issuehelp wanted

Repository metrics

Stars
 (13 stars)
PR merge metrics
 (PR metrics pending)

Description

What is your proposal: Now the reconciler only handles k8s.Node update event, yarn requested info may not be updated in time.

Why is this needed: the yarn requested info on node maybe outdated if k8s.Node not update.

Is there a suggested solution, if so, please add it: using an independent controller to handle yarn requested update from yarnNodeSyncer.

Contributor guide

Research direction
Investigate the current reconciler for node updates and design a new controller using source.Channel to handle yarn requested updates from yarnNodeSyncer.
Tech stack
gokubernetes
Domain
backendcloudinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35