Usman Rasheed

The flexibility Kubernetes provides for the RPCs Exec, Attach and PortForward is truly outstanding compared to other methods. Nevertheless, container runtimes have to keep up with the latest and greatest implementations to support those features in a meaningful way. The general effort to support WebSockets is not only a plain Kubernetes thing, it also has to be supported by container runtimes as well as clients like crictl. ✍️✍️✍️ Container Runtime Interface streaming explained https://lnkd.in/gfgnqDmd

3

K2D allows extremely resource-constrained devices to be able to accept management operations via a stripped-down Kubernetes API, negating the need to run Kubernetes on the device itself. https://lnkd.in/e7mUtny7

2

Maintain safe and secure deployments to Kubernetes with Octopus 👏 When scaling Kubernetes deployments it can be hard to ensure safety and security. But not with Octopus. Octopus provides built-in RBAC controls and ITSM integrations to handle access to projects, approvals, and safe deployments to production. Audit logs store every action so you have a complete picture of who did what and when. Runbooks let you automate day-0 provisioning and day-2 maintenance tasks that your team can self-serve with a single click. Learn more: https://lnkd.in/g63sT52P #Kubernetes #ContinuousDelivery #OctopusDeploy #DevOps

16

You should be able to treat Kubernetes clusters like a blue/green deployment. Let's break down what that means: A blue/green deployment is a deployment strategy in which you create two separate, but identical environments. One environment (blue) is running the current application version and one environment (green) is running the new application version. The same can be done for Kubernetes clusters. One cluster is running an environment and another cluster can run either the same environment OR a new environment. It just comes down to storing the cluster configurations somewhere in a dynamic fashion. Think about it like GitOps 2.0, but for clusters. #kubernetes #devops #platformengineering

94

43 Comments

Containerization is a powerful tool for managing workloads. However, not all workloads are suitable for containerization. In this tech talk I cover out how to handle virtualized workloads that don’t make sense to containerize while leveraging the robust self-healing capabilities of Kubernetes.

9

2 Comments

Properly defined requests & limits can significantly optimize your #K8s resource management. This FREE ebook is a practical guide that explores #VPA's functionality and its real-world applications. Download your copy here! 👉 https://lnkd.in/dWtSuSji #kubernetes #cpu #memory

16

Kubernetes isn’t the end goal. What we get from Kubernetes is. The fact that you can not only take a set of APIs and run them virtually anywhere to manage your infrastructure (true software-defined infrastructure), but the API is extendable. I can take any API that currently exists and manage it within Kubernetes. This is done via Operators. Kubernetes was able to change how we think about underlying infrastructure. #kubernetes #devops #platformengineering

119

12 Comments

In a recent video, I explored how to configure Carpenter on AWS EKS to function as a cluster autoscaler. This is a valuable tool for anyone looking to optimize their AWS EKS cluster's resource utilization. Carpenter is an open-source solution that automatically provisions new nodes in response to unschedulable pods. By analyzing pending pods' resource requirements, it can choose the optimal instance type to run them on. The video provides a step-by-step guide to configuring Carpenter on AWS EKS. It covers essential steps like installing the AWS CLI and eksctl, creating a cluster configuration file, and setting up IAM roles and policies. Helm charts are then used to seamlessly install Carpenter on the EKS cluster. The video includes specific commands to streamline the process. To validate Carpenter's functionality, a dummy application is deployed and scaled up and down. As expected, Carpenter automatically scales the cluster by provisioning additional nodes when needed and removing unnecessary ones when pods decrease. The video concludes by demonstrating how to monitor Carpenter's activity using kubectl logs. If you're looking to leverage autoscaling for your AWS EKS cluster, this video is a comprehensive resource!  #AWS #EKS #Kubernetes #Carpenter #ClusterAutoscaler #cloud #automation https://lnkd.in/eSYt3Erh

15

Data on Kubernetes: Part 2 — Deploying Databases in K8s with PostgreSQL, CloudNative-PG, and Ceph Rook on Amazon EKS #WorkSmartWithK8s #kubernetes #eks #operator #postgresql #cloudnative-pg #cephrook #hands-ondemo https://lnkd.in/ejusdRsy

8

Streamlining Test Environments with Terraform   Tired of the manual hassle of setting up test environments? Discover how Terraform can revolutionize your Devops workflow. By creating reusable infrastructure modules, I've significantly reduced the time and effort required to provision consistent test environments.   Key benefits:   Efficiency: Automate the creation of complex test setups. Consistency: Ensure standardized environments across teams. Flexibility:Easily adapt to changing requirements.   Want to learn more about how Terraform can benefit your projects? Let's connect on LinkedIn to discuss!   #Devops #Terraform #InfrastructureAsCode   https://lnkd.in/ef5dGMz7

8

The HashiCorp #Terraform AWS Cloud Control provider just got better. Important new features in the AWS Cloud Control provider include sample configurations and enhanced schema-level documentation. Learn more: https://hashi.co/4dVCvm1 #AWSPartner

306

3 Comments

🌐 Interfaces in Kubernetes: Why Standardization Matters If you're starting out with Kubernetes, you've probably encountered CRI, CNI, and CSI – but why are these interfaces essential? 🤔 Kubernetes was designed to work with diverse hardware and providers, but achieving consistency across them takes time and effort. Imagine switching cloud providers for your Nodes – without standardization, every API call *should* fail! 🚫 Standardization brings the consistency that admins and developers rely on for a true cloud native experience and helps with: ✨ Consistency Across Environments Run your workloads anywhere without worrying about the specifics of your environment. Kubernetes abstracts the complexity, providing a consistent experience. 🔌 Decoupling Superpower CRI, for example, decouples Kubernetes from specific container runtimes, supporting multiple options for performance, security, and flexibility. Build for your desired state with ease. 🔗 Layered Approach for Flexibility High-level and low-level runtimes work together, enhancing Kubernetes' adaptability and scalability. Moreover, you can use whatever you find best without any vendor lock-in. Switching is easier if required 🚀 Takeaway: Interfaces like CRI, CNI, and CSI enable Kubernetes’ modularity, making it more scalable, flexible, and interoperable. 💡 #Kubernetes #CloudNative

38

AWS Lambda is an almost instinctual choice when it comes to building on AWS Cloud (and why not? It's awesome!). But are Lambda functions - and the custom libraries and code that comes with them - always the right choice? Particularly for gluing components together? I spend some time exploring the potential of working with native AWS services to produce an event-driven solution with no Lambda or custom code in sight. #aws #eventbridge #software #architecture #serverless

38

6 Comments

Imagine you have the following requirement: some pods need to be placed on specific nodes dedicated to compute intensive, memory intensive, and storage intensive workloads. How do you ensure these pods are scheduled correctly and not placed on other nodes? At the same time, how do you ensure that no other pods are placed on these optimized nodes? My latest article, “Kubernetes Pod Scheduling Explained: Taints, Tolerations, and Node Affinity”, tackles this exact scenario. https://lnkd.in/d3X7w2Bi #kubernetes #devops #cloud

4

Why did John choose OpenObserve for the observability of Nginx? Because he can and it is very simple. Be like John, you can follow these simple steps - https://lnkd.in/gPfA4cnb #nginx #openobserve #observability #fluentbit #logmanagement

16

Faizan Bashir: "Great explanation! 👏 Taints and tolerations are key mechanisms for effectively managing workload distribution in Kubernetes. By adding taints to nodes, teams can ensure optimal resource allocation, isolating workloads based on criticality or resource requirements. This is particularly useful for maintaining production stability, ensuring that high-priority services are not competing with lower-priority jobs. Additionally, applying them in scenarios like maintenance mode or on nodes with specialized hardware allows for smoother cluster operations and better resource utilization. Thanks for breaking it down so clearly!"

1

Struggling with secure inter-VPC data transfer?   VPC peering might be the answer!  Watch this video by Ben Dalton for a clear explanation on how VPC peering enables private connections between VPCs in the same or even different AWS accounts!     Here's why your connections will love it:    Lower latency for faster data transfer ️  Enhanced security using the private AWS network    Potential cost savings for VPC traffic   Let me know in the comments if you've used VPC peering in your projects!     #AWS #CloudComputing #DevOps #VPCPeering #InterVPC #InterAWSAccess #VPCSecurity #AWSCloud #Networking #Security https://lnkd.in/eE_PZ3vf

10

Don't miss this fireside chat on August 21 at 2 PM ET/11 AM PT designed for technology leaders responsible for Kubernetes management, efficiency, and cost optimization. Dieter Matzion, Sr. Cloud Governance Engineer at Roku, will join Andy Suderman, CTO at Fairwinds, and Emilia A’Bell, Chief Revenue Officer, Platform9 who will provide actionable insights to elevate your Kubernetes strategy. Register here: https://bit.ly/3AgmUOj #webinar #kubernetesmanagement #kubernetesefficiency #costefficiency #roku #kubernetesstrategy #kubernetes #managedkubernetesasaservice #devops #finops

1