-
Notifications
You must be signed in to change notification settings - Fork 37
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
Fargate New cluster #93
Conversation
@Howlla Please fix GitHub Issues. |
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.
@Howlla Great work, much needed pattern. Have some tactial and closure comments.
- Doc is incomplete.
- Please merge from main and fix all conflicts and GH issues.
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Show resolved
Hide resolved
/do-e2e-test single-new-eks-cluster deploy |
3 similar comments
/do-e2e-test single-new-eks-cluster deploy |
/do-e2e-test single-new-eks-cluster deploy |
/do-e2e-test single-new-eks-cluster deploy |
/do-e2e-test single-new-eks-cluster destroy |
2 similar comments
/do-e2e-test single-new-eks-cluster destroy |
/do-e2e-test single-new-eks-cluster destroy |
@Howlla Can you work on the changes pls. I want to merge this and release this week. |
Ready for merge from my side. :) |
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.
@Howlla This is AWSome work, great that you got it working. We had some major breaking change with latest merge that happened yesterday.
- We are using
ObservabilityBuilder
from blueprints and removed it from common. - Im not sure why you need specific values to two addons, probably because of Fargate. So you need make those changes as optional props in blueprints ObservabilityBuilder and then use those here, which will happen only after next blueprints release.
- Also the pattern needs to be revamped with latest standards of using enable methods, See other patterns for more details.
- Also pull from main to push latest code
Please reachout for any questions.
lib/single-new-eks-awsnative-fargate-observability-construct/index.ts
Outdated
Show resolved
Hide resolved
lib/single-new-eks-awsnative-fargate-observability-construct/index.ts
Outdated
Show resolved
Hide resolved
lib/single-new-eks-opensource-observability-pattern/graviton-index.ts
Outdated
Show resolved
Hide resolved
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.
Check the comment
lib/single-new-eks-opensource-observability-pattern/graviton-index.ts
Outdated
Show resolved
Hide resolved
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.
@Howlla Once the current Release upgrade PR goes, in merge from Main to remove all conflicts. Also please update the doc, remove observabilitybuilder
and other extra files noted.
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Outdated
Show resolved
Hide resolved
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Show resolved
Hide resolved
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.
@Howlla Please follow the guidance for the doc and architecture.
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Show resolved
Hide resolved
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.
@Howlla This is AWSome work. Couple of comments on checkin files not related to this work. And Can we raise the bar in deploying a sample workload like yelb app or something like in Java pattern and show some metrics from the App to CW.?
lib/single-new-eks-awsnative-fargate-observability-construct/index.ts
Outdated
Show resolved
Hide resolved
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Outdated
Show resolved
Hide resolved
lib/single-new-eks-awsnative-fargate-observability-construct/index.ts
Outdated
Show resolved
Hide resolved
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.
@Howlla Minor doc feedback. I will run e2e now.
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Outdated
Show resolved
Hide resolved
/do-e2e-test single-new-eks-awsnative-fargate-observability deploy |
/do-e2e-test single-new-eks-awsnative-fargate-observability destroy |
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.
@Howlla Check this
.../single-new-eks-observability-accelerators/single-new-eks-awsnative-fargate-observability.md
Outdated
Show resolved
Hide resolved
@Howlla Destroy is failing. Please make sure |
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.
LGTM, Nice work
/do-e2e-test single-new-eks-awsnative-fargate-observability deploy |
1 similar comment
/do-e2e-test single-new-eks-awsnative-fargate-observability deploy |
/do-e2e-test single-new-eks-awsnative-fargate-observability destroy |
Error is due to CoreDNS failure while destroy. Merging the PR. |
Issue #, if available: 57
Description of changes: New pattern for creating fargate cluster with observability using cloudwatch and containerInsights
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.