kubectl
glow
Our great sponsors
kubectl | glow | |
---|---|---|
13 | 60 | |
2,684 | 14,718 | |
1.8% | 2.6% | |
9.2 | 6.9 | |
3 days ago | 11 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kubectl
-
What are these orphaned PVC objects?
Check https://github.com/kubernetes/kubectl/issues/151
-
Setting kubectl context via env var
I have read this issue, and up to now it seems not possible to change the kubectl context via an env var: https://github.com/kubernetes/kubectl/issues/1154
-
Deciding between Rust or Go for desktop applications
However, I would encourage people to take a look at what the code looks like before assuming the Go developer experience on this was positive. Bear in mind that's just the top level kubectl command and some helper functions, the subcommand definitions take up a several more files split into a few more packages. Then you're still not even done, because code that uses the parsed flags still has to redundantly check things that couldn't be enforced at the type level, something Go folks like to pretend is a good thing for some reason.
-
Recommendations on file/dir/module structure, common dependencies, and/or anti-patterns for writing CLI tool in Rust
kubectl is for sure battle tested, but it involves very Kubernetes specific implementations and is going to be too complicated for the first pointer
- Recommendations on building a simple DSL REPL?
-
Why Go and Not Rust?
> context.Background() is typically only used when one doesn’t care about the result. If you did care about the result, you should be passing the parent context to preserve the circuit breaker timeout in case the operation takes too long.
Not necessarily. You would use context.Background in a test situation. It's also commonly used for short-lived applications like a CLI invocation. You can see kubectl uses context.Background quite a lot: https://github.com/kubernetes/kubectl/search?q=context.backg...
> I think the level of pain you experience from mutable references in Rust depends on if you’re coming from an OOP or FP background. I have a FP background and so the patterns I use to build code already greatly restrict mutation. You can usually change code that updates data immutably (creating a new copy of it) with mutable code in rust because the control flow of your program already involves passing that new version back to the caller which also satisfies the borrow checker in most situations.
There has to be a better solution to needlessly copying data.
-
kubectl - Create PV/PVC
This is particularly useful for academic purposes, and makes somehow convinient to get the yaml template of k8s objects. I was looking for this as well due to an upcoming ckad test i have. Unfourtunately due to not being considered best practice the request for it was dismissed. https://github.com/kubernetes/kubectl/issues/1073
-
Must `kubectl apply` twice to allow CRD usage?
I see, apologies, I did misunderstand. This is actually a known race condition between kubectl (or even helm, or any Kube API client) issuing the requests to deploy CRs that depend on CRDs while those CRDs are still being installed on the API server. Simply put, kubectl makes these requests too quickly. There is no solution to this currently aside from deploying CRDs separately from the resources they expose. See this kubectl issue: https://github.com/kubernetes/kubectl/issues/1117, and there are some links in the comments to other issues echoing the same problem in helm and elsewhere.
-
What's the number one annoyance that drives you crazy about Kubernetes?
Go add --no-really-all if you really want it: https://github.com/kubernetes/kubectl
-
How to change a POD label via client-go?
You could take a look at how kubectl actually does it: https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/label/label.go
glow
-
Essential Command Line Tools for Developers
To get started, install Mods and check out some of the examples below. Since Mods has built-in Markdown formatting, you may also want to grab Glow to give the output some pizzazz.
- Ask HN: How do you synchronise your notes?
-
Not trying to start a rumble, but why neovim
I recently started using markdown in neovim (with an LSP) along with https://github.com/charmbracelet/glow to view markdown / navigate. Does everything I used to use Obsidian for minus the links / graph functionality which I don't really need and it's pretty snappy on an old Lenovo. Very customizable as well.
- How would you read your files if Obsidian disappeared?
-
Show HN: GPT-engineer – platform for devs to tinker with AI programming tools
Yup, those seem to be the key challenges. I've been making good progress on them, but there's plenty more work to do!
On the topic of "AI-generated PRs", I used my tool to file a PR to the `glow` CLI tool. I don't know the go language, so I had aider make the changes to glow.
https://github.com/charmbracelet/glow/pull/502
I've also been able solve a couple of github issues that were file by users by just pasting the issue into my tool... it fixed itself. Links below:
https://github.com/paul-gauthier/aider/issues/13#issuecommen...
https://github.com/paul-gauthier/aider/issues/5#issuecomment...
- FLiPN-FLaNK Stack Weekly May 8 2023
-
How to host your own Golang based Git server for the command line.
I'm personally also quite fond of Glow. I use it pretty much every time I touch a markdown file.
-
Show HN: Frogmouth – A Markdown browser for your terminal
Nice idea! I’m excited to check it out. I write a lot of docs in Markdown and this could be a great way to browse them.
Out of curiosity, have you seen glow[0]?
[0] https://github.com/charmbracelet/glow
-
Recommendations on file/dir/module structure, common dependencies, and/or anti-patterns for writing CLI tool in Rust
Charm's Glow is a joy to use, a good example of having the Charm's Bubbletea usage - but from the code perspective, it's a bit difficult to navigate as many code paths are put in the same package
-
AI - a commandline ChatGPT client in with conversation/completion support
thanks! Yeah all the markdown is handled through glow, which is one fairly awesome tool.
What are some alternatives?
helm - The Kubernetes Package Manager
markdown-preview.nvim - markdown preview plugin for (neo)vim
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
pcstat - Page Cache stat: get page cache stats for files on Linux
kubernetes - Production-Grade Container Scheduling and Management
mdless
client-go - Go client for Kubernetes.
mdcat - cat for markdown
cli - GitHub’s official command line tool
bat - A cat(1) clone with wings.
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
glow.nvim - A markdown preview directly in your neovim.