Core Internet and Networking Concepts Every Aspiring DevOps Engineer Must Know

·1 views

A foundational guide for beginner DevOps engineers explains how key internet and networking technologies work together behind everyday online activities. The article covers essential concepts including protocols, packet switching, IP addresses, and the TCP/IP model that enables reliable device communication. It also explains the roles of HTTP and HTTPS in web data transfer, as well as DNS in translating domain names to IP addresses. These topics are presented as critical building blocks for anyone starting a career in DevOps, cloud computing, or software engineering.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

PostHog Newsletter Explores Limits of Delegating Tasks to AI Agents

PostHog published a newsletter piece examining how much work can realistically be handed off to autonomous AI agents. The article explores the boundaries of agent autonomy in software and product development workflows. It was shared on Hacker News, where it received 3 points at the time of reporting. The discussion thread had no comments, suggesting the post was relatively new or niche in appeal.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

How to Deploy, Update, and Scale a Custom App on an On-Premise Kubernetes Cluster

Part 6 of this Kubernetes on-premise series walks through building a Docker image for a custom Spring Boot REST API and publishing it to Docker Hub or a private registry. The guide demonstrates creating a Deployment using the kubectl command line and exposing it via a LoadBalancer Service with a manually assigned external IP, as on-premise environments lack cloud-native load balancer provisioning. It covers rolling updates using kubectl set image, which replaces the running container image with a new version while recording the change in revision history. In case of issues, a rollback to the previous revision can be performed instantly with kubectl rollout undo. The article also explains both manual replica scaling with kubectl scale and automatic scaling through a Horizontal Pod Autoscaler configured to maintain CPU utilization below a defined threshold.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

On-Premise Kubernetes Cluster: Deploying Your First Container with Nginx

A technical tutorial series on building an on-premise Kubernetes cluster has reached its fifth installment, focusing on deploying the first application. Using Nginx as a practical example, the guide walks through creating a Deployment manifest with two pod replicas managed across available worker nodes. A NodePort Service is then configured to expose the application externally via any cluster node's IP address, without requiring an external load balancer. The article also covers best practices such as organizing Kubernetes manifests in per-application directories for easier maintenance and version control. Successfully accessing the default Nginx page through the assigned NodePort confirms the cluster is functioning end-to-end.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Guide: Installing Containerd and Kubernetes on an On-Premise Cluster

A technical tutorial series on building an on-premise Kubernetes cluster has released its second part, focusing on installing the container runtime and core Kubernetes components. The guide covers configuring required Linux kernel modules — overlay and br_netfilter — and setting sysctl parameters to ensure correct network routing between pods and services. Containerd is installed via Docker's official repository using only the containerd.io package, with the systemd cgroup driver enabled to align with kubelet's default configuration. Kubernetes components kubelet and kubeadm are then installed from the official Kubernetes v1.31 repository, with package versions pinned to prevent automatic updates that could break cluster compatibility. All steps are intended to be run on every node in the cluster, both master and workers, unless stated otherwise.

0 comments Read more at DEV Community