Discussion: Should the default app config and testing support certs signed by a custom CA?
(Makes sense to start this out as a discussion and then maybe make a merge req based on the results of discussions here.)
Should a Merge Req be created for PackageRequirements.md & Testing.md To have support for certs signed by a custom CA baked into the product.
A customer (who shouldn't be named here) has been bit by the fact that not only do we not have testing around custom ca certs, but we don't even have built in support for loading a ca.crt at some correct file locations. So they've had to do last min injection of yaml hacks to mount ca.crt's at pod locations, IMO we have enough customers who will need this exact thing (like pretty much every airgapped/high IL environment) that I believe it should be baked into the default offering vs a toggleable config.
If other's agree to the need I suggest that we throw an 0 bytes ca.crt placeholder file that gets deployed by default and doesn't hurt anything.