Closed AlexBulankou closed 5 years ago
Looks like this is an ordering issue, so instructions need to be updated not to install everything from install-bundle with a single command install-bundle/core_v1alpha1_servicemapping.yaml
needs to be applied first, after that all *servicemapping.yaml
can be applied. For deletion instructions we need the opposite order.
Same thing happened to me yesterday when I first tried to install this on my local machine, but I wanted to wait before reporting anything or giving my feedback on the product. When running the sample bookstore app, both the booksve and the inventory pods entered the crashloopbackoff. The logs for the booksve pod indictate a problem with something to do with cnrm. I deleted the cluster. Trying it again, this time I manually installed the yaml files that were unrecognized and the service mappings were created.
Then when I ran the bookstore sample I got an error related to jq. I needed to install jq. Once I did that, I was able to get the books books books website up. The website appears but it is insecure. What would it require for these examples to use ssl/tls or have I just not proceeded far enough in the guide?
Hey xpat; TLS for the frontend service is outside of the scope of the bookstore sample, as that's more of a core Kubernetes functionality and should just plug right in. The communication between the Kubernetes workloads and GCP is already handled over HTTPS via the GCP client libraries.
The user guide has now been updated to protect against the "no matches for kind ServiceMapping" issue, so closing this issue out.
After 0.0.6 release: going through the installation steps, running
kubectl apply
on the CRD directory and getting partial success with servicemapping resources failing to install:CC @kibbles-n-bytes @xiaobaitusi