This is an automated email from the ASF dual-hosted git repository.
dgrove pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-deploy-kube.git
The following commit(s) were added to refs/heads/master by this push:
new 958be76 Update k8s-diy-ubuntu.md (#709)
958be76 is described below
commit 958be76e9078e91ccca3046fd13d3756d1bf6a0a
Author: Paul.42 <[email protected]>
AuthorDate: Fri Nov 5 07:10:15 2021 -0700
Update k8s-diy-ubuntu.md (#709)
1. fix link for helm deployment instructions
2. add a very minor troubleshooting instruction for weave networks plugin
that I ran into
---
docs/k8s-diy-ubuntu.md | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/docs/k8s-diy-ubuntu.md b/docs/k8s-diy-ubuntu.md
index c8a0b39..5153b90 100644
--- a/docs/k8s-diy-ubuntu.md
+++ b/docs/k8s-diy-ubuntu.md
@@ -100,4 +100,13 @@ Now you have a running cluster with a master node and one
or more worker nodes.
Before deploying OpenWhisk, you have to set up [Dynamic Volume
Provision](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/),
as the [technical
-requirements](docs/k8s-technical-requirements.md) specify. For example, you
can dynamically provision NFS persistent volumes, setting up an nfs server, a
client provisioner and a storage class. Now you're ready to deploy openwhisk
with [Helm](##Helm).
+requirements](docs/k8s-technical-requirements.md) specify. For example, you
can dynamically provision NFS persistent volumes, setting up an nfs server, a
client provisioner and a storage class. Now you're ready to deploy openwhisk
with [Helm](../README.md#deploy-with-helm).
+
+#### Weave Network Plugin Troubleshooting
+ensure that weave has launched by running `kubectl get pods -A` and looking
for a pod named similarly to `weave-net-#####` - if the status is `Running`
you're good. if you see `CrashLoopBackOff` perform the following steps:
+1. Get logs `kubectl logs -n kube-system weave-net-m4j75 -c weave`
+2. if you see an error like this: `Network 10.32.0.0/12 overlaps with existing
route 10.33.82.0/23 on host` that means you need to choose a different network
for kubernetes to assign to itself
+3. return your cluster to a default state `sudo kubeadm reset` and hit y when
it asks if you're certain you want to do this
+4. Choose a new [private
network](https://en.wikipedia.org/wiki/Private_network) and init the cluster
like this: `sudo kubeadm init --pod-network-cidr=192.168.128.0/17
--apiserver-advertise-address=<IP ADDRESS>`
+5. tell the weave plugin to use these new values as listed in the
[configuration
options](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-changing-configuration-options)
`kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl
version | base64 | tr -d '\n')&env.IPALLOC_RANGE=192.168.128.0/17"`
+6. it should now show as `Running` under status
