-
Notifications
You must be signed in to change notification settings - Fork 749
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
fix(eventbus): Refine auto-reconnection and bugfix #761
Conversation
@@ -4,7 +4,7 @@ RUN yum -y update && yum -y install ca-certificates openssh openssh-server opens | |||
# Argo Workflow CLI | |||
COPY assets/argo-linux-amd64 /usr/local/bin/argo | |||
|
|||
RUN argo version | |||
RUN argo version || true |
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.
Latest argo
cli has an issue that it throws an error if no kubeconfig
is provided.
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.
so shall we pin it to a version that doesnt require kubeconfig? or whats the solution?
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.
It looks like the issue has been fixed in workflow
, let me create a PR to release a new CLI version and then we update it.
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.
It was merged 4 days ago, not in any release.
It only impacts docker build
, let's use argo version || true
here for now to workaround the issue, and update it later with new CLI.
@@ -4,7 +4,7 @@ RUN yum -y update && yum -y install ca-certificates openssh openssh-server opens | |||
# Argo Workflow CLI | |||
COPY assets/argo-linux-amd64 /usr/local/bin/argo | |||
|
|||
RUN argo version | |||
RUN argo version || true |
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.
so shall we pin it to a version that doesnt require kubeconfig? or whats the solution?
There were some cases auto-reconnection didn't work, this change fixes them.
Stop using
reconnect
feature provided by NATS because sometimes there was inconsistent natsConn and stanConn statuses. Handling reconnection in Sensor and EventSource is good enough.