[HN Gopher] Kubed (Emacs-based Kubernetes interface) user manual...
___________________________________________________________________
Kubed (Emacs-based Kubernetes interface) user manual, now with
pretty images
Author : oskardrums
Score : 64 points
Date : 2024-09-21 07:52 UTC (15 hours ago)
(HTM) web link (eshelyaron.com)
(TXT) w3m dump (eshelyaron.com)
| whirlwin wrote:
| > Pods, logs, shells, YAMLs, all in one integrated interface
|
| Has anyone tried Kubed?
|
| Personally I have very good experience with k9s which seems to do
| the same, and a bit more.
|
| https://k9scli.io/
| _joel wrote:
| k9s is easily my favourite k8s util
| donaldihunter wrote:
| Just learned about Kubed here, but I'm a longtime user of k9s
| and I'm keen to try out Kubed to see how it compares. It will
| be interesting to see if there are any workflow benefits to be
| gained from Kubed.
| gigatexal wrote:
| This is very cool. But now instead of emacs make it Vi ;-)
|
| update: I am very sorry for this silly post. I love you all
| whether you use vi or emacs.
| dingnuts wrote:
| emacs has a vi implementation, you just turn on evil mode.
|
| I don't know why this is so hard for vimmers to understand.
| evil mode will work with this.
|
| I'm only half joking. The holy war between vim and emacs is
| like a bunch of machinists arguing over whether they prefer a
| lathe, or an entire machine shop that also includes a lathe if
| you want it.
| gigatexal wrote:
| For the same reason vimmers despise IDEs: we don't need it.
| We just need a tool to edit text and the rest we can do with
| other Unix tools. ;-)
| dingnuts wrote:
| so just open vim when you don't need the rest? that's what
| I do. they're just tools. you can use both of them as
| appropriate.
|
| but also the grand parent I was replying to wants to
| control kubernetes from vim.
|
| so do you want to control kubernetes from vim, or do you
| dislike IDEs? you can't have both a minimal editor and an
| editor that does everything all in one program
|
| just install evil mode in emacs and leave vim installed and
| use both and you can have your cake and eat it too!
| sometimes I think programmers just don't want to be happy
| desumeku wrote:
| At this point, why not use nano, or simply echo your code
| into text files? You don't need to see your code while
| writing it when you have cat and less.
| dingnuts wrote:
| nano? pff, just use sed
| ashton314 wrote:
| I knew I was in the presence of a hard-core programmer
| when my interim advisor unironcially used sed to make a
| tiny edit to a config file. He just up-and-used it
| correctly like the first time. I was amazed.
| umanwizard wrote:
| OK, so back to the original point of the thread: where is
| the vim implementation of something like kubed?
|
| There isn't one, because vim isn't a general-purpose
| application development platform, but emacs is.
|
| If people don't want to access general-purpose applications
| from within their text editor, that is fine, but then why
| complain on threads about new emacs packages for people who
| do?
| nocman wrote:
| > The holy war between vim and emacs is like a bunch of
| machinists arguing over whether they prefer a lathe, or an
| entire machine shop that also includes a lathe if you want
| it.
|
| IMHO not really a fair comparison. There are signifcant
| differences in the feel and the workflow between using vim
| and using emacs in evil mode. Other people have preferences
| that differ from yours. I have many years experience using
| both vim and emacs (in evil-mode), and I see both sides.
| Don't get me wrong, emacs in evil mode is great, and I would
| not want to be without it, but it does not 100% reproduce the
| workflow of logging in to a terminal and editing text there
| in vim.
|
| The differences are significant. I'm not saying the
| experience in emacs is bad, it's just different. If you
| already have, say, 10 years of muscle memory built up from
| using vim in a terminal, it will take a fair amount of
| adjustment to move to an emacs/evil-mode way of doing things.
|
| I personally see no reason that I have to pick one or the
| other, and at present I spend a lot of time in both editors.
| I realize that would drive some people crazy, but I'm OK with
| my preferences being a little unusual.
| dingnuts wrote:
| I've used emacs for ten years and vim for twenty. You know
| something I've noticed? vim users always show up in emacs
| spaces to poke fun at emacs users, for some reason. But the
| reverse was never true anecdotally, when I used vim only.
|
| I use emacs because people in #vim on freenode were mean to me
| ten years ago for having an interest in Lisp, and told me to
| just use emacs if I was interested in that..
|
| ok I said. #emacs treated me respectfully. ten years later,
| emacs has a lively community. vim has some forks.
|
| I wonder why this is. Just something to think about.
| gigatexal wrote:
| I'm only teasing. emacs is on my list but in evil mode only
| for the time being.
| dingnuts wrote:
| yeah sorry IDK why it bugged me today. I just love both
| these tools so much.. the holy war is dumb :(
| imp0cat wrote:
| Is this related to https://github.com/kubernetes-el/kubernetes-el
| ?
| sham1 wrote:
| One thing I appreciate about this package is that it's in GNU
| ELPA. Far too many emacs packages end up just languishing in
| MELPA.
|
| It wouldn't even be a problem if they were in MELPA Stable
| (although I personally prefer GNU ELPA and nongnu ELPA), but the
| fact that so many packages exist without any versioned releases
| bugs me way too much. It makes having a reproducible config far
| more annoying than it could be.
___________________________________________________________________
(page generated 2024-09-21 23:01 UTC)