fixing the helm login command for the onprem installation (#17222)
Mateusz Bularz committed
Mar 22, 2024 at 09:42 UTC
fcbdafac40d972f903dc2b3a0c8c9cd76c8055c9
2 files changed
+2
-2
docs/netdata-cloud-onprem/getting-started.md
+1
-1
@@ -75,7 +75,7 @@ aws configure
75
#### Configure helm to use secured ECR repository
76
Using `aws` command we will generate a token for helm to access the secured ECR repository:
77
```bash
78
-aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com/netdata-cloud-onprem
78
+aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com
79
```
80
81
After this step you should be able to add the repository to your helm or just pull the helm chart:
docs/netdata-cloud/netdata-cloud-on-prem/installation.md
+1
-1
@@ -34,7 +34,7 @@ aws configure
34
Using `aws` command we will generate a token for helm to access the secured ECR repository:
35
36
```bash
37
-aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com/netdata-cloud-onprem
37
+aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com
38
```
39
40
After this step you should be able to add the repository to your helm or just pull the helm chart: