Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-931

wrong tags in imagestream for backend, zync, wildcard router and description of wildcard router

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Minor Minor
    • None
    • 2.2 CR2
    • OSE Templates
    • None

      According https://issues.jboss.org/browse/THREESCALE-702 there should be for backend:

      Tags: integration, api management, 3scale, api analytics, rate limits, authorization

      but there are

      io.openshift.tags=api, backend, 3scale, 3scale-amp

      for zync there should be:

      Tags: integration, api management, 3scale, data synchronization

      but there are:

      io.openshift.tags=sync, api management, 3scale, rhamp

      for wildcard router there should be:

      Tags: integration, api management, 3scale, api, gateway, wildcard router

      but there are

      io.openshift.tags=integration, nginx, lua, openresty, api, gateway, 3scale, rhamp

      There is wrong description of wildcard router. There is:

      io.k8s.description=To avoid having to create a new route for every 3scale service you define by deploying a wildcard router. The container includes Openresty and it depends on 3scale API gateway (APIcast)

      but there should be:

      Description: Accepts all wildcard subdomain traffic and distributes it between staging and production APIcast API gateways, based on their API public base URL.

              msorianod Miguel Soriano
              mkudlej@redhat.com Martin Kudlej
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: