More barrels of fun

pull/7329/head
Thomas Stromberg 2020-03-30 22:00:48 -07:00
parent 3265444aea
commit fe49cab611
17 changed files with 86 additions and 148 deletions

View File

@ -1,7 +1,7 @@
--- ---
title: "Commands" title: "Commands"
linkTitle: "Commands" linkTitle: "Commands"
weight: 1 weight: 2
date: 2019-08-01 date: 2019-08-01
description: > description: >
minikube command reference minikube command reference

View File

@ -6,3 +6,14 @@ description: >
Questions that come up regularly Questions that come up regularly
--- ---
## Operating-systems
## Linux
### Preventing password prompts
The easiest approach is to use the `docker` driver, as the backend service always runs as `root`.
`none` users may want to try `CHANGE_MINIKUBE_NONE_USER=true`, where kubectl and such will still work: [see environment variables](https://minikube.sigs.k8s.io/docs/reference/environment_variables/)
Alternatively, configure `sudo` to never prompt for the commands issued by minikube.

View File

@ -1,20 +0,0 @@
---
title: "Sudo prompts"
linkTitle: "Sudo prompts"
weight: 1
date: 2020-03-26
description: >
Disabling sudo prompts when using minikude start/stop/status, kubectl cluster-info, ...
---
## Use the `docker` driver
Use the `docker` driver rather than the `none` driver. `docker` driver should be used unless it does not meet requirements for some reason.
## For `none` users
For `none` users, `CHANGE_MINIKUBE_NONE_USER=true`, kubectl and such will still work: [see environment variables](https://minikube.sigs.k8s.io/docs/reference/environment_variables/)
## Otherwise deal with `sudo`
Configure `sudo` to never prompt for the commands issued by minikube.

View File

@ -1,5 +1,5 @@
--- ---
title: "Configuration & Tuning" title: "Configuration"
weight: 4 weight: 4
description: > description: >
Configuring your cluster Configuring your cluster

View File

@ -1,7 +1,6 @@
--- ---
title: "Basic controls" title: "Basic controls"
linkTitle: "Basic controls"
weight: 1 weight: 1
description: > description: >
See minikube in action! See minikube in action!

View File

@ -1,6 +1,6 @@
--- ---
title: "Dashboard" title: "Dashboard"
weight: 3 weight: 4
description: > description: >
Dashboard Dashboard
--- ---

View File

@ -1,6 +1,5 @@
--- ---
title: "Deploying apps" title: "Deploying apps"
linkTitle: "Deploying apps"
weight: 2 weight: 2
description: > description: >
How to deploy an application to minikube How to deploy an application to minikube

View File

@ -1,8 +1,6 @@
--- ---
title: "File Sync" title: "File Sync"
linkTitle: "File Sync" weight: 12
weight: 15
date: 2019-08-01
description: > description: >
How to sync files into minikube How to sync files into minikube
--- ---

View File

@ -1,7 +1,7 @@
--- ---
title: "Host access" title: "Host access"
date: 2017-01-05 date: 2017-01-05
weight: 10 weight: 9
description: > description: >
How to access host resources from a pod How to access host resources from a pod
--- ---

View File

@ -1,6 +1,7 @@
--- ---
title: "Mounting filesystems" title: "Mounting filesystems"
date: 2017-01-05 date: 2017-01-05
weight: 11
description: > description: >
How to mount a host directory into the VM How to mount a host directory into the VM
--- ---

View File

@ -1,7 +1,7 @@
--- ---
title: "Persistent Volumes" title: "Persistent Volumes"
linkTitle: "Persistent Volumes" linkTitle: "Persistent Volumes"
weight: 12 weight: 10
date: 2019-08-01 date: 2019-08-01
description: > description: >
About persistent volumes (hostPath) About persistent volumes (hostPath)

View File

@ -1,7 +1,6 @@
--- ---
title: "Pushing images" title: "Pushing images"
date: 2019-08-05 weight: 5
weight: 4
description: > description: >
There are many ways to push images into minikube. There are many ways to push images into minikube.
--- ---

View File

@ -1,72 +1,45 @@
--- ---
title: "Uninstall minikube" title: "Uninstall"
linkTitle: "Uninstall minikube" linkTitle: "Uninstall"
weight: 6 weight: 99
draft: true
date: 2019-08-18 date: 2019-08-18
description: > description: >
Reference on uninstalling minikube from your system completely. Reference on uninstalling minikube
--- ---
# Uninstall minikube on Windows NOTE: To be moved to the FAQ
Following are the ways you can install minikube on Windows. Depending on how you installed minikube, please follow the guide appropriately.
## Chocolatey ## Chocolatey
If you have installed minikube using Chocolatey package manager, follow the below steps to completely uninstall minikube from your system -
- Open a command prompt with Administrator privileges. - Open a command prompt with Administrator privileges.
- We need to delete the cluster which was created by minikube - `minikube delete` - Run `minikube delete --purge --all`
- Run, `choco uninstall minikube` to remove the minikube package from your system. - Run, `choco uninstall minikube` to remove the minikube package from your system.
- Now, navigate to your User Folder - `C:\Users\YOUR_USER_NAME` (You can also find the path by expanding the environment variable `%USERPROFILE%`)
- In this folder, delete the `.minikube` folder.
## Windows Installer ## Windows Installer
If you have downloaded and installed minikube using the Windows Installer provided in our Releases, kindly follow the below steps -
- Open a command prompt with Administrator privileges. - Open a command prompt with Administrator privileges.
- We need to delete the cluster which was created by minikube - `minikube delete` - Run `minikube delete --purge --all`
- Now, open the Run dialog box (**Win+R**), type in `appwiz.cpl` and hit **Enter** key. - Open the Run dialog box (**Win+R**), type in `appwiz.cpl` and hit **Enter** key.
- In there, find an entry for the Minikube installer, right click on it & click on **Uninstall**. - In there, find an entry for the Minikube installer, right click on it & click on **Uninstall**.
- Follow the onscreen prompts to uninstall minikube from your system.
- Now, navigate to your User Folder - `C:\Users\YOUR_USER_NAME` (You can also find the path by expanding the environment variable `%USERPROFILE%`)
- In this folder, delete the `.minikube` folder.
## Binary/Direct ## Binary/Direct
If you have downloaded just the binary and are using it to run minikube, please follow the below steps -
- Open a command prompt with Administrator privileges. - Open a command prompt with Administrator privileges.
- We need to delete the cluster which was created by minikube - `minikube delete` - Run `minikube delete --purge --all`
- Delete the minikube binary. - Delete the minikube binary.
- Now, navigate to your User Folder - `C:\Users\YOUR_USER_NAME` (You can also find the path by expanding the environment variable `%USERPROFILE%`)
- In this folder, delete the `.minikube` folder.
# Uninstall minikube on Linux
## Binary/Direct
If you have installed minikube using the direct download method, follow the below steps to uninstall minikube completely from your system -
- In the shell, type in `minikube delete` to delete the minikube cluster.
- Remove the binary using `rm /usr/local/bin/minikube`
- Remove the directory containing the minikube configuration `rm -rf ~/.minikube`
## Debian/Ubuntu (Deb) ## Debian/Ubuntu (Deb)
If you have installed minikube using the (deb) file, follow the below instructions -
- In the shell, type in `minikube delete` to delete the minikube cluster. - Run `minikube delete --purge --all`
- Uninstall the minikube package completely - `sudo dpkg -P minikube` - Run `sudo dpkg -P minikube`
- Remove the minikube configuration directory - `rm -rf ~/.minikube`
## Fedora/Red Hat (RPM) ## Fedora/Red Hat (RPM)
If you have installed minikube using RPM, follow the below steps -
- In the shell, type in `minikube delete` to delete the minikube cluster.
- Uninstall the minikube package - `sudo rpm -e minikube`
- Remove the minikube configuration directory - `rm -rf ~/.minikube`
# Uninstall minikube on MacOS
## Binary/Direct
If you have installed minikube using the direct download method, follow the below steps to uninstall minikube completely from your system -
- In the shell, type in `minikube delete` to delete the minikube cluster.
- Remove the binary using `rm /usr/local/bin/minikube`
- Remove the directory containing the minikube configuration `rm -rf ~/.minikube`
- Run `minikube delete --purge --all`
- Run `sudo rpm -e minikube`
## Brew ## Brew
If you have installed minikube using the direct download method, follow the below steps to uninstall minikube completely from your system -
- In the shell, type in `minikube delete` to delete the minikube cluster. - Run `minikube delete --purge --all`
- Uninstall the minikube package using `brew uninstall minikube` - Run `brew uninstall minikube`
- Remove the directory containing the minikube configuration `rm -rf ~/.minikube`

View File

@ -0,0 +1,35 @@
---
title: "Certificates"
weight: 7
date: 2019-08-15
description: >
All about TLS certificates
---
## Untrusted Root Certificates
Many organizations deploy their own Root Certificate and CA service inside the corporate networks.
Internal websites, image repositories and other resources may install SSL server certificates issued by this CA service for security and privacy concerns.
You may install the Root Certificate into the minikube cluster to access these corporate resources within the cluster.
### Tutorial
You will need a corporate X.509 Root Certificate in PEM format. If it's in DER format, convert it:
```
openssl x509 -inform der -in my_company.cer -out my_company.pem
```
Copy the certificate into the certs directory:
```shell
mkdir -p $HOME/.minikube/certs
cp my_company.pem $HOME/.minikube/certs/my_company.pem
```
Then restart minikube to sync the certificates:
```shell
minikube start
```

View File

@ -1,45 +1,30 @@
--- ---
title: "Continuous Integration" title: "Continuous Integration"
linkTitle: "Continuous Integration"
weight: 1 weight: 1
date: 2018-01-02
description: > description: >
Using minikube for Continuous Integration Using minikube for Continuous Integration
--- ---
## Overview ## Overview
Most continuous integration environments are already running inside a VM, and may not support nested virtualization. The `none` driver was designed for this use case. or you could alternatively use the [Docker](https://minikube.sigs.k8s.io/docs/Drivers/docker). Most continuous integration environments are already running inside a VM, and may not support nested virtualization.
## Prerequisites The `docker` driver was designed for this use case, as well as the older `none` driver.
- VM running a systemd based Linux distribution ## Example
## using none driver
Here is an example, that runs minikube from a non-root user, and ensures that the latest stable kubectl is installed: Here is an example, that runs minikube from a non-root user, and ensures that the latest stable kubectl is installed:
```shell ```shell
curl -Lo minikube \ curl -LO \
https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 \ https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 \
&& sudo install minikube /usr/local/bin/ && install minikube-linux-amd64 /tmp/
kv=$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt) kv=$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)
curl -Lo kubectl \ curl -LO \
https://storage.googleapis.com/kubernetes-release/release/$kv/bin/linux/amd64/kubectl \ https://storage.googleapis.com/kubernetes-release/release/$kv/bin/linux/amd64/kubectl \
&& sudo install kubectl /usr/local/bin/ && install kubectl /tmp/
export MINIKUBE_WANTUPDATENOTIFICATION=false export MINIKUBE_WANTUPDATENOTIFICATION=false
export MINIKUBE_HOME=$HOME /tmp/minikube-linux-amd64 start --driver=docker
export CHANGE_MINIKUBE_NONE_USER=true
export KUBECONFIG=$HOME/.kube/config
mkdir -p $HOME/.kube $HOME/.minikube
touch $KUBECONFIG
sudo -E minikube start --driver=none
``` ```
## Alternative ways
you could alternatively use minikube's container drivers such as [Docker](https://minikube.sigs.k8s.io/docs/Drivers/docker) or [Podman](https://minikube.sigs.k8s.io/docs/Drivers/podman).

View File

@ -1,42 +0,0 @@
---
title: "Untrusted Root Certificate"
linkTitle: "Untrusted Root Certificate"
weight: 1
date: 2019-08-15
description: >
Using minikube with Untrusted Root Certificate
---
## Overview
Most organizations deploy their own Root Certificate and CA service inside the corporate networks.
Internal websites, image repositories and other resources may install SSL server certificates issued by this CA service for security and privacy concerns.
You may install the Root Certificate into the minikube cluster to access these corporate resources within the cluster.
## Prerequisites
- Corporate X.509 Root Certificate
- Latest minikube binary and ISO
## Tutorial
* The certificate must be in PEM format. You may use `openssl` to convert from DER format.
```
openssl x509 -inform der -in my_company.cer -out my_company.pem
```
* You may need to delete existing minikube cluster
```shell
minikube delete
```
* Copy the certificate before creating the minikube cluster
```shell
mkdir -p $HOME/.minikube/certs
cp my_company.pem $HOME/.minikube/certs/my_company.pem
minikube start
```