Printer FriendlyEmail Article Link

VW Virtual Controller: Why are API requests to conductor failing with "405 error Something went wrong – Page not found" error?

Environment/Versions
VW Virtual Controller - All versions
Answer
Verify the ingress is setup for the conductor pod. 
To check issue:  kubectl get ingress conductor -n namespace
Where namespace is the namespace being used.
Example:
$ kubectl get ingress conductor -n vsa
NAME        CLASS    HOSTS   ADDRESS        PORTS   AGE
conductor   <none>   *       10.32.90.108   80      9d

Here are steps to enable the ingress if it is not currently enabled.
  1. helm get values vsa -n namespace >values.yaml
    Where "vsa" is the release name where conductor exists and "namespace" is the namespace where conductor exists.
  2. vi values.yaml
    Verify conductor.ingress.enabled is set to true.
      ingress:
        annotations:
          konghq.com/strip-path: "true"
          kubernetes.io/ingress.class: kong
          nginx.ingress.kubernetes.io/rewrite-target: /$2
          traefik.ingress.kubernetes.io/rule-type: PathPrefixStrip
        enabled: true

    Save changes.
  3. Upgrade the helm chart to install change.
    helm upgrade -f values.yaml vsa -n namespace spirent/vsa
    where "vsa" is the release name where conductor exists and "namespace" is the namespace where conductor exists.
  4. Done.
     
Example of error is in attached document.
 
Attachments
Attachment Description
Example of error

Product : VW Controller Virtual