You can simply set the replicas to 0 in the yaml and it'll effectively turn off the cluster. And, it'd then be a fairly simple matter of scaling it back up the same way.
So, if you wanted to, you could set up a job to run "kubectl apply -f your-deployment-day.yaml" during the day to start the cluster and kubectl apply -f your-development-night.yaml" to stop it during evening and weekends.