philipz philipz

export CLOUD_SHELL_IP=$(dig +short myip.opendns.com @resolver1.opendns.com)

Refer: datakurre/operaton-cockpit-plugins#16

docker buildx build --push --platform linux/arm64,linux/amd64,linux/amd64/v2 -t philipz/camunda-cockpit-plugins:7.21.0 .

FROM camunda/camunda-bpm-platform:run-7.21.0

USER root
RUN apk add --no-cache git zip
USER camunda

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

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

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

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"

VM increasing the size of Disk.
sudo fdisk -l 確認是否已經DISK空間是否擴增。
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.

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.

Seven Rules for Sound Documentation

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

	apiVersion: apps/v1
	kind: Deployment
	metadata:
	name: postgres-deployment
	namespace: default
	spec:
	replicas: 1
	selector:
	matchLabels:
	app: postgres