Add secretName to spec.tls. Closes #294

[CC007]

Purpose

Be able to configure a TLS certificate secret in your k8s cluster, based on the wso2is deployment name

Goals

Added secretName to spec.tls property in the ingress config file

User stories

#294

Release note

Added secretName to spec.tls property in the ingress config file, so that you can add a TLS certificate secret to your k8s cluster that will be used for requests to wso2is.

Documentation

N/A. Nothing changes in regards to what the user has to configure

Certification

N/A. This is a very basic kubernetes feature.

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
• Ran FindSecurityBugs plugin and verified report? no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

This allows you to do this:

sudo kubectl create secret tls wso2is-pattern-1-tls -n <NAMESPACE> --cert="path/to/cert.pem" --key="path/to/key.pem"

Test environment

OS: Windows 10 2020H2 using WSL2 Ubuntu 18.04
K8S: v1.18
kubernetes-is: 5.11.0-3

[CLAassistant]

All committers have signed the CLA.

[sahangunathilaka]

@CC007, Thank you for your contribution on this.

Please note that this is the minimal reference version that we are maintaining simply that everyone can use. There can be multiple changes as you suggested to be done on top of this. We are not planing to add them here but let everyone to take the advantage of making any improvement on top this and use.

Further, we need close the PR as this has been opened for long time.