Thanks for showcasing the excellent demo. I have been a fan of both @scotthanselman and @liorkamrat. The trick with lazy git function was quite handy. Will definitely use that with my own workflow
Hi, Thanks for asking - Control Plane nodes are based on Linux, so we must create a Linux VM on top of Hyper-V to create the cluster. Regarding the Windows nodes, there's a strict kernel version match between the host OS and the container base image. We created a Windows VM to decouple the host OS kernel version and leverage the latest versions (like ServerCore 2022). In the future, we are considering bringing support for running a Windows node directly on the Windows host OS. If you have more questions, feel free to reach out. Thanks, Francisco
In a similar scenario as showcased in this demo, where we are running the “Dev” env in K8s and “prod” in K3s, how to check/validate if any feature build/tested on K8s won’t fail in K3s due to resource limitations or for any other reason ?
Usally, where you see diffences between K8s and K3s, is in the Kubernertes core components and implementation. When it comes to the apps, i've never seen an application that runs on K8s and cannot run on K3s. Compute resources requirment is generic, you need to have enough resources on either one, regardless of the Kubernetes distro.
AKS i growing up in another level. May be now it's leading managed Kubernets service.
Awesome demo! One quick question though!
Where are below values coming from?
- name: SQL_HOST
value: ""
- name: SQL_USERNAME
value: ""
- name: SQL_PASSWORD
value: ""
- name: SQL_DATABASE
value: ""
Thanks for showcasing the excellent demo. I have been a fan of both @scotthanselman and @liorkamrat. The trick with lazy git function was quite handy. Will definitely use that with my own workflow
Glad you found it useful, Nilesh! Thanks for watching! 😊
Why is it necessary to deploy AKS EE on Hyper-V instead of directly on the host OS? It seems that using Hyper-V adds complexity to the setup.
Hi,
Thanks for asking - Control Plane nodes are based on Linux, so we must create a Linux VM on top of Hyper-V to create the cluster. Regarding the Windows nodes, there's a strict kernel version match between the host OS and the container base image. We created a Windows VM to decouple the host OS kernel version and leverage the latest versions (like ServerCore 2022). In the future, we are considering bringing support for running a Windows node directly on the Windows host OS.
If you have more questions, feel free to reach out.
Thanks,
Francisco
In a similar scenario as showcased in this demo, where we are running the “Dev” env in K8s and “prod” in K3s, how to check/validate if any feature build/tested on K8s won’t fail in K3s due to resource limitations or for any other reason ?
Usally, where you see diffences between K8s and K3s, is in the Kubernertes core components and implementation. When it comes to the apps, i've never seen an application that runs on K8s and cannot run on K3s. Compute resources requirment is generic, you need to have enough resources on either one, regardless of the Kubernetes distro.
Hi Scott
Can you have take some video about async communication documentations?
like... swagger but for service bus or other message broker
Is it possible to run this setup of kubernetes on an offline environment with no access to the internet ?
Yes - AKS Edge Essentials supports fully offline environments.
16gigs i5 small machine 🙂
Hi, you can run AKS Edge Essentials in an 8GB device. We are actively working to reduce memory consumption even further.