*: support "AWS_K8S_TESTER_EKS_SKIP_DELETE_CLUSTER_AND_NODES"

[gyuho]

Partially address #123.

Short-term solution without breaking changes.

[ellistarn]

Consider calling this "Attach to cluster"

[ellistarn]

Instead of skipping, can we idempotently check that it already exists and just succeed?

[ellistarn]

Thinking even higher level, how much effort would it be to make everything within AKT idempotent, so that we could modify the yaml config and it would simply execute the deltas?

[gyuho]

Do you mean skipping creation? Creation is already done here

aws-k8s-tester/eks/cluster/cluster.go

Lines 288 to 303 in 4cad9b3

	func (ts *tester) createEKS() (err error) {
	fmt.Printf(ts.cfg.EKSConfig.Colorize("\n\n[yellow]*********************************\n"))
	fmt.Printf(ts.cfg.EKSConfig.Colorize("[light_green]createEKS [default](%q)\n"), ts.cfg.EKSConfig.ConfigPath)
	if ts.cfg.EKSConfig.Status.ClusterCFNStackID != "" ||
	ts.cfg.EKSConfig.Status.ClusterARN != "" ||
	ts.cfg.EKSConfig.Status.ClusterAPIServerEndpoint != "" ||
	ts.cfg.EKSConfig.Status.ClusterCA != "" ||
	ts.cfg.EKSConfig.Status.ClusterCADecoded != "" {
	ts.cfg.Logger.Info("non-empty cluster given; no need to create a new one", zap.String("status", ts.cfg.EKSConfig.Status.ClusterStatusCurrent))
	return nil
	}
	if ts.cfg.EKSConfig.Status.Up {
	ts.cfg.Logger.Info("cluster is up; no need to create cluster")
	return nil
	}

which means you can run create cluster command multiple times and it will automatically skip if already created.

[ellistarn]

with this path to yaml eventually be our custom resource yaml config?

[gyuho]

Yes.