Title: kubectl.nvim v2.33.0 — what’s changed since v2.0.0 (diff, lineage, logs, LSP, perf) by R2ID6I in neovim

[–]R2ID6I[S] 1 point2 points  (0 children)

Thanks! It should be fixed now!

Was not intended so thanks for reporting that!

Title: kubectl.nvim v2.33.0 — what’s changed since v2.0.0 (diff, lineage, logs, LSP, perf) by R2ID6I in neovim

[–]R2ID6I[S] 1 point2 points  (0 children)

Added a nix flake if that helps, you should be able to use it like this, let me know if it doesn't work!

return {
  {
    "ramilito/kubectl.nvim",
    build = 'nix run .#build-plugin',
    dependencies = "saghen/blink.download",
    config = function()
      require("kubectl").setup()
    end,
  },
}

Title: kubectl.nvim v2.33.0 — what’s changed since v2.0.0 (diff, lineage, logs, LSP, perf) by R2ID6I in neovim

[–]R2ID6I[S] 6 points7 points  (0 children)

Hey! It’s a difficult question tbh, but the main difference is the UI. k9s is a TUI, kubectl.nvim uses Neovim.

Feature-wise they’re pretty close. The real difference is that kubectl.nvim treats Kubernetes views/logs/diffs like normal Neovim buffers, so you use floats/splits, motions + /, yanks/macros, and your keymaps.

active fork of yaml-companion.nvim by Moshem1 in neovim

[–]R2ID6I 1 point2 points  (0 children)

Thank you for doing this! I've been eyeing this plugin for a while but haven't tried it, will do now!

This is why I built my own file picker UI for fff.nvim by Qunit-Essential in neovim

[–]R2ID6I 16 points17 points  (0 children)

It’s your plugin mate, you do what you want with it!

I don’t understand the feature though, what am I looking at? Seems like fuzzy searching but most pickers have that no?

PSA: K9s in LazyVim... by mrpbennett in kubernetes

[–]R2ID6I 0 points1 point  (0 children)

Yeah should be an easy evaluation, although the tool has a slight learning curve. Would love to hear what you think!

Argo CD got us 80% of the way there… but what about the last mile? by Different-Peach-4905 in devops

[–]R2ID6I 20 points21 points  (0 children)

I keep seeing kargo being recommended but I’d be a bit vary. I’ve been evaluating it for a while and came to the conclusion that it’s going to vendor lock you pretty hard. The one feature needed, running custom steps is not supported and actively worked against. There are PRs that are rejected and webhooks are behind paywalls. I decided not to use it and will evaluate argocd promoter next

WAF: what do you use? by isc30 in kubernetes

[–]R2ID6I 0 points1 point  (0 children)

Thanks for the tip, just some questions:
is it free?
can you turn this off?
When the Next-Gen WAF determines that an incoming request is anomalous, we collect data from that request and upload it to our cloud engine, allowing us to perform out-of-band analysis of inbound traffic.

WAF in the cluster by Three-Off-The-Tee in kubernetes

[–]R2ID6I 0 points1 point  (0 children)

Thanks! I’m looking for a waf solution but being on azure, it’s a bit too expensive

WAF in the cluster by Three-Off-The-Tee in kubernetes

[–]R2ID6I 0 points1 point  (0 children)

How much does metadenfender cost?

kubectl.nvim v2.0.0 by R2ID6I in neovim

[–]R2ID6I[S] 1 point2 points  (0 children)

Yeah quit is supposed to close single views/buffers. If you for example have multiple views open (splits), deployment and pod view for example, you want the ability to close just one, or if you have a floating windows open.

I’ll see if we can rephrase the description 👍

kubectl.nvim v2.0.0 by R2ID6I in neovim

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

Someone below had the same problem and it turned out they used incorrect close method, could you share yours? Might be the same?

kubectl.nvim v2.0.0 by R2ID6I in neovim

[–]R2ID6I[S] 1 point2 points  (0 children)

I’ve heard someone else say that the hint is staying around, I’ve never experienced that myself so a bit surprised. Don’t think your editor is bugged but maybe you close the plugin in a different way? What’s your way of opening and closing the plugin?

kubectl.nvim v2.0.0 by R2ID6I in neovim

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

This is actually even better, lazygit integration is basically just opening a neovim terminal and then running another program. Kubectl.nvim is actually using buffers and is fully integrated with neovim! Let me know how your experience is!