Skip to content

feature: Go backend - #1329

Draft
ralgozino wants to merge 133 commits into
mainfrom
feature/go-backend
Draft

feature: Go backend#1329
ralgozino wants to merge 133 commits into
mainfrom
feature/go-backend

Conversation

@ralgozino

Copy link
Copy Markdown
Member

Summary 💡

WIP

This PR tracks the progress for moving to the new Go-based backend that will become v2.x unblocking some issues and adding new features.

Closes:

Description 📝

Breaking Changes 💔

Tests performed 🧪

Future work 🔧

ralgozino added 30 commits April 6, 2023 19:16
- first MVP of the backend in Go instead of Python
- clean up unneeded files
- clean up old files
- updated Dockerfile
fix #631 Frontend does not show the full error description
remove addTrailingSlash middleware and add manually the needed routes, because it was breaking the prometheus middleware.
get rid of the second kubeConfig used to detect context and simplify
client configuration generation using the same approach than kubectl.
@ralgozino ralgozino self-assigned this Jul 8, 2025
@ralgozino ralgozino added the enhancement New feature or request label Jul 8, 2025
ralgozino added 22 commits July 10, 2025 15:05
Note we need to update the baseline too
GPM does not need HPAs, removing them from the Helm Chart
Add GPM_SKIP_TLS_VERIFY paramater to support old EKS control planes with
the go backend like we do for the python one.
port support for having GPM exposed in a subpath, requires building a
custom docker image
Liveness and readiness probes are now configurable via values,
defaulting to the previous hardcoded behaviour. config.secretRef allows
pointing at an existing secret instead of setting config.secretKey in
plain text.

secret.yaml no longer uses `required` on config.secretKey, so the chart
installs with no values at all. Previously it failed unless you supplied
a secret that the Go backend does not read.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant