Patrick Ohly a2b0ea30b0 DRA upgrade/downgrade: run etcd directly ... The local-up-cluster.sh script was used as proxy for controlling the etcd lifecycle because the script was using a helper function that didn't support dry-run mode. That approach was flawed in several ways, causing etcd to be left running: - Cmd.Stop wasn't actually called for the script by Cluster.Stop. - If it had been called, the additional output during shutdown wouldn't have been processed, which might have caused the command to block instead of terminating (untested). - It's unclear whether the script would have handled the signal properly. A cleaner approach is to enable dry-run mode also in etcd .sh and then let Cluster manage it like any other long-running process. Then we can let local-up-cluster.sh terminate when it's done with its work. Cluster.Start can check it's result immediately.		2026-05-04 09:24:47 +02:00
..
apiserver
client-go/ktesting	ktesting: address linter hints	2026-04-24 21:54:19 +02:00
crd
fakedns
format	ktesting: move format package	2026-04-24 21:54:19 +02:00
harness
hermeticpodcertificatesigner
image	etcd: update etcd image to v3.6.10	2026-04-15 16:18:52 +05:30
junit
ktesting	ktesting: move format package	2026-04-24 21:54:19 +02:00
kubeconfig
localupcluster	DRA upgrade/downgrade: run etcd directly	2026-05-04 09:24:47 +02:00
oidc
admission_webhook.go
audit.go
conditions.go
create_resources.go
delete_resources.go
density_utils.go
deployment.go
node.go
paths.go
pki_helpers.go
pod_store.go
replicaset.go
runners.go
tmpdir.go
update_resources.go