Use maven repository to store helm charts. This has three goals:

1. Package helm chart and add as a secondary artifact for build
2. Upgrade (install) helm chart release(s)
3. Uninstall helm chart release(s)

Deploy your containers using helm charts to docker desktop or minikube for integration testing. Build the containers using docker-maven-plugin, jib, or buildpacks. Start k8s pods/deployments/services during pre-integration-test phase. Use failsafe to run integration tests during integration-test phase. Capture logs and uninstall k8s pods/deployments/services during the post-integration-test phase.

Plugin reports available at plugin info.

The upgrade goal binds by default to the pre-integration-test phase. This goal will execute helm upgrade --install for each release. If the release name is not specified, the name will be derived from the chart name.

A chart name can be any of the following:

1. Maven GAV coordinate: org.honton.chas:test-reports:1.3.4
2. URL: https://​repo.maven.apache.org/maven2/org/honton/chas/test-reports/1.3.4/test-reports-1.3.4.tgz
3. Path to an unpacked chart directory: src/helm/superfantastic
4. Path to a packaged chart: superfantastic-44.12.3.tgz
5. Chart reference: repository/chartname
6. OCI registry URL: oci://example.com/charts/nginx

Kubernetes has a network mapping of host ports to pod ports. During integration test, we need to use the host port instead of the target port. With NodePort and LoadBalancer service types, the nodePort is unlikely to equal targetPort value. After each release is upgraded, the upgrade goal will set specified maven properties to the assigned nodePort values.

Each element of nodeports is of form [namespace/]name[:port]. The name is required. The namespace and port are optional. The name will match the Service's metadata. The port will match either the ServicePortname or port.

The uninstall goal binds by default to the post-integration-test phase. This goal will capture the logs from specified pods and execute helm uninstall for each release. Configuration is similar to the install goal; except the valueYaml, valueFile, and nodePorts parameters are ignored.

Before uninstalling a release, this goal captures the logs of any specified pods to the podLogs directory. Each element of logs is of form [namespace/]name. The name is required. The namespace is optional. These are used to match the Pod's metadata.

The template goal binds by default to the verify phase. This goal will expand the chart source. Content will be filtered using maven properties. Parameters are same as for the upgrade goal with the addition of the following:

The package goal binds by default to the package phase. This goal will create a helm package from the chart source. Content will be filtered using maven properties. Resulting .tgz artifact is attached as a secondary artifact for the build. The helm package will be installed in the local maven repository during the install phase and deployed to the remote maven repository during the deploy phase.

The chart within helmDir must equal ${project.artifactId}.

This plugin can also be used as an extension that packages, installs, and deploys the tgz packaging type. Just set the top level element to tgz and register this plugin as an extension.

<build>
  <pluginManagement>
    <plugins>
      <plugin>
        <groupId>org.honton.chas</groupId>
        <artifactId>helmrepo-maven-plugin</artifactId>
        <version>0.0.3</version>
      </plugin>
    </plugins>
  </pluginManagement>

  <plugins>
    <plugin>
      <groupId>org.honton.chas</groupId>
      <artifactId>helmrepo-maven-plugin</artifactId>
      <executions>
        <execution>
          <goals>
            <goal>package</goal>
            <goal>upgrade</goal>
            <goal>uninstall</goal>
          </goals>
        </execution>
      </executions>
      <configuration>
        <valueYaml><![CDATA[
name: globalValue
]]>
        </valueYaml>
        <releases combine.children="append">
          <release>
            <chart>org.honton.chas:test-reports:1.3.4</chart>
            <valueYaml><![CDATA[
name: releaseValue
nested:
  list:
  - one
  - two
]]>
            </valueYaml>
            <nodePorts>
              <nodePort>
                <portName>http</portName>
                <propertyName>report.port</propertyName>
                <serviceName>test-reports</serviceName>
              </nodePort>
            </nodePorts>
            <logs>
              <pod>test</pod>
              <pod>report</pod>
            </logs>
          </release>
          <release>
            <name>report-job</name>
            <namespace>report</namespace>
            <requires>test-reports</requires>
            <chart>src/helm/${project.artifactId}</chart>
          </release>
        </releases>
      </configuration>
    </plugin>
  </plugins>
</build>

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.example.helm</groupId>
  <artifactId>chart</artifactId>
  <packaging>tgz</packaging>

  <build>
    <extensions>
      <extension>
        <groupId>org.honton.chas</groupId>
        <artifactId>helmrepo-maven-plugin</artifactId>
        <version>0.0.2</version>
      </extension>
    </extensions>
  </build>

</project>

If the package goal fails with the following error, your chart directory is probably empty.

[ERROR] Failed to execute goal org.honton.chas:helmrepo-maven-plugin:0.0.3:package (tutorial) on project tutorial: Execution tutorial of goal org.honton.chas:helmrepo-maven-plugin:0.0.3:package failed: archive cannot be empty -> [Help 1]