kubes 0.5.0 → 0.5.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/README.md +1 -1
- data/docs/_docs/intro/how-kubes-works.md +7 -11
- data/lib/kubes/version.rb +1 -1
- data/lib/templates/new/yaml/deployment.yaml +0 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 19bc1aa1219b83ad85fb8ac5e2b5e8ed463e97e546927658127b75afc212fd77
|
4
|
+
data.tar.gz: 9cc42229b38fbc1d3eaa3c289133b2bb17fe4677fb6c8603dfd793c6c377ed33
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 566c1e5d878bebdd41d8eba2639e2b176896a33d103388b6380ad9524d52613dfbe55ee8e9b328cdab43cc732d9194d7908a1de4543e1e24f6daf3b83d50274b
|
7
|
+
data.tar.gz: 1ee99b1c620161b5b02b3443327c0757a8bce94de80e5f6c8c3d8bced6bfdb116035f71188eb7fec6b535bb228577a3705e9a52866af8134cf642ea9ba7937f4
|
data/CHANGELOG.md
CHANGED
@@ -3,6 +3,9 @@
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
4
4
|
This project *loosely tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
|
5
5
|
|
6
|
+
## [0.5.1]
|
7
|
+
- fix deployment generator
|
8
|
+
|
6
9
|
## [0.5.0]
|
7
10
|
- #34 Generators, docker_image helper, check project, also write full.yaml #34
|
8
11
|
- new generators: docs: https://kubes.guru/docs/generators/
|
data/README.md
CHANGED
@@ -44,8 +44,8 @@ In fact, you can use Kubes to build the files first, and then run `kubectl` dire
|
|
44
44
|
Now, use `kubectl` directly in the proper order:
|
45
45
|
|
46
46
|
kubectl apply -f .kubes/output/shared/namespace.yaml
|
47
|
-
kubectl apply -f .kubes/output/web/deployment.yaml
|
48
47
|
kubectl apply -f .kubes/output/web/service.yaml
|
48
|
+
kubectl apply -f .kubes/output/web/deployment.yaml
|
49
49
|
|
50
50
|
You can also apply with kubes. This will compile the automatically files also.
|
51
51
|
|
@@ -10,20 +10,16 @@ In fact, you can use Kubes to build the files first, and then run `kubectl` dire
|
|
10
10
|
kubes docker push
|
11
11
|
kubes compile # compiles the .kubes/resources files to .kubes/output
|
12
12
|
|
13
|
-
Now, use `kubectl` directly
|
13
|
+
Now, use `kubectl` directly and apply them in the proper order:
|
14
14
|
|
15
|
-
kubectl apply
|
16
|
-
|
17
|
-
You can also selectively apply specific files:
|
18
|
-
|
19
|
-
kubectl apply -f .kubes/output/web/deployment.yaml
|
15
|
+
kubectl apply -f .kubes/output/shared/namespace.yaml
|
20
16
|
kubectl apply -f .kubes/output/web/service.yaml
|
17
|
+
kubectl apply -f .kubes/output/web/deployment.yaml
|
21
18
|
|
22
|
-
|
23
|
-
|
24
|
-
kubes apply
|
25
|
-
|
26
|
-
The deploy command, does all 3 steps: builds the docker image, compiles the `.kubes/resources` files, and runs kubectl apply.
|
19
|
+
The deploy command simpifily does all 3 steps: build, compile, and apply.
|
27
20
|
|
28
21
|
kubes deploy
|
29
22
|
|
23
|
+
You can also run the `kubectl apply` only. The `kube apply` command compiles but will skip the docker build stage if it's already been built.
|
24
|
+
|
25
|
+
kubes apply
|
data/lib/kubes/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: kubes
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.5.
|
4
|
+
version: 0.5.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Tung Nguyen
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2020-11-
|
11
|
+
date: 2020-11-04 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: activesupport
|