-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update readme #287
base: master
Are you sure you want to change the base?
Update readme #287
Conversation
Signed-off-by: Logan Blyth <[email protected]>
Signed-off-by: Logan Blyth <[email protected]>
|
||
**NOTE:** Run `make help` for more information on all potential `make` targets | ||
* (TODO) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
KUBECONFIG env var set to target cluster that have access to the registry you push to (or you can use registry on control node in the upstream mode and push directly to it, in case of VLAB the registry port on control node is forwarded from the host as well) and run oras oci_repo="..." push patch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
making a note from our conversation - pushing to the registry on the control node has limited utility. It is better in most cases to use upstream mode.
127.0.0.1:30000` flag and argument to `hhfab init` along with other flags. | ||
From there continue on with the `hhfab` commands. To get vlab running with | ||
local changes: | ||
* `hhfab init --dev --registry-repo 127.0.0.1` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When defining localhost address it ends up in error when creating a control node VM as the zot instance inside the VM is not able to reach the upstream zot
So far I've only managed to deploy a control VM using a zot with a fully valid SSL cert
"storage": { | ||
"rootDirectory": "/tmp/zot" | ||
}, | ||
"http": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is plain HTTP valid for push/pull forl all of the operations in the justfile or other places where the registry is required?
as OCI compliant artifacts. | ||
|
||
|
||
## Local Build Instructions | ||
|
||
### Prerequisites |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing just (requires 1.38.0?)
|
||
**Deploy the Manager to the cluster with the image specified by `IMG`:** | ||
[Zot installation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why the _localreg just target cannot be used here?
127.0.0.1:30000` flag and argument to `hhfab init` along with other flags. | ||
From there continue on with the `hhfab` commands. To get vlab running with | ||
local changes: | ||
* `hhfab init --dev --registry-repo 127.0.0.1` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing :30000
No description provided.