Installing WordPress through a traditional Apache server shared hosting account only requires one click, and you can host as many sites as you want for like $9 per month.
Ok so just learn Kubernetes. And then realize that for it to be useful in a production environment, it needs like 10 other third party things, which you’ll also have to learn, and you’re done!
Thanks. So TL;DR it allows you to set up a little cloud computing service on your own physical machines, minus load balancing which you have to add on?
It can be used to scale cloud computing services as much as you want. It’s a scalable container runtime at its core. It provides a means for scaling an overlay network with service discovery and uniform ingress configuration.
I’ve found it best explained in some stackoverflow answer mentioning the pet vs cattle analogy. In short, if you know how many servers you have from the tip of your tongue, and what they do more or less, then they are akin to pets: you treat them well and keep an eye on each of them.
Kubernetes is meant for when you have so many of them, that come and go without you even noticing or caring, bearing a number for the sake of production/cost control, this is cattle. Needless to say that this is not your typical app/company running at such a scale, and that there is a 24/7 team of “ranchers” keeping an eye on the herd.
10 is a bit exaggerating. What do you really need?
ExternalDNS is nice so you don’t have to config your DNS manually. You might need to install your own Ingress controller. If you want to automatically add and renew certificates cert-manager is great. Security is important! Speaking of, you should add some kind of secret management (something like sealed-secrets, vault or Secrets Store CSI Driver).
A really important thing is monitoring so you know your pods and the cluster itself is healthy. Prometheus is still king in that regard in my opinion. PromQL isn’t that hard. Of course some kind of alerting like AlertManager is a must for prod environments. Be aware that the front ends of those tools are not behind a login so something like oauth2-proxy and dex is vital! You might want to have some visualisation too so Grafana is a nice addition. If you add Loki too you got your OPs covered.
Keeping track of all of your stuff is the hard part so some GitOps is highly recommended. ArgoCD or FluxCD are popular for a reason!
I think that should cover the basic setup so you may scale your CRUD app without worries!
It’s been a few years since my networking course, but I believe it refers to DNS it refers to stuff like IP addresses. DNS is related to the Internet layer, but it’s not correct to call it the Internet layer
DNS is an application layer on top of the Internet layer that lets you have host names (i.e. “www.google.com”) towards the user side instead of IP addresses (i.e. 127.0.0.1).
However the internet layer only understands IP addresses so any application that is using hostnames internally and for displaying to the user has to translate them into IP addresses (using DNS) as it has to use those for the internet layer to know which hosts it wants to talk to.
URLs are yet something else: they’re a text format for encoding protocol, host if applicable (in name or in IP address), IP port if applicable and protocol specific stuff (i.e. the page address on a website) to form an application level “address”, which is more than just the host address (as that’s only a machine on the network, not a service hanging from an IP port on that machine waiting for requests).
People are so used to web URLs that they often don’t know URLs can encode more than just pages in what they think as “normal” web addresses (such as www.google.com and www.google.com) and can actually support the same protocol in a different port (www.google.com:8080 - note that this one probably doesn’t work because google just uses the default port for HTTP which is 80 and doesn’t have an HTTP server running in 8080), host identification by IP address instead of hostname (i.e. 127.0.0.1) and even different protocols (i.e. ftp://127.0.0.1).
This meme is kind of wrong though, because it’s mixing the OSI model with the TCP/IP model, which are different representations of the same thing, but in either model the “link layer”, ie layer 2 switching would never hand over to the “internet” layer without going through network first. So if you’re confused, it’s because it’s wrong.
The internet layer of the TCP/IP network stack is where the packets are routed between hosts. It operates between devices that have their own logical (IP) addresses, such as computers, routers, modems, or network bridges. It is the layer where the packet finds its way from the sender to the destination. Its most common protocols are IPv4, IPv6, and ICMP.
Might be true, honestly. I'm on NixOS using the proprietary drivers for my 3080 and 4090. No issues, took one line of configuration. I do have to stay on X11 unfortunately until Wayland supports the real drivers at least (though i hear that's being worked on, maybe already working?).
For all of NixOS' pain, it really does make some things awesome and simple.
Actually he was helping decommission that datacenter as the company was consolidating in another location. This was near the end of the decommission. My buddy worked as a datacenter tech under this guy with one other on the team and all 3 of them got pictures with this. This is the only one that went viral as far as I’ve seen though.
Encrypt then sign. Verification is often much faster than (or at worst as fast as) decryption. Signature can also be verified without decryption key, making it possible to verify the data along the way.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.