With a basic understanding of how k8s works and an already running cluster, all one needs to know is how to run a service as a docker file to have it also run in k8s
CubitOom
joined 2 years ago
Well the kubernetes API has all the necessary parts built in mostly, although sometimes you may want to install a custom resource which often comes with complex service installs.
But I think the biggest strength of kubernetes is all the foss projects that are available for it. Specifically external-dns, cert-manager, and istio. These are separate projects and will have to be installed after the cluster is up.
You can also look at the cloud native computing foundation's list of projects. It's a good list of things that work well.
Caution, not all cloud providers support istio. I know that Google's GKS doesn't, they make you use their own fork of it
I would also recommend you avoid helm if possible as it obfuscates what the cluster is doing and might make learning harder. Try to just stick to using kubectl if possible.
I have heard good things about nomad too but I have yet to try it.
You should try out all the options you listed and the other recommendations and find what works best for you.
I personally use Kubernetes. It can be overwhelming but if you're willing to learn some new jargon then try a managed kubernetes cluster. Like AKS or digital ocean kubernetes. I would avoid managing a kubernetes cluster yourself.
Kubernetes gets a lot of flack for being overly complicated but what is being overlooked with that statement is all the things that kubernetes does for you.
If you can spin up kubernetes with cert-manager, external-dns, and an ingress controller like istio then you got a whole automated data center for your docker containers.
Checkout ollama.
There's a lot of models you can pull from the official library.
Using ollama, you can also run external gguf models found on places like huggingface if you use a modelfile with something as simple as
echo "FROM ~/Documents/ollama/models/$model_filepath" >| ~/Documents/ollama/modelfiles/$model_name.modelfile
Not hotdog
What are we growing?
Are we just growing fake numbers? Making them go up an arbitrary amount without concern for the methods used?
Is this growth natural or is it forced? Are we trying to have a positive impact on the community? Is the growth in balance with society's needs and it's dreams?
Are we actually growing as a species, or do we just alternate in cycles of growth and decay? From infancy to middle age and then back again repeating endlessly?
Are we hitting checkpoints that we can go back to without starting over from nothing?
There is "growth" and then there is growth.
I've been running Manjaro for about 6 years. I've only had self induced issues.
- I restarted during a GPU driver update
- I only used pacman to do system updates and it kept failing. I needed to use pamac for those round of updates instead.
Arch is a better OS in that you have more control of exactly what it will do. But Manjaro also provides a great experience out of the box with all the major DEs. It really comes down to how much convenience are you willing to trade for control.
For what it's worth, I've only noticed the slower Manjaro repo helping me once when steam fonts broke on the arch repo. So I basically had a warning and was able to switch to the beta version of the steam client to avoid that issue. So the slower Manjaro repo is not a selling point IMO, but the DE tweaks and configurations are.
How does llm compare to ollama?
That's a good point.
Somethings I didn't realize I don't know of till now. When does one withdraw money from social security? Like do they have to request it from the government? A government worker might have a retirement age but for most Americans, it's more of a guide. I know plenty of people that are in their 70s and they never plan to retire. If they continue to get paid on w-2 and report earnings to the IRS, does that mean they are ineligible to receive social security benefits?
I suppose if they are not able to collect social security money, and they continue to pay into it but they retire later then you are 100% correct and it's not as big of a problem for the younger generations as I thought.
Although I would say that the job market is in fact a competition. No matter if you are someone with seniority and experience, someone with little experience willing to work for less, or simply an automaton.
I'm talking about in the USA. It is supposed to work the way you say. But in reality, you aren't paying into an individual account for yourself. You pay into a pool that the government uses as soon as it receives the money for the current recipients of social security.
Really it's a ponzi scheme with declining contributors and an increasing amount of people cashing out.
It honestly is really good to reinstall your OS once a year, especially if using windows.
It's a pain but you can use scripting to make it easier if you are up to it.
I would say that if you are going to host it at home then kubenetes is more complex. Bare metal kubernetes control plane management has some pitfalls. But if you were to use a cloud provider like linode or digital ocean and use their kubernetes service, then only real extra complexity is learning how to manage Kubernetes which is minimal.
There is a decent hardware investment needed to run kubernetes if you want it to be fully HA (which I would argue means it needs to be a minimum of 2 clusters of 3 nodes each on different continents) but you could run a single node cluster with autoscaling at a cloud provider if you don't need HA. I will say it's nice not to have to worry about a service failing periodically as it will just transfer to another node in a few seconds automatically.