pkg encoding/csv, type ParseError struct, StartLine int
pkg encoding/hex, func NewDecoder(io.Reader) io.Reader
pkg encoding/hex, func NewEncoder(io.Writer) io.Writer
pkg encoding/json, method (*Decoder) DisallowUnknownFields()
pkg encoding/xml, func NewTokenDecoder(TokenReader) *Decoder
pkg encoding/xml, type TokenReader interface { Token }
pkg encoding/xml, type TokenReader interface, Token() (Token, error)

pkg encoding/json, method (*RawMessage) UnmarshalJSON([]uint8) error
pkg encoding/json, method (*SyntaxError) Error() string
pkg encoding/json, method (*UnmarshalFieldError) Error() string
pkg encoding/json, method (*UnmarshalTypeError) Error() string
pkg encoding/json, method (*UnsupportedTypeError) Error() string
pkg encoding/json, method (*UnsupportedValueError) Error() string
pkg encoding/json, type Decoder struct

### (No, really, you MUST do this before you upgrade)

Before upgrading to Kubernetes 1.11, you must keep the following in mind:

- github.com/envoyproxy/protoc-gen-validate: [v0.9.1 → v1.0.2](https://github.com/envoyproxy/protoc-gen-validate/compare/v0.9.1...v1.0.2)
- github.com/evanphx/json-patch: [v5.6.0+incompatible → v4.12.0+incompatible](https://github.com/evanphx/json-patch/compare/v5.6.0...v4.12.0)
- github.com/fsnotify/fsnotify: [v1.6.0 → v1.7.0](https://github.com/fsnotify/fsnotify/compare/v1.6.0...v1.7.0)

The YAML tests support various operators defined in the link:/rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/README.asciidoc[rest-api-spec] and adhere to the link:/rest-api-spec/README.markdown[Elasticsearch REST API JSON specification]
In order to run the YAML tests, the relevant API specification needs
to be on the test classpath. Any gradle project that has support for REST

  * `kubectl create secret tls` command
  * Webhook Token Authenticator
  * **beta** PodSecurityPolicy objects limits use of security-sensitive features by pods.
* Kubectl
  * Display line number on JSON errors
  * Add flag -t as shorthand for --tty
* Resources

你應該可以透過 Docker 容器的網址檢查，例如：[http://192.168.99.100/items/5?q=somequery](http://192.168.99.100/items/5?q=somequery) 或 [http://127.0.0.1/items/5?q=somequery](http://127.0.0.1/items/5?q=somequery)（或等效的、使用你的 Docker 主機）。

你會看到類似這樣：

```JSON
{"item_id": 5, "q": "somequery"}
```

## 互動式 API 文件 { #interactive-api-docs }

現在你可以前往 [http://192.168.99.100/docs](http://192.168.99.100/docs) 或 [http://127.0.0.1/docs](http://127.0.0.1/docs)（或等效的、使用你的 Docker 主機）。

    /** The key of the message: User Info */
    public static final String LABELS_USER_INFO = "{labels.userInfo}";

    /** The key of the message: JSON Response */
    public static final String LABELS_WEB_API_JSON = "{labels.webApiJson}";

    /** The key of the message: Web Crawl Config Name */

'object' ? config : data)\n      localStorage.setItem('AdminLTE:IFrame:Options', JSON.stringify(_options))\n\n      const plugin = new IFrame($(this), _options)\n\n      $(this).data(DATA_KEY, typeof config === 'object' ? config : data)\n\n      if (typeof config === 'string' && /createTab|openTabSidebar|switchTab|removeActiveTab/.test(config)) {\n        plugin[config]()\n      }\n    } else {\n      new IFrame($(this), JSON.parse(localStorage.getItem('AdminLTE:IFrame:Options')))._initFrameElement()\n...

- E2e framework: added `--report-complete-ginkgo` and `--report-complete-junit` parameters. They work like `ginkgo --json-report <report dir>/ginkgo/report.json --junit-report <report dir>/ginkgo/report.xml`. ([#115678](https://github.com/kubernetes/kubernetes/pull/115678), [@pohly](https://github.com/pohly)) [SIG Testing]