python-tuf VS Kyverno

Using Python-TUF, but it's purpose is not to package app, check new version and apply updates and patches, so a non negligible layer of development is needed to achieve the same work as the first choices.

Confusingly named, it’s not a framework, but a specification that developers can follow when implementing their update systems to help users know they can trust the updates they receive. There’s also a Python reference implementation.

Hello world! I want to recommend a wonderful open-source package called Tufup. It's a simple software updater for stand-alone Python applications. This package was created as a replacement for PyUpdater, given the fact that PyUpdater has been archived and is no longer maintained. However, whereas PyUpdater implements a custom security mechanism to ensure authenticity (and integrity) of downloaded update files, Tufup is built on top of the security mechanisms implemented in the python-tuf package, a.k.a. TUF (The Update Framework). By entrusting the design of security measures to security professionals, Tufup can focus on high-level tools.

Anyway, I haven’t checked for sure as I’m away from laptop but it should be possible to use something like Kyverno to block that operation. We had to do similar in the past to hotfix a bug in our CLI tool. I wrote a blog post about it that might give you an idea: https://www.giantswarm.io/blog/restricting-cluster-admin-permissions

Cosign is used for signing containers through a variety of different methods. It has strong integration with other open source tools, such as Kyverno.

cosign: https://docs.sigstore.dev/cosign/overview/ kyverno: https://kyverno.io/

Kyverno - Kubernetes Native Policy Management

You could use a policy tool like kyverno or OPA.

Kyverno is present in the management cluster;

You do still have to create a policy for every namespace, but don't have to worry about labeling individual pods. We're starting to move to Helm/kustomize for our namespaces to deploy default things like network policies to each one, and we're also starting to use kyverno more, which I think is a little more purpose built for this type of thing than metacontroller is.

I knew it was unsupported so about 6 months ago I had started an effort to switch to Kyverno, which is far better and actually supported. The version of Kyverno I was using had a v1beta1 AdmissionController. Fortunately that was in a helm chart so easily caught by pluto before my upgrade.

Kyverno Kyverno is a policy engine designed for Kubernetes, Kyverno policies can validate, mutate, and generate Kubernetes resources plus ensure OCI image supply chain security.