- Sort Score
- Result 10 results
- Languages All
Results 161 - 170 of 969 for Port (0.02 sec)
-
src/main/java/jcifs/util/PathValidator.java
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 30 05:58:03 UTC 2025 - 14.5K bytes - Viewed (0) -
internal/config/errors.go
) ErrPortAlreadyInUse = newErrFn( "Port is already in use", "Please ensure no other program uses the same address/port", "", ) ErrPortAccess = newErrFn( "Unable to use specified port", "Please ensure MinIO binary has 'cap_net_bind_service=+ep' permissions",
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 9.4K bytes - Viewed (0) -
cmd/common-main.go
server.Host = globalMinioConsoleHost server.Port = consolePort consoleapi.Port = globalMinioConsolePort consoleapi.Hostname = globalMinioConsoleHost if globalIsTLS { // If TLS certificates are provided enforce the HTTPS. server.EnabledListeners = []string{"https"} server.TLSPort = consolePort // Need to store tls-port, tls-host un config variables so secure.middleware can read from thereRegistered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 32.5K bytes - Viewed (3) -
helm-releases/minio-4.1.0.tgz
## Additional volumes to minio container extraVolumes: [] ## Additional volumeMounts to minio container extraVolumeMounts: [] ## 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 Dec 28 19:28:13 UTC 2025 - Last Modified: Mon Oct 24 20:37:05 UTC 2022 - 20K 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 Dec 28 19:28:13 UTC 2025 - 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 Dec 28 19:28:13 UTC 2025 - 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 Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 24 19:04:07 UTC 2021 - 13.6K bytes - Viewed (0) -
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 Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Aug 25 02:12:51 UTC 2021 - 13.6K bytes - Viewed (0) -
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 Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Aug 25 19:53:57 UTC 2021 - 13.6K bytes - Viewed (0) -
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 Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Aug 26 07:36:46 UTC 2021 - 13.6K bytes - Viewed (0)