NoProxy in some self host environments

Abierto
#405 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
helm, kubernetes
Área
devops, documentation, infrastructure

Línea de trabajo

El issue identifica los pods gitserver-0 y repo-updater y los valores NO_PROXY requeridos localhost, sourcegraph-frontend-internal y gitserver-0.gitserver. Encuentra la entrada relevante de la documentación de Helm para la configuración del proxy de los pods, documenta estos ajustes y el contexto del fallo, y verifica que las indicaciones cubran ambos pods.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

I've recently deployed SourceGraph with the Code Host GitHub. The environment where it was delpoyed uses injected proxies for the internal applications to reach the internet; this includes http, https and no_proxy. I had quite some issues for a while, having to track the traffic to see what went wrong.

Specifically, there was a problem in the repo-updater pod that caused other pods to fail as well; the error message found in the logs being: [...] error="invalid character '<' looking for beginning of value". Furthermore, the gitserver-0 pod failed once the repo-updater had been fixed.

Solution:
The problem in my case was that the proxy was routing internal traffic using the cluster internal DNS to the internet, which of course returned errors. In this specific case, an error page that returned HTML content, which caused the go code to fail.
When setting proxies for the pods, the gitserver-0 and repo-updater pods require a no_proxy/NO_PROXY envvar with the following values: localhost,sourcegraph-frontend-internal,gitserver-0.gitserver. This is assuming that your http/https proxies forward all other traffic elsewhere.

Given that this has caused quite a headache while fixing,this might be worth adding somewhere in your documentation, hopefully helping out other PoCs.

not sure if it's a similar issue, but at least the error message and the use of a proxy was identical in https://github.com/sourcegraph/sourcegraph/issues/2360

Lenguaje dominante
Go Template
Estrellas
19
Forks
24
Merge medio
1 d 4 h
PR fusionados (30 d)
13

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de sourcegraph/deploy-sourcegraph-helm

Todos los issues de sourcegraph/deploy-sourcegraph-helm

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.