Akash Singhal
Akash Singhal
### What would you like to be added? OCI Artifact has been removed from OCI Image spec 1.1.0 rc.2 and onwards. Ratify should no longer support this. We have set...
### What would you like to be added? Ratify plans to add support for multiple auth providers the ORAS referrer store. Each auth provider will be selected via a regex/prefix...
### What would you like to be added? Ratify's main scenario in k8s has been through admission controller integration with Gatekeeper. Although this is the prevailing solution today, there are...
### What would you like to be added? Update chart to support PVC creation depending on context (OSS, Azure, AWS, etc). This PVC will mount to the ORAS OCI store...
### What would you like to be added? add an exclusion to the workflows to not run on PR for doc changes only ### Anything else you would like to...
### What would you like to be added? Currently, AKV KMP provider will fail to create if any key/certificate fetch operation fails. This causes a blocking operation for the entire...
### What would you like to be added? Some resource status like KMP and certificate store may contain what might be considered sensitive information such as keys/certificate metadata. Ratify should...
### What would you like to be added? Ratify's Azure Key Vault and ORAS workload identity provider utilize `azure/go-autorest` library for fetching the AAD token. This library is now deprecated...
### What would you like to be added? The newer versions of aws go sdk have deprecated global endpoint resolution. Now regional endpoint resolution is required. This will required updating...
### What would you like to be added? Ratify already supports generating SBOM and Provenance buildx attestations. Ratify should also attach these as referrers to the images for discoverability with...