Closed duxbuse closed 3 years ago
Sometimes the nginx controller does not generate a default cert, you might try generating your own and applying that to the cluster; that potentially solves the ssl/tls issue.
Generate cert:
$ cat << EOF > openssl.conf
[req]
req_extensions = v3_req
[v3_req]
subjectAltName = @alt_names
[alt_names]
DNS.1 = *.example.shop
DNS.2 = *.*.example.shop
EOF
$ openssl req -new -newkey rsa:2048 -sha256 -nodes -out cacert.csr -keyout cacert.key -config openssl.conf
$ openssl x509 -req -sha256 -days 365 -in cacert.csr -signkey cacert.key -out cacert.crt
Apply to the default namespace:
$ kubectl create secret tls tls-secret \
--key key.pem \
--cert cert.pem
Your specific error is because you are setting the api url to the storefront itself i.e. http://test-web:4000/graphql , that should actually be http://test-api:3000/graphql .
On the internal vs. external side, yeah that could/should be:
http://{{ template "reactioncommerce.fullname" . }}-api.{{ .Release.Namespace }}.svc:3000
I will get around to updating that soon - for now it works.
This is issue has been open over a month with no response, going to close for now.
Howdy team, I was going through the blog post trying to set reaction up locally to test out the helm chart. I am fairly new to kubernetes and totally new to Reaction so if I have made any obvious errors, apologies. Any assistance to get this up and running would be most appreciated. After I get this test working locally I will attempt to load this into GKE.
I have run into a couple of issues so I will raise them all here in one place rather than seperate github issues. If desired I can break it up too. Issues:
http://test-web:4000/graphql
for testing and I was now able to connect.Steps to reproduce
myvalues.yaml