Marcus Feltsen

@ehlomarcus

Technical Specialist at Betsson Technologies | Specializes in | Building hybrid-clouds in multi-domain env. Tweets are my own.

Vrijeme pridruživanja: siječanj 2010.

Tweetovi

Blokirali ste korisnika/cu @ehlomarcus

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @ehlomarcus

  1. proslijedio/la je Tweet
    25. sij

    This would be a better argument if most things today were programmed in bash. No one is arguing k8s isn’t great, they’re saying it’s a bit low level *as the developer-facing UX* for e.g. 90% of web apps, web services and simple functions

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    25. sij

    (A few) Ops Lessons We All Learn The Hard Way -- a Twitter 🧵:

    Prikaži ovu nit
    Poništi
  3. 25. sij

    Have come to the same conclusion. Will be interesting to see how this evolves.

    Poništi
  4. 24. sij

    Then we could choose if we wanted to use the rancher json api, or do it with yaml. Doing it with yaml is something we are aiming for. Not sure if it will work yet. But will soon find out.

    Prikaži ovu nit
    Poništi
  5. 24. sij

    With this I would really like for to open up docs on all of the Custom Resource Definitions that are available when you deploy into a clusters.

    Prikaži ovu nit
    Poništi
  6. 24. sij

    It’s like we at the beginning want it easy and help to get started. Then as we learn, we want to build our own and customize or use the raw tech. I guess and believe we will go full circle ⭕️, and appreciate the hard work others do.

    Prikaži ovu nit
    Poništi
  7. 24. sij

    is good, but it has its quirks and sometimes fails. But one of the things it does really well is hiding the complexities of the underlying tech. Almost to good, which we are finding out now.

    Prikaži ovu nit
    Poništi
  8. 24. sij

    Sort of out of the blue came . Which now have been the platform we’ve used for almost 1 1/2 years now.

    Prikaži ovu nit
    Poništi
  9. 24. sij

    Anyway. Then came a period of running this in prod and it worked, with some hiccups. A few month’s later it was sort of decided to standardize on Kubernetes. A few where evaluated. , etc.

    Prikaži ovu nit
    Poništi
  10. 24. sij

    Wasn’t totally onboard with this setup. It sort of conflicted with the knowledge of vSphere and VM networking. This new thing was totally unsecured, which got confirmed 2years later.

    Prikaži ovu nit
    Poništi
  11. 24. sij

    Started our journey with containers by jumping right at orchestration. No stand-alone docker hosts behind a F5 BigIP or anything. At first it was

    Prikaži ovu nit
    Poništi
  12. 24. sij

    Kubernetes, IaC, terraform, yaml. Wonders and fiction.

    Poništi
  13. 9. sij

    I think I have to credit the past 3 weeks vacation to the progress made today with 💪

    Poništi
  14. 6. sij

    The new year have only begun, and already finding new fascinating things that I didn’t know. Really cool thread 👇

    Poništi
  15. 17. pro 2019.

    Feel lucky to not having to deal with a service mesh yet. Working hard to get the underlying platform working smoothly, while thinking on the developer experience as no1. No1 issue is to easily address app, which equals ingress for us. Then and or

    Poništi
  16. 13. pro 2019.

    🌑🧙‍♂️. Looking good. Maybe I can learn some magic.

    Poništi
  17. 9. pro 2019.

    The original, 1.0 if you will, was a bit tighter at the same size as these new ones.

    Prikaži ovu nit
    Poništi
  18. 9. pro 2019.

    They finally arrived, th brand new 2.0 glove. The new liner will surely be a nice addition to test

    Prikaži ovu nit
    Poništi
  19. 9. pro 2019.

    And also lots of infra that could have been more standardized for easier deployment and scale-out.

    Prikaži ovu nit
    Poništi
  20. 9. pro 2019.

    Seeing lots of legacy that might not have been there if developers have had more freedom.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·