ASG launch lifecycle events showing up as UnknownInterruption

[stevehipwell]

Describe the bug
All events for the ASG launch lifecycle are categorised as UnknownInterruption instead of the expected ASGLifecycle.

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

• NTH App Version: 1.22.0
• NTH Mode (IMDS/Queue processor): Queue processor
• OS/Arch:
• Kubernetes version:
• Installation method: Helm

[github-actions]

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.

[stevehipwell]

/not-stale

[stevehipwell]

CC @LikithaVemulapalli

[github-actions]

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.

[stevehipwell]

/not-stale

[github-actions]

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.

[stevehipwell]

/not-stale

[github-actions]

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.

[stevehipwell]

/not-stale

CC @LikithaVemulapalli

[LikithaVemulapalli]

Hello @stevehipwell, we will further see that this issue is not marked as stale and will give an update on this as soon as possible. Thanks!