yamlint image: doesnt support arm64 and 2 years old

[medyagh]

the docker image used "cytopia/yamllint:1.26` lint yamls was Last updated over 2 years ago and doesn't have arm64

https://github.com/kubernetes/test-infra/blob/9953805b095e4fa09ce47fafe1268534595d4416/hack/make-rules/verify/yamllint.sh#L38C6-
L38C26

the maintainer of the project does NOT want to have an official image adrienverge/yamllint#281 (comment)

we would need to either migrate to a different yaml linter or make an automated mirror that pushes docker images somewhere

This would be helpful for the the developers that make PRs from a macbook they could lint their yamls and have less warnings piled up

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[upodroid]

This PR should fix it.

#35536

[BenTheElder]

This linter is pretty annoying, I think we should consider instead: https://github.com/kubernetes-sigs/yaml/tree/master/yamlfmt

+ ensuring config strict parses (we already do that with unit tests)

[BenTheElder]

cc @aojea @dims @michelle192837 (repo OWNERS not currently in this thread)

[aojea]

I'm unclear is what is the proposal here. sorry

[BenTheElder]

We either need to build a custom version of this image that is up to date, or ditch the tool.

Personally, I would suggest ditching the tool.
IMHO, formatting enforcement should be done with a formatter, and this linter largely nitpicks formatting.

If we want standardized formatting, we should just use the Kubernetes project's own auto-formatter (we can provide an update and verify script using the go module) and we cover parsing with the existing unit tests for the various configs ...

[medyagh]

We either need to build a custom version of this image that is up to date, or ditch the tool.

Personally, I would suggest ditching the tool. IMHO, formatting enforcement should be done with a formatter, and this linter largely nitpicks formatting.

If we want standardized formatting, we should just use the Kubernetes project's own auto-formatter (we can provide an update and verify script using the go module) and we cover parsing with the existing unit tests for the various configs ...

I agree with @BenTheElder I prefer a go based tool we can run
here is an attempt #36183 let me know what you think

[aojea]

/assign @medyagh

Thanks for taking the initiative