Add CreateContainerError and InvalidImageName to waiting reasons

[keisku]

What does this PR do?

Add CreateContainerError and InvalidImageName to waiting reasons.

Motivation

kubernetes/kube-state-metrics#763 is the similar work.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.

[ahmed-mez]

Thanks for the contribution!

[lerlacher-haylix]

Hi,

this PR comes out of a Datadog support ticket that I filed - very grateful to @keisku for diagnosing the issue and taking this straight here.

I can see this has been added to the 7.40 milestone. As this is for an ongoing problem we are facing (we need to detect & alert on containers in CreateContainerError state), is there any chance to pull this forward to 7.39?

Let me know if there is anything I can do to help.

Thanks.