-
Notifications
You must be signed in to change notification settings - Fork 204
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
Method for terminating the proxy remotely #77
Comments
amcintosh
pushed a commit
to amcintosh/aws-es-proxy
that referenced
this issue
Jul 31, 2020
Provide a method of remotely terminating the proxy. See Issue abutaha#77
amcintosh
pushed a commit
to amcintosh/aws-es-proxy
that referenced
this issue
Aug 4, 2020
Probably don't want to add the ability to remotely shutdown the proxy to be accessible unless desired and in a safe environment, so moving behind a flag. Also updated the README with latest usage. See Issue abutaha#77
amcintosh
added a commit
to amcintosh/aws-es-proxy
that referenced
this issue
Aug 4, 2020
Provide a method of remotely terminating the proxy. See Issue abutaha#77
amcintosh
added a commit
to amcintosh/aws-es-proxy
that referenced
this issue
Aug 4, 2020
Probably don't want to add the ability to remotely shutdown the proxy to be accessible unless desired and in a safe environment, so moving behind a flag. Also updated the README with latest usage. See Issue abutaha#77
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. We've had an issue when using the es-proxy with cronjobs in kubernetes. The main container finishes its work and terminates, however the es-proxy sidecar continues to run and so the pod itself never finishes. We thus need to go manually clean these up periodically.
So, I'm hoping to add a patch for the proxy to accept a HTTP POST that gracefully exits, which our main container can invoke upon completion.
The text was updated successfully, but these errors were encountered: