# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 15
# self = https://watcher.sour.is/conv/ztwih5a
Phippy and friends: bringing cloud native concepts to the masses
At KubeCon + CloudNativeCon North America last week, we welcomed Hazel the Hedgehog and Linky the Lobster to the Phippy and Friends family, thanks to the Helm and Linkerd project teams. Hazel... ⌘ Read more
\n\n> Phippy and friends: bringing cloud native concepts to the masses\n\nWith Kubernetes? 🤔 I don't think so ! 😂 k8s is a complicated over engineering monstrosity! 🤣
> Phippy and friends: bringing cloud native concepts to the masses
With Kubernetes? 🤔 I don't think so ! 😂 k8s is a complicated over engineering monstrosity! 🤣
> Phippy and friends: bringing cloud native concepts to the masses
With Kubernetes? 🤔 I don't think so ! 😂 k8s is a complicated over engineering monstrosity! 🤣
@prologic It is. 😭 But some people are convinced that it’s awesome, so we have to use it at work. 😭😭😭
@prologic It is. 😭 But some people are convinced that it’s awesome, so we have to use it at work. 😭😭😭
@prologic It is. 😭 But some people are convinced that it’s awesome, so we have to use it at work. 😭😭😭
@movq and what problems does it solve for you that say Docker Swarm or Nomad can’t? 😂\n\nOr better yet; Why was Kubernetes chosen? 🤔 Let me guess…\n\n> Because everyone else is using it it must be good !\n\n🤣
@movq and what problems does it solve for you that say Docker Swarm or Nomad can’t? 😂
Or better yet; Why was Kubernetes chosen? 🤔 Let me guess…
> Because everyone else is using it it must be good !
🤣
@movq and what problems does it solve for you that say Docker Swarm or Nomad can’t? 😂
Or better yet; Why was Kubernetes chosen? 🤔 Let me guess…
> Because everyone else is using it it must be good !
🤣
@prologic I can’t really compare k8s to those other tools, never used them. 🤔 At this point, we have so much stuff in k8s, it’s gonna be a lot of work to migrate away from it. 🤣
Our devs are pushing hard for k8s. They *might* be happy with another solution, but they know k8s very well know and it works well (for them – just not for me as a sysadmin), so there’s very little motivation to investigate other tools …
@prologic I can’t really compare k8s to those other tools, never used them. 🤔 At this point, we have so much stuff in k8s, it’s gonna be a lot of work to migrate away from it. 🤣
Our devs are pushing hard for k8s. They *might* be happy with another solution, but they know k8s very well know and it works well (for them – just not for me as a sysadmin), so there’s very little motivation to investigate other tools …
@prologic I can’t really compare k8s to those other tools, never used them. 🤔 At this point, we have so much stuff in k8s, it’s gonna be a lot of work to migrate away from it. 🤣\n\nOur devs are pushing hard for k8s. They *might* be happy with another solution, but they know k8s very well know and it works well (for them – just not for me as a sysadmin), so there’s very little motivation to investigate other tools …
@prologic I can’t really compare k8s to those other tools, never used them. 🤔 At this point, we have so much stuff in k8s, it’s gonna be a lot of work to migrate away from it. 🤣
Our devs are pushing hard for k8s. They *might* be happy with another solution, but they know k8s very well know and it works well (for them – just not for me as a sysadmin), so there’s very little motivation to investigate other tools …
@vain @prologic A few comments:\n\n1) I'm fairly new to devops, never mind k8s, :-P _but_ I found HashiCorp's blog post A Kubernetes User's Guide to Nomad really helped me get my head around where the 'nail' for the k8s 'hammer' is and isn't. (A similar page on the Nomad site generated a 500+ point discussion on Hacker News, btw, so I'll link to that too.)\n\n2) It's actually HashiConf this week, and, honestly, you'd swear _they_ made k8s for the number of times it's come up in the keynote alone! It's very clear they're changing course on their new product from last year, Waypoint, to ease the lives of k8s users. Your devs know it really well, but, I don't know, if you're planning on bringing on new devs at any point, something like this, that abstracts away a lot of the deployment architecture -- that, in my opinion ;-P devs should care less about -- and, importantly, from a sysadmin's perspective, means they'll be less likely to break k8s and all its bits that they currently 'mess with,' might be a good thing.\n\nI don't know; all devs probably roughly fall into two camps: those that *love* the idea of waypoint up to deploy, so they can get back to coding, and those who absolutely *hate* it and want complete control over the whole process, for every architecture they could be called to support at 2am. :-P