-
Notifications
You must be signed in to change notification settings - Fork 208
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
Feature: AWS CloudWatch Container Insights Addon #878
Feature: AWS CloudWatch Container Insights Addon #878
Conversation
…umentation for it with appropriate kubectl views
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.
@5herlocked Nice work on this new Addon. Some feedback.
- Doc can be improved aligning to enhanced CW features of the addon
- Managed Policy is missing
- CW logs functionality is missing
- mkdocs is missing
- adding to doc index is missing
- Are we not adding the blueprints stack. I would add and comment it.
|
||
const app = new cdk.App(); | ||
|
||
const addOn = new blueprints.addons.CloudWatchInsights(); |
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.
Could we show additional different variants of usage like EBS, CW Logs etc?
@5herlocked Wanted to check if you need any help to make progress on this addon. We want to add this with next blueprints release. |
I'll have this completed in a few weeks. |
Could you plan to add this for upcoming blueprints release? |
Resolved most of the requested changes, still working on the documentation. |
…bal stack and added conflict with cloudWatch logs addon
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. @shapirov103 Please check from your end.
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, however the way it stands now it will be very confusing for the customers to select the right addon, especially choosing between ContainerInsightsAddon and this addon.
So let's apply the following changes:
- deprecate the current container insights addon (e..g similar to what we did for calico)
- update documentation for the deprecated addon and specify that there will be no maintenace on it and customers should move over to the CloudWatchInsightsAddon.
- In the docs for this addon, also call out that it is replacing the current CI addon.
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.
Please see the recommended naming and deprecation changes, otherwise looks great.
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.
Nice work, Please make sure the screenshots are up-to-date after your testing.
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.
@5herlocked looks great!
@elamaran11 since this addon is not part of e2e test, have you tested it on your account?
@shapirov103 I was able to pull the fork and test, everything works fine. I can see CI in CW Console. Please proceed with e2e and merge. |
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
Issue #, if available: #872
Description of changes:
Added container insights add-on using CoreAddOn.
Added documentation for container insights along with what it's doing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.