⚠️ IMPORTANT ⚠️: This is a public repository. Make sure to not disclose:
[x] personal data beyond what is necessary for interacting with this Pull Request;
[x] business confidential information, such as customer names.
Quality gates:
[x] I'm aware of the Contributor Guide and did my best to follow the guidelines.
[x] I'm aware of the Glossary and did my best to use those terms.
Add the decision on cert-manager.
Note: I realise that we don't actually give cert-manager 0.0.0.0:443/tcp by default in apps config, rather when we configure it we do set it to 0.0.0.0:443/tcp as that is required to communicate to Let's Encrypt.
So, should I add that this is plainly recommendation, and the standard practice for us?
Or should we make it the default for prod and dev flavours, and leave it to be set explicitly in air-gapped?
⚠️ IMPORTANT ⚠️: This is a public repository. Make sure to not disclose:
Quality gates:
Add the decision on cert-manager.
Note: I realise that we don't actually give cert-manager
0.0.0.0:443/tcpby default in apps config, rather when we configure it we do set it to0.0.0.0:443/tcpas that is required to communicate to Let's Encrypt.So, should I add that this is plainly recommendation, and the standard practice for us? Or should we make it the default for prod and dev flavours, and leave it to be set explicitly in air-gapped?