[Part 3] Python3: Basics for Beginners – If/Else, Nesting

In Part 2 for Python3 Basics for beginners blog, we read about Input function, Return and Casting. In this blog, we will advance our understanding of python by learning conditional coding techniques like if else and nesting. 1. IF/Else Conditions If/Else plays important role in evaluating user inputs from input functions and then determining whether … Continue reading [Part 3] Python3: Basics for Beginners – If/Else, Nesting

Advertisement

[Part 2] Python3: Basics for Beginners – Variables, Input, Return

In Part 1 for Python3, Basics for beginners blog, we read about three python3 usages, viz. Print, Variables and Defining Functions with Parameters. Next we will be learning about, Scope of Variables, Input and Return functions. 1. Scope of Variables In layman terms, it simply determining boundary for variables, something like namespaces,so we can call … Continue reading [Part 2] Python3: Basics for Beginners – Variables, Input, Return

[Part 1] Python3: Basics for Beginners – Print, Variables, Functions

Python is one of few coding languages, which is easy to deploy and use for day to day tasks, whether in DevOps for configuration management or Cloud Infra for health checks and instance life cycle management. What I like most about python is its easy for anyone to switch over and get their hands dirty … Continue reading [Part 1] Python3: Basics for Beginners – Print, Variables, Functions

Kubelet Service: “Error getting node” err=”node \”workernode\” not found”

I faced this error while resetting my cluster to swap memory enabled node. Basically this error comes if you have swap memory enabled and kubelet service is not able to find eligible node for running services. After resetting kubernetes cluster on Master node I initialized my kubernetes cluster with extra argument of “–fail-swap-on=false” . root@ubmaster:/home/ubuntu# echo … Continue reading Kubelet Service: “Error getting node” err=”node \”workernode\” not found”

Kubernetes Cluster using ‘swap memory’ on Host Node

Before Kubernetes release 1.22, swap space must be disabled on host node in order to provide full disk resource for cluster and pods running on it. With new release, swap space can remain on host node. For new deployments, this seems pretty straightforward but what if you have kubernetes cluster already deployed, running without swap … Continue reading Kubernetes Cluster using ‘swap memory’ on Host Node

“username” is not in the sudoers file. This incident will be reported. Privilege escalation for new user in Linux

Before providing with you resolution of above error, remember this case is for providing sudo access to new user which actually can be security risk if you are working in production enviornment. Do consult with you infosecurity team if new user really need sudo access. I am assuming here that you are already aware of … Continue reading “username” is not in the sudoers file. This incident will be reported. Privilege escalation for new user in Linux

“Failed to run kubelet” err=”failed to run Kubelet: misconfiguration: kubelet cgroup driver: \”systemd\” is different from docker cgroup driver

With support of different type of container runtimes provided with current kubernetes release, one of important aspect to consider is using same cgroup manager for both kubelet and container runtime engines so resource allocation to pods can be managed centrally. While, kubelet service itself integrates with linux default "systemd" as cgroup manager, runtime engines like … Continue reading “Failed to run kubelet” err=”failed to run Kubelet: misconfiguration: kubelet cgroup driver: \”systemd\” is different from docker cgroup driver

(CentOS-8) Error: Failed to download metadata for repo ‘appstream’: Cannot prepare internal mirrorlist: No URLs in mirrorlist

While migrating my kubernetes cluster from Docker runtime engine to CRI-O, I faced error below, [root@cntmaster ~]# yum update CentOS Linux 8 - AppStream 59 B/s | 38 B 00:00 Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist This error occured since I am using old CentOS … Continue reading (CentOS-8) Error: Failed to download metadata for repo ‘appstream’: Cannot prepare internal mirrorlist: No URLs in mirrorlist

K8 v1.23.1 – The connection to the server localhost:8080 was refused – did you specify the right host or port?

Above, is one of the most common error we get whenever we install a new K8 cluster or start working on one deployed by other users. First thing first, this error is not version specific and also doesn't imply something is wrong with your configuration. (So please don't send that mail you wrote for your … Continue reading K8 v1.23.1 – The connection to the server localhost:8080 was refused – did you specify the right host or port?