When conducting load tests with k6, there may be cases where TLS verification is unnecessary.
For example, when using an ALB (Application Load Balancer) as an endpoint to call APIs.
When the connection destination is already known to be correct, and it’s troublesome to prepare a domain name that matches the server certificate, you might want to skip TLS verification.
In such cases, set the insecureSkipTLSVerify option to true.
official: https://grafana.com/docs/k6/latest/using-k6/k6-options/reference/#insecure-skip-tls-verify
export const options = {
insecureSkipTLSVerify: true,
}Here’s an example of its use:
That’s all I wanted to share in this article.
Exploring a Bit More
Since that alone feels a bit sparse, let’s explore what TLS actually is.
What Does TLS Communication Do?
The article from Nikkei XTECH was easy to understand, so I’ll borrow from it.
https://xtech.nikkei.com/it/atcl/column/16/072100153/072100004/
It’s like omitting the verification that occurs between steps 2 and 3.
When using curl, you can similarly skip TLS verification by adding the -k option.
That’s all for this article.
