Release v2.6.0 #776
Comments
|
[Triage] |
github-project-automation
bot
moved this to Backlog
in OpenSearch Engineering Effectiveness
|
Looking forward to this release! Any ETA? Days? Weeks? (It would still be nice with releases of beta or release candidate packages for early testing) |
|
Hey @cthtrifork and everyone thanks for your patience. I know this release is pending for some time, we are reviewing and trying to merge the following features as well to the release, so that its bundled with lot of good stuff. But I like the idea to have release candidate packages for early testing, we can consider this to fast track the process. Also for this v2.6.0 the release date is April 22, 2024. I will go ahead with the release even though above PR's are pending for review and can plan a next release sooner. |
|
We just released Release Highlights:https://github.com/opensearch-project/opensearch-k8s-operator/releases/tag/v2.6.0 Dockerhttps://hub.docker.com/r/opensearchproject/opensearch-operator/tags, Helmhttps://artifacthub.io/packages/helm/opensearch-operator/opensearch-operator, https://artifacthub.io/packages/helm/opensearch-operator/opensearch-cluster ECRhttps://gallery.ecr.aws/opensearchproject/opensearch-operator Jenkins Workflowhttps://build.ci.opensearch.org/job/opensearch-operator-release/11/console Release Tag:https://github.com/opensearch-project/opensearch-k8s-operator/tree/v2.6.0 |
|
Any updates to https://github.com/opensearch-project/opensearch-k8s-operator?tab=readme-ov-file#compatibility |
|
Hey @kfox1111 looks to me like the compatibility table is not updated for a while, may I know what are exactly looking for? |
|
Yeah, curious what versions of opensearch v2.6.0 works with. There's an open bug here (#779) that seems to indicate it may not work with 2.11.1. So maybe not versions newer still then 2.8.0? |
|
@kfox1111 that issue looks to me like an issue with plugin but not an issue with the operator. Please check opensearch-project/security-analytics#1352. I have installed |
|
[Triage] |
prudhvigodithi
added
release
and removed
untriaged
…tibility (#792) ### Description Update Operator compatibility matrix and honor compatibility for functional tests ### Issues Resolved Coming from #776 (comment). This should also fix #760. ### Check List - [x] Commits are signed per the DCO using --signoff - [x] Unittest added for the new/changed functionality and all unit tests are successful - [ ] Customer-visible features documented - [ ] No linter warnings (`make lint`) If CRDs are changed: - [ ] CRD YAMLs updated (`make manifests`) and also copied into the helm chart - [ ] Changes to CRDs documented Please refer to the [PR guidelines](https://github.com/opensearch-project/opensearch-k8s-operator/blob/main/docs/developing.md#submitting-a-pr) before submitting this pull request. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). Signed-off-by: Prudhvi Godithi <[email protected]>
|
Closing this issue and the PR was merged. |
github-project-automation
bot
moved this from In Progress
to Done
in OpenSearch Engineering Effectiveness
Release v2.6.0
Prepare for the release of
v2.6.0by creating a corresponding tag,v2.6.0. Below are the commit details that will be included in this release: link.The text was updated successfully, but these errors were encountered: