Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 20 of 2,456 for layers (0.11 sec)

  1. staging/src/k8s.io/cli-runtime/README.md

    will track Kubernetes and be compatible with that repo.  As we more cleanly separate the layers, we will review the
    compatibility guarantee.
    
    
    ## Where does it come from?
    
    `cli-runtime` is synced from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cli-runtime.
    Code changes are made in that location, merged into `k8s.io/kubernetes` and later synced here.
    
    
    ## Things you should *NOT* do
    
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri Dec 03 01:38:34 UTC 2021
    - 1.2K bytes
    - Viewed (0)
  2. staging/src/k8s.io/apiserver/README.md

    compatibility guarantee. We have a goal to make this easier to use in the future.
    
    
    ## Where does it come from?
    
    `apiserver` is synced from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver.
    Code changes are made in that location, merged into `k8s.io/kubernetes` and later synced here.
    
    
    ## Things you should *NOT* do
    
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri Dec 03 01:38:34 UTC 2021
    - 1.3K bytes
    - Viewed (0)
  3. tensorflow/compiler/mlir/quantization/tensorflow/passes/add_quantization_unit_loc.cc

    namespace mlir {
    namespace quant {
    namespace {
    
    using QuantizationUnit =
        tensorflow::quantization::UnitWiseQuantizationSpec::QuantizationUnit;
    
    // Adds QuantizationUnitLoc to quantizable layers.
    class AddQuantizationUnitLocPass
        : public PassWrapper<AddQuantizationUnitLocPass,
                             OperationPass<func::FuncOp>> {
     public:
    Registered: Sun Jun 16 05:45:23 UTC 2024
    - Last Modified: Thu Apr 25 16:01:03 UTC 2024
    - 7.4K bytes
    - Viewed (0)
  4. tools/packaging/common/gcp_envoy_bootstrap.json

    {
      "node": {
        {{ if (index .metadata.Labels "td.networking.gke.io/mesh-name") }}
          "id": "projects/{{ .gcp_project_number }}/networks/mesh:{{ (index .metadata.Labels "td.networking.gke.io/mesh-name") }}/nodes/{{ .nodeID}}",
        {{ else if (index .metadata.Labels "td.networking.gke.io/gateway-name") }}
          "id": "projects/{{ .gcp_project_number }}/networks/scope:{{ (index .metadata.Labels "td.networking.gke.io/gateway-name") }}/nodes/{{ .nodeID}}",
        {{ else }}
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu May 16 17:05:28 UTC 2024
    - 6.9K bytes
    - Viewed (0)
  5. tools/istio-docker.mk

    #  1) make target calls ./tools/docker
    #  2) ./tools/docker calls `make build.docker.x` targets to compute the dependencies required
    #  3) ./tools/docker triggers the actual docker commands required
    # As a result, there are two layers of make involved.
    
    docker: ## Build all docker images
    	./tools/docker
    
    docker.save: ## Build docker images and save to tar.gz
    	./tools/docker --save
    
    docker.push: ## Build all docker images and push to
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu Mar 31 21:56:36 UTC 2022
    - 2.1K bytes
    - Viewed (0)
  6. pkg/kubelet/eviction/types.go

    	// fsStatsLogs identifies stats for pod logs.
    	fsStatsLogs fsStatsType = "logs"
    	// fsStatsRoot identifies stats for pod container writable layers.
    	fsStatsRoot fsStatsType = "root"
    	// fsStatsContainer identifies stats for pod container read-only layers
    	fsStatsImages fsStatsType = "images"
    )
    
    // Config holds information about how eviction is configured.
    type Config struct {
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Nov 01 18:46:33 UTC 2023
    - 7.1K bytes
    - Viewed (0)
  7. ci/official/containers/linux_arm64/build.sh

    AR_IMAGE_PATH="us-central1-docker.pkg.dev/tensorflow-sigs/tensorflow/build-arm64"
    
    # Build for both JAX and TF usage.  We do these in one place because they share
    # almost all of the same cache layers
    export DOCKER_BUILDKIT=1
    for target in jax tf; do
      IMAGE="gcr.io/tensorflow-sigs/build-arm64:$target-$TAG"
      AR_IMAGE="$AR_IMAGE_PATH:$target-$TAG"
      docker pull "$IMAGE" || true
    Registered: Sun Jun 16 05:45:23 UTC 2024
    - Last Modified: Mon May 20 22:33:16 UTC 2024
    - 2.6K bytes
    - Viewed (0)
  8. tests/testdata/bootstrap_tmpl.json

        "access_log_path": "{{.AccessLogPath}}",
        "address": {
          "socket_address": {
            "address": "0.0.0.0",
            "port_value": {{.Ports.AdminPort}}
          }
        }
      },
      "layered_runtime": {
          "layers": [
              {
                  "name": "deprecation",
                  "static_layer": {
                      "envoy.deprecated_features:envoy.config.listener.v3.Listener.hidden_envoy_deprecated_use_original_dst": true,
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Wed Jan 13 02:10:15 UTC 2021
    - 9.5K bytes
    - Viewed (0)
  9. staging/src/k8s.io/apiserver/pkg/endpoints/filters/audit.go

    	}
    	audit.LogRequestMetadata(ctx, req, requestReceivedTimestamp, rac.Level, attribs)
    
    	return ac, nil
    }
    
    // writeLatencyToAnnotation writes the latency incurred in different
    // layers of the apiserver to the annotations of the audit object.
    // it should be invoked after ev.StageTimestamp has been set appropriately.
    func writeLatencyToAnnotation(ctx context.Context, ev *auditinternal.Event) {
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Mon Jul 03 16:16:51 UTC 2023
    - 8.6K bytes
    - Viewed (0)
  10. pkg/test/framework/features/README.md

    "usability.observability.status" is the feature, and "exist-by-default" is the scenario in the first case, and the second case has no scenario.
    
    The hierarchical nature of feature labels allows us to aggregate data about related feature sets.  To provide for consistent reporting and aggregation, we have defined the top two layers of hierarchy, and ask that you place your feature under these headings.  For more detail on the purpose of each heading, see Top-Level Feature Headings below.  If you feel that...
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu Jul 20 19:13:32 UTC 2023
    - 2.8K bytes
    - Viewed (0)
Back to top