-
Notifications
You must be signed in to change notification settings - Fork 49
pod-checkpointer: Update to pod-checkpointer image that fixes #432 #498
Conversation
b6a1130
to
ce9041a
Compare
ce9041a
to
29e2a28
Compare
29e2a28
to
e622e63
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a small comment to https://github.com/kinvolk/bootkube/pull/2 but otherwise this LGTM.
You might wanna mention in the commit message the Kubelet running as a DaemonSet listens on the Host IP of the node and that's why you need the pod checkpointer to access the Host IP. |
...ts/lokomotive-kubernetes/bootkube/resources/charts/pod-checkpointer/templates/daemonset.yaml
Show resolved
Hide resolved
7ea91f3
to
c94ed88
Compare
done. |
c94ed88
to
e650fcc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
6015488
to
3dbfbfb
Compare
Baremetal pipline has been a PITA, @ipochi can you rebase and trigger CI again? |
- Fixes #432. - pod-checkpointer pod logs errors as it cannot talk to the kubelet api as mentioned in the issue. This is becuase the pod-checkpointer queries the localhost at 10250 and 10255 ports to talk to the kubelet API. Since in Lokomotive, we run the kubelet as a pod, this causes `connection refused` errors as nothing is listening at localhost. To rectify the above problem, the solution requires chanves in two places: 1. Provide a way to access the pod's `status.hostIP` as an environment variable named `HOST_IP` to use instead of localhost. This is done by modifying the daemonset configuration of kubelet. 2. Change the pod-checkpointer code to use the `HOST_IP` from above. This is done in the PR: https://github.com/kinvolk/bootkube/pull/2 - Next we update the image tag to use the new pod-checkpointer image. The tag includes the commit id which made this change. - Lastly we update the generated assets. Signed-off-by: Imran Pochi <imran@kinvolk.io>
3dbfbfb
to
8714e85
Compare
Fixes PodCheckpointer cannot talk to kubelet and logs errors #432.
pod-checkpointer pod logs errors as it cannot talk to the kubelet api
as mentioned in the issue.
This is becuase the pod-checkpointer queries the localhost at 10250 and
10255 ports to talk to the kubelet API.
Since in Lokomotive, we run the kubelet as a pod, this causes
connection refused
errors as nothing is listening at localhost.To rectify the above problem, the solution requires chanves in two
places:
Provide a way to access the pod's
status.hostIP
as an environmentvariable named
HOST_IP
to use instead of localhost. This is done bymodifying the daemonset configuration of kubelet.
Change the pod-checkpointer code to use the
HOST_IP
from above.This is done in the PR: https://github.com/kinvolk/bootkube/pull/2
Next we update the image tag to use the new pod-checkpointer image.
The tag includes the commit id which made this change.
Lastly we update the generated assets.
Signed-off-by: Imran Pochi imran@kinvolk.io