| From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
|---|---|
| To: | SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com> |
| Cc: | "pgsql-advocacy(at)lists(dot)postgresql(dot)org" <pgsql-advocacy(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL on K8 with Operator |
| Date: | 2020-12-08 22:54:07 |
| Message-ID: | CANNMO++YPue70i32=rqCSh2V5W-Y4rLx0GToCZq1xCVTYSVtPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
There is a 2-part article that compares operators from Zalando, Crunchy,
KubeDB and StackGres.io (unfortunately only in Russian, but Google
Translate and its alternatives do job well nowadays)
https://habr.com/en/company/flant/blog/527524/
All of them are being developed very actively, so I recommend defining your
own goals and making your own tests (plus, maybe talking to developers on
your own needs to see where a good match exists).
On Mon, Dec 7, 2020 at 19:54 SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com>
wrote:
> Hi All
>
> Greetings.
>
> I am looking for advise of running Postgres in K8 along with Operator.
> Which Operator will be best for this solution? Is any company running the
> similar setup in Production?
>
> Regards,
> Sasi
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SASIKUMAR Devaraj | 2020-12-09 07:11:46 | Re: PostgreSQL on K8 with Operator |
| Previous Message | Katherine Mcmillan | 2020-12-08 21:38:03 | Re: PostgreSQL on K8 with Operator |