Tomas Kral

v2 was failing, but we don't have to fail necessarily. Showing only a warning when the user runs odo dev against `default` project on OpenShift is enough.

Hi @rofrano, thanks for raising this. I'll keep this issue open and only rename it. As you discovered we need to mention M1 binaries on openshift docs. /title Missing link...

> When executing `kubectl create -f https://operatorhub.io/install/postgresql.yaml` > get the following error > `error: unable to recognize "https://operatorhub.io/install/postgresql.yaml": no matches for kind "Subscription" in version "operators.coreos.com/v1alpha1"` It loops like you...

/close not valid for v3

> But then #5780 is about doing the opposite. I'm only concerned that work done to accomplish #5780 might get invalidated if we go ahead with this issue. I think...

The same devfile with the same project works correctly with odo v2. The run commands gets executed as it is supposed to. ``` ▶ odov2 push Validation ✓ Validating the...

> > What I am describing below was purposefully done to break stuff. > > I first created an Operator backed service in the namespace `myproject`. > > > >...

The https://odo.dev/docs/development/devfile#how-odo-creates-resources-from-devfile just says that odo create Deployment and Service, without any details. We need to get to more details. We should at least document what labels and annotations are...

> I've passed many time during this week checking the responsability of this issue for these failing tests: > > [redhat-developer/service-binding-operator#1172](https://github.com/redhat-developer/service-binding-operator/issues/1172) > > I'm waiting for the 1.1.1 release to...

@dependabot recreate