Block a user
refactor(operator): replace gen-crd yaml pipeline with a harmony Score
johnride
pushed to feat/install-reconcile-operator-score at NationTech/harmony
2026-04-21 20:53:10 +00:00
johnride
pushed to feat/install-reconcile-operator-score at NationTech/harmony
2026-04-21 20:52:41 +00:00
refactor(operator): replace gen-crd yaml pipeline with a harmony Score
InstallTopology feels very unnatural.
refactor(operator): replace gen-crd yaml pipeline with a harmony Score
johnride
pushed to feat/install-reconcile-operator-score at NationTech/harmony
2026-04-21 20:37:51 +00:00
johnride
created branch feat/install-reconcile-operator-score in NationTech/harmony
2026-04-21 20:37:50 +00:00
refactor(iot): extract iot-contracts crate for cross-boundary types
feat: scaffold IoT walking skeleton — podman module, operator, and agent
never write yaml. This must be typed rust. kube-rs provides all we need to declare a fully typed crd. Same goes for operator.yaml file.
feat: scaffold IoT walking skeleton — podman module, operator, and agent
Why is this not part of the full crd? Why add a bit more json into it after the fact? Am I missing something?
refactor(iot): extract iot-contracts crate for cross-boundary types
podman is not iot specific. Podman belongs as a first-class citizen in harmony . Containers / containerruntime is a first class abstraction (I think it belongs in domain) and podman is either modules or infra. Definitely does not belong hidden in an iot crate.