mirror of https://github.com/kubernetes/kops.git
Merge pull request #16145 from hakman/remove-docker-docs
docs: Remove Docker config section
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
c82d4d95ec
|
|
@ -845,8 +845,6 @@ spec:
|
|||
|
||||
Will make kube-scheduler use the scheduler policy from configmap "scheduler-policy" in namespace kube-system.
|
||||
|
||||
Note that as of Kubernetes 1.8.0 kube-scheduler does not reload its configuration from configmap automatically. You will need to ssh into the master instance and restart the Docker container manually.
|
||||
|
||||
### LogFormat
|
||||
|
||||
Choose between log format. Permitted formats: "json", "text". Default: "text".
|
||||
|
|
@ -1042,7 +1040,7 @@ When creating a systemd unit hook using the `manifest` field, the hook system wi
|
|||
spec:
|
||||
# many sections removed
|
||||
|
||||
# run a docker container as a hook
|
||||
# run a container as a hook
|
||||
hooks:
|
||||
- before:
|
||||
- some_service.service
|
||||
|
|
@ -1319,87 +1317,6 @@ spec:
|
|||
|
||||
If you have NRI disabled (i.e., `nri.enabled = false`), please note that settings for `pluginRegistrationTimeout`, and `pluginRequestTimeout` won't take effect. These settings are only applicable when NRI is enabled. It is valid configuration to enable NRI without specifying custom values for `pluginRegistrationTimeout`, and `pluginRequestTimeout`, as these fields will inherit their default values from containerd. If you need to configure additional NRI parameters, you can do so by providing your complete containerd configuration using `configOverride`.
|
||||
|
||||
## Docker
|
||||
|
||||
It is possible to override Docker daemon options for all masters and nodes in the cluster. See the [API docs](https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#DockerConfig) for the full list of options.
|
||||
|
||||
### Registry Mirrors
|
||||
|
||||
If you have a bunch of Docker instances (physical or vm) running, each time one of them pulls an image that is not present on the host, it will fetch it from the internet (DockerHub). By caching these images, you can keep the traffic within your local network and avoid egress bandwidth usage.
|
||||
This setting benefits not only cluster provisioning but also image pulling.
|
||||
|
||||
@see [Cache-Mirror Dockerhub For Speed](https://hackernoon.com/mirror-cache-dockerhub-locally-for-speed-f4eebd21a5ca)
|
||||
@see [Configure the Docker daemon](https://docs.docker.com/registry/recipes/mirror/#configure-the-docker-daemon).
|
||||
|
||||
```yaml
|
||||
spec:
|
||||
docker:
|
||||
registryMirrors:
|
||||
- https://registry.example.com
|
||||
```
|
||||
|
||||
### Skip Install
|
||||
|
||||
If you want nodeup to skip the Docker installation tasks, you can do so with:
|
||||
|
||||
```yaml
|
||||
spec:
|
||||
docker:
|
||||
skipInstall: true
|
||||
```
|
||||
|
||||
**NOTE:** When this field is set to `true`, it is entirely up to the user to install and configure Docker.
|
||||
|
||||
### Storage
|
||||
|
||||
The Docker [Storage Driver](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-storage-driver) can be specified in order to override the default. Be sure the driver you choose is supported by your operating system and docker version.
|
||||
|
||||
```yaml
|
||||
docker:
|
||||
storage: devicemapper
|
||||
storageOpts:
|
||||
- "dm.thinpooldev=/dev/mapper/thin-pool"
|
||||
- "dm.use_deferred_deletion=true"
|
||||
- "dm.use_deferred_removal=true"
|
||||
```
|
||||
|
||||
### Networking
|
||||
|
||||
In order for containers started with `docker run` instead of Kubernetes to have network and internet access you need to enable the necessary [iptables](https://docs.docker.com/network/iptables/) rules:
|
||||
|
||||
```yaml
|
||||
docker:
|
||||
ipMasq: true
|
||||
ipTables: true
|
||||
```
|
||||
|
||||
### Custom Packages
|
||||
|
||||
kOps uses the `.tgz` (static) packages for installing Docker on any supported OS. This makes it easy to use a custom build or pre-release packages, by specifying its URL and sha256:
|
||||
|
||||
```yaml
|
||||
spec:
|
||||
containerd:
|
||||
packages:
|
||||
urlAmd64: https://download.docker.com/linux/static/stable/x86_64/docker-20.10.1.tgz
|
||||
hashAmd64: 8790f3b94ee07ca69a9fdbd1310cbffc729af0a07e5bf9f34a79df1e13d2e50e
|
||||
```
|
||||
|
||||
The format of the custom package must be identical to the official packages:
|
||||
|
||||
```bash
|
||||
tar tf docker-20.10.1.tgz
|
||||
docker/containerd
|
||||
docker/containerd-shim
|
||||
docker/containerd-shim-runc-v2
|
||||
docker/ctr
|
||||
docker/docker
|
||||
docker/docker-init
|
||||
docker/docker-proxy
|
||||
docker/dockerd
|
||||
docker/runc
|
||||
```
|
||||
|
||||
## sshKeyName
|
||||
|
||||
In some cases, it may be desirable to use an existing AWS SSH key instead of allowing kOps to create a new one.
|
||||
|
|
|
|||
|
|
@ -290,7 +290,7 @@ spec:
|
|||
|
||||
Full documentation is accessible via [godoc](https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#ClusterSpec).
|
||||
|
||||
The `ClusterSpec` allows a user to set configurations for such values as Docker log driver, Kubernetes API server log level, VPC for reusing a VPC (`NetworkID`), and the Kubernetes version.
|
||||
The `ClusterSpec` allows a user to set configurations for such values as Kubernetes API server log level, VPC for reusing a VPC (`NetworkID`), and the Kubernetes version.
|
||||
|
||||
More information about some of the elements in the `ClusterSpec` is available in the following:
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ pod components require to run, such as:
|
|||
|
||||
* Operating system components i.e. `sshd`, `udev` etc.
|
||||
* Kubernetes system components i.e. `kubelet`, `container runtime` (e.g.
|
||||
Docker), `node problem detector`, `journald` etc.
|
||||
containerd), `node problem detector`, `journald` etc.
|
||||
|
||||
As you manage your cluster, it's important that you are cognisant of these
|
||||
components because if your critical non-pod components don't have enough
|
||||
|
|
|
|||
Loading…
Reference in New Issue