1. 17 Jun, 2017 3 commits
    • Kubernetes Submit Queue's avatar
      Merge pull request #46382 from verult/FlexVolumeMinorPatches · fdc67468
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 38751, 44282, 46382, 47603, 47606)
      
      Adding 'flexvolume' prefix to FlexVolume plugin names.
      
      **What this PR does / why we need it**: Adds a prefix to FlexVolume plugin names in order to more easily identify plugins as FlexVolume. Improves debugging.
      
      **Special notes for your reviewer**: Unfortunately the delimiter after 'flexvolume' is restricted to either '-' or '.' . This makes the prefix seem like it's part of the vendor name. Not sure if this could cause issues later on.
      
      **Release note**:
      
      ```release-note
      NONE
      ```
      fdc67468
    • Kubernetes Submit Queue's avatar
      Merge pull request #44282 from derekwaynecarr/fix-kubectl-logs · 48d263d3
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 38751, 44282, 46382, 47603, 47606)
      
      kubectl logs with label selector supports specifying a container name
      
      **What this PR does / why we need it**:
      Allows `kubectl logs` to take both a label selector and container name.  This allows me to fetch logs from pods by selector whose pods have multiple containers with a common name.  This is a common action when debugging components like the service-catalog that ship more than one container in their pod.  With this change, the following command lets me get logs for service-catalog.
      
      ```
      $ kubectl logs -l app=sc-catalog-apiserver --namespace=service-catalog --container=apiserver
      ```
      48d263d3
    • Kubernetes Submit Queue's avatar
      Merge pull request #38751 from chenchun/warn · 9054e70c
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Raise a warning instead of info if br-netfilter is missing or unset
      
      Took quite a while to figure out why service VIP is unreachable on my cluster. It turns out br-nf-call-iptables is unset. I wish this message could be a warning to attract considerable attention.
      9054e70c
  2. 16 Jun, 2017 33 commits
  3. 15 Jun, 2017 4 commits