Skip to content
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

Merged
merged 2 commits into from
Feb 28, 2024

Conversation

csantanapr
Copy link
Contributor

@csantanapr csantanapr commented Feb 20, 2024

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?

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Yes, I have updated the docs for this feature
  • Yes, I ran pre-commit run -a with this PR

Additional Notes

@csantanapr csantanapr requested a review from a team as a code owner February 20, 2024 02:55
@csantanapr csantanapr requested a review from candonov February 20, 2024 02:55
@csantanapr
Copy link
Contributor Author

@candonov please take a look when you have a chance.

Copy link
Contributor

@candonov candonov left a 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.

Comment on lines +68 to +71
This command creates the application set manifest to deploy the addons.
```shell
kubectl --context hub apply -n argocd -f ../hub/bootstrap/addons.yaml
```
Copy link
Contributor

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

Copy link
Contributor Author

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

Comment on lines +188 to +191
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
```
Copy link
Contributor

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

Copy link
Contributor

@candonov candonov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@candonov candonov merged commit 03e4550 into aws-ia:main Feb 28, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update gitops patterns to make more clear how bootstrap works
2 participants