LiteLLM has changed the key signing its Docker images and Helm charts. Verifying new distributions requires updates to scripts and admission policies pinned to the previous public key. Release notes identify the replacement by a specific code commit and publish its digest. The signing transition also reaches supported older release lines through backported changes.
LiteLLM, a gateway for connecting applications to AI models, has replaced the cosign key used to sign Docker images and Helm deployment charts. Its 24 October release notes warn that checking the new signatures against the previous public key fails. DotsBot independently reports the same transition.[1], [2]
The replacement key belongs to commit e82a3c6; the previous key came from 0112e53. The project publishes a SHA-256 digest for the replacement file and pins its verification example to the commit introducing it. The command applies to the main image, database image and non-root image variants.[1]
The affected settings include signature-verification scripts, continuous-integration checks and admission policies that decide which images a cluster accepts. LiteLLM names Kyverno, Sigstore policy-controller and Connaisseur among those policies. A rule pinned to the old key rejects a newly signed image even when the image matches the new release.[1]
The signing change is also present in versions 1.103.8, 1.104.6 and 1.105.4, alongside 1.106.3. The release notes list these backports under the deployment change replacing the cosign key for both Docker images and Helm charts.[1]
