Skip to content
This repository was archived by the owner on Aug 12, 2025. It is now read-only.
This repository was archived by the owner on Aug 12, 2025. It is now read-only.

clusterctl init fails with "repository name must be canonical" #184

@luxas

Description

@luxas

What steps did you take and what happened:

I tried to get started with the Packet provider.
I downloaded the recent kind and clusterctl versions (v0.8.1 and v0.3.9, respectively), created a kind cluster, exported the Packet API key locally, and ran clusterctl init --infrastructure packet, which failed with error message:

Fetching providers
Error: failed to get provider components for the "packet" provider: failed to apply image overrides: failed to fix image for container manager in deployment cluster-api-provider-packet-controller-manager: couldn't parse image name: repository name must be canonical

The same goes for:

$ clusterctl config repositories
NAME          TYPE                     URL                                                                                          FILE
cluster-api   CoreProvider             https://github.com/kubernetes-sigs/cluster-api/releases/latest/                              core-components.yaml
kubeadm       BootstrapProvider        https://github.com/kubernetes-sigs/cluster-api/releases/latest/                              bootstrap-components.yaml
talos         BootstrapProvider        https://github.com/talos-systems/cluster-api-bootstrap-provider-talos/releases/latest/       bootstrap-components.yaml
kubeadm       ControlPlaneProvider     https://github.com/kubernetes-sigs/cluster-api/releases/latest/                              control-plane-components.yaml
talos         ControlPlaneProvider     https://github.com/talos-systems/cluster-api-control-plane-provider-talos/releases/latest/   control-plane-components.yaml
aws           InfrastructureProvider   https://github.com/kubernetes-sigs/cluster-api-provider-aws/releases/latest/                 infrastructure-components.yaml
azure         InfrastructureProvider   https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/latest/               infrastructure-components.yaml
metal3        InfrastructureProvider   https://github.com/metal3-io/cluster-api-provider-metal3/releases/latest/                    infrastructure-components.yaml
openstack     InfrastructureProvider   https://github.com/kubernetes-sigs/cluster-api-provider-openstack/releases/latest/           infrastructure-components.yaml
packet        InfrastructureProvider   https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/latest/              infrastructure-components.yaml
sidero        InfrastructureProvider   https://github.com/talos-systems/sidero/releases/latest/                                     infrastructure-components.yaml
vsphere       InfrastructureProvider   https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/releases/latest/             infrastructure-components.yaml
$ clusterctl config provider -i packet
Error: failed to apply image overrides: failed to fix image for container manager in deployment cluster-api-provider-packet-controller-manager: couldn't parse image name: repository name must be canonical

What did you expect to happen:

clusterctl init would succeed.

Anything else you would like to add:

I think that we need to release a new version with canonical image repository references, i.e. {,docker.io/}packethost/cluster-api-provider-packet:v0.3.2

Environment:

  • cluster-api-provider-packet version: v0.3.2
  • Kubernetes version: (use kubectl version): v1.18.2
  • OS (e.g. from /etc/os-release): Ubuntu 20.04 laptop

Thanks for looking into this.

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