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

Add Documentation #165

Open
2 of 9 tasks
leonnicolas opened this issue May 13, 2021 · 3 comments
Open
2 of 9 tasks

Add Documentation #165

leonnicolas opened this issue May 13, 2021 · 3 comments

Comments

@leonnicolas
Copy link
Collaborator

leonnicolas commented May 13, 2021

  • NAT to NAT
  • Tutorials
    • How to connect nodes in two different cloud providers
  • Contribution Guide
    • Building the website
    • Style guide
  • Update Installation Guide in README.md
  • Monitoring with Prometheus Operator
  • Auto Generate CRD Documentation (cmd/gen-docs/main.go: auto generate docs for CRD #169)
@stv0g
Copy link
Contributor

stv0g commented Jul 13, 2021

I would add a paragraph describing how Kilo handles routing.

Especially the difference when used in standalone/CNI and addon mode.

@stv0g
Copy link
Contributor

stv0g commented Jul 13, 2021

A quick note for the NAT-to-NAT documentation:

Endpoint discovery only works for nodes with a persistentKeepalive greater than 0.

@squat
Copy link
Owner

squat commented Jul 16, 2021

I think we could also add a new guide/tutorial about balancing scheduling across different clouds/locations. This would help people see the value of multi-cloud and get started. We could use some of the concepts shown in this blog post: https://particule.io/blog/scaleway-kosmos/#d%C3%A9monstration-sch%C3%A9duling (french). This post describes getting started with Scaleway Kosmos, which is built on Kilo, and scheduling workloads across cloud providers.

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

No branches or pull requests

3 participants