You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But no support for port, basic auth, CA cert, or base path. So we support public custom image registries, but not private ones. Refer to palette-cli for sample code pertaining to base path.
Requirements
Implement prompts for scenario 3. Ensure that the kind configuration is populated correctly - including base path.
Proposed top-level flow:
Configure Hauler for air-gapped installation?
If yes, scenario 2
If no, continue
Use a private image registry?
If yes, scenario 3
If no, continue
Using a public image registry
Prompt for registry host, with quay.io/validator-labs as the default
The text was updated successfully, but these errors were encountered:
## Issue
#81
## Description
This PR adds support for cutom image registries. Under the hood, the
`Registry` struct will use Hauler if its `IsAirgapped` prop is set to
true.
Tested by configuring artifacts in a harbor registry as shown below and
installing validator with `InsecureSkipTLSVerify` set to `true` (and
passing in the CA cert) and `false`
<img width="1036" alt="Screenshot 2024-07-22 at 1 40 21 PM"
src="https://github.com/user-attachments/assets/05f1646b-eeb7-46f0-86ee-c6440024b11c">
Summary
Context
There are three image registry scenarios:
quay.io
, charts from GitHubRequirements
Implement prompts for scenario 3. Ensure that the kind configuration is populated correctly - including base path.
Proposed top-level flow:
quay.io/validator-labs
as the defaultThe text was updated successfully, but these errors were encountered: