- Sort Score
- Num 10 results
- Language All
Results 211 - 220 of 289 for comandos (0.1 seconds)
-
helm-releases/minio-3.0.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Sep 02 01:47:43 GMT 2021 - 13.8K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.32.md
A security vulnerability has been discovered in Kubernetes windows nodes that could allow a user with the ability to query a node's '/logs' endpoint to execute arbitrary commands on the host. **Affected Versions**: - kubelet <= v1.29.12 - kubelet <= v1.30.8 - kubelet <= v1.31.4 - kubelet = v1.32.0 **Fixed Versions**: - kubelet 1.29.13
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Feb 26 23:58:21 GMT 2026 - 470.5K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.11.md
### SIG Cluster Lifecycle
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Feb 06 06:04:15 GMT 2020 - 328.4K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.15.md
block, continues to receive features and stability work required for bootstrapping production clusters efficiently. kubeadm has promoted high availability (HA) capability to beta, allowing users to use the familiar `kubeadm init` and `kubeadm join` commands to [configure and deploy an HA control plane](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/). An entire new test suite has been created specifically for ensuring these features will stay stable over time....
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu May 05 13:44:43 GMT 2022 - 278.9K bytes - Click Count (0) -
helm-releases/minio-5.0.11.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Jun 21 19:29:09 GMT 2023 - 20.3K bytes - Click Count (0) -
helm-releases/minio-5.0.12.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Jul 07 16:44:16 GMT 2023 - 20.4K bytes - Click Count (0) -
helm-releases/minio-5.0.13.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Jul 09 07:13:05 GMT 2023 - 20.3K bytes - Click Count (0) -
helm-releases/minio-3.6.5.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Apr 13 22:45:54 GMT 2022 - 18K bytes - Click Count (0) -
helm-releases/minio-5.0.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Mon Feb 13 10:37:23 GMT 2023 - 20.3K bytes - Click Count (0) -
helm-releases/minio-4.0.9.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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Aug 03 06:10:44 GMT 2022 - 18.6K bytes - Click Count (0)