Skip to content

replicatedhq/ekco

Folders and files

NameName
Last commit message
Last commit date

Latest commit

f8112c4 · Mar 20, 2025
Feb 10, 2025
Jan 12, 2024
May 15, 2024
Mar 20, 2025
Dec 7, 2021
Sep 6, 2022
Sep 6, 2022
Feb 24, 2020
Apr 12, 2024
Feb 22, 2023
Mar 20, 2025
Mar 20, 2025

Repository files navigation

Embedded kURL cluster operator (EKCO)

EKCO is responsible for performing various operations to maintain the health of a kURL cluster.

Documentation

Test manually

Deprecated

make docker-image
kubectl apply -k deploy/

This method is very much out of sync and doesn't work. The current best way to test is to deploy a kurl cluster and modify the deployment to pull the docker container produced as part of development.

Steps

  1. make build-ttl.sh - Build the docker container for the current development environment and deploy it to ttl.sh
  2. Deploy a kurl cluster that includes ecko and any other requirements for testing.
  3. kubectl edit -n kurl deployment/ekc-operator
    1. Replace .spec.image with your ttl.sh image
    2. Replace .spec.imagePullPolicy with "Always"
    3. kubectl delete pod -l app=ekc-operator -n kurl - Delete the pod in the deployment to pull the new image

Release

To make a new release push a tag in the format v[0-9]+\.[0-9]+\.[0-9]+(-[0-9a-z-]+)?.

git tag -a v0.1.0 -m "Release v0.1.0" && git push origin v0.1.0