Skip to content
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

How to run Duckdb bundle with superset #2

Open
nagarajmmu opened this issue May 31, 2023 · 6 comments
Open

How to run Duckdb bundle with superset #2

nagarajmmu opened this issue May 31, 2023 · 6 comments

Comments

@nagarajmmu
Copy link

Hi

I am new to kubernetes, I have tried to deploy DuckDb bundle with superset, but is showing pods of superset, not Duckdb, I have used YAML that is specified in Github.

I have used below command to deploy.
helm upgrade --install --namespace duckdbexample1 --create-namespace --values duckdb_values_example.yaml superset superset/superset

Please let me know if I am missing something.

Thanks in advance

@abhishek-ch
Copy link
Owner

@nagarajmmu
Copy link
Author

Hi Abhishek

Thanks for the suggestion, I have tried deploying duck db bundle by below command.
kubectl apply -f deployment_duckdb_bundle.yaml -n dexa
Everything works fine, but not able to access superset outside.
services are showing external IP
image

but not able to access it from external IP, it is showing "Can't reach this page"

Thanks
Nagaraja M M

@abhishek-ch
Copy link
Owner

To do that, you need to create ingress in Kubernetes / DNS. Check that

@nagarajmmu
Copy link
Author

Thanks Abhishek I will check about ingress

@nagarajmmu
Copy link
Author

Hi Abhishek

I have tried Ingress also but is it not working, below is the Yaml file, that I have tried.

apiVersion: apps/v1
kind: Deployment
metadata:
name: duckdb-bundle
spec:
selector:
matchLabels:
app.kubernetes.io/name: app-duckdb-bundle
replicas: 1
template:
metadata:
labels:
app.kubernetes.io/name: app-duckdb-bundle
spec:
containers:
- image: buntha/duckdb-bundle:0.0.3
imagePullPolicy: Always
name: duckdb-bundle
ports:
- containerPort: 8088

apiVersion: v1
kind: Service
metadata:
name: duckdb-bundle
spec:
ports:
- port: 8088
targetPort: 8088
protocol: TCP
type: NodePort
selector:
app.kubernetes.io/name: app-duckdb-bundle

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: example-ingress
annotations:
ingress.kubernetes.io/rewrite-target: /
spec:
rules:
- http:
paths:
- path: /app
pathType: Prefix
backend:
service:
name: duckdb-bundle
port:
number: 8088

Note: YAML is not formatted in this text box

Still I am not able to access application outside,
Please let me now, if any changes needs to be made in yaml file.

Thanks
Nagaraja M M

@abhishek-ch
Copy link
Owner

Have you created loadbalancer in your kubernetes cluster? What the dns?
Make sure your ingress framework is ready and allow access outside cluster .

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

No branches or pull requests

2 participants