Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for upgrades (0.44 sec)

  1. CHANGELOG/CHANGELOG-1.19.md

    - Kubeadm: during 'upgrade apply', if the kube-proxy ConfigMap is missing, assume that kube-proxy should not be upgraded. Same applies to a missing kube-dns/coredns ConfigMap for the DNS server addon. Note that this is a temporary workaround until 'upgrade apply' supports phases. Once phases are supported the kube-proxy/dns upgrade should be skipped manually. ([#89593](https://github.com/kubernetes/kubernetes/pull/89593), ...
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jan 05 05:42:32 UTC 2022
    - 489.7K bytes
    - Viewed (0)
  2. manifests/charts/istiod-remote/templates/crd-all.gen.yaml

                                        Specify if http1.1 connection should be upgraded to http2 for the associated destination.
    
                                        Valid Options: DEFAULT, DO_NOT_UPGRADE, UPGRADE
                                      enum:
                                      - DEFAULT
                                      - DO_NOT_UPGRADE
                                      - UPGRADE
                                      type: string
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu Jun 06 21:31:42 UTC 2024
    - 671.7K bytes
    - Viewed (0)
  3. manifests/charts/base/crds/crd-all.gen.yaml

                                        Specify if http1.1 connection should be upgraded to http2 for the associated destination.
    
                                        Valid Options: DEFAULT, DO_NOT_UPGRADE, UPGRADE
                                      enum:
                                      - DEFAULT
                                      - DO_NOT_UPGRADE
                                      - UPGRADE
                                      type: string
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu Jun 06 21:31:42 UTC 2024
    - 671.6K bytes
    - Viewed (0)
  4. operator/cmd/mesh/testdata/manifest-generate/output/all_on.golden-show-in-gh-pull-request.yaml

                                        be upgraded to http2 for the associated destination.
                                      enum:
                                      - DEFAULT
                                      - DO_NOT_UPGRADE
                                      - UPGRADE
                                      type: string
                                    http1MaxPendingRequests:
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Wed Jan 10 05:10:03 UTC 2024
    - 506.8K bytes
    - Viewed (0)
  5. pkg/apis/core/validation/validation_test.go

    			oldClaim:          validClaim,
    			newClaim:          unboundSizeUpdate,
    		},
    		"valid-upgrade-storage-class-annotation-to-spec": {
    			isExpectedFailure: false,
    			oldClaim:          validClaimStorageClass,
    			newClaim:          validClaimStorageClassInSpec,
    		},
    		"valid-upgrade-nil-storage-class-spec-to-spec": {
    			isExpectedFailure: false,
    			oldClaim:          validClaimStorageClassNil,
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 857.7K bytes
    - Viewed (0)
  6. RELEASE.md

        * Discussion for these changes can be found on SIG Build's [TensorFlow Community Forum thread](https://discuss.tensorflow.org/t/tensorflow-linux-wheels-are-being-upgraded-to-manylinux2014/8339)
    *   The `tf.keras.mixed_precision.experimental` API has been removed. The non-experimental symbols under `tf.keras.mixed_precision` have been available since TensorFlow 2.4 and should be used instead.
    Registered: Sun Jun 16 05:45:23 UTC 2024
    - Last Modified: Tue Jun 11 23:24:08 UTC 2024
    - 730.3K bytes
    - Viewed (0)
  7. tests/integration/pilot/testdata/gateway-api-crd.yaml

              accept HTTP/2 connections without an initial upgrade from HTTP/1.1, i.e. via
              ALPN. If the implementation does not support this, then it MUST set the
              "Accepted" condition to "False" for the affected listener with a reason of
              "UnsupportedProtocol".  Implementations MAY also accept HTTP/2 connections
              with an upgrade from HTTP/1.
    
    
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu May 09 02:01:51 UTC 2024
    - 912.2K bytes
    - Viewed (0)
Back to top