• Menu

    Bundlebee Integration

    Yupiik BundleBee integration module enables to ease the BundleBee manifest and layout management.

    Dependency

    <dependency>
  <groupId>io.yupiik.kubernetes</groupId>
  <artifactId>bundlebee-java</artifactId>
  <version>${kubernetes-java-descriptors.version}</version>
</dependency>

    Sample

    It is also based on descriptors and the module bundlebee-java provides you an enriched DSL to generate them easily and integrated with any version of kubernetes-java descriptors:

    // (1)
final var deployment = new Deployment()
        .metadata(new ObjectMeta()
                .name("demo-deployment"))
        .spec(new DeploymentSpec()
            .replicas(1)
            .selector(new LabelSelector()
                .matchLabels(Map.of("app", "demo")))
            .template(new PodTemplateSpec()
                .spec(new PodSpec()
                    .containers(List.of(new Container()
                        .name(name)
                        .image("nginx:1.14.2")
                        .ports(List.of(new ContainerPort()
                            .containerPort(80))))))))
        .validate();

(2)
new Manifest()
    .alveoli(List.of(
        new Alveolus() (3)
            .name("my-deployment")
            .descriptors(List.of(
                new Descriptor()
                    .name("deployment.yaml")
                    .interpolate(true)
                    .underlyingDescriptor(myDeployment) (4)
                    .validate()))
            .validate()))
    .validate()
    .writeTo(Path.of("target/bundlebee_dump")); (5)

    1. Create a deployment - or more generally a Kubernetes descriptor - with the technique seen in previous part but don’t serialize it yet,

    2. Create a manifest (BundleBee entry point),

    3. Create an alveolus (a library/application recipe in BundleBee semantic),

    4. Bind the descriptor you created to the reference BundleBee uses,

    5. Finally dump the manifest in a folder. This will create the correct BundleBee layout and if the underlyingDescriptor instance is attached and an Exportable of the kubernetes-java-$version module you use, then it will dump the descriptor as well in a single step!

    Tip
    		 don’t hesitate to create functions to instantiate the Descriptor using conventions to enforce the consistency in your deployment code. A typical case is to ame the descriptor from its underlying descriptor (reusing metadata name for example).

    Navigation