I hereby claim:
- I am thiyagaraj on github.
- I am thiyag (https://keybase.io/thiyag) on keybase.
- I have a public key whose fingerprint is 7831 BBC3 EAFF 6E13 A9F5 1435 8906 04D0 CE55 B815
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
Convert jks and get public and private keys out:
keytool -importkeystore -srckeystore default.keystore -destkeystore new-store.p12 -deststoretype PKCS12
openssl pkcs12 -in new-store.p12 -nokeys -out public.pem
openssl pkcs12 -in new-store.p12 -nodes -nocerts -out private.pem
Install the custom CSS plugin, then make a file on your computer that will hold your custom CSS, I like to make one in my home directory called ~/.vscodestyles.css
and then add the CSS into it.
Once done, open your command palette and select enable custom CSS and JS
The official guide for setting up Kubernetes using kubeadm
works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy
image defaults to the architecture of the master node (where kubeadm
was run in the first place).
This causes issues when arm
nodes join the cluster, as they will try to execute the amd64
version of kube-proxy
, and will fail.
It turns out that the pod running kube-proxy
is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.
Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see