Expose Solace Service to the Internet using Kong Ingress

Options
praveen
praveen Member Posts: 4 ✭
in PubSub+ Event Broker #1
I am using Solace PubSub+ standard, which is deployed using Helm Chart.
All pods and services are up and running. I have exposed Solace service into the internet using Kong Ingress.
Issue is I am able to expose using root path, I want to use custom path.
Please help me with the configuration changes that are made.
Tagged:

Answers

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 921 admin
    #2
    Options

    Hi @praveen,

    Can you elaborate more on what you mean by root and custom path? Are you referring to the SEMP REST API for management? or something else?

  • praveen
    praveen Member Posts: 4 ✭
    #3
    Options
    @marc Thanks for quick response, Sorry I was out of town for a while.
    Issue is I am exposing the solace service to the internet using http://<IP-addr>
    I want to use something like this http://<IP-addr>/solace or http://<IP-addr>/foo, other than root path (http://<IP-addr>/).
  • marc
    marc Member, Administrator, Moderator, Employee Posts: 921 admin
    #4
    Options

    Hi @praveen,

    I think what you want to do is use a route in Kong to provide that. I'm definitely not a Kong expert, but that is what I'm thinking from this stackoverflow question: https://stackoverflow.com/questions/61687855/in-kong-api-gateway-how-to-make-custom-url

    Hope that helps!

Categories

This Month's Leaders

This Week's Leaders