Open stevehipwell opened 4 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue to never become stale, please ask a maintainer to apply the "stalebot-ignore" label.
/not-stale
CC @LikithaVemulapalli
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue to never become stale, please ask a maintainer to apply the "stalebot-ignore" label.
/not-stale
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue to never become stale, please ask a maintainer to apply the "stalebot-ignore" label.
/not-stale
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue to never become stale, please ask a maintainer to apply the "stalebot-ignore" label.
/not-stale
CC @LikithaVemulapalli
Describe the bug All events for the ASG launch lifecycle are categorised as
UnknownInterruption
instead of the expectedASGLifecycle
.Steps to reproduce Use the ASG launch functionality with K8s events enabled.
Expected outcome I'd expect to see the events categorised as
ASGLifecycle
.Application Logs n/a
Environment