OpenShift CLI morsels

After building a docker image, it is added to the Image Stream in OpenShift. It can be identified by a unique ID and/or a tag. Tags can be added to any existing Image Stream. Discovering information about tags After listing image streams, you can see a short list of tags. In my case the [crayon-69e785f0c6ba8027547654-i/]  image stream has image tagged as [crayon-69e785f0c6bb5003630749-i/] . [crayon-69e785f0c6bb7260751807/] You can retrieve information about all existing tags using oc describe [crayon-69e785f0c6bba564028527/] Tagging images New Image Stream can be created immediately based on the existing tag. Below you can see creation of [crayon-69e785f0c6bbc860448571-i/]  IS with [crayon-69e785f0c6bcf855724232-i/]  tag based on [crayon-69e785f0c6bd2338189605-i/]  image. [crayon-6...

Having a public repository is a great thing, but not always possible or useful. OpenShift supports git access using ssh private keys and password. Below you can find the few steps on how you can use basic authentication (more…)

The command and resource completion is built into oc client. You can generate it for bash and zsh. (more…)

Recently, when I tried to answer the question: Openshift: how to edit scc non-interactively? I learned about nice feature of [crayon-69e785f0c9068373809644-i/] . It allows to change single values in OpenShift objects. Patching the resources For this scenario, let's say we have a deployment config called paprika. Standard way to update it is to run [crayon-69e785f0c9078854080699-i/]  and change fields. That works only until it is not a repeatable task or something that needs to be done often. Changing single value Using [crayon-69e785f0c907b937265395-i/]  you can easily automate simple tasks. Setting the rolling update timeout using this approach looks like this: [crayon-69e785f0c907d607025189/] The patch is an array of objects with the following fields: op - one of the operation...

Usually I build images directly inside OpenShift. Sometimes it is useful to import an existing image into OpenShift's ImageStream. (more…)

The documentation is not the only place with information about OpenShift CLI. The tool itself contains a huge amount of data about the managed resources itself. Finding the managed resources A good starting point is to read output of [crayon-69e785f0cabd9925301390-i/] that returns description of used concept and types. These are not all of them, but the ones used during development. You will not find there details about [crayon-69e785f0cabea697086405-i/] or [crayon-69e785f0cabed935462045-i/] . For the listed types you can run [crayon-69e785f0cabef282349178-i/] Exploring type's details Armed with the knowledge of various types, further details can be displayed for it with[crayon-69e785f0cabf1723535861-i/] . The command prints our all the fields, their types and descriptions. [crayon...