[PPGC] Adding loadBalancerIP into proxy.pgBouncer.expose specs

PostgreSQL Percona Operator for PostgreSQL
,
1

Description:

Hi,

I have been trying to manage the LoadBalancerIPs of my PPGC Clusters.

I am using Octavia as the LoadBalancer Controller with Openstack.

In order to control the IP of the PPGC Cluster LoadBalancer Service, I would like to force the IP directly in the CR PerconaPGCluster.

Octavia does not allow to force this IP through labels or annonations on the k8s LoadBalancer Service.

Is it possible to add this spec into the PerconaPGCluster CR under proxy.pgBouncer.expose.loadBalancerIP (this is possible within PXC PerconaXtraDBCluster CRD) so that the ppgc operator creates the k8s LoadBalancer Service with the spec.loadBalancerIP that matches with the on in the CR PerconaPGCluster ?

Thank you for the help

Steps to Reproduce:

  • Creating a Percona PG Cluster with PGBouncer enabled and a LoadBalancer Type k8s Service
  • spec.proxy.pgBouncer.expose does not have a “loadBalancerIP” spec to force the IP address of the LoadBalancer k8s Service
  • Adding this spec directly into the CR PerconaPGCluster to force the Service IP

Version:

Percona PG Operator 2.8.2

Logs:

No relevant logs

Expected Result:

Adding the spec “LoadBalancerIP” to force the IP of the k8s LoadBalancer Service (with Octavia)

Actual Result:

Service does not get an IP because the Openstack Tenant does not have enough quota to add automatically provisioned IPs

2

Hi @b.balmon, We had this option in the PG operator, but it was removed because k8s deprecated it. Please check the official documentation: Service | Kubernetes, and also, we are going to remove it from PXCO in v1.21.0 as well. Please vote for this fix [occm] Provide alternative way to define floatingIP instead of `spec.loadBalancerIP` · Issue #3086 · kubernetes/cloud-provider-openstack · GitHub to be able to set it via annotation for Openstack.