Skip to content
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

Aggregate Cloud.gov ES instances #2814

Closed
10 tasks
elipe17 opened this issue Jan 17, 2024 · 0 comments · Fixed by #2876
Closed
10 tasks

Aggregate Cloud.gov ES instances #2814

elipe17 opened this issue Jan 17, 2024 · 0 comments · Fixed by #2876
Assignees
Labels
dev devops Refined Ticket has been refined at the backlog refinement

Comments

@elipe17
Copy link

elipe17 commented Jan 17, 2024

Description:
As the development of Kibana has wrapped up it has been discovered that it is prohibitelve expensive to deploy ES, Kibana, and the ES proxy on a per app basis. Thus, we want to aggregate all ES instances into one singular (larger) instance to help mitigate cost and deployment complexity.

Acceptance Criteria:
Create a list of functional outcomes that must be achieved to complete this issue

  • Singular Elastic instance
  • Singular Kibana instance
  • Frontend and backend apps for all environments happily talk to the singular instances
  • Testing Checklist has been run and all tests pass
  • README is updated, if necessary

Tasks:

  • Delete existing Elastic instances
  • Update Terraform to stand up a singular Elastic instance
  • Update deploy scripts to connect frontend/backend apps to the correct Elastic instance
  • Update Kibana and Elastic proxy deployment manifests to not be environment specific
  • Redeploy/restage frontend/backend apps so that they connect to the new instances

Notes:
Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this

  • Note 1
  • Note 2
  • Note 3

Supporting Documentation:
Please include any relevant log snippets/files/screen shots

  • Doc 1
  • Doc 2

Open Questions:
Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete

  • Open Question 1
  • Open Question 2
@jtimpe jtimpe added the Refined Ticket has been refined at the backlog refinement label Jan 23, 2024
@jtimpe jtimpe mentioned this issue Jan 23, 2024
7 tasks
@raftmsohani raftmsohani self-assigned this Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev devops Refined Ticket has been refined at the backlog refinement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants