OpenSSL | Swift OpenSSL for OS X and Linux | SSH Utils library

Here I'm wondering about the line [in s_client]
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384

You're apparently using OpenSSL 1.0.2, where that's a basically useless relic. Back in the days when OpenSSL supported SSLv2 (mostly until 2010, although almost no one used it much after 2000), the ciphersuite values used for SSLv3 and up (including all TLS, but before 2014 OpenSSL didn't implement higher than TLS1.0) were structured differently than those used for SSLv2, so it was important to qualify the ciphersuite by the 'universe' it existed in. It has almost nothing to do with the protocol version actually used, which appears later in the session-param decode:

First, make sure that https://github.com/mycomp/repo-pr does exist (meaning the case, uper or lower, of the URL is correct)

Second, check that you are correctly authenticated by GitHub through SSH:

This has been resolved. See above for the solution. It is marked with a header saying solution.

Try this it may help

If you want to use kubernetes inside a docker container my suggestion is to use k3d .

k3d is a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker.k3d makes it very easy to create single- and multi-node k3s clusters in docker, e.g. for local development on Kubernetes.

You can Download , install and use it directly with Docker. For more information you can follow the official documentation from https://k3d.io/ .

To get the list of pods you dont' need to create a k8s cluster inside a docker container . what you need is a config file for any k8s cluster . ├── Dockerfile ├-- config └── main.py 0 directories, 3 files

after that :

Whenever you fix issues, start by the first one (cause solving that may remove the remaining), which in you case seems to be:

I notice that you're connecting to https://mydomain.dev, but passing a host header for a different domain. My guess would be that curl is sending an SNI request for a mydomain.dev cert; since networking-ns-cert will acquire wildcard certs for *..my domain.dev, it's possible that the server doesn't have a cert matching the SNI request, and closes the TCP connection.

Try using the -kvv options to curl (instead of -v) to print more verbose debugging information and bypass some SSL errors. Since you have DNS and certs set up, I'd try:

curl -kvv https://helloworld-go.default.mydomain.dev

They appear to be using an implementation of the http signatures draft.

The linked document explains the way the signature needs to be calculated and how to verify it. But this is probably why your example doesn't work:

2.1.3. headers

OPTIONAL. The headers parameter is used to specify the list of HTTP headers included when generating the signature for the message.

Basically the signature doesn't include just the message, probably to prevent replay attacks. Since you just hash the message it is working as intended.

The data is dynamically retrieved from an API call. You can retrieve direct from that url and simplify the json returned to get a dataframe: