add additional information to AppDefinition for other hostnames that have to be exposed
path based ingresses did not specify a secretName but relied on a working default certificate.
This adds a hosts.paths.tlsSecretName boolean property which defaults to false (i.e. default behaviour is the same). When set to true the same secretName as for the subdomain based ingresses will be used then.
allows to configure whether cert manager annotations should be added on the ingresses or not via ingress.certManagerAnnotations. This is useful when the certifcates won't be managed by cert-manager at all. Default is still true.
adds hosts.additionalWildcardInstances to instances. This is required when the certificates shall be managed via cert-manager, so that all possible paths are already available in the ingress and therefore included in the requests of the cert-manager.
changes the self-signed certificates to use a custom certificate authority. This allows to accept all certificates from this authority and eases local testing with subdomains.
adapt document regeneration documentation to always use latest image
hosts.paths.tlsSecretNameboolean property which defaults tofalse(i.e. default behaviour is the same). When set totruethe same secretName as for the subdomain based ingresses will be used then.ingress.certManagerAnnotations. This is useful when the certifcates won't be managed by cert-manager at all. Default is stilltrue.hosts.additionalWildcardInstancesto instances. This is required when the certificates shall be managed via cert-manager, so that all possible paths are already available in the ingress and therefore included in the requests of the cert-manager.Also see https://github.com/eclipsesource/theia-cloud/pull/298 (also contains testing instructions)
eclipsesource/theia-cloud#296