models: add restart-commands for docker, kubelet, containerd #1231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
N/A
Description of changes:
Testing done:
Testing kubelet restarts for kubernetes variants:
settings.kubernetes.max-pods
to 29 to kick off the restart-command forservices.kubelet
sudo sheltie
'd and checked kubelet.service and saw that it restarted successfully.Testing containerd restarts for kubernetes variants:
settings.kubernetes.pod-infra-container-image
to "gcr.io/google-containers/pause-amd64:3.2" to kick off the restart-command forservices.kubelet
ANDservices.containerd
sudo sheltie
'd and checked kubelet.service containerd.service and saw that both restarted successfully.Testing docker restarts for ECS variants:
localhost:80
and saw nginx running successfully.sudo sheltie
'd and ransystemctl try-restart docker.service
to simulate a docker restart due to settings/configuration file changelocalhost:80
and saw nginx is still running fine.Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.