kumahq / kuma-counter-demo Goto Github PK

Hello,
I am following article https://konghq.com/blog/getting-started-kuma-service-mesh/
and when running kubectl port-forward svc/kuma-control-plane -n kuma-system 5681:5681 command, below error logs are appearing on terminal and GUI is either not working or very very slow.

what am I doing wrong?

Error Logs: -

jaikratsinghtariyal@C02G47JNML7H bin % kubectl port-forward svc/kuma-control-plane -n kuma-system 5681:5681
Forwarding from 127.0.0.1:5681 -> 5681
Forwarding from [::1]:5681 -> 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
E0914 23:02:27.145726   24504 portforward.go:372] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:5681->127.0.0.1:60517: write tcp4 127.0.0.1:5681->127.0.0.1:60517: write: broken pipe
E0914 23:02:27.910222   24504 portforward.go:372] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:5681->127.0.0.1:60519: write tcp4 127.0.0.1:5681->127.0.0.1:60519: write: broken pipe
Handling connection for 5681
E0914 23:02:57.142136   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
E0914 23:02:57.927721   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
E0914 23:03:27.149215   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:27.937567   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
E0914 23:03:38.330821   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:38.653888   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
E0914 23:03:45.625788   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:47.466218   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
Handling connection for 5681
E0914 23:03:53.193923   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:56.610405   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:59.576055   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:04:12.001369   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:04:19.851502   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:04:19.851553   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681

What happened?

I am trying to get started with Kuma Service mesh, and faced an issue while working with the kuma-counter-demo

Environment Details :

Windows
Docker Desktop with Linux containers
WSL (Ubuntu)

I tried spinning up a new cluster with kind. and was able to install a install kuma control plane.

When I tried deploying the counter demo App.

The App was unable to start. Kuma Dashboard shows:

"Inbound port is not ready for the service" (I even tried with different ports.)

What happened?

While trying to deploy the DPPs my copy-paste of the code snippet was failiing.

kuma-dp run --cp-address=https://localhost:5678/ --dns-enabled=false --dataplane="type: Dataplane mesh: default name: redis networking: address: 0.0.0.0 inbound: - port: 16379 servicePort: 26379 serviceAddress: 127.0.0.1 tags: kuma.io/service: redis kuma.io/protocol: tcp" --dataplane-token-file=kuma-token-redis 2022-03-05T10:28:06.725+0500 INFO Skipping reading config from file 2022-03-05T10:28:06.726+0500 INFO kuma-dp.run effective configuration {"config": "{\"controlPlane\":{\"caCert\":\"\",\"caCertFile\":\"\",\"retry\":{\"backoff\":\"3s\",\"maxDuration\":\"5m0s\"},\"url\":\"https://localhost:5678/\"},\"dataplane\":{\"drainTime\":\"30s\",\"proxyType\":\"dataplane\"},\"dataplaneRuntime\":{\"binaryPath\":\"envoy\",\"dataplaneTokenPath\":\"kuma-token-redis\",\"resource\":\"type: Dataplane\\n mesh: default\\n name: redis\\n networking: \\n address: 0.0.0.0\\n inbound: \\n - port: 16379\\n servicePort: 26379\\n serviceAddress: 127.0.0.1\\n tags: \\n kuma.io/service: redis\\n kuma.io/protocol: tcp\"},\"dns\":{\"coreDnsBinaryPath\":\"coredns\",\"coreDnsEmptyPort\":15055,\"coreDnsPort\":15053,\"envoyDnsPort\":15054,\"prometheusPort\":19153}}"} 2022-03-05T10:28:06.726+0500 INFO kuma-dp.run rendered resource {"resource": "type: Dataplane\n mesh: default\n name: redis\n networking: \n address: 0.0.0.0\n inbound: \n - port: 16379\n servicePort: 26379\n serviceAddress: 127.0.0.1\n tags: \n kuma.io/service: redis\n kuma.io/protocol: tcp"} 2022-03-05T10:28:06.726+0500 ERROR kuma-dp.run failed to read policy {"proxyType": "dataplane", "error": "invalid meta type: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context", "errorVerbose": "error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context

Looking at error it felt an indentation issues so I copied the quoted YAML into redis.yaml, and line 2 was of whack, which I then fixed.

Now when I passed the redis.yaml file it gave me the following error.

kuma-dp run --cp-address=https://localhost:5678/ --dns-enabled=false -d redis.yaml --dataplane-token-file=kuma-token-redis 2022-03-05T10:31:24.162+0500 INFO Skipping reading config from file 2022-03-05T10:31:24.163+0500 INFO kuma-dp.run effective configuration {"config": "{\"controlPlane\":{\"caCert\":\"\",\"caCertFile\":\"\",\"retry\":{\"backoff\":\"3s\",\"maxDuration\":\"5m0s\"},\"url\":\"https://localhost:5678/\"},\"dataplane\":{\"drainTime\":\"30s\",\"proxyType\":\"dataplane\"},\"dataplaneRuntime\":{\"binaryPath\":\"envoy\",\"dataplaneTokenPath\":\"kuma-token-redis\",\"resourcePath\":\"redis.yaml\"},\"dns\":{\"coreDnsBinaryPath\":\"coredns\",\"coreDnsEmptyPort\":15055,\"coreDnsPort\":15053,\"envoyDnsPort\":15054,\"prometheusPort\":19153}}"} 2022-03-05T10:31:24.163+0500 INFO kuma-dp.run rendered resource {"resource": " type: Dataplane\n mesh: default\n name: redis\n networking: \n address: 0.0.0.0\n inbound: \n - port: 16379\n servicePort: 26379\n serviceAddress: 127.0.0.1\n tags: \n kuma.io/service: redis\n kuma.io/protocol: tcp\n"} 2022-03-05T10:31:24.163+0500 ERROR kuma-dp.run failed to read policy {"proxyType": "dataplane", "error": "invalid meta type: error converting YAML to JSON: yaml: line 7: did not find expected '-' indicator", "errorVerbose": "error converting YAML to JSON: yaml: line 7: did not find expected '-' indicator\ninvalid meta type\ngithub.com/kumahq/kuma/pkg/core/resources/model/rest.Unmarshall\n\t/home/circleci/project/pkg/core/resources/model/rest/unmarshaller.go:23\ngithub.com/kumahq/kuma/pkg/core/resources/model/rest.UnmarshallToCore\n\t/home/circleci/project/pkg/core/resources/model/rest/unmarshaller.go:13\ngithub.com/kumahq/kuma/app/kuma-dp/cmd.readResource\n\t/home/circleci/project/app/kuma-dp/cmd/dataplane.go:44\ngithub.com/kumahq/kuma/app/kuma-dp/cmd.newRunCmd.func2\n\t/home/circleci/project/app/kuma-dp/cmd/run.go:75\ngithub.com/spf13/cobra.(*Command).execute\n\t/home/circleci/.go_workspace/pkg/mod/github.com/spf13/[email protected]/command.go:845\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/home/circleci/.go_workspace/pkg/mod/github.com/spf13/[email protected]/command.go:974\ngithub.com/spf13/cobra.(*Command).Execute\n\t/home/circleci/.go_workspace/pkg/mod/github.com/spf13/[email protected]/command.go:902\ngithub.com/kumahq/kuma/app/kuma-dp/cmd.Execute\n\t/home/circleci/project/app/kuma-dp/cmd/root.go:83\nmain.main\n\t/home/circleci/project/app/kuma-dp/main.go:6\nruntime.main\n\t/home/circleci/go/src/runtime/proc.go:255\nruntime.goexit\n\t/home/circleci/go/src/runtime/asm_amd64.s:1581"} Error: invalid meta type: error converting YAML to JSON: yaml: line 7: did not find expected '-' indicator

Just to be clear, I am doing a Universal deployment, on an ubuntu 20.04 image over wsl2.

Description

2022-02-21T13:41:28.696Z INFO injector WARNING: you are using kuma.io/sidecar-injection as annotation. Please migrate it to label to have strong guarantee that application can only start with sidecar {"namespace": "kuma-demo"}

What happened?

Same error occured when I deployed this demo app with kuma-cp installed or not.

container: k3s

k3s default CNI: VXLAN

UI shows followed pic:

And the logs followed:

Description

It's required for universal demo.

Description

The builtin gateway is here. It would be great to have it running in the demo