Failed to create channel if peer ingress enabled

[gentios]

I am trying to expose order, peer and ca so I can interact with the applications from outside world by enabling for them an ingress controller. Doing so, at the moment without a tls since I cannot find any documentation on how to properly enable it except from the helm charts configuration:

  ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: nginx
    # TODO: When working locally, we may wish to comment the cluster-issuer
    #certmanager.k8s.io/cluster-issuer: "letsencrypt-production"
  path: /
  hosts:
    # TODO: Change this to your Domain Name if not working locally
    - beta.nephos.local

I am doing also the same for order too.

The deploy fails to create the channel with the following error:

2020-01-19 11:59:34,968 misc       INFO     kubectl exec beta-peer1-hlf-peer-7f647985fc-tpbz7 -n beta -- peer channel list
2020-01-19 11:59:36,035 misc       ERROR    Command failed with CalledProcessError:
2020-01-19 11:59:36,036 misc       ERROR    2020-01-19 10:59:35.162 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2020-01-19 10:59:35.165 UTC [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
Error: error getting endorser client for channel: endorser client failed to connect to beta.nephos.local:443: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup beta.nephos.local on 10.96.0.10:53: no such host"
command terminated with exit code 1

I cannot figure it out why it keep looking for the host beta.nephos.local and not to ping the internal kubernetes ip

[alexvicegrab]

Hi @gentios, this is a known issue https://github.com/hyperledger-labs/nephos/issues (e.g. #23, #24, #22, etc.)

I have mostly moved to the AI field, so have not been, unfortunately, very active maintaining this codebase. It would be welcome if someone could help resolve these issues that I, unfortunately, do not have time to address.

Sorry to not be of further help.

[gentios]

Hi @alexvicegrab, no worries, I understand you. Probably if you enrich the documentation we would be able to understand better Nephos as a project and help in the maintenance.

Regarding the bug, even if I disable ingress and then later on I attach an ingress manually to the peer node or order node it won't arrive traffic toe the expected peer or order.

I guess the only way to expose it's through a LoadBalancer service type, however this is not the "secured" way, since there is no secured communication and so on.

What would your recommendation be in this case ?