Extend Bundle Validation with bundle-validate Target #27
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.
Running the operator-sdk validation without any flags validates the bundle format and conforms it's contents to what is allowed in a
registry+v1
bundle (see ValidateBundleFormat and ValidateBundleContent functions).This PR (Similar PR to NMO's PR) extends our bundle validation to three more validators (from
operatorframework
suite):// the projects on OperatorHub.io.
--optional-values=k8s-version=K8S_VERSION
if provided) .The validation will error if it knows you are using a deprecated API and warn if it thinks there could be a deprecated API being used. Currently, operator-sdk v1.26.0, it supports only three deprecated Kubernetes API versions.
To see more options for using the bundle validation - Please run
operator-sdk bundle validate --list-optional