You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new to Argo events and I am trying to create use case, where I trigger a workflow upon receiving an argo event from my bitbucket server.
I think I have created all the necessary resources in my EKS cluster. However, when I try to call the webhook url, I get a 502 Bad gateway error. I noticed that the k8s service that gets called from the webhook url, is of type Nodeport and I do not see any pods being added as end point to the service. This exaplains why I am getting a 502 Bad gateway error.
Is the BitbucketServer eventsource expected to create some pods in the cluster and get attached to the service?
I am attaching the manifest file I am deploying to my cluster.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi There,
I am new to Argo events and I am trying to create use case, where I trigger a workflow upon receiving an argo event from my bitbucket server.
I think I have created all the necessary resources in my EKS cluster. However, when I try to call the webhook url, I get a 502 Bad gateway error. I noticed that the k8s service that gets called from the webhook url, is of type Nodeport and I do not see any pods being added as end point to the service. This exaplains why I am getting a 502 Bad gateway error.
Is the BitbucketServer eventsource expected to create some pods in the cluster and get attached to the service?
I am attaching the manifest file I am deploying to my cluster.
Beta Was this translation helpful? Give feedback.
All reactions