🌱Add new config to pr-link check

[smoshiur1237]

Adding new config for link check on PRs.

1. --insecure = ignore ssl problems
2. --exclude-all-private = private addresses are unreachable anyways
3. --no-progress = don't print progress

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	2411f14
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-openstack/deploys/692ffb99308ff300085cd720
😎 Deploy Preview	https://deploy-preview-2876--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[smoshiur1237]

/cc @bnallapeta

[lentzi90]

The other I understand, but why --insecure. Do we have links to sites with broken TLS? I am thinking that we should probably check if we link to such sites.

[smoshiur1237]

The other I understand, but why --insecure. Do we have links to sites with broken TLS? I am thinking that we should probably check if we link to such sites.

Actually I have seen issues in other projects where the links are correct but it was giving error in link check with broken TLS.. That's why I am thinking to add it here for future check

[smoshiur1237]

If you don't want this insecure tag. I am also ok, not to add it here. Just let me know @lentzi90

[lentzi90]

Discussed offline. The issue is that lychtee can get TLS issues even when browsers work well.
So I am fine with this.
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lentzi90]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bnallapeta]

/lgtm