loadBalancerSourceRanges does not work on GKE

[gedimin45]

Hello!

I am running a cluster on GKE (k8s version 1.3.3) and have the following service definition:

apiVersion: v1
kind: Service
metadata:
  name: frontend
  labels:
    app: api
    tier: frontend
spec:
  type: LoadBalancer
  loadBalancerIP: <a static IP>
  loadBalancerSourceRanges:
  - 10.0.0.0/8
  ports:
  - name: https
    port: 443
  - name: http
    port: 80
  selector:
    app: api
    tier: frontend

When I apply this configuration, the source IP range in the created firewall rule is still 0.0.0.0/0. Am I missing something? The loadBalancerIP seems to be applied correctly every time.

[freehan]

I just tried it on GKE. It works for me. Here is how I do it:

1. Create a regional static IP.
2. Create loadbalancer service with the ip and loadBalancerSourceRanges

Anything I missed?

[freehan]

For the firewall rule of 0.0.0.0/0, is it formatted like k8s-fw-${Name of the Loadbalancer}?

[gedimin45]

@freehan the IP is set correctly, it's the source IP range that is being ignored.
I have been told on Slack, that this feature still does not work on GKE. Is that true? If so, is there a plan to enable it? :)

[freehan]

@Ged15 The source IP ranges works as expected on my GKE cluster.

I wonder if this is related to GKE upgrades, because my cluster is a brand new one.

[freehan]

Can you confirm the following?
For the 0.0.0.0/0 rule, does its name look like k8s-fw-${Name of the Loadbalancer}? Does ${Name of the Loadbalancer} matches the service loadbalancer name?

[freehan]

Okay. I think I understand the problem now. Will apply a fix soon.