tree 139e9e56ea87c77cbfd94e71eb2bbb89273ce4ee
parent f7a3ede85b5ecd30f4910f86bc3edcdd4d040869
author Musab Shakeel <mskeel@arista.com> 1694907225 -0400
committer Musab Shakeel <mskeel@arista.com> 1696431622 -0400

[Operator] Add TLS + Host resource support for Ambassador ingress type

Create TLSContext resource with the specified tls secret if tls is
enabled (TLSContext is created independent of Host resource being
created).

Let the user specify if they want a Host resource, associated
with the Mappings, to be created by the operator. If tls is enabled, and
users choose `createHost: true`, then the created Host resource has
`tlsSecret` and `tlsContext` spec fields populated appropriately.

Also add Ambassador config to GerritClusterIngressConfig:
- Enable support for users to define the `ambassador_id` spec field in
  Ambassador CRs (Mapping, TLSContext) created by the operator. This is
  done by adding a new field (`ambassadorId`) in
  `GerritClusterIngressConfig`.
- The `createHost` setting referenced above is also part of this
  ambassador config.

Modifications to the Ambassador CRDs:
- `Host` CRD was copied over from the `emissary-crds.yaml` file in the
  source GitHub repo
  (https://github.com/emissary-ingress/emissary/blob/master/manifests/emissary/emissary-crds.yaml.in)
  and added to the local `emissary-crds.yaml` file in this project.
- `ambassador_id` field was copied over from v3 `Host` CRD version to
  the v2 version.

Change-Id: I30ce8cdea93ef8b84ab5d4b4e3b6080c59dd3fed