此内容没有您所选择的语言版本。
Chapter 7. Configuring Red Hat Quay (post-deployment)
After the Quay Operator deploys Red Hat Quay, by default the Config Tool continues to run. Going forward, you can use the Config Tool or the Red Hat Quay Operator itself to update and maintain your Red Hat Quay deployment.
7.1. Using the Config Tool
The Red Hat Quay Config Tool provides a web UI for enabling or modifying many of the settings in your Red Hat Quay cluster. To use the Config Tool:
Get the route to the Config Tool by typing:
$ oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD ... example-quayecosystem-quay-config.example.com ...-
Add
https://to the HOST/PORT entry for the Config Tool and enter it into your web browser. -
When prompted, log in using the Config Tool user name and password (
quayconfigandquay, by default). -
Select
Modify configuration for this cluster.
At this point you can change the configuration as you choose. When you are done, select Save Configuration Changes. Here are a few things you should know about using the Config Tool:
- Most changes you make will be checked for accuracy. For example, if you change the location of a service, the Config Tool will check that it can reach that service before saving the configuration. If the connection fails, you have the chance to modify the setting before saving.
- After checking for accuracy, you now have the choice of continuing to edit or completing your changes.
- After you make changes and they are accepted, those changes are deployed to all Red Hat Quay instances in the cluster. There is no need to stop and restart those pods manually.
7.2. Using the Red Hat Quay Operator
Updating your Red Hat Quay cluster using the Red Hat Quay Operator offers a way to deploy changes without having to click through a web UI. Here are some things you should know about changing settings through the Operator:
- The same level of error checking is not performed when you change settings directly through the Red Hat Quay Operator. If, for example, you provide the wrong address to a service, the connection to that service will probably just fail and you would have to track down the problem through OpenShift.
- Once you make a change, those changes will not automatically be applied to your Red Hat Quay instances. To have the changes take effect, you will have to restart the Red Hat Quay pods manually.
'%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}