Use kops to create kubernetes cluster in existing VPC and Subnets.
How to install crowdstrike antivirus (falcon-sensor) in kops cluster using additionalUserData
Additional user-data can be passed to the host provisioning by setting the additionalUserData field.
How to install sqlcmd on kubernetes pod container to test sql server connection
This article covers setting up of mssql-tools which includes the sqlcmd client utility. These steps are needed for container in which you wish to use the sqlcmd command or other Microsoft-originating utilities on Ubuntu to interact with an MSSQL Server.
Run PostgreSQL and pgAdmin in container on windows WSL (ubuntu 18.04)
Instead of installing postgreSQL server as local service for development setup, you can run postgreSQL and pgAdmin as Docker containers.
How to resolve error – container has runAsNonRoot and image will run as root
The error “container has runAsNonRoot and image will run as root” is due to non availability of required volume not mounted for container.
How to let your team members access kubernetes cluster
As Kops creates a Bastion server to access Cluster nodes, so this article will be based on user created on Bastion server from where they will access kubernetes cluster.
Deploying the AWS IAM Authenticator using kops
Managing authentication protocols is huge task, requiring admins to maintain a list of acceptable users, validate permissions on an ongoing basis for each user, prune users that don’t need access, and even periodically recycle token- and certificate-based access.
How to resolve aws-iam-authenticator error “could not load/generate a certificate”
aws-iam-authenticator error “could not load/generate a certificate” can be resolved by terminating master node
Connecting to your kops created Bastion server (Linux) using EC2 Instance Connect
You can use Amazon EC2 Instance Connect which provides a simple and secure way to connect to your instances using Secure Shell (SSH).
Error thrown while building code using azure pipeline
Resolve error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.1. Either target .NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.1