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

[Story]: Validate Use-Cases #1914

Closed
andrewballantyne opened this issue Oct 5, 2023 · 2 comments
Closed

[Story]: Validate Use-Cases #1914

andrewballantyne opened this issue Oct 5, 2023 · 2 comments
Assignees
Labels
feature/ossm OpenShift Service Mesh kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.

Comments

@andrewballantyne
Copy link
Member

andrewballantyne commented Oct 5, 2023

Goal

Validate OSSM use-case scenarios

Dependency issue

Itemized goals

Here are some high level test scenarios — we’ll really need QE to spend some time thinking about these, but these are a good start. Vet for what you think it should do. Log bugs for issues.

  1. Fully Disabled

    Supported, noop

    • Pre-reqs
      • Disabled feature flag
      • No Service Mesh installed
    • Steps
      • Create DS Project; Expect: No enabled state annotation
      • Create Workbench; Expect: Route to work with oauth proxy
  2. Flag Disabled

    not valid -- Service Mesh enables feature flag

    • Pre-reqs
      • Disabled feature flag
      • Install Service Mesh
    • Steps
      • Create DS Project; Expect: Project has annotations
      • Create Workbench; Expect: Route to work with oauth proxy
  3. Install Service Mesh - fresh path

    supported, standard flow

    • Pre-reqs
      • No projects
      • Install Service Mesh
      • Enabled feature flag
    • Steps
      • Create DS Project; Expect: State flags enabled
      • Create Workbench; Expect: Route to use Istio proxy
  4. Install Service Mesh - post DS Projects install

    needs docs, looking for dashboard label; problem for OpenShift Projects

    • Pre-reqs
      • At Start: No Service Mesh installed
      • Have two projects
        • A: service-mesh = true — does not have annotations
        • B: service-mesh = false — does not have annotations
    • Steps
      • Install Service Mesh, once finished:
      • Expect: project A to migrate on install & new workbenches to use Istio proxy
      • Expect: project B to NOT migrate on install (no annotation change); new and existing workbenches use oauth proxy
  5. Test Upgrade

    Supported as scenario 4 for Data Science projects (needs docs)

    • Do scenario 2 (flag disabled) again & follow up with:
      • Enable Feature Flag
      • Re-rollout pods (operator will do this when image references change)
  6. Flag Enabled / No Service Mesh

    Remove flag, not a scenario anymore

    • Pre-reqs
      • Enabled feature flag
      • No Service Mesh installed
    • Steps
      • Create DS Project; Expect: No enabled state annotation
      • Create Workbench; Expect: Route to use oauth proxy

Aspects continued elsewhere

  • [Andrew] Ask the Operator folks about reading DSCI and getting service mesh status
    • Is there ever a reason to not use service mesh in the UI while it is installed

Mocks

N/A

@andrewballantyne andrewballantyne added priority/high Important issue that needs to be resolved asap. Releases should not have too many of these. kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. labels Oct 5, 2023
@andrewballantyne andrewballantyne moved this from Untriaged to Dev To do in ODH Dashboard Planning Oct 5, 2023
@andrewballantyne andrewballantyne added the feature/ossm OpenShift Service Mesh label Oct 30, 2023
@andrewballantyne
Copy link
Member Author

@cam-garrison any update here?

@andrewballantyne
Copy link
Member Author

We talked about this today. I've updated the topic. We can consider this ticket done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/ossm OpenShift Service Mesh kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.
Projects
Status: Done
Status: No status
Archived in project
Development

No branches or pull requests

2 participants