Add the ability to control cpu and memory resources from top level Wildfly YAML

[seeker25]

Currently it defaults to what the namespace defaults are. I believe this is under control of a cluster admin?

$ oc describe limits default-limits
Name: default-limits
Namespace: xxxxx
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio

---

Container cpu - - 50m 250m -
Container memory - - 256Mi 1Gi -

As a work around I've had to do an OC patch to set the StatefulSet resources:

oc patch statefulset xxx -p '{"spec": {"template": {"spec": {"containers": [{"name": "xxx", "resources": {"limits": {"cpu": "1000m","memory": "1Gi"}}}]}}}}'

I figured the storage is already on there, why not have the CPU and memory as well for each replica?

https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/index#wildflyserverspec_default

Wouldn't it be possible to pass down from WildFlySpec / WildFlyServerSpec to the StatefulSet here?:

wildfly-operator/pkg/resources/statefulsets/statefulset.go

Line 87 in 6aba9ae

Containers: []corev1.Container{{

[danbigthink]

Currently it defaults to what the namespace defaults are. I believe this is under control of a cluster admin?

$ oc describe limits default-limits
Name: default-limits
Namespace: xxxxx
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio

Container cpu - - 50m 250m -
Container memory - - 256Mi 1Gi -

As a work around I've had to do an OC patch to set the StatefulSet resources:

oc patch statefulset xxx -p '{"spec": {"template": {"spec": {"containers": [{"name": "xxx", "resources": {"limits": {"cpu": "1000m","memory": "1Gi"}}}]}}}}'

I figured the storage is already on there, why not have the CPU and memory as well for each replica?

https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/index#wildflyserverspec_default

Wouldn't it be possible to pass down from WildFlySpec / WildFlyServerSpec to the StatefulSet here?:

wildfly-operator/pkg/resources/statefulsets/statefulset.go

Line 87 in 6aba9ae

Containers: []corev1.Container{{

I love this idea and would find it useful so I don't have to do extra work!
A great example of this is in openfaas faas-netes github repo
https://github.com/openfaas/faas-netes#configuration-of-the-controller

[BobVanB]

Maybe something like:
#212 Add support for resources on the Stateful Set

[jmesnil]

Fixed in #215