This message was deleted.

Hello @quaint-match-50796, I saw your support email coming in, but I'll answer here so more people can see the answer. When looking at the Azure documentation, this command seems to perform all-in one installation:

az connectedk8s connect --name AzureArcTest1 --resource-group AzureArcTest

My assumption for now that it contains the following steps: • Creates a keypair • Installs Helm locally • Deploys the Helm chart for Arc Agent, feeding it the private key from the keypair • Creates the ConnectedCluster resource on Azure, feeding it the public key from the keypair I have been searching the docs today for the Arch Agent helm chart, but couldn't find it. If you can find it, then here is in short the Pulumi resources you can use to mimic that

az

CLI command: • tls.LocallySignedCert (or another certificate source) • kubernetes.helm.v3.Release with the private key from the certificate in the input values (which doesn't need the Helm CLI) • azure-native.kubernetes.ConnectedCluster with the certificate as the

agentPublicKeyCertificate

With the private part of the certificate in your cluster, and the public key on the Azure side, the agent arc pod(s) should be able to set up the connection.

Thank you @limited-rainbow-51650! MS tries to hide the helm repo and charts inside their az cli extension. In the end, it maps to: "mcr.microsoft.com/azurearck8s/batch1/stable/azure-arc-k8sagents:1.10.6"