Option to ignore error from certificate auto signed
See original GitHub issueI am trying to use the optional args to pass --insecure-skip-tls-verify
but this is not working. Has some way to do this?
- uses: Azure/k8s-deploy@v1.3
with:
manifests: |
/tmp/deployment.yaml
images: deploy-service:${{ env.ENVIRONMENT }}
args: '--insecure-skip-tls-verify=true'
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
How to ignore invalid and self signed ssl connection errors ...
I wanted to curl command to ignore SSL certification warning. Does curl command have a --no-check-certificate option like wget command on ...
Read more >Ignore SSL Certificate Checks with Curl - ReqBin
To ignore invalid and self-signed certificate checks on Curl, use the -k or --insecure command-line option. This option allows Curl to ...
Read more >Ignore invalid self-signed ssl certificate in node.js with https ...
To connect to 192.168. 1.1 insecurely, use `--no-check-certificate'. My current sample code is: var req = https.
Read more >How to ignore self-signed certificates - Microsoft Q&A
I am running a web server locally with a self-signed certificate that I would like to send requests to using this code.
Read more >Option to ignore certificate errors? · Issue #93 - GitHub
Is it possible to have an option to EyeWitness to ignore errors from self-signed certificates? I'm not seeing this in the options and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@koushdey so what about the problem of having an option to ignore error from certificate auto signed?
I thought the whole issue is about that. Am I the only one feel this way? lol
Yes, there was a bug but IMO that was not the point of the issue.
I agree that this should be reopened. Right now, it is not possible to deploy to clusters which use a self-signed certificate. The issue here was not that it seemed possible to pass arguments, it’s that it isn’t possible to pass arguments.