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

CheckRegistryImagesJob: Is this working? #1866

Closed
jefflill opened this issue Oct 18, 2023 · 1 comment
Closed

CheckRegistryImagesJob: Is this working? #1866

jefflill opened this issue Oct 18, 2023 · 1 comment
Assignees
Labels
bug Identifies a bug or other failure cluster-operators Related to one of our cluster operators neon-kube Related to our Kubernetes distribution

Comments

@jefflill
Copy link
Collaborator

@marcusbooyah: I'm not entirely sure this job is actually working.

I'm running the neon-cluster-operator on my workstation and have this job scheduled to run every 5 minutes and when it runs, I'm seeing NeonClusterOperator.Harbor.ApiException exceptions thrown saying that the container images don't exist.

This will happen the first time this job is run, but afterward that, the images should have been loaded into Harbor and we shouldn't see these errors any more, right?

@jefflill jefflill added neon-kube Related to our Kubernetes distribution bug Identifies a bug or other failure cluster-operators Related to one of our cluster operators labels Oct 18, 2023
@marcusbooyah
Copy link
Member

This is normal - the job checks to see if the image is in Harbor, and if not creates a NodeTask to push it. If the image isn't in Harbor, we get a 404.

The issue was that the Node Agent wasn't reconciling the NodeTasks but it's working now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies a bug or other failure cluster-operators Related to one of our cluster operators neon-kube Related to our Kubernetes distribution
Projects
None yet
Development

No branches or pull requests

2 participants