Skip to content

Files

Latest commit

 

History

History
58 lines (53 loc) · 1.46 KB

operator-unmanaged-route.adoc

File metadata and controls

58 lines (53 loc) · 1.46 KB

Disabling the Route component

Use the following procedure to prevent the {productname} Operator from creating a route.

Procedure
  1. Set the component as managed: false in the quayregistry.yaml file:

    apiVersion: quay.redhat.com/v1
    kind: QuayRegistry
    metadata:
      name: example-registry
      namespace: quay-enterprise
    spec:
      components:
        - kind: route
          managed: false
  2. Edit the config.yaml file to specify that {productname} handles SSL/TLS. For example:

    # ...
    EXTERNAL_TLS_TERMINATION: false
    # ...
    SERVER_HOSTNAME: example-registry-quay-quay-enterprise.apps.user1.example.com
    # ...
    PREFERRED_URL_SCHEME: https
    # ...

    If you do not configure the unmanaged route correctly, the following error is returned:

    {
      {
        "kind":"QuayRegistry",
        "namespace":"quay-enterprise",
        "name":"example-registry",
        "uid":"d5879ba5-cc92-406c-ba62-8b19cf56d4aa",
        "apiVersion":"quay.redhat.com/v1",
        "resourceVersion":"2418527"
      },
      "reason":"ConfigInvalid",
      "message":"required component `route` marked as unmanaged, but `configBundleSecret` is missing necessary fields"
    }
Note

Disabling the default route means you are now responsible for creating a Route, Service, or Ingress in order to access the {productname} instance. Additionally, whatever DNS you use must match the SERVER_HOSTNAME in the {productname} config.