You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 1, 2024. It is now read-only.
Copy file name to clipboardexpand all lines: deploy/minikube/index.md
+29-14
Original file line number
Diff line number
Diff line change
@@ -8,26 +8,41 @@ sidebar:
8
8
9
9
In this option you will test k8guard against a minikube context and will also deploy it to minikube. (safest way for development)
10
10
11
-
### Setup and start minikube
12
-
1.Make sure you install minikube v0.18.0. There is an [issue](https://github.com/kubernetes/minikube/issues/1521) with latest version of minikube - don't install latest.
July 14, 2017| Bear |v1.6|v1.0.0| v1.0.0| v0.1.3| v1.0.0| v1.0.0
15
+
June 1, 2017| Awyar|v1.5.1|v0.1.3| v0.1.3| v0.1.3| v0.1.3| v0.1.3
16
+
17
+
18
+
With each Kuberentes' breaking api change. There will be a new breaking change in K8Guard releases.
19
+
20
+
For that reason, K8Guard microservices versions will be pinned down to a "code name". that will be mountain names from A to Z.
21
+
22
+
23
+
For example the first code name, `Awyar` (which is a beautiful mountain in Kurdistan) has all the k8guards microservices' versions that works with Kuberentes 1.5 and the second code name which is `Bear` (a mountain in New York state), has all the versions for Kuberentes 1.6.
0 commit comments