I don't think so. Replica Sets and Replicaiton controllers are a simple way to deploy things. I would use deployments, which do basically the same thing, but give you a lot more options for doing versioning, rollbacks, etc.
I am building a containerized web application that has a .net frontend container and a REST Api backend container. I'd like to know which of these options is the best for our needs: · Deploy everything in the same cluster and node pool and let kubernetes manage and scale them as needed · Deploy everything in the same cluster and 2 different node pools with different machine types and node limits for frontend and backend · Deploy frontend and backend in different clusters all together with a single node pool each
How you deploy it depends on what you're trying to do. Different node pools would imply that the compute needs for the front end and backend are different. If they're not, then I wouldn't use that. You could use the same node pool and the same cluster as a default and see how it performs, then tune it from there. I wouldn't use multiple clusters though. There's no need for that.
Depends on how you want them to communicate. You can put two clusters on the same VNet, or separate VNet's and use peering for internal apps. Or you can have them reach over the internet between one clusters public end points.
You can do it really easily now with the AZ CLI. The method in this video is a bit dated, so check out this link here. docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration
For the external IP, you can use the generated hostname with Azure or you can use an external DNS with a custom domain name and a static IP on Azure. With internal IP's, you can use Azure DNS for a private DNS zone, and add a record to that for your private IP's. You can then set the DNS resolver for the cluster to use the the private DNS
One of the best quality content on AKS
Thanks for this very informative video. I liked the clear explanations. Very tempted to setup the Dos game server.
nice course,pls share the sripts mentioned in description .
Good call....
Check it out here! :) github.com/theonemule/aks-demos
Woo! great explanation... but I was a bit confused about Replica sets & Replication controller... Was the definition altered in slides?
I don't think so. Replica Sets and Replicaiton controllers are a simple way to deploy things. I would use deployments, which do basically the same thing, but give you a lot more options for doing versioning, rollbacks, etc.
Informative
I am building a containerized web application that has a .net frontend container and a REST Api backend container.
I'd like to know which of these options is the best for our needs:
· Deploy everything in the same cluster and node pool and let kubernetes manage and scale them as needed
· Deploy everything in the same cluster and 2 different node pools with different machine types and node limits for frontend and backend
· Deploy frontend and backend in different clusters all together with a single node pool each
How you deploy it depends on what you're trying to do.
Different node pools would imply that the compute needs for the front end and backend are different. If they're not, then I wouldn't use that.
You could use the same node pool and the same cluster as a default and see how it performs, then tune it from there.
I wouldn't use multiple clusters though. There's no need for that.
@@Atmosera- thank you so much for your reply
Hi ,I tried to communicate 2 aks cluster ,but failed .is there any way to communicate between 2 clusters?????
Depends on how you want them to communicate. You can put two clusters on the same VNet, or separate VNet's and use peering for internal apps. Or you can have them reach over the internet between one clusters public end points.
Hi how do we login to an existing AKS cluster?
You can use the Azure CLI.
az aks get-credentials --name AKSClusterName -g ResourceGroup
@@Atmosera- thanks a lot
How can we add more than one variable per cluster ?
Save time. Start @4:10
Fantastic vid. Minor gripe: All pod depictions show 2+ containers, whereas narrator states you should almost never have > 1.
"Never" is a strong word. The idea of more than one application pod is probably what that's getting at. A pod will often have a "sidecar" container.
@@Atmosera- Fair point, which is why I qualified with "almost." What functionality do you most often see in pod sidecars?
Thanks a lot, great content !!
17:56 - Where's the script man?
You can do it really easily now with the AZ CLI. The method in this video is a bit dated, so check out this link here.
docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration
Great video
Great job
Bro what is the password that you used to login into your vnc ? :)
Password1 :P
WintellectNOW Thank you appreciate that :)
Very nice video. thanks!
All commercials until 04:10
Thanks, scripts please.
Check it out here! :) github.com/theonemule/aks-demos
How to give the valid to name to ingress IP ? Because real world difficult to access IP but users ?
Can you please suggest ?
For the external IP, you can use the generated hostname with Azure or you can use an external DNS with a custom domain name and a static IP on Azure.
With internal IP's, you can use Azure DNS for a private DNS zone, and add a record to that for your private IP's. You can then set the DNS resolver for the cluster to use the the private DNS
@@Atmosera- Thanks for your reply.
@@Atmosera- Do you have any example for it ?
I mean any content or video as such
@@sachinmishra5218 I don't, but here is the Azure doc for it.
docs.microsoft.com/en-us/azure/dns/private-dns-overview
I lost you at 16:59. Out of a sudden, you talk about Container Registry with a script from the planet Krypton involved that does: .
The script does not exist anymore. It can be done right from the Azure CLI.
Please share the scripts! Thanks for a great video. Cheers.
Check it out here! :) github.com/theonemule/aks-demos
"container lover" - when u have no social life
Lolz
Notepad++ 👀
Best IDE Ever
@@Atmosera- #triggered