0

But we are getting status code 404 while accessing the API.

Implemented below steps:

  1. Pointed domain URL to istio load balancer external IP.
  2. Applyed a VirtualService that maps its route destinations to istio-ingressgateway.istio-system.svc.cluster.local

Yaml file :

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: entry-route
  namespace: vulcan
spec:
  # gateways:
  # - istio-ingressgateway.istio-system.svc.cluster.local
  hosts:
  - ktest.xxx.com
  http:
  - match:
    - uri:
        prefix: "/atlas/*"
    rewrite:
      authority: k-atlas-service.vulcan.xxx.com
    route:
      - destination:
          host: istio-ingressgateway.istio-system.svc.cluster.local
        weight: 100
Mikołaj Głodziak
  • 4,775
  • 7
  • 28
  • Hi, which endpoint gives you this error? What is your expected situation? Where is your application? Which version of Kubernetes and Istio did you use? – Mikołaj Głodziak Jul 09 '21 at 10:59

1 Answers1

0

Have you tried the Domain Mapping API? That API is designed to make this task easier and more consistent across the different Knative networking implementations.

If that API isn't available, these instructions for Istio might provide a working example. I suspect that you may need to either target the Knative-internal VirtualService or the internal url for the Knative Service in the VirtualService you posted above.

E. Anderson
  • 3,405
  • 1
  • 16
  • 19