Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use --app-namespace rather than -n for dedicated option in state-namespace docs #734

Merged
merged 2 commits into from
Mar 17, 2024
+9 −9
Merged

Use --app-namespace rather than -n for dedicated option in state-namespace docs #734

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8fe5af9
Use --app-namespace rather than -n for dedicated option in state-name…
jfmontanaro Mar 5, 2024
a6f89fa
add app-namespace documentation for v0.59.x and v0.60.x
jfmontanaro Mar 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions site/content/kapp/docs/develop/state-namespace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: Namespace for State Storage

To show list of deployed applications (via `kapp ls`), kapp manages metadata `ConfigMap` for each saved application. Each metadata `ConfigMap` contains generated label used to label all application resources. Additionally kapp creates `ConfigMap` per each deploy to record deployment history (seen via `kapp app-change list -a app1`).

`-n` (`--namespace`) flag allows to control which namespace is used for finding and storing metadata `ConfigMaps`. If namespace is not explicitly specified your current namespace is selected from kube config (typically `~/.kube/config`).
`--app-namespace` flag allows to control which namespace is used for finding and storing metadata `ConfigMaps`. If namespace is not explicitly specified the app-wide namespace is used as specified by `-n` or `--namespace`); if `-n` is not specified your current namespace is selected from kube config (typically `~/.kube/config`).

There are currently two approaches to deciding which namespace to use for storing metadata `ConfigMaps`:

Expand All @@ -22,8 +22,8 @@ There are currently two approaches to deciding which namespace to use for storin

```bash
$ kubectl create ns apps
$ kapp deploy -n apps -f app1/config.yml
$ kapp deploy -n apps -f app2/config.yml
$ kapp deploy --app-namespace apps -f app1/config.yml
$ kapp deploy --app-namespace apps -f app2/config.yml
$ kapp ls -n apps
```

Expand Down
6 changes: 3 additions & 3 deletions site/content/kapp/docs/v0.59.x/state-namespace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ title: Namespace for State Storage

To show list of deployed applications (via `kapp ls`), kapp manages metadata `ConfigMap` for each saved application. Each metadata `ConfigMap` contains generated label used to label all application resources. Additionally kapp creates `ConfigMap` per each deploy to record deployment history (seen via `kapp app-change list -a app1`).

`-n` (`--namespace`) flag allows to control which namespace is used for finding and storing metadata `ConfigMaps`. If namespace is not explicitly specified your current namespace is selected from kube config (typically `~/.kube/config`).
`--app-namespace` flag allows to control which namespace is used for finding and storing metadata `ConfigMaps`. If namespace is not explicitly specified the app-wide namespace is used as specified by `-n` or `--namespace`); if `-n` is not specified your current namespace is selected from kube config (typically `~/.kube/config`).

There are currently two approaches to deciding which namespace to use for storing metadata `ConfigMaps`:

Expand All @@ -23,8 +23,8 @@ There are currently two approaches to deciding which namespace to use for storin

```bash
$ kubectl create ns apps
$ kapp deploy -n apps -f app1/config.yml
$ kapp deploy -n apps -f app2/config.yml
$ kapp deploy --app-namespace apps -f app1/config.yml
$ kapp deploy --app-namespace apps -f app2/config.yml
$ kapp ls -n apps
```

Expand Down
6 changes: 3 additions & 3 deletions site/content/kapp/docs/v0.60.x/state-namespace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ title: Namespace for State Storage

To show list of deployed applications (via `kapp ls`), kapp manages metadata `ConfigMap` for each saved application. Each metadata `ConfigMap` contains generated label used to label all application resources. Additionally kapp creates `ConfigMap` per each deploy to record deployment history (seen via `kapp app-change list -a app1`).

`-n` (`--namespace`) flag allows to control which namespace is used for finding and storing metadata `ConfigMaps`. If namespace is not explicitly specified your current namespace is selected from kube config (typically `~/.kube/config`).
`--app-namespace` flag allows to control which namespace is used for finding and storing metadata `ConfigMaps`. If namespace is not explicitly specified the app-wide namespace is used as specified by `-n` or `--namespace`); if `-n` is not specified your current namespace is selected from kube config (typically `~/.kube/config`).

There are currently two approaches to deciding which namespace to use for storing metadata `ConfigMaps`:

Expand All @@ -23,8 +23,8 @@ There are currently two approaches to deciding which namespace to use for storin

```bash
$ kubectl create ns apps
$ kapp deploy -n apps -f app1/config.yml
$ kapp deploy -n apps -f app2/config.yml
$ kapp deploy --app-namespace apps -f app1/config.yml
$ kapp deploy --app-namespace apps -f app2/config.yml
$ kapp ls -n apps
```

Expand Down
Loading