linuxdude314

Maybe if you’re a junior engineer, but this absolutely not what most SWEs do.

Right?! Get some free IP space from he.net tunnel broker and build your own IPv6 AnyCast network using Quagga for BGP.

Kidding about building your own AnyCast network (although you really could…), but he.net tunnel broker is GOAT.

This could all be solved using HE.net tunnel broker for free…

It’s not virtualization, it’s namespaces. Docker makes use of Linux kernel features; started out with cgroups and now uses libcontainer. Each container is running in its own isolated(ish) namespace on the same host kernel.

It’s _very_ different technology than virtualization.

You don’t need docker to make a container on Linux (or Solaris for that matter).

Virtue signaling your dislike of music because of the environment it is played in is asinine.

Do you wish you’d never listened to Mozart? He was a serial misogynist after all.

I can understand parents not wanting their children to listen to music with explicit lyrics, but for an adult to feel this way?

Music is not decadent.

You can do this with SSH alone.

https://tenshidev.medium.com/ngrok-you-might-not-need-it-de4...

FWIW the title of this article is a play on the title of Milan Kundera's famous book "The Unbearable Lightness of Being".

Pretty sure they were referring to the operators you can install that will stand up production ready replicated clusters.

They work quite well.

Why would you transcode on the NAS? Not what I’m suggesting at all; perf on most NAS is awful for that…

There’s a pretty well understood concept of what a NAS is; this isn’t a complicated philosophical problem.

A very common workflow in motion picture production is to use NAS for storage on a fast network, mount the SMB share, have a script/tool/app that monitors the ingest directory and writes to an output dir.

FWIW the key differentiator between a NAS and other types of network storage is the protocols they use.

If files is the main primitive, it’s a NAS; it’s its blocks it’s considered a SAN.

Sometimes SANs have NAS “heads” for clients that want file access or a block level storage device.

Did you build your NAS in the 90’s or early 2000’s?

This has been available in Synology and QNAP devices for that long…

I used to own the tape library that is the Disney Vault. A common pattern for transcoding is to have a watched folder. Drop files you need transcoded in, get files you want in a diff directory when finished.

It’s still not true.

This is the normal implication with C constant. Nothing is different.

First person in this thread to make any sense… The level of physics knowledge has declined on this site.

This is not true. You can easily measure TOF of a photon using an APD in Geiger mode or other detectors easily purchasable in 2024.

So what exactly are you talking about?

This isn’t true though…

You typically don’t even have to go to that length. This is usually supported out of the box.

No idea what problem this is trying to solve. Just seems like the user wasn’t familiar enough with how to use a NAS.

Just use OpenTelemetry. No need to keep reinventing wheels.

Tons; have you actually looked?

https://opentelemetry.io/docs/kubernetes/operator/automatic/ https://github.com/open-telemetry/opentelemetry-demo

Agreed this ask makes no sense to me.

It sounds like they want the system to somehow know which IP is supposed to be associated with a particular key.

You already can restrict public IPs using iptables…

The examples are pretty silly, especially the first one.

If you know that you need either a shipping or billing address and the user has specified which one they need, just query based on that.

There’s no need to introduce a function (getTableName) to detemplate a string or match on a case.

Instead just create a function that gets the item you want from the DB and has the table name as input.

On your UI make sure when the users specifies billing or shipping address the correct parameter is passed to the API.

If I were in your position I would craft my own OTel distribution and ship it.

This is very easy to do: https://github.com/open-telemetry/opentelemetry-collector-bu...

With this approach you’re standing on the shoulders of giants, compatible with any agent that speaks OTLP, and can market your distribution as an ecosystem tool.

Why would you not use OTel?

This is clearly the industry standard protocol and the present and future of o11y.

The whole point is that o11y vendors can stop reinventing lower level protocols and actually offer unique value props to their customers.

So why would you want to waste your time on such an endeavor?

Vector is GOATed, also reccomend.

It’s really not abnormal. GrafanaLabs does this all the time with their IaaS product.

There’s nothing wrong with exposing Grafana as long as you’re following security best practices.

It’s 2024, zero trust networking is where you want to be. Real zero trust networking is NOT adding a VPN to access internal services. It’s doing away with the notion of internal services all together and securing them for exposure on the internet.

This really sounds like a _you_ problem and not something you need hardware to fix.

You can already enable silence/focus time bypass modes for apps like PagerDuty and such…

If you can’t develop some sense of responsibility to check if you’re on-call, frankly you have no business being in an on-call role.

No hardware will make you or your engineers more diligent. The only reason pagers made more sense than phones is/was because of protocol reasons NOT because it’s some separate device.

As someone who literally used to own the digital version of the Disney vault I find this leak highly unlikely what it is claimed to be.

Disney doesn’t just use one Slack instance across the whole company and everyone knows to not put pre-release content on my public platforms.

Maybe they compromised an instance owned by DTSS (Disneys centralized IT entity), but this would have little to do with Disney Studios like they imply.

Its pretty standard in the industry to only store pre-release content on airgapped systems.

I get that it’s Jeff, but why is this on the homepage?

Silly to think this is relevant at all to HN.

If you need something like this to use k8s you’re probably better off with a different solution.

Kubernetes is not intended to be something you use with no background. It’s hard, and without making a full blown PaaS there’s no getting away from that complexity.

Agreed, this makes little sense to me.

Fundamentally there’s no such thing as a k8s “package”. OLM is great for packaging operators, but I don’t see why we need yet another Helm.

It was a mistake that shouldn’t be repeated.

This fails completely even at small scale when the script is interrupted before finishing.

The difference between just using some Python vs Terraform is idempotency. TF isn’t going to touch the nodes the script succeeded on; if you have to start your for-loop script it will, which may not be desirable.

Frankly these days configuration management is a bit dated…

You’re much better off in most cases using a tool like Packer with whatever system you want to bake an image, then use a simple user-data script for customization.

It’s very hard to scale continuous config management to thousands of servers.