Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(registry): using etcd storage for chartmuseum #1328

Merged
merged 1 commit into from
Jun 2, 2021

Conversation

jianzzz
Copy link
Contributor

@jianzzz jianzzz commented May 30, 2021

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind feature

What this PR does / why we need it:
Chartmuseum supports etcd storage, see https://github.com/helm/chartmuseum#using-with-etcd.
The use of etcd to store chart is supported first, and the minimal run of TKEStack is supported next.
We should replace the version of storage and etcd, you can see the details in the go.mod file.
Refer to choujimmy/storage#1

Refer to #1300

We don't need installer change to make this feature as built-in. This is an optional option at this stage.
The relevant configuration is as follows:

apiVersion: registry.config.tkestack.io/v1
kind: RegistryConfiguration
storage:
  etcd:
    cafile: "/app/certs/etcd-ca.crt"
    certfile: "/app/certs/etcd.crt"
    keyfile: "/app/certs/etcd.key"
    endpoints:
      - "https://etcd.kube-system:2379"
    prefix: "/chart_backend_bucket"
  fileSystem:
    rootDirectory: /storage
  delete:
    enabled: true

@leoryu leoryu merged commit c70a9cd into tkestack:master Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants