Skip to content

Commit 634a5c5

Browse files
committed
fix(seaweedfs): restore s3 Service name to chart-prefix form
The seaweedfs 4.31 upstream bump (#2834) switched the s3 Service name from "$chartname-s3" (built with the seaweedfs.name helper, evaluates to "seaweedfs-s3") to the seaweedfs.componentName helper, which is release-name based and now evaluates to "$release-s3" — "seaweedfs- system-s3" for the tenant-root deployment. The bats E2E asset hack/e2e-apps/bucket.bats hard-codes "service/seaweedfs-s3" for the port-forward that sets up its S3 client; backup-controller and other in-cluster consumers also referenced the legacy name. After the bump, the legacy Service is gone and the port-forward immediately exits, the test then times out on the 30-second nc poll for localhost:8333. Restore the legacy Service name. Internal references inside the chart (s3-deployment -filer=, etc) keep using componentName for the filer endpoint, so this change only re-exposes the public-facing name without touching the internal topology. Signed-off-by: Ivan Okhotnikov <[email protected]>
1 parent 700149e commit 634a5c5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎packages/system/seaweedfs/charts/seaweedfs/templates/s3/s3-service.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
apiVersion: v1
33
kind: Service
44
metadata:
5-
name: {{ include "seaweedfs.componentName" (list . "s3") }}
5+
name: {{ template "seaweedfs.name" . }}-s3
66
namespace: {{ .Release.Namespace }}
77
labels:
88
app.kubernetes.io/name: {{ template "seaweedfs.name" . }}

0 commit comments

Comments
 (0)