operator-framework/operator-sdk

Helm-based operator does not reconcile operand with base image v1.34.0

Closed this issue · 3 comments

bitscuit commented

Bug Report

What did you do?

Updated the operator-sdk base image for my helm-based operator to use v1.34.0. After installing my operator, it did not reconcile its operand. No status is shown in the CR nor are there logs in the operator pod showing that it reconciled the CR.

Link to my operator.

Steps to build and run operator for testing, assuming you cloned the repo:

  1. Ensure that you check out the community-issue branch
  2. export QUAY_REGISTRY=<your personal registry>
  3. export DEV_REGISTRY=$QUAY_REGISTRY
  4. make build-image-dev
  5. Edit the operator image in the CSV to use the image you just built
  6. make build-bundle-image
  7. make run-bundle
  8. Notice that the CR has no status, and the logs of the operator show no indication it reconciled anything

This issue exists in v1.34.1 as well. If I change the base image in the Dockerfile to v1.33.0, this error does not exist.

What did you expect to see?

The operator reconciles its operand

What did you see instead? Under which circumstances?

After creating an operand, the operator does not reconcile it

Environment

Operator type:

/language helm

Kubernetes cluster type:

$ operator-sdk version

$ operator-sdk version
operator-sdk version: "v1.29.0", commit: "78c564319585c0c348d1d7d9bbfeed1098fab006", kubernetes version: "1.26.0", go version: "go1.19.9", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)

$ kubectl version

Possible Solution

Additional context

Tested with v1.33.0 base image, and the issue is not present

bitscuit commented

/kind bug

sigfodr commented

@bitscuit are you monitoring a specific namespace or all namespaces? I am having an issue similar to yours where the v1.34 base image works fine when monitoring all namespaces, but when I specify a namespace, I see the same issue. After applying my CR file, nothing happens, and nothing appears in the log.

This issue also occurs when running the nginx helm operator tutorial at https://sdk.operatorframework.io/docs/building-operators/helm/tutorial/. The last commit that works is 28a6aa093acb0580066bd8a3e686bd5238a0b9f9, and it fails in the next commit at 1fd7f4dafc954ecc79326d042b42e7d420699f44.

  • 👍1
acornett21 commented
  • Relates: #6692
    Closing as duplicate.