- Sort Score
- Result 10 results
- Languages All
Results 81 - 90 of 552 for lport (0.03 sec)
-
helm-releases/minio-3.1.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: Thu Sep 23 19:56:39 UTC 2021 - 14.5K bytes - Viewed (0) -
helm-releases/minio-5.0.8.tgz
[] ## 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 external port number minioConsolePort: "9001" ## Update strategy for Deployments DeploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Apr 13 21:49:51 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.9.tgz
[] ## 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 external port number minioConsolePort: "9001" ## Update strategy for Deployments deploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed May 03 06:23:26 UTC 2023 - 20.2K bytes - Viewed (0) -
helm-releases/minio-5.0.10.tgz
[] ## 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 external port number minioConsolePort: "9001" ## Update strategy for Deployments deploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat May 27 00:05:49 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.2.tgz
[] ## 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 external port number minioConsolePort: "9001" ## Update strategy for Deployments DeploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Dec 18 07:57:10 UTC 2022 - 20.4K bytes - Viewed (0) -
helm-releases/minio-3.1.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: Sun Oct 10 21:28:04 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.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 Nov 25 17:33:26 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.4.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: Sun Dec 19 22:32:49 UTC 2021 - 14.8K bytes - Viewed (0) -
helm-releases/minio-3.4.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: Mon Dec 20 21:11:50 UTC 2021 - 15.2K bytes - Viewed (0) -
architecture/ambient/ztunnel.md
* It is critical that this path preserves the Service IP, if the traffic was to a Service. * All traffic *ingressing* a pod on port 15008 in the mesh is assumed to be HBONE, and should be redirected to the node-local ztunnel on port 15008 (more on this later).
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 16.8K bytes - Viewed (0)