Add configurable container resource requests and limits via CR spec

[omkarjoshi0304]

Summary

This adds a spec.resources field to the OpenStackLightspeed CR that accepts per-container corev1.ResourceRequirements overrides following the same pattern used by other openstack-k8s-operators (e.g. test-operator). Defaults are declared via kubebuilder:default markers on the API types, so the API server sets them automatically — no fallback logic needed in the controllers.

How it works

• Add ContainerResourcesSpec struct with kubebuilder:default markers encoding the previous hardcoded values for each container
• Controllers read instance.Spec.Resources directly — no nil checks or resolve helpers needed since the API server guarantees defaults
• Update sample CR with commented-out resource override examples
• Regenerate CRD manifests and deepcopy methods

Example CR

spec:
  resources:
    llamaStack:
      requests:
        cpu: "2"
        memory: "8Gi"
      limits:
        cpu: "8"
        memory: "32Gi"
    postgres:
      requests:
        cpu: "100m"
        memory: "512Mi"
      limits:
        cpu: "1"
        memory: "4Gi"

Test Proof

[cloud-user@ojoshi-rhoso-lightspeed ~]$ oc patch openstacklightspeed openstack-lightspeed -n openstack-lightspeed --type=merge -p '{"spec": {"resources": {"llamaStack": {"requests": {"cpu": "1", "memory": "4Gi"}, "limits": {"cpu": "4", "memory": "16Gi"}}, "lightspeedService": {"requests": {"cpu": "500m", "memory": "1Gi"}, "limits": {"cpu": "2", "memory": "4Gi"}}, "postgres": {"requests": {"cpu": "100m", "memory": "512Mi"}, "limits": {"cpu": "1", "memory": "4Gi"}}}}}'
openstacklightspeed.lightspeed.openstack.org/openstack-lightspeed patched
[cloud-user@ojoshi-rhoso-lightspeed ~]$ echo "=== llama-stack ==="
oc get deployment lightspeed-stack-deployment -n openstack-lightspeed \
  -o jsonpath='{.spec.template.spec.containers[?(@.name=="llama-stack")].resources}' | \
  python3 -m json.tool
=== llama-stack ===
{
    "limits": {
        "cpu": "4",
        "memory": "16Gi"
    },
    "requests": {
        "cpu": "1",
        "memory": "4Gi"
    }
}
[cloud-user@ojoshi-rhoso-lightspeed ~]$ echo "=== lightspeed-service-api ==="
oc get deployment lightspeed-stack-deployment -n openstack-lightspeed \
  -o jsonpath='{.spec.template.spec.containers[?(@.name=="lightspeed-service-api")].resources}' | \
  python3 -m json.tool
=== lightspeed-service-api ===
{
    "limits": {
        "cpu": "2",
        "memory": "4Gi"
    },
    "requests": {
        "cpu": "500m",
        "memory": "1Gi"
    }
}
[cloud-user@ojoshi-rhoso-lightspeed ~]$ echo "=== postgres ==="
oc get deployment lightspeed-postgres-server -n openstack-lightspeed \
  -o jsonpath='{.spec.template.spec.containers[0].resources}' | \
  python3 -m json.tool
=== postgres ===
{
    "limits": {
        "cpu": "1",
        "memory": "4Gi"
    },
    "requests": {
        "cpu": "100m",
        "memory": "512Mi"
    }
}
[cloud-user@ojoshi-rhoso-lightspeed ~]$ 

[omkarjoshi0304]

/retest

[omkarjoshi0304]

/retest

[lpiwowar]

Just very quickly skimmed through it and there is one thing that crossed my mind we should try IMO but overall I like the PR 👍.

[omkarjoshi0304]

/retest

[omkarjoshi0304]

/retest

[umago]

Change overall looks fine. I think the version bumps and the Init containers at least we should think a bit more before exposing it.

The version bumps looks unrelated to the change (and should at least be on it's own commit). And the Init containers seems like a leak from internal implementation to CR.

[omkarjoshi0304]

/retest

[umago]

Thanks Omkar! It /lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: omkarjoshi0304, umago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [umago]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[umago]

/lgtm