From ba785be0acd34a5899fe245278fb63cf9156850b Mon Sep 17 00:00:00 2001 From: Nour Date: Wed, 18 Mar 2026 05:17:28 +0200 Subject: [PATCH] Drop CSR analogy, mark ObjectMeta +required,reduce limits (maxItems=500, maxLength=128) for etcd safety, add Errors printer column Signed-off-by: Nour Kubernetes-commit: 8b9159baa41418bcc62592e9da3b878e7cd138ca --- .../resource/v1alpha3/resourcepoolstatusrequest.go | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/applyconfigurations/resource/v1alpha3/resourcepoolstatusrequest.go b/applyconfigurations/resource/v1alpha3/resourcepoolstatusrequest.go index 4ccbabc97..aee4d0ed9 100644 --- a/applyconfigurations/resource/v1alpha3/resourcepoolstatusrequest.go +++ b/applyconfigurations/resource/v1alpha3/resourcepoolstatusrequest.go @@ -31,11 +31,8 @@ import ( // with apply. // // ResourcePoolStatusRequest triggers a one-time calculation of resource pool status -// based on the provided filters. The request follows a request/response pattern similar -// to CertificateSigningRequest - create a request, and the controller populates the status. -// -// Once status is set, the request is considered complete and will not -// be reprocessed. Users should delete and recreate requests to get updated information. +// based on the provided filters. Once status is set, the request is considered complete and will not be reprocessed. +// Users should delete and recreate requests to get updated information. type ResourcePoolStatusRequestApplyConfiguration struct { v1.TypeMetaApplyConfiguration `json:",inline"` // Standard object metadata