@@ -78,7 +78,7 @@ To get more detail please refer to this [link](https://blog.alexellis.io/introdu
78
78
79
79
Once we have arkade, we can create a cluster and install ArgoCD. If you prefer, you can also manually download all the tools required, and find the instructions for ArgoCD's helm chart.
80
80
81
- * [arkade](https://get-arkade.dev) (v0.7.10 ) Kubernetes marketplace
81
+ * [arkade](https://get-arkade.dev) (v0.7.13 ) Kubernetes marketplace
82
82
83
83
` ` ` bash
84
84
# Run with or without sudo
@@ -141,8 +141,39 @@ arkade is not only for the CLI tooling, it also helps you to get started to inst
141
141
hopefully arkade also supports installing ArgoCD.
142
142
143
143
` ` ` bash
144
- $ kubectl create namespace argocd
145
144
$ arkade install argocd
145
+ Using Kubeconfig: /Users/batuhan.apaydin/.kube/config
146
+ Node architecture: "amd64"
147
+ =======================================================================
148
+ = ArgoCD has been installed =
149
+ =======================================================================
150
+
151
+
152
+ # Get the ArgoCD CLI
153
+ arkade install argocd
154
+
155
+ # Port-forward the ArgoCD API server
156
+ kubectl port-forward svc/argocd-server -n argocd 8443:443 &
157
+
158
+ # Get the password
159
+ PASS=$(kubectl get secret argocd-initial-admin-secret \
160
+ -n argocd \
161
+ -o jsonpath="{.data.password}" | base64 -d)
162
+ echo $PASS
163
+
164
+ # Or log in:
165
+ argocd login --name local 127.0.0.1:8443 --insecure \
166
+ --username admin \
167
+ --password $PASS
168
+
169
+ # Open the UI:
170
+ https://127.0.0.1:8443
171
+
172
+ # Get started with ArgoCD at
173
+ # https://argoproj.github.io/argo-cd/#quick-start
174
+
175
+ Thanks for using arkade!
176
+
146
177
` ` `
147
178
148
179
Verify if everything is working properly in _argocd_ namespace before moving onto the next step.
@@ -168,31 +199,45 @@ First, we need to authenticate to ArgoCD server.Argo CD v1.9. Later the initial
168
199
auto-generated and stored as clear text in the field password in a secret named argocd-initial-admin-secret in your Argo
169
200
CD installation namespace.
170
201
171
- You can simply retrieve this password using kubectl :
202
+ Because ArgoCD Server is running on a Kubernetes, we should do port-forwarding first in order to access the server, it
203
+ can be achieved by the following command easily :
172
204
173
205
` ` ` bash
174
- $ kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d && echo
175
- SyudUgAtDobmgSjM
206
+ # Port-forward the ArgoCD API server
207
+ $ kubectl port-forward svc/argocd-server -n argocd 8443:443 &
208
+ Forwarding from 127.0.0.1:8443 -> 443
209
+ Forwarding from [::1]:8443 -> 443
176
210
` ` `
177
211
178
- Because ArgoCD Server is running on a Kubernetes, we should do port-forwarding first in order to access the server, it
179
- can be achieved by the following command easily :
212
+ You can simply retrieve this password using kubectl :
180
213
181
214
` ` ` bash
182
- $ kubectl port-forward svc/argocd-server -n argocd 8080:443
183
- Forwarding from 127.0.0.1:8080 -> 8080
184
- Forwarding from [::1]:8080 -> 8080
215
+ # Get the password
216
+ $ PASS=$(kubectl get secret argocd-initial-admin-secret \
217
+ -n argocd \
218
+ -o jsonpath="{.data.password}" | base64 -d)
219
+ echo $PASS
185
220
` ` `
186
221
187
222
After that, by using the username _admin_ and the password from above, lets log into ArgoCD :
188
223
189
224
` ` ` bash
190
- $ argocd login --name local localhost:8080
225
+ # log in:
226
+ $ argocd login --name local 127.0.0.1:8443 --insecure \
227
+ --username admin \
228
+ --password $PASS
191
229
WARNING: server certificate had error: x509: certificate signed by unknown authority. Proceed insecurely (y/n)? y
192
230
Username: admin
193
231
Password:
194
232
'admin:login' logged in successfully
195
233
Context 'local' updated
234
+
235
+
236
+ # Open the UI:
237
+ $ open https://127.0.0.1:8443
238
+
239
+ # Get started with ArgoCD at
240
+ # https://argoproj.github.io/argo-cd/#quick-start
196
241
` ` `
197
242
198
243
To get more detail about login process, please refer to
0 commit comments