Skip to content

Commit

Permalink
Merge pull request #6123 from k8s-infra-cherrypick-robot/cherry-pick-…
Browse files Browse the repository at this point in the history
…6116-to-release-1.1

📖 Update cert-manager links after migration
  • Loading branch information
k8s-ci-robot authored Feb 14, 2022
2 parents 7ee79fe + 7278d9d commit fec2feb
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion cmd/clusterctl/client/config/cert_manager.go
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ package config
// CertManager defines cert-manager configuration.
type CertManager interface {
// URL returns the name of the cert-manager repository.
// If empty, "https://github.com/jetstack/cert-manager/releases/latest/cert-manager.yaml" will be used.
// If empty, "https://github.com/cert-manager/cert-manager/releases/latest/cert-manager.yaml" will be used.
URL() string

// Version returns the cert-manager version to install.
Expand Down
2 changes: 1 addition & 1 deletion docs/book/src/clusterctl/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ the environment variable takes precedence.
While doing init, clusterctl checks if there is a version of cert-manager already installed. If not, clusterctl will
install a default version.

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

```yaml
Expand Down
4 changes: 2 additions & 2 deletions docs/book/src/developer/guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ The generated binary can be found at ./hack/tools/bin/envsubst
You'll need to deploy [cert-manager] components on your [management cluster][mcluster], using `kubectl`

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

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

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

## Development

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,11 @@ The approach most Cluster API projects is using [a `Makefile` that uses `sed` to
Cluster API uses [cert-manager] to manage the certificates it needs for its webhooks.
Before you apply Cluster API's yaml, you should [install `cert-manager`][cm-install]

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

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

### Cluster API
Expand Down

0 comments on commit fec2feb

Please sign in to comment.