We have TP feature in 4.15 for OLMv1.
After we use bundledeployment to install the operator, we use command `oc get bd bd-ok1-nonexist` and it will make me think the operator is installed sucessfully and think it works
--
[root@preserve-olm-env2 cluster-olm-operator]# oc get bd bd-ok1-nonexist
NAME              ACTIVE BUNDLE            INSTALL STATE           AGE
bd-ok1-nonexist   bd-ok1-nonexist-2db4bc   InstallationSucceeded   2m15s
--

but actually it does not work. when we use `oc get bd bd-ok1-nonexist -o yaml`, we will see it does not work.
--
[root@preserve-olm-env2 cluster-olm-operator]# oc get bd bd-ok1-nonexist -o yaml
apiVersion: core.rukpak.io/v1alpha1
kind: BundleDeployment
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"core.rukpak.io/v1alpha1","kind":"BundleDeployment","metadata":{"annotations":{},"name":"bd-ok1-nonexist"},"spec":{"provisionerClassName":"core-rukpak-io-plain","template":{"spec":{"provisionerClassName":"core-rukpak-io-registry","source":{"image":{"ref":"quay.io/olmqe/nginx-ok-bundle:v1-0.0.5-multi-noexist"},"type":"image"}}}}}
  creationTimestamp: "2023-11-09T05:28:08Z"
  generation: 2
  name: bd-ok1-nonexist
  resourceVersion: "198142"
  uid: 091395a6-a414-416a-931b-5d411429cc3a
spec:
  provisionerClassName: core-rukpak-io-plain
  template:
    metadata: {}
    spec:
      provisionerClassName: core-rukpak-io-registry
      source:
        image:
          ref: quay.io/olmqe/nginx-ok-bundle:v1-0.0.5-multi-noexist
        type: image
status:
  activeBundle: bd-ok1-nonexist-2db4bc
  conditions:
  - lastTransitionTime: "2023-11-09T05:28:08Z"
    message: Successfully unpacked the bd-ok1-nonexist-2db4bc Bundle
    reason: UnpackSuccessful
    status: "True"
    type: HasValidBundle
  - lastTransitionTime: "2023-11-09T05:28:18Z"
    message: Instantiated bundle bd-ok1-nonexist-2db4bc successfully
    reason: InstallationSucceeded
    status: "True"
    type: Installed
  - lastTransitionTime: "2023-11-09T05:28:18Z"
    message: '(apps/v1, Kind=Deployment)(nginx-ok1-1399-system/nginx-ok1-1399-controller-manager):
      object InProgress: Available: 0/1'
    reason: Unhealthy
    status: "False"
    type: Healthy
  observedGeneration: 2
--

we'd better change the output of `oc get bd` to let customer know the operator does not work

currently it make customer confused.

[root@preserve-olm-env2 cluster-olm-operator]# oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.15.0-0.nightly-2023-11-08-062604   True        False         5h2m    Cluster version is 4.15.0-0.nightly-2023-11-08-062604
[root@preserve-olm-env2 cluster-olm-operator]# 

always

[root@preserve-olm-env2 cluster-olm-operator]# oc patch featuregate cluster -p '{"spec": {"featureSet": "TechPreviewNoUpgrade"}}' --type=merge
featuregate.config.openshift.io/cluster patched
[root@preserve-olm-env2 cluster-olm-operator]# cat bd-ok1-nonexist.yaml 
apiVersion: core.rukpak.io/v1alpha1
kind: BundleDeployment
metadata:
  name: bd-ok1-nonexist
spec:
  provisionerClassName: core-rukpak-io-plain
  template:
    spec:
      provisionerClassName: core-rukpak-io-registry
      source:
        image:
          ref: quay.io/olmqe/nginx-ok-bundle:v1-0.0.5-multi-noexist
        type: image  
[root@preserve-olm-env2 cluster-olm-operator]# oc apply -f bd-ok1-nonexist.yaml 
bundledeployment.core.rukpak.io/bd-ok1-nonexist created
[root@preserve-olm-env2 cluster-olm-operator]# oc get bd bd-ok1-nonexist
NAME              ACTIVE BUNDLE            INSTALL STATE           AGE
bd-ok1-nonexist   bd-ok1-nonexist-2db4bc   InstallationSucceeded   2m15s
[root@preserve-olm-env2 cluster-olm-operator]# oc get bd bd-ok1-nonexist -o yaml
apiVersion: core.rukpak.io/v1alpha1
kind: BundleDeployment
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"core.rukpak.io/v1alpha1","kind":"BundleDeployment","metadata":{"annotations":{},"name":"bd-ok1-nonexist"},"spec":{"provisionerClassName":"core-rukpak-io-plain","template":{"spec":{"provisionerClassName":"core-rukpak-io-registry","source":{"image":{"ref":"quay.io/olmqe/nginx-ok-bundle:v1-0.0.5-multi-noexist"},"type":"image"}}}}}
  creationTimestamp: "2023-11-09T05:28:08Z"
  generation: 2
  name: bd-ok1-nonexist
  resourceVersion: "198142"
  uid: 091395a6-a414-416a-931b-5d411429cc3a
spec:
  provisionerClassName: core-rukpak-io-plain
  template:
    metadata: {}
    spec:
      provisionerClassName: core-rukpak-io-registry
      source:
        image:
          ref: quay.io/olmqe/nginx-ok-bundle:v1-0.0.5-multi-noexist
        type: image
status:
  activeBundle: bd-ok1-nonexist-2db4bc
  conditions:
  - lastTransitionTime: "2023-11-09T05:28:08Z"
    message: Successfully unpacked the bd-ok1-nonexist-2db4bc Bundle
    reason: UnpackSuccessful
    status: "True"
    type: HasValidBundle
  - lastTransitionTime: "2023-11-09T05:28:18Z"
    message: Instantiated bundle bd-ok1-nonexist-2db4bc successfully
    reason: InstallationSucceeded
    status: "True"
    type: Installed
  - lastTransitionTime: "2023-11-09T05:28:18Z"
    message: '(apps/v1, Kind=Deployment)(nginx-ok1-1399-system/nginx-ok1-1399-controller-manager):
      object InProgress: Available: 0/1'
    reason: Unhealthy
    status: "False"
    type: Healthy
  observedGeneration: 2 

the output of `oc get bd` make customer confused.

1, add one new column to indicated healthy
or
2, change column `install status` to reflect healthy status.