Summary

The Argo CD core mode should allow the user to set a permanent path to a K8s client configuration file, instead of either using ~/.kube/config per default or having to specify --kubeconfig for each command.

Motivation

Some K8s distributions by default install a Kubernetes client CLI (kubectl) which uses a custom path for its configuration. For example, K3s uses `/etc/ran

Hi,

It is quite stupid to have one type for many events.
Suggestion:
On feature_segment update sends : FLAG_SEGMENT_UPDATED
On feature_identity update sends : FLAG_IDENTITY_UPDATED
on feature update sends : FLAG_FEATURE_UPDATED

What would you like to be added:
Currently we are defining our own Docker client interface on docker package, which is basically a copy and paste of the methods that we use from [Docker client](https://pkg.go.dev/github.com/dock

Look into and create a POC of a public github action using rok8s-scripts