- Sort Score
- Num 10 results
- Language All
Results 201 - 210 of 268 for comandos (0.06 seconds)
-
helm-releases/minio-4.1.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 Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Oct 24 20:37:05 GMT 2022 - 20K bytes - Click Count (0) -
helm-releases/minio-5.1.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 Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Mar 03 18:49:37 GMT 2024 - 21.3K bytes - Click Count (0) -
helm-releases/minio-5.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 21.7K bytes - Click Count (0) -
.bazelrc
# experimental job that is build-only, i.e, we only build the test targets and # do not run them. By prefixing the configs with "build", we can run both # `bazel build` and `bazel test` commands with the same config as test configs # inherit from build. common:linux_arm64_pycpp_test_filters --test_tag_filters=-no_oss,-no_oss_py313,-tf_tosa,-no_aarch64,-oss_excluded,-oss_serial,-gpu,-tpu,-benchmark-test,-v1only
Created: Tue Dec 30 12:39:10 GMT 2025 - Last Modified: Fri Dec 26 23:20:26 GMT 2025 - 56.8K bytes - Click Count (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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Jan 08 06:24:06 GMT 2022 - 15.2K bytes - Click Count (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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jan 28 18:33:38 GMT 2022 - 15.2K bytes - Click Count (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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Feb 08 00:29:26 GMT 2022 - 15.4K bytes - Click Count (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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Oct 07 05:03:47 GMT 2021 - 14.6K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.18.md
- Kubeadm: avoid detection of the container runtime for commands that do not need it ([#97849](https://github.com/kubernetes/kubernetes/pull/97849), [@pacoxu](https://github.com/pacoxu)) [SIG Cluster Lifecycle] ## Dependencies ### Added _Nothing has changed._ ### Changed
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Wed Jun 16 17:18:28 GMT 2021 - 373.2K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.31.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 Dec 26 09:05:12 GMT 2025 - Last Modified: Wed Nov 12 11:33:21 GMT 2025 - 451.9K bytes - Click Count (0)