-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document changing the sandbox image in CR #33660
Document changing the sandbox image in CR #33660
Conversation
@@ -266,6 +266,49 @@ visit [MCR Deployment Guide](https://docs.mirantis.com/mcr/20.10/install.html). | |||
Check the systemd unit named `cri-docker.socket` to find out the path to the CRI | |||
socket. | |||
|
|||
## Overriding the sandbox (pause) image |
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.
I wasn't sure if this should be it's own section or sub headings under the other CR docs, felt nice to keep this separate.
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.
I think these should be separate sub sections under the individual CRs.
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Thanks for this PR @domgoodwin
Added a couple if comments but this looks good to me overall.
/sig node cluster-lifecycle
@@ -266,6 +266,49 @@ visit [MCR Deployment Guide](https://docs.mirantis.com/mcr/20.10/install.html). | |||
Check the systemd unit named `cri-docker.socket` to find out the path to the CRI | |||
socket. | |||
|
|||
## Overriding the sandbox (pause) image |
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.
I think these should be separate sub sections under the individual CRs.
#### Custom sandbox (pause) images | ||
|
||
Container runtimes are responsible for their sandbox images, a common default being `k8s.gcr.io/pause`. | ||
To set a custom image for these you need to [configure the container-runtime](/docs/setup/production-environment/container-runtimes/#overriding-the-sandbox-pause-image) |
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.
Here we can just link to the main CR page ALA "find how to setup the pause image for your CR of choice"
@neolit123: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/label tide/merge-method-squash |
### Docker Engine and Mirantis Container Runtime | ||
|
||
{{< note >}} | ||
If using the Docker Engine these instructions assume that you are using the | ||
[`cri-dockerd`](https://github.com/Mirantis/cri-dockerd) adapter to integrate | ||
Docker Engine with Kubernetes. | ||
{{< /note >}} | ||
|
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.
i think we can omit this addition given both sections ### Docker Engine
and ### Mirantis Container Runtime
already mention cri-dockerd
?
To overwrite the sandbox (pause) image the `cri-dockerd` adapter | ||
[accepts a flag](https://github.com/Mirantis/cri-dockerd/blob/master/src/config/options.go) | ||
to configure this `--pod-infra-container-image`. |
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.
To overwrite the sandbox (pause) image the `cri-dockerd` adapter | |
[accepts a flag](https://github.com/Mirantis/cri-dockerd/blob/master/src/config/options.go) | |
to configure this `--pod-infra-container-image`. | |
To overwrite the sandbox (pause) image the [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd) adapter | |
accepts the `--pod-infra-container-image` flag. |
instead of linking to the source code, suggesting that we link to the main cri-dockerd
page with hopes that its documentation will enumerate flags eventually.
#### Overriding the sandbox (pause) image | ||
|
||
To overwrite the sandbox (pause) image the `cri-dockerd` adapter | ||
[accepts a flag](https://github.com/Mirantis/cri-dockerd) | ||
to configure this `--pod-infra-container-image`. |
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.
we can just duplicate this section under ### Mirantis Container Runtime
, given both use cri-dockerd
.
this is what i meant here:
#33660 (comment)
LGTM label has been added. Git tree hash: 70732dae0185672ccb22078b92b496474a91c49c
|
other than this detail the change LGTM. thanks! /lgtm |
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
LGTM label has been added. Git tree hash: a9577aa3c910675b3bf9283688c5b40750e6c4ba
|
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.
I'd prefer not to have several headings in the same page that have identical text, unless we give them suitable custom fragment identifiers.
I also made some other style / content suggestions; these are less important.
To set a custom image for these you need to configure this in your [container runtime](/docs/setup/production-environment/container-runtimes/) | ||
to use the image. | ||
|
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.
We don't document all container runtimes and we don't have a lot of capacity to maintain docs for
lots of container runtimes. Ideally we'd be able to link to container runtimes' docs on this, however those docs aren't there to link to.
So, we need to compromise.
How about:
To set a custom image for these you need to configure this in your [container runtime](/docs/setup/production-environment/container-runtimes/) | |
to use the image. | |
To set a custom image for these you need to configure this in your | |
{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} | |
to use the image. | |
Consult the documentation for your container runtime to find out how to change this setting; | |
for selected container runtimes, you can also find advice within the | |
[Container Runtimes]((/docs/setup/production-environment/container-runtimes/) topic. |
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.
💭 are there any container runtimes that work properly with Kubernetes and that don't use a pause image at all?
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
BTW, @domgoodwin: if you know how to do a squash on your side, please do. That's slightly tidier. No worries though if you're not sure. |
6dcf806
to
88885dd
Compare
Thanks @sftim I've added those changes now and merged all commits into 1. I'm too used to squashing on PR merge! |
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
@sftim PTAL again
LGTM label has been added. Git tree hash: ed77052921705e0e937090f7cb975d2ff0cfb985
|
(Since the author force-pushed with squashed commit 12 days ago) |
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/container-runtimes.md
Outdated
Show resolved
Hide resolved
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
LGTM label has been added. Git tree hash: 9fbf1adb81f161b695396faea8b7d15c16a65749
|
Add back label if @domgoodwin are not going to squash commits by their-self. Note: Free to use |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zacharysarah The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Adds documentation around how to overwrite the pause/sandbox image in an airgapped environment.
Also adds mention to these instructions in the kubeadm-init page
closes #33613