List view
- No due date•50/50 issues closed
- No due date•15/15 issues closed
- No due date•72/72 issues closed
- No due date•90/90 issues closed
- No due date•62/62 issues closed
- No due date•9/9 issues closed
Let's improve the release process of the UI (ui-backend + ui dashboard).
Due by February 28, 2023Since AWS is one of the biggest cloud providers it's good to have a nice integration with the AWS auth/authz from Epinio (IAM roles, IRSA..).
No due date•3/3 issues closedAchieve a better and cleaner release process
Due by January 31, 2023•16/16 issues closed- No due date•4/4 issues closed
Discussion here: https://github.com/epinio/epinio/discussions/1190
Due by March 7, 2022•7/7 issues closedMilestone to track work needed by the UI team Discussion: https://github.com/epinio/epinio/discussions/1150
No due dateImproving the experience of Developers using VS Code Discussion: https://github.com/epinio/epinio/discussions/1144
No due dateFocus on observability Discussion: https://github.com/epinio/epinio/discussions/1143
No due dateFocus on integrations with Rancher. This needs to wait until after Rancher 2.6.4 is released. Discussion: https://github.com/epinio/epinio/discussions/1142
No due date•7/7 issues closedFocus on developer experience See [this discussion](https://github.com/epinio/epinio/discussions/852)
Due by February 4, 2022•14/14 issues closedFocus of milestone 3: - Declarative installation (so people can review and change what is going to happen) - Idempotency (this is a pseudo-feature, shouldn't be needed if the installer succeeded in the first place, not sure if we should do this - TBD) - Integration with rancher (in other words, helm) - Upgrades (the solutions to the previous points would affect how this can be solved) - Sharing (components, cert-manager exists) - Uninstall (make this a feature?)
Due by December 17, 2021•18/18 issues closed- Due by November 15, 2021•33/33 issues closed
(Early) Summer 2022
Due by June 6, 2022•30/30 issues closedFeatures needed for (and bugs preventing) Epinio to be used as a day to day developer tool. This milestone is focused on stability of existing features rather than building new ones. Out of scope: - Security - Multi-tenancy - Seamless/Easy upgrades (although research into upgrades should be) In scope: - Stability - End to end story - API Completeness - Documentation - Examples - QA to find edge cases
Due by September 10, 2021•40/40 issues closedAll traffic is encrypted
Due by July 2, 2021•5/5 issues closedBased on https://herman.bearblog.dev/mvp-vs-slc/ For SLC we will only "officially" support one public cloud provider - namely Amazon AWS/EKS. Any bug that appears during QA on AWS/EKS we add to the SLC milestone. Other cloud providers will be postponed for the next milestone. This means, any Epinio feature that is part of SLC, should work both locally (on local clusters) and on AWS/EKS.
Due by July 30, 2021•33/33 issues closed- No due date•8/8 issues closed
- No due date•8/8 issues closed