-
Notifications
You must be signed in to change notification settings - Fork 498
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
Introduce k8s like state to easegress controllers #1061
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Providing more detailed and Kubernetes-like states to Easegress controllers.
Describe the solution you'd like
Introduce the following states to easegress controllers, accessible via
egctl
commands:Pending
: Indicates that a controller has been created but is not yet active or is in the process of initialization.Running
: Reflects that the controller is operating as expected and carrying out its tasks.Failed
: Signifies that an error has occurred within the controller, necessitating investigation or action.When
Failed
, controllers should provide an error message for user to find problem (save time for checking log).By implementing these states, users can gain more insight and easily identify potential issues. This proposal is open for further discussion and refinement to ensure alignment with easegress's existing architecture and the specific needs of its users.
The text was updated successfully, but these errors were encountered: