Per parent ticket, this namespace will be used to test the OpenSearch operator version 3.x.
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T414217 ☂️Test OpenSearch k8s Operator 3.x ☂️ | |||
| Resolved | brouberol | T418176 Provision opensearch-operator-ng namespace in dse-k8s |
Event Timeline
From my past experience with the -ng naming scheme (quickly turning into ng2 or -ng-ng when whatever was ng becomes legacy), I'm going to say: "let's name it opensearch-operator-3".
Change #1243041 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/puppet@production] deployment_server: provision the dse-k8s opensearch-operator-3 kubeconfigs
Change #1243046 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] dse-k8s: define the opensearch-operator-3 namespace to all clusters
Change #1243041 merged by Brouberol:
[operations/puppet@production] deployment_server: provision the dse-k8s opensearch-operator-3 kubeconfigs
Change #1243046 merged by jenkins-bot:
[operations/deployment-charts@master] dse-k8s: define the opensearch-operator-3 namespace to all clusters