- Sort Score
- Result 10 results
- Languages All
Results 221 - 230 of 250 for comandos (0.05 sec)
-
helm-releases/minio-3.2.0.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Oct 13 02:16:24 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.3.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Dec 11 17:28:02 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.4.7.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Jan 25 20:49:24 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.5.0.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Feb 02 00:16:41 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.5.1.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Feb 04 22:54:20 UTC 2022 - 15.4K bytes - Viewed (0) -
helm-releases/minio-3.1.7.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Oct 03 22:23:22 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.1.tgz
"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 port...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Dec 02 20:09:18 UTC 2021 - 14.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.14.md
* kubeadm: use the default kubeconfig (/etc/kubernetes/admin.conf) for "kubeadm reset" and "kubeadm upgrade" commands.
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Mon Jun 14 22:06:39 UTC 2021 - 271.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.9.md
* Add flag "--include-uninitialized" to kubectl annotate, apply, edit-last-applied, delete, describe, edit, get, label, set. "--include-uninitialized=true" makes kubectl commands apply to uninitialized objects, which by default are ignored if the names of the objects are not provided. "--all" also makes kubectl commands apply to uninitialized objects. Please see the [initializer](https://kubernetes.io/docs/admin/extensible-admission-controllers/) doc for more details. ([#50497](https://githu...
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Tue Nov 16 10:46:27 UTC 2021 - 313.7K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.34.md
- `kubectl create|delete|get|replace --raw` commands now honored the server root paths specified in the kubeconfig file. ([#131165](https://github.com/kubernetes/kubernetes/pull/131165), [@liggitt](https://github.com/liggitt)) ### Other (Cleanup or Flake)
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Wed Dec 10 01:13:50 UTC 2025 - 333.3K bytes - Viewed (1)