Skip to content

tracking: glasskube package #2181

@cdxker

Description

@cdxker

Description

Wanting to migrate from helm exclusivley to Glasskube. Mainly for easier management of different custom releases and having databases be configured better via the helm chart

  • Refactor helm chart to remove database. (Swap to using external Glasskube packages) feat: add glasskube installation instructions #2266
    • Qdrant Glasskube packges
  • security: configure secret references to pull from databases (instead of envs / values.yaml) feat: add glasskube installation instructions #2266
    • security: onfigure keycloak realm and push OIDC SECRET into secret that server references
    • security: setup other server secretmaps (postgres, clickhouse, s3, etc)
    • cleanup: server and workers share the same configmap. (easier to maintain instead of copy/pasting envs)
  • Deployment process
    • Trieve release bot
    • Add release please bot
    • Tagged docker images based on git tag
    • helm chart "safe enough" to be pushed to Dockerhub
      • helm chart build/push CI action
  • Create Glasskube package pull request. Add to docs. (For minikube cpu based setup).
  • docs: update documentation for how to release via glasskube

Community channels

Matrix is preferred. Reach out on discord or Matrix for further assistance.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions