Repository Move!

[Flydiverny]

Kubernetes External Secrets has moved to a new home in the external-secrets organization.

This might cause a few issues for you!

• The old repository URL of https://godaddy.github.io/kubernetes-external-secrets/index.yaml will no longer work!
  Please change your repository to point to https://external-secrets.github.io/kubernetes-external-secrets/index.yaml

helm repo remove external-secrets
helm repo add external-secrets https://external-secrets.github.io/kubernetes-external-secrets/

Will try to update this issue with relevant changes :)
I'm guessing the image repository will change as well and there will be a new release out in connection to that :)

[jonatasbaldin]

If anything else changes because of the move, let's please document here. I'll link this issue in the README header, so people can easily find it.

[jonatasbaldin]

What is happening? 🤔

Multiple people/companies are joining efforts to create a standard way to manage External Secrets within Kubernetes and one of our first steps was to move the repository to a vendor neutral organization.

We are bootstrapping a new project written in Golang, based on this and this project, since that's the major language of choice in the Kubernetes space.

Once the new solution is ready, tested and stable, we will replace this current project, with the proper deprecation warnings and migration instructions.

This project will keep receiving normal updates from its community and maintainers.

If you want to participate in this exciting new organization, please reach out in the #external-secrets channel on the Kubernetes Slack.

[hayao-k]

It seems that the old URL is still listed on Artifact HUB.
Sorry if I shouldn't have written here.
https://artifacthub.io/packages/helm/external-secrets/kubernetes-external-secrets

[shay-berman]

Hi @jonatasbaldin , few questions about your comments of what happening:

1. Any estimation when the new project will be ready? And whats his github link?
2. Does the migration plan for the new project going to be disruptive for the pods?
3. If we need to use external secret for our k8s application, is it the right path to use this project kubernetes-external-secrets and later on to migrate? or its better to use alternative and return back once the new project is stable?

Thanks

[jonatasbaldin]

Hi @shay-berman!

1. We are having by-weekly meetings to discuss what we are doing, but we have no estimation yet. You can find the project here.
2. It will probably be disruptive on the controller side since we are working on a new CRD spec. We will try to make it not disruptive on the Pods using the generated secrets though, but it's too early to be 100% confident there.
3. We suggest to use one of the following three projects for now and migrating to the new solution once it's stable (we will let everyone now):

• https://github.com/external-secrets/kubernetes-external-secrets
• https://github.com/ContainerSolutions/externalsecret-operator
• https://github.com/itscontained/secret-manager

Hope this answers all of your questions!

Cheers,

[Geethree]

Mildly curious if it was ever discussed getting this into the k8s sigs?

https://github.com/kubernetes-sigs

[Flydiverny]

KES 6.1.0 has been released using the new container registry on github!

https://github.com/orgs/external-secrets/packages/container/package/kubernetes-external-secrets

6.1.0 (2020-12-22)

Features

• add general support for isBinary for all backends (#585) (e138a28)
• restart watcher if no events seen for specified period (default 60 sec) (#532) (bb1ed9e)
• helm: add the ability to set the priorityClassName (#534) (e719c87)
• metrics: add metrics names following Prometheus best practices, deprecating old metrics names! (#540) (5b5a00f)

Bug Fixes

• values: imagePullSecrets was wrongly indented under image (#577) (7861473), closes #522
• configure nestedKey in logger to avoid invalid json (#568) (a430320)
• deps: bumping @grpc/grpc-js to 1.1.8 (#550) (4e88026)
• deps: bumping lodash from 4.17.19 to 4.17.20 (#545) (6c9d60d)

[jonatasbaldin]

@Geethree yeah, we discussed it! It's a long road to get there, but we will totes try for it :)

[Geethree]

Gotcha. I’m curious if/how the community could help with that process?

…

On Sun, Jan 3, 2021 at 11:56 PM Jonatas Baldin ***@***.***> wrote: @Geethree <https://github.com/Geethree> yeah, we discussed it! It's a long road to get there, but we will totes try for it :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#554 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABC5MLUZ3JK757W7ZYEJLPTSYFYEHANCNFSM4TX4WGMA> .

[jonatasbaldin]

We still don't know how @Geethree 😅 Our first priority is to get the code base to a stable state, then we will discuss the steps to get into a SIG or something like it!

If you wanna help around, please join us on the Kubernetes Slack :)

[yitsushi]

Once the new solution is ready, tested and stable, we will replace this current project, with the proper deprecation warnings and migration instructions.

Is there any migration documentation somewhere? Where can I find it if it exists, I tried to find, but I couldn't land on success.