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

Fix typo #215

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+8 −6
Open

Fix typo #215

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
c0f5c50
Fix typo
p-se Jan 31, 2025
d0fc32d
Fix typo, add type to code block
p-se Jan 31, 2025
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
7 changes: 4 additions & 3 deletions docs/oci-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This feature will allow users to choose an OCI registry as storage for bundle re

When using this feature the bundle resources are stored once, in the configured OCI registry, and Fleet won't be tied to possible `etcd` size limitations.

This may me interesting for users who need to store big `Bundles`, and could also be seen as the first step for an `OCIOps` feature in the future.
This may be interesting for users who need to store big `Bundles`, and could also be seen as the first step for an `OCIOps` feature in the future.

Once the OCI registry is enabled, Fleet will use it as the source for storing `Bundle` resources.
When Fleet can't access the OCI registry, it won't fall back to default `etcd` storage. Instead, it will log errors so they can be fixed.
Expand All @@ -22,15 +22,16 @@ When Fleet can't access the OCI registry, it won't fall back to default `etcd` s
OCI registry values should be configured as an extra section in the `GitRepo` yaml.

There are the fields involved:
```

```yaml
// when ociRegistry is defined Fleet will use oci registry as storage
ociRegistry:
// reference is the OCI registry url.
reference: "docker.io/your-user-here"
// secret name where the credentials for the OCI registry are.
// expects a generic secret with username and password keys set.
authSecretName: oci-secret
// basicHTTP allows Fleet to uses basic http connections to communicate
// basicHTTP allows Fleet to use basic http connections to communicate
// with the registry (defaults to false)
basicHTTP: false
// insecureSkipTLS allows connections to the OCI registry
Expand Down
7 changes: 4 additions & 3 deletions versioned_docs/version-0.11/oci-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This feature will allow users to choose an OCI registry as storage for bundle re

When using this feature the bundle resources are stored once, in the configured OCI registry, and Fleet won't be tied to possible `etcd` size limitations.

This may me interesting for users who need to store big `Bundles`, and could also be seen as the first step for an `OCIOps` feature in the future.
This may be interesting for users who need to store big `Bundles`, and could also be seen as the first step for an `OCIOps` feature in the future.

Once the OCI registry is enabled, Fleet will use it as the source for storing `Bundle` resources.
When Fleet can't access the OCI registry, it won't fall back to default `etcd` storage. Instead, it will log errors so they can be fixed.
Expand All @@ -22,15 +22,16 @@ When Fleet can't access the OCI registry, it won't fall back to default `etcd` s
OCI registry values should be configured as an extra section in the `GitRepo` yaml.

There are the fields involved:
```

```yaml
// when ociRegistry is defined Fleet will use oci registry as storage
ociRegistry:
// reference is the OCI registry url.
reference: "docker.io/your-user-here"
// secret name where the credentials for the OCI registry are.
// expects a generic secret with username and password keys set.
authSecretName: oci-secret
// basicHTTP allows Fleet to uses basic http connections to communicate
// basicHTTP allows Fleet to use basic http connections to communicate
// with the registry (defaults to false)
basicHTTP: false
// insecureSkipTLS allows connections to the OCI registry
Expand Down