Search Options

Results per page
Sort
Preferred Languages
Advance

Results 961 - 970 of 1,037 for comments (0.07 sec)

  1. helm-releases/minio-3.5.8.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Feb 27 06:44:38 UTC 2022
    - 17.7K bytes
    - Viewed (0)
  2. helm-releases/minio-3.6.1.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Mar 15 00:13:17 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  3. tensorflow/c/eager/c_api_test.cc

        if (TF_GetCode(status.get()) != TF_OK) {
          ADD_FAILURE() << tag << " -- " << TF_Message(status.get());
          continue;
        }
        TFE_DeleteTensorHandle(hdevice2);
    
        // Ensure that the contents are the same!
        TF_Tensor* tcopy = TFE_TensorHandleResolve(hcopy, status.get());
        TFE_DeleteTensorHandle(hcopy);
        if (TF_GetCode(status.get()) != TF_OK) {
          ADD_FAILURE() << tag;
          continue;
        }
    Registered: Tue Nov 05 12:39:12 UTC 2024
    - Last Modified: Thu Aug 03 20:50:20 UTC 2023
    - 94.6K bytes
    - Viewed (0)
  4. helm-releases/minio-3.0.0.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  5. helm-releases/minio-3.1.3.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sat Sep 18 18:09:59 UTC 2021
    - 14.4K bytes
    - Viewed (0)
  6. helm-releases/minio-3.4.6.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sat Jan 08 06:24:06 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  7. helm-releases/minio-3.4.8.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Jan 28 18:33:38 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  8. helm-releases/minio-3.5.2.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Feb 08 00:29:26 UTC 2022
    - 15.4K bytes
    - Viewed (0)
  9. helm-releases/minio-3.1.8.tgz

    "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 }} Read more about port...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Oct 07 05:03:47 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  10. CHANGELOG/CHANGELOG-1.15.md

    block, continues to receive features and stability work required for bootstrapping production clusters efficiently. kubeadm has promoted high availability (HA) capability to beta, allowing users to use the familiar `kubeadm init` and `kubeadm join` commands to [configure and deploy an HA control plane](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/). An entire new test suite has been created specifically for ensuring these features will stay stable over time....
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu May 05 13:44:43 UTC 2022
    - 278.9K bytes
    - Viewed (0)
Back to top