↓こいつのスイッチを静音化する。
https://www.kensington.com/ja-jp/p/製品/コントロール/トラックボール/エキスパートマウス-ワイヤレストラックボール/
元々のスイッチは D2F-01F 互換っぽい形をした Kailh のスイッチ。Redditのスレッド によると KH-PS1704-42
との事。
電子工作は子供の頃にやった以来ほとんどしてない素人で色々あれかもしれないけど、一応成功している。
↓こいつのスイッチを静音化する。
https://www.kensington.com/ja-jp/p/製品/コントロール/トラックボール/エキスパートマウス-ワイヤレストラックボール/
元々のスイッチは D2F-01F 互換っぽい形をした Kailh のスイッチ。Redditのスレッド によると KH-PS1704-42
との事。
電子工作は子供の頃にやった以来ほとんどしてない素人で色々あれかもしれないけど、一応成功している。
MetricCategory | MetricName | MetricDimensions | MetricType | MetricTable | MetricNamespace | MetricOrigin | Comments | |
---|---|---|---|---|---|---|---|---|
Node-CPU | cpuAllocatableNanoCores | Objectname='K8SNode', Instancename=<nodename> | Gauge | Perf | Amount of cpu that is allocatable by Kubernetes to run pods, expressed in nanocores/nanocpu unit | |||
Node-CPU | cpuCapacityNanocores | Objectname='K8SNode', Instancename=<nodename> | Gauge | Perf | Total CPU capacity of the node in nanocore/nanocpu unit | |||
Node-CPU | cpuUsageNanocores | Objectname='K8SNode', Instancename=<nodename> | Gauge | Perf | CPU used by node in nanocore/nanocpu unit | |||
Node-Memory | memoryAllocatableBytes | Objectname='K8SNode', Instancename=<nodename> | Gauge | Perf | Amount of memory in bytes that is allocatable by kubernetes to run pods | |||
Node-Memory | memoryCapacityBytes | Objectname='K8SNode', Instancename=<nodename> | Gauge | Perf | Total memory capacity of the node in bytes | |||
Node-Memory | memoryRssBytes | Objectname='K8SNode', Instancename=<nodename> | Gauge | Perf | Rss memory used by the node in bytes. Collected only for L |
run tcpdump on a POD and then (live) see that information through wireshark locally on my machine. the magic of ssh and fifo | |
Topology | |
-------- | |
[laptop with wireshark] ------> [AKS Node] ----> [POD (tcpdump is here)]. | |
1. create the fifo on your local machine (where wireshark will run) | |
mkfifo /tmp/remote-capture.fifo | |
2. execute the following command to send traffic from within a POD to the stdout. This will then be redirected to the fifo locally |
{ | |
"Name": "Azure k8s Cloud Provider", | |
"IsCustom": true, | |
"Description": "Everything needed by the k8s 1.11 Azure cloud provider (not including ACR, addons, etc)", | |
"Actions": [ | |
"Microsoft.Compute/disks/delete", | |
"Microsoft.Compute/disks/read", | |
"Microsoft.Compute/disks/write", | |
"Microsoft.Compute/virtualMachineScaleSets/manualUpgrade/action", | |
"Microsoft.Compute/virtualMachineScaleSets/read", |
Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.
This is just a picture of this link from March 2, 2019
Originally, I had included some other solution
FROM golang:1.8 | |
RUN curl https://glide.sh/get | sh | |
ENV PKG_NAME=github.com/medicalwei/some-project | |
ENV PKG_PATH=$GOPATH/src/$PKG_NAME | |
WORKDIR $PKG_PATH | |
COPY glide.yaml glide.lock $PKG_PATH/ | |
RUN glide install |