Skip to content

fix(langfuse): name the MinIO container minio, not its alias - #133

Merged
tarannum-2002 merged 1 commit into
developmentfrom
fix/235-langfuse-minio-name
Nov 7, 2026
Merged

tarannum-2002 merged 1 commit into
developmentfrom
fix/235-langfuse-minio-name

Conversation

@tarannum-2002

Copy link
Copy Markdown
Contributor

What

Inside the langfuse chart, MinIO's container is now named minio, and its labels say minio instead of objectStorage. Chart 3.0.0 to 3.0.1.

Why

Under the alias objectStorage, Helm gives the subchart that name, and the MinIO template used it for the container. Container names must be lowercase, so Kubernetes refused the Deployment:

Deployment.apps "langfuse-minio" is invalid: spec.template.spec.containers[0].name: Invalid value: "objectStorage"

On dev, Langfuse is stuck OutOfSync and Missing because of it, and has no object storage.

Testing

  • Rendered the chart with dev's values: the MinIO Deployment's container is minio, its labels say minio, and no container in the chart has an invalid name.
  • scripts/lint-charts.sh langfuse: langfuse lints clean. The run also lints cert-manager, which fails the same way on development without this change.

Relates to OpenAgriNet/engineering-tracker#235

@tarannum-2002
tarannum-2002 merged commit 8dd9112 into development Nov 7, 2026
1 check passed
@tarannum-2002
tarannum-2002 deleted the fix/235-langfuse-minio-name branch November 7, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant