1. 17 May, 2017 9 commits
    • Kubernetes Submit Queue's avatar
      Merge pull request #45898 from MrHohn/update-test-owner · 2d30afb7
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45247, 45810, 45034, 45898, 45899)
      
      Add MrHohn to couple e2e tests
      
      /assign @bowei 
      
      **Release note**:
      
      ```release-note
      NONE
      ```
      2d30afb7
    • Kubernetes Submit Queue's avatar
      Merge pull request #45034 from shashidharatd/federation-service-controller-3 · b8f084a6
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45247, 45810, 45034, 45898, 45899)
      
      [Federation] Segregate DNS related code to separate controller
      
      **What this PR does / why we need it**:
      This is the continuation of service controller re-factor work as outlined in #41253
      This PR segregates DNS related code from service controller to another controller `service-dns controller` which manages the DNS records on the configured DNS provider.
      `service-dns controller` monitors the federated services for the ingress annotations and create/update/delete DNS records accordingly.
      `service-dns controller` can be optionally disabled and DNS record management could be done by third party components by monitoring the ingress annotations on federated services. (This would enable something like federation middleware for CoreDNS where federation api server could be used as a backend to CoreDNS eliminating the need for etcd storage.)
      
      **Special notes for your reviewer**:
      
      **Release note**:
      ```
      Federation: A new controller for managing DNS records is introduced which can be optionally disabled to enable third party components to manage DNS records for federated services.
      ```
      cc @kubernetes/sig-federation-pr-reviews
      b8f084a6
    • Kubernetes Submit Queue's avatar
      Merge pull request #45810 from superbrothers/expand-env-vals · 79dae5c0
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45247, 45810, 45034, 45898, 45899)
      
      kubectl plugin: Expand environment variables in the command of plugin.yaml
      
      **What this PR does / why we need it**:
      
      This commit improves kubectl plugins to expand environment variables in the command of plugin.yaml.
      I'd like to use environment variables in the command of plugin.yaml as follows:
      ```yaml
      name: hello
      shortDesc: "The hello plugin"
      longDesc: >
        The hello plugin is a new
        plugin used by test-cmd
        to test multiple plugin locations.
      command: $HOME/path/to/plugins/hello.sh
      ```
      
      **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
      
      **Special notes for your reviewer**:
      
      **Release note**:
      
      ```release-note
      NONE
      ```
      79dae5c0
    • Kubernetes Submit Queue's avatar
      Merge pull request #45247 from mbohlool/c3 · 3f0ebbe8
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45247, 45810, 45034, 45898, 45899)
      
      Apiregistration v1alpha1→v1beta1
      
      Promoting apiregistration api from v1alpha1 to v1beta1.
      
      API Registration is responsible for registering an API `Group`/`Version` with
      another kubernetes like API server. The `APIService` holds information
      about the other API server in `APIServiceSpec` type as well as general
      `TypeMeta` and `ObjectMeta`. The `APIServiceSpec` type have the main
      configuration needed to do the aggregation. Any request coming for
      specified `Group`/`Version` will be directed to the service defined by
      `ServiceReference` (on port 443) after validating the target using provided
      `CABundle` or skipping validation if development flag `InsecureSkipTLSVerify`
      is set. `Priority` is controlling the order of this API group in the overall
      discovery document.
      The return status is a set of conditions for this aggregation. Currently
      there is only one condition named "Available", if true, it means the
      api/server requests will be redirected to specified API server.
      
      ```release-note
      API Registration is now in beta.
      ```
      3f0ebbe8
    • Kubernetes Submit Queue's avatar
      Merge pull request #45888 from zjj2wry/zjj-tt · 8f81307b
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45374, 44537, 45739, 44474, 45888)
      
      fix typo
      
      **What this PR does / why we need it**:
      
      **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
      
      **Special notes for your reviewer**:
      
      **Release note**:
      
      ```release-note
      ```
      8f81307b
    • Kubernetes Submit Queue's avatar
      Merge pull request #44474 from ahmetb/fix-types-links · 2c2c9265
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45374, 44537, 45739, 44474, 45888)
      
      Update 'More info' links on API types and fields
      
      > **Please just review the first commit, the rest is generated files.**
      
      Recent docs website shuffling during 1.6 caused majority of links in the API
      types and fields to break. Since we do not have server-side 301 redirects, user
      has to click an extra link, and the #target fragment in the URL will be lost.  (This is
      because GitHub’s redirect_from feature is not ideal.) 
      
      For the time being, I have manually gone through all of them to bring them up to date
      and add HTTPS to those missing it. This is a docs-only change and impacts generated
      code, generated swaggers, API reference docs etc.
      
      cc: @steveperry-53 @devin-donnelly @chenopis fyi, docs links changes (even small title changes) easily breaks links in API reference, Swagger, kubectl explain, and many other places.
      Signed-off-by: 's avatarAhmet Alp Balkan <ahmetb@google.com>
      2c2c9265
    • Kubernetes Submit Queue's avatar
      Merge pull request #45739 from timothysc/cm_lock · 7f92d35f
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45374, 44537, 45739, 44474, 45888)
      
      Allow kcm and scheduler to lock on ConfigMaps.
      
      **What this PR does / why we need it**:
      Plumbs through the ability to lock on ConfigMaps through the kcm and scheduler.  
      
      **Which issue this PR fixes** 
      Fixes: #44857
      Addresses issues with: #45415
      
      **Special notes for your reviewer**:
      
      **Release note**:
      
      ```
      Add leader-election-resource-lock support to kcm and scheduler to allow for locking on ConfigMaps as well as Endpoints(default) 
      ```
      /cc @kubernetes/sig-cluster-lifecycle-pr-reviews @jamiehannaford @bsalamat @mikedanese
      7f92d35f
    • Kubernetes Submit Queue's avatar
      Merge pull request #44537 from FengyunPan/fix-volume-bug · f1716832
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45374, 44537, 45739, 44474, 45888)
      
      Fix attach volume to instance repeatedly
      
      1.When volume's status is 'attaching', controllermanager will attach
          it again and return err. So it is necessary to check volume's
          status before attach/detach volume.
      
         2. When volume's status is 'attaching', its attachments will be None,
          controllermanager can't get device path and make some failed event.
          But it is normal, so don't return err when attachments is None
      
      Fix bug: #44536
      f1716832
    • Kubernetes Submit Queue's avatar
      Merge pull request #45374 from marun/fed-refactor-sync-controller · 0e735961
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 45374, 44537, 45739, 44474, 45888)
      
      [Federation] Refactor sync controller's reconcile method for maintainability
      
      This PR refactors the sync controllers reconcile method for maintainability with the goal of eliminating the need for type-specific controller unit tests.  The unit test coverage for reconcile is not complete, but I think it's a good start.
      
      cc: @kubernetes/sig-federation-pr-reviews
      0e735961
  2. 16 May, 2017 31 commits