[BUG] Can’t set the value of externalTrafficPolicy to Cluster in the Service.

[shuoshadow]

Kubernetes: v1.28.9
KubeBlocks: 0.9.0
kbcli: 0.9.1-beta.13
WARNING: version difference between kbcli (0.9.1-beta.13) and kubeblocks (0.9.0) 

When I create a Service of type LoadBalancer, the value of externalTrafficPolicy is set to Local by default and cannot be changed to Cluster.

apiVersion: apps.kubeblocks.io/v1alpha1
kind: OpsRequest
metadata:
  name: camellia-expose-enable
  namespace: kb-cloud
spec:
  # Specifies the name of the Cluster resource that this operation is targeting.
  clusterName: camellia-cluster
  # Lists Expose objects, each specifying a Component and its services to be exposed.
  expose:
    # Specifies the name of the Component.
  - componentName: proxy
    # Specifies a list of OpsService. When an OpsService is exposed, a corresponding ClusterService will be added to `cluster.spec.services`. 
    services:
    - name: internet
      roleSelector: ""
      serviceType: LoadBalancer
    # Indicates whether the services will be exposed. 'Enable' exposes the services. while 'Disable' removes the exposed Service.
    switch: Enable
  # Specifies the maximum number of seconds the OpsRequest will wait for its start conditions to be met before aborting. If set to 0 (default), the start conditions must be met immediately for the OpsRequest to proceed.
  preConditionDeadlineSeconds: 0
  type: Expose

In my Kubernetes cluster, I’m using the Cilium CNI component and assigning EXTERNAL-IP to LoadBalancer type services through the CiliumBGPPeeringPolicy.
When the Service has externalTrafficPolicy: Cluster, BGP Control Plane unconditionally advertises the ingress IPs of the selected Service. When the Service has externalTrafficPolicy: Local, BGP Control Plane keeps track of the endpoints for the service on the local node and stops advertisement when there’s no local endpoint.

https://docs.cilium.io/en/stable/network/bgp-control-plane/bgp-control-plane-v1/#externaltrafficpolicy

So I need to set the externalTrafficPolicy for the Service to Cluster.

[shanshanying]

Hi @shuoshadow
I'd suggest updating the services api of 'cluster.spec.services'. This api is designed to allow users to define a list of "additional" Services to be exposed by a Cluster.

[shanshanying]

the serviceType LoadBalancer is used on Cloud , such as EKS from AWS, GKE from Google Cloud, TKE from Tencent Cloud, and AKS from Aliyun.

Instead of posing an OpsRequest, you can manipulate the services api w.r.t. your own needs, for instance:

apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
  name: camellia-cluster
  namespace: default
spec:
  terminationPolicy: Delete
  services:  # patch Cluster CR with your services
  - componentSelector: proxy
    name: proxy-internet
    serviceName: proxy-internet
    annotations:  # customized annotations if necessary
      yourkey: yourvalue
    spec: # this is `corev1.ServiceSpec`
      ports:
      - name: redis-proxy
        nodePort: 30449
        port: 6380
        protocol: TCP
        targetPort: redis-proxy
      - name: console-port
        nodePort: 31347
        port: 16379
        protocol: TCP
        targetPort: console-port
      type: LoadBalancer
      externalTrafficPolicy: Cluster  # specify the externalTrafficPolicy attribute here
  componentSpecs:
  - name: proxy
    componentDef: camellia-redis-proxy
    ...

[shuoshadow]

the serviceType LoadBalancer is used on Cloud , such as EKS from AWS, GKE from Google Cloud, TKE from Tencent Cloud, and AKS from Aliyun.

Instead of posing an OpsRequest, you can manipulate the services api w.r.t. your own needs, for instance:

apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
  name: camellia-cluster
  namespace: default
spec:
  terminationPolicy: Delete
  services:  # patch Cluster CR with your services
  - componentSelector: proxy
    name: proxy-internet
    serviceName: proxy-internet
    annotations:  # customized annotations if necessary
      yourkey: yourvalue
    spec: # this is `corev1.ServiceSpec`
      ports:
      - name: redis-proxy
        nodePort: 30449
        port: 6380
        protocol: TCP
        targetPort: redis-proxy
      - name: console-port
        nodePort: 31347
        port: 16379
        protocol: TCP
        targetPort: console-port
      type: LoadBalancer
      externalTrafficPolicy: Cluster  # specify the externalTrafficPolicy attribute here
  componentSpecs:
  - name: proxy
    componentDef: camellia-redis-proxy
    ...

@shanshanying Thanks, I successfully implemented the modification of the externalTrafficPolicy in the service using this method.