-
Notifications
You must be signed in to change notification settings - Fork 30
[DOC] update setting up workload cluster #461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Anand Kumar Singh <anandrkskd@gmail.com>
Update the config-map with details with principal server address URL, creds, agent type and more. | ||
|
||
__Note:__ | ||
Set `agent.tls.client.insecure` to `insecure` to if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. Just no :)
@@ -97,4 +97,63 @@ To install the principal component on the control plane cluster, you can use the | |||
|
|||
``` | |||
kubectl --context <control plane context> -n argocd apply -k install/kubernetes/principal | |||
``` | |||
## Installation and configuration of the workload components |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we plan on adding this document in our release notes, can we add the configuraion for setting up control plane cluster as well? (using argocd or gitops operator)
https://github.com/argoproj-labs/argocd-operator/blob/master/controllers/argocdagent/docs/quickstart.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change the directory:
kubectl --context <principal context> apply -n argocd -k install/kubernetes/argo-cd/principal
error: must build at directory: not a valid directory: evalsymlink failure on 'install/argo-cd/principal' : lstat /home/varshab/argocd-agent/install/argo-cd: no such file or directory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
better to have oc
|
||
The following Argo CD components **must not** run on the workload cluster. If you installed them, either delete the StatefulSet or Deployment resource (recommended) or scale them *permanently* down to 0. | ||
|
||
* `argocd-server` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add enabled: false
here for operator specific installation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add argocd-agentctl
as a prerequisite?
#### Create the PKI on the agent: | ||
|
||
```bash | ||
argocd-agentctl pki issue agent <agent-name> --agent-context <workload context> --agent-namespace <workload namespace> --upsert |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to run it from control plane right? It seems a little confusing as the title starts with prereq for agent
What does this PR do / why we need it:
This PR adds documentation for argo-cd agent workload setup.
Which issue(s) this PR fixes:
Fixes #?
How to test changes / Special notes to the reviewer:
Checklist