Skip to content

Commit 078c649

Browse files
authored
Merge pull request kubernetes-sigs#6116 from apricote/cert-manager-repo
📖 Update cert-manager links after migration
2 parents dddc320 + f02a649 commit 078c649

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

cmd/clusterctl/client/config/cert_manager.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ package config
1919
// CertManager defines cert-manager configuration.
2020
type CertManager interface {
2121
// URL returns the name of the cert-manager repository.
22-
// If empty, "https://github.com/jetstack/cert-manager/releases/latest/cert-manager.yaml" will be used.
22+
// If empty, "https://github.com/cert-manager/cert-manager/releases/latest/cert-manager.yaml" will be used.
2323
URL() string
2424

2525
// Version returns the cert-manager version to install.

docs/book/src/clusterctl/configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ the environment variable takes precedence.
5757
While doing init, clusterctl checks if there is a version of cert-manager already installed. If not, clusterctl will
5858
install a default version.
5959

60-
By default, cert-manager will be fetched from `https://github.com/jetstack/cert-manager/releases`; however, if the user
60+
By default, cert-manager will be fetched from `https://github.com/cert-manager/cert-manager/releases`; however, if the user
6161
wants to use a different repository, it is possible to use the following configuration:
6262

6363
```yaml

docs/book/src/developer/guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ The generated binary can be found at ./hack/tools/bin/envsubst
8181
You'll need to deploy [cert-manager] components on your [management cluster][mcluster], using `kubectl`
8282

8383
```bash
84-
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.yaml
84+
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.5.3/cert-manager.yaml
8585
```
8686

8787
Ensure the cert-manager webhook service is ready before creating the Cluster API components.
@@ -92,7 +92,7 @@ This can be done by running:
9292
kubectl wait --for=condition=Available --timeout=300s apiservice v1beta1.webhook.cert-manager.io
9393
```
9494

95-
[cert-manager]: https://github.com/jetstack/cert-manager
95+
[cert-manager]: https://github.com/cert-manager/cert-manager
9696

9797
## Development
9898

docs/book/src/developer/providers/implementers-guide/building_running_and_testing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,11 @@ The approach most Cluster API projects is using [a `Makefile` that uses `sed` to
1919
Cluster API uses [cert-manager] to manage the certificates it needs for its webhooks.
2020
Before you apply Cluster API's yaml, you should [install `cert-manager`][cm-install]
2121

22-
[cert-manager]: https://github.com/jetstack/cert-manager
22+
[cert-manager]: https://github.com/cert-manager/cert-manager
2323
[cm-install]: https://cert-manager.io/docs/installation/
2424

2525
```
26-
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/<version>/cert-manager.yaml
26+
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/<version>/cert-manager.yaml
2727
```
2828

2929
### Cluster API

0 commit comments

Comments
 (0)