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

CloudWatch service controller #1093

Open
project0 opened this issue Dec 9, 2021 · 6 comments
Open

CloudWatch service controller #1093

project0 opened this issue Dec 9, 2021 · 6 comments
Labels
kind/new-service Categorizes issue or PR as related to a new service. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@project0
Copy link

project0 commented Dec 9, 2021

New ACK Service Controller

Support for Cloudwatch resources.

We currently use cloudformation-operator to automatically create alarms from within a kubernetes controller.

List of API resources

List the API resources in order of importance to you:

  1. MetricAlarm
@project0 project0 added the kind/new-service Categorizes issue or PR as related to a new service. label Dec 9, 2021
@jaypipes jaypipes changed the title [Cloudwatch] service controller Cloudwatch service controller Jan 5, 2022
@jlandowner
Copy link

I really need this!
We do Blue/Green deployment so that we have to create or update Container Insights metrics alarms and ALB metrics alarms created by Ingress controller in every release.

@jaypipes jaypipes added this to Proposed in Service Controller Release Roadmap via automation Mar 29, 2022
@RedbackThomson RedbackThomson changed the title Cloudwatch service controller CloudWatch service controller Apr 29, 2022
@ack-bot
Copy link
Collaborator

ack-bot commented Jul 28, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

@ack-bot ack-bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 28, 2022
@project0
Copy link
Author

/remove-lifecycle stale

@a-hilaly
Copy link
Member

/lifecycle frozen

@ack-bot ack-bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 30, 2022
@demikl
Copy link

demikl commented May 16, 2023

Would be interested in such a controller, to be able to create Log Subscription Filters. I want to send the control-plane audit logs that EKS is storing on Cloudwatch to a Lambda that will forward these logs to Datadog.

jaypipes added a commit to jaypipes/ack-cloudwatchlogs-controller that referenced this issue May 16, 2023
Generated with controller-bootstrap:

```
make SERVICE=cloudwatch SERVICE_MODEL_NAME=logs
```

Issue aws-controllers-k8s/community#1093

Signed-off-by: Jay Pipes <jaypipes@gmail.com>
@mikestef9 mikestef9 moved this from Proposed to Planned in Service Controller Release Roadmap May 17, 2023
ack-prow bot pushed a commit to aws-controllers-k8s/cloudwatchlogs-controller that referenced this issue May 19, 2023
Adds resource management for LogGroup resources in CloudWatchLogs.

Issue aws-controllers-k8s/community#1093

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
@jessebye
Copy link

@project0 Check out https://github.com/aws-controllers-k8s/cloudwatch-controller
It provides support for MetricAlarm resources 😄

@a-hilaly a-hilaly moved this from Planned to Preview in Service Controller Release Roadmap Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/new-service Categorizes issue or PR as related to a new service. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Development

No branches or pull requests

6 participants