We can use dse-k8s-codfw as a testing ground to be able to validate that the 2.8 operator works as expected, or iron out bugs we find in the wild.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T414217 ☂️Test OpenSearch k8s Operator 3.x ☂️ | |||
| Open | None | T414687 Deploy the opensearch operator 2.8.0 to dse-k8s-codfw | |||
| Open | None | T414688 Deploy a test opensearch cluster managed by operator 3.x | |||
| Open | None | T416714 OpenSearch on K8s: Create separate admin user for cluster operations | |||
| Declined | None | T414689 Deploy the opensearch operator 2.8.0 to dse-k8s-eqiad |
Event Timeline
Comment Actions
Per this Slack conversation , we have decided against using deploying the 2.8.0 operator as we know the 2.7.0 version of the operator works. Long-term, we'll run the 3.x version of the operator (ref T414217 ☂️Test OpenSearch k8s Operator 3.x ☂️). Closing...
Comment Actions
Re-opening, as using the 2.8 chart will be a requirement for OpenSearch operator 3 project
Comment Actions
@Gehel: Data-Platform-SRE (2026.01.23 - 2026.02.13) got archived and this task is still opened. Should this task get another active project tag? TIA :)