Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kelseyhightower
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
Show HN: Kubernetes Certificate Manager – Native Let's Encrypt Integration
(github.com)
186 points
by
kelseyhightower
10y ago
|
19 comments
62.
▲
by
kelseyhightower
11y ago
I've been a big fan of ipvlan since it was added to the kernel[1] mainly for the reasons you've outlined and the overall reduction in complexity compared to bridges and overlay networks. It should also be noted that ipvlan offers
63.
▲
by
kelseyhightower
11y ago
Go's TLS support should be greatly improved in Go 1.6 thanks to the performance work you referenced by Cloudflare. The licensing issue was resolved and the work was merged 11/10/2016[1] While GC will always carry a cost, grea
64.
▲
by
kelseyhightower
11y ago
I don't think looking for better is the right way to go about this. There are many things that are different in Go which you might find a nice fit for a specific use case. Also, nothing wrong with learning another language to increas
65.
▲
by
kelseyhightower
11y ago
You're welcome. You have managed to capture the spirit of the post. The goal was to highlight areas where developers can take action, and how improving even the little things can go a long way to improving the entire system -- even the
66.
▲
12 Fractured Apps
(medium.com)
146 points
by
kelseyhightower
11y ago
|
50 comments
67.
▲
12 Fractured Apps
(medium.com)
19 points
by
kelseyhightower
11y ago
|
0 comments
68.
▲
by
kelseyhightower
11y ago
CoreOS was CoreOS before I got there. I came to CoreOS because of the open source nature of the company and the awesome collection of projects such as etcd, CoreOS Linux, and their work around containers. The release of Clair proves this wi
69.
▲
Introducing the Kubernetes Kubelet in CoreOS Linux
(coreos.com)
5 points
by
kelseyhightower
11y ago
|
0 comments
70.
▲
by
kelseyhightower
11y ago
I gotta say this is such a well written post and especially timely for me. I'm currently employed at a startup in a highly competitive market and I constantly think about "time to market", and "the competition". The
71.
▲
by
kelseyhightower
12y ago
I hope not! I can tell you first hand the majority of our team members work on our opensource projects. It's one of the main reasons I came to work for CoreOS over a year ago. But the concern is still valid -- will CoreOS really keep f
72.
▲
by
kelseyhightower
12y ago
It's true, the CoreOS team has been moving really fast. It's what startups have to do in the beginning -- before the money runs out :). While our announcement today introduces Tectonic and some funding, it also communicates that w
73.
▲
by
kelseyhightower
12y ago
This is something that all companies that set out to build great products have to figure out. Do you take the Apple path and attempt to build the best product possible, even if that means limiting where and what it runs on? While we try to
74.
▲
by
kelseyhightower
12y ago
This is a great question. CoreOS is currently working on adding support for Rocket[0] to Kubernetes. There is still a lot of work to do here, but things are progressing nicely. Kubernetes is a true opensource project and accepts contributio
75.
▲
by
kelseyhightower
12y ago
It's better to compare RedHat's Atomic Host with CoreOS Linux. Both projects are focused on providing a slimmed down Linux OS focused on running containers in a server environment. Tectonic would be closer to RedHat's Openshi
76.
▲
by
kelseyhightower
12y ago
Kubernetes is the perfect complement to CoreOS, and it's the type of cluster manager we would have built over time -- thanks Google! We started building fleet from the ground up with plans to build a higher level tool on top, which wou
77.
▲
by
kelseyhightower
12y ago
You bring up a really good point. Many of the docs on etcd promote the use of the discovery service[1] as a convenient way of bootstrapping an etcd cluster -- really useful when you don't know the IP addresses of each cluster member up
78.
▲
Rocket and App Container 0.2.0 Release
(coreos.com)
151 points
by
kelseyhightower
12y ago
|
33 comments
79.
▲
by
kelseyhightower
12y ago
For those looking for a little more context or who want to see the App Container Spec in action we recorded videos following the initial announce of Rocket -- the initial implementation of the spec. Rocket & App Container Spec Overview
80.
▲
by
kelseyhightower
12y ago
Disclosure: CoreOS employee. The application container specification (ACI) and the initial implementation, Rocket, are here to provide balance to the container ecosystem. If you review the draft spec ( http://bit.ly/1s4Om8p )
81.
▲
by
kelseyhightower
12y ago
That was my first question as well, but there must be a reason why Kubernetes was brought in.
82.
▲
by
kelseyhightower
12y ago
Disclosure: CoreOS employee; Kubernetes contributor. After reading the title I was a bit tempted to call BS since I think Kubernetes should have the rights to "The first Datacenter OS" tagline[1]. However, after reading up on the
83.
▲
CoreOS is building a container runtime, Rocket
(coreos.com)
902 points
by
kelseyhightower
12y ago
|
277 comments
84.
▲
by
kelseyhightower
12y ago
Again not to take anything away from consul-template or pyconfd, but confd supports "real-time" updates from both consul and etcd, the watch support was added about 2 weeks ago on the master branch. confd also has dry run support:
85.
▲
by
kelseyhightower
12y ago
confd author here. I'm glad to see this idea validated, and I think consul-template looks pretty awesome and well integrated with consul. consul-template takes advantage of consul specific features such as the consul services API and d
86.
▲
by
kelseyhightower
12y ago
Not to take anything away from consul-template, but that has been a feature of confd for a while: https://github.com/kelseyhightower/confd/blob/master/docs/te...
87.
▲
by
kelseyhightower
12y ago
Are you saying that compressed data should not be encrypted? We are trying to limit the amount of data we have to store in the backend K/V store. Can you provide links so I can read up on this. Thanks.
88.
▲
by
kelseyhightower
12y ago
Hopefully we corrected the docs and the comments here help, but we don't encrypt before we compress. We compress before we encrypt.
89.
▲
by
kelseyhightower
12y ago
Yeah, I'm open working with anyone on other client libs. Ideally we can track them in an official doc in the repo. To help others get started I'll document the data we store in etcd/consul in more detail. Ideally clients only
90.
▲
by
kelseyhightower
12y ago
Sorry, if I said that in the video. What we do is base64(gpg(gzip(data))) We gzip the data first, then encrypt it, finally base64 encode it.
More ›