janhoy commented on PR #887:
URL: https://github.com/apache/solr-operator/pull/887#issuecomment-6727996225

   PR updated with @dsmiley's latest improvements to the solr workflow. Tuned 
the assessments on some more read PRs. Here is the new output on the same PR 
#843 as below (table output):
   
   **Automated PR readiness judgements** (LLM-generated; may be wrong; not 
updated on later pushes).
   
   - ⚠️ [Operator chart 
changelog](https://github.com/apache/solr-operator/blob/main/helm/solr-operator/Chart.yaml)
 **— missing** (suggest added): The PR introduces a new opt-in external 
addressability method `Gateway` (new CRD fields in 
api/v1beta1/solrcloud_types.go) and new controller logic to 
manage HTTPRoute and BackendTLSPolicy resources, which is a new capability 
for users.
   - ✅ [Chart README values 
table](https://github.com/apache/solr-operator/blob/main/helm/solr-operator/README.md#chart-values):
 not needed <!-- The changes add RBAC rules to the Helm chart&#39;s 
role&#46;yaml but do not add&#44; rename&#44; or change any Helm chart values 
in helm&#47;solr&#45;operator or helm&#47;solr&#46; -->
   - ✅ [User 
documentation](https://github.com/apache/solr-operator/tree/main/docs/modules): 
included <!-- New CRD fields 
&#40;spec&#46;solrAddressability&#46;external&#46;method&#61;Gateway&#44; 
spec&#46;solrAddressability&#46;external&#46;gateway&#41; and their behavior 
&#40;HTTPRoute&#47;BackendTLSPolicy management&#41; are user&#45;facing 
features that require documentation in docs&#47;modules&#46; -->
   - ⚠️ [Upgrade 
notes](https://github.com/apache/solr-operator/blob/main/docs/modules/upgrade-notes/pages/upgrade-notes.adoc)
 **— missing**: The operator requires new RBAC permissions for 
gateway&#46;networking&#46;k8s&#46;io resources &#40;httproutes&#44; 
backendtlspolicies&#41;&#44; which users managing RBAC themselves must add&#44; 
and the PR upgrades dependencies &#40;Go&#44; Kubernetes libraries&#44; 
controller&#45;runtime&#41; which may have implications for the operator&#39;s 
runtime environment&#46;
   - ✅ 
[Tests](https://github.com/apache/solr-operator/blob/main/docs/modules/development/pages/development.adoc#testing):
 included <!-- The PR adds significant new Go logic in controllers&#47; 
&#40;solr&#95;gateway&#95;util&#46;go&#44; gateway&#95;util&#46;go&#44; 
gateway&#95;util&#95;backendtls&#46;go&#41; and modifies the reconciler&#44; 
which warrants new or changed tests in the envtest unit tests or e2e tests&#46; 
-->
   - ✅ [CRD option 
completeness](https://github.com/apache/solr-operator/blob/main/docs/modules/solr-cloud/pages/solr-cloud-crd.adoc):
 no concern <!-- The new CRD fields are wired through to the controllers 
&#40;reconcileGatewayResources&#41;&#44; have appropriate doc comments and 
kubebuilder markers&#44; and use pointers where &#39;unset&#39; vs 
&#39;zero&#39; matters&#46; The solr Helm chart does not need to expose this as 
it is a SolrCloud spec option&#44; not a chart value&#46; -->
   - ⚠️ [Version 
compatibility](https://github.com/apache/solr-operator/blob/main/docs/modules/upgrade-notes/pages/upgrade-notes.adoc#version-compatibility-matrixes)
 **— please check**: The PR requires Gateway API v1&#46;4&#46;0&#43; for 
BackendTLSPolicy GA support and upgrades to Go 1&#46;24&#46;0&#43; and 
Kubernetes libraries v0&#46;34&#46;1&#44; which may not be available across the 
entire supported range &#40;Kubernetes 1&#46;22&#43;&#41;&#46;
   - ✅ Testing notes: no concern <!-- The PR description explicitly states that 
e2e tests were added 
&#40;tests&#47;e2e&#47;solrcloud&#95;gateway&#95;test&#46;go&#41; and manual 
testing was performed with kgateway on Kubernetes 1&#46;32&#44; verifying 
backward compatibility and TLS backend connections&#46; -->
   
   <!-- Assessed commit 3c472c71da7403522cb2c81d5ea96e09f5eb8b62 -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to