Skip to content

Conversation

GuopingJia
Copy link
Contributor

Automatically generated by Netlify CMS

Copy link

netlify bot commented Oct 3, 2025

Deploy Preview for hpe-dev-portal ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit c0581d8
🔍 Latest deploy log https://app.netlify.com/projects/hpe-dev-portal/deploys/68ee41d7646d3d00086bd988
😎 Deploy Preview https://deploy-preview-3163--hpe-dev-portal.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Collaborator

@choukden choukden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Guoping,

Thank you very much for your great blog post and contribution to the community!

I have just added one comment for the date of the blog post.

I will engage with Joe Boyle's team (I guess that Kathleen Johnson's team will review your blog post from an editorial standpoint).

THANKS!

Best regards,
Denis

---
title: Exposing Grafana service using Tailscale for MKS monitoring in HPE
Private Cloud Enterprise
date: 2025-09-26T20:28:43.991Z
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may want to change the date of blog to October 3, 2025.

@GuopingJia
Copy link
Contributor Author

Hi Guoping,

Thank you very much for your great blog post and contribution to the community!

I have just added one comment for the date of the blog post.

I will engage with Joe Boyle's team (I guess that Kathleen Johnson's team will review your blog post from an editorial standpoint).

THANKS!

Best regards, Denis

Thanks Denis for your review.

The new patch has changed the date.

Guoping

@mrajkumarmapr
Copy link

Language Edits Only


Change 1:

  • Original: "This blog post describes how to expose the Grafana service, running in an MKS cluster"
  • Modified: "This blog post describes how to expose the Grafana service running in an MKS cluster"
  • Difference: Removed comma after "service" (unnecessary comma before restrictive clause)

Change 2:

  • Original: "Through the integration with"
  • Modified: "Through integration with"
  • Difference: Removed unnecessary article "the"

Change 3:

  • Original: "The following sections will describe"
  • Modified: "The following sections describe"
  • Difference: Changed future tense "will describe" to present tense "describe"

Change 4:

  • Original: "from a HPE Private Cloud Enterprise workspace"
  • Modified: "from an HPE Private Cloud Enterprise workspace"
  • Difference: Changed "a" to "an" (correct article before vowel sound "H")

Change 5:

  • Original: "to securely connects devices"
  • Modified: "to securely connect devices"
  • Difference: Fixed subject-verb agreement error (connects → connect)

Change 6:

  • Original: "called tailnet"
  • Modified: "called a tailnet"
  • Difference: Added missing article "a"

Change 7:

  • Original: "through Tailscale's admin console"
  • Modified: "through Tailscale's admin console"
  • Difference: Fixed escaped apostrophe to regular apostrophe

Change 8:

  • Original: "This makes the applications easily reachable"
  • Modified: "This makes applications easily reachable"
  • Difference: Removed unnecessary article "the" (referring to applications in general)

Change 9:

  • Original: "found in the blog post"
  • Modified: "in the blog post"
  • Difference: Removed redundant word "found"

Change 10:

  • Original: "the deployed MetalLB in namespace metallb-system"
  • Modified: "the deployed MetalLB in the metallb-system namespace"
  • Difference: Added article "the" and reordered for proper English syntax

Change 11:

  • Original: "such as Linux, Windows, MacOS, iOS, Android"
  • Modified: "such as Linux, Windows, macOS, iOS, and Android"
  • Difference: Corrected "MacOS" to "macOS" (proper Apple capitalization) and added Oxford comma before "and"

Change 12:

  • Original: "It's used"
  • Modified: "It is used"
  • Difference: Fixed escaped apostrophe and expanded contraction for formal technical writing

Change 13:

  • Original: "It's the bridge"
  • Modified: "It is the bridge"
  • Difference: Fixed escaped apostrophe and expanded contraction for formal technical writing

Change 14:

  • Original: "using the package avaible from Tailscale download page"
  • Modified: "using the package available from the Tailscale download page"
  • Difference: Fixed spelling error "avaible" → "available" and added missing article "the"

Change 15:

  • Original: "by choosing the GitHub"
  • Modified: "by choosing GitHub"
  • Difference: Removed unnecessary article "the" before proper noun

Change 16:

  • Original: "Type below command"
  • Modified: "Type the following command"
  • Difference: Changed "below command" to "the following command" (proper English usage)

Change 17:

  • Original: "After few minutes"
  • Modified: "After a few minutes"
  • Difference: Added missing article "a"

Change 18:

  • Original: "the service's IP aaadress stays hidden"
  • Modified: "the service's IP address stays hidden"
  • Difference: Fixed escaped apostrophe and corrected spelling "aaadress" → "address"

Change 19:

  • Original: "You need also add a node attribute"
  • Modified: "You also need to add a node attribute"
  • Difference: Corrected word order and added missing infinitive "to"

Change 20:

  • Original: "Create below Ingress YAML manifest file"
  • Modified: "Create the following Ingress YAML manifest file"
  • Difference: Changed "below" to "the following" (proper English usage)

Change 21:

  • Original: "you can land to one of the pre-configured Grafana dashboard"
  • Modified: "you can navigate to one of the pre-configured Grafana dashboards"
  • Difference: Changed "land to" to "navigate to" (proper verb usage) and pluralized "dashboard" to "dashboards"

Change 22:

  • Original: "Conclusions"
  • Modified: "Conclusion"
  • Difference: Changed plural "Conclusions" to singular "Conclusion" (standard section heading)

Change 23:

  • Original: "in MKS clustes"
  • Modified: "in MKS clusters"
  • Difference: Fixed spelling error "clustes" → "clusters"

Change 24:

  • Original: "this approach offers s simple and secure way"
  • Modified: "this approach offers a simple and secure way"
  • Difference: Fixed typo "s simple" → "a simple"

Change 25:

  • Original: "it's recommended"
  • Modified: "it is recommended"
  • Difference: Fixed escaped apostrophe and expanded contraction for formal writing

Change 26:

  • Original: "configure Tailscale to automatically disable Funnel if connection drops"
  • Modified: "configure Tailscale to automatically disable Funnel if the connection drops"
  • Difference: Added missing article "the"

@GuopingJia GuopingJia force-pushed the cms/GuopingJia/hpe-dev-portal/blog/exposing-grafana-service-using-tailscale-for-mks-monitoring-in-hpe-private-cloud-enterprise branch from ac15fc9 to 26ee0b7 Compare October 14, 2025 08:18
@GuopingJia
Copy link
Contributor Author

Thank you, @mrajkumarmapr, for your review and detailed comments. The latest patch incorporates all your feedback. When you have a moment, please take a look. Much appreciated! - Guoping

@mrajkumarmapr
Copy link

An MKS cluster has been provisioned from an HPE Private Cloud Enterprise workspace.
should be:
An MKS cluster has been provisioned from a HPE Private Cloud Enterprise workspace

@mrajkumarmapr
Copy link

Use below command to view the details

Use the following command....

@mrajkumarmapr
Copy link

After login, you can navigate to one of the pre-configured Grafana dashboards, e.g., Kubernetes/API server.

After logging in....

@GuopingJia
Copy link
Contributor Author

Thank you, @mrajkumarmapr , for your further review. The latest patch incorporates all these review feedback. - Guoping

@choukden choukden merged commit f79dd61 into hpe-dev-incubator:master Oct 15, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants