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

Fix a bug with registry push/pull on detected but invalid clusters #1930

Merged
merged 6 commits into from
Aug 1, 2023

Conversation

Racer159
Copy link
Contributor

Description

This fixes an issue with zarf tools registry where an invalid cluster (one that was not connectable or did not have state) could cause a failure.

Related Issue

Fixes #1929

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

@netlify
Copy link

netlify bot commented Jul 29, 2023

Deploy Preview for zarf-docs canceled.

Name Link
🔨 Latest commit 714590b
🔍 Latest deploy log https://app.netlify.com/sites/zarf-docs/deploys/64c97e091fc46c000872c205

@Racer159 Racer159 changed the title Fix the bug with registry push/pull on detected but invalid clusters Fix a bug with registry push/pull on detected but invalid clusters Jul 29, 2023
@Noxsios Noxsios enabled auto-merge (squash) August 1, 2023 21:50
@Noxsios Noxsios merged commit 5f4151f into main Aug 1, 2023
@Noxsios Noxsios deleted the 1929-zarf-tools-crane-invalid-kubeconfig branch August 1, 2023 22:22
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

Successfully merging this pull request may close these issues.

zarf tools registry pull - i/o time out error
3 participants