Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bugfix: Implement wait for vault readiness to fix bug. #1286

Merged
merged 3 commits into from
Feb 14, 2023

Conversation

echoboomer
Copy link
Contributor

Signed-off-by: Scott Hawkins scott@echoboomer.net

Implements a few new Kubernetes functions for working with resources. I think moving forward this would be a better blueprint for handling similar issues versus parsing flags from the config.

2023-02-13T20:14 INF internal/k8s/exec.go:34 > Waiting for vault StatefulSet to be created.
2023-02-13T20:14 INF internal/k8s/exec.go:83 > Waiting for StatefulSet vault to be ready. This could take up to 60 seconds.
2023-02-13T20:14 INF internal/k8s/exec.go:97 > All Pods in StatefulSet vault are ready.
LOG: 2023/02/13 20:14:43.625777 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF vault
LOG: 2023/02/13 20:14:43.626065 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF vault-0
2023-02-13T20:14 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-02-13T20:14 INF internal/k8s/wrappers.go:172 > Pod "vault-0" at namespace "vault" has port-forward accepting local connections at port 8200

@echoboomer echoboomer added the bug Something isn't working label Feb 14, 2023
cmd/civo/civo.go Outdated Show resolved Hide resolved
cmd/civo/civo.go Outdated Show resolved Hide resolved
@echoboomer
Copy link
Contributor Author

Implemented recommended changes to references kubeconfig. Also changed out hold for ArgoCD:

2023-02-14T09:28 INF internal/k8s/exec.go:91 > Waiting for argocd StatefulSet to be created.
2023-02-14T09:28 INF internal/k8s/exec.go:189 > Waiting for argocd-application-controller StatefulSet to be ready. This could take up to 90 seconds.
2023-02-14T09:28 INF internal/k8s/exec.go:203 > All Pods in StatefulSet argocd-application-controller are ready.
LOG: 2023/02/14 09:28:45.905406 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF argocd
LOG: 2023/02/14 09:28:45.905504 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF argocd-server-67f9dbb459-2zszq
2023-02-14T09:28 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-02-14T09:28 INF internal/k8s/wrappers.go:172 > Pod "argocd-server" at namespace "argocd" has port-forward accepting local connections at port 8080

2023-02-14T09:28 INF pkg/helpers.go:676 > port-forward to argocd is available at http://localhost:8080
2023-02-14T09:28 INF pkg/helpers.go:676 > Setting argocd username and password credentials
2023-02-14T09:28 INF pkg/helpers.go:676 > argocd username and password credentials set successfully
2023-02-14T09:28 INF pkg/helpers.go:676 > Getting an argocd auth token
2023-02-14T09:29 INF internal/argocd/argocd.go:374 > requesting auth token from argocd: attempt 1 of 20
2023-02-14T09:29 INF pkg/helpers.go:676 > argocd admin auth token set
2023-02-14T09:29 INF pkg/helpers.go:676 > applying the registry application to argocd
2023-02-14T09:29 INF pkg/shell.go:29 > OUT: application.argoproj.io/registry created

2023-02-14T09:29 INF pkg/shell.go:30 > Command: /Users/scott/.k1/tools/kubectl
2023-02-14T09:29 INF internal/k8s/exec.go:91 > Waiting for vault StatefulSet to be created.
2023-02-14T09:29 INF internal/k8s/exec.go:189 > Waiting for vault StatefulSet to be ready. This could take up to 60 seconds.
2023-02-14T09:29 INF internal/k8s/exec.go:203 > All Pods in StatefulSet vault are ready.
LOG: 2023/02/14 09:29:45.908798 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF vault
LOG: 2023/02/14 09:29:45.908907 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF vault-0
2023-02-14T09:29 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-02-14T09:29 INF internal/k8s/wrappers.go:172 > Pod "vault-0" at namespace "vault" has port-forward accepting local connections at port 8200

This now works for both.

Signed-off-by: Scott Hawkins <scott@echoboomer.net>
Signed-off-by: Scott Hawkins <scott@echoboomer.net>
Signed-off-by: Scott Hawkins <scott@echoboomer.net>
@echoboomer
Copy link
Contributor Author

Added wait/pf for console too:

2023-02-14T11:50 INF internal/k8s/exec.go:35 > Waiting for kubefirst-console Deployment to be created.
2023-02-14T11:50 INF internal/k8s/exec.go:187 > Waiting for kubefirst-console Deployment to be ready. This could take up to 120 seconds.
2023-02-14T11:51 INF internal/k8s/exec.go:201 > All Pods in Deployment kubefirst-console are ready.
LOG: 2023/02/14 11:51:11.471897 /Users/scott/src/kubefirst/internal/k8s/portForward.go:94: Namespace for PF kubefirst
LOG: 2023/02/14 11:51:11.471991 /Users/scott/src/kubefirst/internal/k8s/portForward.go:95: Name for PF kubefirst-console-84ccd6cd4b-7gl7v
2023-02-14T11:51 INF internal/k8s/wrappers.go:169 > port forwarding is ready to get traffic
2023-02-14T11:51 INF internal/k8s/wrappers.go:172 > Pod "kubefirst-console" at namespace "kubefirst" has port-forward accepting local connections at port 9094

2023-02-14T11:51 INF cmd/civo/civo.go:504 > kubefirst installation complete
2023-02-14T11:51 INF cmd/civo/civo.go:505 > welcome to your new kubefirst platform powered by Civo cloud
2023-02-14T11:51 INF pkg/helpers.go:725 > console UI is up and running

@echoboomer echoboomer merged commit bc15a46 into main Feb 14, 2023
@echoboomer echoboomer deleted the civo-vault-ready-bugfix branch February 14, 2023 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants