Got error when using k8s service discovery

[nhanh9d]

Actual Behavior

• After add solution from issue 977, I still got error when calling service through k8s service discovery:
  • 
  • UnableToFindLoadBalancerError Message: unabe to find load balancer for /k8s/{url}|Options,Put,Get,Delete| exception is System.InvalidOperationException: KubeApiClient.CreateFromPodServiceAccount can only be called when running in a Kubernetes Pod (KUBERNETES_SERVICE_HOST and/or KUBERNETES_SERVICE_PORT environment variable is not defined)
• After I added 2 environment variables: KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT, I got another error:
  • 
  • UnableToFindLoadBalancerError Message: unabe to find load balancer for /k8s/{url}|Options,Put,Get,Delete| exception is System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\var\run\secrets\kubernetes.io\serviceaccount\token'

Steps to Reproduce the Problem

1. Use Consul Service Discovery Provider
2. Change to use K8s Service Discovery Provider
3. Here is my config:

"Routes": [
 //k8s test
 {
   "DownstreamPathTemplate": "/{url}",
   "DownstreamScheme": "http",
   "UpstreamPathTemplate": "/k8s/{url}",
   "UpstreamHttpMethod": [ "Options", "Put", "Get", "Delete" ],
   "ServiceName": "service-auth-admin-api"
 }
],
"GlobalConfiguration": {
 "ServiceDiscoveryProvider": {
   //Specify the host of Service Discovery
   "Host": "172.20.40.141",
   //Specify the port of Service Discovery
   "Port": 6443,
   "Token": "MyToken",
   "Type": "kube",
   "Namespace": "admin-auth-server"
   ////1. Consul, means that Ocelot will get service information from consul per request
   ////2. PollConsul, means that Ocelot will poll Consul for latest service information
   //"Type": "Consul",
   ////Tells Ocelot how often to call Consul for changes in the service configuration
   //"PollingInterval": 60000
 },
 "RateLimitOptions": {
   "DisableRateLimitHeaders": false,
   "QuotaExceededMessage": "Your out!",
   "HttpStatusCode": 703
 }
}

Specifications

• Version: 20H2
• Platform: Window 10 Pro

[yoramda]

Hi,

1. Try to Add Type: KubernetesServiceDiscoveryProvider to

"GlobalConfiguration": {
 "ServiceDiscoveryProvider": {
   //Specify the host of Service Discovery
   "Host": "172.20.40.141",
   //Specify the port of Service Discovery
   "Port": 6443,
   "Token": "MyToken",
   "Type": "kube",
   "Namespace": "admin-auth-server"
   ////1. Consul, means that Ocelot will get service information from consul per request
   ////2. PollConsul, means that Ocelot will poll Consul for latest service information
   Type: "KubernetesServiceDiscoveryProvider",
   ////Tells Ocelot how often to call Consul for changes in the service configuration
   //"PollingInterval": 60000
 },

2. Add LoadBalncer

Service Discovery
The following shows how to set up a Route using service discovery then select the LeastConnection load balancer.

{
    "DownstreamPathTemplate": "/api/posts/{postId}",
    "DownstreamScheme": "https",
    "UpstreamPathTemplate": "/posts/{postId}",
    "UpstreamHttpMethod": [ "Put" ],
    "ServiceName": "product",
    "LoadBalancerOptions": {
        "Type": "LeastConnection"
    },
}

When this is set up Ocelot will lookup the downstream host and port from the service discover provider and load balance requests across any available services. If you add and remove services from the service discovery provider (consul) then Ocelot should respect this and stop calling services that have been removed and start calling services that have been added.

[raman-m]

Try to Add Type: KubernetesServiceDiscoveryProvider to...

This is absolutely wrong!
The correct type of K8s provider is Kube ❗

[ghost]

@nhanh9d Hi An, have you ever successfully solved the issue? I am dealing with the same issue and also tried doing @yoramda 's suggestion but no luck.

[tomfanara]

Hello did anybody have any luck at this? I have tried reading the docs over and over and cannot get it to work. It works in Docker. I am having the same issue. Here is my routing file. Also do I need RBAC setup?

{
  "Routes": [
    {
      "DownstreamPathTemplate": "/home",
      "DownstreamScheme": "http",
      "UpstreamPathTemplate": "/test",
      "ServiceName": "productshttpaggegator",
      "UpstreamHttpMethod": [ "Get" ]
    },
    {
      "DownstreamPathTemplate": "/api/products/{postId}",
      "DownstreamScheme": "http",
      "UpstreamPathTemplate": "/products/{postId}",
      "ServiceName": "productshttpaggegator",
      "UpstreamHttpMethod": [ "Get" ]
    }
  ],
        "GlobalConfiguration": {
          "ServiceDiscoveryProvider": {
      
            "Type": "KubernetesServiceDiscoveryProvider"

          }
        }

}

[raman-m]

"Type": "KubernetesServiceDiscoveryProvider

This type doesn't exist ❗

[raman-m]

Hello everyone! The issue #977 has been reopened today due to a critical inconsistency found in testing projects. It has been acknowledged following similar reports in issue #2178 (comment).
The upcoming hotfix release will be version 23.3.6. Once the patch is released, this discussion will be concluded.