operator ack-eks-controller (1.7.4)

[ack-bot]

ack-eks-controller artifacts for version 1.7.4

This pull request is created by ack-bot after release of ACK eks-controller-v1.7.4

NOTE: CreateContainerConfigError is expected since ACK controllers have
pre-installation steps to create resources in a cluster before the manager pod
can come up.

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dear @ack-bot,
Some errors and/or warnings were found while doing the check of your operator (ack-eks-controller/1.7.4) against the entire suite of validators for Operator Framework with Operator-SDK version v1.36.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
⚠️	Value eks.services.k8s.aws/v1alpha1, Kind=IdentityProviderConfig: provided API should have an example annotation
⚠️	Value eks.services.k8s.aws/v1alpha1, Kind=PodIdentityAssociation: provided API should have an example annotation
⚠️	Value eks.services.k8s.aws/v1alpha1, Kind=AccessEntry: provided API should have an example annotation
⚠️	Value : (ack-eks-controller.v1.7.4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.