OLS-3397: Add resource limits removal to deployment-lifecycle spec

[xrajesh]

Summary

• Adds resource conventions rule (11c) to the cross-repo deployment-lifecycle spec, documenting that all operator-managed container defaults follow OpenShift conventions: requests only, no limits
• Adds OLS-3397 to the Planned Changes table
• Explicitly notes RHOKP ~75 GiB ephemeral storage is unaffected

Test plan

• Spec-only change — no code affected
• Verify deployment-lifecycle.md renders correctly

🤖 Generated with Claude Code

[openshift-ci-robot]

@xrajesh: This pull request references OLS-3397 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds resource conventions rule (11c) to the cross-repo deployment-lifecycle spec, documenting that all operator-managed container defaults follow OpenShift conventions: requests only, no limits
• Adds OLS-3397 to the Planned Changes table
• Explicitly notes RHOKP ~75 GiB ephemeral storage is unaffected

Test plan

• Spec-only change — no code affected
• Verify deployment-lifecycle.md renders correctly

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.