Old version kubectl's rolling-update command is compatible with Kubernetes 1.4 and higher only if you specify a new replication controller name. You will need to update to kubectl 1.4 or higher to use the rolling update command against a 1.4 cluster if you want to keep the original name, or you'll have to do two rolling updates.

	VRANGEPD $14, Z23, Z27, K1, Z2                     // 62b3a54150d70e
	VRANGEPD $14, Z9, Z27, K1, Z2                      // 62d3a54150d10e
	VRANGEPD $14, (R14), Z27, K1, Z2                   // 62d3a54150160e
	VRANGEPD $14, -7(DI)(R8*8), Z27, K1, Z2            // 62b3a5415094c7f9ffffff0e
	VRANGEPD $14, Z23, Z25, K1, Z2                     // 62b3b54150d70e

* If you used the [PodDisruptionBudget](http://kubernetes.io/docs/admin/disruptions/) feature in 1.4 (i.e. created `PodDisruptionBudget` objects), then **BEFORE**  upgrading from 1.4 to 1.5, you must delete all `PodDisruptionBudget` objects (`policy/v1alpha1/PodDisruptionBudget`) that you have created. It is not possible to delete these objects after you upgrade, and their presence will prevent...

### Changed
- github.com/armon/circbuf: [bbbad09 → 5111143](https://github.com/armon/circbuf/compare/bbbad09...5111143)
- github.com/docker/docker: [v27.1.1+incompatible → v26.1.4+incompatible](https://github.com/docker/docker/compare/v27.1.1...v26.1.4)
- github.com/exponent-io/jsonpath: [d6023ce → 1de76d7](https://github.com/exponent-io/jsonpath/compare/d6023ce...1de76d7)

40700,4040700,E,QN26,North Corona,4102,641,377,4,Queens,037700,4037700,E,QN26,North Corona,4102^3389272,1,2014-03-06 12:39:41,2014-03-06 12:50:50,N,1,-73.86492919921875,40.748310089111328,-73.873153686523438,40.774505615234375,1,3.70,13,0,0.5,1,0,,,14.5,1,,173,138,green,0.00,3.9,0.0,31,16,8.50,1281,407,4,Queens,040700,4040700,E,QN26,North Corona,4102,1840,331,4,Queens,033100,4033100,I,QN98,Airport,4102^3389273,1,2014-03-08 11:31:27,2014-03-08 11:45:12,N,1,-73.862953186035156,40.750247955322266,-...

          <description>
            Specifies that this profile will be activated when a matching JDK is detected.
            For example, {@code 1.4} only activates on JDKs versioned 1.4,
            while {@code !1.4} matches any JDK that is not version 1.4. Ranges are supported too:
            {@code [1.5,)} activates when the JDK is 1.5 minimum.
          </description>
        </field>
        <field>

			accessKey:          credentials.AccessKey,
			secretKey:          credentials.SecretKey,
			expectedRespStatus: http.StatusPreconditionFailed,
		},
		// Test case - 14, copy metadata from newObject1 with wrong modified header format
		14: {
			bucketName:         bucketName,
			newObjectName:      "newObject1",
			copySourceHeader:   url.QueryEscape(SlashSeparator + bucketName + SlashSeparator + objectName),

          },
          "unit": "percentunit"
        },
        "overrides": []
      },
      "gridPos": {
        "h": 4,
        "w": 6,
        "x": 6,
        "y": 4
      },
      "id": 14,
      "links": [],
      "maxDataPoints": 100,
      "options": {
        "colorMode": "none",
        "graphMode": "area",
        "justifyMode": "auto",
        "orientation": "horizontal",

          },
          "unit": "percentunit"
        },
        "overrides": []
      },
      "gridPos": {
        "h": 4,
        "w": 8,
        "x": 8,
        "y": 4
      },
      "id": 14,
      "links": [],
      "maxDataPoints": 100,
      "options": {
        "colorMode": "none",
        "graphMode": "area",
        "justifyMode": "auto",
        "orientation": "horizontal",

in the result. The result has indices starting at 0 and length equal to
<code>high</code>&nbsp;-&nbsp;<code>low</code>.
After slicing the array <code>a</code>
</p>

<pre>
a := [5]int{1, 2, 3, 4, 5}
s := a[1:4]
</pre>

<p>
the slice <code>s</code> has type <code>[]int</code>, length 3, capacity 4, and elements
</p>

<pre>
s[0] == 2
s[1] == 3
s[2] == 4
</pre>

<p>