kubernetes provider resources v1 vs non-v1 is it just me or is this dumb?

• kube-graffiti

  1 26 0.0 Go

  Paint your kubernetes objects with 'mutating' webhooks

  

To get proper monitoring and control and to integrate it with the istio service mesh and kong gateway, I was using a tool called kube-graffiti to modify the services, ingresses and pod/deployments on the fly as they were deployed. Well, it is no longer supported and 100% failed.

• pluto

  18 1,979 5.8 Go

  A cli tool to help discover deprecated apiVersions in Kubernetes

  

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.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• Kyverno

  35 5,143 9.9 Go

  Kubernetes Native Policy Management

  

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.

• external-attacher

  1 155 8.0 Go

  Sidecar container that watches Kubernetes VolumeAttachment objects and triggers ControllerPublish/Unpublish against a CSI endpoint

  

Also broken: we had an sftp to s3 gateway running that leveraged an s3 CSI (ctrox) that was using a very old version of the CSI Attacher that was trying to use a v1beta1 VolumeAttachment, so that container wouldn't start up. That wasn't caught by any checks...

Suggest a related project