Welcome to the Linux Foundation Forum!

LAB 5.7 on Instruction 10 encountering "error: error parsing STDIN.."

josephkwong
josephkwong Posts: 10
in LFS243 Class Forum

Hi Richard,

I've followed the instructions and it came out this error. Please advise w/ thank.

ERROR:
$ curl -sL https://run.linkerd.io/emojivoto.yml \

| sed 's| metadata:| metadata:\n annotations:\nconsul.hashicorp.com/connect-inject: "true"|' \
| kubectl apply -f -

namespace/emojivoto unchanged
serviceaccount/emoji unchanged
serviceaccount/voting unchanged
serviceaccount/web unchanged
service/emoji-svc unchanged
service/voting-svc unchanged
service/web-svc unchanged
error: error parsing STDIN: error converting YAML to JSON: yaml: line 17: did not find expected key**

OTHERS ARE GOOD IN RUNNING:
$ docker container ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6b066eae932c kindest/node:v1.18.20 "/usr/local/bin/entr…" 29 hours ago Up 29 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 127.0.0.1:34699->6443/tcp consul-control-plane

$ kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO NAMESPACE

kind-consul kind-consul kind-consul
$ helm status consul -n consul
NAME: consul
LAST DEPLOYED: Fri Mar 25 12:54:48 2022
NAMESPACE: consul
STATUS: deployed
REVISION: 1
NOTES:
Thank you for installing HashiCorp Consul!

$ kubectl get all -n consul
NAME READY STATUS RESTARTS AGE
pod/consul-client-lk8nx 1/1 Running 0 80m
pod/consul-connect-injector-8b6d555bc-9xlxf 1/1 Running 0 80m
pod/consul-connect-injector-8b6d555bc-jd7q5 1/1 Running 0 80m
pod/consul-server-0 1/1 Running 0 80m
pod/consul-webhook-cert-manager-7d97c959df-hjrw5 1/1 Running 0 80m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/consul-connect-injector ClusterIP 10.96.59.163 443/TCP 80m
service/consul-dns ClusterIP 10.96.168.115 53/TCP,53/UDP 80m
service/consul-server ClusterIP None 8500/TCP,8301/TCP,8301/UDP,8302/TCP,8302/UDP,8300/TCP,8600/TCP,8600/UDP 80m
service/consul-ui ClusterIP 10.96.51.201 80/TCP 80m

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/consul-client 1 1 1 1 1 80m

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/consul-connect-injector 2/2 2 2 80m
deployment.apps/consul-webhook-cert-manager 1/1 1 1 80m

NAME DESIRED CURRENT READY AGE
replicaset.apps/consul-connect-injector-8b6d555bc 2 2 2 80m
replicaset.apps/consul-webhook-cert-manager-7d97c959df 1 1 1 80m

NAME READY AGE
statefulset.apps/consul-server 1/1 80m

Answers

  • chrispokorni
    chrispokorni Posts: 1,843

    Hi @josephkwong,

    Changing the syntax of the sed command may help - that is replacing "|" with "/" such as sed 's/.../.../'

    NOTE: Please do not create duplicate posts, they will be removed.

    Regards,
    -Chris

  • Irvnet
    Irvnet Posts: 8

    Hey @josephkwong I didn't quite get that far yet... I have Ambassador working, now i'm working on getting TLS configured in Lab 4.2. I did peek ahead though.. I was wondering how that SED command was gonna work out :D

    Think I'm gonna listen to @chrispokorni and take a careful look at what SED is doing when i get to lab 5.7

    R-

  • Irvnet
    Irvnet Posts: 8

    Hey @josephkwong ... ok, I finally got to Lab 5.7, and I got the same error. Now I see what @chrispokorni is talking about now with fixing the sed command.

    I didn't really look at the yaml too carefully ... Next I'll have to dig thru ambassador-consul-connector.yaml and experiment with it a little bit to better understand what sed is doing so I can try to fix it.

    Richard

Categories

Upcoming Training