Big Bang Component Extension #1094
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
runyontr
requested review from
mike-winberry,
Racer159,
Noxsios,
jeff-mccoy,
YrrepNoj,
Madeline-UX,
JasonvanBrackel,
RothAndrew and
a team
as code owners
…e and repo management Signed-off-by: Tom Runyon <tom@defenseunicorns.com>
Signed-off-by: Tom Runyon <tom@defenseunicorns.com>
separate flux and bb into different components allow for multiple bb components stop using custom deploy logic for bb
|
Progress:
Different PR?
|
I think we could add this backwards compatibility after getting it working for the current (or A version) so people can play with it and see how it works. Thoughts? |
|
I already have versions 1.44-1.49 done, about to be finished with 1.50 |
jeff-mccoy
previously approved these changes
Feb 27, 2023
YrrepNoj
suggested changes
Feb 27, 2023
Racer159
requested changes
Feb 27, 2023
Signed-off-by: Tom Runyon <tom@defenseunicorns.com>
Signed-off-by: Tom Runyon <tom@defenseunicorns.com>
YrrepNoj
approved these changes
Mar 3, 2023
Racer159
removed
the
needs-git-sign-off
jeff-mccoy
approved these changes
Mar 3, 2023
Noxsios
added a commit
that referenced
this pull request
Mar 8, 2023
Introduces the first Zarf Extension: `bigbang`. This PR establishes the pattern for create-time extensions and provides a simple/reliable way to deploy [Big Bang](https://p1.dso.mil/products/big-bang) using Zarf. In addition to collecting all the necessary assets, including Flux, the extension adds [component actions](https://docs.zarf.dev/docs/user-guide/component-actions) to verify the proper deployment of Big Bang Packages. In the event of a failure during deployment, details support data is also provided to the user to help expedite troubleshooting. ## Example usage: ```yaml components: - name: bigbang required: true extensions: bigbang: version: 1.53.0 valuesFiles: # Istio configs - config/ingress.yaml # Use Kyverno instead of Gatekeeper - config/kyverno.yaml ``` Conversation around #1093 The following things should be completed in future issues - [ ] Ensure Cleanup works consistently and smoothly when un-installing - [ ] Add labels to services for `zarf connect` - [ ] Perform upgrade test after Zarf CRD upgrade support + Big Bang 1.55 are released. --------- Signed-off-by: Tom Runyon <tom@defenseunicorns.com> Co-authored-by: corang <jordan@defenseunicorns.com> Co-authored-by: Megamind <882485+jeff-mccoy@users.noreply.github.com> Co-authored-by: Andy Roth <roth.andy@gmail.com> Co-authored-by: Jeff McCoy <code@jeffm.us> Co-authored-by: Wayne Starr <me@racer159.com> Co-authored-by: razzle <harry@razzle.cloud> Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com>
Noxsios
added a commit
that referenced
this pull request
Mar 8, 2023
Introduces the first Zarf Extension: `bigbang`. This PR establishes the pattern for create-time extensions and provides a simple/reliable way to deploy [Big Bang](https://p1.dso.mil/products/big-bang) using Zarf. In addition to collecting all the necessary assets, including Flux, the extension adds [component actions](https://docs.zarf.dev/docs/user-guide/component-actions) to verify the proper deployment of Big Bang Packages. In the event of a failure during deployment, details support data is also provided to the user to help expedite troubleshooting. ## Example usage: ```yaml components: - name: bigbang required: true extensions: bigbang: version: 1.53.0 valuesFiles: # Istio configs - config/ingress.yaml # Use Kyverno instead of Gatekeeper - config/kyverno.yaml ``` Conversation around #1093 The following things should be completed in future issues - [ ] Ensure Cleanup works consistently and smoothly when un-installing - [ ] Add labels to services for `zarf connect` - [ ] Perform upgrade test after Zarf CRD upgrade support + Big Bang 1.55 are released. --------- Signed-off-by: Tom Runyon <tom@defenseunicorns.com> Co-authored-by: corang <jordan@defenseunicorns.com> Co-authored-by: Megamind <882485+jeff-mccoy@users.noreply.github.com> Co-authored-by: Andy Roth <roth.andy@gmail.com> Co-authored-by: Jeff McCoy <code@jeffm.us> Co-authored-by: Wayne Starr <me@racer159.com> Co-authored-by: razzle <harry@razzle.cloud> Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com> Signed-off-by: razzle <harry@razzle.cloud>
Racer159
added a commit
that referenced
this pull request
Mar 8, 2023
Introduces the first Zarf Extension: `bigbang`. This PR establishes the pattern for create-time extensions and provides a simple/reliable way to deploy [Big Bang](https://p1.dso.mil/products/big-bang) using Zarf. In addition to collecting all the necessary assets, including Flux, the extension adds [component actions](https://docs.zarf.dev/docs/user-guide/component-actions) to verify the proper deployment of Big Bang Packages. In the event of a failure during deployment, details support data is also provided to the user to help expedite troubleshooting. ## Example usage: ```yaml components: - name: bigbang required: true extensions: bigbang: version: 1.53.0 valuesFiles: # Istio configs - config/ingress.yaml # Use Kyverno instead of Gatekeeper - config/kyverno.yaml ``` Conversation around #1093 The following things should be completed in future issues - [ ] Ensure Cleanup works consistently and smoothly when un-installing - [ ] Add labels to services for `zarf connect` - [ ] Perform upgrade test after Zarf CRD upgrade support + Big Bang 1.55 are released. --------- Signed-off-by: Tom Runyon <tom@defenseunicorns.com> Co-authored-by: corang <jordan@defenseunicorns.com> Co-authored-by: Megamind <882485+jeff-mccoy@users.noreply.github.com> Co-authored-by: Andy Roth <roth.andy@gmail.com> Co-authored-by: Jeff McCoy <code@jeffm.us> Co-authored-by: Wayne Starr <me@racer159.com> Co-authored-by: razzle <harry@razzle.cloud> Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com> Signed-off-by: Wayne Starr <me@racer159.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces the first Zarf Extension:
bigbang. This PR establishes the pattern for create-time extensions and provides a simple/reliable way to deploy Big Bang using Zarf. In addition to collecting all the necessary assets, including Flux, the extension adds component actions to verify the proper deployment of Big Bang Packages. In the event of a failure during deployment, details support data is also provided to the user to help expedite troubleshooting.Example usage:
Conversation around #1093
The following things should be completed in future issues
zarf connect