-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: Make gitops-bridge example to use kubectl to deploy addons and workloads #1886
Conversation
Signed-off-by: Carlos Santana <[email protected]>
Signed-off-by: Carlos Santana <[email protected]>
@candonov please take a look when you have a chance. |
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.
Much easier to understand the code.
This command creates the application set manifest to deploy the addons. | ||
```shell | ||
kubectl --context hub apply -n argocd -f ../hub/bootstrap/addons.yaml | ||
``` |
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 to kubectl apply with Terraform
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.
@candonov I don't understand the comment
change to kubectl apply with Terraform
In all our patterns now, we moved away from using terraform providers like kubernertes, helm, or kubectl and instead tell the user to use kubectl apply
this way is easier to understand like we have in the single cluster gitops-bridge pattern here https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/patterns/gitops/getting-started-argocd#deploy-the-addons
This command will deploy the application using kubectl to all clusters connected to the hub cluster, using the manifest files in [./hub/bootstrap/workloads.yaml](./hub/bootstrap/workloads.yaml). | ||
```shell | ||
kubectl --context hub apply -n argocd -f ../hub/bootstrap/workloads.yaml | ||
``` |
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.
Same here, apply with terraform
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.
LGTM
Description
This change makes it more clear how the bootstrap of addons and workloads happens, by removing the use of gitops-bridge module to deploy the bootstrap ArgoCD apps.
This change should make it more clearn to the end user trying out the pattern and following step by step the instructions in the README.md of each corresponding gitops pattern.
Motivation and Context
How was this change tested?
pre-commit run -a
with this PRAdditional Notes