How to delete calico from azure kubernetes cluster, it got created with tigera operator while creating the cluster.

Abhishek Singh 381 Reputation points
2022-10-17T09:40:44.08+00:00

How to delete calico from azure Kubernetes cluster, it got created with tigera operator while creating the cluster.
I tried deleting the namespaces but it somehow got redeployed after sometime.

I need a way to remove it permanently and make my network policy to none from calico.

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,447 questions
0 comments No comments
{count} votes

Accepted answer
  1. deherman-MSFT 38,021 Reputation points Microsoft Employee Moderator
    2022-10-17T16:49:23.087+00:00

    @Abhishek Singh

    I understand you want to remove the Calico network policy from your AKS cluster. Please correct me if I am misunderstanding the issue.

    At this time, you cannot change or remove a network policy from a cluster once created. You will need to recreate the cluster without the network policy.

    Sorry for the inconvenience. Let me know if you need further assistance or have further questions.

    -------------------------------

    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Abhishek Singh 381 Reputation points
    2022-10-21T05:11:07.15+00:00

    I was able to fix this issue by removing the health check annotation for nginx in aks

    1 person found this answer helpful.
    0 comments No comments

  2. Abhishek Singh 381 Reputation points
    2022-10-17T17:49:46.157+00:00

    Thanks for your reply, is there any way to prevent it from updating my load balancer health probes that is the issue that I am facing my health probes are getting updated automatically and hence downtime.

    0 comments No comments

  3. deherman-MSFT 38,021 Reputation points Microsoft Employee Moderator
    2022-10-18T15:38:30.56+00:00

    @Abhishek Singh

    It sounds like you are manually changing it but the configuration you had specified was not updated. If this is an internal load balancer you can update the internal-lb.yaml file. If external you can update the public-svc.yaml file. More configuration and options are available on the documentation pages. Please check to see if you can update this file and if it resolves your issue.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.