Skip to content

Commit

Permalink
Fixed broken links (gardener#8230)
Browse files Browse the repository at this point in the history
  • Loading branch information
n-boshnakov authored Jul 13, 2023
1 parent 45b6050 commit aa55aa7
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/usage/shoot_credentials_rotation.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ End-users must provide credentials such that Gardener and Kubernetes controllers
For example, Gardener uses them to setup and maintain the networks, security groups, subnets, etc., while the [cloud-controller-manager](https://kubernetes.io/docs/concepts/architecture/cloud-controller/) uses them to reconcile load balancers and routes, and the [CSI controller](https://kubernetes-csi.github.io/docs/) uses them to reconcile volumes and disks.

Depending on the cloud provider, the required [data keys of the `Secret` differ](https://github.com/gardener/gardener/blob/master/example/70-secret-provider.yaml).
Please consult the documentation of the respective provider extension documentation to get to know the concrete data keys (e.g., [this document for AWS](https://github.com/gardener/gardener-extension-provider-aws/blob/master/docs/usage-as-end-user.md#provider-secret-data)).
Please consult the documentation of the respective provider extension documentation to get to know the concrete data keys (e.g., [this document for AWS](https://github.com/gardener/gardener-extension-provider-aws/blob/master/docs/usage/usage.md#provider-secret-data)).

**It is the responsibility of the end-user to regularly rotate those credentials.**
The following steps are required to perform the rotation:
Expand Down
2 changes: 1 addition & 1 deletion docs/usage/shoot_versions.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Patch releases are done more frequently.

When using the term `Machine image` in the following, we refer to the OS version that comes with the machine image of the node/worker pool of a Gardener Shoot cluster.
As such, we are not referring to the `CloudProvider` specific machine image like the [`AMI`](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html) for AWS.
For more information on how Gardener maps machine image versions to `CloudProvider` specific machine images, take a look at the individual gardener extension providers, such as the [provider for AWS](https://github.com/gardener/gardener-extension-provider-aws/blob/master/docs/usage-as-operator.md).
For more information on how Gardener maps machine image versions to `CloudProvider` specific machine images, take a look at the individual gardener extension providers, such as the [provider for AWS](https://github.com/gardener/gardener-extension-provider-aws/blob/master/docs/operations/operations.md).

Gardener should be configured accordingly to reflect the "logical state" of a version.
It should be possible to define the Kubernetes or Machine image versions that still receive bug fixes and security patches, and also vice-versa to define the version that are out-of-maintenance and are potentially vulnerable.
Expand Down

0 comments on commit aa55aa7

Please sign in to comment.