Page MenuHomePhabricator

Deploy opensearch-k8s-operator 2.8.0 to the dse-k8s Kubernetes clusters
Closed, DeclinedPublic

Description

We are currently running opensearch-k8s-operator 2.7.0 + a custom patch to support the watching of multiple k8s namespaces. We need to run the 2.8.0 version to support opensearch 3.x.

Event Timeline

brouberol triaged this task as Medium priority.

The compatibility matrix for OpenSearch versions is here . However, the matrix is missing a third column: chart version. Let me explain.

We are currently running the 2.7.0 version of the operator, and the 2.7.0 version of the chart. The chart was refactored between 2.7.0 and 2.8.0, which means we'd have to pull in a new version of the chart and do some refactoring. I'm not sure how much work this would be yet. Newer versions of the operator are almost certainly going to key off of the newer versions of the chart, which means our currently-deployed values charts would have to be refactored.

So rather than updating the operator, I think we should try to get OpenSearch 3.x to work with the current version of the chart and the operator, since that's the quickest path to production. If that doesn't work, then we should look at updating the chart and the operator. Thoughts?

Update: We have successfully deployed OpenSearch 3.x in the opensearch-test namespace on dse-k8s-codfw using the existing 2.7.0 version of the OpenSearch operator.

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...