Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 131 - 140 of 237 for below (0.01 seconds)

  1. helm-releases/minio-2.0.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: Tue Aug 31 09:09:09 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  2. 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)
  3. 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)
  4. 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)
  5. 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)
  6. doc/go_mem.html

    </p>
    
    <p>
    Examples of incorrect synchronization are given in the
    “Incorrect synchronization” section below.
    </p>
    
    <p>
    Examples of the limitations on implementations are given in the
    “Incorrect compilation” section below.
    </p>
    
    <h2 id="synchronization">Synchronization</h2>
    
    <h3 id="init">Initialization</h3>
    
    <p>
    Created: Tue Dec 30 11:13:12 GMT 2025
    - Last Modified: Tue Aug 05 15:41:37 GMT 2025
    - 26.6K bytes
    - Click Count (0)
  7. internal/logger/target/http/http.go

    		maxRetries := h.config.MaxRetry
    
    	retry:
    		// If the channel reaches above half capacity
    		// we spawn more workers. The workers spawned
    		// from this main worker routine will exit
    		// once the channel drops below half capacity
    		// and when it's been at least 30 seconds since
    		// we launched a new worker.
    		if mainWorker && len(h.logCh) > cap(h.logCh)/2 {
    			nWorkers := h.workers.Load()
    			if nWorkers < h.maxWorkers {
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Aug 29 02:39:48 GMT 2025
    - 15.6K bytes
    - Click Count (0)
  8. docs/sts/web-identity.md

    2018/12/26 17:49:36 listening on http://localhost:8080/
    ```
    
    > NOTE: for a reasonable test outcome, make sure the assumed user has at least permission/policy to list all buckets. That policy would look like below:
    
    ```
    {
      "version": "2012-10-17",
      "statement": [
        {
          "effect": "Allow",
          "action": [
            "s3:ListAllMyBuckets"
          ],
          "resource": [
            "arn:aws:s3:::*"
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 18.9K bytes
    - Click Count (0)
  9. helm-releases/minio-3.0.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: Thu Sep 02 01:47:43 GMT 2021
    - 13.8K bytes
    - Click Count (0)
  10. helm-releases/minio-3.1.3.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: Sat Sep 18 18:09:59 GMT 2021
    - 14.4K bytes
    - Click Count (0)
Back to Top