Conversation
The release workflow builds the production OLM bundle and catalog images. It attaches the CatalogSource manifest to the GitHub release, and then it writes the bundle to the artifacts repository. The operator deployment gets a RELATED_IMAGE_SIDECAR variable. operator-sdk changes this variable to a digest, and it writes the image into the relatedImages field of the ClusterServiceVersion (CSV). Four new patches correct the bundle. Two patches give the correct image to the CSV annotation and to the sample server, because both files had a fixed image that no registry holds. The third patch adds an olm.skipRange to the CSV, so a catalog that carries a single bundle can still offer an upgrade from any earlier release. The fourth patch removes the example secret, because OLM makes a secret for each secret in a bundle; the CSV description now lists the secrets a Server needs, since the bundle no longer ships them and the CRD requires the fields that name them. Digest resolution covers every image in the CSV, the operand included, so the olm job depends on the core job as well. That job is skipped on a pull request that only touches the operator, so the bundle is built against mutable tags there rather than making every such pull request pay for a core build. Assisted-by: Claude Signed-off-by: John Long <john.long@enterprisedb.com>
Signed-off-by: John Long <john.long@enterprisedb.com>
Aspell splits the bare "operator-sdk" on the hyphen and rejects the lowercase "sdk". The spellcheck pipeline ignores code spans, and every other identifier in the paragraph is already backticked. Assisted-by: Claude Signed-off-by: John Long <john.long@enterprisedb.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The release workflow builds the production OLM bundle and catalog images. It attaches the CatalogSource manifest to the GitHub release, and then it writes the bundle to the artifacts repository.
The operator deployment gets a RELATED_IMAGE_SIDECAR variable. operator-sdk changes this variable to a digest, and it writes the image into the relatedImages field of the ClusterServiceVersion (CSV).
Four new patches correct the bundle. Two patches give the correct image to the CSV annotation and to the sample server, because both files had a fixed image that no registry holds. The third patch adds an olm.skipRange to the CSV, so a catalog that carries a single bundle can still offer an upgrade from any earlier release. The fourth patch removes the example secret, because OLM makes a secret for each secret in a bundle; the CSV description now lists the secrets a Server needs, since the bundle no longer ships them and the CRD requires the fields that name them.
Digest resolution covers every image in the CSV, the operand included, so the olm job depends on the core job as well. That job is skipped on a pull request that only touches the operator, so the bundle is built against mutable tags there rather than making every such pull request pay for a core build.
Assisted-by: Claude