Create K3D Cluster with Local Docker Registry

 K3D is the lightweight wrapper allowing us to run K3S Ranchers minimal Kubernetes deployment easily in local environments. Developers can quickly create a cluster, test the apps in containers with Kubernetes locally. Advantage is it is really really simple and faster to get a Kubernetes cluster created, and deleted using K3D, giving the opportunity to the developers to play around with Kubernetes as much as they want, without a worry. This is a great way to develop with Kubernetes as if you are using a central development Kubernetes cluster, such as Azure AKS, it takes time for you to get the cluster up and running if you made a mess with it while development. Instead K3D let's you have your own development Kubernetes cluster running locally in your machine, which you can destroy and create faster when ever you want or need.

Resolve C# Connection Issue "StackExchange.Redis.RedisConnectionException: No connection is active/available to service this operation: It was not possible to connect to the redis server(s). There was an authentication failure; check that passwords (or client certificates) are configured correctly." to Azure Redis cache Connection via Private Endpoint

 Using Azure Redis cache with C# throws an error message such as below while accessing the Redis cache via a private endpoint.

StackExchange.Redis.RedisConnectionException: 

No connection is active/available to service this operation: 

GET Zdddddddddddddddddddddddddd; It was not possible to connect to the redis server(s). 

There was an authentication failure; check that passwords (or client certificates) are 

configured correctly. ConnectTimeout, mc: 1/1/0, mgr: 10 of 10 available,

 clientName: DESKTOP-XXXXX, IOCP: (Busy=1,Free=999,Min=16,Max=1000), WORKER: 

(Busy=3,Free=32764,Min=16,Max=32767), v: 2.2.88.56325
 ---> StackExchange.Redis.RedisConnectionException: It was not possible to connect to the 

redis server(s). There was an authentication failure; check that passwords 

(or client certificates) are configured correctly. ConnectTimeout
   --- End of inner exception stack trace ---