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

☔ Konnect managed entities #370

Closed
47 tasks done
lahabana opened this issue Jun 24, 2024 · 1 comment
Closed
47 tasks done

☔ Konnect managed entities #370

lahabana opened this issue Jun 24, 2024 · 1 comment

Comments

@lahabana
Copy link
Contributor

lahabana commented Jun 24, 2024

Problem Statement

Users would like to manage Konnect entities directly from Kubernetes resources.
This issue is the main tracker to cover having CRD routes for things like: Service, Consumers, Routes.

The goal is to have a semi-automatic way to add support for entities in platform-api. This is necessary to minimise future work when new Konnect entities are added.

Proposed Solution

Pending Product brief and Engineering brief.

Some open questions:

  • How does relationship work?
  • What's in status/condition?
  • Can you mix entities managed by CRDs and non.

Additional Information

Some useful reads:

Implementation uses https://github.com/Kong/sdk-konnect-go/ to interact with Konnect which is generated from https://github.com/Kong/platform-api.

Acceptance Criteria

Design

Preview Give feedback
  1. area/spike release/required
    pmalek

Implementation - August demo scope

Preview Give feedback
  1. area/konnect
    pmalek
  2. area/konnect
    pmalek
  3. area/crds area/konnect
    pmalek
  4. area/crds area/konnect
    pmalek
  5. area/crds area/konnect
    pmalek
  6. area/crds area/konnect
    pmalek
  7. area/crds area/konnect
    pmalek
  8. area/konnect
    pmalek
  9. area/crds area/konnect
    mlavacca
  10. area/konnect
    randmonkey
  11. area/konnect area/tests
    czeslavo
  12. area/konnect
    czeslavo
  13. area/konnect
    mlavacca
  14. area/konnect
    czeslavo

Implementation - GA scope (October-ish)

Preview Give feedback
  1. area/konnect
    pmalek
  2. area/crds area/konnect
    pmalek
  3. area/crds area/konnect
    randmonkey
  4. area/konnect
    randmonkey
  5. area/crds area/konnect
    tao12345666333
  6. area/crds area/konnect
    czeslavo
  7. area/crds area/konnect
    czeslavo
  8. area/crds area/konnect
    czeslavo
  9. area/crds area/konnect
    randmonkey
  10. area/konnect
    czeslavo
  11. area/crds area/konnect
    pmalek
  12. area/crds area/konnect
    pmalek
  13. area/crds area/konnect
    pmalek
  14. area/crds area/konnect
    pmalek
  15. area/crds area/konnect
    tao12345666333
  16. area/konnect
    pmalek
  17. area/konnect
    pmalek
  18. area/konnect
    pmalek
  19. area/konnect
    pmalek
  20. area/konnect
    randmonkey
  21. area/konnect
    randmonkey
  22. area/konnect
    mlavacca
  23. area/konnect
    pmalek
  24. pmalek
  25. area/konnect
    pmalek
  26. area/konnect
  27. area/konnect area/maintenance
    pmalek
  28. pmalek

Documentation

Preview Give feedback
  1. 10 of 10
    area/konnect documentation
    czeslavo pmalek
  2. area/konnect documentation
    randmonkey

Related issues

Preview Give feedback
@pmalek
Copy link
Member

pmalek commented Nov 6, 2024

#827 covers the Post GA issues for this epic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants