WS-E convergence: import SDK canonical label constants (eval vs controller-graph weight; gated on #175)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the seictl seinode package and its existing drift test, then inspect the SDK dependency implications described in this issue. Review sei-k8s-controller#175 before deciding whether to retain local constants or move to a lightweight SDK/api package; done means the tradeoff and chosen path are documented and the relevant dependency and drift-test behavior is covered.
Written by the indexing model from the issue text.
Description
Follow-up to the WS-E SDK landing (sei-k8s-controller#421). seictl's seinode package re-declares the sei.io/role=node / sei.io/seinetwork label constants locally (pinned to the controller's values by a drift test). The SDK is now the canonical home for these.
Decision needed (not a mechanical swap):
- Importing
github.com/sei-protocol/sei-k8s-controller/sdk/seifor the constants pulls the full controller module graph (controller-runtime, reconcilers) into seictl — heavy for a CLI. - This is the accepted tradeoff of landing the SDK in the controller repo, and it's exactly what the api/ leaf-module split (sei-k8s-controller#175) would lighten.
Options to evaluate:
- Keep seictl's local constants + drift test (status quo; zero new dep weight) — possibly the right call for a CLI.
- After #175 lands, import a lightweight constants package from the SDK/api leaf module.
Gated on / informed by sei-k8s-controller#175. Tracked from the WS-E xreview ledger.
- Dominant language
- Go
- Stars
- 1
- Forks
- 3
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 14
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.
More from sei-protocol/seictl
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
sei-protocol/seictl#236 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
sei-protocol/seictl#178 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sei-protocol/seictl#176 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
sei-protocol/seictl#174 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
sei-protocol/seictl#171 ·
All issues in sei-protocol/seictl
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100