From 45f38d2b2bc891e859181cf3cbfb10e4449043a8 Mon Sep 17 00:00:00 2001 From: mclarke Date: Tue, 12 Jan 2021 22:27:00 +0000 Subject: [PATCH 1/2] fix image links --- ...ackstage-feature-kubernetes-for-service-owners.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md b/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md index a99cb8e65b..8877c5607c 100644 --- a/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md +++ b/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md @@ -4,14 +4,12 @@ author: Matthew Clarke, Spotify authorURL: https://github.com/mclarke47 --- -![Animation of Kubernetes and cloud provider icons becoming the Backstage logo](/microsite/blog/assets/21-01-12/backstage-k8s-1-hero.gif) +![Animation of Kubernetes and cloud provider icons becoming the Backstage logo](/blog/assets/21-01-12/backstage-k8s-1-hero.gif) TLDR; We’re rethinking the Kubernetes developer experience with a new feature: a Kubernetes monitoring tool that’s designed around the needs of service owners, not cluster admins. Now developers can easily check the health of their services no matter how or where those services are deployed — whether it’s on a local host for testing or in production on dozens of clusters around the world. And since Backstage uses the native Kubernetes API, the feature works with whichever cloud provider (AWS, Azure, GCP, etc.) or managed service (OpenShift, IBM Cloud, GKE, etc.) you already use. -<--truncate--> - ## The missing link between K8s and your service A core feature of Backstage is its service catalog, which aggregates information about software systems together inside a single tool, with a consistent, familiar UI. @@ -22,21 +20,21 @@ By navigating to a service’s overview page in Backstage, you can see everythin Kubernetes in Backstage can be configured to search multiple clusters for your services. It will then aggregate them together into a single view. So if you deploy to multiple clusters you will no longer need to switch kubectl contexts to understand the current state of your service. -![List of deployments in Backstage Kubernetes plugin](/microsite/blog/assets/21-01-12/backstage-k8s-2-deployments.png) +![List of deployments in Backstage Kubernetes plugin](/blog/assets/21-01-12/backstage-k8s-2-deployments.png) ## Automatic error reporting Instead of trying different kubectl commands to figure out where an error occurred, Backstage will automatically find and highlight errors in Kubernetes resources that are affecting your service. So you can spend time fixing errors, not hunting for them. -![Error reporting screen in Backstage Kubernetes plugin](/microsite/blog/assets/21-01-12/backstage-k8s-3-error-reporting.png) +![Error reporting screen in Backstage Kubernetes plugin](/blog/assets/21-01-12/backstage-k8s-3-error-reporting.png) ## Autoscaling limits at a glance Backstage also shows you how close your service is to its autoscaling limit. Coming up to a period of high load? Now you will be able to see how your horizontal autoscaling is dealing with it across multiple clusters. -![Autoscaling limits screen in Backstage Kubernetes plugin](/microsite/blog/assets/21-01-12/backstage-k8s-4-autoscaling-limits.png) +![Autoscaling limits screen in Backstage Kubernetes plugin](/blog/assets/21-01-12/backstage-k8s-4-autoscaling-limits.png) -![Autoscaling limits screen in Backstage Kubernetes plugin](/microsite/blog/assets/21-01-12/backstage-k8s-5-autoscaling-limits.png) +![Autoscaling limits screen in Backstage Kubernetes plugin](/blog/assets/21-01-12/backstage-k8s-5-autoscaling-limits.png) ## Pick a cloud, any Cloud From 240ce7ac79e22c3befeb475bf054d2a214ea1435 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Tue, 12 Jan 2021 23:38:46 +0100 Subject: [PATCH 2/2] Update 2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md --- ...01-12-new-backstage-feature-kubernetes-for-service-owners.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md b/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md index 8877c5607c..b26806fecd 100644 --- a/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md +++ b/microsite/blog/2021-01-12-new-backstage-feature-kubernetes-for-service-owners.md @@ -10,6 +10,8 @@ TLDR; We’re rethinking the Kubernetes developer experience with a new feature: And since Backstage uses the native Kubernetes API, the feature works with whichever cloud provider (AWS, Azure, GCP, etc.) or managed service (OpenShift, IBM Cloud, GKE, etc.) you already use. + + ## The missing link between K8s and your service A core feature of Backstage is its service catalog, which aggregates information about software systems together inside a single tool, with a consistent, familiar UI.