philipz

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  extraMounts:
  - hostPath: /Users/YOURNAME/lab/kind
    containerPath: /home/kind
  extraPortMappings:
 ## expose port 31080 of the node to port 80 on the host

philipz

helm template <CHART_NAME> <REPO_NAME>/<PATH_TO_CHART>
- example -
helm template nginx-ingress nginx/nginx-ingress

helm template validator-1 ./charts/goquorum-node --namespace quorum --values ./values/validator.yml --debug > test.yaml

philipz

Knative Quickstart in Kind

Ref: How to set up a local Knative environment with KinD and without DNS headaches

Install kn and kn-quickstart

https://knative.dev/docs/client/install-kn/

https://github.com/knative-extensions/kn-plugin-quickstart

Create Kind Cluster

philipz

copy a file from local filesystem into a container:

cat [local file path] | kubectl exec -i -n [namespace] [pod] -c [container] "--" sh -c "cat > [remote file path]"

ex:

cat keycloak-benchmark-dataset-0.10-SNAPSHOT.jar | k exec -i pods/keycloak-65f866dc7b-2kpn5 "--" sh -c "cat > /opt/keycloak/providers/keycloak-benchmark-dataset-0.10-SNAPSHOT.jar"

philipz

1. VM increasing the size of Disk.
2. sudo fdisk -l 確認是否已經DISK空間是否擴增。
3. sudo fdisk /dev/sda

[root@localhost ~]# fdisk /dev/sda Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them. Be careful before using the write command.

philipz

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

philipz

Seven Rules for Sound Documentation

1. Write Documentation from the Reader’s Point of View
2. Avoid Unnecessary Repetition
3. Avoid Ambiguity 3.a Explain Your Notation
4. Use a Standard Organization
5. Record Rationale
6. Keep Documentation Current but Not Too Current
7. Review Documentation for Fitness of Purpose

philipz

Task 1: Create a Docker image and store the Dockerfile

source <(gsutil cat gs://cloud-training/gsp318/marking/setup_marking.sh)
gcloud source repos clone valkyrie-app
cd valkyrie-app

cat > Dockerfile <<EOF
FROM golang:1.10
WORKDIR /go/src/app
COPY source .

philipz

########################################################################################

Task 1: Download the monolith code and build your container

git clone https://github.com/googlecodelabs/monolith-to-microservices.git

cd ~/monolith-to-microservices
./setup.sh

philipz

Task1

gcloud compute instances create nucleus-jumphost \
          --network nucleus-vpc \
          --zone us-east1-b  \
          --machine-type f1-micro  \
          --image-family debian-9  \
          --image-project debian-cloud