Skip to content
This repository was archived by the owner on Apr 19, 2023. It is now read-only.
This repository was archived by the owner on Apr 19, 2023. It is now read-only.

enable wildcard route on router #552

Description

@yithian

Description

The installer should configure the secondary router with a 3scale wildcard route and superdomain.

Expected Behavior

The installer:

  • configures a 3scale wildcard route on the second (3amp) router:
apiVersion: route.openshift.io/v1
kind: Route
metadata:
 labels:
   3scale.component: apicast
   3scale.component-element: wildcard-router
   app: 3scale-api-management
 name: apicast-wildcard-router-routing-shard
spec:
 host: wildcard.${CLUSTER}.${DOMAIN}.${TLD}
 port:
   targetPort: http
 tls:
   termination: edge
 to:
   kind: Service
   name: apicast-wildcard-router
   weight: 100
 wildcardPolicy: Subdomain
  • sets ROUTER_ALLOW_WILDCARD_ROUTES=true on the secondary (3amp) router
  • sets {\"data\":{\"THREESCALE_SUPERDOMAIN\": \"3amp.${CLUSTER}.${DOMAIN}.${TLD}\"}} on the system-environment configmap and ensures that the changes are rolled out

Actual Behavior

None of those things happen.

Environment

  • Operating system: (E.g RHEL 7.6 )
    Red Hat Enterprise Linux Server release 7.5 (Maipo)

  • OpenShift version:
    oc v3.11.43
    kubernetes v1.11.0+d4cacc0
    features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://internal.api.integreatly-phx.openshift.com:443
openshift v3.11.43
kubernetes v1.11.0+d4cacc0

  • Ansible version:
    ansible 2.7.1

  • Project Version/Tag: (E.g release-1.0.1)
    release-1.3.0

Steps to reproduce

run the installer

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions