-
Notifications
You must be signed in to change notification settings - Fork 204
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
Add diagram for eks deployment #552
Conversation
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.
Can you add a Hazelcast service into the mypega namespace? you add the hazelcast Docker image to the pega values.yaml so when you deploy that namespace, it brings up Hazelcast-dedicated pod
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.
that looks great. thank you!
We should probably identify the versions of Pega this diagram is applicable for. |
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.
looks great! thanks for adding the addons tier
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.
Looks great!
@feenr Are we good to merge this PR? |
@MadhuriArugula sorry for ignoring your previous comment. Branch is merged now. |
I added a diagram for a recomended approach to deploying the Pega Helm charts on AWS, with some consideration given to high availability.