- Sort Score
- Num 10 results
- Language All
Results 271 - 280 of 408 for below (0.02 seconds)
-
helm-releases/minio-3.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 12 18:19:27 GMT 2021 - 14.3K bytes - Click Count (0) -
helm-releases/minio-3.1.1.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Sep 13 16:43:10 GMT 2021 - 14.3K bytes - Click Count (0) -
helm-releases/minio-3.1.6.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Sep 23 19:56:39 GMT 2021 - 14.5K bytes - Click Count (0) -
doc/go_spec.html
<!-- ul below only for regular layout --> <ul> </ul> </li> <li> A call to the built-in function <a href="#Handling_panics"><code>panic</code></a>. <!-- ul below only for regular layout --> <ul> </ul> </li> <li> A <a href="#Blocks">block</a> in which the statement list ends in a terminating statement. <!-- ul below only for regular layout --> <ul> </ul>
Created: Tue Dec 30 11:13:12 GMT 2025 - Last Modified: Tue Dec 02 23:07:19 GMT 2025 - 286.5K bytes - Click Count (1) -
helm-releases/minio-3.5.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Feb 02 00:16:41 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.5.1.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Feb 04 22:54:20 GMT 2022 - 15.4K bytes - Click Count (0) -
helm-releases/minio-3.1.7.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Oct 03 22:23:22 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.3.1.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Dec 02 20:09:18 GMT 2021 - 14.6K bytes - Click Count (0) -
docs/en/docs/tutorial/bigger-applications.md
#### How relative imports work { #how-relative-imports-work } /// tip If you know perfectly how imports work, continue to the next section below. /// A single dot `.`, like in: ```Python from .dependencies import get_token_header ``` would mean:Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 10 08:55:32 GMT 2025 - 18.6K bytes - Click Count (0) -
tensorflow/c/c_api_experimental.cc
// Update the vector with information from `input_tensors` if provided. if (input_tensors != nullptr) { // Note that we take the address of the elements in `all_input_tensors` // below. Allocate enough space so that no reallocation happens, which will // make the pointers invalid. all_input_tensors.reserve(num_inputs); for (int i = 0; i < num_inputs; ++i) {
Created: Tue Dec 30 12:39:10 GMT 2025 - Last Modified: Sat Oct 04 05:55:32 GMT 2025 - 29.4K bytes - Click Count (0)