1166 - 'Quay Enterprise' to 'Red Hat Quay'
This commit is contained in:
Tom McKay
parent
b5a5ce7c43
commit
674e471973
24 changed files with 71 additions and 71 deletions
|
|
@ -228,9 +228,9 @@
|
|||
|
||||
### v2.1.0
|
||||
|
||||
**IMPORTANT NOTE FOR POSTGRES USERS:** This release contains a migration which adds full-text searching capabilities to Quay Enterprise. In order to support this feature, the migration will attempt to create the `pg_trgm` extension in the database. This operation requires **superuser access** to run and requires the extension to be installed. See https://coreos.com/quay-enterprise/docs/latest/postgres-additional-modules.html for more information on installing the extension.
|
||||
**IMPORTANT NOTE FOR POSTGRES USERS:** This release contains a migration which adds full-text searching capabilities to Red Hat Quay. In order to support this feature, the migration will attempt to create the `pg_trgm` extension in the database. This operation requires **superuser access** to run and requires the extension to be installed. See https://coreos.com/quay-enterprise/docs/latest/postgres-additional-modules.html for more information on installing the extension.
|
||||
|
||||
If the user given to Quay Enterprise is not a superuser, please temporarily grant superuser access to the Quay Enterprise user in the database (or change the user in config) **before** upgrading.
|
||||
If the user given to Red Hat Quay is not a superuser, please temporarily grant superuser access to the Red Hat Quay user in the database (or change the user in config) **before** upgrading.
|
||||
|
||||
- Added: Full text search support (#2272)
|
||||
- Added: OIDC support (#2300, #2348)
|
||||
|
|
@ -638,7 +638,7 @@ In order to upgrade to this version, your cluster must contain a valid license,
|
|||
|
||||
### v1.13.0
|
||||
|
||||
- Added new Quay Enterprise rebranding (#723, #738, #735, #745, #746, #748, #747, #751)
|
||||
- Added new Red Hat Quay rebranding (#723, #738, #735, #745, #746, #748, #747, #751)
|
||||
- Added a styled 404 page (#683)
|
||||
- Hid the run button from users that haven't created a trigger (#727)
|
||||
- Added timeouts to calls to GitLab, Bitbucket, GitHub APIs (#636, #633, #631, #722)
|
||||
|
|
|
|||
|
|
@ -363,7 +363,7 @@ docker build -t $QUAY_TAG --build-arg RUN_TESTS=true .
|
|||
|
||||
## Documentation
|
||||
|
||||
* [Quay Enterprise Documentation](https://tectonic.com/quay-enterprise/docs/latest)
|
||||
* [Red Hat Quay Documentation](https://tectonic.com/quay-enterprise/docs/latest)
|
||||
* [Quay.io Documentation](https://docs.quay.io)
|
||||
|
||||
### Architecture at a Glance
|
||||
|
|
|
|||
|
|
@ -87,8 +87,8 @@ class DefaultConfig(ImmutableConfig):
|
|||
PREFERRED_URL_SCHEME = 'http'
|
||||
SERVER_HOSTNAME = 'localhost:5000'
|
||||
|
||||
REGISTRY_TITLE = 'Quay Enterprise'
|
||||
REGISTRY_TITLE_SHORT = 'Quay Enterprise'
|
||||
REGISTRY_TITLE = 'Red Hat Quay'
|
||||
REGISTRY_TITLE_SHORT = 'Red Hat Quay'
|
||||
|
||||
CONTACT_INFO = [
|
||||
'mailto:support@quay.io',
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Quay config tool
|
||||
|
||||
The Quay config tool is a project to ease the setup, modification, and deployment of Red Hat Quay (sometimes referred to as Quay Enterprise).
|
||||
The Quay config tool is a project to ease the setup, modification, and deployment of Red Hat Quay (sometimes referred to as Red Hat Quay).
|
||||
|
||||
The project was built by [Sam Chow] in the summer of 2018.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ logger = logging.getLogger(__name__)
|
|||
|
||||
@resource('/v1/kubernetes/deployments/')
|
||||
class SuperUserKubernetesDeployment(ApiResource):
|
||||
""" Resource for the getting the status of Quay Enterprise deployments and cycling them """
|
||||
""" Resource for the getting the status of Red Hat Quay deployments and cycling them """
|
||||
schemas = {
|
||||
'ValidateDeploymentNames': {
|
||||
'type': 'object',
|
||||
|
|
|
|||
|
|
@ -141,7 +141,7 @@ class KubernetesAccessorSingleton(object):
|
|||
"""
|
||||
Removes the old config and replaces it with the new_secret_data as one action
|
||||
"""
|
||||
# Check first that the namespace for Quay Enterprise exists. If it does not, report that
|
||||
# Check first that the namespace for Red Hat Quay exists. If it does not, report that
|
||||
# as an error, as it seems to be a common issue.
|
||||
namespace_url = 'namespaces/%s' % (self.kube_config.qe_namespace)
|
||||
response = self._execute_k8s_api('GET', namespace_url)
|
||||
|
|
@ -251,7 +251,7 @@ class KubernetesAccessorSingleton(object):
|
|||
if '/' in relative_file_path:
|
||||
raise Exception('Expected path from get_volume_path, but found slashes')
|
||||
|
||||
# Check first that the namespace for Quay Enterprise exists. If it does not, report that
|
||||
# Check first that the namespace for Red Hat Quay exists. If it does not, report that
|
||||
# as an error, as it seems to be a common issue.
|
||||
namespace_url = 'namespaces/%s' % (self.kube_config.qe_namespace)
|
||||
response = self._execute_k8s_api('GET', namespace_url)
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
# On-premises installation
|
||||
|
||||
Quay Enterprise requires three components to be running to begin the setup process:
|
||||
Red Hat Quay requires three components to be running to begin the setup process:
|
||||
|
||||
- A supported database (MySQL, Postgres)
|
||||
- A Redis instance (for real-time events)
|
||||
- The Quay Enterprise image
|
||||
- The Red Hat Quay image
|
||||
|
||||
**NOTE**: Please have the host and port of the database and the Redis instance ready.
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ sudo docker run -d -p 6379:6379 quay.io/quay/redis
|
|||
|
||||
**NOTE**: This host will have to accept incoming connections on port 6379 from the hosts on which the registry will run.
|
||||
|
||||
## Downloading the Quay Enterprise image
|
||||
## Downloading the Red Hat Quay image
|
||||
|
||||
After signing up you will be able to download a pull secret file named `config.json`.
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ Visit the image locally by going to https://yourhost/
|
|||
|
||||
**Note**: You will see warning about an invalid certificate authority when visiting in your browser. This is because we self sign the certificate at container load time, so you can safely bypass this warning. (On Chrome, for example, click on Advanced, then "Proceed to localhost")
|
||||
|
||||
<img src="img/initial-choice-screen.png" class="img-center" alt="Quay Enterprise Configuration Tool"/>
|
||||
<img src="img/initial-choice-screen.png" class="img-center" alt="Red Hat Quay Configuration Tool"/>
|
||||
|
||||
Click on "Start New Registry Setup", and follow the instructions to create your configuration, downloading and saving it when complete.
|
||||
|
||||
|
|
@ -72,7 +72,7 @@ Click on "Start New Registry Setup", and follow the instructions to create your
|
|||
|
||||
## Setting up the directories
|
||||
|
||||
Quay Enterprise requires a configuration directory (and a storage directory if using local storage):
|
||||
Red Hat Quay requires a configuration directory (and a storage directory if using local storage):
|
||||
|
||||
You will need to extract the tarball you received in the previous step into a directory:
|
||||
```
|
||||
|
|
@ -107,21 +107,21 @@ sudo docker run --restart=always -p 443:443 -p 80:80 --privileged=true -v /local
|
|||
|
||||
## Verifying the status of QE
|
||||
|
||||
Visit the `/health/endtoend` endpoint on the Quay Enterprise hostname and verify that the `code` is `200` and `is_testing` is `false`.
|
||||
Visit the `/health/endtoend` endpoint on the Red Hat Quay hostname and verify that the `code` is `200` and `is_testing` is `false`.
|
||||
|
||||
If `code` is anything other than `200`, visit http://yourhost/ and you will see instructions detailing the problems Quay Enterprise is having with the configuration.
|
||||
If `code` is anything other than `200`, visit http://yourhost/ and you will see instructions detailing the problems Red Hat Quay is having with the configuration.
|
||||
|
||||
|
||||
## Logging in
|
||||
|
||||
### If using database authentication:
|
||||
|
||||
Once Quay Enterprise is running, new users can be created by clicking the `Sign Up` button. If e-mail is enabled, the sign up process will require an e-mail confirmation step, after which repositories, organizations and teams can be setup by the user.
|
||||
Once Red Hat Quay is running, new users can be created by clicking the `Sign Up` button. If e-mail is enabled, the sign up process will require an e-mail confirmation step, after which repositories, organizations and teams can be setup by the user.
|
||||
|
||||
|
||||
### If using LDAP authentication:
|
||||
|
||||
Users should be able to login to the Quay Enterprise directly with their LDAP username and password.
|
||||
Users should be able to login to the Red Hat Quay directly with their LDAP username and password.
|
||||
|
||||
|
||||
## Updating your configuration
|
||||
|
|
@ -136,12 +136,12 @@ Click on "Modify an existing configuration", and upload the tarball provided whe
|
|||
|
||||
You will be taken to the setup page, with your previous configuration values pre-populated. After you have made your changes, save the configuration and download the tarball.
|
||||
|
||||
<img src="img/load-tarball-config.png" class="img-center" alt="Quay Enterprise Load Configuration"/>
|
||||
<img src="img/load-tarball-config.png" class="img-center" alt="Red Hat Quay Load Configuration"/>
|
||||
|
||||
Extract the tarball into the config directory where your Quay Enterprise will run:
|
||||
Extract the tarball into the config directory where your Red Hat Quay will run:
|
||||
```
|
||||
mkdir config && tar xzf quay-config.tar.gz -C config
|
||||
```
|
||||
|
||||
Now run Quay Enterprise as stated in the **Running the registry** step, and your new instance will reflect the changes made in the new configuration.
|
||||
Now run Red Hat Quay as stated in the **Running the registry** step, and your new instance will reflect the changes made in the new configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,18 +1,18 @@
|
|||
# Quay Enterprise Installation on Kubernetes
|
||||
# Red Hat Quay Installation on Kubernetes
|
||||
|
||||
This guide walks through the deployment of [Quay Enterprise][quay-enterprise-tour] onto a Kubernetes cluster.
|
||||
After completing the steps in this guide, a deployer will have a functioning instance of Quay Enterprise orchestrated as a Kubernetes service on a cluster, and will be able to access the Quay Enterprise Setup tool with a browser to complete configuration of image repositories, builders, and users.
|
||||
This guide walks through the deployment of [Red Hat Quay][quay-enterprise-tour] onto a Kubernetes cluster.
|
||||
After completing the steps in this guide, a deployer will have a functioning instance of Red Hat Quay orchestrated as a Kubernetes service on a cluster, and will be able to access the Red Hat Quay Setup tool with a browser to complete configuration of image repositories, builders, and users.
|
||||
|
||||
[quay-enterprise-tour]: https://quay.io/tour/enterprise
|
||||
|
||||
## Prerequisites
|
||||
|
||||
A PostgreSQL database must be available for Quay Enterprise metadata storage.
|
||||
A PostgreSQL database must be available for Red Hat Quay metadata storage.
|
||||
We currently recommend running this database server outside of the cluster.
|
||||
|
||||
## Download Kubernetes Configuration Files
|
||||
|
||||
Visit the [RedHat Documentation][RedHat-documentation] and download the pre-formatted pull secret, under "Account Assets". There are several formats of the secret, be sure to download the "dockercfg" format resulting in a `config.json` file. This pull secret is used to download the Quay Enterprise containers.
|
||||
Visit the [RedHat Documentation][RedHat-documentation] and download the pre-formatted pull secret, under "Account Assets". There are several formats of the secret, be sure to download the "dockercfg" format resulting in a `config.json` file. This pull secret is used to download the Red Hat Quay containers.
|
||||
|
||||
This will be used later in the guide.
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ Next, download each of the following files to your workstation, placing them alo
|
|||
|
||||
## Role Based Access Control
|
||||
|
||||
Quay Enterprise has native Kubernetes integrations. These integrations require Service Account to have access to Kubernetes API. When Kubernetes RBAC is enabled, Role Based Access Control policy manifests also have to be deployed.
|
||||
Red Hat Quay has native Kubernetes integrations. These integrations require Service Account to have access to Kubernetes API. When Kubernetes RBAC is enabled, Role Based Access Control policy manifests also have to be deployed.
|
||||
|
||||
Kubernetes API has minor changes between versions 1.4 and 1.5, Download appropiate versions of Role Based Access Control (RBAC) Policies.
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ kubectl create -f quay-servicetoken-role-k8s1-6.yaml
|
|||
kubectl create -f quay-servicetoken-role-binding-k8s1-6.yaml
|
||||
```
|
||||
|
||||
### Deploy Quay Enterprise objects
|
||||
### Deploy Red Hat Quay objects
|
||||
|
||||
Finally, the remaining Kubernetes objects can be deployed onto Kubernetes:
|
||||
|
||||
|
|
@ -71,7 +71,7 @@ kubectl create -f quay-enterprise-config-secret.yml -f quay-enterprise-redis.yml
|
|||
|
||||
## Expose via Kubernetes Service
|
||||
|
||||
In order to access Quay Enterprise, a user must route to it through a Kubernetes Service.
|
||||
In order to access Red Hat Quay, a user must route to it through a Kubernetes Service.
|
||||
It is up to the deployer to decide which Service type is appropriate for their use case: a [LoadBalancer](http://kubernetes.io/docs/user-guide/services/#type-loadbalancer) or a [NodePort](http://kubernetes.io/docs/user-guide/services/#type-nodeport).
|
||||
|
||||
A LoadBalancer is recommended if the Kubernetes cluster is integrated with a cloud provider, otherwise a NodePort will suffice.
|
||||
|
|
@ -102,9 +102,9 @@ kubectl create -f quay-enterprise-service-nodeport.yml
|
|||
By default, the quay-enterprise service will be available on port 30080 on every node in the Kubernetes cluster.
|
||||
If this port conflicts with an existing Kubernetes Service, simply modify the sample configuration file and change the value of NodePort.
|
||||
|
||||
## Continue with Quay Enterprise Setup
|
||||
## Continue with Red Hat Quay Setup
|
||||
|
||||
All that remains is to configure Quay Enterprise itself through the configuration tool.
|
||||
All that remains is to configure Red Hat Quay itself through the configuration tool.
|
||||
|
||||
Download the following files to your workstation:
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ kubectl apply -f qe-config-tool.yml -f config-tool-service-nodeport.yml
|
|||
|
||||
By default, the config-tool service will be available on port 30090 on every node in the Kubernetes cluster.
|
||||
Similar to the Quay application service, if this port conflicts with an existing Kubernetes Service, simply modify the sample configuration file and change the value of NodePort.
|
||||
Once at the Quay Enterprise setup UI, follow the setup instructions to finalize your installation.
|
||||
Once at the Red Hat Quay setup UI, follow the setup instructions to finalize your installation.
|
||||
|
||||
## Using the Configuration Tool
|
||||
Click on "Start New Configuration for this Cluster", and follow the instructions to create your configuration, downloading and saving it (to load as a backup or if you ever wish to change your settings).
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@
|
|||
<!-- Body -->
|
||||
<div class="modal-body download-tarball-modal">
|
||||
<div ng-if="$ctrl.loadedConfig">
|
||||
Please download your updated configuration. To deploy these changes to your Quay Enterprise instances, please
|
||||
Please download your updated configuration. To deploy these changes to your Red Hat Quay instances, please
|
||||
<a target="_blank" href="https://coreos.com/quay-enterprise/docs/latest/initial-setup.html">
|
||||
see the docs.
|
||||
</a>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ export class KubeDeployModalComponent implements OnDestroy {
|
|||
this.state = 'error';
|
||||
this.errorMessage = `There are no Quay deployments active in this namespace. \
|
||||
Please check that you are running this \
|
||||
tool in the same namespace as the Quay Enterprise application\
|
||||
tool in the same namespace as the Red Hat Quay application\
|
||||
Associated error message: ${err.toString()}`;
|
||||
})
|
||||
}
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@
|
|||
<td>TLS:</td>
|
||||
<td>
|
||||
<select class="form-control" ng-model="mapped.TLS_SETTING">
|
||||
<option value="internal-tls">Quay Enterprise handles TLS</option>
|
||||
<option value="internal-tls">Red Hat Quay handles TLS</option>
|
||||
<option value="external-tls">My own load balancer handles TLS (Not Recommended)</option>
|
||||
<option value="none">None (Not For Production)</option>
|
||||
</select>
|
||||
|
|
@ -80,7 +80,7 @@
|
|||
</div>
|
||||
|
||||
<div class="co-alert co-alert-warning" ng-if="mapped.TLS_SETTING == 'external-tls'" style="margin-bottom: 20px">
|
||||
Terminating TLS outside of Quay Enterprise can result in unusual behavior if the external load balancer is not
|
||||
Terminating TLS outside of Red Hat Quay can result in unusual behavior if the external load balancer is not
|
||||
configured properly. <strong>This option is not recommended for simple setups</strong>. Please contact support
|
||||
if you encounter problems while using this option.
|
||||
</div>
|
||||
|
|
@ -495,7 +495,7 @@
|
|||
pattern="http(s)?://.+"></span>
|
||||
<div class="help-text">
|
||||
The HTTP URL at which the torrents should be announced. A JWT-compatible tracker such as <a href="https://github.com/chihaya/chihaya" ng-safenewtab>Chihaya</a> must be run to ensure proper security. Documentation on running Chihaya with
|
||||
this support can be found at <a href="https://tectonic.com/quay-enterprise/docs/latest/running-chihaya.html">Running Chihaya for Quay Enterprise</a>.
|
||||
this support can be found at <a href="https://tectonic.com/quay-enterprise/docs/latest/running-chihaya.html">Running Chihaya for Red Hat Quay</a>.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ const templateUrl = require('./setup.html');
|
|||
|
||||
(function() {
|
||||
/**
|
||||
* The Setup page provides a nice GUI walkthrough experience for setting up Quay Enterprise.
|
||||
* The Setup page provides a nice GUI walkthrough experience for setting up Red Hat Quay.
|
||||
*/
|
||||
|
||||
angular.module('quay-config').directive('setup', () => {
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<div class="page-content" ng-show="currentStep == States.CONFIG">
|
||||
<div class="cor-title">
|
||||
<span class="cor-title-link"></span>
|
||||
<span class="cor-title-content">Quay Enterprise Setup</span>
|
||||
<span class="cor-title-content">Red Hat Quay Setup</span>
|
||||
</div>
|
||||
|
||||
<div class="co-main-content-panel" style="padding: 20px;">
|
||||
|
|
|
|||
|
|
@ -351,7 +351,7 @@
|
|||
|
||||
<b>Can I change my plan?</b>
|
||||
|
||||
<p>Yes, you can change your plan at any time and your account will be pro-rated for the difference. For large organizations, Quay Enterprise offers unlimited users and repos.</p>
|
||||
<p>Yes, you can change your plan at any time and your account will be pro-rated for the difference. For large organizations, Red Hat Quay offers unlimited users and repos.</p>
|
||||
|
||||
<b>Do you offer special plans for business or academic institutions?</b>
|
||||
|
||||
|
|
@ -404,14 +404,14 @@
|
|||
</div>
|
||||
</div>
|
||||
<div class="co-p-quay-diagram">
|
||||
<img src="/static/img/QE-complex.svg" alt="Quay Enterprise System" class="vertical" />
|
||||
<img src="/static/img/QE-complex-h.svg" alt="Quay Enterprise System" class="horizontal" />
|
||||
<img src="/static/img/QE-complex.svg" alt="Red Hat Quay System" class="vertical" />
|
||||
<img src="/static/img/QE-complex-h.svg" alt="Red Hat Quay System" class="horizontal" />
|
||||
<div class="co-p-quay-diagram-caption co-m-text-light">Highly available installation with geo-replication</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="flex-wrap">
|
||||
<div class="co-p-quay-enterprise-top-cta">
|
||||
<div class="co-p-quay-enterprise-top-cta-text">Ready to try Quay Enterprise?</div>
|
||||
<div class="co-p-quay-enterprise-top-cta-text">Ready to try Red Hat Quay?</div>
|
||||
<div class="co-p-quay-enterprise-top-cta-buttons">
|
||||
<div class="co-p-quay-enterprise-top-cta-button-wrap">
|
||||
<button class="btn btn-primary btn-lg trial-button" ng-click="qeStartTrial()">
|
||||
|
|
@ -485,26 +485,26 @@
|
|||
|
||||
<!-- FAQ -->
|
||||
<div class="col-md-7 col-md-pull-5 faq-col">
|
||||
<h4>How can I run Quay Enterprise?</h4>
|
||||
<h4>How can I run Red Hat Quay?</h4>
|
||||
<p>
|
||||
Quay Enterprise is delivered as a set of containers that can run on any infrastructure.
|
||||
It is recommended to run Quay Enterprise in highly-available fashion, on multiple machines.
|
||||
Red Hat Quay is delivered as a set of containers that can run on any infrastructure.
|
||||
It is recommended to run Red Hat Quay in highly-available fashion, on multiple machines.
|
||||
</p>
|
||||
|
||||
<h4>How is Quay Enterprise different than Quay.io?</h4>
|
||||
<h4>How is Red Hat Quay different than Quay.io?</h4>
|
||||
|
||||
<p>
|
||||
Quay Enterprise is closely related to Quay.io, but runs on your own hardware or in your cloud environment.
|
||||
Red Hat Quay is closely related to Quay.io, but runs on your own hardware or in your cloud environment.
|
||||
Running the application yourself is more secure and is more performant when running on the same cluster as your containerized applications.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
When running behind your firewall, Quay Enterprise can connect to private Git repositories, LDAP infrastructure, and more.
|
||||
When running behind your firewall, Red Hat Quay can connect to private Git repositories, LDAP infrastructure, and more.
|
||||
</p>
|
||||
|
||||
<h4>Additional FAQs</h4>
|
||||
|
||||
<b>Is there a free trial for Quay Enterprise?</b>
|
||||
<b>Is there a free trial for Red Hat Quay?</b>
|
||||
|
||||
<p>
|
||||
Yes, the first 30 days of usage are free, and then your license will be automatically converted to the standard rate.
|
||||
|
|
@ -513,11 +513,11 @@
|
|||
|
||||
<b>What types of payment do you accept?</b>
|
||||
|
||||
<p>Quay Enterprise is billed annually with a purchase order.</p>
|
||||
<p>Red Hat Quay is billed annually with a purchase order.</p>
|
||||
|
||||
<b>Can I ugrade from Quay.io (hosted)?</b>
|
||||
|
||||
<p>Yes, you can upgrade from Quay.io to Quay Enterprise easily.</p>
|
||||
<p>Yes, you can upgrade from Quay.io to Red Hat Quay easily.</p>
|
||||
|
||||
<b>Data transfer limits?</b>
|
||||
|
||||
|
|
@ -553,7 +553,7 @@
|
|||
</h1>
|
||||
|
||||
<p class="text-left">
|
||||
To get started, download the Red Hat® Quay Enterprise container image. Red Hat® Quay is distributed via container images only.
|
||||
To get started, download the Red Hat® Red Hat Quay container image. Red Hat® Quay is distributed via container images only.
|
||||
In previous versions of Quay a license file has been required to run Quay. This license file got deprecated with Quay v2.9.0
|
||||
and is no longer required. To pull the Quay images from Quay.io a secret is provided inside the Red Hat® Customer Portal.
|
||||
</p>
|
||||
|
|
@ -591,7 +591,7 @@
|
|||
</p>
|
||||
<div class="step-text">Step 5: Get the Red Hat® Quay container image</div>
|
||||
<p>
|
||||
Visit the <a href="https://access.redhat.com/solutions/3533201" target="_blank">"Accessing Quay Enterprise without a
|
||||
Visit the <a href="https://access.redhat.com/solutions/3533201" target="_blank">"Accessing Red Hat Quay without a
|
||||
CoreOS login"</a> page in the customer portal. Follow the directions listed on that page for pulling the Red Hat®
|
||||
Quay container image.
|
||||
</p>
|
||||
|
|
@ -613,7 +613,7 @@
|
|||
<div class="step-text">Step 1: <a href="https://access.redhat.com/login" target="_blank">Log in</a> to the customer portal</div>
|
||||
<div class="step-text">Step 2: Get the Red Hat® Quay container image</div>
|
||||
<p>
|
||||
Visit the <a href="https://access.redhat.com/solutions/3533201" target="_blank">"Accessing Quay Enterprise without a
|
||||
Visit the <a href="https://access.redhat.com/solutions/3533201" target="_blank">"Accessing Red Hat Quay without a
|
||||
CoreOS login"</a> page in the customer portal. Follow the directions listed on that page for pulling the Red Hat®
|
||||
Quay container image.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
</div>
|
||||
|
||||
<div class="section-description-header twenty">
|
||||
Service keys provide a recognized means of authentication between Quay Enterprise and external services, as well as between external services. <br>Example services include Quay Security Scanner speaking to a <a href="https://github.com/coreos/clair" target="_blank">Clair</a> cluster, or Quay Enterprise speaking to its
|
||||
Service keys provide a recognized means of authentication between Red Hat Quay and external services, as well as between external services. <br>Example services include Quay Security Scanner speaking to a <a href="https://github.com/coreos/clair" target="_blank">Clair</a> cluster, or Red Hat Quay speaking to its
|
||||
<a href="https://tectonic.com/quay-enterprise/docs/latest/build-support.html" target="_blank">build workers</a>.
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -198,7 +198,7 @@
|
|||
</div>
|
||||
|
||||
<div class="row" style="text-align: center; margin-bottom: 20px;">
|
||||
<a href="/plans?tab=enterprise" class="btn btn-primary">Learn more about Quay Enterprise</a>
|
||||
<a href="/plans?tab=enterprise" class="btn btn-primary">Learn more about Red Hat Quay</a>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
pages.create('incomplete-setup', 'incomplete-setup.html', IncompleteSetupCtrl,
|
||||
{
|
||||
'newLayout': true,
|
||||
'title': 'Quay Enterprise Setup Incomplete'
|
||||
'title': 'Red Hat Quay Setup Incomplete'
|
||||
})
|
||||
}]);
|
||||
|
||||
|
|
@ -65,7 +65,7 @@
|
|||
|
||||
if (window.__kubernetes_namespace) {
|
||||
title = "Configuration Secret Missing";
|
||||
message = `It looks like the Quay Enterprise secret is not present in the namespace <code>${window.__kubernetes_namespace}.</code>` +
|
||||
message = `It looks like the Red Hat Quay secret is not present in the namespace <code>${window.__kubernetes_namespace}.</code>` +
|
||||
"<br>Please double-check that the secret exists, or " +
|
||||
"<a href='https://coreos.com/docs/enterprise-registry/initial-setup/'>" +
|
||||
"refer to the Setup Guide</a>";
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
(function() {
|
||||
/**
|
||||
* The superuser admin page provides a new management UI for Quay Enterprise.
|
||||
* The superuser admin page provides a new management UI for Red Hat Quay.
|
||||
*/
|
||||
angular.module('quayPages').config(['pages', function(pages) {
|
||||
pages.create('superuser', 'super-user.html', SuperuserCtrl,
|
||||
{
|
||||
'newLayout': true,
|
||||
'title': 'Quay Enterprise Management'
|
||||
'title': 'Red Hat Quay Management'
|
||||
})
|
||||
}]);
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
<div class="page-content" quay-show="Features.SUPER_USERS">
|
||||
<div class="cor-title">
|
||||
<span class="cor-title-link"></span>
|
||||
<span class="cor-title-content">Quay Enterprise Setup Incomplete</span>
|
||||
<span class="cor-title-content">Red Hat Quay Setup Incomplete</span>
|
||||
</div>
|
||||
|
||||
<div class="co-main-content-panel" style="padding: 20px;">
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
|
||||
<div class="cor-title">
|
||||
<span class="cor-title-link"></span>
|
||||
<span class="cor-title-content">Quay Enterprise Management</span>
|
||||
<span class="cor-title-content">Red Hat Quay Management</span>
|
||||
</div>
|
||||
|
||||
<cor-tab-panel orientation="vertical" cor-nav-tabs>
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ class HtmlOutput:
|
|||
|
||||
#output += '<h1 class="root_title">{}</h1>\n'.format(root_item['title'])
|
||||
#output += '<h1 class="root_title">{}</h1>\n'.format(root_item['title'])
|
||||
output += "Schema for Quay Enterprise"
|
||||
output += "Schema for Red Hat Quay"
|
||||
|
||||
output += '<ul class="level0">\n'
|
||||
last_level = 0
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<link rel="stylesheet" type="text/css" href="style.css" />
|
||||
</head>
|
||||
<body>
|
||||
Schema for Quay Enterprise<ul class="level0">
|
||||
Schema for Red Hat Quay<ul class="level0">
|
||||
<li class="schema item">
|
||||
<div class="name">AUTHENTICATION_TYPE</div>
|
||||
<div class="type">[string]</div>
|
||||
|
|
@ -970,7 +970,7 @@ Schema for Quay Enterprise<ul class="level0">
|
|||
<div class="required"></div>
|
||||
<div class="docs">
|
||||
<div class="title"></div>
|
||||
<div class="description">If specified, the long-form title for the registry. Defaults to `Quay Enterprise`.</div>
|
||||
<div class="description">If specified, the long-form title for the registry. Defaults to `Red Hat Quay`.</div>
|
||||
<div class="x-example">Example: <code>Corp Container Service</code></div>
|
||||
</div>
|
||||
</li>
|
||||
|
|
@ -980,7 +980,7 @@ Schema for Quay Enterprise<ul class="level0">
|
|||
<div class="required"></div>
|
||||
<div class="docs">
|
||||
<div class="title"></div>
|
||||
<div class="description">If specified, the short-form title for the registry. Defaults to `Quay Enterprise`.</div>
|
||||
<div class="description">If specified, the short-form title for the registry. Defaults to `Red Hat Quay`.</div>
|
||||
<div class="x-example">Example: <code>CCS</code></div>
|
||||
</div>
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ class KubernetesConfigProvider(BaseFileProvider):
|
|||
if '/' in relative_file_path:
|
||||
raise Exception('Expected path from get_volume_path, but found slashes')
|
||||
|
||||
# Check first that the namespace for Quay Enterprise exists. If it does not, report that
|
||||
# Check first that the namespace for Red Hat Quay exists. If it does not, report that
|
||||
# as an error, as it seems to be a common issue.
|
||||
namespace_url = 'namespaces/%s' % (QE_NAMESPACE)
|
||||
response = self._execute_k8s_api('GET', namespace_url)
|
||||
|
|
|
|||
|
|
@ -132,12 +132,12 @@ CONFIG_SCHEMA = {
|
|||
# User-visible configuration.
|
||||
'REGISTRY_TITLE': {
|
||||
'type': 'string',
|
||||
'description': 'If specified, the long-form title for the registry. Defaults to `Quay Enterprise`.',
|
||||
'description': 'If specified, the long-form title for the registry. Defaults to `Red Hat Quay`.',
|
||||
'x-example': 'Corp Container Service',
|
||||
},
|
||||
'REGISTRY_TITLE_SHORT': {
|
||||
'type': 'string',
|
||||
'description': 'If specified, the short-form title for the registry. Defaults to `Quay Enterprise`.',
|
||||
'description': 'If specified, the short-form title for the registry. Defaults to `Red Hat Quay`.',
|
||||
'x-example': 'CCS',
|
||||
},
|
||||
'CONTACT_INFO': {
|
||||
|
|
|
|||
Reference in a new issue