Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Deploying ClusterExtensions using spec.config does not work

Open
#2,937 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api, infrastructure

Research direction

Start with the ClusterExtension CRD and the v1.11.0 olmv1_manifest used by the installer, then compare their schemas with the documented spec.config example in the issue. Trace how the v1.11.0 manifest is generated or packaged and verify the resulting API accepts the supplied resource without the strict decoding error.

Written by the indexing model from the issue text.

Description

I am using OLMv1 with version v1.11.0.

I am trying to deploy a ClusterExtension like this:

apiVersion: olm.operatorframework.io/v1
kind: ClusterExtension
metadata:
  name: argocd
spec:
  namespace: argocd-operator
  source:
    sourceType: Catalog
    catalog:
      packageName: argocd-operator
      channels: ["alpha"]
      version: "0.18.0"
  config:
    configType: "Inline"
    inline:
      deploymentConfig:
        env:
          - name: ARGOCD_CLUSTER_CONFIG_NAMESPACES
            value: "cluster-argocd"

However I am seeing an error on deploy. The relevant part of the error:

The request is invalid: patch: Invalid value: "{\"apiVersion\":\"olm.operatorframework.io/v1\",\"kind\":\"ClusterExtension\",
......
\"type:\"Progressing\"}],\"install\":{\"bundle\":{\"name\":\"argocd-operator.v0.18.0\",\"version\":\"0.18.0\"}}}}": strict decoding error: unknown field "spec.config"

Looking into the CRD, it seems config is not a field.
Looking into the olmv1_manifest that the installer uses specifically for v1.11.0, even that CRD does not have the spec.config field defined.

Dominant language
Go
Stars
213
Forks
85
Avg merge
1d 10h
Merged PRs (30d)
38

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from operator-framework/operator-controller

All issues in operator-framework/operator-controller

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.