kubectl VS cockroach

Check https://github.com/kubernetes/kubectl/issues/151

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

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.

kubectl is for sure battle tested, but it involves very Kubernetes specific implementations and is going to be too complicated for the first pointer

> 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.

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

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.

Go add --no-really-all if you really want it: https://github.com/kubernetes/kubectl

You could take a look at how kubectl actually does it: https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/label/label.go

CockroachDB is an open source distributed SQL database designed for scalability and resilience. While it offers SQL databases, CockroachDB is also compatible with PostgreSQL.

cockroachdb might be close: https://github.com/cockroachdb/cockroach

CockroachDB - SQL

For example, when you create a serverless postgres database with a platform like CockroachDB or Neon, you effectively get a connection string with a strong password. Anyone can connect to your database from anywhere so long as they have the right connection string. There are no security settings in these services to change this behavior.

> Yes you can on the android emulator. The biggest issue is compu arch in that case.

I can also download VirtualBox and run all Windows programs, that would mean that all Windows apps are Linux apps?

> Yes you can for the most part

You can't statically link glibc: https://github.com/cockroachdb/cockroach/issues/3392

glibc can break stuff: https://www.gamingonlinux.com/2022/08/valve-dev-understandab...

I had binaries break because the newer version if openssl was put under a slightly different name.

Also, worth noting, if you're already using PostgreSQL (or plan to) you might want to take a look at https://www.cockroachlabs.com/ they have a free tier too and CockroachDB has a PostgreSQL interface.

I know that some projects like cockroach use custom build tools like bazel. But we actually really like to use to be able to build our projects simply with the great go toolchain and don't really aim to dive deep into custom build solutions.

CockroachDB is designed to be globally distributed. It has to handle causality when resolving collisions. It has to account for having a write operation to arrive after another and still have time priority because it was sent out a few milliseconds earlier.

Cockroachdb created a go runtime patch which measures the Grunning time of a goroutine: https://github.com/cockroachdb/cockroach/pull/82356. It doesn't entirely solve the problem though.

Our entire backend is written in Go. We've built a platform that allows other companies to offer automatic data syncing to their customers' data warehouses. Go works great for building distributed systems like this (see K8s). We're not the only ones in the space building data intensive applications with Go. Pachyderm, Pinecone, Cockroach Labs and are all also doing it. We've been quite happy with how Go has worked for us.