The NFS 4.1 support on Azure File Shares -in public preview- is a fully POSIX-compliant offer ideal for workloads that require POSIX-compliant file shares, case sensitivity, or UNIX style permissions (UID/GID).
This is a demo guide of how to install kubernetes master and worker nodes on Microsoft Azure standalone virtual machines.
This guide is not intended as a solution for production purposes.
Pre-requisites
This guide assumes that you have a Microsoft Azure account and that you installed the Azure CLI and you are logged in to the respective subscription in Azure.
First steps
To create a resource group:
az group create -n rg_k8sdemo --location eastus2 --tags Purpose=Education
There are many usage cases of kubernetes and, hence, very distinct support scenarios when it deals to supporting a kubernetes issue. In my experience, I would call the following basic kubernetes commands to investigate an issue, as the most useful -and necessary- to accompany any kubernetes issue report.
kubectl version
kubectl cluster-info
kubectl get nodes -o wide
kubectl get pods --all-namespaces -o wide
kubectl get deployments --all-namespaces
kubectl get svc --all-namespaces -o wide
On the same time, I would include these couple of Docker commands:
docker -v docker ps
To speed up any kubernetes troubleshooting, I’d recommend to provide the output of those commands in TXT format, rather than taking a screenshot.
Do you have any other experienced-based basic kubernetes command you would add to this list? Please share in the comments section.
In virtually every installation of Debian -or derivative- it will happen that at some point during software management one will be prompted this message: The following packages have been kept back Let’s provide an example to make it clear.
Example
First, you ran:
apt-get update
and everything was fine. We can affirm the command reported a 0 exit code.
After this you ran:
sudo apt-get upgrade
if your OS‘ software gets updated often and if it is updated at the time of running the upgrade command the output will be like this:
iamsysadmin@examplehost:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
cinnamon-screensaver
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
… and there is the weird message: The following packages have been kept back.
The latest couple of articles examined in some basic advices to choose a datacenter for your company.
This article exposes the location of world wide well known datacenters which belongs to companies like Google, IBM, Amazon (AWS) and a few others. The objective of this post is to share the location of such datacenters as of typing to these lines; it is based upon the good practice of reducing latency through short geographical separation among the DC and the own company headquarters.
So, let’s go ahead to meet the datacenter location of the chosen companies.
Google
Google’s datacenters are distributed into three major regions around the world, these are: Americas, Europe and Asia.The following image shows in the Google’s datacenter locations by specific country:
The most noteworthy hosting services offered by Google belongs to their public cloud, in specific:
Compute
Storage and Databases
Networking
Big Data
Machine learning
Management tools
Developer tools
Identity and security
You may check out an updated list of Google’s datacenter in this link.