ztka ingress missing ssl cert reference

[estein9825]

Expected vs actual behavior

ztka ingress yaml doesn't offer the TLS option like the general console ingress. This results in issues with clients talking to relay server:

{"level":"info","ts":"2023-02-28T20:05:52.860Z","caller":"tunnel/client.go:416","msg":"Relay Agent.Client.paralus-core-relay-agent::dial failed network: tcp  addr: 6dfa6800-ac76-4f6b-9635-ac99a7e5b492.core-connector.paralus.iherbpreprod.net:443  err: x509: certificate has expired or is not yet valid: current time 2023-02-28T20:05:52Z is after 2020-09-18T12:00:00Z  "}
{"level":"info","ts":"2023-02-28T20:05:52.860Z","caller":"tunnel/client.go:424","msg":"Relay Agent.Client.paralus-core-relay-agent::action dial out network: tcp  addr: 6dfa6800-ac76-4f6b-9635-ac99a7e5b492.core-connector.paralus.iherbpreprod.net:443  "}
{"level":"info","ts":"2023-02-28T20:05:52.860Z","caller":"tunnel/client.go:460","msg":"Relay Agent.Client.paralus-core-relay-agent::action backoff sleep: 10.224562499s  address: 6dfa6800-ac76-4f6b-9635-ac99a7e5b492.core-connector.paralus.iherbpreprod.net:443  "}

Steps to reproduce the bug

1. Enable ingress tls
2. Bootstrap a cluster

Are you using the latest version of the project?

You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.

Version 0.2.0

What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!

(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here

Had to update ztka ingress manually

• [X ] I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
• [X ] I'm using the latest version of the project.