How to get into the cluster and make a request to the app live view service and port that the HTTPProxy is configured to use
search cancel

How to get into the cluster and make a request to the app live view service and port that the HTTPProxy is configured to use

book

Article ID: 397997

calendar_today

Updated On:

Products

VMware Tanzu Application Platform

Issue/Introduction

The tls section is added like the below:

tls:
  secretName: tap-default-tls
  namespace: tanzu-system-ingresss


The Contour overlay is also used:

package_overlays:
- name: contour
  secrets:
  - name: contour-loadbalancer-nsg


- Even when configuring `appliveview_connector.backend.caCertData` in the run cluster with the TLS secret (`tanzu-system-ingress/tap-default-tls`), the backend connection still fails with a 503.

Resolution

As for checking, you could do the following:

  • Find the HTTPProxy resource that provides the route for live-view. It might be called app-live-view in the appliveview namespace. It seems like it provides the URL appliveview.internal.view.****.jp
    kubectl get httpproxy -A
  • Find the service name and port in spec.routes[].services[]. Based on app-live-view HTTPProxy output via the below command, it would be like application-live-view-7000.appliveview.svc.cluster.local:7000
    kubectl get httpproxy -A -oyaml > httpproxy.yaml 
  • Run a pod in the cluster and try to reach the app live view service. Using netshoot for this purpose: 
    kubectl -n appliveview run tmp-shell --rm -i --tty --image nicolaka/netshoot
  • From inside the netshoot tmp-shell container: curl application-live-view-7000.appliveview.svc.cluster.local:7000 and see what happens.