Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 6. Post-installation integrations
6.1. (Optional) Integrating Quay deployed by RHADS - SSC
If you’re using a new instance of Quay that the RHADS - SSC installer has deployed during the installation, you need to regenerate the Quay OAuth access token and update the Quay integration secret on an OpenShift cluster where RHADS - SSC is running.
This is necessary because the initial token, generated during the RHADS - SSC installation, expires within 2 hours. After its expiration, RHADS - SSC can’t access Quay and view the repositories under the rhtap organization. As a result, the Image Registry tab in the RHDH UI doesn’t display artifacts stored in your Quay repositories.
The following procedure ensures that RHADS - SSC has access to Quay.
Procedure
- Log in to the Quay instance that runs on the same cluster with RHADS - SSC.
-
Navigate to the
rhtaporganization. - Select Applications > OAuth Applications > Create New Application > Generate Token.
- Check the box for the View all visible repositories option.
- Click Generate Access Token.
- Copy and save the access token.
Update the
rhtap-quay-integrationsecret by running the following commands in the terminal:export ACCESS_TOKEN=<generated-Quay-token> oc patch secret rhtap-quay-integration \ -n rhtap \ --type='merge' \ -p="{\"data\":{\"token\":\"$(echo -n $ACCESS_TOKEN | base64)\"}}" tssc deploy chart/rhtap-dhThis step should automatically update the
developer-hub-rhtap-envsecret as well.
The changes take effect when the new backstage-developer-hub pod in the rhtap-dh project is up and running.
Verification
- Go to the Red Hat Developer Hub UI and reload the Image Registry tab. The tab should now list all the artifacts stored in your Quay repositories.
Additionally, to verify that the required secrets have been successfully updated, you can display the values of the
rhtap-quay-integrationanddeveloper-hub-rhtap-envsecrets:oc get secret rhtap-quay-integration -o json -n rhtap | jq -r .data.token | base64 -d oc get secrets developer-hub-rhtap-env -o json -n rhtap-dh | jq -r .data.QUAY__API_TOKEN | base64 -dThe output should show your newly generated Quay access token.
Additional resources
- For more information on Quay OAuth tokens, refer to OAuth 2 access tokens in the Red Hat Quay documentation.
Revised on 2025-08-20 05:37:06 UTC
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}