Skip to content

Remote vs Local Assets #40

Answered by RothAndrew
mikhailswift asked this question in Q&A
Discussion options

You must be logged in to vote

local: Uses a native k3s capability that enables Kubernetes to use local image tarballs when pulling images instead of needing an image registry.

remote: loads the desired images into the private docker registry and repos into the private Gitea that Zarf creates when you initialize with the "Utility Cluster" feature turned on.

See the brand new Big Bang Core Example for an example of how remote: is being used to facilitate GitOps

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by mikhailswift
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants