-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be possible to run kubent against manifest #6
Comments
would also be nice to pipe to it :) |
Thanks for suggestions, support for local files, and stdin is certainly something that can be added, I was thinking about this myself - just decided to leave out of initial implementation to simplify things. More than happy to accept PRs ;) 🎖️ , eventually I should be able to look at this in a short while myself too. |
@NargiT support for local files has now been merged into the master via #15 :
A release incl. this should follow later this week (with a couple of other improvements). @alam0rt pipe is not supported in the initial take, but I'm planning to add soon (it should be ready for it) as it totally makes sense 👍 |
This will definitely go to our CICD for analyzing purpose. And definitly a github bot for status check in a PR. 👍 Thanks for your work @stepanstipl |
This has now been merged and released incl. the support for stdin input (use |
One issue I found in kubent is that it requires to run it against the cluster, I would prefer using local manifests.
This will avoid putting credentials inside a CI/CD and be able to detect deprecated api during development or allow to prepare migration to new version not yet deployed.
I heard from @drewboswell that kubeval could provide the model.
e.x:
The text was updated successfully, but these errors were encountered: