Because the Utility Community service is in preview, begin by registering it in your account. This could take a while, however as soon as it’s registered you’ll be able to set up the AppNet CLI extension that’s used to handle and management Utility Community to your AKS clusters. Now you can begin to arrange the ambient service mesh, both creating new clusters to make use of it, or including the service mesh to current AKS deployments.
Ranging from scratch is the best method, because it ensures that you simply’re working in the identical tenant. AKS clusters and Utility Community will be in the identical useful resource group if you need, nevertheless it’s not crucial. You’re free to make use of separate useful resource teams for administration.
The appnet command makes it simple to create an Utility Community from the command line; all you want is a reputation for the community, a useful resource group, a location, and an identification sort. When you’ve run the command to create your ambient mesh, look forward to the mesh to be provisioned earlier than becoming a member of a cluster to your community. This once more merely wants a useful resource group, a reputation for the member cluster, and its useful resource group and cluster identify. On the similar time, you outline how the community can be managed, i.e. whether or not you handle upgrades your self or go away Azure to handle them for you. Extra clusters will be added to the community the identical method.
