younsl opened a new pull request, #452: URL: https://github.com/apache/superset-kubernetes-operator/pull/452
## Summary The internals page still shows status fields that the API no longer has, plus two smaller wording mistakes. The parent status example lists ready and ref on component entries and ref on the migrate task, but ComponentRefStatus and TaskRefStatus have neither field. A reader who compares the example with kubectl output looks for fields that are never set. This PR brings the page in line with the API and the code. It changes docs only. ## Details - Parent status example: removed ready and ref from the component entries and ref from the migrate entry. The Celery worker and beat entries now show replicas and readyReplicas, which ComponentRefStatus does have. The top-level ready field stays, since SupersetStatus still has it. - Status Aggregation: "ready count, replica details" becomes "replica counts", matching the same change. - DeploymentConfig snippet: the ContainerName comment said "superset-web-server". Every component uses the reserved container name superset (common.Container), so the comment now says that. - Ingress, HTTPRoute, ServiceMonitor and NetworkPolicy were called cluster-scoped. They are all namespaced and belong to one Superset instance, so the sentence now calls them instance-level resources. <details> <summary>Verification</summary> - Field lists checked against SupersetStatus, ComponentRefStatus and TaskRefStatus in api/v1alpha1/superset_types.go, and container names against ComponentResourceDefs in internal/controller/component_resources.go. - make lint-md passes. - mkdocs build in strict mode passes with the pinned docs requirements. </details> -- 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]
