Kubernetes - Part 1
Kubernetes is a container orchestrator thought to run using a container architecture, that is, a cluster containing a master node (the control plane node) and slave nodes (the working nodes). A control plane node is only responsible for managing the working nodes and ensuring their health to run their workloads. The control plane node won’t have any workload running on it due to getting more robust and efficient, increasing the chances of avoiding a problem occurring on it due to a workload problem....
Container Basic Concepts
Virtual Machines and Containers One approach to deploying software as a portable solution is to use virtual machines. The virtual machines are able to emulate the proper operating system needed for that application, running on top of the host operating system in that bare metal. However, it considers a high usage of the host resources that leverage the costs. Another point to bring to the discussion as another example is about scaling the applications....
Connections with TCP Wrappers and Systemd Sockets
You can create an extra layer for connections using Systemd Sockets with TCP Wrappers. Firstly, we need check the sshd.socket is stopped: systemctl status sshd.socket Otherwise, we can use the below command to achieve this goal. systemctl stop sshd.socket The next step could be create a job to stop sshd.service and start sshd.socket. The following commands help in this task: sudo at now + 3 minutes at > systemctl stop sshd....
SSH Tunnel for Network Traffics
SSH tunnel is Port forwarding via SSH in which you will able to pass traffic that it can use an unencrypted protocol over an encrypted network stream. The command is: ssh -f <remote address> -L <local port>:<remote address>:<remote port> -N
Journal Control to investigate service logs
When you face with a problem in one of the service and would like to investigate about its execution through logs, you can use the Journal Control to this task as mentioned in the below command: journalctl -u <service file> Service is an example but the option -u can be used to any unit file, either system or user-defined one.
Create a Systemd Timer Unit
In order to schedule an execution for a specific service given a period of time, a timer file can helps achieve this goal. Timers are systemd unit files, in which its name is followed by the suffix .timer, and it has that characteristic. Look into to its file content as demonstrated in the following example, we can notice the presence of section Timer: [Unit] Description=XXXX [Timer] OnCalendar=*-*-* 10:30:00 Persistent=true Unit=<service file> [Install] WantedBy=<target> The Timer section uses the option OnCalendar to establish when the service should be executed (in the above example, always at 10:30) pointing out to its service in the option Unit....
Check and change the default target boot for Linux
Systemd is responsible to manage Linux system resources. Those resources are known as units, such as services, targets, sockets and so on. It is possible to use systemd to list all of units are made of by the following command: systemctl list-units Targets represent the state of Linux has reached during startup. It is also possible to run the above command to filter only for target units: systemctl list-units --type=target To get the default target boot has been used for Linux, the following command fit the purpose:...
Linux User Management Commands
In the below table there are some commands can be used to handle users and groups: Goal Command add user adduser <username> add user group addgroup <groupname> add specific user group as primary group usermod -g <groupname> <username> append user group as suplementary group usermod -aG <groupname> <username> lock user usermod -L <username> check the user groups id <username> change to root user sudo -i or sudo su - change to another user sudo su - <username> set password passwd <username> To give permissions for specific user/group in order to execute commands with sudo, it can be pointed out in a separeted sudoer file (within sudoers....
Azure IAM Components
There are 3 components used for Azure Identity Authorization Management: Azure Active Directory Azure Role-Based Control Scopes Azure Active Directory It belongs to top of resources hierarchy, in which identify and prove you are who you are saying you are. Once the identity has been resolved, the role and permissions can set to that identity. Each identity in Azure in known as security principal because identity can represents users, applications and so on....
Azure Resources Hierarchy
There is a resources organization in Azure applied at 5 levels, such as: Tenant Management Group Subscriptions Resource Group Resources One of the advantages of that organization is a centralize manner to set up permissions. Permissions applied in one level will be replicated to the lower levels. For example, access policy established for a set of identities and roles to a specific subscription means all resources belong to it will conform with those policies....