willejs

9 ms·

1. 31.▲
   by willejs 5y ago

   +1 for using hadolint! I have been using it for ages, and I highly recommend it. I also sometimes write some Goss tests, and even run Trivy at the final stages of the container build and delete them once done in the same layer. It takes abo
2. 32.▲
   by willejs 5y ago

   This sounds a bit like request collapsing on their CDN was enabled perhaps?
3. 33.▲
   by willejs 5y ago

   #HugOps
4. 34.▲
   by willejs 5y ago

   Spotify have it in the works, for release later this year. https://newsroom.spotify.com/2021-02-22/five-things-to-know-...
5. 35.▲
   by willejs 5y ago

   I guess this is a response to Amazon Music HD, and soon Spotify HiFi. I have been waiting for Spotify HiFi since the Feb announcement...
6. 36.▲
   by willejs 6y ago

   You beat me to it! https://news.ycombinator.com/item?id=16197436
7. 37.▲
   by willejs 6y ago

   I wish I knew this existed the other day, I spent about 10 minutes tracing all the crapware creative cloud had installed onto my macbook and deleted it. Some of it was using 5% cpu occationally, to do what?
8. 38.▲
   by willejs 6y ago

   See original author clarifying this wasnt a leak or a hack. https://twitter.com/donk_enby/status/1348666166978424832
9. 39.▲
   by willejs 6y ago

   This wasn't leaked, it was archived from public sources. https://news.ycombinator.com/item?id=25727025
10. 40.▲
    by willejs 6y ago

    This directly references the public archive team effort, not evidence of a the hack. The comment and “story” that is circulating seems like it’s just taking the public archive team effort and adding some sort of falsehoods around a hack whe
11. 41.▲
    by willejs 6y ago

    Your post just links to the list of public Parler posts that were scraped from the website. Not evidence of a hack.
12. 42.▲
    by willejs 6y ago

    That is just a list of parler public urls.
13. 43.▲
    by willejs 6y ago

    This post seems fake. There was a group of people archiving the public content of parler using this docker container https://github.com/ArchiveTeam/parler-grab and archiving it here https://tracker.archivet
14. 44.▲
    by willejs 6y ago

    Sops can use GPG key groups too. There are multiple encryption methods available, such as GPG, KMS (GCP and AWS) and azure key vault.
15. 45.▲
    by willejs 6y ago

    Kind of. Who ever is on call should be able to deal with the issue. Your highest level of escalation should be your engineering manager, VP of engineering or CTO. Your product manager should care about team health checks, and how much you a
16. 46.▲
    by willejs 6y ago

    If your writing software or operating infrastructure, you need to be on call. Otherwise you don’t have skin in the game. It makes you a better engineer, and at most places increases the quality of your software in two ways. One, you don’t w
17. 47.▲
    by willejs 6y ago

    I like this. I am a firm believer of keeping things simple until you need them. Service meshes have their place, and they are useful when your running at scale, or you really need all the features, but most people don't need them. You
18. 48.▲
    by willejs 6y ago

    I agree. However for a lot of people, their workloads have been running on x86 forever, maybe their production instances are not reproducible, and with combinations of cpu/memory/io being limited, at scale this could cost $$$. I’m
19. 49.▲
    by willejs 6y ago

    Sorry I made an edit to clarify what I meant as it was confusing.
20. 50.▲
    by willejs 6y ago

    Is it going to be interesting to see how new Apple machines running ARM based processors plays out. Writing code, and building docker images locally on ARM and building and running the same code on X86 in production could potentially, in so
21. 51.▲
    by willejs 6y ago

    google are now offering beyond corp as a product too it seems https://cloud.google.com/solutions/beyondcorp-remote-access
22. 52.▲
    by willejs 6y ago

    1. I usually advise people to raise an ADR when they are adding new component to a system, a new technology, or really anything that they feel needs context and want to have a discussion about. Usually I advise either making a pr in the rep
23. 53.▲
    by willejs 6y ago

    Previous discussion here https://news.ycombinator.com/item?id=11218677
24. 54.▲
    by willejs 6y ago

    I am presuming they are having some database issues. In their last incident we saw them mention running out of database connections. They also have some planned downtime when they are planning on switching quay to readonly whilst they perfo
25. 55.▲
    by willejs 7y ago

    Can't wait for someone on here to say: "This is why you should run your own gitlab instance".
26. 56.▲
    by willejs 7y ago

    Theres an interesting article about the technology behind the story by the company worked with MIB on this. https://www.anatune.co.uk/resources/blog/the-smell-of-parkin...
27. 57.▲
    by willejs 7y ago

    Everyone has avoided running tiller server for a while and ran it locally (tillerless) instead. It serves the same purpose and works around the huge potential security issues tiller causes when ran in the cluster.
28. 58.▲
    by willejs 7y ago

    Someone has actually just bought that!
29. 59.▲
    by willejs 8y ago

    I think so! I am reluctantly using it currently, it’s simplicity is great if your just building, testing and deploying to a couple of environments. So maybe it’s just good enough for most, and that’s fine. However, It’s practically useless,
30. 60.▲
    by willejs 8y ago

    I am looking forwards to digging in to this a bit more and figuring out how this compares to Istio. I am guessing integration with AWS services such as X-ray and Cloudwatch/logs are the selling point. Still, I am a bit weary about conf