jx: Monocular UI does not display charts, it is waiting forever

Summary

This is the same situation relate with the issue #667 but for some reason is happening again

Steps to reproduce the behavior

screen shot 2019-01-18 at 10 53 11 am

Jx version

NAME               VERSION
jx                 1.3.761
jenkins x platform 0.0.3193
Kubernetes cluster v1.11.5-eks-6bad6d
kubectl            v1.13.2
helm client        v2.12.2+g7d2b0c7
helm server        v2.12.1+g02a47c7
git                git version 2.17.2 (Apple Git-113)
Operating System   Mac OS X 10.13.6 build 17G4015

Kubernetes cluster

EKS

Expected behavior

Actual behavior

I ran the command inside the container using

jx rsh jenkins-x-monocular-ui

And inside the container I ran

curl http://jenkins-x-monocular-api/v1/charts

{
  "data": [
    {
      "attributes": {
        "description": "A Helm chart for Kubernetes",
        "home": null,
        "maintainers": null,
        "name": "microservice01",
        "repo": {
          "URL": "http://jenkins-x-chartmuseum:8080",
          "name": "chartmuseum",
          "source": "https://github.com/jenkins-x/jenkins-x-platform"
        },
        "sources": null
      },
      "id": "chartmuseum/microservice01",
      "links": {
        "self": "/v1/charts/chartmuseum/microservice01"
      },
      "relationships": {
        "latestChartVersion": {
          "data": {
            "app_version": null,
            "created": "2019-01-18T00:23:40.186851802Z",
            "digest": "1420f2a95317f5dbbd27cb6e6d0630d8cd0e8e62bfecfdad509710b2d48f2a68",
            "icons": [
              {
                "name": "160x160-fit",
                "path": "/assets/chartmuseum/microservice01/0.0.4/logo-160x160-fit.png"
              }
            ],
            "readme": "/assets/chartmuseum/microservice01/0.0.4/README.md",
            "urls": [
              "charts/microservice01-0.0.4.tgz"
            ],
            "version": "0.0.4"
          },
          "links": {
            "self": "/v1/charts/chartmuseum/microservice01/versions/0.0.4"
          }
        }
      },
      "type": "chart"
    }
  ]
}

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 10
  • Comments: 21 (6 by maintainers)

Most upvoted comments

Check the version of nginx-ingress controller you’re using. They made a breaking change starting v0.22.x . You’ll need to explicitly state the capture group in your ingress rule.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    fabric8.io/generated-by: exposecontroller
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /$1
  name: monocular
  namespace: jx
spec:
  rules:
  - host: monocular.jx.blah.com
    http:
      paths:
      - backend:
          serviceName: jenkins-x-monocular-api
          servicePort: 80
        path: /api/?(.*)
      - backend:
          serviceName: jenkins-x-monocular-ui
          servicePort: 80
        path: /?(.*)

https://kubernetes.github.io/ingress-nginx/examples/rewrite/#rewrite-target

Same problem after jx upgrade platform, same fix. Thanks! @mdiez19

I apologize for the possibly obvious question, but where do I edit the aforementioned file?

kubectl edit ingress monocular

Yup! That’s the trick.

Same problem using EKS.

NAME               VERSION
jx                 1.3.1011
jenkins x platform 0.0.3629
Kubernetes cluster v1.11.8-eks-7c34c0
kubectl            v1.11.8
helm client        v2.12.2+g7d2b0c7
helm server        v2.12.2+g7d2b0c7
git                git version 2.21.0.windows.1
Operating System   Windows 10 Pro 1809 build 17763

I am running into this problem as well. As far as I can tell, the /api/ backend is not being properly exposed via Ingress because I’m getting the default nginx-ingress-controller 404 message when I hit any /api/ routes. I have updated the Ingress record per the suggestions above.