Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for expanded (0.15 sec)

  1. Makefile.core.mk

    # The build-linux target is responsible for building binaries used within containers.
    # This target should be expanded upon as we add more Linux architectures: i.e. build-arm64.
    # Then a new build target can be created such as build-container-bin that builds these
    # various platform images.
    .PHONY: build-linux
    build-linux: depend
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed May 08 20:25:15 GMT 2024
    - 22.5K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/storage/v1beta1/generated.proto

      // Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount
      // option when mounting a ReadWriteOncePod volume used in Pod that has
      // explicitly set SELinux context. In the future, it may be expanded to other
      // volume AccessModes. In any case, Kubernetes will ensure that the volume is
      // mounted only with a single SELinux context.
      //
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.9K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/storage/v1/generated.proto

      // Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount
      // option when mounting a ReadWriteOncePod volume used in Pod that has
      // explicitly set SELinux context. In the future, it may be expanded to other
      // volume AccessModes. In any case, Kubernetes will ensure that the volume is
      // mounted only with a single SELinux context.
      //
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.7K bytes
    - Viewed (0)
  4. architecture/networking/pilot.md

    The Push Queue is mostly a normal queue, but it has some special logic to merge push requests for each given proxy. This results in each proxy having 0 or 1 outstanding push requests; if additional updates come in the existing push request is just expanded.
    
    Another job polls this queue and triggers each client to start a push.
    
    ```mermaid
    graph TD
        subgraph Config Flow
            cu(Config Update)
            db(Debounce)
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Feb 07 17:53:24 GMT 2024
    - 19.1K bytes
    - Viewed (0)
  5. common/scripts/kind_provisioner.sh

      if ! (kind delete cluster --name="${NAME}" -v9) > /dev/null; then
        echo "No existing kind cluster with name ${NAME}. Continue..."
      fi
    
      # explicitly disable shellcheck since we actually want $NAME to expand now
      # shellcheck disable=SC2064
      if [[ "${CLEANUP}" == "true" ]]; then
        trap "cleanup_kind_cluster ${NAME}" EXIT
      fi
    
        # If config not explicitly set, then use defaults
      if [[ -z "${CONFIG}" ]]; then
    Shell Script
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 08 19:12:55 GMT 2024
    - 17.3K bytes
    - Viewed (1)
  6. common-protos/k8s.io/api/certificates/v1/generated.proto

      //  4. Required, permitted, or forbidden key usages / extended key usages.
      //  5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin.
      //  6. Whether or not requests for CA certificates are allowed.
      optional string signerName = 7;
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 11.6K bytes
    - Viewed (0)
Back to top