You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is a rather complex problem. Right now when using OpenShift mode, we use S2I binary builds which use ImageStreams.
The problem is we can't refer to an image stream created in one namespace from another namespace. So we can't use CD Pipelines with kubernetesApply() or use mvn fabric8:deploy for a different namespace or use fabric8-arquillian system testing with image streams until we figure out some way to:
move images to different ImageStreams / images in other namespaces
update the DeploymentConfig / ReplicationController resources in each namespace to refer to the updated location of the image
One approach could be to just not use ImageStreams and stick with regular docker images which are labelled using the CD release number as we do for kubernetes.
Any ideas?
The text was updated successfully, but these errors were encountered:
incidentally they now mostly work on OpenShift in kubernetes mode; they just don't yet work for the new S2I binary builder and ImageStreams (i.e. openshift or auto mode)
this is a rather complex problem. Right now when using OpenShift mode, we use S2I binary builds which use ImageStreams.
The problem is we can't refer to an image stream created in one namespace from another namespace. So we can't use CD Pipelines with
kubernetesApply()
or usemvn fabric8:deploy
for a different namespace or use fabric8-arquillian system testing with image streams until we figure out some way to:One approach could be to just not use ImageStreams and stick with regular docker images which are labelled using the CD release number as we do for kubernetes.
Any ideas?
The text was updated successfully, but these errors were encountered: