[US] Buildpacks with opinionated defaults (Zero config)

[rohanKanojia]

Component

JKube Kit

Task description

Part of #439

User Story: As a user, I want to effortlessly use JKube's build goals with Buildpacks as a build strategy without needing additional configuration. This allows me to generate Kubernetes manifests using buildpack-based images.

Expected Behavior

• Using Buildpacks CLI (pack) with Pre-installed pack CLI

  • Given:
    • The user has Docker and buildpacks installed.
    • User has a Spring Boot project (created from springboot starter.io) with Maven GAV: com.acme:myspringapp:1.0.0-SNAPSHOT.
    • The user has added the kubernetes-maven-plugin.
    • jkube.build.strategy is specified as buildpacks in the pom.xml Maven properties.

    <properties>
        <jkube.build.strategy>buildpacks</jkube.build.strategy>
        [...]
    </properties>

  • When:
    • User runs mvn package k8s:build.
  • Then:
    • An image named com.acme:myspringapp:1.0.0-SNAPSHOT is available in the local Docker registry.
    • The image contains labels indicating that 'pack' was used for its creation.
  • When:
    • User runs mvn k8s:resource.
  • Then:
    • The generated deployment resource contains com.acme:myspringapp:1.0.0-SNAPSHOT for the container usage.
  • When:
    • User runs mvn k8s:apply
  • Then:
    • Then generated manifests get applied to currently logged in Kubernetes Cluster
  • Sub tasks:
    • Buildpacks CLI (pack) controller #2453
    • Buildpacks build service #2493
    • Buildpacks Maven integration #2491

• Acceptance Criteria for k8s:push

  • k8s:push/k8sPush should work with buildpacks build strategy #2464
  • Given:
    • User has build an image with k8s:build in previous step
    • User has configured image name with appropriate registry and registry username
    • User has configured registry credentials in ~/.docker/config.json or properties or ~/.m2/settings.xml
  • When:
    • User runs mvn k8s:push
  • Then:
    • Kubernetes Maven Plugin relies on Docker daemon to push the image to specified registry

• Using Buildpacks CLI (pack) without Installed CLI

  • Given:
    • The user has Docker installed.
    • The user has not installed the buildpack CLI
    • User has a Spring Boot project (created from springboot starter.io) with Maven GAV: com.acme:myspringapp:1.0.0-SNAPSHOT.
    • The user has added the kubernetes-maven-plugin.
    • jkube.build.strategy is specified as buildpacks in the pom.xml Maven properties.

    <properties>
        <jkube.build.strategy>buildpacks</jkube.build.strategy>
        [...]
    </properties>

  • When:
    • User runs mvn package k8s:build.
  • Then:
    • An image named com.acme:myspringapp:1.0.0-SNAPSHOT is available in the local Docker registry.
    • The image contains labels indicating that 'pack' was used for its creation.
  • Sub tasks:
    • Buildpacks CLI (pack) downloader #2454
    • Add utility class to decompress archive files #2456

• Acceptance Criteria for Gradle

  • Using Buildpacks CLI (pack) without Pre-installed pack CLI
  • Given:
    • The user has Docker and buildpacks installed.
    • User has a Spring Boot project (created from springboot starter.io) with Gradle GAV: com.acme:myspringapp:1.0.0-SNAPSHOT.
    • The user has added the kubernetes-gradle-plugin.
    • jkube.build.strategy is specified as buildpacks in the build.gradle Groovy DSL or gradle properties.

    jkube.build.strategy=buildpacks

  • When:
    • User runs gradle build k8sBuild.
  • Then:
    • An image named com.acme:myspringapp:1.0.0-SNAPSHOT is available in the local Docker registry.
    • The image contains labels indicating that 'pack' was used for its creation.
  • When:
    • User runs gradle k8sResource.
  • Then:
    • The generated deployment resource contains com.acme:myspringapp:1.0.0-SNAPSHOT for the container usage.
  • When:
    • User runs gradle k8sApply
  • Then:
    • Then generated manifests get applied to currently logged in Kubernetes Cluster
  • Sub tasks:
    • Buildpacks CLI (pack) controller #2453
    • Buildpacks build service #2493
  • Sub tasks:
    • Buildpacks Gradle integration #2492
  • Acceptance Criteria for k8sPush
    • k8s:push/k8sPush should work with buildpacks build strategy #2464
    • Given:
      • User has build an image with k8sBuild in previous step
      • User has configured image name with the appropriate registry and registry username
      • User has configured registry credentials in ~/.docker/config.json or properties
    • When:
      • User runs gradle k8sPush
    • Then:
      • Kubernetes Gradle Plugin relies on Docker daemon to push the image to specified registry