Live data from Hacker News

Viewing profile — nicolast

nicolast

HN member
Joined
Mon, Dec 19, 2011, 1:58 PM UTC
HN karma
1,108
Public activity
100 items

About nicolast

Multi-language, multi-paradigm hacker, spreading noise using @eikke, formerly working at @Scality on #Kubernetes and #OSS projects.

Recent public activity

  1. comment
    Comment #37270697

    Exactly: a non-blacklisted IP with good reputation, correct mailname and valid PTR record is the foundation, ideally augmented with SPF. I've been running an e-mail service without…

  2. story
  3. story
  4. story
  5. story
  6. comment
    Comment #35280673

    I am indeed. Feel free to reach out, would be happy to learn from the approach you took.

  7. comment
    Comment #35280212

    You may be interested in https://discourse.haskell.org/t/towards-an-actor-framework-f... , then!

  8. story
  9. comment
    Comment #34183613

    For this kind of decisions, why not simply keep notes as comments in the code? These can easily be added later, even 14+ years after the code was written. Then, when someone dives …

  10. comment
    Comment #30699277

    GoPro would like a word.

  11. story
  12. comment
    Comment #28368545

    There's also 'AX_APPEND_COMPILE_FLAGS' [1] (and its dependency 'AX_CHECK_COMPILE_FLAG' [2]), next to many other (related or unrelated) macros in the autoconf archive. [1] https://w…

  13. story
  14. comment
    Comment #25512157

    An 'easy' way to deploy a cluster could be using kubeadm. Then you'll need a CNI like Calico to get Pod networking up-and-running. However, you'll want to install a bunch of other …

  15. comment
    Comment #25512115

    > first of all with k3s keeping a production cluster running is still pretty easy. Fair enough. I'll admit I have no direct experience with K3s. There are, however, many K8s deploy…

  16. comment
    Comment #25512008

    My comment above did not come out of the blue, but based on real-world experience ;-) You may be interested in our MetalK8s project [1] which seems related to yours. [1] https://gi…

  17. comment
    Comment #25508780

    > Getting Kubernetes up and running isn't really the issue anymore, that's pretty easy to do. The tricky part is long term maintenance and storage. This times 100. Deploying basic …

  18. comment
    Comment #24777290

    > How to distribute secrets if not by env? (which I agree! Honest question) You'll want to use BuildKit (`docker buildx`), see https://docs.docker.com/develop/develop-images/build_…

  19. comment
    Comment #24541757

    Not an Arrow expert at all, so I may be missing something, but I fail to understand the "The Science of Reading/Writing Data" section, or rather, its relevance to the article (and …

  20. comment
    Comment #22432461

    Not all services exposed to the outside are HTTP(S).

  21. story
  22. comment
    Comment #20582665

    Cases like this seem to confirm the approach LetsEncrypt took of only issuing certificates of a somewhat-short lifetime, which kind-of forces a user to fully automate the handling …

  23. comment
    Comment #18993713

    There's https://github.com/openstack/ansible-hardening and https://github.com/dev-sec/ansible-os-hardening

  24. comment
    Comment #18944759

    > If you verify that your hardware is unstable, how can you expect the software not to fail and corrupt data? No such thing as 'stable hardware' at scale.

  25. comment
    Comment #18672316

    I'm not involved in the Phippy 'project' in any way (only got a copy of the books and some plastic version of the animals as a speaker here at KubeCon :-D). I agree the wording may…