- Sort Score
- Result 10 results
- Languages All
Results 171 - 180 of 250 for comandos (0.05 sec)
-
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
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Tue Dec 16 18:27:41 UTC 2025 - 448.1K bytes - Viewed (0) -
helm-releases/minio-3.4.6.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 Jan 08 06:24:06 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.4.8.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 Jan 28 18:33:38 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.5.2.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 Feb 08 00:29:26 UTC 2022 - 15.4K bytes - Viewed (0) -
helm-releases/minio-3.1.8.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 Oct 07 05:03:47 UTC 2021 - 14.6K bytes - Viewed (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....
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Thu May 05 13:44:43 UTC 2022 - 278.9K bytes - Viewed (0) -
helm-releases/minio-5.0.6.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: Mon Feb 13 06:53:06 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-4.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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Aug 07 05:41:47 UTC 2022 - 19.2K bytes - Viewed (0) -
helm-releases/minio-4.0.2.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: Mon May 09 04:25:47 UTC 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-4.0.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: Fri Jul 08 06:16:22 UTC 2022 - 18K bytes - Viewed (0)