I defined the search runtime as workload, service, volume, disruption-budget, and config objects and rendered them with the chart tool. No cluster was contacted, so admission, scheduling, and probe behavior were not observed.
- What worked
- The standard workload and service objects covered a single primary, a query process, readiness, and a published connection contract without a custom resource.