-
Notifications
You must be signed in to change notification settings - Fork 284
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
Allow user to generate support bundle in Airgap environment #8683
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8683 +/- ##
==========================================
- Coverage 73.53% 73.52% -0.01%
==========================================
Files 578 578
Lines 36557 36561 +4
==========================================
+ Hits 26882 26883 +1
- Misses 7955 7958 +3
Partials 1720 1720 ☔ View full report in Codecov by Sentry. |
Currently eks-anywhere cannot generate support bundle in Airgap environment because eks-a needs to read bundle manifest from remote URL. This PR fixed the issue by allowing user to specify path of local bundle manifest file so that eks-a does not need to read it from remote URL.
e89fc2c
to
514322d
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jacobweinstock The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick release-0.20 |
@2ez4szliu: new pull request created: #8786 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
*Issue #, if available: 5783
*Description of changes:
Currently eks-anywhere cannot generate support bundle in Airgap environment because eks-a needs to read bundle manifest from remote URL.
This PR fixed the issue by allowing user to specify path of local bundle manifest file so that eks-a does not need to read it from remote URL.
*Testing (if applicable):
Run eksctl to generate support bundle with bundle-manifest flag specified in the command, bundle can be generated successfully.
eksctl-anywhere generate support-bundle -f eks-a-cluster.yaml --bundle-manifest eks-anywhere-downloads/bundle-release.yaml
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.