Kubernetes account key secrets are left behind upon solo network destroy

[jeromy-cannon]

solo network destroy runs a helm uninstall therefore leaving behind PVCs and secrets. We have already added an flag for deleting the PVCs (--delete-pvcs).

After the network nodes are up and running, then solo account init will update the account public keys and generate the Kubernetes secrets.

Here we want to add a flag to delete the Kubernetes secrets within the same namespace, eg: --delete-secrets

  SOLO_CLUSTER_NAME=solo-e2e
  SOLO_NAMESPACE=solo-e2e
  SOLO_CLUSTER_SETUP_NAMESPACE=solo-e2e-cluster
  kind delete cluster -n "${SOLO_CLUSTER_NAME}"
  kind create cluster -n "${SOLO_CLUSTER_NAME}"
  solo init --namespace "${SOLO_NAMESPACE}" -i node0,node1,node2 -t v0.47.0 -s "${SOLO_CLUSTER_SETUP_NAMESPACE}"
  solo node keys --gossip-keys --tls-keys --key-format pem
  solo cluster setup
  solo network deploy
  solo node setup
  solo node start
  solo account init