Entre para ver o perfil completo de George
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Entre para ver o perfil completo de George
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Grécia
Entre para ver o perfil completo de George
George pode apresentar você a mais de 10 pessoas na empresa PacketFabric
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
528 seguidores
+ de 500 conexões
Entre para ver o perfil completo de George
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Ver conexões em comum com George
George pode apresentar você a mais de 10 pessoas na empresa PacketFabric
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Ver conexões em comum com George
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Entre para ver o perfil completo de George
ou
Nunca usou o LinkedIn? Cadastre-se agora
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Atividades
528 seguidores
-
George Tseres compartilhou issoRemington is one of the best engineers I have ever worked with. He has a very strong technical background and can wear multiple hats, has an excellent work ethic and he is able to take a large project and break it into small actionable, well-defined tasks. He is an amazing team player and helps other engineers ramp up and further develop their skills. Remington can be a great asset to any engineering team.George Tseres compartilhou issoHi professional network! If you are in need of a creative, solution-focused engineer with full-stack skillset, let's talk. After 3 serendipitous years at PacketFabric developing infrastructure and code, I am looking for a fresh challenge building creative software solutions and technologies. I am proud to have worked with the PacketFabric team and accomplished what we have. If you are working on an exciting project and want another set of hands, let me know. My experience is diverse, extending from sales engineering and software development through SRE and DevOps. I am… #OpenToWork!
-
George Tseres compartilhou issoGiorgos Strimpakos is a top-notch engineer with excellent work ethic and a great mindset. If you, or anyone in your network is hiring for a Site Reliability Engineering or DevOps role, you can reach out to me for a reference, or to Giorgos Strimpakos directly.George Tseres compartilhou issoHi everyone - I have been hit by layoffs. I am looking for a new role and would appreciate your support. Thank you in advance for any connections, advice, or opportunities you can offer. #OpenToWork
-
George Tseres compartilhou issoGeorge Tseres compartilhou issoNew PacketFabric Terraform Provider version v1.0.0 was released today! You can now do pretty much everything with our Terraform Provider. Use #automation to power your #network with #terraform and #packetfabric.
-
George Tseres compartilhou issoGeorge Tseres compartilhou isso📢 BIG NEWS 📢 PacketFabric is thrilled to announce our intent to merge with Unitas Global! Together, both companies and their combined assets and automation capabilities create the first True NaaS Platform, delivering real-time, on-demand control to our customers from the Edge to Everywhere. Read the full press release: https://lnkd.in/g3Bw8YKX Spread the love by sharing our exciting news. 🔗 #Merger #EdgetoEverywhere #networking #infrastructure #connectivity #cloud #NaaSPacketFabric and Unitas Global Announce Merger - PacketFabricPacketFabric and Unitas Global Announce Merger - PacketFabric
-
George Tseres compartilhou issoGeorge Tseres compartilhou issoYou’ve seen our claims on how fast PacketFabric’s network agility is, but have you ever wanted to test it out for yourself? Try our new bandwidth calculator to get an estimate of how long (or should we say short) it takes to move your data around the world. https://lnkd.in/geN8GHFt #cloudconnectivity #agilecloud #NaaS #BandwidthCalculator
-
George Tseres compartilhou issoGeorge Tseres compartilhou issoPacketFabric's Senior Product Manager (in Networking) role is a great fit for someone who has a solid technical background in networking, who has a flair for value proposition creation, market positioning, and creating a go to market plan. This role gets to be front and center discovering customer pain points, and creating the magic of NaaS to solve them. For more information, and to apply directly: https://lnkd.in/gcFuPgge #networking #network #productjobs #product
-
George Tseres reagiu a issoGeorge Tseres reagiu a isso🌊 Kicking off the year by making a splash 🌊 I'm excited to share at the beginning of the year I joined DigitalOcean as a Senior Network Sourcing Engineer. If you had told me 5 years ago that at this point I would be deep into network infrastructure I don't think I would have believed you. Yet here I am working with an incredible team- excited about the work I get to do! Thank you to all the incredible mentors and teachers I've had on this journey. Jezzibell Gilmore, Joe Oligny, Julie Elrod, Deb Airozo, Guy Tal, MBA I would not be here today without your leadership, mentorship, and support.
-
George Tseres gostou dissoGeorge Tseres gostou dissoΑν αναρωτιέστε πόσο νερό 💧 έχει η Αθήνα, μπορείτε να το παρακολουθείτε ζωντανά (ενημερώνεται καθημερινά): https://lnkd.in/dxKwn4pG
-
George Tseres gostou dissoGeorge Tseres gostou disso📣 I am incredibly excited to finally share this with you. For the past couple of months, we’ve been quietly pouring our energy into building and refining Ask Feather AI, an AI research partner for tax pros, with audit-ready citations! Why Feather? 🪶 🔹 Citations included: Never wonder where an answer came from. We show our work so you can do yours. 🔹 Multi-state support: Navigate state-specific nuances effortlessly. 🔹 Context-Aware Intelligence: It doesn’t just answer; it anticipates. Feather flags related risks, exceptions, and filing deadlines proactively. 🔹 Secure: SOC 2 compliant. Check out the launch details here: https://lnkd.in/dGFc2at3Introducing Feather: The Professional-Grade AI Copilot for Technical Tax ReasoningIntroducing Feather: The Professional-Grade AI Copilot for Technical Tax Reasoning
-
George Tseres reagiu a issoGeorge Tseres reagiu a issoHave you ever tried Matcha? It looks like a swamp, and also tastes what I would expect a swamp to taste like. Can you tell them apart? https://lnkd.in/dF2VkUQY
-
George Tseres gostou dissoGeorge Tseres gostou dissoThe anxiety surrounding AI job displacement doesn't fit with the long and consistent history of human labor. Consider a hunter-gatherer from 10,000 years ago. To them, "work" was the immediate, visceral act of securing calories. The moment we developed agriculture, we unlocked a food surplus that allowed for the first "surplus elites"—priests, tax collectors, artists and professional warriors, who didn't have to touch the soil to be fed. Throughout history, every technological wave, from the plow to the microchip, has simply pushed that surplus percentage higher. Already, long before AI, we've reached a point where 98% of us are now that "surplus caste." The "work" we do isn't strictly necessary for biological survival; we're performing cognitive labor that would look like a frivolous fiction to our ancestors. Take a "User Experience Researcher" or a "Compliance Officer." These are not survival needs we met, but roles we invented. There doesn't seem to be a logical limit to this process - we can keep coming up with stuff to do. Just as we moved from tilling fields to managing databases, we'll move from managing databases to overseeing AI-driven abstractions. The "fear" of AI is based on the idea that there is a finite amount of work to be done. History shows us the opposite: as soon as technology automates one layer of effort, we immediately invent a more complex layer of bullshit jobs on top of it. We aren't going to run out of jobs; we’re just going to get even better at inventing them.
Experiência e formação acadêmica
-
PacketFabric
**** **** *********** ********
-
********** ** ******
******* ******** *********** undefined
-
Ver experiência completa de George
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Olá novamente
Ao clicar em Continuar para se cadastrar ou entrar, você aceita o Contrato do Usuário, a Política de Privacidade e a Política de Cookies do LinkedIn.
Nunca usou o LinkedIn? Cadastre-se agora
Idiomas
-
Greek
Nível nativo ou bilíngue
-
English
Nível avançado
-
French
Nível básico
Recomendações recebidas
6 pessoas recomendaram George
Cadastre-se agora para visualizarVeja o perfil completo de George
-
Saiba quem vocês conhecem em comum
-
Apresente-se
-
Entre em contato direto com George
Outros perfis semelhantes
Ver mais publicações
-
Desmond Muyukha
SCARATEC • 843 seguidores
Simplify Kubernetes CLI Tool Development with clientcmd Building a kubectl-style command line tool? You don't have to implement all those options from scratch. The Kubernetes project provides the clientcmd library in client-go that handles kubectl-style command line arguments for you, including: • Kubeconfig file selection via KUBECONFIG environment variable • Context and namespace selection • Client certificates and authentication • User impersonation • Configuration merging from multiple files The library follows kubectl semantics: defaults from ~/.kube/config, environment variable overrides, and command line argument overrides on top. Key workflow: 1. Configure loading rules with NewDefaultClientConfigLoadingRules() 2. Set up ConfigOverrides for command line values 3. Bind flags using pflag integration 4. Build merged configuration with NewNonInteractiveDeferredLoadingClientConfig() 5. Obtain your API client The deferred loading pattern means you can set everything up before parsing arguments, and the final configuration resolves at runtime. Bonus: The library supports prefixes for multi-cluster scenarios (--from-context, --to-namespace, etc.). #Kubernetes #Go #CloudNative #DevTools #ClientGo
2
-
Desmond Muyukha
SCARATEC • 843 seguidores
🚀 Argo CD v3.2.6 Released - Stability and Reliability Improvements for Your GitOps Workflows The Argo CD team has released v3.2.6, the latest stable version of the popular GitOps continuous delivery tool for Kubernetes. This release focuses on bug fixes and reliability improvements that platform teams will appreciate. 🎯 🔧 What's New in v3.2.6: 🐛 Bug Fixes: • ✅ Fixed an issue with the Hydrator where .gitattributes wasn't properly including deeply nested files - important for teams with complex repository structures • ✅ Resolved empty links appearing for failed hydration operations, improving the debugging experience • ✅ Fixed a connection leak caused by response bodies not being closed on error paths - this addresses potential resource exhaustion in long-running deployments • ✅ Corrected invalid error messages on health check failures, making troubleshooting more straightforward 📦 Dependency Updates: • 🔄 Updated the notifications-engine to fix a nil panic issue when posting GitHub PR comments - critical for teams relying on Argo CD notifications for their review workflows 💡 Why This Matters: For teams running Argo CD in production, these fixes address real-world operational concerns. Connection leaks, while subtle, can accumulate over time and impact cluster stability. The improved error messaging helps reduce mean time to resolution when issues occur. ⏱️ 📊 Current Supported Versions: • 🟢 3.2.x branch: v3.2.6 (current stable) • 🟢 3.1.x branch: v3.1.12 • 🟢 3.0.x branch: v3.0.23 • 🔜 Coming soon: v3.3.0 (currently at rc4) ⚡ Quick Upgrade: kubectl apply -n argocd -f https://lnkd.in/dDr3gPJV 🔐 All container images are signed with cosign and include SLSA Level 3 provenance, so you can verify the integrity of what you're deploying. 📚 If you're still on v2.x, now is a good time to start planning your upgrade path to v3.x. The Argo CD team has comprehensive upgrade documentation to help with the transition. 🔗 Release notes: https://lnkd.in/dEJ53e_z 💬 What version of Argo CD is your team running? Have you made the jump to v3.x yet? Let me know in the comments! 👇 #ArgoCD #GitOps #Kubernetes #DevOps #CloudNative #ContinuousDelivery #PlatformEngineering #CNCF #SRE #InfrastructureAsCode 🌐☸️
2
-
Desmond Muyukha
SCARATEC • 843 seguidores
Just yesterday, January 28th, the Kubernetes blog published a practical guide on experimenting with Gateway API using kind (Kubernetes in Docker). Why This Matters: The Ingress Deprecation Story For years, Ingress has been the standard way to expose HTTP services in Kubernetes. However, Ingress has significant limitations: it only supports basic HTTP/HTTPS routing, lacks standardized support for TCP/UDP, and forces vendors to use non-portable annotations for advanced features like traffic splitting, header manipulation, and canary deployments. Gateway API is the official successor to Ingress, developed by the Kubernetes SIG-Network community. It provides a more expressive, extensible, and role-oriented approach to routing. While Ingress is not removed yet, Gateway API is now the recommended path forward for new deployments. The Hands-On Guide The tutorial walks you through setting up a complete Gateway API environment locally: 1. Create a kind cluster with a single command 2. Deploy cloud-provider-kind, which provides both LoadBalancer support and a Gateway API controller 3. Create a Gateway resource listening on port 80 4. Deploy an HTTPRoute to direct traffic to your application 5. Test everything with curl The setup uses three key Gateway API resources: • GatewayClass: defines the controller implementation • Gateway: configures listeners and ports • HTTPRoute: handles hostname and path-based routing This local environment is ideal for learning Gateway API concepts before choosing a production-ready implementation like Envoy Gateway, Istio, or NGINX Gateway Fabric. #Kubernetes #GatewayAPI #CloudNative #DevOps #kind
1
-
Alex Torgboshie
JOMACS • 2 mil seguidores
🧑💻 🔒 💪 Strengthening Infrastructure Reliability with AWS ALB & CloudWatch 💪 🧑💻 🔒 I recently completed a project focused on building a resilient and observable environment on AWS for the Nautilus DevOps team. The goal was simple: ensure high availability and proactive monitoring for our core application. Key Milestones: 🔹 Traffic Management: Set up an Application Load Balancer (ALB) (datacenter-alb) to manage public HTTP traffic. 🔹 Targeted Routing: Configured a Target Group (datacenter-tg) to seamlessly route requests to our Nginx-powered EC2 instances. 🔹 Security First: Implemented a dedicated Security Group (datacenter-sg) and refined instance-level rules to ensure only the ALB can communicate with the backend. 🔹 Proactive Monitoring: Established a CloudWatch Alarm (xfusion-alarm) to track CPU Utilization. If the load hits ≥90% for 5 minutes, our team is instantly notified via SNS (xfusion-sns-topic). This setup not only improves our application's uptime but ensures we aren't flying blind. #AWS #DevOps #CloudComputing #Nginx #InfrastructureAsCode #CloudWatch #SRE
5
-
Veljko Dimovic
Engineering Software Lab… • 2 mil seguidores
If you're working with AWS serverless architectures or exploring workflow orchestration, this meetup in Belgrade is definitely worth attending. My colleague Željko, who is a strong expert in AWS Step Functions and large-scale orchestration patterns, will be speaking about advanced patterns for building reliable distributed workflows — including scaling strategies, payload management, retry semantics, and modern integrations with EventBridge and HTTP services. These topics are becoming increasingly important as more systems move toward event-driven and serverless architectures. If you're in Belgrade and interested in cloud architecture, orchestration, and modern backend design, feel free to join the event. Advanced Orchestration Patterns with AWS Step Functions March 24, 18:00 – AWS User Group Belgrade https://lnkd.in/dbjer9Qm
8
-
Akalanka De Silva
Amazon Web Services (AWS) • 2 mil seguidores
In a world where writing prompts is called 'engineering' and running few blocks of copy pasted code in a notebook is called 'building' its refreshing to see what real engineers build. I was fascinated listening to Dr. Werner Vogels at his keynote at re:Invent last year explaining about how they handle transaction based workloads at virtually limitless scale and how they solve key challenges around time sync. This blog post is defnitely worth your time if you are interested to learn more about what goes on under the hood in a database which can do ACID at multi region scale.
20
-
Argo Unpacked
688 seguidores
🤔 Do you really think Kubernetes is complex? What if it’s actually simpler than we make it? In this quick short, Daniele Polencic explains why #Kubernetes can feel complicated — and shares a tip that might change how you approach it. Watch here 👉 https://lnkd.in/dA6_3rG4
1 comentário -
Data Stack Conf
367 seguidores
🔐 PostgreSQL Security you can’t ignore. Valeria Bogatyreva from Percona shows how Open Source TDE closes real security and compliance gaps in PostgreSQL. If you store sensitive or regulated data — this is a must-watch. 🎥 Watch here: https://lnkd.in/dcgqNwRu #PostgreSQL #Security #TDE #Compliance #OpenSource #DataStackConf
7
-
ABHILASH R
United Airlines • 4 mil seguidores
"Just use Terraform" they said. "Infrastructure as Code is easy" they said. Then we hit 50+ microservices and our Terraform state file became a 15-minute nightmare. The real challenge with IaC isn't writing the code. It's managing it at scale: • Single state file = single point of failure • Long plan times blocking CI/CD pipelines • State lock conflicts during deployments • Blast radius of a bad apply = entire infrastructure We restructured our approach: • Split state files by service and environment • Implemented remote state with S3 + DynamoDB locking • Created reusable modules for common patterns • Added automated testing with Terratest • Set up drift detection to catch manual changes Plan time: 15 minutes → 90 seconds. Deployment confidence: way up. After years of managing AWS infrastructure with Terraform, I've learned that good DevOps practices scale. Bad ones compound. The tools are just tools. The architecture and discipline matter more. What's your biggest Terraform pain point? #DevOps #Terraform #InfrastructureAsCode #AWS #CloudEngineering #CICD #Automation
47
10 comentários -
Nirmata
22 mil seguidores
Kyverno Chainsaw is an open-source tool designed to simplify the integration testing of Kubernetes resources. It allows engineers to test deployments, services, ingress configurations, and more before changes hit production. Great talk by Maram El-Sayed! https://bit.ly/42zkIfv #kyverno #chainsaw #nirmata
20
-
Ngozi Nwadialo
Cloudboosta • 2 mil seguidores
Terraform Data Sources for Dynamic Configurations Instead of hard-coding values, Terraform data sources allow you to fetch existing infrastructure details at runtime, making your configurations smarter and more flexible. They help you: - Query existing resources (VPCs, AMIs, subnets, IAM roles) - Reuse infrastructure across environments - Reduce duplication and configuration drift If infrastructure already exists, Terraform should read from it, not reinvent it. Follow me for more Terraform tips and share the data source you use most!
8
1 comentário -
Ayoub Ajdour
Webloo • 6 mil seguidores
🚀 Day 16/30: #30DaysOfKubernetes - DaemonSets: The Cluster-Wide Services That Run Everywhere! Here's a fundamental distributed systems question: How do you collect logs from 100 nodes? Monitor CPU on every machine? Ensure security policies cluster-wide? You could manually install agents on every node, write deployment scripts, pray your infrastructure doesn't miss servers when new ones appear. But there's a deeper problem: In dynamic environments, nodes come and go constantly. Auto-scaling adds nodes. Failures remove nodes. Your carefully deployed agents become scattered and inconsistent. After managing production clusters with hundreds of nodes, DaemonSets are what make cluster-wide functionality reliable and automatic. 🔥 What DaemonSets guarantee: • Exactly one pod per node, always • Automatic deployment on new nodes • Coordinated updates across entire cluster • Proper cleanup when nodes disappear 💡 Essential use cases mastered: • Log collection: Fluentd on every node • Monitoring: Node Exporter for system metrics • Security: Falco runtime threat detection • Networking: CNI plugins and network policies 🛠️ Built complete observability stack: Fluentd collecting logs, Node Exporter gathering metrics, Falco monitoring security - all automatically deployed to every node including new auto-scaled instances. Watching cluster-wide services maintain perfect coverage was pure magic! The secret? DaemonSets turn manual node-by-node operations into automated, consistent, cluster-wide services. 👉 Full deep-dive with production observability stack: https://lnkd.in/ejGJFqim What's your biggest challenge with cluster-wide service management? Tomorrow: Jobs & CronJobs - batch processing and scheduled automation! #30DaysOfKubernetes #Kubernetes #DevOps #CloudNative #DaemonSets
18
-
HAProxy Technologies
15 mil seguidores
The #Kubernetes community is at a turning point. It’s a moment that demands a change, but it’s also our collective opportunity to unify around a more stable, future-proof standard. We built the HAProxy Unified Gateway to be your bridge to that future. This is a free, open-source solution supporting both Gateway API and legacy Ingress standards simultaneously. Why this is your best path forward: 🔹Migrate on your own terms and eliminate the need for a risky "rip and replace." Adopt the Gateway API at your own pace while keeping your existing Ingress reliable. 🔹Gain flexible protocol support (TCP, HTTP/S) and true role-based access control (RBAC) in a single, high-performance platform. 🔹Built on the legendary HAProxy core, ensuring the reliability your clusters rely on. HAProxy Unified Gateway is not just a long-term strategic upgrade, but a more powerful, reliable, and fully-supported solution. Read the details: https://hubs.la/Q03TLKms0
10
-
Edvinas Sulžickis
Too Good To Go • 2 mil seguidores
My homelab Kubernetes cluster worked… until it needed updates. Originally, I installed K3s manually. SSH into each node, ran commands and done. However, the cluster upgrades were also manual. I wanted something repeatable and automated. So I rebuilt the process using k3s-ansible github project. The challenge I was facing was that my applications already had PVCs with the data I did not want to lose. Here was the workflow: • Backup existing PVC data • Uninstall K3s • Reinstall the cluster using k3s-ansible • Bootstrap the cluster with Flux • Restore PVC data Result: • Automated cluster installation • Repeatable upgrade procedure • Everything documented and stored in Git Now upgrading my homelab cluster is just running automation. The best part that it is fully reproducible. How do you handle Kubernetes upgrades in your homelab environments? #Kubernetes #Homelab #DevOps #GitOps #Automation
35
23 comentários