Disabling and reeanabling ingress fails after updeate to 1.35

[EzekielaRakotoarijaona]

Summary

I updated my node to 1.35 and updated my addon core repo. After I disabled my ingress addon and enabled it again. When I enable it again it says that the addon is already enabled. Also when I run microk8s status the addon is enabled. I checked my resources in cluster no ingress namespace and resources are left.

What Should Happen Instead?

The addon should be disabled after I run disable ingress

Reproduction Steps

1. Upgrade node from 1.34 to 1.35
2. Update addon repo
3. Disable ingress
4. Enable ingress

Introspection Report

Can you suggest a fix?

I try to enable the addon from the enable executable but I encounter another error, it cannot find helm 3 wrapper.

Are you interested in contributing with a fix?

Yes

[EzekielaRakotoarijaona]

Hello, for everyone encountering the same issue I found out that the presence of ingress class public was checked to know if ingress was already enabled
Somehow it has not been deleted from cluster so what I did was just remove the ingress class public and ingress class nginx from the cluster using kubectl then microk8s status showed ingress was disabled. Then I could enable it and it installed the new traefik ingress.