(feat) Add OCI scheme support to RemoteURL#1851
Merged
Merged
Conversation
RemoteURL in PolicyRef now accepts oci:// URLs in addition to http:// and https://. When a URL starts with oci://, Sveltos pulls the OCI artifact from the registry on each reconciliation using the configured interval, computes a content hash, and redeploys if the content has changed. Identical to the existing HTTP polling behaviour. Authentication is controlled by the same secretRef field with the same Secret keys: - token — Bearer token (OCI RegistryToken) - username + password — basic auth - caFile — PEM-encoded CA certificate for TLS verification Content extraction handles two common OCI artifact layouts: a tar archive (the standard ORAS/Flux format), where .yaml, .yml, and .json files are extracted and concatenated; or a raw YAML/JSON blob where the bytes are used directly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RemoteURL in PolicyRef now accepts oci:// URLs in addition to http:// and https://.
When a URL starts with oci://, Sveltos pulls the OCI artifact from the registry on each reconciliation using the configured interval, computes a content hash, and redeploys if the content has changed. Identical to the existing HTTP polling behaviour.
Authentication is controlled by the same secretRef field with the same Secret keys:
Content extraction handles two common OCI artifact layouts: a tar archive (the standard ORAS/Flux format), where .yaml, .yml, and .json files are extracted and concatenated; or a raw YAML/JSON blob where the bytes are used directly.