Enhancements to Operator Configuration and Installation Options #430
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.
Overview
Extended Configuration for Paladin/Besu Workloads
Added support for the following fields in the operator configuration to enhance flexibility when deploying Paladin/Besu workloads:
labels
annotations
envs
tolerations
affinity
nodeSelector
securityContext
New Installation Mode
Introduced a configurable installation mode, allowing the operator to be installed without the default CRs. This supports environments where only the operator setup is required.
Flux Integration Example
Added an example configuration for using Flux.