- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 112 for reflow (0.18 sec)
-
helm-releases/minio-4.0.3.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Jul 08 06:16:22 GMT 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-3.6.5.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Apr 13 22:45:54 GMT 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-4.0.9.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Aug 03 06:10:44 GMT 2022 - 18.6K bytes - Viewed (0) -
helm-releases/minio-4.0.11.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Aug 07 05:41:47 GMT 2022 - 19.2K bytes - Viewed (0) -
helm-releases/minio-4.1.0.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Oct 24 20:37:05 GMT 2022 - 20K bytes - Viewed (0) -
helm-releases/minio-4.0.15.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Sep 21 11:07:01 GMT 2022 - 20K bytes - Viewed (0) -
helm-releases/minio-5.0.14.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 20:46:10 GMT 2023 - 20.6K bytes - Viewed (0) -
helm-releases/minio-5.0.10.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat May 27 00:05:49 GMT 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.8.tgz
"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 }} Read more about...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 13 21:49:51 GMT 2023 - 20.3K bytes - Viewed (0) -
docs/sts/dex.yaml
expiry: signingKeys: "3h" idTokens: "3h" # Options for controlling the logger. logger: level: "debug" format: "text" # can also be "json" # Default values shown below oauth2: # use ["code", "token", "id_token"] to enable implicit flow for web-only clients responseTypes: [ "code", "token", "id_token" ] # also allowed are "token" and "id_token" # By default, Dex will ask for approval to share data with application
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jul 15 11:55:55 GMT 2020 - 2.7K bytes - Viewed (1)