Sha256: c833c06b1cfc4a9b09ea1ce2728195a44b07f48fc84693acc39b2550efeba5c4
Contents?: true
Size: 1.42 KB
Versions: 12
Compression:
Stored size: 1.42 KB
Contents
---
title: Review Project
---
Let's review the resources.
## Namespace
We'll create a namespace for the app resources:
.kubes/resources/shared/namespace.rb
```ruby
name "demo"
labels(app: "demo")
```
## Deployment
The `web/deployment.rb` file is a little more interesting:
.kubes/resources/web/deployment.rb
```ruby
name "demo-web"
labels(role: "web")
namespace "default"
replicas 1
image built_image # IE: user/demo:kubes-2020-06-13T19-55-16-43afc6e
```
The DSL form is more concise than the YAML form. Also, notice the use of the `built_image` helper. The `built_image` is a kubes helper method that refers to the latest Docker image built. This spares you from updating the image manually.
## Base Folder
Also let's check the files in the base folder.
.kubes/resources/base/all.rb
```ruby
namespace "default"
labels(app: "demo")
```
The base folder files are processed first as a part of [Kubes Layering]({% link _docs/layering.md %}). This allows you to define common fields and keep your code DRY.
Next, let's look at `service.rb`
.kubes/resources/web/service.rb
```ruby
name "demo-web"
labels(role: "web")
# Optional since default port is 80
# port 80
# targetPort 80
```
Service is also pretty simple. Though the DSL may seem simple, it allows you to fully control the generated YAML. You can learn more about the DSL form at: [Deployment DSL Docs]({% link _docs/dsl/resources/deployment.md %})
Next, we'll deploy the app.
Version data entries
12 entries across 12 versions & 1 rubygems