Skip to content
This repository has been archived by the owner on Jul 16, 2021. It is now read-only.

ingress controller problem with OPENSHIFT: monocular could not work #666

Open
ntnchrrn07 opened this issue Apr 17, 2020 · 1 comment
Open

Comments

@ntnchrrn07
Copy link

ntnchrrn07 commented Apr 17, 2020

Hello all,
On openshift platform, monocular is not working. We could not so use Monocular on it.
We think this problem is caused by a dependency too much important with nginx-ingress.

We think to have find the problem in monocular, it could be interesting to investigate :

  • frontend send requests on "/chartsvc/v1/*"
  • backend wait receive requests on "/v1/*"

Prefix of the back is only "/v1" where I think it must be "/chartsvc/v1" to don't create an dependency with nginx-ingress

Source code frontend: frontend/src/app/shared/services/charts.service.ts
l23: this.hostname = ${config.backendHostname}/chartsvc;
Source code backend: cmd/chartsvc/main.go
l31: const pathPrefix = "/v1"

Potential fix:
Source code backend: cmd/chartsvc/main.go
l31: const pathPrefix = "/chartsvc/v1"

Is someone have find an issue / workaround about it ?
Are you agree with this approach ?

Best regards,

@mahmoud-mahdi
Copy link

I have the same issue in Openshift and it is not working. Is there any update regarding this case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants