Skip to content

fix(stack/trino-superset-s3): Use FQDN for minio, restrict to default namespace #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion stacks/stacks-v2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -305,7 +305,7 @@ stacks:
- plainYaml: https://raw.githubusercontent.com/stackabletech/demos/main/stacks/trino-superset-s3/hive-metastore.yaml
- plainYaml: https://raw.githubusercontent.com/stackabletech/demos/main/stacks/trino-superset-s3/trino.yaml
- plainYaml: https://raw.githubusercontent.com/stackabletech/demos/main/stacks/trino-superset-s3/superset.yaml
supportedNamespaces: []
supportedNamespaces: [default] # until namespace can be templates, the minio FQDN hard-codes the namespace
resourceRequests:
cpu: 6800m
memory: 15822Mi
Expand Down
2 changes: 1 addition & 1 deletion stacks/trino-superset-s3/s3-connection.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ kind: S3Connection
metadata:
name: minio
spec:
host: minio
host: minio.default.svc.cluster.local
port: 9000
accessStyle: Path
credentials:
Expand Down