Aman did you verify the CRDs that were injected by the Operator were deleted as well? Is the Object Buket Claim tab also seen?
I just tried to reproduce it using two versions of ODF 4.9.3 and ODF 4.10.0-171 with OCP 4.11. The issues were not reproducible. When `oc delete -n openshift-storage storagesystem --all --wait=true` command was applied the OB/C tabs stopped appearing. After `oc delete project openshift-storage --wait=true --timeout=5m` command was applied and the page was refreshed the ODF tab stopped appearing as well. Refresh is mandatory as we are not uninstalling operator from Installed Operators page when using the above command and the console manifest cannot get updated( we could update it from the cli as well). If the console manifest were to be updated a toast notification would appear for refreshing the page. Even if we don't incorporate commands to update manifest a very easy workaround is to just refresh the page and everything would work.
Just FYI, I tried as well and was unable to reproduce this issue. Maybe something was wrong with the cluster or the points which are mentioned in comment 10 may be the valid reasons.
I think we need to update the uninstallation docs stating that a refresh is mandatory.
Not a 4.11 blocker
Moving it ODF 4.13
When Operator is uninstalled from the `Installed Operator` page, then a proper refresh popup will appear clicking on it will result in the removal of ODF tab from under Storage section. Based on this closing the bug. Please update the BZ if the behavior is not enough.
For the UI to work correctly, correct uninstallation operations need to be taken. The process that is taken is not the correct way to uninstall an Operator. If you want to delete the operator by performing patch operations then, please delete the odf-console consolePlugin CR followed by patching the consoleoperatorconfig that would show the Refresh Popup. If these things are not documented we need a doc bug. But this is something that we cannot do about from the product side.