v1.33.0: Quarkus: panic: interface conversion: *v1.Plugin is not plugin.Deprecated: missing method DeprecationWarning

[stellirin]

Bug Report

What did you do?

git checkout v1.33.0
make build
operator-sdk init --plugins quarkus --domain halkyon.io --project-name expose

What did you expect to see?

Next: define a resource with:
$ operator-sdk create api

What did you see instead? Under which circumstances?

panic: interface conversion: *v1.Plugin is not plugin.Deprecated: missing method DeprecationWarning

goroutine 1 [running]:
sigs.k8s.io/kubebuilder/v3/pkg/cli.CLI.printDeprecationWarnings({{0x33beeda, 0xc}, {0xc0000e2160, 0xab}, {0x34502d7, 0x37}, 0xc0006cec60, 0xc0006cec90, {0x3, 0x0}, ...})
	/Users/stellirin/go/pkg/mod/sigs.k8s.io/kubebuilder/[email protected]/pkg/cli/cli.go:446 +0x7a
sigs.k8s.io/kubebuilder/v3/pkg/cli.New({0xc00070f670?, 0x62?, 0xc00070f708?})
	/Users/stellirin/go/pkg/mod/sigs.k8s.io/kubebuilder/[email protected]/pkg/cli/cli.go:116 +0x178
github.com/operator-framework/operator-sdk/internal/cmd/operator-sdk/cli.GetPluginsCLIAndRoot()
	operator-sdk/internal/cmd/operator-sdk/cli/cli.go:161 +0x1a30
github.com/operator-framework/operator-sdk/internal/cmd/operator-sdk/cli.Run()
	operator-sdk/internal/cmd/operator-sdk/cli/cli.go:75 +0x1b
main.main()
	operator-sdk/cmd/operator-sdk/main.go:28 +0x13

Environment

Operator type:

Kubernetes cluster type:

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Possible Solution

Additional context

Checkout and build of v1.32.0 give me functional operator-sdk.

[Sparker0i]

I'm facing the Same issue as well on a new Mac. Downgrading back to v1.32.0 worked for the time being..

[varshaprasad96]

@csviri could you please take a look at this issue as this is related to Java Operator plugin. Thanks!

[csviri]

cc @metacosm

[metacosm]

I haven't looked at the details yet but the problem is most likely that no one has released the java operator plugin before releasing the 1.33 version of the cli. A fix will most likely involve such a release and a new operator-sdk cli release as well.

[jberkhahn]

This will be fixed in the next release. We probably need to add some checks to our pipeline to make sure this sort of thing doesn't happen again.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Sparker0i]

Hi @jberkhahn, is there any update to this?

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[amitmun]

Is there a workaround for this issue until it is fixed?

[kemosabe102]

This is still a problem.

[metacosm]

I would suggest to just bootstrap your Quarkus-based operator by following the bootstraping instructions and then use the iterative development mode with the qosdk api Dev mode command to create an API (CRD + associated classes).

Moving forward, supporting this plugin will not be a priority (unless the community steps up to maintain it) as the Quarkus Dev mode commands are more natural to a Quarkus-based workflow and can be updated much faster and in synch with the Java SDK releases (which isn't the case here).

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[xstefank]

/reopen

[openshift-ci[bot]]

@xstefank: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[metacosm]

/reopen

[openshift-ci[bot]]

@metacosm: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.