Skip to content
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

Registry no longer exists for byoh provider #894

Open
owenthomas17 opened this issue Jul 3, 2024 · 6 comments
Open

Registry no longer exists for byoh provider #894

owenthomas17 opened this issue Jul 3, 2024 · 6 comments

Comments

@owenthomas17
Copy link

owenthomas17 commented Jul 3, 2024

What steps did you take and what happened:
It looks like some point in the past 4/5 days, the byoh provider images are no longer served by projects.registry.vmware.com:

# Docker
$ docker pull projects.registry.vmware.com/cluster_api_provider_bringyourownhost/cluster-api-byoh-controller:v0.5.0
Error response from daemon: manifest for projects.registry.vmware.com/cluster_api_provider_bringyourownhost/cluster-api-byoh-controller:v0.5.0 not found: manifest unknown: The named manifest is not known to the registry.

# Kubectl 
Events:
  Type    Reason   Age                        From     Message
  ----    ------   ----                       ----     -------
  Normal  Pulling  14m (x1308 over 4d15h)     kubelet  Pulling image "projects.registry.vmware.com/cluster_api_provider_bringyourownhost/cluster-api-byoh-controller:v0.5.0"
  Normal  BackOff  4m45s (x29489 over 4d15h)  kubelet  Back-off pulling image "projects.registry.vmware.com/cluster_api_provider_bringyourownhost/cluster-api-byoh-controller:v0.5.0"


This issue implies there were some changes to the registry around that time. Please could you provide an alternative registry for the existing images?

What did you expect to happen:
For the docker pull to work.

Anything else you would like to add:
N/A

Environment:

N/A

@gjkim42
Copy link

gjkim42 commented Sep 3, 2024

@dharmjit @jamiemonserrate @shivi28

Hello contributors, could you take a look at this?

I guess the last commit to this project was 7 months ago.
Is this project in maintenance mode or deprecated?

If it is, it would be great to inform the status of the project to others.

Thank you.

@4everming
Copy link
Contributor

4everming commented Sep 3, 2024

@dharmjit @jamiemonserrate @shivi28

Hello contributors, could you take a look at this?

I guess the last commit to this project was 7 months ago. Is this project in maintenance mode or deprecated?

If it is, it would be great to inform the status of the project to others.

Thank you.

Try this?
https://projects.registry.vmware.com/ui/packages/docker:%2F%2Fharbor-projects-registry%2Ftkg%2Fcluster-api%2Fcluster-api-byoh-controller

@jamiemonserrate
Copy link
Contributor

Apologies for the delay in responding folks. But this project is no longer being maintained.

@tuxillo
Copy link

tuxillo commented Nov 16, 2024

Does anyone know if there are provisioners that are supported which provide the same functionality as this one?

@cellux
Copy link

cellux commented Nov 24, 2024

Until someone adopts the project (let's hope), you can easily build your own byoh-controller-manager image:

git clone https://github.com/vmware-tanzu/cluster-api-provider-bringyourownhost
cd cluster-api-provider-bringyourownhost
docker build -t example.com/cluster-api-byoh-controller:v0.5.0 .

Push the resulting image to a registry, update the image reference in your byoh-controller-manager deployment and it works again.

@tuxillo
Copy link

tuxillo commented Nov 24, 2024

What do you mean by adopt? Is there a process for adoption? I thought one would just fork it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants