[Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. Prerequisites ---------- - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using https://github.com/minio/direct-csi) - Use Kubernetes version v1.19 and later for best experience. Configure MinIO Helm repo ---------- ```bash helm repo add minio https://charts.min.io/ ``` Installing the Chart ---------- Install this chart using: ```bash helm install --namespace...

[Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. Prerequisites ---------- - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using https://github.com/minio/direct-csi) - Use Kubernetes version v1.19 and later for best experience. Configure MinIO Helm repo ---------- ```bash helm repo add minio https://charts.min.io/ ``` Installing the Chart ---------- Install this chart using: ```bash helm install --namespace...

pkg reflect, func Append(Value, ...Value) Value
pkg reflect, func AppendSlice(Value, Value) Value
pkg reflect, func Copy(Value, Value) int
pkg reflect, func DeepEqual(interface{}, interface{}) bool
pkg reflect, func Indirect(Value) Value
pkg reflect, func MakeChan(Type, int) Value
pkg reflect, func MakeMap(Type) Value
pkg reflect, func MakeSlice(Type, int, int) Value
pkg reflect, func New(Type) Value

* Restores redirect behavior for proxy subresources ([#52933](https://github.com/kubernetes/kubernetes/pull/52933), [@liggitt](https://github.com/liggitt))

- Kube-apiserver: redirect responses are no longer returned from backends by default. Set `--aggregator-reject-forwarding-redirect=false` to continue forwarding redirect responses. ([#112359](https://github.com/kubernetes/kubernetes/pull/112359), [@enj](https://github.com/enj)) [SIG API Machinery]

    * In this way, the whole container streaming connection is secure. To switch back to the old behavior, set `--redirect-container-streaming=true` flag.

against a 1.4 cluster if you want to keep the original name, or you'll have to do two rolling updates.

If you do happen to use old version kubectl's rolling update against a 1.4 cluster, it will fail, usually with an error message that will direct you here. If you saw that error, then don't worry, the operation succeeded except for the part where the new replication controller is renamed back to the old name. You can just do another rolling update using kubectl 1.4 or higher to change the name...

'lte.directchat'\nconst EVENT_KEY = `.${DATA_KEY}`\nconst JQUERY_NO_CONFLICT = $.fn[NAME]\n\nconst EVENT_TOGGLED = `toggled${EVENT_KEY}`\n\nconst SELECTOR_DATA_TOGGLE = '[data-widget=\"chat-pane-toggle\"]'\nconst SELECTOR_DIRECT_CHAT = '.direct-chat'\n\nconst CLASS_NAME_DIRECT_CHAT_OPEN = 'direct-chat-contacts-open'\n\n/**\n * Class Definition\n * ====================================================\n */\n\nclass DirectChat {\n  constructor(element) {\n    this._element = element\n  }\n\n  toggle() {\n    $(this....

- Kube-apiserver: redirect responses are no longer returned from backends by default. Set `--aggregator-reject-forwarding-redirect=false` to continue forwarding redirect responses. ([#112193](https://github.com/kubernetes/kubernetes/pull/112193), [@jindijamie](https://github.com/jindijamie)) [SIG API Machinery and Testing]

## Changes since v1.3.0-alpha.4

### Action Required

* Add direct serializer ([#26251](https://github.com/kubernetes/kubernetes/pull/26251), [@caesarxuchao](https://github.com/caesarxuchao))