- Sort Score
- Result 10 results
- Languages All
Results 191 - 200 of 552 for lport (0.03 sec)
-
src/main/webapp/WEB-INF/view/admin/fileauth/admin_fileauth_details.jsp
<tr> <th><la:message key="labels.file_auth_port"/></th> <td>${f:h(port)}<la:hidden property="port"/></td> </tr> <tr> <th><la:message key="labels.file_auth_scheme"/></th>
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Thu Feb 13 07:47:04 UTC 2020 - 6.2K bytes - Viewed (0) -
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) -
helm-releases/minio-5.2.0.tgz
[] # example for enabling FTP: # - --ftp=\"address=:8021\" # - --ftp=\"passive-port-range=10000-10010\" ## Additional volumes to minio container extraVolumes: [] ## Additional volumeMounts to minio container extraVolumeMounts: [] ## Additional sidecar containers extraContainers: [] ## Internal port number for MinIO S3 API container ## Change service.port to change external port number minioAPIPort: "9000" ## Internal port number for MinIO Browser Console container ## Change consoleService.port to change...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Apr 28 10:14:37 UTC 2024 - 21.7K bytes - Viewed (0) -
helm-releases/minio-3.5.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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Feb 19 20:34:14 UTC 2022 - 17.6K bytes - Viewed (0) -
helm-releases/minio-3.5.9.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 Mar 03 23:29:03 UTC 2022 - 17.7K bytes - Viewed (0) -
common-protos/k8s.io/api/core/v1/generated.proto
optional string name = 1; } // PodPortForwardOptions is the query options to a Pod's port forward call // when using WebSockets. // The `port` query parameter must specify the port or // ports (comma separated) to forward over. // Port forwarding over SPDY does not use these options. It requires the port // to be passed in the `port` header as part of request. message PodPortForwardOptions { // List of ports to forward
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 255.8K bytes - Viewed (0) -
tensorflow/c/eager/parallel_device/parallel_device_remote_test.cc
job_def->set_name(job_name); for (int i = 0; i < num_tasks; i++) { int port = tensorflow::testing::PickUnusedPortOrDie(); job_def->mutable_tasks()->insert( {i, tensorflow::strings::StrCat("localhost", ":", port)}); LOG(INFO) << "Picked test port: " << port << " for job: " << job_name << ", task: " << i; } return server_def; } namespace tensorflow {
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Jul 10 07:18:05 UTC 2024 - 6.8K bytes - Viewed (0) -
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) -
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) -
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)