Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 291 - 300 of 523 for LOCALHOST (0.15 seconds)

  1. tensorflow/c/c_api_experimental_test.cc

      const std::string expected_text_proto(R"(cluster {
      job {
        name: "worker"
        tasks {
          key: 0
          value: "tpuserver:0"
        }
        tasks {
          key: 1
          value: "localhost:1"
        }
      }
    }
    job_name: "worker"
    task_index: 1
    protocol: "grpc"
    )");
    
      TF_Status* status = TF_NewStatus();
      TF_Buffer* result = TFE_GetServerDef(expected_text_proto.c_str(), status);
    Created: Tue Apr 07 12:39:13 GMT 2026
    - Last Modified: Wed Jan 07 04:56:09 GMT 2026
    - 13.1K bytes
    - Click Count (0)
  2. helm-releases/minio-3.4.8.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Fri Jan 28 18:33:38 GMT 2022
    - 15.2K bytes
    - Click Count (0)
  3. helm-releases/minio-3.5.2.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Feb 08 00:29:26 GMT 2022
    - 15.4K bytes
    - Click Count (0)
  4. helm-releases/minio-3.1.8.tgz

    .Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Thu Oct 07 05:03:47 GMT 2021
    - 14.6K bytes
    - Click Count (0)
  5. helm-releases/minio-3.4.6.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sat Jan 08 06:24:06 GMT 2022
    - 15.2K bytes
    - Click Count (0)
  6. TESTING.asciidoc

    There is a known issue with macOS localhost resolve strategy that can cause
    some integration tests to fail. This is because integration tests have timings
    for cluster formation, discovery, etc. that can be exceeded if name resolution
    takes a long time.
    To fix this, make sure you have your computer name (as returned by `hostname`)
    inside `/etc/hosts`, e.g.:
    ....
    127.0.0.1       localhost ElasticMBP.local
    255.255.255.255 broadcasthost
    Created: Wed Apr 08 16:19:15 GMT 2026
    - Last Modified: Mon Jun 07 13:55:20 GMT 2021
    - 32.5K bytes
    - Click Count (0)
  7. helm-releases/minio-3.3.2.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sat Dec 11 17:26:01 GMT 2021
    - 14.6K bytes
    - Click Count (0)
  8. helm-releases/minio-3.3.4.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sat Dec 11 17:59:34 GMT 2021
    - 14.6K bytes
    - Click Count (0)
  9. helm-releases/minio-3.4.2.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Dec 21 02:58:25 GMT 2021
    - 15.2K bytes
    - Click Count (0)
  10. helm-releases/minio-3.5.3.tgz

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Feb 13 23:43:44 GMT 2022
    - 15.4K bytes
    - Click Count (0)
Back to Top