- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 15 for balancers (0.33 sec)
-
CHANGELOG/CHANGELOG-1.28.md
- [KCCM] drop filtering nodes for the providerID when syncing load balancers, but have changes to the field trigger a re-sync of load balancers. This should ensure that cloud providers which don't specify providerID, can still use the service controller implementation to provision load balancers. ([#117602](https://github.com/kubernetes/kubernetes/pull/117602), [@alexanderConstantinescu](https://github.com/alexanderConstantinescu))...
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Tue Apr 16 20:44:48 GMT 2024 - 385.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.30.md
providers now waits for the providerID value to be available before untainting it. This ensures that nodes are not declared Ready without necessary information such as the providerID and zone labels, which are required for integrations like load balancers to function correctly. Cloud providers that do not implement the GetInstanceProviderID method will not require the providerID to be set and will not fail to initialize the node for backward compatibility. ([#123713](https://github.com/kubernetes...
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Wed Apr 17 17:56:15 GMT 2024 - 227.9K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.29.md
unauthenticated. The mitigation may be disabled by setting the `UnauthenticatedHTTP2DOSMitigation` feature gate to `false` (it is enabled by default). An API server fronted by an L7 load balancer that already mitigates these http/2 attacks may choose to disable the kube-apiserver mitigation to avoid disrupting load balancer -> kube-apiserver connections if http/2 requests from multiple clients share the same backend connection. An API server on a private network may opt to disable the kube-apiserver mitigation...
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Tue Apr 16 21:41:06 GMT 2024 - 299.9K bytes - Viewed (1) -
docs/en/docs/deployment/docker.md
And when working with containers, the same system you use to start and manage them would already have internal tools to transmit the **network communication** (e.g. HTTP requests) from that **load balancer** (that could also be a **TLS Termination Proxy**) to the container(s) with your app. ### One Load Balancer - Multiple Worker Containers
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 34.3K bytes - Viewed (0) -
manifests/charts/base/crds/crd-all.gen.yaml
type: object type: object loadBalancer: description: Settings controlling the load balancer algorithms. oneOf: - not: anyOf: - required: - simple
Others - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 20:20:47 GMT 2024 - 606.1K bytes - Viewed (0) -
manifests/charts/install-OpenShift.md
```console helm install -n istio-system istiod manifests/charts/istio-control/istio-discovery --set profile=openshift ``` 4) `gateways` charts install a load balancer with `ingress` and `egress`. Ingress secrets and access should be separated from the control plane. ```console helm install -n istio-system istio-ingress manifests/charts/gateways/istio-ingress --set profile=openshift
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Fri Apr 12 16:01:31 GMT 2024 - 1.8K bytes - Viewed (0) -
docs/metrics/prometheus/list.md
```shell https://HOSTNAME:PORT/minio/v2/metrics/cluster ``` Replace ``HOSTNAME:PORT`` with the hostname of your MinIO deployment. For deployments behind a load balancer, use the load balancer hostname instead of a single node hostname. ## Audit Metrics | Name | Description |
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Apr 25 22:01:31 GMT 2024 - 43.4K bytes - Viewed (2) -
CHANGELOG/CHANGELOG-1.27.md
- [KCCM] service controller: change the cloud controller manager to make `providerID` a predicate when synchronizing nodes. This change allows load balancer integrations to ensure that the `providerID` is set when configuring load balancers and targets. ([#117450](https://github.com/kubernetes/kubernetes/pull/117450), [@alexanderConstantinescu](https://github.com/alexanderConstantinescu)) [SIG Cloud Provider and Network]
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Tue Apr 16 15:20:21 GMT 2024 - 434.3K bytes - Viewed (3) -
helm/minio/values.yaml
# - 10.10.10.0/24 loadBalancerSourceRanges: [] ## service.externalTrafficPolicy minio service external traffic policy ## ref http://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip ## externalTrafficPolicy: Cluster ## Configure Ingress based on the documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/ ## ingress:
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 18.4K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
Prometheus sets the `Host` header to `domain:port` as part of HTTP operations against the MinIO metrics endpoint. For MinIO deployments behind a load balancer, reverse proxy, or other control plane (HAProxy, nginx, pfsense, opnsense, etc.), ensure the network service supports routing these requests to the deployment. ### 6. Configure Grafana
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0)