Use server-side apply for swift-ring-files ConfigMap - #1382
Conversation
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
Client-side `oc apply` writes the entire manifest into the last-applied-configuration annotation, which can exceed the limit when Swift ring files are large. Using `oc apply --server-side` avoids this annotation entirely while remaining idempotent, unlike `oc create` which would fail on retries if the resource already exists. Closes: OSPRH-25258 Co-Authored-By: Claude Opus <noreply@anthropic.com> Signed-off-by: Francesco Pantano <fpantano@redhat.com>
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
recheck |
|
@jistr are we ok merging this change? |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
19a2827
into
openstack-k8s-operators:main
4 participants
Client-side
oc applywrites the entire manifest into the last-applied-configuration annotation, which can exceed the limit when Swift ring files are large. Usingoc apply --server-sideavoids this annotation entirely while remaining idempotent, unlikeoc createwhich would fail on retries if the resource already exists.Closes: OSPRH-25258