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

Flux update #794

Merged
merged 14 commits into from
Aug 4, 2023
Merged

Flux update #794

merged 14 commits into from
Aug 4, 2023

Conversation

zjaco13
Copy link
Contributor

@zjaco13 zjaco13 commented Jul 26, 2023

Issue #, if available: #694

Description of changes:
Added workload repos to flux

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link
Collaborator

@elamaran11 elamaran11 left a comment

Choose a reason for hiding this comment

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

@zjaco13 Please check my comments. Also check on another Flux Multi path PR which has some common changes.

name: "nginx",
namespace: "default",
repository: {
repoUrl: 'https://github.com/zjaco13/flux-tester',
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could we use a standard repos vs pointing to your own personal repo? Something like this - https://github.com/aws-observability/aws-observability-accelerator/tree/main or PodInfo

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We can use another repo. Not sure if the observability accelerator manifests will be the best option though, because they require values and a different namespace.

elamaran11
elamaran11 previously approved these changes Jul 29, 2023
Copy link
Collaborator

@elamaran11 elamaran11 left a comment

Choose a reason for hiding this comment

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

LGTM. @shapirov103 Please check this and do e2e if you are good.

Copy link
Collaborator

@shapirov103 shapirov103 left a comment

Choose a reason for hiding this comment

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

@zjaco13 looks great, I will run e2e just as a sanity check, although we don't have a direct impact on the e2e test.


const nginxDashUrl = "https://raw.githubusercontent.com/aws-observability/aws-observability-accelerator/main/artifacts/grafana-dashboards/eks/nginx/nginx.json"

const addOn = new blueprints.addons.FluxCDAddOn({
Copy link
Collaborator

Choose a reason for hiding this comment

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

@zjaco13 was this example validated?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes I validated it

@shapirov103
Copy link
Collaborator

/do-e2e-tests

Copy link

@aws-ia-ci aws-ia-ci left a comment

Choose a reason for hiding this comment

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

end to end tests failed. A maintainer can provide more details.

@shapirov103
Copy link
Collaborator

/do-e2e-tests

Copy link

@aws-ia-ci aws-ia-ci left a comment

Choose a reason for hiding this comment

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

end to end tests failed. A maintainer can provide more details.

@shapirov103
Copy link
Collaborator

Failure as reported:

[21:08:13] Stack blueprint-construct-dev has an ongoing operation in progress and is not stable (ROLLBACK_IN_PROGRESS (The following resource(s) failed to create: [blueprintconstructdevE0DAE201]. Rollback requested by user.))
40 | blueprint-construct-dev | 92/245 | 9:08:10 PM | CREATE_IN_PROGRESS | Custom::AWSCDK-EKS-Cluster | blueprint-construct-dev/Resource/Resource/Default (blueprintconstructdevE0DAE201) Resource creation Initiated
41 | blueprint-construct-dev | 92/245 | 9:08:10 PM | CREATE_FAILED | Custom::AWSCDK-EKS-Cluster | blueprint-construct-dev/Resource/Resource/Default (blueprintconstructdevE0DAE201) Received response status [FAILED] from custom resource. Message returned: Cluster is in a FAILED status
42


It may be related to the actual account where we run the test, as I was not able to see a better diagnostic message. Were you able to run this successfully in your account?

@shapirov103
Copy link
Collaborator

/do-e2e-tests

Copy link

@aws-ia-ci aws-ia-ci left a comment

Choose a reason for hiding this comment

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

end to end tests passed

@shapirov103 shapirov103 merged commit f3d2f0f into aws-quickstart:main Aug 4, 2023
9 checks passed
@freschri
Copy link
Collaborator

freschri commented Aug 7, 2023

@zjaco13 this PR is causing problems when using it to deploy multiple Kustomizations. Could you please review, test (against your use case) and approve #811 which fixes the mentioned problems?
@elamaran11 @shapirov103 FYI

shapirov103 added a commit that referenced this pull request Aug 15, 2023
…y-multiple-kustomizations-following-pr-794

FluxCD fails to deploy multiple Kustomizations following PR #794
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.

5 participants