When openfaas addon is enabled, gopaddle-lite shows as enabled - and vice versa

[jtraxy]

Summary

When you enable the openfaas addon, if you check what addons are enabled, the gopaddle-lite addon shows as enabled, which is not the case. This is because openfaas creates a gateway deployment which gopaddle-lite uses to check whether it is enabled. The same situation occurs in reverse; if gopaddle-lite is enabled, openfaas will report as enabled as well.

What Should Happen Instead?

The 'enabled' checks for openfaas and gopaddle-lite should be granular enough to distinguish between which is enabled and only then show as enabled the addon that is enabled (when you perform a microk8s status command).

Reproduction Steps

Easily reproducible:

1. In a MicroK8s cluster, perform microk8s enable openfaas
2. Then: microk8s status

Introspection Report

N/A

Can you suggest a fix?

The 'enabled' checks for openfaas and gopaddle-lite should be more granular, focusing on checking for something that is specific to each of those addon which the other of the addons does not have.
If it is difficult to find something specific per addon, it might be worth implementing the regex check code that Ali suggested in #166 and using a regex instead.

Are you interested in contributing with a fix?

no