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

Fix: github pages build #195

Merged
merged 14 commits into from
Jun 3, 2024
Merged

Fix: github pages build #195

merged 14 commits into from
Jun 3, 2024

Conversation

edgarsilva948
Copy link
Collaborator

What does this PR do?

This PR fixes the existing issues with the GitHub Pages build process. it also introduces a new feature that allows users to switch between light and dark modes, enhancing UX of the doc.

here's my forked repo working: https://edgarsilva948.github.io/crossplane-on-eks/

we need to adjust the Repository -> Settings -> Pages to be:

image

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)

  • Yes, I have added a new example under examples to support my PR

  • [] Yes, I have updated the docs for this feature

  • Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)

Note:

  • Not all the PRs require examples and docs
  • We prefer small, well tested pull requests. Please ensure your pull requests are self-contained, and commits are squashed

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

N/A

Comment on lines 14 to 20
- name: "argocd"
namespaceSelector:
matchNames:
- "argocd"
podMetricsEndpoints:
- port: "metrics"
selector: {}
Copy link
Contributor

@candonov candonov Jun 3, 2024

Choose a reason for hiding this comment

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

Crossplane has a podmonitor because the family provider pods don't have a service. Since ArgoCD has a service, it is better to add a servicemonitor for it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

fixed

revision: 1
datasource: prometheusdatasource
ekscontrolplane:
gnetId: 21192
Copy link
Contributor

Choose a reason for hiding this comment

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

nice one! The instances and control plane nodes version can be timeseries count and the version in the legend. With 3 nodes is ok but 300 would be hard to see. Merging this PR is not dependent on that update.

Comment on lines +180 to +182
module "gatekeeper" {
source = "aws-ia/eks-blueprints-addon/aws"
version = "1.1.1"
Copy link
Contributor

Choose a reason for hiding this comment

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

If this works but the addon doesn't, can you file an issue on the addon repo and link here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I noticed the Gatekeeper deployment's liveness probe doesn't have an initialDelaySeconds set, or it's too low. This can be a problem when not all cluster pods (like coredns, vpc-cpi, etc.) are up and running right away. If Gatekeeper starts too early, it doesn’t retry enough times and fail.

To work around this, I added a dependency, forcing Gatekeeper to wait until all the addons are up and running, which seems to work now. I will see if I can open a PR to adjust this in the addon repo.

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 f126c12 into awslabs:main Jun 3, 2024
1 of 2 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.

2 participants