{"id":49170,"date":"2025-06-21T15:35:48","date_gmt":"2025-06-21T15:35:48","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=49170"},"modified":"2026-02-21T07:29:31","modified_gmt":"2026-02-21T07:29:31","slug":"what-is-imagestreams-step-by-step-tutorials","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-imagestreams-step-by-step-tutorials\/","title":{"rendered":"Openshift: What is ImageStreams & Step by Step Tutorials"},"content":{"rendered":"\n

\ud83d\udc49 What ImageStream really gives you<\/strong>
\ud83d\udc49 Why OpenShift uses it<\/strong>
\ud83d\udc49 How it\u2019s better (in some cases) than just pulling a normal image<\/strong><\/p>\n\n\n\n

\n\n\n\n

\ud83e\udde0 First, imagine two situations:<\/h1>\n\n\n\n

\ud83d\udd35 Situation 1: Without ImageStream<\/strong> (Normal Kubernetes)<\/h2>\n\n\n\n
    \n
  • You deploy an app with a direct Docker image URL: image: nginx:latest<\/code><\/li>\n\n\n\n
  • Kubernetes will never track<\/strong> changes in nginx:latest<\/code>.<\/li>\n\n\n\n
  • If someone updates the latest<\/code> image, your running pods stay the same<\/strong> unless you manually trigger<\/strong> an update (like delete the pod, rollout new version).<\/li>\n\n\n\n
  • There\u2019s no history<\/strong>, no auto-notifications<\/strong>, and no internal record<\/strong> of what “latest” pointed to when you deployed it.<\/li>\n\n\n\n
  • No control, no tracking, no automatic trigger.<\/li>\n<\/ul>\n\n\n\n

    \u2705 Simple but very dumb<\/strong> way.
    \u2705 Works when you fully control your CI\/CD pipeline.<\/p>\n\n\n\n

    \n\n\n\n

    \ud83d\udfe0 Situation 2: With OpenShift ImageStream<\/strong><\/h2>\n\n\n\n
      \n
    • Instead of pulling images directly, OpenShift tracks them through an ImageStream.<\/li>\n\n\n\n
    • When nginx:latest<\/code> is updated on DockerHub<\/strong>, OpenShift automatically<\/strong> imports the new image metadata into ImageStream.<\/li>\n\n\n\n
    • You can:\n
        \n
      • Automatically redeploy<\/strong> apps when the image changes (without touching anything).<\/li>\n\n\n\n
      • View history<\/strong> of all previous images that ever existed for that tag.<\/li>\n\n\n\n
      • Tag images manually<\/strong> between environments (example: promote dev image \u2192 staging \u2192 prod by just changing a tag).<\/li>\n\n\n\n
      • Control access<\/strong> to images inside OpenShift’s internal registry.<\/li>\n\n\n\n
      • Pin exact images<\/strong> by digest to avoid accidental breakage.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

        \u2705 Smart, controlled, observable, CI\/CD friendly.<\/p>\n\n\n\n

        \n\n\n\n

        \u2728 So, in simple words:<\/h1>\n\n\n\n
        Normal Images (Kubernetes)<\/th>ImageStream (OpenShift)<\/th><\/tr><\/thead>
        Pull and forget. No update tracking.<\/td>Tracks external and internal images in OpenShift.<\/td><\/tr>
        No automatic redeploy when images change.<\/td>Can auto-trigger deployment when new image arrives.<\/td><\/tr>
        No history of what version you pulled.<\/td>Maintains history of images for every tag.<\/td><\/tr>
        Cannot promote images safely between environments.<\/td>Can tag\/promote images easily between dev \u2192 staging \u2192 prod.<\/td><\/tr>
        No OpenShift access control for images.<\/td>Full OpenShift permission control for pull, tag, promote.<\/td><\/tr>
        You manage everything outside cluster.<\/td>OpenShift manages image lifecycle inside cluster.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n

        \ud83d\udcf8 Example to make it even more practical<\/h1>\n\n\n\n

        \u2705 Without ImageStream:<\/strong><\/p>\n\n\n\n

          \n
        • You push a new app build to DockerHub (myapp:latest<\/code> updated).<\/li>\n\n\n\n
        • Your Kubernetes app still uses old container<\/strong> unless you manually trigger a deployment.<\/li>\n<\/ul>\n\n\n\n

          \u2705 With ImageStream:<\/strong><\/p>\n\n\n\n

            \n
          • You push a new app build to DockerHub (myapp:latest<\/code> updated).<\/li>\n\n\n\n
          • OpenShift automatically imports<\/strong> the new version into ImageStream.<\/li>\n\n\n\n
          • If a Deployment (with image trigger) is linked to that ImageStream:\n
              \n
            • \u2794 OpenShift triggers redeployment automatically!<\/strong><\/li>\n\n\n\n
            • \u2794 Zero manual work.<\/li>\n\n\n\n
            • \u2794 New app version is live safely.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              Final Summary (Easy Language)<\/h1>\n\n\n\n
              \n

              Normal images<\/strong> are like pulling files from the internet manually every time.
              ImageStreams<\/strong> are like having a smart librarian inside your OpenShift cluster who:<\/p>\n\n\n\n

                \n
              • Tracks when your images change.<\/li>\n\n\n\n
              • Keeps history of all versions.<\/li>\n\n\n\n
              • Alerts your applications and triggers updates.<\/li>\n\n\n\n
              • Controls who can pull what.<\/li>\n<\/ul>\n<\/blockquote>\n\n\n\n
                \n\n\n\n

                Practical Advantages of ImageStreams<\/h1>\n\n\n\n
                Benefit<\/th>Why it matters<\/th><\/tr><\/thead>
                Auto-updates<\/td>No need to manually redeploy when a new version is available.<\/td><\/tr>
                History tracking<\/td>Rollback to any old image version easily.<\/td><\/tr>
                Environment promotion<\/td>Promote builds from Dev \u2192 QA \u2192 Prod by tagging.<\/td><\/tr>
                Pull secrets and control<\/td>Manage access securely for private registries.<\/td><\/tr>
                Cluster registry integration<\/td>OpenShift can manage images internally without external dependency.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                \n\n\n\n

                Real Example<\/h1>\n\n\n\n

                If you\u2019re running CI\/CD pipelines in OpenShift (Jenkins, Tekton, GitOps ArgoCD):<\/p>\n\n\n\n

                  \n
                • Build finishes \u2794 ImageStream updated \u2794 New Deployment triggered \u2794 App upgraded automatically.<\/li>\n<\/ul>\n\n\n\n

                  \u2705 No downtime.
                  \u2705 No manual intervention.
                  \u2705 Full visibility on which image you are using.<\/p>\n\n\n\n

                  \n\n\n\n

                  Very Short Answer<\/h1>\n\n\n\n
                  If you want<\/th>Use<\/th><\/tr><\/thead>
                  Simple “set and forget” deploys<\/td>Normal Kubernetes image reference.<\/td><\/tr>
                  Smart, auto-tracked, secure, history-managed image lifecycle<\/td>OpenShift ImageStreams.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n

                  \ud83e\udde0 What Are We Building?<\/h1>\n\n\n\n

                  You have three projects (namespaces):<\/p>\n\n\n\n

                  Environment<\/th>OpenShift Project<\/th><\/tr><\/thead>
                  Development (Dev)<\/td>app-dev<\/code><\/td><\/tr>
                  Staging<\/td>app-staging<\/code><\/td><\/tr>
                  Production<\/td>app-prod<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                  We will:<\/p>\n\n\n\n

                    \n
                  • Build or Import an Image into app-dev<\/code><\/li>\n\n\n\n
                  • Promote (copy) the image to app-staging<\/code><\/li>\n\n\n\n
                  • Finally promote it to app-prod<\/code><\/li>\n\n\n\n
                  • All using ImageStreams<\/strong> without rebuilding the app again<\/li>\n<\/ul>\n\n\n\n

                    \u2705 No re-building needed!
                    \u2705 Full traceability!
                    \u2705 Full security control!<\/p>\n\n\n\n

                    \n\n\n\n

                    \ud83d\udee0 Prerequisites:<\/h1>\n\n\n\n
                      \n
                    • OpenShift CLI (oc<\/code>) installed<\/li>\n\n\n\n
                    • Access to an OpenShift 4.x+ cluster<\/li>\n\n\n\n
                    • admin<\/code> or sufficient permissions on projects<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n

                      \ud83d\ude80 Step-by-Step Tutorial<\/h1>\n\n\n\n
                      \n\n\n\n

                      1\ufe0f\u20e3 Create Three OpenShift Projects<\/h2>\n\n\n
                      oc new<\/span>-project app-dev\noc new<\/span>-project app-staging\noc new<\/span>-project app-prod\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      2\ufe0f\u20e3 Create ImageStreams in Each Project<\/h2>\n\n\n\n
                      Create an ImageStream<\/strong> named myapp<\/code> in each project.<\/p>\n\n\n
                      # myapp-imagestream.yaml<\/span>\napiVersion: image.openshift.io\/v1\nkind: ImageStream\nmetadata:\n  name: myapp\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Apply in all three projects:<\/p>\n\n\n
                      oc<\/span> project<\/span> app-dev<\/span>\noc<\/span> apply<\/span> -f<\/span> myapp-imagestream<\/span>.yaml<\/span>\n\noc<\/span> project<\/span> app-staging<\/span>\noc<\/span> apply<\/span> -f<\/span> myapp-imagestream<\/span>.yaml<\/span>\n\noc<\/span> project<\/span> app-prod<\/span>\noc<\/span> apply<\/span> -f<\/span> myapp-imagestream<\/span>.yaml<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \u2705 Now, each project has an empty myapp<\/code> ImageStream.<\/p>\n\n\n\n
                      \n\n\n\n
                      3\ufe0f\u20e3 Import or Build Image into Dev (First Deployment)<\/h2>\n\n\n\n
                      For simplicity, let’s just import a public image (you could also BuildConfig if needed).<\/p>\n\n\n
                      oc project app-dev\n\noc import<\/span>-image myapp:latest --from<\/span>=nginx:latest --confirm\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \u2705 Now, the app-dev<\/code> project myapp:latest<\/code> points to the latest nginx image!<\/p>\n\n\n\n
                      You can check:<\/p>\n\n\n
                      oc describe is myapp\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      4\ufe0f\u20e3 Create Deployment that Uses ImageStream (optional but recommended)<\/h2>\n\n\n\n
                      In Dev, create a Deployment that uses the ImageStream:<\/p>\n\n\n
                      # myapp-deployment.yaml<\/span>\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n  name: myapp-deployment\nspec:\n  replicas: 1<\/span>\n  selector:\n    matchLabels:\n      app: myapp\n  template:\n    metadata:\n      labels:\n        app: myapp\n    spec:\n      containers:\n      - name: myapp\n        image: image-registry.openshift-image-registry.svc:5000<\/span>\/app-dev\/myapp:latest\n        ports:\n        - containerPort: 80<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Apply:<\/p>\n\n\n
                      oc<\/span> apply<\/span> -f<\/span> myapp-deployment<\/span>.yaml<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \u2705 Dev environment is now running your image!<\/p>\n\n\n\n
                      \n\n\n\n
                      5\ufe0f\u20e3 Promote Image from Dev \u2794 Staging<\/strong><\/h2>\n\n\n\n
                      Now the magic: Tagging<\/strong> from one project’s ImageStream to another project\u2019s ImageStream.<\/p>\n\n\n
                      oc tag app-dev\/myapp:latest app-staging\/myapp:latest\n<\/code><\/span><\/pre>\n\n\n
                      \u2705 This command copies the image reference<\/strong> into app-staging<\/code>‘s ImageStream.<\/p>\n\n\n\n
                      Important:<\/strong><\/p>\n\n\n\n
                        \n
                      • No rebuild.<\/li>\n\n\n\n
                      • No re-pulling from DockerHub.<\/li>\n\n\n\n
                      • Full OpenShift internal secured movement.<\/li>\n<\/ul>\n\n\n\n
                        You can verify:<\/p>\n\n\n
                        oc project app-staging\noc describe is myapp\n<\/code><\/span><\/pre>\n\n\n
                        You will see that it points to the image from Dev.<\/p>\n\n\n\n
                        \n\n\n\n
                        6\ufe0f\u20e3 Deploy in Staging<\/h2>\n\n\n\n
                        Create a Deployment in app-staging<\/code>, pointing to:<\/p>\n\n\n
                        image<\/span>: image-registry.openshift-image-registry.svc:5000\/app-staging\/myapp:latest\n<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
                        Now staging runs the exact same image!<\/p>\n\n\n\n
                        \n\n\n\n
                        7\ufe0f\u20e3 Promote Image from Staging \u2794 Production<\/h2>\n\n\n\n
                        Same simple command:<\/p>\n\n\n
                        oc tag app-staging\/myapp:latest app-prod\/myapp:latest\n<\/code><\/span><\/pre>\n\n\n
                        \u2705 Now your Production ImageStream is updated with the exact tested image.<\/p>\n\n\n\n
                        Create a Deployment in app-prod<\/code> using:<\/p>\n\n\n
                        image<\/span>: image-registry.openshift-image-registry.svc:5000\/app-prod\/myapp:latest\n<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
                        \u2705 Production environment runs only after successful promotion from staging!<\/p>\n\n\n\n
                        \n\n\n\n
                        \ud83d\udd25 Auto-Promotion Pipeline Idea (Optional)<\/h1>\n\n\n\n
                        You can fully automate this using Tekton Pipelines<\/strong>, Jenkins<\/strong>, GitHub Actions<\/strong>, or GitOps (ArgoCD)<\/strong>:<\/p>\n\n\n\n
                          \n
                        • After tests pass in Dev \u2794 automatically tag to Staging.<\/li>\n\n\n\n
                        • After staging approval \u2794 automatically tag to Production.<\/li>\n<\/ul>\n\n\n\n
                          \u2705 Fully secure.
                          \u2705 CI\/CD friendly.
                          \u2705 Traceable images across all stages.<\/p>\n\n\n\n
                          \n\n\n\n
                          \ud83c\udfc6 Final Architecture Diagram<\/h1>\n\n\n
                          DockerHub or Build --> app-dev\/myapp:latest\n                              |\n                       oc tag\n                              \u2193\n                     app-staging\/myapp:latest\n                              |\n                       oc tag\n                              \u2193\n                      app-prod\/myapp:latest\n<\/code><\/span><\/pre>\n\n\n
                          Each environment runs exactly the promoted image, NOT a rebuilt one. \ud83d\ude80<\/p>\n\n\n\n
                          \n\n\n\n
                          \ud83d\udccb Quick Commands Cheat Sheet<\/h1>\n\n\n\n
                          Command<\/th>Purpose<\/th><\/tr><\/thead>
                          oc import-image myapp:latest --from=<external-image> --confirm<\/code><\/td>Import image from external registry<\/td><\/tr>
                          oc tag app-dev\/myapp:latest app-staging\/myapp:latest<\/code><\/td>Promote image from Dev to Staging<\/td><\/tr>
                          oc tag app-staging\/myapp:latest app-prod\/myapp:latest<\/code><\/td>Promote image from Staging to Prod<\/td><\/tr>
                          oc describe is myapp<\/code><\/td>View ImageStream details<\/td><\/tr>
                          oc get istag<\/code><\/td>List image tags<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          \n\n\n\n
                          \ud83c\udfaf Real-World Benefits of This Method<\/h1>\n\n\n\n
                          Benefit<\/th>Why It Matters<\/th><\/tr><\/thead>
                          No Rebuilding<\/td>Promotes the same built image \u2014 ensures consistency<\/td><\/tr>
                          Fast and Secure<\/td>No need to pull externally again \u2014 internal registry handles it<\/td><\/tr>
                          Full Traceability<\/td>You can always check where an image came from<\/td><\/tr>
                          Automation Friendly<\/td>Easily integrate with pipelines and GitOps<\/td><\/tr>
                          Safe Rollbacks<\/td>Previous tags\/history available if you want to revert<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          \n\n\n\n
                          \ud83d\ude80 Conclusion<\/h1>\n\n\n\n
                          \u2705 ImageStreams<\/strong> make Dev \u2794 Staging \u2794 Prod promotions super clean and safe!
                          \u2705 Tagging<\/strong> avoids risks of “it works on my machine but fails on prod” issues.
                          \u2705 Production-ready<\/strong> method in OpenShift CI\/CD workflows!<\/p>\n\n\n\n
                          \n\n\n\n
                          Lab with Existing <\/h1>\n\n\n\n
                          Here’s a short and clear tutorial<\/strong> on how to check and deploy ImageStreams in OpenShift<\/strong>, using the example where you added httpd<\/code> via the Developer Catalog UI<\/strong> and then used oc<\/code> commands to deploy and expose it.<\/p>\n\n\n\n
                          \"\"<\/figure>\n\n\n\n
                          \n\n\n\n
                          Deploy ImageStreams in OpenShift (ARO)<\/h2>\n\n\n\n
                          \u2705 Step 1: Add ImageStream via Developer Catalog (UI)<\/h3>\n\n\n\n
                            \n
                          • In OpenShift Web Console:\n
                              \n
                            • Go to Developer \u2192 +Add \u2192 Container Image<\/strong><\/li>\n\n\n\n
                            • Search for httpd<\/code><\/strong> and add it<\/li>\n\n\n\n
                            • This will create an ImageStream<\/strong> but not<\/strong> a running application<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n
                              \u2705 Step 2: Check What Was Created<\/h3>\n\n\n\n
                              Use the CLI:<\/p>\n\n\n
                              oc get<\/span> all -n test2\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                              \n
                              You\u2019ll see only:<\/p>\n<\/blockquote>\n\n\n
                              imagestream.image.openshift.io\/httpd\n<\/code><\/span><\/pre>\n\n\n
                              \n\n\n\n
                              \u2705 Step 3: Deploy an App Using the ImageStream<\/h3>\n\n\n\n
                              To deploy a pod from the ImageStream you created:<\/p>\n\n\n
                              oc new<\/span>-app httpd -n test2\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                              This automatically creates:<\/p>\n\n\n\n
                                \n
                              • DeploymentConfig<\/li>\n\n\n\n
                              • Pod<\/li>\n\n\n\n
                              • Service<\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n
                                \u2705 Step 4: Verify Deployment<\/h3>\n\n\n
                                oc get<\/span> all -n test2\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                You\u2019ll now see:<\/p>\n\n\n\n
                                  \n
                                • deploymentconfig.apps.openshift.io\/httpd<\/code><\/li>\n\n\n\n
                                • pod\/httpd-xxxxx<\/code><\/li>\n\n\n\n
                                • svc\/httpd<\/code><\/li>\n<\/ul>\n\n\n\n
                                  \n\n\n\n
                                  \u2705 Step 5: Expose the Service to Create a Public Route<\/h3>\n\n\n
                                  oc expose svc\/httpd -n test2\n<\/code><\/span><\/pre>\n\n\n
                                  \n\n\n\n
                                  \u2705 Step 6: Get the Route URL<\/h3>\n\n\n
                                  oc get<\/span> route httpd -n test2\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                  Open the displayed URL in a browser to see the httpd<\/code> default page.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  \ud83e\uddea Command History You Used<\/h3>\n\n\n
                                  512<\/span>  oc get all -n test2\n513<\/span>  oc new<\/span>-app jenkins              # (unrelated, probably test)<\/span>\n514<\/span>  oc new<\/span>-app httpd -n test2       # \u2705 deploy httpd app<\/span>\n515<\/span>  oc get all -n test2\n516<\/span>  oc expose svc\/httpd -n test2    # \u2705 expose the service<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                                  \n\n\n\n
                                  \u2705 Summary<\/h2>\n\n\n\n
                                  Task<\/th>Command<\/th><\/tr><\/thead>
                                  Check what exists<\/td>oc get all -n test2<\/code><\/td><\/tr>
                                  Deploy app from ImageStream<\/td>oc new-app httpd -n test2<\/code><\/td><\/tr>
                                  Expose service<\/td>oc expose svc\/httpd -n test2<\/code><\/td><\/tr>
                                  Access app<\/td>oc get route httpd -n test2<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                  \n\n\n\n
                                  <\/p>\n","protected":false},"excerpt":{"rendered":"
                                  \ud83d\udc49 What ImageStream really gives you\ud83d\udc49 Why OpenShift uses it\ud83d\udc49 How it\u2019s better (in some cases) than just pulling a normal image \ud83e\udde0 First, imagine two situations: \ud83d\udd35 Situation 1:… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[5153],"tags":[],"class_list":["post-49170","post","type-post","status-publish","format-standard","hentry","category-openshift"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49170","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=49170"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49170\/revisions"}],"predecessor-version":[{"id":59007,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49170\/revisions\/59007"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=49170"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=49170"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=49170"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}