potiuk commented on issue #20424: URL: https://github.com/apache/airflow/issues/20424#issuecomment-1000155872
> Unfortunately, the issue actually isn't with Bitnami, as I can deploy their Postgresql easily with Helm, with the default settings, on the same K3s cluster. So this issue needs to reopened to better look into this. TCan you try on a different cluster that K3s ? Because if it is K3S. then I am afraid this at most can be turned into discussion. This is not a bug, really if it works with K3s - possibly this could be addressed to K3S then. > Also, out of curiosity, why do you want an external cluster for production? Postgres works nicely in K8s production environments: https://dok.community/blog/deploying-postgres-on-kubernetes/ The fact that you can do something does not mean you should. If you watched that presentation, you will likely see all the hoops that you have to go through as K8S adrministrator. They say about days of work to make the deployment robust. So this is not something simple bitnami chart will handle. > But I do see this request to use external database for production with a lot of products so I assume there's a good reason for it. > Why is that the case here? It's everywhere not here. K8S is simply not (yet) fully ready for "stateful" components. It was not designed to do it initially and a lot of changes in it were implemented to get closer to be able to support them. But it's simply not best tool to do it and you have to be an expert in K8S and expert in DB administration and expert in your own deployment to make it really robuts. You can. Sure. Should you ? Maybe, if your job is paid by hour, probably it's even a good idea for you. Is it good for the business that uses Airlfow ? Probably not. using a managed database service is likely going to be cheaper and more stable overall. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
