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

feat: [LKEAPIFW-258] - Enabling LKE events in CM #10443

Merged

Conversation

talmai
Copy link
Contributor

@talmai talmai commented May 7, 2024

Description πŸ“

Enables LKE events (from apinext) to become highlighted as valid events on CM.

Changes πŸ”„

Added new messages

Target release date πŸ—“οΈ

Not sure of which goes first, but this is related to these nimbus/apinext PRs.

Preview πŸ“·

image

How to test πŸ§ͺ

Spin up a dev CPC and wire everything in devenv. You will need to pull my apinext/nimbus as well. Since this relies on custom apinext code, you can't just wire it up to alpha. Once wired in though, execute actions related to LKE clusters.

Prerequisites

See how to test

Verification steps

See how to test

As an Author I have considered πŸ€”

Check all that apply

  • πŸ‘€ Doing a self review
  • ❔ Our contribution guidelines
  • 🀏 Splitting feature into small PRs
  • [NO] βž• Adding a changeset
  • [NO] πŸ§ͺ Providing/Improving test coverage
  • πŸ” Removing all sensitive information from the code and PR description
  • [N/A] 🚩 Using a feature flag to protect the release
  • πŸ‘£ Providing comprehensive reproduction steps
  • [NO] πŸ“‘ Providing or updating our documentation
  • [ANYTIME!] πŸ•› Scheduling a pair reviewing session
  • [N/A] πŸ“± Providing mobile support
  • [N/A] β™Ώ Providing accessibility support

@talmai talmai requested a review from a team as a code owner May 7, 2024 03:20
@talmai talmai requested review from carrillo-erik and cpathipa and removed request for a team May 7, 2024 03:20
@talmai talmai force-pushed the feature/lkeapifw-258-apinext-lke-events branch 2 times, most recently from 4a6c6e8 to 71065cd Compare May 7, 2024 03:26
Copy link

github-actions bot commented May 7, 2024

Coverage Report: ❌
Base Coverage: 81.52%
Current Coverage: 81.51%

@talmai talmai force-pushed the feature/lkeapifw-258-apinext-lke-events branch 2 times, most recently from 097ad93 to 4efa8dd Compare May 8, 2024 02:14
@bnussman-akamai bnussman-akamai changed the title feat:[LKEAPIFW-258] Enabling LKE events in CM feat: [LKEAPIFW-258] Enabling LKE events in CM May 8, 2024
@bnussman-akamai bnussman-akamai added the LKE Related to Linode Kubernetes Engine offerings label May 8, 2024
@bnussman-akamai bnussman-akamai changed the title feat: [LKEAPIFW-258] Enabling LKE events in CM feat: [LKEAPIFW-258] - Enabling LKE events in CM May 8, 2024
@@ -616,6 +616,62 @@ export const eventMessageCreators: { [index: string]: CreatorsForStatus } = {
e.entity?.label ? ` ${e.entity.label}` : ''
}.`,
},
lke_node_recycle: {
notification: (e) =>
`The node for Kubernetes Cluster ${e.entity!.label} has been recycled.`,
Copy link
Contributor

@cpathipa cpathipa May 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use optional chaining with default values instead of a null assertion?
example: e.entity?.label ?? '' We could follow the same approach in other places as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

βœ…

@talmai talmai force-pushed the feature/lkeapifw-258-apinext-lke-events branch from 53cffb5 to 98bf6ba Compare May 8, 2024 21:45
updated with optional chaining instead of null assertion
@talmai talmai force-pushed the feature/lkeapifw-258-apinext-lke-events branch from cdb0a5c to ed6201e Compare May 8, 2024 21:48
e.entity?.label ? ` ${e.entity.label}` : ''
} has been created.`,
},
lke_pool_recyle: {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Suggested change
lke_pool_recyle: {
lke_pool_recycle: {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

βœ…

Copy link
Contributor

@jdamore-linode jdamore-linode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @talmai! I think you'll need to also update our API library's EventAction type to include these new LKE event actions:

https://github.com/linode/manager/blob/develop/packages/api-v4/src/account/types.ts#L280

Other than that, this is looking great!

Copy link
Contributor

@jdamore-linode jdamore-linode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again @talmai!

(Just to follow up from our discussion, here's a quick screenshot of the commands/output used to generate the changeset files -- then I just committed and pushed the files generated by the command πŸ‘)

Screenshot 2024-05-16 at 2 06 01 PM

@jdamore-linode jdamore-linode merged commit 0381f12 into linode:develop May 17, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LKE Related to Linode Kubernetes Engine offerings
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants