Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for CIDR (0.03 sec)

  1. common-protos/k8s.io/apimachinery/pkg/apis/meta/v1/generated.proto

      optional GroupVersionForDiscovery preferredVersion = 3;
    
      // a map of client CIDR to server address that is serving this group.
      // This is to help clients reach servers in the most network-efficient way possible.
      // Clients can use the appropriate server address as per the CIDR that they match.
      // In case of multiple matches, clients should use the longest matching CIDR.
      // The server returns only those CIDRs that it thinks that the client can match.
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Mar 11 18:43:24 UTC 2024
    - 53.3K bytes
    - Viewed (0)
  2. CHANGELOG/CHANGELOG-1.3.md

    * AWS kube-up: Allow VPC CIDR to be specified (experimental) ([#23362](https://github.com/kubernetes/kubernetes/pull/23362), [@miguelfrde](https://github.com/miguelfrde))
    * Return "410 Gone" errors via watch stream when using watch cache ([#25369](https://github.com/kubernetes/kubernetes/pull/25369), [@liggitt](https://github.com/liggitt))
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu Dec 24 02:28:26 UTC 2020
    - 84K bytes
    - Viewed (0)
  3. common/scripts/metallb-native.yaml

                      You can list multiple ranges in a single pool, they will all share
                      the same settings. Each range can be either a CIDR prefix, or an
                      explicit start-end range of IPs.
                    items:
                      type: string
                    type: array
                  autoAssign:
                    default: true
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Fri Feb 23 23:56:31 UTC 2024
    - 63.9K bytes
    - Viewed (0)
Back to top