-
Notifications
You must be signed in to change notification settings - Fork 123
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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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>
echoboomer
force-pushed
the
civo-vault-ready-bugfix
branch
from
February 14, 2023 16:03
8964360
to
048d87b
Compare
Signed-off-by: Scott Hawkins <scott@echoboomer.net>
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 |
kubefirst-demo-bot
approved these changes
Feb 14, 2023
jarededwards
approved these changes
Feb 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.