Hey 👋

We'd love to use emojivoto as an example workload in @polarsignals. To produce some data for Polar Signals Continuous Profiler we'de love to add pprof endpoints to each of the components. Would you be open to us adding the pprof endpoints in a similar manner as the prometheus endpoint? If you prefer we can also generalize them into a single "telemetry" port.

Let me know what you think, we're happy to take care of it!

When trying to access the web app through kubectl proxy at http://localhost:8001/api/v1/namespaces/emojivoto/services/web-svc:http/proxy/ , I get a blank page:

These other web apps work fine:

• http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy
• http://localhost:8001/api/v1/namespaces/linkerd/services/web:http/proxy
• http://localhost:8001/api/v1/namespaces/linkerd/services/grafana:http/proxy

The emojivoto-api app appears to be unused, since the web app also serves api endpoints. We should remove emojivoto-api to avoid confusion.

With the --single-namespace flag being added in linkerd/linkerd2#1721, emojivoto is no longer a viable demo for that configuration. This is due to a naming collision between Linkerd's web deployment and emojivoto's web deployment.

Output from --single-namespace installation:

$ bin/go-run cli install --single-namespace -l emojivoto|kubectl apply -f -
...

$ curl -sL https://run.linkerd.io/emojivoto.yml | bin/go-run cli inject -l emojivoto - | kubectl apply -f -
...
The Deployment "web" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"app":"web-svc", "linkerd.io/control-plane-ns":"emojivoto", "linkerd.io/proxy-deployment":"web"}: `selector` does not match template `labels`

As a workaround, replace this:

apiVersion: apps/v1beta1
kind: Deployment
metadata:
  creationTimestamp: null
  name: web
  namespace: emojivoto

...with...

apiVersion: apps/v1beta1
kind: Deployment
metadata:
  creationTimestamp: null
  name: web-svc
  namespace: emojivoto

https://github.com/BuoyantIO/emojivoto/blob/main/Makefile#L30

I use docker-compose to deploy the applications, and got some log which seem a little strange.

voting-svc_1 | 2019/10/26 08:41:15 Starting grpc server on GRPC_PORT=[8080]
emoji-svc_1 | 2019/10/26 08:41:15 Starting grpc server on GRPC_PORT=[8080]
web_1 | 2019/10/26 08:41:16 Connecting to [voting-svc:8080]
web_1 | 2019/10/26 08:41:16 Connecting to [emoji-svc:8080]
web_1 | 2019/10/26 08:41:16 Starting web server on WEB_PORT=[8080]
voting-svc_1 | 2019/10/26 08:42:55 Voted for [:interrobang:], which now has a total of [1] votes
web_1 | 2019/10/26 08:42:56 Error serving request [&{GET /api/vote?choice=:doughnut: HTTP/1.1 1 1 map[User-Agent:[Go-http-client/1.1] Accept-Encoding:[gzip]] {} 0 [] false localhost:8089 map[choice:[:doughnut:]] map[] map[] 172.19.0.1:33281 /api/vote?choice=:doughnut: 0xc0002858c0}]: rpc error: code = Unknown desc = ERROR
voting-svc_1 | 2019/10/26 08:42:57 Voted for [:poop:], which now has a total of [1] votes
voting-svc_1 | 2019/10/26 08:42:58 Voted for [:dancer:], which now has a total of [1] votes

I got an error message of web_1.

The docker-compose

version: '3'
services:
web:
image: buoyantio/emojivoto-web:v8
environment:
- WEB_PORT=8080
- EMOJISVC_HOST=emoji-svc:8080
- VOTINGSVC_HOST=voting-svc:8080
- INDEX_BUNDLE=dist/index_bundle.js
ports:
- "8080:8080"
depends_on:
- voting-svc
- emoji-svc
emoji-svc:
image: buoyantio/emojivoto-emoji-svc:v8
environment:
- GRPC_PORT=8080
ports:
- "8081:8080"
voting-svc:
image: buoyantio/emojivoto-voting-svc:v8
environment:
- GRPC_PORT=8080
ports:
- "8082:8080"

I use go run main.go to run the emojivoto-vote-bot.

I also deploy the application to k8s, and got an error of web-svc,

2019/10/25 07:09:47 Connecting to [voting-svc-2.emojivoto:8080]
2019/10/25 07:09:47 Connecting to [emoji-svc-2.emojivoto:8080]
2019/10/25 07:09:47 Starting web server on WEB_PORT=[8080]
2019/10/25 07:10:08 Error serving request [&{GET /api/list HTTP/1.1 1 1 map[] {} 0 [] false web-svc-2.emojivoto.svc.cluster.local:8080 map[] map[] map[] 172.16.60.3:58724 /api/list 0xc00023ff80}]: rpc error: code = Canceled desc = context canceled
2019/10/25 07:10:08 Error serving request [&{GET /api/list HTTP/1.1 1 1 map[] {} 0 [] false web-svc-2.emojivoto.svc.cluster.local:8080 map[] map[] map[] 172.16.60.3:58742 /api/list 0xc000360040}]: rpc error: code = Canceled desc = context canceled.

What do the error means?

Make the following changes to make things clearer to people using the emojivoto demo application:

• #29 the Poop page should have an explanation about why it’s broken
• #29 add an optional step to README.md describing how to provide auto-generated load (i.e. deploying the vote-bot)
• #36 Remove svc from names of emoji.voto deployments
• #36 for consistency with the other configurations, vote-bot should address the web service as "web-svc.emojivoto:80", instead of "web-svc:80" as it does currently

Hey Buoyant folks 👋

Problem

$ make deploy-to-docker-compose
docker-compose stop
docker-compose rm -vf
No stopped containers
/Library/Developer/CommandLineTools/usr/bin/make -C emojivoto-web build-container
docker build .. -t "buoyantio/emojivoto-web:v10" --build-arg svc_name=emojivoto-web
Sending build context to Docker daemon  37.67MB
Step 1/5 : FROM buoyantio/emojivoto-svc-base:v10
v10: Pulling from buoyantio/emojivoto-svc-base
91028a6d2ef7: Pull complete
21c90fa7ccf4: Pull complete
Digest: sha256:1e7039ceb589274f493d3c29f6d0e0b764795b268693ecafe127285808f63f03
Status: Downloaded newer image for buoyantio/emojivoto-svc-base:v10
 ---> f59fdbacafa2
Step 2/5 : ARG svc_name
 ---> Running in 5fcd7438e7b3
Removing intermediate container 5fcd7438e7b3
 ---> 50be637330ab
Step 3/5 : COPY $svc_name/target/ /usr/local/bin/
COPY failed: stat /var/lib/docker/tmp/docker-builder245391831/emojivoto-web/target: no such file or directory
make[1]: *** [build-container] Error 1
make: *** [deploy-to-docker-compose] Error 2

Solution
I ran the following:

$ make web
.
.
Successfully tagged buoyantio/emojivoto-web:v10

$ make emoji-svc
.
.
Successfully tagged buoyantio/emojivoto-emoji-svc:v10

$ make voting-svc
.
.
Successfully tagged buoyantio/emojivoto-voting-svc:v10

.. and then it worked.

OS, Go version, docker-compose version
MacOS, go 1.15.3 darwin, docker-compose version 1.24.1

It looks like we have the same styles applied to the emoji on the home page and the emoji on the leaderboard, such that hovering over a leaderboard emoji looks like this:

That gives the impression that the emoji is clickable, but clicking on an emoji on the leaderboard doesn't do anything. I think it would be better to remove the hover background color and pointer tooltip for the emoji on that page.

The failure page (e.g. when donut is clicked) has the text "404" in it, but this is actually a 500 response.

Follow up from #41. Containers in the lifecycle test app intentionally exit after a given number of requests. Per kubernetes/kubernetes#57291, Kubernetes puts these pods into an exponential CrashLoopBackoff, with up to 5 minute backoff. Ideally for our testing, we need a faster restart.

One option to mitigate this would be a script that periodically runs a kubectl delete po/foo command.

In order to see stats generated by the vote-bot service, we need to move the vote-bot image into its own pod in the emojivoto namespace

Not sure where we need to be placing this in the React project, maybe through import?...

=====

Add favicon to demo app. Check with @siggy about serving resource deployment and where we need to reference in the React project.

//emoji-app-favicon.png//

make build fails when run with recent versions of protocol. We should update the build tooling to work on recent dependencies.

Some of the Emoji we're using are from a newer version of Unicode. They show up as empty boxes on macOS 10.10 according to @klingerf. @klingerf said he would like us to stick to an older version of Unicode that is more widely supported and I agree.

The test environment introduced in #41, intended to exercising route, telemetry, and
service discovery lifecycles in Conduit, includes the following:

• conduit control + data plane
• 1 slow-cooker, 100qps
• 10 HTTP point-to-point servers
• 10 gRPC terminus servers, with container restart every 600 requests (~1 minute)

We should extend this environment to exercise additional dimensions, namely:

• #45 M number of point-to-point servers
• #45 N number of terminus servers
• X call-depth length via point-to-point servers
• #45 Y discrete call graphs
• #44 full pod restart, on an interval, rather than container
• #49 Deployment rolling restart, on an interval
• #51 injected vs. baseline performance
• performance at 10qps, 100qps, 1,000qps, 10,000qps
• #51 with and without TLS (depends on linkerd/linkerd2#1295)

The Prometheus Benchmark Grafana dashboard introduced in linkerd/linkerd2#984 should provide better performance analysis of Prometheus in Conduit.

Relates to #42.

docker.l5d.io/buoyantio/emojivoto-emoji-svc:v11 are not currently pullable

Issue

In MOOC LinuxFoundationX LFS143x - Introduction to Service Mesh with Linkerd Chapter 11. Canary and Blue-Green Deployments / Canary and Blue-Green Deployments / Using TrafficSplit: Part 2

Next, update the vote-bot deployment:
            Run: kubectl apply -f https://raw.githubusercontent.com/BuoyantIO/emojivoto/linux-training/training/traffic-split/vote-bot-update.yml

Command above fails because of the version number mismatch which exists in the current/existing resource. i.e. The current resource has v11 and the file still has v10.

File Path: emojivoto/training/traffic-split/vote-bot-update.yml

Linkerd Version Client version: stable-2.10.2 Server version: stable-2.10.2

Proposed Solution

Change the version number to v11.

Similar to linkerd/linkerd2#3847, the Kubernetes docs recommend a common set of labels for resources:
https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels

Add the following 3 labels to all emojivoto workloads:

app.kubernetes.io/name: web # or voting, etc
app.kubernetes.io/part-of: Emojivoto
app.kubernetes.io/version: v9

This repo does not have a license associated with it.

Are there plans to license this code under a standard open source license?

In my local setup I have a headless Linux machine running minikube and stuff. I ssh into the Linux box and do local dev on my desktop. It makes commands like minikube -n emojivoto service web-svc not work correctly because it can't figure out how to open a browser window.

Anyway just a quick note that for the instructions step 5 works for local, but this works for remote:
kubectl -n emojivoto port-forward svc/web-svc 8899:80 --address MYIP. Then open in your browser window http://MYIP:8899/

Thanks!

add a .travis.yml that tests emojivote