The Custom Resource Definitions used by the opensearch operator will have changed between 2.7.0 and 2.8.0, so we need to install them in our Kubernetes clusters.
This is where we might encounter an issue, as it might not be able to collocate the CRDs between 2.7.0 and 2.8.0, so we might have to uninstall the current version of the operator, leaving opensearch-ipoid un-managed until we start watching it by the 2.8.0 operator.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T414217 ☂️Test OpenSearch k8s Operator 3.x ☂️ | |||
| Open | None | T414698 Import and install the opensearch operator 2.8.0 CRDs |
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...
Re-opening, as using the 2.8 chart will be a requirement for OpenSearch operator 3 project