1. 07 May, 2018 3 commits
    • Kubernetes Submit Queue's avatar
      Merge pull request #62712 from Lion-Wei/ipvs-fw · 90e8ea9d
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
      
      fix ipvs firewall rules for loadbalancer type service
      
      **What this PR does / why we need it**:
      fix ipvs firewall rules for loadbalancer type service.
      
      **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
      Fixes #62638
      
      **Special notes for your reviewer**:
      The original firewall rules for loadblancer type service with sourceRange may looks like:
      ```
      Chain KUBE-FIRE-WALL (1 references)
      target     prot opt source               destination
      ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            match-set KUBE-LB-INGRESS-LOCAL dst,dst
      KUBE-MARK-MASQ  all  --  0.0.0.0/0            0.0.0.0/0            /* mark MASQ for external traffic policy not local */
      ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            match-set KUBE-LOAD-BALANCER-SOURCE-CIDR dst,dst,src
      KUBE-MARK-DROP  all  --  0.0.0.0/0            0.0.0.0/0
      
      Chain KUBE-SERVICES (2 references)
      target     prot opt source               destination
      KUBE-MARK-MASQ  all  -- !10.64.0.0/14         0.0.0.0/0            match-set KUBE-CLUSTER-IP dst,dst
      KUBE-FIRE-WALL  all  --  0.0.0.0/0            0.0.0.0/0            match-set KUBE-LOAD-BALANCER dst,dst
      KUBE-NODE-PORT  tcp  --  0.0.0.0/0            0.0.0.0/0            tcp match-set KUBE-NODE-PORT-TCP dst
      ```
      Which may result in other loadbalancer type service can't be access.
      
      In this pr, rules of loadbalancer type service with sourceRange specified will be:
      ```
      Chain KUBE-FIRE-WALL (1 references)
      target     prot opt source               destination
      RETURN     all  --  0.0.0.0/0            0.0.0.0/0            match-set KUBE-LOAD-BALANCER-SOURCE-CIDR dst,dst,src
      KUBE-MARK-DROP  all  --  0.0.0.0/0            0.0.0.0/0
      
      Chain KUBE-LOAD-BALANCER (1 references)
      target     prot opt source               destination
      KUBE-FIRE-WALL  all  --  0.0.0.0/0            0.0.0.0/0            match-set KUBE-LB-INGRESS dst,dst
      KUBE-MARK-MASQ  all  --  0.0.0.0/0            0.0.0.0/0            /* mark MASQ for external traffic policy not local */
      
      
      Chain KUBE-SERVICES (2 references)
      target     prot opt source               destination
      KUBE-MARK-MASQ  all  -- !10.64.0.0/14         0.0.0.0/0            match-set KUBE-CLUSTER-IP dst,dst
      KUBE-LOAD-BALANCER  all  --  0.0.0.0/0            0.0.0.0/0            match-set KUBE-LOAD-BALANCER dst,dst
      ```
      
      **Release note**:
      ```release-note
      NONE
      ```
      90e8ea9d
    • Lion-Wei's avatar
      fix ipvs fw · e90de22a
      Lion-Wei authored
      e90de22a
    • Kubernetes Submit Queue's avatar
      Merge pull request #61970 from sak0/dev-endpoints · 28a19562
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
      
      controller/endpoint: explict log msg when syncing error
      
      explict log msg for retrying sync
      Signed-off-by: 's avatarCuiHaozhi <cuihaozhi@chinacloud.com.cn>
      
      
      
      **What this PR does / why we need it**:
      
      **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
      Fixes #
      
      **Special notes for your reviewer**:
      
      **Release note**:
      
      ```release-note
      NONE
      ```
      28a19562
  2. 05 May, 2018 4 commits
  3. 04 May, 2018 26 commits
  4. 03 May, 2018 7 commits