Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. Prerequisites ---------- - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using https://github.com/minio/direct-csi) - Use Kubernetes version v1.19 and later for best experience. Configure MinIO Helm repo ---------- ```bash helm repo add minio https://charts.min.io/ ``` Installing the Chart ---------- Install this chart using: ```bash helm...

Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. Prerequisites ---------- - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using https://github.com/minio/direct-csi) - Use Kubernetes version v1.19 and later for best experience. Configure MinIO Helm repo ---------- ```bash helm repo add minio https://charts.min.io/ ``` Installing the Chart ---------- Install this chart using: ```bash helm...

Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. Prerequisites ---------- - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using https://github.com/minio/direct-csi) - Use Kubernetes version v1.19 and later for best experience. Configure MinIO Helm repo ---------- ```bash helm repo add minio https://charts.min.io/ ``` Installing the Chart ---------- Install this chart using: ```bash helm...

Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. Prerequisites ---------- - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using https://github.com/minio/direct-csi) - Use Kubernetes version v1.19 and later for best experience. Configure MinIO Helm repo ---------- ```bash helm repo add minio https://charts.min.io/ ``` Installing the Chart ---------- Install this chart using: ```bash helm...

Such a set typically includes many root certificates from well-known certificate authorities like
Entrust and Verisign.

This is the behavior you'll get with your OkHttpClient if you don't specifically configure
`HandshakeCertificates`. Or you can do it explicitly with `addPlatformTrustedCertificates()`:

```java
HandshakeCertificates clientCertificates = new HandshakeCertificates.Builder()
    .addPlatformTrustedCertificates()

https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service ## #loadBalancerSourceRa: # - 10.10.10.0/24 loadBalancerSourceRa: [] ## service.externalTrafficPolic minio service external traffic policy ## ref http://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip ## externalTrafficPolic: Cluster ## Configure Ingress based on the documentation here: https://kubern...

    - how-to/custom-request-and-route.md
    - how-to/conditional-openapi.md
    - how-to/extending-openapi.md
    - how-to/separate-openapi-schemas.md
    - how-to/custom-docs-ui-assets.md
    - how-to/configure-swagger-ui.md
    - how-to/testing-database.md
- Reference (Code API):
  - reference/index.md
  - reference/fastapi.md
  - reference/parameters.md
  - reference/status.md
  - reference/uploadfile.md

    public SisuDiBridgeModule() {
        this(true);
    }

    public SisuDiBridgeModule(boolean discover) {
        this.discover = discover;
    }

    @Override
    protected void configure() {
        Provider<PlexusContainer> containerProvider = getProvider(PlexusContainer.class);
        Provider<BeanLocator> beanLocatorProvider = getProvider(BeanLocator.class);

        </field>
        <field>
          <name>alias</name>
          <version>1.0.0+</version>
          <type>String</type>
          <description>
            Specifies an alias which can be used to configure this parameter from the POM.
            This is primarily useful to improve user-friendliness, where Mojo field names are not intuitive to the
            user or are otherwise not conducive to configuration via the POM.

Plexus component. Typically this is done within Plexus with the configuration supplied with component configuration, but in Maven we take configuration values from the POM. So we have to use the ComponentConfigurator outside of Plexus in order to configure the Maven Mojo which is just a Plexus component. We can use the information from the MojoDescriptor along with the merged configuration information that is now present in the POM to create the complete PlexusConfiguration used to populate values...