Off Boarding Openshift 4 from Container Insight

slsbla 11 Reputation points
2022-11-30T16:31:40.257+00:00

Hello,
I'm trying to off board ARO cluster from Azure container insight as described in https://github.com/clarenceb/aro4x-demo#optional-delete-cluster in order to use Azure-ARC.
when I executed the helm del azmon-containers-release-1 in the Azure cloud cli I'm getting the follwing error :

Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials  

1- What's the server that is asking for credentials? is it the ARO?
2- the link is referring to "(Optional) Delete cluster". Is that mean the ARO cluster will be deleted or only the connection of the cluster in Container Insight that will be deleted?
3- is it possible to off board it without using helm ?
4- is that the correct way to off-bord / migrate the ARO cluster from the old Container Insight (retired on 31/05/2022) to the Azure-Arc

Thank you.

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,826 questions
Azure Red Hat OpenShift
Azure Red Hat OpenShift
An Azure service that provides a flexible, self-service deployment of fully managed OpenShift clusters.
72 questions
Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
332 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Maxim Sergeev 6,566 Reputation points Microsoft Employee
    2022-12-01T00:13:12.827+00:00

  2. slsbla 11 Reputation points
    2022-12-05T16:14:14.823+00:00

    Thank you verry much @Maxim Sergeev for your valuable support.
    I was able to remove the ARO form the monitored cluster by
    1- Removing all omsAgent Pods from Openshift
    2- Since the onboarding legacy script uses "az deployment create " to deploy the monitoring solution to the Resource Group. identified the Deployment Name from the ressource group overview and executed "az deployment delete"
    3- I noticed that the legacy script was adding a tag with the log workspaceID to the ARO resource, I just delete it

    I'm ready to start the ARC onboarding for the ARO cluster.