Since the introduction of the Generic API the previous API around specific resource types was deprecated
There are several reasons for removing the deprecated API:
Simplify the code base
Simplify documentation (as the generic API allows to do almost everything the K8s API allows using YAML manifests)
Hopefully, reduce the size of the resulting binary or at least facilitate the identification of the dependencies that have more impact
One of main blockers so far for removing the deprecated API is that most of the examples depend on that API. Most of these examples seems to be superfluous now and would add not benefit if converted to the new API because the tasks they implement are covered by the official k8s documentation.
Another blocker for removing the API is that some helper functions such as jobs.wait and pods.exec should be moved as helper functions. The pods.addEphemeralContainer function should probably be removed as it was introduced as a requirement for the xk6-disruptor and was since moved to that extension.
Since the introduction of the Generic API the previous API around specific resource types was deprecated
There are several reasons for removing the deprecated API:
One of main blockers so far for removing the deprecated API is that most of the examples depend on that API. Most of these examples seems to be superfluous now and would add not benefit if converted to the new API because the tasks they implement are covered by the official k8s documentation.
Another blocker for removing the API is that some helper functions such as
jobs.waitandpods.execshould be moved as helper functions. Thepods.addEphemeralContainerfunction should probably be removed as it was introduced as a requirement for the xk6-disruptor and was since moved to that extension.The suggested plan is: