Skip to content

bug: AgentRuntime CRD missing from config/crd/kustomization.yaml #250

@Schimuneck

Description

@Schimuneck

Problem

config/crd/kustomization.yaml only includes the agentcards CRD but not the agentruntimes CRD. The file config/crd/bases/agent.kagenti.dev_agentruntimes.yaml exists (added in PR #212) but was never registered in the kustomization resources list.

This causes the operator to crash on startup with:

no matches for kind "AgentRuntime" in version "agent.kagenti.dev/v1alpha1"
failed to wait for agentruntime caches to sync

Impact

Any make deploy or kustomize-based installation crashes immediately. The operator enters CrashLoopBackOff because the AgentRuntime controller can't sync its cache against a non-existent CRD.

Suggested fix

Add bases/agent.kagenti.dev_agentruntimes.yaml to config/crd/kustomization.yaml:

resources:
- bases/agent.kagenti.dev_agentcards.yaml
- bases/agent.kagenti.dev_agentruntimes.yaml

Reproduction

make deploy IMG=<any-image>
kubectl logs -n kagenti-operator-system deployment/kagenti-operator-controller-manager
# "no matches for kind AgentRuntime" → CrashLoopBackOff

Workaround

Manually apply the CRD before deploying:

kubectl apply --server-side -f config/crd/bases/agent.kagenti.dev_agentruntimes.yaml

Found during

E2E walkthrough of all 4 AgentCard demo scenarios on OpenShift 4.19 (ROSA), operator built from main at commit 06e0419.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions