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.

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

Clarify the sources usage on PolicyServer CRs #435

Merged
merged 2 commits into from
Aug 8, 2024
Merged
Changes from all commits
Commits
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
9 changes: 6 additions & 3 deletions docs/reference/sources_yaml.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,16 @@ doc-topic: [operator-manual, sources.yaml]
<link rel="canonical" href="https://docs.kubewarden.io/reference/sources_yaml"/>
</head>

## The `sources.yaml` file
You can tune the push-pull behavior of `kwctl` and `policy-server` binaries with the `--sources-path` argument,
for specifying the path to the `sources.yaml` file.

You can tune the push-pull behavior of `kwctl` and `policy-server` using the `sources.yaml` file.
To configure a PolicyServer CR, set its `spec.insecureSources` and `spec.sourceAuthorities` fields. The format
of these fields corresponds with the respective sections below.

The `--sources-path` argument to both tools specifies the file.
## The `sources.yaml` file

The command `kwctl` tries to load the `sources.yaml` file from these folders if the `--sources-path` argument is omitted:

- Linux: `$HOME/.config/kubewarden/sources.yaml`
- Mac: `$HOME/Library/Application Support/io.kubewarden.kubewarden/sources.yaml`
- Windows: `$HOME\AppData\Roaming\kubewarden\config\sources.yaml`
Expand Down
Loading