[TECH DEBT] Remove k8s execution module

[djivey]

Description of the tech debt to be addressed, include links and screenshots

Looking through the history of the k8s module and comparing it to the kubernetesmod module. k8s has similar functionality to kubernetesmod, but has not been updated with any meaningful contributions since 2016. Most of the functionality of k8s can be found in kubernetesmod. It looks like k8s was created first, but kubernetesmod is a lot more robust as a module and has a corresponding state module.

Common functions in both modules:

• namespaces
• secrets
• node labels
• Both use the Kubernetes API for operations

Differences in both modules:

• kubernetesmod:

  • Also manages (deployments, pods, services, and configmaps)
  • Uses the official kubernetes python client library
  • More comprehensive error handling
  • Supports newer Kubernetes features
  • Has better authentication handling

• k8s:

  • More basic implementation
  • Uses direct http requests
  • May lack support for newer Kubernetes features

[djivey]

Kubeadm may also be worth scrapping unless someone has a desire/need to update it.

[hello070707-byte]

The k8s module has not been updated since 2016 and duplicates functionality already provided by kubernetesmod. While both handle namespaces, secrets, and node labels via the Kubernetes API, kubernetesmod is more robust, using the official Python client, supporting deployments/pods/services/configmaps, and offering better error handling, authentication, and state modules. In contrast, k8s is a basic, outdated implementation using direct HTTP calls. To reduce confusion and maintenance overhead, we should deprecate k8s and migrate fully to kubernetesmod. I've gotten this answer from here- https://medium.com/@manrajsinghglobal/i-automated-my-entire-web-scraping-workflow-from-ticket-creation-to-pull-request-58653ed79bbd