-
Notifications
You must be signed in to change notification settings - Fork 68
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
feat: (IAC-508) Viya 4 Monitoring replacing Elasticsearch with OpenSearch #238
Conversation
…prior to trying move2opensearch branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lots of questions and concerns on coding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More comments and request for a meeting on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the June these changes are fine. Need to focus on the next release unifying names on the DAC side and mappings with the logging monitoring team.
Viya 4 Monitoring sassoftware/viya4-monitoring-kubernetes is moving from deploying Kibana to deploying OpenSearch with their 1.2.0 release planned for 14 June 2022. Consequently, this repo is being updated to provide support for deploying OpenSearch with the upcoming Viya 4 Monitoring changes.
Note: If this updated version of viya4-deployment is used to deploy OpenSearch into a cluster that has Kibana currently deployed to it, Viya 4 Monitoring will try to preserve customer changes made to Kibana, uninstall Kibana, deploy OpenSearch and restore the saved customer changes. Note that this is a non-reversible operation.