From eafd87a990ef490f932906adeaa3b1e468a016b9 Mon Sep 17 00:00:00 2001 From: HarinAcharya <84226672+HarinAcharya@users.noreply.github.com> Date: Fri, 31 Oct 2025 13:42:52 +0530 Subject: [PATCH 1/2] Update Kubecost dashboard access instructions Added instructions for using Amazon EKS add-on to access Kubecost dashboard. --- .../cost-monitoring-kubecost-view-dashboard.adoc | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc b/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc index fe7455d7e..9da238a6d 100644 --- a/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc +++ b/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc @@ -19,10 +19,20 @@ kubectl get pods --namespace kubecost . On your device, enable port-forwarding to expose the Kubecost dashboard. + +[NOTE] +* If kubecost is installed using helm: ++ [source,bash,subs="verbatim,attributes"] ---- kubectl port-forward deployment/kubecost-cost-analyzer 9090 --namespace kubecost ---- + +* If kubecost is installed using Amazon EKS add-on: ++ +[source,bash,subs="verbatim,attributes"] +---- +kubectl port-forward deployment/cost-analyzer 9090 --namespace kubecost +---- + Alternatively, you can use the <> to expose Kubecost and use Amazon Cognito for authentication, authorization, and user management. For more information, see link:containers/how-to-use-application-load-balancer-and-amazon-cognito-to-authenticate-users-for-your-kubernetes-web-apps[How to use Application Load Balancer and Amazon Cognito to authenticate users for your Kubernetes web apps,type="blog"]. . On the same device that you completed the previous step on, open a web browser and enter the following address. @@ -38,4 +48,4 @@ You see the Kubecost Overview page in your browser. It might take 5–10 minutes * *Cost allocation* – View monthly Amazon EKS costs and cumulative costs for each of your namespaces and other dimensions over the past seven days. This is helpful for understanding which parts of your application are contributing to Amazon EKS spend. -* *Assets* – View the costs of the {aws} infrastructure assets that are associated with your Amazon EKS resources. \ No newline at end of file +* *Assets* – View the costs of the {aws} infrastructure assets that are associated with your Amazon EKS resources. From 0c4cefad4502c9cc165d2c81adf0bf099099868f Mon Sep 17 00:00:00 2001 From: HarinAcharya <84226672+HarinAcharya@users.noreply.github.com> Date: Fri, 31 Oct 2025 13:47:12 +0530 Subject: [PATCH 2/2] Added command and rectified document Current document had command to expose kubecost deployment when installed via helm but it did not have command to expose kubecost deployment when installed via addon add the command to expose kubecost deployment when installed via addon and rectified the wordings accordingly --- .../cost-monitoring-kubecost-view-dashboard.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc b/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc index 9da238a6d..3bcea18c6 100644 --- a/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc +++ b/latest/ug/cluster-management/cost-monitoring-kubecost-view-dashboard.adoc @@ -19,7 +19,6 @@ kubectl get pods --namespace kubecost . On your device, enable port-forwarding to expose the Kubecost dashboard. + -[NOTE] * If kubecost is installed using helm: + [source,bash,subs="verbatim,attributes"]