Got it
Thanks a lot!
Sent from my iPhone
On 14 janv. 2016, at 19:08, Clayton Coleman wrote:
You can set the image field to anything if you have a deployment trigger
pointing to an image stream. The deployment trigger overrides the value
set in the container when the first deployment is kicked
You can set the image field to anything if you have a deployment trigger
pointing to an image stream. The deployment trigger overrides the value
set in the container when the first deployment is kicked off
On Jan 14, 2016, at 3:39 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> w
On Thu, Jan 14, 2016 at 2:54 PM, Clayton Coleman
wrote:
> The name of the openshift registry? Just set the field to a
> placeholder in the deployment config.
>
Sorry Clayton, I'm not sure to follow you :(
Do you have an example I can checkout somewhere?
Thanks
Philippe
_
The name of the openshift registry? Just set the field to a
placeholder in the deployment config.
On Thu, Jan 14, 2016 at 2:45 PM, Philippe Lafoucrière
wrote:
> Also, I'm a little lost with containers specifications.
> What's the value of DeploymentConfig.spec.Containers[0].spec.image field?
> I
Also, I'm a little lost with containers specifications.
What's the value of DeploymentConfig.spec.Containers[0].spec.image field?
I don't know the name of the registry when creating the templates.
Thanks
___
users mailing list
users@lists.openshift.redhat
Hmm, I think I found it in
https://docs.openshift.com/enterprise/3.0/install_config/install/docker_registry.html#securing-the-registry
I was using [private-repo]:443/[someproject]/[somerepo] while
[private-repo]/[someproject]/[somerepo] (without the port) seems to work.
Last issue, in the doc:
"
Hmm, same error with "cluster-admin" role :(
To sum-up our current setup, we have a route pointing to docker-registry
service (with a valid certificate), and we're trying to push to
[private-repo]:443/[someproject]/[somerepo]
___
users mailing list
users
On Fri, Dec 11, 2015 at 11:59 AM, Clayton Coleman
wrote:
> The bonus with this method is that we are able to abuse openshift's use of
>> the special features they've built into the OSE registry. Some of the
>> nifty things we do with this, whether it's good/recommended or not:
>>
>>- We don'
