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

[Task]: deploy in k8s helm with postgresql db persistence #4735

Open
wfrankoti opened this issue Dec 20, 2024 · 3 comments
Open

[Task]: deploy in k8s helm with postgresql db persistence #4735

wfrankoti opened this issue Dec 20, 2024 · 3 comments

Comments

@wfrankoti
Copy link

What needs to happen?

Hello,
There is little information on the web portal and all the documentation with the persistence process in postgresql db. What is the process and step by step to install apache hop in k8s, using helm, and configure a db postgresql for persistence. To manage the restarts of the pods in k8s without losing data, flows, configurations, and others.
Tnks!

Issue Priority

Priority: 2

Issue Component

Component: Hop Config

@hansva
Copy link
Contributor

hansva commented Dec 20, 2024

Hop does not have a DB persistence layer, everything is done in files.

@wfrankoti
Copy link
Author

How is the practice to persist the archives? From hop-web to hop-server?
How is the practice for restarts of the hop-server or hop-web pods, so as not to lose the information?

@bamaer
Copy link
Contributor

bamaer commented Dec 21, 2024

For hop web, you'll have to mount your project and environment configuration files to volumes or clone from a git repository when the pod starts.

Hop server doesn't persist anything either. You'll have to add or register your workflows and pipelines before you can run them there.

Let's see if we can improve that part of the documentation over the winter holidays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants