mtaufen

diff --git a/passing_sorted.yaml b/failing_sorted.yaml
index 457769a..b7787f7 100644
--- a/passing_sorted.yaml
+++ b/failing_sorted.yaml
@@ -2,72 +2,37 @@
   agent: kubernetes
   annotations:
     - args:
-    - author: lauchokyip
-      author_link: https://github.com/lauchokyip

mtaufen

diff --git a/passing.yaml b/failing.yaml
index 3fcc3ca..a50de2c 100644
--- a/passing.yaml
+++ b/failing.yaml
@@ -1,75 +1,51 @@
 metadata:
   annotations:
-    fork-per-release: "true"
-    prow.k8s.io/context: pull-kubernetes-e2e-gce-ubuntu-containerd
-    prow.k8s.io/job: pull-kubernetes-e2e-gce-ubuntu-containerd

mtaufen

Verifying verify-shellcheck.sh

+++ Running case: verify.shellcheck
+++ working dir: /home/prow/go/src/k8s.io/kubernetes
+++ command: bash "hack/make-rules/../../hack/verify-shellcheck.sh"
Using shellcheck 0.6.0 docker image.
Errors from shellcheck:

In ./cluster/gce/win1803/node-helper.sh line 49:
  create-node-template "${template_name}" "${scope_flags[*]}" "$(get-windows-node-instance-metadata-from-file)" "$(get-windows-node-instance-metadata)" "windows"

mtaufen

Verifying my Blockstack ID is secured with the address 1PnLvwikUDrbnqDMvE7TEAYd7QF5vWuLwf https://explorer.blockstack.org/address/1PnLvwikUDrbnqDMvE7TEAYd7QF5vWuLwf

mtaufen

I'd like to propose moving mtaufen/non-masquerade-daemon under the kubernetes-incubator/ org. As this is a network configuration daemon, I believe this effort belongs under sig-network.

The OWNERS file in the above repo should serve as the OWNERS file for this proposal. The README in the above repo provides more details, but I'll summarize here:

This daemon solves the problem of configuring the CIDR ranges for non-masquerade in a cluster (via iptables rules). Today, this is accomplished by passing a --non-masquerade-cidr flag to the Kubelet, which only allows one CIDR to be configured as non-masquerade. RFC 1918, however, defines three ranges (10/8, 172.16/12, 192.168/16) for the private IP address space.

Some users will want to communicate between these ranges without masquerade - for instance, if an organization's existing network uses the 10/8 range, they may wish to run their cluster and Pods in `192.