kubectl
prysm
Our great sponsors
kubectl | prysm | |
---|---|---|
13 | 134 | |
2,680 | 3,346 | |
1.7% | 1.2% | |
9.2 | 9.7 | |
5 days ago | 5 days ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 only |
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
prysm
-
Did I break CURL ? can't update my validator from github
curl -LO https://github.com/prysmaticlabs/prysm/releases/download/v4.0.7/beacon-chain-v4.0.7-modern-linux-amd64
-
Does anyone know how to use Prysmctl?
I do not believe that there is a Windows version of prysymctl. Appears to be only built for linux.
-
Smartnode Release v1.9.7 - Prysm and Teku Updates
Prysm's debug image for v4.0.6 (which Rocket Pool requires due to it having a Linux shell) claims to contain the v4.0.5 binaries. The Prysm team has been notified but is not in a position to redeploy the Docker image with the correct version at this time. Due to this, we have created our own Docker image for Prysm v4.0.6 which uses the correct binaries from their release page (https://github.com/prysmaticlabs/prysm/releases/tag/v4.0.6).
- PRYSM: how exactly do I get the "modern" version to run?
-
Bot for GitHub/Lab Releases
I want to create a bot that sends messages once new releases of certain GitHub/Gitlab repo’s ( -https://github.com/bitcoin/bitcoin/releases -https://github.com/ethereum/go-ethereum/releases -https://github.com/prysmaticlabs/prysm/releases -https://github.com/dashpay/dash/releases -https://github.com/Team-Kujira/core/tags -https://gitlab.com/thorchain/thornode/-/releases ) have been released.
- MEV boost Yes or No?
-
Proposal missed with error "posting the SignedBlindedBeaconBlockCapella to the builder api"
The same thing happened to me, I opened an issue in prysm and in mevboost, we are not the only ones with bad luck, https://github.com/prysmaticlabs/prysm/issues/12434 https://github.com/flashbots/mev-boost/issues/516 try adding the --build-block-parallel flag I also removed 2 relays, flashboot and brute. Hopefully next time we'll have better luck. sorry for my bad english
- Block Missed?
- Prysm Release v4.0.4 · first full release following recent mainnet issues · pls update immediately
What are some alternatives?
helm - The Kubernetes Package Manager
lighthouse - Ethereum consensus client in Rust
kubernetes - Production-Grade Container Scheduling and Management
go-ethereum - Official Go implementation of the Ethereum protocol
client-go - Go client for Kubernetes.
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
eth2-staking-rewards-calculator - [Archived, see README] Allows you to calculate the Ethereum 2.0 staking rewards on a day-by-day basis (useful for tax purposes).
cli - GitHub’s official command line tool
Nethermind - A robust execution client for Ethereum node operators.
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
teku - Open-source Ethereum consensus client written in Java