Stefan Prodan

You can change the metrics as you like in the kube-state-metrics config. If you prefer the reason instead of the `status` for ready, change the config to: ``` ready: [...

> If we have an ExternalArtifact, Flux will always need to reference ExternalArtifact, and users will not be able to use their origin CRDs. @jakobmoellerdev an arbitrary sourceRef would imply...

@matheuscscp @stealthybox I've added a policy example for protecting a cluster against malicious tenants trying to hijack `ExternalArtifacts`.

@bgrant0607 @ebourgeois are you using some kind of proprietary storage and you can't run `flux push artifact` in your system? Trying to understand why would you need a 3rd-party source...

@bb-Ricardo can you please rebase with upstream main and force push

I think the official [community-plugins](https://github.com/backstage/community-plugins) is the best place for this project to continue. ~Sadly Weaveworks didn't setup a license for this project, but given that the company has shutdown...

> The plugin does have a licence https://github.com/weaveworks/weaveworks-backstage/blob/main/plugins/backstage-plugin-flux/LICENSE I guess the fork is for the contents of that dir so should be fine to move it given that it's an...

@bigkevmcd do you have access to the NPM package to run the deprecate command and archive this repo? I do not

This is probably an issue with your CNI, the source-controller Kubernetes Service exposes port 80 https://github.com/fluxcd-community/helm-charts/blob/main/charts/flux2/templates/source-controller-service.yaml

> no service is listening on HTTP (port 80) inside the source-controller pod. Why would it?