From 8fc44c291c562c04a5501e7b32fc79cb6d054b2a Mon Sep 17 00:00:00 2001 From: gardener-robot-ci-1 Date: Sat, 9 Nov 2024 17:49:16 +0000 Subject: [PATCH] Automatic build triggered by last commit --- docs/404.html | 4 +- docs/_print/adopter/index.html | 4 +- docs/_print/community/index.html | 4 +- docs/_print/contribute/docs/index.html | 4 +- docs/_print/docs/contribute/code/index.html | 4 +- docs/adopter/index.html | 4 +- docs/blog/2018/06.11-anti-patterns/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../2018/06.11-namespace-isolation/index.html | 9 +- .../2018/06.11-namespace-scope/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../12.22-cookies-are-dangerous/index.html | 9 +- .../2018/12.25-gardener_cookies/index.html | 9 +- docs/blog/2018/_print/index.html | 4 +- docs/blog/2018/index.html | 9 +- docs/blog/2018/page/2/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- docs/blog/2019/_print/index.html | 4 +- docs/blog/2019/index.html | 9 +- .../index.html | 9 +- .../2020/05.27-pingcaps-experience/index.html | 9 +- .../08.06-gardener-v1.8.0-released/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../11.23-gardener-v1.13-released/index.html | 9 +- .../index.html | 9 +- docs/blog/2020/_print/index.html | 4 +- docs/blog/2020/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- docs/blog/2021/_print/index.html | 4 +- docs/blog/2021/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- docs/blog/2022/_print/index.html | 4 +- docs/blog/2022/index.html | 9 +- .../index.html | 9 +- docs/blog/2023/_print/index.html | 4 +- docs/blog/2023/index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 9 +- .../index.html | 20 +- .../2024/11-06-promcon-eu-2024/index.html | 11 +- docs/blog/2024/11-09-demo/index.html | 173 ++++ docs/blog/2024/11/09/01/index.html | 1 + docs/blog/2024/_print/index.html | 19 +- docs/blog/2024/index.html | 13 +- docs/blog/2024/index.xml | 25 +- docs/blog/_print/index.html | 19 +- docs/blog/index.html | 16 +- docs/blog/index.xml | 25 +- docs/blog/page/2/index.html | 14 +- docs/blog/page/3/index.html | 13 +- docs/blog/page/4/index.html | 11 +- docs/community/index.html | 4 +- docs/contribute/docs/index.html | 4 +- docs/curated-links/index.html | 4 +- docs/docs/_print/index.html | 4 +- docs/docs/contribute/_print/index.html | 4 +- docs/docs/contribute/code/cicd/index.html | 4 +- .../contributing-bigger-changes/index.html | 4 +- .../contribute/code/dependencies/index.html | 4 +- docs/docs/contribute/code/index.html | 4 +- .../code/security-guide/_print/index.html | 4 +- .../contribute/code/security-guide/index.html | 4 +- .../adding-existing-documentation/index.html | 4 +- .../documentation/formatting-guide/index.html | 4 +- .../documentation/images/index.html | 4 +- .../documentation/markup/index.html | 4 +- .../documentation/organization/index.html | 4 +- .../documentation/pr-description/index.html | 4 +- .../documentation/shortcodes/index.html | 4 +- .../style-guide/_print/index.html | 4 +- .../style-guide/concept_template/index.html | 4 +- .../documentation/style-guide/index.html | 4 +- .../style-guide/reference_template/index.html | 4 +- .../style-guide/task_template/index.html | 4 +- docs/docs/contribute/index.html | 4 +- docs/docs/dashboard/_print/index.html | 4 +- .../dashboard/access-restrictions/index.html | 4 +- docs/docs/dashboard/architecture/index.html | 4 +- .../automated-resource-management/index.html | 4 +- .../docs/dashboard/connect-kubectl/index.html | 4 +- docs/docs/dashboard/custom-fields/index.html | 4 +- docs/docs/dashboard/customization/index.html | 4 +- docs/docs/dashboard/index.html | 4 +- docs/docs/dashboard/local-setup/index.html | 4 +- docs/docs/dashboard/process/index.html | 4 +- .../dashboard/project-operations/index.html | 4 +- .../dashboard/terminal-shortcuts/index.html | 4 +- docs/docs/dashboard/testing/index.html | 4 +- docs/docs/dashboard/using-terminal/index.html | 4 +- docs/docs/dashboard/webterminals/index.html | 4 +- .../working-with-projects/index.html | 4 +- docs/docs/extensions/_print/index.html | 4 +- .../_print/index.html | 4 +- .../_print/index.html | 4 +- .../index.html | 4 +- .../container-runtime-extensions/index.html | 4 +- docs/docs/extensions/index.html | 4 +- .../_print/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../local-setup/index.html | 4 +- .../operations/index.html | 4 +- .../tutorials/_print/index.html | 4 +- .../tutorials/index.html | 4 +- .../index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../dual-stack-ingress/index.html | 4 +- .../index.html | 4 +- .../local-setup/index.html | 4 +- .../operations/index.html | 4 +- .../index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../azure-permissions/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../local-setup/index.html | 4 +- .../migrate-loadbalancer/index.html | 4 +- .../operations/index.html | 4 +- .../tutorials/_print/index.html | 4 +- .../tutorials/index.html | 4 +- .../index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../index.html | 4 +- .../operations/index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../local-setup/index.html | 4 +- .../operations/index.html | 4 +- .../datadisk-image-restore/index.html | 4 +- .../tutorials/_print/index.html | 4 +- .../tutorials/index.html | 4 +- .../index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../local-setup/index.html | 4 +- .../operations/index.html | 4 +- .../usage/index.html | 4 +- .../infrastructure-extensions/index.html | 4 +- .../network-extensions/_print/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../operations/index.html | 4 +- .../shoot_overlay_network/index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../index.html | 4 +- .../usage/index.html | 4 +- .../extensions/network-extensions/index.html | 4 +- .../os-extensions/_print/index.html | 4 +- .../_print/index.html | 4 +- .../gardener-extension-os-coreos/index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../index.html | 4 +- .../_print/index.html | 4 +- .../index.html | 4 +- .../usage/index.html | 4 +- .../_print/index.html | 4 +- .../gardener-extension-os-ubuntu/index.html | 4 +- .../usage/index.html | 4 +- docs/docs/extensions/os-extensions/index.html | 4 +- docs/docs/extensions/others/_print/index.html | 4 +- .../_print/index.html | 4 +- .../extension-registry-cache/index.html | 4 +- .../getting-started-locally/index.html | 4 +- .../getting-started-remotely/index.html | 4 +- .../index.html | 4 +- .../registry-cache/configuration/index.html | 4 +- .../upstream-credentials/index.html | 4 +- .../registry-mirror/configuration/index.html | 4 +- .../_print/index.html | 4 +- .../alerting/index.html | 4 +- .../custom_shoot_issuer/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../request_cert/index.html | 4 +- .../request_default_domain_cert/index.html | 4 +- .../tutorials/gateway-api-gateways/index.html | 4 +- .../tutorials/istio-gateways/index.html | 4 +- .../index.html | 4 +- .../_print/index.html | 4 +- .../configuration/index.html | 4 +- .../deployment/index.html | 4 +- .../dns_names/index.html | 4 +- .../dns_providers/index.html | 4 +- .../index.html | 4 +- .../tutorials/gateway-api-gateways/index.html | 4 +- .../tutorials/istio-gateways/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../lakom/index.html | 4 +- .../shoot-extension/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../shoot-networking-filter/index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../index.html | 4 +- .../_print/index.html | 4 +- .../deployment/index.html | 4 +- .../index.html | 4 +- .../openidconnects/index.html | 4 +- .../_print/index.html | 4 +- .../configuration/index.html | 4 +- .../getting-started-remotely/index.html | 4 +- .../getting-started/index.html | 4 +- .../index.html | 4 +- .../monitoring/index.html | 4 +- .../shoot-rsyslog-relp/index.html | 4 +- docs/docs/extensions/others/index.html | 4 +- docs/docs/faq/_print/index.html | 4 +- docs/docs/faq/add-feature-gates/index.html | 4 +- docs/docs/faq/automatic-migrate/index.html | 4 +- docs/docs/faq/automatic-upgrade/index.html | 4 +- docs/docs/faq/backup/index.html | 4 +- docs/docs/faq/clusterhealthz/index.html | 4 +- .../faq/configure-worker-pools/index.html | 4 +- docs/docs/faq/dns-config/index.html | 4 +- docs/docs/faq/index.html | 4 +- .../docs/faq/privileged-containers/index.html | 4 +- .../docs/faq/reconciliation-impact/index.html | 4 +- docs/docs/faq/rotate-iaas-keys/index.html | 4 +- docs/docs/gardenctl-v2/index.html | 4 +- docs/docs/gardener/_print/index.html | 4 +- docs/docs/gardener/advanced/_print/index.html | 4 +- .../index.html | 4 +- .../index.html | 4 +- .../advanced/csi_components/index.html | 4 +- .../custom-containerd-config/index.html | 4 +- docs/docs/gardener/advanced/index.html | 4 +- .../advanced/node-readiness/index.html | 4 +- .../advanced/shoot_cleanup/index.html | 4 +- .../gardener/advanced/tolerations/index.html | 4 +- .../gardener/api-reference/_print/index.html | 4 +- .../api-reference/authentication/index.html | 4 +- .../gardener/api-reference/core-v1/index.html | 4 +- .../gardener/api-reference/core/index.html | 4 +- .../api-reference/extensions/index.html | 4 +- docs/docs/gardener/api-reference/index.html | 4 +- .../api-reference/operations/index.html | 4 +- .../api-reference/operator/index.html | 4 +- .../api-reference/provider-local/index.html | 4 +- .../api-reference/resources/index.html | 4 +- .../api-reference/security/index.html | 4 +- .../api-reference/seedmanagement/index.html | 4 +- .../api-reference/settings/index.html | 4 +- .../index.html | 4 +- .../gardener/autoscaling/_print/index.html | 4 +- .../autoscaling/dns-autoscaling/index.html | 4 +- docs/docs/gardener/autoscaling/index.html | 4 +- .../autoscaling/shoot_autoscaling/index.html | 4 +- .../index.html | 4 +- .../docs/gardener/changing-the-api/index.html | 4 +- .../gardener/component-checklist/index.html | 4 +- docs/docs/gardener/concepts/_print/index.html | 4 +- .../concepts/admission-controller/index.html | 4 +- .../apiserver-admission-plugins/index.html | 4 +- .../gardener/concepts/apiserver/index.html | 4 +- .../gardener/concepts/architecture/index.html | 4 +- .../concepts/backup-restore/index.html | 4 +- .../gardener/concepts/cluster-api/index.html | 4 +- .../concepts/controller-manager/index.html | 4 +- docs/docs/gardener/concepts/etcd/index.html | 4 +- .../gardener/concepts/gardenadm/index.html | 4 +- .../gardener/concepts/gardenlet/index.html | 4 +- docs/docs/gardener/concepts/index.html | 4 +- .../gardener/concepts/node-agent/index.html | 4 +- .../gardener/concepts/operator/index.html | 4 +- .../concepts/resource-manager/index.html | 4 +- .../gardener/concepts/scheduler/index.html | 4 +- docs/docs/gardener/configuration/index.html | 4 +- .../control_plane_migration/index.html | 4 +- docs/docs/gardener/defaulting/index.html | 4 +- docs/docs/gardener/dependencies/index.html | 4 +- .../gardener/deployment/_print/index.html | 4 +- .../index.html | 4 +- .../deployment/configuring_logging/index.html | 4 +- .../deployment/deploy_gardenlet/index.html | 4 +- .../deploy_gardenlet_automatically/index.html | 4 +- .../deploy_gardenlet_manually/index.html | 4 +- .../deploy_gardenlet_via_operator/index.html | 4 +- .../deployment/feature_gates/index.html | 4 +- .../gardenlet_api_access/index.html | 4 +- .../getting_started_locally/index.html | 4 +- .../index.html | 4 +- .../deployment/image_vector/index.html | 4 +- docs/docs/gardener/deployment/index.html | 4 +- .../deployment/migration_v0_to_v1/index.html | 4 +- .../index.html | 4 +- .../deployment/setup_gardener/index.html | 4 +- .../deployment/version_skew_policy/index.html | 4 +- .../gardener/extensions/_print/index.html | 4 +- .../gardener/extensions/admission/index.html | 4 +- .../extensions/ca-rotation/index.html | 4 +- .../gardener/extensions/cluster/index.html | 4 +- .../controllerregistration/index.html | 4 +- .../controlplane-webhooks/index.html | 4 +- .../extensions/conventions/index.html | 4 +- .../extensions/force-deletion/index.html | 4 +- .../extensions/garden-api-access/index.html | 4 +- .../extensions/healthcheck-library/index.html | 4 +- .../gardener/extensions/heartbeat/index.html | 4 +- docs/docs/gardener/extensions/index.html | 4 +- .../logging-and-monitoring/index.html | 4 +- .../index.html | 4 +- .../extensions/managedresources/index.html | 4 +- .../gardener/extensions/migration/index.html | 4 +- .../gardener/extensions/overview/index.html | 4 +- .../extensions/project-roles/index.html | 4 +- .../extensions/provider-local/index.html | 4 +- .../extensions/reconcile-trigger/index.html | 4 +- .../referenced-resources/index.html | 4 +- .../extensions/resources/_print/index.html | 4 +- .../resources/backupbucket/index.html | 4 +- .../resources/backupentry/index.html | 4 +- .../extensions/resources/bastion/index.html | 4 +- .../resources/containerruntime/index.html | 4 +- .../controlplane-exposure/index.html | 4 +- .../resources/controlplane/index.html | 4 +- .../extensions/resources/dnsrecord/index.html | 4 +- .../extensions/resources/extension/index.html | 4 +- .../gardener/extensions/resources/index.html | 4 +- .../resources/infrastructure/index.html | 4 +- .../extensions/resources/network/index.html | 4 +- .../operatingsystemconfig/index.html | 4 +- .../extensions/resources/worker/index.html | 4 +- .../shoot-health-status-conditions/index.html | 4 +- .../extensions/shoot-maintenance/index.html | 4 +- .../extensions/shoot-webhooks/index.html | 4 +- .../getting_started_locally/index.html | 4 +- .../index.html | 4 +- .../high-availability/_print/index.html | 4 +- .../gardener/high-availability/index.html | 4 +- .../shoot_high_availability/index.html | 4 +- .../index.html | 4 +- docs/docs/gardener/index.html | 4 +- docs/docs/gardener/ipv6/index.html | 4 +- docs/docs/gardener/istio/index.html | 4 +- .../gardener/kubernetes-clients/index.html | 4 +- docs/docs/gardener/local_setup/index.html | 4 +- docs/docs/gardener/log_parsers/index.html | 4 +- docs/docs/gardener/logging/index.html | 4 +- docs/docs/gardener/managed_seed/index.html | 4 +- .../docs/gardener/monitoring-stack/index.html | 4 +- .../gardener/monitoring/_print/index.html | 4 +- .../gardener/monitoring/alerting/index.html | 4 +- .../monitoring/connectivity/index.html | 4 +- docs/docs/gardener/monitoring/index.html | 4 +- .../gardener/monitoring/profiling/index.html | 4 +- .../docs/gardener/network_policies/index.html | 4 +- .../gardener/networking/_print/index.html | 4 +- .../networking/custom-dns-config/index.html | 4 +- .../dns-search-path-optimization/index.html | 4 +- .../networking/exposureclasses/index.html | 4 +- docs/docs/gardener/networking/index.html | 4 +- .../networking/node-local-dns/index.html | 4 +- .../index.html | 4 +- .../networking/shoot_networking/index.html | 4 +- .../gardener/new-cloud-provider/index.html | 4 +- .../new-kubernetes-version/index.html | 4 +- .../gardener/observability/_print/index.html | 4 +- docs/docs/gardener/observability/index.html | 4 +- .../gardener/observability/logging/index.html | 4 +- .../docs/gardener/priority-classes/index.html | 4 +- docs/docs/gardener/process/index.html | 4 +- docs/docs/gardener/project/_print/index.html | 4 +- docs/docs/gardener/project/index.html | 4 +- .../namespaced-cloud-profiles/index.html | 4 +- .../docs/gardener/project/projects/index.html | 4 +- .../service-account-manager/index.html | 4 +- .../gardener/reversed-vpn-tunnel/index.html | 4 +- .../gardener/secrets_management/index.html | 4 +- docs/docs/gardener/security/_print/index.html | 4 +- .../default_seccomp_profile/index.html | 4 +- .../etcd_encryption_config/index.html | 4 +- docs/docs/gardener/security/index.html | 4 +- .../security/openidconnect-presets/index.html | 4 +- .../gardener/security/pod-security/index.html | 4 +- .../security/shoot_auditpolicy/index.html | 4 +- .../security/shoot_serviceaccounts/index.html | 4 +- .../gardener/seed_bootstrapping/index.html | 4 +- docs/docs/gardener/seed_settings/index.html | 4 +- .../shoot-operations/_print/index.html | 4 +- .../docs/gardener/shoot-operations/index.html | 4 +- .../shoot_credentials_rotation/index.html | 4 +- .../shoot_operations/index.html | 4 +- .../shoot-operations/shoot_updates/index.html | 4 +- .../shoot_versions/index.html | 4 +- .../supported_k8s_versions/index.html | 4 +- .../worker_pool_k8s_versions/index.html | 4 +- docs/docs/gardener/shoot/_print/index.html | 4 +- .../shoot/access_restrictions/index.html | 4 +- docs/docs/gardener/shoot/index.html | 4 +- .../gardener/shoot/shoot_access/index.html | 4 +- .../gardener/shoot/shoot_hibernate/index.html | 4 +- .../shoot/shoot_info_configmap/index.html | 4 +- .../shoot/shoot_maintenance/index.html | 4 +- .../gardener/shoot/shoot_purposes/index.html | 4 +- .../shoot_scheduling_profiles/index.html | 4 +- .../gardener/shoot/shoot_status/index.html | 4 +- .../shoot_supported_architectures/index.html | 4 +- .../shoot/shoot_workerless/index.html | 4 +- .../shoot/shoot_workers_settings/index.html | 4 +- docs/docs/gardener/testing/index.html | 4 +- .../gardener/testmachinery_tests/index.html | 4 +- .../topology_aware_routing/index.html | 4 +- .../trusted-tls-for-control-planes/index.html | 4 +- .../trusted-tls-for-garden-runtime/index.html | 4 +- docs/docs/getting-started/_print/index.html | 4 +- .../getting-started/architecture/index.html | 4 +- .../getting-started/ca-components/index.html | 4 +- .../common-pitfalls/index.html | 4 +- .../features/_print/index.html | 4 +- .../certificate-management/index.html | 4 +- .../features/cluster-autoscaler/index.html | 4 +- .../features/credential-rotation/index.html | 4 +- .../features/dns-management/index.html | 4 +- .../features/hibernation/index.html | 4 +- docs/docs/getting-started/features/index.html | 4 +- .../getting-started/features/vpa/index.html | 4 +- .../features/workerless-shoots/index.html | 4 +- docs/docs/getting-started/index.html | 4 +- .../getting-started/introduction/index.html | 4 +- .../docs/getting-started/lifecycle/index.html | 4 +- .../observability/_print/index.html | 4 +- .../observability/alerts/index.html | 4 +- .../observability/components/index.html | 4 +- .../getting-started/observability/index.html | 4 +- .../observability/shoot-status/index.html | 4 +- docs/docs/getting-started/project/index.html | 4 +- docs/docs/getting-started/shoots/index.html | 4 +- docs/docs/glossary/_print/index.html | 4 +- docs/docs/glossary/index.html | 4 +- docs/docs/guides/_print/index.html | 4 +- .../administer-shoots/_print/index.html | 4 +- .../backup-restore/index.html | 4 +- .../conversion-webhook/index.html | 4 +- .../create-delete-shoot/index.html | 4 +- .../index.html | 4 +- .../guides/administer-shoots/gpu/index.html | 4 +- docs/docs/guides/administer-shoots/index.html | 4 +- .../maintain-shoot/index.html | 4 +- .../administer-shoots/oidc-login/index.html | 4 +- .../administer-shoots/scalability/index.html | 4 +- .../administer-shoots/tailscale/index.html | 4 +- .../guides/applications/_print/index.html | 4 +- .../access-pod-from-local/index.html | 4 +- .../applications/antipattern/index.html | 4 +- .../commit-secret-fail/index.html | 4 +- .../applications/container-startup/index.html | 4 +- .../applications/content_trust/index.html | 4 +- .../dockerfile-pitfall/index.html | 4 +- .../applications/dynamic-pvc/index.html | 4 +- .../applications/image-pull-policy/index.html | 4 +- docs/docs/guides/applications/index.html | 4 +- .../insecure-configuration/index.html | 4 +- .../applications/knative-install/index.html | 4 +- .../missing-registry-permission/index.html | 4 +- .../applications/network-isolation/index.html | 4 +- .../pod-disruption-budget/index.html | 4 +- .../guides/applications/prometheus/index.html | 4 +- .../applications/secure-seccomp/index.html | 4 +- .../service-cache-control/index.html | 4 +- .../index.html | 4 +- .../guides/client-tools/_print/index.html | 4 +- .../client-tools/bash-kubeconfig/index.html | 4 +- .../guides/client-tools/bash-tips/index.html | 4 +- docs/docs/guides/client-tools/index.html | 4 +- .../working-with-kubeconfig/index.html | 4 +- .../high-availability/_print/index.html | 4 +- .../best-practices/index.html | 4 +- .../chaos-engineering/index.html | 4 +- .../control-plane/index.html | 4 +- docs/docs/guides/high-availability/index.html | 4 +- docs/docs/guides/index.html | 4 +- .../_print/index.html | 4 +- .../analysing-node-failures/index.html | 4 +- .../debug-a-pod/index.html | 4 +- .../monitoring-and-troubleshooting/index.html | 4 +- .../shell-to-node/index.html | 4 +- .../tail-logfile/index.html | 4 +- docs/docs/guides/networking/_print/index.html | 4 +- .../index.html | 4 +- .../certificate-extension/index.html | 4 +- .../networking/dns-extension/index.html | 4 +- .../index.html | 4 +- docs/docs/guides/networking/index.html | 4 +- docs/docs/index.html | 4 +- docs/docs/other-components/_print/index.html | 4 +- .../dependency-watchdog/_print/index.html | 4 +- .../concepts/_print/index.html | 4 +- .../dependency-watchdog/concepts/index.html | 4 +- .../concepts/prober/index.html | 4 +- .../concepts/weeder/index.html | 4 +- .../contribution/index.html | 4 +- .../deployment/_print/index.html | 4 +- .../deployment/configure/index.html | 4 +- .../dependency-watchdog/deployment/index.html | 4 +- .../deployment/monitor/index.html | 4 +- .../dependency-watchdog/index.html | 4 +- .../setup/dwd-using-local-garden/index.html | 4 +- .../dependency-watchdog/testing/index.html | 4 +- .../etcd-druid/_print/index.html | 4 +- .../add-new-etcd-cluster-component/index.html | 4 +- .../etcd-druid/api-reference/index.html | 4 +- .../benchmark/etcd-network-latency/index.html | 4 +- .../etcd-druid/changing-api/index.html | 4 +- .../etcd-cluster-components/index.html | 4 +- .../index.html | 4 +- .../etcd-druid/contribution/index.html | 4 +- .../etcd-druid/controllers/index.html | 4 +- .../dependency-management/index.html | 4 +- .../configure-etcd-druid/index.html | 4 +- .../deployment/feature-gates/index.html | 4 +- .../getting-started-locally/index.html | 4 +- .../manage-azurite-emulator/index.html | 4 +- .../manage-s3-emulator/index.html | 4 +- .../index.html | 4 +- .../version-compatibility-matrix/index.html | 4 +- .../getting-started-locally/index.html | 4 +- .../other-components/etcd-druid/index.html | 4 +- .../managing-etcd-clusters/index.html | 4 +- .../etcd-druid/monitoring/metrics/index.html | 4 +- .../prepare-dev-environment/index.html | 4 +- .../proposals/00-template/index.html | 4 +- .../01-multi-node-etcd-clusters/index.html | 4 +- .../02-snapshot-compaction/index.html | 4 +- .../03-scaling-up-an-etcd-cluster/index.html | 4 +- .../04-etcd-member-custom-resource/index.html | 4 +- .../05-etcd-operator-tasks/index.html | 4 +- .../etcd-druid/raising-a-pr/index.html | 4 +- .../recovering-etcd-clusters/index.html | 4 +- .../etcd-druid/running-e2e-tests/index.html | 4 +- .../securing-etcd-clusters/index.html | 4 +- .../etcd-druid/testing/index.html | 4 +- docs/docs/other-components/index.html | 4 +- .../_print/index.html | 4 +- .../cp_support_new/index.html | 4 +- .../deployment/index.html | 4 +- .../documents/_print/index.html | 4 +- .../documents/apis/index.html | 4 +- .../documents/index.html | 4 +- .../machine-controller-manager/faq/index.html | 4 +- .../machine-controller-manager/index.html | 4 +- .../integration_tests/index.html | 4 +- .../local_setup/index.html | 4 +- .../machine/index.html | 4 +- .../machine_deployment/index.html | 4 +- .../machine_error_codes/index.html | 4 +- .../machine_set/index.html | 4 +- .../prerequisite/index.html | 4 +- .../proposals/_print/index.html | 4 +- .../excess_reserve_capacity/index.html | 4 +- .../external_providers_grpc/index.html | 4 +- .../proposals/hotupdate-instances/index.html | 4 +- .../proposals/index.html | 4 +- .../proposals/initialize-machine/index.html | 4 +- .../testing_and_dependencies/index.html | 4 +- .../todo/_print/index.html | 4 +- .../todo/index.html | 4 +- .../todo/outline/index.html | 4 +- docs/docs/resources/_print/index.html | 4 +- docs/docs/resources/index.html | 4 +- docs/docs/resources/videos/_print/index.html | 4 +- .../resources/videos/fairy-tail/index.html | 4 +- .../videos/gardener-teaser/index.html | 4 +- .../videos/in-out-networking/index.html | 4 +- docs/docs/resources/videos/index.html | 4 +- .../videos/livecheck-readiness/index.html | 4 +- .../microservices-in_kubernetes/index.html | 4 +- .../resources/videos/namespace/index.html | 4 +- .../videos/small-container/index.html | 4 +- .../videos/why-kubernetes/index.html | 4 +- .../security-and-compliance/_print/index.html | 4 +- docs/docs/security-and-compliance/index.html | 4 +- .../kubernetes-hardening/index.html | 4 +- .../partial-disa-k8s-stig-shoot/index.html | 4 +- .../regional-restrictions/index.html | 4 +- .../security-and-compliance/report/index.html | 4 +- docs/index.html | 4 +- docs/js/404.js | 810 +++++++++--------- ...ndex.0f3bdb01b6bf379426fd48a02fca37e9.json | 1 - ...ndex.29a495dd93b0b39fb590fa9c5f89feb0.json | 1 + docs/sitemap.xml | 2 +- 615 files changed, 2089 insertions(+), 1697 deletions(-) create mode 100644 docs/blog/2024/11-09-demo/index.html create mode 100644 docs/blog/2024/11/09/01/index.html delete mode 100644 docs/offline-search-index.0f3bdb01b6bf379426fd48a02fca37e9.json create mode 100644 docs/offline-search-index.29a495dd93b0b39fb590fa9c5f89feb0.json diff --git a/docs/404.html b/docs/404.html index 82fb30563a8..3d455a146c5 100644 --- a/docs/404.html +++ b/docs/404.html @@ -1,8 +1,8 @@ 404 Page not found | Gardener -

Page Not Found

We dug around, but couldn't find the page that you were looking for.

You could go back to our home page or use the search bar to find what you were looking for.

diff --git a/docs/_print/adopter/index.html b/docs/_print/adopter/index.html index 77d251d78ed..cc4c527fa09 100644 --- a/docs/_print/adopter/index.html +++ b/docs/_print/adopter/index.html @@ -12,10 +12,10 @@ SAP uses Gardener …"> -

See who is using Gardener

Gardener adopters in production environments that have publicly shared details of their usage.

teaser

SAPSAP uses Gardener to deploy and manage Kubernetes clusters at scale in a uniform way across infrastructures (AWS, Azure, GCP, Alicloud, as well as generic interfaces to OpenStack and vSphere). Workloads include Databases (SAP HANA Cloud), Big Data (SAP Data Intelligence), Kyma, many other cloud native applications, and diverse business workloads.
OVHcloudGardener can now be run by customers on the Public Cloud Platform of the leading European Cloud Provider OVHcloud.
ScaleUp TechnologiesScaleUp Technologies runs Gardener within their public Openstack Clouds (Hamburg, Berlin, Düsseldorf). Their clients run all kinds of workloads on top of Gardener maintained Kubernetes clusters ranging from databases to Software-as-a-Service applications.
Finanz Informatik Technologie Services GmbHFinanz Informatik Technologie Services GmbH uses Gardener to offer k8s as a service for customers in the financial industry in Germany. It is built on top of a “metal as a service” infrastructure implemented from scratch for k8s workloads in mind. The result is k8s on top of bare metal in minutes.
PingCAPPingCAP TiDB, is a cloud-native distributed SQL database with MySQL compatibility, and one of the most popular open-source database projects - with 23.5K+ stars and 400+ contributors. Its sister project TiKV is a Cloud Native Interactive Landscape project. PingCAP envisioned their managed TiDB service, known as TiDB Cloud, to be multi-tenant, secure, cost-efficient, and to be compatible with different cloud providers and they chose Gardener.
BeezlabsBeezlabs uses Gardener to deliver Intelligent Process Automation platform, on multiple cloud providers and reduce costs and lock-in risks.
b’nerdb’nerd uses Gardener as the core technology for its own managed Kubernetes as a Service solution and operates multiple Gardener installations for several cloud hosting service providers.
STACKITSTACKIT is a digital brand of Europe’s biggest retailer, the Schwarz Group, which includes Lidl, Kaufland, but also production and recycling companies. It uses Gardener to offer public and private Kubernetes as a service in own data centers in Europe and targets to become the cloud provider for German and European small and mid-sized companies.
T-SystemsSupporting and managing multiple application landscapes on-premises and across different hyperscaler infrastructures can be painful. At T-Systems we use Gardener both for internal usage and to manage clusters for our customers. We love the openness of the project, the flexibility and the architecture that allows us to manage clusters around the world with only one team from one single pane of glass and to meet industry specific certification standards. The sovereignty by design is another great value, the technology implicitly brings along.
23 TechnologiesThe German-based company 23 Technologies uses Gardener to offer an enterprise-class Kubernetes engine for industrial use cases as well as cloud service providers and offers managed and professional services for it. 23T is also the team behind okeanos.dev, a public service that can be used by anyone to try out Gardener.
B1 Systems GmbHB1 Systems GmbH is a international provider of Linux & Open Source consulting, training, managed service & support. We are founded in 2004 and based in Germany. Our team of 140 Linux experts offers tailor-made solutions based on cloud & container technologies, virtualization & high availability as well as monitoring, system & configuration management. B1 is using Gardener internally and also set up solutions/environments for customers.
finleap connect GmbHfinleap connect GmbH is the leading independent Open Banking platform provider in Europe. It enables companies across a multitude of industries to provide the next generation of financial services by understanding how customers transact and interact. With its “full-stack” platform of solutions, finleap connect makes it possible for its clients to compliantly access the financial transactions data of customers, enrich said data with analytics tools, provide digital banking services and deliver high-quality, digital financial services products and services to customers. Gardener uniquly enables us to deploy our platform in Europe and across the globe in a uniform way on the providers preferred by our customers.
CodesphereCodesphere is a Cloud IDE with integrated and automated deployment of web apps. It uses Gardener internally to manage clusters that host customer deployments and internal systems all over the world.
plusserverplusserver combines its own cloud offerings with hyperscaler platforms to provide individually tailored multi-cloud solutions. The plusserver Kubernetes Engine (PSKE) based on Gardener reduces the complexity in managing multi-cloud environments and enables companies to orchestrate their containers and cloud-native applications across a variety of platforms such as plusserver’s pluscloud open or hyperscalers such as AWS, either by mouseclick or via an API. With PSKE, companies remain vendor-independent and profit from guaranteed data sovereignty and data security due to GDPR-compliant cloud platforms in the certified plusserver data centers in Germany.
Fuga CloudFuga Cloud uses Gardener as the basis for its Enterprise Managed Kubernetes (EMK), a platform that simplifies the management of your k8s and provides insight into usage and performance. The other Fuga Cloud services can be added with a mouse click, and the choice of another cloud provider is a negotiable option. Fuga Cloud stands for Digital Sovereignty, Data Portability and GDPR compatibility.
Metalstack Cloudmetalstack.cloud uses Gardener and is based on the open-source software metal-stack.io, which is developed for regulated financial institutions. The focus here is on the highest possible security and compliance conformity. This makes metalstack.cloud perfect for running enterprise-grade container applications and provides your workloads with the highest possible performance.
CleuraCleura uses Gardener to power its Container Orchestration Engine for Cleura Public Cloud and Cleura Compliant Cloud. Cleura Container Orchestration Engine simplifies the creation and management of Kubernetes clusters through their user-friendly Cleura Cloud Management Panel or API, allowing users to focus on deploying applications instead of maintaining the underlying infrastructure.
PITS Globale DatenrettungsdienstePITS Globale Datenrettungsdienste is a data recovery company located in Germany specializing in recovering lost or damaged files from hard drives, solid-state drives, flash drives, and other storage media. Gardener is used to handle highly-loaded internal infrastructure and provide reliable, fully-managed K8 cluster solutions.

If you’re using Gardener and you aren’t on this list, submit a pull request!

diff --git a/docs/_print/community/index.html b/docs/_print/community/index.html index 8857bb52de6..b0e1197bf68 100644 --- a/docs/_print/community/index.html +++ b/docs/_print/community/index.html @@ -1,10 +1,10 @@ Community | Gardener -

Gardener Community

Follow - Engage - Contribute

Community Calls

Join our community calls to connect with other Gardener enthusiasts and watch cool presentations.

What content can you expect?

  • Gardener core developers roll out new information, share knowledge with the members and demonstrate new service capabilities.
  • Adopters and contributors share their use-cases, experience and exchange on future requirements.

If you want to receive updates, sign up here:

TopicSpeakerDate and TimeLink
Get more computing power in Gardener by overcoming Kubelet limitations with CRI-resource-managerPawel Palucki, Alexander D. KanevskiyOctober 20, 2022Recording
Summary
Cilium / Isovalent PresentationRaymond de JongOctober 6, 2022Recording
Summary
Gardener Extension Development - From scratch to the gardener-extension-shoot-fluxJens Schneider, Lothar GessleinJune 9, 2022Recording
Summary
Deploying and Developing Gardener Locally (Without Any External Infrastructure!)Tim Ebert, Rafael FranzkeMarch 17, 2022Recording
Summary
Gardenctl-v2Holger Kosser, Lukas Gross, Peter SutterFebruary 17, 2022Recording
Summary

Google Calendar

Presenting a Topic

If there is a topic you would like to present, message us in our #gardener slack channel or get in touch with Jessica Katz.

Get in Touch

@GardenerProject Follow the latest project updates on Twitter
GitHub diff --git a/docs/_print/contribute/docs/index.html b/docs/_print/contribute/docs/index.html index 90322eb0e4d..4c8bf0dcfa3 100644 --- a/docs/_print/contribute/docs/index.html +++ b/docs/_print/contribute/docs/index.html @@ -2,10 +2,10 @@ The following rules govern documentation contributions: Contributions must be licensed under …"> -

This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Contributing Documentation

You are welcome to contribute documentation to Gardener.

The following rules govern documentation contributions:

  • Contributions must be licensed under the Creative Commons Attribution 4.0 International License
  • You need to sign the Contributor License Agreement. We are using CLA assistant providing a click-through workflow for accepting the CLA. For company contributors additionally the company needs to sign a corporate license agreement. See the following sections for details.

1 - Working with Images

Using images on the website has to contribute to the aesthetics and comprehensibility of the materials, with uncompromised experience when loading and browsing pages. That concerns crisp clear images, their consistent layout and color scheme, dimensions and aspect ratios, flicker-free and fast loading or the feeling of it, even on unreliable mobile networks and devices.

Image Production Guidelines

A good, detailed reference for optimal use of images for the web can be found at web.dev’s Fast Load Times topic. The following summarizes some key points plus suggestions for tools support.

You are strongly encouraged to use vector images (SVG) as much as possible. They scale seamlessly without compromising the quality and are easier to maintain.

If you are just now starting with SVG authoring, here are some tools suggestions: Figma (online/Win/Mac), Sketch (Mac only).

For raster images (JPG, PNG, GIF), consider the following requirements and choose a tool that enables you to conform to them:

  • Be mindful about image size, the total page size and loading times.
  • Larger images (>10K) need to support progressive rendering. Consult with your favorite authoring tool’s documentation to find out if and how it supports that.
  • The site delivers the optimal media content format and size depending on the device screen size. You need to provide several variants (large screen, laptop, tablet, phone). Your authoring tool should be able to resize and resample images. Always save the largest size first and then downscale from it to avoid image quality loss.

If you are looking for a tool that conforms to those guidelines, IrfanView is a very good option.

Screenshots can be taken with whatever tool you have available. A simple Alt+PrtSc (Win) and paste into an image processing tool to save it does the job. If you need to add emphasized steps (1,2,3) when you describe a process on a screeshot, you can use Snaggit. Use red color and numbers. Mind the requirements for raster images laid out above.

Diagrams can be exported as PNG/JPG from a diagraming tool such as Visio or even PowerPoint. Pick whichever you are comfortable with to design the diagram and make sure you comply with the requirements for the raster images production above. Diagrams produced as SVG are welcome too if your authoring tool supports exporting in that format. In any case, ensure that your diagrams “blend” with the content on the site - use the same color scheme and geometry style. Do not complicate diagrams too much. The site also supports Mermaid diagrams produced with markdown and rendered as SVG. You don’t need special tools for them, but for more complex ones you might want to prototype your diagram wth Mermaid’s online live editor, before encoding it in your markdown. More tips on using Mermaid can be found in the Shortcodes documentation.

Using Images in Markdown

The standard for adding images to a topic is to use markdown’s ![caption](image-path). If the image is not showing properly, or if you wish to serve images close to their natural size and avoid scaling, then you can use HTML5’s <picture> tag.

Example:

<picture>
     <!-- default, laptop-width-L max 1200px -->
     <source srcset="https://github.tools.sap/kubernetes/documentation/tree/master/website/documentation/015-tutorials/my-guide/images/overview-XL.png"
diff --git a/docs/_print/docs/contribute/code/index.html b/docs/_print/docs/contribute/code/index.html
index f1243a10b6a..a95ac2ef00e 100644
--- a/docs/_print/docs/contribute/code/index.html
+++ b/docs/_print/docs/contribute/code/index.html
@@ -1,9 +1,9 @@
 Contributing Code | Gardener
-
This is the multi-page printable view of this section.
 Click here to print.
Return to the regular view of this page.
Contributing Code
You are welcome to contribute code to Gardener in order to fix a bug or to implement a new feature.
The following rules govern code contributions:
  • Contributions must be licensed under the Apache 2.0 License
  • You need to sign the Contributor License Agreement. We are using CLA assistant providing a click-through workflow for accepting the CLA. For company contributors additionally the company needs to sign a corporate license agreement. See the following sections for details.
1 - Contributing Bigger Changes
Contributing Bigger Changes
Here are the guidelines you should follow when contributing larger changes to Gardener:
  • We strongly recommend to write a Gardener Enhancement Proposal (GEP) to get a common understanding what you want to achieve. This makes it easier for reviewers to understand the big picture.
  • Avoid proposing a big change in one single PR. Instead, split your work into multiple stages which are independently mergeable and create one PR for each stage. For example, if introducing a new API resource and its controller, these stages could be:
    • API resource types, including defaults and generated code.
    • API resource validation.
    • API server storage.
    • Admission plugin(s), if any.
    • Controller(s), including changes to existing controllers. Split this phase further into different functional subsets if appropriate.
  • If you realize later that changes to artifacts introduced in a previous stage are required, by all means make them and explain in the PR why they were needed.
  • Consider splitting a big PR further into multiple commits to allow for more focused reviews. For example, you could add unit tests / documentation in separate commits from the rest of the code. If you have to adapt your PR to review feedback, prefer doing that also in a separate commit to make it easier for reviewers to check how their feedback has been addressed.
  • To make the review process more efficient and avoid too many long discussions in the PR itself, ask for a “main reviewer” to be assigned to your change, then work with this person to make sure he or she understands it in detail, and agree together on any improvements that may be needed. If you can’t reach an agreement on certain topics, comment on the PR and invite other people to join the discussion.
  • Even if you have a “main reviewer” assigned, you may still get feedback from other reviewers. In general, these “non-main reviewers” are advised to focus more on the design and overall approach rather than the implementation details. Make sure that you address any concerns on this level appropriately.
2 - CI/CD
CI/CD
As an execution environment for CI/CD workloads, we use Concourse.
 We however abstract from the underlying “build executor” and instead offer a
 Pipeline Definition Contract, through which components declare their build pipelines as
diff --git a/docs/adopter/index.html b/docs/adopter/index.html
index ee5980178e1..f6b00deed04 100644
--- a/docs/adopter/index.html
+++ b/docs/adopter/index.html
@@ -12,10 +12,10 @@
 
 
 SAP uses Gardener …">
-
See who is using Gardener
Gardener adopters in production environments that have publicly shared details of their usage.
teaser
SAPSAP uses Gardener to deploy and manage Kubernetes clusters at scale in a uniform way across infrastructures (AWS, Azure, GCP, Alicloud, as well as generic interfaces to OpenStack and vSphere). Workloads include Databases (SAP HANA Cloud), Big Data (SAP Data Intelligence), Kyma, many other cloud native applications, and diverse business workloads.
OVHcloudGardener can now be run by customers on the Public Cloud Platform of the leading European Cloud Provider OVHcloud.
ScaleUp TechnologiesScaleUp Technologies runs Gardener within their public Openstack Clouds (Hamburg, Berlin, Düsseldorf). Their clients run all kinds of workloads on top of Gardener maintained Kubernetes clusters ranging from databases to Software-as-a-Service applications.
Finanz Informatik Technologie Services GmbHFinanz Informatik Technologie Services GmbH uses Gardener to offer k8s as a service for customers in the financial industry in Germany. It is built on top of a “metal as a service” infrastructure implemented from scratch for k8s workloads in mind. The result is k8s on top of bare metal in minutes.
PingCAPPingCAP TiDB, is a cloud-native distributed SQL database with MySQL compatibility, and one of the most popular open-source database projects - with 23.5K+ stars and 400+ contributors. Its sister project TiKV is a Cloud Native Interactive Landscape project. PingCAP envisioned their managed TiDB service, known as TiDB Cloud, to be multi-tenant, secure, cost-efficient, and to be compatible with different cloud providers and they chose Gardener.
BeezlabsBeezlabs uses Gardener to deliver Intelligent Process Automation platform, on multiple cloud providers and reduce costs and lock-in risks.
b’nerdb’nerd uses Gardener as the core technology for its own managed Kubernetes as a Service solution and operates multiple Gardener installations for several cloud hosting service providers.
STACKITSTACKIT is a digital brand of Europe’s biggest retailer, the Schwarz Group, which includes Lidl, Kaufland, but also production and recycling companies. It uses Gardener to offer public and private Kubernetes as a service in own data centers in Europe and targets to become the cloud provider for German and European small and mid-sized companies.
T-SystemsSupporting and managing multiple application landscapes on-premises and across different hyperscaler infrastructures can be painful. At T-Systems we use Gardener both for internal usage and to manage clusters for our customers. We love the openness of the project, the flexibility and the architecture that allows us to manage clusters around the world with only one team from one single pane of glass and to meet industry specific certification standards. The sovereignty by design is another great value, the technology implicitly brings along.
23 TechnologiesThe German-based company 23 Technologies uses Gardener to offer an enterprise-class Kubernetes engine for industrial use cases as well as cloud service providers and offers managed and professional services for it. 23T is also the team behind okeanos.dev, a public service that can be used by anyone to try out Gardener.
B1 Systems GmbHB1 Systems GmbH is a international provider of Linux & Open Source consulting, training, managed service & support. We are founded in 2004 and based in Germany. Our team of 140 Linux experts offers tailor-made solutions based on cloud & container technologies, virtualization & high availability as well as monitoring, system & configuration management. B1 is using Gardener internally and also set up solutions/environments for customers.
finleap connect GmbHfinleap connect GmbH is the leading independent Open Banking platform provider in Europe. It enables companies across a multitude of industries to provide the next generation of financial services by understanding how customers transact and interact. With its “full-stack” platform of solutions, finleap connect makes it possible for its clients to compliantly access the financial transactions data of customers, enrich said data with analytics tools, provide digital banking services and deliver high-quality, digital financial services products and services to customers. Gardener uniquly enables us to deploy our platform in Europe and across the globe in a uniform way on the providers preferred by our customers.
CodesphereCodesphere is a Cloud IDE with integrated and automated deployment of web apps. It uses Gardener internally to manage clusters that host customer deployments and internal systems all over the world.
plusserverplusserver combines its own cloud offerings with hyperscaler platforms to provide individually tailored multi-cloud solutions. The plusserver Kubernetes Engine (PSKE) based on Gardener reduces the complexity in managing multi-cloud environments and enables companies to orchestrate their containers and cloud-native applications across a variety of platforms such as plusserver’s pluscloud open or hyperscalers such as AWS, either by mouseclick or via an API. With PSKE, companies remain vendor-independent and profit from guaranteed data sovereignty and data security due to GDPR-compliant cloud platforms in the certified plusserver data centers in Germany.
Fuga CloudFuga Cloud uses Gardener as the basis for its Enterprise Managed Kubernetes (EMK), a platform that simplifies the management of your k8s and provides insight into usage and performance. The other Fuga Cloud services can be added with a mouse click, and the choice of another cloud provider is a negotiable option. Fuga Cloud stands for Digital Sovereignty, Data Portability and GDPR compatibility.
Metalstack Cloudmetalstack.cloud uses Gardener and is based on the open-source software metal-stack.io, which is developed for regulated financial institutions. The focus here is on the highest possible security and compliance conformity. This makes metalstack.cloud perfect for running enterprise-grade container applications and provides your workloads with the highest possible performance.
CleuraCleura uses Gardener to power its Container Orchestration Engine for Cleura Public Cloud and Cleura Compliant Cloud. Cleura Container Orchestration Engine simplifies the creation and management of Kubernetes clusters through their user-friendly Cleura Cloud Management Panel or API, allowing users to focus on deploying applications instead of maintaining the underlying infrastructure.
PITS Globale DatenrettungsdienstePITS Globale Datenrettungsdienste is a data recovery company located in Germany specializing in recovering lost or damaged files from hard drives, solid-state drives, flash drives, and other storage media. Gardener is used to handle highly-loaded internal infrastructure and provide reliable, fully-managed K8 cluster solutions.
If you’re using Gardener and you aren’t on this list, submit a pull request!

 
 
diff --git a/docs/blog/2018/06.11-anti-patterns/index.html b/docs/blog/2018/06.11-anti-patterns/index.html
index 420f55e2e3f..afe8b6c29e3 100644
--- a/docs/blog/2018/06.11-anti-patterns/index.html
+++ b/docs/blog/2018/06.11-anti-patterns/index.html
@@ -4,16 +4,19 @@
 Instead of running a root user, use RUN groupadd -r anygroup && useradd -r -g anygroup myuser to create a group and a user in it.">
-