ARO-14443: Bump hypershift image digest

[jubittajohn]

https://issues.redhat.com/browse/ARO-14443

This update to the image digest correlates to openshift/hypershift@26fc3ce which includes previous commits openshift/hypershift#5456 that introduces the concept of capabilities to Hypershift on a limited basis, as described in openshift/enhancements#1729 and openshift/hypershift#5810

[jubittajohn]

@miguelsorianod @machi1990
(Could you help with reviewing the changes and confirming if this is the right time to merge these changes)
I verified that this bump of the operator works with the current version of CS with the following steps:

1. Created and deployed a new infrastructure for ARO-HCP with the latest changes.
2. Included the changes in this PR and redeployed hypershift using make hypershiftoperator.deploy_pipeline.

3. I pulled down the latest changes for the CS repo and am I on master branch.
4. Initialized the db schemas and started the CS locally after running make cmds.
5. Send a cluster creation request without the new capabilities attribute.
6. The cluster is created successfully.
   
7. Created nodepools in the above created hostedcluster
   

[geoberle]

@miguelsorianod @bryan-cox @machi1990 what about the --tech-preview-no-upgrade flag? can we remove this one with this bump?

[machi1990]

@miguelsorianod @bryan-cox @machi1990 what about the --tech-preview-no-upgrade flag? can we remove this one with this bump?

I think the issue we faced the other time has been fixed in hypershift side. It might be good to test it out though, @jubittajohn fancing doing the same test as #1563 (comment) without the --tech-preview-no-upgrade flag; https://github.com/Azure/ARO-HCP/blob/main/config/config.yaml#L20

[bryan-cox]

@miguelsorianod @bryan-cox @machi1990 what about the --tech-preview-no-upgrade flag? can we remove this one with this bump?

@geoberle @machi1990 - Yeah you shouldn't need that flag anymore.

[jubittajohn]

@miguelsorianod @bryan-cox @machi1990 what about the --tech-preview-no-upgrade flag? can we remove this one with this bump?

@geoberle @machi1990
As I understand, the --tech-preview-no-upgrade flag will no longer be required only after the this PR commit which was merged two days ago. I have to bump the hypershift operator image up to this commit before removing the flag. But for that, I see no images synced into this ACR repo acm-d/rhtap-hypershift-operator after 20/03/2025 as of the time I am commenting.

cc: @bryan-cox

[geoberle]

@miguelsorianod @bryan-cox @machi1990 what about the --tech-preview-no-upgrade flag? can we remove this one with this bump?

@geoberle @machi1990 As I understand, the --tech-preview-no-upgrade flag will no longer be required only after the this PR commit which was merged two days ago. I have to bump the hypershift operator image up to this commit before removing the flag. But for that, I see no images synced into this ACR repo acm-d/rhtap-hypershift-operator after 20/03/2025 as of the time I am commenting.

cc: @bryan-cox

there are no new images in the source repo on quay after the date you mentioned, hence nothing to sync to ACR
https://quay.io/repository/acm-d/rhtap-hypershift-operator?tab=tags

[github-actions]

Please rebase pull request.

[jubittajohn]

@geoberle @machi1990
Thank you for the reviews on this PR.

A new image digest was available yesterday after 10 days. I have used this image to bump the hypershift operator to include both the commits openshift/hypershift#5456 and openshift/hypershift#5810 and removed the flag and have successfully repeated the steps as here #1563 (comment)

[machi1990]

Thank you @jubittajohn
lgtm

[geoberle]

thank you for your thorough testing!