Este contenido no está disponible en el idioma seleccionado.
Chapter 3. Adding TLS Certificates to the Red Hat Quay Container
			To add custom TLS certificates to Red Hat Quay, create a new directory named extra_ca_certs/ beneath the Red Hat Quay config directory. Copy any required site-specific TLS certificates to this new directory.
		
3.1. Add TLS certificates to Red Hat Quay
- View certificate to be added to the container - cat storage.crt -----BEGIN CERTIFICATE----- MIIDTTCCAjWgAwIBAgIJAMVr9ngjJhzbMA0GCSqGSIb3DQEBCwUAMD0xCzAJBgNV [...] -----END CERTIFICATE----- - $ cat storage.crt -----BEGIN CERTIFICATE----- MIIDTTCCAjWgAwIBAgIJAMVr9ngjJhzbMA0GCSqGSIb3DQEBCwUAMD0xCzAJBgNV [...] -----END CERTIFICATE------ Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Create certs directory and copy certificate there - Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Obtain the quay container’s - CONTAINER IDwith- docker ps:- docker ps - $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS 5a3e82c4a75f <registry>/<repo>/quay:v3.3.4 "/sbin/my_init" 24 hours ago Up 18 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 443/tcp grave_keller- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Restart the container with that ID: - docker restart 5a3e82c4a75f - $ docker restart 5a3e82c4a75f- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Examine the certificate copied into the container namespace: - docker exec -it 5a3e82c4a75f cat /etc/ssl/certs/storage.pem -----BEGIN CERTIFICATE----- MIIDTTCCAjWgAwIBAgIJAMVr9ngjJhzbMA0GCSqGSIb3DQEBCwUAMD0xCzAJBgNV - $ docker exec -it 5a3e82c4a75f cat /etc/ssl/certs/storage.pem -----BEGIN CERTIFICATE----- MIIDTTCCAjWgAwIBAgIJAMVr9ngjJhzbMA0GCSqGSIb3DQEBCwUAMD0xCzAJBgNV- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
3.2. Add certs when deployed on Kubernetes
When deployed on Kubernetes, Red Hat Quay mounts in a secret as a volume to store config assets. Unfortunately, this currently breaks the upload certificate function of the superuser panel.
To get around this error, a base64 encoded certificate can be added to the secret after Red Hat Quay has been deployed. Here’s how:
- Begin by base64 encoding the contents of the certificate: - Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Use the - kubectltool to edit the quay-enterprise-config-secret.- kubectl --namespace quay-enterprise edit secret/quay-enterprise-config-secret - $ kubectl --namespace quay-enterprise edit secret/quay-enterprise-config-secret- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Add an entry for the cert and paste the full base64 encoded string under the entry: - custom-cert.crt: c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo= - custom-cert.crt: c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- 
						Finally, recycle all Red Hat Quay pods. Use kubectl deleteto remove all Red Hat Quay pods. The Red Hat Quay Deployment will automatically schedule replacement pods with the new certificate data.