Skip to content

bug: no supported path to install the substrate CRDs #2583

Description

@jjamroga

kagent-crds gates its substrate-crds subchart on substrate.enabled, but helm-install-provider passes only kmcp.enabled to that release:

helm $(HELM_ACTION) kagent-crds helm/kagent-crds \
    ...
    --set kmcp.enabled=$(KMCP_ENABLED)

KAGENT_HELM_EXTRA_ARGS applies to the kagent release only, so the documented flow cannot install WorkerPool, ActorTemplate, or the other ate.dev CRDs. Installing them takes a manual helm upgrade --install kagent-crds helm/kagent-crds --set substrate.enabled=true, after which 4 ate.dev CRDs appear.

Anything that renders a WorkerPool before that runs fails with no matches for kind "WorkerPool" in version "ate.dev/v1alpha1".

Part of #2574.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions