I am going to repeat my tests today and may start over with fresh deployments of everything, but use the manifests that I have shared since they worked in my previous testing on the community version. Although nginx is very popular and stable, which is a good thing, the downside is that there is a lot of incorrect and out-of-date information on the Net. The use case that I've shown is such a common one, that having this discussion in one location with the same set of manifests configuring the deployment/service and ingress for the commercial and community editions will be very helpful for others. For the commercial version, I installed using the helm chart without any alterations. For the community version, I used DigitalOceans "MarketPlace" installer. In both cases, I've deployed the ingress. One cluster has the community version of nginx (aboh-cluster) and the other cluster (abitofhelp-cluster) has. Hi, Actually, I have both deployed to separate Kubernetes clusters at Digital Ocean. Basically, I want the /httpbin to disappear and pass the path onto the backend service, httpbin. What I really need is to be able to redirect to different services off of this single host, so I changed the ingress to the following, but the query always fails with a 404. When I create the following ingress with a path of '/' and send the query, I receive a proper response. > /anything (the httpbin backend service) This must be a common task, but I cannot figure out how to do the following fanout rewrite in our nginx ingress: I am not sure whether my posting is appropriate in this area, so please delete it if there is a violation of posting rules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |