4 ms·

The author of this post is using v0.17 but the latest Kubernetes version is v0.21 and soon v1.0 will be out. Beware that some of the commands he uses have alrea

The author of this post is using v0.17 but the latest Kubernetes version is v0.21 and soon v1.0 will be out. Beware that some of the commands he uses have already been renamed (run-container to run and resize to scale). Also a tip, some resources have abbreviations, eg. you can pass rc instead of replicationControllers in the cli kubectl get rc -l name=www-nginx

ams6110 11y ago
Thanks for the tip. Yet another thing I will file under "see if it's still around in a few years" before I bother with it too much.
- zwischenzug 11y ago
  Trust me, it will be. RedHat, Microsoft and Google are backing it. The chances of it disappearing are minimal.
  - dkarapetyan 11y ago
    Wasn't OpenStack a thing like that too? Big company backing doesn't really mean as much as people think.
    - harlowja 11y ago
      It's still not a thing?? https://wiki.openstack.org/wiki/Contributors/Corporate https://wiki.openstack.org/wiki/Contributors/Corporate Looks to me like a pretty big list.
      - ossreality 11y ago
        lol, not only that OpenShift 3 is completely based on and built on top of kubernetes. people like ams6110 amuse me greatly. I picked Go and Rust before they were even on peoples' radar and kubernetes was the same. It's already got it's fingers everywhere.
      - detaro 11y ago
        It's a thing in that it exists, can be deployed, has industry backing and a lot of hype around it. And enough mindshare that no direct (open) competitor has a chance. But the difference between what it claims to be able to do and what you want to actually use without hiring a bunch of developers (if possible, those that build the feature you are interested in) is also a thing. Anything going above a basic feature set is quite tricky, and many components are of bad quality. Or have undocumented specialties and the only way to get support that can help is to track down the original developers on IRC. Or 3 components share a concept, but all do it in slightly different ways. To many cooks and all that... Many developers have recognized that, but cleaning up takes time & there are new bits and features added all the time. Which also means that if someone doesn't need the full feature set OpenStack promises a competitor (like using containers & Kubernetes maybe) can easily beat it. (I don't have that much experience using it myself, but I've heard the above from many developers, vendors and people trying to use it on conferences and online)
        harlowja 11y ago
        I'm well aware of all you have state, difficulties, to many cooks... [I'm one of the top 3 contributors to openstack right now]; but what u have just described IMHO is applicable to all projects that gain momentum (I mean look at what happened to node.js and io.js and the split or whatever that happened there), linux itself has lots of similarities (or so I have heard) so I am thinking this is just the nature of the game... TLDR; software takes time to mature, software that is subject to hype probably takes a little more time to mature (due to more people/cooks and more hype).
        felixgallo 11y ago
        thing is, you can deploy node.js or io.js, and they largely work according to the description or the documentation. Having seen 4 sequential openstack deployment failures and rollbacks, I wouldn't wish it on my worst enemy.
        harlowja 11y ago
        Out of curiosity where did these 4 sequential openstack deployment failures and rollbacks happen? Would whoever this is be willing to share 'their story' (because if they do they can help, the software matures and get better, if they don't share it, then well nobody can fix problems that won't be talked about/shared); at yahoo we've had 4+ deployments and have not had a issue (but we also have engineers and operators who know openstack in & out).
  - jacques_chester 11y ago
    Large companies have collectively backed all sorts of things that faded into obscurity. Tell me about the last CORBA system you worked on. What matters in the end is developer momentum. That's what will keep Kubernetes alive.
avtar 11y ago
"The author of this post is using v0.17 but the latest Kubernetes version is v0.21 and soon v1.0 will be out" Thanks for the heads-up. I was trying to keep up with Kubernetes development a few months ago and then lost track. Looks like 1.0 will be released on July 21 http://www.kuberneteslaunch.com/ http://www.kuberneteslaunch.com/ Looking forward to this.

ams6110 11y ago

Thanks for the tip. Yet another thing I will file under "see if it's still around in a few years" before I bother with it too much.

zwischenzug 11y ago
Trust me, it will be. RedHat, Microsoft and Google are backing it. The chances of it disappearing are minimal.
- dkarapetyan 11y ago
  Wasn't OpenStack a thing like that too? Big company backing doesn't really mean as much as people think.
  - harlowja 11y ago
    It's still not a thing?? https://wiki.openstack.org/wiki/Contributors/Corporate https://wiki.openstack.org/wiki/Contributors/Corporate Looks to me like a pretty big list.
    - ossreality 11y ago
      lol, not only that OpenShift 3 is completely based on and built on top of kubernetes. people like ams6110 amuse me greatly. I picked Go and Rust before they were even on peoples' radar and kubernetes was the same. It's already got it's fingers everywhere.
    - detaro 11y ago
      It's a thing in that it exists, can be deployed, has industry backing and a lot of hype around it. And enough mindshare that no direct (open) competitor has a chance. But the difference between what it claims to be able to do and what you want to actually use without hiring a bunch of developers (if possible, those that build the feature you are interested in) is also a thing. Anything going above a basic feature set is quite tricky, and many components are of bad quality. Or have undocumented specialties and the only way to get support that can help is to track down the original developers on IRC. Or 3 components share a concept, but all do it in slightly different ways. To many cooks and all that... Many developers have recognized that, but cleaning up takes time & there are new bits and features added all the time. Which also means that if someone doesn't need the full feature set OpenStack promises a competitor (like using containers & Kubernetes maybe) can easily beat it. (I don't have that much experience using it myself, but I've heard the above from many developers, vendors and people trying to use it on conferences and online)
      - harlowja 11y ago
        I'm well aware of all you have state, difficulties, to many cooks... [I'm one of the top 3 contributors to openstack right now]; but what u have just described IMHO is applicable to all projects that gain momentum (I mean look at what happened to node.js and io.js and the split or whatever that happened there), linux itself has lots of similarities (or so I have heard) so I am thinking this is just the nature of the game... TLDR; software takes time to mature, software that is subject to hype probably takes a little more time to mature (due to more people/cooks and more hype).
        felixgallo 11y ago
        thing is, you can deploy node.js or io.js, and they largely work according to the description or the documentation. Having seen 4 sequential openstack deployment failures and rollbacks, I wouldn't wish it on my worst enemy.
        harlowja 11y ago
        Out of curiosity where did these 4 sequential openstack deployment failures and rollbacks happen? Would whoever this is be willing to share 'their story' (because if they do they can help, the software matures and get better, if they don't share it, then well nobody can fix problems that won't be talked about/shared); at yahoo we've had 4+ deployments and have not had a issue (but we also have engineers and operators who know openstack in & out).
- jacques_chester 11y ago
  Large companies have collectively backed all sorts of things that faded into obscurity. Tell me about the last CORBA system you worked on. What matters in the end is developer momentum. That's what will keep Kubernetes alive.

avtar 11y ago

"The author of this post is using v0.17 but the latest Kubernetes version is v0.21 and soon v1.0 will be out" Thanks for the heads-up. I was trying to keep up with Kubernetes development a few months ago and then lost track. Looks like 1.0 will be released on July 21 http://www.kuberneteslaunch.com/ http://www.kuberneteslaunch.com/ Looking forward to this.