alberteinstein

10 ms·

1.
Hasura Cloud: Managed GraphQL for your database and services(hasura.io)
11 points by alberteinstein 6y ago|0 comments
2.
Linux Foundation Announces GraphQL Foundation(gql.foundation)
5 points by alberteinstein 8y ago|0 comments
3.
by alberteinstein 8y ago
Whether it's a gimmick or not, the fact that there is a need/demand for such products is a scary one. People want to wear bullet proof fashionable clothing since they are not sure when they'll be shot at? It didn't matte
4.
by alberteinstein 8y ago
The system with worst or no abort procedures is the Space Shuttle. Earlier versions had ejection seats, but they got rid of that. Imagine if they had Soyuz like capsule which can popped off. Both Challenger and Discovery crew would have bee
5.
by alberteinstein 8y ago
One of the authors here: You can open GraphiQL on any GraphQL endpoint using graphqurl: gq https://api.yelp.com/v3/graphql -H "Authorization: Bearer ACCESS_TOKEN" -H "Content-Type: application/gra
6.
Show HN: Graphqurl: curl for GraphQL with autocomplete, subscriptions, GraphiQL(github.com)
3 points by alberteinstein 8y ago|0 comments
7.
by alberteinstein 8y ago
Please do reach out to us on discord [1] if you have any questions whatsoever :) [1]: https://discord.gg/vBPpJkS
8.
by alberteinstein 8y ago
The GraphQL Engine is written in Haskell, the Console in JavaScript and the CLI in Go. The repo contains all the three components. :) (I am one of the maintainers)
9.
by alberteinstein 8y ago
We built this tool to bootstrap vendor specific declarative templates (Google Cloud Deployment Manager Template [1], Azure Resource Manager Template [2] etc.) that provisions a Kuberentes cluster (and disks), because writing them by hand is
10.
Show HN: Kubeformation – simplify cluster creation on managed kubernetes vendors(kubeformation.sh)
13 points by alberteinstein 8y ago|1 comments
11.
by alberteinstein 8y ago
Co-author here. We built this tool to bootstrap vendor specific declarative templates (Google Cloud Deployment Manager Template [1], Azure Resource Manager Template [2] etc.) that provisions a Kuberentes cluster (and disks), because writing
12.
Create declarative cluster specifications for your managed Kubernetes vendor(kubeformation.sh)
18 points by alberteinstein 8y ago|1 comments
13.
by alberteinstein 8y ago
Indeed! And when the logs show nothing being wrong? All k8s components were reporting that everything is fine.
14.
by alberteinstein 8y ago
Using netstat/lsof/tcp_dump from inside the containers did not help unfortunately. Eventual next step was to check nodes and kernel logs revealed the issue rightaway.
15.
Debugging a TCP socket leak in a Kubernetes cluster(blog.hasura.io)
61 points by alberteinstein 8y ago|11 comments
16.
by alberteinstein 9y ago
Spacemacs in Vim mode: best of both worlds
17.
by alberteinstein 9y ago
Yes, ksync and telepresence lets you develop on k8s cluster as if you were doing on the local system. Haven't looked at forge yet. These tools are really useful when you're writing code dependent on other components or features on
18.
Draft, Gitkube, Helm, Ksonnet, Metaparticle, Skaffold – Comparison of K8s Tools(blog.hasura.io)
79 points by alberteinstein 9y ago|22 comments
19.
by alberteinstein 9y ago
Gitkube is simpler since everything is contained in the cluster itself. Image is built and rolled out from within the cluster right now. (gitkube contributor here)
20.
by alberteinstein 9y ago
Kubernetes will definitely be an overkill if you run only one container. But, if your application follows microservice architecture and have multiple containers, Kubernetes is the best solution to run them. Kubernetes architecture is entire
21.
by alberteinstein 9y ago
Yes, it does. Kubernetes can perform rolling updates [1]. One scenario is that when you rollout a new version, the old container will only be killed when new one is up and running. If there are many replicas running, Kubernetes will replace
22.
by alberteinstein 9y ago
If you use container orchestration platforms like Kubernetes, this is not required, as restarts load balancing etc. are handled by the orchestrator.
23.
by alberteinstein 9y ago
True, optimising with a multi-stage build after `yarn build` should do it.
24.
by alberteinstein 9y ago
This doesn't happen on Kubernetes. The Pod stays in ContainerCreating state unless the entire image is pulled. We are running some Java containers which are >2GB and apart from the time it takes to start-up on a fresh node, everythi
25.
by alberteinstein 9y ago
This adds an un-necessary dependency between services. Team working on service A would need to coordinate with team working on service B to keep same layers. The contract should be to keep the image size as small as possible, and teams can
26.
by alberteinstein 9y ago
#4: Another motivation for using Alpine is to have a shell available so that quick debugging is possible if something goes wrong. For e.g. use ping to see if DNS lookups are happening in a Kubernetes cluster.
27.
by alberteinstein 9y ago
When a container is scheduled to a node in Kubernetes, if the image is already available, it takes only ~2s for it to be up and running. But, if it is not present on a node and the image is of 2GB, the download speed is the rate limiting fa
28.
by alberteinstein 9y ago
Thanks, will try this out and update.
29.
by alberteinstein 9y ago
Having two different versions is not an issue, tools like GVM helps in managing them. Docker helps in handling this easily without any extra tools. But, if something is built with a version, it cannot be easily changed without thorough test
30.
by alberteinstein 9y ago
Thanks! Will try, test and update regarding points 1,2,3. My use case required ca certs but I'll mention the scratch alternative too.

More ›