-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Wazuh indexer based on OpenSearch 2.3.0 #4160
Comments
OpenSearch 2.0.0Breaking changes
@wazuh/cicd These settings must be removed and updated in the Development environmentsWe need to adjust our development environments with the following changes:
Found issues
|
OpenSearch 2.1.0 is liveOpenSearch 2.1.0 was released the 7th of July. We need to create images for this new version. OpenSearch and Dashboards 2.1.0 Release NotesTasks
|
OpenSearch 2.2.0 is liveOpenSearch 2.2.0 was released the 12th of August. We need to create images for this new version, if we decide to provide support for this new version. OpenSearch and Dashboards 2.2.0 Release NotesTasks
This version contains a CVE that is solved in 2.2.1. In case of providing support for OpenSearch 2.2.x we should upgrade directly to v2.2.1.
|
OpenSearch 2.2.1 is liveOpenSearch 2.2.1 was released the 2nd of September. We need to create images for this new version, if we decide to provide support for this new version. OpenSearch and Dashboards 2.2.1 Release NotesTasks
Issue:IMPORTANTThis version solves a CVE in the OpenSearch Reporting plugin. The patched versions are 1.3.5 and 2.2.1, so any other version is vulnerable. More information about this vulnerability can be found in this link. |
In OpenSearch 2.2.1 a new CSS class is being added to the navbar components, in particular to the breadcrumbs headers, that breaks the visualization of the Wazuh breadcrumbs. In the images below, we can see this new CSS class, named This problem applies to both, the light and the dark mode. Disabling this property, considerably improves the situation, although there are rendering problems still. |
hi . is there a way to know how to build or get the wazuh plugin package (zip) for opensearch 2.2.1 .. ? as i need to install plugin in existing opensearchv 2.2.1 |
Hi @samrit-narshing thank you for your interest in Wazuh, currently the application is not compatible with OSD 2.2.1, this issue is to see if it can be compatible with this version. |
Hello @wazuh-cloud-cicd team. One of the breaking changes of OS 2.x is the deprecation of the setting ### Option to allow Filebeat-oss 7.10.2 to work ###
compatibility.override_main_response_version: true Are you aware of this conflict? |
I was testing the configuration, and it only caused me problems in version 2.0.0, in versions 2.1.0 or 2.2.1 I had no problem. The deprecation of the setting |
OpenSearch 2.3.0 is liveOpenSearch 2.3.0 was released the 14th of September. We need to create images for this new version, if we decide to support it. OpenSearch and Dashboards 2.3.0 Release NotesTasks
Notable changes
|
From what I was testing I could not find other things to highlight in the 2.2.1 versions and, since version 2.3.0 was released, I was testing that version and so far I found no differences in performance with respect to version 2.2.1. |
A new problem has been found in every version of OpenSearch 2.x, more concretely related to the OpenSearch Dashboards. We use the flyout component from EUI, which closes automatically when the user clicks outside it. However, in 2.x, these components will also close automatically when clicking inside them. This is not the correct behavior, and it's probably related to OSD updating the EUI library to a newer version, breaking our customized components behavior. Videoflyoutclose.mp4We'll need to hunt and fix this bug. Related release notes
|
Comparison tableChanges compared to OpenSearch and OpenSearch Dashboards 1.2.0.
|
The team has decided to move to OpenSearch 2.3.0 on the new minor version of Wazuh (4.4.0). |
Description
We need to ensure the UI compatibility with the next Wazuh Indexer which might be based on OpenSearch 2.0.0. This update is still being discussed, and we need to know potential issues.
Note: we'll move to the latest version of OpenSearch, which is 2.3.0 at this time.
Issues
The text was updated successfully, but these errors were encountered: