Philipp B.

Not really. But according to https://github.com/mr-karan/calert/pkgs/container/calert/64363789?tag=v2.0.6 the latest release had 39353 downloads during the 9 months since release. But there's definitely some interest, and at our company we use it...

@simonpasquier / @gotjosh any chance to get this included? :)

> Why do we want the bridge to support a file type that whatsapp doesn't? That's the whole point. So the bridge can convert it to a supported format.

Use an umbrella chart in ArgoCD. ``` $ cat Chart.yaml apiVersion: v2 name: metallb description: A Helm chart for Kubernetes type: application version: 0.1.0 appVersion: "0.1.0" dependencies: - name: metallb...

Helm has a special `crds` folder. That way helm will install the CRDs before other any other resources: https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you

> > Helm has a special `crds` folder. That way helm will install the CRDs before other any other resources: https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you > > The problem with this is "These CRDs...

Based on #332 I don't think this will be implemented in this bridge.

Just tried it with the latest v0.16.0 release and still getting `Please check the provider name and/or add configuration for new providers using the .clusterctl config file`. Unfortunately, @w21froster's PR...

@w21froster in my case it's complaining about the custom k3s providers ```yaml --- apiVersion: operator.cluster.x-k8s.io/v1alpha2 kind: BootstrapProvider metadata: name: k3s spec: version: v0.2.1 fetchConfig: url: https://github.com/k3s-io/cluster-api-k3s/releases/v0.2.1/bootstrap-components.yaml --- apiVersion: operator.cluster.x-k8s.io/v1alpha2 kind:...

@w21froster replayed my scenario [described earlier](https://github.com/kubernetes-sigs/cluster-api-operator/issues/570#issuecomment-2679447245) and it seemed to have worked fine 👍