-
Notifications
You must be signed in to change notification settings - Fork 0
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
173 cleanup #187
Merged
Merged
173 cleanup #187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aws_cluster/database/aws_postgres_kube_persistantvolume_statefulset.yaml
Dismissed
Show dismissed
Hide dismissed
aws_cluster/database/aws_postgres_kube_persistantvolume_statefulset.yaml
Dismissed
Show dismissed
Hide dismissed
aws_cluster/database/aws_postgres_kube_persistantvolume_statefulset.yaml
Dismissed
Show dismissed
Hide dismissed
aws_cluster/database/aws_postgres_kube_persistantvolume_statefulset.yaml
Dismissed
Show dismissed
Hide dismissed
Jest CoverageSummary
Junit Summary
Coverage Report (72%)
|
Seems like there are multiple container types that are not supported
…be deployed as EC2 instead" This reverts commit a4df66e.
Currently failing to pull the image
the goal is to source aws_common_resources to dry out code and to reduce liklyhood of naming missmatch
Can extend this for all needed images we need to build
This is due to us not having any current customers
Since we want to make the tcp socket connections we need to use a Network load Blancer instead of the Application load balancerd
This hsold allow us to create and push all needed images
Previously we were making id's strictly based on our study id but we need to extend this funcitonality to allow for the same study to be processed multiple times
This was the last straw in what needs for deployment
Quality Gate passedIssues Measures |
powersaudrey25
approved these changes
May 2, 2024
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.
fantastic work thanks guys!
Ivan-E-Johnson
assigned powersaudrey25, zmorris248, Ivan-E-Johnson and mbrzus and unassigned powersaudrey25
May 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR enables full system deployment and functionality on Amazon Web Services (AWS) using the Elastic Kubernetes Service (EKS). It ensures that our application can operate seamlessly in a cloud environment, catering to the demands of scalable infrastructure.
Implementation
This implementation primarily focuses on configuring AWS systems, including network settings, service subnets, and other essential cloud components. Key updates include:
Testing
Testing was conducted through comprehensive manual checks to validate the functionality of each component and the system as a whole. Specific focus areas included:
Problems Faced
Several challenges were encountered during the implementation, particularly with network connectivity and HTTPS protocol handling between Kubernetes pods. Key issues included:
This pull request lays the groundwork for a robust and scalable deployment of our system in a cloud environment, addressing past connectivity issues and streamlining operations.