ingress - nginx - specify namespace of service within rules

[ajohnstone]

It would be ideal to specify another namespace of a service within the ingress rules.

my use case is to wrap authentication over the logging without providing kubernetes accounts to developers/qas etc.

"ELB -> bitly/oauth2_proxy -> ingress routing -> logging".

apiVersion: v1
items:
- apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    namespace: default
  spec:
    rules:
    - http:
        paths:
        - backend:
            nameSpace: kube-system
            serviceName: kibana-logging
            servicePort: 5601
          path: /logs

[aledbf]

@ajohnstone please check kubernetes/kubernetes#17088

[thockin]

Dup of kubernetes/kubernetes#17088

[chestack]

my workaround:

1. serviceA in namespaceA
2. create serviceB in namespaceB

spec:
    ...
    type: ExertalName
    externalName: serviceA.namespaceA.svc.cluster.local

3. add ingress rule into ingressB in namespaceB

     - path: /****
        backend:
          serviceName: serviceB
          servicePort: ***

[kornface13]

Theres a pretty big limitation here:

• spec.rules[0].http.backend.serviceName: Invalid value: "testbed-a-really-long-name.really-long-name-service-namespace.svc.cluster.local": must be no more than 63 characters

Would be much better if we could specify the namespace on its own, or if there wasn't the 63 character limit.

[thockin]

Well, it's supposed to be the literal name of a Service in the same namespace. Any interpretation beyond that is thoroughly non-portable and runs counter to the current spec.

…

On Tue, Feb 12, 2019 at 10:09 AM kornface13 ***@***.***> wrote: Theres a pretty big limitation here: - spec.rules[0].http.backend.serviceName: Invalid value: "testbed-a-really-long-name.really-long-name-service-namespace.svc.cluster.local": must be no more than 63 characters Would be much better if we could specify the namespace on its own, or if there wasn't the 63 character limit. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#878 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVODUICmEGtnhT-ear-Dtc8AOnUHiks5vMwNFgaJpZM4IVQa6> .