add valkey to oci-factory

[reneradoi]

• I have signed the CLA?
• I am following the CONTRIBUTING guidelines

Ping the @canonical/rocks team.

---

Description

This PR adds the valkey rock to the OCI factory. The onboarding issue can be found here.

---

Picture of a cool rock:

[cjdcordeiro]

@zhijie-yang I think we can no longer use our self-hosted runners, according to https://github.com/canonical/oci-factory/actions/runs/12694115078/job/35383511241?pr=306.

We'll need to discuss this offline as it will affect arm64 builds.

(FYI @reneradoi )

[reneradoi]

Hello @cjdcordeiro I just wanted to update on this topic. Is anything still to be done from my side? I see that one CI step is failing, but I'm not sure if this is related to my PR or to your previous comment.

What are the next steps for publishing the image to Dockerhub?

[cjdcordeiro]

Hi @reneradoi there isn't yet a fix but I'm trying to apply a patch and change a few settings, even if temporarily, just to get this going

[cjdcordeiro]

It seems there's a CVE to be addressed:

'[{"Target":"usr/bin/redis_exporter","LastModifiedDate":"2024-09-09T15:35:07.573Z","VulnerabilityID":"CVE-2024-34156","PkgName":"stdlib","Severity":"HIGH"}]'

If you cannot fix it, then see https://github.com/canonical/oci-factory?tab=readme-ov-file#Vulnerability-Filtering

[reneradoi]

The vulnerability has been patched now.

[cjdcordeiro]

Sry for the extra pass, but it would also be good to expand a bit more on the documentation. Here's an example: https://github.com/canonical/oci-factory/blob/main/oci/grafana/documentation.yaml

[reneradoi]

I've updated the documentation.yaml and added usage information.

[cjdcordeiro]

tyvm for the changes. lgtm ;)