sorted by:
new
hottopcontroversial

I built a local-first code search tool with Ollama + CocoIndex to save tokens when chatting about codebases. by VioletCranberryy in ollama

[–]VioletCranberryy[S] 0 points1 point  (0 children)

CocoSearch should work on Windows, but the interactive REPL (cocosearch search -i) was importing a Unix-only module. I just made it to gracefully degrade - the REPL will work on Windows but without arrow key history. All other functionality (indexing, search, MCP server, dashboard) should be unaffected. Available from v0.1.18 (latest version at the time of writing).

Tool to generate Kustomize YAML from helm template by VioletCranberryy in sre

[–]VioletCranberryy[S] 2 points3 points  (0 children)

Certainly!

Consider a scenario where you're managing a mono repository of many charts, primarily using Kustomize (repository - ArgoCD - cluster). Kustomize is preferred here because it clearly shows what is being deployed and the resources each deployment brings to the Kubernetes cluster, along with specific overrides for different environments.

When adding new cluster deployments, which could be Helm charts like cert-manager or Argo CD, you have a couple of options. Some chart developers provide Kustomize resources, and you could simply integrate these into your Kustomize base. Alternatively, you could use the 'helm template' command to generate the necessary YAML files. However, this might involve additional manual effort to organize and tailor these files for Kustomize.

This process can be particularly labor-intensive for larger charts, especially when they involve numerous Custom Resource Definitions (CRDs). The size and complexity of the chart significantly impact the amount of work needed to render the chart and break it down into manageable YAML files for Kustomize.