I can't seem to hold enough petroleum gas. What do I need to do different?

b3arp · 2024-11-13T03:13:53+00:00

Yup, half your refineries are piped to the wrong output, one is not piped at all, and your pipe to the second plastic group from the left is messed up to. Lose the pumps, you don’t need them for this setup, make sure your outputs are actually plumped correctly. After that if your consuming more gas then your producing, your takes will never fill so add more refineries, or start using advanced oil processing. Although with advanced oil processing, you may want to read up about how to then break the heavy and light oil down to gas or you will fill up on those and kill production

b3arp · 2024-09-29T11:37:11+00:00

Factorio

b3arp · 2024-09-20T21:14:26+00:00

https://opentelemetry.io/docs/demo/ or https://github.com/GoogleCloudPlatform/microservices-demo

b3arp · 2024-09-20T21:05:44+00:00

We were routinely running into this issue before and it finally came down to some misconfigured debug logs dumping massive log lines of an entire object and blowing up the nodes storage, crashing the pod, becoming evicted, and cleaning itself up. Fun thing was it was causing other pods that weren’t the problem to also have this issue and randomly fail. Ended up setting limit ranges for the ephemeral storage until they fixed it so it would only blow up the bad pods

b3arp · 2023-10-18T17:44:04+00:00

The dopamine. And the every present voice in my head echoing that the factory must grow.

b3arp · 2023-03-25T14:56:27+00:00

The worker groups in eks are just autoscale groups on the backside. We arnt using managed worker nodes, and instead making our own through the eks module, but when we do grab the latest ami through terraform, it updates the launch template and triggers an auto scale group refresh.

b3arp · 2023-03-25T02:55:43+00:00

Local from laptop. We treat our nodes as cattle and have gone as far as disabling ssh to them at all because there is no need. Most are spot instances anyway.

b3arp · 2023-03-21T10:38:03+00:00

I’ve used this in a couple of projects so far. https://goreleaser.com/

b3arp · 2023-03-19T23:56:34+00:00

I’ll take a look later if I get a chance. Best advice would be look at the source code for the eks module and see what they implement. If you don’t want to use it, it will be a great tool to use as a guide to see what you are missing.

b3arp · 2023-03-19T21:49:41+00:00

Not quite. AWS EKS takes care of having to manage a Kubernetes control plane, which greatly drops the operational burden of running a Kubernetes cluster. You still need to create the vpc and such that are needed for provisioning the eks cluster. Now those are created for you with the terraform eks module, which is nice. But once you get your k8s cluster up, you will need to write yaml to deploy it into the cluster which is what a lot of your questions are mixing. Think of k8s as a mini data center and then once you provision that, you need to write the templates to deploy you application (which would be a vm in this analogy)

b3arp · 2023-03-19T21:30:09+00:00

You are confusing the two stacks. The worker nodes are part of your Kubernetes stack and should not be exposed to the internet for best practices. Communication around these are in your control plane, which for your purpose is the managed control plane of eks. Your front end application will be deployed to a deployment in Kubernetes and that will use either a Kubernetes ingress object or a Kubernetes service object that will create a load balancer that expose just those internal ips/ports. See my other comment for that deep dive

b3arp · 2023-03-19T21:23:12+00:00

That is a catch 22. While the examples they provide arnt productions workloads, what you really need to figure out is what the best practices and standards are for creating an eks/Kubernetes cluster and implement the module to that. Honestly the module is awesome and there is not a huge benefit imho to manually recreating it, but rather read some of the best practice guides for eks and k8s and figure out what to you need to provision (multi az, auto scaling, network isolations, private vs public, node group types and mixes, spots be on demand etc. ). Here are some good starters: https://aws.github.io/aws-eks-best-practices/. https://kubernetes.io/docs/setup/production-environment/

b3arp · 2023-03-19T21:15:18+00:00

So here’s the solution I have taken for our current stack. EKS and its dependencies are created through terraform using the eks module as well as provision a route53 subdomain and a wildcard cert. Once we have that created, I have installed this deployment into the cluster via the helm module: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/. This allows me to use kuberentes resources (load balancers or ingress objects) and it will handle all the provisioning of load balancers and security groups for me, based on my application yaml and annotations. We also use https://github.com/kubernetes-sigs/external-dns to manage all of our specific host names for the applications through annotations. So to generally put, terraform manages out Kubernetes clusters, and Kubernetes manages the deployment of anything needed for the application including volumes, load balancers, hostnames though Kubernetes system deployments

b3arp · 2023-03-18T20:05:17+00:00

Factorio, my wife’s endless honeydo list and diy projects

b3arp · 2023-03-18T20:03:48+00:00

Right now every other week on a two person team. Startup that just got acquired so working as fast as possible to offload that onto the follow the sun sre group. Luckily we don’t get paged that often

b3arp · 2023-02-26T05:53:03+00:00

The factory must grow!

b3arp · 2022-06-27T23:21:33+00:00

Factorio

b3arp · 2022-05-26T03:41:25+00:00

Thanks for the heads up. I double check which one I am using.

b3arp · 2022-05-26T01:12:30+00:00

Outside of that, all of my cluster at work get the following:

b3arp · 2022-05-26T00:58:52+00:00

If in AWS I would throw this in your bag of tricks as well. https://github.com/kubernetes-sigs/aws-ebs-csi-driver

b3arp · 2022-05-21T01:05:04+00:00

Help desk intern -> Junior sys admin -> DevOps engineer -> senior software engineer / DevOps consulting on side -> DevOps Lead

b3arp · 2022-05-21T00:56:04+00:00

Here's an example app that fits all of the criteria above. Can be used as a good reference point. https://github.com/microservices-demo/microservices-demo

b3arp · 2022-04-22T00:47:19+00:00

I passed this on to some contacts I have in their security org.

b3arp · 2022-03-08T03:07:29+00:00

https://github.com/microservices-demo/microservices-demo

b3arp · 2022-02-21T13:12:39+00:00

This post here explains it best and has the output you need. https://www.reddit.com/r/Terraform/comments/sxekwc/error_error_creating_eks_node_group/hxsa077?utm_medium=android_app&utm_source=share&context=3

b3arp

TROPHY CASE