Add a feature to select non-usable cloud(s) for the GitOps catalog entries

[fharper]

What is your feature idea?

Add a features to select non-usable cloud(s) for the GitOps catalog entries.

Why is it needed?

Some applications or tools added to the GitOps catalog won't be working on k3d (ex.: Datadog), as an example, or were created for a specific cloud features, so not useful for others. In that case, we should add a new property in the index.yaml to exclude some clouds where the specific application will be available. The console app should now display the proper list of available applications depending on which cloud the user wants to install them.

It is a more complete solution than #1810, covering all user cases, not just k3d. We will also need to take in consideration a near future were multi-clusters will also be cloud agnostic.

Is this missing feature preventing you from using kubefirst?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct