Skip to content

docs: remove outdated etcd-druid CRD manual installation steps#4039

Merged
kcp-ci-bot merged 1 commit into
kcp-dev:mainfrom
Krone-Business-Center-DigITal-Gmbh:docs/remove-obsolete-etcd-crd-steps
Apr 20, 2026
Merged

docs: remove outdated etcd-druid CRD manual installation steps#4039
kcp-ci-bot merged 1 commit into
kcp-dev:mainfrom
Krone-Business-Center-DigITal-Gmbh:docs/remove-obsolete-etcd-crd-steps

Conversation

@rose-krone
Copy link
Copy Markdown
Contributor

@rose-krone rose-krone commented Apr 17, 2026

Summary

Upgrade the etcd-druid version to 0.36.1 and remove the needed workaround section for the crds. The linked issue in the etcd-druid project is solved.

What Type of PR Is This?

/kind cleanup
/kind documentation

Related Issue(s)

none

Release Notes

Update etcd-druid version in ref architectures

Signed-off-by: Rene Rose <rene.rose@krone.de>
@kcp-ci-bot kcp-ci-bot added dco-signoff: yes Indicates the PR's author has signed the DCO. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/documentation Categorizes issue or PR as related to documentation. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 17, 2026
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

Hi @rose-krone. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@mjudeikis
Copy link
Copy Markdown
Contributor

/ok-to-test
Thanks @rose-krone , did you test this? Are CRDs now auto-installed?

@kcp-ci-bot kcp-ci-bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 17, 2026
@rose-krone
Copy link
Copy Markdown
Contributor Author

Yes I have installed the etcd druid chart in a empty cluster:

╰$ k get customresourcedefinitions.apiextensions.k8s.io | grep etcd                                                                                              
╭─INTRANET\roser@vd600008 in ~/Downloads 
╰$ helm install etcd-druid oci://europe-docker.pkg.dev/gardener-project/releases/charts/gardener/etcd-druid \
  --namespace etcd-druid \
  --create-namespace \
  --version v0.36.1
Pulled: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/etcd-druid:v0.36.1
Digest: sha256:b670e8d5d0c0a20a5598a68df0c432c1e2dd54ed98251a6f6920c6d0cefa190c
NAME: etcd-druid
LAST DEPLOYED: Fri Apr 17 08:11:42 2026
NAMESPACE: etcd-druid
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Etcd-Druid operator has been deployed to Namespace etcd-druid
Following resources has been deployed with name "etcd-druid":
 * Operator Deployment
 * Service
 * ServiceAccount
 * ClusterRole
 * ClusterRoleBinding

NOTE: Etcd cluster resource protection webhook has not been enabled. etcd-druid operator will
not be able to protect against any accidental deletion of resources that are created for an Etcd Cluster.
To read more about Etcd cluster resource protection see https://gardener.github.io/etcd-druid/deployment/configure-etcd-druid.html#etcd-components-webhook
To enable 'Etcd cluster resource protection webhook' you can set ".Values.operatorConfig.webhooks.etcdComponentProtection.enabled" (in 'charts/values.yaml' file) to true and re-install the chart.

Now that you have deployed etcd-druid operator you can create Etcd clusters by following the 'Getting Started Guide'.
See: https://gardener.github.io/etcd-druid/deployment/getting-started-locally/getting-started-locally.html#04-preparing-etcd-cr
Etcd examples are present at https://github.com/gardener/etcd-druid/tree/master/examples
╭─INTRANET\roser@vd600008 in ~/Downloads 
╰$ k get customresourcedefinitions.apiextensions.k8s.io | grep etcd                                          
etcdcopybackupstasks.druid.gardener.cloud               2026-04-17T06:11:39Z
etcdopstasks.druid.gardener.cloud                       2026-04-17T06:11:39Z
etcds.druid.gardener.cloud                              2026-04-17T06:11:39Z

@mjudeikis
Copy link
Copy Markdown
Contributor

/lgtm
/approve

thanks for this :)

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 17, 2026
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 078a7dbd0d2d5d8dbd63e93ac59e8ae541e9d837

@kcp-ci-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mjudeikis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 17, 2026
@kcp-ci-bot kcp-ci-bot merged commit c1b5fb3 into kcp-dev:main Apr 20, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants