-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get nothing but 502's when deployed on k8s cluster #2387
Comments
Hi @scphantm! Could you please share us your Kubernetes deployment configuration file so we can easily reproduce your problem. |
Here is the service
and the route
|
im running this on openshift, so i have routes instead of ingress. |
I am newby in the Kubernetes word and I am not familiar with openshift but I tried to debug your problem. First I started a local Kubernetes cluster by using minikube, and I have created the following deployments and service: deployment.yaml: apiVersion: apps/v1
kind: Deployment
metadata:
name: codechecker-deployment
labels:
name: codechecker
spec:
replicas: 2
selector:
matchLabels:
name: codechecker
template:
metadata:
labels:
name: codechecker
spec:
containers:
- args:
image: 'codechecker/codechecker-web:6.10.0'
name: codechecker-web
ports:
- containerPort: 8001
protocol: TCP
volumeMounts:
- mountPath: /workspace
name: workspace
volumes:
- name: workspace
hostPath:
path: /home/username/workspace/k8s
type: Directory service.yaml: apiVersion: v1
kind: Service
metadata:
name: codechecker-service
spec:
ports:
- port: 8001
targetPort: 8001
selector:
name: codechecker
type: LoadBalancer To make the service accessible through minikube I run the following command: When I opened the link in a browser given by the command above I didn't get any errors. I tried it by turning authentication on and off and it works in both cases. Maybe the problem will be that you are using routes. |
yea, problem is i cant use ingress (not putting in an ingress server). I have found instances of the http.server having problems behind proxy servers, which is exactly what routes are. ps, difference between routes and ingress, ingress is more or less an ngnix server running url rewrites. Routes are (in my case) an ha proxy service acting as a router based on hostname and ports. OpenShift does have the ability to run ingress, but i would have to deploy an ngnix server, which isn't going to happen any time soon. RedHat made this change to k8s because its easier to do direct integration with enterprise load balancers (like F5's and such) when it does its routing by proxy. short of editing code, i have gone as far as i can. If i get some time i will attempt to create a dev env and see if i can get it to do anything. You may want to test with https://github.com/minishift/minishift most popular enterprise k8s server, by a massive margin. may wanna make sure your stuff works on it. |
Describe the bug
I deployed the docker container on a k8s cluster. when authentication is turned off, i get 502 errors when i navigate to the products.html or the login.html page.
When i turn authentication on, (doesn't matter dictionary or ldap), then i get nothing but 502 errors on every page, including the login.html page.
CodeChecker version
6.10
here is the end of my log file.
The text was updated successfully, but these errors were encountered: