Hacker News new | past | comments | ask | show | jobs | submit | szszrk's comments login

We considered this in my team, to have a feel of real office, but after a few weeks remote it was obvious we rather need some guaranteed no-zoom time, then more zoom.

edit: even without that idea implemented!

That's an odd default to send it to the Internet...

And a disturbing trend that it is becoming so common as to be normalized.

Soon people are going to be asking "you don't have anything to hide, do you" when you want to run and debug locally.

For me it means that project is just a toy. Maybe an amazing one, but still.

In most of my positions in the past pushing random company data outside is a serious nono. I have enforced and agreed on that myself. So me using recklessly such a project naively thinking it will act politely means I might not have a job any more.

So - maybe I would play with it at home, but if I won't ever use it at a job (AGPL also adds to it), why bother?

I'm curious of other answers as well, but one place that kind of does what I think you ask for is [0]. Also you can get nice info from kubectl [1]

[0] https://kubernetes.io/docs/reference/generated/kubernetes-ap...

[1] kubectl explain deploy --recursive

That's a really nice documentation page, however what's missing in my eyes is an example or two for each parameter in YAML format. Personally, when attempting to use Docker Swarm, things like that were immensely useful, even more so for Hashicorp Nomad and its somewhat niche HCL.

I know that people like to use something like Kustomize (https://kustomize.io/) and Helm (https://helm.sh/) at least last i checked, but it's also really nice to be able to read up on everything without necessarily following tutorials and such, or using specialized tools.

For example, with Docker Swarm, if i want to change how restarts would be handled, i have a really easy reference available: https://docs.docker.com/compose/compose-file/compose-file-v3...

But with Kubernetes, in the first linked page i find a short description (just scroll down a bit or CTRL+F "restartPolicy") which doesn't offer further parameters: https://kubernetes.io/docs/reference/generated/kubernetes-ap...

To its credit, there is a link to another page as well which contains more information: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifec...

That said, usability wise i'd have to spend more time to figure out how to get my containers/pods restarting just once every 1 minute as opposed to whatever the default is (say, low end cluster with limited resources) with Kubernetes instead of other technologies, due to this difference.

I can relate to all your experiences. Swarm has such a nice learning curve and I wish it would still be used widely.

With K8s I guess we are between a really decent (!) documentation that doesn't work very well as a "tutorial", and third party resources that does that.

It does make things harder at the beginning, but is still much better then, say, Hashicorps docs: "here is a cool starting tutorial that covers basics you'll need for the first 30 minutes. That is all, look other things up in the code". For a longer while I felt this was the case with Vault or Consul.

Why? What's the alternative?

I see a lot of things that has to be solved on your own even when using Helm. I find their templates repulsive. But "avoid helm" is not an advise, really. How do you suggest to structure, version, deploy, encapsulate with important metadata your deployment descriptions? How do you package it? Is there anything else that integrate with larger tools like Rancher so well?

Kustomize look it up, much more native for k8s apps

Disagree. Plain Pi won't be able to attach 4 sata drives natively and is not a real alternative for actual NAS. This might be. Jeff does a lot of Pi-NAS testing and I'm thankful for that, as I find of the shelf solutions lacking a lot. Mostly software-wise. There is a huge demand for a simple NAS device that is not much larger then drives it uses, but doesn't have Qnap OS installed on it.

It has good network connectivity. 2.5G is a nice option for homelabs and actuall advanced home use.

> There is a huge demand for a simple NAS device that is not much larger then drives it uses, but doesn't have Qnap OS installed on it.

So how did this article enlighten you on software alternatives to Qnap?

Not saying the board is uninteresting, I do like these new PCIe breakout Pi "motherboards". But the whole I built a $5k server is the wrong way to sell it.

> a simple NAS device that is not much larger then drives it uses, but doesn't have Qnap OS installed on it.

Well, you could just install your favorite Linux distro on a QNAP NAS device. Cost-wise the Pi-NAS option isn't even competitive if you aim for similar spec and form factor and packaging.

I can, but:

a) it's hard to get support on the device when you can't provide any of the configuration dumps they ask (from their software) :)

b) It is not even close to being comparable in price with NASes Jeff tests and shows on his videos and blogs. PiBox (currently on kickstarter) is $250 in a version that has a full solution, including case, pi, charger, LCD, OS, fan, board to connect regular 3.5" drives... It is the same form factor, it has better spec than cheapest qnap devices.

Not sure about ARM-based NAS, but most x86-based QNAP NAS devices are basically a PC in hardware configuration with mature Linux support, so there's not really any support issue.

The PiBox case apparently can only house two 2.5" SATA drives, not regular 3.5" hard disks commonly used for cheap mass storage. 2.5" hard disks seem to peak at 5TB per drive so the potential capacity is limited unless you go with SSD at much much higher cost.

The PiBox's 15W power supply leaves very tight margin for its components: Pi4 peak power consumption is about 6.5W, two SATA SSDs will peak over 5W each as well, so you should watch for power for stable operation.

I couldn't find a 2.5" 2-bay NAS model so the form factor isn't identical, but the closest match is probably QNAP TS-230 w/ similar 4-core ARM A53 SoC supporting two 3.5" drives for $199. The obvious downside is that RAM is capped at 2GB and that might be a deal breaker if you want to run lots of apps, but for entry-level storage needs it should be sufficient.

PiBox with 2x3.5" is in the making, I'm actually waiting for it to be "released".

On Qnap and Linux - I'm not talking linux support. It... exists. I'm talking hardware product support. 2-3 years of warranty are standard in my region. But if I can't provide them with "proper" logs and allow them access using their software, they just won't investigate further.

I'm sorry but what you wrote I find very untrue. K8s is bloat, but comparing it to NPM is very unfair towards K8s.

I often see developers or admins who ask questions how to setup their "simple" setup in plain docker on dev machine, while all they have trouble with - networking, volumes, exposing services - is actually very simple with minikube. There is more cool learning resources as well, IMO. It's even easier if you use cloud providers. Creating a working cluster on Scaleway takes a minute and you can't really screw anything up. You'll waste more time looking for a proper credit card, or figuring how basic user auth and privileges work on AWS, etc..

Yes, there is a lot of "magic in the background", but I have not yet seen any developer who reviewed all 1000 dependencies in their Angular Hello World application...

The K8s itself is quite stable from simple user's perspective and does not follow very rapid changes. I am able to easily follow old tutorials, books and documentation that was not updated in a long time without much issues. If something was broken I usually knew how to fix that after first basic k8s training. Core concepts did not change much, or at all. Some things got tidied up, like storage abstraction, but it makes sense and it's nothing new. A lot of cloud integration is build into K8s for years, some integrations like ... ingresses that implement certain external products are delivered mostly by vendors and it's quite easy to find options available.

There is a lot of mess into implementing proper production or large scale setup, misconceptions on how storage is handled and "why plain k8s does not provide Read Write Many storage out of the box?" kind of questions at the start. But a lot of that are issues that exist in any on premise infrastructure and has to be handled with a personal touch - taking in to account what you already have.

Yeah true, NPM is not the right comparison, I typed too fast, meant the frontend world and k8s world remind me of each other in certain ways. And I really find k8s and HELM im using not so stable, or ready, that's why everyone is using lots of different tools. I found old school Apache/Nginx a lot more stable. True Kubernetes solves a lot more problems, but as a result simple things, like a simple filesystem mount, causes all kind of issues.

I understood it more like "it was a very clever, well organized import/forwarding trade operation".

They diversified their wood sources, chose different sources for different parts produced, which made difference during general wood shortage. Also company created some clever tools like wind sawmill and ship designs.

The wind-powered sawmills is a good example of how building in the past were actually more advanced that one thinks about them.

I hope it's a research project and not an actual search engine. It's not bad, it's random in every field of response.

Searched for opensearch ssl setup, second result:

- Title is a chapter from mysql documentation;

- Site link is a burger restaurant in US;

- Description is "Setup instructions for Mail-in-a-Box";

Easily is an overstatement, given number of changes they did recently. I'm trying for over a year to find stable replacement for remarkable desktop app (which syncs all my data without my control) on a company computer for screen sharing. And have only just now found a way to do that in a stable way with the new "share" from RM and rmview 3 opensource app. Before that more things didn't work then did (various issues, crashes, incorrect screen sizes, all soft of things).

But I'm certain this idiotic step by remarkable will push more and more devs and hackers to polish their tools create more and more full/complex environment without their cloud.

But it clearly suggests it's his work. It isn't. Let the original author worry about how he protects his own work.

I understand where you’re coming from, but just finding things can be a lot of effort. If someone wants the images with no watermark, they can look them up

Oh, so I can go to your blog or science article with those nice, detailed posts, take all the photos you made yourself and then make a shitty article on the Internet including your hard work. I will just in case slam my own watermark, so it will look like I did it myself and will not include you as an author.

Apparently this sounds fair to you!

You're posting this on a site where the admin encourages users to post archive links to bypass paywalls. Wrong place for arguments that content creators get their fair share.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact