https://pulumi.com logo
#general
Title
# general
b

busy-umbrella-36067

01/23/2019, 9:36 PM
I keep getting these messages when creating a kubernetes ingress The ingress creates successfully and all of the services behind the path rules exist, so I’m not sure what’s going on.
Copy code
~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updated error: No matching service found for ingress rule: ""
@ Updating...| / - \ | /                  prebuilt:Deploy ethereum
c

creamy-potato-29402

01/23/2019, 9:50 PM
cc @gorgeous-egg-16927?
since he is now the de facto
Ingress
expert
g

gorgeous-egg-16927

01/23/2019, 10:50 PM
@busy-umbrella-36067 Can you give some more detail on the Ingress object you've defined? Based on the
""
for the rule path, I'm guessing that's a default rule that would route traffic to your default backend. If so, that's probably a bug in the provider logic.
b

busy-umbrella-36067

01/23/2019, 10:53 PM
@gorgeous-egg-16927 Here’s a snippet, you’re right about the path being empty. It just sends all traffic to a service based on hostname only.
Copy code
spec:
  rules:
  - host: <http://bitcoin-0171.rpc.cointainers.staging.XXXXX.org|bitcoin-0171.rpc.cointainers.staging.XXXXX.org>
    http:
      paths:
      - backend:
          serviceName: bitcoin-0171
          servicePort: 8332
  - host: <http://bitcoin-01701.rpc.cointainers.staging.XXXXX.org|bitcoin-01701.rpc.cointainers.staging.XXXXX.org>
    http:
      paths:
      - backend:
          serviceName: bitcoin-01701
          servicePort: 8332
  - host: <http://litecoin-0163.rpc.cointainers.staging.XXXXX.org|litecoin-0163.rpc.cointainers.staging.XXXXX.org>
    http:
      paths:
      - backend:
          serviceName: litecoin-0163
          servicePort: 8332
  - host: <http://dogecoin-1100.rpc.cointainers.staging.XXXXX.org|dogecoin-1100.rpc.cointainers.staging.XXXXX.org>
    http:
      paths:
      - backend:
          serviceName: dogecoin-1100
          servicePort: 8332
g

gorgeous-egg-16927

01/23/2019, 10:58 PM
Ok, I just checked the k8s API reference again (https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#httpingresspath-v1beta1-extensions) and think it's a bug. I'll open an issue and get that fixed. In the meantime, can you omit the empty path and see if that gets you unblocked?
b

busy-umbrella-36067

01/23/2019, 11:03 PM
it isnt blocking in any way, just gets output in the update logs, adding the path back removes the message @gorgeous-egg-16927
g

gorgeous-egg-16927

01/23/2019, 11:04 PM
Great! 👍