Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gangams/onboarding Extend ARM templates for AMPLS scenario #1155

Merged
merged 3 commits into from
Jan 19, 2024

Conversation

ganga1980
Copy link
Contributor

@ganga1980 ganga1980 commented Jan 16, 2024

Extend ARM templates for e2e private link/AMPLS scenario. Same ARM templates supported for both private & non-private link scenario. If user specify the "useAzureMonitorPrivateLinkScope" : true then required resources related for AMPLS will be deployed and user doesnt need any manual steps else the behavior same as what exists already.

No changes to the non private link/AMPLS scenario. For AMPLS scenario, and these are deployment steps

  1. Create DCE in the Region of the specified Log Analytics Workspace with
    "networkAcls": {
    "publicNetworkAccess": "Disabled"
    }
  2. Create Container Insights Extension DCR in the Region of the specified Log Analytics Workspace
  3. Associate DCR with AKS cluster resource (i.e. DCR-A)
  4. Associate DCE with AKS cluster resource (i.e. DCE-A) and association name must be “configurationAccessEndpoint” .
  5. Link the dataCollectionEndpointId & workspaceResourceId with provided AMPLS resource.
  6. AKS RP PUT to enable the Container Insights Addon

@ganga1980 ganga1980 requested a review from a team as a code owner January 16, 2024 22:39
@ganga1980 ganga1980 changed the title Gangams/onboarding templates updates ampls Gangams/onboarding Extend ARM templates for AMPLS scenario Jan 16, 2024
@ganga1980 ganga1980 merged commit dc971db into ci_prod Jan 19, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants