-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error Starting local Podset Operator test (crash) #11
Comments
This is the last big step in the podset operator section. High priority bug |
I'm seeing this issue and also seeing Golang version within terminal dashboard pod is Before continuing to troubleshoot further should we remove the package here and manually fetch/install/setup |
It is installed from the |
See #13. |
#14 should resolve the issues with the operator-sdk crashing. |
Both PR are merged, so after re testing this one should be closed |
@jorgemoralespou thanks Jorge. tested and looks good. |
In the "Start the Operator" step of the Podset Operator section, the user is asked to test their local operator code by running:
Expected: Watch to see if the podset operator is started. Try listing pods or deployments related to the operator for the initial test. Then load a CR and watch for pods that are created by the operator code.
Actual: Crash / closed connection. Users can restart the workshop by clicking in the top right corner to open the nav menu, then select "Restart Session".
The text was updated successfully, but these errors were encountered: