Ability to declare Kubernetes resources requests and limits through properties

[yanaga]

Description
Kubernetes allows to specify how much resources (memory and cpu) a container needs to be executed. In addition to this, Kubernetes also allows you to enforce a limit on the amount of resources (again memory and cpu) that a container can use.

This information can be provided inside the following structure in the following yaml excerpt:

    spec:
      containers:
        image: quay.io/myrepo/myapp:1.0.0-SNAPSHOT
        imagePullPolicy: Always
        resources:
          requests:
            memory: "64Mi"
            cpu: "250m"
          limits:
            memory: "512Mi"
            cpu: "1000m"

It'd be nice if the quarkus-kubernetes extension could generate these information using some properties. A proposed name and usage for these properties is:

quarkus.kubernetes.resources.requests.memory=64Mi
quarkus.kubernetes.resources.requests.cpu=250m
quarkus.kubernetes.resources.limits.memory=512Mi
quarkus.kubernetes.resources.limits.cpu=1000m

[quarkusbot]

/cc @geoand

[geoand]

@iocanel we have this capability in dekorate right? So we just need to expose it here

[mkonzal]

Is a dedicated issue for the OpenShift extension needed?

[geoand]

Nope, introducing the feature would be done generally

[yanaga]

I can see that in dekorate you can declare the information with these properties:

dekorate.kubernetes.request-resources.cpu=1m
dekorate.kubernetes.request-resources.memory=64Mi
dekorate.kubernetes.limit-resources.cpu=5m
dekorate.kubernetes.limit-resources.memory=256Mi

And for OpenShift, it's:

dekorate.openshift.request-resources.cpu=1m
dekorate.openshift.request-resources.memory=64Mi
dekorate.openshift.limit-resources.cpu=5m
dekorate.openshift.limit-resources.memory=256Mi

[geoand]

Right, so we just need to expose it to the Quarkus config system.

@iocanel do you want to take this one?

[missourian55]

Appreciate guys, just tested this with 1.10.0.CR1 works great

[yanaga]

Reporting that I also tested it today and works great too!

[geoand]

Thanks for testing and reporting back folks!