- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 207 for Clusters (0.17 sec)
-
common/scripts/kind_provisioner.sh
fi done } # load_cluster_topology function reads cluster configuration topology file and # sets up environment variables used by other functions. So this should be called # before anything else. # # Note: Cluster configuration topology file specifies basic configuration of each # KinD cluster like its name, pod and service subnets and network_id. If two cluster
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Aug 21 04:47:23 UTC 2024 - 17.2K bytes - Viewed (0) -
docs/config/README.md
``` KEY: etcd federate multiple clusters for IAM and Bucket DNS ARGS: endpoints* (csv) comma separated list of etcd endpoints e.g. "http://localhost:2379"
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Aug 16 08:43:49 UTC 2024 - 17.9K bytes - Viewed (1) -
architecture/networking/pilot.md
controllers. Per Kubernetes, "controllers are control loops that watch the state of your cluster, then make or request changes where needed." In Istio, we use the term a bit more liberally. Istio controllers watch more than just the state of *a* cluster -- many are reading from multiple clusters, or even external sources (files and XDS). Generally, Kubernetes controllers are then writing state back to the cluster; Istio does have a few of these controllers, but most of them are centered around...
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Feb 07 17:53:24 UTC 2024 - 19.1K bytes - Viewed (0) -
istioctl/pkg/multicluster/remote_secret_test.go
clusters: - cluster: certificate-authority-data: Y2FEYXRh server: https://1.2.3.4 name: {cluster} contexts: - context: cluster: {cluster} user: {cluster} name: {cluster} current-context: {cluster} kind: Config preferences: {} users: - name: {cluster} user: token: token `, "{cluster}", fakeClusterName) cases := []struct {
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Oct 24 17:36:49 UTC 2024 - 20.7K bytes - Viewed (0) -
docs/bucket/replication/DESIGN.md
remote target is configured with --sync mode in `mc admin bucket remote add` does not apply to `DELETE` operations. The version being deleted on the source cluster needs to maintain state and ensure that the operation is mirrored to the target cluster prior to completing on the source object version. Since this needs to account for the target cluster availability and the need to serialize concurrent DELETE operations on different versions of the same object during multi DELETE operations, the current...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 29 04:28:45 UTC 2022 - 14.7K bytes - Viewed (0) -
common-protos/k8s.io/api/resource/v1alpha2/generated.proto
// +optional optional string selectedNode = 1; // PotentialNodes lists nodes where the Pod might be able to run. // // The size of this field is limited to 128. This is large enough for // many clusters. Larger clusters may need more attempts to find a node // that suits all pending resources. This may get increased in the // future, but not reduced. // // +listType=set // +optional
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 14.4K bytes - Viewed (0) -
docs/bucket/replication/README.md
created prior to adding replication configuration OR while replication rules were disabled will be synced to the target cluster. Depending on the number of previously existing objects, the existing objects that are now eligible to be replicated will eventually be synced to the target cluster as the scanner schedules them. This may be slower depending on the load on the cluster, latency and size of the namespace. In the rare event that target DR site is entirely lost and previously replicated...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Jan 24 23:46:33 UTC 2023 - 18.2K bytes - Viewed (0) -
architecture/ambient/ztunnel.md
However, while we chose to use the xDS *transport protocol*, we chose to not use the xDS resource types, such as Clusters and Listeners. In our experience and testing, these types force us to represent data in inefficient ways because they are general purpose. Ztunnel is not general purpose; it has an extremely tight goal.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 16.8K bytes - Viewed (0) -
manifests/addons/dashboards/ztunnel-dashboard.gen.json
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Jul 26 23:54:32 UTC 2024 - 17.3K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.2.md
declaratively. It handles versioning, multiple simultaneous rollouts, aggregating status across all pods, maintaining application availability, and rollback. * <strong>Automated cluster management: </strong> * Kubernetes clusters can now span zones within a cloud provider. Pods from a service will be automatically spread across zones, enabling applications to tolerate zone failure.
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Fri Dec 04 06:36:19 UTC 2020 - 41.4K bytes - Viewed (0)