Closed phantomjinx closed 4 years ago
That’s a good start, but we need to restore the param IMAGESTREAM_NAMESPACE and corresponding imagestreams as well. On the eval cluster, the images are imported manually and referenced from a different namespace.
The images are definitely tagged with the image namespace, eg. fuse-ignite, after the perl import script is executed. However, that can be encompassed by setting the SYNDESIS_REGISTRY parameter to '
We can get some of the ImageStreams back using the operator install forge
command (obviously can add them manually) but I note the syndesis-db one has disappeared from the operator code entirely.
So I think perhaps a collaborative coding session going through a diff of 1.8 and 1.9 might be useful to address some of these differences.
Superseded by #231
That’s a good start, but we need to restore the param IMAGESTREAM_NAMESPACE and corresponding imagestreams as well. On the eval cluster, the images are imported manually and referenced from a different namespace.