K8s sts bugfix

[echoboomer]

• Refactors vault based on recent enhancements - removes command-based approach for joining and initializing raft followers.
• Breaks out progress indicator for Civo package to give better detail on individual steps for tracking timing.
• Refactors k8s statefulset wait logic to remove depending on flaky time.Sleep calls and looks for appropriate Pod statuses before returning.
• Various fixes to package naming and syntax cleanup.

[echoboomer]

Sample of log output during Vault setup:

2023-03-02T21:33 INF internal/k8s/exec.go:254 > Waiting for vault StatefulSet to be created.
2023-03-02T21:33 INF internal/k8s/exec.go:394 > Waiting for vault StatefulSet to be ready. This could take up to 120 seconds.
2023-03-02T21:34 INF internal/k8s/exec.go:424 > pod vault-0 in statefulset vault is running
2023-03-02T21:34 INF internal/k8s/exec.go:424 > pod vault-1 in statefulset vault is running
2023-03-02T21:34 INF internal/k8s/exec.go:424 > pod vault-2 in statefulset vault is running
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:40 > starting port-forward for vault-0
LOG: 2023/03/02 21:34:42.410863 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF vault
LOG: 2023/03/02 21:34:42.410947 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF vault-0
2023-03-02T21:34 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-03-02T21:34 INF internal/k8s/wrappers.go:172 > Pod "vault-0" at namespace "vault" has port-forward accepting local connections at port 8200

2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:72 > initializing vault raft leader
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:98 > creating secret vault-unseal-secret containing vault initialization data
2023-03-02T21:34 INF internal/k8s/exec.go:36 > Created Secret vault-unseal-secret in Namespace vault

2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:106 > passing unseal shard 0 to vault-0
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:106 > passing unseal shard 1 to vault-0
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:106 > passing unseal shard 2 to vault-0
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:106 > passing unseal shard 3 to vault-0
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:106 > passing unseal shard 4 to vault-0
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:150 > closing port-forward for vault-0
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:168 > starting port-forward for vault-1
LOG: 2023/03/02 21:34:56.905800 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF vault
LOG: 2023/03/02 21:34:56.905871 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF vault-1
2023-03-02T21:34 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-03-02T21:34 INF internal/k8s/wrappers.go:172 > Pod "vault-1" at namespace "vault" has port-forward accepting local connections at port 8200

2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:187 > created vault client for vault-1
2023-03-02T21:34 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:198 > joining raft follower vault-1 to vault cluster
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:230 > passing unseal shard 0 to vault-1
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:230 > passing unseal shard 1 to vault-1
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:230 > passing unseal shard 2 to vault-1
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:243 > closing port-forward for vault-1
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:168 > starting port-forward for vault-2
LOG: 2023/03/02 21:35:06.472483 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF vault
LOG: 2023/03/02 21:35:06.472716 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF vault-2
2023-03-02T21:35 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-03-02T21:35 INF internal/k8s/wrappers.go:172 > Pod "vault-2" at namespace "vault" has port-forward accepting local connections at port 8200

2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:187 > created vault client for vault-2
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:198 > joining raft follower vault-2 to vault cluster
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:230 > passing unseal shard 0 to vault-2
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:230 > passing unseal shard 1 to vault-2
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:230 > passing unseal shard 2 to vault-2
2023-03-02T21:35 INF kubefirst/internal/vault/(*VaultConfiguration)/autounseal.go:243 > closing port-forward for vault-2
LOG: 2023/03/02 21:35:15.998684 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF vault
LOG: 2023/03/02 21:35:15.998881 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF vault-0
2023-03-02T21:35 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-03-02T21:35 INF internal/k8s/wrappers.go:172 > Pod "vault-0" at namespace "vault" has port-forward accepting local connections at port 8200

2023-03-02T21:35 INF cmd/civo/create.go:1184 > configuring vault with terraform

[echoboomer]

Sample of progress feedback during Civo create:

[johndietz]

that output is really nice