-
Notifications
You must be signed in to change notification settings - Fork 0
/
data.example.csv
We can make this file beautiful and searchable if this error is corrected: Illegal quoting in line 1.
11 lines (11 loc) · 6.55 KB
/
data.example.csv
1
2
3
4
5
6
7
8
9
10
11
https://api.github.com/repos/kubernetes/kubernetes/issues/65389,335020016,Add /home/kubernetes/bin into sudoers path so that `sudo crictl` works.,Add `/home/kubernetes/bin` to sudoers path so that user can call `sudo crictl` directly. Without this fix user has to either use the full path `sudo /home/kubernetes/bin/crictl` or switch to root which is not a good user experience. /cc @yujuhong @feiskyer @filbranden @kubernetes/sig-node-pr-reviews @kubernetes/sig-gcp-pr-reviews **Release note**: <!-- Write your release note: 1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release include the string "action required". 2. If no release note is required just write "NONE". --> ```release-note User can now use `sudo crictl` on GCE cluster. ``` ,bug
https://api.github.com/repos/kubernetes/kubernetes/issues/65388,335019459,Always create kubeClusterIPSet in ipvs proxier,**What this PR does / why we need it**: This PR creates the kubeClusterIPSet ipset even if kube-proxy is started without masqueradeAll and clusterCIDR. This is necessary to masquerade traffic sent to a clusterIP from the host network namespace. The code to do so is actually already present here: https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/ipvs/proxier.go#L1220-L1244 However the second else (neither masqueradeAll nor clusterCIDR are set) cannot be used because before this PR the initial test `if !proxier.ipsetList[kubeClusterIPSet].isEmpty()` can never return true when masqueradeAll and clusterCIDR are not set because kubeClusterIPSet is empty. **Which issue(s) this PR fixes** Fixes #65158 ```release-note Allow access to ClusterIP from the host network namespace when kube-proxy is started in IPVS mode without either masqueradeAll or clusterCIDR flags ``` **Additional comment** Issue #65158 is closed because ClusterIP access from the host has already fixed in master except for the case described here (no masquerade flag). More detail in the issue.,bug
https://api.github.com/repos/kubernetes/kubernetes/issues/65377,334935368,restore pre-1.11 behavior of `kubectl get --template=...`,**Release note**: ```release-note NONE ``` Restores old behavior to the `--template` flag in `get.go`. In old releases providing a `--template` flag value and no `--output` value implicitly assigned a default value ("go-template") to `--output` printing using the provided template argument. Example: ```bash # this should print using GoTemplate printer but currently does not $ kubectl get pod foo --template="{{ .metadata.name }}" ``` cc @deads2k @soltysh ,bug
https://api.github.com/repos/kubernetes/kubernetes/issues/65389,335020016,Add /home/kubernetes/bin into sudoers path so that `sudo crictl` works.,Add `/home/kubernetes/bin` to sudoers path so that user can call `sudo crictl` directly. Without this fix user has to either use the full path `sudo /home/kubernetes/bin/crictl` or switch to root which is not a good user experience. /cc @yujuhong @feiskyer @filbranden @kubernetes/sig-node-pr-reviews @kubernetes/sig-gcp-pr-reviews **Release note**: <!-- Write your release note: 1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release include the string "action required". 2. If no release note is required just write "NONE". --> ```release-note User can now use `sudo crictl` on GCE cluster. ``` ,doc
https://api.github.com/repos/kubernetes/kubernetes/issues/65388,335019459,Always create kubeClusterIPSet in ipvs proxier,**What this PR does / why we need it**: This PR creates the kubeClusterIPSet ipset even if kube-proxy is started without masqueradeAll and clusterCIDR. This is necessary to masquerade traffic sent to a clusterIP from the host network namespace. The code to do so is actually already present here: https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/ipvs/proxier.go#L1220-L1244 However the second else (neither masqueradeAll nor clusterCIDR are set) cannot be used because before this PR the initial test `if !proxier.ipsetList[kubeClusterIPSet].isEmpty()` can never return true when masqueradeAll and clusterCIDR are not set because kubeClusterIPSet is empty. **Which issue(s) this PR fixes** Fixes #65158 ```release-note Allow access to ClusterIP from the host network namespace when kube-proxy is started in IPVS mode without either masqueradeAll or clusterCIDR flags ``` **Additional comment** Issue #65158 is closed because ClusterIP access from the host has already fixed in master except for the case described here (no masquerade flag). More detail in the issue.,doc
https://api.github.com/repos/kubernetes/kubernetes/issues/65377,334935368,restore pre-1.11 behavior of `kubectl get --template=...`,**Release note**: ```release-note NONE ``` Restores old behavior to the `--template` flag in `get.go`. In old releases providing a `--template` flag value and no `--output` value implicitly assigned a default value ("go-template") to `--output` printing using the provided template argument. Example: ```bash # this should print using GoTemplate printer but currently does not $ kubectl get pod foo --template="{{ .metadata.name }}" ``` cc @deads2k @soltysh ,bug
https://api.github.com/repos/kubernetes/kubernetes/issues/65369,334869648,Automated cherry pick of #65367: make sure delete waiting doesn't re-evaluate the resource,Cherry pick of #65367 on release-1.11. #65367: make sure delete waiting doesn't re-evaluate the resource,feature
https://api.github.com/repos/kubernetes/kubernetes/issues/65366,334867894,kubectl delete re-evaluates resource lists for its wait,When it does this for controller managed resources it can hang indefinitely. /assign,feature
https://api.github.com/repos/kubernetes/kubernetes/issues/65365,334867706,Automated cherry pick of #65339: Remove item from taint manager workqueue on completion,Cherry pick of #65339 on release-1.8. #65339: Remove item from taint manager workqueue on completion,feature
https://api.github.com/repos/kubernetes/kubernetes/issues/65364,334867341,Automated cherry pick of #65339: Remove item from taint manager workqueue on completion,Cherry pick of #65339 on release-1.9. #65339: Remove item from taint manager workqueue on completion,bug
https://api.github.com/repos/kubernetes/kubernetes/issues/65362,334866454,Automated cherry pick of #65339: Remove item from taint manager workqueue on completion,Cherry pick of #65339 on release-1.11. #65339: Remove item from taint manager workqueue on completion,bug