search

operator-framework / operator-sdk

SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.
https://sdk.operatorframework.io
Apache License 2.0
7.1k stars 1.73k forks source link

Unable to remove an operator #6742

Closed marrip closed 1 month ago

marrip commented 1 month ago

Type of question

General operator-related help

Question

What did you do?

We are running a k3s cluster and installed olm via operator-sdk which worked perfectly. We started adding a couple of operators and wrongly placed one of them into the namespace stackgres and "moved" the operator later to the namespace operators, however, the initial one is still there even after a complete uninstall and new install of olm via the cli.

What did you expect to see?

We expect the operator to be deleted after "moving" to a different namespace and we also expect it to be deleted after reinstalling everything.

What did you see instead? Under which circumstances?

The operator is present for both the stackgres and the operators namespace.

Environment

Operator type:

Kubernetes cluster type:

$ operator-sdk version

operator-sdk version: "v1.34.1", commit: "edaed1e5057db0349568e0b02df3743051b54e68", kubernetes version: "1.28.0", go version: "go1.21.7", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)

$ kubectl version

Major:"1", Minor:"27", GitVersion:"v1.27.10+k3s2", GitCommit:"5b2ac8816958c90888150efb848fc2e2e2c29153", GitTreeState:"clean", BuildDate:"2024-02-06T01:35:14Z", GoVersion:"go1.20.13", Compiler:"gc", Platform:"linux/amd64"

Additional context

acornett21 commented 1 month ago

Hi @marrip It's unclear if you are having an issue with operator-sdk or with olm what is the workflow you are following? Are you running operator-sdk run bundle?

marrip commented 1 month ago

we installed olm via operator-sdk install olm. We got rid of the stackgres operator after removing finalizers on different associated resources. However, we came to the conclusion that it was an issue with olm and not operator-sdk. Sorry about opening it here.