Skip to content

Updated RELEASE-NOTES.md file for 1.24 version #396

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.

Sign up for GitHub

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

Merged
vladsha-dev merged 1 commit into from
Oct 31, 2024
Merged

Updated RELEASE-NOTES.md file for 1.24 version #396

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion doc/release/RELEASE-NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,17 @@ This project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html
* *Describe what's new here. The changes that can impact user experience should be listed in this section.*

### Release instructions:
* Run the `[Release] Deploy` pipeline for the Staging or Production environment with the flag 'Clear OpenSearch indexes' set to true. This will allow Logstash to refill OpenSearch since the OpenSearch instance will be recreated due to the version increase.
* The following steps should be completed while deploying to Staging or Production:
1. Run the `[Release] Deploy` pipeline for these environments with the flag 'Clear OpenSearch indexes' set to true. This will allow Logstash to refill OpenSearch since the OpenSearch instance will be recreated due to the version increase.
2. Open the triggered `Deploy to AWS` workflow and ensure that the `apply` job is completed. **Right after** finishing the `apply` job, follow these instructions, which should be the last steps in setting up the recreated OpenSearch instance:
- Copy the ARN of the `terraform_ci` user from the AWS IAM console.
- Navigate to the AWS console's search input, type "IAM", and open the IAM console.
- In the IAM console, find and click on the "Users" tab.
- In the list of available users, locate the `terraform_ci` user, click on it, and on that page, you will find its ARN.
- After copying this value, go to the AWS OpenSearch console in the same way you accessed the IAM console.
- Open the available domains and locate the domain for the corresponding environment. Open it, then navigate to the security configuration and click "Edit".
- Find the section titled "Fine-grained access control", and under this section, you will find an "IAM ARN" input field. Paste the copied ARN into this field and save the changes. It may take several minutes to apply. Make sure that the "Configuration change status" field has green status.
3. Then, return to the running `Deploy to AWS` workflow and ensure that the logs for `clear_opensearch` job do not contain errors related to access for deleting the OpenSearch index or lock files in EFS storage. In case of **an access error**, simply rerun the `Deploy to AWS` workflow manually from the appropriate release Git tag.


## Release 1.23.0
Expand Down