jeho

Results 116 issues of jeho

# WHY To improve platform robustness, reliability, time to deploy and self healing. # User Story **AS A** a platform engineer **I WANT TO** all Helm releases to be independently...

Story
not-ready

The project-id was treated as a secret but it is not a secret. After this change it will be possible to copy and paste scw k8s cluster creation command.

# WHY Contributors should be able tests their images on their clusters # User Story **AS A** OSS contributor **I WANT TO** the `Build and publish Docker` pipeline to be...

Story
not-ready

# WHY Workload in their own namespaces will make it easy to filter metrics, logs and set egress filtering for a given app, without any knowledge of app k8s labels....

Story
not-ready

# WHY Developers need golden deployment paths for their applications # User Story **AS A** platform engineer **I WANT TO** use provide my own workload catalog **SO** development teams can...

Story
not-ready

# WHY Users needs to know about manual steps that should be performed to prune a team from Otomi. # Acceptance criteria **GIVEN** a team in Otomi console **WHEN** a...

Story

# WHY Users too often end up with Otomi installation failing due to insufficient cluster resources # User Story **AS A** user installing Otomi **I WANT TO** to be warned...

Story

**Describe the bug:** (a clear and concise description of what the bug is) **To Reproduce** Steps to reproduce the behavior: 1. run otomi CLI command and observe that you are...

bug

# WHY The Otomi SHELL replaces the DOWNLOAD KUEBCFG functionality. After Talk with Jeho: - How to handle deprecation? - Show latest major release notes on dashboard - Add a...

Story
on hold

**Describe the bug:** (a clear and concise description of what the bug is) **To Reproduce** Steps to reproduce the behavior: 1. Got to github action and trigger `Deploy Otomi` job...

bug