Skip to content

Define k8s workload manifest for backend component #324

Open
@andyatmiami

Description

@andyatmiami

🛑 Blocked by #323

Description

Presently, the only way to run the backend component is by invoking it locally on your machine. We must be able to run this component on kubernetes while also providing sufficient tooling to enable developers working on the component to easily deploy / undeploy the workload.

Acceptance Criteria

  • Implementation is kustomize-compatible (but no overlays directory need necessarily be defined)
  • Workload can be successfully deployed to k8s (enter READY state) using a deploy Makefile target
  • Workload can be successfully undeployed from k8s using an undeploy Makefile target
  • API endpoints function appropriately when workload running on cluster

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/backendarea - related to backend componentsarea/v2area - version - kubeflow notebooks v2

    Type

    No type

    Projects

    Status

    Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions