Create PG Cluster via user interface not yaml

PostgreSQL Percona Operator for PostgreSQL
1

Description:

Could someone please help with creation of PGCluster via Operator in RedHat Openshift via user interface not the yaml itself? Is there any guide how to achive so?

When I do so it never creates a POD. Also, there is no ability to adjust for instance resource/limits etc. So is it even possible to setup via the interface only?

Version:

2.7.0

Many thanks!

2

@kase007

Let me point to a manual:- Install on OpenShift - Percona Operator for PostgreSQL which guides setting up PGCluster on Openshift via the OLM/UI interface . Did you check this already ?

Similarly from command line operation also you can installed on the Openshift environment:- Install on OpenShift - Percona Operator for PostgreSQL

If the pods are failing, you can check the errors or try to get more information

oc get pods

oc  logs <POD_NAME>

oc describe pod <POD_NAME>

Can you try attaching the screenshot or errors for a better understanding ?

3

Hi Joshi,

Many thanks for reply.

Yes, I’ve already read it.

I do manage to deploy it via the operator but only by customizing the yaml.There is a plenty of options I need to configure that are not configurable via FORM for instance resources, limits etc. So my question was, is there a way to deploy it just by using the FORM of operator?

Also, I’ve another question. Is there a way to set up for instance paramter max_connections not forcing the POD to restart immediately as Openshif tend to do?

Thank you

4

Hi @kase007

In Openshift interface the options available in the FORM are based on the default values defined in the manifest.
You can check these here:
for operator: percona-postgresql-operator/deploy/operator.yaml at v2.7.0 · percona/percona-postgresql-operator · GitHub
for cluster: percona-postgresql-operator/deploy/cr.yaml at v2.7.0 · percona/percona-postgresql-operator · GitHub

Any options that are either commented out or missing from these manifests need to be explicitly configured in YAML.

So, to answer your question — yes, you should be able to deploy it using just the FORM, as it reflects the default values. If that’s not working, please let us know which options are causing issues, and we’ll help investigate further.

Thanks!