Fixed broken links
parent
804e772efd
commit
30ad081298
|
|
@ -12,7 +12,7 @@ minikube relies on docker-machine drivers to manage machines. This document disc
|
|||
|
||||
## Creating a new driver
|
||||
|
||||
See https://github.com/machine-drivers, the fork where all new docker-machine drivers are located.
|
||||
See [MachineDrivers](https://github.com/machine-drivers) , the fork where all new docker-machine drivers are located.
|
||||
|
||||
## Builtin vs External Drivers
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ description: >
|
|||
Development Roadmap
|
||||
---
|
||||
|
||||
This roadmap is a living document outlining the major technical improvements which we would like to see in minikube during 2020, divided by how they apply to our [guiding principles](principles.en.md)
|
||||
This roadmap is a living document outlining the major technical improvements which we would like to see in minikube during 2020, divided by how they apply to our [guiding principles](https://minikube.sigs.k8s.io/docs/contrib/principles/)
|
||||
|
||||
Please send a PR to suggest any improvements to it.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
## experimental
|
||||
|
||||
This is an experimental driver. please use it only for experimental reasons.
|
||||
for a better kubernetes in container experience, use docker [driver](https://minikube.sigs.k8s.io/Drivers/docker).
|
||||
for a better kubernetes in container experience, use docker [driver](https://minikube.sigs.k8s.io/docs/drivers/docker/).
|
||||
|
||||
## Install Podman
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ aliases:
|
|||
This driver is experimental and in active development. Help wanted!
|
||||
{{% /pageinfo %}}
|
||||
|
||||
The podman driver is another kubernetes in container driver for minikube. similar to [docker](https://minikube.sigs.k8s.io/Drivers/docker/) driver. The podman driver is experimental, and only supported on Linux and macOS (with a remote podman server).
|
||||
The podman driver is another kubernetes in container driver for minikube. similar to [docker](https://minikube.sigs.k8s.io/docs/drivers/docker/) driver. The podman driver is experimental, and only supported on Linux and macOS (with a remote podman server).
|
||||
|
||||
## Requirements
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Here is a comparison table to help you choose:
|
|||
|--- |--- |--- |--- |--- |
|
||||
| [docker-env command](/docs/handbook/pushing/#1pushing-directly-to-the-in-cluster-docker-daemon-docker-env) | only docker | good |
|
||||
| [podman-env command](/docs/handbook/pushing/#3-pushing-directly-to-in-cluster-crio-podman-env) | only cri-o | good |
|
||||
| [cache add command](/pushing/#2-push-images-using-cache-command) | all | ok |
|
||||
| [cache add command](/docs/commands/cache/#minikube-cache-add) | all | ok |
|
||||
| [registry addon](/docs/handbook/pushing/#4-pushing-to-an-in-cluster-using-registry-addon) | all | ok |
|
||||
| [minikube ssh](/docs/handbook/pushing/#5-building-images-inside-of-minikube-using-ssh) | all | best |
|
||||
|
||||
|
|
@ -182,7 +182,7 @@ For illustration purpose, we will assume that minikube VM has one of the ip from
|
|||
|
||||
Ensure that docker is configured to use `192.168.39.0/24` as insecure registry. Refer [here](https://docs.docker.com/registry/insecure/) for instructions.
|
||||
|
||||
Ensure that `192.168.39.0/24` is enabled as insecure registry in minikube. Refer [here](https://minikube.sigs.k8s.io/Handbook/registry/insecure/) for instructions..
|
||||
Ensure that `192.168.39.0/24` is enabled as insecure registry in minikube. Refer [here](https://minikube.sigs.k8s.io/docs/handbook/registry/#enabling-insecure-registries/) for instructions..
|
||||
|
||||
Enable minikube registry addon:
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ registry-creds was successfully configured
|
|||
$ minikube addons enable registry-creds
|
||||
```
|
||||
|
||||
For additional information on private container registries, see [this page](https://kubernetes.io/docs/Handbook/configure-pod-container/pull-image-private-registry/).
|
||||
For additional information on private container registries, see [this page](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).
|
||||
|
||||
We recommend you use _ImagePullSecrets_, but if you would like to configure access on the minikube VM you can place the `.dockercfg` in the `/home/docker` directory or the `config.json` in the `/var/lib/kubelet` directory. Make sure to restart your kubelet (for kubeadm) process with `sudo systemctl restart kubelet`.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ configured via both, [Ingress](https://kubernetes.io/docs/concepts/services-netw
|
|||
### Installing Ambassador
|
||||
|
||||
Ambassador is available as a Minikube
|
||||
[addon]((https://github.com/kubernetes/minikube/tree/master/deploy/addons/ambassdor)). Install it by running -
|
||||
[addon]((https://minikube.sigs.k8s.io/docs/commands/addons/)). Install it by running -
|
||||
|
||||
```shell script
|
||||
minikube addons enable ambassador
|
||||
|
|
|
|||
|
|
@ -9,8 +9,8 @@ description: >
|
|||
|
||||
## Overview
|
||||
|
||||
[Auditing](https://kubernetes.io/docs/Handbook/debug-application-cluster/audit/) is not enabled in minikube by default.
|
||||
This tutorial shows how to provide an [Audit Policy](https://kubernetes.io/docs/Handbook/debug-application-cluster/audit/#audit-policy) file to the minikube API server on startup.
|
||||
[Auditing](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/) is not enabled in minikube by default.
|
||||
This tutorial shows how to provide an [Audit Policy](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/#audit-policy) file to the minikube API server on startup.
|
||||
|
||||
## Tutorial
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ is only configured to listen on ports 80 and 443. TCP and UDP services listening
|
|||
|
||||
- Latest minikube binary and ISO
|
||||
- Telnet command line tool
|
||||
- [Kubectl](https://kubernetes.io/docs/Handbook/tools/install-kubectl) command line tool
|
||||
- [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) command line tool
|
||||
- A text editor
|
||||
|
||||
## Configuring TCP and UDP services with the nginx ingress controller
|
||||
|
|
@ -228,6 +228,6 @@ for the latest info on these potential changes.
|
|||
|
||||
## Related articles
|
||||
|
||||
- [Routing traffic multiple services on ports 80 and 443 in minikube with the Kubernetes Ingress resource](https://kubernetes.io/docs/Handbook/access-application-cluster/ingress-minikube/)
|
||||
- [Use port forwarding to access applications in a cluster](https://kubernetes.io/docs/Handbook/access-application-cluster/port-forward-access-application-cluster/)
|
||||
- [Routing traffic multiple services on ports 80 and 443 in minikube with the Kubernetes Ingress resource](https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/)
|
||||
- [Use port forwarding to access applications in a cluster](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/)
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ description: >
|
|||
When using NVIDIA GPUs with the kvm2 driver, we passthrough spare GPUs on the
|
||||
host to the minikube VM. Doing so has a few prerequisites:
|
||||
|
||||
- You must install the [kvm2 driver](/docs/start/linux/#hypervisor-setup). If you already had
|
||||
- You must install the [kvm2 driver](https://minikube.sigs.k8s.io/docs/drivers/kvm2/). If you already had
|
||||
this installed make sure that you fetch the latest
|
||||
`docker-machine-driver-kvm2` binary that has GPU support.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue