Comments (6)
As discussed in the community meeting, we should the name External Secrets Operator
for the Helm chart.
from external-secrets.
Did you think something about repository?
It would be nice to have ESO and KES under the same repo but it also adds quite a bit of hassle to set that up and would be nice if the projects remained separated so KES can be deprecatedπ
I'm not really sure how the organisations work on artifacthub but I have an organisation called external-secrets there, where I migrated the KES chart after the deprecation of helm hub.
Ping me with usernames on artifacthub and I can add you to the org when that's relevant
from external-secrets.
I had some free time this weekend and gave a shot at this:
https://github.com/external-secrets/helm-charts
I set used github pages as suggested.
@Flydiverny how do you suggest to use artifacthub and what the advantage would be?
The repo is already live and can be used as follows:
β helm repo add external-secrets https://external-secrets.github.io/helm-charts/
β helm search repo external-secrets
NAME CHART VERSION APP VERSION DESCRIPTION
external-secrets/external-secrets 0.1.1 0.1.0 External secret management for Kubernetes
There is no release automation for this yet but frankly, I am not sure is necessary yet. Depending on how often releases will happen it might be worth it.
One thing that needs to be decided is where the chart should reside. Currently, I copied the chart from the main repository but we should avoid this to prevent drift. If we decide to go forward with this there are two additional tasks:
- update documentation to use the new charts repo url
- consider using the CNAME as suggested:
charts.external-secrets.io
Looking forward to your feedback.
from external-secrets.
@riccardomc I think the only benefit of artifacthub is increased discoverability. We had someone point out it was referring to the old godaddy repo in the past. which is why I made the owner claim there. Think anyone could add any repo there for it to be indexed and searchable. But seems the repo names are unique anyway.
from external-secrets.
We might also consider using this github action: https://github.com/helm/chart-releaser-action
from external-secrets.
+1 for artifacthhub β¨
One thing that needs to be decided is where the chart should reside.
Let's discuss that on wednesday. IMHO we should serve both docs
and helm chart
via github pages from this repo. But we need to be careful not overriding the helm index. I found out ingress-nginx
does it exactly that way (1 / 2 / 3).
from external-secrets.
Related Issues (20)
- GithubApp CRD is not installed through Kustomize
- Support for Azure KV Authentication with ClientCertificate HOT 7
- Installation with helm of version v0.9.17 fails HOT 2
- PushSecret doesn't create custom metadata in Vault. HOT 3
- Integration for Infisical Secret Manager HOT 3
- webhook crashlooping on certificate expiration HOT 1
- Removal of namespace qualifier for clustersecretstore fixes "invalid vault credentials: configured Vault token contains non-printable" but produces not found error in pod
- Empty String in data[].remoteRef.key in ExternalSecret when using the GitLab Provider crashses controller
- CR validation fails with ExternalSecret objects using Orphan creationPolicy HOT 2
- Empty ExternalSecret should create an empty Secret instead of not creating anything HOT 1
- Website broken link(s) for Contributing section HOT 4
- Does not send a POST request. Sends PUT
- Add IBM Power (ppc64le) support HOT 1
- ESO is not able to remove Secret fields that are not managed by itself
- Supporting not public secret stores HOT 1
- Add direct template parsing to data block
- Support for GetAllSecrets in Vault kv1? HOT 4
- Azure KeyVault PushSecret not working if SoftDelete enabled and secret in deleted state ("ObjectIsDeletedButRecoverable")
- Error whenever creating new secretStore (namespaced one) HOT 1
- No examples for Oracle Cloud Vault integration with Workload Identity HOT 13
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from external-secrets.