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 inaccessible clusters in a kube config preventing the arch check #1724

Merged
merged 2 commits into from
May 17, 2023

Conversation

Racer159
Copy link
Contributor

@Racer159 Racer159 commented May 17, 2023

Description

This fixes an issue where an inaccessible cluster in a kube config can prevent the arch check

Related Issue

Fixes #1723

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 May 17, 2023

Deploy Preview for zarf-docs ready!

Name Link
🔨 Latest commit 315774a
🔍 Latest deploy log https://app.netlify.com/sites/zarf-docs/deploys/6465320c3bb69a0008d7546b
😎 Deploy Preview https://deploy-preview-1724--zarf-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@Racer159 Racer159 enabled auto-merge (squash) May 17, 2023 19:59
@Racer159 Racer159 merged commit 82f73c7 into main May 17, 2023
@Racer159 Racer159 deleted the 1723-warn-on-inaccessible-cluster branch May 17, 2023 21:34
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.

Latest zarf version (0.26.3 as well) cannot deploy package without k8s present
2 participants