azure kubernetes 集群中所有服务的入口返回 404

如何解决azure kubernetes 集群中所有服务的入口返回 404

我在设置入口控制器 Nginx 和入口资源以管理到我的服务的路由后遇到问题，当它们的端点正确时，我一直为所有服务获取 404。 这是在 azure 中托管的。

入口控制器是命名空间：ingress-basic 服务是命名空间：默认 入口资源在命名空间中：默认

我的服务的部署由 Helm 和 Helm File 处理，这是关于服务端点的简短片段：development-manager-demo

Name:              development-manager-demo
Namespace:         default
Labels:            app.kubernetes.io/managed-by=Helm
Annotations:       meta.helm.sh/release-name: development-manager-demo
                   meta.helm.sh/release-namespace: default
Selector:          app=development-manager-demo
Type:              ClusterIP
IP Families:       <none>
IP:                10.0.22.107
IPs:               <none>
Port:              <unset>  80/TCP
TargetPort:        80/TCP
Endpoints:         10.244.0.192:80
Session Affinity:  None
Events:            <none>

我的入口文件看起来像这样，它将我引导到两个服务：

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: app-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.class: nginx
    #nginx.ingress.kubernetes.io/ssl-redirect: "false"
    #nginx.ingress.kubernetes.io/force-ssl-redirect: "false"
    #nginx.ingress.kubernetes.io/rewrite-target: /$1
    #nginx.ingress.kubernetes.io/default-backend: navigation-service
    #nginx.ingress.kubernetes.io/rewrite-target: /
spec:
 #tls:
 #- secretName: tls-secret
 #backend:
    #serviceName: defualt-http-backend
    #servicePort: 80
  rules:
  - host: myservice.cloudapp.azure.com
    http:
      paths:
      - path: /demo
        backend:
          serviceName: development-manager-demo
          servicePort: 80
      - path: /dev
        backend:
          serviceName: development-manager
          servicePort: 80

我的入口：

app-ingress     myservice.westeurope.cloudapp.azure.com   X.X.X.57   80        20h

入口描述：

Name:             app-ingress
Namespace:        default
Address:          X.X.X.57
Default backend:  default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
Rules:
  Host                                           Path  Backends
  ----                                           ----  --------
  myservice.westeurope.cloudapp.azure.com
                                                 /demo    development-manager-demo:80 (10.244.0.192:80)
                                                 /dev     development-manager:80 (10.244.0.193:80)
Annotations:                                     kubernetes.io/ingress.class: nginx
Events:
  Type    Reason  Age                 From                      Message
  ----    ------  ----                ----                      -------
  Normal  Sync    45m (x12 over 20h)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    15m (x16 over 20h)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    15m (x16 over 20h)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    15m (x16 over 20h)  nginx-ingress-controller  Scheduled for sync

当我尝试导航到 myservice.westeurope.cloudapp.azure.com/demo 或 /dev 时，我不断收到 404。 有人可以帮忙吗？ :)

已编辑

我在 Azure（Angular APP）中部署了一项服务，并配置了入口以将流量路由到应用程序并且运行良好。我相信这个问题更多地与 asp.net 核心 Swagger API 相关，它没有正确配置来处理来自入口的传入请求。

我的入门课，

  public void ConfigureServices(IServiceCollection services)
        {
            services.Configure<KafkaOptions>(configuration.GetSection(KafkaOptions.Kafka));
            services.Configure<RestOptions>(configuration.GetSection(RestOptions.Rest));
            services.AddSingleton<IDmsJsonMessageConsumer,DmsJsonMessageConsumer>();
            services.AddSingleton<IDmsJsonMessageProducer,DmsJsonMessageProducer>();
            services.AddSingleton<IVaultManagerService,VaultManagerService>();

            services.AddControllers();

            services.AddHttpClient<IVaultManagerHttpService,VaultManagerHttpService>();

            services.AddHealthChecks();

            services.AddApiVersioning(o =>
            {
                o.ReportApiVersions = true;
                o.AssumeDefaultVersionWhenUnspecified = true;
                o.DefaultApiVersion = new ApiVersion(1,0);
            });

            services.AddSwaggerGen(c =>
            {
                c.SwaggerDoc("v1",new OpenApiInfo { Title = "Demo API",Version = "v1" });
            });
        }

        // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
        public void Configure(IApplicationBuilder app,IWebHostEnvironment env)
        {
            var healthCheckOptions = new HealthCheckOptions
            {
                ResponseWriter = WriteReadinessResponse
            };

            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }
          
            app.UseRouting();

            app.UseAuthorization();

            app.UseEndpoints(endpoints =>
            {
                endpoints.MapControllers();
                endpoints.MapHealthChecks("/health/readiness",healthCheckOptions);
                endpoints.MapHealthChecks("/health/liveness",new HealthCheckOptions()
                {
                    Predicate = (_) => false
                });
            });

            // enable swagger support
            app.UseSwagger();

            app.UseSwaggerUI(c =>
           {
               c.SwaggerEndpoint("/swagger/v1/swagger.json","Demo API V1");
           });
        }

有人可以帮我吗？任何帮助表示赞赏:)

解决方法

我设法解决了这个问题，在launchSettings.json中配置的路径是swagger

..
      "launchUrl": "swagger",..

通过改变入口路由来大摇大摆地工作。

..
 paths:
      - path: /swagger
        backend:
          serviceName: development-manager
          servicePort: 80
..