Allow the ability to sign images the formats of ImageStreamTag, ImageStreamImage, and DockerImage and include the ability to add pull secrets for remote registries.
Reproduce Tests:
Follow the Workflow Openshift example in the README to test the ImageStreamTag repository type.
Make sure to use the following command when testing as described in the development.md document instead of applying the operator.yaml file as described in the README for the OpenShift Workflow examle.
$ operator-sdk run --local --namespace="image-management"
For the ImageStreamImage I grabbed the SHA256 digest from the DockerImageReference attribute in the ImageStreamTag that is created in the dotnet-example Workflow in the README.
NOTE: The E2E image now points by default to the signing image built by this repo. It now can run a test for both ImageStreamTag and ContainerRepository with tag.
To run the E2E tests you'll need to make two modifications since,
Allow the ability to sign images the formats of ImageStreamTag, ImageStreamImage, and DockerImage and include the ability to add pull secrets for remote registries.
Reproduce Tests:
ImageStreamTag
repository type. Make sure to use the following command when testing as described in the development.md document instead of applying the operator.yaml file as described in the README for the OpenShift Workflow examle.ImageStreamImage
I grabbed the SHA256 digest from the DockerImageReference attribute in the ImageStreamTag that is created in the dotnet-example Workflow in the README.ContainerRepository
and
For a private repository I made one of my quay.io images private and added a pull secret
NOTE: The E2E image now points by default to the signing image built by this repo. It now can run a test for both
ImageStreamTag
andContainerRepository
with tag. To run the E2E tests you'll need to make two modifications since,and
Both pointing to the latest versions of the signer and operator.