Search Options

Results per page
Sort
Preferred Languages
Advance

Results 231 - 240 of 909 for dort (0.03 sec)

  1. istioctl/pkg/workload/testdata/vmconfig-nil-proxy-metadata/workloadgroup.yaml

    kind: WorkloadGroup
    metadata:
      name: foo
      namespace: bar
    spec:
      metadata:
        annotations: {}
        labels: {}
      template:
        ports: {}
        serviceAccount: vm-serviceaccount
      probe:
        httpGet:
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Thu Jun 15 15:02:17 UTC 2023
    - 215 bytes
    - Viewed (0)
  2. helm-releases/minio-1.0.0.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Aug 20 22:30:54 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  3. helm-releases/minio-1.0.1.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Aug 20 22:32:29 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  4. helm-releases/minio-1.0.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Aug 24 19:04:07 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  5. helm-releases/minio-1.0.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Aug 25 02:12:51 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  6. helm-releases/minio-1.0.5.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Aug 25 19:53:57 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  7. helm-releases/minio-2.0.0.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Aug 26 07:36:46 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  8. android/guava/src/com/google/common/net/InetAddresses.java

         */
        // TODO: why is this public?
        public TeredoInfo(
            @CheckForNull Inet4Address server, @CheckForNull Inet4Address client, int port, int flags) {
          checkArgument(
              (port >= 0) && (port <= 0xffff), "port '%s' is out of range (0 <= port <= 0xffff)", port);
          checkArgument(
              (flags >= 0) && (flags <= 0xffff),
              "flags '%s' is out of range (0 <= flags <= 0xffff)",
              flags);
    
    Registered: Fri Nov 01 12:43:10 UTC 2024
    - Last Modified: Sat Oct 19 00:26:48 UTC 2024
    - 47.1K bytes
    - Viewed (0)
  9. istioctl/pkg/kubeinject/testdata/mesh-config.yaml

      # CAP_NET_ADMIN capability, which is required to use TPROXY.
      #interceptionMode: REDIRECT
      #
      # Port where Envoy listens (on local host) for admin commands
      # You can exec into the istio-proxy container in a pod and
      # curl the admin port (curl http://localhost:15000/) to obtain
      # diagnostic information from Envoy. See
      # https://lyft.github.io/envoy/docs/operations/admin.html
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Thu Jun 15 15:02:17 UTC 2023
    - 2.2K bytes
    - Viewed (0)
  10. helm-releases/minio-3.5.0.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 }}...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Feb 02 00:16:41 UTC 2022
    - 15.2K bytes
    - Viewed (0)
Back to top