I'm curious to what this means for the existing puppet code base, is it now irrelevant, or are there still usages for it in the k8s world?
Needa bootstrap your k8s servers somehow ;)
Kubernetes at GitHub
101–110 of 142 posts
Re: Kubernetes at GitHub
#102Earlier quoted context omitted.
Tectonic is Enterprise Kubernetes. We start with pure upstream Kubernetes at the core and install it in a production ready setup with the Tectonic Installer[1] across clouds or bare metal. On top of those basics Tectonic provides things most organizations need: - Authentication backed by LDAP/SAML/etc - One-click automated updates of the entire cluster - Pre-configured cluster monitoring/alerting There is a bunch mor…
I'm currently deploying Tectonic flavoured Kubernetes at a large organisation and I can vouch for how great you guys are at supporting users (who are not yet customers) at any stage of the process - love that, and can't recommend you guys for that more. However, as the comment above says, Tectonic (and Quay for that matter) documentation is... just horrible and if not the engineers support, I'd be pretty much stuck o…
Happy to report that the Tectonic docs are open source and we would love to review your PRs: https://github.com/coreos/tectonic-installer/tree/master/Doc...
Any topics that stick out as needing the most attention? Glad you're enjoying your interaction with our engineers :)
(Product manager for Tectonic)
Re: Kubernetes at GitHub
#103Any favorted training for learning Kubernetes? I found this one so far: https://classroom.udacity.com/courses/ud615 But any extra courses/trainings is always appreciated
Udemy: https://www.udemy.com/learn-devops-the-complete-kubernetes-c... Pluralsight: https://www.pluralsight.com/courses/getting-started-kubernet...
I'm got that Pluralsight one earmarked for 'soon'.
I thought Nigel Poulton's Docker courses were excellent, so looking forward to it...
Re: Kubernetes at GitHub
#104Earlier quoted context omitted.
Red Hat's OpenShift makes it a lot easier by providing all of the infrastructure around it (docker registry, docker build from Git, Ansible integration and so on). Best docs of all open source projects I've seen.
I second this. Have been PoCing OpenShift for a couple of months now and it's been a joy to use.
3rd for sure. We're a RH partner and specialize in OpenShift work. Tons of excitement with customers on using OpenShift. I love it.
Re: Kubernetes at GitHub
#105Love to see more Kubernetes success stories. I work for an ISP and we are trying to write another success story ;) As an ISP, we have tons of constraints in terms of infrastructure. We're not allowed to use any public cloud services. At the same time, the in-house infrastructure is either too limited, or managed via spreadsheets by a bunch of dysfunctional teams. For my team, Kubernetes has been truly a life saver wh…
From the ops side, I would also suggest to take a look at Mesos, DC/OS and Marathon. Kubernetes, like Docker, is more developer-friendly; DC/OS is more ops-friendly. DC/OS can use Kubernetes natively.
>DC/OS can use Kubernetes natively.
Although this is possible. I've never actually heard of anyone using this in production. Would be curious to know what kind of issues ppl run into with this in production.
Re: Kubernetes at GitHub
#106Earlier quoted context omitted.
You should take a look at Deis Workflow. I say this in spite of the fact that it was announced last week[1], the next release of Deis Workflow will be the last (under the current stewardship, and probably under that name.) It's just such a solid system, I would even more strongly recommend the (already EOL'ed early last year)[2] Deis v1 PaaS, except that you've already indicated you're moving to K8S, and Deis v2 is d…
I'm still waiting for anyone who downvoted to tell me what better alternatives to Deis Workflow exist. I would rather have a better solution than a supported one.
I'm still waiting for anyone who downvoted to tell me what better alternatives to Deis Workflow exist
The kind of people that prefer to downvote you because you said something they didn´t agree with are by definition not the kind of people that would have anything meaningful to contribute. Downvoting on HN is increasingly getting in the way of the utility of HN. I used to come here for the interesting discussions. I don´t bother that much anymore.
Re: Kubernetes at GitHub
#107Earlier quoted context omitted.
I'm still waiting for anyone who downvoted to tell me what better alternatives to Deis Workflow exist. I would rather have a better solution than a supported one.
I'm still waiting for anyone who downvoted to tell me what better alternatives to Deis Workflow exist The kind of people that prefer to downvote you because you said something they didn´t agree with are by definition not the kind of people that would have anything meaningful to contribute. Downvoting on HN is increasingly getting in the way of the utility of HN. I used to come here for the interesting discussions. I…
Yeah I see a lot of downvotes, but I must be getting almost as many upvotes because I don't seem to be gray text...
Drive-by downvoters definitely bother me! I try not to let it bother me though.
Re: Kubernetes at GitHub
#108Earlier quoted context omitted.
Hey, this is Aaron from GitHub. We're using devicemapper w/ LVM backed pools. Would love to hear about your experience there. We definitely see this problem during periods of high container churn.
Any particular reason you didn't choose something like overlay2?
Assuming they are using RedHat, they only recently announced overlay2 will be fully supported in newest release 7.4
Re: Kubernetes at GitHub
#109Earlier quoted context omitted.
From the ops side, I would also suggest to take a look at Mesos, DC/OS and Marathon. Kubernetes, like Docker, is more developer-friendly; DC/OS is more ops-friendly. DC/OS can use Kubernetes natively.
>DC/OS can use Kubernetes natively. Although this is possible. I've never actually heard of anyone using this in production. Would be curious to know what kind of issues ppl run into with this in production.
No way I am running ZooKeeper AND etcd.
Re: Kubernetes at GitHub
#110Earlier quoted context omitted.
swarm is a batteries-included system. you can use it in the way that kubernetes is used... or (if you dont have all these sophisticated load balancers), you can allow it to load balance for you. https://docs.docker.com/engine/swarm/ingress/#publish-a-port... What it means is that when you create a docker swarm - it starts working.
Thanks for the link, but this sounds the same as Kubernetes' Service NodePort.
I think I hashlinked directly. I wanted to post the main page. Ingress also use nodeport, the difference is not in nodeport..But in the ingress setup itself.
Docker Swarm's inbuilt ingress is now trying to build in proxy protocol and ipip mode for default usage.
Fwiw, you can use Swarm's inbuilt ingress with an external load balancer as well.