Bartosz Bierkowski - Low dose cloud

morsels

OpenShift CLI morsels: tagging images

OpenShift CLI morsels: tagging images

morsels, OpenShift, 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-616a940fc4dc9589005727-i/]  image stream has image tagged as [crayon-616a940fc4dd1110064243-i/] . [crayon-616a940fc4dd4803305405/] You can retrieve information about all existing tags using oc describe [crayon-616a940fc4dd6057505131/] Tagging images New Image Stream can be created immediately based on the existing tag. Below you can see creation of [crayon-616a940fc4dd9184737864-i/]  IS with [crayon-616a940fc4ddc953321572-i/]  tag based on [crayon-616a940fc4dde680459142-i/]  image. [crayon-6
OpenShift CLI morsels: updating objects non-interactively

OpenShift CLI morsels: updating objects non-interactively

morsels, OpenShift, OpenShift CLI morsels
Recently, when I tried to answer the question: Openshift: how to edit scc non-interactively? I learned about nice feature of [crayon-616a940fc5d7f365105333-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-616a940fc5d87626039386-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-616a940fc5d8a386866766-i/]  you can easily automate simple tasks. Setting the rolling update timeout using this approach looks like this: [crayon-616a940fc5d8d593110077/] The patch is an array of objects with the following fields: op - one of the operation
OpenShift CLI morsels: getting docs from oc client

OpenShift CLI morsels: getting docs from oc client

morsels, OpenShift, OpenShift CLI morsels
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-616a940fc6735584825302-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-616a940fc6756314493778-i/] or [crayon-616a940fc675a416276619-i/] . For the listed types you can run [crayon-616a940fc675c375780254-i/] Exploring type's details Armed with the knowledge of various types, further details can be displayed for it with[crayon-616a940fc676c017641637-i/] . The command prints our all the fields, their types and descriptions. [crayon...