It makes a self-signed TLS Secret for mx.lab.test and installs the chart with server.certificates.secrets, then checks IMAPS on the mail Service serves that certificate.
It replaces the Secret's certificate, as a renewal does, and checks that eight connections in a row get the new one within five minutes, with the same pods and no restarts.
`lab/chart/cert-test.sh` plays cert-manager's part:
1. It makes a self-signed TLS Secret for `mx.lab.test` and installs the chart with `server.certificates.secrets`, then checks IMAPS on the mail Service serves that certificate.
2. It replaces the Secret's certificate, as a renewal does, and checks that eight connections in a row get the new one within five minutes, with the same pods and no restarts.
Passes with inbuxa/inbuxa-server#477 and inbuxa/inbuxa-charts#26 (115 s). The test puts the chart back and deletes the Secret.
Plays cert-manager's part: a self-made TLS Secret for mx.lab.test, mounted
through server.certificates.secrets, is what IMAPS serves; after its
certificate is replaced, every connection gets the new one within five
minutes, with no pod restarted.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
lab/chart/cert-test.shplays cert-manager's part:mx.lab.testand installs the chart withserver.certificates.secrets, then checks IMAPS on the mail Service serves that certificate.Passes with inbuxa/inbuxa-server#477 and inbuxa/inbuxa-charts#26 (115 s). The test puts the chart back and deletes the Secret.