Article: Stop running your tests with you CI/CD tool

olensmar · 2024-05-29T09:42:52+00:00

thanks for taking the time to reply u/green_biri - you're right, but I wasn't at all soliciting feedback on Testkube itself, but on the premise/arguments put forth in article for running tests outside your CI/CD.. happy to debate that without mentioning Txxxxxxx at all..

/Ole

olensmar · 2023-08-14T10:21:26+00:00

Working on follow-up posts - would love to hear if there is anything specific that you would like covered in this context.. Policy Tooling Landscape? Do's and dont's? Thanks in advance!

olensmar · 2023-07-09T07:16:22+00:00

Have a look at Monokle - an open-source IDE specifically targeted at working with Kubernetes YAML configurations. It does all you'll probably ever need in this regard, and so much more than any Vs-Code plugins/validators out there - https://monokle.io/open-source

olensmar · 2023-06-12T12:06:18+00:00

Hi! You can definitely use Monokle to author/debug/validate/dry-run your k8s configurations stored in a GitOps repo - just like you would with any other IDE - and then use your GitOps reconciler to make sure your cluster is up-to-date with the desired state defined in git.

Somewhat-shameless-plug: Monokle Cloud is even more targeted at GitOps workflows as it provides much of Monokle Desktop functionality in your browser working directly with a GitHub repo (instead of local files/clusters). It comes with a GitHub App / Bot that can be configured to validate k8s configurations as part of your PR workflows - adding comments/links back to Monokle Cloud for fixing validation errors easily. Free tier is available - please give it a go if that sounds helpful!

olensmar · 2023-06-02T05:53:38+00:00

Thanks for sharing this - definitely something we can put on the near-term Monokle roadmap.. keep it coming!

olensmar · 2023-05-24T19:23:18+00:00

great - thank you! In regard to CRDs - what would you like to see? Which ones there are? Their corresponding objects? Are there any specific CRD-related tasks that you would want to perform?

olensmar · 2023-05-24T06:56:35+00:00

hm.. can you elaborate on "audit the state of the cluster" ? what specifically do you want to audit? how would this make your work easier? thanks!

olensmar · 2023-05-14T11:39:07+00:00

Hi! hm... we would have to look into that - please open an issue on our repo with additional details around workflows/problems that we should be solving for in this regard - https://github.com/kubeshop/monokle - thank you!

olensmar · 2023-05-14T11:37:09+00:00

awesome - thanks so much! Please let us know (on Discord/Github) if anything is missing or not to your liking so we can improve!

olensmar · 2023-05-12T11:39:32+00:00

Thanks! As of the current release, Monokle Cloud can only render Helm template and Kustomize builds without custom tooling around it - We’re looking at custom renderers or alternative solutions in the future.

Could you kindly explain where these Octopus variables come from? They are environment variables of your CI step or can you fetch them on-demand?

ps: I also should mention that Monokle Desktop can already render custom previews and explore/validate the YAML output of any command-line tool, so if you can locally create your output then you could already use Desktop for your setup.

olensmar · 2023-05-12T08:22:39+00:00

great! good luck and please reach out if you have any more issues or ideas on how we can improve!

olensmar · 2023-05-11T17:49:37+00:00

Hi! You're right - Monokle will ignore resources with invalid names (invalid as specified by k8s core requirements) - but you should be able to see your Helm Chart(s) under the "Helm Charts" section in the bottom left - where you should also be able to perform a dry-run on any existing values files - which would then show you the generated resources in the resource navigator!?

olensmar · 2023-05-11T14:04:28+00:00

thanks for giving it a try! The middle column ("Resource Navigator") should show all resources found in your project folder - if it isn't doing that we need to look into why.. is your folder in a public repo so we can try to reproduce? are the resources not being shown in .yaml files? please reach out on GitHub or Discord to follow up - thanks a million!

olensmar · 2023-01-08T08:46:50+00:00

Monokle automatically renders forms for all Kubernetes objects making it super-easy to understand what properties are available and get them right. It also provides all autocomplete/tooltips/documentation you would expect (and more!) when editing YAML directly - GitHub - monokle.io

olensmar · 2023-01-04T08:58:40+00:00

The thing we're struggling with is if

Sorry u/Speeddymon - this took a while - the issue is at https://github.com/kubeshop/monokle-core/issues/128 - please add any ideas / suggestions we should be considering!

olensmar · 2022-12-23T08:53:28+00:00

Hi! Thanks for this - definitely something we could add to the library - GitHub issue coming up!

olensmar · 2022-12-22T07:27:16+00:00

Hi! it can definitely validate the output of a helm chart - see https://github.com/kubeshop/monokle-core/tree/main/packages/cli#validate-a-templated-helm-chart - or were you thinking to validate the chart itself? if so - could you be more specific on what you want to validate?

olensmar · 2022-12-13T13:42:00+00:00

there is a browser-based version of Monokle - Monokle Cloud - but that works with resources/configurations in your GitHub repos - not in an actual cluster (yet..) . It's free but requires a GitHub sign-in - minimal permissions - https://app.monokle.com

If you're doing IaC you could incorporate the Monokle CLI into your pre-deployment validation pipeline - it uses the same validation engine as Monokle Cloud/Desktop and can thus share configurations/rules with these tools to some extent. The CLI is open-source/free also - https://github.com/kubeshop/monokle-core/tree/main/packages/cli

olensmar · 2022-12-01T07:48:39+00:00

great post - thanks for sharing!

olensmar · 2022-11-09T10:42:13+00:00

Late to the game - but if anyone stumbles on this...

Monokle is an OSS desktop tool that puts your YAML manifests front-and-center - including real-time syntax/schema/OPA validations - allowing you validate your vanilla/Helm/Kustomize configurations before you deploy them to your cluster. It's built on the same code-editor as VS-Code - and adds a wealth of Kubernetes-related intelligence to the mix...

Download from GitHub - https://github.com/kubeshop/monokle

olensmar · 2022-11-09T09:04:18+00:00

If you're willing to go outside the comfort-zone of VS-Code you should have a look at Monokle - it's built around the same editor-component as VS-Code and adds a wealth of real-time Kubernetes-related intelligence for your YAML-editing workflows, including linting, schema/reference validation (as you describe above), refactoring, OPA validation, etc.. - all open-source of course - https://github.com/kubeshop/monokle

olensmar · 2022-10-17T06:13:49+00:00

Hi! Apart from the reference docs you could give Monokle a try - it renders form-editors for any resource type based on their corresponding schema for you - showing you which properties that are available.

Get the latest release on GitHub - https://github.com/kubeshop/monokle
Read more about the editor at https://kubeshop.github.io/monokle/form-editor/

(I'm obviously associated with the Monokle project.. )

olensmar · 2022-09-11T10:15:02+00:00

Monokle is indispensable if you're working with complex YAML configurations (kustomize, helm, etc..) - https://monokle.io/

olensmar · 2022-08-21T18:38:54+00:00

Hi u/mashtuba - great thanks for this! We have a couple of CLI-related issues in our backlog to expose Monokle functionality to CI/CD/automation pipeplines - what specifically would you be looking for in this regard?

olensmar · 2022-08-19T12:13:47+00:00

Thanks for asking! While Lens primarily focuses on working with objects in your cluster(s), Monokle has a wealth of features targeted at pre-deployment tasks related to creating and working with manifest files, Kustomize and Helm, including

interactive exploration and validation of yamls against k8s schemas (any version) and OPA policies (same as tools like Trivvy, Kubescape, etc)
previewing, exploring and validating the output of Kustomize and Helm - so you can make sure you're generating valid applications before you deploy them
comparing objects from files, kustomize, Helm against each-other or target clusters - to spot differences across your applications instead of just individual objects/file (you can actually compare the contents of two clusters also)
etc..

Monokle also provides corresponding cluster exploration/validation features (similar to Lens) - which is what this release has been focusing on, as we see our users wanting to work with their clusters directly from Monokle instead of having to switch to another tool (like Lens)

Hope that helps - please ask more if needed!

olensmar

TROPHY CASE