{"id":6286,"date":"2025-07-03T07:08:27","date_gmt":"2025-07-03T07:08:27","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=6286"},"modified":"2025-07-03T07:08:27","modified_gmt":"2025-07-03T07:08:27","slug":"working-with-kubernetes-cluster-using-kubectl-part-6-namespaces","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/working-with-kubernetes-cluster-using-kubectl-part-6-namespaces\/","title":{"rendered":"Working with Kubernetes Namespaces"},"content":{"rendered":"\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"429\" src=\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-47-1024x429.png\" alt=\"\" class=\"wp-image-40976\" srcset=\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-47-1024x429.png 1024w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-47-300x126.png 300w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-47-768x322.png 768w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-47-1536x643.png 1536w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-47.png 1669w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Kubernetes namespaces are a way to organize, isolate, and manage Kubernetes resources. They provide a virtual sub-cluster within a Kubernetes cluster, and they can be used to separate resources by project, team, or environment.<\/p>\n\n\n\n<p>Each namespace has its own unique identifier, and resources within a namespace can only be accessed by users who have permission to access that namespace. This helps to prevent conflicts between different teams or projects, and it also helps to improve security by isolating resources from each other.<\/p>\n\n\n\n<p>Some of the benefits of using Kubernetes namespaces include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Isolation:<\/strong>&nbsp;Namespaces isolate resources from each other, which can help to prevent conflicts and improve security.<\/li>\n\n\n\n<li><strong>Organization:<\/strong>&nbsp;Namespaces can be used to organize resources by project, team, or environment. This can make it easier to manage resources and to find the resources that you need.<\/li>\n\n\n\n<li><strong>Resource quotas:<\/strong>&nbsp;Namespaces can be used to set resource quotas, which can help to ensure that no single team or project consumes too many resources.<\/li>\n\n\n\n<li><strong>Role-based access control (RBAC):<\/strong>&nbsp;RBAC can be used to grant users different levels of access to resources within a namespace. This can help to improve security and to ensure that users only have access to the resources that they need.<\/li>\n<\/ul>\n\n\n\n<p>Here are some examples of how Kubernetes namespaces can be used:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A production team can use a namespace to isolate their production resources from the development team&#8217;s resources.<\/li>\n\n\n\n<li>A company can use namespaces to isolate the resources of its different customers.<\/li>\n\n\n\n<li>A team can use namespaces to isolate the resources of its different projects.<\/li>\n\n\n\n<li>A developer can use namespaces to isolate the resources of their different development environments.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"536\" src=\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-48-1024x536.png\" alt=\"\" class=\"wp-image-40977\" srcset=\"https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-48-1024x536.png 1024w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-48-300x157.png 300w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-48-768x402.png 768w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-48-1536x804.png 1536w, https:\/\/www.devopsschool.com\/blog\/wp-content\/uploads\/2023\/10\/image-48.png 1594w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p>Here&#8217;s a detailed and easy-to-follow <strong>Kubernetes Namespace Tutorial<\/strong> using the notes you provided. This guide includes explanations, command examples, YAML usage, and follows best practices for teaching both CLI and declarative methods.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">\ud83e\udde0 Kubernetes Namespace Tutorial<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udccc What is a Namespace in Kubernetes?<\/h2>\n\n\n\n<p>Namespaces in Kubernetes are used to <strong>organize resources<\/strong> into <strong>virtual clusters<\/strong> within the same physical cluster. They are ideal for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Environment separation (dev, test, prod)<\/li>\n\n\n\n<li>Multi-tenancy<\/li>\n\n\n\n<li>Resource scoping<\/li>\n\n\n\n<li>Access control<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\u2699\ufe0f CRUD Pattern for Kubernetes Resources<\/h2>\n\n\n\n<p>Understanding the <strong>CRUD pattern<\/strong> (Create, Read, Update, Delete) is key for managing any Kubernetes resource.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Action<\/th><th>CLI Command<\/th><th>YAML Equivalent<\/th><\/tr><\/thead><tbody><tr><td>Create<\/td><td><code>kubectl create<\/code><\/td><td><code>kubectl create -f<\/code><\/td><\/tr><tr><td>Read<\/td><td><code>kubectl get<\/code>, <code>describe<\/code><\/td><td><code>kubectl get -o yaml<\/code><\/td><\/tr><tr><td>Update<\/td><td><code>kubectl edit<\/code><\/td><td><code>kubectl apply -f<\/code><\/td><\/tr><tr><td>Delete<\/td><td><code>kubectl delete<\/code><\/td><td><code>kubectl delete -f<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\ude80 Create Namespace (Imperative Command)<\/h2>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-1\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">$ kubectl get ns\n<span class=\"hljs-comment\"># Check existing namespaces<\/span>\n\n$ kubectl create ns rajesh\n<span class=\"hljs-comment\"># Create a new namespace called \"rajesh\"<\/span>\n\n$ kubectl get ns\n<span class=\"hljs-comment\"># Confirm creation<\/span>\n\n$ kubectl describe ns rajesh\n<span class=\"hljs-comment\"># Detailed metadata and status<\/span>\n\n$ kubectl edit ns rajesh\n<span class=\"hljs-comment\"># Edit namespace labels or annotations<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-1\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\uddd1\ufe0f Delete Namespace (Imperative)<\/h2>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-2\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">$ kubectl delete ns rajesh\n<span class=\"hljs-comment\"># Deletes the namespace<\/span>\n\n$ kubectl get ns\n<span class=\"hljs-comment\"># Confirm deletion<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-2\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udcc4 Namespace YAML Definition (Declarative Method)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Generate YAML<\/h3>\n\n\n\n<p>You can export an existing namespace YAML for reference:<\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-3\" data-shcb-language-name=\"JavaScript\" data-shcb-language-slug=\"javascript\"><span><code class=\"hljs language-javascript\">$ kubectl <span class=\"hljs-keyword\">get<\/span> ns devops -o yaml\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-3\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">JavaScript<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">javascript<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<p>Sample output:<\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">apiVersion: v1\nkind: Namespace\nmetadata:\n  name: devops1\n  labels:\n    kubernetes.io\/metadata.name: devops1\n<\/code><\/span><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create Namespace from YAML<\/h3>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">$ mkdir rajesh\n$ cd rajesh\/\n$ vi ns.yaml\n<\/code><\/span><\/pre>\n\n\n<p>Paste the following:<\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-4\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">apiVersion: v1\nkind: <span class=\"hljs-keyword\">Namespace<\/span>\n<span class=\"hljs-title\">metadata<\/span>:\n  <span class=\"hljs-title\">name<\/span>: <span class=\"hljs-title\">rajesh<\/span>\n  <span class=\"hljs-title\">labels<\/span>:\n    <span class=\"hljs-title\">env<\/span>: <span class=\"hljs-title\">test<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-4\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-5\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">$ kubectl create -f ns.yaml\n<span class=\"hljs-comment\"># Namespace created from YAML<\/span>\n\n$ kubectl get ns\n<span class=\"hljs-comment\"># Verify<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-5\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Update Namespace via YAML<\/h3>\n\n\n\n<p>Edit <code>ns.yaml<\/code>:<\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">metadata:\n  name: rajesh\n  labels:\n    env: production\n<\/code><\/span><\/pre>\n\n\n<p>Apply changes:<\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-6\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">$ kubectl apply -f ns.yaml\n<span class=\"hljs-comment\"># Changes applied declaratively<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-6\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Read &amp; Inspect YAML<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-7\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">$ kubectl get ns rajesh -o yaml\n<span class=\"hljs-comment\"># See YAML view of the namespace<\/span>\n\n$ kubectl describe -f ns.yaml\n<span class=\"hljs-comment\"># Detailed view of YAML-based namespace (alternative to `describe ns rajesh`)<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-7\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Delete Namespace from YAML<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-8\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">$ kubectl delete -f ns.yaml\n<span class=\"hljs-comment\"># Deletes using the YAML definition<\/span>\n\n$ kubectl get ns\n<span class=\"hljs-comment\"># Verify it's deleted<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-8\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83e\udde0 Summary of Key Commands<\/h2>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-9\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\"><span class=\"hljs-comment\"># Check existing namespaces<\/span>\nkubectl get ns\n\n<span class=\"hljs-comment\"># Create a namespace<\/span>\nkubectl create ns &lt;name&gt;\n\n<span class=\"hljs-comment\"># Read details<\/span>\nkubectl describe ns &lt;name&gt;\n\n<span class=\"hljs-comment\"># Edit namespace inline<\/span>\nkubectl edit ns &lt;name&gt;\n\n<span class=\"hljs-comment\"># Delete namespace<\/span>\nkubectl delete ns &lt;name&gt;\n\n<span class=\"hljs-comment\"># YAML-based:<\/span>\nkubectl create -f ns.yaml\nkubectl apply -f ns.yaml\nkubectl delete -f ns.yaml\nkubectl get ns &lt;name&gt; -o yaml\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-9\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>namespace.yaml<\/strong><\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-10\" data-shcb-language-name=\"PHP\" data-shcb-language-slug=\"php\"><span><code class=\"hljs language-php\">apiVersion: v1\nkind: <span class=\"hljs-keyword\">Namespace<\/span>\n<span class=\"hljs-title\">metadata<\/span>:\n  <span class=\"hljs-title\">name<\/span>: <span class=\"hljs-title\">playgroundinyaml<\/span><\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-10\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">PHP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">php<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>deployment.yaml<\/strong><\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">apiVersion: apps\/v1\nkind: Deployment\nmetadata:\n  name: hello-world\n  labels:\n    app: hello-world\n  namespace: playground1\nspec:\n  replicas: 4\n  selector:\n    matchLabels:\n      app: hello-world\n  template:\n    metadata:\n      labels:\n        app: hello-world\n    spec:\n      containers:\n      - name: hello-world\n        image: gcr.io\/google-samples\/hello-app:1.0\n        ports:\n        - containerPort: 8080\n<\/code><\/span><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Commands<\/strong><\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">$ ssh aen@c1-master1\n$ cd ~\/content\/course\/m3\/demos\n\n#Get a list of all the namespaces in our cluster\n$ kubectl get namespaces\n\n#get a list of all the API resources and if they can be in a namespace\n$ kubectl api-resources --namespaced=true | head\n$ kubectl api-resources --namespaced=false | head\n\n#Namespaces have state, Active and Terminating (when it's deleting)\n$ kubectl describe namespaces\n\n#Describe the details of an indivdual namespace\n$ kubectl describe namespaces kube-system\n\n#Get all the pods in our cluster across all namespaces. Right now, only system pods, no user workload\n$ kubectl get pods --all-namespaces\n\n#Get all the resource across all of our namespaces\n$ kubectl get all --all-namespaces\n\n#Get a list of the pods in the kube-system namespace\n$ kubectl get pods --namespace kube-system\n\n#Imperatively create a namespace\n$ kubectl create namespace playground1\n\n#Imperatively create a namespace...but there's some character restrictions. Lower case and only dashes.\n$ kubectl create namespace Playground1\n\n#Declaratively create a namespace\nmore namespace.yaml\n$ kubectl apply -f namespace.yaml\n\n#Get a list of all the current namespaces\n$ kubectl get namespaces\n\n#Start a deployment into our playground1 namespace\n$ more deployment.yaml\n$ kubectl apply -f deployment.yaml\n\n#Creating a resource imperitively\n$ kubectl run hello-world-pod \\\n    --image=gcr.io\/google-samples\/hello-app:1.0 \\\n    --generator=run-pod\/v1 \\\n    --namespace playground1\n\n#Where are the pods?\n$ kubectl get pods\n\n#List all the pods on our namespace\n$ kubectl get pods --namespace playground1\n$ kubectl get pods -n playground1\n\n#Get a list of all of the resources in our namespace...Deployment, ReplicaSet and Pods\n$ kubectl get all --namespace=playground1\n\n# Try to delete all the pods in our namespace...this will delete the single pod.\n# But the pods under the Deployment controller will be recreated.\n$ kubectl delete pods --all --namespace playground1\n\n# Get a list of all of the *new* pods in our namespace\n$ kubectl get pods -n playground1\n\n#Delete all of the resources in our namespace and the namespace and delete our other created namespace.\n#This deletes the Deployment controller, the Pods...or really ALL resources in the namespaces\n$ kubectl delete namespaces playground1\n$ kubectl delete namespaces playgroundinyaml\n\n#List all resources in all namespaces, now our Deployment is gone.\n$ kubectl get all\n$ kubectl get all --all-namespaces\n<\/code><\/span><\/pre>\n\n<div class=\"epyt-gallery\" data-currpage=\"1\" id=\"epyt_gallery_83444\"><iframe loading=\"lazy\"  id=\"_ytid_66658\"  width=\"760\" height=\"427\"  data-origwidth=\"760\" data-origheight=\"427\" src=\"https:\/\/www.youtube.com\/embed\/?enablejsapi=1&#038;autoplay=0&#038;cc_load_policy=0&#038;cc_lang_pref=&#038;iv_load_policy=1&#038;loop=0&#038;rel=1&#038;fs=1&#038;playsinline=0&#038;autohide=2&#038;theme=dark&#038;color=red&#038;controls=1&#038;disablekb=0&#038;\" class=\"__youtube_prefs__  no-lazyload\" title=\"YouTube player\"  data-epytgalleryid=\"epyt_gallery_83444\"  allow=\"fullscreen; accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen data-no-lazy=\"1\" data-skipgform_ajax_framebjll=\"\"><\/iframe><div class=\"epyt-gallery-list\"><div>Sorry, there was a YouTube error.<\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Kubernetes namespaces are a way to organize, isolate, and manage Kubernetes resources. They provide a virtual sub-cluster within a Kubernetes cluster, and they can be used to separate resources by&#8230; <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[4859],"tags":[],"class_list":["post-6286","post","type-post","status-publish","format-standard","hentry","category-kubernetes"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/6286","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=6286"}],"version-history":[{"count":6,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/6286\/revisions"}],"predecessor-version":[{"id":49933,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/6286\/revisions\/49933"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=6286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=6286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=6286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}