
Closed
Posted
Paid on delivery
I run production workloads on AWS EKS and, from time to time, I hit two recurring pain points: pods that restart in loops and source-to-destination reachability failures inside the cluster. When a CrashLoopBackOff or abrupt connectivity drop appears, I need an expert who can drop in quickly, trace the cause, apply a solid fix, and then document what was done so the issue stays resolved. The work usually involves digging through Kubernetes events with kubectl, checking CloudWatch and container logs, inspecting liveness/readiness probe settings, reviewing resource limits, and following packets through the AWS VPC CNI, ENIs, security groups, and route tables until we know exactly why traffic stops mid-flight. Familiarity with tools like eksctl, tcpdump, Wireshark, Prometheus, and AWS networking dashboards will help you move fast. Deliverables for each engagement • A short root-cause report explaining why the pod restart or reachability issue happened • The precise commands or config changes you applied • Clear preventive recommendations so the same symptom does not return I consider the incident closed once the affected pods stay healthy for at least 24 hours and all endpoints that were unreachable respond consistently. If you have deep hands-on EKS troubleshooting experience and enjoy detective work in distributed systems, let’s get started.
Project ID: 40766939
24 proposals
Remote project
Active 1 day ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
24 freelancers are bidding on average ₹4,539 INR for this job

As an experienced AWS practitioner, I have dealt with numerous EKS troubleshooting cases very similar to yours. My familiarity with kubectl, CloudWatch, and key Kubernetes components such as liveness and readiness probes will enable me to swiftly diagnose the root cause of any anomalies that may be occurring in your production workloads. Additionally, my knowledge of networking tools like TCPDump, Wireshark, and familiarity with AWS VPC CNI will allow me to thoroughly trace and evaluate every aspect of your network connectivity issues. One thing that separates me from the competition is my ability to not just resolve current problems but also provide preventative recommendations. I'll thoroughly document my diagnosis process and the changes executed so you'll always be equipped with a comprehensive understanding of the fix. After working on your project, you can rest assured knowing that I will not only ensure healthy pod running for 24 hours but will also extend my support towards consistent response across all previously unreachable endpoints. Moreover, what distinguishes me from others is my ability to leverage diverse tools that are necessary for complex distributed systems like yours. If you're seeking someone who has a deep-rooted appreciation for effective troubleshooting in the intricate web of EKS and prides themselves in keeping your systems optimized long-term, then I'm the right fit for you! Don't hesitate in bringing me on board - let's get started!
₹3,500 INR in 7 days
5.8
5.8

With more than 5 years of solid experience in AWS, my knowledge of creating efficient cloud infrastructure, integrated with AI/ML solutions, runs wide and deep. I have a proven expertise in several areas that are directly applicable to your project. As a seasoned Kubernetes specialist familiar with EKS troubleshooting and network administration, I am confident in my ability to dig into any issue causing unreliability or pod restarts and get it resolved swiftly and effectively. My toolkit includes powerful diagnostics tools like eksctl, tcpdump as well as application monitoring options like Prometheus which would come super handy for this task. As you've laid out key deliverables for the engagement, I offer not just exceptional troubleshooting skills but also a unique habit of preparing comprehensive documentation. My reports will provide you detailed insights on the root causes, the specific adjustments I made (whether command changes or applied configurations), and preventive measures to mitigate future recurrences. Lastly, my proficiency extends beyond mere identification of issues - I pride myself in providing holistic solutions which is exactly what you need. I look forward to bringing this unmatched level of dedication to your project helping you achieve consistent productivity and making pain points like these a thing of the past.
₹5,000 INR in 7 days
5.6
5.6

Hi there. I am Mario, sysadmin from Argentina with 25 years experience. I am focused on infrastructure projects, like server installations, databases, web servers, IP connectivity, virtualization, etc. I perform troubleshooting and optimization on AWS EKS clusters on a regular basis. Recurring pod and networking issues in EKS typically boil down to a few critical areas: AWS VPC CNI limitations (such as ENI and secondary IP exhaustion on EC2 instances preventing pods from being scheduled), CoreDNS throttling or upstream latency causing DNS lookup timeouts, misconfigured security groups between worker nodes and the control plane, or readiness/liveness probe misalignments triggering CrashLoopBackOff states. My approach is to inspect cluster events, analyze `kube-system` daemonsets (specifically aws-node, kube-proxy, and coredns), review VPC subnet CIDR availability, and check node resource pressure or taint/toleration conflicts to identify the exact bottleneck rather than applying temporary patches. Are you using the default AWS VPC CNI plugin, and do these issues manifest as pods stuck in 'Pending' due to IP allocation or intermittent connection timeouts between services? I usually work collaboratively via screen-sharing / remote sessions so you do not have to share sensitive passwords, allowing you to observe every step of the execution and verify results. I am available for chat whenever you need.
₹3,000 INR in 2 days
4.6
4.6

Hi there, I can help diagnose and resolve your AWS EKS CrashLoopBackOff and pod-to-pod connectivity issues, focusing on root causes rather than temporary workarounds. Kubernetes production troubleshooting is part of my daily work, including investigating pod failures, analyzing Kubernetes events and logs, resolving networking issues, and maintaining workload stability. I’ll investigate container logs, probes, resource limits, and CloudWatch metrics, then trace network issues through the AWS VPC CNI, ENIs, security groups, network policies, and route tables. You’ll receive a root-cause report, exact commands/configuration changes, and preventive recommendations. I’ll also help verify recovery against your 24-hour stability requirement. My hands-on experience includes AWS, EKS, Kubernetes, Linux, Docker, Prometheus, Grafana, and production infrastructure troubleshooting. Available to start immediately for urgent incidents or ongoing support.
₹4,500 INR in 1 day
3.0
3.0

I understand that you're looking for an expert to address recurring issues with pod restarts and connectivity failures in your AWS EKS environment. With over four years of experience in DevOps and cloud services, I am proficient in Kubernetes and AWS networking. My approach would include quickly analyzing Kubernetes events using kubectl, reviewing logs, and checking configuration settings to identify the root cause of the issues. I have extensive experience with tools such as tcpdump, Prometheus, and AWS dashboards. Once the issue is resolved, I will provide a comprehensive root-cause report, document the applied changes, and offer recommendations for preventing future occurrences. My goal would be to ensure your pods remain stable for at least 24 hours post-resolution. Let's discuss how I can assist you effectively. What is your preferred communication method for updates during the troubleshooting process?
₹2,000 INR in 2 days
1.9
1.9

Hello, I can help troubleshoot your AWS EKS issues, identify the root cause of CrashLoopBackOff errors and connectivity failures, and document the fixes to prevent recurring incidents. Here’s what I can provide: - Analyze Kubernetes events, pod logs, probes, and resource limits. - Investigate CloudWatch logs and container failures. - Troubleshoot VPC CNI, ENIs, security groups, and route tables. - Apply targeted fixes and verify pod health and endpoint connectivity. - Provide a root-cause report, exact commands/config changes, and preventive recommendations. I bring 15+ years of software development experience, including AWS infrastructure, Linux administration, deployment, and performance troubleshooting. I’ll focus on a systematic investigation rather than temporary workarounds. Just to clarify: - Are you currently facing an active incident, and what EKS symptoms are you seeing? - Do you have access to CloudWatch logs, Kubernetes events, and cluster configuration for diagnosis? Please come to the chat box to discuss more about your project. Best regards, Mohammed Nazim
₹2,000 INR in 7 days
0.8
0.8

Scope understanding: Recurring pod crashes and unpredictable network failures can put production reliability at risk, you need lasting fixes, not temporary workarounds. Who we are: SCAIMLON LABS PVT. LTD. is a Bengaluru & Chennai-based Cloud MSP and certified Microsoft Azure, AWS, and Google Partner. Your Ask: Resolve recurring CrashLoopBackOff issues and intermittent connectivity failures in an existing AWS EKS production cluster by identifying root causes, applying targeted fixes, validating pod health and endpoint reachability, and documenting changes with preventive recommendations. Our Solution Approach: We will troubleshoot EKS pods using kubectl, container logs, and CloudWatch, inspect probes and resource limits, trace network paths through VPC CNI, ENIs, security groups, and route tables, then implement targeted fixes and validate stability. Deliverables: Root-cause report, configuration fixes, network validation, 24-hour health monitoring, prevention runbook Relevant Experience: Firepack faced cloud security and access reliability challenges. We used Microsoft Azure to strengthen access controls and improve environment reliability, delivering a more secure and stable cloud setup. Call To Action: Let’s identify the root cause, restore reliable EKS connectivity, and keep your production workloads stable with verified fixes and clear documentation. Happy to jump on a quick call to walk you through our approach before you decide.
₹3,000 INR in 1 day
1.1
1.1

Hello, I hope you're doing well. I develop mobile and web applications with Flutter, including user flows, API integration, authentication, and responsive interfaces. Since the project description wasn't available, I'd prefer to understand the actual requirements before suggesting a technical direction. A related project I worked on was BookMyTurf, a cricket-ground booking app where users could browse availability and submit bookings through a structured backend flow. That involved handling time-based booking data and keeping the experience clear on mobile screens. Once you share the main features, target platforms, and any preferred technology, I can outline the best starting approach and clarify the data flow. A quick conversation on Freelancer.com would help us confirm the scope before moving ahead. Thank you, Neel
₹3,500 INR in 7 days
0.0
0.0

Hi, I run AWS in production as the founding engineer at DroneLeaf, where I own the architecture end to end (Lambda, DynamoDB, IoT Core, Cognito, CloudFormation, multi-arch Docker builds in GitHub Actions). On the Kubernetes side, my public sqlguard-mcp project ships with a Helm chart, so kubectl, probes and resource limits are daily tools. To be upfront: most of my production work is serverless rather than EKS, so I won't claim a long EKS ops history. This kind of tracing is how I fixed an MQTT bug on an 83-device tenant (subscribe failures from 1,828 to 0). How I would handle each incident: 1. Pod events, previous container logs and CloudWatch to separate probe or OOM restarts from app crashes. 2. Check probe timings and requests/limits against real usage. 3. For reachability, walk the path: VPC CNI and free IPs on the node, ENIs, security groups, NACLs and route tables, with tcpdump where needed. 4. Apply the fix, watch 24 hours, then a short root-cause report with commands and prevention steps. Questions: - Which EKS and VPC CNI versions, and do you use security groups for pods? - Is there a live incident now, or should I start with the last one? - What access can you give (read-only IAM role plus kubectl)? Best, Ahmed
₹3,000 INR in 3 days
0.0
0.0

Hello! I went through your brief for "EKS Pod & Network Troubleshooting". I'm a senior engineer (11+ yrs) specialized in full-stack development (front-end + back-end, databases, cloud deployment), which is exactly what this needs. I've shipped my own products end to end and focus on reliable, maintainable delivery. How I'd approach it: 1) Confirm the exact scope and edge cases with you 2) Build in small, testable steps so you see progress early 3) Clean handover with docs I'm available to start now. Let me know your questions. Best, Chris
₹4,740 INR in 1 day
0.0
0.0

Hi, I work with EKS in production and regularly debug CrashLoopBackOff and pod-to-pod reachability issues. I’d check pod events and logs, probes and resource limits, then trace the network path (security groups, route tables, VPC CNI/ENIs, CoreDNS, tcpdump) to find the root cause. You’ll get the fix applied, a short root-cause report, the exact commands or config changes, and prevention recommendations. I only need read-only or time-limited access, or we can do a screen-share. Quick questions: what’s the exact symptom right now, and which EKS version and CNI are you on? I can start today. Thanks, Uttam
₹5,000 INR in 3 days
0.2
0.2

Hi, I’m a DevOps engineer with hands-on experience managing production AWS EKS clusters, supporting 100+ worker nodes and 30+ microservices across multiple environments. I can help investigate and troubleshoot Kubernetes issues such as CrashLoopBackOff, pod restarts, failed health probes, and service-to-service connectivity problems. My approach is to: - Analyze Kubernetes events, pod logs, and previous container logs. - Investigate resource limits, probes, scheduling, services, and DNS. - Troubleshoot AWS networking components, including VPCs, security groups, route tables, and EKS networking. - Apply appropriate fixes and validate the affected workloads and endpoints. - Provide a root-cause report, commands/configuration changes, and preventive recommendations. I also have experience with Prometheus and Grafana for monitoring and troubleshooting production workloads. I’ll focus on identifying the actual root cause rather than applying temporary fixes, and I’ll keep you updated throughout the engagement. I look forward to helping you stabilize your workloads and improve reliability. Best regards, Harshil
₹4,000 INR in 5 days
0.0
0.0

I’d approach this by tracing the failure before changing anything: Kubernetes events and pod logs first, then probes/resource limits/configuration for CrashLoopBackOff cases, and service/endpoints, DNS, network policies and the VPC/CNI path for reachability problems. Once the root cause is isolated, I’ll make the smallest safe correction and document exactly what changed. My hands-on background includes Kubernetes/OpenShift, Linux production troubleshooting, containerized workloads, monitoring with Prometheus/Grafana and debugging deployment/network issues. I can also provide the requested root-cause summary, commands/config changes and preventive recommendations, then verify stability during the 24-hour observation period.
₹2,000 INR in 2 days
0.0
0.0

Hello, I understand you need fast, reliable troubleshooting for AWS EKS CrashLoopBackOff incidents and in-cluster connectivity failures. The goal is to restore stable workloads, identify the exact root cause, and prevent recurring issues. Here’s what I can provide: Analyze Kubernetes events, pod logs, probes, and resource limits to diagnose restart loops. Trace network failures across VPC CNI, ENIs, security groups, and route tables to restore endpoint connectivity. Deliver a root-cause report with commands, configuration changes, validation results, and preventive recommendations. I bring over 4+ years of experience in software development, cloud technologies, Linux, Docker, and backend systems, with a focus on reliable deployments, troubleshooting, and maintainable infrastructure. Just to clarify a few things: Could you share a recent EKS incident, including relevant pod events, logs, and network symptoms? Do you have staging access for testing fixes before applying them to production? Please come to the chat box to discuss more about your project. Best regards Indresh Kushwaha
₹4,500 INR in 7 days
0.0
0.0

One kind of drop never shows in a route table or a security group. EC2 lets each network interface send only 1024 packets a second to the VPC's DNS resolver, and CoreDNS forwards every outside lookup it hasn't cached that way. With CoreDNS on a couple of nodes under load, lookups can time out at random. An app that can't resolve its database at startup often exits and loops, and a running one logs errors that look like a network fault. On the node, ethtool -S shows it: linklocal_allowance_exceeded climbs. For restarts, the previous container's logs and exit code come first: 137 with OOMKilled is a memory limit, a liveness kill shows in the events, anything else is the app. A liveness probe that checks the database turns one network blip into restarts on every replica. For reachability, tcpdump on both nodes shows where packets stop. Each incident closes with the root cause, the exact changes and prevention steps, after 24 healthy hours. Background: Kubernetes and Docker in production, including bank fraud models deployed on Kubernetes, 20+ AWS services, AWS Solutions Architect Associate. My rating here is 5 out of 5. When it breaks, do your app logs show name-resolution errors, or timeouts to an IP? Ronak
₹2,200 INR in 1 day
0.0
0.0

I'm Egor from Alixio, with 5+ years in DevOps/systems administration. For an EKS incident, I would start with the affected workloads' events, previous container logs, probe settings and resource pressure, then trace reachability through DNS, endpoints, VPC CNI, security groups and routes. I propose ₹5,000 for one scoped incident, estimated three days including your 24-hour healthy observation window after the fix. I would agree production changes and rollback with you first, then deliver the root-cause report, exact configuration/commands and prevention recommendations. AWS charges and unrelated application changes are separate. Which EKS/Kubernetes version and workloads are affected, when did the issue start, and can you provide recent events plus a source/destination example? We can confirm the incident scope before starting. I can work through a supervised session or least-privilege access. No broad production changes without your approval. Please confirm the incident priority and preferred session time. I am based in UTC+3. We will verify both pod health and the failing endpoints before closing.
₹5,000 INR in 3 days
0.0
0.0

I bring strong hands-on expertise in Linux/Windows system administration, network troubleshooting, and cloud environments. I have practical experience diagnosing container lifecycle failures like CrashLoopBackOff, inspecting Kubernetes events via kubectl, and tracing VPC CNI network reachability issues down to the packet level. I deliver clear root-cause analysis reports and permanent fixes to keep cluster workloads healthy
₹3,500 INR in 7 days
0.0
0.0

Hello, CrashLoopBackOff and intermittent reachability are usually probes, resource limits, VPC CNI IP exhaustion or security groups for pods. I check them in that order with kubectl events, CloudWatch/container logs and tcpdump on the node, then deliver a short root-cause report, the fix and a runbook so it stays fixed. I have run Kubernetes in production for years (AKS, Rancher) with Prometheus/Grafana monitoring. Guy
₹5,000 INR in 3 days
0.0
0.0

Hi, I can help investigate your recurring pod restarts and cluster connectivity failures. I am a Senior Platform Engineer with 8+ years in systems and infrastructure, including AWS, production Kubernetes, Terraform, Linux, and Prometheus/Grafana observability. For the first incident, I would correlate pod events, previous container logs, probes, and resource limits, then trace the failing network path through Kubernetes networking and the relevant AWS configuration. Before making changes, I would agree the remediation and rollback approach with you. I would document the root cause, exact changes, and preventive recommendations, then validate the affected service against your 24-hour stability criterion. This bid covers one initial incident, with the exact scope confirmed after reviewing the symptoms. Could you share the relevant pod events, sanitized logs, and whether the network failure is intermittent or reproducible?
₹5,000 INR in 3 days
0.0
0.0

Hi — I troubleshoot production AWS EKS, from the pod out to the VPC. For CrashLoopBackOff I start with kubectl: events, previous logs, probe failures, OOMKilled, and requests/limits. I check CloudWatch and the container log for the last exit, then change the probe, limit, or config that caused the restart. I do not raise the limit and call it fixed. For a dropped connection I trace pod IP, VPC CNI, the node ENI, security groups, route tables, and NAT, and compare that with the target port and security group before changing anything. tcpdump on the node confirms a drop when the console still looks correct. Each case ends with a short root-cause note, the exact command or manifest change, and one prevention step. I call it done only after the pod stays healthy for 24 hours and the endpoint keeps answering. My clusters are built with Terraform, not eksctl. I can still read an eksctl cluster. Grafana and metrics are what I use during an incident; Prometheus is not my primary store. Two questions: 1. One cluster, and are the failing calls in-VPC or to the public internet? 2. One incident now, or the next time this shows up? I can start from the current failing pod with read-only kubectl and the AWS network view.
₹5,000 INR in 7 days
0.0
0.0

Chennai, India
Member since Oct 14, 2026
min $50 USD / hour
₹2000-5000 INR
₹750-1250 INR / hour
₹37500-75000 INR
min $10 USD
$15-18 USD / hour
₹600-1500 INR
₹12500-37500 INR
£20-250 GBP
$15-25 USD / hour
$750-1500 USD
₹37500-75000 INR
$15-25 USD / hour
₹2000-5000 INR
$15-25 USD / hour
₹600-1500 INR
$30-250 USD
$250-750 USD
₹1500-12500 INR
₹1500-12500 INR