-
Notifications
You must be signed in to change notification settings - Fork 41
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
feat: Add e2 command line tool #339
base: main
Are you sure you want to change the base?
Conversation
9314200
to
83bafc0
Compare
83bafc0
to
efac1cc
Compare
util.LogInfo("Services:") | ||
util.Command.Run("kubectl get svc -n suborbital") | ||
|
||
return nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's also try starting up the kubectl proxy and pinging the e2core health endpoint to make sure it's actually started and serving?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'd just pull metadata from Kubernetes itself to ensure the services are healthy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll make some changes to the templates to support this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is a first crack at a much smaller replacement for subo, called e2.
The main change from subo is that it pulls templates from the e2core repo (not suborbital/templates) at the tag it was released at, unless told otherwise.
Testing:
The branch flag is necessary because the current release doesn't contain the templates.