Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for from (0.13 sec)

  1. helm-releases/minio-5.0.15.tgz

    to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Fri Jan 12 18:18:57 GMT 2024
    - 20.8K bytes
    - Viewed (0)
  2. helm-releases/minio-5.1.0.tgz

    to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Mar 03 18:49:37 GMT 2024
    - 21.3K bytes
    - Viewed (0)
  3. .github/workflows/go-fips.yml

            run: |
              GO_VERSION=$(go version | cut -d ' ' -f 3 | sed 's/go//')
              echo Detected go version $GO_VERSION
              cat > Dockerfile.fips.test <<EOF
              FROM golang:${GO_VERSION}
              COPY . /minio
              WORKDIR /minio
              ENV GOEXPERIMENT=boringcrypto
              RUN make
              EOF
    
          - name: Build
            uses: docker/build-push-action@v3
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Mar 28 23:44:49 GMT 2024
    - 1.5K bytes
    - Viewed (0)
  4. helm/minio/values.yaml

      ## This is especially handy for volume plugins that don't natively support sub mounting (like glusterfs).
      ##
      subPath: ""
    
    ## Expose the MinIO service to be accessed from outside the cluster (LoadBalancer service).
    ## or access it from within the cluster (ClusterIP service). Set the service type and the port to serve it.
    ## ref: http://kubernetes.io/docs/user-guide/services/
    ##
    service:
      type: ClusterIP
      clusterIP: ~
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Apr 28 10:14:37 GMT 2024
    - 18.4K bytes
    - Viewed (0)
  5. helm/minio/templates/networkpolicy.yaml

          release: {{ .Release.Name }}
      ingress:
        - ports:
            - port: {{ .Values.minioAPIPort }}
            - port: {{ .Values.minioConsolePort }}
          {{- if not .Values.networkPolicy.allowExternal }}
          from:
            - podSelector:
                matchLabels:
                  {{ template "minio.name" . }}-client: "true"
          {{- end }}
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Wed Jan 24 07:27:57 GMT 2024
    - 819 bytes
    - Viewed (0)
  6. helm-releases/minio-5.2.0.tgz

    to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Apr 28 10:14:37 GMT 2024
    - 21.7K bytes
    - Viewed (0)
Back to top