We need to figure out a build process for production images. A couple things to consider:
Emissary support policy (how many versions do they support)?
Curiefense support policy
Emissary release cycle
Curiefense release cycle
An optimal scenario: support the latest patch versions, two minor versions and all supported major versions of each. That would result in a matrix build, combining all support versions (minus all incompatible versions).
For example:
Emissary supported versions: 2.3.x, 3.2.x
Curiefense supported versions: 1.5.x, 1.6.x
Emissary 2.3.x and Curiefense 1.6.x are known NOT to work (eg. too old Envoy version, etc).
The build matrix would look like this:
Emissary 2.3.x, Curiefense 1.5.x
Emissary 2.4.x, Curiefense 1.5.x
Emissary 2.4.x, Curiefense 1.6.x
Builds should be automated as much as possible (for example: use Dependabot for automatically updating and releasing patch versions)
We need to figure out a build process for production images. A couple things to consider:
An optimal scenario: support the latest patch versions, two minor versions and all supported major versions of each. That would result in a matrix build, combining all support versions (minus all incompatible versions).
For example:
Emissary 2.3.x and Curiefense 1.6.x are known NOT to work (eg. too old Envoy version, etc).
The build matrix would look like this:
Builds should be automated as much as possible (for example: use Dependabot for automatically updating and releasing patch versions)
Requires #8
References