Yamllint configuration needs improvements

[tuminoid]

Our yamllint config is quite simple and needs improvements. For example, we want to enforce yaml to be linted in k8s way, meaning lists are not indented.

Study the yamllint tool, and its options and decide what is the acceptable level of enforcement. Make the change here in project-infra (as it is the only repo where it is implemented right now), then add the linter to other repos as well.

Some notes to consider:

• We have manifestlint check in CAPM3/IPAM/IRSO/BMO, which might or might not have options for this too. Check the synergies with that
• yamllint action is out of date by 3 years, not maintained
• the tool under yamllint action is maintained, so changing the action might be needed, or changing workflow to prow job

[Rozzii]

/triage accepted
/kind feature
/help

[metal3-io-bot]

@Rozzii:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/triage accepted
/kind feature
/help

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.

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/remove-lifecycle stale

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/remove-lifecycle stale
/lifecycle frozen