(aws-eks): Ability to suppress selected warnings

[lucaswilric]

Introduce a means of selectively suppressing warnings

Use Case

The @aws-eks/Cluster construct sometimes emits warnings for which the most appropriate response is to ignore them. See #14724 for an example of this.

Non-actionable warnings introduce a usability issue because they make it harder to spot warnings that do need action.

To remedy this, it would be useful to have some way of selectively suppressing errors that we know to be non-actionable, to avoid confusion for folks who are new to our codebase, and to help us reliably notice warnings that we need to pay attention to.

Proposed Solution

The following workaround suppresses warnings by bypassing the Cluster construct's standard interface:

(Works with aws-cdk version 1.104.1)

import * as eks from "@aws-cdk/aws-eks";

function filterSomeWarning(cluster: eks.Cluster) {
  const node = cluster.node._actualNode;

  (node as any)._metadata = node.metadata.filter(
    (m) => m.type != "aws:cdk:warning" || !m.data.includes("Some substring of the warning message")
  );
}

Although this works, it is not really satisfactory, because it is undocumented and relies on knowledge of CDK's internal workings, which could theoretically change at any time.

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[peterwoodworth]

I am marking this issue as p2, which means that we are unable to work on this immediately.

We use +1s to help prioritize our work, and are happy to revaluate this issue based on community feedback. You can reach out to the cdk.dev community on Slack to solicit support for reprioritization.

[cayman-amzn]

Another possible solution: #23403

[peterwoodworth]

I think we can close this in favor of the one you've opened @cayman-amzn, thanks for bringing this to our attention 🙂

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.