webo

iirc, you have to do additional setup for Android 7+ apps -- installing a custom apk with modified manifest.xml for each app that you want to intercept TLS traffic.

SupplyPike | Software Engineer & Site Reliability Engineer | Fayetteville, Arkansas | Onsite | https://supplypike.com

SupplyPike is a place set on bringing innovation to a stagnant industry: supply chain. Here you'll find a motley crew of designers, engineers and data scientists working together to solve problems that supply chain professionals encounter everyday.

We are a very well backed startup that's is growing quickly. We grew from 5 people to 80+ (~40 engineers) in less than two years.

We constantly experiment with a wide array of technologies - Node.js, Python, React, AngularJS, GraphQL, AWS, Kubernetes, Docker, etc (more on that here: https://stackshare.io/supplypike/default). Although specific knowledge of programming languages and toolchains is useful, we are more interested in individuals with problem-solving abilities, intellectual curiosity, and eagerness to learn.

Please apply at https://supplypike.com/careers

I've been trying to think more about this model. How do people perform code reviews with incomplete features? I feel like you lose context as you review incremental commits that span across multiple days.

Slack permissions seem excessive:

>UNUBO will be able to send messages to any channel or person on your workspace.

>UNUBO will be able to read all messages, files, and profiles that you can access.

>UNUBO will be able to receive all messages and activity that occurs in {company} as well as send messages on your behalf.

Very beautiful. Where is this quote from?

We use vagrant with VMware Fusion. Haven't had much problem other than OSX upgrades occasionally breaking vagrant itself.

Mostly off-topic but I've been looking for more than a CI for some quite time, more on the CD side. How are you guys handling some of these cases? Bonus points for hosted options.

- Truly a pipeline based stages. No messing around with git branches/tags for each environment release.

- Ability to combine multiple builds together.

- Build dependencies. Ability to trigger project-B build when project-A build succeeds. (Docker Cloud Builds have something like this.)

- Use the same artifact across multiple build stages.

- An option to promote a build to the next step either manually or automatically.

Amazon's internal Apollo system was amazing. AWS Code Pipelines kind of does some of these things but it's every limited and hard to work with.

SupplyPike | Frontend, Backend, Devops Engineers | Fayetteville Arkansas | ONSITE (https://supplypike.com/)

SupplyPike is the fastest growing emerging technology company in Arkansas focusing on creating new and innovative ways to solve problems in Logistics and Supply Chain.

More about the role: https://drive.google.com/file/d/0ByeS3h3e7vQTWGtZZ0RkYmVBaVE...

Some of our stack: https://stackshare.io/supplypike/default

Frontend: JavaScript, React, Angular, Aurelia, TypeScript, websockets, etc. Backend: Node.Js, GraphQL, Python, Mongo, Redis, ElasticSearch, RabbitMQ, Big Data, etc. Infrastructure: Microservices, Docker, Kubernetes, AWS, terraform, prometheus, etc.

Interview process: 2-3 hour technical interview.

Questions/resumes: kanat [at] casestack.io

CoreOS Tectonic is not trademarked and is not unique.

Looks like OP's project started around November. I believe that's around when CoreOS Tectonic was released as well.

Is one year paid maternity/paternal leave normal in the UK/EU?

In the US it's only a few weeks, maybe a few months if at a really good company.

There are other tools your team need as well: git, nvm, rvm, awscli, terraform, kubectl, etc. Vagrant helps with pre-installing all of that, whereas docker is mostly for running specific containers.

Is the common pattern to support http2 at the highest level?

If a request goes through CDN/edge network -> Load Balancer -> nginx -> Python app, should http2 be enabled on all components or is enabling just on the CDN enough? Any pros/cons?

With HTTPS, usually enabling on the CDN is good enough for most cases.

The content of the article does not have anything to do with the title. There is not mention of how linkerd and k8s work together.

SupplyPike | Frontend, Backend, Devops Engineers | Fayetteville Arkansas | ONSITE (https://angel.co/supplypike/jobs/)

SupplyPike is the fastest growing emerging technology company in Northwest Arkansas focusing on creating new and innovative ways to solve problems in Logistics and Supply Chain. The team grew from 1 engineer to over 20 engineers in just over a year. We plan to continue to grow at that rate.

Some of our stack: https://stackshare.io/supplypike/default

Frontend: JavaScript, React, Angular, Aurelia, TypeScript, websockets, etc.

Backend: Node.Js, GraphQL, Python, Mongo, Redis, ElasticSearch, RabbitMQ, etc.

Infrastructure: Microservices, docker, Kubernetes, AWS, terraform, prometheus, etc.

Interview process: 2-3 hour technical interview.

Questions/resumes: kanat [at] casestack.io

For this we have been creating the CloudFormation in Terraform itself. CF is a giant mess to work with.

Great stuff.

We have been doing "state environments" using different var files and different state files for a while now, while keeping the same terraform files.

As long as you keep paying taxes in CA, I imagine this is not an uncommon practice.

Senior Backend Engineer shows 85-95k in Chicago, which is below average. It shows 45-55k for Fayetteville -- most junior guys/gals start around 75k in Fayetteville at mediocre companies.

I'm on a $30 unlimited data T-Mobile family/friends plan.

Since I'm not home a whole lot, I cancelled my ISP two months ago and have been tethering for two months. I can still work for home just fine, and watch Netflix in HD.

The speed is slowed down after 40Gb , and I get about 15-25Mb download speed.

Curious why are you still using a 3-year old version on your personal computer?

>EC2: why are you replicating EC2 instances or AMIs across regions?

Exactly to avoid single region outages?

You're right. We always have one container per pod so I didn't fully think about this.

Eviction works fine when k8s detects there's a problem. I was referring to cases like this one: https://github.com/kubernetes/kubernetes/issues/13385

No- liveness probe just restarts the pod if the check fails, doesn't kill it.

Also, in our case it doesn't help when CoreOs auto-upgrades docker versions :(

I'm really looking forward to rkt so that we can finally have a solid alternative to docker.

You may have misunderstood me. The case I'm talking is, the node reports Ready, but the pod itself is not functioning properly.

One common issue we have is the pod gets stuck in a restart loop (for whatever reason, including starvation of resources). k8s just keeps restarting it for days on that node, instead of simply rescheduling it after X restarts or some other condition.

https://github.com/kubernetes/kubernetes/issues/13385

We've been running Kubernetes in production for over a year. It has a steep learning curve and it takes a lot of time to fine-tune the underlying infrastructure (we use CoreOs) to make it production-ready. There still seems to be a lot of shortcomings of k8s that seem like should have been addressed by now:

- it is impossible to trigger a rescheduling / rebalancing. When a new node comes in (via AutoScaling policy or whatever), kubernetes doesn't do anything. Thus, the new nodes can be sitting there doing nothing.

- once a pod has been scheduled onto a node, it never reschedules it anywhere else. The node may be experiencing problems, thus the pod is affected. k8s doesn't do anything to heal that -- it could simply delete the pod so it is rescheduled somewhere else.

- docker itself constantly ships with a lot of bugs. To this day (we are on docker 1.12.6), we constantly have problems with the docker daemon hanging or becoming unresponsive. I'm not sure if k8s can do much about this, but I feel like it should since we don't directly control docker.

- doesn't integrate more tightly with the OS / cloud provider. For example, it could perform health checks and decide if the node should be restarted, terminated, or idle.

All of our services are stateless, so it would be nice to have the option for all the above, especially k8s started as being the solution for stateless apps.

I wonder if there's any significance too this.

In my experience, docker itself is not very stable, and swarm is nowhere close to Kubernetes offers.

Our team is <15 engineers. The set up is roughly as below. We have around 40 services. Ping me if you wanna talk more.

https://cloudcraft.co/view/5582ddd4-c6f8-4354-8f5b-9fb0a3744...

* Development: docker + docker-compose. Ideally, we would want to get rid of docker-compose for development.

* CI: Travis (planning on switching to something that is more on the CD side)

* Infrastructure management: terraform

* Prod: AWS, CoreOs, Kubernetes 1 master node and 5-6 worker nodes (m4.large) in an autoscaling group.

Infrastructure deployments and updates are done by Terraform. Blue/Green deployments thanks to the autoscaling group.

Kubernetes deployments and updates are done by kubectl.

There's still problems with each piece, but for the most part they work great without much trouble.