Problem with Rabbitmq cluster in Kubernetes
up vote
0
down vote
favorite
I successfully setup RabbitMQ cluster by helm usig this chart (https://github.com/helm/charts/tree/master/stable/rabbitmq-ha) in k8s, but can't create connection with server in my exteranl .net core application. Receiving such exception:
RabbitMQ.Client.Exceptions.BrokerUnreachableException: "None of the specified endpoints were reachable
I have enabled ingress and have access to rmq managment console with hostname. I checked ports(5672, 15672) in docker containers, they are opened. What is wrong with this?
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
kubernetes rabbitmq edited Nov 21 at 13:05
Shudipta Sharma
1,059212
asked Nov 21 at 12:30
Шебалов Денис
12
add a comment |
up vote
0
down vote
favorite
I successfully setup RabbitMQ cluster by helm usig this chart (https://github.com/helm/charts/tree/master/stable/rabbitmq-ha) in k8s, but can't create connection with server in my exteranl .net core application. Receiving such exception:
RabbitMQ.Client.Exceptions.BrokerUnreachableException: "None of the specified endpoints were reachable
I have enabled ingress and have access to rmq managment console with hostname. I checked ports(5672, 15672) in docker containers, they are opened. What is wrong with this?
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
asked Nov 21 at 12:30
Шебалов Денис
12
What do you mean byingress? That's just HTTP(S). You should have the broker exposed as a service, either as ClusterIP or LoadBalancer -- kubernetes.io/docs/concepts/services-networking/service/…
– evilSnobu
Nov 21 at 12:33
@evilSnobu, yes, of course i exposed by service. If you will look in this chart, you will see that deployment create two services: 1)client-facing one, designed to be used for client connections to the RabbitMQ cluster with port forwarding or using a LoadBalancer I am truuing to use port-forwarding. 2)and service discovery - a headless service for connections between the RabbitMQ nodes. Saying "ingress", i just mean that in values.yaml, i am set ingress enable to true.
– Шебалов Денис
Nov 21 at 12:40
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I successfully setup RabbitMQ cluster by helm usig this chart (https://github.com/helm/charts/tree/master/stable/rabbitmq-ha) in k8s, but can't create connection with server in my exteranl .net core application. Receiving such exception:
RabbitMQ.Client.Exceptions.BrokerUnreachableException: "None of the specified endpoints were reachable
I have enabled ingress and have access to rmq managment console with hostname. I checked ports(5672, 15672) in docker containers, they are opened. What is wrong with this?
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
asked Nov 21 at 12:30
Шебалов Денис
12
I successfully setup RabbitMQ cluster by helm usig this chart (https://github.com/helm/charts/tree/master/stable/rabbitmq-ha) in k8s, but can't create connection with server in my exteranl .net core application. Receiving such exception:
RabbitMQ.Client.Exceptions.BrokerUnreachableException: "None of the specified endpoints were reachable
I have enabled ingress and have access to rmq managment console with hostname. I checked ports(5672, 15672) in docker containers, they are opened. What is wrong with this?
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
asked Nov 21 at 12:30
Шебалов Денис
12
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
asked Nov 21 at 12:30
Шебалов Денис
12
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
edited Nov 21 at 13:05
Shudipta Sharma
1,059212
1,059212
asked Nov 21 at 12:30
Шебалов Денис
12
asked Nov 21 at 12:30
Шебалов Денис
12
asked Nov 21 at 12:30
Шебалов Денис
12
12
What do you mean byingress? That's just HTTP(S). You should have the broker exposed as a service, either as ClusterIP or LoadBalancer -- kubernetes.io/docs/concepts/services-networking/service/…
– evilSnobu
Nov 21 at 12:33
@evilSnobu, yes, of course i exposed by service. If you will look in this chart, you will see that deployment create two services: 1)client-facing one, designed to be used for client connections to the RabbitMQ cluster with port forwarding or using a LoadBalancer I am truuing to use port-forwarding. 2)and service discovery - a headless service for connections between the RabbitMQ nodes. Saying "ingress", i just mean that in values.yaml, i am set ingress enable to true.
– Шебалов Денис
Nov 21 at 12:40
add a comment |
What do you mean byingress? That's just HTTP(S). You should have the broker exposed as a service, either as ClusterIP or LoadBalancer -- kubernetes.io/docs/concepts/services-networking/service/…
– evilSnobu
Nov 21 at 12:33
@evilSnobu, yes, of course i exposed by service. If you will look in this chart, you will see that deployment create two services: 1)client-facing one, designed to be used for client connections to the RabbitMQ cluster with port forwarding or using a LoadBalancer I am truuing to use port-forwarding. 2)and service discovery - a headless service for connections between the RabbitMQ nodes. Saying "ingress", i just mean that in values.yaml, i am set ingress enable to true.
– Шебалов Денис
Nov 21 at 12:40
What do you mean by
ingress? That's just HTTP(S). You should have the broker exposed as a service, either as ClusterIP or LoadBalancer -- kubernetes.io/docs/concepts/services-networking/service/…– evilSnobu
Nov 21 at 12:33
What do you mean by
ingress? That's just HTTP(S). You should have the broker exposed as a service, either as ClusterIP or LoadBalancer -- kubernetes.io/docs/concepts/services-networking/service/…– evilSnobu
Nov 21 at 12:33
@evilSnobu, yes, of course i exposed by service. If you will look in this chart, you will see that deployment create two services: 1)client-facing one, designed to be used for client connections to the RabbitMQ cluster with port forwarding or using a LoadBalancer I am truuing to use port-forwarding. 2)and service discovery - a headless service for connections between the RabbitMQ nodes. Saying "ingress", i just mean that in values.yaml, i am set ingress enable to true.
– Шебалов Денис
Nov 21 at 12:40
@evilSnobu, yes, of course i exposed by service. If you will look in this chart, you will see that deployment create two services: 1)client-facing one, designed to be used for client connections to the RabbitMQ cluster with port forwarding or using a LoadBalancer I am truuing to use port-forwarding. 2)and service discovery - a headless service for connections between the RabbitMQ nodes. Saying "ingress", i just mean that in values.yaml, i am set ingress enable to true.
– Шебалов Денис
Nov 21 at 12:40
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412088%2fproblem-with-rabbitmq-cluster-in-kubernetes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What do you mean by
ingress? That's just HTTP(S). You should have the broker exposed as a service, either as ClusterIP or LoadBalancer -- kubernetes.io/docs/concepts/services-networking/service/…– evilSnobu
Nov 21 at 12:33
@evilSnobu, yes, of course i exposed by service. If you will look in this chart, you will see that deployment create two services: 1)client-facing one, designed to be used for client connections to the RabbitMQ cluster with port forwarding or using a LoadBalancer I am truuing to use port-forwarding. 2)and service discovery - a headless service for connections between the RabbitMQ nodes. Saying "ingress", i just mean that in values.yaml, i am set ingress enable to true.
– Шебалов Денис
Nov 21 at 12:40