Este conteúdo não está disponível no idioma selecionado.

Chapter 9. Troubleshooting the QuayRegistry CR


To troubleshoot issues during Red Hat Quay registry deployment, you can check the QuayRegistry custom resource status using the OpenShift Container Platform web console Events page or the oc CLI. These methods help you identify and resolve deployment problems.

To monitor and debug your Red Hat Quay registry deployment, you can check the Events page on the OpenShift Container Platform web console. The Events page shows lifecycle observability and helps you identify problems related to registry deployment.

Prerequisites

  • You have deployed a Red Hat Quay registry.

Procedure

  1. On the OpenShift Container Platform web console, click Operators Installed Operators Red Hat Quay.
  2. On the Red Hat Quay Operator details page, click Quay Registry.
  3. Click the name of the registry Events. On this page, events a streamed in real-time.
  4. Optional: To reveal more information about deployment issues, you can click the name of the registry on the Events page to navigate to the QuayRegistry details page. On the QuayRegistry details page, you can view the condition of all QuayRegistry CR components.

9.2. Monitoring and debugging the QuayRegistry CR by using the CLI

To monitor and debug your Red Hat Quay registry deployment, you can use the oc CLI to check the QuayRegistry custom resource status. The Status field shows component health and helps you troubleshoot deployment issues.

With the oc CLI, you can obtain the following information about the QuayRegistry CR:

  • The conditions field, which field shows the status of all QuayRegistry components.
  • The currentVersion field, which shows the version of Red Hat Quay.
  • The registryEndpoint field, which shows the publicly available hostname of the registry.

Prerequisites

  • You have deployed a Red Hat Quay registry by using the web console or the CLI.

Procedure

  1. View the state of deployed components by entering the following command:

    $ oc get pods -n quay-enterprise
    NAME                                                   READY   STATUS              RESTARTS   AGE
    example-registry-clair-app-86554c6b49-ds7bl            0/1     ContainerCreating   0          2s
    example-registry-clair-app-86554c6b49-hxp5s            0/1     Running             1          17s
    example-registry-clair-postgres-68d8857899-lbc5n       0/1     ContainerCreating   0          17s
    example-registry-quay-app-upgrade-h2v7h                0/1     ContainerCreating   0          9s
    example-registry-quay-database-66f495c9bc-wqsjf        0/1     ContainerCreating   0          17s
    example-registry-quay-mirror-854c88457b-d845g          0/1     Init:0/1            0          2s
    example-registry-quay-mirror-854c88457b-fghxv          0/1     Init:0/1            0          17s
    example-registry-quay-postgres-init-bktdt              0/1     Terminating         0          17s
    example-registry-quay-redis-f9b9d44bf-4htpz            0/1     ContainerCreating   0          17s
  2. Return information about your deployment by entering the following command:

    $ oc get quayregistry -n <namespace> -o yaml
    apiVersion: v1
    items:
    - apiVersion: quay.redhat.com/v1
      kind: QuayRegistry
      metadata:
        annotations:
    ...
      spec:
        components:
        - kind: clair
          managed: true
        - kind: objectstorage
          managed: false
    ...
     status:
        conditions:
        - lastTransitionTime: "2025-10-01T18:46:13Z"
          lastUpdateTime: "2025-10-07T13:12:54Z"
          message: Horizontal pod autoscaler found
          reason: ComponentReady
          status: "True"
          type: ComponentHPAReady
    ...
        currentVersion: v3.15.2
        lastUpdated: 2025-10-07 13:12:54.48811705 +0000 UTC
        registryEndpoint: https://example-registry-quay-cluster-new.gcp.quaydev.org 
    1
    • conditions shows information about the status of all QuayRegistry components.
    • currentVersion shows the current version that the registry is using.
    • registryEndpoint shows the publicly available hostname of the registry.
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2026 Red Hat
Voltar ao topo