Flavio Castelli

Currently blocked, the staging TUF repository of sigstore has broken metadata inside of it. I cannot reproduce the issue right now.

Closing, the upstream change happened unexpectedly before the aws/tough changes got published. I handled the backporting of the fixes. Policy Server 1.16.1 and kwctl 1.16.1 have all the required patches.

You can reuse your OPA/Gatekeeper policies with kubewarden. Please take a look at [this](https://docs.kubewarden.io/tutorials/writing-policies/rego/intro-rego) section of our documentation. You will see how you can use `opa` cli tool to compile...

You should start by using the [gatekeeper-policy-template](https://github.com/kubewarden/gatekeeper-policy-template) repository. Then replace the contents of `policy.rego` wit the Rego code you pasted above. Running make policy will produce a `.wasm` file. Update...

We now have a [dedicated howto](https://docs.kubewarden.io/howtos/gatekeeper-migration) explaining how to migrate Gatekeeper policies to Kubewarden. Closing. Feel free to comment here if you need help

I've reported the issue to `oci-spec`, which is including this dependency. There's hope this is going to be addressed soon. See https://github.com/containers/oci-spec-rs/issues/209

This is a transitive dependency brought by `kube`. Upstream [is aware of the issue](https://github.com/kube-rs/kube/issues/1635)

Blocked by https://github.com/RustCrypto/traits/issues/1642 . The rust-crypto libraries are still depending on version 0.8. We cannot bump rand and getrandom to newer version until rust-crypto libraries are using that same version

Blocked, the `rsa` crate is bringing the `v0.8` version of `rand` through the `num-bigint-dig` dependency. The `num-bigint-dig` dependency is unmaintained since years, there are plans inside of `rsa` to move...

This is a valid request. Based on what you said, I would propose: - completion - config - version - plugin Am I missing something