mirrors/external-secrets
1
0
Fork 0
mirror of https://github.com/external-secrets/external-secrets.git synced 2024-12-14 11:57:59 +00:00
Code Activity

chore: deprecate olm proposal (#4175)

Browse source 
* chore: deprecate olm proposal

Signed-off-by: Gustavo Carvalho <gusfcarvalho@gmail.com>

* fix: mark as approved on community meeting

Signed-off-by: Gustavo Carvalho <gusfcarvalho@gmail.com>

---------

Signed-off-by: Gustavo Carvalho <gusfcarvalho@gmail.com>
This commit is contained in:
Gustavo Fernandes de Carvalho 2024-12-04 13:48:31 -03:00 committed by GitHub
parent fdf85f4984
commit bd3511601c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 43 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
design/011-deprecate-olm.md Normal file
View file

@ -0,0 +1,43 @@
```yaml
---
title: Deprecaation of OLM Builds
authors: @gusfcarvalho
creation-date: 2024-12-04
status: approved
---
```
This Proposal was approved on community meeting of 4th december 2024 (meeting notes: https://hackmd.io/GSGEpTVdRZCP6LDxV3FHJA?both)
# Deprecaation of OLM Builds
## Introduction
As part of our Release process, we currently build & maintain several docker images, helm releases, bundle manifests for users, and OLM builds via a community effort based on olm helm operator.
However, OLM helm operator itself would require a better support and constant maintenance, and its process when building OLM builds is already not automated anymore.
## Summary
Stpo building OLM Releases
## Motivation
Make maintenance lives easier for a project that is struggling to get maintainers together :)
### Goals
Remove OLM builds as part of our build assets
## Proposal
Archive repository & communicate on next release within the release notes.
### API
None
### Behavior
None
### Drawbacks
Users might complain - but then they can fork the archived repository to build their own OLM builds locally.
## Alternatives
Find community members to handle the maintanence aspect of it. Have a new dedicated OLM repository in/out of the org. Make this be maintained by other parties than external-secrets maintainers.
Do not use the current olm helm operator anymore as anyways this is not really supported.