Replies: 1 comment 1 reply
-
I like this idea, but I'll need to take a step back from this project very soon due to a conflict of interest with a new employer. Another contributor has mentioned a possible interest in maybe becoming the new maintainer but we'll see what happens there! If this person chooses to take the reigns it'll be up to them whether this is something they want to merge, but I suspect their answer will be yes. More strict linting in CI is (almost?) always a good thing. If this person doesn't end up taking a maintainer role I'll probably have to archive the project. It will continue to be available but will exist in an essentially frozen state. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@ellenhp what is your opinion about adding a K8s linting tool to your CI?
You have already merged my PR to fix the K8s manifest, so now they are meeting the basic security standards recommended by the CISA Harding guide.
Adding the linter to the GitHub workflow will ensure the manifests always comply with the Harding guide requirements.
I can help to set it up in the project pipeline and open a PR.
Beta Was this translation helpful? Give feedback.
All reactions