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.

Sign up for GitHub

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

Jump to bottom

control plane log deletion #1018

Closed
errordeveloper opened this issue Jul 11, 2019 · 4 comments
Closed

control plane log deletion #1018

errordeveloper opened this issue Jul 11, 2019 · 4 comments
Labels
kind/feature New feature or request priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@errordeveloper
Copy link
Contributor

When users deletes a cluster, logs should be deleted from CloudWatch also.
@errordeveloper
Copy link
Contributor Author

This is more important than #1017, as it would be an annoyance to user if we don't do it right away when we introduce #704.

@errordeveloper errordeveloper added this to the 0.2.0 milestone Jul 11, 2019
@errordeveloper errordeveloper added the kind/feature New feature or request label Jul 11, 2019
@whereisaaron
Copy link

If easier in the interim you could include messages with the cluster delete output mentioning any resources that might need cleaning up. Like these logs and cluster-created LBs for Ingresses.

@errordeveloper
Copy link
Contributor Author

@whereisaaron we are working on addressing the issue with LBs actually, because it's too tedious. But as far as logs are concerned, I could your suggestion if this doesn't get done in time.

@errordeveloper errordeveloper modified the milestones: 0.2.0, 0.3.0 Jul 12, 2019
@gemagomez gemagomez modified the milestones: 0.3.0, 0.4.0 Aug 5, 2019
@gemagomez gemagomez modified the milestones: 0.4.0, 0.5.0 Aug 21, 2019
@errordeveloper errordeveloper modified the milestones: 0.5.0, 0.6.0 Aug 30, 2019
@gemagomez gemagomez modified the milestones: 0.6.0, 0.7.0 Sep 9, 2019
@gemagomez gemagomez removed this from the 0.7.0 milestone Oct 8, 2019
@D3nn D3nn assigned martina-if and unassigned D3nn Mar 12, 2020
@martina-if martina-if removed their assignment Mar 19, 2020
@martina-if martina-if added the priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases label Sep 11, 2020
@aclevername
Copy link
Contributor

This issue's request sounds pretty reasonable, but I'm surprised by how inactive this has been. Users might not mind the logs being left around? Or perhaps EKS has addressed it themselves.

Closing due to staleness. Feel free to re-open if people still think this is an issue 😄

torredil pushed a commit to torredil/eksctl that referenced this issue May 20, 2022
@k8s-ci-robot
Merge pull request eksctl-io#1018 from wongma7/csiproxyv1bump
945e31a 
Bump csi-proxy from RC v1.0.0 to GA v1.0.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature or request priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@errordeveloper @martina-if @gemagomez @whereisaaron @kalbir @aclevername @D3nn