Skip to content
This repository was archived by the owner on Mar 31, 2023. It is now read-only.
This repository was archived by the owner on Mar 31, 2023. It is now read-only.

Better documentation on private registry usage #140

@kingdonb

Description

@kingdonb

There is an environments/ in wksctl repo which explains how to start a registry and copy the required images for wks into it, but it is not clear from README.md or script source what else if anything is needed to make the K8s API able to pull from that registry, if special handling is needed for pods generally to start from insecure registries (I know this is a configuration option in Docker insecure-registries, maybe it just works by default in Kubernetes... not sure?), guidance about how to install WKS from your image source, or other basic prerequisites.

I have some private builds that I would like to push to some private registry and install to WKS, is exactly what specific use case has driven me to report this as an issue... the source code is private and unpublished, so the images should be too. Maybe with something like a private CI / docker builder can be incorporated as a separate use case, private builds on private registry? (I was planning on building them locally and pushing them to the private registry, I am using WKS on footloose.)

I know that some flags were added to pass in the controller image, also saw dependencies.toml in the latest merges for alpha. Other than perhaps in wks-controller.yaml, is there more configuration needed to be performed before WKSctl can self-bootstrap from a private registry?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions