emissary-ingress/emissary

mapping: invalid add_response_headers causes pod crash

Open

#4,760 opened on Dec 14, 2022

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Python (679 forks)batch import
contrib-festgood first issuestalet:feature

Repository metrics

Stars
 (4,096 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I have been running Ambassador version 3.3.0 for more than a month without issue. Today, I tried to restart the edge-stack deployment after updating our SSL certificate, as I wasn't getting the new cert when making an HTTP request.

The pods would start, crash, and repeat, without ever going into a healthy state. I decided to upgrade to 3.3.1 to see if that would fix it. Still, the pods start, crash, and repeat. It appears that the pod cannot download the file "github.com/datawire/apro/v3/cmd/amb-sidecar/devportal/server/http.go:75". Not sure if this is the root issue though. I have attached a log of one of the pods trying to start up. ambass.txt

Contributor guide

Research direction
Analyze the crash logs and the configuration of add response headers in mappings to identify the root cause of the pod crash.
Tech stack
gopython
Domain
apiinfrastructuredevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesEnvoyGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30