Skip to content

services should be created if ingress is disabled #43

@raffaelespazzoli

Description

@raffaelespazzoli

this allows for manual use of different ingresses.
In particular the way ingress is designed here does not work for OCP. It would be nice to have support for OCP.
This would fix the issue for OCP (but the services are needed):

kind: Route
apiVersion: route.openshift.io/v1
metadata:
  name: velero-ui
spec:
  host: velero.apps.${CLUSTER_BASE_DOMAIN}
  path: /
  to:
    kind: Service
    name: velero-ui-vui-ui
    weight: 100
  port:
    targetPort: velero-ui
  tls:
    termination: edge
    insecureEdgeTerminationPolicy: Redirect
  wildcardPolicy: None
---
kind: Route
apiVersion: route.openshift.io/v1
metadata:
  name: velero-api
spec:
  host: velero.apps.${CLUSTER_BASE_DOMAIN}
  path: /api
  to:
    kind: Service
    name: velero-ui-vui-api
    weight: 100
  port:
    targetPort: 8001
  tls:
    termination: edge
    insecureEdgeTerminationPolicy: Redirect
  wildcardPolicy: None  
---
kind: Route
apiVersion: route.openshift.io/v1
metadata:
  name: velero-ws
spec:
  host: velero.apps.${CLUSTER_BASE_DOMAIN}
  path: /ws
  to:
    kind: Service
    name: velero-ui-vui-api
    weight: 100
  port:
    targetPort: 8001
  tls:
    termination: edge
    insecureEdgeTerminationPolicy: Redirect
  wildcardPolicy: None

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions