kubernetes-sigs / external-dns

Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
Apache License 2.0
7.58k stars 2.54k forks source link

Minikube externaldns + coredns documentation is out of date #4723

Closed k8s-1 closed 1 week ago

k8s-1 commented 1 week ago

What happened: Followed https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/coredns.md, starting with the install of etcd-operator. The helm chart no longer exists so I checked out coreos/etcd-operator.

There, I discovered that the etcd-operator repository has been in archive-mode since 2020, e.g. applying example resources from this repository using deprecated kubernetes api resources: resource mapping not found for name: "etcd-operator" namespace: "" from "cluster-role.yaml": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1"

What you expected to happen: No errors, coredns and external-dns deployed.

How to reproduce it (as minimally and precisely as possible): Follow coreDNS + external-dns minikube documentation Client Version: v1.30.3 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.31.0

Anything else we need to know?: etcd-operator has been archived since 2020

Environment: n/a since I could not install anything

k8s-1 commented 1 week ago

/label docs

k8s-ci-robot commented 1 week ago

@k8s-1: The label(s) /label docs cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/4723#issuecomment-2328333344): >/label docs Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.