2
0
Fork
You've already forked extensions
0
No description
  • Go 96.7%
  • Shell 2.7%
  • Dockerfile 0.3%
  • Makefile 0.3%
Finn a9735a3f91
All checks were successful
/ build-container (push) Successful in 17s
/ Build entanglement-garden-cluster-bootstrap binary (push) Successful in 6m44s
/ Build container image (push) Successful in 3m2s
/ Build Oathkeeper container image (push) Successful in 53s
/ lint (push) Successful in 2m44s
fix cluster-bootstrap/go.*
2023年12月08日 23:37:02 -08:00
.forgejo/workflows move cluster-bootstrap to it's own module 2023年11月29日 02:39:05 -08:00
cluster-bootstrap fix cluster-bootstrap/go.* 2023年12月08日 23:37:02 -08:00
extensions go mod tidy in extensions/ module 2023年10月31日 09:46:19 -07:00
server webhook: use common retryer 2023年12月08日 20:41:09 -08:00
supporting-containers lots of refactor to make the install work 2023年10月27日 23:58:59 -07:00
web/internal/openapi update README and fix CI 2023年09月11日 23:51:15 -07:00
.gitignore move cluster-bootstrap to it's own module 2023年11月29日 02:39:05 -08:00
ci-build.sh move cluster-bootstrap to it's own module 2023年11月29日 02:39:05 -08:00
container-local-build-and-push.sh Deliver webhook notification when a new extension is registered 2023年11月29日 21:41:13 -08:00
Containerfile lots of refactor to make the install work 2023年10月27日 23:58:59 -07:00
README.md lots of refactor to make the install work 2023年10月27日 23:58:59 -07:00
version.sh lots of refactor to make the install work 2023年10月27日 23:58:59 -07:00

Entanglement Extensions

This repository contains the extensions microservice. It will install, update and remove other extensions.

Currently, it is not capable of doing anything other than installing/updating the default core extensions, including itself.

modules

  • extensions - common code expected to be used by other extensions
  • server - the microservice
  • web (eventually) the webui for the microservice

local dev

minikube start
cd server/
EG_INSTALL_DATA=dev-install-data.json go run ./cmd/cluster-bootstrap

Outstanding major features

in no particular order

  • issue API keys to deployed extensions
  • check for updates + load new extensions that aren't hard-coded
  • notify other components about changes to active extensions
    • iam, ingress and webui will all need to know all active extensions
  • webui
  • remove/pause extension
  • provision superuser during install
    • not currently clear how the human will be receiving the password, seems suboptimal to have it passed in via InstallData
    • previous iterations have provisioned a user with a static password (changeme)
    • might also be good to add some way for the superadmin to get admin on k8s