Duplicate entries in deployment yaml with gradle plugin

[manojvignesh]

I've the below gradle config

kubernetes {
    images {
        image {
            name = "..."
        }
    }
    resources {
        namespace = '...'
    }
    enricher {
        config {
            'jkube-prometheus' {
                prometheusPath = '/actuator/prometheus'
                prometheusPort = 8080
            }
            'jkube-healthcheck-spring-boot' {
                failureThreshold = '10'
            }
        }
    }
}

with this under spec.template.spec.containers I'm getting two entries for same image.
If I remove the images block, it generates only one image entry.

      containers:
      - env:
        - name: KUBERNETES_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: HOSTNAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        image: ...
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 10
          httpGet:
            path: /actuator/health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 180
          successThreshold: 1
        name: spring-boot
        ports:
        - containerPort: 8080
          name: http
          protocol: TCP
        - containerPort: 9779
          name: prometheus
          protocol: TCP
        - containerPort: 8778
          name: jolokia
          protocol: TCP
        readinessProbe:
          failureThreshold: 10
          httpGet:
            path: /actuator/health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 10
          successThreshold: 1
        securityContext:
          privileged: false
      - env:
        - name: HOSTNAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        image: ...
        imagePullPolicy: Always
        livenessProbe:
          failureThreshold: 10
          httpGet:
            path: /actuator/health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 180
          successThreshold: 1
        name: spring-boot
        readinessProbe:
          failureThreshold: 10
          httpGet:
            path: /actuator/health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 10
          successThreshold: 1

[rohanKanojia]

@manojvignesh : Is your Image configuration complete? I think plugin is trying to create opinionated image itself because it doesn't see full image configuration (requires build section where you specify things like from, entrypoint etc).

Do you just want to configure image name? You can do it using jkube.generator.name property.

[manojvignesh]

In this case the images.image.name was actually ignored. But it inserts a duplicate entry with default name.
If I add images.image.build.from along with the above provided one, then it creates only one entry with correct name.
The problem being it doesn't have some ports exposed.

    spec:
      containers:
      - env:
        - name: KUBERNETES_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: HOSTNAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        image: ...
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 10
          httpGet:
            path: /actuator/health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 180
          successThreshold: 1
        name: ...
        readinessProbe:
          failureThreshold: 10
          httpGet:
            path: /actuator/health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 10
          successThreshold: 1
        securityContext:
          privileged: false

can't I use them both together? images and other configs?

[rohanKanojia]

could you please elaborate a bit on your use case? It will help us in understanding your problem and providing applicable solutions.

[rohanKanojia]

You can use them both together but for images you need to provide complete config (for example, quickstarts/gradle/groovy-dsl-config/build.gradle)

[manojvignesh]

I just want to customize two things under image:

1. The image.name so that I point it to pull from aws ECR
2. Base image build.from so I can use java 11 instead of the default 17.

        image {
            name = "xxx.dkr.ecr.us-east-1.amazonaws.com/xxx:latest"
            build {
                from = "quay.io/jkube/jkube-java:0.0.11"
            }
        }

I just want to use the default for other configs.

I'd skip this if there are better ways to do the above two steps.

[rohanKanojia]

I think you should be able to do it using jkube.generator.name and jkube.generator.from properties

[manojvignesh]

Thanks a lot. That did the trick.

So these are system properties which I'm passing as -Djkube.generator.name=xxx.dkr.ecr.us-east-1.amazonaws.com/xxx:latest -Djkube.generator.from=quay.io/jkube/jkube-java:0.0.11 to k8sResource task and it works.

Is there a better way of passing this? Like in application.yaml or build.gradle?

[rohanKanojia]

@manojvignesh : Are you using a Spring Boot application? I think you can either specify these properties ingradle.properties file or provide Spring boot opinionated config like this:

    generator {
        config {
            'spring-boot' {
                name = 'xxx.dkr.ecr.us-east-1.amazonaws.com/xxx:latest'
                from = 'quay.io/jkube/jkube-java:0.0.11'
            }
        }
    }

[manojvignesh]

yes, I'm using spring boot. and with this config I'm getting the same result like system properties.

Thanks.