From 899786c7a906f8101eb19eca568b26f1c05b9d7a Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Fri, 2 Sep 2022 18:14:11 -0700 Subject: [PATCH] Remove unused version-2.6 files --- .../admin-settings/admin-settings.md | 50 - .../admin-settings/authentication/ad/ad.md | 206 - .../authentication/authentication.md | 93 - .../authentication/azure-ad/azure-ad.md | 205 - .../authentication/freeipa/freeipa.md | 51 - .../authentication/github/github.md | 49 - .../authentication/google/google.md | 112 - .../keycloak-oidc/keycloak-oidc.md | 137 - .../keycloak-saml/keycloak-saml.md | 179 - .../authentication/local/local.md | 16 - .../microsoft-adfs-setup.md | 82 - .../microsoft-adfs/microsoft-adfs.md | 30 - .../rancher-adfs-setup/rancher-adfs-setup.md | 45 - .../authentication/okta/okta.md | 50 - .../openldap-config/openldap-config.md | 86 - .../authentication/openldap/openldap.md | 49 - .../ping-federate/ping-federate.md | 52 - .../authentication/shibboleth/about/about.md | 32 - .../authentication/shibboleth/shibboleth.md | 108 - .../authentication/user-groups/user-groups.md | 65 - .../admin-settings/branding/branding.md | 213 - .../cluster-templates/cluster-templates.md | 130 - .../config-private-registry.md | 38 - .../cluster-drivers/cluster-drivers.md | 39 - .../admin-settings/drivers/drivers.md | 48 - .../drivers/node-drivers/node-drivers.md | 38 - .../k8s-metadata/k8s-metadata.md | 77 - .../pod-security-policies.md | 78 - .../cluster-project-roles.md | 225 - .../default-custom-roles.md | 121 - .../global-permissions/global-permissions.md | 254 - .../rbac/locked-roles/locked-roles.md | 39 - .../version-2.6/admin-settings/rbac/rbac.md | 26 - .../applying-templates/applying-templates.md | 61 - .../creating-and-revising.md | 171 - .../creator-permissions.md | 58 - .../rke-templates/enforcement/enforcement.md | 40 - .../example-scenarios/example-scenarios.md | 71 - .../example-yaml/example-yaml.md | 112 - .../rke-templates/overrides/overrides.md | 15 - .../rke-templates-and-hardware.md | 70 - .../rke-templates/rke-templates.md | 127 - .../template-access-and-sharing.md | 65 - .../version-2.6/api/api-tokens/api-tokens.md | 58 - versioned_docs/version-2.6/api/api.md | 84 - .../back-up-rancher/back-up-rancher.md | 76 - versioned_docs/version-2.6/backups/backups.md | 99 - .../backup-config/backup-config.md | 176 - .../backups/configuration/configuration.md | 10 - .../restore-config/restore-config.md | 87 - .../storage-config/storage-config.md | 60 - .../docker-backups/docker-backups.md | 71 - .../docker-installs/docker-installs.md | 8 - .../docker-restores/docker-restores.md | 70 - .../version-2.6/backups/examples/examples.md | 308 - .../migrating-rancher/migrating-rancher.md | 125 - .../restoring-rancher/restoring-rancher.md | 87 - .../best-practices/best-practices.md | 18 - .../rancher-managed/containers/containers.md | 49 - .../rancher-managed/logging/logging.md | 88 - .../managed-vsphere/managed-vsphere.md | 59 - .../rancher-managed/monitoring/monitoring.md | 120 - .../rancher-managed/rancher-managed.md | 21 - .../deployment-strategies.md | 45 - .../deployment-types/deployment-types.md | 37 - .../rancher-in-vsphere/rancher-in-vsphere.md | 91 - .../rancher-server/rancher-server.md | 19 - .../version-2.6/cis-scans/cis-scans.md | 292 - .../cis-scans/configuration/configuration.md | 98 - .../custom-benchmark/custom-benchmark.md | 84 - .../version-2.6/cis-scans/rbac/rbac.md | 50 - .../cis-scans/skipped-tests/skipped-tests.md | 54 - versioned_docs/version-2.6/cli/cli.md | 133 - .../backing-up-etcd/backing-up-etcd.md | 166 - .../certificate-rotation.md | 75 - .../cleaning-cluster-nodes.md | 285 - .../cloning-clusters/cloning-clusters.md | 99 - .../cluster-admin/cluster-access/ace/ace.md | 44 - .../cluster-access/cluster-access.md | 32 - .../cluster-members/cluster-members.md | 52 - .../cluster-access/kubectl/kubectl.md | 103 - .../cluster-admin/cluster-admin.md | 35 - .../cluster-autoscaler/amazon/amazon.md | 580 - .../cluster-autoscaler/cluster-autoscaler.md | 25 - .../aks-config-reference.md | 218 - .../editing-clusters/editing-clusters.md | 30 - .../eks-config-reference.md | 145 - .../gke-config-reference.md | 307 - .../private-clusters/private-clusters.md | 42 - .../k3s-config-reference.md | 143 - .../rke-config-reference.md | 360 - .../rke2-config-reference.md | 188 - .../editing-clusters/syncing/syncing.md | 35 - .../version-2.6/cluster-admin/nodes/nodes.md | 188 - .../pod-security-policies.md | 19 - .../pod-security-policy.md | 28 - .../projects-and-namespaces.md | 183 - .../restoring-etcd/restoring-etcd.md | 81 - .../version-2.6/cluster-admin/tools/tools.md | 59 - .../upgrading-kubernetes.md | 134 - .../attaching-existing-storage.md | 82 - .../volumes-and-storage/ceph/ceph.md | 433 - .../volumes-and-storage/examples/ebs/ebs.md | 16 - .../volumes-and-storage/examples/examples.md | 12 - .../volumes-and-storage/examples/nfs/nfs.md | 66 - .../examples/vsphere/vsphere.md | 76 - .../glusterfs-volumes/glusterfs-volumes.md | 32 - .../how-storage-works/how-storage-works.md | 76 - .../iscsi-volumes/iscsi-volumes.md | 33 - .../provisioning-new-storage.md | 88 - .../volumes-and-storage.md | 74 - .../cluster-capabilities-table/index.md | 29 - .../cluster-provisioning.md | 89 - .../hosted-kubernetes-clusters/ack/ack.md | 58 - .../hosted-kubernetes-clusters/aks/aks.md | 158 - .../hosted-kubernetes-clusters/cce/cce.md | 95 - .../hosted-kubernetes-clusters/eks/eks.md | 116 - .../eks/permissions/permissions.md | 223 - .../hosted-kubernetes-clusters/gke/gke.md | 104 - .../hosted-kubernetes-clusters.md | 30 - .../hosted-kubernetes-clusters/tke/tke.md | 94 - .../node-requirements/node-requirements.md | 126 - .../nodes-and-roles/nodes-and-roles.md | 43 - .../production/production.md | 50 - .../recommended-architecture.md | 74 - .../registered-clusters.md | 288 - ...avior-differences-between-rke1-and-rke2.md | 34 - .../cloud-providers/amazon/amazon.md | 150 - .../cloud-providers/azure/azure.md | 112 - .../cloud-providers/cloud-providers.md | 43 - .../rke-clusters/cloud-providers/gce/gce.md | 54 - .../vsphere/in-tree/in-tree.md | 21 - .../vsphere/out-of-tree/out-of-tree.md | 66 - .../vsphere-volume-migration.md | 108 - .../cloud-providers/vsphere/vsphere.md | 14 - .../agent-options/agent-options.md | 54 - .../rke-clusters/custom-nodes/custom-nodes.md | 126 - .../azure-machine-config.md | 121 - .../azure-node-template-config.md | 19 - .../rke-clusters/node-pools/azure/azure.md | 142 - .../node-pools/digital-ocean/digital-ocean.md | 103 - .../do-machine-config/do-machine-config.md | 34 - .../do-node-template-config.md | 19 - .../ec2-machine-config/ec2-machine-config.md | 79 - .../ec2-node-template-config.md | 50 - .../rke-clusters/node-pools/ec2/ec2.md | 279 - .../rke-clusters/node-pools/node-pools.md | 161 - .../nutanix-node-template-config.md | 64 - .../node-pools/nutanix/nutanix.md | 20 - .../provisioning-nutanix-clusters.md | 90 - .../creating-a-vm-template.md | 160 - .../creating-credentials.md | 43 - .../provisioning-vsphere-clusters.md | 112 - .../vsphere-node-template-config.md | 89 - .../node-pools/vsphere/vsphere.md | 58 - .../rke-clusters/options/options.md | 6 - .../rancher-agents/rancher-agents.md | 42 - .../rke-clusters/rke-clusters.md | 81 - .../azure-storageclass/azure-storageclass.md | 41 - .../host-gateway-requirements.md | 37 - .../windows-clusters/windows-clusters.md | 281 - .../windows-parity/windows-parity.md | 47 - .../version-2.6/contributing/contributing.md | 120 - .../deploy-across-clusters.md | 15 - .../fleet/architecture/architecture.md | 9 - .../deploy-across-clusters/fleet/fleet.md | 76 - .../fleet/proxy/proxy.md | 55 - .../fleet/windows/windows.md | 23 - .../multi-cluster-apps/multi-cluster-apps.md | 169 - .../deprecated-features.md | 26 - .../version-2.6/faq/dockershim/dockershim.md | 46 - versioned_docs/version-2.6/faq/faq.md | 70 - .../version-2.6/faq/kubectl/kubectl.md | 30 - .../networking/cni-providers/cni-providers.md | 201 - .../version-2.6/faq/networking/networking.md | 9 - .../faq/removing-rancher/removing-rancher.md | 61 - .../version-2.6/faq/security/security.md | 15 - .../version-2.6/faq/technical/technical.md | 173 - .../version-2.6/faq/telemetry/telemetry.md | 32 - .../creating-apps/creating-apps.md | 128 - .../version-2.6/helm-charts/helm-charts.md | 137 - .../install-rancher-on-k8s/aks/aks.md | 119 - .../amazon-eks/amazon-eks.md | 164 - .../chart-options/chart-options.md | 273 - .../install-rancher-on-k8s/gke/gke.md | 186 - .../install-rancher-on-k8s.md | 301 - .../rollbacks/rollbacks.md | 107 - .../air-gap-upgrade/air-gap-upgrade.md | 83 - .../upgrades/upgrades.md | 185 - .../version-2.6/installation/installation.md | 94 - .../air-gap/air-gap.md | 27 - .../docker-install-commands.md | 133 - .../install-rancher/install-rancher.md | 245 - .../launch-kubernetes/launch-kubernetes.md | 226 - .../populate-private-registry.md | 294 - .../air-gap/prepare-nodes/prepare-nodes.md | 178 - .../behind-proxy/behind-proxy.md | 14 - .../install-rancher/install-rancher.md | 89 - .../launch-kubernetes/launch-kubernetes.md | 169 - .../prepare-nodes/prepare-nodes.md | 61 - .../other-installation-methods.md | 20 - .../single-node-docker/advanced/advanced.md | 115 - .../single-node-docker/proxy/proxy.md | 60 - .../single-node-docker/single-node-docker.md | 192 - .../single-node-rollbacks.md | 84 - .../single-node-upgrades.md | 375 - .../troubleshooting/troubleshooting.md | 88 - .../requirements/dockershim/dockershim.md | 44 - .../installing-docker/installing-docker.md | 18 - .../ports/common-ports-table/index.md | 22 - .../installation/requirements/ports/ports.md | 335 - .../installation/requirements/requirements.md | 179 - .../resources/advanced/advanced.md | 6 - .../advanced/api-audit-log/api-audit-log.md | 559 - .../advanced/arm64-platform/arm64-platform.md | 40 - .../resources/advanced/etcd/etcd.md | 40 - .../resources/advanced/firewall/firewall.md | 108 - .../single-node-install-external-lb.md | 253 - .../bootstrap-password/bootstrap-password.md | 28 - .../choosing-version/choosing-version.md | 101 - .../custom-ca-root-certificate.md | 25 - .../continuous-delivery.md | 14 - .../enable-not-default-storage-drivers.md | 40 - .../resources/feature-flags/feature-flags.md | 147 - .../istio-virtual-service-ui.md | 33 - .../resources/helm-version/helm-version.md | 13 - .../resources/k8s-tutorials/ha-RKE/ha-RKE.md | 169 - .../k8s-tutorials/ha-rke2/ha-rke2.md | 167 - .../ha-with-external-db.md | 120 - .../how-ha-works/how-ha-works.md | 25 - .../ec2-node/ec2-node.md | 67 - .../infra-for-ha-with-external-db.md | 67 - .../infra-for-ha/infra-for-ha.md | 58 - .../infra-for-rke2-ha/infra-for-rke2-ha.md | 52 - .../infrastructure-tutorials.md | 10 - .../infrastructure-tutorials/nginx/nginx.md | 83 - .../infrastructure-tutorials/nlb/nlb.md | 179 - .../infrastructure-tutorials/rds/rds.md | 34 - .../resources/k8s-tutorials/k8s-tutorials.md | 8 - .../local-system-charts.md | 15 - .../installation/resources/resources.md | 26 - .../resources/tls-secrets/tls-secrets.md | 38 - .../resources/tls-settings/tls-settings.md | 22 - .../troubleshooting/troubleshooting.md | 185 - .../update-rancher-cert.md | 251 - .../upgrading-cert-manager.md | 246 - .../canal-and-project-network.md | 22 - .../configuration-reference.md | 48 - .../enable-istio-with-psp.md | 52 - .../configuration-reference/rke2/rke2.md | 38 - .../selectors-and-scrape.md | 121 - .../istio/disabling-istio/disabling-istio.md | 39 - versioned_docs/version-2.6/istio/istio.md | 134 - versioned_docs/version-2.6/istio/rbac/rbac.md | 44 - .../version-2.6/istio/resources/resources.md | 60 - .../deploy-workloads/deploy-workloads.md | 356 - .../enable-istio-in-cluster.md | 28 - .../enable-istio-in-namespace.md | 45 - .../istio/setup/gateway/gateway.md | 147 - .../set-up-traffic-management.md | 76 - .../version-2.6/istio/setup/setup.md | 28 - .../istio/setup/view-traffic/view-traffic.md | 23 - .../certificates/certificates.md | 35 - .../k8s-in-rancher/configmaps/configmaps.md | 32 - .../horitzontal-pod-autoscaler.md | 28 - .../hpa-background/hpa-background.md | 40 - .../manage-hpa-with-kubectl.md | 208 - .../manage-hpa-with-rancher-ui.md | 44 - .../testing-hpa/testing-hpa.md | 531 - .../k8s-in-rancher/k8s-in-rancher.md | 70 - .../ingress-config/ingress-config.md | 46 - .../ingress/ingress.md | 20 - .../load-balancers-and-ingress.md | 61 - .../load-balancers/load-balancers.md | 64 - .../k8s-in-rancher/registries/registries.md | 146 - .../k8s-in-rancher/secrets/secrets.md | 61 - .../service-discovery/service-discovery.md | 30 - .../workloads/add-a-sidecar/add-a-sidecar.md | 35 - .../deploy-workloads/deploy-workloads.md | 57 - .../rollback-workloads/rollback-workloads.md | 15 - .../upgrade-workloads/upgrade-workloads.md | 21 - .../k8s-in-rancher/workloads/workloads.md | 79 - .../logging/architecture/architecture.md | 29 - .../custom-resource-config.md | 9 - .../custom-resource-config/flows/flows.md | 85 - .../custom-resource-config/outputs/outputs.md | 302 - .../helm-chart-options/helm-chart-options.md | 91 - versioned_docs/version-2.6/logging/logging.md | 132 - .../logging/migrating/migrating.md | 190 - .../version-2.6/logging/rbac/rbac.md | 21 - .../taints-tolerations/taints-tolerations.md | 66 - .../version-2.6/longhorn/longhorn.md | 70 - .../configuration/advanced/advanced.md | 16 - .../advanced/alertmanager/alertmanager.md | 40 - .../advanced/prometheus/prometheus.md | 16 - .../prometheusrules/prometheusrules.md | 74 - .../configuration/configuration.md | 48 - .../configuration/examples/examples.md | 25 - .../helm-chart-options/helm-chart-options.md | 77 - .../configuration/receiver/receiver.md | 313 - .../configuration/route/route.md | 87 - .../servicemonitor-podmonitor.md | 31 - .../dashboards/dashboards.md | 107 - .../expression/expression.md | 428 - .../customize-grafana/customize-grafana.md | 41 - .../enable-monitoring/enable-monitoring.md | 71 - .../monitoring-alerting/guides/guides.md | 13 - .../guides/memory-usage/memory-usage.md | 20 - .../guides/migrating/migrating.md | 138 - .../monitoring-workloads.md | 31 - .../guides/persist-grafana/persist-grafana.md | 138 - .../guides/uninstall/uninstall.md | 16 - .../how-monitoring-works.md | 256 - .../monitoring-alerting.md | 105 - .../customizing-grafana.md | 8 - .../guides/enable-prom-fed/enable-prom-fed.md | 62 - .../prom-fed-workloads/prom-fed-workloads.md | 18 - .../uninstall-prom-fed/uninstall-prom-fed.md | 14 - .../prometheus-federator.md | 83 - .../prometheus-federator/rbac/rbac.md | 29 - .../monitoring-alerting/rbac/rbac.md | 181 - .../windows-clusters/windows-clusters.md | 57 - .../neuvector-integration.md | 120 - .../opa-gatekeper/opa-gatekeper.md | 100 - .../architecture-recommendations.md | 113 - .../overview/architecture/architecture.md | 183 - .../version-2.6/overview/concepts/concepts.md | 72 - .../version-2.6/overview/overview.md | 66 - .../pipelines/concepts/concepts.md | 36 - .../version-2.6/pipelines/config/config.md | 643 - .../pipelines/example-repos/example-repos.md | 80 - .../version-2.6/pipelines/example/example.md | 72 - .../version-2.6/pipelines/pipelines.md | 271 - .../version-2.6/pipelines/storage/storage.md | 94 - .../project-admin/namespaces/namespaces.md | 68 - .../project-admin/pipelines/pipelines.md | 16 - .../pod-security-policies.md | 32 - .../project-admin/project-admin.md | 39 - .../project-members/project-members.md | 53 - .../override-container-default.md | 40 - .../override-namespace-default.md | 32 - .../quota-type-reference.md | 24 - .../quotas-for-projects.md | 61 - .../resource-quotas/resource-quotas.md | 41 - .../version-2.6/project-admin/tools/tools.md | 39 - .../amazon-aws-marketplace-qs.md | 7 - .../deployment/amazon-aws-qs/amazon-aws-qs.md | 87 - .../deployment/deployment.md | 20 - .../digital-ocean-qs/digital-ocean-qs.md | 68 - .../equinix-metal-qs/equinix-metal-qs.md | 124 - .../deployment/google-gcp-qs/google-gcp-qs.md | 70 - .../hetzner-cloud-qs/hetzner-cloud-qs.md | 68 - .../microsoft-azure-qs/microsoft-azure-qs.md | 76 - .../quickstart-manual-setup.md | 139 - .../quickstart-vagrant/quickstart-vagrant.md | 47 - .../quick-start-guide/quick-start-guide.md | 17 - .../quickstart-deploy-workload-ingress.md | 74 - .../quickstart-deploy-workload-nodeport.md | 139 - .../quick-start-guide/workload/workload.md | 9 - versioned_docs/version-2.6/rancher-manager.md | 24 - .../security/best-practices/best-practices.md | 12 - .../version-2.6/security/cve/cve.md | 31 - .../hardening-guides/hardening-guides.md | 63 - ...her_v2-6_CIS_v1-6_Benchmark_Assessment.pdf | 14862 ---------------- .../rke-1.6-benchmark-2.6.md | 3100 ---- .../Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf | 8259 --------- .../rke-1.6-hardening-2.6.md | 643 - ...KE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf | 14240 --------------- .../rke2-1.6-benchmark-2.6.md | 3326 ---- ...her_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf | 4149 ----- .../rke2-1.6-hardening-2.6.md | 403 - .../security/security-scan/security-scan.md | 6 - .../version-2.6/security/security.md | 99 - .../version-2.6/security/selinux/selinux.md | 87 - .../version-2.6/system-tools/system-tools.md | 116 - .../version-2.6/troubleshooting/dns/dns.md | 217 - .../expired-webhook-certificates.md | 25 - .../imported-clusters/imported-clusters.md | 64 - .../controlplane/controlplane.md | 48 - .../kubernetes-components/etcd/etcd.md | 365 - .../kubernetes-components.md | 18 - .../nginx-proxy/nginx-proxy.md | 69 - .../worker-and-generic/worker-and-generic.md | 35 - .../kubernetes-resources.md | 271 - .../troubleshooting/logging/logging.md | 48 - .../troubleshooting/networking/networking.md | 118 - .../troubleshooting/rancherha/rancherha.md | 80 - .../troubleshooting/troubleshooting.md | 45 - .../userid-tracking-in-audit-logs.md | 23 - .../user-settings/api-keys/api-keys.md | 56 - .../cloud-credentials/cloud-credentials.md | 52 - .../node-templates/node-templates.md | 51 - .../user-settings/preferences/preferences.md | 18 - .../user-settings/user-settings.md | 16 - .../virtualization-admin.md | 35 - versioned_sidebars/version-2.6-sidebars.json | 8 - 396 files changed, 85419 deletions(-) delete mode 100644 versioned_docs/version-2.6/admin-settings/admin-settings.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/ad/ad.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/authentication.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/azure-ad/azure-ad.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/freeipa/freeipa.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/github/github.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/google/google.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/keycloak-oidc/keycloak-oidc.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/keycloak-saml/keycloak-saml.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/local/local.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup/microsoft-adfs-setup.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/rancher-adfs-setup/rancher-adfs-setup.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/okta/okta.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap-config/openldap-config.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/ping-federate/ping-federate.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/shibboleth/about/about.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/shibboleth/shibboleth.md delete mode 100644 versioned_docs/version-2.6/admin-settings/authentication/user-groups/user-groups.md delete mode 100644 versioned_docs/version-2.6/admin-settings/branding/branding.md delete mode 100644 versioned_docs/version-2.6/admin-settings/cluster-templates/cluster-templates.md delete mode 100644 versioned_docs/version-2.6/admin-settings/config-private-registry/config-private-registry.md delete mode 100644 versioned_docs/version-2.6/admin-settings/drivers/cluster-drivers/cluster-drivers.md delete mode 100644 versioned_docs/version-2.6/admin-settings/drivers/drivers.md delete mode 100644 versioned_docs/version-2.6/admin-settings/drivers/node-drivers/node-drivers.md delete mode 100644 versioned_docs/version-2.6/admin-settings/k8s-metadata/k8s-metadata.md delete mode 100644 versioned_docs/version-2.6/admin-settings/pod-security-policies/pod-security-policies.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rbac/cluster-project-roles/cluster-project-roles.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rbac/default-custom-roles/default-custom-roles.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rbac/global-permissions/global-permissions.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rbac/locked-roles/locked-roles.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rbac/rbac.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/applying-templates/applying-templates.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/creating-and-revising/creating-and-revising.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/creator-permissions/creator-permissions.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/enforcement/enforcement.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/example-scenarios/example-scenarios.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/example-yaml/example-yaml.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/overrides/overrides.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates-and-hardware/rke-templates-and-hardware.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates.md delete mode 100644 versioned_docs/version-2.6/admin-settings/rke-templates/template-access-and-sharing/template-access-and-sharing.md delete mode 100644 versioned_docs/version-2.6/api/api-tokens/api-tokens.md delete mode 100644 versioned_docs/version-2.6/api/api.md delete mode 100644 versioned_docs/version-2.6/backups/back-up-rancher/back-up-rancher.md delete mode 100644 versioned_docs/version-2.6/backups/backups.md delete mode 100644 versioned_docs/version-2.6/backups/configuration/backup-config/backup-config.md delete mode 100644 versioned_docs/version-2.6/backups/configuration/configuration.md delete mode 100644 versioned_docs/version-2.6/backups/configuration/restore-config/restore-config.md delete mode 100644 versioned_docs/version-2.6/backups/configuration/storage-config/storage-config.md delete mode 100644 versioned_docs/version-2.6/backups/docker-installs/docker-backups/docker-backups.md delete mode 100644 versioned_docs/version-2.6/backups/docker-installs/docker-installs.md delete mode 100644 versioned_docs/version-2.6/backups/docker-installs/docker-restores/docker-restores.md delete mode 100644 versioned_docs/version-2.6/backups/examples/examples.md delete mode 100644 versioned_docs/version-2.6/backups/migrating-rancher/migrating-rancher.md delete mode 100644 versioned_docs/version-2.6/backups/restoring-rancher/restoring-rancher.md delete mode 100644 versioned_docs/version-2.6/best-practices/best-practices.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-managed/containers/containers.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-managed/logging/logging.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-managed/managed-vsphere/managed-vsphere.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-managed/monitoring/monitoring.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-managed/rancher-managed.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-server/deployment-strategies/deployment-strategies.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-server/deployment-types/deployment-types.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-server/rancher-in-vsphere/rancher-in-vsphere.md delete mode 100644 versioned_docs/version-2.6/best-practices/rancher-server/rancher-server.md delete mode 100644 versioned_docs/version-2.6/cis-scans/cis-scans.md delete mode 100644 versioned_docs/version-2.6/cis-scans/configuration/configuration.md delete mode 100644 versioned_docs/version-2.6/cis-scans/custom-benchmark/custom-benchmark.md delete mode 100644 versioned_docs/version-2.6/cis-scans/rbac/rbac.md delete mode 100644 versioned_docs/version-2.6/cis-scans/skipped-tests/skipped-tests.md delete mode 100644 versioned_docs/version-2.6/cli/cli.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/backing-up-etcd/backing-up-etcd.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/certificate-rotation/certificate-rotation.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cleaning-cluster-nodes/cleaning-cluster-nodes.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cloning-clusters/cloning-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-access/ace/ace.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-access.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-members/cluster-members.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-access/kubectl/kubectl.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-admin.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/amazon/amazon.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/cluster-autoscaler.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/aks-config-reference/aks-config-reference.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/editing-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/eks-config-reference/eks-config-reference.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/gke-config-reference.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/private-clusters/private-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/k3s-config-reference/k3s-config-reference.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/rke-config-reference/rke-config-reference.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/rke2-config-reference/rke2-config-reference.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/editing-clusters/syncing/syncing.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/nodes/nodes.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/pod-security-policies/pod-security-policies.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/pod-security-policy/pod-security-policy.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/projects-and-namespaces/projects-and-namespaces.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/restoring-etcd/restoring-etcd.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/tools/tools.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/upgrading-kubernetes/upgrading-kubernetes.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/attaching-existing-storage/attaching-existing-storage.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/ceph/ceph.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/ebs/ebs.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/examples.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/nfs/nfs.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/vsphere/vsphere.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/glusterfs-volumes/glusterfs-volumes.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/how-storage-works/how-storage-works.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/iscsi-volumes/iscsi-volumes.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/provisioning-new-storage/provisioning-new-storage.md delete mode 100644 versioned_docs/version-2.6/cluster-admin/volumes-and-storage/volumes-and-storage.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/cluster-capabilities-table/index.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/cluster-provisioning.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/ack/ack.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/aks/aks.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/cce/cce.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/eks.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/permissions/permissions.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/gke/gke.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/hosted-kubernetes-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/tke/tke.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/node-requirements/node-requirements.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/production/nodes-and-roles/nodes-and-roles.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/production/production.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/production/recommended-architecture/recommended-architecture.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/registered-clusters/registered-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/behavior-differences-between-rke1-and-rke2.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/amazon/amazon.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/azure/azure.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/cloud-providers.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/gce/gce.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/in-tree/in-tree.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/out-of-tree.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/vsphere-volume-migration/vsphere-volume-migration.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/vsphere.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/agent-options/agent-options.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/custom-nodes.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-machine-config/azure-machine-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-node-template-config/azure-node-template-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/digital-ocean.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-machine-config/do-machine-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-node-template-config/do-node-template-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-machine-config/ec2-machine-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-node-template-config/ec2-node-template-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/node-pools.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix-node-template-config/nutanix-node-template-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/provisioning-nutanix-clusters/provisioning-nutanix-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-a-vm-template/creating-a-vm-template.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-credentials/creating-credentials.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/provisioning-vsphere-clusters/provisioning-vsphere-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/vsphere-node-template-config.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/options/options.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rancher-agents/rancher-agents.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rke-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/azure-storageclass/azure-storageclass.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/host-gateway-requirements.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-clusters.md delete mode 100644 versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-parity/windows-parity.md delete mode 100644 versioned_docs/version-2.6/contributing/contributing.md delete mode 100644 versioned_docs/version-2.6/deploy-across-clusters/deploy-across-clusters.md delete mode 100644 versioned_docs/version-2.6/deploy-across-clusters/fleet/architecture/architecture.md delete mode 100644 versioned_docs/version-2.6/deploy-across-clusters/fleet/fleet.md delete mode 100644 versioned_docs/version-2.6/deploy-across-clusters/fleet/proxy/proxy.md delete mode 100644 versioned_docs/version-2.6/deploy-across-clusters/fleet/windows/windows.md delete mode 100644 versioned_docs/version-2.6/deploy-across-clusters/multi-cluster-apps/multi-cluster-apps.md delete mode 100644 versioned_docs/version-2.6/faq/deprecated-features/deprecated-features.md delete mode 100644 versioned_docs/version-2.6/faq/dockershim/dockershim.md delete mode 100644 versioned_docs/version-2.6/faq/faq.md delete mode 100644 versioned_docs/version-2.6/faq/kubectl/kubectl.md delete mode 100644 versioned_docs/version-2.6/faq/networking/cni-providers/cni-providers.md delete mode 100644 versioned_docs/version-2.6/faq/networking/networking.md delete mode 100644 versioned_docs/version-2.6/faq/removing-rancher/removing-rancher.md delete mode 100644 versioned_docs/version-2.6/faq/security/security.md delete mode 100644 versioned_docs/version-2.6/faq/technical/technical.md delete mode 100644 versioned_docs/version-2.6/faq/telemetry/telemetry.md delete mode 100644 versioned_docs/version-2.6/helm-charts/creating-apps/creating-apps.md delete mode 100644 versioned_docs/version-2.6/helm-charts/helm-charts.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/aks/aks.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/amazon-eks/amazon-eks.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/chart-options/chart-options.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/gke/gke.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/install-rancher-on-k8s.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/rollbacks/rollbacks.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/air-gap-upgrade/air-gap-upgrade.md delete mode 100644 versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/upgrades.md delete mode 100644 versioned_docs/version-2.6/installation/installation.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/air-gap/air-gap.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/docker-install-commands/docker-install-commands.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/install-rancher.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/air-gap/populate-private-registry/populate-private-registry.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/air-gap/prepare-nodes/prepare-nodes.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/behind-proxy.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/install-rancher/install-rancher.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/launch-kubernetes/launch-kubernetes.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/prepare-nodes/prepare-nodes.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/other-installation-methods.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/advanced/advanced.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/proxy/proxy.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-docker.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-rollbacks/single-node-rollbacks.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md delete mode 100644 versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/troubleshooting/troubleshooting.md delete mode 100644 versioned_docs/version-2.6/installation/requirements/dockershim/dockershim.md delete mode 100644 versioned_docs/version-2.6/installation/requirements/installing-docker/installing-docker.md delete mode 100644 versioned_docs/version-2.6/installation/requirements/ports/common-ports-table/index.md delete mode 100644 versioned_docs/version-2.6/installation/requirements/ports/ports.md delete mode 100644 versioned_docs/version-2.6/installation/requirements/requirements.md delete mode 100644 versioned_docs/version-2.6/installation/resources/advanced/advanced.md delete mode 100644 versioned_docs/version-2.6/installation/resources/advanced/api-audit-log/api-audit-log.md delete mode 100644 versioned_docs/version-2.6/installation/resources/advanced/arm64-platform/arm64-platform.md delete mode 100644 versioned_docs/version-2.6/installation/resources/advanced/etcd/etcd.md delete mode 100644 versioned_docs/version-2.6/installation/resources/advanced/firewall/firewall.md delete mode 100644 versioned_docs/version-2.6/installation/resources/advanced/single-node-install-external-lb/single-node-install-external-lb.md delete mode 100644 versioned_docs/version-2.6/installation/resources/bootstrap-password/bootstrap-password.md delete mode 100644 versioned_docs/version-2.6/installation/resources/choosing-version/choosing-version.md delete mode 100644 versioned_docs/version-2.6/installation/resources/custom-ca-root-certificate/custom-ca-root-certificate.md delete mode 100644 versioned_docs/version-2.6/installation/resources/feature-flags/continuous-delivery/continuous-delivery.md delete mode 100644 versioned_docs/version-2.6/installation/resources/feature-flags/enable-not-default-storage-drivers/enable-not-default-storage-drivers.md delete mode 100644 versioned_docs/version-2.6/installation/resources/feature-flags/feature-flags.md delete mode 100644 versioned_docs/version-2.6/installation/resources/feature-flags/istio-virtual-service-ui/istio-virtual-service-ui.md delete mode 100644 versioned_docs/version-2.6/installation/resources/helm-version/helm-version.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-RKE/ha-RKE.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-rke2/ha-rke2.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-with-external-db/ha-with-external-db.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/how-ha-works/how-ha-works.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/ec2-node.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db/infra-for-ha-with-external-db.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha/infra-for-ha.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-rke2-ha/infra-for-rke2-ha.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infrastructure-tutorials.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/nginx.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/rds.md delete mode 100644 versioned_docs/version-2.6/installation/resources/k8s-tutorials/k8s-tutorials.md delete mode 100644 versioned_docs/version-2.6/installation/resources/local-system-charts/local-system-charts.md delete mode 100644 versioned_docs/version-2.6/installation/resources/resources.md delete mode 100644 versioned_docs/version-2.6/installation/resources/tls-secrets/tls-secrets.md delete mode 100644 versioned_docs/version-2.6/installation/resources/tls-settings/tls-settings.md delete mode 100644 versioned_docs/version-2.6/installation/resources/troubleshooting/troubleshooting.md delete mode 100644 versioned_docs/version-2.6/installation/resources/update-rancher-cert/update-rancher-cert.md delete mode 100644 versioned_docs/version-2.6/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md delete mode 100644 versioned_docs/version-2.6/istio/configuration-reference/canal-and-project-network/canal-and-project-network.md delete mode 100644 versioned_docs/version-2.6/istio/configuration-reference/configuration-reference.md delete mode 100644 versioned_docs/version-2.6/istio/configuration-reference/enable-istio-with-psp/enable-istio-with-psp.md delete mode 100644 versioned_docs/version-2.6/istio/configuration-reference/rke2/rke2.md delete mode 100644 versioned_docs/version-2.6/istio/configuration-reference/selectors-and-scrape/selectors-and-scrape.md delete mode 100644 versioned_docs/version-2.6/istio/disabling-istio/disabling-istio.md delete mode 100644 versioned_docs/version-2.6/istio/istio.md delete mode 100644 versioned_docs/version-2.6/istio/rbac/rbac.md delete mode 100644 versioned_docs/version-2.6/istio/resources/resources.md delete mode 100644 versioned_docs/version-2.6/istio/setup/deploy-workloads/deploy-workloads.md delete mode 100644 versioned_docs/version-2.6/istio/setup/enable-istio-in-cluster/enable-istio-in-cluster.md delete mode 100644 versioned_docs/version-2.6/istio/setup/enable-istio-in-namespace/enable-istio-in-namespace.md delete mode 100644 versioned_docs/version-2.6/istio/setup/gateway/gateway.md delete mode 100644 versioned_docs/version-2.6/istio/setup/set-up-traffic-management/set-up-traffic-management.md delete mode 100644 versioned_docs/version-2.6/istio/setup/setup.md delete mode 100644 versioned_docs/version-2.6/istio/setup/view-traffic/view-traffic.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/certificates/certificates.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/configmaps/configmaps.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/horitzontal-pod-autoscaler.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/hpa-background.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/manage-hpa-with-kubectl.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/manage-hpa-with-rancher-ui.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/testing-hpa.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/k8s-in-rancher.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress-config/ingress-config.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress/ingress.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers-and-ingress.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/registries/registries.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/secrets/secrets.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/service-discovery/service-discovery.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/workloads/add-a-sidecar/add-a-sidecar.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/workloads/deploy-workloads/deploy-workloads.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/workloads/rollback-workloads/rollback-workloads.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/workloads/upgrade-workloads/upgrade-workloads.md delete mode 100644 versioned_docs/version-2.6/k8s-in-rancher/workloads/workloads.md delete mode 100644 versioned_docs/version-2.6/logging/architecture/architecture.md delete mode 100644 versioned_docs/version-2.6/logging/custom-resource-config/custom-resource-config.md delete mode 100644 versioned_docs/version-2.6/logging/custom-resource-config/flows/flows.md delete mode 100644 versioned_docs/version-2.6/logging/custom-resource-config/outputs/outputs.md delete mode 100644 versioned_docs/version-2.6/logging/helm-chart-options/helm-chart-options.md delete mode 100644 versioned_docs/version-2.6/logging/logging.md delete mode 100644 versioned_docs/version-2.6/logging/migrating/migrating.md delete mode 100644 versioned_docs/version-2.6/logging/rbac/rbac.md delete mode 100644 versioned_docs/version-2.6/logging/taints-tolerations/taints-tolerations.md delete mode 100644 versioned_docs/version-2.6/longhorn/longhorn.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/advanced.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/alertmanager/alertmanager.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheus/prometheus.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheusrules/prometheusrules.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/configuration.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/examples/examples.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/helm-chart-options/helm-chart-options.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/receiver/receiver.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/route/route.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/configuration/servicemonitor-podmonitor/servicemonitor-podmonitor.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/dashboards/dashboards.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/expression/expression.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/customize-grafana/customize-grafana.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/enable-monitoring/enable-monitoring.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/guides.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/memory-usage/memory-usage.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/migrating/migrating.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/monitoring-workloads/monitoring-workloads.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/persist-grafana/persist-grafana.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/guides/uninstall/uninstall.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/how-monitoring-works/how-monitoring-works.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/monitoring-alerting.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/customizing-grafana/customizing-grafana.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/enable-prom-fed/enable-prom-fed.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/prom-fed-workloads/prom-fed-workloads.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/uninstall-prom-fed/uninstall-prom-fed.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/prometheus-federator.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/rbac/rbac.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/rbac/rbac.md delete mode 100644 versioned_docs/version-2.6/monitoring-alerting/windows-clusters/windows-clusters.md delete mode 100644 versioned_docs/version-2.6/neuvector-integration/neuvector-integration.md delete mode 100644 versioned_docs/version-2.6/opa-gatekeper/opa-gatekeper.md delete mode 100644 versioned_docs/version-2.6/overview/architecture-recommendations/architecture-recommendations.md delete mode 100644 versioned_docs/version-2.6/overview/architecture/architecture.md delete mode 100644 versioned_docs/version-2.6/overview/concepts/concepts.md delete mode 100644 versioned_docs/version-2.6/overview/overview.md delete mode 100644 versioned_docs/version-2.6/pipelines/concepts/concepts.md delete mode 100644 versioned_docs/version-2.6/pipelines/config/config.md delete mode 100644 versioned_docs/version-2.6/pipelines/example-repos/example-repos.md delete mode 100644 versioned_docs/version-2.6/pipelines/example/example.md delete mode 100644 versioned_docs/version-2.6/pipelines/pipelines.md delete mode 100644 versioned_docs/version-2.6/pipelines/storage/storage.md delete mode 100644 versioned_docs/version-2.6/project-admin/namespaces/namespaces.md delete mode 100644 versioned_docs/version-2.6/project-admin/pipelines/pipelines.md delete mode 100644 versioned_docs/version-2.6/project-admin/pod-security-policies/pod-security-policies.md delete mode 100644 versioned_docs/version-2.6/project-admin/project-admin.md delete mode 100644 versioned_docs/version-2.6/project-admin/project-members/project-members.md delete mode 100644 versioned_docs/version-2.6/project-admin/resource-quotas/override-container-default/override-container-default.md delete mode 100644 versioned_docs/version-2.6/project-admin/resource-quotas/override-namespace-default/override-namespace-default.md delete mode 100644 versioned_docs/version-2.6/project-admin/resource-quotas/quota-type-reference/quota-type-reference.md delete mode 100644 versioned_docs/version-2.6/project-admin/resource-quotas/quotas-for-projects/quotas-for-projects.md delete mode 100644 versioned_docs/version-2.6/project-admin/resource-quotas/resource-quotas.md delete mode 100644 versioned_docs/version-2.6/project-admin/tools/tools.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-marketplace-qs/amazon-aws-marketplace-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-qs/amazon-aws-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/deployment.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/digital-ocean-qs/digital-ocean-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/equinix-metal-qs/equinix-metal-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/google-gcp-qs/google-gcp-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/hetzner-cloud-qs/hetzner-cloud-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/microsoft-azure-qs/microsoft-azure-qs.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-manual-setup/quickstart-manual-setup.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-vagrant/quickstart-vagrant.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/quick-start-guide.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-ingress/quickstart-deploy-workload-ingress.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-nodeport/quickstart-deploy-workload-nodeport.md delete mode 100644 versioned_docs/version-2.6/quick-start-guide/workload/workload.md delete mode 100644 versioned_docs/version-2.6/rancher-manager.md delete mode 100644 versioned_docs/version-2.6/security/best-practices/best-practices.md delete mode 100644 versioned_docs/version-2.6/security/cve/cve.md delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/hardening-guides.md delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/Rancher_v2-6_CIS_v1-6_Benchmark_Assessment.pdf delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/rke-1.6-benchmark-2.6.md delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/rke-1.6-hardening-2.6.md delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/rke2-1.6-benchmark-2.6.md delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf delete mode 100644 versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/rke2-1.6-hardening-2.6.md delete mode 100644 versioned_docs/version-2.6/security/security-scan/security-scan.md delete mode 100644 versioned_docs/version-2.6/security/security.md delete mode 100644 versioned_docs/version-2.6/security/selinux/selinux.md delete mode 100644 versioned_docs/version-2.6/system-tools/system-tools.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/dns/dns.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/expired-webhook-certificates/expired-webhook-certificates.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/imported-clusters/imported-clusters.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/kubernetes-components/controlplane/controlplane.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/kubernetes-components/etcd/etcd.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/kubernetes-components/kubernetes-components.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/kubernetes-components/nginx-proxy/nginx-proxy.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/kubernetes-components/worker-and-generic/worker-and-generic.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/kubernetes-resources/kubernetes-resources.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/logging/logging.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/networking/networking.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/rancherha/rancherha.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/troubleshooting.md delete mode 100644 versioned_docs/version-2.6/troubleshooting/userid-tracking-in-audit-logs/userid-tracking-in-audit-logs.md delete mode 100644 versioned_docs/version-2.6/user-settings/api-keys/api-keys.md delete mode 100644 versioned_docs/version-2.6/user-settings/cloud-credentials/cloud-credentials.md delete mode 100644 versioned_docs/version-2.6/user-settings/node-templates/node-templates.md delete mode 100644 versioned_docs/version-2.6/user-settings/preferences/preferences.md delete mode 100644 versioned_docs/version-2.6/user-settings/user-settings.md delete mode 100644 versioned_docs/version-2.6/virtualization-admin/virtualization-admin.md delete mode 100644 versioned_sidebars/version-2.6-sidebars.json diff --git a/versioned_docs/version-2.6/admin-settings/admin-settings.md b/versioned_docs/version-2.6/admin-settings/admin-settings.md deleted file mode 100644 index 4b73dc848be..00000000000 --- a/versioned_docs/version-2.6/admin-settings/admin-settings.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Authentication, Permissions and Global Configuration -weight: 6 ---- - -After installation, the [system administrator]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) should configure Rancher to configure authentication, authorization, security, default settings, security policies, drivers and global DNS entries. - -## First Log In - -After you log into Rancher for the first time, Rancher will prompt you for a **Rancher Server URL**.You should set the URL to the main entry point to the Rancher Server. When a load balancer sits in front a Rancher Server cluster, the URL should resolve to the load balancer. The system will automatically try to infer the Rancher Server URL from the IP address or host name of the host running the Rancher Server. This is only correct if you are running a single node Rancher Server installation. In most cases, therefore, you need to set the Rancher Server URL to the correct value yourself. - ->**Important!** After you set the Rancher Server URL, we do not support updating it. Set the URL with extreme care. - -## Authentication - -One of the key features that Rancher adds to Kubernetes is centralized user authentication. This feature allows to set up local users and/or connect to an external authentication provider. By connecting to an external authentication provider, you can leverage that provider's user and groups. - -For more information how authentication works and how to configure each provider, see [Authentication]({{}}/rancher/v2.6/en/admin-settings/authentication/). - -## Authorization - -Within Rancher, each person authenticates as a _user_, which is a login that grants you access to Rancher. Once the user logs in to Rancher, their _authorization_, or their access rights within the system, is determined by the user's role. Rancher provides built-in roles to allow you to easily configure a user's permissions to resources, but Rancher also provides the ability to customize the roles for each Kubernetes resource. - -For more information how authorization works and how to customize roles, see [Roles Based Access Control (RBAC)]({{}}/rancher/v2.6/en/admin-settings/rbac/). - -## Pod Security Policies - -_Pod Security Policies_ (or PSPs) are objects that control security-sensitive aspects of pod specification, e.g. root privileges. If a pod does not meet the conditions specified in the PSP, Kubernetes will not allow it to start, and Rancher will display an error message. - -For more information how to create and use PSPs, see [Pod Security Policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/). - -## Provisioning Drivers - -Drivers in Rancher allow you to manage which providers can be used to provision [hosted Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/) or [nodes in an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) to allow Rancher to deploy and manage Kubernetes. - -For more information, see [Provisioning Drivers]({{}}/rancher/v2.6/en/admin-settings/drivers/). - -## Adding Kubernetes Versions into Rancher - -With this feature, you can upgrade to the latest version of Kubernetes as soon as it is released, without upgrading Rancher. This feature allows you to easily upgrade Kubernetes patch versions (i.e. `v1.15.X`), but not intended to upgrade Kubernetes minor versions (i.e. `v1.X.0`) as Kubernetes tends to deprecate or add APIs between minor versions. - -The information that Rancher uses to provision [RKE clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) is now located in the Rancher Kubernetes Metadata. For details on metadata configuration and how to change the Kubernetes version used for provisioning RKE clusters, see [Rancher Kubernetes Metadata.]({{}}/rancher/v2.6/en/admin-settings/k8s-metadata/) - -Rancher Kubernetes Metadata contains Kubernetes version information which Rancher uses to provision [RKE clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/). - -For more information on how metadata works and how to configure metadata config, see [Rancher Kubernetes Metadata]({{}}/rancher/v2.6/en/admin-settings/k8s-metadata/). - -## Enabling Experimental Features - -Rancher includes some features that are experimental and disabled by default. Feature flags were introduced to allow you to try these features. For more information, refer to the section about [feature flags.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) diff --git a/versioned_docs/version-2.6/admin-settings/authentication/ad/ad.md b/versioned_docs/version-2.6/admin-settings/authentication/ad/ad.md deleted file mode 100644 index 6ed722deb90..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/ad/ad.md +++ /dev/null @@ -1,206 +0,0 @@ ---- -title: Configuring Active Directory (AD) -weight: 1112 ---- - -If your organization uses Microsoft Active Directory as central user repository, you can configure Rancher to communicate with an Active Directory server to authenticate users. This allows Rancher admins to control access to clusters and projects based on users and groups managed externally in the Active Directory, while allowing end-users to authenticate with their AD credentials when logging in to the Rancher UI. - -Rancher uses LDAP to communicate with the Active Directory server. The authentication flow for Active Directory is therefore the same as for the [OpenLDAP authentication]({{}}/rancher/v2.6/en/admin-settings/authentication/openldap) integration. - -> **Note:** -> -> Before you start, please familiarise yourself with the concepts of [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -## Prerequisites - -You'll need to create or obtain from your AD administrator a new AD user to use as service account for Rancher. This user must have sufficient permissions to perform LDAP searches and read attributes of users and groups under your AD domain. - -Usually a (non-admin) **Domain User** account should be used for this purpose, as by default such user has read-only privileges for most objects in the domain partition. - -Note however, that in some locked-down Active Directory configurations this default behaviour may not apply. In such case you will need to ensure that the service account user has at least **Read** and **List Content** permissions granted either on the Base OU (enclosing users and groups) or globally for the domain. - -> **Using TLS?** -> -> - If the certificate used by the AD server is self-signed or not from a recognized certificate authority, make sure have at hand the CA certificate (concatenated with any intermediate certificates) in PEM format. You will have to paste in this certificate during the configuration so that Rancher is able to validate the certificate chain. -> -> - Upon an upgrade to v2.6.0, authenticating via Rancher against an active directory using TLS can fail if the certificates on the AD server do not support SAN attributes. This is a check enabled by default in Go v1.15. -> -> - The error received is "Error creating SSL connection: LDAP Result Code 200 "Network Error": x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0". -> -> - To resolve the error, update or replace the certificates on the AD server with new ones that support the SAN attribute. Alternatively, this error can be ignored by setting `GODEBUG=x509ignoreCN=0` as an environment variable to Rancher server container. - -## Configuration Steps -### Open Active Directory Configuration - -1. Log into the Rancher UI using the initial local `admin` account. -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **ActiveDirectory**. The **Authentication Provider: ActiveDirectory** form will be displayed. -1. Fill out the form. For help, refer to the details on configuration options below. -1. Click **Enable**. - -### Configure Active Directory Server Settings - -In the section titled `1. Configure an Active Directory server`, complete the fields with the information specific to your Active Directory server. Please refer to the following table for detailed information on the required values for each parameter. - -> **Note:** -> -> If you are unsure about the correct values to enter in the user/group Search Base field, please refer to [Identify Search Base and Schema using ldapsearch](#annex-identify-search-base-and-schema-using-ldapsearch). - -**Table 1: AD Server parameters** - -| Parameter | Description | -|:--|:--| -| Hostname | Specify the hostname or IP address of the AD server | -| Port | Specify the port at which the Active Directory server is listening for connections. Unencrypted LDAP normally uses the standard port of 389, while LDAPS uses port 636.| -| TLS | Check this box to enable LDAP over SSL/TLS (commonly known as LDAPS).| -| Server Connection Timeout | The duration in number of seconds that Rancher waits before considering the AD server unreachable. | -| Service Account Username | Enter the username of an AD account with read-only access to your domain partition (see [Prerequisites](#prerequisites)). The username can be entered in NetBIOS format (e.g. "DOMAIN\serviceaccount") or UPN format (e.g. "serviceaccount@domain.com"). | -| Service Account Password | The password for the service account. | -| Default Login Domain | When you configure this field with the NetBIOS name of your AD domain, usernames entered without a domain (e.g. "jdoe") will automatically be converted to a slashed, NetBIOS logon (e.g. "LOGIN_DOMAIN\jdoe") when binding to the AD server. If your users authenticate with the UPN (e.g. "jdoe@acme.com") as username then this field **must** be left empty. | -| User Search Base | The Distinguished Name of the node in your directory tree from which to start searching for user objects. All users must be descendents of this base DN. For example: "ou=people,dc=acme,dc=com".| -| Group Search Base | If your groups live under a different node than the one configured under `User Search Base` you will need to provide the Distinguished Name here. Otherwise leave it empty. For example: "ou=groups,dc=acme,dc=com".| - ---- - -### Configure User/Group Schema - -In the section titled `2. Customize Schema` you must provide Rancher with a correct mapping of user and group attributes corresponding to the schema used in your directory. - -Rancher uses LDAP queries to search for and retrieve information about users and groups within the Active Directory. The attribute mappings configured in this section are used to construct search filters and resolve group membership. It is therefore paramount that the provided settings reflect the reality of your AD domain. - -> **Note:** -> -> If you are unfamiliar with the schema used in your Active Directory domain, please refer to [Identify Search Base and Schema using ldapsearch](#annex-identify-search-base-and-schema-using-ldapsearch) to determine the correct configuration values. - -#### User Schema - -The table below details the parameters for the user schema section configuration. - -**Table 2: User schema configuration parameters** - -| Parameter | Description | -|:--|:--| -| Object Class | The name of the object class used for user objects in your domain. If defined, only specify the name of the object class - *don't* include it in an LDAP wrapper such as &(objectClass=xxxx) | -| Username Attribute | The user attribute whose value is suitable as a display name. | -| Login Attribute | The attribute whose value matches the username part of credentials entered by your users when logging in to Rancher. If your users authenticate with their UPN (e.g. "jdoe@acme.com") as username then this field must normally be set to `userPrincipalName`. Otherwise for the old, NetBIOS-style logon names (e.g. "jdoe") it's usually `sAMAccountName`. | -| User Member Attribute | The attribute containing the groups that a user is a member of. | -| Search Attribute | When a user enters text to add users or groups in the UI, Rancher queries the AD server and attempts to match users by the attributes provided in this setting. Multiple attributes can be specified by separating them with the pipe ("\|") symbol. To match UPN usernames (e.g. jdoe@acme.com) you should usually set the value of this field to `userPrincipalName`. | -| Search Filter | This filter gets applied to the list of users that is searched when Rancher attempts to add users to a site access list or tries to add members to clusters or projects. For example, a user search filter could be (|(memberOf=CN=group1,CN=Users,DC=testad,DC=rancher,DC=io)(memberOf=CN=group2,CN=Users,DC=testad,DC=rancher,DC=io)). Note: If the search filter does not use [valid AD search syntax,](https://docs.microsoft.com/en-us/windows/win32/adsi/search-filter-syntax) the list of users will be empty. | -| User Enabled Attribute | The attribute containing an integer value representing a bitwise enumeration of user account flags. Rancher uses this to determine if a user account is disabled. You should normally leave this set to the AD standard `userAccountControl`. | -| Disabled Status Bitmask | This is the value of the `User Enabled Attribute` designating a disabled user account. You should normally leave this set to the default value of "2" as specified in the Microsoft Active Directory schema (see [here](https://docs.microsoft.com/en-us/windows/desktop/adschema/a-useraccountcontrol#remarks)). | - ---- - -#### Group Schema - -The table below details the parameters for the group schema configuration. - -**Table 3: Group schema configuration parameters** - -| Parameter | Description | -|:--|:--| -| Object Class | The name of the object class used for group objects in your domain. If defined, only specify the name of the object class - *don't* include it in an LDAP wrapper such as &(objectClass=xxxx) | -| Name Attribute | The group attribute whose value is suitable for a display name. | -| Group Member User Attribute | The name of the **user attribute** whose format matches the group members in the `Group Member Mapping Attribute`. | -| Group Member Mapping Attribute | The name of the group attribute containing the members of a group. | -| Search Attribute | Attribute used to construct search filters when adding groups to clusters or projects. See description of user schema `Search Attribute`. | -| Search Filter | This filter gets applied to the list of groups that is searched when Rancher attempts to add groups to a site access list or tries to add groups to clusters or projects. For example, a group search filter could be (|(cn=group1)(cn=group2)). Note: If the search filter does not use [valid AD search syntax,](https://docs.microsoft.com/en-us/windows/win32/adsi/search-filter-syntax) the list of groups will be empty. | -| Group DN Attribute | The name of the group attribute whose format matches the values in the user attribute describing a the user's memberships. See `User Member Attribute`. | -| Nested Group Membership | This settings defines whether Rancher should resolve nested group memberships. Use only if your organization makes use of these nested memberships (i.e., you have groups that contain other groups as members. We advise avoiding nested groups when possible to avoid potential performance issues when there is a large amount of nested memberships). | - ---- - -### Test Authentication - -Once you have completed the configuration, proceed by testing the connection to the AD server **using your AD admin account**. If the test is successful, authentication with the configured Active Directory will be enabled implicitly with the account you test with set as admin. - -> **Note:** -> -> The AD user pertaining to the credentials entered in this step will be mapped to the local principal account and assigned administrator privileges in Rancher. You should therefore make a conscious decision on which AD account you use to perform this step. - -1. Enter the **username** and **password** for the AD account that should be mapped to the local principal account. -2. Click **Authenticate with Active Directory** to finalise the setup. - -**Result:** - -- Active Directory authentication has been enabled. -- You have been signed into Rancher as administrator using the provided AD credentials. - -> **Note:** -> -> You will still be able to login using the locally configured `admin` account and password in case of a disruption of LDAP services. - -## Annex: Identify Search Base and Schema using ldapsearch - -In order to successfully configure AD authentication it is crucial that you provide the correct configuration pertaining to the hierarchy and schema of your AD server. - -The [`ldapsearch`](http://manpages.ubuntu.com/manpages/artful/man1/ldapsearch.1.html) tool allows you to query your AD server to learn about the schema used for user and group objects. - -For the purpose of the example commands provided below we will assume: - -- The Active Directory server has a hostname of `ad.acme.com` -- The server is listening for unencrypted connections on port `389` -- The Active Directory domain is `acme` -- You have a valid AD account with the username `jdoe` and password `secret` - -### Identify Search Base - -First we will use `ldapsearch` to identify the Distinguished Name (DN) of the parent node(s) for users and groups: - -``` -$ ldapsearch -x -D "acme\jdoe" -w "secret" -p 389 \ --h ad.acme.com -b "dc=acme,dc=com" -s sub "sAMAccountName=jdoe" -``` - -This command performs an LDAP search with the search base set to the domain root (`-b "dc=acme,dc=com"`) and a filter targeting the user account (`sAMAccountNam=jdoe`), returning the attributes for said user: - -{{< img "/img/rancher/ldapsearch-user.png" "LDAP User">}} - -Since in this case the user's DN is `CN=John Doe,CN=Users,DC=acme,DC=com` [5], we should configure the **User Search Base** with the parent node DN `CN=Users,DC=acme,DC=com`. - -Similarly, based on the DN of the group referenced in the **memberOf** attribute [4], the correct value for the **Group Search Base** would be the parent node of that value, i.e., `OU=Groups,DC=acme,DC=com`. - -### Identify User Schema - -The output of the above `ldapsearch` query also allows to determine the correct values to use in the user schema configuration: - -- `Object Class`: **person** [1] -- `Username Attribute`: **name** [2] -- `Login Attribute`: **sAMAccountName** [3] -- `User Member Attribute`: **memberOf** [4] - -> **Note:** -> -> If the AD users in our organization were to authenticate with their UPN (e.g. jdoe@acme.com) instead of the short logon name, then we would have to set the `Login Attribute` to **userPrincipalName** instead. - -We'll also set the `Search Attribute` parameter to **sAMAccountName|name**. That way users can be added to clusters/projects in the Rancher UI either by entering their username or full name. - -### Identify Group Schema - -Next, we'll query one of the groups associated with this user, in this case `CN=examplegroup,OU=Groups,DC=acme,DC=com`: - -``` -$ ldapsearch -x -D "acme\jdoe" -w "secret" -p 389 \ --h ad.acme.com -b "ou=groups,dc=acme,dc=com" \ --s sub "CN=examplegroup" -``` - -This command will inform us on the attributes used for group objects: - -{{< img "/img/rancher/ldapsearch-group.png" "LDAP Group">}} - -Again, this allows us to determine the correct values to enter in the group schema configuration: - -- `Object Class`: **group** [1] -- `Name Attribute`: **name** [2] -- `Group Member Mapping Attribute`: **member** [3] -- `Search Attribute`: **sAMAccountName** [4] - -Looking at the value of the **member** attribute, we can see that it contains the DN of the referenced user. This corresponds to the **distinguishedName** attribute in our user object. Accordingly will have to set the value of the `Group Member User Attribute` parameter to this attribute. - -In the same way, we can observe that the value in the **memberOf** attribute in the user object corresponds to the **distinguishedName** [5] of the group. We therefore need to set the value for the `Group DN Attribute` parameter to this attribute. - -## Annex: Troubleshooting - -If you are experiencing issues while testing the connection to the Active Directory server, first double-check the credentials entered for the service account as well as the search base configuration. You may also inspect the Rancher logs to help pinpointing the problem cause. Debug logs may contain more detailed information about the error. Please refer to [How can I enable debug logging]({{}}/rancher/v2.6/en/faq/technical/#how-can-i-enable-debug-logging) in this documentation. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/authentication.md b/versioned_docs/version-2.6/admin-settings/authentication/authentication.md deleted file mode 100644 index 66a270b2264..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/authentication.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: Authentication -weight: 10 ---- - -One of the key features that Rancher adds to Kubernetes is centralized user authentication. This feature allows your users to use one set of credentials to authenticate with any of your Kubernetes clusters. - -This centralized user authentication is accomplished using the Rancher authentication proxy, which is installed along with the rest of Rancher. This proxy authenticates your users and forwards their requests to your Kubernetes clusters using a service account. - -## External vs. Local Authentication - -The Rancher authentication proxy integrates with the following external authentication services. - -| Auth Service | -| ------------------------------------------------------------------------------------------------ | -| [Microsoft Active Directory]({{}}/rancher/v2.6/en/admin-settings/authentication/ad/) | -| [GitHub]({{}}/rancher/v2.6/en/admin-settings/authentication/github/) | -| [Microsoft Azure AD]({{}}/rancher/v2.6/en/admin-settings/authentication/azure-ad/) | -| [FreeIPA]({{}}/rancher/v2.6/en/admin-settings/authentication/freeipa/) | -| [OpenLDAP]({{}}/rancher/v2.6/en/admin-settings/authentication/openldap/) | -| [Microsoft AD FS]({{}}/rancher/v2.6/en/admin-settings/authentication/microsoft-adfs/) | -| [PingIdentity]({{}}/rancher/v2.6/en/admin-settings/authentication/ping-federate/) | -| [Keycloak (OIDC)]({{}}/rancher/v2.6/en/admin-settings/authentication/keycloak-oidc/) | -| [Keycloak (SAML)]({{}}/rancher/v2.6/en/admin-settings/authentication/keycloak-saml/) | -| [Okta]({{}}/rancher/v2.6/en/admin-settings/authentication/okta/) | -| [Google OAuth]({{}}/rancher/v2.6/en/admin-settings/authentication/google/) | -| [Shibboleth]({{}}/rancher/v2.6/en/admin-settings/authentication/shibboleth) | - -
-However, Rancher also provides [local authentication]({{}}/rancher/v2.6/en/admin-settings/authentication/local/). - -In most cases, you should use an external authentication service over local authentication, as external authentication allows user management from a central location. However, you may want a few local authentication users for managing Rancher under rare circumstances, such as if your external authentication provider is unavailable or undergoing maintenance. - -## Users and Groups - -Rancher relies on users and groups to determine who is allowed to log in to Rancher and which resources they can access. When authenticating with an external provider, groups are provided from the external provider based on the user. These users and groups are given specific roles to resources like clusters, projects, multi-cluster apps, and global DNS providers and entries. When you give access to a group, all users who are a member of that group in the authentication provider will be able to access the resource with the permissions that you've specified. For more information on roles and permissions, see [Role Based Access Control]({{}}/rancher/v2.6/en/admin-settings/rbac/). - -> **Note:** Local authentication does not support creating or managing groups. - -For more information, see [Users and Groups]({{}}/rancher/v2.6/en/admin-settings/authentication/user-groups/) - -## Scope of Rancher Authorization - -After you configure Rancher to allow sign on using an external authentication service, you should configure who should be allowed to log in and use Rancher. The following options are available: - -| Access Level | Description | -|----------------------------------------------|-------------| -| Allow any valid Users | _Any_ user in the authorization service can access Rancher. We generally discourage use of this setting! | -| Allow members of Clusters, Projects, plus Authorized Users and Organizations | Any user in the authorization service and any group added as a **Cluster Member** or **Project Member** can log in to Rancher. Additionally, any user in the authentication service or group you add to the **Authorized Users and Organizations** list may log in to Rancher. | -| Restrict access to only Authorized Users and Organizations | Only users in the authentication service or groups added to the Authorized Users and Organizations can log in to Rancher. | - -To set the Rancher access level for users in the authorization service, follow these steps: - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Auth Provider**. -1. After setting up the configuration details for an auth provider, use the **Site Access** options to configure the scope of user authorization. The table above explains the access level for each option. -1. Optional: If you choose an option other than **Allow any valid Users,** you can add users to the list of authorized users and organizations by searching for them in the text field that appears. -1. Click **Save**. - -**Result:** The Rancher access configuration settings are applied. - -{{< saml_caveats >}} - -## External Authentication Configuration and Principal Users - -Configuration of external authentication requires: - -- A local user assigned the administrator role, called hereafter the _local principal_. -- An external user that can authenticate with your external authentication service, called hereafter the _external principal_. - -Configuration of external authentication affects how principal users are managed within Rancher. Follow the list below to better understand these effects. - -1. Sign into Rancher as the local principal and complete configuration of external authentication. - - ![Sign In]({{}}/img/rancher/sign-in.png) - -2. Rancher associates the external principal with the local principal. These two users share the local principal's user ID. - - ![Principal ID Sharing]({{}}/img/rancher/principal-ID.png) - -3. After you complete configuration, Rancher automatically signs out the local principal. - - ![Sign Out Local Principal]({{}}/img/rancher/sign-out-local.png) - -4. Then, Rancher automatically signs you back in as the external principal. - - ![Sign In External Principal]({{}}/img/rancher/sign-in-external.png) - -5. Because the external principal and the local principal share an ID, no unique object for the external principal displays on the Users page. - - ![Sign In External Principal]({{}}/img/rancher/users-page.png) - -6. The external principal and the local principal share the same access rights. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/azure-ad/azure-ad.md b/versioned_docs/version-2.6/admin-settings/authentication/azure-ad/azure-ad.md deleted file mode 100644 index 10b846aa428..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/azure-ad/azure-ad.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -title: Configuring Azure AD -weight: 1115 ---- - -If you have an instance of Active Directory (AD) hosted in Azure, you can configure Rancher to allow your users to log in using their AD accounts. Configuration of Azure AD external authentication requires you to make configurations in both Azure and Rancher. - ->**Note:** Azure AD integration only supports Service Provider initiated logins. - ->**Prerequisite:** Have an instance of Azure AD configured. - ->**Note:** Most of this procedure takes place from the [Microsoft Azure Portal](https://portal.azure.com/). - -## Azure Active Directory Configuration Outline - -Configuring Rancher to allow your users to authenticate with their Azure AD accounts involves multiple procedures. Review the outline below before getting started. - - - ->**Tip:** Before you start, we recommend creating an empty text file. You can use this file to copy values from Azure that you'll paste into Rancher later. - - - -- [1. Register Rancher with Azure](#1-register-rancher-with-azure) -- [2. Create a new client secret](#2-create-a-new-client-secret) -- [3. Set Required Permissions for Rancher](#3-set-required-permissions-for-rancher) -- [4. Add a Reply URL](#4-add-a-reply-url) -- [5. Copy Azure Application Data](#5-copy-azure-application-data) -- [6. Configure Azure AD in Rancher](#6-configure-azure-ad-in-rancher) - - - -### 1. Register Rancher with Azure - -Before enabling Azure AD within Rancher, you must register Rancher with Azure. - -1. Log in to [Microsoft Azure](https://portal.azure.com/) as an administrative user. Configuration in future steps requires administrative access rights. - -1. Use search to open the **App registrations** service. - - ![Open App Registrations]({{}}/img/rancher/search-app-registrations.png) - -1. Click **New registrations** and complete the **Create** form. - - ![New App Registration]({{}}/img/rancher/new-app-registration.png) - - 1. Enter a **Name** (something like `Rancher`). - - 1. From **Supported account types**, select "Accounts in this organizational directory only (AzureADTest only - Single tenant)" This corresponds to the legacy app registration options. - - 1. In the **Redirect URI** section, make sure **Web** is selected from the dropdown and enter the URL of your Rancher Server in the text box next to the dropdown. This Rancher server URL should be appended with the verification path: `/verify-auth-azure`. - - >**Tip:** You can find your personalized Azure reply URL in Rancher on the Azure AD Authentication page (Global View > Security Authentication > Azure AD). - - 1. Click **Register**. - ->**Note:** It can take up to five minutes for this change to take affect, so don't be alarmed if you can't authenticate immediately after Azure AD configuration. - -### 2. Create a new client secret - -From the Azure portal, create a client secret. Rancher will use this key to authenticate with Azure AD. - -1. Use search to open **App registrations** services. Then open the entry for Rancher that you created in the last procedure. - - ![Open Rancher Registration]({{}}/img/rancher/open-rancher-app.png) - -1. From the navigation pane on left, click **Certificates and Secrets**. - -1. Click **New client secret**. - - ![Create new client secret]({{< baseurl >}}/img/rancher/select-client-secret.png) - - 1. Enter a **Description** (something like `Rancher`). - - 1. Select duration for the key from the options under **Expires**. This drop-down sets the expiration date for the key. Shorter durations are more secure, but require you to create a new key after expiration. - - 1. Click **Add** (you don't need to enter a value—it will automatically populate after you save). - - -1. Copy the key value and save it to an [empty text file](#tip). - - You'll enter this key into the Rancher UI later as your **Application Secret**. - - You won't be able to access the key value again within the Azure UI. - -### 3. Set Required Permissions for Rancher - -Next, set API permissions for Rancher within Azure. - -1. From the navigation pane on left, select **API permissions**. - - ![Open Required Permissions]({{}}/img/rancher/select-required-permissions.png) - -1. Click **Add a permission**. - -1. From the **Azure Active Directory Graph**, select the following **Delegated Permissions**: - - ![Select API Permissions]({{< baseurl >}}/img/rancher/select-required-permissions-2.png) - -
-
- - **Access the directory as the signed-in user** - - **Read directory data** - - **Read all groups** - - **Read all users' full profiles** - - **Read all users' basic profiles** - - **Sign in and read user profile** - -1. Click **Add permissions**. - -1. From **API permissions**, click **Grant admin consent**. Then click **Yes**. - - >**Note:** You must be signed in as an Azure administrator to successfully save your permission settings. - - -### 4. Add a Reply URL - -To use Azure AD with Rancher you must whitelist Rancher with Azure. You can complete this whitelisting by providing Azure with a reply URL for Rancher, which is your Rancher Server URL followed with a verification path. - - -1. From the **Setting** blade, select **Reply URLs**. - - ![Azure: Enter Reply URL]({{}}/img/rancher/enter-azure-reply-url.png) - -1. From the **Reply URLs** blade, enter the URL of your Rancher Server, appended with the verification path: `/verify-auth-azure`. - - >**Tip:** You can find your personalized Azure reply URL in Rancher on the Azure AD Authentication page (Global View > Security Authentication > Azure AD). - -1. Click **Save**. - -**Result:** Your reply URL is saved. - ->**Note:** It can take up to five minutes for this change to take affect, so don't be alarmed if you can't authenticate immediately after Azure AD configuration. - -### 5. Copy Azure Application Data - -As your final step in Azure, copy the data that you'll use to configure Rancher for Azure AD authentication and paste it into an empty text file. - -1. Obtain your Rancher **Tenant ID**. - - 1. Use search to open the **Azure Active Directory** service. - - ![Open Azure Active Directory]({{}}/img/rancher/search-azure-ad.png) - - 1. From the left navigation pane, open **Overview**. - - 2. Copy the **Directory ID** and paste it into your [text file](#tip). - - You'll paste this value into Rancher as your **Tenant ID**. - -1. Obtain your Rancher **Application ID**. - - 1. Use search to open **App registrations**. - - ![Open App Registrations]({{}}/img/rancher/search-app-registrations.png) - - 1. Find the entry you created for Rancher. - - 1. Copy the **Application ID** and paste it to your [text file](#tip). - -1. Obtain your Rancher **Graph Endpoint**, **Token Endpoint**, and **Auth Endpoint**. - - 1. From **App registrations**, click **Endpoints**. - - ![Click Endpoints]({{}}/img/rancher/click-endpoints.png) - - 2. Copy the following endpoints to your clipboard and paste them into your [text file](#tip) (these values will be your Rancher endpoint values). - - - **Microsoft Graph API endpoint** (Graph Endpoint) - - **OAuth 2.0 token endpoint (v1)** (Token Endpoint) - - **OAuth 2.0 authorization endpoint (v1)** (Auth Endpoint) - ->**Note:** Copy the v1 version of the endpoints - -### 6. Configure Azure AD in Rancher - -From the Rancher UI, enter information about your AD instance hosted in Azure to complete configuration. - -Enter the values that you copied to your [text file](#tip). - -1. Log into Rancher. -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **AzureAD**. -1. Complete the **Configure Azure AD Account** form using the information you copied while completing [Copy Azure Application Data](#5-copy-azure-application-data). - - >**Important:** When entering your Graph Endpoint, remove the tenant ID from the URL, like below. - > - >https://graph.windows.net/abb5adde-bee8-4821-8b03-e63efdc7701c - - The following table maps the values you copied in the Azure portal to the fields in Rancher. - - | Rancher Field | Azure Value | - | ------------------ | ------------------------------------- | - | Tenant ID | Directory ID | - | Application ID | Application ID | - | Application Secret | Key Value | - | Endpoint | https://login.microsoftonline.com/ | - | Graph Endpoint | Microsoft Azure AD Graph API Endpoint | - | Token Endpoint | OAuth 2.0 Token Endpoint | - | Auth Endpoint | OAuth 2.0 Authorization Endpoint | - -1. Click **Enable**. - -**Result:** Azure Active Directory authentication is configured. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/freeipa/freeipa.md b/versioned_docs/version-2.6/admin-settings/authentication/freeipa/freeipa.md deleted file mode 100644 index 40de727fac5..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/freeipa/freeipa.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Configuring FreeIPA -weight: 1114 ---- - -If your organization uses FreeIPA for user authentication, you can configure Rancher to allow your users to login using their FreeIPA credentials. - ->**Prerequisites:** -> ->- You must have a [FreeIPA Server](https://www.freeipa.org/) configured. ->- Create a service account in FreeIPA with `read-only` access. Rancher uses this account to verify group membership when a user makes a request using an API key. ->- Read [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -1. Sign into Rancher using a local user assigned the `administrator` role (i.e., the _local principal_). -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **FreeIPA**. -1. Complete the **Configure an FreeIPA server** form. - - You may need to log in to your domain controller to find the information requested in the form. - - >**Using TLS?** - >If the certificate is self-signed or not from a recognized certificate authority, make sure you provide the complete chain. That chain is needed to verify the server's certificate. -
-
- >**User Search Base vs. Group Search Base** - > - >Search base allows Rancher to search for users and groups that are in your FreeIPA. These fields are only for search bases and not for search filters. - > - >* If your users and groups are in the same search base, complete only the User Search Base. - >* If your groups are in a different search base, you can optionally complete the Group Search Base. This field is dedicated to searching groups, but is not required. - -1. If your FreeIPA deviates from the standard AD schema, complete the **Customize Schema** form to match it. Otherwise, skip this step. - - >**Search Attribute** The Search Attribute field defaults with three specific values: `uid|sn|givenName`. After FreeIPA is configured, when a user enters text to add users or groups, Rancher automatically queries the FreeIPA server and attempts to match fields by user id, last name, or first name. Rancher specifically searches for users/groups that begin with the text entered in the search field. - > - >The default field value `uid|sn|givenName`, but you can configure this field to a subset of these fields. The pipe (`|`) between the fields separates these fields. - > - > * `uid`: User ID - > * `sn`: Last Name - > * `givenName`: First Name - > - > With this search attribute, Rancher creates search filters for users and groups, but you *cannot* add your own search filters in this field. - -1. Enter your FreeIPA username and password in **Authenticate with FreeIPA** to confirm that Rancher is configured to use FreeIPA authentication. -1. Click **Enable**. - -**Result:** - -- FreeIPA authentication is configured. -- You are signed into Rancher with your FreeIPA account (i.e., the _external principal_). diff --git a/versioned_docs/version-2.6/admin-settings/authentication/github/github.md b/versioned_docs/version-2.6/admin-settings/authentication/github/github.md deleted file mode 100644 index a5b5ba93281..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/github/github.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Configuring GitHub -weight: 1116 ---- - -In environments using GitHub, you can configure Rancher to allow sign on using GitHub credentials. - ->**Prerequisites:** Read [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -1. Sign into Rancher using a local user assigned the `administrator` role (i.e., the _local principal_). -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **GitHub**. -1. Follow the directions displayed to set up a GitHub Application. Rancher redirects you to GitHub to complete registration. - - >**What's an Authorization Callback URL?** - > - >The Authorization Callback URL is the URL where users go to begin using your application (i.e. the splash screen). - - >When you use external authentication, authentication does not actually take place in your application. Instead, authentication takes place externally (in this case, GitHub). After this external authentication completes successfully, the Authorization Callback URL is the location where the user re-enters your application. - -1. From GitHub, copy the **Client ID** and **Client Secret**. Paste them into Rancher. - - >**Where do I find the Client ID and Client Secret?** - > - >From GitHub, select Settings > Developer Settings > OAuth Apps. The Client ID and Client Secret are displayed prominently. - -1. Click **Authenticate with GitHub**. - -1. Use the **Site Access** options to configure the scope of user authorization. - - - **Allow any valid Users** - - _Any_ GitHub user can access Rancher. We generally discourage use of this setting! - - - **Allow members of Clusters, Projects, plus Authorized Users and Organizations** - - Any GitHub user or group added as a **Cluster Member** or **Project Member** can log in to Rancher. Additionally, any GitHub user or group you add to the **Authorized Users and Organizations** list may log in to Rancher. - - - **Restrict access to only Authorized Users and Organizations** - - Only GitHub users or groups added to the Authorized Users and Organizations can log in to Rancher. -
-1. Click **Enable**. - -**Result:** - -- GitHub authentication is configured. -- You are signed into Rancher with your GitHub account (i.e., the _external principal_). diff --git a/versioned_docs/version-2.6/admin-settings/authentication/google/google.md b/versioned_docs/version-2.6/admin-settings/authentication/google/google.md deleted file mode 100644 index 2ac8b6cb8c9..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/google/google.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: Configuring Google OAuth -weight: 10 ---- - -If your organization uses G Suite for user authentication, you can configure Rancher to allow your users to log in using their G Suite credentials. - -Only admins of the G Suite domain have access to the Admin SDK. Therefore, only G Suite admins can configure Google OAuth for Rancher. - -Within Rancher, only administrators or users with the **Manage Authentication** [global role]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) can configure authentication. - -# Prerequisites - -- You must have a [G Suite admin account](https://admin.google.com) configured. -- G Suite requires a [top private domain FQDN](https://github.com/google/guava/wiki/InternetDomainNameExplained#public-suffixes-and-private-domains) as an authorized domain. One way to get an FQDN is by creating an A-record in Route53 for your Rancher server. You do not need to update your Rancher Server URL setting with that record, because there could be clusters using that URL. -- You must have the Admin SDK API enabled for your G Suite domain. You can enable it using the steps on [this page.](https://support.google.com/a/answer/60757?hl=en) - -After the Admin SDK API is enabled, your G Suite domain's API screen should look like this: -![Enable Admin APIs]({{}}/img/rancher/Google-Enable-APIs-Screen.png) - -# Setting up G Suite for OAuth with Rancher - -Before you can set up Google OAuth in Rancher, you need to log in to your G Suite account and do the following: - -1. [Add Rancher as an authorized domain in G Suite](#1-adding-rancher-as-an-authorized-domain) -1. [Generate OAuth2 credentials for the Rancher server](#2-creating-oauth2-credentials-for-the-rancher-server) -1. [Create service account credentials for the Rancher server](#3-creating-service-account-credentials) -1. [Register the service account key as an OAuth Client](#4-register-the-service-account-key-as-an-oauth-client) - -### 1. Adding Rancher as an Authorized Domain - -1. Click [here](https://console.developers.google.com/apis/credentials) to go to credentials page of your Google domain. -1. Select your project and click **OAuth consent screen**. -![OAuth Consent Screen]({{}}/img/rancher/Google-OAuth-consent-screen-tab.png) -1. Go to **Authorized Domains** and enter the top private domain of your Rancher server URL in the list. The top private domain is the rightmost superdomain. So for example, www.foo.co.uk a top private domain of foo.co.uk. For more information on top-level domains, refer to [this article.](https://github.com/google/guava/wiki/InternetDomainNameExplained#public-suffixes-and-private-domains) -1. Go to **Scopes for Google APIs** and make sure **email,** **profile** and **openid** are enabled. - -**Result:** Rancher has been added as an authorized domain for the Admin SDK API. - -### 2. Creating OAuth2 Credentials for the Rancher Server - -1. Go to the Google API console, select your project, and go to the [credentials page.](https://console.developers.google.com/apis/credentials) -![Credentials]({{}}/img/rancher/Google-Credentials-tab.png) -1. On the **Create Credentials** dropdown, select **OAuth client ID**. -1. Click **Web application**. -1. Provide a name. -1. Fill out the **Authorized JavaScript origins** and **Authorized redirect URIs**. Note: The Rancher UI page for setting up Google OAuth (available from the Global view under **Security > Authentication > Google**) provides you the exact links to enter for this step. - - Under **Authorized JavaScript origins,** enter your Rancher server URL. - - Under **Authorized redirect URIs,** enter your Rancher server URL appended with the path `verify-auth`. For example, if your URI is `https://rancherServer`, you will enter `https://rancherServer/verify-auth`. -1. Click on **Create**. -1. After the credential is created, you will see a screen with a list of your credentials. Choose the credential you just created, and in that row on rightmost side, click **Download JSON**. Save the file so that you can provide these credentials to Rancher. - -**Result:** Your OAuth credentials have been successfully created. - -### 3. Creating Service Account Credentials -Since the Google Admin SDK is available only to admins, regular users cannot use it to retrieve profiles of other users or their groups. Regular users cannot even retrieve their own groups. - -Since Rancher provides group-based membership access, we require the users to be able to get their own groups, and look up other users and groups when needed. - -As a workaround to get this capability, G Suite recommends creating a service account and delegating authority of your G Suite domain to that service account. - -This section describes how to: - -- Create a service account -- Create a key for the service account and download the credentials as JSON - -1. Click [here](https://console.developers.google.com/iam-admin/serviceaccounts) and select your project for which you generated OAuth credentials. -1. Click on **Create Service Account**. -1. Enter a name and click **Create**. -![Service account creation Step 1]({{}}/img/rancher/Google-svc-acc-step1.png) -1. Don't provide any roles on the **Service account permissions** page and click **Continue** -![Service account creation Step 2]({{}}/img/rancher/Google-svc-acc-step2.png) -1. Click on **Create Key** and select the JSON option. Download the JSON file and save it so that you can provide it as the service account credentials to Rancher. -![Service account creation Step 3]({{}}/img/rancher/Google-svc-acc-step3-key-creation.png) - -**Result:** Your service account is created. - -### 4. Register the Service Account Key as an OAuth Client - -You will need to grant some permissions to the service account you created in the last step. Rancher requires you to grant only read-only permissions for users and groups. - -Using the Unique ID of the service account key, register it as an Oauth Client using the following steps: - -1. Get the Unique ID of the key you just created. If it's not displayed in the list of keys right next to the one you created, you will have to enable it. To enable it, click **Unique ID** and click **OK**. This will add a **Unique ID** column to the list of service account keys. Save the one listed for the service account you created. NOTE: This is a numeric key, not to be confused with the alphanumeric field **Key ID**. - - ![Service account Unique ID]({{}}/img/rancher/Google-Select-UniqueID-column.png) -1. Go to the [**Domain-wide Delegation** page.](https://admin.google.com/ac/owl/domainwidedelegation) -1. Add the Unique ID obtained in the previous step in the **Client Name** field. -1. In the **One or More API Scopes** field, add the following scopes: - ``` - openid,profile,email,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.group.readonly - ``` -1. Click **Authorize**. - -**Result:** The service account is registered as an OAuth client in your G Suite account. - -# Configuring Google OAuth in Rancher - -1. Sign into Rancher using a local user assigned the [administrator]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions) role. This user is also called the local principal. -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **Google**. The instructions in the UI cover the steps to set up authentication with Google OAuth. - 1. Admin Email: Provide the email of an administrator account from your GSuite setup. In order to perform user and group lookups, google apis require an administrator's email in conjunction with the service account key. - 1. Domain: Provide the domain on which you have configured GSuite. Provide the exact domain and not any aliases. - 1. Nested Group Membership: Check this box to enable nested group memberships. Rancher admins can disable this at any time after configuring auth. - - **Step One** is about adding Rancher as an authorized domain, which we already covered in [this section.](#1-adding-rancher-as-an-authorized-domain) - - For **Step Two,** provide the OAuth credentials JSON that you downloaded after completing [this section.](#2-creating-oauth2-credentials-for-the-rancher-server) You can upload the file or paste the contents into the **OAuth Credentials** field. - - For **Step Three,** provide the service account credentials JSON that downloaded at the end of [this section.](#3-creating-service-account-credentials) The credentials will only work if you successfully [registered the service account key](#4-register-the-service-account-key-as-an-oauth-client) as an OAuth client in your G Suite account. -1. Click **Authenticate with Google**. -1. Click **Enable**. - -**Result:** Google authentication is successfully configured. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/keycloak-oidc/keycloak-oidc.md b/versioned_docs/version-2.6/admin-settings/authentication/keycloak-oidc/keycloak-oidc.md deleted file mode 100644 index a56af63a28e..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/keycloak-oidc/keycloak-oidc.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -title: Configuring Keycloak (OIDC) -description: Create a Keycloak OpenID Connect (OIDC) client and configure Rancher to work with Keycloak. By the end your users will be able to sign into Rancher using their Keycloak logins -weight: 1200 ---- -If your organization uses [Keycloak Identity Provider (IdP)](https://www.keycloak.org) for user authentication, you can configure Rancher to allow your users to log in using their IdP credentials. Rancher supports integration with Keycloak using the OpenID Connect (OIDC) protocol and the SAML protocol. Both implementations are functionally equivalent when used with Rancher. This page describes the process to configure Rancher to work with Keycloak using the OIDC protocol. - -If you prefer to use Keycloak with the SAML protocol instead, refer to [this page]({{}}/rancher/v2.6/en/admin-settings/authentication/keycloak-saml/). - -If you have an existing configuration using the SAML protocol and want to switch to the OIDC protocol, refer to [this section](#migrating-from-saml-to-oidc). - -## Prerequisites - -- On Rancher, Keycloak (SAML) is disabled. -- You must have a [Keycloak IdP Server](https://www.keycloak.org/docs/latest/server_installation/) configured. -- In Keycloak, create a [new OIDC client](https://www.keycloak.org/docs/latest/server_admin/#oidc-clients), with the settings below. See the [Keycloak documentation](https://www.keycloak.org/docs/latest/server_admin/#oidc-clients) for help. - - Setting | Value - ------------|------------ - `Client ID` | <CLIENT_ID> (e.g. `rancher`) - `Name` | <CLIENT_NAME> (e.g. `rancher`) - `Client Protocol` | `openid-connect` - `Access Type` | `confidential` - `Valid Redirect URI` | `https://yourRancherHostURL/verify-auth` - -- In the new OIDC client, create [Mappers](https://www.keycloak.org/docs/latest/server_admin/#_protocol-mappers) to expose the users fields. - - Create a new "Groups Mapper" with the settings below. - - Setting | Value - ------------|------------ - `Name` | `Groups Mapper` - `Mapper Type` | `Group Membership` - `Token Claim Name` | `groups` - `Add to ID token` | `OFF` - `Add to access token` | `OFF` - `Add to user info` | `ON` - - - Create a new "Client Audience" with the settings below. - - Setting | Value - ------------|------------ - `Name` | `Client Audience` - `Mapper Type` | `Audience` - `Included Client Audience` | <CLIENT_NAME> - `Add to access token` | `ON` - - - Create a new "Groups Path" with the settings below. - - Setting | Value - ------------|------------ - `Name` | `Group Path` - `Mapper Type` | `Group Membership` - `Token Claim Name` | `full_group_path` - `Full group path` | `ON` - `Add to user info` | `ON` - -## Configuring Keycloak in Rancher - -1. In the Rancher UI, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Auth Provider**. -1. Select **Keycloak (OIDC)**. -1. Complete the **Configure a Keycloak OIDC account** form. For help with filling the form, see the [configuration reference](#configuration-reference). -1. After you complete the **Configure a Keycloak OIDC account** form, click **Enable**. - - Rancher redirects you to the IdP login page. Enter credentials that authenticate with Keycloak IdP to validate your Rancher Keycloak configuration. - - >**Note:** You may need to disable your popup blocker to see the IdP login page. - -**Result:** Rancher is configured to work with Keycloak using the OIDC protocol. Your users can now sign into Rancher using their Keycloak logins. - -## Configuration Reference - -| Field | Description | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Client ID | The `Client ID` of your Keycloak client. | -| Client Secret | The generated `Secret` of your Keycloak client. In the Keycloak console, select **Clients**, select the client you created, select the **Credentials** tab and copy the value of the `Secret` field. | -| Private Key / Certificate | A key/certificate pair to create a secure shell between Rancher and your IdP. Required if HTTPS/SSL is enabled on your Keycloak server. | -| Endpoints | Choose whether to use the generated values for the `Rancher URL`, `Issue`, and `Auth Endpoint` fields or to provide manual overrides if incorrect. | -| Keycloak URL | The URL for your Keycloak server. | -| Keycloak Realm | The name of the realm in which the Keycloak client was created in. | -| Rancher URL | The URL for your Rancher Server. | -| Issuer | The URL of your IdP. | -| Auth Endpoint | The URL where users are redirected to authenticate. | - -## Migrating from SAML to OIDC - -This section describes the process to transition from using Rancher with Keycloak (SAML) to Keycloak (OIDC). - -### Reconfigure Keycloak - -1. Change the existing client to use the OIDC protocol. In the Keycloak console, select **Clients**, select the SAML client to migrate, select the **Settings** tab, change `Client Protocol` from `saml` to `openid-connect`, and click **Save** - -1. Verify the `Valid Redirect URIs` are still valid. - -1. Select the **Mappers** tab and create a new Mapper with the settings below. - - Setting | Value - ------------|------------ - `Name` | `Groups Mapper` - `Mapper Type` | `Group Membership` - `Token Claim Name` | `groups` - `Add to ID token` | `ON` - `Add to access token` | `ON` - `Add to user info` | `ON` - -### Reconfigure Rancher - -Before configuring Rancher to use Keycloak (OIDC), Keycloak (SAML) must be first disabled. - -1. In the Rancher UI, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Auth Provider**. -1. Select **Keycloak (SAML)**. -1. Click **Disable**. - -Configure Rancher to use Keycloak (OIDC) by following the steps in [this section](#configuring-keycloak-in-rancher). - -> **Note:** After configuration is completed, Rancher user permissions will need to be reapplied as they are not automatically migrated. - -## Annex: Troubleshooting - -If you are experiencing issues while testing the connection to the Keycloak server, first double-check the configuration options of your OIDC client. You may also inspect the Rancher logs to help pinpoint what's causing issues. Debug logs may contain more detailed information about the error. Please refer to [How can I enable debug logging]({{}}/rancher/v2.6/en/faq/technical/#how-can-i-enable-debug-logging) in this documentation. - -All Keycloak related log entries will be prepended with either `[generic oidc]` or `[keycloak oidc]`. - -### You are not redirected to Keycloak - -When you fill the **Configure a Keycloak OIDC account** form and click on **Enable**, you are not redirected to your IdP. - - * Verify your Keycloak client configuration. - -### The generated `Issuer` and `Auth Endpoint` are incorrect - - * On the **Configure a Keycloak OIDC account** form, change **Endpoints** to `Specify (advanced)` and override the `Issuer` and `Auth Endpoint` values. To find the values, go to the Keycloak console and select **Realm Settings**, select the **General** tab, and click **OpenID Endpoint Configuration**. The JSON output will display values for `issuer` and `authorization_endpoint`. - -### Keycloak Error: "Invalid grant_type" - - * In some cases, this error message may be misleading and is actually caused by setting the `Valid Redirect URI` incorrectly. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/keycloak-saml/keycloak-saml.md b/versioned_docs/version-2.6/admin-settings/authentication/keycloak-saml/keycloak-saml.md deleted file mode 100644 index 3ddca672fa6..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/keycloak-saml/keycloak-saml.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -title: Configuring Keycloak (SAML) -description: Create a Keycloak SAML client and configure Rancher to work with Keycloak. By the end your users will be able to sign into Rancher using their Keycloak logins -weight: 1200 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -If your organization uses Keycloak Identity Provider (IdP) for user authentication, you can configure Rancher to allow your users to log in using their IdP credentials. - -## Prerequisites - -- You must have a [Keycloak IdP Server](https://www.keycloak.org/docs/latest/server_installation/) configured. -- In Keycloak, create a [new SAML client](https://www.keycloak.org/docs/latest/server_admin/#saml-clients), with the settings below. See the [Keycloak documentation](https://www.keycloak.org/docs/latest/server_admin/#saml-clients) for help. - - Setting | Value - ------------|------------ - `Sign Documents` | `ON` 1 - `Sign Assertions` | `ON` 1 - All other `ON/OFF` Settings | `OFF` - `Client ID` | Either `https://yourRancherHostURL/v1-saml/keycloak/saml/metadata` or the value configured in the `Entry ID Field` of the Rancher Keycloak configuration2 - `Client Name` | (e.g. `rancher`) - `Client Protocol` | `SAML` - `Valid Redirect URI` | `https://yourRancherHostURL/v1-saml/keycloak/saml/acs` - - >1: Optionally, you can enable either one or both of these settings. - >2: Rancher SAML metadata won't be generated until a SAML provider is configured and saved. - - {{< img "/img/rancher/keycloak/keycloak-saml-client-configuration.png" "">}} - -- In the new SAML client, create Mappers to expose the users fields - - Add all "Builtin Protocol Mappers" - {{< img "/img/rancher/keycloak/keycloak-saml-client-builtin-mappers.png" "">}} - - Create a new "Group list" mapper to map the member attribute to a user's groups - {{< img "/img/rancher/keycloak/keycloak-saml-client-group-mapper.png" "">}} - -## Getting the IDP Metadata - - - - -To get the IDP metadata, export a `metadata.xml` file from your Keycloak client. -From the **Installation** tab, choose the **SAML Metadata IDPSSODescriptor** format option and download your file. - - - - -1. From the **Configure** section, click the **Realm Settings** tab. -1. Click the **General** tab. -1. From the **Endpoints** field, click **SAML 2.0 Identity Provider Metadata**. - -Verify the IDP metadata contains the following attributes: - -``` -xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" -xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" -xmlns:ds="http://www.w3.org/2000/09/xmldsig#" -``` - -Some browsers, such as Firefox, may render/process the document such that the contents appear to have been modified, and some attributes appear to be missing. In this situation, use the raw response data that can be found using your browser. - -The following is an example process for Firefox, but will vary slightly for other browsers: - -1. Press **F12** to access the developer console. -1. Click the **Network** tab. -1. From the table, click the row containing `descriptor`. -1. From the details pane, click the **Response** tab. -1. Copy the raw response data. - -The XML obtained contains `EntitiesDescriptor` as the root element. Rancher expects the root element to be `EntityDescriptor` rather than `EntitiesDescriptor`. So before passing this XML to Rancher, follow these steps to adjust it: - -1. Copy all the attributes from `EntitiesDescriptor` to the `EntityDescriptor` that are not present. -1. Remove the `` tag from the beginning. -1. Remove the `` from the end of the xml. - -You are left with something similar as the example below: - -``` - -.... - -``` - - - - -1. From the **Configure** section, click the **Realm Settings** tab. -1. Click the **General** tab. -1. From the **Endpoints** field, click **SAML 2.0 Identity Provider Metadata**. - -Verify the IDP metadata contains the following attributes: - -``` -xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" -xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" -xmlns:ds="http://www.w3.org/2000/09/xmldsig#" -``` - -Some browsers, such as Firefox, may render/process the document such that the contents appear to have been modified, and some attributes appear to be missing. In this situation, use the raw response data that can be found using your browser. - -The following is an example process for Firefox, but will vary slightly for other browsers: - -1. Press **F12** to access the developer console. -1. Click the **Network** tab. -1. From the table, click the row containing `descriptor`. -1. From the details pane, click the **Response** tab. -1. Copy the raw response data. - - - - -## Configuring Keycloak in Rancher - - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **Keycloak SAML**. -1. Complete the **Configure Keycloak Account** form. For help with filling the form, see the [configuration reference](#configuration-reference). -1. After you complete the **Configure a Keycloak Account** form, click **Enable**. - - Rancher redirects you to the IdP login page. Enter credentials that authenticate with Keycloak IdP to validate your Rancher Keycloak configuration. - - >**Note:** You may have to disable your popup blocker to see the IdP login page. - -**Result:** Rancher is configured to work with Keycloak. Your users can now sign into Rancher using their Keycloak logins. - -{{< saml_caveats >}} - -## Configuration Reference - -| Field | Description | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Display Name Field | The attribute that contains the display name of users.

Example: `givenName` | -| User Name Field | The attribute that contains the user name/given name.

Example: `email` | -| UID Field | An attribute that is unique to every user.

Example: `email` | -| Groups Field | Make entries for managing group memberships.

Example: `member` | -| Entity ID Field | The ID that needs to be configured as a client ID in the Keycloak client.

Default: `https://yourRancherHostURL/v1-saml/keycloak/saml/metadata` | -| Rancher API Host | The URL for your Rancher Server. | -| Private Key / Certificate | A key/certificate pair to create a secure shell between Rancher and your IdP. | -| IDP-metadata | The `metadata.xml` file that you exported from your IdP server. | - ->**Tip:** You can generate a key/certificate pair using an openssl command. For example: -> -> openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout myservice.key -out myservice.cert - -## Annex: Troubleshooting - -If you are experiencing issues while testing the connection to the Keycloak server, first double-check the configuration option of your SAML client. You may also inspect the Rancher logs to help pinpointing the problem cause. Debug logs may contain more detailed information about the error. Please refer to [How can I enable debug logging]({{}}/rancher/v2.6/en/faq/technical/#how-can-i-enable-debug-logging) in this documentation. - -### You are not redirected to Keycloak - -When you click on **Authenticate with Keycloak**, you are not redirected to your IdP. - - * Verify your Keycloak client configuration. - * Make sure `Force Post Binding` set to `OFF`. - - -### Forbidden message displayed after IdP login - -You are correctly redirected to your IdP login page and you are able to enter your credentials, however you get a `Forbidden` message afterwards. - - * Check the Rancher debug log. - * If the log displays `ERROR: either the Response or Assertion must be signed`, make sure either `Sign Documents` or `Sign assertions` is set to `ON` in your Keycloak client. - -### HTTP 502 when trying to access /v1-saml/keycloak/saml/metadata - -This is usually due to the metadata not being created until a SAML provider is configured. -Try configuring and saving keycloak as your SAML provider and then accessing the metadata. - -### Keycloak Error: "We're sorry, failed to process response" - - * Check your Keycloak log. - * If the log displays `failed: org.keycloak.common.VerificationException: Client does not have a public key`, set `Encrypt Assertions` to `OFF` in your Keycloak client. - -### Keycloak Error: "We're sorry, invalid requester" - - * Check your Keycloak log. - * If the log displays `request validation failed: org.keycloak.common.VerificationException: SigAlg was null`, set `Client Signature Required` to `OFF` in your Keycloak client. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/local/local.md b/versioned_docs/version-2.6/admin-settings/authentication/local/local.md deleted file mode 100644 index b7dea954681..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/local/local.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Local Authentication -weight: 1111 ---- - -Local authentication is the default until you configure an external authentication provider. Local authentication is where Rancher stores the user information, i.e. names and passwords, of who can log in to Rancher. By default, the `admin` user that logs in to Rancher for the first time is a local user. - -## Adding Local Users - -Regardless of whether you use external authentication, you should create a few local authentication users so that you can continue using Rancher if your external authentication service encounters issues. - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Users**. -1. Click **Create**. -1. Complete the **Add User** form. -1. Click **Create**. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup/microsoft-adfs-setup.md b/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup/microsoft-adfs-setup.md deleted file mode 100644 index 190ebafee11..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup/microsoft-adfs-setup.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: 1. Configuring Microsoft AD FS for Rancher -weight: 1205 ---- - -Before configuring Rancher to support AD FS users, you must add Rancher as a [relying party trust](https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/technical-reference/understanding-key-ad-fs-concepts) in AD FS. - -1. Log into your AD server as an administrative user. - -1. Open the **AD FS Management** console. Select **Add Relying Party Trust..**. from the **Actions** menu and click **Start**. - - {{< img "/img/rancher/adfs/adfs-overview.png" "">}} - -1. Select **Enter data about the relying party manually** as the option for obtaining data about the relying party. - - {{< img "/img/rancher/adfs/adfs-add-rpt-2.png" "">}} - -1. Enter your desired **Display name** for your Relying Party Trust. For example, `Rancher`. - - {{< img "/img/rancher/adfs/adfs-add-rpt-3.png" "">}} - -1. Select **AD FS profile** as the configuration profile for your relying party trust. - - {{< img "/img/rancher/adfs/adfs-add-rpt-4.png" "">}} - -1. Leave the **optional token encryption certificate** empty, as Rancher AD FS will not be using one. - - {{< img "/img/rancher/adfs/adfs-add-rpt-5.png" "">}} - -1. Select **Enable support for the SAML 2.0 WebSSO protocol** - and enter `https:///v1-saml/adfs/saml/acs` for the service URL. - - {{< img "/img/rancher/adfs/adfs-add-rpt-6.png" "">}} - -1. Add `https:///v1-saml/adfs/saml/metadata` as the **Relying party trust identifier**. - - {{< img "/img/rancher/adfs/adfs-add-rpt-7.png" "">}} - -1. This tutorial will not cover multi-factor authentication; please refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configure-additional-authentication-methods-for-ad-fs) if you would like to configure multi-factor authentication. - - {{< img "/img/rancher/adfs/adfs-add-rpt-8.png" "">}} - -1. From **Choose Issuance Authorization RUles**, you may select either of the options available according to use case. However, for the purposes of this guide, select **Permit all users to access this relying party**. - - {{< img "/img/rancher/adfs/adfs-add-rpt-9.png" "">}} - -1. After reviewing your settings, select **Next** to add the relying party trust. - - {{< img "/img/rancher/adfs/adfs-add-rpt-10.png" "">}} - - -1. Select **Open the Edit Claim Rules..**. and click **Close**. - - {{< img "/img/rancher/adfs/adfs-add-rpt-11.png" "">}} - -1. On the **Issuance Transform Rules** tab, click **Add Rule..**.. - - {{< img "/img/rancher/adfs/adfs-edit-cr.png" "">}} - -1. Select **Send LDAP Attributes as Claims** as the **Claim rule template**. - - {{< img "/img/rancher/adfs/adfs-add-tcr-1.png" "">}} - -1. Set the **Claim rule name** to your desired name (for example, `Rancher Attributes`) and select **Active Directory** as the **Attribute store**. Create the following mapping to reflect the table below: - - | LDAP Attribute | Outgoing Claim Type | - | -------------------------------------------- | ------------------- | - | Given-Name | Given Name | - | User-Principal-Name | UPN | - | Token-Groups - Qualified by Long Domain Name | Group | - | SAM-Account-Name | Name | -
- {{< img "/img/rancher/adfs/adfs-add-tcr-2.png" "">}} - -1. Download the `federationmetadata.xml` from your AD server at: -``` -https:///federationmetadata/2007-06/federationmetadata.xml -``` - -**Result:** You've added Rancher as a relying trust party. Now you can configure Rancher to leverage AD. - -### [Next: Configuring Rancher for Microsoft AD FS]({{}}/rancher/v2.6/en/admin-settings/authentication/microsoft-adfs/rancher-adfs-setup/) diff --git a/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs.md b/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs.md deleted file mode 100644 index 32a60c9fec0..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/microsoft-adfs.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Configuring Microsoft Active Directory Federation Service (SAML) -weight: 1205 ---- - -If your organization uses Microsoft Active Directory Federation Services (AD FS) for user authentication, you can configure Rancher to allow your users to log in using their AD FS credentials. - -## Prerequisites - -You must have Rancher installed. - -- Obtain your Rancher Server URL. During AD FS configuration, substitute this URL for the `` placeholder. -- You must have a global administrator account on your Rancher installation. - -You must have a [Microsoft AD FS Server](https://docs.microsoft.com/en-us/windows-server/identity/active-directory-federation-services) configured. - -- Obtain your AD FS Server IP/DNS name. During AD FS configuration, substitute this IP/DNS name for the `` placeholder. -- You must have access to add [Relying Party Trusts](https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/create-a-relying-party-trust) on your AD FS Server. - -## Setup Outline - -Setting up Microsoft AD FS with Rancher Server requires configuring AD FS on your Active Directory server, and configuring Rancher to utilize your AD FS server. The following pages serve as guides for setting up Microsoft AD FS authentication on your Rancher installation. - -- [1. Configuring Microsoft AD FS for Rancher]({{}}/rancher/v2.6/en/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup) -- [2. Configuring Rancher for Microsoft AD FS]({{}}/rancher/v2.6/en/admin-settings/authentication/microsoft-adfs/rancher-adfs-setup) - -{{< saml_caveats >}} - - -### [Next: Configuring Microsoft AD FS for Rancher]({{}}/rancher/v2.6/en/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup) diff --git a/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/rancher-adfs-setup/rancher-adfs-setup.md b/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/rancher-adfs-setup/rancher-adfs-setup.md deleted file mode 100644 index d7424d986fd..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/microsoft-adfs/rancher-adfs-setup/rancher-adfs-setup.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: 2. Configuring Rancher for Microsoft AD FS -weight: 1205 ---- - -After you complete [Configuring Microsoft AD FS for Rancher]({{}}/rancher/v2.6/en/admin-settings/authentication/microsoft-adfs/microsoft-adfs-setup/), enter your AD FS information into Rancher to allow AD FS users to authenticate with Rancher. - ->**Important Notes For Configuring Your ADFS Server:** -> ->- The SAML 2.0 WebSSO Protocol Service URL is: `https:///v1-saml/adfs/saml/acs` ->- The Relying Party Trust identifier URL is: `https:///v1-saml/adfs/saml/metadata` ->- You must export the `federationmetadata.xml` file from your AD FS server. This can be found at: `https:///federationmetadata/2007-06/federationmetadata.xml` - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **ADFS**. -1. Complete the **Configure AD FS Account** form. Microsoft AD FS lets you specify an existing Active Directory (AD) server. The [configuration section below](#configuration) describe how you can map AD attributes to fields within Rancher. -1. After you complete the **Configure AD FS Account** form, click **Enable**. - - Rancher redirects you to the AD FS login page. Enter credentials that authenticate with Microsoft AD FS to validate your Rancher AD FS configuration. - - >**Note:** You may have to disable your popup blocker to see the AD FS login page. - -**Result:** Rancher is configured to work with MS FS. Your users can now sign into Rancher using their MS FS logins. - -# Configuration - -| Field | Description | -|---------------------------|-----------------| -| Display Name Field | The AD attribute that contains the display name of users.

Example: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` | -| User Name Field | The AD attribute that contains the user name/given name.

Example: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname` | -| UID Field | An AD attribute that is unique to every user.

Example: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn` | -| Groups Field | Make entries for managing group memberships.

Example: `http://schemas.xmlsoap.org/claims/Group` | -| Rancher API Host | The URL for your Rancher Server. | -| Private Key / Certificate | This is a key-certificate pair to create a secure shell between Rancher and your AD FS. Ensure you set the Common Name (CN) to your Rancher Server URL.

[Certificate creation command](#cert-command) | -| Metadata XML | The `federationmetadata.xml` file exported from your AD FS server.

You can find this file at `https:///federationmetadata/2007-06/federationmetadata.xml`. | - - - - -**Tip:** You can generate a certificate using an openssl command. For example: - -``` -openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj "/CN=myservice.example.com" -``` diff --git a/versioned_docs/version-2.6/admin-settings/authentication/okta/okta.md b/versioned_docs/version-2.6/admin-settings/authentication/okta/okta.md deleted file mode 100644 index 919bb90cd41..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/okta/okta.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Configuring Okta (SAML) -weight: 1210 ---- - -If your organization uses Okta Identity Provider (IdP) for user authentication, you can configure Rancher to allow your users to log in using their IdP credentials. - ->**Note:** Okta integration only supports Service Provider initiated logins. - -## Prerequisites - -In Okta, create a SAML Application with the settings below. See the [Okta documentation](https://developer.okta.com/standards/SAML/setting_up_a_saml_application_in_okta) for help. - -Setting | Value -------------|------------ -`Single Sign on URL` | `https://yourRancherHostURL/v1-saml/okta/saml/acs` -`Audience URI (SP Entity ID)` | `https://yourRancherHostURL/v1-saml/okta/saml/metadata` - -## Configuring Okta in Rancher - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **Okta**. -1. Complete the **Configure Okta Account** form. The examples below describe how you can map Okta attributes from attribute statements to fields within Rancher. - - | Field | Description | - | ------------------------- | ----------------------------------------------------------------------------- | - | Display Name Field | The attribute name from an attribute statement that contains the display name of users. | - | User Name Field | The attribute name from an attribute statement that contains the user name/given name. | - | UID Field | The attribute name from an attribute statement that is unique to every user. | - | Groups Field | The attribute name in a group attribute statement that exposes your groups. | - | Rancher API Host | The URL for your Rancher Server. | - | Private Key / Certificate | A key/certificate pair used for Assertion Encryption. | - | Metadata XML | The `Identity Provider metadata` file that you find in the application `Sign On` section. | - - >**Tip:** You can generate a key/certificate pair using an openssl command. For example: - > - > openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout myservice.key -out myservice.crt - - - -1. After you complete the **Configure Okta Account** form, click **Enable**. - - Rancher redirects you to the IdP login page. Enter credentials that authenticate with Okta IdP to validate your Rancher Okta configuration. - - >**Note:** If nothing seems to happen, it's likely because your browser blocked the pop-up. Make sure you disable the pop-up blocker for your rancher domain and whitelist it in any other extensions you might utilize. - -**Result:** Rancher is configured to work with Okta. Your users can now sign into Rancher using their Okta logins. - -{{< saml_caveats >}} diff --git a/versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap-config/openldap-config.md b/versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap-config/openldap-config.md deleted file mode 100644 index deb1b0799f9..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap-config/openldap-config.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: OpenLDAP Configuration Reference -weight: 2 ---- - -This section is intended to be used as a reference when setting up an OpenLDAP authentication provider in Rancher. - -For further details on configuring OpenLDAP, refer to the [official documentation.](https://www.openldap.org/doc/) - -> Before you proceed with the configuration, please familiarize yourself with the concepts of [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -- [Background: OpenLDAP Authentication Flow](#background-openldap-authentication-flow) -- [OpenLDAP server configuration](#openldap-server-configuration) -- [User/group schema configuration](#user-group-schema-configuration) - - [User schema configuration](#user-schema-configuration) - - [Group schema configuration](#group-schema-configuration) - -## Background: OpenLDAP Authentication Flow - -1. When a user attempts to login with LDAP credentials, Rancher creates an initial bind to the LDAP server using a service account with permissions to search the directory and read user/group attributes. -2. Rancher then searches the directory for the user by using a search filter based on the provided username and configured attribute mappings. -3. Once the user has been found, they are authenticated with another LDAP bind request using the user's DN and provided password. -4. Once authentication succeeded, Rancher then resolves the group memberships both from the membership attribute in the user's object and by performing a group search based on the configured user mapping attribute. - -# OpenLDAP Server Configuration - -You will need to enter the address, port, and protocol to connect to your OpenLDAP server. `389` is the standard port for insecure traffic, `636` for TLS traffic. - -> **Using TLS?** -> -> If the certificate used by the OpenLDAP server is self-signed or not from a recognized certificate authority, make sure have at hand the CA certificate (concatenated with any intermediate certificates) in PEM format. You will have to paste in this certificate during the configuration so that Rancher is able to validate the certificate chain. - -If you are in doubt about the correct values to enter in the user/group Search Base configuration fields, consult your LDAP administrator or refer to the section [Identify Search Base and Schema using ldapsearch]({{}}/rancher/v2.6/en/admin-settings/authentication/ad/#annex-identify-search-base-and-schema-using-ldapsearch) in the Active Directory authentication documentation. - -
OpenLDAP Server Parameters
- -| Parameter | Description | -|:--|:--| -| Hostname | Specify the hostname or IP address of the OpenLDAP server | -| Port | Specify the port at which the OpenLDAP server is listening for connections. Unencrypted LDAP normally uses the standard port of 389, while LDAPS uses port 636.| -| TLS | Check this box to enable LDAP over SSL/TLS (commonly known as LDAPS). You will also need to paste in the CA certificate if the server uses a self-signed/enterprise-signed certificate. | -| Server Connection Timeout | The duration in number of seconds that Rancher waits before considering the server unreachable. | -| Service Account Distinguished Name | Enter the Distinguished Name (DN) of the user that should be used to bind, search and retrieve LDAP entries. | -| Service Account Password | The password for the service account. | -| User Search Base | Enter the Distinguished Name of the node in your directory tree from which to start searching for user objects. All users must be descendents of this base DN. For example: "ou=people,dc=acme,dc=com".| -| Group Search Base | If your groups live under a different node than the one configured under `User Search Base` you will need to provide the Distinguished Name here. Otherwise leave this field empty. For example: "ou=groups,dc=acme,dc=com".| - -# User/Group Schema Configuration - -If your OpenLDAP directory deviates from the standard OpenLDAP schema, you must complete the **Customize Schema** section to match it. - -Note that the attribute mappings configured in this section are used by Rancher to construct search filters and resolve group membership. It is therefore always recommended to verify that the configuration here matches the schema used in your OpenLDAP. - -If you are unfamiliar with the user/group schema used in the OpenLDAP server, consult your LDAP administrator or refer to the section [Identify Search Base and Schema using ldapsearch]({{}}/rancher/v2.6/en/admin-settings/authentication/ad/#annex-identify-search-base-and-schema-using-ldapsearch) in the Active Directory authentication documentation. - -### User Schema Configuration - -The table below details the parameters for the user schema configuration. - -
User Schema Configuration Parameters
- -| Parameter | Description | -|:--|:--| -| Object Class | The name of the object class used for user objects in your domain. If defined, only specify the name of the object class - *don't* include it in an LDAP wrapper such as &(objectClass=xxxx) | -| Username Attribute | The user attribute whose value is suitable as a display name. | -| Login Attribute | The attribute whose value matches the username part of credentials entered by your users when logging in to Rancher. This is typically `uid`. | -| User Member Attribute | The user attribute containing the Distinguished Name of groups a user is member of. Usually this is one of `memberOf` or `isMemberOf`. | -| Search Attribute | When a user enters text to add users or groups in the UI, Rancher queries the LDAP server and attempts to match users by the attributes provided in this setting. Multiple attributes can be specified by separating them with the pipe ("\|") symbol. | -| User Enabled Attribute | If the schema of your OpenLDAP server supports a user attribute whose value can be evaluated to determine if the account is disabled or locked, enter the name of that attribute. The default OpenLDAP schema does not support this and the field should usually be left empty. | -| Disabled Status Bitmask | This is the value for a disabled/locked user account. The parameter is ignored if `User Enabled Attribute` is empty. | - -### Group Schema Configuration - -The table below details the parameters for the group schema configuration. - -
Group Schema Configuration Parameters
- -| Parameter | Description | -|:--|:--| -| Object Class | The name of the object class used for group entries in your domain. If defined, only specify the name of the object class - *don't* include it in an LDAP wrapper such as &(objectClass=xxxx) | -| Name Attribute | The group attribute whose value is suitable for a display name. | -| Group Member User Attribute | The name of the **user attribute** whose format matches the group members in the `Group Member Mapping Attribute`. | -| Group Member Mapping Attribute | The name of the group attribute containing the members of a group. | -| Search Attribute | Attribute used to construct search filters when adding groups to clusters or projects in the UI. See description of user schema `Search Attribute`. | -| Group DN Attribute | The name of the group attribute whose format matches the values in the user's group membership attribute. See `User Member Attribute`. | -| Nested Group Membership | This settings defines whether Rancher should resolve nested group memberships. Use only if your organization makes use of these nested memberships (ie. you have groups that contain other groups as members). This option is disabled if you are using Shibboleth. | \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap.md b/versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap.md deleted file mode 100644 index dd722903236..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/openldap/openldap.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Configuring OpenLDAP -weight: 1113 ---- - -If your organization uses LDAP for user authentication, you can configure Rancher to communicate with an OpenLDAP server to authenticate users. This allows Rancher admins to control access to clusters and projects based on users and groups managed externally in the organisation's central user repository, while allowing end-users to authenticate with their LDAP credentials when logging in to the Rancher UI. - -## Prerequisites - -Rancher must be configured with a LDAP bind account (aka service account) to search and retrieve LDAP entries pertaining to users and groups that should have access. It is recommended to not use an administrator account or personal account for this purpose and instead create a dedicated account in OpenLDAP with read-only access to users and groups under the configured search base (see below). - -> **Using TLS?** -> -> If the certificate used by the OpenLDAP server is self-signed or not from a recognised certificate authority, make sure have at hand the CA certificate (concatenated with any intermediate certificates) in PEM format. You will have to paste in this certificate during the configuration so that Rancher is able to validate the certificate chain. - -## Configure OpenLDAP in Rancher - -Configure the settings for the OpenLDAP server, groups and users. For help filling out each field, refer to the [configuration reference.](./openldap-config) - -> Before you proceed with the configuration, please familiarise yourself with the concepts of [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **OpenLDAP**. Fill out the **Configure an OpenLDAP server** form. -1. Click **Enable**. - -### Test Authentication - -Once you have completed the configuration, proceed by testing the connection to the OpenLDAP server. Authentication with OpenLDAP will be enabled implicitly if the test is successful. - -> **Note:** -> -> The OpenLDAP user pertaining to the credentials entered in this step will be mapped to the local principal account and assigned administrator privileges in Rancher. You should therefore make a conscious decision on which LDAP account you use to perform this step. - -1. Enter the **username** and **password** for the OpenLDAP account that should be mapped to the local principal account. -2. Click **Authenticate With OpenLDAP** to test the OpenLDAP connection and finalise the setup. - -**Result:** - -- OpenLDAP authentication is configured. -- The LDAP user pertaining to the entered credentials is mapped to the local principal (administrative) account. - -> **Note:** -> -> You will still be able to login using the locally configured `admin` account and password in case of a disruption of LDAP services. - -## Annex: Troubleshooting - -If you are experiencing issues while testing the connection to the OpenLDAP server, first double-check the credentials entered for the service account as well as the search base configuration. You may also inspect the Rancher logs to help pinpointing the problem cause. Debug logs may contain more detailed information about the error. Please refer to [How can I enable debug logging]({{}}/rancher/v2.6/en/faq/technical/#how-can-i-enable-debug-logging) in this documentation. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/ping-federate/ping-federate.md b/versioned_docs/version-2.6/admin-settings/authentication/ping-federate/ping-federate.md deleted file mode 100644 index 484b0a1610c..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/ping-federate/ping-federate.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Configuring PingIdentity (SAML) -weight: 1200 ---- - -If your organization uses Ping Identity Provider (IdP) for user authentication, you can configure Rancher to allow your users to log in using their IdP credentials. - ->**Prerequisites:** -> ->- You must have a [Ping IdP Server](https://www.pingidentity.com/) configured. ->- Following are the Rancher Service Provider URLs needed for configuration: -Metadata URL: `https:///v1-saml/ping/saml/metadata` -Assertion Consumer Service (ACS) URL: `https:///v1-saml/ping/saml/acs` -Note that these URLs will not return valid data until the authentication configuration is saved in Rancher. ->- Export a `metadata.xml` file from your IdP Server. For more information, see the [PingIdentity documentation](https://documentation.pingidentity.com/pingfederate/pf83/index.shtml#concept_exportingMetadata.html). - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **Ping Identity**. -1. Complete the **Configure a Ping Account** form. Ping IdP lets you specify what data store you want to use. You can either add a database or use an existing ldap server. For example, if you select your Active Directory (AD) server, the examples below describe how you can map AD attributes to fields within Rancher. - - 1. **Display Name Field**: Enter the AD attribute that contains the display name of users (example: `displayName`). - - 1. **User Name Field**: Enter the AD attribute that contains the user name/given name (example: `givenName`). - - 1. **UID Field**: Enter an AD attribute that is unique to every user (example: `sAMAccountName`, `distinguishedName`). - - 1. **Groups Field**: Make entries for managing group memberships (example: `memberOf`). - - 1. **Entity ID Field** (optional): The published, protocol-dependent, unique identifier of your partner. This ID defines your organization as the entity operating the server for SAML 2.0 transactions. This ID may have been obtained out-of-band or via a SAML metadata file. - - 1. **Rancher API Host**: Enter the URL for your Rancher Server. - - 1. **Private Key** and **Certificate**: This is a key-certificate pair to create a secure shell between Rancher and your IdP. - - You can generate one using an openssl command. For example: - - ``` - openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj "/CN=myservice.example.com" - ``` - 1. **IDP-metadata**: The `metadata.xml` file that you [exported from your IdP server](https://documentation.pingidentity.com/pingfederate/pf83/index.shtml#concept_exportingMetadata.html). - - -1. After you complete the **Configure Ping Account** form, click **Enable**. - - Rancher redirects you to the IdP login page. Enter credentials that authenticate with Ping IdP to validate your Rancher PingIdentity configuration. - - >**Note:** You may have to disable your popup blocker to see the IdP login page. - -**Result:** Rancher is configured to work with PingIdentity. Your users can now sign into Rancher using their PingIdentity logins. - -{{< saml_caveats >}} diff --git a/versioned_docs/version-2.6/admin-settings/authentication/shibboleth/about/about.md b/versioned_docs/version-2.6/admin-settings/authentication/shibboleth/about/about.md deleted file mode 100644 index fc8797e82ef..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/shibboleth/about/about.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Group Permissions with Shibboleth and OpenLDAP -weight: 1 ---- - -This page provides background information and context for Rancher users who intend to set up the Shibboleth authentication provider in Rancher. - -Because Shibboleth is a SAML provider, it does not support searching for groups. While a Shibboleth integration can validate user credentials, it can't be used to assign permissions to groups in Rancher without additional configuration. - -One solution to this problem is to configure an OpenLDAP identity provider. With an OpenLDAP back end for Shibboleth, you will be able to search for groups in Rancher and assign them to resources such as clusters, projects, or namespaces from the Rancher UI. - -### Terminology - -- **Shibboleth** is a single sign-on log-in system for computer networks and the Internet. It allows people to sign in using just one identity to various systems. It validates user credentials, but does not, on its own, handle group memberships. -- **SAML:** Security Assertion Markup Language, an open standard for exchanging authentication and authorization data between an identity provider and a service provider. -- **OpenLDAP:** a free, open-source implementation of the Lightweight Directory Access Protocol (LDAP). It is used to manage an organization’s computers and users. OpenLDAP is useful for Rancher users because it supports groups. In Rancher, it is possible to assign permissions to groups so that they can access resources such as clusters, projects, or namespaces, as long as the groups already exist in the identity provider. -- **IdP or IDP:** An identity provider. OpenLDAP is an example of an identity provider. - -### Adding OpenLDAP Group Permissions to Rancher Resources - -The diagram below illustrates how members of an OpenLDAP group can access resources in Rancher that the group has permissions for. - -For example, a cluster owner could add an OpenLDAP group to a cluster so that they have permissions view most cluster level resources and create new projects. Then the OpenLDAP group members will have access to the cluster as soon as they log in to Rancher. - -In this scenario, OpenLDAP allows the cluster owner to search for groups when assigning persmissions. Without OpenLDAP, the functionality to search for groups would not be supported. - -When a member of the OpenLDAP group logs in to Rancher, she is redirected to Shibboleth and enters her username and password. - -Shibboleth validates her credentials, and retrieves user attributes from OpenLDAP, including groups. Then Shibboleth sends a SAML assertion to Rancher including the user attributes. Rancher uses the group data so that she can access all of the resources and permissions that her groups have permissions for. - -![Adding OpenLDAP Group Permissions to Rancher Resources]({{}}/img/rancher/shibboleth-with-openldap-groups.svg) - \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/authentication/shibboleth/shibboleth.md b/versioned_docs/version-2.6/admin-settings/authentication/shibboleth/shibboleth.md deleted file mode 100644 index f5ff30298e7..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/shibboleth/shibboleth.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Configuring Shibboleth (SAML) -weight: 1210 ---- - -If your organization uses Shibboleth Identity Provider (IdP) for user authentication, you can configure Rancher to allow your users to log in to Rancher using their Shibboleth credentials. - -In this configuration, when Rancher users log in, they will be redirected to the Shibboleth IdP to enter their credentials. After authentication, they will be redirected back to the Rancher UI. - -If you also configure OpenLDAP as the back end to Shibboleth, it will return a SAML assertion to Rancher with user attributes that include groups. Then the authenticated user will be able to access resources in Rancher that their groups have permissions for. - -> The instructions in this section assume that you understand how Rancher, Shibboleth, and OpenLDAP work together. For a more detailed explanation of how it works, refer to [this page.](./about) - -This section covers the following topics: - -- [Setting up Shibboleth in Rancher](#setting-up-shibboleth-in-rancher) - - [Shibboleth Prerequisites](#shibboleth-prerequisites) - - [Configure Shibboleth in Rancher](#configure-shibboleth-in-rancher) - - [SAML Provider Caveats](#saml-provider-caveats) -- [Setting up OpenLDAP in Rancher](#setting-up-openldap-in-rancher) - - [OpenLDAP Prerequisites](#openldap-prerequisites) - - [Configure OpenLDAP in Rancher](#configure-openldap-in-rancher) - - [Troubleshooting](#troubleshooting) - -# Setting up Shibboleth in Rancher - -### Shibboleth Prerequisites -> ->- You must have a Shibboleth IdP Server configured. ->- Following are the Rancher Service Provider URLs needed for configuration: -Metadata URL: `https:///v1-saml/shibboleth/saml/metadata` -Assertion Consumer Service (ACS) URL: `https:///v1-saml/shibboleth/saml/acs` ->- Export a `metadata.xml` file from your IdP Server. For more information, see the [Shibboleth documentation.](https://wiki.shibboleth.net/confluence/display/SP3/Home) - -### Configure Shibboleth in Rancher - -If your organization uses Shibboleth for user authentication, you can configure Rancher to allow your users to log in using their IdP credentials. - -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **Shibboleth**. -1. Complete the **Configure Shibboleth Account** form. Shibboleth IdP lets you specify what data store you want to use. You can either add a database or use an existing ldap server. For example, if you select your Active Directory (AD) server, the examples below describe how you can map AD attributes to fields within Rancher. - - 1. **Display Name Field**: Enter the AD attribute that contains the display name of users (example: `displayName`). - - 1. **User Name Field**: Enter the AD attribute that contains the user name/given name (example: `givenName`). - - 1. **UID Field**: Enter an AD attribute that is unique to every user (example: `sAMAccountName`, `distinguishedName`). - - 1. **Groups Field**: Make entries for managing group memberships (example: `memberOf`). - - 1. **Rancher API Host**: Enter the URL for your Rancher Server. - - 1. **Private Key** and **Certificate**: This is a key-certificate pair to create a secure shell between Rancher and your IdP. - - You can generate one using an openssl command. For example: - - ``` - openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj "/CN=myservice.example.com" - ``` - 1. **IDP-metadata**: The `metadata.xml` file that you exported from your IdP server. - - -1. After you complete the **Configure Shibboleth Account** form, click **Enable**. - - Rancher redirects you to the IdP login page. Enter credentials that authenticate with Shibboleth IdP to validate your Rancher Shibboleth configuration. - - >**Note:** You may have to disable your popup blocker to see the IdP login page. - -**Result:** Rancher is configured to work with Shibboleth. Your users can now sign into Rancher using their Shibboleth logins. - -### SAML Provider Caveats - -If you configure Shibboleth without OpenLDAP, the following caveats apply due to the fact that SAML Protocol does not support search or lookup for users or groups. - -- There is no validation on users or groups when assigning permissions to them in Rancher. -- When adding users, the exact user IDs (i.e. UID Field) must be entered correctly. As you type the user ID, there will be no search for other user IDs that may match. -- When adding groups, you must select the group from the drop-down that is next to the text box. Rancher assumes that any input from the text box is a user. -- The group drop-down shows only the groups that you are a member of. You will not be able to add groups that you are not a member of. - -To enable searching for groups when assigning permissions in Rancher, you will need to configure a back end for the SAML provider that supports groups, such as OpenLDAP. - -# Setting up OpenLDAP in Rancher - -If you also configure OpenLDAP as the back end to Shibboleth, it will return a SAML assertion to Rancher with user attributes that include groups. Then authenticated users will be able to access resources in Rancher that their groups have permissions for. - -### OpenLDAP Prerequisites - -Rancher must be configured with a LDAP bind account (aka service account) to search and retrieve LDAP entries pertaining to users and groups that should have access. It is recommended to not use an administrator account or personal account for this purpose and instead create a dedicated account in OpenLDAP with read-only access to users and groups under the configured search base (see below). - -> **Using TLS?** -> -> If the certificate used by the OpenLDAP server is self-signed or not from a recognized certificate authority, make sure have at hand the CA certificate (concatenated with any intermediate certificates) in PEM format. You will have to paste in this certificate during the configuration so that Rancher is able to validate the certificate chain. - -### Configure OpenLDAP in Rancher - -Configure the settings for the OpenLDAP server, groups and users. For help filling out each field, refer to the [configuration reference.]({{}}/rancher/v2.6/en/admin-settings/authentication/openldap/openldap-config) Note that nested group membership is not available for Shibboleth. - -> Before you proceed with the configuration, please familiarise yourself with the concepts of [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -1. Log into the Rancher UI using the initial local `admin` account. -1. In the top left corner, click **☰ > Users & Authentication**. -1. In the left navigation menu, click **Auth Provider**. -1. Click **OpenLDAP**. The **Configure an OpenLDAP server** form will be displayed. - -# Troubleshooting - -If you are experiencing issues while testing the connection to the OpenLDAP server, first double-check the credentials entered for the service account as well as the search base configuration. You may also inspect the Rancher logs to help pinpointing the problem cause. Debug logs may contain more detailed information about the error. Please refer to [How can I enable debug logging]({{}}/rancher/v2.6/en/faq/technical/#how-can-i-enable-debug-logging) in this documentation. diff --git a/versioned_docs/version-2.6/admin-settings/authentication/user-groups/user-groups.md b/versioned_docs/version-2.6/admin-settings/authentication/user-groups/user-groups.md deleted file mode 100644 index f82c58a3935..00000000000 --- a/versioned_docs/version-2.6/admin-settings/authentication/user-groups/user-groups.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Users and Groups -weight: 1 ---- - -Rancher relies on users and groups to determine who is allowed to log in to Rancher and which resources they can access. When you configure an external authentication provider, users from that provider will be able to log in to your Rancher server. When a user logs in, the authentication provider will supply your Rancher server with a list of groups to which the user belongs. - -Access to clusters, projects, multi-cluster apps, and global DNS providers and entries can be controlled by adding either individual users or groups to these resources. When you add a group to a resource, all users who are members of that group in the authentication provider, will be able to access the resource with the permissions that you've specified for the group. For more information on roles and permissions, see [Role Based Access Control]({{}}/rancher/v2.6/en/admin-settings/rbac/). - -## Managing Members - -When adding a user or group to a resource, you can search for users or groups by beginning to type their name. The Rancher server will query the authentication provider to find users and groups that match what you've entered. Searching is limited to the authentication provider that you are currently logged in with. For example, if you've enabled GitHub authentication but are logged in using a [local]({{}}/rancher/v2.6/en/admin-settings/authentication/local/) user account, you will not be able to search for GitHub users or groups. - -All users, whether they are local users or from an authentication provider, can be viewed and managed. In the upper left corner, click **☰ > Users & Authentication**. In the left navigation bar, click **Users**. - -{{< saml_caveats >}} - -## User Information - -Rancher maintains information about each user that logs in through an authentication provider. This information includes whether the user is allowed to access your Rancher server and the list of groups that the user belongs to. Rancher keeps this user information so that the CLI, API, and kubectl can accurately reflect the access that the user has based on their group membership in the authentication provider. - -Whenever a user logs in to the UI using an authentication provider, Rancher automatically updates this user information. - -### Automatically Refreshing User Information - -Rancher will periodically refresh the user information even before a user logs in through the UI. You can control how often Rancher performs this refresh. - -Two settings control this behavior: - -- **`auth-user-info-max-age-seconds`** - - This setting controls how old a user's information can be before Rancher refreshes it. If a user makes an API call (either directly or by using the Rancher CLI or kubectl) and the time since the user's last refresh is greater than this setting, then Rancher will trigger a refresh. This setting defaults to `3600` seconds, i.e. 1 hour. - -- **`auth-user-info-resync-cron`** - - This setting controls a recurring schedule for resyncing authentication provider information for all users. Regardless of whether a user has logged in or used the API recently, this will cause the user to be refreshed at the specified interval. This setting defaults to `0 0 * * *`, i.e. once a day at midnight. See the [Cron documentation](https://en.wikipedia.org/wiki/Cron) for more information on valid values for this setting. - -To change these settings, - -1. In the upper left corner, click **☰ > Global Settings**. -1. Go to the setting you want to configure and click **⋮ > Edit Setting**. - -> **Note:** Since SAML does not support user lookup, SAML-based authentication providers do not support periodically refreshing user information. User information will only be refreshed when the user logs into the Rancher UI. - -### Manually Refreshing User Information - -If you are not sure the last time Rancher performed an automatic refresh of user information, you can perform a manual refresh of all users. - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. On the **Users** page, click on **Refresh Group Memberships**. - -**Results:** Rancher refreshes the user information for all users. Requesting this refresh will update which users can access Rancher as well as all the groups that each user belongs to. - ->**Note:** Since SAML does not support user lookup, SAML-based authentication providers do not support the ability to manually refresh user information. User information will only be refreshed when the user logs into the Rancher UI. - - -## Session Length - -The default length (TTL) of each user session is adjustable. The default session length is 16 hours. - -1. In the upper left corner, click **☰ > Global Settings**. -1. Go to **`auth-user-session-ttl-minutes`** and click **⋮ > Edit Setting**. -1. Enter the amount of time in minutes a session length should last and click **Save**. - -**Result:** Users are automatically logged out of Rancher after the set number of minutes. diff --git a/versioned_docs/version-2.6/admin-settings/branding/branding.md b/versioned_docs/version-2.6/admin-settings/branding/branding.md deleted file mode 100644 index fcd8e53345f..00000000000 --- a/versioned_docs/version-2.6/admin-settings/branding/branding.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -title: Custom Branding -weight: 90 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Rancher v2.6 introduced the ability to customize Rancher’s branding and navigation links. - -- [Changing Brand Settings](#changing-brand-settings) -- [Brand Configuration](#brand-configuration) -- [Custom Navigation Links](#custom-navigation-links) -- [Link Configuration](#link-configuration) -- [Link Examples](#link-examples) - -# Changing Brand Settings - -> **Prerequisite:** You will need to have at least cluster member permissions. - -To configure the brand settings, - -1. Click **☰ > Global settings**. -2. Click **Branding**. - -# Brand Configuration - -### Private Label Company Name - -This option replaces “Rancher” with the value you provide in most places. Files that need to have Rancher in the name, such as “rancher-compose.yml”, will not be changed. - -### Support Links - -Use a url address to send new "File an Issue" reports instead of sending users to the Github issues page. Optionally show Rancher community support links. - -### Logo - -Upload light and dark logos to replace the Rancher logo in the top-level navigation header. - -### Primary Color - -You can override the primary color used throughout the UI with a custom color of your choice. - -### Fixed Banners - - - - -Display a custom fixed banner in the header, footer, or both. - - - - -Display a custom fixed banner in the header, footer, or both. - -As of Rancher v2.6.4, configuration of fixed banners has moved from the **Branding** tab to the **Banners** tab. - -To configure banner settings, - -1. Click **☰ > Global settings**. -2. Click **Banners**. - - - - -# Custom Navigation Links - -In this section, you'll learn how to configure the links in the left navigation bar of the **Cluster Dashboard**. To get to the cluster dashboard, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want custom navigation links and click **Explore**. - -It can be useful to add a link for quick access to services installed on a cluster. For example, you could add a link to the Kiali UI for clusters with Istio installed, or you could add a link to the Grafana UI for clusters with Rancher monitoring installed. - -The custom links don't affect who has access to each service. - -Links can be created at the top level and multiple links can be grouped together. - -### Adding a Custom Navigation Link - -> **Prerequisite:** You will need to have at least cluster member or project member permissions. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you would like to add custom navigation links and click **Explore**. -2. In the top navigation menu, click **🔍 (Resource Search)**. -3. Type **Nav** and click **Nav Links**. -4. Click **Create from YAML**. -5. The simplest way to create a navigation link is to add these fields: - - name: linkname - toURL: https://example.com - - For more details on setting up links, including optional fields, see [Link Configuration.](#link-configuration) -6. Click **Create**. - -# Link Configuration - -### `name` - -Display name for the link. Required. - -### `group` - -Name of a group of links that expands when clicked. - -Optional. If not provided, the link appears standalone. - -Groups are displayed separately from standalone links, as shown below: - -![Screenshot of group and standalone link]({{}}/img/rancher/grouped-vs-standalone-links.png) - -### `iconSrc` - -Icon source in in base64 format. - -Below is an example of the Grafana logo in base64 format: - -``` -data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMgAAADICAYAAACtWK6eAAAgAElEQVR4Aey9d5xkZZn3zb/P+3mffZ9nDcDAzHTuqs49PZEhCBhBJc10nO7pHKbD9PR07p5AWlEEZM2ioph3dXGNqLgCxhVBRIYRmNy5cjqnTlWdqu/7ue5zTk+DiNIsCn4suOacrjrxvq/fle/7PofX+ycDZNT/pIAUaUUmaRBKp8FMQ1L9qL6S4+VYUikIeuBrn+LppiuJNG/BvHYd7HbhbXLBZ/dB8AkwFokCHsAH6Kb8IxTHJIyBHwgDMTBT6h7yWAmb1L3sxyEjfxkYxDDQMa0nWV0vyE2slwZ5JtUO8v5JUhgk0EkRw5TnUg9sgJm03lsezkyTIU0C2VrNJU2WsdtTPVQyAmYU4mGIhDESaULAcSG5RjwJEQ8YsxgEOZoOcSxjvXsyKM8nL24QJ4UmF5TnlL7IWLure/G/3lnn/PVu9SrdaQVApO3/CCAZAYjNSLIVBrD/VMwSnsf4/B38ofWthFu3krhhPZmaLJZuyEY7vJPIV++AwEnImJwJ66qTFcMLSswkGWKkiKqtMIICwB890zL/2lwoHGLYnCIMtMqP3Md5N7mMDRDTBkhKAURAqNBs3TOdspjWERgrmkYuJbQMEPUeKdAEIBrIuSIKEiZ+B0ShADz7W/Tjv8TMLOIjybxcJwNJOUgAkjHQSFoAkedMWn2g7rXKV/9rnfZ3DRCRjgoN0ik2A0nDLgMkbYD3aU7dPcRT7ZfhadmEVldA/IZ1RN6TRahxO8f37CTyxU/B4pySvOlYHNM0sZhQRKgwTRrRWALOZc0lWksoY30n0lPkuMBCPYCcKn/Ic632Iy/ivNvy+4k2EOAamDbJ/rIKFYEhx74AWPIWcpRhv8dyu5mQTEEkmUYTjSsaMBWDiA9mjsF/foWTH76Z33zqEL6jD5IgRkTeR64valfOQQSL6My0Ap/c32qvlNJgq339v8Z5fzcAkcayBKrFkNIBCiDOD/Lj8jG2iZWOwvGHefxQNY+3beHk7grCDS7067JhRwn6dZX4d72L3zVei/6Vz0HYB/EQJINKawRTQXVP+UfYQEjdRphITBlTNIrFqBopIsqcsZnaQYww0iv5yA1XkuJ+eRJREStJvrMFhnO8A5S09ewCDoMkCQUw67KxOMQMCBkpkok4JIIQnYGf3k/s7mlO7N3Fw7VX8J2Ot3Pi/rvBXMLMJKxbx+UR5L4CEJ0IKYUbeV0xAUXDZVSrvZIGeHXPff0DRDGE9PRZPhGec8jhBWcr30uXCWEG4Xf/wW+H38ajXVUcaS7GX+dGvyYX6jeQvL6MZO1lzFx7Mc81XkPyM3eC/xlIz5LJzBIz/bbUtUyKZaksUtPUIS06wzK/LGluM6jwrVg9wkCvECDOe51lE2kL5w2drdU+Ths5bSBbMacsVMtGtKDFug5+5Q00Iw2JFOhhmD0C3/goS6M1HKvfiqfxMo7t3MLv2i7F97nDoJ+BpG45IXLysgYRgIhvJPeRu4QVibZ7LX/+rgDiNLTT58IADjM4rPI8HyXpgYc+yXODF3G0ZyPPtZSxUFeM/9p8MrUVJK4rIX5NMfEdm1jauZ1j7Vfj/exNcPoRSB2HxIICiHI+Hb4U00mYSWkP4RAhHTKiUexggfCEPJDiUOepX/5W3tN5R9m3PpZZJ6bdWbJ+kWPkto51JyaVxbBnpYtcT35XwFDXt8Ee8cJ//wj9X6c40fF2TtZU4qspJV5bidawCU/HxWgfHoTwccuhl4srE0saRnwQwwaIZQKa+BH6B0CcfnvVttIBK8jmFId5zjKEmA+WhJTIkeoYYxY+t5/FtmJ8zeUEWzdypqmM07VFhGpK0W9wYVyXh15dQLxnG/NdF/NE00V4PzgAv/0OLB5RbyWKQD2CML5wV1KMbIlmCSgkapQEkcLCNPJ72mJAsdXl+Vb7cRh+mcnlQvKl0IomUfs2mOT28rwCaiErgiW+hXWOaBSnzRSw4/Mw/wR87zN4xht55vqNzNxQQXj3VoyWzRjX5ZPcWUigrozozU0QeMbSNAnIyA0EcaQRE1N8EPWn0hoSDxSSRnntfl73GkTMAsvXsDnCYZAXMERc2dei2i0HVnWMdpro4etYuv58orUujLatLLZsZKapkqXaYqINRZi7XWQ63ASacwh2lhPtvZwjdVs4M94ETz4M8ajFjI5TLlsJLavwsu0GCA84JpX4uEAAVHBYGHa1H3lVuZaQxXgvAIh86QDFDqu+ECDSIstS3AGWnCdmUnwRjv4Y/XMHON51OSerSwjv2kCqdRta81ZiDZWwqwjq8onWFKIfrIPQs5CIKl/ekJvZDyagFJJbWKFuiQFLePwfJtZq+//PnieNLc64lUuwTYoXMITwZowMgbSu3EIjE8NMiKMdhmd/zlzrRjJ12UQb3IQaKojUbiRUW8VSQynzjQV4mtfjbz6fSNN5hBvXsrjbzXzTZjz1V/Bs0/Xw0A9g7qRy3E3DRzARUJpKni0ZSljpEUkcCEBsQR3BYIEIC2mxw+WBV/dx3v950TP5UshpBxskqURG+cvCjtImwqyyDYZ9pDPiMKfR4hHQY5aJdPIIPPg1jrS/nZndW/E0lRJodBHY5SbYUEq4biOx2goi16+D1iLCO/PwDL0HfvdD5X9JFNwXP+vjyL2UMJDnUs8kRpzkjv4BkNX1/l9wlmiOhHL4RIbaDrA0vs0UwifSMVEkuSWJsyTxRACMIKSi8Nj3WWyphLr16PWFaPVlGDs3ou2swldXpgCy0LoWT+t5RJreqEASaMpRDGLs2E6w+u2c7mkgcM/t8IdHID2PSZAQUaJmSrkAypgXXrClaTIj5kZcRXXiKlH4ygAibXA2Yme3wUqAJDMWWDJgGEmiWgzDFL1hCRcjHkWP+kgaPkgHQUyqIz8l+fHDzLa/i0DdVrTaUmL1LsINBTZIignXVRCpK8W3cx3Jdjehnfl4970bHnsA0rpi/QWxLqUf7SiZ2pd/BBPio0kQQyVO/4LO/hsd8ro2sYQxRPYJSJSZJYwhHSBkWoJUABJRqTLRM0m08KKlPYwgiR99kZOdlRi71pOuKSS90wJIrLqK2M4yZTaEGy0N4ml9M96W89Hqs0lVu0nt2Ii+YztPv8XF8ZZ3EPrkAfj9dyF50gaJhscwEP5U0twGrZlKkEhKwDNkZ7gV27yC7ndUxYtfwkymMZMp5L7KF0pJNj2OmYiR0MMkRWsIoyY8MPsYia/fyZmxGzjdsInAjjKM6nIS1aUKJOH6UgK7LAo2FBPc5WKh9kJiYoJWF7I08G5SP7sfMrryLuZsYCjZJYlFp39EWKhIn4TBVy8gXvyN/2e/fd0DREoY4sqvsEo8lHQSCSV8Z5c8RDJJxAeRUKvmm4FEGDQ/S1+6k2NdG4g1ZWPWFJLZWUZi5wbiOypJXF9GfIcbrT6HYNNaPC0X4G2+AF0BxEVqZ7k6NvRuN96dGzjR+VZOva+LyMNfgOizYrwQJkIkY1qmhcMcSZGccTJmCF0XJ/UVAESuuRytOssY8rWjSGVf12MYsbDKyYh0z4SXyIQWIB60hIU2D7/6FjN37uVo56XMNpQSqXdj1LpIVBdj1JSi1WwgUrtBaQ4xscTc8u7O40z9hYTa3UR2uvD2vpPIA/dBJooXmLOfQwkIx7SS13X6RwIY/wDI2Y77n94TDWKVMCQtP0Q6QRpfJJRsJXyfgWhaoCFaJk5SACKM4ZnlxIemOd2+mWhTnvJB4nUlmDsqMK8vVwDRdxYr0yLSkEekIYfwrhyCjXkqmajVFlvMc0M++k43vh2lnKzfxqmpRrRvfRwWHlPVW7G0D40YyaSBGRVJLV66xSWmZPIV96yyZRQSnIy9JRDkK7m6NIES1CIYMgkykv0W3yvug+giaB7LnDrxK1LfvYeT040cqdvEUm0JdFRhtpbhr84mXF9MuL4crWYjevVG9JoKYhIKbypgsTmH0w3rCLcWkbjBTbD9SrxfuxvSfnyYLDmvpQIXKzSpoFceVJlX/9AgTjP9j2/FsYyRVKQcdWlr4QrHIzQhYUIsbSq7Py2Z8/CC0h4cO8rRw3uZb9mKvstFZJdoixISO8tJ3lCuTKxItUjSYiVNtTqXAotyVBtd6ju91gWNLpI7skheV4BevYHFhks4PnA9S/feQup3D4B+0o7WxIjrYUxdEogWs4j584o+DkCk3kku9YJIlTjikZROUsIGKfEvvJDyg+EB3wkSj3yD2dt7OTnwdk7UbySwq4pE0wYiNYUEavOJNJfiF5OqoVw55HpNOUICEKVBmgo4U7+OsBR2Xu8itvsyFu65GVIegsRUpkN1hiRNRVvY7+3UellZ9FfYBq+oAf/8ya9rE0sAItlZAclLAUTLpIkmJfQoUZoASNLrsV/x9Gg3vqaLSNcWkagtQq8rUY6nxPT9tWXKUQ/WVygJKlJUnFIHMFKSEqvPg+4K0rU5pG7IgdpSkjdUMn/NBmbarmLu1n7MR/4NPE8qkMTQCKSlhtcSnlIoqyTpn++nFz9CACKaUsiWyqI9RD5ICkLyDhF0YmYYQ1+CmJhVi7BwlNPf+zK/PtBGtPsSwlefy+w7z1P+RazrYhYbN3K6upTFunIFDvE35H0jDQVKMKg2qCtV2mWxJksFOHivi2TdxczdNQqJWaKZABKtIxO2KhZsh1we09JuVtWxFaJ/8dd7LXz7ugaINLb4FpZ/YYd5RZ07XJK0SoESaZOY5icj9dcSvZLy7Ie/y+mBBsINW0nXlJKsKVEAEfva11CCTyI0dWUogNRV2FEbkZ6lSoKKjR6pd5FoLMLcVUSqzkXyhgL09+ShS/a9fjvB7qs5PlJP8vufhugzKjEmxp4wsDyiVIorS8PGibP/oowhP4oIdrbOvi2V5VfHtLJyDhLhk5yPbmmN2Ax4j5L61bc58pGDPDTcyFNd78SoLoTq9dBUjL67grn6ck5Ul3GmpgJPQxXB+nLCDW4VwXLMSzG7YrVWW/h2ZqHX5cF1hcTrt+G5bS/EThNP+YjKmwowklEwJWJllZo4Cl4EnHqdF33h18aXr2uAqCa0TQtpaKvCVuobjGVTS3zAuCHJvCCYAZICEM2DcecowV0X2aZDKbo4ohLOFC2xTGJarKA66xjruGIideUqbyI5AUvTyPluxBwzatzqev66TXj73g2fvRWOPQpxj2KaU1qIZ2NhO5ttMbcw+LJ5btsjmYyE44QEHBKIcLZytDU2Q5KOkmqRrELELsBPZOKQDkPKC8YMnPkl+r/fydHhnfy+YRvzjdtJtl+GUVNMosaFVudW7y2ACDRUqPdR4Kh3tKZoEREK8t5WG4mppTfkE63OVu8c7ryMk/vq4fhvVeInYJorhJVIAyvULhUN8p6veXQAr2+ACCrEvLATcAlV8xNUA4WUHo+DRDWTCRnLEADTgxxDeAbz5naSNWXLwBCmf7kkibJw7VYCddvwN2zE21iKv9GlnHkV7arJg8ZKaLmUeP8NxO+cgF9+T4VUpZJ1MR1TCbuzDvXZ6FPaCYvKOzpaQrbCWYoEKOJbpfASZyEVYTERJGRKUFukdRik1mzpaXjk6yzePcLxve9ltmkbkboK0tUlZKrd6LVnGd5h/L90K8IgUZdPpCbb8km6L2W2fycc+ZXKhQTkOaV/RGWIv5XRVd9IxbAChy3cXhu64sWf4u8OIHGkFF23OiYOetQkrQoHxbySMYE6zD5FdLzOju8XK5NJpOHLJqVdJPy5Udnq3sZiPLsL8O7OIdyYrULEyVo3qcbNeOsv4Wjj2zl2yyCZn/4nhE6qkXppCSRImZZpkRPkUmkLqWdaaTeJ8xJNk4mYZMIp0mHNMhkTS6rM3Kpt8oG5CN4j8Mwj+L54JzOHezjW/HbmqrcSq5YQtovUNdkY165Hr7W1ggpGSEDiLycBiFGbpwAigsHTtZ2Z/hvg1z9WWjKsRk39AyAvDr2/xrciXYWBVmiQuCqjtgFiQDRkmSLL5obk1Z98mKW+d2PsLEHCtS8bGDaYRONIIk2rLVcOqwzTXWjJY6ElB//ubKVJQjuyiVaLlN7CfMOlHG27iuMHOkh842Nw9BcQ84IeAc2maBhiMuYiCJEgEm3j2afh6FNw5En4/eOkn3iUzOO/hsd+Bk88BI//CJ78L3juF3Div+G3P8T4z3vwfewQj7VdzTONV6roWrLxIlXGn7khH65bR2ZHNhKJezmgWHmsACReY2kQ365Cljq3MrPnGvjJf6j8SlTU4PM0iDUGRHyjf2iQvyZARHur6Ig4wFGVEFQdk4BYWPS8HCCOokhXP+Eff4XZjiuIVxe9IoCIeZLaKTa85bB7mwqYb81jti1HgUQ0iUR+gtflEb2uGKPhIoJNlzHbdDmefTtI3L4HfnUf/Pwe+OHd8B+3wudGMT7cQ/C23XhursV7Yw3ew9V4DlzP4tS1LIy/h7nRq5nd/w7m9l1FaLgeT88OllquI9xRjdm/G/qbibVdz2LNFczVXsJ8/RYWaivw1rgxGlywuwh25UN1tkoGrmT6l7MvANGr84hU5+JpzGexfSMz3e+Cb34GdC9xGaIrALESMsrekuG/UtHwD4D8DQAiDS9DPsVZd0I6CTFLRJJJNEUAEjnJwlc+yJmWi/4HAOLG3OkiVS0h3wKVPJtvKWCmLQ/Zirnlr8kjurOA5A1ukteXkthZgV5bRbhhM77GSuYb3cwJsHa7WGh2sdTsxtPqwt/qVhRocRNsLiDYlE+gMQ9/Qw6++vV469bhq87FaN5GtHoLwasriF1VBddeDDVXQt1boe5StOrNxHZVqfox784cwrXryezOh0YpmblQDTF+OaBYeawARNuZvwyQhfYK5trfCl+4EyLzmKrU3/ZDRE5lZEShjLBcAZC/Bp+8gnu8/n0Q24GV9heAWMM4ZRyG3TGSaLYdRFI+mP8tpz48ohKEEmmSTrZCti9/K5EfAUequkAlEcUOX2h2M9viZr65GE9TMUvX55KQ7HRtKZnrCkm8NwdzRyHpWpcybxJdm9G6thDr3EqkfSPR1irCzZWEdlcQ3F2Kt86Ft64An02B2gKVxJNEnqIGF776QjUSMlBfonI2oZoygjfIwK9CNfhL8jvplgqSzUWEG7Lw1a5hqfZNeOrWqPCtFcaVUO7LI2m72I48wjtzWGrMYb6tlPnWizE/cRiC4mNJlMQ2g6WfVFhXQs82QETtv8Y/r2+ASOPakRALICKh7LCW9YX6XUq9JcRI0gfHH+H0+9rxNm9RodhXChAJkUrNkoAssEtAUcrC7nI8jRX4d1UQra9QtUzmDS7YUQA78mBnNunq9aTq85h/73pmr8ln/rpCFm9w4a0uIVgrSbhyIg1lBGqKCFbLAC6poC2y/SUr6y8l+r7GXPxt+QQ6ixR5W4tZairEU5uPrzqPeEOxer5kvYtUc5Eqq5mvXcOJujczs+tCAo0FLxsYDpCk7aLXWwBZbMpisa2IxeatpP51BHzPWZM7SD8ICRgUIOz+Wf77tY2Q1z9A7Ia2+kEST45TbneMjHKNZ0gbGsTm4dff4Ll9V+HdVUFkR54aKBWuc7EakkFWMaGaIsK1JWpUnb+uEl99FYHaKjWuRKJGcSlf2VGiRt4ZNdnEa9cRq19DtH6dun+0RiqHy4jWlqhtrKYEi4rUtbWaIixyEa92Ea8pVNtoXT6epizmWtcx15JlUy4Lu3PxNeYTqi8kVluIVmNRTLROg5yTy1xLLvPNuYhzHWhwrYqkzVKitXbmEel2M9ucQ6BlI6cHr4VnfmbNpyUdY/uIFhRWRFVe29hQT/d3ARDBiAMQ9VYKNHZ9kgKIOIoJ0Bbgh59kpu9ygo1lRHfmvyKAWKCywBGqKyNUW6lAEarZpPyC2M5NaIoq0apLFLOG6yVnsA7f7jX4G9cpYMZqyrBIgCH7Jep4BYrqEhscAhKXTWcB4m/MwrN7Hb6mdch+qEEKDHMRMGi1+QpMAhABijyvgMG3y4WnsVCRf5XgkOvI9TKNlerawW4XpxsvVLVbZ/a8Ax7/nnLUpWOk9spRIhZabCH2D4C8+i3gaGoLILYaV2aX3QkSaZTaCylBic3BFw7i6d5MrEkYNl+Vi0id0epIRtcVWyPspCSjbgOxmo3Eajaj79yKXr3ZcpKlTFyNpXCrEvHFlmzm29YiWzlfEncWSb2X7MvWrv1a3p7NaIs5p0LT9S60+jwStdnKbEPqwa4VyoNrC1QBYXqHW5mSco5VmWuFtSUCJyFu+V7GdayG5Fx2b1ZmnL87n5O7zlNaa777Cvjp1yC2ZJm4diBL+mi5ImA5+/nq88grucPrXoM42kPgIPtn292ydSURJ9l09aPvGJHbWwm3lxFvLlYRHLHjpZJ3NRRqLCLYWKK0kfgL4m9odVUqShWv2YReu4loXZUayhtoKsHb7GapJZ+FtlwW2rNYaslV58t50Xo53yJ1rYYSIg0lRO1tZFcRFp191uguqX/KJ1mXT6Y6H3bkg+Q4ri+EGwphhxuzxi7ErC9S1crisCdqyzCry1TwQMbdhxrdqyI5l8aNGLtK8HbmcqrxXPRdBYR6r4AHP2dVDcuQAztXKH1k9Y/s2QLslXDvX+Hcvz+ALKsSVd+gZsuURLoCyPHH8Ey8B6PFhdkiYz0KiO0qItq4Ogo3FRFqKlYUbSwmtqsUvaGUeH05upSIN5QTbiwluLsYX0sRvhYXntYCfK15ioLNecQaXarcXkruHbK+KyDWWIDeKMesoKZcYjbJOJbw7gKCzS517aVWF/PtFkmoWL6X90vWF6mK5UxNMUIpSXDWW88qzx3aXbQqiu0qJlVTqTSIpyub2eY3k2krIrnvbfDtj1rjTaQWzh4DvwwQmfFFjc957YPkdQ0QR3sIJqSplQax2l6VlMiUm6rOT6KKaQj88gGWBq+E1nwyLUVEanPQmtzEmopXRZHdxUR2uxXJdYTijdY21uQm3Owm0FqIt80if2uh+jvcXIjWlE+8KR+tSfbPUmx3IbHd+RYJgGyKNOcRacl5PjXnWfdoKWapvZjZzmJOdbs52eNmpsvNggyFbZH3c5PY5casd5NqKCbRUEx8V4kyM+Udws2rIzFT9etLlgGy0HYedBeT2Xcl+hduBn1WFVeenWLIcRb/AZC/gvKzAOGAYxkgdhRRaq5UqbeNIhFaz/3nF/ANXKoAQoubUHWWYh6HyVezFYYWZtd259lkMXGoNQd/Ww6ejhyWOmWbR6A1TzF+QrLYdYVkJMrU5CYkz/I8soAk4LIoX4Vy/W15rKRQSz7xxmJl4lgMbwFWQCFg9LQXstRhkewLUOU3Aa7zrrK/WlJ+3LVFGA1leLuzWGw/HzpdJHsu4rRUCcwfeXGAqBGVMsJTek0lSP4q/LKam7yGNYg03AtImH0l2X9KM4udq5xASzjZVq8M2LF/MBIcue9u/AOXQ0chtOYS3HkuWnMBEdEmq6Boi4toSwFaS766jlxL9iOt+QTb8vF15CKmh5C3M5tgezZ6cy5mYz7UCxWo84JtBTyfXATank++dhe+9gLObgsIt7owmmQ8SolNRSTFZNttPVegvQBvRwGLXfksdMlWzrfuFWktUM8uzy/7kRbXi9AL26WESMsKai7FU+0i1FaqAOJrPRfackk2l3F85Fr43Q9UTZb0i5hZ0keqS6WPVg7DVUEV6UyJBzsduAI49kzyZ7veCuf/NQD2NweIemm7ASwbyW5FaShFYh8JOWMhbFTY2DH0FKFYnEBaJmawf9OTEI1DPIVKEkpnhDw8dfdBwmPXIqFW/7X/C63h/6J3FBDrKH4F5LbPLUVrq0Br20CsfQORjgrCnaUEu9wEevII9uQQ6c5C78wi1ZYDLXkgJlPTeQR3WxRqXkOweR3B3VmEmnMJiXllP1u0qwShSFcZEdnvLkXvKiXVWUK6vRizrYhUq4u4Ddjobjk/l+DuHIIt2YRa8wi35RNtK0BvdxHvcBPvLCTTX0Zqj7UfFaEhxyvKJbS7AL2t1KZy9LYK9NYNyxTs3MCZvnJO9RcR6F6P2boGGtbArlx8HZt5Yu+74blHIHpazSujy8yWUuErGJCpkJYk9C6DWVIQS9jDcmWAlcxbJgdYCRQVJl4xQbhUTJiq5k7mPZaLvXqfvz1AnBj5WfFgN4wARIAhWmAFQBylImLJljwpE8JpmXTZBoiIKl2mNMkQlepYmazg+GMcOdSJv/cdBGtz0Rr/mVjLG9A684h0Fq+Kwp3FBLtKCXQJEEoJd5YT6Sgn1lFqkwBPAOQm1ulC63Ap5jTaC0i0uZBttD2HyDIJE+cqRhZmDreKlrA0RailUDndgd2FquZLEnzeXXnonUXqurF2l2J+0QYWMCxm1zrc6nfZxtoLcY6LthUSEQ3TkoO3JQtfS5YCUrglj1hrAUabm1R7MYlWtyKjrRi9vRit3Xq3SEcp/p5iTvWXcKbfRbgzF7NlPTQK5aK1lnFqz0Wc/FAXxq+/BimZ4ySKaWhktKQFDBlyvDLEJdEUGXkY91ujEJVQtPIoAgM51NIvUq4SVmR98/cMEOHpleCQ/WU9LA6FTUqb2ClZOcYGhxxtJFLEjJTS2nYLKmUkQzp1meTTnIOf/RvHB65Fb96OUZ2P2VeAv20Nka4CIp3uVZGAwtu9AU9PBd49bvx7cgj3XECs+3z0rgswOrIsBmupING8WRUW6i1b0No2Kk0T7thAcM8lBHovw997Ef6erfh6qvB1leHvKsLfUUi8v1xRYk8ZiT0VJLorMbo2kOisIt6xAb13I9G+DUR6qwjvqSDUU0mop5xgdwXB7jKWWouQ6Ja3vQRfRzGBrnL1e3jPBoL9Vcz3livy9pap4/WOEhKtxdaUq40F0JxHujWHVJul/cI96/H3rmexfy3evvWEOwrR2oqItZURtSncXkKoo4iFnjKe6d3MiffVE/7OR+HMb0Am7ktrpE2ZsClD1ATNnsPMshIMezoima9LhuxafS7yUMAhW+vj8IYwwtH2mK0AACAASURBVKv3+ZtrkBf6FC8KDtU0KxpiBaDiCQMhmR9agUa2KUvaxJUenwf9d6S+cjNL3ZdD6zaodcPQRubb1qsSiWhXEashMXVC3WUEe0oI7ikk2JtFqG8N0T3nE+9eQ7IzC7O1ALO5HHP3ZhK7t6G1bCfcth1/5za8ndsI9V9OsO8tCij+nm0Eujfh79qAv70Uf0cx3uZ8fM35BHbnK5NHImDK92kW/8ClGFGAtJIsX8XyN8I9xaykUHcRDgX2lLDQVcRiVyn+7lJlthldZUpzpFvdpFsKSLflYrZnk+jMQutZR6j3Qnz9F7K0d41633SzG5rE9NpIoHMjiz0bWNhTgWdPsSU0ess51V7BM3vfhudTY/D7H0JK1qAKq8k2ZhI6c8kUkUzGsrClRF40iZhYQmI9KCjZUUpHOFqqxP7y7xkg8m4OwysOFyDI2zsSwop2yOwXzmErtzK6Wf5W/5j2HAEx0FOaWhIMjsLv72Pp5huItGyAzougqRRz31Zm2wsJdYttvzqA6J2FinnS7VkkOnPRugqXr6V1WXZ9ol2kbw6pVrH93Yjd7unaxkzPW5jv2U5kTxnx7gLiXUWWuSQmTGs5sdZKoi2WTyO+jfgClrlUgN6Vi96VTbxrHVrHhWida5ZJNNdKCrW8iXDrm4m0nUus43x1XLz7QoyetaR6sqC3CPaUwZ5i6Cki2eNSzxPtzifcnUeoJ5/Qntw/okhPrvJj2LUBdm0m0bJBaadZ8UkGyjk9UM7inlLlR9FZgtnmxtNejveDTfDYVyEzq2Zc8WCySEZNESTTM1n9qEqwQeYSUHPAyJgFMaDtyQGFPeRPoRVy89WAyd9egyyDwgGGAwirLFqcMGuCaqfe6vlbOdoBiClDVMW3k/GrMsWPcZzQo5/lzGc6ebarglBjIXRuhLYK4n2bWOouI9xTSqy7eFUU73JBe7aiTHuBkrzJ9kqMjg3EOyuJdxUrHyfWlaUcdHHU/T1uPD3lLPRsxttdgdaejdl+gTJhku35JDrcGJ2l6nytu4pY9xYi3VsI7dlCsG8zgf6N+Pduwje4Ed9QFWe6rNzH6Z4SzuwpZqa3jJneEoRRZ/tKWdi7gYW9FcwPVDLXX6a+l9/P7CllsdtNqrecdFcRiY5Com15hNoLCHQVEuotItxfQrC3yNrfU0S0pwi9u0iBOdlZRLqtlExzJWZLFVpHJYEeuUclswMVLPaVEepxk27NgqYLQbY9JSwObufY+xsJPHQvxI+rhT/DagWqJFEzoeYPVh0qnSrLRygUSKeqjrU6X76WiMzfP0DssJ74Fyu0howXsIBhgUN8CecIZyu2qFAsmSSeThNPmWoOWjVBmRGGM0/AL77KsX9t46n9F3O6w0203QWdpdBdTqijhEhvJdGeYtXx0vkvl2KKWYpJdhSTaSuGllKbykm3laN3lePtKWa+z83sgIv5/jy8vVmEe9aS6DxfASO9ex1mSzbptnzMrnxSfS4Sg0XEhyuIjFUxt7eS0/u3cmb87cwcvJ75W1tZ+mA/3rtGmf/INOZ370V/4F7iP7gP44efJ/ngl0j9+IuY//UV0j/5Mvz062qrP/B5fP/xUc588Q6euecmnvzIAf5wRz8nJt/J3P4tnOyt4GRnKTMdxfh6KtH3biWz/2IFVKOjklS79U7yXplWi8SJj3bnEugtZKm3ksU9W/D2bCXSWYnZng9ta6BnHVrdPyEROnPsYkKjb+NY18WEpnfCN2+HM/9F2jyhpmoVq0F8SS1h8b70tQjHsyCRCejsUYoCDvHa/741iAMQx5yytgIQmQjO+k/A8XyAOOCQBtRUOtCad1eNGpRZA71HSXzn4xw9UM+xfVfyXFsZsaHNJPZWqmiS0Vem6qBifWWEbcn4csEhx4v2CfVsINwtGqOcVHupKrVQ5RYSnu0uxttTynxfKbP9xcz3F+DvzVJOvNnxz5jt5xHtKFQOdaC3iuC+LQRGLsY/fQWLN76D2Vuvgf84AN+9HX5yLzz2HXjuUVg6DiEZHSnj1kPWeHZdVqKVCNCfIRn7LueF/OA/BY/+O/z4bmJfmWLu7g5OHtzByeGrmN/7Nvx9VxDu3I7esZVU20YyrZXQWm4JgdZiUh0u5YcsDmSz2F+EV4IEXRXEO0rItOVC6zqMhjcqX0zrkQBBKaHujST7Loaei1jq3U7gK1Okn/0OJGfUNEWJpEnAgGDaWqBKcGCFciWaac/Q6Mx9JoygzIdXw7iyrvk3NrEEIHYo9wU+h0gOAUYsqas1ti2QpNXU/VpcxzBkjiWZORD8yTAZAUZiFk79HP2rt3D64E4W979DRYciPZuI9FQR2VNBuLeEUL+bUH8h4b5CIr1uIr3Fq6JwbxmhgYsI7NtOaGgL4X0VBAeK8PVk42lfy1LzGrQ9Vpg30laI1llEvLcUY28xWl8eS31uToxdzLGb3sviv7ahf3EafvBJ+M234blfw+yzEPFDLAq6zPUlQ4nFiXVyRLIvs+OtklKylqBMYC1zZy2A/1l4+mFS3/8c/k8eYPHWDuZGriW4753oA5eS7tsCPRXQ6YaOPOjMJT5USnS/1F/lYu5dT7L3QrSutfhac5nfXajMQ61rE2ZHBbQXQ1shtBdidhYjkbRj+7ZjfGUcnvsRhE+QNmJqfi9ZWkfm+1KznCnr24CUzOIijrvARozrV//zGgGIo0EsA8oBh4BCZpaV5Q3ipoFuRLEmfLYYJGnGmUv41YqzSgL9/rtEPjPK7ORVeIYuITl2GWLHG50Wad0bCPWV4B9w49+bq8gCyWoBUkJo72Z8e7fgFZ9gpJLAeAWBURf+gWx8XRdi9rthsBIGt2Ds3YZv8BIWxt6B933VLH1sD8YPP0ryv78Gxx4C/x9AZlrXRDNEIBg5G/wXv1XW+FieVtQywxWLCAOthjIQ0ZJoyYwValeTLAgYF8H3DMz9Gn79NTJfO8zcjdfybO9G5nsr0PZvwhypwtxXQbK3HGOPi8SeCzH6ziW+91wi+9bhHShmsbeKQM+laB1vISPRw5YKCyAdORh7soj05ZIa2Yxn5C2EPjEIR36gZoGUyR7mE7AohpcpARd5P5lXQISpRjIZQktbK7682lOXvgYAskIa2supiea0oCLbNEY6QVQLocl0OCr0JwkliWzEVJ4jkzoGj99P7GNDLAxchlcy2AMlxPaVou8pJdlVCe0bSXdUofWWEtjrYnF/LovD2QT3uoj2Fa2aRFJG9pSgDVcR2l+JZ28xnoECtJEiOLABvS9XZdElJzAz9nY8HxtSfgKnnrKWbwuKiSTTg9raQGL/GV2tgmUtj+CYmxZWBCDin0oCWvalrVb7EQmsEttSki5zc6mtRAXl6iLDpdjwGOiPw6lvk3j4Q8x+dg9P3nw1j49cwrHeKlLid7WXkt5bTniomDP7cjk5uJ6FoXxi+ysxujeT7LiEZNtbSXRcjtazmUi/i+DQm4kOvgm616vk5cz+K1n8zCippx8EM6T632OkCMQzhGPidwhARAoY6EkfYdOrVl5XczKvtgH+gvP+tgBRkQp7PT+pwzkbrX0+QJKamhldqVgjjBlcsObXTcv6GsfxPPYFTt3ejm/gbZh9WzD7iwkN5OIbyEbrc5HsLoH2ckWJnlIFioXhXIReKUCMgVJCnYUsteYQ6HRhDFVhjm9BG97AQn8R0ZveQuTO64l/aQR+/jmYewIkiGAzpRIEUhKehFjcJBo3iCY04qZGAs2eBURmApGAhQWI/8mtU8Yhgb9oKkM4lSSc0YgisSUfCRaAU8AxQDTcb0g8803+8O338+Rd7cr8MnsvJdS3nfl+GW5bxtxgEYGhIuJD5eji8HdvJdJzGYHeS/AObMSzz4V3+M1E972BVOMboK8cfeRijo69g2c/PUbm2YfU9EwChlQiSTQSJ67ZdXWyTHVGpuQOqxls/r5LTQQgCiRnnS0l1VZoEGEGNQuGWndcJK3M0O6B6DzEjhH41Sc59slWZgcuJdWzFfZUoHVmsbh3HeEDLqKDOaR686FD7GY3qT3FRAfceIfcLO13E9orf6+OIgOl+PaUEeqtwOgpJdNdCj3lsHczxtTb8PzLTvj5p+H4g5A4LXljtU6JP5ViMawzGwgRNDQFCN1MIsuzyfuKNWGaGSsq5xTwKfPCWbZM5hqWBXGseiWnGVe3XVn45wRJ4qRFi2WiJNJBYkkfkZRHMWWcKBphvJlFwv6nmP/mR/D+6xBnRq9lrutSol2byfRvxezfRKyvAt9gBYv7y5gbKWVuxM3ScD6+/XmE9uUR788j05YNXW6SQ5vxT17Oczdew4l79pF54n5IzEBKSoV04ppOMmXlwtIk1eJ7ii9e5TDW316DOAARBWIXLQqTiGRVklJpFjHD7BIEWedCZicJncH87bd47Jb3MDu+lVTfRugsJ9GWh6f9As4MrcN/MJ/ovrWk+9ZCVxZ05ZDszVcACQ6KJikj8goBstTlVgDR+qvQ+jajD10Od7TC9z8Kz8oquIvq2WViackfz6QzLKUFKhLUzBCKB4kmIyQyoiXOJkOV7y02j+NbSORGrbEh64s4AJGrnHVWpSkdLfyXbOXiGbWIj5irTjLOWqJN1i6MabJMnMwSLzPoy8TYsGgmmU0nmFeGWIq0/wQceRi+fQ/6HYOE915NqGWLKtgUcza4rxDvcBaLYxewNHoBvuF1BPflERkoUwCS+jTJvxgD5SQnt7M0spWjo5exdO8gPHW/NfF2Okg6k0A3TeIpazHSjCwrZ8gqodY7v1r//u0B4jDACwCiwCHS1JnNXCIYRggML/hP4v31jzh272HmhreSEQ3R6YIOF+E9LuYHCzgxms2Z4QuI71sD/edC77nQvwZtMJfwYAnC0JIs1KSj9hatirS9LpjcgD5UxPzQJvx3NsGDn4b5p8CIKZQLvrUURAzQhcdVT6ZVLZKmiZ0vDJ5W852bmRSptEhHK/n5ohpBhIhNZ5ljZSO+jH2ZyC0WISMr28rAfclkv4gfGE0k8IdlASA7ky2HxSGyFLAEl0j5yAI8+RDpL91B+OYmYvsvJj3ottp+4J/IDP4TqcE3EB9cp9o6vHeTigDOdJYQGChH31tKRLL2XbkEhysJvO89nP54Jzz9HYgdVwBWII2nSciO4DlqC5BXCx0yu7u8qwVCJyehQgbqO8dRtjpVDnT8BZHo9okrStXVdV7498t+eOlgub5M/iYmlTT+HERmQJ8Bz+8JPvh5fvPhcZ44cAPcciUMCkByoN+NNlLG3LCL40NZzA+vUwDJDJyLUHLvGqL7cgnvKyLeV0Wytwqjv4j4gMvqtMESooNFimKDLrS9BcQHLBIQRQdLCA+WEdpnkX9ISr3LiN1VAz+5C+Z+CvE5VWQnTq/Id6nkliWRRQEobSDOpvRwRhxhXUlwicwlUjpGUkNPxRFzSyI5MuRLcmEOOf3hbJf7ZYXHptruL/1bhI+Ej6XUPGaQihsqfK4nU8iiQ/KEihclepZIk1RIF7SnIJqBeFqZPoYCV8oSCoFZePS7ZD49RnjyCuJ788kMnAf9b1JgSQ2st9p7oJLA3q3M79uOZ/92fH3l+NrWo7WdR2ZvLsbERmYPvgX/v43CyR9BJqiESzSWsCbhcBpFAdriWcWTTjvL1uFRtSti56yGtnj+zzPnOdIIEuZLRHzWRMpGkIweJRQHX8Jad0KTq0lvSLw9IYVkMjm0tVCNDGlVK4DZW8GQREaU8ycxBzt8n5Sl+WxGERvbuaSEcWUFc7VMmJQTqHU8vJCYA/0EBJ6EmZ/CE1+HH3yI1OeG8XygnpMT7+TkwEai+0tIDuaTHCwkPlRIdL+L0IiL4GghoZF8tOFc4vuzFen7c4kOW8doQyUqY53oySLZl4e+v5zo+EZi4xuIjZYQGxJgZMFQLum9uUT6i1jqK2F+oJyF4U0EDmxn7rZrmPv6nYR++6AFYDH/TA0jFkXTk6TsUv5lIbTcYbYQULkfQ6U6rVUUrVYQplT9smIrESvhCetazvmy1LSMo7BzI85WKjdtyiSd1W1F4NjHiaZQJHMi2ReWrf2gspF7Oc8hW/lbfSQULLNgJERD6giYxPSSY6TfVWjNG4Hjz8ETD+O9o5fZ4Svw7CmFsUoV2ZP2jPesx9hfgXffpfgmrsI79lY8feWkutfAwAUwlEVsbw6nRyvQ75+CpafsnE8aM2pYkb+krpZ6ULP5y4vI/QUrK7MG0lRKP69MPC+/qv1Sf3pzjrycNL6KMZuy4IosmSXrOFg2pyzMIq6gxdEyCCmo1vjLxCIktJgFBFuxpFMmYhsSF3tCA01UtzSmbkkXZxZzZ/bymAf96E+JHvkRoce/jf8XX2PpwXtY+vYdeP79MIEvj3Lqrnrmb78e7/veReCmywkf2kZ0spLoWCmx0SKL4YXpV0H6UCHJvhxM0RLDZUTHNxCcqCI4WkpoqIDI3vUw7ibRn6Wknj6xhfmRbfxh/3ZCH2uFR7+szD1JWjqfRCJBLBZD0zQljZ3vX3wrvWnZ/zJ+XiJVKxnTAYnDoMK4Vu/rloMumeWUQSadIiMqSqSVSB9RVbL5c1slzUTQ2bafLXUdPpNnEZKntLFjD2Kzw+xqQRxL0zjaRiaxFPmZ8SVhdhGO/Abzm59k7uYmTvZvwz9YRmaiBEbzVHLRN1BFYPhyAiOXEhnaBMMlMFkEY9kk+y9Q/ey9/Rq0733YWutEVqtKGKTj0ioy1WzMjmbZAHEALw8u+zZABB4yq7z4U897nxfvmOVvzxEAyMupj7Lzg6QTIaJxHa9usBCPs2RohBMBjKQPM+0V11I9WIogaWbI8BzwDKSPgnEEor+DwOPgeRROPgJP/wh+9Z8gSwR/+cNkPn4Lidsnid/aS+TA9cSm30ls+h1Ep68gOnUZkaltxKY2E5ssJzRWQHgsh/D4WiJj5xMZfxORsf9DZOz/IzL6RqIj2asChwBK2+9SmeDEUBnJkSLi48X4xzewOFbJ4nAxS4NuVQ+VGK2AkQLM0VICt1xF9L4x+O13rYnolJMr89IliMfjpFIpMlK6ncmofadpX3wrjCzhSyHLbBXmdCT4SuZUHa0Uhy3BJR8kmfCMwMoKdr7YViw6iY4JU8jvcm2HrCSb46BLyMAyQZbVuxxonWidZONOvhKRICR5KusJFCdawJRdeXjh4XgKluYxHrqfUx8Z4pnxK5kbLCYxlAWj64n2riXen0+mJ59kr5vwyDYiBy4iPOrC07de8cLMyEV4b3sP/PgOCB612wuloSWJLIsiSTDheRpkBQqsuj4Bk5AVKZRXUzLkxTtm+dtzfAYE4qBpcUjIEgGiQXyoiZ5lXTtZjEXq95NnVHUskT9A6Aj4nwLvf5M59XUyz34W44kPE3zkfSx8e5JTX+jj+CdaOHlXPSduuZaZm65h6dA1BKbeTXT83ehjV5EYfhfsv4K0lB60rrOofS10rCXTfSFmz/kkxLEeW09mYh2pqTUkp8/DOPBm9ANvInbwjcQOnE90NIfYiGt1NOzGGKtSlBgrQRsrwj9RwcJ4BXOj5cwNl+Ef30RkfBOJySrSH7gavvMvajkzlctIWhJbgBGJRBRAlltWBJiYpC/1UWgQ6b1CggtzvZBWMqpjPigT12JKh4dfbCsOdixpoKVSyq8xMk4pqMXcsqSoQUwZuSJd5Vbq/nIxYXKH5L5iItt8L5aHkPxsiWo7BJ0W/8qW5vJ4coK0kyyc+uzPCX39Vv5w8F0cE59utABz34UwKIGUtUqTL+zfyqmxS5gbrWRufwmBqYsIT28jNl1B5K6rMR7+FETFz4OIWPzqGawckWJ4555yXxsBFkAERJJ0PeuHOL+/VBedE08lEScrbUSs9fOiJyzJ/8y34NHPwoN3wPdvg/tvIfXlQ0TvGWPpQwPMvL+ThVvqWRi9FN/wJvwjm/GNbVQMFZjYiH9qE/6pjYQObyZwuArfwUoWD5QyN1nEmYkCTo/msTCUA6NlsK8Y9hXBYBH0F5Lqz1cx8uhArpLy0RE3oVE3ofEiAlPF+KdL8B8sJ3SgVEmaVwKQ1HgF8fEqgpOb8E5swDfhxjPhZmZqA3OTGwlOVOKd3Er0I+3w8/vAd8Raa1ySe7bzqurCEgkr4ma3tmiUaFTc9D/zkU50ACGdqrhcfAMxfSSDbPsJDvfLMSIsbV9PggGJjJVDEfloaRFHq5hKeyjZmZHsQep5f8tKHWFSyh6I2KFcuc3zJPELASIxhhf4RkozpXTSMlow4YOMU0Wlq+XvTPFX0mIO+sHzFNGHP8cfPt7PsQNXkh7Khv1vhulcMjeWEzq4lYWJS5mfuBzPgSuUsIrfUoV5sBD/SCGhuxvgN99S682L5SPPIs8szaIwYfu/0qwWCXjEz3PIEir2j3+mc+Ac9VKiNdIRCBwn9N9f59i9+znz/muIve8KEoc2Yx7YTHzqEiITbyE49jb8I1cSGroMfe8WGK6CoVIYKoEhqTsqJL0vj8S+XLShLEJDa/HvX4t/bC2+qfV4D67Hd2M2gZtzid5UQGK8EEaKyIyWYI6VKDMmNVZOcqxSRTK00SoiYxsJj2wiNLoF/8hWvCNb8I5sVcCMjJagjbpXTfGxMiLj5XgnqlicLMc/6cY37cJ7eAPew1uZP7Ad874BePJ7EJoDQypKlz0Ba3KOdFqZVIq3bPPKMbNeqgfOduJyb2LNdCdOthTnOSTOtQUMcYSFKcR6ERNHysPjCYmAxe0QsZSKOBGbF9864WQtIwCxAjGOLyq3UcyzUhLb9xZQOiFm59klEKFAmohjGCFMQxYp8trl60FSpoDFHs8hyU0zCAkv0T/8kvl/uw3/eBXpobXo0wXoN1eg37gR7/gmTo9eyszEJSyNFhCbyiE5uZ7wcA7+qYuJfX4M89nHl4fjOs8ijynkyBILOKI1rECI1WK2KeYIJTn5JT7npPynSIdnIBmA8Ck8D3+e37x/J8+OFmMeLoDRN8LIG0mOZhMdLyI0uYHQpER7yjAmpPAvm8DeLCKDOWj78zFGXSQnXKQni8hMuUmM5dqUTWIsG2M0i8ToOoyRtcRG1xM56CZ4qJjAwRKC08X4J4vwjxcTGCkjMFKhIkcS3ZDx0+GBzeiD2zGGLiO1/0qSIxersG5srJDVUGSsSDnkgZES/KMFeMfy8EwXEjjsJnmzm+htF6F9dRKe+xnEJaMLft3qbmlXMyVh2hSmaSpSOZuXaOwX/mR1rGPDixx27CdhfWdfutkyfWTPAYcDEHVN5b+IDyN5ColWSeTKIJOMk9AiJPUoqXjMmjBBQrLyezqpQC3Xs3wJxyKRu8i9rXs6v8tWgUcBR7SaDV47IJYwIW5CTGaXkSy8MsAkT7IEyNqQHtLxBTJSjStMLNp39jm0f59Ev+sqZqc3sTRRijblUn6nRK/OjJah7V9LYug8jLE8olOleCY3MHvr1cS+eYe1arDSThaopT3l6eV9HLJmQHkBQBzwy/bPAURlZePyItKwUcK/e4AnPtzOsclyuNUF+/8X7P9/SIydS2wyj/DBUsKHK4gfLiFxuJTgeAH+cReBCTehCTeRiSKi4y70CTfx8UIFltR4AamxfMyRPFJDOST3ZZMaXI+2fz3esRwWpnJZmipQzOmbLiI4XUJ0qhxtagPahPgIm0iObiY1shVz+CIYvkRRemSbKgpcDTjknPC4G+9IMZ4RFwHJ8I5egH86i9BNbqLv38T83deC/7dqzUDhKbF5fRlL4lpdIZ2dUqaVOOcrASKgEd/kpT/SQ1bnOSsvWdEWcTytDLbjBJ/VWfYKthkJKftAPw3h58D3NMz9Fk78itQfHiH++x8TfeKHJJ9+CPOZn6rv1e/+oxA7AfHTYMxb0UUpo3cYXkwhO6sugBVj7awTLuFKu6hSwsiqzN72n+xKY9FEEviRtXZ1Ff4JQnqRdPy0BZC0rFNoB4bk9aNPwX99kOMf2MGxye0EDlWg31RM+MZStEMu0vvXwPCFpCbdyg9ZHC9jZnIz0Q/VkfrG+6wlLdSzW0EOAbGAYzmqpt7BgYsEQ+zkohz4lwBE5a1slS0Pju7H+8h9PHf7e5mfKCA2/Ab0oX8iPHIBwSkXnuly5ibK8E+Xod20geBUGcGpCkWhyQqEIpNliqITJQjFbNLHixGSaJFFbvSJfPTJvGWKT+SzTOOFygQTMywxJtrITVJotFiR/C1AjE0Wroqik26lrbxKjWeRPHgh8Yl/JvIvJfDgYdCetMpaZGJ4ex1ykaSW0HEkvLTyS38EPLpujWER08v5SA4jri2RSPqUByDgEEhJ5wqjiQcTjmtkpP5MCjNTpyH0Gzj2Tfjlx0g/cCOBTzQS/WgN4bt34L/rOjwfeA/zt13F7C3v4Mwtb+fY9GWcOHwFc7e+E9+d16J9tJbUZ3bDfR3w5X2qnJ2nH4KFp60aNwmjSoLWtH3S9JI1mMk4qRK1GVl70IgSNNJEpTRAluU1ksrmk5GAQUAMLClVl9IaaTe1aKdjZknEzp6pRDGoVEZEn4Hf34/vi8OceP+78N6yidShtaT2/2+Sg2/CHF5HeiKPuPieN27Ff+M2jOkNykcJf+cTVhY/EcaMSvGqNf3TYjyCpoSM5YNYsEla95YucwDidMaf2J4jLyDk5DvEZDCO/YLFL45wfHoL4YlczIn1JCfy0cZF/ZUpM0tCsGJmCRhCU2VEJmxgONtlkJQRnRCywLJyG5sQoLjPgmA8n4RNFkjyiE+cBY/Yos+jyTxik/kvCQ5R2S9F/uFcQuM5hCbWEphah3nXBnigD05/H+ILymwRwSFttBwOtxX4yymWE5CIMy+RLdEulo8i/kJSMVw4GkI3pHpXACg9KEwXAP8JMid+jv6rL+K7/zBzn2rm1O3v5PTN21g4UI55axXcVAaHy0kdLCI5VUR8sgB9rIDYmGSkXepv0ebaeN7y97GRPPxjpfhueQ/zd7TgvWeU2P13wi++Bsd/CsGnWewSOQAAIABJREFUrahl4jikjoM5Axlh+6gan+PLZPALMGI6BMOkQgaiMB1eEpDMZ2TuEqvd5L2U1lUmoJPIdELWsrLvKTVoau7rh/j9wUtYGvg/MPZPcFMuifG1aENr0MfzCB3cRHi6HCZySB7exKm7u+Hx74MmGnEJUrIMuEwimCaUljCEFbZQ7SlWkoDT0RxnZdWfgAeoRKG8lLyIkPrI6Lxf3Mfs+68ndnAzTBXDaCEM5sCgC0bKYX8pZl8+KQmPThYRn7C22qSzLVLfy29/mkrQJsrRJiptKle5j9hkKdHpEsIHilRFbuigi9DBAgKH8vEfzrUpm8ChXGLTBS8JgJcChzBScjKb6NhavBPZ+O66nPSDN8HSTyB5gozhU1BQhpI0pmpQm3ntBJ/V2k7D/fFWolkCCgGIbJ19OVKYRq4dk7XSRTWpS8cgeAaO/hfmw/eyeO8w3o8147ntXSxOb2RJqgRGckiM55GeyleCy5i0BIs+nqtsdW0sh/hoLrLlcCncWAIHizEPujGnXDjHByeLmb3xLZw4fCUz0xfhnd6Cfsul8OHr4EsD8K33wZmfQeiYmi5GTC0pwg8SJYIMWJIKWystYbstjnqVOfsIJayRJSJYxMhRIJE2VOZZ1Brbk05jZsScFDEUJn3mlyx8dRrPwU1oI2tI35hN4uA64pNr0cfFhy0iNV4E09nKxD86fSVz98mIxAdAgVnK8wXESfyGGHp2vylgiI8mZDvqf9xdf/TNOVa1pl37lcpYGVnJpi88hv6Nmwh94N1KnaWH1sPgBTAsodkC2F+golWm+Bc2JScKEDImz5IwoZA2ZZEw9DJNFdmAqLSy41PlyvcIT5cSXgGQ8IECwgfzCR3KJXQo26b1hA9m/1mA6NNu/hQZ0wVwcxHBiRw8H3gLPHirFeJOLZJJBkiZcdWxwruKeUX6qQiRdKZjqyvD9I8a1vlC8iOiORz/RLYCFkVSniP952BOxpk/8wsSD3wC/z19LP3L1fimNiFCJzNZCFP5MJUH03lwoAAOFpAczyE+kWMx/VQeyelCktP5pA64SB0oIDFVsPy3hErTh4rIHHYr0Ji3lBG4uRLfjeVEDxRgjGeTHlkLYtIe2IL/pqsI3TuM/zsfRzvykLUwJ34y+EixoMaLCOOr9hHGl3yORN5kdsSkTsaQ3IP1+/OOU+UqkuiU8K+pJsEU40hpaIl0Lf0GfvAvRD70LuZG1pO8OZ/MbRXKWtCGs2HKBYfEesjDe/PFPHvL1YTvPwCen4J5EtIe9ERImaeqH6R9paHl+eTeapIQK8Ln9NOf2p6jXkYShAkdMx5VJM46yVk48QCeL/Vx5raLmBk+j8jUGzBvXoN2+Hy8h9YSuTGflHTYuE0TeTCRp+xFczJP/SYdJIwoYTztQAGxgxZFDhUgFDvgPksHC9EOCBWgH8jDmM4jMZ1DaipLkTm1HqH01FpF5lSWurZ1jnPu87f6QRcvRfFDbvzvu4zQNw/D4qNKikXSCbwJqYsS7rWljlOEqVryLwfICxteTCtHm6hybcl1BL2YR39J8PufZunTQyze9l6CUxswhBluzIcDa2HiPBg9F/avIbN/HYmRXKUlBBzxqWzVVsmDeaQOFZK+sZDMTUVkbnKp743pHLWV4+JTuep4fVLOuwB97P8lMfW/SRw4n8RNBRg3V2Hcsp34TZeh3XQ5wUOXMX/wck697z0sfWEvyUfvBd8vgTNqftyQDNu1eU/5LhLmjS9ZVdcyMExK9O2aNAGSEgiqUSypEIj6kJiXaFJxaSxTSIYzHIHffZngnVeRvHUzocMb8U4XEz6YS+qmfNKHRBMWwPu3MH9oI8++/53Ef/JBMJ6EzDwyGjMptWdyTUGpyDYFEvlHqgYkAGFVD7ywj1b+fQ4pAYc4ZGEy8TAyDkBFtERCmrPEfvkZTt1Ty7ED2YRuPI/UbRcQuvHNzNy4Dv9tJYqRxYESElA4JMBJKHo+QFaCRMAifys6mId2MG8ZGNKpFjhyMCdzSCvKgoksGLdIvhPwvRRA/n/e3gO6ruu689b62swksS1ZYhFI9F4JgBSpFpdxquM4TuI4zngmseOZzKRMkkkmK7YlkUTvAEH0QoIA2FQs23KXYjuO4xa5SLIkq8vsRH29l9+3/vvcB0KyLUfkzGCtg/vKfe/du/f+73b22UcA+GlD2biLLXcQvffvXNOAxJLNtCrQlEYT482tMq2z4T14BJZ2FISMq5tp+hMfK+4QMF7xlwzAc18i8+URLs7+Oc93/ibnD9yB/0CTaX8+tgP+7kb4nze4499tJfP3BaQ+VkHi7hpi+2sJfqyUwN2FBO8uIbS/mMiBcqItZUQPVhBrLScukLRVEGuptOc65t6PHyyEljeTPfgm4i03E2wpZf1gLWsHGlm/R9a8nszBRuJ3KdOnJQT1vNT5qyyf+Esy/zIHF75pzTKcKlHZiwJ8zXOsQUxLE/TcZZfMs/KsiYDiwJIhkgkSS0eJe3OiTq8nHG3TF+HRY8RnPsgLd+3j/D2NRLtqibeVEd9fDa31cLDMUvLP3r2Lp0beR+KJU5A556JGscbhwf2gQKLrsdIUxSeql35t/l1nlWWZhMuZJxLmOMjUKS4x5q/8kMgX+swFibdUQlsJyXuKWLm7hrXWZvwHawgdrLQROVCJRnT/lRG7pwo3aoypYuyVUUXi7ioS98ikv2rodRubz68jcXcdybvcMCG5p+Y1LUT8YA0/bSy338nlEx+DJ78IMZXSLBGO+S17pOktBZqiw4YLYb6ry17JZ47napdeIfU//kRxh4oXFY/oT2BZWVkh9NSXiB95L/RWE7pnB/67dhBuKSPRXUeso45AazXLd5Wwur+SYGsdkY5dxDp2EWmrJXSgytzOtf1lFospPlNMpqPvYBm+gxV2zL2v5/6WcgKtVQTbKgm11xDqrGWltYLltjKbvF1rKcR/sIDAgZ2EDuwkcqCQ5b/dRuxAFfTshZ7biO/fbe5w4uBt+A69h8Sj04TOPALhZ7117EpbuwIAzY3YxKJueqOCO7cAK2OrK6XJ1YQhHlGdX2xjnkeTj6aok0skHr2XlZkPstZ1p5tMPFhF9GA1mdZy+Nib4WAeq+31fL/jLTx2/G8Jq/5PYLVCtE0+3gZABA7FKWGviu3HeZZ75Tp/yN1QOu1KTsRCmbt1FeXqiUozH/88q0f+C6udd5Bsryd9sIrwXXVu7uNgDb7WSnwtVfhaagwwAk3wYJUxUYCJSfhfIfB1JO5qMGF/NUB07mZQRQWAe2Sp6ojsbyB6T8OmY50BUlozdLDcgdPOd6DRb4dbq4m0ViNwJw6WE28pJ9xaZ77rM92/R+Kxh12aUKXqcR/B0DqBVNqyesvqGu/R44olcbZapDFxlzR4SsjccM+i67H9STCSKbLWmCFmWRbOP84LDx/l8dEPsL5/O9x1HRz4t2Rb30yybQfR9lLCHbUEOxpZ72hmtXMPa+1NJgTrrVWst5ThaynCBLqjkvWOatbaq/C1ubHeVk5uBDqr0PB3VNr7662VaKy1CBiVnG2t5XxHLcudVQS7y4h17iTevo1YyxYi+7eSaCsmcHc+vr8vspQ8B13GjL8vx/+3pTx5cB/Pz3+I0LcnYPnrNuchDS3ayL5KX28EyoYT5ZVkc1RZmySuiT4VXmqZg601d+ltNbSOJNLus5EL8J1jrE7+By7cs4fQQSmJeoKysAe2kr3rBuhvYqnnTr7R8hYufL7TpY7Da+4idCGObRvunmZpsqb+XmXVc3zzjtcJDLoZVw9qmXd3aznG68sTARKPf5zHR97PSx23EOtugP0lcFcByZYqp9F0we27CHgj2F5PpK3GzHuypYy0xsEKktLoLbtsDiXS2kS8tda5AXIFNkYN8dYfH5pA0vkbx7Yqou3FRDoKCXYWE2qvInGwieSBZvt8qKOCpdZSIr01JNuLyLTuINmxgzP3lPPs4T8h/O0vuDb7tt5bvrKIdWXWWs82GGwEExLcMACozGI15NJQXgmIKKg158FU0vbCSMdyRVspiKzC9+7n8tQfcv5gFYGOmwn2bCXYcxOhru1EOgWOYosFRKf0gVrSB+pJHqwl0eJoGekoJtSZT7B7B76efNa7K1jvqmG9qwrfxqgg0PmTxuZzquwzq91VrHZX4OsuJdhVSLRjB4n2PJLteaTbdpBsyzeQyE1ztN9FtKXZSkKiLU1mXaQYz/XcwYXjf0zyiaOQesqcVFkE0UmeZUpC5imSZEa9zlQR7pSznaS5l2zcQCWrLbmU6Pm1nkWPkkvw1KcIHvvPLB/cQ/hgLQw1EW8vhJ5yaKm1xESwpZhLfXtIffEeiDwJkRDZtRgRrb7wem35jLFayeb3MiSvQsWmp7ZgShdyBSBrriGARfwuKWGB1vJTXPiHQzw19E4utdVDWxns30HmYKkJtsy+QCGA+Dp2EeioNYGNtpcZgdMtpQgoidYqoq31hFqbCbU1GbiiEvSrGe1lRDrzCXXtINBVTLCjinjLKwHi76/h/P6bCR7YQranEH9bHi9338rlz47DyiWX1dhEkNf1UAwPu10qxcdg0jWyE4OV4wqq4Zssh+q3tCXyN+9nfeqP8Xc2Q+cW6L/BgLHeU4yvu5hgZymR9jKibRUOJC1VZq1NsYh2baXEPYUQ6nRKQdbB11lLoKPGhmggxaDvsdFRahZJVkm8yA29F+oo2wBSsLOMiM7tKCTRnm/AEDiSbYXud9sqTOFJCfram1lv32v8o10ZpUJz5852N/PS7Hu4/PB+ki9/BmIvuSJFT6/YOvtE1lZPJtTAIhs0bFyxzq4qV+DQkECvqdOKiCsARV6C7x8jevQPWWm5Bd+BagLt5QQPFpFRVq+1Cva/mfWPXk94+l3wvWMQugShhLUz1QLnFa30FGpl1mJa3++h9qcwfsOC2Ps2kSJz57Wdt2rVlNXykF6Di9/g/MJf8lLb7SQ6a6GlwPLUsg7S/rIYwXYxS2C5ApB4WymJVoHDnScLIOsRad1FtK3m6sBh1qPMNJ40b7CjglC7rEu95celcQW61FA9F+/eynrrVoLdJbzcUs3K/B/Dy/9sltHSfj+FOP+ql0XfpDCgYj0tNHMzuaYBVfekVObqM2T+aZqzh3+f8wf3EO+phwFljPJItlQ469DqrlfCHegsM42+3l1qR1+XE2RZSCmieIvucZdZy2irrPEuu29peN23rLpAJeXFwWJQMH5AI3/T2GHvyVLLXdH3ihfio7JZOX4Zz9pUSLiZv/WeEqwnoc8drLCM5lJrOc8dqOCp7lu5cOrPiH57DvzPeVbatTbS3jnmlJAgquSQVUCahnbk1ky7uWAu/ltVWbspa7li6mTztLlbvpk/4kd3NxHpamTlYzutRCjTWQWtO4jdvZPVrn28NPZBOPeoldEIDz6to1e1SQ4gWuJqrsBP5/R1uhxZHPsTsy01JofNXWhErT9jEYfg+EUyXz/GhfEPsNzZRORgMdnWEmgpIdVWRqK9nGhHtfnPCgDDHdVEOyqJdZSTaK90o63aiBpra8BGey2x9uqrGx3l5jPHOguIttdZABdrq7PvT7bWWnYj2V1JrLcUf28BL7SW8MLgu+BbRyH2sosHbG4jR4DXd8zRWRv4JBPSd45msWQIdX20tjzrPyTw5RFeGHgnZ/dXE+2uhqF6/N3VXPhoIamWBrIHGu1owtZRTaizEn93OWu9Zaz1lrPWU4m/q5ZgZwOh9mairbegIDlxcB+Jlt0kWptJtjSSbGkg1VJHVu6H5joOVMKBcpsz4ECJc4v3F4GNAns9c7Bh4zs2f0/C6FhHzPhT6/FVvNX1uRHsrMXfXkegrY5Ie4XxOXCwiMsHyjjXfRsvj70P/5cOk9I2bEnFGBmLm0MpBeqebHoAkQCbrFrHlpAp+JxLJKoaLa29rEpTnod/WWB56kOsdr2V1YNVrHeWEuoqIbq/kExbPdGefTyx/y2saf1I+Ix9uRZ+ZjX772UlfxY49LPXuWpHl4qzqzKnW0hxacxQJkI8mySrzmJqjLz8FMmHB3l54Je4IC0lgBwsgBb5+CUeSCoJd3pDgOmsNALHBBIDiKuWzT2+FoAkOneS6Cgi1tpMrHU3UWNoJQJIpqXatEl2oJKLPSU83Xcrvi8M2T2QuAgpr0jz9eFi42wx1NyBTMra0rhIUAyIeKnOF7n8xT7OzPwel9oriXfsINtdQLgtn4utNSx37SHc3kiitYGcQG4+CuzR9gbCNhoJdjTj79iNr/MWfB37CLbfYvctcCRa3RBIHFAcWDIH67DRUmvAEXjcqCZ7sI7sgWYyB1T7tM+GyjcSLfre3UTbmu367Pc7aj2elhPtLCPaWUKoqxxfbyPB3iYHkLt3krpru1ksxSyXWhv5Yfcvc+nBj8JLD7vFd7h17FpLY4pZRPQeO4B4JfGeJZa7agAhSSq86rqvyN3yPQ/fu48LYx/kcvcdrPcXEuzdYUWvvv3NZHpvY7XvLTx39I9IvPAZNx8jFNr+h2tuojYHyg2O/viD61wkL6Z6pkRXrce6IOKEslpxBiGVsvojbrHQi1/iwvE/4+Xe20mq4rc1H1oLoa2YdHspSdPsFUS6qgh31diIdNYQ66wh3lFFsqOCdJsb+ny8Q69fxeisINlZaL+Xat1NsnUPkc46Yp1VpNrqoKXGViKGW4t5oaeWix//b7CkAsSwt1xWMx6yllf3J3qHbLbdBfZJdSuRo61KhMuPE/nnKX44/C6WDu0h1qfrvJHowZsIthbh67mF4ODb8HfvJty5y1K48fZ6Um31ZFtUHqIcvzumW3eRbNM5TQS6drPevZvVnj2s9zQR76izCcF0Ww2p9hq772R7nWUb9X3x9l02Yu1NvHok25rg4G44sAe07ufgXlIttxJvvZVI+62EO/YS7thDuLOJcFed8TPWVU68q5h4Vz6R7mJLgvh76o23sbsLSH30ZtifDy3FxPYXs9JWw/Pdt/PywodJPn7CGuhp8ZTcHO2zmrMcOtqfqollRWwSz4FDHR8jiaRrqCehlnyqgjd+iew3Frk4+X6ebdnGxfYtpjwCrXeQ6GgmPngrz/btZfWLH4Nz33OVy+qpFl8hop3Jchm23G//hON1Lpz0lkjqKjWsVMXlq0PeSjMtLU5Z0VAYwi8T+5djnJn9AKHOJmgthjYBpJBsezGpjmLineVEuioIddcQ6qqzISJLeAUgAcmBqcJe0+uvd8QNIKWk2itwQtREpLPeQCIhsaCtQynREi7M/hbZpxe9+EqqX9ZDSdxrAYgaFsQ2Mi7GOJWOX36O5FcmuDj2XlZ7dxEfLCbRl0eo4yYC7fnE+htI9N9GsGsfa917We/eY3TUHEe6VcBW4FvhuUflcLAcWitMGYmGEkh9r7+nhnRHPrRth/Y8aN9JuqNwE/2dggp0y6XbZUOg0ljrabLfNDAeEBh3kVWCo203sfY9BoxQp65rt513BSClxLsKSXXuJNmVz/KBbfjaipECTHU0uMLJllrMpTuQB4MV+A7czPP7izk/9154TIHzC+ojxLpfcyE5C5GTfEmpBND8IZsLUTtWvysYNqsTVY1XDlnhs6S+Ps6PRu/kTEcJgf47ifW9zVnezkp8PWVcPHwnwS90w+XHbFWj1qRoN6t/JUAkIF6K0wq6nN3R78tPVMQvXzDnM2ZDPrde/fJ3OHf/3Sz33EmqvYp0e7mBQwBJdxSTVEamq9wAEuiuQ0wSUGRVBJBsuwOTgPR6gbH5fFkk+31p0LY608ahrl2mWdNtVXCokXDvHmKf/xisP+Z8YNMUihY1HbgRgf0E/fHaL4lGIrI/rZy+Z3mjQVJfe4DlsT9iuaWRbG859OWRHMonNlxOeKCBgK6vvYlE5257LOENdeWArRKRGgeSlgpXaqJyk7ZSUh2lxEXX7lJCPToWQsdWaL8B2m+0x9mOPBNeaXk7r7uCQE+VgUmA2jzCXVVk25QidQAUvaRYBFRZDSm/QJfGrldYkGRnManOfJJdO8kOlRnoV/aXEm5vJttzJ3TeCm210FHkZeu2kurbwaWeal6eei/+r4zD0nPWTUV0Ew0tHthoLqHn8mpUzRG1OrbcBIR6GKtNlarP7XNKKCWeg0eHeHn4VzjX2kS4u5FYdx3J7nIYKuXiR29ibeJd8Ox9toZGa22UZRQ4za17DTZfl7swd3ruY1dWk+kiNPRlTpSEbK+kIPoMkfkP4ZPpb62GgXrSncpW7STdXUqsq5RQdxUCiLSejuHuCmNytiMfjVhHGeHO8qsaSgCkuhqtvit2oIB0Z4XNxay1NhLurCfZowRAJckj74FnPmlBuXzai+pkbskI3ZX5k69Bop/+lughJ031SM56aFL1q5wb/nNSg78BPU3QkU+m62bCfSWs99ey3ttMuKuZTFsDaNXigTxC7TuMVom+GpJ9TcS7mwm2NrC+v8YeJ7oaSHdVkeosJNN+M5n2G8h0/Dy0/zy03QBtN5Jpu4lMxzZSHZrr2WlaPiZXqLuEaGcR4bYdBFu2ET6wlcjBrTYRmGrdBl159p2a95C7muqrRNcR7Kpktb3ceGZ866rZcLGk/OQl6PxYdz7hnmIDeKBzL+H2O4m13UpaZSDyKto10/3/km7/OeL9hVzuv4VzY79H5stjth+I5E9S5/jgLIr60qXkQtkut5I397oBwnNyVAakoaJEsqrdet7iy5WhO4n3lZEarLbro7MADlWS6Skhcuo/WlcU/d6lgN+aWPxsgEg+7Cx9TDiVCLl8tK039laKCekK6LM57Cn1pqzCPw4RmX4vSwoauxtJ99aQ6Sol011MqrfMABHoqWG9VyCpI9RdgRgn10Aj1lFyVeAwUHVUk+7Za5mWRPsO0t3FRLt3E+y5lWDfLgK9Daz17IaH/hYuPm7VnBJoFUSL2BllM67hT59e9poMWhXrxSfJPjRIeOB3Sbfshu46aC8i0V1CoK+a9b4GfL3NRDsbnYZtKyPdmUei52biPQWEZRm6a1jvrGe5vZHLrY3Ehn+RcP8tbib8wA4C+28k1no9dL8RBncQ6akk0NNowbK/bzf+3lvw9d1CoG8vgf49BHsaCPfUkuiuId1dTqazyEBLWx60bSF04I1Eu24i2b+D1EAB0d4CAp078XUU4tOkZLfc5Arjo1zmWKcUXLl5AbJmod5iAr0CUj0BuWQdil/2uoqL9lLo2k6m5Q2k2n+BdO92/B2lXGrfRWL29+Gro1bek0jEyCTlp7j2RLYNQyJFRk0Kvepbiagstv501NmSVFecouW/wIUfwmf/gtWeUtZbtsOhCtBE4oGtZFpuIDhxJ0vfOkI4eMHm8TW/8rMBol8zJSqAyCf3AiRVYOY60lg1pkCTm573Yhah/OI34B86OT/8W5xr20usrxH6q8n2FMFgGdGeMoK9lfj6am3ocbSnhHRXgQ1ZGRH+qob83r59pHoarYgy3p1Hoq+ZyNAd+AaaOdfTxNLEb9rkkm1Kk4b1jNv5QgBJZLwNQD3Cv96DeLLkbZlH/DzZR4aJDP0WdN9maxfoqUPaP6R4oW+XgTba00CyS8CpIdtZSaq/iPhgAdGBIhM2X5c3M97TZMK+2r3bQO6XsA80ERxsIDBYjb+vlIt9jVw++iHOHP0fNs4e+2vOzf01F4/9FctH/4K1o39CYOYPCYz9Dv6+X8anyb2DSgTUgaohhhoI9exgvXc7Po2ePAI9eYR68wn3FRDtKzZeiYcacVn/rkobic5qIt3VxtP1vnoCvfVEuutJdNaT6qgl1VlNQuf2VeDvyDfQxfpLCHcVsX73zcRbS4iOvxOe/gSsv+S2V1PK3eaO0taFUzsebHg43ky7BFp013DuWYqQukSav5uBHz3I+vHfZFUKoDMP5NJ/JI9Y+82sDNTy4vT7SDz9oMm5Xw2wfwbTr7MzDEa6misWxC5MwNmwMLn3BZKUazOpb9e65pcfZuXev+OZjrey0tVEqq+ajPzjoRLiPUWEe8vw9TliCiCRnjJS3QU24t1lRLsrr2pEumuJ9ewhOdBMrCePcOcW4v01RIf3cXloN88PvoXApz8CF9R0IYlaNkW9mEoaKPKvXzfzE8mo2zf3QAHlS//A2ux/InigzhV03pVHtqeGUE+TaXRpdwEl0V1FuqvSwKGj6p/8A+VEhmoID1YT7K8k0FdBeLCO8OEm/MO3sHJoHxcHbuPs0Nu5OPluAif/mNRn/ob0l/tg+XFYfdEbL8CqxnOw8jQsfx9e/BI8fi98aZDU6f9JaPwD+Pp/g/WOt7PWuY+zHRWc7ytldagS36EKAkNlhAdLLLGQGiol0V3gjRLEK4HE8auacHc9a32NrPU3EOytJdpdQaqrhHRnCQkpvZ5KQkNNLHXXsNRZRWigllRfubl0tLyJTF8Nl+Y/TPrpT0HqsqvgCF22tqZG282pYC3BSIdMLC3es5WCScLErIe1lbLY9N2L8MMp0vO/xtpHt0KPJlQriQ/UstZfy/nOBlKf/4htnaFCSc86/ET+6kUvBtFD11XDlZyYSXHoNYBonkSi4LLSKhE25Jnd0z5350k9usjzY3/AGWVAuivIdBdAXz7JXmmiUoL9VajsQ8dIXzmJ3kKSPYXEesuJyqpczeipMdMeHdxFsDuP9Y43E+0vwD9UxdnhvTw/+3vw9AMQPKPmUWSEDrOGyj5lbYbW7uOnkudnveFlW8IvEvxcK0tDbzd3KttyI3Tnk+gpJ9DfjG/AuTvR3l0ke6vMH870FhHvreJSSx3LvXsJDu4lNCRNXMx69834+rfhGypgbayWlZk7WT/1BwQ/9zGS356H5/4Zln8EIc0uez6HbmTzkIq1Xsra3FPNHc65FPczD8PXjhH+ZA/rp/6Wx9ru4OXBO1mbejuh6bcQOiw3rdw0vcAhPmZ6dprCS/YUb/BL9W3BvgazjP7+BuOfeJru2Umydyex3mLjdXBkn9VGXehsZqWnkWg4+/l8AAAgAElEQVR/FdnefOi5AQYK+VF7E2v3/xU892mIvuB6Msd91g4sF/ua/pYFSav61lkPFxXHrdG3XLJkWP2lBR25Pefg0UGCw2/D39ZoMd/64K2s9zeR6CojPfsr8MRJW1hl2bLXYPN1OQTphzcPez2XSVCmwIYKykT5K2ZOKTerk1n6Lv7PHOTy8C+ZH20A6dlOujfP5gCkGX0DNfgHqgj1a3a7mERvsZngWF8VVzOiskrdtUSG6vF1F+Lr2kp0cAvLvTfzo7HbWfrsRyHwDKgSQK37NVQ5l3VrloNZr1r0NQj0mm8py6LdWZ/7JC9O/h5Lw7eSHa0g1v4GGMoj1ZdPuL/WQKKYINTXbPeZ7Csk1b/d/P611hJLYEQE8v4qVjuLudRZyNJABcvje0k++B/gKx+BZ4+D//uuMZs1lfO692hNkDwMrU60NqNXeCO8RCPy5dWxRn661v6sQfSitwfhN4h8vp31U/+VsyPv5kzf21jpv5XwQJNZg2iLXJSd0J1Htnsn6Z4C45sUnK412F9DpLeOWE+V8TLRt5NY/3aiA3kEB4rxidejt7M2eDuXuvey1NnEuiaQ5V733ES2P8+U6bnOvayc+jN4+XOg5hCJgDU9F0A0TOIsw5rT+HpFHo1iFK2CxeKVVDrrMlsCidrePjrKub63s9631yo/ZMEZqiMy2Ezsof8Boe+49SuvwWRvHkT9ZF13buvMbh/QBag8YNXrqKElkl4DM9PC7hJXVEem89We9NkHSN37QWKDzdBbAN0qENxOoreA4EC5EUxEE1hkVQSSWF/FVYFDgBJAZJUiI40OeAMFxIffyMXuX+D8kXfAD+bNLEuRpiVU2nBFBYQJVUzJiniW8DUI9JpvqT5t7Z9JfPYj/HDoHVwYv43wdA3BwZvIDLwJDm0l3V9gbl9gYB/rg/vwDzUQGSoiPaQg+9+Q7f6/oP/nYXArkd4iVnsaWBv5VaKn/pLUI0Nw6VFYeR4CWqUXcQrSEw8THGUU1fFEbYDMRVYFhGuCLQ6aK6ljNkMsk7BCwbSWxKpTSuwiBB+3lXvh+z/CxdH3szr4a0SGfpFkT70VKtK5Ezq3G0hkSTThGeovxT9QaYou21WMMkWyHAKGf2gn64cKWD0kt62KwKFmwkP7iA7eRrB3N6tdtaz0VLA2WEZwsNDiVK0/We65lewX7rGl3lK4ygpq2wjZhNwwS2LzI86TMWWtxtsJFc+rQthlu9RoxXVb+RHhz/xPwlNvs0VW9NWTGHkLl/puJTX7a/C9Qbdy9jWY/GMA2VjgYggV0QWQNWclcl3APTdFDFjSmgkz7apYfQ6+0odv8teJDtaS7M0j03ezaVIBISyNMqhjGbF+N+KyJgOVXM0xMlhNeLiO2FgjoUNVxEeKyYy9mbNdN/Hi8T+CpW9btaYW7jjbHCezvmSbZ+bW4hvRN/Vr3WxF7b1cHOatRReznGCKMVqWPI9v+le5MHQna6O3EhirIDqyg0D3z8Ooywzp/oKDjQQGmwgYQIpJHfoFGLoO+q9zQBnaYe9dGn03a/ffBd/9NFx+CdS+VJtYumpw85py+UYrJldvrOQFSC07PuGaiGpBqbSvRElDQMlp5Ki2184kSce1BuYyRF6Ey9+Fby5wee5veLHrnSy330aqvxm6S6Bnh41M3w5iA4UWo4QGHf/oLoLuQpL9+YSH8vENF7J6uIjVw2X4hlx5vWJEhu8ge2gfkcEmUxKrY3VGKwZ2wGCxxSO+sV8n/vVJp2yzKfwh3cUVi3gFIKKAZ02sY13MmtWFBRPNk0QduKx+68JDxD7xYWJDt8LoHQRGf8lcPsYa4BMfgOQLr/BMc/x3nlWK69zPu5jDXUAOTnpNFyEYeBOJVz7t+YLq46Qafq+Vik5dfp7ww/2cHXsHofE6ksMFMFwMh+rJ9lcbIeP9+SQGK0gMVJE4VEnsUOVVHquJDCgoryYyWkh2ugRmKjnbu5tL37qXpLZgyAm4lTXrfpRk8NYh6Fb1unZa8jSVYd1r2qbHJlXm2kZtn75lEq77i0qlg0+yNPMrpMbrjPkM7CEzWGpZqdBgCb7BcvyHqu0Y6S+0ib1wa4mluePDNxDr+39gVtm+Yla6dnFp6vdJf/soqD9yKkTCr7okL7ZQutMrstNLEnaR2/iXm3U2fgm+Wrh65aO5r9h8NF4bcVyhpTbPsS0rLr1A5GunWZn7c1b63krmUJNNtikFnBgoIDZURHyohPShMjhcTXKwjsRgnfEgNFJKcLTERvhwqfE0018HfQ3QI6+ikdSAOzc4Uk5wtIjo0M0k+7ZDbyGx/jpWFn8bnj1mnktOHjPaPiOrqUFHDyW7tMAvpcV8Of6+KkRw9xeG2LPw0oNcuv8veHbg7Vwc3kd4uBr63kx48hYuP3GvWZ71RIalQNqslegkmU/FVgSQq/9TQB+3jSmTLqsl+QtFyTz1CEsP/gXnx24lMFxKWqa0Twvsy8n2FZAa2ElS5d6DHkCGy22WWTPNr2sckqtWTWSwnPj4DtKTO2Gshosjv8nFpx4l4CmZjXy1uR6qLXOiZcLn5dklVnpVR7lfAr1ZCiX2JI3am5tLXLJmz0JT2LJ3genbYLQYBhpNAOgrJSH/e6iapUN1rIzsYn2onFh/Hpkel3ZUGjw+mkf40E0wVE5q8DbiJz4M35kDdT5Mhm22WNfvmOUlAxTzKC70wKzrdYJwdTzUd+s7AllYkfepG9YXqhXt9+8n+sm/4/LAW0iN7iNzuIZY906ivfkWZ6WGS1lu3070UB3hQw2EDlcTGiknNFJCeKSE2HAJqcFyS/nTWwc9DeiYGagmcajczgmNFhAbzSc5tMMSOqn+Utan9xH+yt/C0jddBa8tB9e+NRc9d9/F4bpMgcSuVyDRCxvE0Au6mSiZ6Hnr65V85jTPzP8hL/TfYpk6+m9k7VAVz365i0T2slUeBsIZ2yrFyuGzKbJJ37UCRH58VN2RHCNFcU3uBF+C70xzfvY9LA3X45f57Soi2VNKpr/EtGxSbtZguRHrdYFiM4g8gMgnjo/l20gdqiJ0/EPEL71o/aZMw9iEjoRIvvmrAKL3tDegJyy6BblfapBpANF0rZUFrZJkBbc7t9ImPlLfmMU3uQ9Gi2BAmrIe+svRvfkP1bA8Usf6WL2lT02w+opgaBccbiA6VoJvpIz1Q7eROPmf4bE5iD1j20/okgJagOix2dSkFfFpnY4uxpvI3SwTV4MRTQLr67z14i6DKfdFTRdegDMPE/9cK6Hp9xHpaoYele5UkBwsZKW/gKWhYqLDlabUoodL0ZDl0BBPk0OVBohsfy301ZoHkRrMnV9CdKSAzHgR6ZECkoMlluZeGmnkR3O/SeCbYxBTwzq/xZGZ5IoJbA4I4pOWnOeebxw9OrhmDHGS2hE5ex7ijxH6p27OzvwmlwcaifQVsDJUxeOL7ye7/AVXaRyJWB4jJYUopyiTuVaAgPabCKXFMKFWKk8r6Fbh4jeJfKGFy7O/wuWhSlY6dxLuKSQ9VGNDLlZ8qIzkcAXxw1c5hquI9FZZajQxXkBoZIelSnnkHtsJS6tdnYvi9Y81i/cqgJjr5dYnyJNyNNdzJ4TZHECiasK8ip+EbdiiJg+XH/gYvom9ZEeKwbRlFQxUkRysxne4hpXRWoLTjYQOK41dQLa3FA7vIjVcz9qhCi6O30Lw/j+F7y+4HrWpVeu4KBHVzyp2MJAat+ROKJvo/G9dp4RkQ2leLUD0dfZF+iX9oiaLFXsG3A6za98j85VDBMd/l8TQbWQPNRDpL7YYI3K03uK+9HA+qeFikgLGSBkx8XO4iuShGlLG7yrSQxoVHr/L7DzFjAIH46UWQ64N1bI03MgLg7dx4fR/gR/e56p/CZNKh60DpQXmuHUlWrPuGCYllxvuJUcb9R9Tlx7F0IqzHib7T21cnvkNLvXWszLSzGMje0l8tx2C33W7pwVd11VVIgmA1+hiOQaqeEyz7M5HVDcJBZbL8NKX8D30V1yafSsX+vIJDOSTGd5FZqjBxSCHSkkOlxE/fJXDA4jqnGITBQRGCvGP3Q6PTdtKPtMwopRUssBiluHVAHGvb86USPu4lpVeYki3lnAdyjUxZfe59G1emv0g/pE9pA8JIIUwUAoDNSQ1nzFax/p4DdHZBmLjtbZoS6U3HK61DNDZwTrOzv82PPMA+J51lkPdTuKwnAGVUQokuq5XWJBNbta1AiQHsmgsQcKv5MXKxv7rcl8StlOvD0JPw2NHuXzs/ZzpaSR4uIHUzC0kJ6tJH94OwzeRHd5pdDCFN1xDXMmT4ToDilOApcQPbx5lBqjE4E7S45WsjdZxabiB9dE9LA81szKhXmV/CuvfMIumWbqgJnvNgiYIxZIEtPmoaTSl7jUEkisAEX2Up0yoF0D8AiSfg0ufI/bFuzk3/m5e7N/NC4criXzyt+Hl+yB0zpltTR0pJLOJQmPA1f0zAstMW38usVN7QwRA2wpr5ZbM2+MnWP/EBzk/Usn6cB6ZkV2khxotQBcxEyPl1zAqbeIpKndtogDfZDnB+d+Cs582S2baN+eOGu2037cAolvPaU73MAcQ90xkFUu89I+2G7ZOWZeJmZZdgR/cy5nx38F/uJnkIQXaO2CokKyC1uFGgnKtJqoJTVSRnKwl0VdtFQbpkRqWBqo4N/F2/A/fDckX0W5VyZTbi1zrps8m4Ly3gaqzICLw/3oLovtTuiIUD5MIr0My6LZ1SyZtbkEC5hcvZU1SzxF+bJYfHf+PnBt5C6HRvTBZC4e3wMj1cPhmGC4iPVxpFjIx3EB0pJ7oaDWRsTIi40VEx4qIjxWRGCkznqcOlxMfLCIxVsHSeB3nDzcQHN1Damw38ZFaLkrZPTEBseeNF/6E5ntjqOmDwBHJlUIYODyQbEpQiHaK2BJqdapFbNotLfgkvPhpgp89wA8G38HFsRpWj94GT6gJ9osbKT9tuKZK9mu2IMKBJqiypu/E3iiJeNQaNlou2vc80X/q5vyRJtbH8yzjkz7UQHywhuRIHYmRSuKj5Vc19FnNzCoTFh3PJ3Cknuin/gR834JUzK7LLIdTJUbkDYAYup2PoocCiAmjnlga2+u6pzcCApTmGi7YnkwkzhD+UgerU79O4NAuEkPFZIa3wKE80oPSms0EJxrwT1WxcqiA5Fg1GZVZDNSRGG/g0kgTq/d9EF76lKVmtVgzqOF13VjKuhovPdflGJsNIF6ud1PnFfe+g/Xr/S9L6U+qC7oSxk77EtdKJm9vMz1MaxdbpTUElDMknrufyx//c/xj/x6mmmBkC4y+EQ5vM4BkDlUj/uYAEh6rJDhRQnCygOBkvgPJaAmpw5WkDlfbMThcweXxKi6N1jgXeawRFKMNlrL2iT+Giw/bfiYCSMTbFTkmoklvmdVQsC4o5LIyjpfGOq0jyRFJezqGzkLoOXj+YZYf+ihnJ27n/NSd8MQshF6EkLrVO6Wv/Mw1AySkCgDjjITIbylUlZL7c/6BOpp/7xTnjt/B6tQ2UhPSMLVunmS0kfg1AiQ2ICJXG0D8c3uIPHIXxJ81Kyba/WsAousXMe0+vM+oTseCVs1S+5VilHU8R1pBY+QF1j/xF0SPvIPAUJ2lPpPDbyZ1eItpz9jIbkKTuwhMV3OpZ5tpS1kWWc7k9G4uz7yV4MMHIKGgXLu0OsuuBgXy/kU6m7fIXVCuosEL0MVvfUYjx/vXCw6dL1Bo+zaXtXOFBrZE3wiSJOpXax53LYpMNB2npt688HFin/pzVoabLDGSHruJzIjc5zIyh2o3AaSW4EQ5vqkifNP5BKbyCU8UEM8BZLiWzESzxWMrY2WsjpVZZTCHqmC6kMxoAWfHb4UfztoqwFA8ixbwqVWpFzo6gOi6cgDxKj1yPF2JqHWQRyvpAK1n0vp47Wf/wuf5wcRv89z078Czn4DIefArRPBCh/8VABEBjY8miRIqEdxlRmVZzJu5+AOWHnwna7PbiI8VkB1zmiI62kRsrIbYePlVjcRoFYw2GUAyR8pZOnorPLvgUoK2/NW7OF2gN/t/xYJ4cYn3+gZAdK4pU1ebZmWllni/DFllRCKw8n3WTn+A6HgzsdFdJEcryIxvsZEYrSEy1oR/0lkQuRdyKZK9FWRHmgjP7GP9vt+HMw9BTFsKXJkMywm96OcEXxci5lsazfnZnqXLzYM42l8NPLzPbNDFeRf6Xl2Hl7qzZuY5QKrmyWbr0y+Q/eExzp1+PxfEg+N1ZKdrLHhnpJHMcAMRrSuZqCM0WY5/upj12QJ8MwWEpgqJjZeSHqkwDyIyupvg+C5CU8XEJgqRC8pwBRzeCqNbCY5Xc2bud2H9Sbt/TYMabHVRqo4wLSiKeRbEAOLmgXQfup/cJKnOMsKqIkTLrtWX4IXPwsuftyXSBC+5LKzR2GUyr9mC6EeNSTltbZNsTgvq4izRvvQjVj71btaObUXZJgEkeGgXIk70WgAyVgEjDUZUAWR54S2e2xIgq15KuYvTtW0IgtwFuSqvBIi0qLkZ3mdkPdTcOKNcu24ivQTZFcgmrEo2ePp3iY9XkhitMx86PbGF5MQWYmMVhMZ34RNAJmtsXiAzVkFmsJzsaCOBI3cQ+NyfweVvubZDpvlEqNyfLjYXdG4Gh3MfROsc40XfawGIZEyf1y1vFiRl8DSZakLnJThU7xTXHmuWRVsmtfYtVr8zzMr9v41vdg/B8SZSU3tgtJn0oVo313GoiNBkqQeQQtZnigkKCALIaDnJkRpCY7cYQCQX6fE8A05mRHzdbgBJjxWyMv1Wkt9dtNWAiiC1qYEtqLK9F0Q3j2YbINHzV96XQKI72pBV3ZdcrrWXwH8G1IVRnek9vidto4fAtbpYLh0qAhuVxUOvRFkmWV6rcXN9hfXPvIfgwjbSE8UwXk9guN6IGpuoJj5RcVUjOV5pAMmM1pIWQE7/GsmLX7OLyajn0WaAiB4mCDmAvLKuTEG5neEdBBYtEEvZPuhx0iq3kfOTUYDwfSKn30VqopDkWC26jtTkzSSnthKbLCM0VYt/ahcBjaEimKgETZiONeA79g4y39TWYS9dabG0YSFUfKdgfNOw9xw4JNC6vBxANhhu4vD6/+m7xCMNPXb/5SpruCSFZNC0bjpDMqJ9Gl3NV1Z7eYQeI/Hdfl4+8uucGb2T5Pw7SE40kzpUQXa0DH/fNqJTJQRmSvDNluGbrSA0XWE0yoyVkRqrJDTRbO5oZmIHjG/DvS6LXEh2fAeM7SQy2cT5U/8NVtRVft21LY2onsxZCtHFgcRztSxod5edo9VmK2LnC0O54SlPR1vJtFqnrhPj8rUBxE2oOR92g3Oe3Akg8qWNm/41Ap97D+GF7WQnq2G8Gd9IHb6pOqKTlVcFDoFKgpk9XG8WKX2kEt8nf5ek7wemDV1libeQRoTwgKvSGGvRLSJ66lcHWQsTEB1EZ7OEWmvu2h9pP1jLM4m6y08Qu/dXyU7m2TXEx6tJTu4gPrWN6HQhgekKA0hoopFAfxHYPZeQGq9hfUFroxdd5xO7rlyGKpel2lw57SYFxUn9bE7bO0Y6cXbCYRLyuv9JeLwCDvt+A6atu5CFdb+nCnJHpjjp+JrbxXajFiFkmw1d/Mzf8dzku1mefgexid3IYjJWSPzQNuKTRYSnyvBPV9sITVUSmxAAikiNlxGdqCc6UUt2PB/GbyY1XkR8ooz4RIkpICYKyEzV8OKht8D3pyFzxs2Qp5MkE25qM4dho8iGS6pXHY2kSGQhddQ92/2IcJ5M5N7XOe48RVtrpFi6doDEbPGit6xOv+RZkZxmMuD4zhL6zDuJzefB2G4Yu4P18SrWj1QSmS4nPnV1IzVRZQBhvJaUtNMX/iOpxHmb6jKOW5m3R5GfBBBHQyPYhkshCnrpdVcjKosjpyxiwaxpnaUnSdz3yzC5xZIOiYkaElNFxGfyCB/JI3CkGP9Mk9X6hAcqYKoSJnaSmq5m7eR74dIjZj0sRjNGea7Uj1kOd4GbgaHHV0AhhF39Xw4gpsjEOE3yqu5J5bCebtEuUcpxpQmTZp1Map2stxGnlWQkLpF+/iFevPeveGb47QSndsOUXKRtMJVvHkNsqsomTAPTTYSn64hPVpKdKLKhpE1istImCxFoJouIyw3zZILpMpit57JKWj75XyDwLbd5qZKLXqcTiZ0DcS5m87J9KhfxQOKx1cTxCv3c5/SegJGznTG0DEJrT66x1EQWRGJj+5YKGDmYZlxgJLNmV7T6FIGH3k78iCaVfhFGf5n16Qp8CyWEZ0qvASCVZIbrYKLBABL/yp+g7rjatsCIEPfUn2dBHCFkQVSyobUhTric0Hno1sEDSMx2kEgQsSSn61huMeHK0yTueztMv5nURDnxyRoSk6XEZnYSnNuCf26nA8jEPhKH60ECMLGV7JEqC+7xPWrmXfS5wlhdjOcimJZxVkOv/jhzJQhe4G6IvTqQODdSFlKiIffOS9/oorziA4UdcjWdIxYkk9GcTRS1EHVLYiWlZ1n/+gTPTP8WgZk9MFsGozfC7E4k9FIgKgwMTu4jPNVIfLKK7EQBTOTZMauYZLzKKZupAmIzBUSmK4lN1pCcqoIj9eZl+KZ/EZ5ZsK6Y4q+WO0sRS+w8Vjq6mKLRO1dcRd2SznG8lkA4emfScVKag9K0ne5JsZadp+RJ+NosiH4i7NUt2VoRXamG139VP2SLlC79M74H9hGd2goDvwoj78Z/pBL/qXzCs8XXBBAFhEzuMoBkvv6X5hKpKMQAoopbj9l64bUB4gmJBxB9TABxu0gkCXo70Cq2Y/kZDyBvIjVZagCRFRRjg3M34p/bbgAJTtxOdnw3jJfD2BthoYr1+z4EgadsT8L17BXmOsY5Qde163lOs+X0ziuEwFuC6kovrg4gBrLkZbfc1eusLtdYbtcGeFXMqeBVrVWTMdsXPpnN2PqSUEaWRWCKwvkv4//8X+Of20tmpgCmboLJmwwgqnaOjN+K6BGe3G0AscLSyS0wsQ3GC0iMNxKbaDQaxmbzDCCRqTqbcE3N1MNMoZXs8MW/h7Xv2e9e2HStopX9SXFYSY7WyXi1axZPuSSMc8oEeDFaMx1K3/vNauo2teWH9iYRraUYrimLJeK4qlepm9QVjnp5Z110JrgK5z6P73QzkfGtMPjvYfRdBI9UET5ZRHS2hMR0xVUNaRdNFqand6G6oPQ3/952JpIFMYFTJZ4eSOF6LpbsnWnMTVksCaRbn+y5il54ogU4mqXQ5JQ2rzQmCCArT+N78L2EjpQRmakmOlNNcrqE5MwO4nM3EDl6M6HpZqITt8FMswlJcuwGEieauPTgn0LwaaKRDD51c93kG4spulwNPdbviY25c/SaZdqkgZQ8sGXQYrbe0U16msG0gycvGy/pwjedY0pUM2JaA67da3WPrqGF6KfH9jXWKTIO4bDtcaLYTtfn9nF3v2yZvfgZeHKeS/O/juIM5gvIjr4BpnaQnKogOtVEdHIviYm9JCbrSczuID0rEG2HiWKSE7uITzYRnykheiTfaBs8Us3KWBXRiWqYyLe6r8SJ34LlLxKN+FHxT27OSBRw9/cqgJgVcTQSONxw0xHO/njrnTIpuw31IVGJl+PDNRYrOoaI6B7hRXRx1cOKbVGWUlnGAmtzjXCsGCb3kZ64g9hMA7HZSpKzVab9FUO83pE8UmHfEZlrwH/irfDUIeuWKIFywuTRzNMIrqAy559urmLdJFtecJoTTgmC7iORWkcVpbZ4LPUCgX8Z4fuTv8ZLU00Ej1TAfBEcuxlmbyQ5sZ3YaAPp0SY4vMOC+fhiHWcW38aTn/rvEH8SUhHXpdSzwB7ZbNmAkVPVCd61KMMmbaYNZ3Rebuge3TZwcicEGC91vQkLDmy50hmvXkkf3PgSCZRgqHPcy3qmx/Zn37mJxxuAE82SxBKCk1Zpxmzb7PVHOjl/5JdJzVeTmLmR+PxNxOa3E58rJj1db/FndnIvoYVCQovbSR0phekqmKqxuZTkbA2RuQr8i4WsHy/EN1tCbKqSzFgJmdlaLszW4//a39iW1NpuIncbjre6MV19LprwvAJzEV1Bbe7WdZZS+y5oFoCuKI/NeuaaLIgxRBpG6BPh9E+/5S2V1LwnqQvwgzn8RwWQQjIzDTabnJzSsYbUNQAkfrSC8NFSfAsNrJ78JXhyzNYY54TCBEgaT4v/jLEyDXK7LE11BUSbCtxyBLxCeImJAljtuXfR7X+XfpHVJz/J149+mOen9xI6Wgzz2+HYFpjZ7vzqsToYb4DRfDJT+QQWannp1Nt47KE/Bf8/u7XQlkN1gqlr1hANbWwIonxht5+eSz++2qpIGwog7p7sS/RFHr/d/UiQ9D06Ry6Tlh97aJCMXPWfmO0t9xXvEwkyT36OCyc/RPBYI/GFbYSO30R48SaSx7aTnVFscgeM324AWDu5ndhcmQHDgvHpCpIz9YTnalg7kc/ayTz8R4tIzAggFaRmarg4V8rKlz4A4ccM2LonKQ9XO6fr+UlDVBCdHaB067KQOopUr/V3bQCRiJmZ1yo9XaT3i0Z/IVZFbpccQObqYD6P9Gwt8dldJGaqScyWkzxSdtUjfrTMABKY9wDy1Ajax0TXIZJoCByvBZDNbol47ATKASr3Hc790szrZZArkT5D4uzX+N6J/86FiWYS09vJLNxIdnEr6aNlpGeqbGUjM7Wg1YbTVQSPbmflvjqee+B9ZF7+uPWINV7mfkSCugFUWQyXTFBCQWlpCYGbzPQUkWcldK9OezpQXLlx933ufrQOxgmSA5IHEr2pm77qP31BiHD4svsa9d4JvET4iy2sCiAndxJazCO8kGcAYaYURm83gAQWClk/uZXYXCnpmQr0ngDkAFJr1mP9xA6CR4vJHK0iO15OarqSpWNFnP3UO0mc+bR5C8o+ilqiwZWkb26idTNxHUAcPa7oh591+9cOEAt0AsvFCHwAACAASURBVF4a0HNQDSDy9TU7uWTNE/xz1bC4hdTRSuJHaokdKSF2tIjUXBmpo+VXNRJz5Q4gC3WsnnobPHXYNSfecE2c16FGFFcsiLp7iICe9hCFPOHMvZYja+5oK9ekb5JrrtgtcxF8T/PiQ/fgn2qG6ZuIL9xA9MR2YvMVpI7Vw9EaOFoP07eQmakjOPMGIvflc+H0W4g92g8KjqXCcppckm4AcRZDOzA5cAgoEgBPlj1gGBA8cus67R5ymkFKVOd54NHnlbJWulpAM8DbZJpnZtypV/FfQpnAH1hxIFWAHPHBE/dy+fg+Qid3ElwsIbJQQlru50wJjN1mbnZkoYDAyW3E54tMqXCkBFVDJI7WETlWR+B4CYHjRUSPlsJRxSBlpKdKWDtWxEsnbmftu4fdQigVx+aUYY5GdvOeW5h77FVK5EiU+8z/ZoCIE8p7aFLFZ8Q3ThpAVFK2Cl4M4jtWCYs3GCBiR6uIzu0kOpdH4liJA4mA8jpHYq7MCBicr2P91C/C04OWI7/iu3vh0StcLKUynWCIWBuC5Qle7rM5cNhRfXWk7lMh0kG5WW59gf8bo6Rnb4GZm2wSdP3kTgKnikicqAbFXEf2wuxe0keqic38HKkTb8Z/ooLgwx+G4DNYxzNxSmT0LkYa0c055DSj6zbzyuvU5KJLY+r6DPy6fu8ynel00uLcCvUOUBCudkculnHrXTwUXQU0ch+JRuOEoxGi6q6iOjW1Vlp5nNVP/QbLxwsILFYSPVZO5uhOmCmCsVtgcg/RhZ2ET2whPr+T9FGBxAEl7gEkuFBOcLEMeQkGkKkyMlPFBOcKeWmunkuP/A3EvmcWLCfsuv0NgdeDVw97yVkS0cVInruRn3K8RgsizrrOJwnW3Eo7/arlkj2AJNetSZdvvhxOXI+EOjJXRfjYzYTnt5GcLyZ9rPyqRvJYuQeQWnynboOne627R07IjWCeT29CJMmR9XAGJCeTzq/yAGJafJMF0mSe+i0ZktIxsjGf279Cu+I+/0k4/jY4VkDweAHLp3fiv/dm4qdK4KiAcxvZI3tIzZaRnXsTyfl/R+z4Vvwf/yV45iFYWbkCDuOsxF0mxeXvjcE5wc8hVs+lqY3usjLuE3aJuuHceXbzkhH53SmbrwqT0tq8jbkrJSDsZ3+KcPxrXg4EEpYWjWT8ZLNhL610kdS3/orLp+vwHa8nNl8FitNmS2GiCaZ3kVjIJ3piK8mFPNLz+aTnC0nOl5I4Vkd0vp7IQhXRhQrzOCw+mSknO11kivXisUouffJ9cP5+U845gOjWc5jYeJB7IXf0LInTjD9bQfwvAEiALGvE8RkjctpL5lwzkWgfusfvZW2+0gASP1ZOeK6K0PzNhBa2kFhwhBFxXvc4Vk7sSCnh+Wr8p/bC0x1uUcyGL38l4HXC4Pnem+JZ08yirATqp4FEk2WpjCtcTGsWUdYkAr7vwIPvg5O7CJ0sY+X0DgL3XU/slGKtW0hO3E5qtpH4bDGczCMy8/+ROnG9CU30kTY4q/0qvASHSaMuwAuk9VDXJR2UG7lrtDe0TZlK9zyA6PP6jM7JBV5Zl/uXACkolc3JDfUEU4pep1/1nzqze1NNccFO/bb0Q9EAnJth+aFfZvXELgeQI+UwXQGTdTBTRXp+J4njW0kubietGGUhn8R8KbH5GgNIdL6GxLEqMrOVruTkaDnM5BM7utOs0tp9byf5WDdwecPF+tcCxBFKZ2uIaD/97xoBoh/QlHzAupuIEcZMS/OK8VrXHDKA+I5Vw/EbiM9VWpYiOJ9HaH7btQFEBD1SQuRYNcFTzfB0K6TPmxrZUBgeWFyFqjfP8WqAmEBtAoho5lkefY/ejicypHNd9bJpsmqynDxD8rN/Dff/EqHT1ayf2kbw3jcSO7mV+Gw9sfFbSM40EZ0qgvsLWZ/8v0mduhHfXBmB0x+A5z/t9loxRomWHjhela7dDN7cfclF0CdeARAxW7PhueGVWogvSn1LdnNDDpyjyWsLyE8XHUejXN9oS0OnI07m1Jwv+lVWHv5Dlk7tIrpQDrM1lso1kBwpJDOfR1JJjQUHElmU2EIpUVmO+ToDSvJYFdmjFdYBhvlSOLKTxNGdxE+UEzrZSOSrfw7ZM0YH0ws/yYJ4vNywKAYIj9b/+wGiX48Ty4RYT/qNWQbnhJo56JKV+QmR+fYCsZO7SR65gfBMuQVhMd3kwg4SC8XmZsnVev2j1Fyz1Ik6/MdryHzzv9uiJk3+iiAJW5TuzK6yOJbl8LSxCb64bzNfV5ILRj9PCnPCuPlohNbn9GJqDZa/QuJz/5W1kzUkPr6D0OIbCc/dQPZkDSzuIT27l+RcvblWodNvImiZnRpiR29nae79pH74WQhdtM4dmpHOxCOkUgnDhG4jlFaoriDbyZ6oamlgZay9+Sa954ot5ZopFrgyg6wO9loguBJO4Yu7NKeyYQnNxMuGaH/FTMZGNpu1phGvCYrNb+bcVytHcXM1Ya3I04XFniHx/S7OLNYRO14Es41WxY2s6dFtJI9uIXnsJtKLWwwoscWdRI4XE1msMJAkjtWQnquCuTKYK7KJR+YLyS6UkjleRvJEGZfu/RVY/66xIpFME405axzTfSZc4bW9uZmBUj5KUGyY5ddWENdoQUzCiGcS1oI+Z0HEn1AsSkp9YONr8Ogs8ePNJKevJzpTQXxxF4lTNQTnCzyAyM0SQF7vsZjssQoyJ2os+E1/408grd1rnQCr2lMEEjDcDPoVCyJBs4kiESznkohWr9I4r6Cthwu9Zn8qsfA/D49PEPjEW/EvbiN5agepE3nEFgvJnqgnfWS3ASR0Mg/fvVtZO1VOaLEGZitIHLmdcw/8BclnP2kd/qzDeWydYGgdXzyCL6vlrqou04y+A4mu29DjTa/ruQO/nCclTLyOJBbHZAhFde+OJFpfZDeogFrd1JVlzAgkVw8Q0ctau3qxTiBqUmA9gONPHuPsqSZiJ/JhugkmG+FoPtn5LaSOaW7kJjILW8yKRI/nEzpeTOh4KZHFcmQ9MnPlFt9xbAcs7iS7WAiLVbBYAcdvZv30bbD0Vbu7dCpBQp0WBPtEBtWpWkX3qxmoC/4/CRAZCi29EFnECAFTfRuCwSDx8GXX3PnRw8QXmkhMXE9itpTMyWbS9zYRPFpCbKHYAjbFIjKzr+coUDFfSWaxitDJEmJf/U9uua2shGbPdbTyAjkUShp4KterYVRcYieKkhqmXTwUGKmvIOLVdDaQ6PxYABUfJr/631iaqyB5qhTuKyZ8bCeZE5WmBcXs4IlSVk+Vs3KqjpAYfGQrHMnn/HQTa5/9Y/jBGCz/o9sLnCTBDJyNWR5QuUDWSVviN6kYSF0y5CuZPCgF7FkOA0cOIK57pLXv9DS9aVNtkJk8A2vfIqG9XdIqQLxKgIg80jkxZ3k00+JPu6JOKZ3Ui1/k4ifuIHpyB8zsghlNFheY1UgJJPNbPIBsJ7pYSPBEsQ1ZEiVgsnPFsLATjm8nfSKP1PFi0ov1MC93fQvhU03wo4ecxUyGScmdV0ugZBrNwUrvbeZbjqWeuvCsiGmNK2+96tE1WxBrTOilUS2TIqaF427f8PQyxB6Df2kltdBAavx6kmq1eV8z3L+X4NEy4oslJBcLrmqkFmR6nUaJnCok8MhvQ+AJd/+qp/EQq5lm5W9+HCAyyR5IcsccRV9FKD3NvbX5aCDMLMOzR1i7/zfwK7g8WWL3FZ8vILOQj64zdLyW9ZMNrJ1qIHq8DI69CY69gfjCDpYWGrh477sIf+0gXPoyiG4qlMzmaqOyrKvlaTpMUn2e1FZJpR1S3RvaMGdBZEW0j4abuNVOssJTStZUiQVtDbD+T0S+P8xL2l8ktXL1ABHwFJtph9e0RSH4iFoiQG4gS4+z8vl3EjldADPVcHQXmYUiEioxOb7NgMLCNjKLO4ieKDElFzpVQPREAZn5Emc9FreRPbGFxGmXHUwu7IGFBlh8s3khsafnIbPutHJc27ElkTVRvJhbcGhu6Sb+/R8FiMmV/H1ZEYFDWw2oc7hptYtw+eMkv/6nZBY12XM96aN58EADPHALIU0aCiDH869qpBYLYEGFcaXETu1k9TO/CivfdvcvcJg/Yo1trC731QDR5JmbgZX4vwoor3j+E9DiEdw8CpWB+n5A6ls9nJ+/Df9CGdn76okc2UbmxPWkjm8lutBAaGGvAcVcjoU3wOK/IXP852w+QDHM2ifehf/Lf0/iBydh5QnH9HQuThCYZadlOhRnBLxq1Zya1A2LAa73sJ7p7KglGFQ2HHYZvsSj8OQQlz71+zzzwIcgffaaAGLOfjwqBFpdmCJRVQObcQudIfyP/4nwac2GF8HxalKL5cidSp/aTnrxBgwgSvkeLyNwqoTA6R1ET95MZqEA5nfAyTeTPn0Dkfu3E7q3jMTx22H+Fli8kezJKgL/Mux6XqmJtxoWqrIjE7e19IpBJQI5UdBjBxbRUu6F3vnfaUGkJfT9qkpVoy0pMRWvZdVHVcszn2XlsTYCj7wbTpbB9PVkj94I95fDx/cQPVZN4ngpqRMFVzXSx51Pmj1WQvz0Di4++Fay5796RUHYvcv9CFi7HgtkJTWeiyWAKA5xhHMpUWdRRLhXj80AcoDR7UtDxzQ5Jq1+8R9Z+9yHCdx3KzxYR3zuTWRP/QLpk1vMgibmbyG1WEXqxE7Sp64nffrnSJ1+I4lTNxK7txj/6V1cPvGLXLrv9wl/tRWefdAqf4mqe7sAoXuR6GkyUW6jHO1NfN6It5TCzcHFuRpypUg9C+cWWP38B7h8qonAI38AqeevHiD6cbl8aW14rmVVMes8qcXJcnYkC4lv/iXhU+Wkj26HUyU2iRo9XkH6vjxTHizkWWwRO1FJ8HQ5wfvyiNy7jezxnbCoz7yJ5H1vIPjAVgL3VxLVvNP87bBwo8nU0lfarMsMGVUmqLGGytxjqLFXPOEqEF7NSSlKDVeaYkLykzXgtXY1MZ8jnbGsogxHPCIOnQdeIBl8maUXP8sTX/gAlx/aC6eLYe4GMnM/D/fmw8ebiS/UGkASJwq4mmEAOV4Nx4qI33szZ+69lcTL/+BkW0DYAIhm+VUOc6UOX6DQXI3iEEdAN8MqojnC6VUv5bWhbXKkdmARQMICiAJmE9RlePE42X/4ANmPF8Dpf+uAcCKPrCzdXA3MVZJdLCB83434HthC7BPVhE5W2ERj/HQhiVOFRBaKiJ9qJv3J98BjnfDsKbj4bQircYRL2arzoqINSxbqXnVpnjHR01xaN6wgOp0iE3yJ1I8+ZZWwZxabid5fAI99ANJPXj1AFIOpEljzHxpErOOI1uPo+lTgmf3ufoKnakgeeyM8kE/8RD2h4/VkH1CM9iYEEHkAkRNVBE6XE7h/O5F7t5A9ngeL2+D0z5P4+C/g/8QWfA9UEznxKzD/Vpi/CY6Xcf5zH3HN4DLnXZeS/5+99wCvK7vuey+HBexEryQI9jKcrhLLlhRFUYrlOLFjRYmduDyX51jOs2PHzy+2FSdOHMe27Eh2JCeO7TiSZoYVBAESIFhBdICoLGCvYEXH7fee8sv33/scEBwNZ4ag9OaT7MtvcV/ce8655+y9/qvttdfWPimKEmn9TkZCxGrSQC4GvrICFyFI3hUgQc/qgUKNoFZkR/3x3p/5zp6nxFgJEa2nMWkG3g3w+0kPH+Rq62/Q9+bL3Nu7GjQgXyvA+4vl8GYF7H2FzNd2PBNAHGkQOcL/ew3ZXWUMv/4iXN4T2OjGQw8yYZXwJ6n7iOctQEJwSAmGAJEm0bO9Ez0CiNZsG7lu1JBWil2G/t9hatcLUFNBamcpmTdWY8D81XXwlxvwv7aO6d2rGd9bSaz6BSbf2GzylvzqCqguwH9zqZWuezbh7PsY3pGfgP4/hLuHIXnZaESbfBgkmYWKZbbVYMZPs3j3IN5L+vrr3G/+Ja7v/hRX/mIb6Vr11S+aiolzdtJNBFAMoHX00hvTJuImD2pC/aF0mL4vMfn6R0h+dSXUFJHauY2YUnH2VuK/XmCjU1/dgNUgG4jvKie1s8Q45Xy9BH9XLpm9uUxXlzG1dwupNz6K/7W/AV8thTe2cefAL8Jkn82yVgV4E8lThzikJLUDs0qjKWGouZ/3Cg6dG1FKulmPrQ7VQ4V8IR4wyzoVU5ddp/yfADPqGMMWWjgfOMNG2GoBzg0YP0i29xe5Vf0Sk3VFZGqWwe4iUDRj52rYuQHvzZdxRbu24O5eP2ealk9TvRn2V5KQ3d/4y5A6C9nbSqNDm6rIbZVE1eOFzyAnUo8a4j1sTY+GBz2xtUfpfHlbijKNKe6uPsjEYLIbzvxH4oe/l7Fdm4ntrSSzbzXe3rW4O9eTfXMLqV3Pk9i9nWT1RpLVlST3lhDfk0ty7zKy1ctwDuTi1JYQ21/JWPU27u77EMO1f5/Rpp8ideY/wJ3/CeMHIN4N0SsQGzPBEeOiyOSTuZHthZt/SLL9hxmv/zATh17l9u5XuPS1DxNv1sKtertPn32cp/9fnRbyCbIcVJrVztZLYpsgwnAz0T0/QqZ6De6BxWRqVxPbWYH7xhp4vQp2rjf84O7ahLN7A+7uKkPsqsLQ7tW4e1bj7Kkis2cD7s7n8XZugzcrcXa+yoM9Pws3DgfFHMaIE2XKi5NUiXYDYPGt5sBsJFOC0pimM/f+zo8dUYRnBiB62BAkRgJoMY11euxcQdghYg2hNGvX6MjgNQDRhu7tOKd/k9G672GqutyCozoHdufDLgFkA7z5PO7OF3F37kAdM1eAqENjr6/F27ce9pfh7NxItu5HYKIR3CtkmWQKz6h7yRITZVOniYLGasp37qQnfasu0nUFQJXFlDa1/TAJY21w7U94eOQHGa3/AGP7q5jcW0Jq7xq8vZtgz0uw+wXYtwl33xqye8rJ7Com9WYuyTdXkti5koTs75oy4nvLGNtZxv3X13D/jY2M73uFaP3HSDV+H+7Rn8A98StkW36fdMefEe38KhMtX2Hi5K8TO/rPyTZ+GK++Cu9gCfGaNdza9SpXq/8JsbN/CpnLgTnypCd8D58bgOjBh4F7xoQROyjEapK0bvUxtednSO5fS6ZuIdmDhcR2FeMKHPJLJSx3rZ8TJXe9xujuH4aLX7fzX0wHAtEnrXQgSSyFMs2CMIX5Y0E0U3wdKAMB5R1ej4d5jRgN5gTCuQFdaDaZC4ZXDxlCnSHtcRku/1eGD34vt9/YTqx6E44xr4pgT67VIm9uw3vzRZxdz+Ps3mKkhrNnPXOi3RvI7N5GRtJmf4H5reje74NbO8G5Y6I+kvCKqsxokFByCCDmed+hd97tq/BainKmPDzVtVXXCDlmYdZNkre+yoPun+PSgRe5truA2IEiOFQJ+7QKcT18bQN8bRN8XZNfWyxpnuSrG+z3e7fDni2wax3+m3Luy3Dk4O4rxzlQydiu1Yzs38BI/YuMHHmVh0df4cHhrYzUljCxbxmxNyL4e5ea4yd27uBuzQ8ycfr38cds1XSL6Hd70Hf4Xs9rQs1Wg0hzPAKIA7d6mNr706Rq1pOpW0TmUCHx3SV4byg/7dkAkt69g5E9fwuv9z9C9Kzpc5Ut0+/LjEopcBIKRFum26xR8iXcQ0Vg+PnJzxeZYX7zRpe2mmHGHwnBYa4RRnoeuSjupBbxqlTMLbzLf8ndY/+Y4dpXmTrwMun9L+Lu3o6/ewPsLYU95fi7tuLu3kF2z1Yy+zbi7t0wd9oj0+pVUm+sxd+/HKe6kLGd3w1n/hhSDw2zChgCiRk0PUPIwCbi8+SOeU/f6Fq6sCjj4afTpNJZEloKaraukFq5Rfx+Dfd7/jW3Gz/JWN1WsjUVsEtOZoExFYxW3bUZdj0PO1+ANxTnfwG+qkVmz5tiD3x9E7y5DnZXwp4y2FcK1SVk9xeTqCliqjaPsbqlTNTnEDu8AKdxHhyeD/ueg+oiMw5Te/8uifbfgtFmM4v+XqI479oPBiD6TzPzY2/RIA7c7mZq708agGTrlpA5VPw4QHYpJL5hTpTZu5XJ/a8wffJHYVg75Gr9kd3xV0ZVLJMwOLAYkJYL54qCWgUCybsCRAfp+YxtoAtYBycEiMn7MULRLuSxSxxtRXdjxEdVCmIYRvfzoOknuLhnB6N1W3GPvIpb+xLerpfwd76Av3uz6QR37zoy1etIVW80lN0ngKybGwkgNR+0E0v7c0jvX8bIzhdItfwaTN6dCecKJNZJD8KiQce8S9+8K2/Y5w9imhKdXoqEN8GoO8KIM82Yp0rAQmIC4lfg+k7iLf83o9UvMbVzMfHdEZyGlWQO5ZOpKzLmlHyV7M4qk2vkfG0L3td3wNdfwn/dkv5Of3ULib/cQPx/rYc9r8Gul3B2bia+s5LpXcXE9xXg7s+D/dLcq6H6Faj/AWj7DbhVD9mHZng10uqKZ3qpE01HWic91CAS3CbfY7iV6L4fJ1OzCad2BdlDZSR2l+FrScCbmwxPeHvWMRcSH8Xrt/Cw9ruh5/dg+oKZb1AQS+WKNNFqx143Ewh/41dbnjf3+C5MEDGDrPNNjdhAe+hPhbi1LmKmGohmozWfoOWfds2RERfJcXjQSKbvl7hT/z3c2rve2NvZui0QAuTN1/B3voK7ZyvZ6jWkasqJ799gHNTMMwFkI96+l40GcaoXk6pZzET1ZkYbfgLuXLRYN4l0EixKD1e0JeAKo0H0xzO8dLrsN8kVk+ikvpEdPMUUUSbNAiXbl7avJuBBA5z5fxk/9ho39y5j5GABD2vzeLg/l4f78pjYV0S8uoJMzQao3YovU2zvVti7w5AmIOWoOm9ux1M0aOfL8OYOM7ckXyZRXczk3gLGdxUz+vpaxt/4AG79j0L/H8Gdk6AFX1m7F59qQH3zACJPzFaqFytagCThbhPR6h8xAHHrVpE9VE5sT5kJVjwrQLL71pKuX8+DvVtIHFZ29Fdh/ApMJMzWcvIPZT2ofJMBiHwSw7wWIIGcfEcGiFgnRikLIhtINxGeIIIoiaDQWMasGNTKQaVsWDVmBv1hO5z+PA8PfZwHNZuYrN1IbH8Vmeq1ULcdf8/zsOtV/F0fxNnzItmaNaRqy4gfWE+iZiPZ/etxqqvmSBvJ7txKdvc6MvuWkqhZSrxhHXdqvheuttjZKj2AAYPmQSatsDMC4R375T1+6eE7SbxsAleFkM3MvECiPlL8TJVGAuFlR8ok8ZHpxbn9RUZO/xhjJ/8eE43fxcO6l7i/bxOj1WuJ1a3Bb6yE42tIV6/A2bfMkLdvJX51oBkOlMEBTaSthF1L8WqeI1kfYeJohAfHl3P/2HpuH/448bZfhbO74e51u1+3wKx5PUWkg4Vj7/Fh3/Yw48eZb3Rhm4elrBYjiBTRu9dAouYzFiC1BTj1FcT3lpvADLs2wt71+Puq5kTim/SBDUzv20h0/wtwSnuu1MDEPTN3qTuysA3sYIFDKiUYFv35LgqEiPHwTY2lIIw7S2uE6tKGxkIG088Gxyrdu//3SDR8L8NvbuDhntWk6jbi12+GgxvgwEb8vZsMSLzdL+PsfYF0TRWJ2jXEa6sMZfdX4eyvtAB52rZ6vdUee6pI7c0nXrOC9LE13K7+EFzYA9H4jEulaTWl/tkZ1PfQM2/LDo9/aFfraalQnKnsJAnHrs03PyqzypTCCUJd6rZQQWu2lxtAD9z8czj728Ta/hX3Gz7D7eq/yZ3qVxk9sI3pQ+tIHV5Dur6EVF0+yZpckjX5ZA8U49aVwcE1UF2Jt7+CWG0po42rGWnZzlj/p5i69C9JXP0CRLshqRBwIE7VamCVGiSz/BlfhsH0nzFd5BrbyxspqjX892tIHPh+sgc249YWBQApMwAxvocBSGUAkKdrFb1M7Nlorh3bnUviwA4499swNWhuQjETC5AgvPgNAJGn8s5WRMSIEhMKCyWt1UIWHCrXrIJpGVw/Y2qymlTd7Ah+8gZMH+b+wU+QqN1MsuZF0vt34NSsw62pxN+/FqrXQfVGQ17NetyazWRqXiB14HmSB6tIHlqDW7sW74Co6m1bt2atud7bt2vN6j1qN+HUrCVzsIL08RLuHtjCaOMvwd0ztockQJgmyR0eRm+RNqkINrbwLPyh/g75TuVJVWjBqi3lJgWaI5BYxsWzCtrwpz42zGX2c7wNYwNw6yjZ83/B9On/xFjL5xg98c+41/ApHjR8jJGGv8FYwwcZa3iNcVH9Bxk/9D1EG/4xsaM/Q6Ll10gP/BHO1Wq7tcLUdUjIaQ2KgolHdE+iQIOa33+WDtClpJ3N9SQ0fbPxpX7CAuQBXPwTotWfNP4R9atNQCG2rwRqt8C+DbB/PdSshZqqp2/3byaz60VczYMdWkaqeinj1R+Bi182m+RIu92Pxon6Lqr270xmbPqBKS3rEc3Kong3gISdFhhkOkErD2xVjRgJN246wfrwStWYAO8q7tgBJgd/gYn6DWTqCnD2b8WpfhF3/6YAHAJIJdSsgQMVeLUVZGvXk6l5idSBl0geXEvqUBlu7ZoAGCFQHm8Ftnei7G519nrky6TqqsicLOZhXQXjDZ+BK/tgUqvbNGJavz3CpDOM1k+LO73A/Jorj6jrHgHEbjFtfkyTqmLIwC80bWDs6yfDuROda8ZH32mFT3oSErfsjrfRdpg+Qvbqn+Fc+zL+tS/CtS/Atd+Ha79r6eofwd39JgeMBwMwph2SMvam9NshKAJA6Oc0vtKidjZZUcm5v3SuwZveCCkz/l7wXM4wXPg9YjUfNRVdLEAKie8vhroNVoDOAEMgeUravxktmzA+Wl0O1D5H4kAVbudPwugpM5OvqKI2/jGRaPGBOt8YQFlSbuI9AEQjpo40QFJ+ihxxrfO9h8MYWSWhqbNlQ0tAph7AZD0T5/8frh1+nujhlbgHF+PuX4e7bwf+vu341QJJJf6BEqgrwj9YhFe3Gq92A86BHWRrt5M9WIlzsNx+iNxyWgAAIABJREFUXleJ9wRyDqzmSeTWrMZTuLNmrVG1ybqNOKdKGT9cyOjBD+F1fR7GtB2b/CsFGSZJ8ZCoP4JWnRkp9wwcolOtpp2xWiy36QsxvbhnFpMaHAS40TgJINNmpl+bwqiCvNXWnjbpEYWJgEpTl6bJToEzYZfpOqopO4HvTpF1EmZDmWzaMRntM4drvPSjgeYSKFRjK8U0CcZNa1cizg0keszw8ULNFMpbA5jsFTjz6yRrP0hS0bRDFcRri+xc0EFN7lbBgSr82so5ETVKen0Z9m2DmuVwKIfsoVwmG14mPvAbJsUGd1ZIVzyuLcudJI6XfU8r8iNGus0ARPlKIzgMGzLLddQLAocy47Sr6EQP8b7Pc+Poa9xtzCd1eAkcXAZyGvfLnHoeb/8WozG8ukL8Q3kBQKrwajcFtM4C4z0ARBrmSSStRE2ZAWNszwYSBy1Aoo25jNRUMnXkH8GNg5AYMdJEjnMKpSOMkxBoxDx6vmd46XQTCg9MDRPnEEOK9JkJENif0s/ZteTKIrabKkSJMUXMGIBy6xUWNqFJreEIuU9t+F4caC9kri0MKJCmIVKuqOZfdJ7Bls4xzyetoXI/KvIQI8UkCSMs5DPpgnN76dLKhlYxa7PMOdAguj1T8Do5iN/zOdIHXzKpNn5dGfHaAkPGfzqwZk7ACAHFgXVwQDlvyu3Kx9+/FL9+KWM1hYwc/bv4V/8bZIZnKQBFZWM4fswsNdbYvNsrYkSg6SOpW0VfBJAHRnuYkpZCnVFNHkzfhPN/wp2Df4fhA4VkmwvIHsrHqyvGq8vHqy3Fq9mIe2Ajbl0x7sFc/Pp8/EPlJmTJgW1QVwEHpWLLg/dr8A8+mdzaCp5EBiC1miRcS6x6PbH6KtInS4keWcF47UpGa1+CPjltKlOpNAPVhRKDxNEaZpM79W499I7fiwMlOZTNaplY2lYRIpn+0i6PAhzKeQu9dHW4zpVWGwm09YiJss3YR8pk0DWFlpCkyeV5aofXjLaHU4DACxxRa9EZ5jSo1Y3rBFWdUXBC46qJvOngnuzl3wOPPLEHZK4pwqm0DpNmMwMQDy8zZdKO0m0/TKZ+G87+CqgtJXEw35B3sAxqy22gQcGGuVDdWji0CQ5uxtldQWpXHv6hXBIHcxmv28B002fhYYOZ95GNZarSe6rTr37ROAWq9YlPqF1u1aPGvLILi6yJpTmDQLJIa5g9z4fh0k4mjv4YD/dvJ3E4F5oEDqnIdVZLHMpDD+4cKsOpV0ivALe+HP+gkL4NDmyGulI4mA91AUgOVrwjQIxpJvPsbUiShAPrze/L6Y83VBI/WkyscQWx+kVM1FUwffKfw/B+8GQ6iv0yaJcpMYZjp7vfoXve7St1tFIVVSvLmlSKlivmod+ypL4ctyWQjFEVLJZWv2vQXG31NULWH8fxdJ1gIZRSVVRqXNmgIam0p8iohwwyxaQTQs2T9rWKzsNxHLOXeNrXdpcqxyRgKEQvsMjcnLm5Z9KgFiBBxUbFdmcAksVT5GzsKNMnvx+ncaPxQ2Vyi3mTh1aZ3DAOCiASmHMFSAXUr4H6dXj7NpLctcYIaw4Xkj5YxKiiWmd/C8aVOTBNwneY9jX6Fhi++PpdJETESixZw7bOklSmBtYkmylOrm18YsMwXM10288b2z7VsA4aC6FOam0HXs2Lxodw6nNxGueTPTKfbEMe2UOrceu24tdug9qNIMRLatQWQ22eBcrBclxFs55AzsHVPIkETmoEuk1kG9cSP1LK1KE84oeX4xxdQOpIIQ/qP0ri7Bcg8cDIApkk0pMaXLNB57t00DtDRKiQJpBmUB+K9F5kxH3wffDeJNAFzKnTgnXT0jTqcwk0Mbg2qElnYmTMfoCPrqfUEOEqBJ/RFvoj9CNVFE9FGHx5M3ESZvmrZmVmfFOrNnQ74a3q/Dm+LEDSpPwk2cCn0z2ZxVyJh/j3DzF65JM4R6qMteDVFBpwpBpW4R4shEMSls8AEAMwCdtSOLQDr+5F3AProaES6guJ7i8n3vSPyF79Y9zUJZR4orCvFLIBhgSQ1Q5P7IGIzaGRhLOTPDpZp5n13Or41Bjc3k+i++eZOPZxEkd34BxbS7ZhJXHlPx3YbgDi1FXh1OeRPTLPkgBysAq3bpsh/+BajMSQ31BbasBlNIkBSEUAkG9sLTjKA5A83kqrULsODm3AO1ZF8shqJmuKiB/Kh5OL8JpWcL9uPZMdPwsT/Qb1inzLsJEv4D1m2AfqVoB5K5lONGp2piPDQ+wH4jJBT9pEqyHU6u9gSwIdPDv5U1wUAEQ8rbQIs2RZZpmksOeazUMdXwaU9vASqWio/tnx0TjJjDNRGXn8Kd9qGhNREUDSZgY5hK05XvehC+iPbwJALJ95qJBENp0x2knmi5ZQuLHbcGcfIw0fgSMSjJX4e0vJ1JWQqi8kVZ9PtrHImN/+IQuSp20NPx1YhX+gAI6+CMc/aMx7o5GOFuDUrWKiYQuJgZ/FGzthxkQjpa4y5rUZUv1n1wBJAIVkgaP9QdwL4N03kkn9LItapL1nTOdPNOIP/hzRxh1m0so7+SLJk5t5cHIZd48uJN24Gk8MWl+J11CGd7jAkt7rs0PrLdUL1astqUPqywKqwGuowKtfPYe2DBoKoKEEt76KbP0WMod2kG1YT/bYQjInIsRPFDJxXFt3/RkkboIW9gdCdzKrFGhxipg5ULe2v6ykNe8FHKlSda3pUYMfKylDDa3P9b06LaTg+BBJT2hnO/LhIRZ04Y2Eg/Z4oqh+X8eb/3SoOXn2OXYBmO5CNHP8o0NmfWh/8an/12+q+0yKm2z7MaLcI+3fhvR1HrT/LtOHP2yiV1RvsNGmA9vM+ERPFDB9MpdsY4kZd/GG+OBpWuor4FCZvf6hqhleM583LsM9ugSvpYzx4x/GH/oSxIcgOYyTiptKPNFE0G3BpkrihTAlySwBIU3ELJF1Y6YCRMyz4FDI0Umrds8AXPk8tH836YNL4NBiOLKZ5PGtPGjK5cGp5WSOluI3rJk7HV6NP1dqLIYjK/AbC/AaNuIdegHn0Es4DRtxji0ne2IBiWPLiB/fQbrj5+DmPltWx1UMHKKeCg1I6UokBAAJOT/g70c5ajJ1JH5tp4aHGSZ9as76DjlBYAtki8cUSYZJowW3Kit0nJHWf0288RU4pIRJpZVshwPbcQ5vYPJUIZPNeZZ/5jj+NJRDQymmrV+L3yBSmk4x/tHleMeW4p0sJN30Aqn2H4crfwqxQcjGSacgqjVVZjwVvbVmaTj/p4CKQBIxYy7fL6mCW5YFHH8YEtUw/pskWz9K9nAZ1ETMRIx1qDYYcyZ1fA1O4zOAQw9jOqcc//AcSB0RAqR+qwWIwCGt1liKc6SYeH0BiRObud/wYaZO/yKkZGrFSCWSJnPK5mfJeQ0UxGMiV3+IA2ymqhWXdnLNdux3CKPP9TFkqpj6COqTSZL+/UCI3CF2/Q8Ybf00ySNbLUBq1oGobi1OYznRk8VMNRWSlYCdy9gfLofDxXA4DznlHLIpTv7hUrwjefhH8gwPZA9vxm1+jQdHNnO/9R+Zbau1dimbcEwdcw28xlK+t5YxK/iufwqLi8x6EBN5kWUQ6uJUL/7Ir+Fe/hST9ZW4tQVQuxRqta5Ys+Mb4dB6aNxgESsmD5n9ads5do7pVAOQPPzGQryGDTgNmw1gDUAa1uEcXke8roTEkUruH67iYcvfgzt/AdnL4GgpsawMJRfK1LKZy+E8hkWMNIY0jAASgkQdJdH51y8xlqpqJh2bnJlOaxJTxfmGGOn/UUabt5I5oiiTQvqiUuM8e0cKiZ8oJnailOyROQjGkGdkQTSugsY8oz28hnV4jeV44gsB5fBa3MPbcI5v537jSm4c3Ub6whdtpRhV59dgy4IOMtY1stYHF1gUrPKIRLlPQkvtLYxAD/mwlvTQDzPduo2E0tYP7oD656FuG+zfDvuVyr4eDlaCNMiRCvy5tjr3SNmcicYyOFKCf6QE92gJ7pE1uI3r8Ru24TdsIXmwlOThIlKtFUy2v8h474/C2C6zTUJoVdn5ChsMmq1AbM0s63Q+8s6kUWRu6ci/2kDRVECcaSY91X1Ut2gtfBRGD/Kg5UNMnVqFe7QIDhdBQyE05MORlfjHckkfLzOJpe4zjL/GnSOFcCQXjq3AP1qIf3ijGXsatsDh9XBsDenGQmInyhk9uZV77Z+G+18CX0JSmylZB01NCBALEssPkYdcYJrbJlpialqNNeFc+vdEOz7CZGMp2cMb4ejLcOQDcPAFqN0OhzbbUJom/BpD5g4Z/Wnb8Py5tBVwuMoA1D2+EufECpxjZThH1hvJIYBogU5aczany0h2r+P28RdJX/lVu5FmQuvtbUc8Aomteh7+bftPjrK80TCEIa2iCNU3IV/821gRaeJ1iklGmcTsMSQOmxyAi/+esRNVJE8shKO50JgPjSuNv2gY+ViuHaejFbhH5zLu4TkCSBEcXYl/IgfxgNu4EbfhRfz6HdCwEY7bbA+/ZS2pjm3cPL6O6NA/hWSdWQVrXIxZ4XaBwwQFA20SGeE8ca7hch9nopn4lV9lsvtjTDVVkjieS+p4Hl5TKeljVcTq15I6vBZOrYNTRbhHlsOxYjhaCkfL59jq3DnSkUo4vBWOrMM7uRS3aRHuiSLco2vxjmyynzeU4B/Nh5Z8Uq0FPDhRznjH98L1P4eoainZ2sICgt3yTHudaDsHK1FCoEhaKnxpTS2p578GiGbRJ5hmTCaqOEuK9eGfE2/7hNEQcpQ5mmfp+HI4sRKOFbwNz8xx/MV75nqr8E6swj1RgHusEq9RAvwFOLwJGpfhH1sEp8rJNK/l4ckiRjtewb/xKyYbnawmZAMtEqxAFEBCikS5RUZrE9whssP/i8nuTzF2tJh4YwE0lxA/lkPs5BLGGldy9+AqJo8V4Xeuga5csicW4R2f9cAhWN5rO1dghOeFAGncYDuoaRFOkzRJEd7R1SBqLIKThWQOLyJ+dAmp1jU8PPYSMc2NxNpmOkeTXjaLQLPOsRl1GwJFALKhP4FExQCCGXGZpn9FX7LTJ0iaYnFW7I7BvX/DpMyeYyU2BG8kfAHeiZW4J1fhHRMYVsORUjgSCte5AqQIjq2C46vwjhfhHi+1dGw13pEN0LgWrYOnKRfv6ApSR1eRbClnpKmKye6PwvgfgDKOBRAZA8EiwVCLCCSRTDZqioulbuxntOVzJJtfhpMlODUqCFBEtG4BY4efY+T4Ukab8phoKSTenofTtRg6l+E15eKfKMY/XvK2LSdKzfXettV3z0LHK+HIFji6BY5X4jcV4LUuNERTnr22BuJoARxfin8yl8zJKmInX2Sy6XsYPqnatNfMwiY/JSfclkBS/ELLUdVRIoHEmlryOYI5Eb0VfYcDJJlM4rrGw5gRA0plUbE59Uk438h0FG7W4PR+F7GGCN6BFXB0HWgW/dhqOzanivCPr4Nj66zFIRAdfxYeKIETeXCyAP9EFd7JKmPteKfyMON/UsK7HATKk0vh1EqyJzcRP7WFyY4S7rV/GGInbE2xVAIv7ZqJWo23lOG0r1ysWILszS7GOn6V0caPkT2sybw8qF8LTdugZQ20l5LtLCPRUUa8o5hE6yrSzYtwTi0OAFJowXHiG1uBjZOS4m/X6rOA3glIOubtvj8hLbEBjm6CYxvwmkpw2ubjtEfwmxcbyYGcRCPFVhnV7h3bSPbEVuLN6xhp+Qjc/e8Q7wHtXJuJ4SY8m2wYzLiGGkSmlmETASLAyaPZtxne+Y57k1UF+VkvgSOVSpHJZMxkm9GsWpE60YV76TdJd1bhHo9Ag6JLSknaEoxNqVmK4J3YYAEipj1WBCeeYfwNXxSYa4QA0XIHp2UlfstCaM6xADy22gLpRAH+8U2kT1UR75rHWOdquP3FIMviAXhR9LwSjgKIwB9h/C7x7v/O2PHvMrOOnFA4Ls+mghypgJPr4dQGaN0E7evw2yugvQRayuCUkFlkpIPfNJdW54RUErx/760BzbEqK6mOS3qU4LTm4LRF8Noi0LwQjss5FEgqbMqDgHSykmzLSqbaS7nb8Qmc2/8Zkn2QiJuisr7WUwWJd9bcUgasXU6qyKARnValfMdrkFnYMFojnU4jraLWJHuqH5K38O/9IdG+v028qQhOSVrLzKqAxu2g9KSmSpymciPlpe2NVDcAeYbxF0CkgY6X4mvsT5WSPbXaZJmLB/zWCDTJTy4H45NughOr8ZpXku6MMNWZS7Tvx+HO18HrM9u5+dkJ4umMqYov6yHC6HmiLb/JyPHV0LMYWjT5kgtHFkDjAlAlioPFpOvLSB8pIXN8hbH3OVYGRyugqdR2hjpkTlQMp+ZI+u3ja+DYWjhRgd9cjNu6Cqd9MW5HBNrmQdMSOFYIjZq3kaapNOrXb1tAqnMxd04UMNb1d+HG/4DoDSs2BBAzy6p1G9q9V6T3wfJSM2nyV8PECgGi7dlkakmDhCaWieIlJ01KefLSZxlrryB6LA9OFUCr+KECjm6DYy/gN63DbS6DpjI4KbOq2FLTHMdePKPxP1Fh6VQxbnMxmZZSMq35OO0L8NvnQctiOKmMi+ct6bdbF+F2Rkh0LmOi9WOkz/0bmHzd1ghQqkx6ykasDUCifcT6/h13W9cy0TmPZPNyaFkCp8VgEWhZhH8qzyDUbcrHPbUQ9+RCM/egORBOlUFLwZOpOR/eieYEqgCM6tzjZdb8kt3ZnIfTIhVbGHRQBP/UAjiuUKMiGpIgCj4shrbncDqeI9a8gPGmtaS7fgzu7oLkHe1nYBas+07UOO42/UCTR3Yy0ZhYf0V8kLCwtVqB5LGXKqmPt8Dl32SyZzvjrYtJyKIwTFgIHRqbdXBiI37TGiPANEacWgUnCi3jPuv4Gx9WwKvAbS4l07aCdMcy0vKTW/OgdbH9vaObQdSkiOYi/LbnSLevINYmf+Rv41xWTed9wEV8Z8xsnaDxjpC+Cnd3M33lJ5m88Alig99Dov9lol1FjJzIIdO5AbdtB27LDvzW9fgdi6H9OWjRepBiKykkLZ5E7wQefddcNHc6Jd9GpOvkGpC6LavJtpbjti/Ha8+xdujJXDhaaemkgCSALIT2+dC6ALelkHTLh/H6fgZG3gDnnNlsJjl536TFS3M8CveGVpU+lX0upHznvkKN8VZH3Txx5oZZJ+/2fpqp9nyi7QtJN5eQPVlmwdBRbiKhSHM0yyzPh9YlVgCfyoemkrmPvfjmlPwXgbAcmlbjtZSQ6VxKunM5mbYysq1l0Cq+yIWT5ZbEJ61LoXUlbls+XncZE80bmOz6Xrj/e+B2KlZt19QYJ13FAlLjuNNncSaPQ3QPzv0vMXH+3zLe86+Y6vgcsbafJtn8z0m3fJxM1woy3REyHRGy0jDtK6BVKvUJpE55Ij0jQKSZZO/KzhRYTpXjtpTbzmkrwW0rwD+10n5/cjmcXAUGIOqkJQFp0EqMepY0yV74LEx+GZIDZKeUOvFoD0aBRGkpZnvrmXV8Asp37is0q6RBwpc+m5qaInG/iWj3D+C0VxqJnWpbbswbmTlO8xoj0WlbDm3q65XQovcSSvOtQNOYPZOAVPBGjC8AFuC15ZLpyCfZWUC6XQCRv1EZgFPAXGjvwQjmcgMoTq8g1Z7PWPsHmTr3L2F8f1CIW7V9IaI1I1pPnFbRQVMoSTVWr4FzEbyLMNIM9w7BzTfg8m+RufgPiJ17kYnezYx3bCTd+jJOy6s4LS/itm7DbduI37YaX458Rz62g4TYgNRJLeqs3MD0eitIZLIV4bWtxGtbjteabx7EPuhqa8pJKrQKeJIOS+CUACJptBq3tYxsW4mRHnrvyR4WSKQ1TikmLpNPYNY9rIQuResK8ZoWku5YQqy3itjQ98OD/2krhodhLNXaDXK3lOCoORNVC58Jos947gJMSKEdFrLWW9vw+0fM99YjvvFvHTv7+sERb7F+vvG8Wcfp2JCMFgwnPYPU/mBdhCZHwyW11gOTxozhJm8yMdzC5MUv8PDoFtzWZdBZQKYtj3RrLm5HCdmWSpInCvDalwSaejm0CiALLZnx19iHJLBIy4iK8FpFBUbKu225hvnFC9ac17EKEgXgMD7PcmM1CCDpjiIyhgfK8Zqr7LHmd2X5iBdK4FQVXrP4NA+vp5ypzud50PV9pG79PtBrsibcdErp7rM6y3SyOkFBrqQtja9dUc1S0HG0nx3eADgdkGmD1Ammu3+HVOevkez4HIn2Hyba/kmibS8Saysn0bYMvzcHTs+DLmkbRZbmwcn5cCwHjkj654LUrbRBSwlKCXAUVj49n2xPhGRbDpm2cpyWl8k0bSPVtIx0i663AnpLwNiZYvhi/NZSQ15bMV6bfe+3hWZgqOH0d/CZAhIKNhzXdZZC53y8vgWk+0pJnP4E453K/r0KsYytjKCZI8OeWr6kPKQkqewkjjONp6WyBjBxfD+K40Uxc0yGmR9lAAdsOhMrDhfoaKJy9lA89kf4hTHnwvFREFKMHVxKuAmPe1Ib4nF2kCGtPdqDfdqVm5SeJp0cIZoeYcofNxOBYyZbz8wMmN3DmK4hdeHfMNr0UTJtimzm4bcJDCEVojHw2wrx21fhy8poywtoFbSJgvFoXmV8RxMRba7Ab60w45/pLCTVvYrk6aUkexaTOr2ITPdSnI5VZmy9lg34LeusCdW2xJjTbscSAxIDKAnW1gBIBnShQC2E5lJoroDmdbintnGvbjX3jlYy2vMhRs78E+LDvwsZ1TEYeRuAPKFzTeKjQp8qjZX2SKdc/MQUZJWuMQSJdhivgTtfxr/6a2Qv/ATZc/+QB03PM9a0jqlTFSSay0g3y4kuNSFlMTRdq/E6y030IXGqmERTKanWPLI9C/AGFpLpWoXftQE6PoDb+hLptkJSbYtwupbC6VVmYASCuRD6fWO/llrV27nQBid6l+L2rCfd9Sm48QV4cBQS9yFjCiqZ6Q8rQlwyaKGQdiHRbubSKAk8L2FLkqrqvUkPDpg3QIedtbf1qbRG3G4oGWiRsP9DZp7dmu/0gUAi1faWRV76Ssc8FkV4y0rJ8HohSJJBKSEJQbN92SiOPxqUBkrywFHdSNcsozXrPKL7cK/8IomeD5HUOLYXBmNQ8NStAY20T+uKwDKwgi3bUUyqq4Dk6RUGHMmeBaR6FpDpXozTucIAT/NzApPAkO1YOousJnHb5WMoB68YTpdCt3itFDpk2ZSYuT3a1kLXazjN20l2ljPds5oH3duZOP9ZmPg6+L08vj/II/H2De9kXphCG9peN+uS0QaJaS3JUpEBbUg/aXdl1TpqLdNNaOuvq7ao2d1quPUVvKufJzX0fxEd/D7G+j7CWM8Oome2MN27jrG29Yw2lTHZstSEX+nLh4FKaFday0Y4vRm6NuO0bTKZuYnOJWROL8KXGddeNDdqk6ottoMjqdaeCx1F0FmB172WdO9Wov0fxLn+4zD9v8A7axfOyMIxeTvSIirZM2FaUw5ADKjvQ69erfg5OEcdqzRqFQ5QqoYFR3hAwMxvZeKQmdXqOuHfBhCBRjG5YdIooU04u9Uxb0M6X1pR92h8qmEy3CLBXVOlS1eQTDC/qe2nJ0+QvfILTHa/xlR7LunORfid6rP8OZLOlXmWAxJOXTn4nctxO3NxO/Mtda00n9G5HDpWgpjemNgy11YabZPqqCDVWUqqU8DKM0I1073MaJx01xIe0VLrQ3etItOVZzQe/VXQVwI9EdLdEaY7lzLR/Tzu5Z+H+J+/O0AEjJBCgGgPakfFBVzHbHWVcFLGoTECVuMQMofpYY2N6uA8hPQgJI5A9HX86S/jTf4W0Zs/TvTqP2bq/A8x2fdJpk9vJdFdQbZD4FhrHT1FyLoK8bvKcNu3km7fQrxbEmaZ6UTaCwOAzKHVtY26z8NeZzV0VOJ1VZDpLWaqbwWT59YRv/YDMPoFSPWCmEUZJ1qVSNqYIZOoBI9vhIhhKPVByKN6L0YTQwZvw69kYs0s6Q21TQgQtSEYZrch0+ozk1EcACNYjz5jIpu5YJliYUJIYDrPmNCPcmm0Pj/JQ6a4yzSjpsCBWQKh8Uw8hFvVpPp/gWjnh4h2FpLuysE5LYZeOUdw5Btw6Xy/axm+wBEAxABOQk8CrK3IRkhbQodeJpL8xxzr/LeXmCCB07Eap6MCp7MEp6sQpyufbHcusZYc4go/ty0h2b6UlELAinLJMjGgWwYdEdxmmfMR3IEI8Z4iJrv+Jt7Fn353gMzUGnjrxlOqwOFbASTrW6TiZSFpd1UzZZ/FgEemmeeEeymo5pO83jH8dDskD8LUXnjwP+Dar+Ke/Qzprg+Sbi0j0zwfpyVCtjWC07aEbMdqMt2bSfZUkTxdjttVbBxEOiX5C3jqVuAyWiiUgrpeMV5XAU7PCtKDOUwN5jAyWMjEhe8iO/xvYbIBEhNGEIj39cyBR2Aqk5jl66GgCJk5ZPqA58OPH/Mhws42TC/zaRbjP/Ze380qHxSCT79hflzw0x3J5HvkG1ng6MZ0QmCO6TIKZHqPjtaZGipzmPacvPtnuAN/n2RrCamWZZaxThfA6aDPu/JgDmT6uLsUp6sct7PcmNq0r4Y2BWPWQnOQOd6kQMoaE8o1Gl9zKc2Knsq3CfwZ+Zptpfbc1rXQKv8kIJlSum57CX5HIZ78mI4VZsrCO6G5sgiJpgjxtgjZMxGifUsZ73wJZ+gH3h0g0haimbELNEooCbWb6Zg/kwQeBD89s/zd1uNQ7SbPTN0nHEhqP/UEJGKgTUgd1XkyVUDugXcJEi0w8jrc/E9w9V8YU8fpXkCyPUKiPUK6vYRM90bSfevJ9K3F7Q6BIXA8JWlQu1daEsA6iq0W6cjF61xKtlt+0HxSg88xPfgco70FjPZ+F6kLKox9GOIjNgYc+g1GSfhknCzxRIppVZcPlnTObi13iptnuQvSBobpW/u1AAAgAElEQVTBw0iSmFwSX+wqCqW/PhdApHmCc2bODZjecLaAIAqON5GpxwMBOl3Va6TgtUZf1T5mLC79XvYc2cu/Ded/EPrXQvcC6BDlQFe+te3nAIwQTJ7ModMFZE4X48gX7VDe3xpoXWNzAAWQpg3QpOUVa6BZ5rAm/wSMFdAus2uJpfaV0C5zW2NYZq/TVgkdG6FjA7Svx2+rxGkuI3WqhGRTEfGTinZuxu3cQra3nNRgKfGBKsb7XyN16Sdg/D+/O0A0UaS4dzijOns2VR0cDqM6Vqu8tVN2nAfEuE2Cm6S4Tdps7jhhlLhklzHZxAeu3Wdc+1QYZ1bF0hRvFnomJmCyBy7+PAy9QmZgAfFuAaSMbNdG3L5S/L58/O58mCudXgH986FP6l3Om6RMkYm6eJ0RXEXe+nLw+paT6VtJ7HQhk53rifV+DIZ+Dq5+Be6dhrG7kBizRd/MRpEJprwkDzOquWs1jPJ6JArUZ9Zx12KtoPxpaD4ZgIQH6Q91jCgAkzk3+D441jr5ykLW/Iwt56/fMBQIs3AjJNO+xWrzFVTw0wYoRvkId6lpstNv4D78Wcb7N+D0F0LfGji9Gjplii4BZXP3LA8ETC50Pz35PcvIDkQMub0r8but9raCShpB0UUBpgI6ZGYvg57n8PsieL05NkLasxB65sPpoO3VeNoxpW8x9OVCfwl+/zr8/m3Q9xp+/3dB/8dxej8DF34Xd+jLcPO/woMvkb31X0nf/EtTYhfn3nsHSAgSI/Vm/acCcyILHMFFal2p45pPuYNnViuqHcFjHOkWVQT0Xc9YWcbq0vyC4QchJli4p+IYIknqG79AamgLsf4ckt0FuKfL8HuKoEca4OkHJjxHA8Tgc/j98w3QvM5S/I4AIB3zcZXL02s1TLYzD6e7FG9gLe7AJjI9zxNt+YTdj+LqmzB2DNyztqIHWnSl1XYm99HssiugCCTCgl0LHdQoDRjdcrTtWBvynV3uZ5Yror4K+svCR9saq2qkStbY2YoQVo8BIzxvFkCM/2PGSoWwo5CagOlrZO/tYfziP+Nezxrigwtx+iK2n00EqBDkd3QrfC9aMecx8HtW4PblkO1fhNe7BL9nCfSE11WrlKcV+KdzcXsKSfWWEOtbw1R/FRP9m5ns20ayZysp0entJHu2E+/ZQaz3RaZ7X2Gq50Okzv0d0kM/gHv5x+DmL8Dd34SRL8DEV2ByP4xfIHvnEkQvgn/Njp+CTupETRTO4vU5vBUyZMTOIv09Q2FUJTQVQps4XLoqyRdIOyP9BLBAaEolhYffbyZ55WeZPqsiYItwJSVkTyoPTCZWz6q5Ue9y/L7F+P05RlPQuxxkW0ubGCqC7lXQLSCWQPdq6KrE75FEkgRbSeJUFdnOT8LQ5+D+VyDeaje1N7UxrPYI/TOjZV3XhMiduEs2ljUVFNPOFBlPJULF6KpwKVJwVaVoRCqXak2gpI8xV5Ne0JpAlN0YT6asjpMuMUVrfG2HbPfsMAWmFa71M2Qczd/ESKfDQndX7bzWw68Qv/gjTPR+gMmuzcS7V5s5oWz/KpyBHDzzzHm2j06vhNPqrzn2vcasu5xsy3YTmfT7lsPZCJyP4A3KUY4w2RkhdSFC8sJSYhe3Ebv4aaYv/Sumr/4Hpm7+B6K3fpvYtf9C4voXyd7+U3iwEyZk+nZCesguqXVGzF4hpjq+CnVoBaFK+GjORwWFJbFMirYV7D7jQSEP64c9I0AEs3BCUVPy+kFbKcIgcLbpICfG2MQCi25GIAm26TXhTlUWETPYpEBpFqPydfhkGu/OHuKX/qlxmJNKpOyQk7jeDpak/BzJ712FGRxjaklNSzqWQKfs10roEkgEkIKABMjlMBCx1CtToxS371WcMz+Ie+XX4OHXINkO/k18Rs0KxaSXJOlmTd1ps/4o0BxZL0nW1NC1GyGEhctsETNVXFHFS81oPwqKGbAEGkmgC0ldpe8eeR2BSacKHdkkmeQkWWkJV7pNY3AP6IP4Trw7nyd1/h+QHqjC61sJfUUwUIHTU066v4jk2RxSZxeSHViO17fKAuNZwBEAhK4PQOfL+D0FeAPzcM5FSJ2PED0zj9GBFSRvvED85qeJ3/4lUvf/B9mxo/iJPvDOABfsgjd3GNwR+1wh0wcaYCaiqh0lAtktv8vUT9beQmHcyFS/j5tKxyr7E/Zx5Bsmld46yfSOf+suQi9Erf7WyIcOp1UP8jmkKozvEah4fWTUh0BkTpF5oOrrsrJkuz8we1joigZX02M4t/6EyfNVTPVG8HsXwflSAwwx+JxI4JA2kLlm7NWF0KsJSGmRSujURFJpICVzQJqrV8eEtNisrNQMb6p7Gan+IjLnN+Fc+wT+7Z/CHf7PkD4JqSugOSP5zDJJg6Wd5tlCFaruMCnlvgmfy9FPOtrfS7P2tuC2ClUn3/Jv0plmyomZIngJ3xZTNf2tPhUJWWHgylTxiEL6ISRuQ6KD2J3PE7v+A8TOvkqmrwp61tgMhe4VZl5C/ldqYBWxMwXEzq4ieXYx2QEJBYEkz7TSpHMhc43+EhhcA4MbcPrKiPYuY2KwgOjlV0ne+imI1sPEdZiSbyrhK6tDGla1q4JAhfrQc021+2wmTiodJZGeJpqaCjYLst0gDn0raQysHBf/2cqKj8xVlR41vRj25tO2spPtTHCYKhEqDdMGdm94E2pnkwFJeEJQh0gAiZJkmltEGTaAMbeoJxs5TfL6DzN1tojU4AI4vwA0WP3LoF8O91O2koS9hdBTDL35oL/NZ7n2MzMLq+/0uX7nORiYB/0LoHeFOTbVtYBk7zwy/RGcs/Pwzi3COZtHZnAj8b6Pw93fgIf/G6ZaIH0zcOS1eUvW1OD1ZDNJBejBxcxhZwVDoWohUspWfEibqD69FnBpjYpMMn1jB9lEGnWNUEmbCIFCh5q3eQDuZUi2wsguYtf+iPGhX+Th4HczMbiGeO9yXK0HklaQ+dS1yKTe+P0ryAzkkzhTSvxsMalzS3DOLLL9HfbXXNv+JXjdETi3DC5WkT2zgdHTVYye+QjZe78M6Xq7kWKgIhXpVoFvdVnMc4m5jonAKZ9Q2M9mfLPSMZNNkHaiyHQN657ZfrLWibpodldbGaUIn0o8CYA2amgrKz4DQGzKxONMbwAgtRXSrJvRoiO7tkKFEe6ZTTWN3hNIBKYA4eoPYVll/RNmB4yslYKxEbMpZOrazzBxMY/xM2LK56B/SQCOubSLoE+OpsKYMtnKLEgGnoPBSHBtgUHREIFQQFF0ZAX+wDK8C4twLi4ge24h7uCSQJLmQW8xfs8asn1byJ79CM7lz+Ld/XUY/7pNy3HugqJ2GqnZYi3U7eFnihQnbAVDL+0bU0m5X9o2IasJSwFJnR5eR+CwHWjb2ChM9cCD1+H2b5C69hmmL36IyaF1TA+VkDxbQuZMAU7vIrPKLq3VmFps1rsAzhZBr8zHMpz+YgMUZyAXd2AZDEg4LXjUP6Zv1D9PQQOLyZ6O4A5GyAxFSFwoIXrxk2Tu/DokjoP/wFTz1opeJ4UpF6qa0Yp6ahMgU+ZUyHgrxxsmnFENto8MCtRZYehbroFsrVC6BBZN+L2ZdFXp0W8FQGZpCv1+KOGsWpR61IYuD5BDZMwsHSB//y1jLR4xm904U2aDeFIqqHoPRvYyeePT3DuziszZlTCwdI60BAYWghzEnnLoqYRe2d5LrcMop3FwCd5gLt5AkSEGVsLgUhhcjndmCdmhRTiXFsOlfLhQCufLYKDISGLNEDunl5DoXs5EVyljp19kcvAfkrr6y3D/yza12u8B9xw4lyGj4toPQflRiRTE3EfgERNkpU60h7N8Ny17jEImjukXTS5pdZ9209I+h8mzkFQm9p/DzX9n0vhj/a8x1VNMtH8B6XMRGFK4VH2QB2dXwJnnyPZFSPdE8Pol2eXbCSRltu0rAFH/SnMsZ2z/mD5RvzwtDS6BcxHivRHGTkeIDr0AD38dsifBVdjcagWlnaeUca6ijYGbq02BTJhTfaF+MTRr7/JQwDwGFplockQUPAoA8tj3gVkq4ATHRd5G/s9i7/DsJ7UhGnU3eh8au0Jq8LL6y3L/W9+H0k+XD7SIjb9oNyYb01fJRy+TxpeZoH23tVdf7AqJe/uYvvxLJBXbVkfPhfqXW80gp3Qgx4R8zaCfmR8AYyXeQB7uQBHuQImlwQLcMyvxzi7EPbuQZJ9MkGI4VwEXVsOFcjhTjNujXKXlMFiC119CuqeIeHehSWNI9pfinFtL8uJ2Jm/8LcZv/xDT93+S9Oj/B9NfhMROSJ+ATD8412xCaHYEU9hPrcwlkXcrAFcbJPeTnfxjEg9+hanhzzJ57buZurKVyaFyEufzyJ5bhX9mFQzkQ48icuUm58wsk+4shDOFcGkV/pUcspeso5wxgQgFLpbbYEWnzivARPsG50PQTwwoaDEHOpODfz5CvC+HidOvkLn4CzDRaKteah2OapYZ5ah6AFpeoK0lFPtXHyjJUoEGmUWWFMOTESVBrKkEV6onVABv5T39Lf4LNUjY6jOT8mN5O9Aguo2QW5+21U1Ir4tC2M4Cy+z8ovAm1M7GXPi5btpcR4FRXctmz5pGE4jZuO21dJLM5D0y9w8x1vd9JAfXkRkswT2z3A7aGZlHOVYTDIpJl+KdEc0C0oDMseXQK6koiRh5pDXOKtS43IJDgAgoa9o88zvuufkGIJwXcFS1cRVRrSfpzCGl+ZUzBTBURqYnD29A70vgSjFcWW4kt8yK6b4Ik5dzGL2Sz/iVtUxce4mpqx8nevUHiV/5KWKXfxnvzn/Bu/0l3Nt/gnvrT8ne/jMyt//MhDWzw3/M9LXfYPL6zzNx7UcYu/JJRi5t4eHFlYwMqdxAhNGBCNGBiIkOcUFh1FwYkLbcAF3roXuNiQhmOpeQ6FtI9sIS3GuL8a9H4FLE9ouWLGi+qUuRw1zokwZdaISE6degj42Qmq3N1e/qx8GVVgsP6rdX2n7vk+ZaTrwvzwQI0hc/B7e/DmMXIWHNJpM5bgAi01xb1N0K9pdX1oXdnFOTnOH+KWFrLRWBJvSPQ/4OzKgQLGL1t5LhQZkzOkfFq81LR+k1l1bnhNz+1l8L7CZdOryp2a0On/23uQd7YzN3Hn4fPokBXPgAw8Qe/jfunP8h7g++SOJSMdmhYGCv5sKFIvzBfOM0Z8+tIHt+Kd65pXBGJlng0A/KtJBJtQDOzTetf24R/tml+GeXPUbezN9Lsccstt+fWYEvmvl+1nmPfW7Ps781D//8PJyh+WSHFpAdWkxmaBmZ83lkzhaTOVNBZnAdqcGNpAY3kxrcSmpgu6HkYNhuJXlmM/Gz60meW0PyfCmpoVVkhhaTvTCf7IUIzoUI3lDESGr7fIvs8+q5B6VRVoHpg2Wmb7xzi3HOL8I7vwDf9IeOXwyDmlQNyPTXYnO8NJP61j+72PbhwCIQnVEfLsYZWk7qfB6pc6U4Z8vgrLSVwsjSTCXcaf0oYxd/Bab2WG2onXy1D6MsoWCLd+tiaApAQQlpEjnRllcfTarKyVbQSK2lGR6a4WvDYI/+C3krbB99M4OcZ5wHeeyK78Mfk2TSzTy8818YufpZoldfJHrWJpxxYQWcL8Y7U0j2bKFhnNTQMpzzGkgNYuC3nBWTv090TqCcZ+xw2eJzITGxf07MPFeyjDyXPpDAyJ7LI3s23wgII2gGF4EijGd1P4vInFtC4twK4mfzyZ4rsZpUWqx/vqm1Nn7mXzI9/HVIdmH3qlG6keVPhaslLi1ANBckTaKoXbBNYCBfv5WM920OEEmSGzjJg2Qe/g7pW59lerCS6e75NtJyvgD3bBHOuRLSQ/lkLyzHHVpow8NnckB0LgfOv1+ke3nOzB7PrdW5CnfrOnOlZ3j2czJp7YSiWbszKA2x/LE+VUg4O5hDdnAhvo6/WAgX8412muqvxB/5HfyYIlZK9VAoOmXTxGUkBJFNa5/IDxE47D6Nssol+L/Vr29zgMjXUSRMdmsjjH2BzOVPm5VhSUWmhlbinCsykit7vojs0ErcC2IoSevn4OxCOCfGegYmeaZz9du6HzH6XCiYC5ozOJ7x2c/Jj5A2CEAyWIF7Lh/3/DLcoRz8oQX4Z+bBWaslvbPPkT6zgtT5CjJXXiB54zPgVQPnbA6UP24mVJ1k1gaRAh9aGiPc0MZuSRGA4/8HhHybA0TLSpQHFofMXRvWfPgfyVz4W8QHC3AuLsW5UIBzvtSQO7QKLs7DOqvz4Px8OL8ILryPJI32rHRhIcyZnuHZBUwBQNGsc4vh/AqcoWIyFwpxLy6Ciza3yrSXrB80PbiUiaEPkb3972HyEDAUVBEZA2cSJxkjGU+YZd2O6xt/QuB45HAHfu3b+g3ffH3ybQ0Q9VEyyBq3AbQHkKiD4Z8mfqGM9JX5ZC6uMoMmkLhDeXbQNHBy5gUQMef7CpBFAUDm2M4ZGCGongEgQ4H/pPki9eeF+TgXVpG5mGcBoiiY+vpqBK5F8C+tJHbhg8Su/zKMd9mJUi3ZVl6eF8XNREmnEqb2bzqbQbvnWsfbAsR6JIFtFcaDvsVa5NseIJkw3V7uiJYxpgfgweeJXqkgcT1C5tJynKFC3POleOdnA2TeI8n9zEwWMtvTtrOYc2ixBerTtu/bvetZA2AYcFgweJciuJfmmwwDo60FjqsREzb2br8Gd34fJs7a1BpZyCYY5Zg9610nY0ubellcX4ZVOF0QtoH20DlyQtT+NUCerDbVN4pwKK0lE7VFOUwh5YdfYPL6ahK3IqQvLzKawztXDAKIBtVoEJk2YsqnZepv9vHSHIvnRkbzfbPv52muJ60R9Kf69DGah3dpHt61CPGLS5m8uJXM8Ocg3mUHLVwVocltOeOhoDM8H4ZsBQyFtNTOWkH51wB5MihmfxMCRGsjTDxQc5XOBKS/xtjtSkavRshcXYB3cSWcL7STZBpEqf4LS/AvrMC/mIN/acH7RIvs719cgj8n0r0vep/uXX22CG4sw72cg2f8uQVwcQlcXoh/KULsfITJC0VMX/t7ZLQvYKzT1uCSz+hlTI0CZTYrSjV7rtgu5HoLOKQuNOAijXdIsxniW/D+29zEUjzcIe27NpVewsZVbtJeRu+s5+H1COnr8+CSIlrSHsvh0jy4PM/Yw97lVfiXF5sB1aC+L3Rpsb2HS0ufukU5YJdz3p/7vrwQ70oO8cs5pK6thGv5cKUALmqCdjnOhRyiQ2vI3v8XpB9+hezEOUgZO9gWkvAn8bLKywusgEDGWQyEk8WB5ngrOEKQqP0Wv77NAaKYuGZYlbvl4GeVyKe850OM3N3G6M0QIDKllsIFMVMErszDubyK7JU8vCuL8a/Mf59oocl9EqMJqE/bKm/Kv6JrPAvN/dmz1+YzdT1CbHgp7s0KuFJhtfKFUvwrH8e9qYrpbZAew/fs/IWiUWaxljuFrw2LvgEgdgnFjGllEfNIY4RFML7FwAgv/20NEClnVTPMKn6ueirelF0qljnF6L0PMHYrggaRSznW11CI93IE/6qK2q8kbQAiJps7kzzrud5VK4kFjqemq88CDJ37bM+tvo3fWcz0neVMX80jeqGY5MX1cOP7YOSLEDsNWWUdWjNK/qIAYUBiFnBoCfAjDTLznQ1JfqPfEVhZOk6LpRT+tcgJ2fmb336bA8TD99K4qupoikQoy1MiqZ+Je59i4lYOzjXZxEpHj1jtEURU0tdXkL6+yiTmce053he6ugD/2iLcOZLO5apowbPRHJ9ffZu6XcbEjXxGrkcYv1lK+s6/gIk3ID5uI1WBby1RpjWAqqWmajZmnLQc4zGAyDmXnSxnUl58wP86XuCYmVlXzq6WI2vlvQb8W/f69gaIOtBRRpvWWA/bNdYSKpnrTN39DNO3i3CursLY6gLIFRuPd29ESN1YQuLmCsOc7ws4rj2Hb2gB7vUFFiRzaN8vcKjP3KsrSF5ea9Lqo3eex5n6p5B5E3zt92gDUI7WcHguGT9lSNEqJSEaVaLIVYAVtdb8CjPDNQEcHKcvtRRmJjdLK/VjM6b1tw4ez1zV5Ft5a+/h2gKIBI4q0JlU6LvBwDwgevcnid3egHe1CC4vseBQTP5GBO9WhMRwDonbS3FvLAQ58u8LzYfr8/FuiBbOoV0I156Rruse5vj8V3Nxr+yAG/8ERv4Akk1mrYakuoYl5vlmWWzKyZr14mZfu0BDSFPITJL8F+m91gLNFMkzi5ZmAWSWtlFJpYTZy16ZvZKI37rXt78Gyfi2IIJZTKNUaYFmgqm7v8T07VfIXiuxTBTM5gog7q0IyeH5hrybFjT6/BGJYcQ4Ak9Ilpm5MW/WcW85R98F5z1i+Hl4TzxH54fnBNc357/H999wXd3bbGafHwBoCVxdakkmp55p9rla+xHchwVreB2dn2OvoWMM5cD1HNRv2WtFMPxD8FD+Rp9d3aiSs6aMaYqEaoR4abP2/tEiJIFAzrnW1atVnlWoPULzSu1jDsfbahBpkb82sd5ROEj2hLULg8VVEiiph7jRL5Gd+H4SwyW4dyJwOwK3xAg5cHMZ7vB8nLsR0Hez6XYE//ZC/FvLcG8tnyH97d/KgdvPwXDE0h0da8m9GcG58RzpazmkruaQuLqI+JUFZG8vIDs8D2c4gnMngjdsSeeZ+7n5HNycPze6FcG/E8G9Z1u9N/cWXts8rwCRC0ZQlMD1fNBz6BkeO34+7u0cnGHRQtzh5+zz3iiAaysMOPxrEdwruTg38snciTA9vB7YbXaHxZ0GN2N3AJgpMiGtELzMG9lMoc7Qd/Z7e0w4saHv9X7Wef+nvXMNte266vg65+xzzj7Pe+7Nuff03pt3G1objG1ME7W9IpVQCTVSqpZUKkZMiSik2pp+CKgfzAcpVBFbNdoiFB/UQCBSIaCxRaGlEUKj1UaTe85+v9+P9V4/+c+51r773ua2+ZDmZF+yYbDW2WudNedce/zHGHOOMcfQDenqlT21pSNMVpP5e7P/eQ2Pi61BjLpo2fyFenN6twKI1yAYfgGv+wCj8gFBykAGJIe7cLhHUlw2zDVj9pTpzffFVcssxQ3C4gaRoXUiAUf/V7IMaRhMIBOVVgxDhUeb+IfbeEebuEdr+KVlw0xBeQ4gApWYV9pLx1ekZSjM0woUrqDisgG/gB6lNGN68/xlOBRAduHidRYcR1skxRU79jmA6DuBIyht4JUFEgsYLp6Bl09YgBw6hC/t4R+ewa+t06v+KPCNWVraLD3t/PE15NVjedSCA0RBbG0SJfkUQLIZn9cmGn+JsP8rDCoHeLWUoSVZ5wEiUBxtw+EpC5qjbZLChmEgaZ2M6SSZDSikPTIm1bmeV1mGSg7Ka1DKQ3ELSlvEpTxROWe0lJ5zuXRfsYx7tGo1wByDZ22a9tUHUUm0bLSeQJqRwBsW9ggLu/Z6phHNuASOdduOjuqrKAW3GY/uS7/XM/W8oLx+OUAO94y3XCBOjhyiQwmNMwT1c4waHzTlyuYBceX5sXD1a9jowgNEkaAJw0srI9IickxNvkwyfJhh5Rx+PZXyxSU4OgFHJ43Ej8s5OHwLXLzJHgsnoZg31y4zu8pLICqtXKJiDor6O2OyHJRWobgOZdEqSWWZuOIQV+fMOPWhoBCNbShsEpdXCGvWTAqrVx6XiCpLhFUdVwirK5cdo3KeqLBvSIBUW7N+q39qR6Q2pS10vWr7Y8ZeEqgtaOLSGmF5E7+Sx6+uEVbWDMiTw004WjX3xUUHX1TZJ27eRdB+xGQ3VMK7q9FryKvH8qhrACADU/4sVLmRTIOoypVqjkw/ybBy/rsBUjhBXF5CTBEfnic+vIm4cNL8PQNCYQcO9y1wdCxsg5hODJWZJjqXmXSZqSTQrBmQJBULkkQAEXOKStI8q1DYgKNdKJwkKl5HXLiOqHiSuHiCqLRDLO90OY8YWeBQfzXXENiiWnrUuUBS2jb3azy2jysWFCnzZyDIwGPGXs4ZcGZjEcAMQKpr+FVpPgFkjeRIgmDJ9F3j8CoOXv0MtD8Cg88DxauCQ6BZ9M+CA0TqYmQAIoetqvVaM0t5tP4VvN9nVLmZoGElp2XOXSjuoh87ruaIi6dJCgck5S0SmUoymaQBCqfg6ACOzkJhH4oblrkFDgMQSdVV4osOiZaOj7R8rIntBklph6SyTVzbJK6vkEiDZSSwGI0iIOVtO4XTcHTatqN2i3tQ3IGS2pQ2kgknU+6SFphpA2mfWo64sk5S3ki119y92f9Iu5W27DjLW8QpeM1zypqPbRFVdghqqwS1HFFV4F414zL3qJ26w7Tu4LbOQ+dRGP9zmsl/0WFw9f4vPEC0dq4sF0EYm4TEBiDBANxvgv8ZhtVb8RsOSU2MLem9C5LQ6Q8e1WQGrVqGETBKYsydOQYVYFKmFrPpXPMMAefoPMHhJkEhT1DcJSjvE1UPiOpvIWyeIWrv4TVX8VoOQdtS3HKImw5JMwWNeZ6kdEoFmWnSMK90FHA1n0iPpRxx3TECQMxrxqL5lsYqyjSXQCYAHp0nKZwnKe4bQOkdWNBdDSA5Qk329ZyWQ9R0GDUdJu3boPtn4B7aBGxX56+Fv7LgALGhCcqDpGTP0iIGICai97/A/3OGldssQIzUFhMKAFsWIA2HSFRPtUl5awYgM58QIPR/lzGbJvGnSApniUoHTKs7TGu7TGvXM629E7f2Ptz6B/DqP4vfuJ9h6f0My+9lXHkX49oPMandilu/Aa9+lrB+ykr8kky3V0tWc2VzHb+2wbSxjltfNeOUttSYYgkFM/fSsvSOAXRydKMBiLRmXNkgrl7SNJdpkPqy1SBVh1CTeD2n5eA3Hfoth3H73baisetjizIuPA6uOoCFB4h2nYmU7yJK4nQeotpuSjL2JOPq7YQtB2RmVVahvA2VzRlAdM1I9NoqSXUTypv2PgFDjNFO/7eYJzw8QVg4RVw5CXrZgg4AAAtoSURBVO1NktEq3bbDoJ/HG78L/Acg/AxET0P0gu1DUAXvJZh+E8ZfgcET0H2cpPVJks4DJK0fgc710DpH3NwnrO/h17bwqmu41WW8umx+B6/x3TSt5Um6dzOu30W3dJpBZQWv48DQgZEDfS3drpKUdqFyGqpnoLZPXN4lKGziyjko8NeXobpDUjtB1FgjauZIGjk7fr23ngNdh2HNodtycMf3wvg/bKzVnMviqly2wBcWHCByKcndZGM7zTZNpThX2Luv3K1fYVK7IwWImECTZwEkTyIp23TMtVAmT32JpLYC1ZRpxDiipv7OQ/mAuHQ9fuU00/oWk7ZDv+vQ7p+mN76bIHwQ+CPgqxBXLfMoM2ZGZiuEijMewvQ5m5zZ+xuYPgbex8F9CNwHYfIxkvFHiEcfJhrdz7DxfobNCwxb72XY+rHLqf4zMHiUuPfbBIMP4vVvZ9o9ybTtGLNO4Pc1udcSdG0DGinVNohKm4SFHMjUayxBfZu4sUvcXCdurUBTpPELaBlAlui0tnHHD8BEmeJTjb3AAPh+XV98gJgANoFEOkSe3DSpq+KzkmcZ1d5NIKmqH7y6DtUtqK0bE0TAkLQUGUbINI00R00T9h2oHED5RpLqzfiNc0xaJ+h3lul2HarNk/T6v8Zw9DmI/xH4lg2YNHn6bbIVw0RZaQOFsmq/ihIuKwI5Ua5ZBVkeXkEXbTkwlQTzXgTvf9KjzkWqN/J/4L4I4+fBfxaSv4LwEdz+Bbr1M3SqDoOqw7TmmFU8CQOjDVtL0MpBbQ2qcyCob84BRPdYs8ocew5xZ4lBbYtu++1Mp58CL417e1ODfD+MHd/1zDeo1V3l3FNu1kRhpAohVV3j+BvG/Ai7S9CUFM1DbRsa6ySadIrqW0SSrGIgMYWOAkhVK0L7UD5PVLkBt3aGcWufQfeAweAWBoMfptv7RfzpU/iT75AombRSYipUNTH1XAh8peyPbck1PyJRhgl5+udJ4eAaQLZMHdnVOFVDMqtyuq65laK/rzjOIgdUU8/klnoK3MeYdO6jU7uJTjXHpOnga5wyFWe0DNIS+jsDQiNP3Ngmaq0TtZcu3avrPYewk6PfOE2v89P43mchTOv4Lf5K7vdk4IXWIBlAxDeKH1X5MlOlT3HRRv0/z6R+D1FvGdrr1sSo70Azbxggbmsyu2fImFIZQBrSNntQvc7Y5V4jz6jt0Ovs0u/dyWT0q0STJ0imXzf17xJhMiviog2NgUK8lSAwxo083GiKH3oEQWTvU6oi5eFWOq8AVB5bKf7NMbT15ZXuX3Xm9RyVZ1ZMplFEc0cpJBNBYMKYhKgaRP8O7ufwex9l1Lwdt3OCsOsQSYvOAJKedx3Ivm+tkbS2iNt54s6y/V7XDUBWCDp5hs23Mug+SBT+A9A3+zNM+9+TxRb74jUEEC33XgmQbzNt/ARxfwU6eWhuQmPbAqTjkHQEkG2o71oTbAYQzTs2jV0uDeO39ph0rmc6uIA3fgS8v4egOB93Zwq8yKpTni5PlY5izYtk9qkYp6JOxzY1v8K2Vc5R6wjTtE55Visv3RCUKhS7IGeUi4LzsgC9YC7LoA0X97VXQgGwZhVPCRFeAO8JGD5E3LsLBmegl7NMn40xM7kEGoGklSNpbbwyQDrrBJ0NRq07mPQfI4m+ZnZwqp/XuALJsrsvJsqNBpltotEOs4HdU6BfTltEoheZNt9HPJREzENrywKktW5XZnoOSVvmRg5km18pYVs5osZJovZ7oKeUNV8A7zkIW2memjTwVB2RRSdGjxLCWKtq6o9KgGXFgurEtEzcWKLiLaaSZEzsTYi9MYk/MWSrsGpvvW/J7ItIH64G5klGZTRmjGtSH6kP1nyTSvoOeE9C52EY/DgMdu2YBRBjQq5BffWSpmivQnuDpLNB0l0xq1ZaudJ7STqb+J0dxq27mfY/C8l/ktAzuzmUSf1a/iy+BplJ3WzDjSoHmdJUEB/Rb96HPxRzbEB7DVoyr1ZIeg7RwCHpWk0ibWKo6xB3HWNSuK0bGFcvEDQ/AcOnIaxdmj+oqJFKHqkSkeFKa+jZdTUFUSqZRB8vruFTMRSmZecS7Z8XghPXFoFRIRjZW7Fr615okm9SqgagIhmKo8lIdpUSganZOGIYdEyZumy/t9EiMi81B4vK0Pw76PwOcfcCQec0QTN1LMr7LoAIBKIUIFq+pnNJgFjBsYHbyzPs3sN08NeQaGGhk9by07iv3c9CA0RAMOE+EmLSGjqa8lppYQma+NGniZO7jEc7C/kwXmzXIZSvYOLA2B4j18FzHSbuHsPBXXRbvwxodep/LcOKKWecqMYyu0bnGYlZdG73O1hO1n0Z6SGXwDQ7NzPwbD/qFUcB/pXIlAHQ8oTmX5bsttW0CfVV5L4Mk7/EG/wS7vBtuON1omkOvHW8wSphb90KjqY07J4xtYKuJubWl8JwnUnPYTB8D/CMWYyIgxrE3VQ4vAmQN+wbmAEkE+RGoqcOQwZMkj8k4l6C3qaVlNmk1F3DFUCCJZg6uAP5Ndbo925hNLmPIPhd4lCZxwvWrMmePzO89YVE9fFJUJk3mulYcNgkBjo3XbQYtQARSLxvEbt/QeB+FHf6TsajLYajJcbjNYLhBnRWQaZnW9p225il8UDaJQ+DTaaDJUbjnySOv27BqoDQWJrw+Mb/ejDlYmuQbJIoZsgY+DKAjHD5Y+B+kuGe9TDL6dVeIh6fYNhdI/KW8CcO49Eqo94dTFufhsHTELycMoCYQMtOWWNiCGkDgUNHXTiejwWIACESWNJIm6yrpm/qZ5r1JX4egi8RTn7DLFO3uuuM/FWCqQMCgzzm/TUQYCZ5GG9D6xR0zuIODphMfoFQBUfN+5apl6YsOZ7hvy6tLjRAZHWIKYz5MbNabLoY41tgyjT+PAk/TzLcTwGi5cwNgv4NdJtnGfZPMRnfSOz/FISPgvcv4CoaODVPDP8LfQKD3OFyjeuo744PHJY7sjiCOXCkczKZWppIJ5RT56Wck/JdfBvcv8V1H2Ls3s3QO4fnrs8BxCEZrRBNNmC8B63T0LqFYHAn/vS3CIKL1m+TCST9CNfw55oAiPmNMvEp71qWewmPSfBF4vhjBL2zYPwh20T1A/zunXRq9zDs30sw+TgEXwSesxNQ1S9XbXIpjxkOBAyFr6RfqtHjxkfaB5mZOrUaRWDRUvDYACSmSmKqwk7AV7HxLgT/DclTwOOMph/And5KMsgZEzToOfgDB3+cIx5uQ/skNG8j6X+I2PtT/KBpMi3JspL/xzT8JkDemG9ATJFVHJrZF2ZZNPVOyzoPv0wS/Tpe+3oSrWI194kb74DRzzHuChh/AsE/QfCSRYRQEcuZEZo0v+a5BggyVQQO1dhOwaHvdX5cH7UtzWnUqLqiRGpKhdMzWUOSNHtIGA8J/AmhOzXLyoQaR9XsJ/emjxO5H4bRLdBfwu87TAcOk5FDMNIqV564+TYYPAzBk3hB2zgtzWt+EyDH9cu/unYlMTVFNdktLFpsPIYWgQzTyAR5BpJH8btvNev5tG+G3gWIPwHTL0DUtNaTvG3hBCLtb1fohkgJ6dKJuJ4vEijm6dV19Qdzl/ohJpWWM1pEDskyCSUSswwbGLdJpKGFIUE0IIx7JhvlDPj+C2ZbANMPwehGgvEy3sRhqlU+1yHpO8Stm2D0KYifwY2qxtgMtYqctvuDGdwb46kLbmLNAyQtMGEcaRlA9JL/Dfg9wt7boasVmnfA+D7gD4BnLf9rSiFGk3POVDxSphTFVknKyqxKJ+kCXSaxj1t7aGjqg6ZGM0kuR+nLJLyUAiSe1d2QqIgZEtEhSnzj+Y+MM1UhKl8F/zfBvYPE3cL3HfzQIQwdkoEins/B+DHga0ySkpmeyRUj18yxatDXAUP/Dzulf7mPSc8LAAAAAElFTkSuQmCC -``` - -### `annotation` - -A Kubernetes annotation for the NavLink custom resource. - -### `label` - -A Kubernetes label for the NavLink custom resource. - -### `sideLabel` - -Label that appears in the left navigation bar - -### `target` - -Sets the target property of the link's anchor tag (``), which (depending on browsers) determines if it opens in a new window or in an existing tab. - -The default value is `_self`, which opens the link on the current tab. To open the link in a new window or tab, set the target to `_blank`. - -For more information about the target property, see [this page.](https://www.w3schools.com/tags/att_a_target.asp) - -### `toService` - -Has five fields that are constructed to create a URL like the following: `https:///k8s/clusters//k8s/namespace//service/::/proxy/` - -For example, a link to a monitoring service can be set up as follows: - -- name: `rancher-monitoring-grafana` -- namespace: `cattle-monitoring-system` -- path: `proxy/?orgId=1` -- port: `"80"` -- scheme: `http` - -It is required to provide either the `toService` directive or the `toURL` directive. - -### `toUrl` - -Can be any link, even to links outside of the cluster. - -It is required to provide either the `toService` directive or the `toURL` directive. - -# Link Examples - -### Example of Link with `toUrl` - -This example NavLink YAML shows an example of configuring a NavLink to a Grafana dashboard: - -```yaml -apiVersion: ui.cattle.io/v1 -kind: NavLink -metadata: - name: grafana -spec: - group: "Monitoring Dashboards" - toURL: https:///api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/?orgId=1 -``` - -Adding the above YAML results in a link to Grafana being created, as shown in the following screenshot: - -![Screenshot of Grafana Link]({{< baseurl >}}/img/rancher/example-grafana-link.png) - -### Example of Link with `toService` - -This example YAML shows an example of `toService` used for the link target: - -```yaml -apiVersion: ui.cattle.io/v1 -kind: NavLink -metadata: - annotations: - key: annotation - labels: - key: label - name: navlinkname -spec: - description: This is a description field # Optional. - group: "group1" # Optional. If not provided, the links appear standalone. - iconSrc: data:image/jpeg;base64,[icon source string is clipped for brevity] - label: This is a label # Optional. - sideLabel: A side label. # Optional. - target: _blank #Optional. _blank opens the link in a new tab or window. - toService: # toService or #toUrl needs to be provided. - name: rancher-monitoring-grafana - namespace: cattle-monitoring-system - path: proxy/?orgId=1 - port: "80" - scheme: http -``` - -Adding the `toService` parameters above results in a link to Grafana being created, as shown in the following screenshot: - -![Screenshot of Grafana Link]({{< baseurl >}}/img/rancher/example-service-link.png) - diff --git a/versioned_docs/version-2.6/admin-settings/cluster-templates/cluster-templates.md b/versioned_docs/version-2.6/admin-settings/cluster-templates/cluster-templates.md deleted file mode 100644 index ae050be8a8f..00000000000 --- a/versioned_docs/version-2.6/admin-settings/cluster-templates/cluster-templates.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Cluster Templates -weight: 100 ---- - -Cluster templates encompass both Kubernetes configuration and node pool configuration, allowing a single template to contain all the information Rancher needs to provision new nodes in a cloud provider and install Kubernetes on those nodes. - -- [Overview](#overview) -- [RKE2 Cluster Template](#rke2-cluster-template) -- [Adding a Cluster Template to Rancher](#adding-a-cluster-template-to-rancher) -- [Creating a Cluster from a Cluster Template](#creating-a-cluster-from-a-cluster-template) -- [Updating a Cluster Created from a Cluster Template](#updating-a-cluster-created-from-a-cluster-template) -- [Deploying Clusters from a Template with Fleet](#deploying-clusters-from-a-template-with-fleet) -- [Uninstalling Cluster Templates](#uninstalling-cluster-templates) -- [Configuration Options](#configuration-options) - -# Overview - -Cluster templates are provided as Helm charts. To use them, you will need to clone and fork the templates, change them according to your use case, and then install the Helm charts on the Rancher management cluster. When the Helm chart is installed on the Rancher management cluster, a new cluster resource is created, which Rancher uses to provision the new cluster. - -After the cluster is provisioned using the template, no changes to the template will affect the cluster. After the cluster is created from the cluster template, its configuration and infrastructure can change, because no restrictions are enforced by cluster templates. - -### Kubernetes Distribution - -Cluster templates can use any Kubernetes distribution. For now, we provide an example with an RKE2 Kubernetes cluster. We may provide more examples in the future using other Kubernetes distributions. - -### Versioning - -Rancher doesn't manage version control for cluster templates. Version control is handled in the repository containing the template's Helm chart. - -# RKE2 Cluster Template - -The example repository for an RKE2 cluster template is [here](https://github.com/rancher/cluster-template-examples). As of Rancher v2.6.0, we provide an RKE2 cluster template and may add more in the future. - -# Adding a Cluster Template to Rancher - -In this section, you'll learn how to add the cluster template to the `local` cluster's chart repo list. The result is that Rancher will include the cluster template as an option when users install new Kubernetes clusters. - -> **Prerequisites:** -> -> - You will need permission to install Helm charts on the `local` Kubernetes cluster that Rancher is installed on. -> - In order for the chart to appear in the form for creating new clusters, the chart must have the annotation `catalog.cattle.io/type: cluster-template`. - -1. Go to a cluster template example repository. Rancher's examples are in [this GitHub repository.](https://github.com/rancher/cluster-template-examples) As of Rancher v2.6.0, we provide an RKE2 cluster template and add to more in the future. -1. Fork the repository. -1. Optional: Edit the cluster options by editing the `values.yaml` file. For help editing the file, see the cluster template's Helm chart README. -1. Add the chart repository to Rancher. Click **☰ > Cluster Management**. -1. Go to the `local` cluster and click **Explore.** -1. In the left navigation bar, click **Apps & Marketplace > Chart Repositories.** -1. Click **Create.** -1. Enter a name for the cluster template repository. -1. Click **Git Repository containing Helm chart definitions.** -1. In the **Git Repo URL** field, enter the URL for the repository. For example, `https://github.com/rancher/cluster-template-examples.git`. -1. In the **Git Branch** field, enter the branch to use as the source for the template. Rancher's example repository uses `main`. -1. Click **Create.** - -**Result:** The cluster template available from the **Apps & Marketplace** in Rancher's `local` cluster. It can now be used to deploy clusters. - -> * **Restricted Admin access:** If you are a restricted admin and don’t have access to the `local` cluster, you may still add new RKE2 templates and manage cluster repositories. To navigate to the chart repository, go to the left navigation bar and click **☰ > Cluster Management > Advanced > Repositories**. You will bypass steps 1 - 6 above, then proceed to follow steps 7 - 12 to create the cluster template. - -# Creating a Cluster from a Cluster Template - -> **Prerequisites:** -> -> - You will need permission to provision new Kubernetes clusters. -> - You will need cloud credentials for provisioning infrastructure using the template. -> - In order to show in the form for creating new clusters, the cluster template's Helm chart must have the `catalog.cattle.io/type: cluster-template` annotation. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create.** -1. Click the name of your cluster template. -1. Finish installing the Helm chart. - -**Result:** After Rancher provisions the new cluster, it is managed in the same way as any other Rancher-launched Kubernetes cluster. You can configure any options through the UI if the cluster template has options for the user to choose from. - -# Updating a Cluster Created from a Cluster Template - -You can update any clusters using a template from the **Apps & Marketplace > Installed Apps** page, given there is a new version of a template being used by those clusters. - -# Deploying Clusters from a Template with Fleet - -> **Prerequisites:** -> -> - You will need permission to provision new Kubernetes clusters. -> - You will need cloud credentials for provisioning infrastructure using the template. -> - In order to show in the form for creating new clusters, the cluster template's Helm chart must have the `catalog.cattle.io/type:cluster-template` annotation. -> - In order to use a template as part of continuous delivery/GitOps, the cluster template needs to be deployed in the `fleet-local` namespace of the `local` cluster. -> - All values must be set in the `values.yaml` of the template. -> - Fleet repositories must follow the guidelines on [this page.](http://fleet.rancher.io/gitrepo-structure/) For RKE2 cluster templates, that means a `fleet.yaml` file must be added to the repository. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create.** -1. Click **Create Cluster from Template.** - -**Result:** After Rancher provisions the new cluster, it is managed by Fleet. - -# Uninstalling Cluster Templates - -1. Click **☰ > Cluster Management**. -1. Go to the `local` cluster and click **Apps & Marketplace > Chart Repositories.** -1. Go to the chart repository for your cluster template and click **⋮ > Delete.** -1. Confirm the deletion. - -**Result:** The cluster template is uninstalled. This action does not affect clusters created with the cluster template. - -An admin with access to the `local` cluster can also remove a cluster deployed via cluster templates through the **Apps & Marketplace > Installed Apps** page. - -# Configuration Options - -Cluster templates are flexible enough that they can be used to configure all of the following options: - -- Node configuration -- Node pools -- Pre-specified cloud credentials -- Enable/configure an authorized cluster endpoint to get kubectl access to the cluster without using Rancher as a proxy -- Install Rancher V2 monitoring -- Kubernetes version -- Assign cluster members -- Infrastructure configuration such as AWS VPC/subnets or vSphere data center -- Cloud provider options -- Pod security options -- Network providers -- Ingress controllers -- Network security configuration -- Network plugins -- Private registry URL and credentials -- Add-ons -- Kubernetes options, including configurations for Kubernetes components such as kube-api, kube-controller, kubelet, and services - -For details on how to configure the template, refer to the cluster template's Helm chart README. \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/config-private-registry/config-private-registry.md b/versioned_docs/version-2.6/admin-settings/config-private-registry/config-private-registry.md deleted file mode 100644 index cd36201d114..00000000000 --- a/versioned_docs/version-2.6/admin-settings/config-private-registry/config-private-registry.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Configuring a Global Default Private Registry -weight: 40 ---- - -You might want to use a private container registry to share your custom base images within your organization. With a private registry, you can keep a private, consistent, and centralized source of truth for the container images that are used in your clusters. - -There are two main ways to set up private registries in Rancher: by setting up the global default registry through the **Settings** tab in the global view, and by setting up a private registry in the advanced options in the cluster-level settings. The global default registry is intended to be used for air-gapped setups, for registries that do not require credentials. The cluster-level private registry is intended to be used in all setups in which the private registry requires credentials. - -This section is about configuring the global default private registry, and focuses on how to configure the registry from the Rancher UI after Rancher is installed. - -For instructions on setting up a private registry with command line options during the installation of Rancher, refer to the [air gapped installation guide]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap). - -If your private registry requires credentials, it cannot be used as the default registry. There is no global way to set up a private registry with authorization for every Rancher-provisioned cluster. Therefore, if you want a Rancher-provisioned cluster to pull images from a private registry with credentials, you will have to [pass in the registry credentials through the advanced cluster options](#setting-a-private-registry-with-credentials-when-deploying-a-cluster) every time you create a new cluster. - -# Setting a Private Registry with No Credentials as the Default Registry - -1. Log into Rancher and configure the default administrator password. -1. Click **☰ > Global Settings**. -1. Go to the setting called `system-default-registry` and choose **⋮ > Edit Setting**. -1. Change the value to your registry (e.g. `registry.yourdomain.com:port`). Do not prefix the registry with `http://` or `https://`. - -**Result:** Rancher will use your private registry to pull system images. - -# Setting a Private Registry with Credentials when Deploying a Cluster - -You can follow these steps to configure a private registry when you create a cluster: - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Choose a cluster type. -1. In the **Cluster Configuration** go to the **Registries** tab and click **Pull images for Rancher from a private registry**. -1. Enter the registry hostname and credentials. -1. Click **Create**. - -**Result:** The new cluster will be able to pull images from the private registry. - -The private registry cannot be configured after the cluster is created. diff --git a/versioned_docs/version-2.6/admin-settings/drivers/cluster-drivers/cluster-drivers.md b/versioned_docs/version-2.6/admin-settings/drivers/cluster-drivers/cluster-drivers.md deleted file mode 100644 index 7bc22f30cfc..00000000000 --- a/versioned_docs/version-2.6/admin-settings/drivers/cluster-drivers/cluster-drivers.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Cluster Drivers -weight: 1 ---- - -Cluster drivers are used to create clusters in a [hosted Kubernetes provider]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/), such as Google GKE. The availability of which cluster driver to display when creating clusters is defined by the cluster driver's status. Only `active` cluster drivers will be displayed as an option for creating clusters. By default, Rancher is packaged with several existing cloud provider cluster drivers, but you can also add custom cluster drivers to Rancher. - -If there are specific cluster drivers that you do not want to show your users, you may deactivate those cluster drivers within Rancher and they will not appear as an option for cluster creation. - -### Managing Cluster Drivers - ->**Prerequisites:** To create, edit, or delete cluster drivers, you need _one_ of the following permissions: -> ->- [Administrator Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) ->- [Custom Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/#custom-global-permissions) with the [Manage Cluster Drivers]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) role assigned. - -## Activating/Deactivating Cluster Drivers - -By default, Rancher only activates drivers for the most popular cloud providers, Google GKE, Amazon EKS and Azure AKS. If you want to show or hide any node driver, you can change its status. - -1. In the upper left corner, click **☰ > Cluster Management**. - -2. In the left navigation menu, click **Drivers**. - -3. On the **Cluster Drivers** tab, select the driver that you wish to activate or deactivate and click **⋮ > Activate** or **⋮ > Deactivate**. - -## Adding Custom Cluster Drivers - -If you want to use a cluster driver that Rancher doesn't support out-of-the-box, you can add the provider's driver in order to start using them to create _hosted_ kubernetes clusters. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **Drivers**. -1. On the **Cluster Drivers** tab, click **Add Cluster Driver**. -1. Complete the **Add Cluster Driver** form. Then click **Create**. - - -### Developing your own Cluster Driver - -In order to develop cluster driver to add to Rancher, please refer to our [example](https://github.com/rancher-plugins/kontainer-engine-driver-example). diff --git a/versioned_docs/version-2.6/admin-settings/drivers/drivers.md b/versioned_docs/version-2.6/admin-settings/drivers/drivers.md deleted file mode 100644 index 32d05779257..00000000000 --- a/versioned_docs/version-2.6/admin-settings/drivers/drivers.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Provisioning Drivers -weight: 70 ---- - -Drivers in Rancher allow you to manage which providers can be used to deploy [hosted Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/) or [nodes in an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) to allow Rancher to deploy and manage Kubernetes. - -### Rancher Drivers - -With Rancher drivers, you can enable/disable existing built-in drivers that are packaged in Rancher. Alternatively, you can add your own driver if Rancher has not yet implemented it. - -There are two types of drivers within Rancher: - -* [Cluster Drivers](#cluster-drivers) -* [Node Drivers](#node-drivers) - -### Cluster Drivers - -Cluster drivers are used to provision [hosted Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/), such as GKE, EKS, AKS, etc.. The availability of which cluster driver to display when creating a cluster is defined based on the cluster driver's status. Only `active` cluster drivers will be displayed as an option for creating clusters for hosted Kubernetes clusters. By default, Rancher is packaged with several existing cluster drivers, but you can also create custom cluster drivers to add to Rancher. - -By default, Rancher has activated several hosted Kubernetes cloud providers including: - -* [Amazon EKS]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/eks/) -* [Google GKE]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/gke/) -* [Azure AKS]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks/) - -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/ack/) -* [Huawei CCE]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/cce/) -* [Tencent]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/tke/) - -### Node Drivers - -Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://docs.docker.com/machine/drivers/). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. - -If there are specific node drivers that you don't want to show to your users, you would need to de-activate these node drivers. - -Rancher supports several major cloud providers, but by default, these node drivers are active and available for deployment: - -* [Amazon EC2]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/) -* [Azure]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/azure/) -* [Digital Ocean]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/digital-ocean/) -* [vSphere]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/vsphere/) - -There are several other node drivers that are disabled by default, but are packaged in Rancher: - -* [Harvester]({{}}/rancher/v2.6/en/virtualization-admin/#harvester-node-driver/), available in Rancher v2.6.1 diff --git a/versioned_docs/version-2.6/admin-settings/drivers/node-drivers/node-drivers.md b/versioned_docs/version-2.6/admin-settings/drivers/node-drivers/node-drivers.md deleted file mode 100644 index 6dbd01a200b..00000000000 --- a/versioned_docs/version-2.6/admin-settings/drivers/node-drivers/node-drivers.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Node Drivers -weight: 2 ---- - -Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://docs.docker.com/machine/drivers/). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. - -If there are specific node drivers that you don't want to show to your users, you would need to de-activate these node drivers. - -#### Managing Node Drivers - ->**Prerequisites:** To create, edit, or delete drivers, you need _one_ of the following permissions: -> ->- [Administrator Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) ->- [Custom Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/#custom-global-permissions) with the [Manage Node Drivers]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) role assigned. - -## Activating/Deactivating Node Drivers - -By default, Rancher only activates drivers for the most popular cloud providers, Amazon EC2, Azure, DigitalOcean and vSphere. If you want to show or hide any node driver, you can change its status. - -1. In the upper left corner, click **☰ > Cluster Management**. - -2. In the left navigation menu, click **Drivers**. - -2. On the **Node Drivers** tab, select the driver that you wish to activate or deactivate and click **⋮ > Activate** or **⋮ > Deactivate**. - -## Adding Custom Node Drivers - -If you want to use a node driver that Rancher doesn't support out-of-the-box, you can add that provider's driver in order to start using them to create node templates and eventually node pools for your Kubernetes cluster. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **Drivers**. -1. On **Node Drivers** tab, click **Add Node Driver**. -1. Complete the **Add Node Driver** form. Then click **Create**. - -### Developing your own node driver - -Node drivers are implemented with [Docker Machine](https://docs.docker.com/machine/). diff --git a/versioned_docs/version-2.6/admin-settings/k8s-metadata/k8s-metadata.md b/versioned_docs/version-2.6/admin-settings/k8s-metadata/k8s-metadata.md deleted file mode 100644 index 29302bf7013..00000000000 --- a/versioned_docs/version-2.6/admin-settings/k8s-metadata/k8s-metadata.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Upgrading Kubernetes without Upgrading Rancher -weight: 30 ---- - -The RKE metadata feature allows you to provision clusters with new versions of Kubernetes as soon as they are released, without upgrading Rancher. This feature is useful for taking advantage of patch versions of Kubernetes, for example, if you want to upgrade to Kubernetes v1.14.7 when your Rancher server originally supported v1.14.6. - -> **Note:** The Kubernetes API can change between minor versions. Therefore, we don't support introducing minor Kubernetes versions, such as introducing v1.15 when Rancher currently supports v1.14. You would need to upgrade Rancher to add support for minor Kubernetes versions. - -Rancher's Kubernetes metadata contains information specific to the Kubernetes version that Rancher uses to provision [RKE clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/). Rancher syncs the data periodically and creates custom resource definitions (CRDs) for **system images,** **service options** and **addon templates**. Consequently, when a new Kubernetes version is compatible with the Rancher server version, the Kubernetes metadata makes the new version available to Rancher for provisioning clusters. The metadata gives you an overview of the information that the [Rancher Kubernetes Engine]({{}}/rke/latest/en/) (RKE) uses for deploying various Kubernetes versions. - -This table below describes the CRDs that are affected by the periodic data sync. - -> **Note:** Only administrators can edit metadata CRDs. It is recommended not to update existing objects unless explicitly advised. - -| Resource | Description | Rancher API URL | -|----------|-------------|-----------------| -| System Images | List of system images used to deploy Kubernetes through RKE. | `/v3/rkek8ssystemimages` | -| Service Options | Default options passed to Kubernetes components like `kube-api`, `scheduler`, `kubelet`, `kube-proxy`, and `kube-controller-manager` | `/v3/rkek8sserviceoptions` | -| Addon Templates | YAML definitions used to deploy addon components like Canal, Calico, Flannel, Weave, Kube-dns, CoreDNS, `metrics-server`, `nginx-ingress` | `/v3/rkeaddons` | - -Administrators might configure the RKE metadata settings to do the following: - -- Refresh the Kubernetes metadata, if a new patch version of Kubernetes comes out and they want Rancher to provision clusters with the latest version of Kubernetes without having to upgrade Rancher -- Change the metadata URL that Rancher uses to sync the metadata, which is useful for air gap setups if you need to sync Rancher locally instead of with GitHub -- Prevent Rancher from auto-syncing the metadata, which is one way to prevent new and unsupported Kubernetes versions from being available in Rancher - -### Refresh Kubernetes Metadata - -The option to refresh the Kubernetes metadata is available for administrators by default, or for any user who has the **Manage Cluster Drivers** [global role.]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) - -To force Rancher to refresh the Kubernetes metadata, a manual refresh action is available: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **Drivers**. -1. Click **Refresh Kubernetes Metadata**. - -You can configure Rancher to only refresh metadata when desired by setting `refresh-interval-minutes` to `0` (see below) and using this button to perform the metadata refresh manually when desired. - -### Configuring the Metadata Synchronization - -> Only administrators can change these settings. - -The RKE metadata config controls how often Rancher syncs metadata and where it downloads data from. You can configure the metadata from the settings in the Rancher UI, or through the Rancher API at the endpoint `v3/settings/rke-metadata-config`. - -The way that the metadata is configured depends on the Rancher version. - -To edit the metadata config in Rancher, - -1. In the upper left corner, click **☰ > Global Settings**. -1. Go to the **rke-metadata-config** section. Click **⋮ > Edit Setting**. -1. You can optionally fill in the following parameters: - - - `refresh-interval-minutes`: This is the amount of time that Rancher waits to sync the metadata. To disable the periodic refresh, set `refresh-interval-minutes` to 0. - - `url`: This is the HTTP path that Rancher fetches data from. The path must be a direct path to a JSON file. For example, the default URL for Rancher v2.4 is `https://releases.rancher.com/kontainer-driver-metadata/release-v2.4/data.json`. -1. Click **Save**. - -If you don't have an air gap setup, you don't need to specify the URL where Rancher gets the metadata, because the default setting is to pull from [Rancher's metadata Git repository.](https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.5/data/data.json) - -However, if you have an [air gap setup,](#air-gap-setups) you will need to mirror the Kubernetes metadata repository in a location available to Rancher. Then you need to change the URL to point to the new location of the JSON file. - -### Air Gap Setups - -Rancher relies on a periodic refresh of the `rke-metadata-config` to download new Kubernetes version metadata if it is supported with the current version of the Rancher server. For a table of compatible Kubernetes and Rancher versions, refer to the [service terms section.](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.2.8/) - -If you have an air gap setup, you might not be able to get the automatic periodic refresh of the Kubernetes metadata from Rancher's Git repository. In that case, you should disable the periodic refresh to prevent your logs from showing errors. Optionally, you can configure your metadata settings so that Rancher can sync with a local copy of the RKE metadata. - -To sync Rancher with a local mirror of the RKE metadata, an administrator would configure the `rke-metadata-config` settings to point to the mirror. For details, refer to [Configuring the Metadata Synchronization.](#configuring-the-metadata-synchronization) - -After new Kubernetes versions are loaded into the Rancher setup, additional steps would be required in order to use them for launching clusters. Rancher needs access to updated system images. While the metadata settings can only be changed by administrators, any user can download the Rancher system images and prepare a private Docker registry for them. - -1. To download the system images for the private registry, click the Rancher server version at the bottom left corner of the Rancher UI. -1. Download the OS specific image lists for Linux or Windows. -1. Download `rancher-images.txt`. -1. Prepare the private registry using the same steps during the [air gap install]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry), but instead of using the `rancher-images.txt` from the releases page, use the one obtained from the previous steps. - -**Result:** The air gap installation of Rancher can now sync the Kubernetes metadata. If you update your private registry when new versions of Kubernetes are released, you can provision clusters with the new version without having to upgrade Rancher. diff --git a/versioned_docs/version-2.6/admin-settings/pod-security-policies/pod-security-policies.md b/versioned_docs/version-2.6/admin-settings/pod-security-policies/pod-security-policies.md deleted file mode 100644 index 9244102623d..00000000000 --- a/versioned_docs/version-2.6/admin-settings/pod-security-policies/pod-security-policies.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Pod Security Policies -weight: 60 ---- - -_Pod Security Policies_ (or PSPs) are objects that control security-sensitive aspects of pod specification (like root privileges). - -If a pod does not meet the conditions specified in the PSP, Kubernetes will not allow it to start, and Rancher will display an error message of `Pod is forbidden: unable to validate...`. - -- [How PSPs Work](#how-psps-work) -- [Default PSPs](#default-psps) - - [Restricted-NoRoot](#restricted-noroot) - - [Restricted](#restricted) - - [Unrestricted](#unrestricted) -- [Creating PSPs](#creating-psps) - - [Requirements](#requirements) - - [Creating PSPs in the Rancher UI](#creating-psps-in-the-rancher-ui) -- [Configuration](#configuration) - -# How PSPs Work - -You can assign PSPs at the cluster or project level. - -PSPs work through inheritance: - -- By default, PSPs assigned to a cluster are inherited by its projects, as well as any namespaces added to those projects. -- **Exception:** Namespaces that are not assigned to projects do not inherit PSPs, regardless of whether the PSP is assigned to a cluster or project. Because these namespaces have no PSPs, workload deployments to these namespaces will fail, which is the default Kubernetes behavior. -- You can override the default PSP by assigning a different PSP directly to the project. - -Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. - -Read more about Pod Security Policies in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/pod-security-policy/). - -# Default PSPs - -Rancher ships with three default Pod Security Policies (PSPs): the `restricted-noroot`, `restricted` and `unrestricted` policies. - -### Restricted-NoRoot - -This policy is based on the Kubernetes [example restricted policy](https://raw.githubusercontent.com/kubernetes/website/master/content/en/examples/policy/restricted-psp.yaml). It significantly restricts what types of pods can be deployed to a cluster or project. This policy: - -- Prevents pods from running as a privileged user and prevents escalation of privileges. -- Validates that server-required security mechanisms are in place, such as restricting what volumes can be mounted to only the core volume types and preventing root supplemental groups from being added. - -### Restricted - -This policy is a relaxed version of the `restricted-noroot` policy, with almost all the restrictions in place, except for the fact that it allows running containers as a privileged user. - -### Unrestricted - -This policy is equivalent to running Kubernetes with the PSP controller disabled. It has no restrictions on what pods can be deployed into a cluster or project. - -# Creating PSPs - -Using Rancher, you can create a Pod Security Policy using our GUI rather than creating a YAML file. - -### Requirements - -Rancher can only assign PSPs for clusters that are [launched using RKE]({{< baseurl >}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/). - -You must enable PSPs at the cluster level before you can assign them to a project. This can be configured by [editing the cluster]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/). - -It is a best practice to set PSP at the cluster level. - -We recommend adding PSPs during cluster and project creation instead of adding it to an existing one. - -### Creating PSPs in the Rancher UI - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation bar, click **Pod Security Policies**. -1. Click **Add Policy**. -1. Name the policy. -1. Complete each section of the form. Refer to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/pod-security-policy/) for more information on what each policy does. -1. Click **Create**. - -# Configuration - -The Kubernetes documentation on PSPs is [here](https://kubernetes.io/docs/concepts/policy/pod-security-policy/). diff --git a/versioned_docs/version-2.6/admin-settings/rbac/cluster-project-roles/cluster-project-roles.md b/versioned_docs/version-2.6/admin-settings/rbac/cluster-project-roles/cluster-project-roles.md deleted file mode 100644 index 8d1d1fb702b..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rbac/cluster-project-roles/cluster-project-roles.md +++ /dev/null @@ -1,225 +0,0 @@ ---- -title: Cluster and Project Roles -weight: 1127 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Cluster and project roles define user authorization inside a cluster or project. - -To manage these roles, - -1. Click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles** and go to the **Cluster** or **Project/Namespaces** tab. - -### Membership and Role Assignment - -The projects and clusters accessible to non-administrative users is determined by _membership_. Membership is a list of users who have access to a specific cluster or project based on the roles they were assigned in that cluster or project. Each cluster and project includes a tab that a user with the appropriate permissions can use to manage membership. - -When you create a cluster or project, Rancher automatically assigns you as the `Owner` for it. Users assigned the `Owner` role can assign other users roles in the cluster or project. - -> **Note:** Non-administrative users cannot access any existing projects/clusters by default. A user with appropriate permissions (typically the owner) must explicitly assign the project and cluster membership. - -### Cluster Roles - -_Cluster roles_ are roles that you can assign to users, granting them access to a cluster. There are two primary cluster roles: `Owner` and `Member`. - -- **Cluster Owner:** - - These users have full control over the cluster and all resources in it. - -- **Cluster Member:** - - These users can view most cluster level resources and create new projects. - -#### Custom Cluster Roles - -Rancher lets you assign _custom cluster roles_ to a standard user instead of the typical `Owner` or `Member` roles. These roles can be either a built-in custom cluster role or one defined by a Rancher administrator. They are convenient for defining narrow or specialized access for a standard user within a cluster. See the table below for a list of built-in custom cluster roles. - -#### Cluster Role Reference - -The following table lists each built-in custom cluster role available and whether that level of access is included in the default cluster-level permissions, `Cluster Owner` and `Cluster Member`. - -| Built-in Cluster Role | Owner | Member | -| ---------------------------------- | ------------- | --------------------------------- | -| Create Projects | ✓ | ✓ | -| Manage Cluster Backups             | ✓ | | -| Manage Cluster Catalogs | ✓ | | -| Manage Cluster Members | ✓ | | -| Manage Nodes [(see table below)](#Manage-Nodes-Permissions)| ✓ | | -| Manage Storage | ✓ | | -| View All Projects | ✓ | | -| View Cluster Catalogs | ✓ | ✓ | -| View Cluster Members | ✓ | ✓ | -| View Nodes | ✓ | ✓ | - -#### Manage Nodes Permissions - -The following table lists the permissions available for the `Manage Nodes` role in RKE and RKE2. - -| Manage Nodes Permissions | RKE | RKE2 | -|-----------------------------|-------- |--------- | -| SSH Access | ✓ | ✓ | -| Delete Nodes | ✓ | ✓ | -| Scale Clusters Up and Down | ✓ | * | -***In RKE2, you must have permission to edit a cluster to be able to scale clusters up and down.** -
- -For details on how each cluster role can access Kubernetes resources, you can look them up in the Rancher UI: - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. Click the **Cluster** tab. -1. Click the name of an individual role. The table shows all of the operations and resources that are permitted by the role. - -> **Note:** ->When viewing the resources associated with default roles created by Rancher, if there are multiple Kubernetes API resources on one line item, the resource will have `(Custom)` appended to it. These are not custom resources but just an indication that there are multiple Kubernetes API resources as one resource. - -### Giving a Custom Cluster Role to a Cluster Member - -After an administrator [sets up a custom cluster role,]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles/) cluster owners and admins can then assign those roles to cluster members. - -To assign a custom role to a new cluster member, you can use the Rancher UI. To modify the permissions of an existing member, you will need to use the Rancher API view. - -To assign the role to a new cluster member, - - - - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to assign a role to a member and click **Explore**. -1. Click **RBAC > Cluster Members**. -1. Click **Add**. -1. In the **Cluster Permissions** section, choose the custom cluster role that should be assigned to the member. -1. Click **Create**. - - - - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to assign a role to a member and click **Explore**. -1. Click **Cluster > Cluster Members**. -1. Click **Add**. -1. In the **Cluster Permissions** section, choose the custom cluster role that should be assigned to the member. -1. Click **Create**. - - - - -**Result:** The member has the assigned role. - -To assign any custom role to an existing cluster member, - -1. Click **☰ > Users & Authentication**. -1. Go to the member you want to give the role to. Click the **⋮ > Edit Config**. -1. If you have added custom roles, they will show in the **Custom** section. Choose the role you want to assign to the member. -1. Click **Save**. - -**Result:** The member has the assigned role. - -### Project Roles - -_Project roles_ are roles that can be used to grant users access to a project. There are three primary project roles: `Owner`, `Member`, and `Read Only`. - -- **Project Owner:** - - These users have full control over the project and all resources in it. - -- **Project Member:** - - These users can manage project-scoped resources like namespaces and workloads, but cannot manage other project members. - - >**Note:** - > - >By default, the Rancher role of `project-member` inherits from the `Kubernetes-edit` role, and the `project-owner` role inherits from the `Kubernetes-admin` role. As such, both `project-member` and `project-owner` roles will allow for namespace management, including the ability to create and delete namespaces. - -- **Read Only:** - - These users can view everything in the project but cannot create, update, or delete anything. - - >**Caveat:** - > - >Users assigned the `Owner` or `Member` role for a project automatically inherit the `namespace creation` role. However, this role is a [Kubernetes ClusterRole](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole), meaning its scope extends to all projects in the cluster. Therefore, users explicitly assigned the `owner` or `member` role for a project can create namespaces in other projects they're assigned to, even with only the `Read Only` role assigned. - -#### Custom Project Roles - -Rancher lets you assign _custom project roles_ to a standard user instead of the typical `Owner`, `Member`, or `Read Only` roles. These roles can be either a built-in custom project role or one defined by a Rancher administrator. They are convenient for defining narrow or specialized access for a standard user within a project. See the table below for a list of built-in custom project roles. - -#### Project Role Reference - -The following table lists each built-in custom project role available in Rancher and whether it is also granted by the `Owner`, `Member`, or `Read Only` role. - -| Built-in Project Role | Owner | Member | Read Only | -| ---------------------------------- | ------------- | ----------------------------- | ------------- | -| Manage Project Members | ✓ | | | -| Create Namespaces | ✓ | ✓ | | -| Manage Config Maps | ✓ | ✓ | | -| Manage Ingress | ✓ | ✓ | | -| Manage Project Catalogs | ✓ | | | -| Manage Secrets | ✓ | ✓ | | -| Manage Service Accounts | ✓ | ✓ | | -| Manage Services | ✓ | ✓ | | -| Manage Volumes | ✓ | ✓ | | -| Manage Workloads | ✓ | ✓ | | -| View Secrets | ✓ | ✓ | | -| View Config Maps | ✓ | ✓ | ✓ | -| View Ingress | ✓ | ✓ | ✓ | -| View Project Members | ✓ | ✓ | ✓ | -| View Project Catalogs | ✓ | ✓ | ✓ | -| View Service Accounts | ✓ | ✓ | ✓ | -| View Services | ✓ | ✓ | ✓ | -| View Volumes | ✓ | ✓ | ✓ | -| View Workloads | ✓ | ✓ | ✓ | - -> **Notes:** -> ->- Each project role listed above, including `Owner`, `Member`, and `Read Only`, is comprised of multiple rules granting access to various resources. You can view the roles and their rules on the Global > Security > Roles page. ->- When viewing the resources associated with default roles created by Rancher, if there are multiple Kubernetes API resources on one line item, the resource will have `(Custom)` appended to it. These are not custom resources but just an indication that there are multiple Kubernetes API resources as one resource. ->- The `Manage Project Members` role allows the project owner to manage any members of the project **and** grant them any project scoped role regardless of their access to the project resources. Be cautious when assigning this role out individually. - -### Defining Custom Roles -As previously mentioned, custom roles can be defined for use at the cluster or project level. The context field defines whether the role will appear on the cluster member page, project member page, or both. - -When defining a custom role, you can grant access to specific resources or specify roles from which the custom role should inherit. A custom role can be made up of a combination of specific grants and inherited roles. All grants are additive. This means that defining a narrower grant for a specific resource **will not** override a broader grant defined in a role that the custom role is inheriting from. - -### Default Cluster and Project Roles - -By default, when a standard user creates a new cluster or project, they are automatically assigned an ownership role: either [cluster owner](#cluster-roles) or [project owner](#project-roles). However, in some organizations, these roles may overextend administrative access. In this use case, you can change the default role to something more restrictive, such as a set of individual roles or a custom role. - -There are two methods for changing default cluster/project roles: - -- **Assign Custom Roles**: Create a [custom role]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles) for either your [cluster](#custom-cluster-roles) or [project](#custom-project-roles), and then set the custom role as default. - -- **Assign Individual Roles**: Configure multiple [cluster](#cluster-role-reference)/[project](#project-role-reference) roles as default for assignment to the creating user. - - For example, instead of assigning a role that inherits other roles (such as `cluster owner`), you can choose a mix of individual roles (such as `manage nodes` and `manage storage`). - ->**Note:** -> ->- Although you can [lock]({{}}/rancher/v2.6/en/admin-settings/rbac/locked-roles/) a default role, the system still assigns the role to users who create a cluster/project. ->- Only users that create clusters/projects inherit their roles. Users added to the cluster/project membership afterward must be explicitly assigned their roles. - -### Configuring Default Roles for Cluster and Project Creators - -You can change the cluster or project role(s) that are automatically assigned to the creating user. - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. Click the **Cluster** or **Project/Namespaces** tab. -1. Find the custom or individual role that you want to use as default. Then edit the role by selecting **⋮ > Edit Config**. -1. In the **Cluster Creator Default** or **Project Creator Default** section, enable the role as the default. -1. Click **Save**. - -**Result:** The default roles are configured based on your changes. Roles assigned to cluster/project creators display a check in the **Cluster/Project Creator Default** column. - -If you want to remove a default role, edit the permission and select **No** from the default roles option. - -### Cluster Membership Revocation Behavior - -When you revoke the cluster membership for a standard user that's explicitly assigned membership to both the cluster _and_ a project within the cluster, that standard user [loses their cluster roles](#clus-roles) but [retains their project roles](#proj-roles). In other words, although you have revoked the user's permissions to access the cluster and its nodes, the standard user can still: - -- Access the projects they hold membership in. -- Exercise any [individual project roles](#project-role-reference) they are assigned. - -If you want to completely revoke a user's access within a cluster, revoke both their cluster and project memberships. diff --git a/versioned_docs/version-2.6/admin-settings/rbac/default-custom-roles/default-custom-roles.md b/versioned_docs/version-2.6/admin-settings/rbac/default-custom-roles/default-custom-roles.md deleted file mode 100644 index 3b6bcb7f837..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rbac/default-custom-roles/default-custom-roles.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: Custom Roles -weight: 1128 ---- - -Within Rancher, _roles_ determine what actions a user can make within a cluster or project. - -Note that _roles_ are different from _permissions_, which determine what clusters and projects you can access. - -> It is possible for a custom role to enable privilege escalation. For details, see [this section.](#privilege-escalation) - -This section covers the following topics: - -- [Prerequisites](#prerequisites) -- [Creating a custom role](#creating-a-custom-role) -- [Creating a custom role that inherits from another role](#creating-a-custom-role-that-inherits-from-another-role) -- [Deleting a custom role](#deleting-a-custom-role) -- [Assigning a custom role to a group](#assigning-a-custom-role-to-a-group) -- [Privilege escalation](#privilege-escalation) - -# Prerequisites - -To complete the tasks on this page, one of the following permissions are required: - - - [Administrator Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/). - - [Custom Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/#custom-global-permissions) with the [Manage Roles]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) role assigned. - -# Creating A Custom Role - -While Rancher comes out-of-the-box with a set of default user roles, you can also create default custom roles to provide users with very specific permissions within Rancher. - -The steps to add custom roles differ depending on the version of Rancher. - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. Select a tab to determine the scope of the role you're adding. The tabs are: - - - **Global:** The role is valid for allowing members to manage global scoped resources. - - **Cluster:** The role is valid for assignment when adding/managing members to clusters. - - **Project/Namespaces:** The role is valid for assignment when adding/managing members to projects or namespaces. - -1. Click **Create Global Role,** **Create Cluster Role** or **Create Project/Namespaces Role,** depending on the scope. -1. Enter a **Name** for the role. -1. Optional: Choose the **Cluster/Project Creator Default** option to assign this role to a user when they create a new cluster or project. Using this feature, you can expand or restrict the default roles for cluster/project creators. - - > Out of the box, the Cluster Creator Default and the Project Creator Default roles are `Cluster Owner` and `Project Owner` respectively. - -1. Use the **Grant Resources** options to assign individual [Kubernetes API endpoints](https://kubernetes.io/docs/reference/) to the role. - - > When viewing the resources associated with default roles created by Rancher, if there are multiple Kubernetes API resources on one line item, the resource will have `(Custom)` appended to it. These are not custom resources but just an indication that there are multiple Kubernetes API resources as one resource. - - > The Resource text field provides a method to search for pre-defined Kubernetes API resources, or enter a custom resource name for the grant. The pre-defined or `(Custom)` resource must be selected from the dropdown, after entering a resource name into this field. - - You can also choose the individual cURL methods (`Create`, `Delete`, `Get`, etc.) available for use with each endpoint you assign. - -1. Use the **Inherit from** options to assign individual Rancher roles to your custom roles. Note: When a custom role inherits from a parent role, the parent role cannot be deleted until the child role is deleted. - -1. Click **Create**. - -# Creating a Custom Role that Inherits from Another Role - -If you have a group of individuals that need the same level of access in Rancher, it can save time to create a custom role in which all of the rules from another role, such as the administrator role, are copied into a new role. This allows you to only configure the variations between the existing role and the new role. - -The custom role can then be assigned to a user or group so that the role takes effect the first time the user or users sign into Rancher. - -To create a custom role based on an existing role, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. Click the **Cluster** or **Project/Namespaces** tab. Click **Create Cluster Role** or **Create Project/Namespaces Role** depending on the scope. Note: Only cluster roles and project/namespace roles can inherit from another role. -1. Enter a name for the role. -1. In the **Inherit From** tab, select the role(s) that the custom role will inherit permissions from. -1. In the **Grant Resources** tab, select the Kubernetes resource operations that will be enabled for users with the custom role. - - > The Resource text field provides a method to search for pre-defined Kubernetes API resources, or enter a custom resource name for the grant. The pre-defined or `(Custom)` resource must be selected from the dropdown, after entering a resource name into this field. -1. Optional: Assign the role as default. -1. Click **Create**. - -# Deleting a Custom Role - -When deleting a custom role, all global role bindings with this custom role are deleted. - -If a user is only assigned one custom role, and the role is deleted, the user would lose access to Rancher. For the user to regain access, an administrator would need to edit the user and apply new global permissions. - -Custom roles can be deleted, but built-in roles cannot be deleted. - -To delete a custom role, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -2. Go to the custom global role that should be deleted and click **⋮ (…) > Delete**. -3. Click **Delete**. - -# Assigning a Custom Role to a Group - -If you have a group of individuals that need the same level of access in Rancher, it can save time to create a custom role. When the role is assigned to a group, the users in the group have the appropriate level of access the first time they sign into Rancher. - -When a user in the group logs in, they get the built-in Standard User global role by default. They will also get the permissions assigned to their groups. - -If a user is removed from the external authentication provider group, they would lose their permissions from the custom role that was assigned to the group. They would continue to have their individual Standard User role. - -> **Prerequisites:** You can only assign a global role to a group if: -> -> * You have set up an [external authentication provider]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-vs-local-authentication) -> * The external authentication provider supports [user groups]({{}}/rancher/v2.6/en/admin-settings/authentication/user-groups/) -> * You have already set up at least one user group with the authentication provider - -To assign a custom role to a group, follow these steps: - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Groups**. -1. Go to the existing group that will be assigned the custom role and click **⋮ > Edit Config**. -1. If you have created roles, they will show in the **Custom** section. Choose any custom role that will be assigned to the group. -1. Optional: In the **Global Permissions** or **Built-in** sections, select any additional permissions that the group should have. -1. Click **Save.**. - -**Result:** The custom role will take effect when the users in the group log into Rancher. - -# Privilege Escalation - -The `Configure Catalogs` custom permission is powerful and should be used with caution. When an admin assigns the `Configure Catalogs` permission to a standard user, it could result in privilege escalation in which the user could give themselves admin access to Rancher provisioned clusters. Anyone with this permission should be considered equivalent to an admin. \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rbac/global-permissions/global-permissions.md b/versioned_docs/version-2.6/admin-settings/rbac/global-permissions/global-permissions.md deleted file mode 100644 index 2a58aa35aef..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rbac/global-permissions/global-permissions.md +++ /dev/null @@ -1,254 +0,0 @@ ---- -title: Global Permissions -weight: 1126 ---- - -_Permissions_ are individual access rights that you can assign when selecting a custom permission for a user. - -Global Permissions define user authorization outside the scope of any particular cluster. Out-of-the-box, there are four default global permissions: `Administrator`, `Restricted Admin`,`Standard User` and `User-base`. - -- **Administrator:** These users have full control over the entire Rancher system and all clusters within it. - -- **Restricted Admin:** These users have full control over downstream clusters, but cannot alter the local Kubernetes cluster. - -- **Standard User:** These users can create new clusters and use them. Standard users can also assign other users permissions to their clusters. - -- **User-Base:** User-Base users have login-access only. - -You cannot update or delete the built-in Global Permissions. - -This section covers the following topics: - -- [Restricted Admin](#restricted-admin) -- [Global permission assignment](#global-permission-assignment) - - [Global permissions for new local users](#global-permissions-for-new-local-users) - - [Global permissions for users with external authentication](#global-permissions-for-users-with-external-authentication) -- [Custom global permissions](#custom-global-permissions) - - [Custom global permissions reference](#custom-global-permissions-reference) - - [Configuring default global permissions for new users](#configuring-default-global-permissions) - - [Configuring global permissions for existing individual users](#configuring-global-permissions-for-existing-individual-users) - - [Configuring global permissions for groups](#configuring-global-permissions-for-groups) - - [Refreshing group memberships](#refreshing-group-memberships) - -# Restricted Admin - -A new `restricted-admin` role was created in Rancher v2.5 in order to prevent privilege escalation from the local Rancher server Kubernetes cluster. This role has full administrator access to all downstream clusters managed by Rancher, but it does not have permission to alter the local Kubernetes cluster. - -The `restricted-admin` can create other `restricted-admin` users with an equal level of access. - -A new setting was added to Rancher to set the initial bootstrapped administrator to have the `restricted-admin` role. This applies to the first user created when the Rancher server is started for the first time. If the environment variable is set, then no global administrator would be created, and it would be impossible to create the global administrator through Rancher. - -To bootstrap Rancher with the `restricted-admin` as the initial user, the Rancher server should be started with the following environment variable: - -``` -CATTLE_RESTRICTED_DEFAULT_ADMIN=true -``` -### List of `restricted-admin` Permissions - -The following table lists the permissions and actions that a `restricted-admin` should have in comparison with the `Administrator` and `Standard User` roles: - -| Category | Action | Global Admin | Standard User | Restricted Admin | Notes for Restricted Admin role | -| -------- | ------ | ------------ | ------------- | ---------------- | ------------------------------- | -| Local Cluster functions | Manage Local Cluster (List, Edit, Import Host) | Yes | No | No | | -| | Create Projects/namespaces | Yes | No | No | | -| | Add cluster/project members | Yes | No | No | | -| | Deploy MulticlusterApp in local cluster | Yes | No | No | | -| | Global DNS | Yes | No | No | | -| | Access to management cluster for CRDs and CRs | Yes | No | Yes | | -| | Save as RKE Template | Yes | No | No | | -| Security | | | | | | -| Enable auth | Configure Authentication | Yes | No | Yes | | -| Roles | Create/Assign GlobalRoles | Yes | No (Can list) | Yes | Auth webhook allows creating globalrole for perms already present | -| | Create/Assign ClusterRoles | Yes | No (Can list) | Yes | Not in local cluster | -| | Create/Assign ProjectRoles | Yes | No (Can list) | Yes | Not in local cluster | -| Users | Add User/Edit/Delete/Deactivate User | Yes | No | Yes | | -| Groups | Assign Global role to groups | Yes | No | Yes | As allowed by the webhook | -| | Refresh Groups | Yes | No | Yes | | -| PSP's | Manage PSP templates | Yes | No (Can list) | Yes | Same privileges as Global Admin for PSPs | -| Tools | | | | | | -| | Manage RKE Templates | Yes | No | Yes | | -| | Manage Global Catalogs | Yes | No | Yes | Cannot edit/delete built-in system catalog. Can manage Helm library | -| | Cluster Drivers | Yes | No | Yes | | -| | Node Drivers | Yes | No | Yes | | -| | GlobalDNS Providers | Yes | Yes (Self) | Yes | | -| | GlobalDNS Entries | Yes | Yes (Self) | Yes | | -| Settings | | | | | | -| | Manage Settings | Yes | No (Can list) | No (Can list) | | -| Apps | | | | | | -| | Launch Multicluster Apps | Yes | Yes | Yes | Not in local cluster | -| User | | | | | | -| | Manage API Keys | Yes (Manage all) | Yes (Manage self) | Yes (Manage self) | | -| | Manage Node Templates | Yes | Yes (Manage self) | Yes (Manage self) | Can only manage their own node templates and not those created by other users | -| | Manage Cloud Credentials | Yes | Yes (Manage self) | Yes (Manage self) | Can only manage their own cloud credentials and not those created by other users | -| Downstream Cluster | Create Cluster | Yes | Yes | Yes | | -| | Edit Cluster | Yes | Yes | Yes | | -| | Rotate Certificates | Yes | | Yes | | -| | Snapshot Now | Yes | | Yes | | -| | Restore Snapshot | Yes | | Yes | | -| | Save as RKE Template | Yes | No | Yes | | -| | Run CIS Scan | Yes | Yes | Yes | | -| | Add Members | Yes | Yes | Yes | | -| | Create Projects | Yes | Yes | Yes | | -| Feature Charts since v2.5 | | | | | | -| | Install Fleet | Yes | | Yes | Should not be able to run Fleet in local cluster | -| | Deploy EKS cluster | Yes | Yes | Yes | | -| | Deploy GKE cluster | Yes | Yes | Yes | | -| | Deploy AKS cluster | Yes | Yes | Yes | | - - -### Changing Global Administrators to Restricted Admins - -If Rancher already has a global administrator, they should change all global administrators over to the new `restricted-admin` role. - -This can be done through **Security > Users** and moving any Administrator role over to Restricted Administrator. - -Signed-in users can change themselves over to the `restricted-admin` if they wish, but they should only do that as the last step, otherwise they won't have the permissions to do so. - -# Global Permission Assignment - -Global permissions for local users are assigned differently than users who log in to Rancher using external authentication. - -### Global Permissions for New Local Users - -When you create a new local user, you assign them a global permission as you complete the **Add User** form. - -To see the default permissions for new users, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. The **Roles** page has tabs for roles grouped by scope. Each table lists the roles in that scope. In the **Global** tab, in the **New User Default** column, the permissions given to new users by default are indicated with a checkmark. - -You can [change the default global permissions to meet your needs.](#configuring-default-global-permissions) - -### Global Permissions for Users with External Authentication - -When a user logs into Rancher using an external authentication provider for the first time, they are automatically assigned the **New User Default** global permissions. By default, Rancher assigns the **Standard User** permission for new users. - -To see the default permissions for new users, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. The **Roles** page has tabs for roles grouped by scope. Each table lists the roles in that scope. In the **New User Default** column on each page, the permissions given to new users by default are indicated with a checkmark. - -You can [change the default permissions to meet your needs.](#configuring-default-global-permissions) - -Permissions can be assigned to an individual user with [these steps.](#configuring-global-permissions-for-existing-individual-users) - -You can [assign a role to everyone in the group at the same time](#configuring-global-permissions-for-groups) if the external authentication provider supports groups. - -# Custom Global Permissions - -Using custom permissions is convenient for providing users with narrow or specialized access to Rancher. - -When a user from an [external authentication source]({{}}/rancher/v2.6/en/admin-settings/authentication/) signs into Rancher for the first time, they're automatically assigned a set of global permissions (hereafter, permissions). By default, after a user logs in for the first time, they are created as a user and assigned the default `user` permission. The standard `user` permission allows users to login and create clusters. - -However, in some organizations, these permissions may extend too much access. Rather than assigning users the default global permissions of `Administrator` or `Standard User`, you can assign them a more restrictive set of custom global permissions. - -The default roles, Administrator and Standard User, each come with multiple global permissions built into them. The Administrator role includes all global permissions, while the default user role includes three global permissions: Create Clusters, Use Catalog Templates, and User Base, which is equivalent to the minimum permission to log in to Rancher. In other words, the custom global permissions are modularized so that if you want to change the default user role permissions, you can choose which subset of global permissions are included in the new default user role. - -Administrators can enforce custom global permissions in multiple ways: - -- [Changing the default permissions for new users](#configuring-default-global-permissions) -- [Configuring global permissions for individual users](#configuring-global-permissions-for-individual-users) -- [Configuring global permissions for groups](#configuring-global-permissions-for-groups) - -### Custom Global Permissions Reference - -The following table lists each custom global permission available and whether it is included in the default global permissions, `Administrator`, `Standard User` and `User-Base`. - -| Custom Global Permission | Administrator | Standard User | User-Base | -| ---------------------------------- | ------------- | ------------- |-----------| -| Create Clusters | ✓ | ✓ | | -| Create RKE Templates | ✓ | ✓ | | -| Manage Authentication | ✓ | | | -| Manage Catalogs | ✓ | | | -| Manage Cluster Drivers | ✓ | | | -| Manage Node Drivers | ✓ | | | -| Manage PodSecurityPolicy Templates | ✓ | | | -| Manage Roles | ✓ | | | -| Manage Settings | ✓ | | | -| Manage Users | ✓ | | | -| Use Catalog Templates | ✓ | ✓ | | -| User-Base (Basic log-in access) | ✓ | ✓ | | - -For details on which Kubernetes resources correspond to each global permission, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. If you click the name of an individual role, a table shows all of the operations and resources that are permitted by the role. - -> **Notes:** -> -> - Each permission listed above is comprised of multiple individual permissions not listed in the Rancher UI. For a full list of these permissions and the rules they are comprised of, access through the API at `/v3/globalRoles`. -> - When viewing the resources associated with default roles created by Rancher, if there are multiple Kubernetes API resources on one line item, the resource will have `(Custom)` appended to it. These are not custom resources but just an indication that there are multiple Kubernetes API resources as one resource. - -### Configuring Default Global Permissions - -If you want to restrict the default permissions for new users, you can remove the `user` permission as default role and then assign multiple individual permissions as default instead. Conversely, you can also add administrative permissions on top of a set of other standard permissions. - -> **Note:** Default roles are only assigned to users added from an external authentication provider. For local users, you must explicitly assign global permissions when adding a user to Rancher. You can customize these global permissions when adding the user. - -To change the default global permissions that are assigned to external users upon their first log in, follow these steps: - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. On the **Roles** page, make sure the **Global** tab is selected. -1. Find the permissions set that you want to add or remove as a default. Then edit the permission by selecting **⋮ > Edit Config**. -1. If you want to add the permission as a default, Select **Yes: Default role for new users** and then click **Save**. If you want to remove a default permission, edit the permission and select **No**. - -**Result:** The default global permissions are configured based on your changes. Permissions assigned to new users display a check in the **New User Default** column. - -### Configuring Global Permissions for Individual Users - -To configure permission for a user, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Users**. -1. Go to the user whose access level you want to change and click **⋮ > Edit Config**. -1. In the **Global Permissions** and **Built-in** sections, check the boxes for each permission you want the user to have. If you have created roles from the **Roles** page, they will appear in the **Custom** section and you can choose from them as well. -1. Click **Save**. - -> **Result:** The user's global permissions have been updated. - -### Configuring Global Permissions for Groups - -If you have a group of individuals that need the same level of access in Rancher, it can save time to assign permissions to the entire group at once, so that the users in the group have the appropriate level of access the first time they sign into Rancher. - -After you assign a custom global role to a group, the custom global role will be assigned to a user in the group when they log in to Rancher. - -For existing users, the new permissions will take effect when the users log out of Rancher and back in again, or when an administrator [refreshes the group memberships.](#refreshing-group-memberships) - -For new users, the new permissions take effect when the users log in to Rancher for the first time. New users from this group will receive the permissions from the custom global role in addition to the **New User Default** global permissions. By default, the **New User Default** permissions are equivalent to the **Standard User** global role, but the default permissions can be [configured.](#configuring-default-global-permissions) - -If a user is removed from the external authentication provider group, they would lose their permissions from the custom global role that was assigned to the group. They would continue to have any remaining roles that were assigned to them, which would typically include the roles marked as **New User Default**. Rancher will remove the permissions that are associated with the group when the user logs out, or when an administrator [refreshes group memberships,](#refreshing-group-memberships) whichever comes first. - -> **Prerequisites:** You can only assign a global role to a group if: -> -> * You have set up an [external authentication provider]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-vs-local-authentication) -> * The external authentication provider supports [user groups]({{}}/rancher/v2.6/en/admin-settings/authentication/user-groups/) -> * You have already set up at least one user group with the authentication provider - -To assign a custom global role to a group, follow these steps: - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Groups**. -1. Go to the group you want to assign a custom global role to and click **⋮ > Edit Config**. -1. In the **Global Permissions,** **Custom,** and/or **Built-in** sections, select the permissions that the group should have. -1. Click **Create**. - -**Result:** The custom global role will take effect when the users in the group log into Rancher. - -### Refreshing Group Memberships - -When an administrator updates the global permissions for a group, the changes take effect for individual group members after they log out of Rancher and log in again. - -To make the changes take effect immediately, an administrator or cluster owner can refresh group memberships. - -An administrator might also want to refresh group memberships if a user is removed from a group in the external authentication service. In that case, the refresh makes Rancher aware that the user was removed from the group. - -To refresh group memberships, - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Users**. -1. Click **Refresh Group Memberships**. - -**Result:** Any changes to the group members' permissions will take effect. diff --git a/versioned_docs/version-2.6/admin-settings/rbac/locked-roles/locked-roles.md b/versioned_docs/version-2.6/admin-settings/rbac/locked-roles/locked-roles.md deleted file mode 100644 index 8964fee2000..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rbac/locked-roles/locked-roles.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Locked Roles -weight: 1129 ---- - -You can set roles to a status of `locked`. Locking roles prevent them from being assigned to users in the future. - -Locked roles: - -- Cannot be assigned to users that don't already have it assigned. -- Are not listed in the **Member Roles** drop-down when you are adding a user to a cluster or project. -- Do not affect users assigned the role before you lock the role. These users retain access that the role provides. - - **Example:** let's say your organization creates an internal policy that users assigned to a cluster are prohibited from creating new projects. It's your job to enforce this policy. - - To enforce it, before you add new users to the cluster, you should lock the following roles: `Cluster Owner`, `Cluster Member`, and `Create Projects`. Then you could create a new custom role that includes the same permissions as a __Cluster Member__, except the ability to create projects. Then, you use this new custom role when adding users to a cluster. - -Roles can be locked by the following users: - -- Any user assigned the `Administrator` global permission. -- Any user assigned the `Custom Users` permission, along with the `Manage Roles` role. - - -## Locking/Unlocking Roles - -If you want to prevent a role from being assigned to users, you can set it to a status of `locked`. - -You can lock roles in two contexts: - -- When you're [adding a custom role]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles/). -- When you editing an existing role (see below). - -Cluster roles and project/namespace roles can be locked, but global roles cannot. - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. Go to the **Cluster** tab or the **Project/Namespaces** tab. -1. From the role that you want to lock (or unlock), select **⋮ > Edit Config**. -1. From the **Locked** option, choose the **Yes** or **No** radio button. Then click **Save**. diff --git a/versioned_docs/version-2.6/admin-settings/rbac/rbac.md b/versioned_docs/version-2.6/admin-settings/rbac/rbac.md deleted file mode 100644 index a0907463d94..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rbac/rbac.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Role-Based Access Control (RBAC) -weight: 20 ---- - -Within Rancher, each person authenticates as a _user_, which is a login that grants you access to Rancher. As mentioned in [Authentication]({{}}/rancher/v2.6/en/admin-settings/authentication/), users can either be local or external. - -After you configure external authentication, the users that display on the **Users** page changes. - -- If you are logged in as a local user, only local users display. - -- If you are logged in as an external user, both external and local users display. - -## Users and Roles - -Once the user logs in to Rancher, their _authorization_, or their access rights within the system, is determined by _global permissions_, and _cluster and project roles_. - -- [Global Permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/): - - Define user authorization outside the scope of any particular cluster. - -- [Cluster and Project Roles]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/): - - Define user authorization inside the specific cluster or project where they are assigned the role. - -Both global permissions and cluster and project roles are implemented on top of [Kubernetes RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/). Therefore, enforcement of permissions and roles is performed by Kubernetes. diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/applying-templates/applying-templates.md b/versioned_docs/version-2.6/admin-settings/rke-templates/applying-templates/applying-templates.md deleted file mode 100644 index 7d1b8ec8392..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/applying-templates/applying-templates.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Applying Templates -weight: 50 ---- - -You can create a cluster from an RKE template that you created, or from a template that has been [shared with you.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing) - -RKE templates can be applied to new clusters. - -You can [save the configuration of an existing cluster as an RKE template.](#converting-an-existing-cluster-to-use-an-rke-template) Then the cluster's settings can only be changed if the template is updated. - -You can't change a cluster to use a different RKE template. You can only update the cluster to a new revision of the same template. - -This section covers the following topics: - -- [Creating a cluster from an RKE template](#creating-a-cluster-from-an-rke-template) -- [Updating a cluster created with an RKE template](#updating-a-cluster-created-with-an-rke-template) -- [Converting an existing cluster to use an RKE template](#converting-an-existing-cluster-to-use-an-rke-template) - -### Creating a Cluster from an RKE Template - -To add a cluster [hosted by an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters) using an RKE template, use these steps: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create** and choose the infrastructure provider. -1. Provide the cluster name and node template details as usual. -1. To use an RKE template, under the **Cluster Options**, check the box for **Use an existing RKE template and revision**. -1. Choose an RKE template and revision from the dropdown menu. -1. Optional: You can edit any settings that the RKE template owner marked as **Allow User Override** when the template was created. If there are settings that you want to change, but don't have the option to, you will need to contact the template owner to get a new revision of the template. Then you will need to edit the cluster to upgrade it to the new revision. -1. Click **Create** to launch the cluster. - -### Updating a Cluster Created with an RKE Template - -When the template owner creates a template, each setting has a switch in the Rancher UI that indicates if users can override the setting. - -- If the setting allows a user override, you can update these settings in the cluster by [editing the cluster.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/) -- If the switch is turned off, you cannot change these settings unless the cluster owner creates a template revision that lets you override them. If there are settings that you want to change, but don't have the option to, you will need to contact the template owner to get a new revision of the template. - -If a cluster was created from an RKE template, you can edit the cluster to update the cluster to a new revision of the template. - -An existing cluster's settings can be [saved as an RKE template.](#converting-an-existing-cluster-to-use-an-rke-template) In that situation, you can also edit the cluster to update the cluster to a new revision of the template. - -> **Note:** You can't change the cluster to use a different RKE template. You can only update the cluster to a new revision of the same template. - -### Converting an Existing Cluster to Use an RKE Template - -This section describes how to create an RKE template from an existing cluster. - -RKE templates cannot be applied to existing clusters, except if you save an existing cluster's settings as an RKE template. This exports the cluster's settings as a new RKE template, and also binds the cluster to that template. The result is that the cluster can only be changed if the [template is updated,]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#updating-a-template) and the cluster is upgraded to [use a newer version of the template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#upgrading-a-cluster-to-use-a-new-template-revision) - -To convert an existing cluster to use an RKE template, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster that will be converted to use an RKE template. Click **⋮ > Save as RKE Template**. -1. Enter a name for the template in the form that appears, and click **Create**. - -**Results:** - -- A new RKE template is created. -- The cluster is converted to use the new template. -- New clusters can be [created from the new template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#creating-a-cluster-from-an-rke-template) \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/creating-and-revising/creating-and-revising.md b/versioned_docs/version-2.6/admin-settings/rke-templates/creating-and-revising/creating-and-revising.md deleted file mode 100644 index d1284ad6498..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/creating-and-revising/creating-and-revising.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -title: Creating and Revising RKE Templates -weight: 32 ---- - -This section describes how to manage RKE templates and revisions. You an create, share, update, and delete templates from the **Cluster Management** view under **RKE1 Configuration > RKE Templates**. - -Template updates are handled through a revision system. When template owners want to change or update a template, they create a new revision of the template. Individual revisions cannot be edited. However, if you want to prevent a revision from being used to create a new cluster, you can disable it. - -Template revisions can be used in two ways: to create a new cluster, or to upgrade a cluster that was created with an earlier version of the template. The template creator can choose a default revision, but when end users create a cluster, they can choose any template and any template revision that is available to them. After the cluster is created from a specific revision, it cannot change to another template, but the cluster can be upgraded to a newer available revision of the same template. - -The template owner has full control over template revisions, and can create new revisions to update the template, delete or disable revisions that should not be used to create clusters, and choose which template revision is the default. - -This section covers the following topics: - -- [Prerequisites](#prerequisites) -- [Creating a template](#creating-a-template) -- [Updating a template](#updating-a-template) -- [Deleting a template](#deleting-a-template) -- [Creating a revision based on the default revision](#creating-a-revision-based-on-the-default-revision) -- [Creating a revision based on a cloned revision](#creating-a-revision-based-on-a-cloned-revision) -- [Disabling a template revision](#disabling-a-template-revision) -- [Re-enabling a disabled template revision](#re-enabling-a-disabled-template-revision) -- [Setting a template revision as default](#setting-a-template-revision-as-default) -- [Deleting a template revision](#deleting-a-template-revision) -- [Upgrading a cluster to use a new template revision](#upgrading-a-cluster-to-use-a-new-template-revision) -- [Exporting a running cluster to a new RKE template and revision](#exporting-a-running-cluster-to-a-new-rke-template-and-revision) - -### Prerequisites - -You can create RKE templates if you have the **Create RKE Templates** permission, which can be [given by an administrator.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creator-permissions) - -You can revise, share, and delete a template if you are an owner of the template. For details on how to become an owner of a template, refer to [the documentation on sharing template ownership.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing/#sharing-ownership-of-templates) - -### Creating a Template - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Click **RKE1 configuration > Node Templates**. -1. Click **Add Template**. -1. Provide a name for the template. An auto-generated name is already provided for the template' first version, which is created along with this template. -1. Optional: Share the template with other users or groups by [adding them as members.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing/#sharing-templates-with-specific-users-or-groups) You can also make the template public to share with everyone in the Rancher setup. -1. Then follow the form on screen to save the cluster configuration parameters as part of the template's revision. The revision can be marked as default for this template. - -**Result:** An RKE template with one revision is configured. You can use this RKE template revision later when you [provision a Rancher-launched cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters). After a cluster is managed by an RKE template, it cannot be disconnected and the option to uncheck **Use an existing RKE Template and Revision** will be unavailable. - -### Updating a Template - -When you update an RKE template, you are creating a revision of the existing template. Clusters that were created with an older version of the template can be updated to match the new revision. - -You can't edit individual revisions. Since you can't edit individual revisions of a template, in order to prevent a revision from being used, you can [disable it.](#disabling-a-template-revision) - -When new template revisions are created, clusters using an older revision of the template are unaffected. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **RKE1 Configuration > RKE Templates**. -1. Go to the template that you want to edit and click the **⋮ > Edit**. -1. Edit the required information and click **Save**. -1. Optional: You can change the default revision of this template and also change who it is shared with. - -**Result:** The template is updated. To apply it to a cluster using an older version of the template, refer to the section on [upgrading a cluster to use a new revision of a template.](#upgrading-a-cluster-to-use-a-new-template-revision) - -### Deleting a Template - -When you no longer use an RKE template for any of your clusters, you can delete it. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Click **RKE1 configuration > RKE Templates**. -1. Go to the RKE template that you want to delete and click the **⋮ > Delete**. -1. Confirm the deletion. - -**Result:** The template is deleted. - -### Creating a Revision Based on the Default Revision - -You can clone the default template revision and quickly update its settings rather than creating a new revision from scratch. Cloning templates saves you the hassle of re-entering the access keys and other parameters needed for cluster creation. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **RKE1 Configuration > RKE Templates**. -1. Go to the RKE template that you want to clone and click the **⋮ > New Revision from Default**. -1. Complete the rest of the form to create a new revision. - -**Result:** The RKE template revision is cloned and configured. - -### Creating a Revision Based on a Cloned Revision - -When creating new RKE template revisions from your user settings, you can clone an existing revision and quickly update its settings rather than creating a new one from scratch. Cloning template revisions saves you the hassle of re-entering the cluster parameters. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Under **RKE1 configuration**, click **RKE Templates**. -1. Go to the template revision you want to clone. Then select **⋮ > Clone Revision**. -1. Complete the rest of the form. - -**Result:** The RKE template revision is cloned and configured. You can use the RKE template revision later when you provision a cluster. Any existing cluster using this RKE template can be upgraded to this new revision. - -### Disabling a Template Revision - -When you no longer want an RKE template revision to be used for creating new clusters, you can disable it. A disabled revision can be re-enabled. - -You can disable the revision if it is not being used by any cluster. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **RKE1 Configuration > RKE Templates**. -1. Go to the template revision you want to disable. Then select **⋮ > Disable**. - -**Result:** The RKE template revision cannot be used to create a new cluster. - -### Re-enabling a Disabled Template Revision - -If you decide that a disabled RKE template revision should be used to create new clusters, you can re-enable it. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Under **RKE1 configuration**, click **RKE Templates**. -1. Go to the template revision you want to re-enable. Then select **⋮ > Enable**. - -**Result:** The RKE template revision can be used to create a new cluster. - -### Setting a Template Revision as Default - -When end users create a cluster using an RKE template, they can choose which revision to create the cluster with. You can configure which revision is used by default. - -To set an RKE template revision as default, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **RKE1 Configuration > RKE templates**. -1. Go to the RKE template revision that should be default and click the **⋮ > Set as Default**. - -**Result:** The RKE template revision will be used as the default option when clusters are created with the template. - -### Deleting a Template Revision - -You can delete all revisions of a template except for the default revision. - -To permanently delete a revision, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **RKE1 Configuration > RKE templates**. -1. Go to the RKE template revision that should be deleted and click the **⋮ > Delete**. - -**Result:** The RKE template revision is deleted. - -### Upgrading a Cluster to Use a New Template Revision - -> This section assumes that you already have a cluster that [has an RKE template applied.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates) -> This section also assumes that you have [updated the template that the cluster is using](#updating-a-template) so that a new template revision is available. - -To upgrade a cluster to use a new template revision, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that you want to upgrade and click **⋮ > Edit Config**. -1. In the **Cluster Options** section, click the dropdown menu for the template revision, then select the new template revision. -1. Click **Save**. - -**Result:** The cluster is upgraded to use the settings defined in the new template revision. - -### Exporting a Running Cluster to a New RKE Template and Revision - -You can save an existing cluster's settings as an RKE template. - -This exports the cluster's settings as a new RKE template, and also binds the cluster to that template. The result is that the cluster can only be changed if the [template is updated,]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#updating-a-template) and the cluster is upgraded to [use a newer version of the template.] - -To convert an existing cluster to use an RKE template, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that will be converted to use an RKE template and **⋮ > Save as RKE Template**. -1. Enter a name for the RKE template in the form that appears, and click **Create**. - -**Results:** - -- A new RKE template is created. -- The cluster is converted to use the new template. -- New clusters can be [created from the new template and revision.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#creating-a-cluster-from-an-rke-template) \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/creator-permissions/creator-permissions.md b/versioned_docs/version-2.6/admin-settings/rke-templates/creator-permissions/creator-permissions.md deleted file mode 100644 index b3dba5b43b0..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/creator-permissions/creator-permissions.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Template Creator Permissions -weight: 10 ---- - -Administrators have the permission to create RKE templates, and only administrators can give that permission to other users. - -For more information on administrator permissions, refer to the [documentation on global permissions]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/). - -# Giving Users Permission to Create Templates - -Templates can only be created by users who have the global permission **Create RKE Templates**. - -Administrators have the global permission to create templates, and only administrators can give that permission to other users. - -For information on allowing users to modify existing templates, refer to [Sharing Templates.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing) - -Administrators can give users permission to create RKE templates in two ways: - -- By editing the permissions of an [individual user](#allowing-a-user-to-create-templates) -- By changing the [default permissions of new users](#allowing-new-users-to-create-templates-by-default) - -### Allowing a User to Create Templates - -An administrator can individually grant the role **Create RKE Templates** to any existing user by following these steps: - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Users**. -1. Choose the user you want to edit and click **⋮ > Edit Config**. -1. In the **Built-in** section, check the box for **Create new RKE Cluster Templates** role along with any other roles the user should have. You may want to also check the box for **Create RKE Template Revisions**. -1. Click **Save**. - -**Result:** The user has permission to create RKE templates. - -### Allowing New Users to Create Templates by Default - -Alternatively, the administrator can give all new users the default permission to create RKE templates by following the following steps. This will not affect the permissions of existing users. - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Roles**. -1. Go to the role named **Create new RKE Cluster Templates and click **⋮ > Edit Config**. -1. Select the option **Yes: Default role for new users**. -1. Click **Save**. -1. If you would like new users to also be able to create RKE template revisions, enable that role as default as well. - -**Result:** Any new user created in this Rancher installation will be able to create RKE templates. Existing users will not get this permission. - -### Revoking Permission to Create Templates - -Administrators can remove a user's permission to create templates with the following steps. Note: Administrators have full control over all resources regardless of whether fine-grained permissions are selected. - -1. In the upper left corner, click **☰ > Users & Authentication**. -1. In the left navigation bar, click **Users**. -1. Choose the user you want to edit permissions for and click **⋮ > Edit Config**. -1. In the **Built-in** section, un-check the box for **Create RKE Templates** and **Create RKE Template Revisions,** if applicable. In this section, you can change the user back to a standard user, or give the user a different set of permissions. -1. Click **Save**. - -**Result:** The user cannot create RKE templates. \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/enforcement/enforcement.md b/versioned_docs/version-2.6/admin-settings/rke-templates/enforcement/enforcement.md deleted file mode 100644 index cd51f196341..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/enforcement/enforcement.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Template Enforcement -weight: 32 ---- - -This section describes how template administrators can enforce templates in Rancher, restricting the ability of users to create clusters without a template. - -By default, any standard user in Rancher can create clusters. But when RKE template enforcement is turned on, - -- Only an administrator has the ability to create clusters without a template. -- All standard users must use an RKE template to create a new cluster. -- Standard users cannot create a cluster without using a template. - -Users can only create new templates if the administrator [gives them permission.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creator-permissions/#allowing-a-user-to-create-templates) - -After a cluster is created with an RKE template, the cluster creator cannot edit settings that are defined in the template. The only way to change those settings after the cluster is created is to [upgrade the cluster to a new revision]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#updating-a-cluster-created-with-an-rke-template) of the same template. If cluster creators want to change template-defined settings, they would need to contact the template owner to get a new revision of the template. For details on how template revisions work, refer to the [documentation on revising templates.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#updating-a-template) - -# Requiring New Clusters to Use an RKE Template - -You might want to require new clusters to use a template to ensure that any cluster launched by a [standard user]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) will use the Kubernetes and/or Rancher settings that are vetted by administrators. - -To require new clusters to use an RKE template, administrators can turn on RKE template enforcement with the following steps: - -1. Click **☰ > Global Settings**. -1. Go to the `cluster-template-enforcement` setting. Click **⋮ > Edit Setting**. -1. Set the value to **True** and click **Save**. - - >**Important:** When the admin sets the `cluster-template-enforcement` to True, they also need to share the `clusterTemplates` with users so that users can select one of these templates to create the cluster. - -**Result:** All clusters provisioned by Rancher must use a template, unless the creator is an administrator. - -# Disabling RKE Template Enforcement - -To allow new clusters to be created without an RKE template, administrators can turn off RKE template enforcement with the following steps: - -1. Click **☰ > Global Settings**. -1. Go to the `cluster-template-enforcement` setting. Click **⋮ > Edit Setting**. -1. Set the value to **False** and click **Save**. - -**Result:** When clusters are provisioned by Rancher, they don't need to use a template. diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/example-scenarios/example-scenarios.md b/versioned_docs/version-2.6/admin-settings/rke-templates/example-scenarios/example-scenarios.md deleted file mode 100644 index 66631990aea..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/example-scenarios/example-scenarios.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Example Scenarios -weight: 5 ---- - -These example scenarios describe how an organization could use templates to standardize cluster creation. - -- **Enforcing templates:** Administrators might want to [enforce one or more template settings for everyone](#enforcing-a-template-setting-for-everyone) if they want all new Rancher-provisioned clusters to have those settings. -- **Sharing different templates with different users:** Administrators might give [different templates to basic and advanced users,](#templates-for-basic-and-advanced-users) so that basic users have more restricted options and advanced users have more discretion when creating clusters. -- **Updating template settings:** If an organization's security and DevOps teams decide to embed best practices into the required settings for new clusters, those best practices could change over time. If the best practices change, [a template can be updated to a new revision](#updating-templates-and-clusters-created-with-them) and clusters created from the template can upgrade to the new version of the template. -- **Sharing ownership of a template:** When a template owner no longer wants to maintain a template, or wants to delegate ownership of the template, this scenario describes how [template ownership can be shared.](#allowing-other-users-to-control-and-share-a-template) - - -# Enforcing a Template Setting for Everyone - -Let's say there is an organization in which the administrators decide that all new clusters should be created with Kubernetes version 1.14. - -1. First, an administrator creates a template which specifies the Kubernetes version as 1.14 and marks all other settings as **Allow User Override**. -1. The administrator makes the template public. -1. The administrator turns on template enforcement. - -**Results:** - -- All Rancher users in the organization have access to the template. -- All new clusters created by [standard users]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) with this template will use Kubernetes 1.14 and they are unable to use a different Kubernetes version. By default, standard users don't have permission to create templates, so this template will be the only template they can use unless more templates are shared with them. -- All standard users must use a cluster template to create a new cluster. They cannot create a cluster without using a template. - -In this way, the administrators enforce the Kubernetes version across the organization, while still allowing end users to configure everything else. - -# Templates for Basic and Advanced Users - -Let's say an organization has both basic and advanced users. Administrators want the basic users to be required to use a template, while the advanced users and administrators create their clusters however they want. - -1. First, an administrator turns on [RKE template enforcement.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/enforcement/#requiring-new-clusters-to-use-an-rke-template) This means that every [standard user]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) in Rancher will need to use an RKE template when they create a cluster. -1. The administrator then creates two templates: - - - One template for basic users, with almost every option specified except for access keys - - One template for advanced users, which has most or all options has **Allow User Override** turned on - -1. The administrator shares the advanced template with only the advanced users. -1. The administrator makes the template for basic users public, so the more restrictive template is an option for everyone who creates a Rancher-provisioned cluster. - -**Result:** All Rancher users, except for administrators, are required to use a template when creating a cluster. Everyone has access to the restrictive template, but only advanced users have permission to use the more permissive template. The basic users are more restricted, while advanced users have more freedom when configuring their Kubernetes clusters. - -# Updating Templates and Clusters Created with Them - -Let's say an organization has a template that requires clusters to use Kubernetes v1.14. However, as time goes on, the administrators change their minds. They decide they want users to be able to upgrade their clusters to use newer versions of Kubernetes. - -In this organization, many clusters were created with a template that requires Kubernetes v1.14. Because the template does not allow that setting to be overridden, the users who created the cluster cannot directly edit that setting. - -The template owner has several options for allowing the cluster creators to upgrade Kubernetes on their clusters: - -- **Specify Kubernetes v1.15 on the template:** The template owner can create a new template revision that specifies Kubernetes v1.15. Then the owner of each cluster that uses that template can upgrade their cluster to a new revision of the template. This template upgrade allows the cluster creator to upgrade Kubernetes to v1.15 on their cluster. -- **Allow any Kubernetes version on the template:** When creating a template revision, the template owner can also mark the the Kubernetes version as **Allow User Override** using the switch near that setting on the Rancher UI. This will allow clusters that upgrade to this template revision to use any version of Kubernetes. -- **Allow the latest minor Kubernetes version on the template:** The template owner can also create a template revision in which the Kubernetes version is defined as **Latest v1.14 (Allows patch version upgrades)**. This means clusters that use that revision will be able to get patch version upgrades, but major version upgrades will not be allowed. - -# Allowing Other Users to Control and Share a Template - -Let's say Alice is a Rancher administrator. She owns an RKE template that reflects her organization's agreed-upon best practices for creating a cluster. - -Bob is an advanced user who can make informed decisions about cluster configuration. Alice trusts Bob to create new revisions of her template as the best practices get updated over time. Therefore, she decides to make Bob an owner of the template. - -To share ownership of the template with Bob, Alice [adds Bob as an owner of her template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing/#sharing-ownership-of-templates) - -The result is that as a template owner, Bob is in charge of version control for that template. Bob can now do all of the following: - -- [Revise the template]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#updating-a-template) when the best practices change -- [Disable outdated revisions]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#disabling-a-template-revision) of the template so that no new clusters can be created with it -- [Delete the whole template]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#deleting-a-template) if the organization wants to go in a different direction -- [Set a certain revision as default]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#setting-a-template-revision-as-default) when users create a cluster with it. End users of the template will still be able to choose which revision they want to create the cluster with. -- [Share the template]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing) with specific users, make the template available to all Rancher users, or share ownership of the template with another user. \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/example-yaml/example-yaml.md b/versioned_docs/version-2.6/admin-settings/rke-templates/example-yaml/example-yaml.md deleted file mode 100644 index 3c85e86d616..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/example-yaml/example-yaml.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: Example YAML -weight: 60 ---- - -Below is an example RKE template configuration file for reference. - -The YAML in the RKE template uses the same customization that is used when you create an RKE cluster. However, since the YAML is within the context of a Rancher provisioned RKE cluster, the customization from the RKE docs needs to be nested under the `rancher_kubernetes_engine` directive. - -```yaml -# -# Cluster Config -# -docker_root_dir: /var/lib/docker - -enable_cluster_alerting: false -# This setting is not enforced. Clusters -# created with this sample template -# would have alerting turned off by default, -# but end users could still turn alerting -# on or off. - -enable_cluster_monitoring: true -# This setting is not enforced. Clusters -# created with this sample template -# would have monitoring turned on -# by default, but end users could still -# turn monitoring on or off. - -enable_network_policy: false -local_cluster_auth_endpoint: - enabled: true -# -# Rancher Config -# -rancher_kubernetes_engine_config: # Your RKE template config goes here. - addon_job_timeout: 30 - authentication: - strategy: x509 - ignore_docker_version: true -# -# # Currently only nginx ingress provider is supported. -# # To disable ingress controller, set `provider: none` -# # To enable ingress on specific nodes, use the node_selector, eg: -# provider: nginx -# node_selector: -# app: ingress -# - ingress: - provider: nginx - kubernetes_version: v1.15.3-rancher3-1 - monitoring: - provider: metrics-server -# -# If you are using calico on AWS -# -# network: -# plugin: calico -# calico_network_provider: -# cloud_provider: aws -# -# # To specify flannel interface -# -# network: -# plugin: flannel -# flannel_network_provider: -# iface: eth1 -# -# # To specify flannel interface for canal plugin -# -# network: -# plugin: canal -# canal_network_provider: -# iface: eth1 -# - network: - options: - flannel_backend_type: vxlan - plugin: canal -# -# services: -# kube-api: -# service_cluster_ip_range: 10.43.0.0/16 -# kube-controller: -# cluster_cidr: 10.42.0.0/16 -# service_cluster_ip_range: 10.43.0.0/16 -# kubelet: -# cluster_domain: cluster.local -# cluster_dns_server: 10.43.0.10 -# - services: - etcd: - backup_config: - enabled: true - interval_hours: 12 - retention: 6 - safe_timestamp: false - creation: 12h - extra_args: - election-timeout: 5000 - heartbeat-interval: 500 - gid: 0 - retention: 72h - snapshot: false - uid: 0 - kube_api: - always_pull_images: false - pod_security_policy: false - service_node_port_range: 30000-32767 - ssh_agent_auth: false -windows_prefered_cluster: false -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/overrides/overrides.md b/versioned_docs/version-2.6/admin-settings/rke-templates/overrides/overrides.md deleted file mode 100644 index bce495f617d..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/overrides/overrides.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Overriding Template Settings -weight: 33 ---- - -When a user creates an RKE template, each setting in the template has a switch in the Rancher UI that indicates if users can override the setting. This switch marks those settings as **Allow User Override**. - -After a cluster is created with a template, end users can't update any of the settings defined in the template unless the template owner marked them as **Allow User Override**. However, if the template is [updated to a new revision]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising) that changes the settings or allows end users to change them, the cluster can be upgraded to a new revision of the template and the changes in the new revision will be applied to the cluster. - -When any parameter is set as **Allow User Override** on the RKE template, it means that end users have to fill out those fields during cluster creation and they can edit those settings afterward at any time. - -The **Allow User Override** model of the RKE template is useful for situations such as: - -- Administrators know that some settings will need the flexibility to be frequently updated over time -- End users will need to enter their own access keys or secret keys, for example, cloud credentials or credentials for backup snapshots \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates-and-hardware/rke-templates-and-hardware.md b/versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates-and-hardware/rke-templates-and-hardware.md deleted file mode 100644 index 8e10bf7ea38..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates-and-hardware/rke-templates-and-hardware.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: RKE Templates and Infrastructure -weight: 90 ---- - -In Rancher, RKE templates are used to provision Kubernetes and define Rancher settings, while node templates are used to provision nodes. - -Therefore, even if RKE template enforcement is turned on, the end user still has flexibility when picking the underlying hardware when creating a Rancher cluster. The end users of an RKE template can still choose an infrastructure provider and the nodes they want to use. - -If you want to standardize the hardware in your clusters, use RKE templates conjunction with node templates or with a server provisioning tool such as Terraform. - -### Node Templates - -[Node templates]({{}}/rancher/v2.6/en/user-settings/node-templates) are responsible for node configuration and node provisioning in Rancher. From your user profile, you can set up node templates to define which templates are used in each of your node pools. With node pools enabled, you can make sure you have the required number of nodes in each node pool, and ensure that all nodes in the pool are the same. - -### Terraform - -Terraform is a server provisioning tool. It uses infrastructure-as-code that lets you create almost every aspect of your infrastructure with Terraform configuration files. It can automate the process of server provisioning in a way that is self-documenting and easy to track in version control. - -This section focuses on how to use Terraform with the [Rancher 2 Terraform provider](https://www.terraform.io/docs/providers/rancher2/), which is a recommended option to standardize the hardware for your Kubernetes clusters. If you use the Rancher Terraform provider to provision hardware, and then use an RKE template to provision a Kubernetes cluster on that hardware, you can quickly create a comprehensive, production-ready cluster. - -Terraform allows you to: - -- Define almost any kind of infrastructure-as-code, including servers, databases, load balancers, monitoring, firewall settings, and SSL certificates -- Leverage catalog apps and multi-cluster apps -- Codify infrastructure across many platforms, including Rancher and major cloud providers -- Commit infrastructure-as-code to version control -- Easily repeat configuration and setup of infrastructure -- Incorporate infrastructure changes into standard development practices -- Prevent configuration drift, in which some servers become configured differently than others - -# How Does Terraform Work? - -Terraform is written in files with the extension `.tf`. It is written in HashiCorp Configuration Language, which is a declarative language that lets you define the infrastructure you want in your cluster, the cloud provider you are using, and your credentials for the provider. Then Terraform makes API calls to the provider in order to efficiently create that infrastructure. - -To create a Rancher-provisioned cluster with Terraform, go to your Terraform configuration file and define the provider as Rancher 2. You can set up your Rancher 2 provider with a Rancher API key. Note: The API key has the same permissions and access level as the user it is associated with. - -Then Terraform calls the Rancher API to provision your infrastructure, and Rancher calls the infrastructure provider. As an example, if you wanted to use Rancher to provision infrastructure on AWS, you would provide both your Rancher API key and your AWS credentials in the Terraform configuration file or in environment variables so that they could be used to provision the infrastructure. - -When you need to make changes to your infrastructure, instead of manually updating the servers, you can make changes in the Terraform configuration files. Then those files can be committed to version control, validated, and reviewed as necessary. Then when you run `terraform apply`, the changes would be deployed. - -# Tips for Working with Terraform - -- There are examples of how to provide most aspects of a cluster in the [documentation for the Rancher 2 provider.](https://www.terraform.io/docs/providers/rancher2/) - -- In the Terraform settings, you can install Docker Machine by using the Docker Machine node driver. - -- You can also modify auth in the Terraform provider. - -- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure. - -- If you want to manage Kubernetes cluster settings, Rancher settings, and hardware settings all in one place, use [Terraform modules](https://github.com/rancher/terraform-modules). You can pass a cluster configuration YAML file or an RKE template configuration file to a Terraform module so that the Terraform module will create it. In that case, you could use your infrastructure-as-code to manage the version control and revision history of both your Kubernetes cluster and its underlying hardware. - -# Tip for Creating CIS Benchmark Compliant Clusters - -This section describes one way that you can make security and compliance-related config files standard in your clusters. - -When you create a [CIS benchmark compliant cluster,]({{}}/rancher/v2.6/en/security/) you have an encryption config file and an audit log config file. - -Your infrastructure provisioning system can write those files to disk. Then in your RKE template, you would specify where those files will be, then add your encryption config file and audit log config file as extra mounts to the `kube-api-server`. - -Then you would make sure that the `kube-api-server` flag in your RKE template uses your CIS-compliant config files. - -In this way, you can create flags that comply with the CIS benchmark. - -# Resources - -- [Terraform documentation](https://www.terraform.io/docs/) -- [Rancher2 Terraform provider documentation](https://www.terraform.io/docs/providers/rancher2/) -- [The RanchCast - Episode 1: Rancher 2 Terraform Provider](https://youtu.be/YNCq-prI8-8): In this demo, Director of Community Jason van Brackel walks through using the Rancher 2 Terraform Provider to provision nodes and create a custom cluster. \ No newline at end of file diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates.md b/versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates.md deleted file mode 100644 index 9d259bcc1bf..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/rke-templates.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: RKE Templates -weight: 80 ---- - -RKE templates are designed to allow DevOps and security teams to standardize and simplify the creation of Kubernetes clusters. - -RKE is the [Rancher Kubernetes Engine,]({{}}/rke/latest/en/) which is the tool that Rancher uses to provision Kubernetes clusters. - -With Kubernetes increasing in popularity, there is a trend toward managing a larger number of smaller clusters. When you want to create many clusters, it’s more important to manage them consistently. Multi-cluster management comes with challenges to enforcing security and add-on configurations that need to be standardized before turning clusters over to end users. - -RKE templates help standardize these configurations. Regardless of whether clusters are created with the Rancher UI, the Rancher API, or an automated process, Rancher will guarantee that every cluster it provisions from an RKE template is uniform and consistent in the way it is produced. - -Admins control which cluster options can be changed by end users. RKE templates can also be shared with specific users and groups, so that admins can create different RKE templates for different sets of users. - -If a cluster was created with an RKE template, you can't change it to a different RKE template. You can only update the cluster to a new revision of the same template. - -You can [save the configuration of an existing cluster as an RKE template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#converting-an-existing-cluster-to-use-an-rke-template) Then the cluster's settings can only be changed if the template is updated. The new template can also be used to launch new clusters. - -The core features of RKE templates allow DevOps and security teams to: - -- Standardize cluster configuration and ensure that Rancher-provisioned clusters are created following best practices -- Prevent less technical users from making uninformed choices when provisioning clusters -- Share different templates with different sets of users and groups -- Delegate ownership of templates to users who are trusted to make changes to them -- Control which users can create templates -- Require users to create clusters from a template - -# Configurable Settings - -RKE templates can be created in the Rancher UI or defined in YAML format. They can define all the same parameters that can be specified when you use Rancher to provision custom nodes or nodes from an infrastructure provider: - -- Cloud provider options -- Pod security options -- Network providers -- Ingress controllers -- Network security configuration -- Network plugins -- Private registry URL and credentials -- Add-ons -- Kubernetes options, including configurations for Kubernetes components such as kube-api, kube-controller, kubelet, and services - -The [add-on section](#add-ons) of an RKE template is especially powerful because it allows a wide range of customization options. - -# Scope of RKE Templates - -RKE templates are supported for Rancher-provisioned clusters. The templates can be used to provision custom clusters or clusters that are launched by an infrastructure provider. - -RKE templates are for defining Kubernetes and Rancher settings. Node templates are responsible for configuring nodes. For tips on how to use RKE templates in conjunction with hardware, refer to [RKE Templates and Hardware]({{}}/rancher/v2.6/en/admin-settings/rke-templates/rke-templates-and-hardware). - -RKE templates can be created from scratch to pre-define cluster configuration. They can be applied to launch new clusters, or templates can also be exported from existing running clusters. - -The settings of an existing cluster can be [saved as an RKE template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#converting-an-existing-cluster-to-use-an-rke-template) This creates a new template and binds the cluster settings to the template, so that the cluster can only be upgraded if the [template is updated]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#updating-a-template), and the cluster is upgraded to [use a newer version of the template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#upgrading-a-cluster-to-use-a-new-template-revision) The new template can also be used to create new clusters. - - -# Example Scenarios -When an organization has both basic and advanced Rancher users, administrators might want to give the advanced users more options for cluster creation, while restricting the options for basic users. - -These [example scenarios]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-scenarios) describe how an organization could use templates to standardize cluster creation. - -Some of the example scenarios include the following: - -- **Enforcing templates:** Administrators might want to [enforce one or more template settings for everyone]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-scenarios/#enforcing-a-template-setting-for-everyone) if they want all new Rancher-provisioned clusters to have those settings. -- **Sharing different templates with different users:** Administrators might give [different templates to basic and advanced users,]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-scenarios/#templates-for-basic-and-advanced-users) so that basic users can have more restricted options and advanced users can use more discretion when creating clusters. -- **Updating template settings:** If an organization's security and DevOps teams decide to embed best practices into the required settings for new clusters, those best practices could change over time. If the best practices change, [a template can be updated to a new revision]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-scenarios/#updating-templates-and-clusters-created-with-them) and clusters created from the template can [upgrade to the new version]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/#upgrading-a-cluster-to-use-a-new-template-revision) of the template. -- **Sharing ownership of a template:** When a template owner no longer wants to maintain a template, or wants to share ownership of the template, this scenario describes how [template ownership can be shared.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-scenarios/#allowing-other-users-to-control-and-share-a-template) - -# Template Management - -When you create an RKE template, it is available in the Rancher UI from the **Cluster Management** view under **RKE Templates**. When you create a template, you become the template owner, which gives you permission to revise and share the template. You can share the RKE templates with specific users or groups, and you can also make it public. - -Administrators can turn on template enforcement to require users to always use RKE templates when creating a cluster. This allows administrators to guarantee that Rancher always provisions clusters with specific settings. - -RKE template updates are handled through a revision system. If you want to change or update a template, you create a new revision of the template. Then a cluster that was created with the older version of the template can be upgraded to the new template revision. - -In an RKE template, settings can be restricted to what the template owner chooses, or they can be open for the end user to select the value. The difference is indicated by the **Allow User Override** toggle over each setting in the Rancher UI when the template is created. - -For the settings that cannot be overridden, the end user will not be able to directly edit them. In order for a user to get different options of these settings, an RKE template owner would need to create a new revision of the RKE template, which would allow the user to upgrade and change that option. - -The documents in this section explain the details of RKE template management: - -- [Getting permission to create templates]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creator-permissions/) -- [Creating and revising templates]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising/) -- [Enforcing template settings](./enforcement/#requiring-new-clusters-to-use-an-rke-template) -- [Overriding template settings]({{}}/rancher/v2.6/en/admin-settings/rke-templates/overrides/) -- [Sharing templates with cluster creators]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing/#sharing-templates-with-specific-users-or-groups) -- [Sharing ownership of a template]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing/#sharing-ownership-of-templates) - -An [example YAML configuration file for a template]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-yaml) is provided for reference. - -# Applying Templates - -You can [create a cluster from a template]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#creating-a-cluster-from-an-rke-template) that you created, or from a template that has been [shared with you.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/template-access-and-sharing) - -If the RKE template owner creates a new revision of the template, you can [upgrade your cluster to that revision.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#updating-a-cluster-created-with-an-rke-template) - -RKE templates can be created from scratch to pre-define cluster configuration. They can be applied to launch new clusters, or templates can also be exported from existing running clusters. - -You can [save the configuration of an existing cluster as an RKE template.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/applying-templates/#converting-an-existing-cluster-to-use-an-rke-template) Then the cluster's settings can only be changed if the template is updated. - -# Standardizing Hardware - -RKE templates are designed to standardize Kubernetes and Rancher settings. If you want to standardize your infrastructure as well, one option is to use RKE templates [in conjunction with other tools]({{}}/rancher/v2.6/en/admin-settings/rke-templates/rke-templates-and-hardware). - -Another option is to use [cluster templates,]({{}}/rancher/v2.6/en/admin-settings/cluster-templates) which include node pool configuration options, but don't provide configuration enforcement. - -# YAML Customization - -If you define an RKE template as a YAML file, you can modify this [example RKE template YAML]({{}}/rancher/v2.6/en/admin-settings/rke-templates/example-yaml). The YAML in the RKE template uses the same customization that Rancher uses when creating an RKE cluster, but since the YAML is located within the context of a Rancher provisioned cluster, you will need to nest the RKE template customization under the `rancher_kubernetes_engine_config` directive in the YAML. - -The RKE documentation also has [annotated]({{}}/rke/latest/en/example-yamls/) `cluster.yml` files that you can use for reference. - -For guidance on available options, refer to the RKE documentation on [cluster configuration.]({{}}/rke/latest/en/config-options/) - -### Add-ons - -The add-on section of the RKE template configuration file works the same way as the [add-on section of a cluster configuration file]({{}}/rke/latest/en/config-options/add-ons/). - -The user-defined add-ons directive allows you to either call out and pull down Kubernetes manifests or put them inline directly. If you include these manifests as part of your RKE template, Rancher will provision those in the cluster. - -Some things you could do with add-ons include: - -- Install applications on the Kubernetes cluster after it starts -- Install plugins on nodes that are deployed with a Kubernetes daemonset -- Automatically set up namespaces, service accounts, or role binding - -The RKE template configuration must be nested within the `rancher_kubernetes_engine_config` directive. To set add-ons, when creating the template, you will click **Edit as YAML**. Then use the `addons` directive to add a manifest, or the `addons_include` directive to set which YAML files are used for the add-ons. For more information on custom add-ons, refer to the [user-defined add-ons documentation.]({{}}/rke/latest/en/config-options/add-ons/user-defined-add-ons/) diff --git a/versioned_docs/version-2.6/admin-settings/rke-templates/template-access-and-sharing/template-access-and-sharing.md b/versioned_docs/version-2.6/admin-settings/rke-templates/template-access-and-sharing/template-access-and-sharing.md deleted file mode 100644 index 8784d5cfcd3..00000000000 --- a/versioned_docs/version-2.6/admin-settings/rke-templates/template-access-and-sharing/template-access-and-sharing.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Access and Sharing -weight: 31 ---- - -If you are an RKE template owner, you can share it with users or groups of users, who can then use the template to create clusters. - -Since RKE templates are specifically shared with users and groups, owners can share different RKE templates with different sets of users. - -When you share a template, each user can have one of two access levels: - -- **Owner:** This user can update, delete, and share the templates that they own. The owner can also share the template with other users. -- **User:** These users can create clusters using the template. They can also upgrade those clusters to new revisions of the same template. When you share a template as **Make Public (read-only),** all users in your Rancher setup have the User access level for the template. - -If you create a template, you automatically become an owner of that template. - -If you want to delegate responsibility for updating the template, you can share ownership of the template. For details on how owners can modify templates, refer to the [documentation about revising templates.]({{}}/rancher/v2.6/en/admin-settings/rke-templates/creating-and-revising) - -There are several ways to share templates: - -- Add users to a new RKE template during template creation -- Add users to an existing RKE template -- Make the RKE template public, sharing it with all users in the Rancher setup -- Share template ownership with users who are trusted to modify the template - -### Sharing Templates with Specific Users or Groups - -To allow users or groups to create clusters using your template, you can give them the basic **User** access level for the template. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Under **RKE1 configuration**, click **RKE Templates**. -1. Go to the template that you want to share and click the **⋮ > Edit**. -1. In the **Share Template** section, click on **Add Member**. -1. Search in the **Name** field for the user or group you want to share the template with. -1. Choose the **User** access type. -1. Click **Save**. - -**Result:** The user or group can create clusters using the template. - -### Sharing Templates with All Users - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the left navigation menu, click **RKE1 Configuration > RKE Templates**. -1. Go to the template that you want to share and click the **⋮ > Edit**. -1. Under **Share Template,** check the box for **Make Public (read-only)**. -1. Click **Save**. - -**Result:** All users in the Rancher setup can create clusters using the template. - -### Sharing Ownership of Templates - -If you are the creator of a template, you might want to delegate responsibility for maintaining and updating a template to another user or group. - -In that case, you can give users the Owner access type, which allows another user to update your template, delete it, or share access to it with other users. - -To give Owner access to a user or group, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Under **RKE1 configuration**, click **RKE Templates**. -1. Go to the RKE template that you want to share and click the **⋮ > Edit**. -1. Under **Share Template**, click on **Add Member** and search in the **Name** field for the user or group you want to share the template with. -1. In the **Access Type** field, click **Owner**. -1. Click **Save**. - -**Result:** The user or group has the Owner access type, and can modify, share, or delete the template. \ No newline at end of file diff --git a/versioned_docs/version-2.6/api/api-tokens/api-tokens.md b/versioned_docs/version-2.6/api/api-tokens/api-tokens.md deleted file mode 100644 index c682ae8460d..00000000000 --- a/versioned_docs/version-2.6/api/api-tokens/api-tokens.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: API Tokens -weight: 1 ---- - -By default, some cluster-level API tokens are generated with infinite time-to-live (`ttl=0`). In other words, API tokens with `ttl=0` never expire unless you invalidate them. Tokens are not invalidated by changing a password. - -You can deactivate API tokens by deleting them or by deactivating the user account. - -### Deleting tokens -To delete a token, - -1. Go to the list of all tokens in the Rancher API view at `https:///v3/tokens`. - -1. Access the token you want to delete by its ID. For example, `https:///v3/tokens/kubectl-shell-user-vqkqt` - -1. Click **Delete**. - -Here is the complete list of tokens that are generated with `ttl=0`: - -| Token | Description | -|-------|-------------| -| `kubeconfig-*` | Kubeconfig token | -| `kubectl-shell-*` | Access to `kubectl` shell in the browser | -| `agent-*` | Token for agent deployment | -| `compose-token-*` | Token for compose | -| `helm-token-*` | Token for Helm chart deployment | -| `*-pipeline*` | Pipeline token for project | -| `telemetry-*` | Telemetry token | -| `drain-node-*` | Token for drain (we use `kubectl` for drain because there is no native Kubernetes API) | - - -### Setting TTL on Kubeconfig Tokens - -Admins can set a global TTL on Kubeconfig tokens. Once the token expires the kubectl command will require the user to authenticate to Rancher. - -Go to the global settings and: - -1. Set the `kubeconfig-generate-token` setting to `false`. This setting instructs Rancher to no longer automatically generate a token when a user clicks on download a kubeconfig file. The kubeconfig file will now provide a command to login to Rancher. - -_**Note:**_ Once this setting is deactivated, a generated kubeconfig will reference the [Rancher CLI]({{}}/rancher/v2.6/en/cli) to retrieve a short lived token for the cluster. When you use this kubeconfig in a client, such as `kubectl`, the Rancher CLI needs to be installed as well. - -2. Set the `kubeconfig-token-ttl-minutes` setting to the desired duration in minutes. By default, `kubeconfig-token-ttl-minutes` is 960 (16 hours). - -_**Note:**_ This value cannot exceed max-ttl of API tokens.(`https://}}/rancher/v2.6/en/installation/resources/feature-flags). - -This feature will affect all tokens which include, but are not limited to, the following: - -- Kubeconfig tokens -- Bearer tokens API keys/calls -- Tokens used by internal operations - diff --git a/versioned_docs/version-2.6/api/api.md b/versioned_docs/version-2.6/api/api.md deleted file mode 100644 index 746895d3d01..00000000000 --- a/versioned_docs/version-2.6/api/api.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: API -weight: 24 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -## How to use the API - -The API has its own user interface accessible from a web browser. This is an easy way to see resources, perform actions, and see the equivalent cURL or HTTP request & response. To access it: - - - - -1. Click on your user avatar in the upper right corner. -1. Click **Account & API Keys**. -1. Under the **API Keys** section, find the **API Endpoint** field and click the link. The link will look something like `https:///v3`, where `` is the fully qualified domain name of your Rancher deployment. - - - - -Go to the URL endpoint at `https:///v3`, where `` is the fully qualified domain name of your Rancher deployment. - - - - -## Authentication - -API requests must include authentication information. Authentication is done with HTTP basic authentication using [API Keys]({{}}/rancher/v2.6/en/user-settings/api-keys/). API keys can create new clusters and have access to multiple clusters via `/v3/clusters/`. [Cluster and project roles]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/) apply to these keys and restrict what clusters and projects the account can see and what actions they can take. - -By default, some cluster-level API tokens are generated with infinite time-to-live (`ttl=0`). In other words, API tokens with `ttl=0` never expire unless you invalidate them. For details on how to invalidate them, refer to the [API tokens page]({{}}/rancher/v2.6/en/api/api-tokens). - -## Making requests - -The API is generally RESTful but has several features to make the definition of everything discoverable by a client so that generic clients can be written instead of having to write specific code for every type of resource. For detailed info about the generic API spec, [see here](https://github.com/rancher/api-spec/blob/master/specification.md). - -- Every type has a Schema which describes: - - The URL to get to the collection of this type of resources - - Every field the resource can have, along with their type, basic validation rules, whether they are required or optional, etc. - - Every action that is possible on this type of resource, with their inputs and outputs (also as schemas). - - Every field that filtering is allowed on - - What HTTP verb methods are available for the collection itself, or for individual resources in the collection. - - -- So the theory is that you can load just the list of schemas and know everything about the API. This is in fact how the UI for the API works, it contains no code specific to Rancher itself. The URL to get Schemas is sent in every HTTP response as a `X-Api-Schemas` header. From there you can follow the `collection` link on each schema to know where to list resources, and other `links` inside of the returned resources to get any other information. - -- In practice, you will probably just want to construct URL strings. We highly suggest limiting this to the top-level to list a collection (`/v3/`) or get a specific resource (`/v3//`). Anything deeper than that is subject to change in future releases. - -- Resources have relationships between each other called links. Each resource includes a map of `links` with the name of the link and the URL to retrieve that information. Again you should `GET` the resource and then follow the URL in the `links` map, not construct these strings yourself. - -- Most resources have actions, which do something or change the state of the resource. To use these, send a HTTP `POST` to the URL in the `actions` map for the action you want. Some actions require input or produce output, see the individual documentation for each type or the schemas for specific information. - -- To edit a resource, send a HTTP `PUT` to the `links.update` link on the resource with the fields that you want to change. If the link is missing then you don't have permission to update the resource. Unknown fields and ones that are not editable are ignored. - -- To delete a resource, send a HTTP `DELETE` to the `links.remove` link on the resource. If the link is missing then you don't have permission to update the resource. - -- To create a new resource, HTTP `POST` to the collection URL in the schema (which is `/v3/`). - -## Filtering - -Most collections can be filtered on the server-side by common fields using HTTP query parameters. The `filters` map shows you what fields can be filtered on and what the filtered values were for the request you made. The API UI has controls to setup filtering and show you the appropriate request. For simple "equals" matches it's just `field=value`. Modifiers can be added to the field name, e.g. `field_gt=42` for "field is greater than 42". See the [API spec](https://github.com/rancher/api-spec/blob/master/specification.md#filtering) for full details. - -## Sorting - -Most collections can be sorted on the server-side by common fields using HTTP query parameters. The `sortLinks` map shows you what sorts are available, along with the URL to get the collection sorted by that. It also includes info about what the current response was sorted by, if specified. - -## Pagination - -API responses are paginated with a limit of 100 resources per page by default. This can be changed with the `limit` query parameter, up to a maximum of 1000, e.g. `/v3/pods?limit=1000`. The `pagination` map in collection responses tells you whether or not you have the full result set and has a link to the next page if you do not. - -## Capturing Rancher API Calls - -You can use browser developer tools to capture how the Rancher API is called. For example, you could follow these steps to use the Chrome developer tools to get the API call for provisioning an RKE cluster: - -1. In the Rancher UI, go to **Cluster Management** and click **Create.** -1. Click one of the cluster types. This example uses Digital Ocean. -1. Fill out the form with a cluster name and node template, but don't click **Create**. -1. You will need to open the developer tools before the cluster creation to see the API call being recorded. To open the tools, right-click on the Rancher UI and click **Inspect.** -1. In the developer tools, click the **Network** tab. -1. On the **Network** tab, make sure **Fetch/XHR** is selected. -1. In the Rancher UI, click **Create**. In the developer tools, you should see a new network request with the name `cluster?_replace=true`. -1. Right-click `cluster?_replace=true` and click **Copy > Copy as cURL.** -1. Paste the result into any text editor. You will be able to see the POST request, including the URL it was sent to, all of the headers, and the full body of the request. This command can be used to create a cluster from the command line. Note: The request should be stored in a safe place because it contains credentials. diff --git a/versioned_docs/version-2.6/backups/back-up-rancher/back-up-rancher.md b/versioned_docs/version-2.6/backups/back-up-rancher/back-up-rancher.md deleted file mode 100644 index 629a7ad2c64..00000000000 --- a/versioned_docs/version-2.6/backups/back-up-rancher/back-up-rancher.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Backing up Rancher -weight: 1 ---- - -In this section, you'll learn how to back up Rancher running on any Kubernetes cluster. To backup Rancher installed with Docker, refer the instructions for [single node backups]({{}}/rancher/v2.6/en/backups/docker-installs/docker-backups) - -The backup-restore operator needs to be installed in the local cluster, and only backs up the Rancher app. The backup and restore operations are performed only in the local Kubernetes cluster. - -Note that the rancher-backup operator version 2.x.x is for Rancher v2.6.x. - -> When restoring a backup into a new Rancher setup, the version of the new setup should be the same as the one where the backup is made. The Kubernetes version should also be considered when restoring a backup, since the supported apiVersion in the cluster and in the backup file could be different. - -### Prerequisites - -The Rancher version must be v2.5.0 and up. - -Refer [here]({{}}/rancher/v2.6/en/backups/migrating-rancher/#2-restore-from-backup-using-a-restore-custom-resource) for help on restoring an existing backup file into a v1.22 cluster in Rancher v2.6.3. - -### 1. Install the Rancher Backups operator - -The backup storage location is an operator-level setting, so it needs to be configured when the Rancher Backups application is installed or upgraded. - -Backups are created as .tar.gz files. These files can be pushed to S3 or Minio, or they can be stored in a persistent volume. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the `local` cluster and click **Explore**. The `local` cluster runs the Rancher server. -1. Click **Apps & Marketplace > Charts**. -1. Click **Rancher Backups**. -1. Click **Install**. -1. Configure the default storage location. For help, refer to the [storage configuration section.](../configuration/storage-config) -1. Click **Install**. - ->**NOTE:** There is a known issue in Fleet that occurs after performing a restoration using the backup-restore-operator: Secrets used for clientSecretName and helmSecretName are not included in Fleet gitrepos. Refer [here]({{}}rancher/v2.6/en/deploy-across-clusters/fleet/#troubleshooting) for a workaround. - -### 2. Perform a Backup - -To perform a backup, a custom resource of type Backup must be created. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the `local` cluster and click **Explore**. -1. In the left navigation bar, click **Rancher Backups > Backups**. -1. Click **Create**. -1. Create the Backup with the form, or with the YAML editor. -1. For configuring the Backup details using the form, click **Create** and refer to the [configuration reference](../configuration/backup-config) and to the [examples.](../examples/#backup) -1. For using the YAML editor, we can click **Create > Create from YAML**. Enter the Backup YAML. This example Backup custom resource would create encrypted recurring backups in S3. The app uses the `credentialSecretNamespace` value to determine where to look for the S3 backup secret: - - ```yaml - apiVersion: resources.cattle.io/v1 - kind: Backup - metadata: - name: s3-recurring-backup - spec: - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: rancher - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig - schedule: "@every 1h" - retentionCount: 10 - ``` - - > **Note:** When creating the Backup resource using YAML editor, the `resourceSetName` must be set to `rancher-resource-set` - - For help configuring the Backup, refer to the [configuration reference](../configuration/backup-config) and to the [examples.](../examples/#backup) - - > **Important:** The `rancher-backup` operator doesn't save the EncryptionConfiguration file. The contents of the EncryptionConfiguration file must be saved when an encrypted backup is created, and the same file must be used when restoring from this backup. -1. Click **Create**. - -**Result:** The backup file is created in the storage location configured in the Backup custom resource. The name of this file is used when performing a restore. - diff --git a/versioned_docs/version-2.6/backups/backups.md b/versioned_docs/version-2.6/backups/backups.md deleted file mode 100644 index d9e4dd96065..00000000000 --- a/versioned_docs/version-2.6/backups/backups.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: Backups and Disaster Recovery -weight: 5 ---- - -In this section, you'll learn how to create backups of Rancher, how to restore Rancher from backup, and how to migrate Rancher to a new Kubernetes cluster. - -The `rancher-backup` operator is used to backup and restore Rancher on any Kubernetes cluster. This application is a Helm chart, and it can be deployed through the Rancher **Apps & Marketplace** page, or by using the Helm CLI. The `rancher-backup` Helm chart is [here.](https://github.com/rancher/charts/tree/release-v2.6/charts/rancher-backup) - -The backup-restore operator needs to be installed in the local cluster, and only backs up the Rancher app. The backup and restore operations are performed only in the local Kubernetes cluster. - -- [Backup and Restore for Rancher installed with Docker](#backup-and-restore-for-rancher-installed-with-docker) -- [How Backups and Restores Work](#how-backups-and-restores-work) -- [Installing the rancher-backup Operator](#installing-the-rancher-backup-operator) - - [Installing rancher-backup with the Rancher UI](#installing-rancher-backup-with-the-rancher-ui) - - [Installing rancher-backup with the Helm CLI](#installing-rancher-backup-with-the-helm-cli) - - [RBAC](#rbac) -- [Backing up Rancher](#backing-up-rancher) -- [Restoring Rancher](#restoring-rancher) -- [Migrating Rancher to a New Cluster](#migrating-rancher-to-a-new-cluster) -- [Default Storage Location Configuration](#default-storage-location-configuration) - - [Example values.yaml for the rancher-backup Helm Chart](#example-values-yaml-for-the-rancher-backup-helm-chart) - -# Backup and Restore for Rancher installed with Docker - -For Rancher installed with Docker, refer to [this page](./docker-installs/docker-backups) to perform backups and [this page](./docker-installs/docker-restores) to perform restores. - -# How Backups and Restores Work - -The `rancher-backup` operator introduces three custom resources: Backups, Restores, and ResourceSets. The following cluster-scoped custom resource definitions are added to the cluster: - -- `backups.resources.cattle.io` -- `resourcesets.resources.cattle.io` -- `restores.resources.cattle.io` - -The ResourceSet defines which Kubernetes resources need to be backed up. The ResourceSet is not available to be configured in the Rancher UI because the values required to back up Rancher are predefined. This ResourceSet should not be modified. - -When a Backup custom resource is created, the `rancher-backup` operator calls the `kube-apiserver` to get the resources in the ResourceSet (specifically, the predefined `rancher-resource-set`) that the Backup custom resource refers to. - -The operator then creates the backup file in the .tar.gz format and stores it in the location configured in the Backup resource. - -When a Restore custom resource is created, the operator accesses the backup .tar.gz file specified by the Restore, and restores the application from that file. - -The Backup and Restore custom resources can be created in the Rancher UI, or by using `kubectl apply`. - ->**Note:** Refer [here]({{}}/rancher/v2.6/en/backups/migrating-rancher/#2-restore-from-backup-using-a-restore-custom-resource) for help on restoring an existing backup file into a v1.22 cluster in Rancher v2.6.3. - -# Installing the rancher-backup Operator - -The `rancher-backup` operator can be installed from the Rancher UI, or with the Helm CLI. In both cases, the `rancher-backup` Helm chart is installed on the Kubernetes cluster running the Rancher server. It is a cluster-admin only feature and available only for the **local** cluster. (*If you do not see `rancher-backup` in the Rancher UI, you may have selected the wrong cluster.*) - ->**NOTE:** There is a known issue in Fleet that occurs after performing a restoration using the backup-restore-operator: Secrets used for clientSecretName and helmSecretName are not included in Fleet gitrepos. Refer [here]({{}}rancher/v2.6/en/deploy-across-clusters/fleet/#troubleshooting) for a workaround. - -### Installing rancher-backup with the Rancher UI - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the `local` cluster and click **Explore**. -1. In the left navigation bar, **Apps & Marketplace > Charts**. -1. Click **Rancher Backups**. -1. Click **Install**. -1. Optional: Configure the default storage location. For help, refer to the [configuration section.](./configuration/storage-config) -1. Click **Install**. - -**Result:** The `rancher-backup` operator is installed. - -From the **Cluster Dashboard,** you can see the `rancher-backup` operator listed under **Deployments**. - -To configure the backup app in Rancher, go to the left navigation menu and click **Rancher Backups**. - -### RBAC - -Only the rancher admins and the local cluster’s cluster-owner can: - -* Install the Chart -* See the navigation links for Backup and Restore CRDs -* Perform a backup or restore by creating a Backup CR and Restore CR respectively -* List backups/restores performed so far - -# Backing up Rancher - -A backup is performed by creating a Backup custom resource. For a tutorial, refer to [this page.](./back-up-rancher) - -# Restoring Rancher - -A restore is performed by creating a Restore custom resource. For a tutorial, refer to [this page.](./restoring-rancher) - -# Migrating Rancher to a New Cluster - -A migration is performed by following [these steps.]({{}}/rancher/v2.6/en/backups/migrating-rancher) - -# Default Storage Location Configuration - -Configure a storage location where all backups are saved by default. You will have the option to override this with each backup, but will be limited to using an S3-compatible or Minio object store. - -For information on configuring these options, refer to [this page.](./configuration/storage-config) - -### Example values.yaml for the rancher-backup Helm Chart - -The example [values.yaml file](./configuration/storage-config/#example-values-yaml-for-the-rancher-backup-helm-chart) can be used to configure the `rancher-backup` operator when the Helm CLI is used to install it. diff --git a/versioned_docs/version-2.6/backups/configuration/backup-config/backup-config.md b/versioned_docs/version-2.6/backups/configuration/backup-config/backup-config.md deleted file mode 100644 index 90d8e5680a0..00000000000 --- a/versioned_docs/version-2.6/backups/configuration/backup-config/backup-config.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -title: Backup Configuration -shortTitle: Backup -weight: 1 ---- - -The Backup Create page lets you configure a schedule, enable encryption and specify the storage location for your backups. - -- [Schedule](#schedule) -- [Encryption](#encryption) -- [Storage Location](#storage-location) - - [S3](#s3) - - [Example S3 Storage Configuration](#example-s3-storage-configuration) - - [Example MinIO Configuration](#example-minio-configuration) - - [Example credentialSecret](#example-credentialsecret) - - [IAM Permissions for EC2 Nodes to Access S3](#iam-permissions-for-ec2-nodes-to-access-s3) -- [Examples](#examples) - -# Schedule - -Select the first option to perform a one-time backup, or select the second option to schedule recurring backups. Selecting **Recurring Backups** lets you configure following two fields: - -- **Schedule**: This field accepts - - Standard [cron expressions](https://en.wikipedia.org/wiki/Cron), such as `"0 * * * *"` - - Descriptors, such as `"@midnight"` or `"@every 1h30m"` -- **Retention Count**: This value specifies how many backup files must be retained. If files exceed the given retentionCount, the oldest files will be deleted. The default value is 10. - -| YAML Directive Name | Description | -| ---------------- | ---------------- | -| `schedule` | Provide the cron string for scheduling recurring backups. | -| `retentionCount` | Provide the number of backup files to be retained. | - -# Encryption - -The rancher-backup gathers resources by making calls to the kube-apiserver. Objects returned by apiserver are decrypted, so even if [encryption At rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/) is enabled, even the encrypted objects gathered by the backup will be in plaintext. - -To avoid storing them in plaintext, you can use the same encryptionConfig file that was used for at-rest encryption, to encrypt certain resources in your backup. - -> **Important:** You must save the encryptionConfig file, because it won’t be saved by the rancher-backup operator. -The same encryptionFile needs to be used when performing a restore. - -The operator consumes this encryptionConfig as a Kubernetes Secret, and the Secret must be in the operator’s namespace. Rancher installs the `rancher-backup` operator in the `cattle-resources-system` namespace, so create this encryptionConfig secret in that namespace. - -For the `EncryptionConfiguration`, you can use the [sample file provided in the Kubernetes documentation.](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#understanding-the-encryption-at-rest-configuration) - -To create the Secret, the encryption configuration file must be named `encryption-provider-config.yaml`, and the `--from-file` flag must be used to create this secret. - -Save the `EncryptionConfiguration` in a file called `encryption-provider-config.yaml` and run this command: - -``` -kubectl create secret generic encryptionconfig \ - --from-file=./encryption-provider-config.yaml \ - -n cattle-resources-system -``` - -This will ensure that the secret contains a key named `encryption-provider-config.yaml`, and the operator will use this key to get the encryption configuration. - -The `Encryption Config Secret` dropdown will filter out and list only those Secrets that have this exact key - -{{< img "/img/rancher/backup_restore/backup/encryption.png" "">}} - -In the example command above, the name `encryptionconfig` can be changed to anything. - - -| YAML Directive Name | Description | -| ---------------- | ---------------- | -| `encryptionConfigSecretName` | Provide the name of the Secret from `cattle-resources-system` namespace, that contains the encryption config file. | - -# Storage Location - -If the StorageLocation is specified in the Backup, the operator will retrieve the backup location from that particular S3 bucket. If not specified, the operator will try to find this file in the default operator-level S3 store, and in the operator-level PVC store. The default storage location is configured during the deployment of the `rancher-backup` operator. - -Selecting the first option stores this backup in the storage location configured while installing the rancher-backup chart. The second option lets you configure a different S3 compatible storage provider for storing the backup. - -### S3 - -The S3 storage location contains the following configuration fields: - -1. **Credential Secret** (optional): If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) The Credential Secret dropdown lists the secrets in all namespaces. -1. **Bucket Name**: The name of the S3 bucket where backup files will be stored. -1. **Region** (optional): The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. This field isn't needed for configuring MinIO. -1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. -1. **Endpoint**: The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket. -1. **Endpoint CA** (optional): This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration) -1. **Skip TLS Verifications** (optional): Set to true if you are not using TLS. - - -| YAML Directive Name | Description | Required | -| ---------------- | ---------------- | ------------ | -| `credentialSecretName` | If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace as long as you provide that namespace in `credentialSecretNamespace`. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | | -| `credentialSecretNamespace` | The namespace of the secret containing the credentials to access S3. This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | | -| `bucketName` | The name of the S3 bucket where backup files will be stored. | ✓ | -| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. | | -| `region` | The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. | ✓ | -| `endpoint` | The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket. | ✓ | -| `endpointCA` | This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration) | | -| `insecureTLSSkipVerify` | Set to true if you are not using TLS. | | - -### Example S3 Storage Configuration - -```yaml -s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: rancher - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com -``` - -### Example MinIO Configuration - -```yaml -s3: - credentialSecretName: minio-creds - bucketName: rancherbackups - endpoint: minio.35.202.130.254.xip.io - endpointCA: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURHakNDQWdLZ0F3SUJBZ0lKQUtpWFZpNEpBb0J5TUEwR0NTcUdTSWIzRFFFQkN3VUFNQkl4RURBT0JnTlYKQkFNTUIzUmxjM1F0WTJFd0hoY05NakF3T0RNd01UZ3lOVFE1V2hjTk1qQXhNREk1TVRneU5UUTVXakFTTVJBdwpEZ1lEVlFRRERBZDBaWE4wTFdOaE1JSUJJakFOQmdrcWhraUc5dzBCQVFFRkFBT0NBUThBTUlJQkNnS0NBUUVBCjA4dnV3Q2Y0SEhtR2Q2azVNTmozRW5NOG00T2RpS3czSGszd1NlOUlXQkwyVzY5WDZxenBhN2I2M3U2L05mMnkKSnZWNDVqeXplRFB6bFJycjlpbEpWaVZ1NFNqWlFjdG9jWmFCaVNsL0xDbEFDdkFaUlYvKzN0TFVTZSs1ZDY0QQpWcUhDQlZObU5xM3E3aVY0TE1aSVpRc3N6K0FxaU1Sd0pOMVVKQTZ6V0tUc2Yzc3ByQ0J2dWxJWmZsVXVETVAyCnRCTCt6cXZEc0pDdWlhNEEvU2JNT29tVmM2WnNtTGkwMjdub3dGRld3MnRpSkM5d0xMRE14NnJoVHQ4a3VvVHYKQXJpUjB4WktiRU45L1Uzb011eUVKbHZyck9YS2ZuUDUwbk8ycGNaQnZCb3pUTStYZnRvQ1d5UnhKUmI5cFNTRApKQjlmUEFtLzNZcFpMMGRKY2sxR1h3SURBUUFCbzNNd2NUQWRCZ05WSFE0RUZnUVU5NHU4WXlMdmE2MTJnT1pyCm44QnlFQ2NucVFjd1FnWURWUjBqQkRzd09ZQVU5NHU4WXlMdmE2MTJnT1pybjhCeUVDY25xUWVoRnFRVU1CSXgKRURBT0JnTlZCQU1NQjNSbGMzUXRZMkdDQ1FDb2wxWXVDUUtBY2pBTUJnTlZIUk1FQlRBREFRSC9NQTBHQ1NxRwpTSWIzRFFFQkN3VUFBNElCQVFER1JRZ1RtdzdVNXRQRHA5Q2psOXlLRW9Vd2pYWWM2UlAwdm1GSHpubXJ3dUVLCjFrTkVJNzhBTUw1MEpuS29CY0ljVDNEeGQ3TGdIbTNCRE5mVVh2anArNnZqaXhJYXR2UWhsSFNVaWIyZjJsSTkKVEMxNzVyNCtROFkzelc1RlFXSDdLK08vY3pJTGh5ei93aHRDUlFkQ29lS1dXZkFiby8wd0VSejZzNkhkVFJzNwpHcWlGNWZtWGp6S0lOcTBjMHRyZ0xtalNKd1hwSnU0ZnNGOEcyZUh4b2pOKzdJQ1FuSkg5cGRIRVpUQUtOL2ppCnIvem04RlZtd1kvdTBndEZneWVQY1ZWbXBqRm03Y0ZOSkc4Y2ZYd0QzcEFwVjhVOGNocTZGeFBHTkVvWFZnclMKY1VRMklaU0RJd1FFY3FvSzFKSGdCUWw2RXBaUVpWMW1DRklrdFBwSQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0t -``` -### Example credentialSecret - -```yaml -apiVersion: v1 -kind: Secret -metadata: - name: creds -type: Opaque -data: - accessKey: - secretKey: -``` - -### IAM Permissions for EC2 Nodes to Access S3 - -There are two ways to set up the `rancher-backup` operator to use S3 as the backup storage location. - -One way is to configure the `credentialSecretName` in the Backup custom resource, which refers to AWS credentials that have access to S3. - -If the cluster nodes are in Amazon EC2, the S3 access can also be set up by assigning IAM permissions to the EC2 nodes so that they can access S3. - -To allow a node to access S3, follow the instructions in the [AWS documentation](https://aws.amazon.com/premiumsupport/knowledge-center/ec2-instance-access-s3-bucket/) to create an IAM role for EC2. When you add a custom policy to the role, add the following permissions, and replace the `Resource` with your bucket name: - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "s3:ListBucket" - ], - "Resource": [ - "arn:aws:s3:::rancher-backups" - ] - }, - { - "Effect": "Allow", - "Action": [ - "s3:PutObject", - "s3:GetObject", - "s3:DeleteObject", - "s3:PutObjectAcl" - ], - "Resource": [ - "arn:aws:s3:::rancher-backups/*" - ] - } - ] -} -``` - -After the role is created, and you have attached the corresponding instance profile to your EC2 instance(s), the `credentialSecretName` directive can be left empty in the Backup custom resource. - -# Examples - -For example Backup custom resources, refer to [this page.](../../examples/#backup) diff --git a/versioned_docs/version-2.6/backups/configuration/configuration.md b/versioned_docs/version-2.6/backups/configuration/configuration.md deleted file mode 100644 index d83cc04b29f..00000000000 --- a/versioned_docs/version-2.6/backups/configuration/configuration.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Rancher Backup Configuration Reference -shortTitle: Configuration -weight: 4 ---- - -- [Backup configuration](./backup-config) -- [Restore configuration](./restore-config) -- [Storage location configuration](./storage-config) -- [Example Backup and Restore Custom Resources](../examples) \ No newline at end of file diff --git a/versioned_docs/version-2.6/backups/configuration/restore-config/restore-config.md b/versioned_docs/version-2.6/backups/configuration/restore-config/restore-config.md deleted file mode 100644 index a3e2ff3a7f7..00000000000 --- a/versioned_docs/version-2.6/backups/configuration/restore-config/restore-config.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Restore Configuration -shortTitle: Restore -weight: 2 ---- - -The Restore Create page lets you provide details of the backup to restore from - -{{< img "/img/rancher/backup_restore/restore/restore.png" "">}} - -- [Backup Source](#backup-source) - - [An Existing Backup Config](#an-existing-backup-config) - - [The default storage target](#the-default-storage-target) - - [An S3-compatible object store](#an-s3-compatible-object-store) -- [Encryption](#encryption) -- [Prune during restore](#prune-during-restore) -- [Getting the Backup Filename from S3](#getting-the-backup-filename-from-s3) - -# Backup Source -Provide details of the backup file and its storage location, which the operator will then use to perform the restore. Select from the following options to provide these details - - - - -### An existing backup config - -Selecting this option will populate the **Target Backup** dropdown with the Backups available in this cluster. Select the Backup from the dropdown, and that will fill out the **Backup Filename** field for you, and will also pass the backup source information from the selected Backup to the operator. - -{{< img "/img/rancher/backup_restore/restore/existing.png" "">}} - -If the Backup custom resource does not exist in the cluster, you need to get the exact filename and provide the backup source details with the default storage target or an S3-compatible object store. - - -### The default storage target - -Select this option if you are restoring from a backup file that exists in the default storage location configured at the operator-level. The operator-level configuration is the storage location that was configured when the `rancher-backup` operator was installed or upgraded. Provide the exact filename in the **Backup Filename** field. - -{{< img "/img/rancher/backup_restore/restore/default.png" "">}} - -### An S3-compatible object store - -Select this option if no default storage location is configured at the operator-level, OR if the backup file exists in a different S3 bucket than the one configured as the default storage location. Provide the exact filename in the **Backup Filename** field. Refer to [this section](#getting-the-backup-filename-from-s3) for exact steps on getting the backup filename from s3. Fill in all the details for the S3 compatible object store. Its fields are exactly same as ones for the `backup.StorageLocation` configuration in the [Backup custom resource.](../../configuration/backup-config/#storage-location) - -{{< img "/img/rancher/backup_restore/restore/s3store.png" "">}} - -# Encryption - -If the backup was created with encryption enabled, its file will have `.enc` suffix. Choosing such a Backup, or providing a backup filename with `.enc` suffix will display another dropdown named **Encryption Config Secret**. - -{{< img "/img/rancher/backup_restore/restore/encryption.png" "">}} - -The Secret selected from this dropdown must have the same contents as the one used for the Backup custom resource while performing the backup. If the encryption configuration doesn't match, the restore will fail - -The `Encryption Config Secret` dropdown will filter out and list only those Secrets that have this exact key - -| YAML Directive Name | Description | -| ---------------- | ---------------- | -| `encryptionConfigSecretName` | Provide the name of the Secret from `cattle-resources-system` namespace, that contains the encryption config file. | - -> **Important** -This field should only be set if the backup was created with encryption enabled. Providing the incorrect encryption config will cause the restore to fail. - -# Prune During Restore - -* **Prune**: In order to fully restore Rancher from a backup, and to go back to the exact state it was at when the backup was performed, we need to delete any additional resources that were created by Rancher after the backup was taken. The operator does so if the **Prune** flag is enabled. Prune is enabled by default and it is recommended to keep it enabled. -* **Delete Timeout**: This is the amount of time the operator will wait while deleting a resource before editing the resource to remove finalizers and attempt deletion again. - -| YAML Directive Name | Description | -| ---------------- | ---------------- | -| `prune` | Delete the resources managed by Rancher that are not present in the backup (Recommended). | -| `deleteTimeoutSeconds` | Amount of time the operator will wait while deleting a resource before editing the resource to remove finalizers and attempt deletion again. | - -# Getting the Backup Filename from S3 - -This is the name of the backup file that the `rancher-backup` operator will use to perform the restore. - -To obtain this file name from S3, go to your S3 bucket (and folder if it was specified while performing backup). - -Copy the filename and store it in your Restore custom resource. So assuming the name of your backup file is `backupfile`, - -- If your bucket name is `s3bucket` and no folder was specified, then the `backupFilename` to use will be `backupfile`. -- If your bucket name is `s3bucket` and the base folder is`s3folder`, the `backupFilename` to use is only `backupfile` . -- If there is a subfolder inside `s3Folder` called `s3sub`, and that has your backup file, then the `backupFilename` to use is `s3sub/backupfile`. - -| YAML Directive Name | Description | -| ---------------- | ---------------- | -| `backupFilename` | This is the name of the backup file that the `rancher-backup` operator will use to perform the restore. | diff --git a/versioned_docs/version-2.6/backups/configuration/storage-config/storage-config.md b/versioned_docs/version-2.6/backups/configuration/storage-config/storage-config.md deleted file mode 100644 index 569532510fe..00000000000 --- a/versioned_docs/version-2.6/backups/configuration/storage-config/storage-config.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Backup Storage Location Configuration -shortTitle: Storage -weight: 3 ---- - -Configure a storage location where all backups are saved by default. You will have the option to override this with each backup, but will be limited to using an S3-compatible object store. - -Only one storage location can be configured at the operator level. - -- [Storage Location Configuration](#storage-location-configuration) - - [No Default Storage Location](#no-default-storage-location) - - [S3-compatible Object Store](#s3-compatible-object-store) - - [Use an existing StorageClass](#existing-storageclass) - - [Use an existing PersistentVolume](#existing-persistent-volume) -- [Encryption](#encryption) -- [Example values.yaml for the rancher-backup Helm Chart](#example-values-yaml-for-the-rancher-backup-helm-chart) - -# Storage Location Configuration - -### No Default Storage Location - -You can choose to not have any operator-level storage location configured. If you select this option, you must configure an S3-compatible object store as the storage location for each individual backup. - -### S3-compatible Object Store - -| Parameter | Description | -| -------------- | -------------- | -| Credential Secret | Choose the credentials for S3 from your secrets in Rancher. [Example]({{}}/rancher/v2.6/en/backups/examples/#example-credential-secret-for-storing-backups-in-s3). | -| Bucket Name | Enter the name of the [S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html) where the backups will be stored. Default: `rancherbackups`. | -| Region | The [AWS region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. | -| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. | -| Endpoint | The [S3 endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) For example, `s3.us-west-2.amazonaws.com`. | -| Endpoint CA | The CA cert used to for the S3 endpoint. Default: base64 encoded CA cert | -| insecureTLSSkipVerify | Set to true if you are not using TLS. | - -### Existing StorageClass - -Installing the `rancher-backup` chart by selecting the StorageClass option will create a Persistent Volume Claim (PVC), and Kubernetes will in turn dynamically provision a Persistent Volume (PV) where all the backups will be saved by default. - -For information about creating storage classes refer to [this section.]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/provisioning-new-storage/) - -> **Important** -It is highly recommended to use a StorageClass with a reclaim policy of "Retain". Otherwise if the PVC created by the `rancher-backup` chart gets deleted (either during app upgrade, or accidentally), the PV will get deleted too, which means all backups saved in it will get deleted. -If no such StorageClass is available, after the PV is provisioned, make sure to edit its reclaim policy and set it to "Retain" before storing backups in it. - -### Existing Persistent Volume - -Select an existing Persistent Volume (PV) that will be used to store your backups. For information about creating PersistentVolumes in Rancher, refer to [this section.]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/attaching-existing-storage/#2-add-a-persistent-volume-that-refers-to-the-persistent-storage) - -> **Important** -It is highly recommended to use a Persistent Volume with a reclaim policy of "Retain". Otherwise if the PVC created by the `rancher-backup` chart gets deleted (either during app upgrade, or accidentally), the PV will get deleted too, which means all backups saved in it will get deleted. - - -# Example values.yaml for the rancher-backup Helm Chart - -The documented `values.yaml` file that can be used to configure `rancher-backup` operator when the Helm CLI is used can be found in the [backup-restore-operator repository.](https://github.com/rancher/backup-restore-operator/blob/master/charts/rancher-backup/values.yaml) - -For more information about `values.yaml` files and configuring Helm charts during installation, refer to the [Helm documentation.](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing) - diff --git a/versioned_docs/version-2.6/backups/docker-installs/docker-backups/docker-backups.md b/versioned_docs/version-2.6/backups/docker-installs/docker-backups/docker-backups.md deleted file mode 100644 index 274a0ece9ea..00000000000 --- a/versioned_docs/version-2.6/backups/docker-installs/docker-backups/docker-backups.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Backing up Rancher Installed with Docker -shortTitle: Backups -weight: 3 ---- - -After completing your Docker installation of Rancher, we recommend creating backups of it on a regular basis. Having a recent backup will let you recover quickly from an unexpected disaster. - -## Before You Start - -During the creation of your backup, you'll enter a series of commands, replacing placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). Here's an example of a command with a placeholder: - -``` -docker run --volumes-from rancher-data- -v $PWD:/backup busybox tar pzcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher -``` - -In this command, `` is a placeholder for the date that the data container and backup were created. `9-27-18` for example. - -Cross reference the image and reference table below to learn how to obtain this placeholder data. Write down or copy this information before starting the [procedure below](#creating-a-backup). - -Terminal docker ps Command, Displaying Where to Find <RANCHER_CONTAINER_TAG> and <RANCHER_CONTAINER_NAME> - -![Placeholder Reference]({{}}/img/rancher/placeholder-ref.png) - -| Placeholder | Example | Description | -| -------------------------- | -------------------------- | --------------------------------------------------------- | -| `` | `v2.0.5` | The rancher/rancher image you pulled for initial install. | -| `` | `festive_mestorf` | The name of your Rancher container. | -| `` | `v2.0.5` | The version of Rancher that you're creating a backup for. | -| `` | `9-27-18` | The date that the data container or backup was created. | -
- -You can obtain `` and `` by logging into your Rancher Server by remote connection and entering the command to view the containers that are running: `docker ps`. You can also view containers that are stopped with `docker ps -a`. Use these commands for help anytime while creating backups. - -## Creating a Backup - -This procedure creates a backup that you can restore if Rancher encounters a disaster scenario. - - -1. Using a remote Terminal connection, log into the node running your Rancher Server. - -1. Stop the container currently running Rancher Server. Replace `` with the name of your Rancher container. - - ``` - docker stop - ``` -1. Use the command below, replacing each placeholder, to create a data container from the Rancher container that you just stopped. - - ``` - docker create --volumes-from --name rancher-data- rancher/rancher: - ``` - -1. From the data container that you just created (rancher-data-<DATE>), create a backup tarball (rancher-data-backup-<RANCHER_VERSION>-<DATE>.tar.gz). Use the following command, replacing each placeholder: - - ``` - docker run --volumes-from rancher-data- -v $PWD:/backup:z busybox tar pzcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher - ``` - - **Step Result:** A stream of commands runs on the screen. - -1. Enter the `ls` command to confirm that the backup tarball was created. It will have a name similar to `rancher-data-backup--.tar.gz`. - -1. Move your backup tarball to a safe location external to your Rancher Server. Then delete the `rancher-data-` container from your Rancher Server. - -1. Restart Rancher Server. Replace `` with the name of your Rancher container: - - ``` - docker start - ``` - -**Result:** A backup tarball of your Rancher Server data is created. See [Restoring Backups: Docker Installs]({{}}/rancher/v2.6/en/backups/docker-installs/docker-restores) if you need to restore backup data. diff --git a/versioned_docs/version-2.6/backups/docker-installs/docker-installs.md b/versioned_docs/version-2.6/backups/docker-installs/docker-installs.md deleted file mode 100644 index a2a71cad6c2..00000000000 --- a/versioned_docs/version-2.6/backups/docker-installs/docker-installs.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Backup and Restore for Rancher Installed with Docker -shortTitle: Docker Installs -weight: 10 ---- - -- [Backups](./docker-backups) -- [Restores](./docker-restores) \ No newline at end of file diff --git a/versioned_docs/version-2.6/backups/docker-installs/docker-restores/docker-restores.md b/versioned_docs/version-2.6/backups/docker-installs/docker-restores/docker-restores.md deleted file mode 100644 index 23e002610c5..00000000000 --- a/versioned_docs/version-2.6/backups/docker-installs/docker-restores/docker-restores.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Restoring Backups—Docker Installs -shortTitle: Restores -weight: 3 ---- - -If you encounter a disaster scenario, you can restore your Rancher Server to your most recent backup. - -## Before You Start - -During restore of your backup, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). Here's an example of a command with a placeholder: - -``` -docker run --volumes-from -v $PWD:/backup \ -busybox sh -c "rm /var/lib/rancher/* -rf && \ -tar pzxvf /backup/rancher-data-backup--" -``` - -In this command, `` and `-` are environment variables for your Rancher deployment. - -Cross reference the image and reference table below to learn how to obtain this placeholder data. Write down or copy this information before starting the procedure below. - -Terminal docker ps Command, Displaying Where to Find <RANCHER_CONTAINER_TAG> and <RANCHER_CONTAINER_NAME> - -![Placeholder Reference]({{}}/img/rancher/placeholder-ref.png) - -| Placeholder | Example | Description | -| -------------------------- | -------------------------- | --------------------------------------------------------- | -| `` | `v2.0.5` | The rancher/rancher image you pulled for initial install. | -| `` | `festive_mestorf` | The name of your Rancher container. | -| `` | `v2.0.5` | The version number for your Rancher backup. | -| `` | `9-27-18` | The date that the data container or backup was created. | -
- -You can obtain `` and `` by logging into your Rancher Server by remote connection and entering the command to view the containers that are running: `docker ps`. You can also view containers that are stopped using a different command: `docker ps -a`. Use these commands for help anytime during while creating backups. - -## Restoring Backups - -Using a [backup]({{}}/rancher/v2.6/en/backups/docker-installs/docker-backups) that you created earlier, restore Rancher to its last known healthy state. - -1. Using a remote Terminal connection, log into the node running your Rancher Server. - -1. Stop the container currently running Rancher Server. Replace `` with the name of your Rancher container: - - ``` - docker stop - ``` -1. Move the backup tarball that you created during completion of [Creating Backups—Docker Installs]({{}}/rancher/v2.6/en/backups/docker-installs/docker-backups) onto your Rancher Server. Change to the directory that you moved it to. Enter `dir` to confirm that it's there. - - If you followed the naming convention we suggested in [Creating Backups—Docker Installs]({{}}/rancher/v2.6/en/backups/docker-installs/docker-backups/), it will have a name similar to `rancher-data-backup--.tar.gz`. - -1. Enter the following command to delete your current state data and replace it with your backup data, replacing the placeholders. Don't forget to close the quotes. - - >**Warning!** This command deletes all current state data from your Rancher Server container. Any changes saved after your backup tarball was created will be lost. - - ``` - docker run --volumes-from -v $PWD:/backup \ - busybox sh -c "rm /var/lib/rancher/* -rf && \ - tar pzxvf /backup/rancher-data-backup--.tar.gz" - ``` - - **Step Result:** A series of commands should run. - -1. Restart your Rancher Server container, replacing the placeholder. It will restart using your backup data. - - ``` - docker start - ``` - -1. Wait a few moments and then open Rancher in a web browser. Confirm that the restore succeeded and that your data is restored. diff --git a/versioned_docs/version-2.6/backups/examples/examples.md b/versioned_docs/version-2.6/backups/examples/examples.md deleted file mode 100644 index b1282f9c3ca..00000000000 --- a/versioned_docs/version-2.6/backups/examples/examples.md +++ /dev/null @@ -1,308 +0,0 @@ ---- -title: Examples -weight: 5 ---- - -This section contains examples of Backup and Restore custom resources. - -The default backup storage location is configured when the `rancher-backup` operator is installed or upgraded. - -Encrypted backups can only be restored if the Restore custom resource uses the same encryption configuration secret that was used to create the backup. - -- [Backup](#backup) - - [Backup in the default location with encryption](#backup-in-the-default-location-with-encryption) - - [Recurring backup in the default location](#recurring-backup-in-the-default-location) - - [Encrypted recurring backup in the default location](#encrypted-recurring-backup-in-the-default-location) - - [Encrypted backup in Minio](#encrypted-backup-in-minio) - - [Backup in S3 using AWS credential secret](#backup-in-s3-using-aws-credential-secret) - - [Recurring backup in S3 using AWS credential secret](#recurring-backup-in-s3-using-aws-credential-secret) - - [Backup from EC2 nodes with IAM permission to access S3](#backup-from-ec2-nodes-with-iam-permission-to-access-s3) -- [Restore](#restore) - - [Restore using the default backup file location](#restore-using-the-default-backup-file-location) - - [Restore for Rancher migration](#restore-for-rancher-migration) - - [Restore from encrypted backup](#restore-from-encrypted-backup) - - [Restore an encrypted backup from Minio](#restore-an-encrypted-backup-from-minio) - - [Restore from backup using an AWS credential secret to access S3](#restore-from-backup-using-an-aws-credential-secret-to-access-s3) - - [Restore from EC2 nodes with IAM permissions to access S3](#restore-from-ec2-nodes-with-iam-permissions-to-access-s3) -- [Example Credential Secret for Storing Backups in S3](#example-credential-secret-for-storing-backups-in-s3) -- [Example EncryptionConfiguration](#example-encryptionconfiguration) - -# Backup - -This section contains example Backup custom resources. - -### Backup in the Default Location with Encryption - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: default-location-encrypted-backup -spec: - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig -``` - -### Recurring Backup in the Default Location - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: default-location-recurring-backup -spec: - resourceSetName: rancher-resource-set - schedule: "@every 1h" - retentionCount: 10 -``` - -### Encrypted Recurring Backup in the Default Location - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: default-enc-recurring-backup -spec: - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig - schedule: "@every 1h" - retentionCount: 3 -``` - -### Encrypted Backup in Minio - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: minio-backup -spec: - storageLocation: - s3: - credentialSecretName: minio-creds - credentialSecretNamespace: default - bucketName: rancherbackups - endpoint: minio.xip.io - endpointCA: LS0tLS1CRUdJTi3VUFNQkl5UUT.....pbEpWaVzNkRS0tLS0t - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig -``` - -### Backup in S3 Using AWS Credential Secret - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: s3-backup -spec: - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig -``` - -### Recurring Backup in S3 Using AWS Credential Secret - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: s3-recurring-backup -spec: - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig - schedule: "@every 1h" - retentionCount: 10 -``` - -### Backup from EC2 Nodes with IAM Permission to Access S3 - -This example shows that the AWS credential secret does not have to be provided to create a backup if the nodes running `rancher-backup` have [these permissions for access to S3.](../configuration/backup-config/#iam-permissions-for-ec2-nodes-to-access-s3) - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Backup -metadata: - name: s3-iam-backup -spec: - storageLocation: - s3: - bucketName: rancher-backups - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - resourceSetName: rancher-resource-set - encryptionConfigSecretName: encryptionconfig -``` - -# Restore - -This section contains example Restore custom resources. - -### Restore Using the Default Backup File Location - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-default -spec: - backupFilename: default-location-recurring-backup-752ecd87-d958-4d20-8350-072f8d090045-2020-09-26T12-29-54-07-00.tar.gz -# encryptionConfigSecretName: test-encryptionconfig -``` - -### Restore for Rancher Migration -```yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-migration -spec: - backupFilename: backup-b0450532-cee1-4aa1-a881-f5f48a007b1c-2020-09-15T07-27-09Z.tar.gz - prune: false - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com -``` - -### Restore from Encrypted Backup - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-encrypted -spec: - backupFilename: default-test-s3-def-backup-c583d8f2-6daf-4648-8ead-ed826c591471-2020-08-24T20-47-05Z.tar.gz - encryptionConfigSecretName: encryptionconfig -``` - -### Restore an Encrypted Backup from Minio - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-minio -spec: - backupFilename: default-minio-backup-demo-aa5c04b7-4dba-4c48-9ac4-ab7916812eaa-2020-08-30T13-18-17-07-00.tar.gz - storageLocation: - s3: - credentialSecretName: minio-creds - credentialSecretNamespace: default - bucketName: rancherbackups - endpoint: minio.xip.io - endpointCA: LS0tLS1CRUdJTi3VUFNQkl5UUT.....pbEpWaVzNkRS0tLS0t - encryptionConfigSecretName: test-encryptionconfig -``` - -### Restore from Backup Using an AWS Credential Secret to Access S3 - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-s3-demo -spec: - backupFilename: test-s3-recurring-backup-752ecd87-d958-4d20-8350-072f8d090045-2020-09-26T12-49-34-07-00.tar.gz.enc - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - encryptionConfigSecretName: test-encryptionconfig -``` - -### Restore from EC2 Nodes with IAM Permissions to Access S3 - -This example shows that the AWS credential secret does not have to be provided to restore from backup if the nodes running `rancher-backup` have [these permissions for access to S3.](../configuration/backup-config/#iam-permissions-for-ec2-nodes-to-access-s3) - -```yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-s3-demo -spec: - backupFilename: default-test-s3-recurring-backup-84bf8dd8-0ef3-4240-8ad1-fc7ec308e216-2020-08-24T10#52#44-07#00.tar.gz - storageLocation: - s3: - bucketName: rajashree-backup-test - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - encryptionConfigSecretName: test-encryptionconfig -``` - -# Example Credential Secret for Storing Backups in S3 - -```yaml -apiVersion: v1 -kind: Secret -metadata: - name: creds -type: Opaque -data: - accessKey: - secretKey: -``` - -# Example EncryptionConfiguration - -The snippet below demonstrates two different types of secrets and their relevance with respect to Backup and Restore of custom resources. - -The first example is that of a secret that is used to encrypt the backup files. The backup operator, in this case, will not be able to read the secrets encryption file. It only uses the contents of the secret. - -The second example is that of a Kubernetes secrets encryption config file that is used to encrypt secrets when stored in etcd. **When backing up the etcd datastore, be sure to also back up the EncryptionConfiguration.** Failure to do so will result in an inability to use the restored data if secrets encryption was in use at the time the data was backed up. - - -```yaml -apiVersion: apiserver.config.k8s.io/v1 -kind: EncryptionConfiguration -resources: - - resources: - - secrets - providers: - - aesgcm: - keys: - - name: key1 - secret: c2VjcmV0IGlzIHNlY3VyZQ== - - name: key2 - secret: dGhpcyBpcyBwYXNzd29yZA== - - aescbc: - keys: - - name: key1 - secret: c2VjcmV0IGlzIHNlY3VyZQ== - - name: key2 - secret: dGhpcyBpcyBwYXNzd29yZA== - - secretbox: - keys: - - name: key1 - secret: YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY= -``` - - - diff --git a/versioned_docs/version-2.6/backups/migrating-rancher/migrating-rancher.md b/versioned_docs/version-2.6/backups/migrating-rancher/migrating-rancher.md deleted file mode 100644 index 5b5e4f3acdd..00000000000 --- a/versioned_docs/version-2.6/backups/migrating-rancher/migrating-rancher.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -title: Migrating Rancher to a New Cluster -weight: 3 ---- - -If you are migrating Rancher to a new Kubernetes cluster, you don't need to install Rancher on the new cluster first. If Rancher is restored to a new cluster with Rancher already installed, it can cause problems. - -### Prerequisites - -These instructions assume you have [created a backup](../back-up-rancher) and you have already installed a new Kubernetes cluster where Rancher will be deployed. - ->**Warning:** It is required to use the same hostname that was set as the server URL in the first cluster. If not done, downstream clusters will show as unavailable in the cluster management page of the UI, and you won't be able to click inside the cluster or on the cluster's Explore button. - -Rancher version must be v2.5.0 and up - -Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes clusters such as Amazon EKS clusters. For help installing Kubernetes, refer to the documentation of the Kubernetes distribution. One of Rancher's Kubernetes distributions may also be used: - -- [RKE Kubernetes installation docs]({{}}/rke/latest/en/installation/) -- [K3s Kubernetes installation docs]({{}}/k3s/latest/en/installation/) - -### 1. Install the rancher-backup Helm chart -Install version 2.x.x of the rancher-backup chart. The following assumes a connected environment with access to DockerHub: -``` -helm repo add rancher-charts https://charts.rancher.io -helm repo update -helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace --version $CHART_VERSION -helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system --version $CHART_VERSION -``` -
-For an **air-gapped environment**, use the option below to pull the `backup-restore-operator` image from your private registry when installing the rancher-backup-crd helm chart. -``` ---set image.repository $REGISTRY/rancher/backup-restore-operator -``` - -### 2. Restore from backup using a Restore custom resource - ->**Important:** Kubernetes v1.22, available as an experimental feature of v2.6.3, does not support restoring from backup files containing CRDs with the apiVersion `apiextensions.k8s.io/v1beta1`. In v1.22, the default `resourceSet` in the rancher-backup app is updated to collect only CRDs that use `apiextensions.k8s.io/v1`. There are currently two ways to work around this issue: -> -1. Update the default `resourceSet` to collect the CRDs with the apiVersion v1. -1. Update the default `resourceSet` and the client to use the new APIs internally, with `apiextensions.k8s.io/v1` as the replacement. -> -> - Note that when making or restoring backups for v1.22, the Rancher version and the local cluster's Kubernetes version should be the same. The Kubernetes version should be considered when restoring a backup since the supported apiVersion in the cluster and in the backup file could be different. - -If you are using an S3 store as the backup source and need to use your S3 credentials for restore, create a secret in this cluster using your S3 credentials. The Secret data must have two keys - `accessKey` and `secretKey` - that contain the S3 credentials. - -**Warning:** The values `accessKey` and `secretKey` in the example below must be base64-encoded first when creating the object directly. If not encoded first, the pasted values will cause errors when you are attempting to backup or restore. - -```yaml -apiVersion: v1 -kind: Secret -metadata: - name: s3-creds -type: Opaque -stringData: - accessKey: - secretKey: -``` - -This secret can be created in any namespace; with the above example, it will get created in the default namespace. - -In the Restore custom resource, `prune` must be set to false. - -Create a Restore custom resource like the example below: - -```yaml -# migrationResource.yaml -apiVersion: resources.cattle.io/v1 -kind: Restore -metadata: - name: restore-migration -spec: - backupFilename: backup-b0450532-cee1-4aa1-a881-f5f48a007b1c-2020-09-15T07-27-09Z.tar.gz - prune: false - encryptionConfigSecretName: encryptionconfig - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: backup-test - folder: ecm1 - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com -``` - ->**Important:** The field `encryptionConfigSecretName` must be set only if your backup was created with encryption enabled. Provide the name of the Secret containing the encryption config file. If you only have the encryption config file, but don't have a secret created with it in this cluster, use the following steps to create the secret: - -1. The encryption configuration file must be named `encryption-provider-config.yaml`, and the `--from-file` flag must be used to create this secret. So save your `EncryptionConfiguration` in a file called `encryption-provider-config.yaml` and run this command: -``` -kubectl create secret generic encryptionconfig \ - --from-file=./encryption-provider-config.yaml \ - -n cattle-resources-system -``` - -1. Apply the manifest, and watch for the Restore resources status: - - Apply the resource: -``` -kubectl apply -f migrationResource.yaml -``` - - Watch the Restore status: -``` -kubectl get restore -``` - - Watch the restoration logs: -``` -kubectl logs -n cattle-resources-system --tail 100 -f rancher-backup-xxx-xxx -``` - -Once the Restore resource has the status `Completed`, you can continue the Rancher installation. - -### 3. Install cert-manager - -Follow the steps to [install cert-manager]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#5-install-cert-manager) in the documentation about installing cert-manager on Kubernetes. - -### 4. Bring up Rancher with Helm - -Use the same version of Helm to install Rancher, that was used on the first cluster. - -``` -helm install rancher rancher-latest/rancher \ - --namespace cattle-system \ - --set hostname= \ -``` diff --git a/versioned_docs/version-2.6/backups/restoring-rancher/restoring-rancher.md b/versioned_docs/version-2.6/backups/restoring-rancher/restoring-rancher.md deleted file mode 100644 index 2ec7691aa79..00000000000 --- a/versioned_docs/version-2.6/backups/restoring-rancher/restoring-rancher.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Restoring Rancher -weight: 2 ---- - -This page outlines how to perform a restore with Rancher. - -> **Important** -> -> * Follow the instructions from this page for restoring rancher on the same cluster where it was backed up from. In order to migrate rancher to a new cluster, follow the steps to [migrate rancher.]({{}}/rancher/v2.6/en/backups/migrating-rancher) -> * While restoring rancher on the same setup, the operator will scale down the rancher deployment when restore starts, and it will scale back up the deployment once restore completes. So Rancher will be unavailable during the restore. -> * If you need to restore Rancher to a previous version after an upgrade, see the [rollback documentation.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/rollbacks/) - -### Additional Steps for Rollbacks with Rancher v2.6.4+ - -In Rancher v2.6.4, the cluster-api module has been upgraded from v0.4.4 to v1.0.2 in which the apiVersion of CAPI CRDs are upgraded from `cluster.x-k8s.io/v1alpha4` to `cluster.x-k8s.io/v1beta1`. This has the effect of causing rollbacks from Rancher v2.6.4 to any previous version of Rancher v2.6.x to fail because the previous version the CRDs needed to roll back are no longer available in v1beta1. - -To avoid this, the Rancher resource cleanup scripts should be run **before** the restore or rollback is attempted. Specifically, two scripts have been created to assist you: one to clean up the cluster (`cleanup.sh`), and one to check for any Rancher-related resources in the cluster (`verify.sh`). Details on the cleanup script can be found in the [rancherlabs/support-tools repo](https://github.com/rancherlabs/support-tools/tree/master/rancher-cleanup). - -> **Caution** Rancher will be down as the `cleanup` script runs as it deletes the resources created by rancher. - -The additional preparations: - -1. Follow these [instructions](https://github.com/rancherlabs/support-tools/blob/master/rancher-cleanup/README.md) to run the scripts. -1. Follow these [instructions](https://rancher.com/docs/rancher/v2.6/en/backups/migrating-rancher/) to install the rancher-backup Helm chart on the existing cluster and restore the previous state. - 1. Omit Step 3. - 1. When Step 4 is reached, install the required Rancher v2.6.x version on the local cluster you intend to roll back to. - -### Create the Restore Custom Resource - -A restore is performed by creating a Restore custom resource. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the `local` cluster and click **Explore**. The `local` cluster runs the Rancher server. -1. In the left navigation bar, click **Rancher Backups > Restores**. -1. Click **Create**. -1. Create the Restore with the form, or with YAML. For creating the Restore resource using form, refer to the [configuration reference]({{}}/rancher/v2.6/en/backups/configuration/restore-config) and to the [examples.]({{}}/rancher/v2.6/en/backups/examples) -1. For using the YAML editor, we can click **Create > Create from YAML**. Enter the Restore YAML. - - ```yaml - apiVersion: resources.cattle.io/v1 - kind: Restore - metadata: - name: restore-migration - spec: - backupFilename: backup-b0450532-cee1-4aa1-a881-f5f48a007b1c-2020-09-15T07-27-09Z.tar.gz - encryptionConfigSecretName: encryptionconfig - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: rancher - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - ``` - - For help configuring the Restore, refer to the [configuration reference]({{}}/rancher/v2.6/en/backups/configuration/restore-config) and to the [examples.]({{}}/rancher/v2.6/en/backups/examples) - -1. Click **Create**. - -**Result:** The rancher-operator scales down the rancher deployment during restore, and scales it back up once the restore completes. The resources are restored in this order: - -1. Custom Resource Definitions (CRDs) -2. Cluster-scoped resources -3. Namespaced resources - -### Logs - -To check how the restore is progressing, you can check the logs of the operator. Run this command to follow the logs: - -``` -kubectl logs -n cattle-resources-system -l app.kubernetes.io/name=rancher-backup -f -``` - -### Cleanup - -If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores. - -### Known Issues -In some cases, after restoring the backup, Rancher logs will show errors similar to the following: -``` -2021/10/05 21:30:45 [ERROR] error syncing 'c-89d82/m-4067aa68dd78': handler rke-worker-upgrader: clusters.management.cattle.io "c-89d82" not found, requeuing -``` -This happens because one of the resources that was just restored has finalizers, but the related resources have been deleted so the handler cannot find it. - -To eliminate the errors, we need to find and delete the resource that causes the error. See more information [here](https://github.com/rancher/rancher/issues/35050#issuecomment-937968556) diff --git a/versioned_docs/version-2.6/best-practices/best-practices.md b/versioned_docs/version-2.6/best-practices/best-practices.md deleted file mode 100644 index 37310b8fdd9..00000000000 --- a/versioned_docs/version-2.6/best-practices/best-practices.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Best Practices Guide -weight: 4 ---- - -The purpose of this section is to consolidate best practices for Rancher implementations. This also includes recommendations for related technologies, such as Kubernetes, Docker, containers, and more. The objective is to improve the outcome of a Rancher implementation using the operational experience of Rancher and its customers. - -If you have any questions about how these might apply to your use case, please contact your Customer Success Manager or Support. - -Use the navigation bar on the left to find the current best practices for managing and deploying the Rancher Server. - -For more guidance on best practices, you can consult these resources: - -- [Security]({{}}/rancher/v2.6/en/security/) -- [Rancher Blog](https://www.suse.com/c/rancherblog/) -- [Rancher Forum](https://forums.rancher.com/) -- [Rancher Users Slack](https://slack.rancher.io/) -- [Rancher Labs YouTube Channel - Online Meetups, Demos, Training, and Webinars](https://www.youtube.com/channel/UCh5Xtp82q8wjijP8npkVTBA/featured) diff --git a/versioned_docs/version-2.6/best-practices/rancher-managed/containers/containers.md b/versioned_docs/version-2.6/best-practices/rancher-managed/containers/containers.md deleted file mode 100644 index 15a21d61e3d..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-managed/containers/containers.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Tips for Setting Up Containers -weight: 100 ---- - -Running well-built containers can greatly impact the overall performance and security of your environment. - -Below are a few tips for setting up your containers. - -For a more detailed discussion of security for containers, you can also refer to Rancher's [Guide to Container Security.](https://rancher.com/complete-guide-container-security) - -### Use a Common Container OS - -When possible, you should try to standardize on a common container base OS. - -Smaller distributions such as Alpine and BusyBox reduce container image size and generally have a smaller attack/vulnerability surface. - -Popular distributions such as Ubuntu, Fedora, and CentOS are more field-tested and offer more functionality. - -### Start with a FROM scratch container -If your microservice is a standalone static binary, you should use a FROM scratch container. - -The FROM scratch container is an [official Docker image](https://hub.docker.com/_/scratch) that is empty so that you can use it to design minimal images. - -This will have the smallest attack surface and smallest image size. - -### Run Container Processes as Unprivileged -When possible, use a non-privileged user when running processes within your container. While container runtimes provide isolation, vulnerabilities and attacks are still possible. Inadvertent or accidental host mounts can also be impacted if the container is running as root. For details on configuring a security context for a pod or container, refer to the [Kubernetes docs](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/). - -### Define Resource Limits -Apply CPU and memory limits to your pods. This can help manage the resources on your worker nodes and avoid a malfunctioning microservice from impacting other microservices. - -In standard Kubernetes, you can set resource limits on the namespace level. In Rancher, you can set resource limits on the project level and they will propagate to all the namespaces within the project. For details, refer to the Rancher docs. - -When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project or namespace, all containers will require a respective CPU or Memory field set during creation. To avoid setting these limits on each and every container during workload creation, a default container resource limit can be specified on the namespace. - -The Kubernetes docs have more information on how resource limits can be set at the [container level](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#resource-requests-and-limits-of-pod-and-container) and the namespace level. - -### Define Resource Requirements -You should apply CPU and memory requirements to your pods. This is crucial for informing the scheduler which type of compute node your pod needs to be placed on, and ensuring it does not over-provision that node. In Kubernetes, you can set a resource requirement by defining `resources.requests` in the resource requests field in a pod's container spec. For details, refer to the [Kubernetes docs](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#resource-requests-and-limits-of-pod-and-container). - -> **Note:** If you set a resource limit for the namespace that the pod is deployed in, and the container doesn't have a specific resource request, the pod will not be allowed to start. To avoid setting these fields on each and every container during workload creation, a default container resource limit can be specified on the namespace. - -It is recommended to define resource requirements on the container level because otherwise, the scheduler makes assumptions that will likely not be helpful to your application when the cluster experiences load. - -### Liveness and Readiness Probes -Set up liveness and readiness probes for your container. Unless your container completely crashes, Kubernetes will not know it's unhealthy unless you create an endpoint or mechanism that can report container status. Alternatively, make sure your container halts and crashes if unhealthy. - -The Kubernetes docs show how to [configure liveness and readiness probes for containers.](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) diff --git a/versioned_docs/version-2.6/best-practices/rancher-managed/logging/logging.md b/versioned_docs/version-2.6/best-practices/rancher-managed/logging/logging.md deleted file mode 100644 index 42edadf1bdb..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-managed/logging/logging.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: Logging Best Practices -weight: 1 ---- -In this guide, we recommend best practices for cluster-level logging and application logging. - -- [Cluster-level Logging](#cluster-level-logging) -- [Application Logging](#application-logging) -- [General Best Practices](#general-best-practices) - -Before Rancher v2.5, logging in Rancher has historically been a pretty static integration. There were a fixed list of aggregators to choose from (ElasticSearch, Splunk, Kafka, Fluentd and Syslog), and only two configuration points to choose (Cluster-level and Project-level). - -Rancher provides a flexible experience for log aggregation. With the logging feature, administrators and users alike can deploy logging that meets fine-grained collection criteria while offering a wider array of destinations and configuration options. - -"Under the hood", Rancher logging uses the Banzai Cloud logging operator. We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters. - -# Cluster-level Logging - -### Cluster-wide Scraping - -For some users, it is desirable to scrape logs from every container running in the cluster. This usually coincides with your security team's request (or requirement) to collect all logs from all points of execution. - -In this scenario, it is recommended to create at least two _ClusterOutput_ objects - one for your security team (if you have that requirement), and one for yourselves, the cluster administrators. When creating these objects take care to choose an output endpoint that can handle the significant log traffic coming from the entire cluster. Also make sure to choose an appropriate index to receive all these logs. - -Once you have created these _ClusterOutput_ objects, create a _ClusterFlow_ to collect all the logs. Do not define any _Include_ or _Exclude_ rules on this flow. This will ensure that all logs from across the cluster are collected. If you have two _ClusterOutputs_, make sure to send logs to both of them. - -### Kubernetes Components - -_ClusterFlows_ have the ability to collect logs from all containers on all hosts in the Kubernetes cluster. This works well in cases where those containers are part of a Kubernetes pod; however, RKE containers exist outside of the scope of Kubernetes. - -Currently the logs from RKE containers are collected, but are not able to easily be filtered. This is because those logs do not contain information as to the source container (e.g. `etcd` or `kube-apiserver`). - -A future release of Rancher will include the source container name which will enable filtering of these component logs. Once that change is made, you will be able to customize a _ClusterFlow_ to retrieve **only** the Kubernetes component logs, and direct them to an appropriate output. - -# Application Logging - -Best practice not only in Kubernetes but in all container-based applications is to direct application logs to `stdout`/`stderr`. The container runtime will then trap these logs and do **something** with them - typically writing them to a file. Depending on the container runtime (and its configuration), these logs can end up in any number of locations. - -In the case of writing the logs to a file, Kubernetes helps by creating a `/var/log/containers` directory on each host. This directory symlinks the log files to their actual destination (which can differ based on configuration or container runtime). - -Rancher logging will read all log entries in `/var/log/containers`, ensuring that all log entries from all containers (assuming a default configuration) will have the opportunity to be collected and processed. - -### Specific Log Files - -Log collection only retrieves `stdout`/`stderr` logs from pods in Kubernetes. But what if we want to collect logs from other files that are generated by applications? Here, a log streaming sidecar (or two) may come in handy. - -The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Banzai Logging Operator can pick up those logs and send them to your desired output. - -To set this up, edit your workload resource (e.g. Deployment) and add the following sidecar definition: - -``` -... -containers: -- args: - - -F - - /path/to/your/log/file.log - command: - - tail - image: busybox - name: stream-log-file-[name] - volumeMounts: - - mountPath: /path/to/your/log - name: mounted-log -... -``` - -This will add a container to your workload definition that will now stream the contents of (in this example) `/path/to/your/log/file.log` to `stdout`. - -This log stream is then automatically collected according to any _Flows_ or _ClusterFlows_ you have setup. You may also wish to consider creating a _Flow_ specifically for this log file by targeting the name of the container. See example: - -``` -... -spec: - match: - - select: - container_names: - - stream-log-file-name -... -``` - - -# General Best Practices - -- Where possible, output structured log entries (e.g. `syslog`, JSON). This makes handling of the log entry easier as there are already parsers written for these formats. -- Try to provide the name of the application that is creating the log entry, in the entry itself. This can make troubleshooting easier as Kubernetes objects do not always carry the name of the application as the object name. For instance, a pod ID may be something like `myapp-098kjhsdf098sdf98` which does not provide much information about the application running inside the container. -- Except in the case of collecting all logs cluster-wide, try to scope your _Flow_ and _ClusterFlow_ objects tightly. This makes it easier to troubleshoot when problems arise, and also helps ensure unrelated log entries do not show up in your aggregator. An example of tight scoping would be to constrain a _Flow_ to a single _Deployment_ in a namespace, or perhaps even a single container within a _Pod_. -- Keep the log verbosity down except when troubleshooting. High log verbosity poses a number of issues, chief among them being **noise**: significant events can be drowned out in a sea of `DEBUG` messages. This is somewhat mitigated with automated alerting and scripting, but highly verbose logging still places an inordinate amount of stress on the logging infrastructure. -- Where possible, try to provide a transaction or request ID with the log entry. This can make tracing application activity across multiple log sources easier, especially when dealing with distributed applications. diff --git a/versioned_docs/version-2.6/best-practices/rancher-managed/managed-vsphere/managed-vsphere.md b/versioned_docs/version-2.6/best-practices/rancher-managed/managed-vsphere/managed-vsphere.md deleted file mode 100644 index d355cdca047..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-managed/managed-vsphere/managed-vsphere.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Best Practices for Rancher Managed vSphere Clusters -shortTitle: Rancher Managed Clusters in vSphere ---- - -This guide outlines a reference architecture for provisioning downstream Rancher clusters in a vSphere environment, in addition to standard vSphere best practices as documented by VMware. - -- [1. VM Considerations](#1-vm-considerations) -- [2. Network Considerations](#2-network-considerations) -- [3. Storage Considerations](#3-storage-considerations) -- [4. Backups and Disaster Recovery](#4-backups-and-disaster-recovery) - -
Solution Overview
- -![Solution Overview]({{}}/img/rancher/solution_overview.drawio.svg) - -# 1. VM Considerations - -### Leverage VM Templates to Construct the Environment - -To facilitate consistency across the deployed Virtual Machines across the environment, consider the use of "Golden Images" in the form of VM templates. Packer can be used to accomplish this, adding greater customisation options. - -### Leverage DRS Anti-Affinity Rules (Where Possible) to Separate Downstream Cluster Nodes Across ESXi Hosts - -Doing so will ensure node VM's are spread across multiple ESXi hosts - preventing a single point of failure at the host level. - -### Leverage DRS Anti-Affinity Rules (Where Possible) to Separate Downstream Cluster Nodes Across Datastores - -Doing so will ensure node VM's are spread across multiple datastores - preventing a single point of failure at the datastore level. - -### Configure VM's as Appropriate for Kubernetes - -It’s important to follow K8s and etcd best practices when deploying your nodes, including disabling swap, double-checking you have full network connectivity between all machines in the cluster, using unique hostnames, MAC addresses, and product_uuids for every node. - -# 2. Network Considerations - -### Leverage Low Latency, High Bandwidth Connectivity Between ETCD Nodes - -Deploy etcd members within a single data center where possible to avoid latency overheads and reduce the likelihood of network partitioning. For most setups, 1Gb connections will suffice. For large clusters, 10Gb connections can reduce the time taken to restore from backup. - -### Consistent IP Addressing for VM's - -Each node used should have a static IP configured. In the case of DHCP, each node should have a DHCP reservation to make sure the node gets the same IP allocated. - -# 3. Storage Considerations - -### Leverage SSD Drives for ETCD Nodes - -ETCD is very sensitive to write latency. Therefore, leverage SSD disks where possible. - -# 4. Backups and Disaster Recovery - -### Perform Regular Downstream Cluster Backups - -Kubernetes uses etcd to store all its data - from configuration, state and metadata. Backing this up is crucial in the event of disaster recovery. - -### Back up Downstream Node VMs - -Incorporate the Rancher downstream node VM's within a standard VM backup policy. \ No newline at end of file diff --git a/versioned_docs/version-2.6/best-practices/rancher-managed/monitoring/monitoring.md b/versioned_docs/version-2.6/best-practices/rancher-managed/monitoring/monitoring.md deleted file mode 100644 index 0abd7a2d515..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-managed/monitoring/monitoring.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Monitoring Best Practices -weight: 2 ---- - -Configuring sensible monitoring and alerting rules is vital for running any production workloads securely and reliably. This is not different when using Kubernetes and Rancher. Fortunately the integrated monitoring and alerting functionality makes this whole process a lot easier. - -The [Rancher monitoring documentation]({{}}/rancher/v2.6/en/monitoring-alerting/) describes how you can set up a complete Prometheus and Grafana stack. Out of the box this will scrape monitoring data from all system and Kubernetes components in your cluster and provide sensible dashboards and alerts for them to get started. But for a reliable setup, you also need to monitor your own workloads and adapt Prometheus and Grafana to your own specific use cases and cluster sizes. This document aims to give you best practices for this. - -- [What to Monitor](#what-to-monitor) -- [Configuring Prometheus Resource Usage](#configuring-prometheus-resource-usage) -- [Scraping Custom Workloads](#scraping-custom-workloads) -- [Monitoring in a (Micro)Service Architecture](#monitoring-in-a-micro-service-architecture) -- [Real User Monitoring](#real-user-monitoring) -- [Security Monitoring](#security-monitoring) -- [Setting up Alerts](#setting-up-alerts) - -# What to Monitor - -Kubernetes itself, as well as applications running inside of it, form a distributed system where different components interact with each other. For the whole system and each individual component, you have to ensure performance, availability, reliability and scalability. A good resource with more details and information is Google's free [Site Reliability Engineering Book](https://landing.google.com/sre/sre-book/), especially the chapter about [Monitoring distributed systems](https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-systems/). - -# Configuring Prometheus Resource Usage - -When installing the integrated monitoring stack, Rancher allows to configure several settings that are dependent on the size of your cluster and the workloads running in it. This chapter covers these in more detail. - -### Storage and Data Retention - -The amount of storage needed for Prometheus directly correlates to the amount of time series and labels that you store and the data retention you have configured. It is important to note that Prometheus is not meant to be used as a long-term metrics storage. Data retention time is usually only a couple of days and not weeks or months. The reason for this is that Prometheus does not perform any aggregation on its stored metrics. This is great because aggregation can dilute data, but it also means that the needed storage grows linearly over time without retention. - -One way to calculate the necessary storage is to look at the average size of a storage chunk in Prometheus with this query - -``` -rate(prometheus_tsdb_compaction_chunk_size_bytes_sum[1h]) / rate(prometheus_tsdb_compaction_chunk_samples_sum[1h]) -``` - -Next, find out your data ingestion rate per second: - -``` -rate(prometheus_tsdb_head_samples_appended_total[1h]) -``` - -and then multiply this with the retention time, adding a few percentage points as buffer: - -``` -average chunk size in bytes * ingestion rate per second * retention time in seconds * 1.1 = necessary storage in bytes -``` - -You can find more information about how to calculate the necessary storage in this [blog post](https://www.robustperception.io/how-much-disk-space-do-prometheus-blocks-use). - -You can read more about the Prometheus storage concept in the [Prometheus documentation](https://prometheus.io/docs/prometheus/latest/storage). - -### CPU and Memory Requests and Limits - -In larger Kubernetes clusters Prometheus can consume quite a bit of memory. The amount of memory Prometheus needs directly correlates to the amount of time series and amount of labels it stores and the scrape interval in which these are filled. - -You can find more information about how to calculate the necessary memory in this [blog post](https://www.robustperception.io/how-much-ram-does-prometheus-2-x-need-for-cardinality-and-ingestion). - -The amount of necessary CPUs correlate with the amount of queries you are performing. - -### Federation and Long-term Storage - -Prometheus is not meant to store metrics for a long amount of time, but should only be used for short term storage. - -In order to store some, or all metrics for a long time, you can leverage Prometheus' [remote read/write](https://prometheus.io/docs/prometheus/latest/storage/#remote-storage-integrations) capabilities to connect it to storage systems like [Thanos](https://thanos.io/), [InfluxDB](https://www.influxdata.com/), [M3DB](https://www.m3db.io/), or others. You can find an example setup in this [blog post](https://rancher.com/blog/2020/prometheus-metric-federation). - -# Scraping Custom Workloads - -While the integrated Rancher Monitoring already scrapes system metrics from a cluster's nodes and system components, the custom workloads that you deploy on Kubernetes should also be scraped for data. For that you can configure Prometheus to do an HTTP request to an endpoint of your applications in a certain interval. These endpoints should then return their metrics in a Prometheus format. - -In general, you want to scrape data from all the workloads running in your cluster so that you can use them for alerts or debugging issues. Often, you recognize that you need some data only when you actually need the metrics during an incident. It is good, if it is already scraped and stored. Since Prometheus is only meant to be a short-term metrics storage, scraping and keeping lots of data is usually not that expensive. If you are using a long-term storage solution with Prometheus, you can then still decide which data you are actually persisting and keeping there. - -### About Prometheus Exporters - -A lot of 3rd party workloads like databases, queues or web-servers either already support exposing metrics in a Prometheus format, or there are so called exporters available that translate between the tool's metrics and the format that Prometheus understands. Usually you can add these exporters as additional sidecar containers to the workload's Pods. A lot of helm charts already include options to deploy the correct exporter. Additionally you can find a curated list of exports by SysDig on [promcat.io](https://promcat.io/) and on [ExporterHub](https://exporterhub.io/). - -### Prometheus support in Programming Languages and Frameworks - -To get your own custom application metrics into Prometheus, you have to collect and expose these metrics directly from your application's code. Fortunately, there are already libraries and integrations available to help with this for most popular programming languages and frameworks. One example for this is the Prometheus support in the [Spring Framework](https://docs.spring.io/spring-metrics/docs/current/public/prometheus). - -### ServiceMonitors and PodMonitors - -Once all your workloads expose metrics in a Prometheus format, you have to configure Prometheus to scrape it. Under the hood Rancher is using the [prometheus-operator](https://github.com/prometheus-operator/prometheus-operator). This makes it easy to add additional scraping targets with ServiceMonitors and PodMonitors. A lot of helm charts already include an option to create these monitors directly. You can also find more information in the Rancher documentation. - -### Prometheus Push Gateway - -There are some workloads that are traditionally hard to scrape by Prometheus. Examples for these are short lived workloads like Jobs and CronJobs, or applications that do not allow sharing data between individual handled incoming requests, like PHP applications. - -To still get metrics for these use cases, you can set up [prometheus-pushgateways](https://github.com/prometheus/pushgateway). The CronJob or PHP application would push metric updates to the pushgateway. The pushgateway aggregates and exposes them through an HTTP endpoint, which then can be scraped by Prometheus. - -### Prometheus Blackbox Monitor - -Sometimes it is useful to monitor workloads from the outside. For this, you can use the [Prometheus blackbox-exporter](https://github.com/prometheus/blackbox_exporter) which allows probing any kind of endpoint over HTTP, HTTPS, DNS, TCP and ICMP. - -# Monitoring in a (Micro)Service Architecture - -If you have a (micro)service architecture where multiple individual workloads within your cluster are communicating with each other, it is really important to have detailed metrics and traces about this traffic to understand how all these workloads are communicating with each other and where a problem or bottleneck may be. - -Of course you can monitor all this internal traffic in all your workloads and expose these metrics to Prometheus. But this can quickly become quite work intensive. Service Meshes like Istio, which can be installed with [a click](https://rancher.com/docs/rancher/v2.6/en/istio/) in Rancher, can do this automatically and provide rich telemetry about the traffic between all services. - -# Real User Monitoring - -Monitoring the availability and performance of all your internal workloads is vitally important to run stable, reliable and fast applications. But these metrics only show you parts of the picture. To get a complete view it is also necessary to know how your end users are actually perceiving it. For this you can look into various [Real user monitoring solutions](https://en.wikipedia.org/wiki/Real_user_monitoring). - -# Security Monitoring - -In addition to monitoring workloads to detect performance, availability or scalability problems, the cluster and the workloads running into it should also be monitored for potential security problems. A good starting point is to frequently run and alert on [CIS Scans]({{}}/rancher/v2.6/en/cis-scans/) which check if the cluster is configured according to security best practices. - -For the workloads, you can have a look at Kubernetes and Container security solutions like [Falco](https://falco.org/), [Aqua Kubernetes Security](https://www.aquasec.com/solutions/kubernetes-container-security/), [SysDig](https://sysdig.com/). - -# Setting up Alerts - -Getting all the metrics into a monitoring systems and visualizing them in dashboards is great, but you also want to be pro-actively alerted if something goes wrong. - -The integrated Rancher monitoring already configures a sensible set of alerts that make sense in any Kubernetes cluster. You should extend these to cover your specific workloads and use cases. - -When setting up alerts, configure them for all the workloads that are critical to the availability of your applications. But also make sure that they are not too noisy. Ideally every alert you are receiving should be because of a problem that needs your attention and needs to be fixed. If you have alerts that are firing all the time but are not that critical, there is a danger that you start ignoring your alerts all together and then miss the real important ones. Less may be more here. Start to focus on the real important metrics first, for example alert if your application is offline. Fix all the problems that start to pop up and then start to create more detailed alerts. - -If an alert starts firing, but there is nothing you can do about it at the moment, it's also fine to silence the alert for a certain amount of time, so that you can look at it later. - -You can find more information on how to set up alerts and notification channels in the [Rancher Documentation]({{}}/rancher/v2.6/en/monitoring-alerting). diff --git a/versioned_docs/version-2.6/best-practices/rancher-managed/rancher-managed.md b/versioned_docs/version-2.6/best-practices/rancher-managed/rancher-managed.md deleted file mode 100644 index 9d3d86d1fc6..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-managed/rancher-managed.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Best Practices for Rancher Managed Clusters -shortTitle: Rancher Managed Clusters -weight: 2 ---- - -### Logging - -Refer to [this guide](./logging) for our recommendations for cluster-level logging and application logging. - -### Monitoring - -Configuring sensible monitoring and alerting rules is vital for running any production workloads securely and reliably. Refer to this [guide](./monitoring) for our recommendations. - -### Tips for Setting Up Containers - -Running well-built containers can greatly impact the overall performance and security of your environment. Refer to this [guide](./containers) for tips. - -### Best Practices for Rancher Managed vSphere Clusters - -This [guide](./managed-vsphere) outlines a reference architecture for provisioning downstream Rancher clusters in a vSphere environment, in addition to standard vSphere best practices as documented by VMware. diff --git a/versioned_docs/version-2.6/best-practices/rancher-server/deployment-strategies/deployment-strategies.md b/versioned_docs/version-2.6/best-practices/rancher-server/deployment-strategies/deployment-strategies.md deleted file mode 100644 index b2544d473b5..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-server/deployment-strategies/deployment-strategies.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Rancher Deployment Strategy -weight: 100 ---- - -There are two recommended deployment strategies for a Rancher server that manages downstream Kubernetes clusters. Each one has its own pros and cons. Read more about which one would fit best for your use case: - -* [Hub and Spoke](#hub-and-spoke-strategy) -* [Regional](#regional-strategy) - -# Hub & Spoke Strategy ---- - -In this deployment scenario, there is a single Rancher control plane managing Kubernetes clusters across the globe. The control plane would be run on a high-availability Kubernetes cluster, and there would be impact due to latencies. - -{{< img "/img/rancher/bpg/hub-and-spoke.png" "Hub and Spoke Deployment">}} - -### Pros - -* Environments could have nodes and network connectivity across regions. -* Single control plane interface to view/see all regions and environments. -* Kubernetes does not require Rancher to operate and can tolerate losing connectivity to the Rancher control plane. - -### Cons - -* Subject to network latencies. -* If the control plane goes out, global provisioning of new services is unavailable until it is restored. However, each Kubernetes cluster can continue to be managed individually. - -# Regional Strategy ---- -In the regional deployment model a control plane is deployed in close proximity to the compute nodes. - -{{< img "/img/rancher/bpg/regional.png" "Regional Deployment">}} - -### Pros - -* Rancher functionality in regions stay operational if a control plane in another region goes down. -* Network latency is greatly reduced, improving the performance of functionality in Rancher. -* Upgrades of the Rancher control plane can be done independently per region. - -### Cons - -* Overhead of managing multiple Rancher installations. -* Visibility across global Kubernetes clusters requires multiple interfaces/panes of glass. -* Deploying multi-cluster apps in Rancher requires repeating the process for each Rancher server. diff --git a/versioned_docs/version-2.6/best-practices/rancher-server/deployment-types/deployment-types.md b/versioned_docs/version-2.6/best-practices/rancher-server/deployment-types/deployment-types.md deleted file mode 100644 index 35e0fcaf41a..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-server/deployment-types/deployment-types.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Tips for Running Rancher -weight: 100 ---- - -This guide is geared toward use cases where Rancher is used to manage downstream Kubernetes clusters. The high-availability setup is intended to prevent losing access to downstream clusters if the Rancher server is not available. - -A high-availability Kubernetes installation, defined as an installation of Rancher on a Kubernetes cluster with at least three nodes, should be used in any production installation of Rancher, as well as any installation deemed "important." Multiple Rancher instances running on multiple nodes ensure high availability that cannot be accomplished with a single node environment. - -If you are installing Rancher in a vSphere environment, refer to the best practices documented [here.](../rancher-in-vsphere) - -When you set up your high-availability Rancher installation, consider the following: - -### Run Rancher on a Separate Cluster -Don't run other workloads or microservices in the Kubernetes cluster that Rancher is installed on. - -### Make sure nodes are configured correctly for Kubernetes ### -It's important to follow K8s and etcd best practices when deploying your nodes, including disabling swap, double checking you have full network connectivity between all machines in the cluster, using unique hostnames, MAC addresses, and product_uuids for every node, checking that all correct ports are opened, and deploying with ssd backed etcd. More details can be found in the [kubernetes docs](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#before-you-begin) and [etcd's performance op guide](https://etcd.io/docs/v3.4/op-guide/performance/). - -### When using RKE: Back up the Statefile -RKE keeps record of the cluster state in a file called `cluster.rkestate`. This file is important for the recovery of a cluster and/or the continued maintenance of the cluster through RKE. Because this file contains certificate material, we strongly recommend encrypting this file before backing up. After each run of `rke up` you should backup the state file. - -### Run All Nodes in the Cluster in the Same Datacenter -For best performance, run all three of your nodes in the same geographic datacenter. If you are running nodes in the cloud, such as AWS, run each node in a separate Availability Zone. For example, launch node 1 in us-west-2a, node 2 in us-west-2b, and node 3 in us-west-2c. - -### Development and Production Environments Should be Similar -It's strongly recommended to have a "staging" or "pre-production" environment of the Kubernetes cluster that Rancher runs on. This environment should mirror your production environment as closely as possible in terms of software and hardware configuration. - -### Monitor Your Clusters to Plan Capacity -The Rancher server's Kubernetes cluster should run within the [system and hardware requirements]({{}}/rancher/v2.6/en/installation/requirements/) as closely as possible. The more you deviate from the system and hardware requirements, the more risk you take. - -However, metrics-driven capacity planning analysis should be the ultimate guidance for scaling Rancher, because the published requirements take into account a variety of workload types. - -Using Rancher, you can monitor the state and processes of your cluster nodes, Kubernetes components, and software deployments through integration with Prometheus, a leading open-source monitoring solution, and Grafana, which lets you visualize the metrics from Prometheus. - -After you [enable monitoring]({{}}/rancher/v2.6/en/monitoring-alerting) in the cluster, you can set up alerts to let you know if your cluster is approaching its capacity. You can also use the Prometheus and Grafana monitoring framework to establish a baseline for key metrics as you scale. - diff --git a/versioned_docs/version-2.6/best-practices/rancher-server/rancher-in-vsphere/rancher-in-vsphere.md b/versioned_docs/version-2.6/best-practices/rancher-server/rancher-in-vsphere/rancher-in-vsphere.md deleted file mode 100644 index 207ab8accb2..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-server/rancher-in-vsphere/rancher-in-vsphere.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Installing Rancher in a vSphere Environment -shortTitle: On-Premises Rancher in vSphere -weight: 3 ---- - -This guide outlines a reference architecture for installing Rancher on an RKE Kubernetes cluster in a vSphere environment, in addition to standard vSphere best practices as documented by VMware. - -- [1. Load Balancer Considerations](#1-load-balancer-considerations) -- [2. VM Considerations](#2-vm-considerations) -- [3. Network Considerations](#3-network-considerations) -- [4. Storage Considerations](#4-storage-considerations) -- [5. Backups and Disaster Recovery](#5-backups-and-disaster-recovery) - -
Solution Overview
- -![Solution Overview](/docs/img/rancher/rancher-on-prem-vsphere.svg) - -# 1. Load Balancer Considerations - -A load balancer is required to direct traffic to the Rancher workloads residing on the RKE nodes. - -### Leverage Fault Tolerance and High Availability - -Leverage the use of an external (hardware or software) load balancer that has inherit high-availability functionality (F5, NSX-T, Keepalived, etc). - -### Back Up Load Balancer Configuration - -In the event of a Disaster Recovery activity, availability of the Load balancer configuration will expedite the recovery process. - -### Configure Health Checks - -Configure the Load balancer to automatically mark nodes as unavailable if a health check is failed. For example, NGINX can facilitate this with: - -`max_fails=3 fail_timeout=5s` - -### Leverage an External Load Balancer - -Avoid implementing a software load balancer within the management cluster. - -### Secure Access to Rancher - -Configure appropriate Firewall / ACL rules to only expose access to Rancher - -# 2. VM Considerations - -### Size the VM's According to Rancher Documentation - -https://rancher.com/docs/rancher/v2.6/en/installation/requirements/ - -### Leverage VM Templates to Construct the Environment - -To facilitate the consistency of Virtual Machines deployed across the environment, consider the use of "Golden Images" in the form of VM templates. Packer can be used to accomplish this, adding greater customization options. - -### Leverage DRS Anti-Affinity Rules (Where Possible) to Separate Rancher Cluster Nodes Across ESXi Hosts - -Doing so will ensure node VM's are spread across multiple ESXi hosts - preventing a single point of failure at the host level. - -### Leverage DRS Anti-Affinity Rules (Where Possible) to Separate Rancher Cluster Nodes Across Datastores - -Doing so will ensure node VM's are spread across multiple datastores - preventing a single point of failure at the datastore level. - -### Configure VM's as Appropriate for Kubernetes - -It’s important to follow K8s and etcd best practices when deploying your nodes, including disabling swap, double-checking you have full network connectivity between all machines in the cluster, using unique hostnames, MAC addresses, and product_uuids for every node. - -# 3. Network Considerations - -### Leverage Low Latency, High Bandwidth Connectivity Between ETCD Nodes - -Deploy etcd members within a single data center where possible to avoid latency overheads and reduce the likelihood of network partitioning. For most setups, 1Gb connections will suffice. For large clusters, 10Gb connections can reduce the time taken to restore from backup. - -### Consistent IP Addressing for VM's - -Each node used should have a static IP configured. In the case of DHCP, each node should have a DHCP reservation to make sure the node gets the same IP allocated. - -# 4. Storage Considerations - -### Leverage SSD Drives for ETCD Nodes - -ETCD is very sensitive to write latency. Therefore, leverage SSD disks where possible. - -# 5. Backups and Disaster Recovery - -### Perform Regular Management Cluster Backups - -Rancher stores its data in the ETCD datastore of the Kubernetes cluster it resides on. Like with any Kubernetes cluster, perform frequent, tested backups of this cluster. - -### Back up Rancher Cluster Node VMs - -Incorporate the Rancher management node VM's within a standard VM backup policy. diff --git a/versioned_docs/version-2.6/best-practices/rancher-server/rancher-server.md b/versioned_docs/version-2.6/best-practices/rancher-server/rancher-server.md deleted file mode 100644 index 32786386a3b..00000000000 --- a/versioned_docs/version-2.6/best-practices/rancher-server/rancher-server.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Best Practices for the Rancher Server -shortTitle: Rancher Server -weight: 1 ---- - -This guide contains our recommendations for running the Rancher server, and is intended to be used in situations in which Rancher manages downstream Kubernetes clusters. - -### Recommended Architecture and Infrastructure - -Refer to this [guide](./deployment-types) for our general advice for setting up the Rancher server on a high-availability Kubernetes cluster. - -### Deployment Strategies - -This [guide](./deployment-strategies) is designed to help you choose whether a regional deployment strategy or a hub-and-spoke deployment strategy is better for a Rancher server that manages downstream Kubernetes clusters. - -### Installing Rancher in a vSphere Environment - -This [guide](./rancher-in-vsphere) outlines a reference architecture for installing Rancher in a vSphere environment, in addition to standard vSphere best practices as documented by VMware. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cis-scans/cis-scans.md b/versioned_docs/version-2.6/cis-scans/cis-scans.md deleted file mode 100644 index f9604b61b59..00000000000 --- a/versioned_docs/version-2.6/cis-scans/cis-scans.md +++ /dev/null @@ -1,292 +0,0 @@ ---- -title: CIS Scans -weight: 17 ---- - -Rancher can run a security scan to check whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark. The CIS scans can run on any Kubernetes cluster, including hosted Kubernetes providers such as EKS, AKS, and GKE. - -The `rancher-cis-benchmark` app leverages kube-bench, an open-source tool from Aqua Security, to check clusters for CIS Kubernetes Benchmark compliance. Also, to generate a cluster-wide report, the application utilizes Sonobuoy for report aggregation. - -- [About the CIS Benchmark](#about-the-cis-benchmark) -- [About the Generated Report](#about-the-generated-report) -- [Test Profiles](#test-profiles) -- [About Skipped and Not Applicable Tests](#about-skipped-and-not-applicable-tests) -- [Roles-based Access Control](./rbac) -- [Configuration](./configuration) -- [How-to Guides](#how-to-guides) - - [Installing CIS Benchmark](#installing-cis-benchmark) - - [Uninstalling CIS Benchmark](#uninstalling-cis-benchmark) - - [Running a Scan](#running-a-scan) - - [Running a Scan Periodically on a Schedule](#running-a-scan-periodically-on-a-schedule) - - [Skipping Tests](#skipping-tests) - - [Viewing Reports](#viewing-reports) - - [Enabling Alerting for rancher-cis-benchmark](#enabling-alerting-for-rancher-cis-benchmark) - - [Configuring Alerts for a Periodic Scan on a Schedule](#configuring-alerts-for-a-periodic-scan-on-a-schedule) - - [Creating a Custom Benchmark Version for Running a Cluster Scan](#creating-a-custom-benchmark-version-for-running-a-cluster-scan) - - -# About the CIS Benchmark - -The Center for Internet Security is a 501(c\)(3) non-profit organization, formed in October 2000, with a mission to "identify, develop, validate, promote, and sustain best practice solutions for cyber defense and build and lead communities to enable an environment of trust in cyberspace". The organization is headquartered in East Greenbush, New York, with members including large corporations, government agencies, and academic institutions. - -CIS Benchmarks are best practices for the secure configuration of a target system. CIS Benchmarks are developed through the generous volunteer efforts of subject matter experts, technology vendors, public and private community members, and the CIS Benchmark Development team. - -The official Benchmark documents are available through the CIS website. The sign-up form to access the documents is -here. - -# About the Generated Report - -Each scan generates a report can be viewed in the Rancher UI and can be downloaded in CSV format. - -By default, the CIS Benchmark v1.6 is used. - -The Benchmark version is included in the generated report. - -The Benchmark provides recommendations of two types: Automated and Manual. Recommendations marked as Manual in the Benchmark are not included in the generated report. - -Some tests are designated as "Not Applicable." These tests will not be run on any CIS scan because of the way that Rancher provisions RKE clusters. For information on how test results can be audited, and why some tests are designated to be not applicable, refer to Rancher's self-assessment guide for the corresponding Kubernetes version. - -The report contains the following information: - -| Column in Report | Description | -|------------------|-------------| -| `id` | The ID number of the CIS Benchmark. | -| `description` | The description of the CIS Benchmark test. | -| `remediation` | What needs to be fixed in order to pass the test. | -| `state` | Indicates if the test passed, failed, was skipped, or was not applicable. | -| `node_type` | The node role, which affects which tests are run on the node. Master tests are run on controlplane nodes, etcd tests are run on etcd nodes, and node tests are run on the worker nodes. | -| `audit` | This is the audit check that `kube-bench` runs for this test. | -| `audit_config` | Any configuration applicable to the audit script. | -| `test_info` | Test-related info as reported by `kube-bench`, if any. | -| `commands` | Test-related commands as reported by `kube-bench`, if any. | -| `config_commands` | Test-related configuration data as reported by `kube-bench`, if any. | -| `actual_value` | The test's actual value, present if reported by `kube-bench`. | -| `expected_result` | The test's expected result, present if reported by `kube-bench`. | - -Refer to the table in the cluster hardening guide for information on which versions of Kubernetes, the Benchmark, Rancher, and our cluster hardening guide correspond to each other. Also refer to the hardening guide for configuration files of CIS-compliant clusters and information on remediating failed tests. - -# Test Profiles - -The following profiles are available: - -- Generic CIS 1.5 -- Generic CIS 1.6 -- RKE permissive 1.5 -- RKE hardened 1.5 -- RKE permissive 1.6 -- RKE hardened 1.6 -- RKE2 permissive 1.5 -- RKE2 hardened 1.5 -- RKE2 permissive 1.6 -- RKE2 hardened 1.6 -- AKS -- EKS -- GKE - -You also have the ability to customize a profile by saving a set of tests to skip. - -All profiles will have a set of not applicable tests that will be skipped during the CIS scan. These tests are not applicable based on how a RKE cluster manages Kubernetes. - -There are two types of RKE cluster scan profiles: - -- **Permissive:** This profile has a set of tests that have been will be skipped as these tests will fail on a default RKE Kubernetes cluster. Besides the list of skipped tests, the profile will also not run the not applicable tests. -- **Hardened:** This profile will not skip any tests, except for the non-applicable tests. - -The EKS and GKE cluster scan profiles are based on CIS Benchmark versions that are specific to those types of clusters. - -In order to pass the "Hardened" profile, you will need to follow the steps on the hardening guide and use the `cluster.yml` defined in the hardening guide to provision a hardened cluster. - -The default profile and the supported CIS benchmark version depends on the type of cluster that will be scanned: - -The `rancher-cis-benchmark` supports the CIS 1.6 Benchmark version. - -- For RKE Kubernetes clusters, the RKE Permissive 1.6 profile is the default. -- EKS and GKE have their own CIS Benchmarks published by `kube-bench`. The corresponding test profiles are used by default for those clusters. -- For RKE2 Kubernetes clusters, the RKE2 Permissive 1.6 profile is the default. -- For cluster types other than RKE, RKE2, EKS and GKE, the Generic CIS 1.5 profile will be used by default. - -# About Skipped and Not Applicable Tests - -For a list of skipped and not applicable tests, refer to this page. - -For now, only user-defined skipped tests are marked as skipped in the generated report. - -Any skipped tests that are defined as being skipped by one of the default profiles are marked as not applicable. - -# Roles-based Access Control - -For information about permissions, refer to this page. - -# Configuration - -For more information about configuring the custom resources for the scans, profiles, and benchmark versions, refer to this page. - -# How-to Guides - -- [Installing rancher-cis-benchmark](#installing-rancher-cis-benchmark) -- [Uninstalling rancher-cis-benchmark](#uninstalling-rancher-cis-benchmark) -- [Running a Scan](#running-a-scan) -- [Running a Scan Periodically on a Schedule](#running-a-scan-periodically-on-a-schedule) -- [Skipping Tests](#skipping-tests) -- [Viewing Reports](#viewing-reports) -- [Enabling Alerting for rancher-cis-benchmark](#enabling-alerting-for-rancher-cis-benchmark) -- [Configuring Alerts for a Periodic Scan on a Schedule](#configuring-alerts-for-a-periodic-scan-on-a-schedule) -- [Creating a Custom Benchmark Version for Running a Cluster Scan](#creating-a-custom-benchmark-version-for-running-a-cluster-scan) -### Installing CIS Benchmark - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to install CIS Benchmark and click **Explore**. -1. In the left navigation bar, click **Apps & Marketplace > Charts**. -1. Click **CIS Benchmark** -1. Click **Install**. - -**Result:** The CIS scan application is deployed on the Kubernetes cluster. - -### Uninstalling CIS Benchmark - -1. From the **Cluster Dashboard,** go to the left navigation bar and click **Apps & Marketplace > Installed Apps**. -1. Go to the `cis-operator-system` namespace and check the boxes next to `rancher-cis-benchmark-crd` and `rancher-cis-benchmark`. -1. Click **Delete** and confirm **Delete**. - -**Result:** The `rancher-cis-benchmark` application is uninstalled. - -### Running a Scan - -When a ClusterScan custom resource is created, it launches a new CIS scan on the cluster for the chosen ClusterScanProfile. - -Note: There is currently a limitation of running only one CIS scan at a time for a cluster. If you create multiple ClusterScan custom resources, they will be run one after the other by the operator, and until one scan finishes, the rest of the ClusterScan custom resources will be in the "Pending" state. - -To run a scan, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to run a CIS scan and click **Explore**. -1. Click **CIS Benchmark > Scan**. -1. Click **Create**. -1. Choose a cluster scan profile. The profile determines which CIS Benchmark version will be used and which tests will be performed. If you choose the Default profile, then the CIS Operator will choose a profile applicable to the type of Kubernetes cluster it is installed on. -1. Click **Create**. - -**Result:** A report is generated with the scan results. To see the results, click the name of the scan that appears. -### Running a Scan Periodically on a Schedule - -To run a ClusterScan on a schedule, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to run a CIS scan and click **Explore**. -1. Click **CIS Benchmark > Scan**. -1. Choose a cluster scan profile. The profile determines which CIS Benchmark version will be used and which tests will be performed. If you choose the Default profile, then the CIS Operator will choose a profile applicable to the type of Kubernetes cluster it is installed on. -1. Choose the option **Run scan on a schedule**. -1. Enter a valid cron schedule expression in the field **Schedule**. -1. Choose a **Retention** count, which indicates the number of reports maintained for this recurring scan. By default this count is 3. When this retention limit is reached, older reports will get purged. -1. Click **Create**. - -**Result:** The scan runs and reschedules to run according to the cron schedule provided. The **Next Scan** value indicates the next time this scan will run again. - -A report is generated with the scan results every time the scan runs. To see the latest results, click the name of the scan that appears. - -You can also see the previous reports by choosing the report from the **Reports** dropdown on the scan detail page. - -### Skipping Tests - -CIS scans can be run using test profiles with user-defined skips. - -To skip tests, you will create a custom CIS scan profile. A profile contains the configuration for the CIS scan, which includes the benchmark versions to use and any specific tests to skip in that benchmark. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to run a CIS scan and click **Explore**. -1. Click **CIS Benchmark > Profile**. -1. From here, you can create a profile in multiple ways. To make a new profile, click **Create** and fill out the form in the UI. To make a new profile based on an existing profile, go to the existing profile and click **⋮ Clone**. If you are filling out the form, add the tests to skip using the test IDs, using the relevant CIS Benchmark as a reference. If you are creating the new test profile as YAML, you will add the IDs of the tests to skip in the `skipTests` directive. You will also give the profile a name: - - ```yaml - apiVersion: cis.cattle.io/v1 - kind: ClusterScanProfile - metadata: - annotations: - meta.helm.sh/release-name: clusterscan-operator - meta.helm.sh/release-namespace: cis-operator-system - labels: - app.kubernetes.io/managed-by: Helm - name: "" - spec: - benchmarkVersion: cis-1.5 - skipTests: - - "1.1.20" - - "1.1.21" - ``` -1. Click **Create**. - -**Result:** A new CIS scan profile is created. - -When you [run a scan](#running-a-scan) that uses this profile, the defined tests will be skipped during the scan. The skipped tests will be marked in the generated report as `Skip`. - -### Viewing Reports - -To view the generated CIS scan reports, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to run a CIS scan and click **Explore**. -1. Click **CIS Benchmark > Scan**. -1. The **Scans** page will show the generated reports. To see a detailed report, go to a scan report and click the name. - -One can download the report from the Scans list or from the scan detail page. - -### Enabling Alerting for rancher-cis-benchmark - -Alerts can be configured to be sent out for a scan that runs on a schedule. - -> **Prerequisite:** -> -> Before enabling alerts for `rancher-cis-benchmark`, make sure to install the `rancher-monitoring` application and configure the Receivers and Routes. For more information, see [this section.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration) -> -> While configuring the routes for `rancher-cis-benchmark` alerts, you can specify the matching using the key-value pair `job: rancher-cis-scan`. An example route configuration is [here.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/receiver/#example-route-config-for-cis-scan-alerts) - -While installing or upgrading the `rancher-cis-benchmark` Helm chart, set the following flag to `true` in the `values.yaml`: - -```yaml -alerts: - enabled: true -``` - -### Configuring Alerts for a Periodic Scan on a Schedule - -It is possible to run a ClusterScan on a schedule. - -A scheduled scan can also specify if you should receive alerts when the scan completes. - -Alerts are supported only for a scan that runs on a schedule. - -The CIS Benchmark application supports two types of alerts: - -- Alert on scan completion: This alert is sent out when the scan run finishes. The alert includes details including the ClusterScan's name and the ClusterScanProfile name. -- Alert on scan failure: This alert is sent out if there are some test failures in the scan run or if the scan is in a `Fail` state. - -> **Prerequisite:** -> -> Before enabling alerts for `rancher-cis-benchmark`, make sure to install the `rancher-monitoring` application and configure the Receivers and Routes. For more information, see [this section.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration) -> -> While configuring the routes for `rancher-cis-benchmark` alerts, you can specify the matching using the key-value pair `job: rancher-cis-scan`. An example route configuration is [here.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/receiver/#example-route-config-for-cis-scan-alerts) - -To configure alerts for a scan that runs on a schedule, - -1. Please enable alerts on the `rancher-cis-benchmark` application (#enabling-alerting-for-rancher-cis-benchmark) -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to run a CIS scan and click **Explore**. -1. Click **CIS Benchmark > Scan**. -1. Click **Create**. -1. Choose a cluster scan profile. The profile determines which CIS Benchmark version will be used and which tests will be performed. If you choose the Default profile, then the CIS Operator will choose a profile applicable to the type of Kubernetes cluster it is installed on. -1. Choose the option **Run scan on a schedule**. -1. Enter a valid [cron schedule expression](https://en.wikipedia.org/wiki/Cron#CRON_expression) in the field **Schedule**. -1. Check the boxes next to the Alert types under **Alerting**. -1. Optional: Choose a **Retention Count**, which indicates the number of reports maintained for this recurring scan. By default this count is 3. When this retention limit is reached, older reports will get purged. -1. Click **Create**. - -**Result:** The scan runs and reschedules to run according to the cron schedule provided. Alerts are sent out when the scan finishes if routes and receiver are configured under `rancher-monitoring` application. - -A report is generated with the scan results every time the scan runs. To see the latest results, click the name of the scan that appears. - -### Creating a Custom Benchmark Version for Running a Cluster Scan - -There could be some Kubernetes cluster setups that require custom configurations of the Benchmark tests. For example, the path to the Kubernetes config files or certs might be different than the standard location where the upstream CIS Benchmarks look for them. - -It is now possible to create a custom Benchmark Version for running a cluster scan using the `rancher-cis-benchmark` application. - -For details, see [this page.](./custom-benchmark) diff --git a/versioned_docs/version-2.6/cis-scans/configuration/configuration.md b/versioned_docs/version-2.6/cis-scans/configuration/configuration.md deleted file mode 100644 index 26df1932e25..00000000000 --- a/versioned_docs/version-2.6/cis-scans/configuration/configuration.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Configuration -weight: 3 ---- - -This configuration reference is intended to help you manage the custom resources created by the `rancher-cis-benchmark` application. These resources are used for performing CIS scans on a cluster, skipping tests, setting the test profile that will be used during a scan, and other customization. - -To configure the custom resources, go to the **Cluster Dashboard** To configure the CIS scans, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to configure CIS scans and click **Explore**. -1. In the left navigation bar, click **CIS Benchmark**. - -### Scans - -A scan is created to trigger a CIS scan on the cluster based on the defined profile. A report is created after the scan is completed. - -When configuring a scan, you need to define the name of the scan profile that will be used with the `scanProfileName` directive. - -An example ClusterScan custom resource is below: - -```yaml -apiVersion: cis.cattle.io/v1 -kind: ClusterScan -metadata: - name: rke-cis -spec: - scanProfileName: rke-profile-hardened -``` - -### Profiles - -A profile contains the configuration for the CIS scan, which includes the benchmark version to use and any specific tests to skip in that benchmark. - -> By default, a few ClusterScanProfiles are installed as part of the `rancher-cis-benchmark` chart. If a user edits these default benchmarks or profiles, the next chart update will reset them back. So it is advisable for users to not edit the default ClusterScanProfiles. - -Users can clone the ClusterScanProfiles to create custom profiles. - -Skipped tests are listed under the `skipTests` directive. - -When you create a new profile, you will also need to give it a name. - -An example `ClusterScanProfile` is below: - -```yaml -apiVersion: cis.cattle.io/v1 -kind: ClusterScanProfile -metadata: - annotations: - meta.helm.sh/release-name: clusterscan-operator - meta.helm.sh/release-namespace: cis-operator-system - labels: - app.kubernetes.io/managed-by: Helm - name: "" -spec: - benchmarkVersion: cis-1.5 - skipTests: - - "1.1.20" - - "1.1.21" -``` - -### Benchmark Versions - -A benchmark version is the name of benchmark to run using `kube-bench`, as well as the valid configuration parameters for that benchmark. - -A `ClusterScanBenchmark` defines the CIS `BenchmarkVersion` name and test configurations. The `BenchmarkVersion` name is a parameter provided to the `kube-bench` tool. - -By default, a few `BenchmarkVersion` names and test configurations are packaged as part of the CIS scan application. When this feature is enabled, these default BenchmarkVersions will be automatically installed and available for users to create a ClusterScanProfile. - -> If the default BenchmarkVersions are edited, the next chart update will reset them back. Therefore we don't recommend editing the default ClusterScanBenchmarks. - -A ClusterScanBenchmark consists of the fields: - -- `ClusterProvider`: This is the cluster provider name for which this benchmark is applicable. For example: RKE, EKS, GKE, etc. Leave it empty if this benchmark can be run on any cluster type. -- `MinKubernetesVersion`: Specifies the cluster's minimum kubernetes version necessary to run this benchmark. Leave it empty if there is no dependency on a particular Kubernetes version. -- `MaxKubernetesVersion`: Specifies the cluster's maximum Kubernetes version necessary to run this benchmark. Leave it empty if there is no dependency on a particular k8s version. - -An example `ClusterScanBenchmark` is below: - -```yaml -apiVersion: cis.cattle.io/v1 -kind: ClusterScanBenchmark -metadata: - annotations: - meta.helm.sh/release-name: clusterscan-operator - meta.helm.sh/release-namespace: cis-operator-system - creationTimestamp: "2020-08-28T18:18:07Z" - generation: 1 - labels: - app.kubernetes.io/managed-by: Helm - name: cis-1.5 - resourceVersion: "203878" - selfLink: /apis/cis.cattle.io/v1/clusterscanbenchmarks/cis-1.5 - uid: 309e543e-9102-4091-be91-08d7af7fb7a7 -spec: - clusterProvider: "" - minKubernetesVersion: 1.15.0 -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/cis-scans/custom-benchmark/custom-benchmark.md b/versioned_docs/version-2.6/cis-scans/custom-benchmark/custom-benchmark.md deleted file mode 100644 index 36f70ccaa55..00000000000 --- a/versioned_docs/version-2.6/cis-scans/custom-benchmark/custom-benchmark.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Creating a Custom Benchmark Version for Running a Cluster Scan -weight: 4 ---- - -Each Benchmark Version defines a set of test configuration files that define the CIS tests to be run by the kube-bench tool. -The `rancher-cis-benchmark` application installs a few default Benchmark Versions which are listed under CIS Benchmark application menu. - -But there could be some Kubernetes cluster setups that require custom configurations of the Benchmark tests. For example, the path to the Kubernetes config files or certs might be different than the standard location where the upstream CIS Benchmarks look for them. - -It is now possible to create a custom Benchmark Version for running a cluster scan using the `rancher-cis-benchmark` application. - -When a cluster scan is run, you need to select a Profile which points to a specific Benchmark Version. - -Follow all the steps below to add a custom Benchmark Version and run a scan using it. - -1. [Prepare the Custom Benchmark Version ConfigMap](#1-prepare-the-custom-benchmark-version-configmap) -2. [Add a Custom Benchmark Version to a Cluster](#2-add-a-custom-benchmark-version-to-a-cluster) -3. [Create a New Profile for the Custom Benchmark Version](#3-create-a-new-profile-for-the-custom-benchmark-version) -4. [Run a Scan Using the Custom Benchmark Version](#4-run-a-scan-using-the-custom-benchmark-version) - -### 1. Prepare the Custom Benchmark Version ConfigMap - -To create a custom benchmark version, first you need to create a ConfigMap containing the benchmark version's config files and upload it to your Kubernetes cluster where you want to run the scan. - -To prepare a custom benchmark version ConfigMap, suppose we want to add a custom Benchmark Version named `foo`. - -1. Create a directory named `foo` and inside this directory, place all the config YAML files that the kube-bench tool looks for. For example, here are the config YAML files for a Generic CIS 1.5 Benchmark Version https://github.com/aquasecurity/kube-bench/tree/master/cfg/cis-1.5 -1. Place the complete `config.yaml` file, which includes all the components that should be tested. -1. Add the Benchmark version name to the `target_mapping` section of the `config.yaml`: - - ```yaml - target_mapping: - "foo": - - "master" - - "node" - - "controlplane" - - "etcd" - - "policies" - ``` -1. Upload this directory to your Kubernetes Cluster by creating a ConfigMap: - - ```yaml - kubectl create configmap -n foo --from-file= - ``` - -### 2. Add a Custom Benchmark Version to a Cluster - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to add a custom benchmark and click **Explore**. -1. In the left navigation bar, click **CIS Benchmark > Benchmark Version**. -1. Click **Create**. -1. Enter the **Name** and a description for your custom benchmark version. -1. Choose the cluster provider that your benchmark version applies to. -1. Choose the ConfigMap you have uploaded from the dropdown. -1. Add the minimum and maximum Kubernetes version limits applicable, if any. -1. Click **Create**. - -### 3. Create a New Profile for the Custom Benchmark Version - -To run a scan using your custom benchmark version, you need to add a new Profile pointing to this benchmark version. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to add a custom benchmark and click **Explore**. -1. In the left navigation bar, click **CIS Benchmark > Profile**. -1. Click **Create**. -1. Provide a **Name** and description. In this example, we name it `foo-profile`. -1. Choose the Benchmark Version from the dropdown. -1. Click **Create**. - -### 4. Run a Scan Using the Custom Benchmark Version - -Once the Profile pointing to your custom benchmark version `foo` has been created, you can create a new Scan to run the custom test configs in the Benchmark Version. - -To run a scan, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to add a custom benchmark and click **Explore**. -1. In the left navigation bar, click **CIS Benchmark > Scan**. -1. Click **Create**. -1. Choose the new cluster scan profile. -1. Click **Create**. - -**Result:** A report is generated with the scan results. To see the results, click the name of the scan that appears. diff --git a/versioned_docs/version-2.6/cis-scans/rbac/rbac.md b/versioned_docs/version-2.6/cis-scans/rbac/rbac.md deleted file mode 100644 index ad2b47bff2c..00000000000 --- a/versioned_docs/version-2.6/cis-scans/rbac/rbac.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Roles-based Access Control -shortTitle: RBAC -weight: 3 ---- - -This section describes the permissions required to use the rancher-cis-benchmark App. - -The rancher-cis-benchmark is a cluster-admin only feature by default. - -However, the `rancher-cis-benchmark` chart installs these two default `ClusterRoles`: - -- cis-admin -- cis-view - -In Rancher, only cluster owners and global administrators have `cis-admin` access by default. - -Note: If you were using the `cis-edit` role added in Rancher v2.5 setup, it has now been removed since -Rancher v2.5.2 because it essentially is same as `cis-admin`. If you happen to create any clusterrolebindings -for `cis-edit`, please update them to use `cis-admin` ClusterRole instead. - -# Cluster-Admin Access - -Rancher CIS Scans is a cluster-admin only feature by default. -This means only the Rancher global admins, and the cluster’s cluster-owner can: - -- Install/Uninstall the rancher-cis-benchmark App -- See the navigation links for CIS Benchmark CRDs - ClusterScanBenchmarks, ClusterScanProfiles, ClusterScans -- List the default ClusterScanBenchmarks and ClusterScanProfiles -- Create/Edit/Delete new ClusterScanProfiles -- Create/Edit/Delete a new ClusterScan to run the CIS scan on the cluster -- View and Download the ClusterScanReport created after the ClusterScan is complete - - -# Summary of Default Permissions for Kubernetes Default Roles - -The rancher-cis-benchmark creates three `ClusterRoles` and adds the CIS Benchmark CRD access to the following default K8s `ClusterRoles`: - -| ClusterRole created by chart | Default K8s ClusterRole | Permissions given with Role -| ------------------------------| ---------------------------| ---------------------------| -| `cis-admin` | `admin`| Ability to CRUD clusterscanbenchmarks, clusterscanprofiles, clusterscans, clusterscanreports CR -| `cis-view` | `view `| Ability to List(R) clusterscanbenchmarks, clusterscanprofiles, clusterscans, clusterscanreports CR - - -By default only cluster-owner role will have ability to manage and use `rancher-cis-benchmark` feature. - -The other Rancher roles (cluster-member, project-owner, project-member) do not have any default permissions to manage and use rancher-cis-benchmark resources. - -But if a cluster-owner wants to delegate access to other users, they can do so by creating ClusterRoleBindings between these users and the above CIS ClusterRoles manually. -There is no automatic role aggregation supported for the `rancher-cis-benchmark` ClusterRoles. diff --git a/versioned_docs/version-2.6/cis-scans/skipped-tests/skipped-tests.md b/versioned_docs/version-2.6/cis-scans/skipped-tests/skipped-tests.md deleted file mode 100644 index f2b125c0262..00000000000 --- a/versioned_docs/version-2.6/cis-scans/skipped-tests/skipped-tests.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Skipped and Not Applicable Tests -weight: 3 ---- - -This section lists the tests that are skipped in the permissive test profile for RKE. - -> All the tests that are skipped and not applicable on this page will be counted as Not Applicable in the v2.5 generated report. The skipped test count will only mention the user-defined skipped tests. This allows user-skipped tests to be distinguished from the tests that are skipped by default in the RKE permissive test profile. - -# CIS Benchmark v1.5 - -### CIS Benchmark v1.5 Skipped Tests - -| Number | Description | Reason for Skipping | -| ---------- | ------------- | --------- | -| 1.1.12 | Ensure that the etcd data directory ownership is set to etcd:etcd (Automated) | A system service account is required for etcd data directory ownership. Refer to Rancher's hardening guide for more details on how to configure this ownership. | -| 1.2.6 | Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated) | When generating serving certificates, functionality could break in conjunction with hostname overrides which are required for certain cloud providers. | -| 1.2.16 | Ensure that the admission control plugin PodSecurityPolicy is set (Automated) | Enabling Pod Security Policy can cause applications to unexpectedly fail. | -| 1.2.33 | Ensure that the --encryption-provider-config argument is set as appropriate (Manual) | Enabling encryption changes how data can be recovered as data is encrypted. | -| 1.2.34 | Ensure that encryption providers are appropriately configured (Manual) | Enabling encryption changes how data can be recovered as data is encrypted. | -| 4.2.6 | Ensure that the --protect-kernel-defaults argument is set to true (Automated) | System level configurations are required before provisioning the cluster in order for this argument to be set to true. | -| 4.2.10 | Ensure that the--tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated) | When generating serving certificates, functionality could break in conjunction with hostname overrides which are required for certain cloud providers. | -| 5.1.5 | Ensure that default service accounts are not actively used. (Automated) | Kubernetes provides default service accounts to be used. | -| 5.2.2 | Minimize the admission of containers wishing to share the host process ID namespace (Automated) | Enabling Pod Security Policy can cause applications to unexpectedly fail. | -| 5.2.3 | Minimize the admission of containers wishing to share the host IPC namespace (Automated) | Enabling Pod Security Policy can cause applications to unexpectedly fail. | -| 5.2.4 | Minimize the admission of containers wishing to share the host network namespace (Automated) | Enabling Pod Security Policy can cause applications to unexpectedly fail. | -| 5.2.5 | Minimize the admission of containers with allowPrivilegeEscalation (Automated) | Enabling Pod Security Policy can cause applications to unexpectedly fail. | -| 5.3.2 | Ensure that all Namespaces have Network Policies defined (Automated) | Enabling Network Policies can prevent certain applications from communicating with each other. | -| 5.6.4 | The default namespace should not be used (Automated) | Kubernetes provides a default namespace. | - -### CIS Benchmark v1.5 Not Applicable Tests - -| Number | Description | Reason for being not applicable | -| ---------- | ------------- | --------- | -| 1.1.1 | Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for kube-apiserver. All configuration is passed in as arguments at container run time. | -| 1.1.2 | Ensure that the API server pod specification file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for kube-apiserver. All configuration is passed in as arguments at container run time. | -| 1.1.3 | Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for controller-manager. All configuration is passed in as arguments at container run time. | -| 1.1.4 | Ensure that the controller manager pod specification file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for controller-manager. All configuration is passed in as arguments at container run time. | -| 1.1.5 | Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for scheduler. All configuration is passed in as arguments at container run time. | -| 1.1.6 | Ensure that the scheduler pod specification file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for scheduler. All configuration is passed in as arguments at container run time. | -| 1.1.7 | Ensure that the etcd pod specification file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for etcd. All configuration is passed in as arguments at container run time. | -| 1.1.8 | Ensure that the etcd pod specification file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for etcd. All configuration is passed in as arguments at container run time. | -| 1.1.13 | Ensure that the admin.conf file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE does not store the kubernetes default kubeconfig credentials file on the nodes. | -| 1.1.14 | Ensure that the admin.conf file ownership is set to root:root (Automated) | Clusters provisioned by RKE does not store the kubernetes default kubeconfig credentials file on the nodes. | -| 1.1.15 | Ensure that the scheduler.conf file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for scheduler. All configuration is passed in as arguments at container run time. | -| 1.1.16 | Ensure that the scheduler.conf file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for scheduler. All configuration is passed in as arguments at container run time. | -| 1.1.17 | Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for controller-manager. All configuration is passed in as arguments at container run time. | -| 1.1.18 | Ensure that the controller-manager.conf file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn't require or maintain a configuration file for controller-manager. All configuration is passed in as arguments at container run time. | -| 1.3.6 | Ensure that the RotateKubeletServerCertificate argument is set to true (Automated) | Clusters provisioned by RKE handles certificate rotation directly through RKE. | -| 4.1.1 | Ensure that the kubelet service file permissions are set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn’t require or maintain a configuration file for the kubelet service. All configuration is passed in as arguments at container run time. | -| 4.1.2 | Ensure that the kubelet service file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn’t require or maintain a configuration file for the kubelet service. All configuration is passed in as arguments at container run time. | -| 4.1.9 | Ensure that the kubelet configuration file has permissions set to 644 or more restrictive (Automated) | Clusters provisioned by RKE doesn’t require or maintain a configuration file for the kubelet. All configuration is passed in as arguments at container run time. | -| 4.1.10 | Ensure that the kubelet configuration file ownership is set to root:root (Automated) | Clusters provisioned by RKE doesn’t require or maintain a configuration file for the kubelet. All configuration is passed in as arguments at container run time. | -| 4.2.12 | Ensure that the RotateKubeletServerCertificate argument is set to true (Automated) | Clusters provisioned by RKE handles certificate rotation directly through RKE. | \ No newline at end of file diff --git a/versioned_docs/version-2.6/cli/cli.md b/versioned_docs/version-2.6/cli/cli.md deleted file mode 100644 index 67c688c3b85..00000000000 --- a/versioned_docs/version-2.6/cli/cli.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -title: CLI with Rancher -description: Interact with Rancher using command line interface (CLI) tools from your workstation. -weight: 21 ---- - -- [Rancher CLI](#rancher-cli) - - [Download Rancher CLI](#download-rancher-cli) - - [Requirements](#requirements) - - [CLI Authentication](#cli-authentication) - - [Project Selection](#project-selection) - - [Commands](#commands) - - [Rancher CLI Help](#rancher-cli-help) - - [Limitations](#limitations) -- [kubectl](#kubectl) - - [kubectl Utility](#kubectl-utility) - - [Authentication with kubectl and kubeconfig Tokens with TTL](#authentication-with-kubectl-and-kubeconfig-tokens-with-ttl) - -# Rancher CLI - -The Rancher CLI (Command Line Interface) is a unified tool that you can use to interact with Rancher. With this tool, you can operate Rancher using a command line rather than the GUI. - -### Download Rancher CLI - -The binary can be downloaded directly from the UI. The link can be found in the right hand side of the footer in the UI. We have binaries for Windows, Mac, and Linux. You can also check the [releases page for our CLI](https://github.com/rancher/cli/releases) for direct downloads of the binary. - -1. In the upper left corner, click **☰**. -1. At the bottom, click **v2.6.x**, where **v2.6.x** is a hyperlinked text indicating the installed Rancher version. -1. Under the **CLI Downloads section**, there are links to download the binaries for Windows, Mac, and Linux. You can also check the [releases page for our CLI](https://github.com/rancher/cli/releases) for direct downloads of the binary. - -### Requirements - -After you download the Rancher CLI, you need to make a few configurations. Rancher CLI requires: - -- Your Rancher Server URL, which is used to connect to Rancher Server. -- An API Bearer Token, which is used to authenticate with Rancher. For more information about obtaining a Bearer Token, see [Creating an API Key]({{}}/rancher/v2.6/en/user-settings/api-keys/). - -### CLI Authentication - -Before you can use Rancher CLI to control your Rancher Server, you must authenticate using an API Bearer Token. Log in using the following command (replace `` and `` with your information): - -```bash -$ ./rancher login https:// --token -``` - -If Rancher Server uses a self-signed certificate, Rancher CLI prompts you to continue with the connection. - -### Project Selection - -Before you can perform any commands, you must select a Rancher project to perform those commands against. To select a [project]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/) to work on, use the command `./rancher context switch`. When you enter this command, a list of available projects displays. Enter a number to choose your project. - -**Example: `./rancher context switch` Output** -``` -User:rancher-cli-directory user$ ./rancher context switch -NUMBER CLUSTER NAME PROJECT ID PROJECT NAME -1 cluster-2 c-7q96s:p-h4tmb project-2 -2 cluster-2 c-7q96s:project-j6z6d Default -3 cluster-1 c-lchzv:p-xbpdt project-1 -4 cluster-1 c-lchzv:project-s2mch Default -Select a Project: -``` - -After you enter a number, the console displays a message that you've changed projects. - -``` -INFO[0005] Setting new context to project project-1 -INFO[0005] Saving config to /Users/markbishop/.rancher/cli2.json -``` - -Ensure you can run `rancher kubectl get pods` successfully. - -### Commands - -The following commands are available for use in Rancher CLI. - -| Command | Result | -|---|---| -| `apps, [app]` | Performs operations on catalog applications (i.e., individual [Helm charts](https://docs.helm.sh/developing_charts/)) or Rancher charts. | -| `catalog` | Performs operations on [catalogs]({{}}/rancher/v2.6/en/helm-charts/). | -| `clusters, [cluster]` | Performs operations on your [clusters]({{}}/rancher/v2.6/en/cluster-provisioning/). | -| `context` | Switches between Rancher [projects]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/). For an example, see [Project Selection](#project-selection). | -| `inspect [OPTIONS] [RESOURCEID RESOURCENAME]` | Displays details about [Kubernetes resources](https://kubernetes.io/docs/reference/kubectl/cheatsheet/#resource-types) or Rancher resources (i.e.: [projects]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/) and [workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/)). Specify resources by name or ID. | -| `kubectl` |Runs [kubectl commands](https://kubernetes.io/docs/reference/kubectl/overview/#operations). | -| `login, [l]` | Logs into a Rancher Server. For an example, see [CLI Authentication](#cli-authentication). | -| `namespaces, [namespace]` |Performs operations on namespaces. | -| `nodes, [node]` |Performs operations on nodes. | -| `projects, [project]` | Performs operations on [projects]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/). | -| `ps` | Displays [workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads) in a project. | -| `settings, [setting]` | Shows the current settings for your Rancher Server. | -| `ssh` | Connects to one of your cluster nodes using the SSH protocol. | -| `help, [h]` | Shows a list of commands or help for one command. | - - -### Rancher CLI Help - -Once logged into Rancher Server using the CLI, enter `./rancher --help` for a list of commands. - -All commands accept the `--help` flag, which documents each command's usage. - -### Limitations - -The Rancher CLI **cannot** be used to install [dashboard apps or Rancher feature charts](../helm-charts/). - -# kubectl - -Interact with Rancher using kubectl. - -### kubectl Utility - -Install the `kubectl` utility. See [install kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/). - -Configure kubectl by visiting your cluster in the Rancher Web UI, clicking on `Kubeconfig`, copying contents, and putting them into your `~/.kube/config` file. - -Run `kubectl cluster-info` or `kubectl get pods` successfully. - -### Authentication with kubectl and kubeconfig Tokens with TTL - -_Requirements_ - -If admins have [enforced TTL on kubeconfig tokens]({{}}/rancher/v2.6/en/api/api-tokens/#setting-ttl-on-kubeconfig-tokens), the kubeconfig file requires the [Rancher CLI](../cli) to be present in your PATH when you run `kubectl`. Otherwise, you’ll see an error like: -`Unable to connect to the server: getting credentials: exec: exec: "rancher": executable file not found in $PATH`. - -This feature enables kubectl to authenticate with the Rancher server and get a new kubeconfig token when required. The following auth providers are currently supported: - -1. Local -2. Active Directory (LDAP only) -3. FreeIPA -4. OpenLDAP -5. SAML providers: Ping, Okta, ADFS, Keycloak, Shibboleth - -When you first run kubectl, for example, `kubectl get pods`, it will ask you to pick an auth provider and log in with the Rancher server. -The kubeconfig token is cached in the path where you run kubectl under `./.cache/token`. This token is valid until [it expires](../api/api-tokens/#setting-ttl-on-kubeconfig-tokens-period), or [gets deleted from the Rancher server](../api/api-tokens/#deleting-tokens). -Upon expiration, the next `kubectl get pods` will ask you to log in with the Rancher server again. diff --git a/versioned_docs/version-2.6/cluster-admin/backing-up-etcd/backing-up-etcd.md b/versioned_docs/version-2.6/cluster-admin/backing-up-etcd/backing-up-etcd.md deleted file mode 100644 index 7602c62450a..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/backing-up-etcd/backing-up-etcd.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -title: Backing up a Cluster -weight: 2045 ---- - -In the Rancher UI, etcd backup and recovery for [Rancher launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) can be easily performed. - -Rancher recommends configuring recurrent `etcd` snapshots for all production clusters. Additionally, one-time snapshots can easily be taken as well. - -Snapshots of the etcd database are taken and saved either [locally onto the etcd nodes](#local-backup-target) or to a [S3 compatible target](#s3-backup-target). The advantages of configuring S3 is that if all etcd nodes are lost, your snapshot is saved remotely and can be used to restore the cluster. - -This section covers the following topics: - -- [How snapshots work](#how-snapshots-work) -- [Configuring recurring snapshots](#configuring-recurring-snapshots) -- [One-time snapshots](#one-time-snapshots) -- [Snapshot backup targets](#snapshot-backup-targets) - - [Local backup target](#local-backup-target) - - [S3 backup target](#s3-backup-target) - - [Using a custom CA certificate for S3](#using-a-custom-ca-certificate-for-s3) - - [IAM Support for storing snapshots in S3](#iam-support-for-storing-snapshots-in-s3) -- [Viewing available snapshots](#viewing-available-snapshots) -- [Safe timestamps](#safe-timestamps) -- [Enabling snapshot features for clusters created before Rancher v2.2.0](#enabling-snapshot-features-for-clusters-created-before-rancher-v2-2-0) - -# How Snapshots Work - -### Snapshot Components - -When Rancher creates a snapshot, it includes three components: - -- The cluster data in etcd -- The Kubernetes version -- The cluster configuration in the form of the `cluster.yml` - -Because the Kubernetes version is now included in the snapshot, it is possible to restore a cluster to a prior Kubernetes version. - -The multiple components of the snapshot allow you to select from the following options if you need to restore a cluster from a snapshot: - -- **Restore just the etcd contents:** This restore is similar to restoring to snapshots in Rancher before v2.4.0. -- **Restore etcd and Kubernetes version:** This option should be used if a Kubernetes upgrade is the reason that your cluster is failing, and you haven't made any cluster configuration changes. -- **Restore etcd, Kubernetes versions and cluster configuration:** This option should be used if you changed both the Kubernetes version and cluster configuration when upgrading. - -It's always recommended to take a new snapshot before any upgrades. - -### Generating the Snapshot from etcd Nodes - -For each etcd node in the cluster, the etcd cluster health is checked. If the node reports that the etcd cluster is healthy, a snapshot is created from it and optionally uploaded to S3. - -The snapshot is stored in `/opt/rke/etcd-snapshots`. If the directory is configured on the nodes as a shared mount, it will be overwritten. On S3, the snapshot will always be from the last node that uploads it, as all etcd nodes upload it and the last will remain. - -In the case when multiple etcd nodes exist, any created snapshot is created after the cluster has been health checked, so it can be considered a valid snapshot of the data in the etcd cluster. - -### Snapshot Naming Conventions - -The name of the snapshot is auto-generated. The `--name` option can be used to override the name of the snapshot when creating one-time snapshots with the RKE CLI. - -When Rancher creates a snapshot of an RKE cluster, the snapshot name is based on the type (whether the snapshot is manual or recurring) and the target (whether the snapshot is saved locally or uploaded to S3). The naming convention is as follows: - -- `m` stands for manual -- `r` stands for recurring -- `l` stands for local -- `s` stands for S3 - -Some example snapshot names are: - -- c-9dmxz-rl-8b2cx -- c-9dmxz-ml-kr56m -- c-9dmxz-ms-t6bjb -- c-9dmxz-rs-8gxc8 - -### How Restoring from a Snapshot Works - -On restore, the following process is used: - -1. The snapshot is retrieved from S3, if S3 is configured. -2. The snapshot is unzipped (if zipped). -3. One of the etcd nodes in the cluster serves that snapshot file to the other nodes. -4. The other etcd nodes download the snapshot and validate the checksum so that they all use the same snapshot for the restore. -5. The cluster is restored and post-restore actions will be done in the cluster. - -# Configuring Recurring Snapshots - -Select how often you want recurring snapshots to be taken as well as how many snapshots to keep. The amount of time is measured in hours. With timestamped snapshots, the user has the ability to do a point-in-time recovery. - -By default, [Rancher launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) are configured to take recurring snapshots (saved to local disk). To protect against local disk failure, using the [S3 Target](#s3-backup-target) or replicating the path on disk is advised. - -During cluster provisioning or editing the cluster, the configuration for snapshots can be found in the advanced section for **Cluster Options**. Click on **Show advanced options**. - -In the **Advanced Cluster Options** section, there are several options available to configure: - -| Option | Description | Default Value| -| --- | ---| --- | -| etcd Snapshot Backup Target | Select where you want the snapshots to be saved. Options are either local or in S3 | local| -|Recurring etcd Snapshot Enabled| Enable/Disable recurring snapshots | Yes| -| Recurring etcd Snapshot Creation Period | Time in hours between recurring snapshots| 12 hours | -| Recurring etcd Snapshot Retention Count | Number of snapshots to retain| 6 | - -# One-Time Snapshots - -In addition to recurring snapshots, you may want to take a "one-time" snapshot. For example, before upgrading the Kubernetes version of a cluster it's best to backup the state of the cluster to protect against upgrade failure. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, navigate to the cluster where you want to take a one-time snapshot. -1. Click **⋮ > Take Snapshot**. - -**Result:** Based on your [snapshot backup target](#snapshot-backup-targets), a one-time snapshot will be taken and saved in the selected backup target. - -# Snapshot Backup Targets - -Rancher supports two different backup targets: - -* [Local Target](#local-backup-target) -* [S3 Target](#s3-backup-target) - -### Local Backup Target - -By default, the `local` backup target is selected. The benefits of this option is that there is no external configuration. Snapshots are automatically saved locally to the etcd nodes in the [Rancher launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) in `/opt/rke/etcd-snapshots`. All recurring snapshots are taken at configured intervals. The downside of using the `local` backup target is that if there is a total disaster and _all_ etcd nodes are lost, there is no ability to restore the cluster. - -### S3 Backup Target - -The `S3` backup target allows users to configure a S3 compatible backend to store the snapshots. The primary benefit of this option is that if the cluster loses all the etcd nodes, the cluster can still be restored as the snapshots are stored externally. Rancher recommends external targets like `S3` backup, however its configuration requirements do require additional effort that should be considered. - -| Option | Description | Required| -|---|---|---| -|S3 Bucket Name| S3 bucket name where backups will be stored| *| -|S3 Region|S3 region for the backup bucket| | -|S3 Region Endpoint|S3 regions endpoint for the backup bucket|* | -|S3 Access Key|S3 access key with permission to access the backup bucket|*| -|S3 Secret Key|S3 secret key with permission to access the backup bucket|*| -| Custom CA Certificate | A custom certificate used to access private S3 backends || - -### Using a custom CA certificate for S3 - -The backup snapshot can be stored on a custom `S3` backup like [minio](https://min.io/). If the S3 back end uses a self-signed or custom certificate, provide a custom certificate using the `Custom CA Certificate` option to connect to the S3 backend. - -### IAM Support for Storing Snapshots in S3 - -The `S3` backup target supports using IAM authentication to AWS API in addition to using API credentials. An IAM role gives temporary permissions that an application can use when making API calls to S3 storage. To use IAM authentication, the following requirements must be met: - - - The cluster etcd nodes must have an instance role that has read/write access to the designated backup bucket. - - The cluster etcd nodes must have network access to the specified S3 endpoint. - - The Rancher Server worker node(s) must have an instance role that has read/write to the designated backup bucket. - - The Rancher Server worker node(s) must have network access to the specified S3 endpoint. - - To give an application access to S3, refer to the AWS documentation on [Using an IAM Role to Grant Permissions to Applications Running on Amazon EC2 Instances.](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2.html) - -# Viewing Available Snapshots - -The list of all available snapshots for the cluster is available in the Rancher UI. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the **Clusters** page, go to the cluster where you want to view the snapshots and click its name. -1. Click the **Snapshots** tab to view the list of saved snapshots. These snapshots include a timestamp of when they were created. - -# Safe Timestamps - -Snapshot files are timestamped to simplify processing the files using external tools and scripts, but in some S3 compatible backends, these timestamps were unusable. - -The option `safe_timestamp` is added to support compatible file names. When this flag is set to `true`, all special characters in the snapshot filename timestamp are replaced. - -This option is not available directly in the UI, and is only available through the `Edit as Yaml` interface. - -# Enabling Snapshot Features for Clusters Created Before Rancher v2.2.0 - -If you have any Rancher launched Kubernetes clusters that were created before v2.2.0, after upgrading Rancher, you must [edit the cluster]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/) and _save_ it, in order to enable the updated snapshot features. Even if you were already creating snapshots before v2.2.0, you must do this step as the older snapshots will not be available to use to [back up and restore etcd through the UI]({{}}/rancher/v2.6/en/cluster-admin/restoring-etcd/). diff --git a/versioned_docs/version-2.6/cluster-admin/certificate-rotation/certificate-rotation.md b/versioned_docs/version-2.6/cluster-admin/certificate-rotation/certificate-rotation.md deleted file mode 100644 index e813cb5fe44..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/certificate-rotation/certificate-rotation.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Certificate Rotation -weight: 2040 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -> **Warning:** Rotating Kubernetes certificates may result in your cluster being temporarily unavailable as components are restarted. For production environments, it's recommended to perform this action during a maintenance window. - -By default, Kubernetes clusters require certificates and Rancher launched Kubernetes clusters automatically generate certificates for the Kubernetes components. Rotating these certificates is important before the certificates expire as well as if a certificate is compromised. After the certificates are rotated, the Kubernetes components are automatically restarted. - -Certificates can be rotated for the following services: - - - - -- etcd -- kubelet (node certificate) -- kubelet (serving certificate, if [enabled]({{}}/rke/latest/en/config-options/services/#kubelet-options)) -- kube-apiserver -- kube-proxy -- kube-scheduler -- kube-controller-manager - - - - -- admin -- api-server -- controller-manager -- scheduler -- rke2-controller -- rke2-server -- cloud-controller -- etcd -- auth-proxy -- kubelet -- kube-proxy - - - - -> **Note:** For users who didn't rotate their webhook certificates, and they have expired after one year, please see this [page]({{}}/rancher/v2.6/en/troubleshooting/expired-webhook-certificates/) for help. - - -### Certificate Rotation - -Rancher launched Kubernetes clusters have the ability to rotate the auto-generated certificates through the UI. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster you want to rotate certificates for amd click **⋮ > Rotate Certificates**. -1. Select which certificates that you want to rotate. - - * Rotate all Service certificates (keep the same CA) - * Rotate an individual service and choose one of the services from the drop-down menu - -1. Click **Save**. - -**Results:** The selected certificates will be rotated and the related services will be restarted to start using the new certificate. - -### Additional Notes - - - - -Even though the RKE CLI can use custom certificates for the Kubernetes cluster components, Rancher currently doesn't allow the ability to upload these in Rancher launched Kubernetes clusters. - - - - -In RKE2, both etcd and control plane nodes are treated as the same `server` concept. As such, when rotating certificates of services specific to either of these components will result in certificates being rotated on both. The certificates will only change for the specified service, but you will see nodes for both components go into an updating state. You may also see worker only nodes go into an updating state. This is to restart the workers after a certificate change to ensure they get the latest client certs. - - - diff --git a/versioned_docs/version-2.6/cluster-admin/cleaning-cluster-nodes/cleaning-cluster-nodes.md b/versioned_docs/version-2.6/cluster-admin/cleaning-cluster-nodes/cleaning-cluster-nodes.md deleted file mode 100644 index 72a62554f29..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cleaning-cluster-nodes/cleaning-cluster-nodes.md +++ /dev/null @@ -1,285 +0,0 @@ ---- -title: Removing Kubernetes Components from Nodes -description: Learn about cluster cleanup when removing nodes from your Rancher-launched Kubernetes cluster. What is removed, how to do it manually -weight: 2055 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This section describes how to disconnect a node from a Rancher-launched Kubernetes cluster and remove all of the Kubernetes components from the node. This process allows you to use the node for other purposes. - -When you use Rancher to install Kubernetes on new nodes in an infrastructure provider, resources (containers/virtual network interfaces) and configuration items (certificates/configuration files) are created. - -When removing nodes from your Rancher launched Kubernetes cluster (provided that they are in `Active` state), those resources are automatically cleaned, and the only action needed is to restart the node. When a node has become unreachable and the automatic cleanup process cannot be used, we describe the steps that need to be executed before the node can be added to a cluster again. - -## What Gets Removed? - -When cleaning nodes provisioned using Rancher, the following components are deleted based on the type of cluster node you're removing. - -| Removed Component | [Nodes Hosted by Infrastructure Provider][1] | [Custom Nodes][2] | [Hosted Cluster][3] | [Registered Nodes][4] | -| ------------------------------------------------------------------------------ | --------------- | ----------------- | ------------------- | ------------------- | -| The Rancher deployment namespace (`cattle-system` by default) | ✓ | ✓ | ✓ | ✓ | -| `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` labeled by Rancher | ✓ | ✓ | ✓ | ✓ | -| Labels, Annotations, and Finalizers | ✓ | ✓ | ✓ | ✓ | -| Rancher Deployment | ✓ | ✓ | ✓ | | -| Machines, clusters, projects, and user custom resource definitions (CRDs) | ✓ | ✓ | ✓ | | -| All resources create under the `management.cattle.io` API Group | ✓ | ✓ | ✓ | | -| All CRDs created by Rancher v2.x | ✓ | ✓ | ✓ | | - -[1]: {{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ -[2]: {{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/ -[3]: {{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/ -[4]: {{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/ - -## Removing a Node from a Cluster by Rancher UI - -When the node is in `Active` state, removing the node from a cluster will trigger a process to clean up the node. Please restart the node after the automatic cleanup process is done to make sure any non-persistent data is properly removed. - -**To restart a node:** - -``` -# using reboot -$ sudo reboot - -# using shutdown -$ sudo shutdown -r now -``` - -## Removing Rancher Components from a Cluster Manually - -When a node is unreachable and removed from the cluster, the automatic cleaning process can't be triggered because the node is unreachable. Please follow the steps below to manually remove the Rancher components. - ->**Warning:** The commands listed below will remove data from the node. Make sure you have created a backup of files you want to keep before executing any of the commands as data will be lost. - -### Removing Rancher Components from Registered Clusters - -For registered clusters, the process for removing Rancher is a little different. You have the option of simply deleting the cluster in the Rancher UI, or your can run a script that removes Rancher components from the nodes. Both options make the same deletions. - -After the registered cluster is detached from Rancher, the cluster's workloads will be unaffected and you can access the cluster using the same methods that you did before the cluster was registered into Rancher. - - - - ->**Warning:** This process will remove data from your cluster. Make sure you have created a backup of files you want to keep before executing the command, as data will be lost. - -After you initiate the removal of a registered cluster using the Rancher UI (or API), the following events occur. - -1. Rancher creates a `serviceAccount` that it uses to remove the Rancher components from the cluster. This account is assigned the [clusterRole](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole) and [clusterRoleBinding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) permissions, which are required to remove the Rancher components. - -1. Using the `serviceAccount`, Rancher schedules and runs a [job](https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/) that cleans the Rancher components off of the cluster. This job also references the `serviceAccount` and its roles as dependencies, so the job deletes them before its completion. - -1. Rancher is removed from the cluster. However, the cluster persists, running the native version of Kubernetes. - -**Result:** All components listed for registered clusters in [What Gets Removed?](#what-gets-removed) are deleted. - - - - - -Rather than cleaning registered cluster nodes using the Rancher UI, you can run a script instead. - ->**Prerequisite:** -> ->Install [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/). - -1. Open a web browser, navigate to [GitHub](https://github.com/rancher/rancher/blob/master/cleanup/user-cluster.sh), and download `user-cluster.sh`. - -1. Make the script executable by running the following command from the same directory as `user-cluster.sh`: - - ``` - chmod +x user-cluster.sh - ``` - -1. **Air Gap Environments Only:** Open `user-cluster.sh` and replace `yaml_url` with the URL in `user-cluster.yml`. - - If you don't have an air gap environment, skip this step. - -1. From the same directory, run the script and provide the `rancher/rancher-agent` image version which should be equal to the version of Rancher used to manage the cluster. (``): - - >**Tip:** - > - >Add the `-dry-run` flag to preview the script's outcome without making changes. - ``` - ./user-cluster.sh rancher/rancher-agent: - ``` - -**Result:** The script runs. All components listed for registered clusters in [What Gets Removed?](#what-gets-removed) are deleted. - - - - -### Windows Nodes - -To clean up a Windows node, you can run a cleanup script located in `c:\etc\rancher`. The script deletes Kubernetes generated resources and the execution binary. It also drops the firewall rules and network settings. - -To run the script, you can use this command in the PowerShell: - -``` -pushd c:\etc\rancher -.\cleanup.ps1 -popd -``` - -**Result:** The node is reset and can be re-added to a Kubernetes cluster. - -### Docker Containers, Images, and Volumes - -Based on what role you assigned to the node, there are Kubernetes components in containers, containers belonging to overlay networking, DNS, ingress controller and Rancher agent. (and pods you created that have been scheduled to this node) - -**To clean all Docker containers, images and volumes:** - -``` -docker rm -f $(docker ps -qa) -docker rmi -f $(docker images -q) -docker volume rm $(docker volume ls -q) -``` - -### Mounts - -Kubernetes components and secrets leave behind mounts on the system that need to be unmounted. - -Mounts | ---------| -`/var/lib/kubelet/pods/XXX` (miscellaneous mounts) | -`/var/lib/kubelet` | -`/var/lib/rancher` | - -**To unmount all mounts:** - -``` -for mount in $(mount | grep tmpfs | grep '/var/lib/kubelet' | awk '{ print $3 }') /var/lib/kubelet /var/lib/rancher; do umount $mount; done -``` - -### Directories and Files - -The following directories are used when adding a node to a cluster, and should be removed. You can remove a directory using `rm -rf /directory_name`. - ->**Note:** Depending on the role you assigned to the node, some of the directories will or won't be present on the node. - -Directories | ---------| -`/etc/ceph` | -`/etc/cni` | -`/etc/kubernetes` | -`/opt/cni` | -`/opt/rke` | -`/run/secrets/kubernetes.io` | -`/run/calico` | -`/run/flannel` | -`/var/lib/calico` | -`/var/lib/etcd` | -`/var/lib/cni` | -`/var/lib/kubelet` | -`/var/lib/rancher/rke/log` | -`/var/log/containers` | -`/var/log/kube-audit` | -`/var/log/pods` | -`/var/run/calico` | - -**To clean the directories:** - -``` -rm -rf /etc/ceph \ - /etc/cni \ - /etc/kubernetes \ - /opt/cni \ - /opt/rke \ - /run/secrets/kubernetes.io \ - /run/calico \ - /run/flannel \ - /var/lib/calico \ - /var/lib/etcd \ - /var/lib/cni \ - /var/lib/kubelet \ - /var/lib/rancher/rke/log \ - /var/log/containers \ - /var/log/kube-audit \ - /var/log/pods \ - /var/run/calico -``` - -### Network Interfaces and Iptables - -The remaining two components that are changed/configured are (virtual) network interfaces and iptables rules. Both are non-persistent to the node, meaning that they will be cleared after a restart of the node. To remove these components, a restart is recommended. - -**To restart a node:** - -``` -# using reboot -$ sudo reboot - -# using shutdown -$ sudo shutdown -r now -``` - -If you want to know more on (virtual) network interfaces or iptables rules, please see the specific subjects below. - -### Network Interfaces - ->**Note:** Depending on the network provider configured for the cluster the node was part of, some of the interfaces will or won't be present on the node. - -Interfaces | ---------| -`flannel.1` | -`cni0` | -`tunl0` | -`caliXXXXXXXXXXX` (random interface names) | -`vethXXXXXXXX` (random interface names) | - -**To list all interfaces:** - -``` -# Using ip -ip address show - -# Using ifconfig -ifconfig -a -``` - -**To remove an interface:** - -``` -ip link delete interface_name -``` - -### Iptables - ->**Note:** Depending on the network provider configured for the cluster the node was part of, some of the chains will or won't be present on the node. - -Iptables rules are used to route traffic from and to containers. The created rules are not persistent, so restarting the node will restore iptables to its original state. - -Chains | ---------| -`cali-failsafe-in` | -`cali-failsafe-out` | -`cali-fip-dnat` | -`cali-fip-snat` | -`cali-from-hep-forward` | -`cali-from-host-endpoint` | -`cali-from-wl-dispatch` | -`cali-fw-caliXXXXXXXXXXX` (random chain names) | -`cali-nat-outgoing` | -`cali-pri-kns.NAMESPACE` (chain per namespace) | -`cali-pro-kns.NAMESPACE` (chain per namespace) | -`cali-to-hep-forward` | -`cali-to-host-endpoint` | -`cali-to-wl-dispatch` | -`cali-tw-caliXXXXXXXXXXX` (random chain names) | -`cali-wl-to-host` | -`KUBE-EXTERNAL-SERVICES` | -`KUBE-FIREWALL` | -`KUBE-MARK-DROP` | -`KUBE-MARK-MASQ` | -`KUBE-NODEPORTS` | -`KUBE-SEP-XXXXXXXXXXXXXXXX` (random chain names) | -`KUBE-SERVICES` | -`KUBE-SVC-XXXXXXXXXXXXXXXX` (random chain names) | - -**To list all iptables rules:** - -``` -iptables -L -t nat -iptables -L -t mangle -iptables -L -``` diff --git a/versioned_docs/version-2.6/cluster-admin/cloning-clusters/cloning-clusters.md b/versioned_docs/version-2.6/cluster-admin/cloning-clusters/cloning-clusters.md deleted file mode 100644 index 39da7fa7310..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cloning-clusters/cloning-clusters.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: Cloning Clusters -weight: 2035 ---- - -If you have a cluster in Rancher that you want to use as a template for creating similar clusters, you can use Rancher CLI to clone the cluster's configuration, edit it, and then use it to quickly launch the cloned cluster. - -Duplication of registered clusters is not supported. - -| Cluster Type | Cloneable? | -|----------------------------------|---------------| -| [Nodes Hosted by Infrastructure Provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) | ✓ | -| [Hosted Kubernetes Providers]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/) | ✓ | -| [Custom Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes) | ✓ | -| [Registered Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/) | | - -> **Warning:** During the process of duplicating a cluster, you will edit a config file full of cluster settings. However, we recommend editing only values explicitly listed in this document, as cluster duplication is designed for simple cluster copying, _not_ wide scale configuration changes. Editing other values may invalidate the config file, which will lead to cluster deployment failure. - -## Prerequisites - -Download and install [Rancher CLI]({{}}/rancher/v2.6/en/cli). Remember to [create an API bearer token]({{}}/rancher/v2.6/en/user-settings/api-keys) if necessary. - - -## 1. Export Cluster Config - -Begin by using Rancher CLI to export the configuration for the cluster that you want to clone. - -1. Open Terminal and change your directory to the location of the Rancher CLI binary, `rancher`. - -1. Enter the following command to list the clusters managed by Rancher. - - - ./rancher cluster ls - - -1. Find the cluster that you want to clone, and copy either its resource `ID` or `NAME` to your clipboard. From this point on, we'll refer to the resource `ID` or `NAME` as ``, which is used as a placeholder in the next step. - -1. Enter the following command to export the configuration for your cluster. - - - ./rancher clusters export - - - **Step Result:** The YAML for a cloned cluster prints to Terminal. - -1. Copy the YAML to your clipboard and paste it in a new file. Save the file as `cluster-template.yml` (or any other name, as long as it has a `.yml` extension). - -## 2. Modify Cluster Config - -Use your favorite text editor to modify the cluster configuration in `cluster-template.yml` for your cloned cluster. - -> **Note:** Cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#config-file-structure-in-rancher-v2-3-0) - -1. Open `cluster-template.yml` (or whatever you named your config) in your favorite text editor. - - >**Warning:** Only edit the cluster config values explicitly called out below. Many of the values listed in this file are used to provision your cloned cluster, and editing their values may break the provisioning process. - - -1. As depicted in the example below, at the `` placeholder, replace your original cluster's name with a unique name (``). If your cloned cluster has a duplicate name, the cluster will not provision successfully. - - ```yml - Version: v3 - clusters: - : # ENTER UNIQUE NAME - dockerRootDir: /var/lib/docker - enableNetworkPolicy: false - rancherKubernetesEngineConfig: - addonJobTimeout: 30 - authentication: - strategy: x509 - authorization: {} - bastionHost: {} - cloudProvider: {} - ignoreDockerVersion: true - ``` - -1. For each `nodePools` section, replace the original nodepool name with a unique name at the `` placeholder. If your cloned cluster has a duplicate nodepool name, the cluster will not provision successfully. - - ```yml - nodePools: - : - clusterId: do - controlPlane: true - etcd: true - hostnamePrefix: mark-do - nodeTemplateId: do - quantity: 1 - worker: true - ``` - -1. When you're done, save and close the configuration. - -## 3. Launch Cloned Cluster - -Move `cluster-template.yml` into the same directory as the Rancher CLI binary. Then run this command: - - ./rancher up --file cluster-template.yml - -**Result:** Your cloned cluster begins provisioning. Enter `./rancher cluster ls` to confirm. diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-access/ace/ace.md b/versioned_docs/version-2.6/cluster-admin/cluster-access/ace/ace.md deleted file mode 100644 index c7776bb0543..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-access/ace/ace.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: How the Authorized Cluster Endpoint Works -weight: 2015 ---- - -This section describes how the kubectl CLI, the kubeconfig file, and the authorized cluster endpoint work together to allow you to access a downstream Kubernetes cluster directly, without authenticating through the Rancher server. It is intended to provide background information and context to the instructions for [how to set up kubectl to directly access a cluster.](../kubectl/#authenticating-directly-with-a-downstream-cluster) - -### About the kubeconfig File - -The _kubeconfig file_ is a file used to configure access to Kubernetes when used in conjunction with the kubectl command line tool (or other clients). - -This kubeconfig file and its contents are specific to the cluster you are viewing. It can be downloaded from the cluster view in Rancher. You will need a separate kubeconfig file for each cluster that you have access to in Rancher. - -After you download the kubeconfig file, you will be able to use the kubeconfig file and its Kubernetes [contexts](https://kubernetes.io/docs/reference/kubectl/cheatsheet/#kubectl-context-and-configuration) to access your downstream cluster. - -If admins have [enforced TTL on kubeconfig tokens]({{}}/rancher/v2.6/en/api/api-tokens/#setting-ttl-on-kubeconfig-tokens), the kubeconfig file requires [rancher cli]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/ace) to be present in your PATH. - - -### Two Authentication Methods for RKE Clusters - -If the cluster is not an [RKE cluster,]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) the kubeconfig file allows you to access the cluster in only one way: it lets you be authenticated with the Rancher server, then Rancher allows you to run kubectl commands on the cluster. - -For RKE clusters, the kubeconfig file allows you to be authenticated in two ways: - -- **Through the Rancher server authentication proxy:** Rancher's authentication proxy validates your identity, then connects you to the downstream cluster that you want to access. -- **Directly with the downstream cluster's API server:** RKE clusters have an authorized cluster endpoint enabled by default. This endpoint allows you to access your downstream Kubernetes cluster with the kubectl CLI and a kubeconfig file, and it is enabled by default for RKE clusters. In this scenario, the downstream cluster's Kubernetes API server authenticates you by calling a webhook (the `kube-api-auth` microservice) that Rancher set up. - -This second method, the capability to connect directly to the cluster's Kubernetes API server, is important because it lets you access your downstream cluster if you can't connect to Rancher. - -To use the authorized cluster endpoint, you will need to configure kubectl to use the extra kubectl context in the kubeconfig file that Rancher generates for you when the RKE cluster is created. This file can be downloaded from the cluster view in the Rancher UI, and the instructions for configuring kubectl are on [this page.](../kubectl/#authenticating-directly-with-a-downstream-cluster) - -These methods of communicating with downstream Kubernetes clusters are also explained in the [architecture page]({{}}/rancher/v2.6/en/overview/architecture/#communicating-with-downstream-user-clusters) in the larger context of explaining how Rancher works and how Rancher communicates with downstream clusters. - -### About the kube-api-auth Authentication Webhook - -The `kube-api-auth` microservice is deployed to provide the user authentication functionality for the [authorized cluster endpoint,]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) which is only available for [RKE clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) When you access the user cluster using `kubectl`, the cluster's Kubernetes API server authenticates you by using the `kube-api-auth` service as a webhook. - -During cluster provisioning, the file `/etc/kubernetes/kube-api-authn-webhook.yaml` is deployed and `kube-apiserver` is configured with `--authentication-token-webhook-config-file=/etc/kubernetes/kube-api-authn-webhook.yaml`. This configures the `kube-apiserver` to query `http://127.0.0.1:6440/v1/authenticate` to determine authentication for bearer tokens. - -The scheduling rules for `kube-api-auth` are listed below: - -| Component | nodeAffinity nodeSelectorTerms | nodeSelector | Tolerations | -| -------------------- | ------------------------------------------ | ------------ | ------------------------------------------------------------------------------ | -| kube-api-auth | `beta.kubernetes.io/os:NotIn:windows`
`node-role.kubernetes.io/controlplane:In:"true"` | none | `operator:Exists` | diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-access.md b/versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-access.md deleted file mode 100644 index 291423864fc..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-access.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Cluster Access -weight: 1 ---- - -This section is about what tools can be used to access clusters managed by Rancher. - -For information on how to give users permission to access a cluster, see the section on [adding users to clusters.]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/cluster-members/) - -For more information on roles-based access control, see [this section.]({{}}/rancher/v2.6/en/admin-settings/rbac/) - -For information on how to set up an authentication system, see [this section.]({{}}/rancher/v2.6/en/admin-settings/authentication/) - - -### Rancher UI - -Rancher provides an intuitive user interface for interacting with your clusters. All options available in the UI use the Rancher API. Therefore any action possible in the UI is also possible in the Rancher CLI or Rancher API. - -### kubectl - -You can use the Kubernetes command-line tool, [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/), to manage your clusters. You have two options for using kubectl: - -- **Rancher kubectl shell:** Interact with your clusters by launching a kubectl shell available in the Rancher UI. This option requires no configuration actions on your part. For more information, see [Accessing Clusters with kubectl Shell]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/). -- **Terminal remote connection:** You can also interact with your clusters by installing [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) on your local desktop and then copying the cluster's kubeconfig file to your local `~/.kube/config` directory. For more information, see [Accessing Clusters with kubectl and a kubeconfig File](./kubectl/). - -### Rancher CLI - -You can control your clusters by downloading Rancher's own command-line interface, [Rancher CLI]({{}}/rancher/v2.6/en/cli/). This CLI tool can interact directly with different clusters and projects or pass them `kubectl` commands. - -### Rancher API - -Finally, you can interact with your clusters over the Rancher API. Before you use the API, you must obtain an [API key]({{}}/rancher/v2.6/en/user-settings/api-keys/). To view the different resource fields and actions for an API object, open the API UI, which can be accessed by clicking on **View in API** for any Rancher UI object. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-members/cluster-members.md b/versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-members/cluster-members.md deleted file mode 100644 index 31d8aaeb564..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-access/cluster-members/cluster-members.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Adding Users to Clusters -weight: 2020 ---- - -If you want to provide a user with access and permissions to _all_ projects, nodes, and resources within a cluster, assign the user a cluster membership. - ->**Tip:** Want to provide a user with access to a _specific_ project within a cluster? See [Adding Project Members]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/project-members/) instead. - -There are two contexts where you can add cluster members: - -- Adding Members to a New Cluster - - You can add members to a cluster as you create it (recommended if possible). - -- [Adding Members to an Existing Cluster](#editing-cluster-membership) - - You can always add members to a cluster after a cluster is provisioned. - -## Editing Cluster Membership - -Cluster administrators can edit the membership for a cluster, controlling which Rancher users can access the cluster and what features they can use. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster you want to add members to and click **⋮ > Edit Config**. -1. In the **Member Roles** tab, click **Add Member**. -1. Search for the user or group that you want to add to the cluster. - - If external authentication is configured: - - - Rancher returns users from your [external authentication]({{}}/rancher/v2.6/en/admin-settings/authentication/) source as you type. - - >**Using AD but can't find your users?** - >There may be an issue with your search attribute configuration. See [Configuring Active Directory Authentication: Step 5]({{}}/rancher/v2.6/en/admin-settings/authentication/ad/). - - - A drop-down allows you to add groups instead of individual users. The drop-down only lists groups that you, the logged in user, are part of. - - >**Note:** If you are logged in as a local user, external users do not display in your search results. For more information, see [External Authentication Configuration and Principal Users]({{}}/rancher/v2.6/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -1. Assign the user or group **Cluster** roles. - - [What are Cluster Roles?]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/) - - >**Tip:** For Custom Roles, you can modify the list of individual roles available for assignment. - > - > - To add roles to the list, [Add a Custom Role]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles/). - > - To remove roles from the list, [Lock/Unlock Roles]({{}}/rancher/v2.6/en/admin-settings/rbac/locked-roles). - -**Result:** The chosen users are added to the cluster. - -- To revoke cluster membership, select the user and click **Delete**. This action deletes membership, not the user. -- To modify a user's roles in the cluster, delete them from the cluster, and then re-add them with modified roles. diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-access/kubectl/kubectl.md b/versioned_docs/version-2.6/cluster-admin/cluster-access/kubectl/kubectl.md deleted file mode 100644 index 2f030570879..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-access/kubectl/kubectl.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: "Access a Cluster with Kubectl and kubeconfig" -description: "Learn how you can access and manage your Kubernetes clusters using kubectl with kubectl Shell or with kubectl CLI and kubeconfig file. A kubeconfig file is used to configure access to Kubernetes. When you create a cluster with Rancher, it automatically creates a kubeconfig for your cluster." -weight: 2010 ---- - -This section describes how to manipulate your downstream Kubernetes cluster with kubectl from the Rancher UI or from your workstation. - -For more information on using kubectl, see [Kubernetes Documentation: Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/overview/). - -- [Accessing clusters with kubectl shell in the Rancher UI](#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) -- [Accessing clusters with kubectl from your workstation](#accessing-clusters-with-kubectl-from-your-workstation) -- [Note on Resources created using kubectl](#note-on-resources-created-using-kubectl) -- [Authenticating Directly with a Downstream Cluster](#authenticating-directly-with-a-downstream-cluster) - - [Connecting Directly to Clusters with FQDN Defined](#connecting-directly-to-clusters-with-fqdn-defined) - - [Connecting Directly to Clusters without FQDN Defined](#connecting-directly-to-clusters-without-fqdn-defined) - - -### Accessing Clusters with kubectl Shell in the Rancher UI - -You can access and manage your clusters by logging into Rancher and opening the kubectl shell in the UI. No further configuration necessary. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster you want to access with kubectl and click **Explore**. -1. In the top navigation menu, click the **Kubectl Shell** button. Use the window that opens to interact with your Kubernetes cluster. - -### Accessing Clusters with kubectl from Your Workstation - -This section describes how to download your cluster's kubeconfig file, launch kubectl from your workstation, and access your downstream cluster. - -This alternative method of accessing the cluster allows you to authenticate with Rancher and manage your cluster without using the Rancher UI. - -> **Prerequisites:** These instructions assume that you have already created a Kubernetes cluster, and that kubectl is installed on your workstation. For help installing kubectl, refer to the official [Kubernetes documentation.](https://kubernetes.io/docs/tasks/tools/install-kubectl/) - -1. Log into Rancher. Click **☰ > Cluster Management**. -1. Go to the cluster that you want to access with kubectl and click **Explore**. -1. In the top navigation bar, click **Download KubeConfig** button. -1. Save the YAML file on your local computer. Move the file to `~/.kube/config`. Note: The default location that kubectl uses for the kubeconfig file is `~/.kube/config`, but you can use any directory and specify it using the `--kubeconfig` flag, as in this command: - ``` - kubectl --kubeconfig /custom/path/kube.config get pods - ``` -1. From your workstation, launch kubectl. Use it to interact with your kubernetes cluster. - - -### Note on Resources Created Using kubectl - -Rancher will discover and show resources created by `kubectl`. However, these resources might not have all the necessary annotations on discovery. If an operation (for instance, scaling the workload) is done to the resource using the Rancher UI/API, this may trigger recreation of the resources due to the missing annotations. This should only happen the first time an operation is done to the discovered resource. - -# Authenticating Directly with a Downstream Cluster - -This section intended to help you set up an alternative method to access an [RKE cluster.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters) - -This method is only available for RKE clusters that have the [authorized cluster endpoint]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) enabled. When Rancher creates this RKE cluster, it generates a kubeconfig file that includes additional kubectl context(s) for accessing your cluster. This additional context allows you to use kubectl to authenticate with the downstream cluster without authenticating through Rancher. For a longer explanation of how the authorized cluster endpoint works, refer to [this page.](../ace) - -We recommend that as a best practice, you should set up this method to access your RKE cluster, so that just in case you can’t connect to Rancher, you can still access the cluster. - -> **Prerequisites:** The following steps assume that you have created a Kubernetes cluster and followed the steps to [connect to your cluster with kubectl from your workstation.](#accessing-clusters-with-kubectl-from-your-workstation) - -To find the name of the context(s) in your downloaded kubeconfig file, run: - -``` -kubectl config get-contexts --kubeconfig /custom/path/kube.config -CURRENT NAME CLUSTER AUTHINFO NAMESPACE -* my-cluster my-cluster user-46tmn - my-cluster-controlplane-1 my-cluster-controlplane-1 user-46tmn -``` - -In this example, when you use `kubectl` with the first context, `my-cluster`, you will be authenticated through the Rancher server. - -With the second context, `my-cluster-controlplane-1`, you would authenticate with the authorized cluster endpoint, communicating with an downstream RKE cluster directly. - -We recommend using a load balancer with the authorized cluster endpoint. For details, refer to the [recommended architecture section.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#architecture-for-an-authorized-cluster-endpoint) - -Now that you have the name of the context needed to authenticate directly with the cluster, you can pass the name of the context in as an option when running kubectl commands. The commands will differ depending on whether your cluster has an FQDN defined. Examples are provided in the sections below. - -When `kubectl` works normally, it confirms that you can access your cluster while bypassing Rancher's authentication proxy. - -### Connecting Directly to Clusters with FQDN Defined - -If an FQDN is defined for the cluster, a single context referencing the FQDN will be created. The context will be named `-fqdn`. When you want to use `kubectl` to access this cluster without Rancher, you will need to use this context. - -Assuming the kubeconfig file is located at `~/.kube/config`: - -``` -kubectl --context -fqdn get nodes -``` -Directly referencing the location of the kubeconfig file: -``` -kubectl --kubeconfig /custom/path/kube.config --context -fqdn get pods -``` - -### Connecting Directly to Clusters without FQDN Defined - -If there is no FQDN defined for the cluster, extra contexts will be created referencing the IP address of each node in the control plane. Each context will be named `-`. When you want to use `kubectl` to access this cluster without Rancher, you will need to use this context. - -Assuming the kubeconfig file is located at `~/.kube/config`: -``` -kubectl --context - get nodes -``` -Directly referencing the location of the kubeconfig file: -``` -kubectl --kubeconfig /custom/path/kube.config --context - get pods -``` diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-admin.md b/versioned_docs/version-2.6/cluster-admin/cluster-admin.md deleted file mode 100644 index ea79525e27d..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-admin.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Cluster Administration -weight: 8 ---- - -After you provision a cluster in Rancher, you can begin using powerful Kubernetes features to deploy and scale your containerized applications in development, testing, or production environments. - -This page covers the following topics: - -- [Switching between clusters](#switching-between-clusters) -- [Managing clusters in Rancher](#managing-clusters-in-rancher) -- [Configuring tools](#configuring-tools) - -> This section assumes a basic familiarity with Docker and Kubernetes. For a brief explanation of how Kubernetes components work together, refer to the [concepts]({{}}/rancher/v2.6/en/overview/concepts) page. - -## Managing Clusters in Rancher - -After clusters have been [provisioned into Rancher]({{}}/rancher/v2.6/en/cluster-provisioning/), [cluster owners]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles) will need to manage these clusters. There are many different options of how to manage your cluster. - -import ClusterCapabilitiesTable from '/rancher/v2.6/en/shared-files/_cluster-capabilities-table.md'; - - - -## Configuring Tools - -Rancher contains a variety of tools that aren't included in Kubernetes to assist in your DevOps operations. Rancher can integrate with external services to help your clusters run more efficiently. Tools are divided into following categories: - -- Alerts -- Notifiers -- Logging -- Monitoring -- Istio Service Mesh -- OPA Gatekeeper - -Tools can be installed through **Apps & Marketplace.** \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/amazon/amazon.md b/versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/amazon/amazon.md deleted file mode 100644 index 717abd28a43..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/amazon/amazon.md +++ /dev/null @@ -1,580 +0,0 @@ ---- -title: Cluster Autoscaler with AWS EC2 Auto Scaling Groups -weight: 1 ---- - -This guide will show you how to install and use [Kubernetes cluster-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/) on Rancher custom clusters using AWS EC2 Auto Scaling Groups. - -We are going to install a Rancher RKE custom cluster with a fixed number of nodes with the etcd and controlplane roles, and a variable nodes with the worker role, managed by `cluster-autoscaler`. - -- [Prerequisites](#prerequisites) -- [1. Create a Custom Cluster](#1-create-a-custom-cluster) -- [2. Configure the Cloud Provider](#2-configure-the-cloud-provider) -- [3. Deploy Nodes](#3-deploy-nodes) -- [4. Install cluster-autoscaler](#4-install-cluster-autoscaler) - - [Parameters](#parameters) - - [Deployment](#deployment) -- [Testing](#testing) - - [Generating Load](#generating-load) - - [Checking Scale](#checking-scale) - -# Prerequisites - -These elements are required to follow this guide: - -* The Rancher server is up and running -* You have an AWS EC2 user with proper permissions to create virtual machines, auto scaling groups, and IAM profiles and roles - -### 1. Create a Custom Cluster - -On Rancher server, we should create a custom k8s cluster v1.18.x. Be sure that cloud_provider name is set to `amazonec2`. Once cluster is created we need to get: - -* clusterID: `c-xxxxx` will be used on EC2 `kubernetes.io/cluster/` instance tag -* clusterName: will be used on EC2 `k8s.io/cluster-autoscaler/` instance tag -* nodeCommand: will be added on EC2 instance user_data to include new nodes on cluster - - ```sh - sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent: --server https:// --token --ca-checksum - ``` - -### 2. Configure the Cloud Provider - -On AWS EC2, we should create a few objects to configure our system. We've defined three distinct groups and IAM profiles to configure on AWS. - -1. Autoscaling group: Nodes that will be part of the EC2 Auto Scaling Group (ASG). The ASG will be used by `cluster-autoscaler` to scale up and down. - * IAM profile: Required by k8s nodes where cluster-autoscaler will be running. It is recommended for Kubernetes master nodes. This profile is called `K8sAutoscalerProfile`. - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "autoscaling:DescribeAutoScalingGroups", - "autoscaling:DescribeAutoScalingInstances", - "autoscaling:DescribeLaunchConfigurations", - "autoscaling:SetDesiredCapacity", - "autoscaling:TerminateInstanceInAutoScalingGroup", - "autoscaling:DescribeTags", - "autoscaling:DescribeLaunchConfigurations", - "ec2:DescribeLaunchTemplateVersions" - ], - "Resource": [ - "*" - ] - } - ] - } - ``` - -2. Master group: Nodes that will be part of the Kubernetes etcd and/or control planes. This will be out of the ASG. - * IAM profile: Required by the Kubernetes cloud_provider integration. Optionally, `AWS_ACCESS_KEY` and `AWS_SECRET_KEY` can be used instead [using-aws-credentials.](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#using-aws-credentials) This profile is called `K8sMasterProfile`. - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "autoscaling:DescribeAutoScalingGroups", - "autoscaling:DescribeLaunchConfigurations", - "autoscaling:DescribeTags", - "ec2:DescribeInstances", - "ec2:DescribeRegions", - "ec2:DescribeRouteTables", - "ec2:DescribeSecurityGroups", - "ec2:DescribeSubnets", - "ec2:DescribeVolumes", - "ec2:CreateSecurityGroup", - "ec2:CreateTags", - "ec2:CreateVolume", - "ec2:ModifyInstanceAttribute", - "ec2:ModifyVolume", - "ec2:AttachVolume", - "ec2:AuthorizeSecurityGroupIngress", - "ec2:CreateRoute", - "ec2:DeleteRoute", - "ec2:DeleteSecurityGroup", - "ec2:DeleteVolume", - "ec2:DetachVolume", - "ec2:RevokeSecurityGroupIngress", - "ec2:DescribeVpcs", - "elasticloadbalancing:AddTags", - "elasticloadbalancing:AttachLoadBalancerToSubnets", - "elasticloadbalancing:ApplySecurityGroupsToLoadBalancer", - "elasticloadbalancing:CreateLoadBalancer", - "elasticloadbalancing:CreateLoadBalancerPolicy", - "elasticloadbalancing:CreateLoadBalancerListeners", - "elasticloadbalancing:ConfigureHealthCheck", - "elasticloadbalancing:DeleteLoadBalancer", - "elasticloadbalancing:DeleteLoadBalancerListeners", - "elasticloadbalancing:DescribeLoadBalancers", - "elasticloadbalancing:DescribeLoadBalancerAttributes", - "elasticloadbalancing:DetachLoadBalancerFromSubnets", - "elasticloadbalancing:DeregisterInstancesFromLoadBalancer", - "elasticloadbalancing:ModifyLoadBalancerAttributes", - "elasticloadbalancing:RegisterInstancesWithLoadBalancer", - "elasticloadbalancing:SetLoadBalancerPoliciesForBackendServer", - "elasticloadbalancing:AddTags", - "elasticloadbalancing:CreateListener", - "elasticloadbalancing:CreateTargetGroup", - "elasticloadbalancing:DeleteListener", - "elasticloadbalancing:DeleteTargetGroup", - "elasticloadbalancing:DescribeListeners", - "elasticloadbalancing:DescribeLoadBalancerPolicies", - "elasticloadbalancing:DescribeTargetGroups", - "elasticloadbalancing:DescribeTargetHealth", - "elasticloadbalancing:ModifyListener", - "elasticloadbalancing:ModifyTargetGroup", - "elasticloadbalancing:RegisterTargets", - "elasticloadbalancing:SetLoadBalancerPoliciesOfListener", - "iam:CreateServiceLinkedRole", - "ecr:GetAuthorizationToken", - "ecr:BatchCheckLayerAvailability", - "ecr:GetDownloadUrlForLayer", - "ecr:GetRepositoryPolicy", - "ecr:DescribeRepositories", - "ecr:ListImages", - "ecr:BatchGetImage", - "kms:DescribeKey" - ], - "Resource": [ - "*" - ] - } - ] - } - ``` - - * IAM role: `K8sMasterRole: [K8sMasterProfile,K8sAutoscalerProfile]` - * Security group: `K8sMasterSg` More info at[RKE ports (custom nodes tab)]({{}}/rancher/v2.6/en/installation/requirements/ports/#downstream-kubernetes-cluster-nodes) - * Tags: - `kubernetes.io/cluster/: owned` - * User data: `K8sMasterUserData` Ubuntu 18.04(ami-0e11cbb34015ff725), installs docker and add etcd+controlplane node to the k8s cluster - - ```sh - #!/bin/bash -x - - cat < /etc/sysctl.d/90-kubelet.conf - vm.overcommit_memory = 1 - vm.panic_on_oom = 0 - kernel.panic = 10 - kernel.panic_on_oops = 1 - kernel.keys.root_maxkeys = 1000000 - kernel.keys.root_maxbytes = 25000000 - EOF - sysctl -p /etc/sysctl.d/90-kubelet.conf - - curl -sL https://releases.rancher.com/install-docker/19.03.sh | sh - sudo usermod -aG docker ubuntu - - TOKEN=$(curl -s -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600") - PRIVATE_IP=$(curl -H "X-aws-ec2-metadata-token: ${TOKEN}" -s http://169.254.169.254/latest/meta-data/local-ipv4) - PUBLIC_IP=$(curl -H "X-aws-ec2-metadata-token: ${TOKEN}" -s http://169.254.169.254/latest/meta-data/public-ipv4) - K8S_ROLES="--etcd --controlplane" - - sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent: --server https:// --token --ca-checksum --address ${PUBLIC_IP} --internal-address ${PRIVATE_IP} ${K8S_ROLES} - ``` - -3. Worker group: Nodes that will be part of the k8s worker plane. Worker nodes will be scaled by cluster-autoscaler using the ASG. - * IAM profile: Provides cloud_provider worker integration. - This profile is called `K8sWorkerProfile`. - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "ec2:DescribeInstances", - "ec2:DescribeRegions", - "ecr:GetAuthorizationToken", - "ecr:BatchCheckLayerAvailability", - "ecr:GetDownloadUrlForLayer", - "ecr:GetRepositoryPolicy", - "ecr:DescribeRepositories", - "ecr:ListImages", - "ecr:BatchGetImage" - ], - "Resource": "*" - } - ] - } - ``` - - * IAM role: `K8sWorkerRole: [K8sWorkerProfile]` - * Security group: `K8sWorkerSg` More info at [RKE ports (custom nodes tab)]({{}}/rancher/v2.6/en/installation/requirements/ports/#downstream-kubernetes-cluster-nodes) - * Tags: - * `kubernetes.io/cluster/: owned` - * `k8s.io/cluster-autoscaler/: true` - * `k8s.io/cluster-autoscaler/enabled: true` - * User data: `K8sWorkerUserData` Ubuntu 18.04(ami-0e11cbb34015ff725), installs docker and add worker node to the k8s cluster - - ```sh - #!/bin/bash -x - - cat < /etc/sysctl.d/90-kubelet.conf - vm.overcommit_memory = 1 - vm.panic_on_oom = 0 - kernel.panic = 10 - kernel.panic_on_oops = 1 - kernel.keys.root_maxkeys = 1000000 - kernel.keys.root_maxbytes = 25000000 - EOF - sysctl -p /etc/sysctl.d/90-kubelet.conf - - curl -sL https://releases.rancher.com/install-docker/19.03.sh | sh - sudo usermod -aG docker ubuntu - - TOKEN=$(curl -s -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600") - PRIVATE_IP=$(curl -H "X-aws-ec2-metadata-token: ${TOKEN}" -s http://169.254.169.254/latest/meta-data/local-ipv4) - PUBLIC_IP=$(curl -H "X-aws-ec2-metadata-token: ${TOKEN}" -s http://169.254.169.254/latest/meta-data/public-ipv4) - K8S_ROLES="--worker" - - sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent: --server https:// --token --ca-checksum --address ${PUBLIC_IP} --internal-address ${PRIVATE_IP} ${K8S_ROLES} - ``` - -More info is at [RKE clusters on AWS]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/amazon/) and [Cluster Autoscaler on AWS.](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md) - -### 3. Deploy Nodes - -Once we've configured AWS, let's create VMs to bootstrap our cluster: - -* master (etcd+controlplane): Depending your needs, deploy three master instances with proper size. More info is at [the recommendations for production-ready clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/production/) - * IAM role: `K8sMasterRole` - * Security group: `K8sMasterSg` - * Tags: - * `kubernetes.io/cluster/: owned` - * User data: `K8sMasterUserData` - -* worker: Define an ASG on EC2 with the following settings: - * Name: `K8sWorkerAsg` - * IAM role: `K8sWorkerRole` - * Security group: `K8sWorkerSg` - * Tags: - * `kubernetes.io/cluster/: owned` - * `k8s.io/cluster-autoscaler/: true` - * `k8s.io/cluster-autoscaler/enabled: true` - * User data: `K8sWorkerUserData` - * Instances: - * minimum: 2 - * desired: 2 - * maximum: 10 - -Once the VMs are deployed, you should have a Rancher custom cluster up and running with three master and two worker nodes. - -### 4. Install Cluster-autoscaler - -At this point, we should have rancher cluster up and running. We are going to install cluster-autoscaler on master nodes and `kube-system` namespace, following cluster-autoscaler recommendation. - -#### Parameters - -This table shows cluster-autoscaler parameters for fine tuning: - -| Parameter | Default | Description | -|---|---|---| -|cluster-name|-|Autoscaled cluster name, if available| -|address|:8085|The address to expose Prometheus metrics| -|kubernetes|-|Kubernetes master location. Leave blank for default| -|kubeconfig|-|Path to kubeconfig file with authorization and master location information| -|cloud-config|-|The path to the cloud provider configuration file. Empty string for no configuration file| -|namespace|"kube-system"|Namespace in which cluster-autoscaler run| -|scale-down-enabled|true|Should CA scale down the cluster| -|scale-down-delay-after-add|"10m"|How long after scale up that scale down evaluation resumes| -|scale-down-delay-after-delete|0|How long after node deletion that scale down evaluation resumes, defaults to scanInterval| -|scale-down-delay-after-failure|"3m"|How long after scale down failure that scale down evaluation resumes| -|scale-down-unneeded-time|"10m"|How long a node should be unneeded before it is eligible for scale down| -|scale-down-unready-time|"20m"|How long an unready node should be unneeded before it is eligible for scale down| -|scale-down-utilization-threshold|0.5|Sum of cpu or memory of all pods running on the node divided by node's corresponding allocatable resource, below which a node can be considered for scale down| -|scale-down-gpu-utilization-threshold|0.5|Sum of gpu requests of all pods running on the node divided by node's allocatable resource, below which a node can be considered for scale down| -|scale-down-non-empty-candidates-count|30|Maximum number of non empty nodes considered in one iteration as candidates for scale down with drain| -|scale-down-candidates-pool-ratio|0.1|A ratio of nodes that are considered as additional non empty candidates for scale down when some candidates from previous iteration are no longer valid| -|scale-down-candidates-pool-min-count|50|Minimum number of nodes that are considered as additional non empty candidates for scale down when some candidates from previous iteration are no longer valid| -|node-deletion-delay-timeout|"2m"|Maximum time CA waits for removing delay-deletion.cluster-autoscaler.kubernetes.io/ annotations before deleting the node| -|scan-interval|"10s"|How often cluster is reevaluated for scale up or down| -|max-nodes-total|0|Maximum number of nodes in all node groups. Cluster autoscaler will not grow the cluster beyond this number| -|cores-total|"0:320000"|Minimum and maximum number of cores in cluster, in the format `:.` Cluster autoscaler will not scale the cluster beyond these numbers| -|memory-total|"0:6400000"|Minimum and maximum number of gigabytes of memory in cluster, in the format `:.` Cluster autoscaler will not scale the cluster beyond these numbers| -cloud-provider|-|Cloud provider type| -|max-bulk-soft-taint-count|10|Maximum number of nodes that can be tainted/untainted PreferNoSchedule at the same time. Set to 0 to turn off such tainting| -|max-bulk-soft-taint-time|"3s"|Maximum duration of tainting/untainting nodes as PreferNoSchedule at the same time| -|max-empty-bulk-delete|10|Maximum number of empty nodes that can be deleted at the same time| -|max-graceful-termination-sec|600|Maximum number of seconds CA waits for pod termination when trying to scale down a node| -|max-total-unready-percentage|45|Maximum percentage of unready nodes in the cluster. After this is exceeded, CA halts operations| -|ok-total-unready-count|3|Number of allowed unready nodes, irrespective of max-total-unready-percentage| -|scale-up-from-zero|true|Should CA scale up when there 0 ready nodes| -|max-node-provision-time|"15m"|Maximum time CA waits for node to be provisioned| -|nodes|-|sets min,max size and other configuration data for a node group in a format accepted by cloud provider. Can be used multiple times. Format: `::`| -|node-group-auto-discovery|-|One or more definition(s) of node group auto-discovery. A definition is expressed `:[[=]]`| -|estimator|-|"binpacking"|Type of resource estimator to be used in scale up. Available values: ["binpacking"]| -|expander|"random"|Type of node group expander to be used in scale up. Available values: `["random","most-pods","least-waste","price","priority"]`| -|ignore-daemonsets-utilization|false|Should CA ignore DaemonSet pods when calculating resource utilization for scaling down| -|ignore-mirror-pods-utilization|false|Should CA ignore Mirror pods when calculating resource utilization for scaling down| -|write-status-configmap|true|Should CA write status information to a configmap| -|max-inactivity|"10m"|Maximum time from last recorded autoscaler activity before automatic restart| -|max-failing-time|"15m"|Maximum time from last recorded successful autoscaler run before automatic restart| -|balance-similar-node-groups|false|Detect similar node groups and balance the number of nodes between them| -|node-autoprovisioning-enabled|false|Should CA autoprovision node groups when needed| -|max-autoprovisioned-node-group-count|15|The maximum number of autoprovisioned groups in the cluster| -|unremovable-node-recheck-timeout|"5m"|The timeout before we check again a node that couldn't be removed before| -|expendable-pods-priority-cutoff|-10|Pods with priority below cutoff will be expendable. They can be killed without any consideration during scale down and they don't cause scale up. Pods with null priority (PodPriority disabled) are non expendable| -|regional|false|Cluster is regional| -|new-pod-scale-up-delay|"0s"|Pods less than this old will not be considered for scale-up| -|ignore-taint|-|Specifies a taint to ignore in node templates when considering to scale a node group| -|balancing-ignore-label|-|Specifies a label to ignore in addition to the basic and cloud-provider set of labels when comparing if two node groups are similar| -|aws-use-static-instance-list|false|Should CA fetch instance types in runtime or use a static list. AWS only| -|profiling|false|Is debug/pprof endpoint enabled| - -#### Deployment - -Based on [cluster-autoscaler-run-on-master.yaml](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/examples/cluster-autoscaler-run-on-master.yaml) example, we've created our own `cluster-autoscaler-deployment.yaml` to use preferred [auto-discovery setup](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/aws#auto-discovery-setup), updating tolerations, nodeSelector, image version and command config: - - -```yml ---- -apiVersion: v1 -kind: ServiceAccount -metadata: - labels: - k8s-addon: cluster-autoscaler.addons.k8s.io - k8s-app: cluster-autoscaler - name: cluster-autoscaler - namespace: kube-system ---- -apiVersion: rbac.authorization.k8s.io/v1 -kind: ClusterRole -metadata: - name: cluster-autoscaler - labels: - k8s-addon: cluster-autoscaler.addons.k8s.io - k8s-app: cluster-autoscaler -rules: - - apiGroups: [""] - resources: ["events", "endpoints"] - verbs: ["create", "patch"] - - apiGroups: [""] - resources: ["pods/eviction"] - verbs: ["create"] - - apiGroups: [""] - resources: ["pods/status"] - verbs: ["update"] - - apiGroups: [""] - resources: ["endpoints"] - resourceNames: ["cluster-autoscaler"] - verbs: ["get", "update"] - - apiGroups: [""] - resources: ["nodes"] - verbs: ["watch", "list", "get", "update"] - - apiGroups: [""] - resources: - - "pods" - - "services" - - "replicationcontrollers" - - "persistentvolumeclaims" - - "persistentvolumes" - verbs: ["watch", "list", "get"] - - apiGroups: ["extensions"] - resources: ["replicasets", "daemonsets"] - verbs: ["watch", "list", "get"] - - apiGroups: ["policy"] - resources: ["poddisruptionbudgets"] - verbs: ["watch", "list"] - - apiGroups: ["apps"] - resources: ["statefulsets", "replicasets", "daemonsets"] - verbs: ["watch", "list", "get"] - - apiGroups: ["storage.k8s.io"] - resources: ["storageclasses", "csinodes"] - verbs: ["watch", "list", "get"] - - apiGroups: ["batch", "extensions"] - resources: ["jobs"] - verbs: ["get", "list", "watch", "patch"] - - apiGroups: ["coordination.k8s.io"] - resources: ["leases"] - verbs: ["create"] - - apiGroups: ["coordination.k8s.io"] - resourceNames: ["cluster-autoscaler"] - resources: ["leases"] - verbs: ["get", "update"] ---- -apiVersion: rbac.authorization.k8s.io/v1 -kind: Role -metadata: - name: cluster-autoscaler - namespace: kube-system - labels: - k8s-addon: cluster-autoscaler.addons.k8s.io - k8s-app: cluster-autoscaler -rules: - - apiGroups: [""] - resources: ["configmaps"] - verbs: ["create","list","watch"] - - apiGroups: [""] - resources: ["configmaps"] - resourceNames: ["cluster-autoscaler-status", "cluster-autoscaler-priority-expander"] - verbs: ["delete", "get", "update", "watch"] - ---- -apiVersion: rbac.authorization.k8s.io/v1 -kind: ClusterRoleBinding -metadata: - name: cluster-autoscaler - labels: - k8s-addon: cluster-autoscaler.addons.k8s.io - k8s-app: cluster-autoscaler -roleRef: - apiGroup: rbac.authorization.k8s.io - kind: ClusterRole - name: cluster-autoscaler -subjects: - - kind: ServiceAccount - name: cluster-autoscaler - namespace: kube-system - ---- -apiVersion: rbac.authorization.k8s.io/v1 -kind: RoleBinding -metadata: - name: cluster-autoscaler - namespace: kube-system - labels: - k8s-addon: cluster-autoscaler.addons.k8s.io - k8s-app: cluster-autoscaler -roleRef: - apiGroup: rbac.authorization.k8s.io - kind: Role - name: cluster-autoscaler -subjects: - - kind: ServiceAccount - name: cluster-autoscaler - namespace: kube-system - ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: cluster-autoscaler - namespace: kube-system - labels: - app: cluster-autoscaler -spec: - replicas: 1 - selector: - matchLabels: - app: cluster-autoscaler - template: - metadata: - labels: - app: cluster-autoscaler - annotations: - prometheus.io/scrape: 'true' - prometheus.io/port: '8085' - spec: - serviceAccountName: cluster-autoscaler - tolerations: - - effect: NoSchedule - operator: "Equal" - value: "true" - key: node-role.kubernetes.io/controlplane - nodeSelector: - node-role.kubernetes.io/controlplane: "true" - containers: - - image: eu.gcr.io/k8s-artifacts-prod/autoscaling/cluster-autoscaler:v1.18.1 - name: cluster-autoscaler - resources: - limits: - cpu: 100m - memory: 300Mi - requests: - cpu: 100m - memory: 300Mi - command: - - ./cluster-autoscaler - - --v=4 - - --stderrthreshold=info - - --cloud-provider=aws - - --skip-nodes-with-local-storage=false - - --expander=least-waste - - --node-group-auto-discovery=asg:tag=k8s.io/cluster-autoscaler/enabled,k8s.io/cluster-autoscaler/ - volumeMounts: - - name: ssl-certs - mountPath: /etc/ssl/certs/ca-certificates.crt - readOnly: true - imagePullPolicy: "Always" - volumes: - - name: ssl-certs - hostPath: - path: "/etc/ssl/certs/ca-certificates.crt" - -``` - -Once the manifest file is prepared, deploy it in the Kubernetes cluster (Rancher UI can be used instead): - -```sh -kubectl -n kube-system apply -f cluster-autoscaler-deployment.yaml -``` - -**Note:** Cluster-autoscaler deployment can also be set up using [manual configuration](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/aws#manual-configuration) - -# Testing - -At this point, we should have a cluster-scaler up and running in our Rancher custom cluster. Cluster-scale should manage `K8sWorkerAsg` ASG to scale up and down between 2 and 10 nodes, when one of the following conditions is true: - -* There are pods that failed to run in the cluster due to insufficient resources. In this case, the cluster is scaled up. -* There are nodes in the cluster that have been underutilized for an extended period of time and their pods can be placed on other existing nodes. In this case, the cluster is scaled down. - -### Generating Load - -We've prepared a `test-deployment.yaml` just to generate load on the Kubernetes cluster and see if cluster-autoscaler is working properly. The test deployment is requesting 1000m CPU and 1024Mi memory by three replicas. Adjust the requested resources and/or replica to be sure you exhaust the Kubernetes cluster resources: - -```yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - labels: - app: hello-world - name: hello-world -spec: - replicas: 3 - selector: - matchLabels: - app: hello-world - strategy: - rollingUpdate: - maxSurge: 1 - maxUnavailable: 0 - type: RollingUpdate - template: - metadata: - labels: - app: hello-world - spec: - containers: - - image: rancher/hello-world - imagePullPolicy: Always - name: hello-world - ports: - - containerPort: 80 - protocol: TCP - resources: - limits: - cpu: 1000m - memory: 1024Mi - requests: - cpu: 1000m - memory: 1024Mi -``` - -Once the test deployment is prepared, deploy it in the Kubernetes cluster default namespace (Rancher UI can be used instead): - -``` -kubectl -n default apply -f test-deployment.yaml -``` - -### Checking Scale - -Once the Kubernetes resources got exhausted, cluster-autoscaler should scale up worker nodes where pods failed to be scheduled. It should scale up until up until all pods became scheduled. You should see the new nodes on the ASG and on the Kubernetes cluster. Check the logs on the `kube-system` cluster-autoscaler pod. - -Once scale up is checked, let check for scale down. To do it, reduce the replica number on the test deployment until you release enough Kubernetes cluster resources to scale down. You should see nodes disappear on the ASG and on the Kubernetes cluster. Check the logs on the `kube-system` cluster-autoscaler pod. diff --git a/versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/cluster-autoscaler.md b/versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/cluster-autoscaler.md deleted file mode 100644 index 093de0f447d..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/cluster-autoscaler/cluster-autoscaler.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Cluster Autoscaler -weight: 1 ---- - -In this section, you'll learn how to install and use the [Kubernetes cluster-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/) on Rancher custom clusters using AWS EC2 Auto Scaling Groups. - -The cluster autoscaler is a tool that automatically adjusts the size of the Kubernetes cluster when one of the following conditions is true: - -* There are pods that failed to run in the cluster due to insufficient resources. -* There are nodes in the cluster that have been underutilized for an extended period of time and their pods can be placed on other existing nodes. - -To prevent your pod from being evicted, set a `priorityClassName: system-cluster-critical` property on your pod spec. - -Cluster Autoscaler is designed to run on Kubernetes master nodes. It can run in the `kube-system` namespace. Cluster Autoscaler doesn't scale down nodes with non-mirrored `kube-system` pods running on them. - -It's possible to run a customized deployment of Cluster Autoscaler on worker nodes, but extra care needs to be taken to ensure that Cluster Autoscaler remains up and running. - -# Cloud Providers - -Cluster Autoscaler provides support to distinct cloud providers. For more information, go to [cluster-autoscaler supported cloud providers.](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#deployment) - -### Setting up Cluster Autoscaler on Amazon Cloud Provider - -For details on running the cluster autoscaler on Amazon cloud provider, refer to [this page.]({{}}/rancher/v2.6/en/cluster-admin/cluster-autoscaler/amazon) diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/aks-config-reference/aks-config-reference.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/aks-config-reference/aks-config-reference.md deleted file mode 100644 index 1b522f15ad3..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/aks-config-reference/aks-config-reference.md +++ /dev/null @@ -1,218 +0,0 @@ ---- -shortTitle: AKS Cluster Configuration -title: AKS Cluster Configuration Reference -weight: 4 ---- - -# Changes in Rancher v2.6 - -- Support for adding more than one node pool -- Support for private clusters -- Enabled autoscaling node pools -- The AKS permissions are now configured in cloud credentials - -# Role-based Access Control - -When provisioning an AKS cluster in the Rancher UI, RBAC cannot be disabled. If role-based access control is disabled for the cluster in AKS, the cluster cannot be registered or imported into Rancher. - -Rancher can configure member roles for AKS clusters in the same way as any other cluster. For more information, see the section on [role-based access control.]({{}}/rancher/v2.6/en/admin-settings/rbac) - -# Cloud Credentials - -> The configuration information in this section assumes you have already set up a service principal for Rancher. For step-by-step instructions for how to set up the service principal, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks/#prerequisites-in-microsoft-azure) - -### Subscription ID - -To get the subscription ID, click **All Services** in the left navigation bar. Then click **Subscriptions**. Go to the name of the subscription that you want to associate with your Kubernetes cluster and copy the **Subscription ID**. - -### Client ID - -To get the client ID, go to the Azure Portal, then click **Azure Active Directory**, then click **App registrations,** then click the name of the service principal. The client ID is listed on the app registration detail page as **Application (client) ID**. - -### Client Secret - -You can't retrieve the client secret value after it is created, so if you don't already have a client secret value, you will need to create a new client secret. - -To get a new client secret, go to the Azure Portal, then click **Azure Active Directory**, then click **App registrations,** then click the name of the service principal. - -Then click **Certificates & secrets** and click **New client secret**. Click **Add**. Then copy the **Value** of the new client secret. - -### Environment - -Microsoft provides multiple [clouds](https://docs.microsoft.com/en-us/cli/azure/cloud?view=azure-cli-latest) for compliance with regional laws, which are available for your use: - -- AzurePublicCloud -- AzureGermanCloud -- AzureChinaCloud -- AzureUSGovernmentCloud - -# Account Access - -In this section you will need to select an existing Azure cloud credential or create a new one. - -For help configuring your Azure cloud credential, see [this section.](#cloud-credentials) - -# Cluster Location - -Configure the cluster and node location. For more information on availability zones for AKS, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/availability-zones) - -The high availability locations include multiple availability zones. - -# Cluster Options - -### Kubernetes Version - -The available Kubernetes versions are dynamically fetched from the Azure API. - -### Cluster Resource Group - -A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to allocate resources to resource groups based on what makes the most sense for your organization. Generally, add resources that share the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group. - -Use an existing resource group or enter a resource group name and one will be created for you. - -Using a resource group containing an existing AKS cluster will create a new resource group. Azure AKS only allows one AKS cluster per resource group. - -For information on managing resource groups, see the [Azure documentation.](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal) - -### Linux Admin Username - -The username used to create an SSH connection to the Linux nodes. - -The default username for AKS nodes is `azureuser`. - -### SSH Public Key - -The key used to create an SSH connection to the Linux nodes. - -### Tags - -Cluster tags can be useful if your organization uses tags as a way to organize resources across multiple Azure services. These tags don't apply to resources within the cluster. - -# Networking Options - -### LoadBalancer SKU - -Azure load balancers support both standard and basic SKUs (stock keeping units). - -For a comparison of standard and basic load balancers, see the official [Azure documentation.](https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus) Microsoft recommends the Standard load balancer. - -The Standard load balancer is required if you have selected one or more availability zones, or if you have more than one node pool. - -### Network Policy - -All pods in an AKS cluster can send and receive traffic without limitations, by default. To improve security, you can define rules that control the flow of traffic. The Network Policy feature in Kubernetes lets you define rules for ingress and egress traffic between pods in a cluster. - -Azure provides two ways to implement network policy. You choose a network policy option when you create an AKS cluster. The policy option can't be changed after the cluster is created: - -- Azure's own implementation, called Azure Network Policies. The Azure network policy requires the Azure CNI. -- Calico Network Policies, an open-source network and network security solution founded by [Tigera](https://www.tigera.io/). - -You can also choose to have no network policy. - -For more information about the differences between Azure and Calico network policies and their capabilities, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/use-network-policies#differences-between-azure-and-calico-policies-and-their-capabilities) - -### DNS Prefix -Enter a unique DNS prefix for your cluster's Kubernetes API server FQDN. - -### Network Plugin -There are two network plugins: kubenet and Azure CNI. - -The [kubenet](https://kubernetes.io/docs/concepts/cluster-administration/network-plugins/#kubenet) Kubernetes plugin is the default configuration for AKS cluster creation. When kubenet is used, each node in the cluster receives a routable IP address. The pods use NAT to communicate with other resources outside the AKS cluster. This approach reduces the number of IP addresses you need to reserve in your network space for pods to use. - -With the Azure CNI (advanced) networking plugin, pods get full virtual network connectivity and can be directly reached via their private IP address from connected networks. This plugin requires more IP address space. - -For more information on the differences between kubenet and Azure CNI, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/concepts-network#compare-network-models) - -### HTTP Application Routing - -When enabled, the HTTP application routing add-on makes it easier to access applications deployed to the AKS cluster. It deploys two components: a [Kubernetes Ingress controller](https://kubernetes.io/docs/concepts/services-networking/ingress/) and an [External-DNS](https://github.com/kubernetes-incubator/external-dns) controller. - -For more information, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/http-application-routing) - -### Set Authorized IP Ranges - -You can secure access to the Kubernetes API server using [authorized IP address ranges.](https://docs.microsoft.com/en-us/azure/aks/api-server-authorized-ip-ranges#overview-of-api-server-authorized-ip-ranges) - -The Kubernetes API server exposes the Kubernetes API. This component provides the interaction for management tools, such as kubectl. AKS provides a single-tenant cluster control plane with a dedicated API server. By default, the API server is assigned a public IP address, and you should control access to it using Kubernetes-based or Azure-based RBAC. - -To secure access to the otherwise publicly accessible AKS control plane and API server, you can enable and use authorized IP ranges. These authorized IP ranges only allow defined IP address ranges to communicate with the API server. - -However, even if you use authorized IP address ranges, you should still use Kubernetes RBAC or Azure RBAC to authorize users and the actions they request. - -### Container Monitoring - -Container monitoring gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers that are available in Kubernetes through the Metrics API. Container logs are also collected. After you enable monitoring, metrics and logs are automatically collected for you through a containerized version of the Log Analytics agent for Linux. Metrics are written to the metrics store and log data is written to the logs store associated with your [Log Analytics](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/log-query-overview) workspace. - -### Log Analytics Workspace Resource Group - -The [resource group](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview#resource-groups) containing the Log Analytics Workspace. You must create at least one workspace to use Azure Monitor Logs. - -### Log Analytics Workspace Name - -Data collected by Azure Monitor Logs is stored in one or more [Log Analytics workspaces.](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/design-logs-deployment) The workspace defines the geographic location of the data, access rights defining which users can access data, and configuration settings such as the pricing tier and data retention. - -You must create at least one workspace to use Azure Monitor Logs. A single workspace may be suffxicient for all of your monitoring data, or may choose to create multiple workspaces depending on your requirements. For example, you might have one workspace for your production data and another for testing. - -For more information about Azure Monitor Logs, see the [Azure documentation.](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/data-platform-logs) - -### Support Private Kubernetes Service - -Typically, AKS worker nodes do not get public IPs, regardless of whether the cluster is private. In a private cluster, the control plane does not have a public endpoint. - -Rancher can connect to a private AKS cluster in one of two ways. - -The first way to ensure that Rancher is running on the same [NAT](https://docs.microsoft.com/en-us/azure/virtual-network/nat-overview) as the AKS nodes. - -The second way is to run a command to register the cluster with Rancher. Once the cluster is provisioned, you can run the displayed command anywhere you can connect to the cluster’s Kubernetes API. This command is displayed in a pop-up when you provision an AKS cluster with a private API endpoint enabled. - -> **Note:** Please be aware that when registering an existing AKS cluster, the cluster might take some time, possibly hours, to appear in the `Cluster To register` dropdown list. This outcome will be based on region. - -For more information about connecting to an AKS private cluster, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/private-clusters#options-for-connecting-to-the-private-cluster) - -# Node Pools - -### Mode - -The Azure interface allows users to specify whether a Primary Node Pool relies on either `system` (normally used for control planes) or `user` (what is most typically needed for Rancher). - -For Primary Node Pools, you can specify Mode, OS, Count and Size. - -System node pools always require running nodes, so they cannot be scaled below one node. At least one system node pool is required. - -For subsequent node pools, the Rancher UI forces the default of User. User node pools allow you to scale to zero nodes. User node pools don't run any part of the Kubernetes controlplane. - -AKS doesn't expose the nodes that run the Kubernetes controlplane components. - -### Availability Zones - -[Availability zones](https://docs.microsoft.com/en-us/azure/availability-zones/az-overview) are unique physical locations within a region. Each zone is made up of one or more data centers equipped with independent power, cooling, and networking. - -Not all regions have support for availability zones. For a list of Azure regions with availability zones, see the [Azure documentation.](https://docs.microsoft.com/en-us/azure/availability-zones/az-region#azure-regions-with-availability-zones) - -### VM Size - -Choose a size for each VM in the node pool. For details about each VM size, see [this page.](https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/) - -### OS Disk Type - -The nodes in the node pool can have either managed or ephemeral disks. - -[Ephemeral OS disks](https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) are created on the local virtual machine storage and not saved to the remote Azure Storage. Ephemeral OS disks work well for stateless workloads, where applications are tolerant of individual VM failures, but are more affected by VM deployment time or reimaging the individual VM instances. With Ephemeral OS disk, you get lower read/write latency to the OS disk and faster VM reimage. - -[Azure managed disks](https://docs.microsoft.com/en-us/azure/virtual-machines/managed-disks-overview) are block-level storage volumes that are managed by Azure and used with Azure Virtual Machines. Managed disks are designed for 99.999% availability. Managed disks achieve this by providing you with three replicas of your data, allowing for high durability. - -### OS Disk Size - -The size in GB for the disk for each node. - -### Node Count -The number of nodes in the node pool. The maximum number of nodes may be limited by your [Azure subscription.](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits) - -### Max Pods Per Node -The maximum number of pods per node defaults to 110 with a maximum of 250. - -### Enable Auto Scaling - -When auto scaling is enabled, you will need to enter a minimum and maximum node count. - -When Auto Scaling is enabled, you can't manually scale the node pool. The scale is controlled by the AKS autoscaler. diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/editing-clusters.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/editing-clusters.md deleted file mode 100644 index b6baba3117d..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/editing-clusters.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Cluster Configuration -weight: 2025 ---- - -After you provision a Kubernetes cluster using Rancher, you can still edit options and settings for the cluster. - -For information on editing cluster membership, go to [this page.]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/cluster-members) - -### Cluster Configuration References - -The cluster configuration options depend on the type of Kubernetes cluster: - -- [RKE Cluster Configuration](./rke-config-reference) -- [RKE2 Cluster Configuration](./rke2-config-reference) -- [K3s Cluster Configuration](./k3s-config-reference) -- [EKS Cluster Configuration](./eks-config-reference) -- [GKE Cluster Configuration](./gke-config-reference) -- [AKS Cluster Configuration](./aks-config-reference) - -### Cluster Management Capabilities by Cluster Type - -The options and settings available for an existing cluster change based on the method that you used to provision it. - -The following table summarizes the options and settings available for each cluster type: - -import ClusterCapabilitiesTable from '/rancher/v2.6/en/shared-files/_cluster-capabilities-table.md'; - - - diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/eks-config-reference/eks-config-reference.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/eks-config-reference/eks-config-reference.md deleted file mode 100644 index 4eec75f21f7..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/eks-config-reference/eks-config-reference.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -title: EKS Cluster Configuration Reference -shortTitle: EKS Cluster Configuration -weight: 2 ---- - -### Account Access - -Complete each drop-down and field using the information obtained for your IAM policy. - -| Setting | Description | -| ---------- | -------------------------------------------------------------------------------------------------------------------- | -| Region | From the drop-down choose the geographical region in which to build your cluster. | -| Cloud Credentials | Select the cloud credentials that you created for your IAM policy. For more information on creating cloud credentials in Rancher, refer to [this page.]({{}}/rancher/v2.6/en/user-settings/cloud-credentials/) | - -### Service Role - -Choose a [service role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html). - -Service Role | Description --------------|--------------------------- -Standard: Rancher generated service role | If you choose this role, Rancher automatically adds a service role for use with the cluster. -Custom: Choose from your existing service roles | If you choose this role, Rancher lets you choose from service roles that you're already created within AWS. For more information on creating a custom service role in AWS, see the [Amazon documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#create-service-linked-role). - -### Secrets Encryption - -Optional: To encrypt secrets, select or enter a key created in [AWS Key Management Service (KMS)](https://docs.aws.amazon.com/kms/latest/developerguide/overview.html) - -### API Server Endpoint Access - -Configuring Public/Private API access is an advanced use case. For details, refer to the EKS cluster endpoint access control [documentation.](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) - -### Private-only API Endpoints - -If you enable private and disable public API endpoint access when creating a cluster, then there is an extra step you must take in order for Rancher to connect to the cluster successfully. In this case, a pop-up will be displayed with a command that you will run on the cluster to register it with Rancher. Once the cluster is provisioned, you can run the displayed command anywhere you can connect to the cluster's Kubernetes API. - -There are two ways to avoid this extra manual step: -- You can create the cluster with both private and public API endpoint access on cluster creation. You can disable public access after the cluster is created and in an active state and Rancher will continue to communicate with the EKS cluster. -- You can ensure that Rancher shares a subnet with the EKS cluster. Then security groups can be used to enable Rancher to communicate with the cluster's API endpoint. In this case, the command to register the cluster is not needed, and Rancher will be able to communicate with your cluster. For more information on configuring security groups, refer to the [security groups documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html). - -### Public Access Endpoints - -Optionally limit access to the public endpoint via explicit CIDR blocks. - -If you limit access to specific CIDR blocks, then it is recommended that you also enable the private access to avoid losing network communication to the cluster. - -One of the following is required to enable private access: -- Rancher's IP must be part of an allowed CIDR block -- Private access should be enabled, and Rancher must share a subnet with the cluster and have network access to the cluster, which can be configured with a security group - -For more information about public and private access to the cluster endpoint, refer to the [Amazon EKS documentation.](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) - -### Subnet - -| Option | Description | -| ------- | ------------ | -| Standard: Rancher generated VPC and Subnet | While provisioning your cluster, Rancher generates a new VPC with 3 public subnets. | -| Custom: Choose from your existing VPC and Subnets | While provisioning your cluster, Rancher configures your Control Plane and nodes to use a VPC and Subnet that you've already [created in AWS](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html). | - - For more information, refer to the AWS documentation for [Cluster VPC Considerations](https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html). Follow one of the sets of instructions below based on your selection from the previous step. - -- [What Is Amazon VPC?](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html) -- [VPCs and Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html) - -### Security Group - -Amazon Documentation: - -- [Cluster Security Group Considerations](https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html) -- [Security Groups for Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) -- [Create a Security Group](https://docs.aws.amazon.com/vpc/latest/userguide/getting-started-ipv4.html#getting-started-create-security-group) - -### Logging - -Configure control plane logs to send to Amazon CloudWatch. You are charged the standard CloudWatch Logs data ingestion and storage costs for any logs sent to CloudWatch Logs from your clusters. - -Each log type corresponds to a component of the Kubernetes control plane. To learn more about these components, see [Kubernetes Components](https://kubernetes.io/docs/concepts/overview/components/) in the Kubernetes documentation. - -For more information on EKS control plane logging, refer to the official [documentation.](https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html) - -### Managed Node Groups - -Amazon EKS managed node groups automate the provisioning and lifecycle management of nodes (Amazon EC2 instances) for Amazon EKS Kubernetes clusters. - -For more information about how node groups work and how they are configured, refer to the [EKS documentation.](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) - -#### Bring your own launch template - -A launch template ID and version can be provided in order to easily configure the EC2 instances in a node group. If a launch template is provided, then none of the settings below will be configurable in Rancher. Therefore, using a launch template would require that all the necessary and desired settings from the list below would need to be specified in the launch template. Also note that if a launch template ID and version is provided, then only the template version can be updated. Using a new template ID would require creating a new managed node group. - -| Option | Description | Required/Optional | -| ------ | ----------- | ----------------- | -| Instance Type | Choose the [hardware specs](https://aws.amazon.com/ec2/instance-types/) for the instance you're provisioning. | Required | -| Image ID | Specify a custom AMI for the nodes. Custom AMIs used with EKS must be [configured properly](https://aws.amazon.com/premiumsupport/knowledge-center/eks-custom-linux-ami/) | Optional | -| Node Volume Size | The launch template must specify an EBS volume with the desired size | Required | -| SSH Key | A key to be added to the instances to provide SSH access to the nodes | Optional | -| User Data | Cloud init script in [MIME multi-part format](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html#launch-template-user-data) | Optional | -| Instance Resource Tags | Tag each EC2 instance in the node group | Optional | - -#### Rancher-managed launch templates - -If you do not specify a launch template, then you will be able to configure the above options in the Rancher UI and all of them can be updated after creation. In order to take advantage of all of these options, Rancher will create and manage a launch template for you. Each cluster in Rancher will have one Rancher-managed launch template and each managed node group that does not have a specified launch template will have one version of the managed launch template. The name of this launch template will have the prefix "rancher-managed-lt-" followed by the display name of the cluster. In addition, the Rancher-managed launch template will be tagged with the key "rancher-managed-template" and value "do-not-modify-or-delete" to help identify it as Rancher-managed. It is important that this launch template and its versions not be modified, deleted, or used with any other clusters or managed node groups. Doing so could result in your node groups being "degraded" and needing to be destroyed and recreated. - -#### Custom AMIs - -If you specify a custom AMI, whether in a launch template or in Rancher, then the image must be [configured properly](https://aws.amazon.com/premiumsupport/knowledge-center/eks-custom-linux-ami/) and you must provide user data to [bootstrap the node](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html#launch-template-custom-ami). This is considered an advanced use case and understanding the requirements is imperative. - -If you specify a launch template that does not contain a custom AMI, then Amazon will use the [EKS-optimized AMI](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html) for the Kubernetes version and selected region. You can also select a [GPU enabled instance](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html#gpu-ami) for workloads that would benefit from it. - ->**Note** ->The GPU enabled instance setting in Rancher is ignored if a custom AMI is provided, either in the dropdown or in a launch template. - -#### Spot instances - -Spot instances are now [supported by EKS](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html#managed-node-group-capacity-types-spot). If a launch template is specified, Amazon recommends that the template not provide an instance type. Instead, Amazon recommends providing multiple instance types. If the "Request Spot Instances" checkbox is enabled for a node group, then you will have the opportunity to provide multiple instance types. - ->**Note** ->Any selection you made in the instance type dropdown will be ignored in this situation and you must specify at least one instance type to the "Spot Instance Types" section. Furthermore, a launch template used with EKS cannot request spot instances. Requesting spot instances must be part of the EKS configuration. - -#### Node Group Settings - -The following settings are also configurable. All of these except for the "Node Group Name" are editable after the node group is created. - -| Option | Description | -| ------- | ------------ | -| Node Group Name | The name of the node group. | -| Desired ASG Size | The desired number of instances. | -| Maximum ASG Size | The maximum number of instances. This setting won't take effect until the [Cluster Autoscaler](https://docs.aws.amazon.com/eks/latest/userguide/cluster-autoscaler.html) is installed. | -| Minimum ASG Size | The minimum number of instances. This setting won't take effect until the [Cluster Autoscaler](https://docs.aws.amazon.com/eks/latest/userguide/cluster-autoscaler.html) is installed. | -| Labels | Kubernetes labels applied to the nodes in the managed node group. | -| Tags | These are tags for the managed node group and do not propagate to any of the associated resources. | - - -### Configuring the Refresh Interval - -The `eks-refresh-cron` setting is deprecated. It has been migrated to the `eks-refresh` setting, which is an integer representing seconds. - -The default value is 300 seconds. - -The syncing interval can be changed by running `kubectl edit setting eks-refresh`. - -If the `eks-refresh-cron` setting was previously set, the migration will happen automatically. - -The shorter the refresh window, the less likely any race conditions will occur, but it does increase the likelihood of encountering request limits that may be in place for AWS APIs. - diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/gke-config-reference.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/gke-config-reference.md deleted file mode 100644 index b87543a3157..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/gke-config-reference.md +++ /dev/null @@ -1,307 +0,0 @@ ---- -title: GKE Cluster Configuration Reference -shortTitle: GKE Cluster Configuration -weight: 3 ---- - -# Changes in Rancher v2.6 - -- Support for additional configuration options: - - Project network isolation - - Network tags - -# Cluster Location - -| Value | Description | -|--------|--------------| -| Location Type | Zonal or Regional. With GKE, you can create a cluster tailored to the availability requirements of your workload and your budget. By default, a cluster's nodes run in a single compute zone. When multiple zones are selected, the cluster's nodes will span multiple compute zones, while the controlplane is located in a single zone. Regional clusters increase the availability of the controlplane as well. For help choosing the type of cluster availability, refer to [these docs.](https://cloud.google.com/kubernetes-engine/docs/best-practices/scalability#choosing_a_regional_or_zonal_control_plane) | -| Zone | Each region in Compute engine contains a number of zones. For more information about available regions and zones, refer to [these docs.](https://cloud.google.com/compute/docs/regions-zones#available) | -| Additional Zones | For zonal clusters, you can select additional zones to create a [multi-zone cluster.](https://cloud.google.com/kubernetes-engine/docs/concepts/types-of-clusters#multi-zonal_clusters) | -| Region | For [regional clusters,](https://cloud.google.com/kubernetes-engine/docs/concepts/types-of-clusters#regional_clusters) you can select a region. For more information about available regions and zones, refer to [this section](https://cloud.google.com/compute/docs/regions-zones#available). The first part of each zone name is the name of the region. | - -# Cluster Options - -### Kubernetes Version - -_Mutable: yes_ - -For more information on GKE Kubernetes versions, refer to [these docs.](https://cloud.google.com/kubernetes-engine/versioning) - -### Container Address Range - -_Mutable: no_ - -The IP address range for pods in the cluster. Must be a valid CIDR range, e.g. 10.42.0.0/16. If not specified, a random range is automatically chosen from 10.0.0.0/8 and will exclude ranges already allocated to VMs, other clusters, or routes. Automatically chosen ranges may conflict with reserved IP addresses, dynamic routes, or routes within VPCs peering with the cluster. - -### Network - -_Mutable: no_ - -The Compute Engine Network that the cluster connects to. Routes and firewalls will be created using this network. If using [Shared VPCs](https://cloud.google.com/vpc/docs/shared-vpc), the VPC networks that are shared to your project will appear here. will be available to select in this field. For more information, refer to [this page](https://cloud.google.com/vpc/docs/vpc#vpc_networks_and_subnets). - -### Node Subnet / Subnet - -_Mutable: no_ - -The Compute Engine subnetwork that the cluster connects to. This subnetwork must belong to the network specified in the **Network** field. Select an existing subnetwork, or select "Auto Create Subnetwork" to have one automatically created. If not using an existing network, **Subnetwork Name** is required to generate one. If using [Shared VPCs](https://cloud.google.com/vpc/docs/shared-vpc), the VPC subnets that are shared to your project will appear here. If using a Shared VPC network, you cannot select "Auto Create Subnetwork". For more information, refer to [this page.](https://cloud.google.com/vpc/docs/vpc#vpc_networks_and_subnets) - -### Subnetwork Name - -_Mutable: no_ - -Automatically create a subnetwork with the provided name. Required if "Auto Create Subnetwork" is selected for **Node Subnet** or **Subnet**. For more information on subnetworks, refer to [this page.](https://cloud.google.com/vpc/docs/vpc#vpc_networks_and_subnets) - -### Ip Aliases - -_Mutable: no_ - -Enable [alias IPs](https://cloud.google.com/vpc/docs/alias-ip). This enables VPC-native traffic routing. Required if using [Shared VPCs](https://cloud.google.com/vpc/docs/shared-vpc). - -### Network Policy - -_Mutable: yes_ - -Enable network policy enforcement on the cluster. A network policy defines the level of communication that can occur between pods and services in the cluster. For more information, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy) - -### Project Network Isolation - -_Mutable: yes_ - -choose whether to enable or disable inter-project communication. Note that enabling Project Network Isolation will automatically enable Network Policy and Network Policy Config, but not vice versa. - -### Node Ipv4 CIDR Block - -_Mutable: no_ - -The IP address range of the instance IPs in this cluster. Can be set if "Auto Create Subnetwork" is selected for **Node Subnet** or **Subnet**. Must be a valid CIDR range, e.g. 10.96.0.0/14. For more information on how to determine the IP address range, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#cluster_sizing) - -### Cluster Secondary Range Name - -_Mutable: no_ - -The name of an existing secondary range for Pod IP addresses. If selected, **Cluster Pod Address Range** will automatically be populated. Required if using a Shared VPC network. - -### Cluster Pod Address Range - -_Mutable: no_ - -The IP address range assigned to pods in the cluster. Must be a valid CIDR range, e.g. 10.96.0.0/11. If not provided, will be created automatically. Must be provided if using a Shared VPC network. For more information on how to determine the IP address range for your pods, refer to [this section.](https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#cluster_sizing_secondary_range_pods) - -### Services Secondary Range Name - -_Mutable: no_ - -The name of an existing secondary range for service IP addresses. If selected, **Service Address Range** will be automatically populated. Required if using a Shared VPC network. - -### Service Address Range - -_Mutable: no_ - -The address range assigned to the services in the cluster. Must be a valid CIDR range, e.g. 10.94.0.0/18. If not provided, will be created automatically. Must be provided if using a Shared VPC network. For more information on how to determine the IP address range for your services, refer to [this section.](https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#cluster_sizing_secondary_range_svcs) - -### Private Cluster - -_Mutable: no_ - -> Warning: private clusters require additional planning and configuration outside of Rancher. Refer to the [private cluster guide]({{< baseurl >}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/private-clusters/). - -Assign nodes only internal IP addresses. Private cluster nodes cannot access the public internet unless additional networking steps are taken in GCP. - -### Enable Private Endpoint - -> Warning: private clusters require additional planning and configuration outside of Rancher. Refer to the [private cluster guide]({{< baseurl >}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/private-clusters/). - -_Mutable: no_ - -Locks down external access to the control plane endpoint. Only available if **Private Cluster** is also selected. If selected, and if Rancher does not have direct access to the Virtual Private Cloud network the cluster is running in, Rancher will provide a registration command to run on the cluster to enable Rancher to connect to it. - -### Master IPV4 CIDR Block - -_Mutable: no_ - -The IP range for the control plane VPC. - -### Master Authorized Network - -_Mutable: yes_ - -Enable control plane authorized networks to block untrusted non-GCP source IPs from accessing the Kubernetes master through HTTPS. If selected, additional authorized networks may be added. If the cluster is created with a public endpoint, this option is useful for locking down access to the public endpoint to only certain networks, such as the network where your Rancher service is running. If the cluster only has a private endpoint, this setting is required. - -# Additional Options - -### Cluster Addons - -Additional Kubernetes cluster components. For more information, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#Cluster.AddonsConfig) - -#### Horizontal Pod Autoscaling - -_Mutable: yes_ - -The Horizontal Pod Autoscaler changes the shape of your Kubernetes workload by automatically increasing or decreasing the number of Pods in response to the workload's CPU or memory consumption, or in response to custom metrics reported from within Kubernetes or external metrics from sources outside of your cluster. For more information, see [this page.](https://cloud.google.com/kubernetes-engine/docs/concepts/horizontalpodautoscaler) - -#### HTTP (L7) Load Balancing - -_Mutable: yes_ - -HTTP (L7) Load Balancing distributes HTTP and HTTPS traffic to backends hosted on GKE. For more information, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer) - -#### Network Policy Config (master only) - -_Mutable: yes_ - -Configuration for NetworkPolicy. This only tracks whether the addon is enabled or not on the master, it does not track whether network policy is enabled for the nodes. - -### Cluster Features (Alpha Features) - -_Mutable: no_ - -Turns on all Kubernetes alpha API groups and features for the cluster. When enabled, the cluster cannot be upgraded and will be deleted automatically after 30 days. Alpha clusters are not recommended for production use as they are not covered by the GKE SLA. For more information, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/concepts/alpha-clusters) - -### Logging Service - -_Mutable: yes_ - -The logging service the cluster uses to write logs. Use either [Cloud Logging](https://cloud.google.com/logging) or no logging service in which case no logs are exported from the cluster. - -### Monitoring Service - -_Mutable: yes_ - -The monitoring service the cluster uses to write metrics. Use either [Cloud Monitoring](https://cloud.google.com/monitoring) or monitoring service in which case no metrics are exported from the cluster. - - -### Maintenance Window - -_Mutable: yes_ - -Set the start time for a 4 hour maintenance window. The time is specified in the UTC time zone using the HH:MM format. For more information, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions) - -# Node Pools - -In this section, enter details describing the configuration of each node in the node pool. - -### Kubernetes Version - -_Mutable: yes_ - -The Kubernetes version for each node in the node pool. For more information on GKE Kubernetes versions, refer to [these docs.](https://cloud.google.com/kubernetes-engine/versioning) - -### Image Type - -_Mutable: yes_ - -The node operating system image. For more information for the node image options that GKE offers for each OS, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/concepts/node-images#available_node_images) - -> Note: the default option is "Container-Optimized OS with Docker". The read-only filesystem on GCP's Container-Optimized OS is not compatible with the [legacy logging]({{}}/rancher/v2.0-v2.4/en/cluster-admin/tools/logging) implementation in Rancher. If you need to use the legacy logging feature, select "Ubuntu with Docker" or "Ubuntu with Containerd". The [current logging feature]({{}}/rancher/v2.6/en/logging) is compatible with the Container-Optimized OS image. - -> Note: if selecting "Windows Long Term Service Channel" or "Windows Semi-Annual Channel" for the node pool image type, you must also add at least one Container-Optimized OS or Ubuntu node pool. - -### Machine Type - -_Mutable: no_ - -The virtualized hardware resources available to node instances. For more information on Google Cloud machine types, refer to [this page.](https://cloud.google.com/compute/docs/machine-types#machine_types) - -### Root Disk Type - -_Mutable: no_ - -Standard persistent disks are backed by standard hard disk drives (HDD), while SSD persistent disks are backed by solid state drives (SSD). For more information, refer to [this section.](https://cloud.google.com/compute/docs/disks) - -### Local SSD Disks - -_Mutable: no_ - -Configure each node's local SSD disk storage in GB. Local SSDs are physically attached to the server that hosts your VM instance. Local SSDs have higher throughput and lower latency than standard persistent disks or SSD persistent disks. The data that you store on a local SSD persists only until the instance is stopped or deleted. For more information, see [this section.](https://cloud.google.com/compute/docs/disks#localssds) - -### Preemptible nodes (beta) - -_Mutable: no_ - -Preemptible nodes, also called preemptible VMs, are Compute Engine VM instances that last a maximum of 24 hours in general, and provide no availability guarantees. For more information, see [this page.](https://cloud.google.com/kubernetes-engine/docs/how-to/preemptible-vms) - -### Taints - -_Mutable: no_ - -When you apply a taint to a node, only Pods that tolerate the taint are allowed to run on the node. In a GKE cluster, you can apply a taint to a node pool, which applies the taint to all nodes in the pool. - -### Node Labels - -_Mutable: no_ - -You can apply labels to the node pool, which applies the labels to all nodes in the pool. - -Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) - -### Network Tags - -_Mutable: no_ - -You can add network tags to the node pool to make firewall rules and routes between subnets. Tags will apply to all nodes in the pool. - -For details on tag syntax and requirements, see the [Kubernetes documentation](https://cloud.google.com/vpc/docs/add-remove-network-tags). - -# Group Details - -In this section, enter details describing the node pool. - -### Name - -_Mutable: no_ - -Enter a name for the node pool. - -### Initial Node Count - -_Mutable: yes_ - -Integer for the starting number of nodes in the node pool. - -### Max Pod Per Node - -_Mutable: no_ - -GKE has a hard limit of 110 Pods per node. For more information on the Kubernetes limits, see [this section.](https://cloud.google.com/kubernetes-engine/docs/best-practices/scalability#dimension_limits) - -### Autoscaling - -_Mutable: yes_ - -Node pool autoscaling dynamically creates or deletes nodes based on the demands of your workload. For more information, see [this page.](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler) - -### Auto Repair - -_Mutable: yes_ - -GKE's node auto-repair feature helps you keep the nodes in your cluster in a healthy, running state. When enabled, GKE makes periodic checks on the health state of each node in your cluster. If a node fails consecutive health checks over an extended time period, GKE initiates a repair process for that node. For more information, see the section on [auto-repairing nodes.](https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair) - -### Auto Upgrade - -_Mutable: yes_ - -When enabled, the auto-upgrade feature keeps the nodes in your cluster up-to-date with the cluster control plane (master) version when your control plane is [updated on your behalf.](https://cloud.google.com/kubernetes-engine/upgrades#automatic_cp_upgrades) For more information about auto-upgrading nodes, see [this page.](https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-upgrades) - -### Access Scopes - -_Mutable: no_ - -Access scopes are the legacy method of specifying permissions for your nodes. - -- **Allow default access:** The default access for new clusters is the [Compute Engine default service account.](https://cloud.google.com/compute/docs/access/service-accounts?hl=en_US#default_service_account) -- **Allow full access to all Cloud APIs:** Generally, you can just set the cloud-platform access scope to allow full access to all Cloud APIs, then grant the service account only relevant IAM roles. The combination of access scopes granted to the virtual machine instance and the IAM roles granted to the service account determines the amount of access the service account has for that instance. -- **Set access for each API:** Alternatively, you can choose to set specific scopes that permit access to the particular API methods that the service will call. - -For more information, see the [section about enabling service accounts for a VM.](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances) - - -### Configuring the Refresh Interval - -The refresh interval can be configured through the setting "gke-refresh", which is an integer representing seconds. - -The default value is 300 seconds. - -The syncing interval can be changed by running `kubectl edit setting gke-refresh`. - -The shorter the refresh window, the less likely any race conditions will occur, but it does increase the likelihood of encountering request limits that may be in place for GCP APIs. - diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/private-clusters/private-clusters.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/private-clusters/private-clusters.md deleted file mode 100644 index 95d9bd39bcc..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/gke-config-reference/private-clusters/private-clusters.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Private Clusters -weight: 2 ---- - -In GKE, [private clusters](https://cloud.google.com/kubernetes-engine/docs/concepts/private-cluster-concept) are clusters whose nodes are isolated from inbound and outbound traffic by assigning them internal IP addresses only. Private clusters in GKE have the option of exposing the control plane endpoint as a publicly accessible address or as a private address. This is different from other Kubernetes providers, which may refer to clusters with private control plane endpoints as "private clusters" but still allow traffic to and from nodes. You may want to create a cluster with private nodes, with or without a public control plane endpoint, depending on your organization's networking and security requirements. A GKE cluster provisioned from Rancher can use isolated nodes by selecting "Private Cluster" in the Cluster Options (under "Show advanced options"). The control plane endpoint can optionally be made private by selecting "Enable Private Endpoint". - -### Private Nodes - -Because the nodes in a private cluster only have internal IP addresses, they will not be able to install the cluster agent and Rancher will not be able to fully manage the cluster. This can be overcome in a few ways. - -#### Cloud NAT - ->**Note** ->Cloud NAT will [incur charges](https://cloud.google.com/nat/pricing). - -If restricting outgoing internet access is not a concern for your organization, use Google's [Cloud NAT](https://cloud.google.com/nat/docs/using-nat) service to allow nodes in the private network to access the internet, enabling them to download the required images from Dockerhub and contact the Rancher management server. This is the simplest solution. - -#### Private registry - ->**Note** ->This scenario is not officially supported, but is described for cases in which using the Cloud NAT service is not sufficient. - -If restricting both incoming and outgoing traffic to nodes is a requirement, follow the air-gapped installation instructions to set up a private container image [registry](https://rancher.com/docs/rancher/v2.6/en/installation/other-installation-methods/air-gap/) on the VPC where the cluster is going to be, allowing the cluster nodes to access and download the images they need to run the cluster agent. If the control plane endpoint is also private, Rancher will need [direct access](#direct-access) to it. - -### Private Control Plane Endpoint - -If the cluster has a public endpoint exposed, Rancher will be able to reach the cluster, and no additional steps need to be taken. However, if the cluster has no public endpoint, then considerations must be made to ensure Rancher can access the cluster. - -#### Cloud NAT - ->**Note** ->Cloud NAT will [incur charges](https://cloud.google.com/nat/pricing). - -As above, if restricting outgoing internet access to the nodes is not a concern, then Google's [Cloud NAT](https://cloud.google.com/nat/docs/using-nat) service can be used to allow the nodes to access the internet. While the cluster is provisioning, Rancher will provide a registration command to run on the cluster. Download the [kubeconfig](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl) for the new cluster and run the provided kubectl command on the cluster. Gaining access -to the cluster in order to run this command can be done by creating a temporary node or using an existing node in the VPC, or by logging on to or creating an SSH tunnel through one of the cluster nodes. - -#### Direct access - -If the Rancher server is run on the same VPC as the cluster's control plane, it will have direct access to the control plane's private endpoint. The cluster nodes will need to have access to a [private registry](#private-registry) to download images as described above. - -You can also use services from Google such as [Cloud VPN](https://cloud.google.com/network-connectivity/docs/vpn/concepts/overview) or [Cloud Interconnect VLAN](https://cloud.google.com/network-connectivity/docs/interconnect) to facilitate connectivity between your organization's network and your Google VPC. diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/k3s-config-reference/k3s-config-reference.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/k3s-config-reference/k3s-config-reference.md deleted file mode 100644 index 00d784cfa0c..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/k3s-config-reference/k3s-config-reference.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -title: K3s Cluster Configuration Reference -shortTitle: K3s Cluster Configuration -weight: 6 ---- - -This section covers the configuration options that are available in Rancher for a new or existing K3s Kubernetes cluster. - -# Overview - -You can configure the Kubernetes options one of two ways: - -- [Rancher UI](#configuration-options-in-the-rancher-ui): Use the Rancher UI to select options that are commonly customized when setting up a Kubernetes cluster. -- [Cluster Config File](#cluster-config-file): Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create a K3s config file. Using a config file allows you to set any of the [options](https://rancher.com/docs/k3s/latest/en/installation/install-options/) available in an K3s installation. - -# Configuration Options in the Rancher UI - -> Some advanced configuration options are not exposed in the Rancher UI forms, but they can be enabled by editing the K3s cluster configuration file in YAML. For the complete reference of configurable options for K3s clusters in YAML, see the [K3s documentation.](https://rancher.com/docs/k3s/latest/en/installation/install-options/) - -### Basics -#### Kubernetes Version - -The version of Kubernetes installed on your cluster nodes. Rancher packages its own version of Kubernetes based on [hyperkube](https://github.com/rancher/hyperkube). - -For more detail, see [Upgrading Kubernetes]({{}}/rancher/v2.6/en/cluster-admin/upgrading-kubernetes). - -#### Encrypt Secrets - -Option to enable or disable secrets encryption. When enabled, secrets will be encrypted using a AES-CBC key. If disabled, any previously secrets will not be readable until encryption is enabled again. Refer to the [K3s documentation](https://rancher.com/docs/k3s/latest/en/advanced/#secrets-encryption-config-experimental) for details. - -#### Project Network Isolation - -If your network provider allows project network isolation, you can choose whether to enable or disable inter-project communication. - -#### SELinux - -Option to enable or disable [SELinux](https://rancher.com/docs/k3s/latest/en/advanced/#selinux-support) support. - -#### CoreDNS - -By default, [CoreDNS](https://coredns.io/) is installed as the default DNS provider. If CoreDNS is not installed, an alternate DNS provider must be installed yourself. Refer to the [K3s documentation](https://rancher.com/docs/k3s/latest/en/networking/#coredns) for details.. - -#### Klipper Service LB - -Option to enable or disable the [Klipper](https://github.com/rancher/klipper-lb) service load balancer. Refer to the [K3s documentation](https://rancher.com/docs/k3s/latest/en/networking/#service-load-balancer) for details. - -#### Traefik Ingress - -Option to enable or disable the [Traefik](https://traefik.io/) HTTP reverse proxy and load balancer. For more details and configuration options, see the [K3s documentation](https://rancher.com/docs/k3s/latest/en/networking/#traefik-ingress-controller). - -#### Local Storage - -Option to enable or disable [local storage](https://rancher.com/docs/k3s/latest/en/storage/) on the node(s). - -#### Metrics Server - -Option to enable or disable the [metrics server](https://github.com/kubernetes-incubator/metrics-server). If enabled, ensure port 10250 is opened for inbound TCP traffic. - -### Add-On Config - -Additional Kubernetes manifests, managed as a [Add-on](https://kubernetes.io/docs/concepts/cluster-administration/addons/), to apply to the cluster on startup. Refer to the [K3s documentation](https://rancher.com/docs/k3s/latest/en/helm/#automatically-deploying-manifests-and-helm-charts) for details. - -### Agent Environment Vars - -Option to set environment variables for [K3s agents](https://rancher.com/docs/k3s/latest/en/architecture/). The environment variables can be set using key value pairs. Refer to the [K3 documentation](https://rancher.com/docs/k3s/latest/en/installation/install-options/agent-config/) for more details. - -### etcd - -#### Automatic Snapshots - -Option to enable or disable recurring etcd snapshots. If enabled, users have the option to configure the frequency of snapshots. For details, refer to the [K3s documentation](https://rancher.com/docs/k3s/latest/en/backup-restore/#creating-snapshots). - -#### Metrics - -Option to choose whether to expose etcd metrics to the public or only within the cluster. - -### Networking - -#### Cluster CIDR - -IPv4/IPv6 network CIDRs to use for pod IPs (default: 10.42.0.0/16). - -#### Service CIDR - -IPv4/IPv6 network CIDRs to use for service IPs (default: 10.43.0.0/16). - -#### Cluster DNS - -IPv4 Cluster IP for coredns service. Should be in your service-cidr range (default: 10.43.0.10). - -#### Cluster Domain - -Select the domain for the cluster. The default is `cluster.local`. - -#### NodePort Service Port Range - -Option to change the range of ports that can be used for [NodePort services](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport). The default is `30000-32767`. - -#### TLS Alternate Names - -Add additional hostnames or IPv4/IPv6 addresses as Subject Alternative Names on the server TLS cert. - -#### Authorized Cluster Endpoint - -Authorized Cluster Endpoint can be used to directly access the Kubernetes API server, without requiring communication through Rancher. - -For more detail on how an authorized cluster endpoint works and why it is used, refer to the [architecture section.]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) - -We recommend using a load balancer with the authorized cluster endpoint. For details, refer to the [recommended architecture section.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#architecture-for-an-authorized-cluster-endpoint) - -### Registries - -Select the image repository to pull Rancher images from. For more details and configuration options, see the [K3s documentation](https://rancher.com/docs/k3s/latest/en/installation/private-registry/). - -### Upgrade Strategy - -#### Controle Plane Concurrency - -Select how many nodes can be upgraded at the same time. Can be a fixed number or percentage. - -#### Worker Concurrency - -Select how many nodes can be upgraded at the same time. Can be a fixed number or percentage. - -#### Drain Nodes (Control Plane) - -Option to remove all pods from the node prior to upgrading. - -#### Drain Nodes (Worker Nodes) - -Option to remove all pods from the node prior to upgrading. - -### Advanced - -Option to set kubelet options for different nodes. For available options, refer to the [Kubernetes documentation](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/). - -# Cluster Config File - -Instead of using the Rancher UI forms to choose Kubernetes options for the cluster, advanced users can create an K3s config file. Using a config file allows you to set any of the [options](https://rancher.com/docs/k3s/latest/en/installation/install-options/) available in an K3s installation. - -To edit an K3s config file directly from the Rancher UI, click **Edit as YAML**. - - diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/rke-config-reference/rke-config-reference.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/rke-config-reference/rke-config-reference.md deleted file mode 100644 index 4c553c29959..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/rke-config-reference/rke-config-reference.md +++ /dev/null @@ -1,360 +0,0 @@ ---- -title: RKE Cluster Configuration Reference -shortTitle: RKE Cluster Configuration -weight: 1 ---- - -When Rancher installs Kubernetes, it uses [RKE]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) or [RKE2](https://docs.rke2.io/) as the Kubernetes distribution. - -This section covers the configuration options that are available in Rancher for a new or existing RKE Kubernetes cluster. - -- [Overview](#overview) -- [Editing Clusters with a Form in the Rancher UI](#editing-clusters-with-a-form-in-the-rancher-ui) -- [Editing Clusters with YAML](#editing-clusters-with-yaml) -- [Configuration Options in the Rancher UI](#configuration-options-in-the-rancher-ui) - - [Kubernetes Version](#kubernetes-version) - - [Network Provider](#network-provider) - - [Project Network Isolation](#project-network-isolation) - - [Kubernetes Cloud Providers](#kubernetes-cloud-providers) - - [Private Registries](#private-registries) - - [Authorized Cluster Endpoint](#authorized-cluster-endpoint) - - [Node Pools](#node-pools) - - [NGINX Ingress](#nginx-ingress) - - [Metrics Server Monitoring](#metrics-server-monitoring) - - [Pod Security Policy Support](#pod-security-policy-support) - - [Docker Version on Nodes](#docker-version-on-nodes) - - [Docker Root Directory](#docker-root-directory) - - [Default Pod Security Policy](#default-pod-security-policy) - - [Node Port Range](#node-port-range) - - [Recurring etcd Snapshots](#recurring-etcd-snapshots) - - [Agent Environment Variables](#agent-environment-variables) - - [Updating ingress-nginx](#updating-ingress-nginx) -- [RKE Cluster Config File Reference](#rke-cluster-config-file-reference) - - [Config File Structure in Rancher](#config-file-structure-in-rancher) - - [Default DNS Provider](#default-dns-provider) -- [Rancher Specific Parameters in YAML](#rancher-specific-parameters-in-yaml) - - [docker_root_dir](#docker_root_dir) - - [enable_cluster_monitoring](#enable_cluster_monitoring) - - [enable_network_policy](#enable_network_policy) - - [local_cluster_auth_endpoint](#local_cluster_auth_endpoint) - - [Custom Network Plug-in](#custom-network-plug-in) - -# Overview - -You can configure the Kubernetes options one of two ways: - -- [Rancher UI](#rancher-ui-options): Use the Rancher UI to select options that are commonly customized when setting up a Kubernetes cluster. -- [Cluster Config File](#cluster-config-file): Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the options available in an RKE installation, except for system_images configuration, by specifying them in YAML. - -The RKE cluster config options are nested under the `rancher_kubernetes_engine_config` directive. For more information, see the section about the [cluster config file.](#cluster-config-file) - -In [clusters launched by RKE]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/), you can edit any of the remaining options that follow. - -For an example of RKE config file syntax, see the [RKE documentation]({{}}/rke/latest/en/example-yamls/). - -The forms in the Rancher UI don't include all advanced options for configuring RKE. For the complete reference of configurable options for RKE Kubernetes clusters in YAML, see the [RKE documentation.]({{}}/rke/latest/en/config-options/) - -# Editing Clusters with a Form in the Rancher UI - -To edit your cluster, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster you want to configure and click **⋮ > Edit Config**. - - -# Editing Clusters with YAML - -Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the options available in an RKE installation, except for system_images configuration, by specifying them in YAML. - -RKE clusters (also called RKE1 clusters) are edited differently than RKE2 and K3s clusters. - -To edit an RKE config file directly from the Rancher UI, - -1. Click **☰ > Cluster Management**. -1. Go to the RKE cluster you want to configure. Click and click **⋮ > Edit Config**. This take you to the RKE configuration form. Note: Because cluster provisioning changed in Rancher 2.6, the **⋮ > Edit as YAML** can be used for configuring RKE2 clusters, but it can't be used for editing RKE1 configuration. -1. In the configuration form, scroll down and click **Edit as YAML**. -1. Edit the RKE options under the `rancher_kubernetes_engine_config` directive. - -# Configuration Options in the Rancher UI - -> Some advanced configuration options are not exposed in the Rancher UI forms, but they can be enabled by editing the RKE cluster configuration file in YAML. For the complete reference of configurable options for RKE Kubernetes clusters in YAML, see the [RKE documentation.]({{}}/rke/latest/en/config-options/) - -### Kubernetes Version - -The version of Kubernetes installed on your cluster nodes. Rancher packages its own version of Kubernetes based on [hyperkube](https://github.com/rancher/hyperkube). - -For more detail, see [Upgrading Kubernetes]({{}}/rancher/v2.6/en/cluster-admin/upgrading-kubernetes). - -### Network Provider - -The [Network Provider](https://kubernetes.io/docs/concepts/cluster-administration/networking/) that the cluster uses. For more details on the different networking providers, please view our [Networking FAQ]({{}}/rancher/v2.6/en/faq/networking/cni-providers/). - -> After you launch the cluster, you cannot change your network provider. Therefore, choose which network provider you want to use carefully, as Kubernetes doesn't allow switching between network providers. Once a cluster is created with a network provider, changing network providers would require you tear down the entire cluster and all its applications. - -Out of the box, Rancher is compatible with the following network providers: - -- [Canal](https://github.com/projectcalico/canal) -- [Flannel](https://github.com/coreos/flannel#flannel) -- [Calico](https://docs.projectcalico.org/v3.11/introduction/) -- [Weave](https://github.com/weaveworks/weave) - -**Notes on Weave:** - -When Weave is selected as network provider, Rancher will automatically enable encryption by generating a random password. If you want to specify the password manually, please see how to configure your cluster using a [Config File]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) and the [Weave Network Plug-in Options]({{}}/rke/latest/en/config-options/add-ons/network-plugins/#weave-network-plug-in-options). - -### Project Network Isolation - -If your network provider allows project network isolation, you can choose whether to enable or disable inter-project communication. - -Project network isolation is available if you are using any RKE network plugin that supports the enforcement of Kubernetes network policies, such as Canal or the Cisco ACI plugin. - -### Kubernetes Cloud Providers - -You can configure a [Kubernetes cloud provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers). If you want to use dynamically provisioned [volumes and storage]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) in Kubernetes, typically you must select the specific cloud provider in order to use it. For example, if you want to use Amazon EBS, you would need to select the `aws` cloud provider. - ->**Note:** If the cloud provider you want to use is not listed as an option, you will need to use the [config file option](#cluster-config-file) to configure the cloud provider. Please reference the [RKE cloud provider documentation]({{}}/rke/latest/en/config-options/cloud-providers/) on how to configure the cloud provider. - -### Private Registries - -The cluster-level private registry configuration is only used for provisioning clusters. - -There are two main ways to set up private registries in Rancher: by setting up the [global default registry]({{}}/rancher/v2.6/en/admin-settings/config-private-registry) through the **Settings** tab in the global view, and by setting up a private registry in the advanced options in the cluster-level settings. The global default registry is intended to be used for air-gapped setups, for registries that do not require credentials. The cluster-level private registry is intended to be used in all setups in which the private registry requires credentials. - -If your private registry requires credentials, you need to pass the credentials to Rancher by editing the cluster options for each cluster that needs to pull images from the registry. - -The private registry configuration option tells Rancher where to pull the [system images]({{}}/rke/latest/en/config-options/system-images/) or [addon images]({{}}/rke/latest/en/config-options/add-ons/) that will be used in your cluster. - -- **System images** are components needed to maintain the Kubernetes cluster. -- **Add-ons** are used to deploy several cluster components, including network plug-ins, the ingress controller, the DNS provider, or the metrics server. - -For more information on setting up a private registry for components applied during the provisioning of the cluster, see the [RKE documentation on private registries]({{}}/rke/latest/en/config-options/private-registries/). - -Rancher v2.6 introduced the ability to configure [ECR registries for RKE clusters]({{}}/rke/latest/en/config-options/private-registries/#amazon-elastic-container-registry-ecr-private-registry-setup). - -### Authorized Cluster Endpoint - -Authorized Cluster Endpoint can be used to directly access the Kubernetes API server, without requiring communication through Rancher. - -> The authorized cluster endpoint only works on Rancher-launched Kubernetes clusters. In other words, it only works in clusters where Rancher [used RKE]({{}}/rancher/v2.6/en/overview/architecture/#tools-for-provisioning-kubernetes-clusters) to provision the cluster. It is not available for clusters in a hosted Kubernetes provider, such as Amazon's EKS. - -This is enabled by default in Rancher-launched Kubernetes clusters, using the IP of the node with the `controlplane` role and the default Kubernetes self signed certificates. - -For more detail on how an authorized cluster endpoint works and why it is used, refer to the [architecture section.]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) - -We recommend using a load balancer with the authorized cluster endpoint. For details, refer to the [recommended architecture section.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#architecture-for-an-authorized-cluster-endpoint) - -### Node Pools - -For information on using the Rancher UI to set up node pools in an RKE cluster, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools) - -### NGINX Ingress - -If you want to publish your applications in a high-availability configuration, and you're hosting your nodes with a cloud-provider that doesn't have a native load-balancing feature, enable this option to use NGINX Ingress within the cluster. - -### Metrics Server Monitoring - -Option to enable or disable [Metrics Server]({{}}/rke/latest/en/config-options/add-ons/metrics-server/). - -Each cloud provider capable of launching a cluster using RKE can collect metrics and monitor for your cluster nodes. Enable this option to view your node metrics from your cloud provider's portal. - -### Pod Security Policy Support - -Enables [pod security policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/) for the cluster. After enabling this option, choose a policy using the **Default Pod Security Policy** drop-down. - -You must have an existing Pod Security Policy configured before you can use this option. - -### Docker Version on Nodes - -Configures whether nodes are allowed to run versions of Docker that Rancher doesn't officially support. - -If you choose to require a supported Docker version, Rancher will stop pods from running on nodes that don't have a supported Docker version installed. - -For details on which Docker versions were tested with each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) - -### Docker Root Directory - -If the nodes you are adding to the cluster have Docker configured with a non-default Docker Root Directory (default is `/var/lib/docker`), specify the correct Docker Root Directory in this option. - -### Default Pod Security Policy - -If you enable **Pod Security Policy Support**, use this drop-down to choose the pod security policy that's applied to the cluster. - -### Node Port Range - -Option to change the range of ports that can be used for [NodePort services](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport). Default is `30000-32767`. - -### Recurring etcd Snapshots - -Option to enable or disable [recurring etcd snapshots]({{}}/rke/latest/en/etcd-snapshots/#etcd-recurring-snapshots). - -### Agent Environment Variables - -Option to set environment variables for [rancher agents]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/rancher-agents/). The environment variables can be set using key value pairs. If rancher agent requires use of proxy to communicate with Rancher server, `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables can be set using agent environment variables. - -### Updating ingress-nginx - -Clusters that were created before Kubernetes 1.16 will have an `ingress-nginx` `updateStrategy` of `OnDelete`. Clusters that were created with Kubernetes 1.16 or newer will have `RollingUpdate`. - -If the `updateStrategy` of `ingress-nginx` is `OnDelete`, you will need to delete these pods to get the correct version for your deployment. - - - -# RKE Cluster Config File Reference - -Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the [options available]({{}}/rke/latest/en/config-options/) in an RKE installation, except for `system_images` configuration. The `system_images` option is not supported when creating a cluster with the Rancher UI or API. - -For the complete reference for configurable options for RKE Kubernetes clusters in YAML, see the [RKE documentation.]({{}}/rke/latest/en/config-options/) - -### Config File Structure in Rancher - -RKE (Rancher Kubernetes Engine) is the tool that Rancher uses to provision Kubernetes clusters. Rancher's cluster config files used to have the same structure as [RKE config files,]({{}}/rke/latest/en/example-yamls/) but the structure changed so that in Rancher, RKE cluster config items are separated from non-RKE config items. Therefore, configuration for your cluster needs to be nested under the `rancher_kubernetes_engine_config` directive in the cluster config file. Cluster config files created with earlier versions of Rancher will need to be updated for this format. An example cluster config file is included below. - -
- Example Cluster Config File - -```yaml -# -# Cluster Config -# -docker_root_dir: /var/lib/docker -enable_cluster_alerting: false -enable_cluster_monitoring: false -enable_network_policy: false -local_cluster_auth_endpoint: - enabled: true -# -# Rancher Config -# -rancher_kubernetes_engine_config: # Your RKE template config goes here. - addon_job_timeout: 30 - authentication: - strategy: x509 - ignore_docker_version: true -# -# # Currently only nginx ingress provider is supported. -# # To disable ingress controller, set `provider: none` -# # To enable ingress on specific nodes, use the node_selector, eg: -# provider: nginx -# node_selector: -# app: ingress -# - ingress: - provider: nginx - kubernetes_version: v1.15.3-rancher3-1 - monitoring: - provider: metrics-server -# -# If you are using calico on AWS -# -# network: -# plugin: calico -# calico_network_provider: -# cloud_provider: aws -# -# # To specify flannel interface -# -# network: -# plugin: flannel -# flannel_network_provider: -# iface: eth1 -# -# # To specify flannel interface for canal plugin -# -# network: -# plugin: canal -# canal_network_provider: -# iface: eth1 -# - network: - options: - flannel_backend_type: vxlan - plugin: canal -# -# services: -# kube-api: -# service_cluster_ip_range: 10.43.0.0/16 -# kube-controller: -# cluster_cidr: 10.42.0.0/16 -# service_cluster_ip_range: 10.43.0.0/16 -# kubelet: -# cluster_domain: cluster.local -# cluster_dns_server: 10.43.0.10 -# - services: - etcd: - backup_config: - enabled: true - interval_hours: 12 - retention: 6 - safe_timestamp: false - creation: 12h - extra_args: - election-timeout: 5000 - heartbeat-interval: 500 - gid: 0 - retention: 72h - snapshot: false - uid: 0 - kube_api: - always_pull_images: false - pod_security_policy: false - service_node_port_range: 30000-32767 - ssh_agent_auth: false -windows_prefered_cluster: false -``` -
- -### Default DNS provider - -The table below indicates what DNS provider is deployed by default. See [RKE documentation on DNS provider]({{}}/rke/latest/en/config-options/add-ons/dns/) for more information how to configure a different DNS provider. CoreDNS can only be used on Kubernetes v1.12.0 and higher. - -| Rancher version | Kubernetes version | Default DNS provider | -|-------------|--------------------|----------------------| -| v2.2.5 and higher | v1.14.0 and higher | CoreDNS | -| v2.2.5 and higher | v1.13.x and lower | kube-dns | -| v2.2.4 and lower | any | kube-dns | - -# Rancher Specific Parameters in YAML - -Besides the RKE config file options, there are also Rancher specific settings that can be configured in the Config File (YAML): - -### docker_root_dir - -See [Docker Root Directory](#docker-root-directory). - -### enable_cluster_monitoring - -Option to enable or disable [Cluster Monitoring]({{}}/rancher/v2.6/en/monitoring-alerting/). - -### enable_network_policy - -Option to enable or disable Project Network Isolation. - -Project network isolation is available if you are using any RKE network plugin that supports the enforcement of Kubernetes network policies, such as Canal or the Cisco ACI plugin. - -### local_cluster_auth_endpoint - -See [Authorized Cluster Endpoint](#authorized-cluster-endpoint). - -Example: - -```yaml -local_cluster_auth_endpoint: - enabled: true - fqdn: "FQDN" - ca_certs: |- - -----BEGIN CERTIFICATE----- - ... - -----END CERTIFICATE----- -``` - -### Custom Network Plug-in - -You can add a custom network plug-in by using the [user-defined add-on functionality]({{}}/rke/latest/en/config-options/add-ons/user-defined-add-ons/) of RKE. You define any add-on that you want deployed after the Kubernetes cluster is deployed. - -There are two ways that you can specify an add-on: - -- [In-line Add-ons]({{}}/rke/latest/en/config-options/add-ons/user-defined-add-ons/#in-line-add-ons) -- [Referencing YAML Files for Add-ons]({{}}/rke/latest/en/config-options/add-ons/user-defined-add-ons/#referencing-yaml-files-for-add-ons) - -For an example of how to configure a custom network plug-in by editing the `cluster.yml`, refer to the [RKE documentation.]({{}}/rke/latest/en/config-options/add-ons/network-plugins/custom-network-plugin-example) diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/rke2-config-reference/rke2-config-reference.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/rke2-config-reference/rke2-config-reference.md deleted file mode 100644 index 3e1ee54d5db..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/rke2-config-reference/rke2-config-reference.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: RKE2 Cluster Configuration Reference -shortTitle: RKE2 Cluster Configuration -weight: 5 ---- - -This section covers the configuration options that are available in Rancher for a new or existing RKE2 Kubernetes cluster. - -# Overview - -You can configure the Kubernetes options in one of the two following ways: - -- [Rancher UI](#configuration-options-in-the-rancher-ui): Use the Rancher UI to select options that are commonly customized when setting up a Kubernetes cluster. -- [Cluster Config File](#cluster-config-file): Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE2 config file. Using a config file allows you to set any of the [options](https://docs.rke2.io/install/install_options/install_options) available in an RKE2 installation. - -# Configuration Options in the Rancher UI - -> Some advanced configuration options are not exposed in the Rancher UI forms, but they can be enabled by editing the RKE2 cluster configuration file in YAML. For the complete reference of configurable options for RKE2 Kubernetes clusters in YAML, see the [RKE2 documentation.](https://docs.rke2.io/install/install_options/install_options/) - -### Basics -#### Kubernetes Version - -The version of Kubernetes installed on your cluster nodes. Rancher packages its own version of Kubernetes based on [hyperkube](https://github.com/rancher/hyperkube). - -For more detail, see [Upgrading Kubernetes]({{}}/rancher/v2.6/en/cluster-admin/upgrading-kubernetes). - -#### Container Network Provider - -The [Network Provider](https://kubernetes.io/docs/concepts/cluster-administration/networking/) that the cluster uses. - -> After you launch the cluster, you cannot change your network provider. Therefore, choose which network provider you want to use carefully, as Kubernetes doesn't allow switching between network providers. Once a cluster is created with a network provider, changing network providers would require you to tear down the entire cluster and all its applications. - -Out of the box, Rancher is compatible with the following network providers: - -- [Canal](https://github.com/projectcalico/canal) -- [Cilium](https://cilium.io/)* -- [Calico](https://docs.projectcalico.org/v3.11/introduction/) -- [Multus](https://github.com/k8snetworkplumbingwg/multus-cni) - -\* When using [project network isolation](#project-network-isolation) in the [Cilium CNI]({{}}/rancher/v2.6/en/faq/networking/cni-providers/#cilium), it is possible to enable cross-node ingress routing. Click the [CNI provider docs]({{}}/rancher/v2.6/en/faq/networking/cni-providers/#ingress-routing-across-nodes-in-cilium) to learn more. - -For more details on the different networking providers and how to configure them, please view our [RKE2 documentation](https://docs.rke2.io/install/network_options/). - -##### Dual-stack Networking - -[Dual-stack](https://docs.rke2.io/install/network_options/#dual-stack-configuration) networking is supported for all CNI providers. To configure RKE2 in dual-stack mode, set valid IPv4/IPv6 CIDRs for your [Cluster CIDR](#cluster-cidr) and/or [Service CIDR](#service-cidr). - -###### Additional Configuration {#dual-stack-additional-config} - -When using `cilium` or `multus,cilium` as your container network interface provider, ensure the **Enable IPv6 Support** option is also enabled. - -#### Cloud Provider - -You can configure a [Kubernetes cloud provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers). If you want to use dynamically provisioned [volumes and storage]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) in Kubernetes, typically you must select the specific cloud provider in order to use it. For example, if you want to use Amazon EBS, you would need to select the `aws` cloud provider. - ->**Note:** If the cloud provider you want to use is not listed as an option, you will need to use the [config file option](#cluster-config-file) to configure the cloud provider. Please reference [this documentation]({{}}/rke/latest/en/config-options/cloud-providers/) on how to configure the cloud provider. - -#### Default Pod Security Policy - -Choose the default [pod security policy]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/) for the cluster. Please refer to the [RKE2 documentation](https://docs.rke2.io/security/policies/) on the specifications of each available policy. - -#### Worker CIS Profile - -Select a [CIS benchmark]({{}}/rancher/v2.6/en/cis-scans/) to validate the system configuration against. - -#### Project Network Isolation - -If your network provider allows project network isolation, you can choose whether to enable or disable inter-project communication. - -Project network isolation is available if you are using any RKE2 network plugin that supports the enforcement of Kubernetes network policies, such as Canal. - -#### SELinux - -Option to enable or disable [SELinux](https://docs.rke2.io/security/selinux) support. - -#### CoreDNS - -By default, [CoreDNS](https://coredns.io/) is installed as the default DNS provider. If CoreDNS is not installed, an alternate DNS provider must be installed yourself. Refer to the [RKE2 documentation](https://docs.rke2.io/networking/#coredns) for additional CoreDNS configurations. - -#### NGINX Ingress - -If you want to publish your applications in a high-availability configuration, and you're hosting your nodes with a cloud-provider that doesn't have a native load-balancing feature, enable this option to use NGINX Ingress within the cluster. Refer to the [RKE2 documentation](https://docs.rke2.io/networking/#nginx-ingress-controller) for additional configuration options. - -Refer to the [RKE2 documentation](https://docs.rke2.io/networking/#nginx-ingress-controller) for additional configuration options. - -#### Metrics Server - -Option to enable or disable [Metrics Server]({{}}/rke/latest/en/config-options/add-ons/metrics-server/). - -Each cloud provider capable of launching a cluster using RKE2 can collect metrics and monitor for your cluster nodes. Enable this option to view your node metrics from your cloud provider's portal. - -### Add-On Config - -Additional Kubernetes manifests, managed as an [Add-on](https://kubernetes.io/docs/concepts/cluster-administration/addons/), to apply to the cluster on startup. Refer to the [RKE2 documentation](https://docs.rke2.io/helm/#automatically-deploying-manifests-and-helm-charts) for details. - -### Agent Environment Vars - -Option to set environment variables for [Rancher agents](https://rancher.com/docs/rancher/v2.6/en/cluster-provisioning/rke-clusters/rancher-agents/). The environment variables can be set using key value pairs. Refer to the [RKE2 documentation](https://docs.rke2.io/install/install_options/linux_agent_config/) for more details. - -### etcd - -#### Automatic Snapshots - -Option to enable or disable recurring etcd snapshots. If enabled, users have the option to configure the frequency of snapshots. For details, refer to the [RKE2 documentation](https://docs.rke2.io/backup_restore/#creating-snapshots). Note that with RKE2, snapshots are stored on each etcd node. This varies from RKE1 which only stores one snapshot per cluster. - -#### Metrics - -Option to choose whether to expose etcd metrics to the public or only within the cluster. - -### Networking - -#### Cluster CIDR - -IPv4 and/or IPv6 network CIDRs to use for pod IPs (default: 10.42.0.0/16). - -##### Dual-stack Networking - -To configure [dual-stack](https://docs.rke2.io/install/network_options/#dual-stack-configuration) mode, enter a valid IPv4/IPv6 CIDR. For example `10.42.0.0/16,2001:cafe:42:0::/56`. - -[Additional configuration](#dual-stack-additional-config) is required when using `cilium` or `multus,cilium` as your [container network](#container-network) interface provider. - -#### Service CIDR - -IPv4/IPv6 network CIDRs to use for service IPs (default: 10.43.0.0/16). - -##### Dual-stack Networking - -To configure [dual-stack](https://docs.rke2.io/install/network_options/#dual-stack-configuration) mode, enter a valid IPv4/IPv6 CIDR. For example `10.42.0.0/16,2001:cafe:42:0::/56`. - -[Additional configuration](#dual-stack-additional-config) is required when using `cilium ` or `multus,cilium` as your [container network](#container-network) interface provider. - -#### Cluster DNS - -IPv4 Cluster IP for coredns service. Should be in your service-cidr range (default: 10.43.0.10). - -#### Cluster Domain - -Select the domain for the cluster. The default is `cluster.local`. - -#### NodePort Service Port Range - -Option to change the range of ports that can be used for [NodePort services](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport). The default is `30000-32767`. - -#### TLS Alternate Names - -Add additional hostnames or IPv4/IPv6 addresses as Subject Alternative Names on the server TLS cert. - -#### Authorized Cluster Endpoint - -Authorized Cluster Endpoint can be used to directly access the Kubernetes API server, without requiring communication through Rancher. - -This is enabled by default in Rancher-launched Kubernetes clusters, using the IP of the node with the `controlplane` role and the default Kubernetes self signed certificates. - -For more detail on how an authorized cluster endpoint works and why it is used, refer to the [architecture section.]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) - -We recommend using a load balancer with the authorized cluster endpoint. For details, refer to the [recommended architecture section.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#architecture-for-an-authorized-cluster-endpoint) - -### Registries - -Select the image repository to pull Rancher images from. For more details and configuration options, see the [RKE2 documentation](https://docs.rke2.io/install/containerd_registry_configuration/). - -### Upgrade Strategy - -#### Control Plane Concurrency - -Select how many nodes can be upgraded at the same time. Can be a fixed number or percentage. - -#### Worker Concurrency - -Select how many nodes can be upgraded at the same time. Can be a fixed number or percentage. - -#### Drain Nodes (Control Plane) - -Option to remove all pods from the node prior to upgrading. - -#### Drain Nodes (Worker Nodes) - -Option to remove all pods from the node prior to upgrading. - -### Advanced - -Option to set kubelet options for different nodes. For available options, refer to the [Kubernetes documentation](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/). - -# Cluster Config File - -Instead of using the Rancher UI forms to choose Kubernetes options for the cluster, advanced users can create an RKE2 config file. Using a config file allows you to set any of the [options](https://docs.rke2.io/install/install_options/install_options) available in an RKE2 installation. - -To edit an RKE2 config file directly from the Rancher UI, click **Edit as YAML**. diff --git a/versioned_docs/version-2.6/cluster-admin/editing-clusters/syncing/syncing.md b/versioned_docs/version-2.6/cluster-admin/editing-clusters/syncing/syncing.md deleted file mode 100644 index 0280aad9349..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/editing-clusters/syncing/syncing.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Syncing -weight: 10 ---- - -Syncing is the feature for EKS and GKE clusters that causes Rancher to update the clusters' values so they are up to date with their corresponding cluster object in the hosted Kubernetes provider. This enables Rancher to not be the sole owner of a hosted cluster’s state. Its largest limitation is that processing an update from Rancher and another source at the same time or within 5 minutes of one finishing may cause the state from one source to completely overwrite the other. - -### How it works - -There are two fields on the Rancher Cluster object that must be understood to understand how syncing works: - -1. The config object for the cluster, located on the Spec of the Cluster: - - * For EKS, the field is called EKSConfig - * For GKE, the field is called GKEConfig - -2. The UpstreamSpec object - - * For EKS, this is located on the EKSStatus field on the Status of the Cluster. - * For GKE, this is located on the GKEStatus field on the Status of the Cluster. - -The struct types that define these objects can be found in their corresponding operator projects: - - * [eks-operator](https://github.com/rancher/eks-operator/blob/master/pkg/apis/eks.cattle.io/v1/types.go) - * [gke-operator](https://github.com/rancher/gke-operator/blob/master/pkg/apis/gke.cattle.io/v1/types.go) - -All fields with the exception of the cluster name, the location (region or zone), Imported, and the cloud credential reference, are nillable on this Spec object. - -The EKSConfig or GKEConfig represents desired state for its non-nil values. Fields that are non-nil in the config object can be thought of as “managed". When a cluster is created in Rancher, all fields are non-nil and therefore “managed”. When a pre-existing cluster is registered in rancher all nillable fields are nil and are not “managed”. Those fields become managed once their value has been changed by Rancher. - -UpstreamSpec represents the cluster as it is in the hosted Kubernetes provider and is refreshed on an interval of 5 minutes. After the UpstreamSpec has been refreshed, Rancher checks if the cluster has an update in progress. If it is updating, nothing further is done. If it is not currently updating, any “managed” fields on EKSConfig or GKEConfig are overwritten with their corresponding value from the recently updated UpstreamSpec. - -The effective desired state can be thought of as the UpstreamSpec + all non-nil fields in the EKSConfig or GKEConfig. This is what is displayed in the UI. - -If Rancher and another source attempt to update a cluster at the same time or within the 5 minute refresh window of an update finishing, then it is likely any “managed” fields can be caught in a race condition. To use EKS as an example, a cluster may have PrivateAccess as a managed field. If PrivateAccess is false and then enabled in EKS console, then finishes at 11:01, and then tags are updated from Rancher before 11:05 the value will likely be overwritten. This would also occur if tags were updated while the cluster was processing the update. If the cluster was registered and the PrivateAccess fields was nil then this issue should not occur in the aforementioned case. diff --git a/versioned_docs/version-2.6/cluster-admin/nodes/nodes.md b/versioned_docs/version-2.6/cluster-admin/nodes/nodes.md deleted file mode 100644 index 9f2243cceab..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/nodes/nodes.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Nodes and Node Pools -weight: 2030 ---- - -After you launch a Kubernetes cluster in Rancher, you can manage individual nodes from the cluster's **Node** tab. Depending on the [option used]({{}}/rancher/v2.6/en/cluster-provisioning/) to provision the cluster, there are different node options available. - -> If you want to manage the _cluster_ and not individual nodes, see [Editing Clusters]({{< baseurl >}}/rancher/v2.6/en/cluster-admin/editing-clusters). - -This section covers the following topics: - -- [Node options available for each cluster creation option](#node-options-available-for-each-cluster-creation-option) - - [Nodes hosted by an infrastructure provider](#nodes-hosted-by-an-infrastructure-provider) - - [Nodes provisioned by hosted Kubernetes providers](#nodes-provisioned-by-hosted-kubernetes-providers) - - [Registered nodes](#registered-nodes) -- [Managing and editing individual nodes](#managing-and-editing-individual-nodes) -- [Viewing a node in the Rancher API](#viewing-a-node-in-the-rancher-api) -- [Deleting a node](#deleting-a-node) -- [Scaling nodes](#scaling-nodes) -- [SSH into a node hosted by an infrastructure provider](#ssh-into-a-node-hosted-by-an-infrastructure-provider) -- [Cordoning a node](#cordoning-a-node) -- [Draining a node](#draining-a-node) - - [Aggressive and safe draining options](#aggressive-and-safe-draining-options) - - [Grace period](#grace-period) - - [Timeout](#timeout) - - [Drained and cordoned state](#drained-and-cordoned-state) -- [Labeling a node to be ignored by Rancher](#labeling-a-node-to-be-ignored-by-rancher) - -# Node Options Available for Each Cluster Creation Option - -The following table lists which node options are available for each type of cluster in Rancher. Click the links in the **Option** column for more detailed information about each feature. - -| Option | [Nodes Hosted by an Infrastructure Provider][1] | [Custom Node][2] | [Hosted Cluster][3] | [Registered EKS Nodes][4] | [All Other Registered Nodes][5] | Description | -| ------------------------------------------------ | ------------------------------------------------ | ---------------- | ------------------- | ------------------- | -------------------| ------------------------------------------------------------------ | -| [Cordon](#cordoning-a-node) | ✓ | ✓ | ✓ | ✓ | ✓ | Marks the node as unschedulable. | -| [Drain](#draining-a-node) | ✓ | ✓ | ✓ | ✓ | ✓ | Marks the node as unschedulable _and_ evicts all pods. | -| [Edit](#managing-and-editing-individual-nodes) | ✓ | ✓ | ✓ | ✓ | ✓ | Enter a custom name, description, label, or taints for a node. | -| [View API](#viewing-a-node-in-the-rancher-api) | ✓ | ✓ | ✓ | ✓ | ✓ | View API data. | -| [Delete](#deleting-a-node) | ✓ | ✓ | | * | * | Deletes defective nodes from the cluster. | -| [Download Keys](#ssh-into-a-node-hosted-by-an-infrastructure-provider) | ✓ | | | | | Download SSH key in order to SSH into the node. | -| [Node Scaling](#scaling-nodes) | ✓ | | | ✓ | | Scale the number of nodes in the node pool up or down. | - -[1]: {{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ -[2]: {{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/ -[3]: {{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/ -[4]: {{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/ -[5]: {{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/ - -\* Delete option accessible via View API - - -### Nodes Hosted by an Infrastructure Provider - -Node pools are available when you provision Rancher-launched Kubernetes clusters on nodes that are [hosted in an infrastructure provider.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) - -Clusters provisioned using [one of the node pool options]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-pools) can be scaled up or down if the node pool is edited. - -A node pool can also automatically maintain the node scale that's set during the initial cluster provisioning if [node auto-replace is enabled.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#about-node-auto-replace) This scale determines the number of active nodes that Rancher maintains for the cluster. - -Rancher uses [node templates]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) to replace nodes in the node pool. Each node template uses cloud provider credentials to allow Rancher to set up the node in the infrastructure provider. - -### Nodes Provisioned by Hosted Kubernetes Providers - -Options for managing nodes [hosted by a Kubernetes provider]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/) are somewhat limited in Rancher. Rather than using the Rancher UI to make edits such as scaling the number of nodes up or down, edit the cluster directly. - -### Registered Nodes - -Although you can deploy workloads to a [registered cluster]({{< baseurl >}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/) using Rancher, you cannot manage individual cluster nodes. All management of imported cluster nodes must take place outside of Rancher. - -# Managing and Editing Individual Nodes - -Editing a node lets you: - -* Change its name -* Change its description -* Add [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) -* Add/Remove [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) - -To manage individual nodes, browse to the cluster that you want to manage and then select **Nodes** from the main menu. You can open the options menu for a node by clicking its **⋮** icon (**..**.). - -# Viewing a Node in the Rancher API - -Select this option to view the node's [API endpoints]({{< baseurl >}}/rancher/v2.6/en/api/). - -# Deleting a Node - -Use **Delete** to remove defective nodes from the cloud provider. - -When you the delete a defective node, Rancher can automatically replace it with an identically provisioned node if the node is in a node pool and [node auto-replace is enabled.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#about-node-auto-replace) - ->**Tip:** If your cluster is hosted by an infrastructure provider, and you want to scale your cluster down instead of deleting a defective node, [scale down](#scaling-nodes) rather than delete. - -# Scaling Nodes - -For nodes hosted by an infrastructure provider, you can scale the number of nodes in each [node pool]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-pools) by using the scale controls. This option isn't available for other cluster types. - -# SSH into a Node Hosted by an Infrastructure Provider - -For [nodes hosted by an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/), you have the option of downloading its SSH key so that you can connect to it remotely from your desktop. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to SSH into a node and click the name of the cluster. -1. On the **Machine Pools** tab, find the node that you want to remote into and click **⋮ > Download SSH Key**. A ZIP file containing files used for SSH will be downloaded. -1. Extract the ZIP file to any location. -1. Open Terminal. Change your location to the extracted ZIP file. -1. Enter the following command: - - ``` - ssh -i id_rsa root@ - ``` - -# Cordoning a Node - -_Cordoning_ a node marks it as unschedulable. This feature is useful for performing short tasks on the node during small maintenance windows, like reboots, upgrades, or decommissions. When you're done, power back on and make the node schedulable again by uncordoning it. - -# Draining a Node - -_Draining_ is the process of first cordoning the node, and then evicting all its pods. This feature is useful for performing node maintenance (like kernel upgrades or hardware maintenance). It prevents new pods from deploying to the node while redistributing existing pods so that users don't experience service interruption. - -- For pods with a replica set, the pod is replaced by a new pod that will be scheduled to a new node. Additionally, if the pod is part of a service, then clients will automatically be redirected to the new pod. - -- For pods with no replica set, you need to bring up a new copy of the pod, and assuming it is not part of a service, redirect clients to it. - -You can drain nodes that are in either a `cordoned` or `active` state. When you drain a node, the node is cordoned, the nodes are evaluated for conditions they must meet to be drained, and then (if it meets the conditions) the node evicts its pods. - -However, you can override the conditions draining when you initiate the drain. You're also given an opportunity to set a grace period and timeout value. - -### Aggressive and Safe Draining Options - -When you configure the upgrade strategy for the cluster, you will be able to enable node draining. If node draining is enabled, you will be able to configure how pods are deleted and rescheduled. - -- **Aggressive Mode** - - In this mode, pods won't get rescheduled to a new node, even if they do not have a controller. Kubernetes expects you to have your own logic that handles the deletion of these pods. - - Kubernetes also expects the implementation to decide what to do with pods using emptyDir. If a pod uses emptyDir to store local data, you might not be able to safely delete it, since the data in the emptyDir will be deleted once the pod is removed from the node. Choosing aggressive mode will delete these pods. - -- **Safe Mode** - - If a node has standalone pods or ephemeral data it will be cordoned but not drained. -### Grace Period - -The timeout given to each pod for cleaning things up, so they will have chance to exit gracefully. For example, when pods might need to finish any outstanding requests, roll back transactions or save state to some external storage. If negative, the default value specified in the pod will be used. - -### Timeout - -The amount of time drain should continue to wait before giving up. - ->**Kubernetes Known Issue:** The [timeout setting](https://github.com/kubernetes/kubernetes/pull/64378) was not enforced while draining a node before Kubernetes 1.12. - -### Drained and Cordoned State - -If there's any error related to user input, the node enters a `cordoned` state because the drain failed. You can either correct the input and attempt to drain the node again, or you can abort by uncordoning the node. - -If the drain continues without error, the node enters a `draining` state. You'll have the option to stop the drain when the node is in this state, which will stop the drain process and change the node's state to `cordoned`. - -Once drain successfully completes, the node will be in a state of `drained`. You can then power off or delete the node. - ->**Want to know more about cordon and drain?** See the [Kubernetes documentation](https://kubernetes.io/docs/tasks/administer-cluster/cluster-management/#maintenance-on-a-node). - -# Labeling a Node to be Ignored by Rancher - -Some solutions, such as F5's BIG-IP integration, may require creating a node that is never registered to a cluster. - -Since the node will never finish registering, it will always be shown as unhealthy in the Rancher UI. - -In that case, you may want to label the node to be ignored by Rancher so that Rancher only shows nodes as unhealthy when they are actually failing. - -You can label nodes to be ignored by using a setting in the Rancher UI, or by using `kubectl`. - -> **Note:** There is an [open issue](https://github.com/rancher/rancher/issues/24172) in which nodes labeled to be ignored can get stuck in an updating state. - - -### Labeling Nodes to be Ignored with kubectl - -To add a node that will be ignored by Rancher, use `kubectl` to create a node that has the following label: - -``` -cattle.rancher.io/node-status: ignore -``` - -**Result:** If you add the node to a cluster, Rancher will not attempt to sync with this node. The node can still be part of the cluster and can be listed with `kubectl`. - -If the label is added before the node is added to the cluster, the node will not be shown in the Rancher UI. - -If the label is added after the node is added to a Rancher cluster, the node will not be removed from the UI. - -If you delete the node from the Rancher server using the Rancher UI or API, the node will not be removed from the cluster if the `nodeName` is listed in the Rancher settings in the Rancher API under `v3/settings/ignore-node-name`. diff --git a/versioned_docs/version-2.6/cluster-admin/pod-security-policies/pod-security-policies.md b/versioned_docs/version-2.6/cluster-admin/pod-security-policies/pod-security-policies.md deleted file mode 100644 index 4d1b3ca719f..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/pod-security-policies/pod-security-policies.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Assigning Pod Security Policies -weight: 2260 ---- - -_Pod Security Policies_ are objects that control security-sensitive aspects of pod specification (like root privileges). - -## Adding a Default Pod Security Policy - -When you create a new cluster with RKE, you can configure it to apply a PSP immediately. As you create the cluster, use the **Cluster Options** to enable a PSP. The PSP assigned to the cluster will be the default PSP for projects within the cluster. - ->**Prerequisite:** ->Create a Pod Security Policy within Rancher. Before you can assign a default PSP to a new cluster, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/). ->**Note:** ->For security purposes, we recommend assigning a PSP as you create your clusters. - -To enable a default Pod Security Policy, set the **Pod Security Policy Support** option to **Enabled**, and then make a selection from the **Default Pod Security Policy** drop-down. - -When the cluster finishes provisioning, the PSP you selected is applied to all projects within the cluster. diff --git a/versioned_docs/version-2.6/cluster-admin/pod-security-policy/pod-security-policy.md b/versioned_docs/version-2.6/cluster-admin/pod-security-policy/pod-security-policy.md deleted file mode 100644 index 92e320f85e4..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/pod-security-policy/pod-security-policy.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Adding a Pod Security Policy -weight: 80 ---- - -> **Prerequisite:** The options below are available only for clusters that are [launched using RKE.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) - -When your cluster is running pods with security-sensitive configurations, assign it a [pod security policy]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/), which is a set of rules that monitors the conditions and settings in your pods. If a pod doesn't meet the rules specified in your policy, the policy stops it from running. - -You can assign a pod security policy when you provision a cluster. However, if you need to relax or restrict security for your pods later, you can update the policy while editing your cluster. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster to which you want to apply a pod security policy and click **⋮ > Edit Config**. -1. From **Pod Security Policy Support**, select **Enabled**. - - >**Note:** This option is only available for clusters [provisioned by RKE]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/). - -4. From the **Default Pod Security Policy** drop-down, select the policy you want to apply to the cluster. - - Rancher ships with [policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/#default-pod-security-policies) of `restricted` and `unrestricted`, although you can [create custom policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/#default-pod-security-policies) as well. - -5. Click **Save**. - -**Result:** The pod security policy is applied to the cluster and any projects within the cluster. - ->**Note:** Workloads already running before assignment of a pod security policy are grandfathered in. Even if they don't meet your pod security policy, workloads running before assignment of the policy continue to run. -> ->To check if a running workload passes your pod security policy, clone or upgrade it. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/projects-and-namespaces/projects-and-namespaces.md b/versioned_docs/version-2.6/cluster-admin/projects-and-namespaces/projects-and-namespaces.md deleted file mode 100644 index d1ae03863b4..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/projects-and-namespaces/projects-and-namespaces.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Projects and Kubernetes Namespaces with Rancher -description: Rancher Projects ease the administrative burden of your cluster and support multi-tenancy. Learn to create projects and divide projects into Kubernetes namespaces -weight: 2032 ---- - -A namespace is a Kubernetes concept that allows a virtual cluster within a cluster, which is useful for dividing the cluster into separate "virtual clusters" that each have their own access control and resource quotas. - -A project is a group of namespaces, and it is a concept introduced by Rancher. Projects allow you to manage multiple namespaces as a group and perform Kubernetes operations in them. You can use projects to support multi-tenancy, so that a team can access a project within a cluster without having access to other projects in the same cluster. - ->**Note:** As of Rancher v2.6, projects are de-emphasized on the UI because it is no longer required to create any Kubernetes resources within a project scope. However, resources such as [Secrets]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/#creating-secrets-in-projects) can still be created in a project scope if the legacy feature flag is enabled. - -This section describes how projects and namespaces work with Rancher. It covers the following topics: - -- [About namespaces](#about-namespaces) -- [About projects](#about-projects) - - [The cluster's default project](#the-cluster-s-default-project) - - [The system project](#the-system-project) -- [Project authorization](#project-authorization) -- [Pod security policies](#pod-security-policies) -- [Creating projects](#creating-projects) -- [Switching between clusters and projects](#switching-between-clusters-and-projects) - -# About Namespaces - -A namespace is a concept introduced by Kubernetes. According to the [official Kubernetes documentation on namespaces,](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) - -> Kubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called namespaces. [...] Namespaces are intended for use in environments with many users spread across multiple teams, or projects. For clusters with a few to tens of users, you should not need to create or think about namespaces at all. - -Namespaces provide the following functionality: - -- **Providing a scope for names:** Names of resources need to be unique within a namespace, but not across namespaces. Namespaces can not be nested inside one another and each Kubernetes resource can only be in one namespace. -- **Resource quotas:** Namespaces provide a way to divide cluster resources between multiple users. - -You can assign resources at the project level so that each namespace in the project can use them. You can also bypass this inheritance by assigning resources explicitly to a namespace. - -You can assign the following resources directly to namespaces: - -- [Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/) -- [Load Balancers/Ingress]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/) -- [Service Discovery Records]({{}}/rancher/v2.6/en/k8s-in-rancher/service-discovery/) -- [Persistent Volume Claims]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) -- [Certificates]({{}}/rancher/v2.6/en/k8s-in-rancher/certificates/) -- [ConfigMaps]({{}}/rancher/v2.6/en/k8s-in-rancher/configmaps/) -- [Registries]({{}}/rancher/v2.6/en/k8s-in-rancher/registries/) -- [Secrets]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/) - -To manage permissions in a vanilla Kubernetes cluster, cluster admins configure role-based access policies for each namespace. With Rancher, user permissions are assigned on the project level instead, and permissions are automatically inherited by any namespace owned by the particular project. - -For more information on creating and moving namespaces, see [Namespaces]({{}}/rancher/v2.6/en/project-admin/namespaces/). - -### Role-based access control issues with namespaces and kubectl - -Because projects are a concept introduced by Rancher, kubectl does not have the capability to restrict the creation of namespaces to a project the creator has access to. - -This means that when standard users with project-scoped permissions create a namespaces with `kubectl`, it may be unusable because `kubectl` doesn't require the new namespace to be scoped within a certain project. - -If your permissions are restricted to the project level, it is better to [create a namespace through Rancher]({{}}/rancher/v2.6/en/project-admin/namespaces/) to ensure that you will have permission to access the namespace. - -If a standard user is a project owner, the user will be able to create namespaces within that project. The Rancher UI will prevent that user from creating namespaces outside the scope of the projects they have access to. - -# About Projects - -In terms of hierarchy: - -- Clusters contain projects -- Projects contain namespaces - -You can use projects to support multi-tenancy, so that a team can access a project within a cluster without having access to other projects in the same cluster. - -In the base version of Kubernetes, features like role-based access rights or cluster resources are assigned to individual namespaces. A project allows you to save time by giving an individual or a team access to multiple namespaces simultaneously. - -You can use projects to perform actions such as: - -- Assign users to a group of namespaces (i.e., [project membership]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles)). -- Assign users specific roles in a project. A role can be owner, member, read-only, or [custom]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles/). -- Assign resources to the project. -- Assign Pod Security Policies. - -When you create a cluster, two projects are automatically created within it: - -- [Default Project](#the-cluster-s-default-project) -- [System Project](#the-system-project) - -### The Cluster's Default Project - -When you provision a cluster with Rancher, it automatically creates a `default` project for the cluster. This is a project you can use to get started with your cluster, but you can always delete it and replace it with projects that have more descriptive names. - -If you don't have a need for more than the default namespace, you also do not need more than the **Default** project in Rancher. - -If you require another level of organization beyond the **Default** project, you can create more projects in Rancher to isolate namespaces, applications and resources. - -### The System Project - -When troubleshooting, you can view the `system` project to check if important namespaces in the Kubernetes system are working properly. This easily accessible project saves you from troubleshooting individual system namespace containers. - -To open it, open the cluster view and click **Cluster > Projects/Namespaces**. This view shows all of the namespaces in the `system` project. - -The `system` project: - -- Is automatically created when you provision a cluster. -- Lists all namespaces that exist in `v3/settings/system-namespaces`, if they exist. -- Allows you to add more namespaces or move its namespaces to other projects. -- Cannot be deleted because it's required for cluster operations. - ->**Note:** In RKE clusters where the project network isolation option is enabled, the `system` project overrides the project network isolation option so that it can communicate with other projects, collect logs, and check health. - -# Project Authorization - -Standard users are only authorized for project access in two situations: - -- An administrator, cluster owner or cluster member explicitly adds the standard user to the project's **Members** tab. -- Standard users can access projects that they create themselves. - -# Pod Security Policies - -Rancher extends Kubernetes to allow the application of [Pod Security Policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/) at the project level in addition to the cluster level. However, as a best practice, we recommend applying Pod Security Policies at the cluster level. - -# Creating Projects - -This section describes how to create a new project with a name and with optional pod security policy, members, and resource quotas. - -1. [Name a new project.](#1-name-a-new-project) -2. [Optional: Select a pod security policy.](#2-optional-select-a-pod-security-policy) -3. [Recommended: Add project members.](#3-recommended-add-project-members) -4. [Optional: Add resource quotas.](#4-optional-add-resource-quotas) - -### 1. Name a New Project - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster you want to project in and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Click **Create Project**. -1. Enter a **Project Name**. - -### 2. Optional: Select a Pod Security Policy - -This option is only available if you've already created a Pod Security Policy. For instruction, see [Creating Pod Security Policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/). - -Assigning a PSP to a project will: - -- Override the cluster's default PSP. -- Apply the PSP to the project. -- Apply the PSP to any namespaces you add to the project later. - -### 3. Recommended: Add Project Members - -Use the **Members** section to provide other users with project access and roles. - -By default, your user is added as the project `Owner`. - ->**Notes on Permissions:** -> ->- Users assigned the `Owner` or `Member` role for a project automatically inherit the `namespace creation` role. However, this role is a [Kubernetes ClusterRole](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole), meaning its scope extends to all projects in the cluster. Therefore, users explicitly assigned the `Owner` or `Member` role for a project can create namespaces in other projects they're assigned to, even with only the `Read Only` role assigned. -> ->- By default, the Rancher role of `project-member` inherits from the `Kubernetes-edit` role, and the `project-owner` role inherits from the `Kubernetes-admin` role. As such, both `project-member` and `project-owner` roles will allow for namespace management, including the ability to create and delete namespaces. -> ->- Choose `Custom` to create a custom role on the fly: [Custom Project Roles]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#custom-project-roles). - -To add members: - -1. In the **Members** tab, click **Add**. -1. From the **Select Member** field, search for a user or group that you want to assign project access. Note: You can only search for groups if external authentication is enabled. -1. In the **Project Permissions** section, choose a role. For more information, refer to the [documentation on project roles.]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/) - -### 4. Optional: Add Resource Quotas - -Resource quotas limit the resources that a project (and its namespaces) can consume. For more information, see [Resource Quotas]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/). - -To add a resource quota, - -1. In the **Resource Quotas** tab, click **Add Resource**. -1. Select a **Resource Type**. For more information, see [Resource Quotas.]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/). -1. Enter values for the **Project Limit** and the **Namespace Default Limit**. -1. **Optional:** Specify **Container Default Resource Limit**, which will be applied to every container started in the project. The parameter is recommended if you have CPU or Memory limits set by the Resource Quota. It can be overridden on per an individual namespace or a container level. For more information, see [Container Default Resource Limit]({{}}/rancher/v2.6/en/project-admin/resource-quotas/) -1. Click **Create**. - -**Result:** Your project is created. You can view it from the cluster's **Projects/Namespaces** view. - -| Field | Description | -| ----------------------- | -------------------------------------------------------------------------------------------------------- | -| Project Limit | The overall resource limit for the project. | -| Namespace Default Limit | The default resource limit available for each namespace. This limit is propagated to each namespace in the project when created. The combined limit of all project namespaces shouldn't exceed the project limit. | \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/restoring-etcd/restoring-etcd.md b/versioned_docs/version-2.6/cluster-admin/restoring-etcd/restoring-etcd.md deleted file mode 100644 index 099fa8295f3..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/restoring-etcd/restoring-etcd.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Restoring a Cluster from Backup -weight: 2050 ---- - -etcd backup and recovery for [Rancher launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) can be easily performed. Snapshots of the etcd database are taken and saved either locally onto the etcd nodes or to a S3 compatible target. The advantages of configuring S3 is that if all etcd nodes are lost, your snapshot is saved remotely and can be used to restore the cluster. - -Rancher recommends enabling the [ability to set up recurring snapshots of etcd]({{}}/rancher/v2.6/en/cluster-admin/backing-up-etcd/#configuring-recurring-snapshots), but [one-time snapshots]({{}}/rancher/v2.6/en/cluster-admin/backing-up-etcd/#one-time-snapshots) can easily be taken as well. Rancher allows restore from [saved snapshots](#restoring-a-cluster-from-a-snapshot) or if you don't have any snapshots, you can still [restore etcd](#recovering-etcd-without-a-snapshot). - -Clusters can also be restored to a prior Kubernetes version and cluster configuration. - -This section covers the following topics: - -- [Viewing Available Snapshots](#viewing-available-snapshots) -- [Restoring a Cluster from a Snapshot](#restoring-a-cluster-from-a-snapshot) -- [Recovering etcd without a Snapshot](#recovering-etcd-without-a-snapshot) -- [Enabling snapshot features for clusters created before Rancher v2.2.0](#enabling-snapshot-features-for-clusters-created-before-rancher-v2-2-0) - -## Viewing Available Snapshots - -The list of all available snapshots for the cluster is available. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the **Clusters** page, go to the cluster where you want to view the snapshots and click the name of the cluster. -1. Click the **Snapshots** tab. The listed snapshots include a timestamp of when they were created. - -## Restoring a Cluster from a Snapshot - -If your Kubernetes cluster is broken, you can restore the cluster from a snapshot. - -Snapshots are composed of the cluster data in etcd, the Kubernetes version, and the cluster configuration in the `cluster.yml.` These components allow you to select from the following options when restoring a cluster from a snapshot: - -- **Restore just the etcd contents:** This restore is similar to restoring to snapshots in Rancher before v2.4.0. -- **Restore etcd and Kubernetes version:** This option should be used if a Kubernetes upgrade is the reason that your cluster is failing, and you haven't made any cluster configuration changes. -- **Restore etcd, Kubernetes versions and cluster configuration:** This option should be used if you changed both the Kubernetes version and cluster configuration when upgrading. - -When rolling back to a prior Kubernetes version, the [upgrade strategy options]({{}}/rancher/v2.6/en/cluster-admin/upgrading-kubernetes/#configuring-the-upgrade-strategy) are ignored. Worker nodes are not cordoned or drained before being reverted to the older Kubernetes version, so that an unhealthy cluster can be more quickly restored to a healthy state. - -> **Prerequisite:** To restore snapshots from S3, the cluster needs to be configured to [take recurring snapshots on S3.]({{}}/rancher/v2.6/en/cluster-admin/backing-up-etcd/#configuring-recurring-snapshots) - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the **Clusters** page, go to the cluster where you want to view the snapshots and click the name of the cluster. -1. Click the **Snapshots** tab to view the list of saved snapshots. -1. Go to the snapshot you want to restore and click **⋮ > Restore Snapshot**. -1. Click **Restore**. - -**Result:** The cluster will go into `updating` state and the process of restoring the `etcd` nodes from the snapshot will start. The cluster is restored when it returns to an `active` state. - -## Recovering etcd without a Snapshot - -If the group of etcd nodes loses quorum, the Kubernetes cluster will report a failure because no operations, e.g. deploying workloads, can be executed in the Kubernetes cluster. The cluster should have three etcd nodes to prevent a loss of quorum. If you want to recover your set of etcd nodes, follow these instructions: - -1. Keep only one etcd node in the cluster by removing all other etcd nodes. - -2. On the single remaining etcd node, run the following command: - - ``` - $ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike etcd - ``` - - This command outputs the running command for etcd, save this command to use later. - -3. Stop the etcd container that you launched in the previous step and rename it to `etcd-old`. - - ``` - $ docker stop etcd - $ docker rename etcd etcd-old - ``` - -4. Take the saved command from Step 2 and revise it: - - - If you originally had more than 1 etcd node, then you need to change `--initial-cluster` to only contain the node that remains. - - Add `--force-new-cluster` to the end of the command. - -5. Run the revised command. - -6. After the single nodes is up and running, Rancher recommends adding additional etcd nodes to your cluster. If you have a [custom cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes) and you want to reuse an old node, you are required to [clean up the nodes]({{}}/rancher/v2.6/en/cluster-admin/cleaning-cluster-nodes/) before attempting to add them back into a cluster. - -# Enabling Snapshot Features for Clusters Created Before Rancher v2.2.0 - -If you have any Rancher launched Kubernetes clusters that were created before v2.2.0, after upgrading Rancher, you must [edit the cluster]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/) and _save_ it, in order to enable the updated snapshot features. Even if you were already creating snapshots before v2.2.0, you must do this step as the older snapshots will not be available to use to [back up and restore etcd through the UI]({{}}/rancher/v2.6/en/cluster-admin/restoring-etcd/). diff --git a/versioned_docs/version-2.6/cluster-admin/tools/tools.md b/versioned_docs/version-2.6/cluster-admin/tools/tools.md deleted file mode 100644 index d502eefc441..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/tools/tools.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Tools for Logging, Monitoring, and Visibility -weight: 2033 ---- - -Rancher contains a variety of tools that aren't included in Kubernetes to assist in your DevOps operations. Rancher can integrate with external services to help your clusters run more efficiently. Tools are divided into following categories: - - - -- [Logging](#logging) -- [Monitoring and Alerts](#monitoring-and-alerts) -- [Istio](#istio) -- [OPA Gatekeeper](#opa-gatekeeper) -- [CIS Scans](#cis-scans) - - - - -# Logging - -Logging is helpful because it allows you to: - -- Capture and analyze the state of your cluster -- Look for trends in your environment -- Save your logs to a safe location outside of your cluster -- Stay informed of events like a container crashing, a pod eviction, or a node dying -- More easily debugg and troubleshoot problems - -Rancher can integrate with Elasticsearch, splunk, kafka, syslog, and fluentd. - -For more information, refer to the logging documentation [here.]({{}}/rancher/v2.6/en/logging/) -# Monitoring and Alerts - -Using Rancher, you can monitor the state and processes of your cluster nodes, Kubernetes components, and software deployments through integration with [Prometheus](https://prometheus.io/), a leading open-source monitoring solution. - -After monitoring is enabled, you can set up alerts and notifiers that provide the mechanism to receive them. - -Notifiers are services that inform you of alert events. You can configure notifiers to send alert notifications to staff best suited to take corrective action. Notifications can be sent with Slack, email, PagerDuty, WeChat, and webhooks. - -Alerts are rules that trigger those notifications. Before you can receive alerts, you must configure one or more notifier in Rancher. The scope for alerts can be set at either the cluster or project level. - -For more information, refer to the monitoring documentation [here.]({{}}/rancher/v2.6/en/monitoring-alerting/) - -# Istio - -[Istio](https://istio.io/) is an open-source tool that makes it easier for DevOps teams to observe, control, troubleshoot, and secure the traffic within a complex network of microservices. - -Rancher's integration with Istio was improved in Rancher v2.5. - -For more information, refer to the Istio documentation [here.]({{}}/rancher/v2.6/en/istio) -# OPA Gatekeeper - -[OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper) is an open-source project that provides integration between OPA and Kubernetes to provide policy control via admission controller webhooks. For details on how to enable Gatekeeper in Rancher, refer to the [OPA Gatekeeper section.]({{}}/rancher/v2.6/en/opa-gatekeper) - -# CIS Scans - -Rancher can run a security scan to check whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark. - -For more information, refer to the CIS scan documentation [here.]({{}}/rancher/v2.6/en/cis-scans) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/upgrading-kubernetes/upgrading-kubernetes.md b/versioned_docs/version-2.6/cluster-admin/upgrading-kubernetes/upgrading-kubernetes.md deleted file mode 100644 index 03e871e5b08..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/upgrading-kubernetes/upgrading-kubernetes.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -title: Upgrading and Rolling Back Kubernetes -weight: 70 ---- - -Following an upgrade to the latest version of Rancher, downstream Kubernetes clusters can be upgraded to use the latest supported version of Kubernetes. - -Rancher calls RKE (Rancher Kubernetes Engine) as a library when provisioning and editing RKE clusters. For more information on configuring the upgrade strategy for RKE clusters, refer to the [RKE documentation]({{}}/rke/latest/en/). - -This section covers the following topics: - -- [New Features](#new-features) -- [Tested Kubernetes Versions](#tested-kubernetes-versions) -- [How Upgrades Work](#how-upgrades-work) -- [Recommended Best Practice for Upgrades](#recommended-best-practice-for-upgrades) -- [Upgrading the Kubernetes Version](#upgrading-the-kubernetes-version) -- [Rolling Back](#rolling-back) -- [Configuring the Upgrade Strategy](#configuring-the-upgrade-strategy) - - [Configuring the Maximum Unavailable Worker Nodes in the Rancher UI](#configuring-the-maximum-unavailable-worker-nodes-in-the-rancher-ui) - - [Enabling Draining Nodes During Upgrades from the Rancher UI](#enabling-draining-nodes-during-upgrades-from-the-rancher-ui) - - [Maintaining Availability for Applications During Upgrades](#maintaining-availability-for-applications-during-upgrades) - - [Configuring the Upgrade Strategy in the cluster.yml](#configuring-the-upgrade-strategy-in-the-cluster-yml) -- [Troubleshooting](#troubleshooting) - -# Tested Kubernetes Versions - -Before a new version of Rancher is released, it's tested with the latest minor versions of Kubernetes to ensure compatibility. For details on which versions of Kubernetes were tested on each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.6.0/) - -# How Upgrades Work - -RKE v1.1.0 changed the way that clusters are upgraded. - -In this section of the [RKE documentation,]({{}}/rke/latest/en/upgrades/how-upgrades-work) you'll learn what happens when you edit or upgrade your RKE Kubernetes cluster. - - -# Recommended Best Practice for Upgrades - -When upgrading the Kubernetes version of a cluster, we recommend that you: - -1. Take a snapshot. -1. Initiate a Kubernetes upgrade. -1. If the upgrade fails, revert the cluster to the pre-upgrade Kubernetes version. This is achieved by selecting the **Restore etcd and Kubernetes version** option. This will return your cluster to the pre-upgrade kubernetes version before restoring the etcd snapshot. - -The restore operation will work on a cluster that is not in a healthy or active state. - -# Upgrading the Kubernetes Version - -> **Prerequisites:** -> -> - The options below are available only for [Rancher-launched RKE Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) and [Registered K3s Kubernetes clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/#additional-features-for-registered-k3s-clusters) -> - Before upgrading Kubernetes, [back up your cluster.]({{}}/rancher/v2.6/en/backups) - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster you want to upgrade and click **⋮ > Edit Config**. -1. From the **Kubernetes Version** drop-down, choose the version of Kubernetes that you want to use for the cluster. -1. Click **Save**. - -**Result:** Kubernetes begins upgrading for the cluster. - -# Rolling Back - -A cluster can be restored to a backup in which the previous Kubernetes version was used. For more information, refer to the following sections: - -- [Backing up a cluster]({{}}/rancher/v2.6/en/cluster-admin/backing-up-etcd/#how-snapshots-work) -- [Restoring a cluster from backup]({{}}/rancher/v2.6/en/cluster-admin/restoring-etcd/#restoring-a-cluster-from-a-snapshot) - -# Configuring the Upgrade Strategy - -As of RKE v1.1.0, additional upgrade options became available to give you more granular control over the upgrade process. These options can be used to maintain availability of your applications during a cluster upgrade if certain [conditions and requirements]({{}}/rke/latest/en/upgrades/maintaining-availability) are met. - -The upgrade strategy can be configured in the Rancher UI, or by editing the `cluster.yml`. More advanced options are available by editing the `cluster.yml`. - -### Configuring the Maximum Unavailable Worker Nodes in the Rancher UI - -From the Rancher UI, the maximum number of unavailable worker nodes can be configured. During a cluster upgrade, worker nodes will be upgraded in batches of this size. - -By default, the maximum number of unavailable worker is defined as 10 percent of all worker nodes. This number can be configured as a percentage or as an integer. When defined as a percentage, the batch size is rounded down to the nearest node, with a minimum of one node. - -To change the default number or percentage of worker nodes, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster you want to upgrade and click **⋮ > Edit Config**. -1. In the **Upgrade Strategy** tab, enter the **Worker Concurrency** as a fixed number or percentage. To get this number, you can take the number of nodes in your cluster and subtract the max unavailable nodes. -1. Click **Save**. - -**Result:** The cluster is updated to use the new upgrade strategy. - -### Enabling Draining Nodes During Upgrades from the Rancher UI - -By default, RKE [cordons](https://kubernetes.io/docs/concepts/architecture/nodes/#manual-node-administration) each node before upgrading it. [Draining](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) is disabled during upgrades by default. If draining is enabled in the cluster configuration, RKE will both cordon and drain the node before it is upgraded. - -To enable draining each node during a cluster upgrade, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster you want to enable node draining and click **⋮ > Edit Config**. -1. Click **⋮ > Edit**. -1. In the **Upgrade Strategy** tab, go to the **Drain nodes** field and click **Yes**. Node draining is configured separately for control plane and worker nodes. -1. Configure the options for how pods are deleted. For more information about each option, refer to [this section.]({{}}/rancher/v2.6/en/cluster-admin/nodes/#aggressive-and-safe-draining-options) -1. Optionally, configure a grace period. The grace period is the timeout given to each pod for cleaning things up, so they will have chance to exit gracefully. Pods might need to finish any outstanding requests, roll back transactions or save state to some external storage. If this value is negative, the default value specified in the pod will be used. -1. Optionally, configure a timeout, which is the amount of time the drain should continue to wait before giving up. -1. Click **Save**. - -**Result:** The cluster is updated to use the new upgrade strategy. - -> **Note:** As of Rancher v2.4.0, there is a [known issue](https://github.com/rancher/rancher/issues/25478) in which the Rancher UI doesn't show state of etcd and controlplane as drained, even though they are being drained. - -### Maintaining Availability for Applications During Upgrades - -_Available as of RKE v1.1.0_ - -In [this section of the RKE documentation,]({{}}/rke/latest/en/upgrades/maintaining-availability/) you'll learn the requirements to prevent downtime for your applications when upgrading the cluster. - -### Configuring the Upgrade Strategy in the cluster.yml - -More advanced upgrade strategy configuration options are available by editing the `cluster.yml`. - -For details, refer to [Configuring the Upgrade Strategy]({{}}/rke/latest/en/upgrades/configuring-strategy) in the RKE documentation. The section also includes an example `cluster.yml` for configuring the upgrade strategy. - -# Troubleshooting - -If a node doesn't come up after an upgrade, the `rke up` command errors out. - -No upgrade will proceed if the number of unavailable nodes exceeds the configured maximum. - -If an upgrade stops, you may need to fix an unavailable node or remove it from the cluster before the upgrade can continue. - -A failed node could be in many different states: - -- Powered off -- Unavailable -- User drains a node while upgrade is in process, so there are no kubelets on the node -- The upgrade itself failed - -If the max unavailable number of nodes is reached during an upgrade, Rancher user clusters will be stuck in updating state and not move forward with upgrading any other control plane nodes. It will continue to evaluate the set of unavailable nodes in case one of the nodes becomes available. If the node cannot be fixed, you must remove the node in order to continue the upgrade. diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/attaching-existing-storage/attaching-existing-storage.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/attaching-existing-storage/attaching-existing-storage.md deleted file mode 100644 index c129077e4dd..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/attaching-existing-storage/attaching-existing-storage.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Setting up Existing Storage -weight: 1 ---- - -This section describes how to set up existing persistent storage for workloads in Rancher. - -> This section assumes that you understand the Kubernetes concepts of persistent volumes and persistent volume claims. For more information, refer to the section on [how storage works.](../how-storage-works) - -To set up storage, follow these steps: - -1. [Set up persistent storage.](#1-set-up-persistent-storage) -2. [Add a PersistentVolume that refers to the persistent storage.](#2-add-a-persistentvolume-that-refers-to-the-persistent-storage) -3. [Use the PersistentVolume for Pods Deployed with a StatefulSet.](#3-use-the-persistentvolume-for-pods-deployed-with-a-statefulset) - -### Prerequisites - -- To create a persistent volume as a Kubernetes resource, you must have the `Manage Volumes` [role.]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-role-reference) -- If you are provisioning storage for a cluster hosted in the cloud, the storage and cluster hosts must have the same cloud provider. - -### 1. Set up persistent storage - -Creating a persistent volume in Rancher will not create a storage volume. It only creates a Kubernetes resource that maps to an existing volume. Therefore, before you can create a persistent volume as a Kubernetes resource, you must have storage provisioned. - -The steps to set up a persistent storage device will differ based on your infrastructure. We provide examples of how to set up storage using [vSphere,](../examples/vsphere) [NFS,](../examples/nfs) or Amazon's [EBS.](../examples/ebs) - -If you have a pool of block storage, and you don't want to use a cloud provider, Longhorn could help you provide persistent storage to your Kubernetes cluster. For more information, see [this page.]({{}}/rancher/v2.6/en/longhorn) - -### 2. Add a PersistentVolume that refers to the persistent storage - -These steps describe how to set up a PersistentVolume at the cluster level in Kubernetes. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to add a persistent volume and click **Explore**. -1. In the left navigation bar, click **Storage > Persistent Volumes**. -1. Click **Create**. -1. Enter a **Name** for the persistent volume. -1. Select the **Volume Plugin** for the disk type or service that you're using. When adding storage to a cluster that's hosted by a cloud provider, use the cloud provider's plug-in for cloud storage. For example, if you have a Amazon EC2 cluster and you want to use cloud storage for it, you must use the `Amazon EBS Disk` volume plugin. -1. Enter the **Capacity** of your volume in gigabytes. -1. Complete the **Plugin Configuration** form. Each plugin type requires information specific to the vendor of disk type. For help regarding each plugin's form and the information that's required, refer to the plug-in's vendor documentation. -1. Optional: In the **Customize** form, configure the [access modes.](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) This options sets how many nodes can access the volume, along with the node read/write permissions. The [Kubernetes Documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) includes a table that lists which access modes are supported by the plugins available. -1. Optional: In the **Customize** form, configure the [mount options.](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#mount-options) Each volume plugin allows you to specify additional command line options during the mounting process. Consult each plugin's vendor documentation for the mount options available. -1. Click **Create**. - -**Result:** Your new persistent volume is created. - - -### 3. Use the Storage Class for Pods Deployed with a StatefulSet - -StatefulSets manage the deployment and scaling of Pods while maintaining a sticky identity for each Pod. In this StatefulSet, we will configure a VolumeClaimTemplate. Each Pod managed by the StatefulSet will be deployed with a PersistentVolumeClaim based on this VolumeClaimTemplate. The PersistentVolumeClaim will refer to the PersistentVolume that we created. Therefore, when each Pod managed by the StatefulSet is deployed, it will be bound a PersistentVolume as defined in its PersistentVolumeClaim. - -You can configure storage for the StatefulSet during or after workload creation. - -The following steps describe how to assign existing storage to a new StatefulSet: - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure storage for the StatefulSet and click **Explore**. -1. In the left navigation bar, click **Workload > StatefulSets**. -1. Click **Create**. -1. Choose the namespace where the workload will be deployed. -1. Enter a name for the StatefulSet. -1. On the **Volume Claim Templates** tab, click **Add Claim Template**. -1. Click **Use an existing Persistent Volume**. -1. In the Persistent Volumes field, select the Persistent Volume that you created. -1. In the **Mount Point** field, enter the path that the workload will use to access the volume. -1. Click **Launch**. - -**Result:** When the workload is deployed, it will make a request for the specified amount of disk space to the Kubernetes master. If a PV with the specified resources is available when the workload is deployed, the Kubernetes master will bind the PV to the PVC. - -The following steps describe how to assign persistent storage to an existing workload: - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure storage for the StatefulSet and click **Explore**. -1. In the left navigation bar, click **Workload > StatefulSets**. -1. Go to the workload that you want to add the persistent storage to. Click **⋮ > Edit**. -1. On the **Volume Claim Templates** tab, click **Add Claim Template**. -1. Click **Use an existing Persistent Volume**. -1. In the Persistent Volumes field, select the Persistent Volume that you created. -1. In the **Mount Point** field, enter the path that the workload will use to access the volume. -1. Click **Launch**. - -**Result:** The workload will make a request for the specified amount of disk space to the Kubernetes master. If a PV with the specified resources is available when the workload is deployed, the Kubernetes master will bind the PV to the PVC. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/ceph/ceph.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/ceph/ceph.md deleted file mode 100644 index c7b633e5b2f..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/ceph/ceph.md +++ /dev/null @@ -1,433 +0,0 @@ ---- -title: Using an External Ceph Driver -weight: 10 ---- - -These instructions are about using the external Ceph driver in an RKE2 cluster. If you are using RKE, additional steps are required. For details, refer to [this section.](#using-the-ceph-driver-with-rke) - -- [Requirements](#requirements) -- [Using the Ceph Driver with RKE](#using-the-ceph-driver-with-rke) -- [Installing the ceph-csi driver on an RKE2 cluster](#installing-the-ceph-csi-driver-on-an-rke2-cluster) -- [Install the ceph-csi driver using Helm](#install-the-ceph-csi-driver-using-helm) -- [Creating RBD Ceph Resources](#creating-rbd-ceph-resources) -- [Configure RBD Ceph Access Secrets](#configure-rbd-ceph-access-secrets) - - [User Account](#user-account) - - [Admin Account](#admin-account) -- [Create RBD Testing Resources](#create-rbd-testing-resources) - - [Using RBD in Pods](#using-rbd-in-pods) - - [Using RBD in Persistent Volumes](#using-rbd-in-persistent-volumes) - - [Using RBD in Storage Classes](#using-rbd-in-storage-classes) - - [RKE2 Server/Master Provisioning](#rke2-server-master-provisioning) - - [RKE2 Agent/Worker provisioning](#rke2-agent-worker-provisioning) -- [Tested Versions](#tested-versions) -- [Troubleshooting](#troubleshooting) - -# Requirements - -Make sure ceph-common and xfsprogs packages are installed on SLE worker nodes. - -# Using the Ceph Driver with RKE - -The resources below are fully compatible with RKE based clusters, but there is a need to do an additional kubelet configuration for RKE. - -On RKE clusters, the kubelet component is running in a Docker container and doesn't have access to the host's kernel modules as rbd and libceph by default. - -To solve this limitation, you can either run `modprobe rbd` on worker nodes, or configure the kubelet containers to automatically mount the `/lib/modules` directory from the host into the container. - -For the kubelet configuration, put the following lines into the `cluster.yml` file prior to RKE cluster provisioning. You can also modify the `cluster.yml` later in the Rancher UI by clicking on **Edit Cluster > Edit as YAML** and restarting the worker nodes. - -```yaml -services: - kubelet: - extra_binds: - - '/lib/modules:/lib/modules:ro' -``` - -For more information about the `extra_binds` directive, refer to [this section.]({{}}/rke/latest/en/config-options/services/services-extras/#extra-binds) - -# Installing the ceph-csi driver on an RKE2 cluster - -> **Note:** These steps are needed for dynamic RBD provisioning only. - -For more information about the `ceph-csi-rbd` chart, refer to [this page.](https://github.com/ceph/ceph-csi/blob/devel/charts/ceph-csi-rbd/README.md) - -To get details about your SES cluster, run: - -``` -ceph mon dump -``` - -Read its output: - -``` -dumped monmap epoch 3 -epoch 3 -fsid 79179d9d-98d8-4976-ab2e-58635caa7235 -last_changed 2021-02-11T10:56:42.110184+0000 -created 2021-02-11T10:56:22.913321+0000 -min_mon_release 15 (octopus) -0: [v2:10.85.8.118:3300/0,v1:10.85.8.118:6789/0] mon.a -1: [v2:10.85.8.123:3300/0,v1:10.85.8.123:6789/0] mon.b -2: [v2:10.85.8.124:3300/0,v1:10.85.8.124:6789/0] mon.c -``` - -Later you'll need the fsid and mon addresses values. - -# Install the ceph-csi Driver Using Helm - -Run these commands: - -``` -helm repo add ceph-csi https://ceph.github.io/csi-charts -helm repo update -helm search repo ceph-csi -l -helm inspect values ceph-csi/ceph-csi-rbd > ceph-csi-rbd-values.yaml -``` - -Modify the `ceph-csi-rbd-values.yaml` file and keep there only the required changes: - -```yaml -# ceph-csi-rbd-values.yaml -csiConfig: - - clusterID: "79179d9d-98d8-4976-ab2e-58635caa7235" - monitors: - - "10.85.8.118:6789" - - "10.85.8.123:6789" - - "10.85.8.124:6789" -provisioner: - name: provisioner - replicaCount: 2 -``` - -Make sure the ceph monitors are reachable from the RKE2 cluster, for example, by ping. - -``` -kubectl create namespace ceph-csi-rbd -helm install --namespace ceph-csi-rbd ceph-csi-rbd ceph-csi/ceph-csi-rbd --values ceph-csi-rbd-values.yaml -kubectl rollout status deployment ceph-csi-rbd-provisioner -n ceph-csi-rbd -helm status ceph-csi-rbd -n ceph-csi-rbd -``` - -in case you'd like to modify the configuration directly via Helm, you may adapt the `ceph-csi-rbd-values.yaml` file and call: - -``` -helm upgrade \ - --namespace ceph-csi-rbd ceph-csi-rbd ceph-csi/ceph-csi-rbd --values ceph-csi-rbd-values.yaml -``` - -# Creating RBD Ceph Resources - -``` -# Create a ceph pool: -ceph osd pool create myPool 64 64 - -# Create a block device pool: -rbd pool init myPool - -# Create a block device image: -rbd create -s 2G myPool/image - -# Create a block device user and record the key: -ceph auth get-or-create-key client.myPoolUser mon "allow r" osd "allow class-read object_prefix rbd_children, allow rwx pool=myPool" | tr -d '\n' | base64 -QVFDZ0R5VmdyRk9KREJBQTJ5b2s5R1E2NUdSWExRQndhVVBwWXc9PQ== - -# Encode the ceph user myPoolUser into a bash64 hash: -echo "myPoolUser" | tr -d '\n' | base64 -bXlQb29sVXNlcg== - -# Create a block device admin user and record the key: -ceph auth get-or-create-key client.myPoolAdmin mds 'allow *' mgr 'allow *' mon 'allow *' osd 'allow * pool=myPool' | tr -d '\n' | base64 -QVFCK0hDVmdXSjQ1T0JBQXBrc0VtcVhlZFpjc0JwaStIcmU5M3c9PQ== - -# Encode the ceph user myPoolAdmin into a bash64 hash: -echo "myPoolAdmin" | tr -d '\n' | base64 -bXlQb29sQWRtaW4= -``` -# Configure RBD Ceph Access Secrets - -### User Account - -For static RBD provisioning (the image within the ceph pool must exist), run these commands: - -``` -cat > ceph-user-secret.yaml << EOF -apiVersion: v1 -kind: Secret -metadata: - name: ceph-user - namespace: default -type: kubernetes.io/rbd -data: - userID: bXlQb29sVXNlcg== - userKey: QVFDZ0R5VmdyRk9KREJBQTJ5b2s5R1E2NUdSWExRQndhVVBwWXc9PQ== -EOF - -kubectl apply -f ceph-user-secret.yaml -``` - -### Admin Account - -For dynamic RBD provisioning (used for automatic image creation within a given ceph pool), run these commands: - -``` -cat > ceph-admin-secret.yaml << EOF -apiVersion: v1 -kind: Secret -metadata: - name: ceph-admin - namespace: default -type: kubernetes.io/rbd -data: - userID: bXlQb29sQWRtaW4= - userKey: QVFCK0hDVmdXSjQ1T0JBQXBrc0VtcVhlZFpjc0JwaStIcmU5M3c9PQ== -EOF - -kubectl apply -f ceph-admin-secret.yaml -``` - -# Create RBD Testing Resources - -### Using RBD in Pods - -``` -# pod -cat > ceph-rbd-pod-inline.yaml << EOF -apiVersion: v1 -kind: Pod -metadata: - name: ceph-rbd-pod-inline -spec: - containers: - - name: ceph-rbd-pod-inline - image: busybox - command: ["sleep", "infinity"] - volumeMounts: - - mountPath: /mnt/ceph_rbd - name: volume - volumes: - - name: volume - rbd: - monitors: - - 10.85.8.118:6789 - - 10.85.8.123:6789 - - 10.85.8.124:6789 - pool: myPool - image: image - user: myPoolUser - secretRef: - name: ceph-user - fsType: ext4 - readOnly: false -EOF - -kubectl apply -f ceph-rbd-pod-inline.yaml -kubectl get pod -kubectl exec pod/ceph-rbd-pod-inline -- df -k | grep rbd -``` - -### Using RBD in Persistent Volumes - -``` -# pod-pvc-pv -cat > ceph-rbd-pod-pvc-pv-allinone.yaml << EOF -apiVersion: v1 -kind: PersistentVolume -metadata: - name: ceph-rbd-pv -spec: - capacity: - storage: 2Gi - accessModes: - - ReadWriteOnce - rbd: - monitors: - - 10.85.8.118:6789 - - 10.85.8.123:6789 - - 10.85.8.124:6789 - pool: myPool - image: image - user: myPoolUser - secretRef: - name: ceph-user - fsType: ext4 - readOnly: false ---- -kind: PersistentVolumeClaim -apiVersion: v1 -metadata: - name: ceph-rbd-pvc -spec: - accessModes: - - ReadWriteOnce - resources: - requests: - storage: 2Gi ---- -apiVersion: v1 -kind: Pod -metadata: - name: ceph-rbd-pod-pvc-pv -spec: - containers: - - name: ceph-rbd-pod-pvc-pv - image: busybox - command: ["sleep", "infinity"] - volumeMounts: - - mountPath: /mnt/ceph_rbd - name: volume - volumes: - - name: volume - persistentVolumeClaim: - claimName: ceph-rbd-pvc -EOF - -kubectl apply -f ceph-rbd-pod-pvc-pv-allinone.yaml -kubectl get pv,pvc,pod -kubectl exec pod/ceph-rbd-pod-pvc-pv -- df -k | grep rbd -``` - -### Using RBD in Storage Classes - -This example is for dynamic provisioning. The ceph-csi driver is needed. - -``` -# pod-pvc-sc -cat > ceph-rbd-pod-pvc-sc-allinone.yaml < /root/.bashrc << EOF -export PATH=$PATH:/var/lib/rancher/rke2/bin/ -export KUBECONFIG=/etc/rancher/rke2/rke2.yaml -EOF - -cat /var/lib/rancher/rke2/server/node-token -token: K10ca0c38d4ff90d8b80319ab34092e315a8b732622e6adf97bc9eb0536REDACTED::server:ec0308000b8a6b595da000efREDACTED -``` - -### RKE2 Agent/Worker provisioning - -``` -mkdir -p /etc/rancher/rke2/ - -cat > /etc/rancher/rke2/config.yaml << EOF -server: https://10.100.103.23:9345 -token: K10ca0c38d4ff90d8b80319ab34092e315a8b732622e6adf97bc9eb0536REDACTED::server:ec0308000b8a6b595da000efREDACTED -EOF - -curl -sfL https://get.rke2.io | INSTALL_RKE2_TYPE="agent" sh - -systemctl enable --now rke2-agent.service -``` - -To import the cluster into Rancher, click **☰ > Cluster Management**. Then on the **Clusters** page, click **Import Existing**. Then run the provided kubectl command on the server/master node. - -# Tested Versions - -OS for running RKE2 nodes: JeOS SLE15-SP2 with installed kernel-default-5.3.18-24.49 - -``` -kubectl version -Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.4", GitCommit:"c96aede7b5205121079932896c4ad89bb93260af", GitTreeState:"clean", BuildDate:"2020-06-22T12:00:00Z", GoVersion:"go1.13.11", Compiler:"gc", Platform:"linux/amd64"} -Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7+rke2r1", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-20T01:50:52Z", GoVersion:"go1.15.5b5", Compiler:"gc", Platform:"linux/amd64"} - -helm version -version.BuildInfo{Version:"3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.12"} -``` - -Kubernetes version on RKE2 cluster: v1.19.7+rke2r1 - -# Troubleshooting - -In case you are using SUSE's ceph-rook based on SES7, it might be useful to expose the monitors on hostNetwork by editing `rook-1.4.5/ceph/cluster.yaml` and setting `spec.network.hostNetwork=true`. - -Also for operating the ceph-rook cluster, it is useful to deploy a toolbox on the Kubernetes cluster where ceph-rook is provisioned by `kubectl apply -f rook-1.4.5/ceph/toolbox.yaml` Then all the ceph related commands can be executed in the toolbox pod, for example, by running `kubectl exec -it -n rook-ceph rook-ceph-tools-686d8b8bfb-2nvqp -- bash` - -Operating with the ceph - basic commands: - -``` -ceph osd pool stats -ceph osd pool delete myPool myPool --yes-i-really-really-mean-it -rbd list -p myPool -> csi-vol-f5d3766c-7296-11eb-b32a-c2b045952d38 -> image -``` - -Delete the image: `rbd rm csi-vol-f5d3766c-7296-11eb-b32a-c2b045952d38 -p myPool` - -CephFS commands in rook toolbox: - -``` -ceph -s -ceph fs ls -ceph fs fail cephfs -ceph fs rm cephfs --yes-i-really-mean-it -ceph osd pool delete cephfs_data cephfs_data --yes-i-really-really-mean-it -ceph osd pool delete cephfs_metadata cephfs_metadata --yes-i-really-really-mean-it -``` - -To prepare a cephfs filesystem, you can run this command on a rook cluster: - -``` -kubectl apply -f rook-1.4.5/ceph/filesystem.yaml -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/ebs/ebs.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/ebs/ebs.md deleted file mode 100644 index 2a08d957fda..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/ebs/ebs.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Creating Persistent Storage in Amazon's EBS -weight: 3053 ---- - -This section describes how to set up Amazon's Elastic Block Store in EC2. - -1. From the EC2 console, go to the **ELASTIC BLOCK STORE** section in the left panel and click **Volumes**. -1. Click **Create Volume**. -1. Optional: Configure the size of the volume or other options. The volume should be created in the same availability zone as the instance it will be attached to. -1. Click **Create Volume**. -1. Click **Close**. - -**Result:** Persistent storage has been created. - -For details on how to set up the newly created storage in Rancher, refer to the section on [setting up existing storage.]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/attaching-existing-storage/) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/examples.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/examples.md deleted file mode 100644 index 2cdd479f767..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/examples.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Provisioning Storage Examples -weight: 3053 ---- - -Rancher supports persistent storage with a variety of volume plugins. However, before you use any of these plugins to bind persistent storage to your workloads, you have to configure the storage itself, whether its a cloud-based solution from a service-provider or an on-prem solution that you manage yourself. - -For your convenience, Rancher offers documentation on how to configure some of the popular storage methods: - -- [NFS](./nfs) -- [vSphere](./vsphere) -- [EBS](./ebs) diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/nfs/nfs.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/nfs/nfs.md deleted file mode 100644 index 65863b93fad..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/nfs/nfs.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: NFS Storage -weight: 3054 ---- - -Before you can use the NFS storage volume plug-in with Rancher deployments, you need to provision an NFS server. - ->**Note:** -> ->- If you already have an NFS share, you don't need to provision a new NFS server to use the NFS volume plugin within Rancher. Instead, skip the rest of this procedure and complete [adding storage]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/). -> ->- This procedure demonstrates how to set up an NFS server using Ubuntu, although you should be able to use these instructions for other Linux distros (e.g. Debian, RHEL, Arch Linux, etc.). For official instruction on how to create an NFS server using another Linux distro, consult the distro's documentation. - ->**Recommended:** To simplify the process of managing firewall rules, use NFSv4. - -1. Using a remote Terminal connection, log into the Ubuntu server that you intend to use for NFS storage. - -1. Enter the following command: - - ``` - sudo apt-get install nfs-kernel-server - ``` - -1. Enter the command below, which sets the directory used for storage, along with user access rights. Modify the command if you'd like to keep storage at a different directory. - - ``` - mkdir -p /nfs && chown nobody:nogroup /nfs - ``` - - The `-p /nfs` parameter creates a directory named `nfs` at root. - - The `chown nobody:nogroup /nfs` parameter allows all access to the storage directory. - -1. Create an NFS exports table. This table sets the directory paths on your NFS server that are exposed to the nodes that will use the server for storage. - - 1. Open `/etc/exports` using your text editor of choice. - 1. Add the path of the `/nfs` folder that you created in step 3, along with the IP addresses of your cluster nodes. Add an entry for each IP address in your cluster. Follow each address and its accompanying parameters with a single space that is a delimiter. - - ``` - /nfs (rw,sync,no_subtree_check) (rw,sync,no_subtree_check) (rw,sync,no_subtree_check) - ``` - - **Tip:** You can replace the IP addresses with a subnet. For example: `10.212.50.12/24` - - 1. Update the NFS table by entering the following command: - - ``` - exportfs -ra - ``` - -1. Open the ports used by NFS. - - 1. To find out what ports NFS is using, enter the following command: - - ``` - rpcinfo -p | grep nfs - ``` - 2. [Open the ports](https://help.ubuntu.com/lts/serverguide/firewall.html.en) that the previous command outputs. For example, the following command opens port 2049: - - ``` - sudo ufw allow 2049 - ``` - -**Result:** Your NFS server is configured to be used for storage with your Rancher nodes. - -## What's Next? - -Within Rancher, add the NFS server as a storage volume and/or storage class. After adding the server, you can use it for storage for your deployments. diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/vsphere/vsphere.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/vsphere/vsphere.md deleted file mode 100644 index 301a5def990..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/examples/vsphere/vsphere.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: vSphere Storage -weight: 3055 ---- - -To provide stateful workloads with vSphere storage, we recommend creating a vSphereVolume StorageClass. This practice dynamically provisions vSphere storage when workloads request volumes through a PersistentVolumeClaim. - -In order to dynamically provision storage in vSphere, the vSphere provider must be [enabled.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere) - -- [Prerequisites](#prerequisites) -- [Creating a StorageClass](#creating-a-storageclass) -- [Creating a Workload with a vSphere Volume](#creating-a-workload-with-a-vsphere-volume) -- [Verifying Persistence of the Volume](#verifying-persistence-of-the-volume) -- [Why to Use StatefulSets Instead of Deployments](#why-to-use-statefulsets-instead-of-deployments) - -### Prerequisites - -In order to provision vSphere volumes in a cluster created with the [Rancher Kubernetes Engine (RKE)]({{< baseurl>}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/), the [vSphere cloud provider]({{}}/rke/latest/en/config-options/cloud-providers/vsphere) must be explicitly enabled in the [cluster options]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/). - -### Creating a StorageClass - -> **Note:** -> -> The following steps can also be performed using the `kubectl` command line tool. See [Kubernetes documentation on persistent volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) for details. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to provide vSphere storage. -1. In the left navigation bar, click **Storage > StorageClasses**. -1. Click **Create**. -3. Enter a **Name** for the StorageClass. -4. Under **Provisioner**, select **VMWare vSphere Volume**. - - {{< img "/img/rancher/vsphere-storage-class.png" "vsphere-storage-class">}} - -5. Optionally, specify additional properties for this storage class under **Parameters**. Refer to the [vSphere storage documentation](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/storageclass.html) for details. -5. Click **Create**. - -### Creating a Workload with a vSphere Volume - -1. In the left navigation bar, click **Workload**. -1. Click **Create**. -1. Click **StatefulSet**. -1. In the **Volume Claim Templates** tab, click **Add Claim Template**. -1. Enter a persistent volume name. -1. In the Storage Class field, select the vSphere StorageClass that you created. -6. Enter the required **Capacity** for the volume. Then click **Define**. -7. Assign a path in the **Mount Point** field. This is the full path where the volume will be mounted in the container file system, e.g. `/persistent`. -8. Click **Create**. - -### Verifying Persistence of the Volume - -1. In the left navigation bar, click **Workload > Pods**. -1. Go to the workload you just created and click **⋮ > Execute Shell**. -2. Note the directory at root where the volume has been mounted to (in this case `/persistent`). -3. Create a file in the volume by executing the command `touch //data.txt`. -4. Close the shell window. -5. Click on the name of the workload to reveal detail information. -7. Click **⋮ > Delete**. -8. Observe that the pod is deleted. Then a new pod is scheduled to replace it so that the workload maintains its configured scale of a single stateful pod. -9. Once the replacement pod is running, click **Execute Shell**. -10. Inspect the contents of the directory where the volume is mounted by entering `ls -l /`. Note that the file you created earlier is still present. - - ![workload-persistent-data]({{}}/img/rancher/workload-persistent-data.png) - -### Why to Use StatefulSets Instead of Deployments - -You should always use [StatefulSets](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/) for workloads consuming vSphere storage, as this resource type is designed to address a VMDK block storage caveat. - -Since vSphere volumes are backed by VMDK block storage, they only support an [access mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) of `ReadWriteOnce`. This setting restricts the volume so that it can only be mounted to a single pod at a time, unless all pods consuming that volume are co-located on the same node. This behavior makes a deployment resource unusable for scaling beyond a single replica if it consumes vSphere volumes. - -Even using a deployment resource with just a single replica may result in a deadlock situation while updating the deployment. If the updated pod is scheduled to a node different from where the existing pod lives, it will fail to start because the VMDK is still attached to the other node. - -### Related Links - -- [vSphere Storage for Kubernetes](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/) -- [Kubernetes Persistent Volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/glusterfs-volumes/glusterfs-volumes.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/glusterfs-volumes/glusterfs-volumes.md deleted file mode 100644 index eaf2386d9fa..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/glusterfs-volumes/glusterfs-volumes.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: GlusterFS Volumes -weight: 5000 ---- - -> This section only applies to [RKE clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) - -In clusters that store data on GlusterFS volumes, you may experience an issue where pods fail to mount volumes after restarting the `kubelet`. The logging of the `kubelet` will show: `transport endpoint is not connected`. To prevent this from happening, you can configure your cluster to mount the `systemd-run` binary in the `kubelet` container. There are two requirements before you can change the cluster configuration: - -- The node needs to have the `systemd-run` binary installed (this can be checked by using the command `which systemd-run` on each cluster node) -- The `systemd-run` binary needs to be compatible with Debian OS on which the hyperkube image is based (this can be checked using the following command on each cluster node, replacing the image tag with the Kubernetes version you want to use) - -``` -docker run -v /usr/bin/systemd-run:/usr/bin/systemd-run --entrypoint /usr/bin/systemd-run rancher/hyperkube:v1.16.2-rancher1 --version -``` - ->**Note:** -> ->Before updating your Kubernetes YAML to mount the `systemd-run` binary, make sure the `systemd` package is installed on your cluster nodes. If this package isn't installed _before_ the bind mounts are created in your Kubernetes YAML, Docker will automatically create the directories and files on each node and will not allow the package install to succeed. - -``` -services: - kubelet: - extra_binds: - - "/usr/bin/systemd-run:/usr/bin/systemd-run" -``` - -After the cluster has finished provisioning, you can check the `kubelet` container logging to see if the functionality is activated by looking for the following logline: - -``` -Detected OS with systemd -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/how-storage-works/how-storage-works.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/how-storage-works/how-storage-works.md deleted file mode 100644 index 4993c0061b3..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/how-storage-works/how-storage-works.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: How Persistent Storage Works -weight: 1 ---- - -A persistent volume (PV) is a piece of storage in the Kubernetes cluster, while a persistent volume claim (PVC) is a request for storage. - -There are two ways to use persistent storage in Kubernetes: - -- Use an existing persistent volume -- Dynamically provision new persistent volumes - -To use an existing PV, your application will need to use a PVC that is bound to a PV, and the PV should include the minimum resources that the PVC requires. - -For dynamic storage provisioning, your application will need to use a PVC that is bound to a storage class. The storage class contains the authorization to provision new persistent volumes. - -![Setting Up New and Existing Persistent Storage]({{}}/img/rancher/rancher-storage.svg) - -For more information, refer to the [official Kubernetes documentation on storage](https://kubernetes.io/docs/concepts/storage/volumes/) - -This section covers the following topics: - -- [About persistent volume claims](#about-persistent-volume-claims) - - [PVCs are required for both new and existing persistent storage](#pvcs-are-required-for-both-new-and-existing-persistent-storage) -- [Setting up existing storage with a PVC and PV](#setting-up-existing-storage-with-a-pvc-and-pv) - - [Binding PVs to PVCs](#binding-pvs-to-pvcs) -- [Provisioning new storage with a PVC and storage class](#provisioning-new-storage-with-a-pvc-and-storage-class) - -# About Persistent Volume Claims - -Persistent volume claims (PVCs) are objects that request storage resources from your cluster. They're similar to a voucher that your deployment can redeem for storage access. A PVC is mounted into a workloads as a volume so that the workload can claim its specified share of the persistent storage. - -To access persistent storage, a pod must have a PVC mounted as a volume. This PVC lets your deployment application store its data in an external location, so that if a pod fails, it can be replaced with a new pod and continue accessing its data stored externally, as though an outage never occurred. - -Each Rancher project contains a list of PVCs that you've created, available from **Resources > Workloads > Volumes**. You can reuse these PVCs when creating deployments in the future. - -### PVCs are Required for Both New and Existing Persistent Storage - -A PVC is required for pods to use any persistent storage, regardless of whether the workload is intended to use storage that already exists, or the workload will need to dynamically provision new storage on demand. - -If you are setting up existing storage for a workload, the workload mounts a PVC, which refers to a PV, which corresponds to existing storage infrastructure. - -If a workload should request new storage, the workload mounts PVC, which refers to a storage class, which has the capability to create a new PV along with its underlying storage infrastructure. - -Rancher lets you create as many PVCs within a project as you'd like. - -You can mount PVCs to a deployment as you create it, or later, after the deployment is running. - -# Setting up Existing Storage with a PVC and PV - -Your pods can store data in [volumes,](https://kubernetes.io/docs/concepts/storage/volumes/) but if the pod fails, that data is lost. To solve this issue, Kubernetes offers persistent volumes (PVs), which are Kubernetes resources that correspond to external storage disks or file systems that your pods can access. If a pod crashes, its replacement pod can access the data in persistent storage without any data loss. - -PVs can represent a physical disk or file system that you host on premise, or a vendor-hosted storage resource, such as Amazon EBS or Azure Disk. - -Creating a persistent volume in Rancher will not create a storage volume. It only creates a Kubernetes resource that maps to an existing volume. Therefore, before you can create a persistent volume as a Kubernetes resource, you must have storage provisioned. - -> **Important:** PVs are created at the cluster level, which means that in a multi-tenant cluster, teams with access to separate namespaces could have access to the same PV. - -### Binding PVs to PVCs - -When pods are set up to use persistent storage, they mount a persistent volume claim (PVC) that is mounted the same way as any other Kubernetes volume. When each PVC is created, the Kubernetes master considers it to be a request for storage and binds it to a PV that matches the minimum resource requirements of the PVC. Not every PVC is guaranteed to be bound to a PV. According to the Kubernetes [documentation,](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) - -> Claims will remain unbound indefinitely if a matching volume does not exist. Claims will be bound as matching volumes become available. For example, a cluster provisioned with many 50Gi PVs would not match a PVC requesting 100Gi. The PVC can be bound when a 100Gi PV is added to the cluster. - -In other words, you can create unlimited PVCs, but they will only be bound to PVs if the Kubernetes master can find a sufficient PVs that has at least the amount of disk space required by the PVC. - -To dynamically provision new storage, the PVC mounted in the pod would have to correspond to a storage class instead of a persistent volume. - -# Provisioning New Storage with a PVC and Storage Class - -Storage Classes allow you to create PVs dynamically without having to create persistent storage in an infrastructure provider first. - -For example, if a workload is bound to a PVC and the PVC refers to an Amazon EBS Storage Class, the storage class can dynamically create an EBS volume and a corresponding PV. - -The Kubernetes master will then bind the newly created PV to your workload's PVC, allowing your workload to use the persistent storage. - diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/iscsi-volumes/iscsi-volumes.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/iscsi-volumes/iscsi-volumes.md deleted file mode 100644 index c8a14cb458d..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/iscsi-volumes/iscsi-volumes.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: iSCSI Volumes -weight: 6000 ---- - -In [Rancher Launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) that store data on iSCSI volumes, you may experience an issue where kubelets fail to automatically connect with iSCSI volumes. This failure is likely due to an incompatibility issue involving the iSCSI initiator tool. You can resolve this issue by installing the iSCSI initiator tool on each of your cluster nodes. - -Rancher Launched Kubernetes clusters storing data on iSCSI volumes leverage the [iSCSI initiator tool](http://www.open-iscsi.com/), which is embedded in the kubelet's `rancher/hyperkube` Docker image. From each kubelet (i.e., the _initiator_), the tool discovers and launches sessions with an iSCSI volume (i.e., the _target_). However, in some instances, the versions of the iSCSI initiator tool installed on the initiator and the target may not match, resulting in a connection failure. - -If you encounter this issue, you can work around it by installing the initiator tool on each node in your cluster. You can install the iSCSI initiator tool by logging into your cluster nodes and entering one of the following commands: - -| Platform | Package Name | Install Command | -| ------------- | ----------------------- | -------------------------------------- | -| Ubuntu/Debian | `open-iscsi` | `sudo apt install open-iscsi` | -| RHEL | `iscsi-initiator-utils` | `yum install iscsi-initiator-utils -y` | - - -After installing the initiator tool on your nodes, edit the YAML for your cluster, editing the kubelet configuration to mount the iSCSI binary and configuration, as shown in the sample below. - ->**Notes:** -> ->- Before updating your Kubernetes YAML to mount the iSCSI binary and configuration, make sure either the `open-iscsi` (deb) or `iscsi-initiator-utils` (yum) package is installed on your cluster nodes. If this package isn't installed _before_ the bind mounts are created in your Kubernetes YAML, Docker will automatically create the directories and files on each node and will not allow the package install to succeed.
->
-> ->- The example YAML below does not apply to K3s, but only to RKE clusters. Since the K3s kubelet does not run in a container, adding extra binds is not necessary. However, all iSCSI tools must still be installed on your K3s nodes. - -``` -services: - kubelet: - extra_binds: - - "/etc/iscsi:/etc/iscsi" - - "/sbin/iscsiadm:/sbin/iscsiadm" -``` diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/provisioning-new-storage/provisioning-new-storage.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/provisioning-new-storage/provisioning-new-storage.md deleted file mode 100644 index 52b13e5d662..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/provisioning-new-storage/provisioning-new-storage.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: Dynamically Provisioning New Storage in Rancher -weight: 2 ---- - -This section describes how to provision new persistent storage for workloads in Rancher. - -This section assumes that you understand the Kubernetes concepts of storage classes and persistent volume claims. For more information, refer to the section on [how storage works.](../how-storage-works) - -New storage is often provisioned by a cloud provider such as Amazon EBS. However, new storage doesn't have to be in the cloud. - -If you have a pool of block storage, and you don't want to use a cloud provider, Longhorn could help you provide persistent storage to your Kubernetes cluster. For more information, see [this page.]({{}}/rancher/v2.6/en/longhorn) - -To provision new storage for your workloads, follow these steps: - -1. [Add a storage class and configure it to use your storage.](#1-add-a-storage-class-and-configure-it-to-use-your-storage) -2. [Use the Storage Class for Pods Deployed with a StatefulSet.](#2-use-the-storage-class-for-pods-deployed-with-a-statefulset) - -### Prerequisites - -- To set up persistent storage, the `Manage Volumes` [role]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-role-reference) is required. -- If you are provisioning storage for a cluster hosted in the cloud, the storage and cluster hosts must have the same cloud provider. -- The cloud provider must be enabled. For details on enabling cloud providers, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) -- Make sure your storage provisioner is available to be enabled. - -The following storage provisioners are enabled by default: - -Name | Plugin ---------|---------- -Amazon EBS Disk | `aws-ebs` -AzureFile | `azure-file` -AzureDisk | `azure-disk` -Google Persistent Disk | `gce-pd` -Longhorn | `flex-volume-longhorn` -VMware vSphere Volume | `vsphere-volume` -Local | `local` -Network File System | `nfs` -hostPath | `host-path` - -To use a storage provisioner that is not on the above list, you will need to use a [feature flag to enable unsupported storage drivers.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/enable-not-default-storage-drivers/) - -### 1. Add a storage class and configure it to use your storage - -These steps describe how to set up a storage class at the cluster level. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to dynamically provision persistent storage volumes and click **Explore**. -1. Click **Storage > Storage Classes**. -1. Click **Create**. -1. Enter a name for your storage class. -1. From the **Provisioner** drop-down, select the service that you want to use to dynamically provision storage volumes. For example, if you have a Amazon EC2 cluster and you want to use cloud storage for it, use the `Amazon EBS Disk` provisioner. -1. In the **Parameters** tab, fill out the information required for the service to dynamically provision storage volumes. Each provisioner requires different information to dynamically provision storage volumes. Consult the service's documentation for help on how to obtain this information. -1. Click **Create**. - -**Result:** The storage class is available to be consumed by a PVC. - -For full information about the storage class parameters, refer to the official [Kubernetes documentation.](https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters). - -### 2. Use the Storage Class for Pods Deployed with a StatefulSet - -StatefulSets manage the deployment and scaling of Pods while maintaining a sticky identity for each Pod. In this StatefulSet, we will configure a VolumeClaimTemplate. Each Pod managed by the StatefulSet will be deployed with a PersistentVolumeClaim based on this VolumeClaimTemplate. The PersistentVolumeClaim will refer to the StorageClass that we created. Therefore, when each Pod managed by the StatefulSet is deployed, it will be bound to dynamically provisioned storage using the StorageClass defined in its PersistentVolumeClaim. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to add use the StorageClass for a workload and click **Explore**. -1. In the left navigation bar, click **Workload**. -1. Click **Create**. -1. Click **StatefulSet**. -1. In the **Volume Claim Templates** tab, click **Add Claim Template**. -1. Enter a name for the persistent volume. -1. In the **StorageClass* field, select the StorageClass that will dynamically provision storage for pods managed by this StatefulSet. -1. In the **Mount Point** field, enter the path that the workload will use to access the volume. -1. Click **Launch**. - -**Result:** When each Pod managed by the StatefulSet is deployed, it will make a request for the specified amount of disk space to the Kubernetes master. If a PV with the specified resources is available when the workload is deployed, the Kubernetes master will bind the PV to Pod with a compatible PVC. - -To attach the PVC to an existing workload, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to add use the StorageClass for a workload and click **Explore**. -1. In the left navigation bar, click **Workload**. -1. Go to the workload that will use storage provisioned with the StorageClass that you cared at click **⋮ > Edit Config**. -1. In the **Volume Claim Templates** section, click **Add Claim Template**. -1. Enter a persistent volume name. -1. In the **StorageClass* field, select the StorageClass that will dynamically provision storage for pods managed by this StatefulSet. -1. In the **Mount Point** field, enter the path that the workload will use to access the volume. -1. Click **Save**. - -**Result:** The workload will make a request for the specified amount of disk space to the Kubernetes master. If a PV with the specified resources is available when the workload is deployed, the Kubernetes master will bind the PV to the PVC. If not, Rancher will provision new persistent storage. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/volumes-and-storage.md b/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/volumes-and-storage.md deleted file mode 100644 index 745fbce0131..00000000000 --- a/versioned_docs/version-2.6/cluster-admin/volumes-and-storage/volumes-and-storage.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: "Kubernetes Persistent Storage: Volumes and Storage Classes" -description: "Learn about the two ways with which you can create persistent storage in Kubernetes: persistent volumes and storage classes" -weight: 2031 ---- -When deploying an application that needs to retain data, you'll need to create persistent storage. Persistent storage allows you to store application data external from the pod running your application. This storage practice allows you to maintain application data, even if the application's pod fails. - -The documents in this section assume that you understand the Kubernetes concepts of persistent volumes, persistent volume claims, and storage classes. For more information, refer to the section on [how storage works.](./how-storage-works) - -### Prerequisites - -To set up persistent storage, the `Manage Volumes` [role]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-role-reference) is required. - -If you are provisioning storage for a cluster hosted in the cloud, the storage and cluster hosts must have the same cloud provider. - -For provisioning new storage with Rancher, the cloud provider must be enabled. For details on enabling cloud providers, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) - -For attaching existing persistent storage to a cluster, the cloud provider does not need to be enabled. - -### Setting up Existing Storage - -The overall workflow for setting up existing storage is as follows: - -1. Set up your persistent storage. This may be storage in an infrastructure provider, or it could be your own storage. -2. Add a persistent volume (PV) that refers to the persistent storage. -3. Add a persistent volume claim (PVC) that refers to the PV. -4. Mount the PVC as a volume in your workload. - -For details and prerequisites, refer to [this page.](./attaching-existing-storage) - -### Dynamically Provisioning New Storage in Rancher - -The overall workflow for provisioning new storage is as follows: - -1. Add a StorageClass and configure it to use your storage provider. The StorageClass could refer to storage in an infrastructure provider, or it could refer to your own storage. -2. Add a persistent volume claim (PVC) that refers to the storage class. -3. Mount the PVC as a volume for your workload. - -For details and prerequisites, refer to [this page.](./provisioning-new-storage) - -### Longhorn Storage - -[Longhorn](https://longhorn.io/) is a lightweight, reliable and easy-to-use distributed block storage system for Kubernetes. - -Longhorn is free, open source software. Originally developed by Rancher Labs, it is now being developed as a sandbox project of the Cloud Native Computing Foundation. It can be installed on any Kubernetes cluster with Helm, with kubectl, or with the Rancher UI. - -If you have a pool of block storage, Longhorn can help you provide persistent storage to your Kubernetes cluster without relying on cloud providers. For more information about Longhorn features, refer to the [documentation.](https://longhorn.io/docs/latest/what-is-longhorn/) - -Rancher v2.5 simplified the process of installing Longhorn on a Rancher-managed cluster. For more information, see [this page.]({{}}/rancher/v2.6/en/longhorn) - -### Provisioning Storage Examples - -We provide examples of how to provision storage with [NFS,](./examples/nfs) [vSphere,](./examples/vsphere) and [Amazon's EBS.](./examples/ebs) - -### GlusterFS Volumes - -In clusters that store data on GlusterFS volumes, you may experience an issue where pods fail to mount volumes after restarting the `kubelet`. For details on preventing this from happening, refer to [this page.](./glusterfs-volumes) - -### iSCSI Volumes - -In [Rancher Launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) that store data on iSCSI volumes, you may experience an issue where kubelets fail to automatically connect with iSCSI volumes. For details on resolving this issue, refer to [this page.](./iscsi-volumes) - -### hostPath Volumes -Before you create a hostPath volume, you need to set up an [extra_bind]({{}}/rke/latest/en/config-options/services/services-extras/#extra-binds/) in your cluster configuration. This will mount the path as a volume in your kubelets, which can then be used for hostPath volumes in your workloads. - -### Migrating vSphere Cloud Provider from In-tree to Out-of-tree - -Kubernetes is moving away from maintaining cloud providers in-tree. vSphere has an out-of-tree cloud provider that can be used by installing the vSphere cloud provider and cloud storage plugins. - -For instructions on how to migrate from the in-tree vSphere cloud provider to out-of-tree, and manage the existing VMs post migration, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree) - -### Related Links - -- [Kubernetes Documentation: Storage](https://kubernetes.io/docs/concepts/storage/) diff --git a/versioned_docs/version-2.6/cluster-provisioning/cluster-capabilities-table/index.md b/versioned_docs/version-2.6/cluster-provisioning/cluster-capabilities-table/index.md deleted file mode 100644 index 2ea295d4617..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/cluster-capabilities-table/index.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -headless: true ---- - - -| Action | Rancher Launched Kubernetes Clusters | EKS, GKE and AKS Clusters1 | Other Hosted Kubernetes Clusters | Non-EKS or GKE Registered Clusters | -| --- | --- | ---| ---|----| -| [Using kubectl and a kubeconfig file to Access a Cluster]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/) | ✓ | ✓ | ✓ | ✓ | -| [Managing Cluster Members]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/cluster-members/) | ✓ | ✓ | ✓ | ✓ | -| [Editing and Upgrading Clusters]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/) | ✓ | ✓ | ✓ | ✓2 | -| [Managing Nodes]({{}}/rancher/v2.6/en/cluster-admin/nodes) | ✓ | ✓ | ✓ | ✓3 | -| [Managing Persistent Volumes and Storage Classes]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) | ✓ | ✓ | ✓ | ✓ | -| [Managing Projects, Namespaces and Workloads]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/) | ✓ | ✓ | ✓ | ✓ | -| [Using App Catalogs]({{}}/rancher/v2.6/en/helm-charts/) | ✓ | ✓ | ✓ | ✓ | -| Configuring Tools ([Alerts, Notifiers, Monitoring]({{}}/rancher/v2.6/en/monitoring-alerting/), [Logging]({{}}/rancher/v2.6/en/logging/), [Istio]({{}}/rancher/v2.6/en/istio/)) | ✓ | ✓ | ✓ | ✓ | -| [Running Security Scans]({{}}/rancher/v2.6/en/security/security-scan/) | ✓ | ✓ | ✓ | ✓ | -| [Use existing configuration to create additional clusters]({{}}/rancher/v2.6/en/cluster-admin/cloning-clusters/)| ✓ | ✓ | ✓ | | -| [Ability to rotate certificates]({{}}/rancher/v2.6/en/cluster-admin/certificate-rotation/) | ✓ | ✓ | | | -| Ability to [backup]({{}}/rancher/v2.6/en/cluster-admin/backing-up-etcd/) and [restore]({{}}/rancher/v2.6/en/cluster-admin/restoring-etcd/) Rancher-launched clusters | ✓ | ✓ | | ✓4 | -| [Cleaning Kubernetes components when clusters are no longer reachable from Rancher]({{}}/rancher/v2.6/en/cluster-admin/cleaning-cluster-nodes/) | ✓ | | | | -| [Configuring Pod Security Policies]({{}}/rancher/v2.6/en/cluster-admin/pod-security-policy/) | ✓ | ✓ | || - -1. Registered GKE and EKS clusters have the same options available as GKE and EKS clusters created from the Rancher UI. The difference is that when a registered cluster is deleted from the Rancher UI, it is not destroyed. - -2. Cluster configuration options can't be edited for registered clusters, except for [K3s and RKE2 clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/) - -3. For registered cluster nodes, the Rancher UI exposes the ability to cordon, drain, and edit the node. - -4. For registered clusters using etcd as a control plane, snapshots must be taken manually outside of the Rancher UI to use for backup and recovery. diff --git a/versioned_docs/version-2.6/cluster-provisioning/cluster-provisioning.md b/versioned_docs/version-2.6/cluster-provisioning/cluster-provisioning.md deleted file mode 100644 index b3e16047f42..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/cluster-provisioning.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Setting up Kubernetes Clusters in Rancher -description: Provisioning Kubernetes Clusters -weight: 7 ---- - -Rancher simplifies the creation of clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a cluster. Use the option that best fits your use case. - -This section assumes a basic familiarity with Docker and Kubernetes. For a brief explanation of how Kubernetes components work together, refer to the [concepts]({{}}/rancher/v2.6/en/overview/concepts) page. - -For a conceptual overview of how the Rancher server provisions clusters and what tools it uses to provision them, refer to the [architecture]({{}}/rancher/v2.6/en/overview/architecture/) page. - -This section covers the following topics: - - - -- [Cluster Management Capabilities by Cluster Type](#cluster-management-capabilities-by-cluster-type) -- [Setting up clusters in a hosted Kubernetes provider](#setting-up-clusters-in-a-hosted-kubernetes-provider) -- [Launching Kubernetes with Rancher](#launching-kubernetes-with-rancher) - - [Launching Kubernetes and Provisioning Nodes in an Infrastructure Provider](#launching-kubernetes-and-provisioning-nodes-in-an-infrastructure-provider) - - [Launching Kubernetes on Existing Custom Nodes](#launching-kubernetes-on-existing-custom-nodes) -- [Registering Existing Clusters](#registering-existing-clusters) -- [Programmatically Creating Clusters](#programmatically-creating-clusters) - - - -### Cluster Management Capabilities by Cluster Type - -The following table summarizes the options and settings available for each cluster type: - -import ClusterCapabilitiesTable from '/rancher/v2.6/en/shared-files/_cluster-capabilities-table.md'; - - - -# Setting up Clusters in a Hosted Kubernetes Provider - -In this scenario, Rancher does not provision Kubernetes because it is installed by providers such as Google Kubernetes Engine (GKE), Amazon Elastic Container Service for Kubernetes, or Azure Kubernetes Service. - -If you use a Kubernetes provider such as Google GKE, Rancher integrates with its cloud APIs, allowing you to create and manage role-based access control for the hosted cluster from the Rancher UI. - -For more information, refer to the section on [hosted Kubernetes clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters) - -# Launching Kubernetes with Rancher - -Rancher uses the [Rancher Kubernetes Engine (RKE)]({{}}/rke/latest/en/) as a library when provisioning Kubernetes on your own nodes. RKE is Rancher’s own lightweight Kubernetes installer. - -In RKE clusters, Rancher manages the deployment of Kubernetes. These clusters can be deployed on any bare metal server, cloud provider, or virtualization platform. - -These nodes can be dynamically provisioned through Rancher's UI, which calls [Docker Machine](https://docs.docker.com/machine/) to launch nodes on various cloud providers. - -If you already have a node that you want to add to an RKE cluster, you can add it to the cluster by running a Rancher agent container on it. - -For more information, refer to the section on [RKE clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) - -### Launching Kubernetes and Provisioning Nodes in an Infrastructure Provider - -Rancher can dynamically provision nodes in infrastructure providers such as Amazon EC2, DigitalOcean, Azure, or vSphere, then install Kubernetes on them. - -Using Rancher, you can create pools of nodes based on a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates). This template defines the parameters used to launch nodes in your cloud providers. - -One benefit of using nodes hosted by an infrastructure provider is that if a node loses connectivity with the cluster, Rancher can automatically replace it, thus maintaining the expected cluster configuration. - -The cloud providers available for creating a node template are decided based on the [node drivers]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-drivers) active in the Rancher UI. - -For more information, refer to the section on [nodes hosted by an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) - -### Launching Kubernetes on Existing Custom Nodes - -When setting up this type of cluster, Rancher installs Kubernetes on existing [custom nodes,]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/) which creates a custom cluster. - -You can bring any nodes you want to Rancher and use them to create a cluster. - -These nodes include on-prem bare metal servers, cloud-hosted virtual machines, or on-prem virtual machines. - -# Registering Existing Clusters - -The cluster registration feature replaces the feature to import clusters. - -Registering EKS clusters now provides additional benefits. For the most part, registered EKS clusters and EKS clusters created in Rancher are treated the same way in the Rancher UI, except for deletion. - -When you delete an EKS cluster that was created in Rancher, the cluster is destroyed. When you delete an EKS cluster that was registered in Rancher, it is disconnected from the Rancher server, but it still exists and you can still access it in the same way you did before it was registered in Rancher. - -For more information, see [this page.](./registered-clusters) - -# Programmatically Creating Clusters - -The most common way to programmatically deploy Kubernetes clusters through Rancher is by using the Rancher2 Terraform provider. The documentation for creating clusters with Terraform is [here.](https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster) - -EKS, GKE, AKS clusters and RKE clusters can be created or imported with Terraform. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/ack/ack.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/ack/ack.md deleted file mode 100644 index 2a701f6a6dc..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/ack/ack.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster -shortTitle: Alibaba Cloud Container Service for Kubernetes -weight: 2120 ---- - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver]({{}}/rancher/v2.6/en/admin-settings/drivers/cluster-drivers/) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver]({{}}/rancher/v2.6/en/admin-settings/drivers/cluster-drivers/#activating-deactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -# Prerequisites Outside of Rancher - ->**Note** ->Deploying to ACK will incur charges. - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -# Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -# Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/aks/aks.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/aks/aks.md deleted file mode 100644 index f54e1e42bdd..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/aks/aks.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -title: Creating an AKS Cluster -shortTitle: Azure Kubernetes Service -weight: 2115 ---- - -You can use Rancher to create a cluster hosted in Microsoft Azure Kubernetes Service (AKS). - -- [Prerequisites in Microsoft Azure](#prerequisites-in-microsoft-azure) -- [Setting Up the Service Principal with the Azure Command Line Tool](#setting-up-the-service-principal-with-the-azure-command-line-tool) - - [Setting Up the Service Principal from the Azure Portal](#setting-up-the-service-principal-from-the-azure-portal) -- [1. Create the AKS Cloud Credentials](#1-create-the-aks-cloud-credentials) -- [2. Create the AKS Cluster](#2-create-the-aks-cluster) -- [Role-based Access Control](#role-based-access-control) -- [AKS Cluster Configuration Reference](#aks-cluster-configuration-reference) -- [Private Clusters](#private-clusters) -- [Syncing](#syncing) -- [Programmatically Creating AKS Clusters](#programmatically-creating-aks-clusters) - -# Prerequisites in Microsoft Azure - ->**Note** ->Deploying to AKS will incur charges. - -To interact with Azure APIs, an AKS cluster requires an Azure Active Directory (AD) service principal. The service principal is needed to dynamically create and manage other Azure resources, and it provides credentials for your cluster to communicate with AKS. For more information about the service principal, refer to the [AKS documentation](https://docs.microsoft.com/en-us/azure/aks/kubernetes-service-principal). - -Before creating the service principal, you need to obtain the following information from the [Microsoft Azure Portal](https://portal.azure.com): - -- Subscription ID -- Client ID -- Client secret - -The below sections describe how to set up these prerequisites using either the Azure command line tool or the Azure portal. - -### Setting Up the Service Principal with the Azure Command Line Tool - -You can create the service principal by running this command: - -``` -az ad sp create-for-rbac --skip-assignment -``` - -The result should show information about the new service principal: -``` -{ - "appId": "xxxx--xxx", - "displayName": "", - "name": "http://", - "password": "", - "tenant": "" -} -``` - -You also need to add roles to the service principal so that it has privileges for communication with the AKS API. It also needs access to create and list virtual networks. - -Below is an example command for assigning the Contributor role to a service principal. Contributors can manage anything on AKS but cannot give access to others: - -``` -az role assignment create \ - --assignee $appId \ - --scope /subscriptions/$/resourceGroups/$ \ - --role Contributor -``` - -You can also create the service principal and give it Contributor privileges by combining the two commands into one. In this command, the scope needs to provide a full path to an Azure resource: - -``` -az ad sp create-for-rbac \ - --scope /subscriptions/$/resourceGroups/$ \ - --role Contributor -``` - -### Setting Up the Service Principal from the Azure Portal - -You can also follow these instructions to set up a service principal and give it role-based access from the Azure Portal. - -1. Go to the Microsoft Azure Portal [home page](https://portal.azure.com). - -1. Click **Azure Active Directory**. -1. Click **App registrations**. -1. Click **New registration**. -1. Enter a name. This will be the name of your service principal. -1. Optional: Choose which accounts can use the service principal. -1. Click **Register**. -1. You should now see the name of your service principal under **Azure Active Directory > App registrations**. -1. Click the name of your service principal. Take note of the application ID (also called app ID or client ID) so that you can use it when provisioning your AKS cluster. Then click **Certificates & secrets**. -1. Click **New client secret**. -1. Enter a short description, pick an expiration time, and click **Add**. Take note of the client secret so that you can use it when provisioning the AKS cluster. - -**Result:** You have created a service principal and you should be able to see it listed in the **Azure Active Directory** section under **App registrations**. You still need to give the service principal access to AKS. - -To give role-based access to your service principal, - -1. Click **All Services** in the left navigation bar. Then click **Subscriptions**. -1. Click the name of the subscription that you want to associate with your Kubernetes cluster. Take note of the subscription ID so that you can use it when provisioning your AKS cluster. -1. Click **Access Control (IAM)**. -1. In the **Add role assignment** section, click **Add**. -1. In the **Role** field, select a role that will have access to AKS. For example, you can use the **Contributor** role, which has permission to manage everything except for giving access to other users. -1. In the **Assign access to** field, select **Azure AD user, group, or service principal**. -1. In the **Select** field, select the name of your service principal and click **Save**. - -**Result:** Your service principal now has access to AKS. - -# 1. Create the AKS Cloud Credentials - -1. In the Rancher UI, click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **Azure**. -1. Fill out the form. For help with filling out the form, see the [configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference/#cloud-credentials) -1. Click **Create**. - -# 2. Create the AKS Cluster - -Use Rancher to set up and configure your Kubernetes cluster. - -1. Click **☰ > Cluster Management**. -1. In the **Clusters** section, click **Create**. -1. Click **Azure AKS**. -1. Fill out the form. For help with filling out the form, see the [configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference) -1. Click **Create**. - -**Result:** Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -# Role-based Access Control -When provisioning an AKS cluster in the Rancher UI, RBAC is not configurable because it is required to be enabled. - -RBAC is required for AKS clusters that are registered or imported into Rancher. - -# AKS Cluster Configuration Reference - -For more information about how to configure AKS clusters from the Rancher UI, see the [configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference) - -# Private Clusters - -Typically, AKS worker nodes do not get public IPs, regardless of whether the cluster is private. In a private cluster, the control plane does not have a public endpoint. - -Rancher can connect to a private AKS cluster in one of two ways. - -The first way to ensure that Rancher is running on the same [NAT](https://docs.microsoft.com/en-us/azure/virtual-network/nat-overview) as the AKS nodes. - -The second way is to run a command to register the cluster with Rancher. Once the cluster is provisioned, you can run the displayed command anywhere you can connect to the cluster’s Kubernetes API. This command is displayed in a pop-up when you provision an AKS cluster with a private API endpoint enabled. - -> **Note:** Please be aware that when registering an existing AKS cluster, the cluster might take some time, possibly hours, to appear in the `Cluster To register` dropdown list. This outcome will be based on region. - -For more information about connecting to an AKS private cluster, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/private-clusters#options-for-connecting-to-the-private-cluster) - -# Syncing - -The AKS provisioner can synchronize the state of an AKS cluster between Rancher and the provider. For an in-depth technical explanation of how this works, see [Syncing.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/syncing) - -For information on configuring the refresh interval, see [this section.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/#configuring-the-refresh-interval) - -# Programmatically Creating AKS Clusters - -The most common way to programmatically deploy AKS clusters through Rancher is by using the Rancher2 Terraform provider. The documentation for creating clusters with Terraform is [here.](https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/cce/cce.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/cce/cce.md deleted file mode 100644 index 1065d360b17..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/cce/cce.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster -shortTitle: Huawei Cloud Kubernetes Service -weight: 2130 ---- - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver]({{}}/rancher/v2.6/en/admin-settings/drivers/cluster-drivers/) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver]({{}}/rancher/v2.6/en/admin-settings/drivers/cluster-drivers/#activating-deactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -# Prerequisites in Huawei - ->**Note** ->Deploying to CCE will incur charges. - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0066738518.html). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -# Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -# Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -# Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -# Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -**Note:** If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#config-file-structure-in-rancher-v2-3-0) - -# Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/eks.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/eks.md deleted file mode 100644 index 3f55612fbdd..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/eks.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: Creating an EKS Cluster -shortTitle: Amazon EKS -weight: 2110 ---- -Amazon EKS provides a managed control plane for your Kubernetes cluster. Amazon EKS runs the Kubernetes control plane instances across multiple Availability Zones to ensure high availability. Rancher provides an intuitive user interface for managing and deploying the Kubernetes clusters you run in Amazon EKS. With this guide, you will use Rancher to quickly and easily launch an Amazon EKS Kubernetes cluster in your AWS account. For more information on Amazon EKS, see this [documentation](https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html). - -- [Prerequisites in Amazon Web Services](#prerequisites-in-amazon-web-services) - - [Amazon VPC](#amazon-vpc) - - [IAM Policies](#iam-policies) -- [Create the EKS Cluster](#create-the-eks-cluster) -- [EKS Cluster Configuration Reference](#eks-cluster-configuration-reference) -- [Architecture](#architecture) -- [AWS Service Events](#aws-service-events) -- [Security and Compliance](#security-and-compliance) -- [Tutorial](#tutorial) -- [Minimum EKS Permissions](#minimum-eks-permissions) -- [Syncing](#syncing) -- [Troubleshooting](#troubleshooting) -- [Programmatically Creating EKS Clusters](#programmatically-creating-eks-clusters) -# Prerequisites in Amazon Web Services - ->**Note** ->Deploying to Amazon AWS will incur charges. For more information, refer to the [EKS pricing page](https://aws.amazon.com/eks/pricing/). - -To set up a cluster on EKS, you will need to set up an Amazon VPC (Virtual Private Cloud). You will also need to make sure that the account you will be using to create the EKS cluster has the appropriate [permissions.](#minimum-eks-permissions) For details, refer to the official guide on [Amazon EKS Prerequisites](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html#eks-prereqs). - -### Amazon VPC - -An Amazon VPC is required to launch the EKS cluster. The VPC enables you to launch AWS resources into a virtual network that you've defined. You can set one up yourself and provide it during cluster creation in Rancher. If you do not provide one during creation, Rancher will create one. For more information, refer to the [Tutorial: Creating a VPC with Public and Private Subnets for Your Amazon EKS Cluster](https://docs.aws.amazon.com/eks/latest/userguide/create-public-private-vpc.html). - -### IAM Policies - -Rancher needs access to your AWS account in order to provision and administer your Kubernetes clusters in Amazon EKS. You'll need to create a user for Rancher in your AWS account and define what that user can access. - -1. Create a user with programmatic access by following the steps [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html). - -2. Next, create an IAM policy that defines what this user has access to in your AWS account. It's important to only grant this user minimal access within your account. The minimum permissions required for an EKS cluster are listed [here.](#minimum-eks-permissions) Follow the steps [here](https://docs.aws.amazon.com/eks/latest/userguide/EKS_IAM_user_policies.html) to create an IAM policy and attach it to your user. - -3. Finally, follow the steps [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey) to create an access key and secret key for this user. - -> **Note:** It's important to regularly rotate your access and secret keys. See this [documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#rotating_access_keys_console) for more information. - -For more detailed information on IAM policies for EKS, refer to the official [documentation on Amazon EKS IAM Policies, Roles, and Permissions](https://docs.aws.amazon.com/eks/latest/userguide/IAM_policies.html). - - -# Create the EKS Cluster - -Use Rancher to set up and configure your Kubernetes cluster. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Choose **Amazon EKS**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Fill out the rest of the form. For help, refer to the [configuration reference.](#eks-cluster-configuration-reference) -1. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -# EKS Cluster Configuration Reference - -For the full list of EKS cluster configuration options, see [this page.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/eks-config-reference) - -# Architecture - -The figure below illustrates the high-level architecture of Rancher 2.x. The figure depicts a Rancher Server installation that manages two Kubernetes clusters: one created by RKE and another created by EKS. - -
Managing Kubernetes Clusters through Rancher's Authentication Proxy
- -![Architecture]({{}}/img/rancher/rancher-architecture-rancher-api-server.svg) - -# AWS Service Events - -To find information on any AWS Service events, please see [this page](https://status.aws.amazon.com/). - -# Security and Compliance - -By default only the IAM user or role that created a cluster has access to it. Attempting to access the cluster with any other user or role without additional configuration will lead to an error. In Rancher, this means using a credential that maps to a user or role that was not used to create the cluster will cause an unauthorized error. For example, an EKSCtl cluster will not register in Rancher unless the credentials used to register the cluster match the role or user used by EKSCtl. Additional users and roles can be authorized to access a cluster by being added to the aws-auth configmap in the kube-system namespace. For a more in-depth explanation and detailed instructions, please see this [documentation](https://aws.amazon.com/premiumsupport/knowledge-center/amazon-eks-cluster-access/). - -For more information on security and compliance with your Amazon EKS Kubernetes cluster, please see this [documentation](https://docs.aws.amazon.com/eks/latest/userguide/shared-responsibilty.html). - -# Tutorial - -This [tutorial](https://aws.amazon.com/blogs/opensource/managing-eks-clusters-rancher/) on the AWS Open Source Blog will walk you through how to set up an EKS cluster with Rancher, deploy a publicly accessible app to test the cluster, and deploy a sample project to track real-time geospatial data using a combination of other open-source software such as Grafana and InfluxDB. - -# Minimum EKS Permissions - -See [this page](./permissions) for the minimum set of permissions necessary to use all functionality of the EKS driver in Rancher. - -# Syncing - -The EKS provisioner can synchronize the state of an EKS cluster between Rancher and the provider. For an in-depth technical explanation of how this works, see [Syncing.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/syncing/) - -For information on configuring the refresh interval, refer to [this section.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/eks-config-reference/#configuring-the-refresh-interval) - -# Troubleshooting - -If your changes were overwritten, it could be due to the way the cluster data is synced with EKS. Changes shouldn't be made to the cluster from another source, such as in the EKS console, and in Rancher within a five-minute span. For information on how this works and how to configure the refresh interval, refer to [Syncing.](#syncing) - -If an unauthorized error is returned while attempting to modify or register the cluster and the cluster was not created with the role or user that your credentials belong to, refer to [Security and Compliance.](#security-and-compliance) - -For any issues or troubleshooting details for your Amazon EKS Kubernetes cluster, please see this [documentation](https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting.html). - -# Programmatically Creating EKS Clusters - -The most common way to programmatically deploy EKS clusters through Rancher is by using the Rancher2 Terraform provider. The documentation for creating clusters with Terraform is [here.](https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/permissions/permissions.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/permissions/permissions.md deleted file mode 100644 index 8f4539e1c6f..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/eks/permissions/permissions.md +++ /dev/null @@ -1,223 +0,0 @@ ---- -title: Minimum EKS Permissions -weight: 1 ---- - -Documented here is a minimum set of permissions necessary to use all functionality of the EKS driver in Rancher. Additional permissions are required for Rancher to provision the `Service Role` and `VPC` resources. Optionally these resources can be created **before** the cluster creation and will be selectable when defining the cluster configuration. - -Resource | Description ----------|------------ -Service Role | The service role provides Kubernetes the permissions it requires to manage resources on your behalf. Rancher can create the service role with the following [Service Role Permissions](#service-role-permissions). -VPC | Provides isolated network resources utilised by EKS and worker nodes. Rancher can create the VPC resources with the following [VPC Permissions](#vpc-permissions). - - -Resource targeting uses `*` as the ARN of many of the resources created cannot be known before creating the EKS cluster in Rancher. - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "EC2Permisssions", - "Effect": "Allow", - "Action": [ - "ec2:RunInstances", - "ec2:RevokeSecurityGroupIngress", - "ec2:RevokeSecurityGroupEgress", - "ec2:DescribeRegions", - "ec2:DescribeVpcs", - "ec2:DescribeTags", - "ec2:DescribeSubnets", - "ec2:DescribeSecurityGroups", - "ec2:DescribeRouteTables", - "ec2:DescribeLaunchTemplateVersions", - "ec2:DescribeLaunchTemplates", - "ec2:DescribeKeyPairs", - "ec2:DescribeInternetGateways", - "ec2:DescribeImages", - "ec2:DescribeAvailabilityZones", - "ec2:DescribeAccountAttributes", - "ec2:DeleteTags", - "ec2:DeleteSecurityGroup", - "ec2:DeleteKeyPair", - "ec2:CreateTags", - "ec2:CreateSecurityGroup", - "ec2:CreateLaunchTemplateVersion", - "ec2:CreateLaunchTemplate", - "ec2:CreateKeyPair", - "ec2:AuthorizeSecurityGroupIngress", - "ec2:AuthorizeSecurityGroupEgress" - ], - "Resource": "*" - }, - { - "Sid": "CloudFormationPermisssions", - "Effect": "Allow", - "Action": [ - "cloudformation:ListStacks", - "cloudformation:ListStackResources", - "cloudformation:DescribeStacks", - "cloudformation:DescribeStackResources", - "cloudformation:DescribeStackResource", - "cloudformation:DeleteStack", - "cloudformation:CreateStackSet", - "cloudformation:CreateStack" - ], - "Resource": "*" - }, - { - "Sid": "IAMPermissions", - "Effect": "Allow", - "Action": [ - "iam:PassRole", - "iam:ListRoles", - "iam:ListRoleTags", - "iam:ListInstanceProfilesForRole", - "iam:ListInstanceProfiles", - "iam:ListAttachedRolePolicies", - "iam:GetRole", - "iam:GetInstanceProfile", - "iam:DetachRolePolicy", - "iam:DeleteRole", - "iam:CreateRole", - "iam:AttachRolePolicy" - ], - "Resource": "*" - }, - { - "Sid": "KMSPermisssions", - "Effect": "Allow", - "Action": "kms:ListKeys", - "Resource": "*" - }, - { - "Sid": "EKSPermisssions", - "Effect": "Allow", - "Action": [ - "eks:UpdateNodegroupVersion", - "eks:UpdateNodegroupConfig", - "eks:UpdateClusterVersion", - "eks:UpdateClusterConfig", - "eks:UntagResource", - "eks:TagResource", - "eks:ListUpdates", - "eks:ListTagsForResource", - "eks:ListNodegroups", - "eks:ListFargateProfiles", - "eks:ListClusters", - "eks:DescribeUpdate", - "eks:DescribeNodegroup", - "eks:DescribeFargateProfile", - "eks:DescribeCluster", - "eks:DeleteNodegroup", - "eks:DeleteFargateProfile", - "eks:DeleteCluster", - "eks:CreateNodegroup", - "eks:CreateFargateProfile", - "eks:CreateCluster" - ], - "Resource": "*" - } - ] -} -``` - -### Service Role Permissions - -Permissions required for Rancher to create service role on users behalf during the EKS cluster creation process. - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "IAMPermisssions", - "Effect": "Allow", - "Action": [ - "iam:AddRoleToInstanceProfile", - "iam:AttachRolePolicy", - "iam:CreateInstanceProfile", - "iam:CreateRole", - "iam:CreateServiceLinkedRole", - "iam:DeleteInstanceProfile", - "iam:DeleteRole", - "iam:DetachRolePolicy", - "iam:GetInstanceProfile", - "iam:GetRole", - "iam:ListAttachedRolePolicies", - "iam:ListInstanceProfiles", - "iam:ListInstanceProfilesForRole", - "iam:ListRoles", - "iam:ListRoleTags", - "iam:PassRole", - "iam:RemoveRoleFromInstanceProfile" - ], - "Resource": "*" - } - ] -} -``` - -When an EKS cluster is created, Rancher will create a service role with the following trust policy: - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Action": "sts:AssumeRole", - "Principal": { - "Service": "eks.amazonaws.com" - }, - "Effect": "Allow", - "Sid": "" - } - ] -} -``` - -This role will also have two role policy attachments with the following policies ARNs: - -``` -arn:aws:iam::aws:policy/AmazonEKSClusterPolicy -arn:aws:iam::aws:policy/AmazonEKSServicePolicy -``` - -### VPC Permissions - -Permissions required for Rancher to create VPC and associated resources. - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "VPCPermissions", - "Effect": "Allow", - "Action": [ - "ec2:ReplaceRoute", - "ec2:ModifyVpcAttribute", - "ec2:ModifySubnetAttribute", - "ec2:DisassociateRouteTable", - "ec2:DetachInternetGateway", - "ec2:DescribeVpcs", - "ec2:DeleteVpc", - "ec2:DeleteTags", - "ec2:DeleteSubnet", - "ec2:DeleteRouteTable", - "ec2:DeleteRoute", - "ec2:DeleteInternetGateway", - "ec2:CreateVpc", - "ec2:CreateSubnet", - "ec2:CreateSecurityGroup", - "ec2:CreateRouteTable", - "ec2:CreateRoute", - "ec2:CreateInternetGateway", - "ec2:AttachInternetGateway", - "ec2:AssociateRouteTable" - ], - "Resource": "*" - } - ] -} -``` diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/gke/gke.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/gke/gke.md deleted file mode 100644 index 95567faa8c9..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/gke/gke.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Managing GKE Clusters -shortTitle: Google Kubernetes Engine -weight: 2105 ---- - -- [Prerequisites](#prerequisites) -- [Provisioning a GKE Cluster](#provisioning-a-gke-cluster) -- [Private Clusters](#private-clusters) -- [Configuration Reference](#configuration-reference) -- [Updating Kubernetes Version](#updating-kubernetes-version) -- [Syncing](#syncing) -- [Programmatically Creating GKE Clusters](#programmatically-creating-gke-clusters) - -# Prerequisites - -Some setup in Google Kubernetes Engine is required. - -### Service Account Token - -Create a service account using [Google Kubernetes Engine](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts). GKE uses this account to operate your cluster. Creating this account also generates a private key used for authentication. - -The service account requires the following roles: - -- **Compute Viewer:** `roles/compute.viewer` -- **Project Viewer:** `roles/viewer` -- **Kubernetes Engine Admin:** `roles/container.admin` -- **Service Account User:** `roles/iam.serviceAccountUser` - -[Google Documentation: Creating and Enabling Service Accounts](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances) - -For help obtaining a private key for your service account, refer to the Google cloud documentation [here.](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating_service_account_keys) You will need to save the key in JSON format. - -### Google Project ID - -Your cluster will need to be part of a Google Project. - -To create a new project, refer to the Google cloud documentation [here.](https://cloud.google.com/resource-manager/docs/creating-managing-projects#creating_a_project) - -To get the project ID of an existing project, refer to the Google cloud documentation [here.](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects) - -# Provisioning a GKE Cluster - ->**Note** ->Deploying to GKE will incur charges. - -### 1. Create a Cloud Credential - -1. Click **☰ > Cluster Management**. -1. In the left navigation bar, click **Cloud Credentials**. -1. Click **Create**. -1. Enter a name for your Google cloud credentials. -1. In the **Service Account** text box, paste your service account private key JSON, or upload the JSON file. -1. Click **Create**. - -**Result:** You have created credentials that Rancher will use to provision the new GKE cluster. - -### 2. Create the GKE Cluster -Use Rancher to set up and configure your Kubernetes cluster. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **Google GKE**. -1. Enter a **Cluster Name**. -1. Optional: Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Optional: Add Kubernetes [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) or [annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) to the cluster. -1. Enter your Google project ID and your Google cloud credentials. -1. Fill out the rest of the form. For help, refer to the [GKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference) -1. Click **Create**. - -**Result:** You have successfully deployed a GKE cluster. - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -# Private Clusters - -Private GKE clusters are supported. Note: This advanced setup can require more steps during the cluster provisioning process. For details, see [this section.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/private-clusters/) - -# Configuration Reference - -For details on configuring GKE clusters in Rancher, see [this page.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference) -# Updating Kubernetes Version - -The Kubernetes version of a cluster can be upgraded to any version available in the region or zone fo the GKE cluster. Upgrading the master Kubernetes version does not automatically upgrade worker nodes. Nodes can be upgraded independently. - ->**Note** ->GKE has removed basic authentication in 1.19+. In order to upgrade a cluster to 1.19+, basic authentication must be disabled in the Google Cloud. Otherwise, an error will appear in Rancher when an upgrade to 1.19+ is attempted. You can follow the [Google documentation](https://cloud.google.com/kubernetes-engine/docs/how-to/api-server-authentication#disabling_authentication_with_a_static_password). After this, the Kubernetes version can be updated to 1.19+ via Rancher. - -# Syncing - -The GKE provisioner can synchronize the state of a GKE cluster between Rancher and the provider. For an in-depth technical explanation of how this works, see [Syncing.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/syncing) - -For information on configuring the refresh interval, see [this section.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/#configuring-the-refresh-interval) - -# Programmatically Creating GKE Clusters - -The most common way to programmatically deploy GKE clusters through Rancher is by using the Rancher2 Terraform provider. The documentation for creating clusters with Terraform is [here.](https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/hosted-kubernetes-clusters.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/hosted-kubernetes-clusters.md deleted file mode 100644 index 32bb6ee82cd..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/hosted-kubernetes-clusters.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Setting up Clusters from Hosted Kubernetes Providers -weight: 3 ---- - -In this scenario, Rancher does not provision Kubernetes because it is installed by providers such as Google Kubernetes Engine (GKE), Amazon Elastic Container Service for Kubernetes, or Azure Kubernetes Service. - -If you use a Kubernetes provider such as Google GKE, Rancher integrates with its cloud APIs, allowing you to create and manage role-based access control for the hosted cluster from the Rancher UI. - -In this use case, Rancher sends a request to a hosted provider using the provider's API. The provider then provisions and hosts the cluster for you. When the cluster finishes building, you can manage it from the Rancher UI along with clusters you've provisioned that are hosted on-prem or in an infrastructure provider. - -Rancher supports the following Kubernetes providers: - -- [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) -- [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) -- [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) - -## Hosted Kubernetes Provider Authentication - -When using Rancher to create a cluster hosted by a provider, you are prompted for authentication information. This information is required to access the provider's API. For more information on how to obtain this information, see the following procedures: - -- [Creating a GKE Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/gke) -- [Creating an EKS Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/eks) -- [Creating an AKS Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks) -- [Creating an ACK Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/ack) -- [Creating a TKE Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/tke) -- [Creating a CCE Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/cce) diff --git a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/tke/tke.md b/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/tke/tke.md deleted file mode 100644 index 7b4f92bd0ea..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/hosted-kubernetes-clusters/tke/tke.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster -shortTitle: Tencent Kubernetes Engine -weight: 2125 ---- - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver]({{}}/rancher/v2.6/en/admin-settings/drivers/cluster-drivers/) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver]({{}}/rancher/v2.6/en/admin-settings/drivers/cluster-drivers/#activating-deactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -# Prerequisites in Tencent - ->**Note** ->Deploying to TKE will incur charges. - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -# Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -# Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - **Note:** If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#config-file-structure-in-rancher-v2-3-0) - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.6/cluster-provisioning/node-requirements/node-requirements.md b/versioned_docs/version-2.6/cluster-provisioning/node-requirements/node-requirements.md deleted file mode 100644 index ba600ef51a1..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/node-requirements/node-requirements.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Node Requirements for Rancher Managed Clusters -weight: 1 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This page describes the requirements for the Rancher managed Kubernetes clusters where your apps and services will be installed. These downstream clusters should be separate from the three-node cluster running Rancher. - -> If Rancher is installed on a high-availability Kubernetes cluster, the Rancher server three-node cluster and downstream clusters have different requirements. For Rancher installation requirements, refer to the node requirements in the [installation section.]({{}}/rancher/v2.6/en/installation/requirements/) - -Make sure the nodes for the Rancher server fulfill the following requirements: - -- [Operating systems and container runtime requirements](#operating-systems-and-container-runtime-requirements) -- [Hardware Requirements](#hardware-requirements) -- [Networking Requirements](#networking-requirements) -- [Optional: Security Considerations](#optional-security-considerations) - -# Operating Systems and Container Runtime Requirements - -Rancher should work with any modern Linux distribution and any modern Docker version. Linux is required for the etcd and controlplane nodes of all downstream clusters. Worker nodes may run Linux or [Windows Server.](#windows-nodes) - -For details on which OS and Docker versions were tested with each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) - -All supported operating systems are 64-bit x86. - -If you plan to use ARM64, see [Running on ARM64 (Experimental).]({{}}/rancher/v2.6/en/installation/resources/advanced/arm64-platform/) - -For information on how to install Docker, refer to the official [Docker documentation.](https://docs.docker.com/) - -### Oracle Linux and RHEL Derived Linux Nodes - -Some distributions of Linux derived from RHEL, including Oracle Linux, may have default firewall rules that block communication with Helm. We recommend disabling firewalld. For Kubernetes 1.19, firewalld must be turned off. - ->**Note:** In RHEL 8.4, two extra services are included on the NetworkManager: `nm-cloud-setup.service` and `nm-cloud-setup.timer`. These services add a routing table that interferes with the CNI plugin's configuration. If these services are enabled, you must disable them using the command below, and then reboot the node to restore connectivity: -> -> ``` - systemctl disable nm-cloud-setup.service nm-cloud-setup.timer - reboot - ``` - -### SUSE Linux Nodes - -SUSE Linux may have a firewall that blocks all ports by default. In that situation, follow [these steps]({{}}/rancher/v2.6/en/installation/requirements/ports/#opening-suse-linux-ports) to open the ports needed for adding a host to a custom cluster. - -### Flatcar Container Linux Nodes - -When [Launching Kubernetes with Rancher]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) using Flatcar Container Linux nodes, it is required to use the following configuration in the [Cluster Config File]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) - - - - -```yaml -rancher_kubernetes_engine_config: - network: - plugin: canal - options: - canal_flex_volume_plugin_dir: /opt/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds - flannel_backend_type: vxlan - - services: - kube-controller: - extra_args: - flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/ -``` - - - - -```yaml -rancher_kubernetes_engine_config: - network: - plugin: calico - options: - calico_flex_volume_plugin_dir: /opt/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds - flannel_backend_type: vxlan - - services: - kube-controller: - extra_args: - flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/ -``` - - - - -It is also required to enable the Docker service, you can enable the Docker service using the following command: - -``` -systemctl enable docker.service -``` - -The Docker service is enabled automatically when using [Node Drivers]({{}}/rancher/v2.6/en/admin-settings/drivers/#node-drivers). - -### Windows Nodes - -Nodes with Windows Server must run Docker Enterprise Edition. - -Windows nodes can be used for worker nodes only. See [Configuring Custom Clusters for Windows]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/) - -# Hardware Requirements - -The hardware requirements for nodes with the `worker` role mostly depend on your workloads. The minimum to run the Kubernetes node components is 1 CPU (core) and 1GB of memory. - -Regarding CPU and memory, it is recommended that the different planes of Kubernetes clusters (etcd, controlplane, and workers) should be hosted on different nodes so that they can scale separately from each other. - -For hardware recommendations for large Kubernetes clusters, refer to the official Kubernetes documentation on [building large clusters.](https://kubernetes.io/docs/setup/best-practices/cluster-large/) - -For hardware recommendations for etcd clusters in production, refer to the official [etcd documentation.](https://etcd.io/docs/v3.4.0/op-guide/hardware/) - -# Networking Requirements - -For a production cluster, we recommend that you restrict traffic by opening only the ports defined in the port requirements below. - -The ports required to be open are different depending on how the user cluster is launched. Each of the sections below list the ports that need to be opened for different [cluster creation options]({{}}/rancher/v2.6/en/cluster-provisioning/). - -For a breakdown of the port requirements for etcd nodes, controlplane nodes, and worker nodes in a Kubernetes cluster, refer to the [port requirements for the Rancher Kubernetes Engine.]({{}}/rke/latest/en/os/#ports) - -Details on which ports are used in each situation are found under [Downstream Cluster Port Requirements]({{}}/rancher/v2.6/en/installation/requirements/ports#downstream-kubernetes-cluster-nodes). - -# Optional: Security Considerations - -If you want to provision a Kubernetes cluster that is compliant with the CIS (Center for Internet Security) Kubernetes Benchmark, we recommend to following our hardening guide to configure your nodes before installing Kubernetes. - -For more information on the hardening guide and details on which version of the guide corresponds to your Rancher and Kubernetes versions, refer to the [security section.]({{}}/rancher/v2.6/en/security/#rancher-hardening-guide) diff --git a/versioned_docs/version-2.6/cluster-provisioning/production/nodes-and-roles/nodes-and-roles.md b/versioned_docs/version-2.6/cluster-provisioning/production/nodes-and-roles/nodes-and-roles.md deleted file mode 100644 index c073cdb4388..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/production/nodes-and-roles/nodes-and-roles.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Roles for Nodes in Kubernetes -weight: 1 ---- - -This section describes the roles for etcd nodes, controlplane nodes, and worker nodes in Kubernetes, and how the roles work together in a cluster. - -This diagram is applicable to Kubernetes clusters [launched with Rancher using RKE.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/). - -![Cluster diagram]({{}}/img/rancher/clusterdiagram.svg)
-Lines show the traffic flow between components. Colors are used purely for visual aid - -# etcd - -Nodes with the `etcd` role run etcd, which is a consistent and highly available key value store used as Kubernetes’ backing store for all cluster data. etcd replicates the data to each node. - ->**Note:** Nodes with the `etcd` role are shown as `Unschedulable` in the UI, meaning no pods will be scheduled to these nodes by default. - -# controlplane - -Nodes with the `controlplane` role run the Kubernetes master components (excluding `etcd`, as it's a separate role). See [Kubernetes: Master Components](https://kubernetes.io/docs/concepts/overview/components/#master-components) for a detailed list of components. - ->**Note:** Nodes with the `controlplane` role are shown as `Unschedulable` in the UI, meaning no pods will be scheduled to these nodes by default. - -### kube-apiserver - -The Kubernetes API server (`kube-apiserver`) scales horizontally. Each node with the role `controlplane` will be added to the NGINX proxy on the nodes with components that need to access the Kubernetes API server. This means that if a node becomes unreachable, the local NGINX proxy on the node will forward the request to another Kubernetes API server in the list. - -### kube-controller-manager - -The Kubernetes controller manager uses leader election using an endpoint in Kubernetes. One instance of the `kube-controller-manager` will create an entry in the Kubernetes endpoints and updates that entry in a configured interval. Other instances will see an active leader and wait for that entry to expire (for example, when a node is unresponsive). - -### kube-scheduler - -The Kubernetes scheduler uses leader election using an endpoint in Kubernetes. One instance of the `kube-scheduler` will create an entry in the Kubernetes endpoints and updates that entry in a configured interval. Other instances will see an active leader and wait for that entry to expire (for example, when a node is unresponsive). - -# worker - -Nodes with the `worker` role run the Kubernetes node components. See [Kubernetes: Node Components](https://kubernetes.io/docs/concepts/overview/components/#node-components) for a detailed list of components. - -# References - -* [Kubernetes: Node Components](https://kubernetes.io/docs/concepts/overview/components/#node-components) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/production/production.md b/versioned_docs/version-2.6/cluster-provisioning/production/production.md deleted file mode 100644 index c0c61b54f01..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/production/production.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Checklist for Production-Ready Clusters -weight: 2 ---- - -In this section, we recommend best practices for creating the production-ready Kubernetes clusters that will run your apps and services. - -For a list of requirements for your cluster, including the requirements for OS/Docker, hardware, and networking, refer to the section on [node requirements.]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements) - -This is a shortlist of best practices that we strongly recommend for all production clusters. - -For a full list of all the best practices that we recommend, refer to the [best practices section.]({{}}/rancher/v2.6/en/best-practices) - -### Node Requirements - -* Make sure your nodes fulfill all of the [node requirements,]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/) including the port requirements. - -### Back up etcd - -* Enable etcd snapshots. Verify that snapshots are being created, and run a disaster recovery scenario to verify the snapshots are valid. etcd is the location where the state of your cluster is stored, and losing etcd data means losing your cluster. Make sure you configure recurring snapshots of etcd for your cluster(s), and make sure the snapshots are stored externally (off the node) as well. - -### Cluster Architecture - -* Nodes should have one of the following role configurations: - * `etcd` - * `controlplane` - * `etcd` and `controlplane` - * `worker` (the `worker` role should not be used or added on nodes with the `etcd` or `controlplane` role) -* Have at least three nodes with the role `etcd` to survive losing one node. Increase this count for higher node fault toleration, and spread them across (availability) zones to provide even better fault tolerance. -* Assign two or more nodes the `controlplane` role for master component high availability. -* Assign two or more nodes the `worker` role for workload rescheduling upon node failure. - -For more information on what each role is used for, refer to the [section on roles for nodes in Kubernetes.]({{}}/rancher/v2.6/en/cluster-provisioning/production/nodes-and-roles) - -For more information about the -number of nodes for each Kubernetes role, refer to the section on [recommended architecture.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/) - -### Logging and Monitoring - -* Configure alerts/notifiers for Kubernetes components (System Service). -* Configure logging for cluster analysis and post-mortems. - -### Reliability - -* Perform load tests on your cluster to verify that its hardware can support your workloads. - -### Networking - -* Minimize network latency. Rancher recommends minimizing latency between the etcd nodes. The default setting for `heartbeat-interval` is `500`, and the default setting for `election-timeout` is `5000`. These [settings for etcd tuning](https://coreos.com/etcd/docs/latest/tuning.html) allow etcd to run in most networks (except really high latency networks). -* Cluster nodes should be located within a single region. Most cloud providers provide multiple availability zones within a region, which can be used to create higher availability for your cluster. Using multiple availability zones is fine for nodes with any role. If you are using [Kubernetes Cloud Provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) resources, consult the documentation for any restrictions (i.e. zone storage restrictions). diff --git a/versioned_docs/version-2.6/cluster-provisioning/production/recommended-architecture/recommended-architecture.md b/versioned_docs/version-2.6/cluster-provisioning/production/recommended-architecture/recommended-architecture.md deleted file mode 100644 index f9d4eb5e427..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/production/recommended-architecture/recommended-architecture.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Recommended Cluster Architecture -weight: 1 ---- - -There are three roles that can be assigned to nodes: `etcd`, `controlplane` and `worker`. - -# Separating Worker Nodes from Nodes with Other Roles - -When designing your cluster(s), you have two options: - -* Use dedicated nodes for each role. This ensures resource availability for the components needed for the specified role. It also strictly isolates network traffic between each of the roles according to the [port requirements]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements). -* Assign the `etcd` and `controlplane` roles to the same nodes. These nodes must meet the hardware requirements for both roles. - -In either case, the `worker` role should not be used or added to nodes with the `etcd` or `controlplane` role. - -Therefore, each node should have one of the following role configurations: - - * `etcd` - * `controlplane` - * Both `etcd` and `controlplane` - * `worker` - -# Recommended Number of Nodes with Each Role - -The cluster should have: - -- At least three nodes with the role `etcd` to survive losing one node. Increase this count for higher node fault toleration, and spread them across (availability) zones to provide even better fault tolerance. -- At least two nodes with the role `controlplane` for master component high availability. -- At least two nodes with the role `worker` for workload rescheduling upon node failure. - -For more information on what each role is used for, refer to the [section on roles for nodes in Kubernetes.]({{}}/rancher/v2.6/en/cluster-provisioning/production/nodes-and-roles) - - -### Number of Controlplane Nodes - -Adding more than one node with the `controlplane` role makes every master component highly available. - -### Number of etcd Nodes - -The number of nodes that you can lose at once while maintaining cluster availability is determined by the number of nodes assigned the `etcd` role. For a cluster with n members, the minimum is (n/2)+1. Therefore, we recommend creating an `etcd` node in 3 different availability zones within a region to survive the loss of one availability zone. If you use only two zones, you can only survive the loss of the zone where you don't lose the majority of nodes. - -| Nodes with `etcd` role | Majority | Failure Tolerance | -|--------------|------------|-------------------| -| 1 | 1 | 0 | -| 2 | 2 | 0 | -| 3 | 2 | **1** | -| 4 | 3 | 1 | -| 5 | 3 | **2** | -| 6 | 4 | 2 | -| 7 | 4 | **3** | -| 8 | 5 | 3 | -| 9 | 5 | **4** | - -References: - -* [Official etcd documentation on optimal etcd cluster size](https://etcd.io/docs/v3.4.0/faq/#what-is-failure-tolerance) -* [Official Kubernetes documentation on operating etcd clusters for Kubernetes](https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/) - -### Number of Worker Nodes - -Adding more than one node with the `worker` role will make sure your workloads can be rescheduled if a node fails. - -### Why Production Requirements are Different for the Rancher Cluster and the Clusters Running Your Applications - -You may have noticed that our [Kubernetes Install]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) instructions do not meet our definition of a production-ready cluster, as there are no dedicated nodes for the `worker` role. However, for your Rancher installation, this three node cluster is valid, because: - -* It allows one `etcd` node failure. -* It maintains multiple instances of the master components by having multiple `controlplane` nodes. -* No other workloads than Rancher itself should be created on this cluster. - -# References - -* [Kubernetes: Master Components](https://kubernetes.io/docs/concepts/overview/components/#master-components) diff --git a/versioned_docs/version-2.6/cluster-provisioning/registered-clusters/registered-clusters.md b/versioned_docs/version-2.6/cluster-provisioning/registered-clusters/registered-clusters.md deleted file mode 100644 index 5bcc0cc73f0..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/registered-clusters/registered-clusters.md +++ /dev/null @@ -1,288 +0,0 @@ ---- -title: Registering Existing Clusters -weight: 6 ---- - -The cluster registration feature replaced the feature to import clusters. - -The control that Rancher has to manage a registered cluster depends on the type of cluster. For details, see [Management Capabilities for Registered Clusters.](#management-capabilities-for-registered-clusters) - -- [Prerequisites](#prerequisites) -- [Registering a Cluster](#registering-a-cluster) -- [Management Capabilities for Registered Clusters](#management-capabilities-for-registered-clusters) -- [Configuring K3s Cluster Upgrades](#configuring-k3s-cluster-upgrades) -- [Debug Logging and Troubleshooting for Registered K3s Clusters](#debug-logging-and-troubleshooting-for-registered-k3s-clusters) -- [Authorized Cluster Endpoint Support for RKE2 and K3s Clusters](#authorized-cluster-endpoint-support-for-rke2-and-k3s-clusters) -- [Annotating Registered Clusters](#annotating-registered-clusters) - -# Prerequisites - -### Kubernetes Node Roles - -Registered RKE Kubernetes clusters must have all three node roles - etcd, controlplane and worker. A cluster with only controlplane components cannot be registered in Rancher. - -For more information on RKE node roles, see the [best practices.]({{}}/rancher/v2.6/en/cluster-provisioning/production/#cluster-architecture) - -### Permissions - -If your existing Kubernetes cluster already has a `cluster-admin` role defined, you must have this `cluster-admin` privilege to register the cluster in Rancher. - -In order to apply the privilege, you need to run: - -```plain -kubectl create clusterrolebinding cluster-admin-binding \ - --clusterrole cluster-admin \ - --user [USER_ACCOUNT] -``` - -before running the `kubectl` command to register the cluster. - -By default, GKE users are not given this privilege, so you will need to run the command before registering GKE clusters. To learn more about role-based access control for GKE, please click [here](https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control). - -If you are registering a K3s cluster, make sure the `cluster.yml` is readable. It is protected by default. For details, refer to [Configuring a K3s cluster to enable importation to Rancher.](#configuring-a-k3s-cluster-to-enable-registration-in-rancher) - -### EKS Clusters - -EKS clusters must have at least one managed node group to be imported into Rancher or provisioned from Rancher successfully. - -# Registering a Cluster - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, **Import Existing**. -1. Choose the type of cluster. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. If you are importing a generic Kubernetes cluster in Rancher, perform the following steps for setup:
- a. Click **Agent Environment Variables** under **Cluster Options** to set environment variables for [rancher cluster agent]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/rancher-agents/). The environment variables can be set using key value pairs. If rancher agent requires use of proxy to communicate with Rancher server, `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables can be set using agent environment variables.
- b. Enable Project Network Isolation to ensure the cluster supports Kubernetes `NetworkPolicy` resources. Users can select the **Project Network Isolation** option under the **Advanced Options** dropdown to do so. -1. Click **Create**. -1. The prerequisite for `cluster-admin` privileges is shown (see **Prerequisites** above), including an example command to fulfil the prerequisite. -1. Copy the `kubectl` command to your clipboard and run it on a node where kubeconfig is configured to point to the cluster you want to import. If you are unsure it is configured correctly, run `kubectl get nodes` to verify before running the command shown in Rancher. -1. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import. -1. When you finish running the command(s) on your node, click **Done**. - -**Result:** - -- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster. -- You can access your cluster after its state is updated to **Active**. -- **Active** clusters are assigned two Projects: `Default` (containing the namespace `default`) and `System` (containing the namespaces `cattle-system`, `ingress-nginx`, `kube-public` and `kube-system`, if present). - - -> **Note:** -> You can not re-register a cluster that is currently active in a Rancher setup. - -### Configuring a K3s Cluster to Enable Registration in Rancher - -The K3s server needs to be configured to allow writing to the kubeconfig file. - -This can be accomplished by passing `--write-kubeconfig-mode 644` as a flag during installation: - -``` -$ curl -sfL https://get.k3s.io | sh -s - --write-kubeconfig-mode 644 -``` - -The option can also be specified using the environment variable `K3S_KUBECONFIG_MODE`: - -``` -$ curl -sfL https://get.k3s.io | K3S_KUBECONFIG_MODE="644" sh -s - -``` - -### Configuring an Imported EKS Cluster with Terraform - -You should define **only** the minimum fields that Rancher requires when importing an EKS cluster with Terraform. This is important as Rancher will overwrite what was in the EKS cluster with any config that the user has provided. - ->**Warning:** Even a small difference between the current EKS cluster and a user-provided config could have unexpected results. - -The minimum config fields required by Rancher to import EKS clusters with Terraform using `eks_config_v2` are as follows: - -- cloud_credential_id -- name -- region -- imported (this field should always be set to `true` for imported clusters) - -Example YAML configuration for imported EKS clusters: - -``` -resource "rancher2_cluster" "my-eks-to-import" { - name = "my-eks-to-import" - description = "Terraform EKS Cluster" - eks_config_v2 { - cloud_credential_id = rancher2_cloud_credential.aws.id - name = var.aws_eks_name - region = var.aws_region - imported = true - } -} -``` - -# Management Capabilities for Registered Clusters - -The control that Rancher has to manage a registered cluster depends on the type of cluster. - -- [Features for All Registered Clusters](#2-5-8-features-for-all-registered-clusters) -- [Additional Features for Registered K3s Clusters](#2-5-8-additional-features-for-registered-k3s-clusters) -- [Additional Features for Registered EKS and GKE Clusters](#additional-features-for-registered-eks-and-gke-clusters) - -### Features for All Registered Clusters - -After registering a cluster, the cluster owner can: - -- [Manage cluster access]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/) through role-based access control -- Enable [monitoring, alerts and notifiers]({{}}/rancher/v2.6/en/monitoring-alerting/) -- Enable [logging]({{}}/rancher/v2.6/en/logging/) -- Enable [Istio]({{}}/rancher/v2.6/en/istio/) -- Use [pipelines]({{}}/rancher/v2.6/en/project-admin/pipelines/) -- Manage projects and workloads - -### Additional Features for Registered K3s Clusters - -[K3s]({{}}/k3s/latest/en/) is a lightweight, fully compliant Kubernetes distribution. - -When a K3s cluster is registered in Rancher, Rancher will recognize it as K3s. The Rancher UI will expose the features for [all registered clusters,](#features-for-all-registered-clusters) in addition to the following features for editing and upgrading the cluster: - -- The ability to [upgrade the K3s version]({{}}/rancher/v2.6/en/cluster-admin/upgrading-kubernetes/) -- The ability to configure the maximum number of nodes that will be upgraded concurrently -- The ability to see a read-only version of the K3s cluster's configuration arguments and environment variables used to launch each node in the cluster - -### Additional Features for Registered EKS and GKE Clusters - -Registering an Amazon EKS cluster or GKE cluster allows Rancher to treat it as though it were created in Rancher. - -Amazon EKS clusters and GKE clusters can now be registered in Rancher. For the most part, these registered clusters are treated the same way as clusters created in the Rancher UI, except for deletion. - -When you delete an EKS cluster or GKE cluster that was created in Rancher, the cluster is destroyed. When you delete a cluster that was registered in Rancher, it is disconnected from the Rancher server, but it still exists and you can still access it in the same way you did before it was registered in Rancher. - -The capabilities for registered clusters are listed in the table on [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/) - -# Configuring K3s Cluster Upgrades - -> It is a Kubernetes best practice to back up the cluster before upgrading. When upgrading a high-availability K3s cluster with an external database, back up the database in whichever way is recommended by the relational database provider. - -The **concurrency** is the maximum number of nodes that are permitted to be unavailable during an upgrade. If number of unavailable nodes is larger than the **concurrency,** the upgrade will fail. If an upgrade fails, you may need to repair or remove failed nodes before the upgrade can succeed. - -- **Controlplane concurrency:** The maximum number of server nodes to upgrade at a single time; also the maximum unavailable server nodes -- **Worker concurrency:** The maximum number worker nodes to upgrade at the same time; also the maximum unavailable worker nodes - -In the K3s documentation, controlplane nodes are called server nodes. These nodes run the Kubernetes master, which maintains the desired state of the cluster. In K3s, these controlplane nodes have the capability to have workloads scheduled to them by default. - -Also in the K3s documentation, nodes with the worker role are called agent nodes. Any workloads or pods that are deployed in the cluster can be scheduled to these nodes by default. - -# Debug Logging and Troubleshooting for Registered K3s Clusters - -Nodes are upgraded by the system upgrade controller running in the downstream cluster. Based on the cluster configuration, Rancher deploys two [plans](https://github.com/rancher/system-upgrade-controller#example-upgrade-plan) to upgrade K3s nodes: one for controlplane nodes and one for workers. The system upgrade controller follows the plans and upgrades the nodes. - -To enable debug logging on the system upgrade controller deployment, edit the [configmap](https://github.com/rancher/system-upgrade-controller/blob/50a4c8975543d75f1d76a8290001d87dc298bdb4/manifests/system-upgrade-controller.yaml#L32) to set the debug environment variable to true. Then restart the `system-upgrade-controller` pod. - -Logs created by the `system-upgrade-controller` can be viewed by running this command: - -``` -kubectl logs -n cattle-system system-upgrade-controller -``` - -The current status of the plans can be viewed with this command: - -``` -kubectl get plans -A -o yaml -``` - -If the cluster becomes stuck in upgrading, restart the `system-upgrade-controller`. - -To prevent issues when upgrading, the [Kubernetes upgrade best practices](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) should be followed. - -# Authorized Cluster Endpoint Support for RKE2 and K3s Clusters - -_Available as of v2.6.3_ - -Authorized Cluster Endpoint (ACE) support has been added for registered RKE2 and K3s clusters. This support includes manual steps you will perform on the downstream cluster to enable the ACE. For additional information on the authorized cluster endpoint, click [here]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/ace/). - -> **Note:** -> -> - These steps only need to be performed on the control plane nodes of the downstream cluster. You must configure each control plane node individually. -> -> - The following steps will work on both RKE2 and K3s clusters registered in v2.6.x as well as those registered (or imported) from a previous version of Rancher with an upgrade to v2.6.x. -> -> - These steps will alter the configuration of the downstream RKE2 and K3s clusters and deploy the `kube-api-authn-webhook`. If a future implementation of the ACE requires an update to the `kube-api-authn-webhook`, then this would also have to be done manually. For more information on this webhook, click [here]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/ace/#about-the-kube-api-auth-authentication-webhook). - -###### **Manual steps to be taken on the control plane of each downstream cluster to enable ACE:** - -1. Create a file at `/var/lib/rancher/{rke2,k3s}/kube-api-authn-webhook.yaml` with the following contents: - - apiVersion: v1 - kind: Config - clusters: - - name: Default - cluster: - insecure-skip-tls-verify: true - server: http://127.0.0.1:6440/v1/authenticate - users: - - name: Default - user: - insecure-skip-tls-verify: true - current-context: webhook - contexts: - - name: webhook - context: - user: Default - cluster: Default - -1. Add the following to the config file (or create one if it doesn’t exist); note that the default location is `/etc/rancher/{rke2,k3s}/config.yaml`: - - kube-apiserver-arg: - - authentication-token-webhook-config-file=/var/lib/rancher/{rke2,k3s}/kube-api-authn-webhook.yaml - -1. Run the following commands: - - sudo systemctl stop {rke2,k3s}-server - sudo systemctl start {rke2,k3s}-server - -1. Finally, you **must** go back to the Rancher UI and edit the imported cluster there to complete the ACE enablement. Click on **⋮ > Edit Config**, then click the **Networking** tab under Cluster Configuration. Finally, click the **Enabled** button for **Authorized Endpoint**. Once the ACE is enabled, you then have the option of entering a fully qualified domain name (FQDN) and certificate information. - - >**Note:** The FQDN field is optional, and if one is entered, it should point to the downstream cluster. Certificate information is only needed if there is a load balancer in front of the downstream cluster that is using an untrusted certificate. If you have a valid certificate, then nothing needs to be added to the CA Certificates field. - -# Annotating Registered Clusters - -For all types of registered Kubernetes clusters except for K3s Kubernetes clusters, Rancher doesn't have any information about how the cluster is provisioned or configured. - -Therefore, when Rancher registers a cluster, it assumes that several capabilities are disabled by default. Rancher assumes this in order to avoid exposing UI options to the user even when the capabilities are not enabled in the registered cluster. - -However, if the cluster has a certain capability, such as the ability to use a pod security policy, a user of that cluster might still want to select pod security policies for the cluster in the Rancher UI. In order to do that, the user will need to manually indicate to Rancher that pod security policies are enabled for the cluster. - -By annotating a registered cluster, it is possible to indicate to Rancher that a cluster was given a pod security policy, or another capability, outside of Rancher. - -This example annotation indicates that a pod security policy is enabled: - -``` -"capabilities.cattle.io/pspEnabled": "true" -``` - -The following annotation indicates Ingress capabilities. Note that that the values of non-primitive objects need to be JSON encoded, with quotations escaped. - -``` -"capabilities.cattle.io/ingressCapabilities": "[ - { - "customDefaultBackend":true, - "ingressProvider":"asdf" - } -]" -``` - -These capabilities can be annotated for the cluster: - -- `ingressCapabilities` -- `loadBalancerCapabilities` -- `nodePoolScalingSupported` -- `nodePortRange` -- `pspEnabled` -- `taintSupport` - -All the capabilities and their type definitions can be viewed in the Rancher API view, at `[Rancher Server URL]/v3/schemas/capabilities`. - -To annotate a registered cluster, - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the custom cluster you want to annotate and click **⋮ > Edit Config**. -1. Expand the **Labels & Annotations** section. -1. Click **Add Annotation**. -1. Add an annotation to the cluster with the format `capabilities/: ` where `value` is the cluster capability that will be overridden by the annotation. In this scenario, Rancher is not aware of any capabilities of the cluster until you add the annotation. -1. Click **Save**. - -**Result:** The annotation does not give the capabilities to the cluster, but it does indicate to Rancher that the cluster has those capabilities. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/behavior-differences-between-rke1-and-rke2.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/behavior-differences-between-rke1-and-rke2.md deleted file mode 100644 index 99a3f18f370..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/behavior-differences-between-rke1-and-rke2.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Behavior Differences Between RKE1 and RKE2 -weight: 2450 ---- - -RKE2, also known as RKE Government, is a Kubernetes distribution that focuses on security and compliance for U.S. Federal Government entities. It is considered the next iteration of the Rancher Kubernetes Engine, now known as RKE1. - -RKE1 and RKE2 have several slight behavioral differences to note, and this page will highlight some of these at a high level. - -### Control Plane Components - -RKE1 uses Docker for deploying and managing control plane components, and it also uses Docker as the container runtime for Kubernetes. By contrast, RKE2 launches control plane components as static pods that are managed by the kubelet. RKE2's container runtime is containerd, which allows things such as container registry mirroring (RKE1 with Docker does not). - -### Cluster API - -RKE2/K3s provisioning is built on top of the Cluster API (CAPI) upstream framework which often makes RKE2-provisioned clusters behave differently than RKE1-provisioned clusters. - -When you make changes to your cluster configuration in RKE2, this **may** result in nodes reprovisioning. This is controlled by CAPI controllers and not by Rancher itself. Note that for etcd nodes, the same behavior does not apply. - -The following are some specific example configuration changes that may cause the described behavior: - -- When editing the cluster and enabling `drain before delete`, the existing control plane nodes and worker are deleted and new nodes are created. - -- When nodes are being provisioned and a scale down operation is performed, rather than scaling down the desired number of nodes, it is possible that the currently provisioning nodes get deleted and new nodes are provisioned to reach the desired node count. Please note that this is a bug in Cluster API, and it will be fixed in an upcoming release. Once fixed, Rancher will update the documentation. - -Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected. - -### Terminology - -You will notice that some terms have changed or gone away going from RKE1 to RKE2. For example, in RKE1 provisioning, you use **node templates**; in RKE2 provisioning, you can configure your cluster node pools when creating or editing the cluster. Another example is that the term **node pool** in RKE1 is now known as **machine pool** in RKE2. - - - - diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/amazon/amazon.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/amazon/amazon.md deleted file mode 100644 index b8582ef3535..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/amazon/amazon.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Setting up the Amazon Cloud Provider -weight: 1 ---- - -When using the `Amazon` cloud provider, you can leverage the following capabilities: - -- **Load Balancers:** Launches an AWS Elastic Load Balancer (ELB) when choosing `Layer-4 Load Balancer` in **Port Mapping** or when launching a `Service` with `type: LoadBalancer`. -- **Persistent Volumes**: Allows you to use AWS Elastic Block Stores (EBS) for persistent volumes. - -See [cloud-provider-aws README](https://kubernetes.github.io/cloud-provider-aws/) for all information regarding the Amazon cloud provider. - -To set up the Amazon cloud provider, - -1. [Create an IAM role and attach to the instances](#1-create-an-iam-role-and-attach-to-the-instances) -2. [Configure the ClusterID](#2-configure-the-clusterid) - -### 1. Create an IAM Role and attach to the instances - -All nodes added to the cluster must be able to interact with EC2 so that they can create and remove resources. You can enable this interaction by using an IAM role attached to the instance. See [Amazon documentation: Creating an IAM Role](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#create-iam-role) how to create an IAM role. There are two example policies: - -* The first policy is for the nodes with the `controlplane` role. These nodes have to be able to create/remove EC2 resources. The following IAM policy is an example, please remove any unneeded permissions for your use case. -* The second policy is for the nodes with the `etcd` or `worker` role. These nodes only have to be able to retrieve information from EC2. - -While creating an [Amazon EC2 cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/), you must fill in the **IAM Instance Profile Name** (not ARN) of the created IAM role when creating the **Node Template**. - -While creating a [Custom cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes), you must manually attach the IAM role to the instance(s). - -IAM Policy for nodes with the `controlplane` role: - -```json -{ -"Version": "2012-10-17", -"Statement": [ - { - "Effect": "Allow", - "Action": [ - "autoscaling:DescribeAutoScalingGroups", - "autoscaling:DescribeLaunchConfigurations", - "autoscaling:DescribeTags", - "ec2:DescribeInstances", - "ec2:DescribeRegions", - "ec2:DescribeRouteTables", - "ec2:DescribeSecurityGroups", - "ec2:DescribeSubnets", - "ec2:DescribeVolumes", - "ec2:CreateSecurityGroup", - "ec2:CreateTags", - "ec2:CreateVolume", - "ec2:ModifyInstanceAttribute", - "ec2:ModifyVolume", - "ec2:AttachVolume", - "ec2:AuthorizeSecurityGroupIngress", - "ec2:CreateRoute", - "ec2:DeleteRoute", - "ec2:DeleteSecurityGroup", - "ec2:DeleteVolume", - "ec2:DetachVolume", - "ec2:RevokeSecurityGroupIngress", - "ec2:DescribeVpcs", - "elasticloadbalancing:AddTags", - "elasticloadbalancing:AttachLoadBalancerToSubnets", - "elasticloadbalancing:ApplySecurityGroupsToLoadBalancer", - "elasticloadbalancing:CreateLoadBalancer", - "elasticloadbalancing:CreateLoadBalancerPolicy", - "elasticloadbalancing:CreateLoadBalancerListeners", - "elasticloadbalancing:ConfigureHealthCheck", - "elasticloadbalancing:DeleteLoadBalancer", - "elasticloadbalancing:DeleteLoadBalancerListeners", - "elasticloadbalancing:DescribeLoadBalancers", - "elasticloadbalancing:DescribeLoadBalancerAttributes", - "elasticloadbalancing:DetachLoadBalancerFromSubnets", - "elasticloadbalancing:DeregisterInstancesFromLoadBalancer", - "elasticloadbalancing:ModifyLoadBalancerAttributes", - "elasticloadbalancing:RegisterInstancesWithLoadBalancer", - "elasticloadbalancing:SetLoadBalancerPoliciesForBackendServer", - "elasticloadbalancing:AddTags", - "elasticloadbalancing:CreateListener", - "elasticloadbalancing:CreateTargetGroup", - "elasticloadbalancing:DeleteListener", - "elasticloadbalancing:DeleteTargetGroup", - "elasticloadbalancing:DescribeListeners", - "elasticloadbalancing:DescribeLoadBalancerPolicies", - "elasticloadbalancing:DescribeTargetGroups", - "elasticloadbalancing:DescribeTargetHealth", - "elasticloadbalancing:ModifyListener", - "elasticloadbalancing:ModifyTargetGroup", - "elasticloadbalancing:RegisterTargets", - "elasticloadbalancing:SetLoadBalancerPoliciesOfListener", - "iam:CreateServiceLinkedRole", - "kms:DescribeKey" - ], - "Resource": [ - "*" - ] - } -] -} -``` - -IAM policy for nodes with the `etcd` or `worker` role: - -```json -{ -"Version": "2012-10-17", -"Statement": [ - { - "Effect": "Allow", - "Action": [ - "ec2:DescribeInstances", - "ec2:DescribeRegions", - "ecr:GetAuthorizationToken", - "ecr:BatchCheckLayerAvailability", - "ecr:GetDownloadUrlForLayer", - "ecr:GetRepositoryPolicy", - "ecr:DescribeRepositories", - "ecr:ListImages", - "ecr:BatchGetImage" - ], - "Resource": "*" - } -] -} -``` - -### 2. Configure the ClusterID - -The following resources need to tagged with a `ClusterID`: - -- **Nodes**: All hosts added in Rancher. -- **Subnet**: The subnet used for your cluster. -- **Security Group**: The security group used for your cluster. - ->**Note:** Do not tag multiple security groups. Tagging multiple groups generates an error when creating an Elastic Load Balancer (ELB). - -When you create an [Amazon EC2 Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/), the `ClusterID` is automatically configured for the created nodes. Other resources still need to be tagged manually. - -Use the following tag: - -**Key** = `kubernetes.io/cluster/CLUSTERID` **Value** = `owned` - -`CLUSTERID` can be any string you like, as long as it is equal across all tags set. - -Setting the value of the tag to `owned` tells the cluster that all resources with this tag are owned and managed by this cluster. If you share resources between clusters, you can change the tag to: - -**Key** = `kubernetes.io/cluster/CLUSTERID` **Value** = `shared`. - -### Using Amazon Elastic Container Registry (ECR) - -The kubelet component has the ability to automatically obtain ECR credentials, when the IAM profile mentioned in [Create an IAM Role and attach to the instances](#1-create-an-iam-role-and-attach-to-the-instances) is attached to the instance(s). When using a Kubernetes version older than v1.15.0, the Amazon cloud provider needs be configured in the cluster. Starting with Kubernetes version v1.15.0, the kubelet can obtain ECR credentials without having the Amazon cloud provider configured in the cluster. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/azure/azure.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/azure/azure.md deleted file mode 100644 index a6e80db75db..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/azure/azure.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: Setting up the Azure Cloud Provider -weight: 2 ---- - -When using the `Azure` cloud provider, you can leverage the following capabilities: - -- **Load Balancers:** Launches an Azure Load Balancer within a specific Network Security Group. - -- **Persistent Volumes:** Supports using Azure Blob disks and Azure Managed Disks with standard and premium storage accounts. - -- **Network Storage:** Support Azure Files via CIFS mounts. - -The following account types are not supported for Azure Subscriptions: - -- Single tenant accounts (i.e. accounts with no subscriptions). -- Multi-subscription accounts. - -# Prerequisites for RKE and RKE2 - -To set up the Azure cloud provider for both RKE and RKE2, the following credentials need to be configured: - -1. [Set up the Azure Tenant ID](#1-set-up-the-azure-tenant-id) -2. [Set up the Azure Client ID and Azure Client Secret](#2-set-up-the-azure-client-id-and-azure-client-secret) -3. [Configure App Registration Permissions](#3-configure-app-registration-permissions) -4. [Set up Azure Network Security Group Name](#4-set-up-azure-network-security-group-name) - -### 1. Set up the Azure Tenant ID - -Visit [Azure portal](https://portal.azure.com), login and go to **Azure Active Directory** and select **Properties**. Your **Directory ID** is your **Tenant ID** (tenantID). - -If you want to use the Azure CLI, you can run the command `az account show` to get the information. - -### 2. Set up the Azure Client ID and Azure Client Secret - -Visit [Azure portal](https://portal.azure.com), login and follow the steps below to create an **App Registration** and the corresponding **Azure Client ID** (aadClientId) and **Azure Client Secret** (aadClientSecret). - -1. Select **Azure Active Directory**. -1. Select **App registrations**. -1. Select **New application registration**. -1. Choose a **Name**, select `Web app / API` as **Application Type** and a **Sign-on URL** which can be anything in this case. -1. Select **Create**. - -In the **App registrations** view, you should see your created App registration. The value shown in the column **APPLICATION ID** is what you need to use as **Azure Client ID**. - -The next step is to generate the **Azure Client Secret**: - -1. Open your created App registration. -1. In the **Settings** view, open **Keys**. -1. Enter a **Key description**, select an expiration time and select **Save**. -1. The generated value shown in the column **Value** is what you need to use as **Azure Client Secret**. This value will only be shown once. - -### 3. Configure App Registration Permissions - -The last thing you will need to do, is assign the appropriate permissions to your App registration. - -1. Go to **More services**, search for **Subscriptions** and open it. -1. Open **Access control (IAM)**. -1. Select **Add**. -1. For **Role**, select `Contributor`. -1. For **Select**, select your created App registration name. -1. Select **Save**. - -### 4. Set up Azure Network Security Group Name - -A custom Azure Network Security Group (securityGroupName) is needed to allow Azure Load Balancers to work. - -If you provision hosts using Rancher Machine Azure driver, you will need to edit them manually to assign them to this Network Security Group. - -You should already assign custom hosts to this Network Security Group during provisioning. - -Only hosts expected to be load balancer back ends need to be in this group. - -# RKE2 Cluster Set-up in Rancher - -1. Choose "Azure" from the Cloud Provider drop-down in the Cluster Configuration section. - -1. * Supply the Cloud Provider Configuration. Note that Rancher will automatically create a new Network Security Group, Resource Group, Availability Set, Subnet, and Virtual Network. If you already have some or all of these created, you will need to specify them before creating the cluster. - * You can click on "Show Advanced" to see more of these automatically generated names and update them if - necessary. Your Cloud Provider Configuration **must** match the fields in the Machine Pools section. If you have multiple pools, they must all use the same Resource Group, Availability Set, Subnet, Virtual Network, and Network Security Group. - * An example is provided below. You will modify it as needed. - -
- Example Cloud Provider Config - - ```yaml - { - "cloud":"AzurePublicCloud", - "tenantId": "YOUR TENANTID HERE", - "aadClientId": "YOUR AADCLIENTID HERE", - "aadClientSecret": "YOUR AADCLIENTSECRET HERE", - "subscriptionId": "YOUR SUBSCRIPTIONID HERE", - "resourceGroup": "docker-machine", - "location": "westus", - "subnetName": "docker-machine", - "securityGroupName": "rancher-managed-KA4jV9V2", - "securityGroupResourceGroup": "docker-machine", - "vnetName": "docker-machine-vnet", - "vnetResourceGroup": "docker-machine", - "primaryAvailabilitySetName": "docker-machine", - "routeTableResourceGroup": "docker-machine", - "cloudProviderBackoff": false, - "useManagedIdentityExtension": false, - "useInstanceMetadata": true - } - ``` - -
- -1. Under the **Cluster Configuration > Advanced** section, click **Add** under **Additional Controller Manager Args** and add this flag: `--configure-cloud-routes=false` - -1. Click the **Create** button to submit the form and create the cluster. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/cloud-providers.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/cloud-providers.md deleted file mode 100644 index bcb6f1d2089..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/cloud-providers.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Setting up Cloud Providers -weight: 2300 ---- -A _cloud provider_ is a module in Kubernetes that provides an interface for managing nodes, load balancers, and networking routes. - -When a cloud provider is set up in Rancher, the Rancher server can automatically provision new nodes, load balancers or persistent storage devices when launching Kubernetes definitions, if the cloud provider you're using supports such automation. - -Your cluster will not provision correctly if you configure a cloud provider cluster of nodes that do not meet the prerequisites. - -By default, the **Cloud Provider** option is set to `None`. - -The following cloud providers can be enabled: - -* Amazon -* Azure -* GCE (Google Compute Engine) -* vSphere - -### Setting up the Amazon Cloud Provider - -For details on enabling the Amazon cloud provider, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/amazon) - -### Setting up the Azure Cloud Provider - -For details on enabling the Azure cloud provider, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/azure) - -### Setting up the GCE Cloud Provider - -For details on enabling the Google Compute Engine cloud provider, refer to [this page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/gce) - -### Setting up the vSphere Cloud Provider - -For details on enabling the vSphere cloud provider, refer to [this page.](./vsphere) - -### Setting up a Custom Cloud Provider - -The `Custom` cloud provider is available if you want to configure any Kubernetes cloud provider. - -For the custom cloud provider option, you can refer to the [RKE docs]({{}}/rke/latest/en/config-options/cloud-providers/) on how to edit the yaml file for your specific cloud provider. There are specific cloud providers that have more detailed configuration: - -* [vSphere]({{}}/rke/latest/en/config-options/cloud-providers/vsphere/) -* [OpenStack]({{}}/rke/latest/en/config-options/cloud-providers/openstack/) diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/gce/gce.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/gce/gce.md deleted file mode 100644 index e1b7c2c3024..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/gce/gce.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Setting up the Google Compute Engine Cloud Provider -weight: 3 ---- - -In this section, you'll learn how to enable the Google Compute Engine (GCE) cloud provider for custom clusters in Rancher. A custom cluster is one in which Rancher installs Kubernetes on existing nodes. - -The official Kubernetes documentation for the GCE cloud provider is [here.](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#gce) - -> **Prerequisites:** The service account of `Identity and API` access on GCE needs the `Computer Admin` permission. - -If you are using Calico, - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the custom cluster and click **⋮ > Edit YAML.* Enter the following configuration: - - ``` - rancher_kubernetes_engine_config: - cloud_provider: - name: gce - customCloudProvider: |- - [Global] - project-id= - network-name= - subnetwork-name= - node-instance-prefix= - node-tags= - network: - options: - calico_cloud_provider: "gce" - plugin: "calico" - ``` - -If you are using Canal or Flannel, - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the custom cluster and click **⋮ > Edit YAML.* Enter the following configuration: - - ``` - rancher_kubernetes_engine_config: - cloud_provider: - name: gce - customCloudProvider: |- - [Global] - project-id= - network-name= - subnetwork-name= - node-instance-prefix= - node-tags= - services: - kube_controller: - extra_args: - configure-cloud-routes: true # we need to allow the cloud provider configure the routes for the hosts - ``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/in-tree/in-tree.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/in-tree/in-tree.md deleted file mode 100644 index 17ddc2b2d57..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/in-tree/in-tree.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: How to Configure In-tree vSphere Cloud Provider -shortTitle: In-tree Cloud Provider -weight: 10 ---- - -To set up the in-tree vSphere cloud provider, follow these steps while creating the vSphere cluster in Rancher: - -1. Set **Cloud Provider** option to `Custom` or `Custom (In-Tree)`. -1. Click on **Edit as YAML** -1. Insert the following structure to the pre-populated cluster YAML. This structure must be placed under `rancher_kubernetes_engine_config`. Note that the `name` *must* be set to `vsphere`. - - ```yaml - rancher_kubernetes_engine_config: - cloud_provider: - name: vsphere - vsphereCloudProvider: - [Insert provider configuration] - ``` - -Rancher uses RKE (the Rancher Kubernetes Engine) to provision Kubernetes clusters. Refer to the [vSphere configuration reference in the RKE documentation]({{}}/rke/latest/en/config-options/cloud-providers/vsphere/config-reference/) for details about the properties of the `vsphereCloudProvider` directive. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/out-of-tree.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/out-of-tree.md deleted file mode 100644 index d9b95fc9b6f..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/out-of-tree.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: How to Configure Out-of-tree vSphere Cloud Provider -shortTitle: Out-of-tree Cloud Provider -weight: 10 ---- - -Kubernetes is moving away from maintaining cloud providers in-tree. vSphere has an out-of-tree cloud provider that can be used by installing the vSphere cloud provider and cloud storage plugins. - -This page covers how to install the Cloud Provider Interface (CPI) and Cloud Storage Interface (CSI) plugins after bringing up a cluster. - -# Prerequisites - -The vSphere versions supported: - -* 6.7u3 -* 7.0u1 or higher. - -The Kubernetes version must be 1.19 or higher. - -Using the vSphere out-of-tree cloud provider requires Linux nodes and is not supported on Windows. - -# Installation - -The Cloud Provider Interface (CPI) should be installed first before installing the Cloud Storage Interface (CSI). - -### 1. Create a vSphere cluster - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **VMware vSphere** or **Custom**. -1. On the **Basics** tab in the **Cluster Configuration** section, set the **Cloud Provider** to **vSphere**. -1. In the **Add-On Config** tab, the vSphere Cloud Provider (CPI) and Storage Provider (CSI) options. -1. Finish creating your cluster. - -### 2. Install the CPI plugin - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where the vSphere CPI plugin will be installed and click **Explore**. -1. Click **Apps & Marketplace > Charts**. -1. Click **vSphere CPI**. -1. Fill out the required vCenter details. -1. vSphere CPI initializes all nodes with ProviderID which is needed by the vSphere CSI driver. Check if all nodes are initialized with the ProviderID before installing CSI driver with the following command: - - ``` - kubectl describe nodes | grep "ProviderID" - ``` - -### 3. Installing the CSI plugin - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where the vSphere CSI plugin will be installed and click **Explore**. -1. Click **Apps & Marketplace > Charts**. -1. Click **vSphere CSI**. -1. Click **Install**. -1. Fill out the required vCenter details. On the **Features** tab, set **Enable CSI Migration** to **false**. -3. On the **Storage** tab, fill out the details for the StorageClass. This chart creates a StorageClass with the `csi.vsphere.vmware.com` as the provisioner. -1. Click **Install**. - - -# Using the CSI driver for provisioning volumes - -The CSI chart by default creates a storageClass. - -If that option was not selected while launching the chart, create a storageClass with the `csi.vsphere.vmware.com` as the provisioner. - -All volumes provisioned using this StorageClass will get provisioned by the CSI driver. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/vsphere-volume-migration/vsphere-volume-migration.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/vsphere-volume-migration/vsphere-volume-migration.md deleted file mode 100644 index 41b9d5d254a..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/out-of-tree/vsphere-volume-migration/vsphere-volume-migration.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Migrating vSphere In-tree Volumes to CSI -weight: 5 ---- -Kubernetes is moving away from maintaining cloud providers in-tree. vSphere has an out-of-tree cloud provider that can be used by installing the vSphere cloud provider and cloud storage plugins. - -This page covers how to migrate from the in-tree vSphere cloud provider to out-of-tree, and manage the existing VMs post migration. - -It follows the steps provided in the official [vSphere migration documentation](https://vsphere-csi-driver.sigs.k8s.io/features/vsphere_csi_migration.html) and provides the steps to be performed in Rancher. - -### Cloud-config Format Limitation - -Existing volumes that were provisioned using the following cloud-config format will NOT get migrated due to an existing bug in vsphere CSI. - -If the cloud-config has this format for datastore and resource pool path, vsphere CSI driver cannot recognize it: - -```yaml -default-datastore: /datastore/ -resourcepool-path: "/host//Resources/" -``` - -Volumes provisioned with the in-tree provider using the following format will get migrated correctly: - -```yaml -default-datastore: -resourcepool-path: "/Resources/" -``` - -Upstream bug: https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/628 - -Rancher issue tracking this bug: https://github.com/rancher/rancher/issues/31105 - -# Prerequisites - -- vSphere CSI Migration requires vSphere 7.0u1. In order to be able to manage existing in-tree vSphere volumes, upgrade vSphere to 7.0u1. -- The Kubernetes version must be 1.19 or higher. - -# Migration - -### 1. Install the CPI plugin - -Before installing CPI, we need to taint all nodes with `node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule`. - -This can be done by running the following commands: - -``` -curl -O https://raw.githubusercontent.com/rancher/helm3-charts/56b622f519728378abeddfe95074f1b87ab73b1e/charts/vsphere-cpi/taints.sh -``` - -Or: - -``` -wget https://raw.githubusercontent.com/rancher/helm3-charts/56b622f519728378abeddfe95074f1b87ab73b1e/charts/vsphere-cpi/taints.sh -chmod +x taints.sh -./taints.sh -``` - -Once all nodes are tainted by the running the script, launch the Helm vSphere CPI chart. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where the vSphere CPI chart will be installed and click **Explore**. -1. Click **Apps & Marketplace > Charts**. -1. Click **vSphere CPI**.. -1. Click **Install**. -1. Fill out the required vCenter details and click **Install**. - -vSphere CPI initializes all nodes with ProviderID, which is needed by the vSphere CSI driver. - -Check if all nodes are initialized with the ProviderID with the following command: - -``` -kubectl describe nodes | grep "ProviderID" -``` - -### 2. Install the CSI driver - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where the vSphere CSI chart will be installed and click **Explore**. -1. Click **Apps & Marketplace > Charts**. -1. Click **vSphere CSI**.. -1. Click **Install**. -1. Fill out the required vCenter details and click **Install**. -1. Check **Customize Helm options before install** and click **Next**. -1. On the **Features** tab, check **Enable CSI Migration**. -1. Optionally, go to the **Storage** tab and set up a datastore. This chart creates a StorageClass with the `csi.vsphere.vmware.com` as the provisioner. You can provide the URL of the datastore to be used for CSI volume provisioning while creating this StorageClass. The datastore URL can be found in the vSphere client by selecting the datastore and going to the Summary tab. Fill out the details for the StorageClass. -1. Click **Install**. - -### 3. Edit the cluster to enable CSI migration feature flags - -1. While editing the cluster, if the Kubernetes version is less than 1.19, select Kubernetes version 1.19 or higher from the **Kubernetes Version** dropdown. -2. For enabling feature flags, click on "Edit as YAML", and add the following under kube-controller and kubelet: - - ```yaml - extra_args: - feature-gates: "CSIMigration=true,CSIMigrationvSphere=true" - ``` - -### 4. Drain worker nodes - -Worker nodes must be drained during the upgrade before changing the kubelet and kube-controller-manager args. - - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you will drain worker nodes and click **⋮ > Edit Config**. -1. In the **Advanced Options** section, set the field **Maximum Worker Nodes Unavailable** to 1. -1. To drain the nodes during upgrade, select **Drain Nodes > Yes**. -1. Set **Force** and **Delete Local Data** to **true**. -1. Click **Save** to upgrade the cluster. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/vsphere.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/vsphere.md deleted file mode 100644 index 77a27a88eab..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/cloud-providers/vsphere/vsphere.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Setting up the vSphere Cloud Provider -weight: 4 ---- - -In this section, you'll learn how to set up a vSphere cloud provider for a Rancher managed RKE Kubernetes cluster in vSphere. - -# In-tree Cloud Provider - -To use the in-tree vSphere cloud provider, you will need to use an RKE configuration option. For details, refer to [this page.](./in-tree) - -# Out-of-tree Cloud Provider - -To set up the out-of-tree vSphere cloud provider, you will need to install Helm charts from the Rancher marketplace. For details, refer to [this page.](./out-of-tree) diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/agent-options/agent-options.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/agent-options/agent-options.md deleted file mode 100644 index 12670480979..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/agent-options/agent-options.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Rancher Agent Options -weight: 2500 ---- - -Rancher deploys an agent on each node to communicate with the node. This pages describes the options that can be passed to the agent. To use these options, you will need to [create a cluster with custom nodes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes) and add the options to the generated `docker run` command when adding a node. - -For an overview of how Rancher communicates with downstream clusters using node agents, refer to the [architecture section.]({{}}/rancher/v2.6/en/overview/architecture/#3-node-agents) - -## General options - -| Parameter | Environment variable | Description | -| ---------- | -------------------- | ----------- | -| `--server` | `CATTLE_SERVER` | The configured Rancher `server-url` setting which the agent connects to | -| `--token` | `CATTLE_TOKEN` | Token that is needed to register the node in Rancher | -| `--ca-checksum` | `CATTLE_CA_CHECKSUM` | The SHA256 checksum of the configured Rancher `cacerts` setting to validate | -| `--node-name` | `CATTLE_NODE_NAME` | Override the hostname that is used to register the node (defaults to `hostname -s`) | -| `--label` | `CATTLE_NODE_LABEL` | Add node labels to the node. For multiple labels, pass additional `--label` options. (`--label key=value`) | -| `--taints` | `CATTLE_NODE_TAINTS` | Add node taints to the node. For multiple taints, pass additional `--taints` options. (`--taints key=value:effect`) | - -## Role options - -| Parameter | Environment variable | Description | -| ---------- | -------------------- | ----------- | -| `--all-roles` | `ALL=true` | Apply all roles (`etcd`,`controlplane`,`worker`) to the node | -| `--etcd` | `ETCD=true` | Apply the role `etcd` to the node | -| `--controlplane` | `CONTROL=true` | Apply the role `controlplane` to the node | -| `--worker` | `WORKER=true` | Apply the role `worker` to the node | - -## IP address options - -| Parameter | Environment variable | Description | -| ---------- | -------------------- | ----------- | -| `--address` | `CATTLE_ADDRESS` | The IP address the node will be registered with (defaults to the IP used to reach `8.8.8.8`) | -| `--internal-address` | `CATTLE_INTERNAL_ADDRESS` | The IP address used for inter-host communication on a private network | - -### Dynamic IP address options - -For automation purposes, you can't have a specific IP address in a command as it has to be generic to be used for every node. For this, we have dynamic IP address options. They are used as a value to the existing IP address options. This is supported for `--address` and `--internal-address`. - -| Value | Example | Description | -| ---------- | -------------------- | ----------- | -| Interface name | `--address eth0` | The first configured IP address will be retrieved from the given interface | -| `ipify` | `--address ipify` | Value retrieved from `https://api.ipify.org` will be used | -| `awslocal` | `--address awslocal` | Value retrieved from `http://169.254.169.254/latest/meta-data/local-ipv4` will be used | -| `awspublic` | `--address awspublic` | Value retrieved from `http://169.254.169.254/latest/meta-data/public-ipv4` will be used | -| `doprivate` | `--address doprivate` | Value retrieved from `http://169.254.169.254/metadata/v1/interfaces/private/0/ipv4/address` will be used | -| `dopublic` | `--address dopublic` | Value retrieved from `http://169.254.169.254/metadata/v1/interfaces/public/0/ipv4/address` will be used | -| `azprivate` | `--address azprivate` | Value retrieved from `http://169.254.169.254/metadata/instance/network/interface/0/ipv4/ipAddress/0/privateIpAddress?api-version=2017-08-01&format=text` will be used | -| `azpublic` | `--address azpublic` | Value retrieved from `http://169.254.169.254/metadata/instance/network/interface/0/ipv4/ipAddress/0/publicIpAddress?api-version=2017-08-01&format=text` will be used | -| `gceinternal` | `--address gceinternal` | Value retrieved from `http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/ip` will be used | -| `gceexternal` | `--address gceexternal` | Value retrieved from `http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip` will be used | -| `packetlocal` | `--address packetlocal` | Value retrieved from `https://metadata.packet.net/2009-04-04/meta-data/local-ipv4` will be used | -| `packetpublic` | `--address packetlocal` | Value retrieved from `https://metadata.packet.net/2009-04-04/meta-data/public-ipv4` will be used | diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/custom-nodes.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/custom-nodes.md deleted file mode 100644 index fcf49838d16..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/custom-nodes/custom-nodes.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Launching Kubernetes on Existing Custom Nodes -description: To create a cluster with custom nodes, you’ll need to access servers in your cluster and provision them according to Rancher requirements -metaDescription: "To create a cluster with custom nodes, you’ll need to access servers in your cluster and provision them according to Rancher requirements" -weight: 2225 ---- - -When you create a custom cluster, Rancher uses RKE (the Rancher Kubernetes Engine) to create a Kubernetes cluster in on-prem bare-metal servers, on-prem virtual machines, or in any node hosted by an infrastructure provider. - -To use this option you'll need access to servers you intend to use in your Kubernetes cluster. Provision each server according to the [requirements]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements), which includes some hardware specifications and Docker. After you install Docker on each server, you willl also run the command provided in the Rancher UI on each server to turn each one into a Kubernetes node. - -This section describes how to set up a custom cluster. - -# Creating a Cluster with Custom Nodes - ->**Want to use Windows hosts as Kubernetes workers?** -> ->See [Configuring Custom Clusters for Windows]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/) before you start. - - - -- [1. Provision a Linux Host](#1-provision-a-linux-host) -- [2. Create the Custom Cluster](#2-create-the-custom-cluster) -- [3. Amazon Only: Tag Resources](#3-amazon-only-tag-resources) - - - -### 1. Provision a Linux Host - -Begin creation of a custom cluster by provisioning a Linux host. Your host can be: - -- A cloud-host virtual machine (VM) -- An on-prem VM -- A bare-metal server - -If you want to reuse a node from a previous custom cluster, [clean the node]({{}}/rancher/v2.6/en/cluster-admin/cleaning-cluster-nodes/) before using it in a cluster again. If you reuse a node that hasn't been cleaned, cluster provisioning may fail. - -Provision the host according to the [installation requirements]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements) and the [checklist for production-ready clusters.]({{}}/rancher/v2.6/en/cluster-provisioning/production) - -If you're using Amazon EC2 as your host and want to use the [dual-stack](https://kubernetes.io/docs/concepts/services-networking/dual-stack/) feature, there are additional [requirements]({{}}/rke//latest/en/config-options/dual-stack#requirements) when provisioning the host. - -### 2. Create the Custom Cluster - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **Custom**. -1. Enter a **Cluster Name**. -1. Use **Cluster Configuration** section to choose the version of Kubernetes, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options**. - - >**Using Windows nodes as Kubernetes workers?** - > - >- See [Enable the Windows Support Option]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/). - >- The only Network Provider available for clusters with Windows support is Flannel. - > - >**Dual-stack on Amazon EC2:** If you're using Amazon EC2 as your host and want to use the [dual-stack](https://kubernetes.io/docs/concepts/services-networking/dual-stack/) feature, there are additional [requirements]({{}}/rke//latest/en/config-options/dual-stack#requirements) when configuring RKE. - -6. Click **Next**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -7. From **Node Role**, choose the roles that you want filled by a cluster node. You must provision at least one node for each role: `etcd`, `worker`, and `control plane`. All three roles are required for a custom cluster to finish provisioning. For more information on roles, see [this section.]({{}}/rancher/v2.6/en/overview/concepts/#roles-for-nodes-in-kubernetes-clusters) - - >**Notes:** - > - >- Using Windows nodes as Kubernetes workers? See [this section]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/). - >- Bare-Metal Server Reminder: If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers). - -8. **Optional**: Click **[Show advanced options]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/rancher-agents/)** to specify IP address(es) to use when registering the node, override the hostname of the node, or to add [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) or [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) to the node. - -9. Copy the command displayed on screen to your clipboard. - -10. Log in to your Linux host using your preferred shell, such as PuTTy or a remote Terminal connection. Run the command copied to your clipboard. - - >**Note:** Repeat steps 7-10 if you want to dedicate specific hosts to specific node roles. Repeat the steps as many times as needed. - -11. When you finish running the command(s) on your Linux host(s), click **Done**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - - -### 3. Amazon Only: Tag Resources - -If you have configured your cluster to use Amazon as **Cloud Provider**, tag your AWS resources with a cluster ID. - -[Amazon Documentation: Tagging Your Amazon EC2 Resources](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html) - ->**Note:** You can use Amazon EC2 instances without configuring a cloud provider in Kubernetes. You only have to configure the cloud provider if you want to use specific Kubernetes cloud provider functionality. For more information, see [Kubernetes Cloud Providers](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/) - - -The following resources need to be tagged with a `ClusterID`: - -- **Nodes**: All hosts added in Rancher. -- **Subnet**: The subnet used for your cluster -- **Security Group**: The security group used for your cluster. - - >**Note:** Do not tag multiple security groups. Tagging multiple groups generates an error when creating Elastic Load Balancer. - -The tag that should be used is: - -``` -Key=kubernetes.io/cluster/, Value=owned -``` - -`` can be any string you choose. However, the same string must be used on every resource you tag. Setting the tag value to `owned` informs the cluster that all resources tagged with the `` are owned and managed by this cluster. - -If you share resources between clusters, you can change the tag to: - -``` -Key=kubernetes.io/cluster/CLUSTERID, Value=shared -``` - -# Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-machine-config/azure-machine-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-machine-config/azure-machine-config.md deleted file mode 100644 index 4c5304eb1e2..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-machine-config/azure-machine-config.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: Azure Machine Configuration -weight: 2 ---- - -For more information about Azure, refer to the official [Azure documentation.](https://docs.microsoft.com/en-us/azure/?product=featured) - -### Environment - -Microsoft provides multiple [clouds](https://docs.microsoft.com/en-us/cli/azure/cloud?view=azure-cli-latest) for compliance with regional laws, which are available for your use: - -- AzurePublicCloud -- AzureGermanCloud -- AzureChinaCloud -- AzureUSGovernmentCloud - -### Location - -Configure the cluster and node [location](https://docs.microsoft.com/en-us/azure/virtual-machines/regions). - -### Resource Group - -A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to allocate resources to resource groups based on what makes the most sense for your organization. Generally, add resources that share the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group. - -Use an existing resource group or enter a resource group name and one will be created for you. - -For information on managing resource groups, see the [Azure documentation.](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal) - -### Availability Set (unmanaged) - -Name or ID of an existing [availability set](https://docs.microsoft.com/en-us/azure/virtual-machines/availability-set-overview) to add the VM to. - -### Image - -The name of the operating system image provided as an ARM resource identifier. Requires using managed disk. - -### VM Size - -Choose a size for each VM in the node pool. For details about each VM size, see [this page.](https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/) - -## Advanced Options - -### Fault Domain Count - -Fault domains define the group of virtual machines that share a common power source and network switch. If the availability set has already been created, the fault domain count will be ignored. - -For more information on fault domains, see [refer here](https://docs.microsoft.com/en-us/azure/virtual-machines/availability-set-overview#how-do-availability-sets-work). - -### Update Domain Count - -Update domains indicate groups of virtual machines and underlying physical hardware that can be rebooted at the same time. If the availability set has already been created, the update domain count will be ignored. - -For more information on update domains, see [refer here](https://docs.microsoft.com/en-us/azure/virtual-machines/availability-set-overview#how-do-availability-sets-work). - -### Purchase Plan - -Some VM images in the Azure Marketplace require a plan. If applicable, select a purchase plan, formatted as `publisher:product:plan`, to use with your chosen image. - -### Subnet - -The name of the subnet when creating a new VNet or referencing an existing one. - -Default: `docker-machine` - -### Subnet Prefix - -The subnet IP address prefix to use when creating a new VNet in CIDR format. - -Default: `192.168.0.0/16` - -### Virtual Network - -The [virtual network](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview) to use or create if one does not exist. Formatted as `[resourcegroup:]name`. - -### Public IP Options - -#### No Public IP - -Do not allocate a public IP address. - -#### Static Public IP - -Allocate a static public IP address. - -### Use Private IP - -Use a static private IP address. - -### Private IP Address - -Configure a static private IP address to use. - -### Network Security Group - -The [network security group](https://docs.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview) to use. All nodes using this template will use the supplied network security group. If no network security group is provided, a new one will be created for each node. - -### DNS Label - -A unique DNS name label for the public IP address. - -### Storage Type - -The [storage account](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview) type to use with your VMs. Options include Standard LRS, Standard ZRS, Standard GRS, Standard RAGRS, and Premium LRS. - -### Use Managed Disks - -[Azure managed disks](https://docs.microsoft.com/en-us/azure/virtual-machines/managed-disks-overview) are block-level storage volumes that are managed by Azure and used with Azure Virtual Machines. Managed disks are designed for 99.999% availability. Managed disks achieve this by providing you with three replicas of your data, allowing for high durability. - -### Managed Disk Size - -The size in GB for the disk for each node. - -### SSH Username - -The username used to create an SSH connection to your nodes. - -### Open Port - -Opens inbound traffic on specified ports. When using an existing Network Security Group, Open Ports are ignored. - -Default: `2379/tcp, 2380/tcp, 6443/tcp, 9796/tcp, 10250/tcp, 10251/tcp, 10252/tcp, 10256/tcp` and `8472/udp, 4789/udp` \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-node-template-config/azure-node-template-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-node-template-config/azure-node-template-config.md deleted file mode 100644 index e7b00c9363e..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure-node-template-config/azure-node-template-config.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Azure Node Template Configuration -weight: 1 ---- - -For more information about Azure, refer to the official [Azure documentation.](https://docs.microsoft.com/en-us/azure/?product=featured) - -Account access information is stored as a cloud credential. Cloud credentials are stored as Kubernetes secrets. Multiple node templates can use the same cloud credential. You can use an existing cloud credential or create a new one. - -- **Placement** sets the geographical region where your cluster is hosted and other location metadata. -- **Network** configures the networking used in your cluster. -- **Instance** customizes your VM configuration. - -The [Docker daemon](https://docs.docker.com/engine/docker-overview/#the-docker-daemon) configuration options include: - -- **Labels:** For information on labels, refer to the [Docker object label documentation.](https://docs.docker.com/config/labels-custom-metadata/) -- **Docker Engine Install URL:** Determines what Docker version will be installed on the instance. -- **Registry mirrors:** Docker Registry mirror to be used by the Docker daemon -- **Other advanced options:** Refer to the [Docker daemon option reference](https://docs.docker.com/engine/reference/commandline/dockerd/) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure.md deleted file mode 100644 index 37fda12e717..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/azure/azure.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Creating an Azure Cluster -shortTitle: Azure -weight: 2220 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -In this section, you'll learn how to install an [RKE]({{}}/rke/latest/en/) Kubernetes cluster in Azure through Rancher. - -First, you will set up your Azure cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision new nodes in Azure. - -Then you will create an Azure cluster in Rancher, and when configuring the new cluster, you will define node pools for it. Each node pool will have a Kubernetes role of etcd, controlplane, or worker. Rancher will install Kubernetes on the new nodes, and it will set up each node with the Kubernetes role defined by the node pool. - ->**Warning:** When the Rancher RKE cluster is running in Azure and has an Azure load balancer in front, the outbound flow will fail. The workaround for this problem is as follows: - -> - Terminate the SSL/TLS on the internal load balancer -> - Use the L7 load balancer - -> For more information, refer to the documentation on [Azure load balancer limitations](https://docs.microsoft.com/en-us/azure/load-balancer/components#limitations). - -For more information on configuring the Kubernetes cluster that Rancher will install on the Azure nodes, refer to the [RKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options) - -For more information on configuring Azure node templates, refer to the [Azure node template configuration reference.](./azure-node-template-config) - -- [Preparation in Azure](#preparation-in-azure) -- [Creating an Azure Cluster](#creating-an-azure-cluster) - -# Preparation in Azure - -Before creating a node template in Rancher using a cloud infrastructure such as Azure, we must configure Rancher to allow the manipulation of resources in an Azure subscription. - -To do this, we will first create a new Azure **service principal (SP)** in Azure **Active Directory (AD)**, which, in Azure, is an application user who has permission to manage Azure resources. - -The following is a template `az cli` script that you have to run for creating an service principal, where you have to enter your SP name, role, and scope: - -``` -az ad sp create-for-rbac \ - --name="" \ - --role="Contributor" \ - --scopes="/subscriptions/" -``` - -The creation of this service principal returns three pieces of identification information, *The application ID, also called the client ID*, and *The client secret*. This information will be used when you create a node template for Azure. - -# Creating an Azure Cluster - - - - -1. [Create your cloud credentials](#1-create-your-cloud-credentials) -2. [Create a node template with your cloud credentials](#2-create-a-node-template-with-your-cloud-credentials) -3. [Create a cluster with node pools using the node template](#3-create-a-cluster-with-node-pools-using-the-node-template) - -### 1. Create your cloud credentials - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **Azure**. -1. Enter your Azure credentials. -1. Click **Create**. - -**Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. - -### 2. Create a node template with your cloud credentials - -Creating a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for Azure will allow Rancher to provision new nodes in Azure. Node templates can be reused for other clusters. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Click **Add Template**. -1. Click **Azure**. -1. Fill out a node template for Azure. For help filling out the form, refer to [Azure Node Template Configuration.](./azure-node-template-config) - -### 3. Create a cluster with node pools using the node template - -Use Rancher to create a Kubernetes cluster in Azure. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **Azure**. -1. Enter a **Cluster Name**. -1. Add one or more node pools to your cluster. Each node pool uses a node template to provision new nodes. For more information about node pools, including best practices, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools) -1. In the **Cluster Configuration** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options**. For help configuring the cluster, refer to the [RKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options) -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Click **Create**. - - - - -### 1. Create your cloud credentials - -If you already have a set of cloud credentials to use, skip this section. - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **Azure**. -1. Enter your Azure credentials. -1. Click **Create**. - -**Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. - -### 2. Create your cluster - -Use Rancher to create a Kubernetes cluster in Azure. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Toggle the switch to **RKE2/K3s**. -1. Click **Azure**. -1. Select a **Cloud Credential**, if more than one exists. Otherwise, it's preselected. -1. Enter a **Cluster Name**. -1. Create a machine pool for each Kubernetes role. Refer to the [best practices]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools#node-roles-in-rke2) for recommendations on role assignments and counts. - 1. For each machine pool, define the machine configuration. Refer to the [Azure machine configuration reference]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/azure/azure-machine-config/) for information on configuration options. -1. Use the **Cluster Configuration** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. For help configuring the cluster, refer to the [RKE2 cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/rke2-config-reference/) -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Click **Create**. - - - - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - - -### Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/digital-ocean.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/digital-ocean.md deleted file mode 100644 index 28d7e799f36..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/digital-ocean.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a DigitalOcean Cluster -shortTitle: DigitalOcean -weight: 2215 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -In this section, you'll learn how to use Rancher to install an [RKE](https://rancher.com/docs/rke/latest/en/) Kubernetes cluster in DigitalOcean. - -First, you will set up your DigitalOcean cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision new nodes in DigitalOcean. - -Then you will create a DigitalOcean cluster in Rancher, and when configuring the new cluster, you will define node pools for it. Each node pool will have a Kubernetes role of etcd, controlplane, or worker. Rancher will install RKE Kubernetes on the new nodes, and it will set up each node with the Kubernetes role defined by the node pool. - - - - -1. [Create your cloud credentials](#1-create-your-cloud-credentials) -2. [Create a node template with your cloud credentials](#2-create-a-node-template-with-your-cloud-credentials) -3. [Create a cluster with node pools using the node template](#3-create-a-cluster-with-node-pools-using-the-node-template) - -### 1. Create your cloud credentials - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **DigitalOcean**. -1. Enter your Digital Ocean credentials. -1. Click **Create**. - -**Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. - -### 2. Create a node template with your cloud credentials - -Creating a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for DigitalOcean will allow Rancher to provision new nodes in DigitalOcean. Node templates can be reused for other clusters. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Click **Add Template**. -1. Click **DigitalOcean**. -1. Fill out a node template for DigitalOcean. For help filling out the form, refer to [DigitalOcean Node Template Configuration.](./do-node-template-config) - -### 3. Create a cluster with node pools using the node template - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **DigitalOcean**. -1. Enter a **Cluster Name**. -1. Add one or more node pools to your cluster. Add one or more node pools to your cluster. Each node pool uses a node template to provision new nodes. For more information about node pools, including best practices for assigning Kubernetes roles to them, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools) -1. **In the Cluster Configuration** section, choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options**. For help configuring the cluster, refer to the [RKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options) -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Click **Create**. - - - - -### 1. Create your cloud credentials - -If you already have a set of cloud credentials to use, skip this section. - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **DigitalOcean**. -1. Enter your Digital Ocean credentials. -1. Click **Create**. - -### 2. Create your cluster - -Use Rancher to create a Kubernetes cluster in DigitalOcean. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Toggle the switch to **RKE2/K3s**. -1. Click **DigitalOcean**. -1. Select a **Cloud Credential**, if more than one exists. Otherwise, it's preselected. -1. Enter a **Cluster Name**. -1. Create a machine pool for each Kubernetes role. Refer to the [best practices]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools#node-roles-in-rke2) for recommendations on role assignments and counts. - 1. For each machine pool, define the machine configuration. Refer to the [DigitalOcean machine configuration reference]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-machine-config/) for information on configuration options. -1. Use the **Cluster Configuration** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. For help configuring the cluster, refer to the [RKE2 cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/rke2-config-reference/) -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Click **Create**. - - - - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces -# Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-machine-config/do-machine-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-machine-config/do-machine-config.md deleted file mode 100644 index 0ae2f8d831a..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-machine-config/do-machine-config.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: DigitalOcean Machine Configuration -weight: 2 ---- - -For more details about DigitalOcean, Droplets, refer to the [official documentation](https://docs.digitalocean.com/products/compute/). - -### Region - -Configure the [region](https://docs.digitalocean.com/products/app-platform/concepts/region/) where Droplets are created. - -### Size - -Configure the [size](https://docs.digitalocean.com/products/droplets/resources/choose-plan/) of Droplets. - -### OS Image - -Configure the operating system [image](https://docs.digitalocean.com/products/images/) Droplets are created from. - -### Monitoring - -Enable the DigitalOcean agent for additional [monitoring](https://docs.digitalocean.com/products/monitoring/). - -### IPv6 - -Enable IPv6 for Droplets. - -### Private Networking - -Enable private networking for Droplets. - -### Droplet Tags - -Apply a tag (label) to a Droplet. Tags may only contain letters, numbers, colons, dashes, and underscores. For example, `my_server`. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-node-template-config/do-node-template-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-node-template-config/do-node-template-config.md deleted file mode 100644 index 84171f27295..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/digital-ocean/do-node-template-config/do-node-template-config.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: DigitalOcean Node Template Configuration -weight: 1 ----- - -Account access information is stored as a cloud credential. Cloud credentials are stored as Kubernetes secrets. Multiple node templates can use the same cloud credential. You can use an existing cloud credential or create a new one. - -### Droplet Options - -The **Droplet Options** provision your cluster's geographical region and specifications. - -### Docker Daemon - -The [Docker daemon](https://docs.docker.com/engine/docker-overview/#the-docker-daemon) configuration options include: - -- **Labels:** For information on labels, refer to the [Docker object label documentation.](https://docs.docker.com/config/labels-custom-metadata/) -- **Docker Engine Install URL:** Determines what Docker version will be installed on the instance. -- **Registry mirrors:** Docker Registry mirror to be used by the Docker daemon -- **Other advanced options:** Refer to the [Docker daemon option reference](https://docs.docker.com/engine/reference/commandline/dockerd/) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-machine-config/ec2-machine-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-machine-config/ec2-machine-config.md deleted file mode 100644 index d29a7567669..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-machine-config/ec2-machine-config.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: EC2 Machine Configuration Reference -weight: 2 ---- - -For more details about EC2 nodes, refer to the official documentation for the [EC2 Management Console](https://aws.amazon.com/ec2). - -### Region - -The geographical [region](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) in which to build your cluster. - -### Zone - -The [zone](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-availability-zones), an isolated location within a region to build your cluster - -### Instance Type - -The [instance type](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html), which determines the hardware characteristics, used to provision your cluster. - -### Root Disk Size - -Configure the size (in GB) for your [root device](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/RootDeviceStorage.html). - -### VPC/Subnet - -The [VPC](https://docs.aws.amazon.com/vpc/latest/userguide/configure-your-vpc.html) or specific [subnet](https://docs.aws.amazon.com/vpc/latest/userguide/configure-subnets.html), an IP range in your VPC, to add your resources to. - -### IAM Instance Profile Name - -The name of the [instance profile] used to pass an IAM role to an EC2 instance. - -## Advanced Options - -### AMI ID - -The [Amazon Machine Image](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html) used for the nodes in your cluster. - -### SSH Username for AMI - -The username for connecting to your launched instances. Refer to [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connection-prereqs.html) for the default usernames to selected AMIs. For AMIs not listed, check with the AMI provider. - -### Security Group - -Choose the default security group or configure a security group. - -Please refer to [Amazon EC2 security group when using Node Driver]({{}}/rancher/v2.6/en/installation/requirements/ports/#rancher-aws-ec2-security-group) to see what rules are created in the `rancher-nodes` Security Group. - -### EBS Root Volume Type - -The [EBS volume type](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html) to use for the root device. - -### Encrypt EBS Volume - -Enable [Amazon EBS Encryption](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html). - -### Request Spot Instance - -Enable option to [request spot instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html) and specify the maximum instance price per hour you're willing to pay. - -### Use only private address - -Enable option on use only [private addresses](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html). - -### EBS-Optimized Instance - -Use an [EBS-optimized instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html). - -### Allow access to EC2 metadata - -Enable access to [EC2 metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html). - -### Use tokens for metadata - -Use [Instance Metadata Service Version 2 (IMDSv2)](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html), a token-based method to access metadata. - -### Add Tag - -Add metadata using [tags](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html) to categorize resources. - diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-node-template-config/ec2-node-template-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-node-template-config/ec2-node-template-config.md deleted file mode 100644 index 4da61dccaf7..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-node-template-config/ec2-node-template-config.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: EC2 Node Template Configuration -weight: 1 ---- - -For more details about EC2, nodes, refer to the official documentation for the [EC2 Management Console](https://aws.amazon.com/ec2). -### Region - -In the **Region** field, select the same region that you used when creating your cloud credentials. - -### Cloud Credentials - -Your AWS account access information, stored in a [cloud credential.]({{}}/rancher/v2.6/en/user-settings/cloud-credentials/) - -See [Amazon Documentation: Creating Access Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey) how to create an Access Key and Secret Key. - -See [Amazon Documentation: Creating IAM Policies (Console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-start) how to create an IAM policy. - -See [Amazon Documentation: Adding Permissions to a User (Console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) how to attach an IAM - -See our three example JSON policies: - -- [Example IAM Policy]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/#example-iam-policy) -- [Example IAM Policy with PassRole]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/#example-iam-policy-with-passrole) (needed if you want to use [Kubernetes Cloud Provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers) or want to pass an IAM Profile to an instance) -- [Example IAM Policy to allow encrypted EBS volumes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/#example-iam-policy-to-allow-encrypted-ebs-volumes) policy to an user. - -### Authenticate & Configure Nodes - -Choose an availability zone and network settings for your cluster. - -### Security Group - -Choose the default security group or configure a security group. - -Please refer to [Amazon EC2 security group when using Node Driver]({{}}/rancher/v2.6/en/installation/requirements/ports/#rancher-aws-ec2-security-group) to see what rules are created in the `rancher-nodes` Security Group. - ---- -**_New in v2.6.4_** - -If you provide your own security group for an EC2 instance, please note that Rancher will not modify it. As such, you will be responsible for ensuring that your security group is set to allow the [necessary ports for Rancher to provision the instance]({{}}/rancher/v2.6/en/installation/requirements/ports/#ports-for-rancher-server-nodes-on-rke). For more information on controlling inbound and outbound traffic to EC2 instances with security groups, refer [here](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html#WorkingWithSecurityGroups). - -### Instance Options - -Configure the instances that will be created. Make sure you configure the correct **SSH User** for the configured AMI. It is possible that a selected region does not support the default instance type. In this scenario you must select an instance type that does exist, otherwise an error will occur stating the requested configuration is not supported. - -If you need to pass an **IAM Instance Profile Name** (not ARN), for example, when you want to use a [Kubernetes Cloud Provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers), you will need an additional permission in your policy. See [Example IAM policy with PassRole](#example-iam-policy-with-passrole) for an example policy. - -### Engine Options - -In the **Engine Options** section of the node template, you can configure the Docker daemon. You may want to specify the docker version or a Docker registry mirror. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2.md deleted file mode 100644 index ee0fcf1169b..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/ec2/ec2.md +++ /dev/null @@ -1,279 +0,0 @@ ---- -title: Creating an Amazon EC2 Cluster -shortTitle: Amazon EC2 -description: Learn the prerequisites and steps required in order for you to create an Amazon EC2 cluster using Rancher -weight: 2210 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -In this section, you'll learn how to use Rancher to install an [RKE](https://rancher.com/docs/rke/latest/en/) Kubernetes cluster in Amazon EC2. - -First, you will set up your EC2 cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision new nodes in EC2. - -Then you will create an EC2 cluster in Rancher, and when configuring the new cluster, you will define node pools for it. Each node pool will have a Kubernetes role of etcd, controlplane, or worker. Rancher will install RKE Kubernetes on the new nodes, and it will set up each node with the Kubernetes role defined by the node pool. - -### Prerequisites - -- **AWS EC2 Access Key and Secret Key** that will be used to create the instances. See [Amazon Documentation: Creating Access Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey) how to create an Access Key and Secret Key. -- **IAM Policy created** to add to the user of the Access Key And Secret Key. See [Amazon Documentation: Creating IAM Policies (Console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-start) how to create an IAM policy. See our three example JSON policies below: - - [Example IAM Policy](#example-iam-policy) - - [Example IAM Policy with PassRole](#example-iam-policy-with-passrole) (needed if you want to use [Kubernetes Cloud Provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers) or want to pass an IAM Profile to an instance) - - [Example IAM Policy to allow encrypted EBS volumes](#example-iam-policy-to-allow-encrypted-ebs-volumes) -- **IAM Policy added as Permission** to the user. See [Amazon Documentation: Adding Permissions to a User (Console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) how to attach it to an user. - -# Creating an EC2 Cluster - -The steps to create a cluster differ based on your Rancher version. - - - - -1. [Create your cloud credentials](#1-create-your-cloud-credentials) -2. [Create a node template with your cloud credentials and information from EC2](#2-create-a-node-template-with-your-cloud-credentials-and-information-from-ec2) -3. [Create a cluster with node pools using the node template](#3-create-a-cluster-with-node-pools-using-the-node-template) - -### 1. Create your cloud credentials - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **Amazon**. -1. Enter a name for the cloud credential. -1. In the **Default Region** field, select the AWS region where your cluster nodes will be located. -1. Enter your AWS EC2 **Access Key** and **Secret Key**. -1. Click **Create**. - -**Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. - -### 2. Create a node template with your cloud credentials and information from EC2 - -Creating a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for EC2 will allow Rancher to provision new nodes in EC2. Node templates can be reused for other clusters. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates** -1. Click **Add Template**. -1. Fill out a node template for EC2. For help filling out the form, refer to [EC2 Node Template Configuration.](./ec2-node-template-config) -1. Click **Create**. - - >**Note:** If you want to use the [dual-stack](https://kubernetes.io/docs/concepts/services-networking/dual-stack/) feature, there are additional [requirements]({{}}/rke//latest/en/config-options/dual-stack#requirements) that must be taken into consideration. - -### 3. Create a cluster with node pools using the node template - -Add one or more node pools to your cluster. For more information about node pools, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools) - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **Amazon EC2**. -1. Create a node pool for each Kubernetes role. For each node pool, choose a node template that you created. For more information about node pools, including best practices for assigning Kubernetes roles to them, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools) -1. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Use **Cluster Options** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. Refer to [Selecting Cloud Providers]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) to configure the Kubernetes Cloud Provider. For help configuring the cluster, refer to the [RKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options) - - >**Note:** If you want to use the [dual-stack](https://kubernetes.io/docs/concepts/services-networking/dual-stack/) feature, there are additional [requirements]({{}}/rke//latest/en/config-options/dual-stack#requirements) that must be taken into consideration. -1. Click **Create**. - - - - -### 1. Create your cloud credentials - -If you already have a set of cloud credentials to use, skip this section. - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **Amazon**. -1. Enter a name for the cloud credential. -1. In the **Default Region** field, select the AWS region where your cluster nodes will be located. -1. Enter your AWS EC2 **Access Key** and **Secret Key**. -1. Click **Create**. - -**Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. - -### 2. Create your cluster - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Toggle the switch to **RKE2/K3s**. -1. Click **Amazon EC2**. -1. Select a **Cloud Credential**, if more than one exists. Otherwise, it's preselected. -1. Enter a **Cluster Name**. -1. Create a machine pool for each Kubernetes role. Refer to the [best practices]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools#node-roles-in-rke2) for recommendations on role assignments and counts. - 1. For each machine pool, define the machine configuration. Refer to [the EC2 machine configuration reference]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/ec2-machine-config/) for information on configuration options. -1. Use the **Cluster Configuration** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. For help configuring the cluster, refer to the [RKE2 cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/rke2-config-reference/) -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Click **Create**. - - - - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -### Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. - -# IAM Policies - -### Example IAM Policy - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "VisualEditor0", - "Effect": "Allow", - "Action": [ - "ec2:AuthorizeSecurityGroupIngress", - "ec2:Describe*", - "ec2:ImportKeyPair", - "ec2:CreateKeyPair", - "ec2:CreateSecurityGroup", - "ec2:CreateTags", - "ec2:DeleteKeyPair", - "ec2:ModifyInstanceMetadataOptions" - ], - "Resource": "*" - }, - { - "Sid": "VisualEditor1", - "Effect": "Allow", - "Action": [ - "ec2:RunInstances" - ], - "Resource": [ - "arn:aws:ec2:REGION::image/ami-*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:instance/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:placement-group/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:volume/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:subnet/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:key-pair/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:network-interface/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:security-group/*" - ] - }, - { - "Sid": "VisualEditor2", - "Effect": "Allow", - "Action": [ - "ec2:RebootInstances", - "ec2:TerminateInstances", - "ec2:StartInstances", - "ec2:StopInstances" - ], - "Resource": "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:instance/*" - } - ] -} -``` - -### Example IAM Policy with PassRole - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "VisualEditor0", - "Effect": "Allow", - "Action": [ - "ec2:AuthorizeSecurityGroupIngress", - "ec2:Describe*", - "ec2:ImportKeyPair", - "ec2:CreateKeyPair", - "ec2:CreateSecurityGroup", - "ec2:CreateTags", - "ec2:DeleteKeyPair", - "ec2:ModifyInstanceMetadataOptions" - ], - "Resource": "*" - }, - { - "Sid": "VisualEditor1", - "Effect": "Allow", - "Action": [ - "iam:PassRole", - "ec2:RunInstances" - ], - "Resource": [ - "arn:aws:ec2:REGION::image/ami-*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:instance/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:placement-group/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:volume/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:subnet/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:key-pair/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:network-interface/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:security-group/*", - "arn:aws:iam::AWS_ACCOUNT_ID:role/YOUR_ROLE_NAME" - ] - }, - { - "Sid": "VisualEditor2", - "Effect": "Allow", - "Action": [ - "ec2:RebootInstances", - "ec2:TerminateInstances", - "ec2:StartInstances", - "ec2:StopInstances" - ], - "Resource": "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:instance/*" - } - ] -} -``` -### Example IAM Policy to allow encrypted EBS volumes -``` json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "kms:Decrypt", - "kms:GenerateDataKeyWithoutPlaintext", - "kms:Encrypt", - "kms:DescribeKey", - "kms:CreateGrant", - "ec2:DetachVolume", - "ec2:AttachVolume", - "ec2:DeleteSnapshot", - "ec2:DeleteTags", - "ec2:CreateTags", - "ec2:CreateVolume", - "ec2:DeleteVolume", - "ec2:CreateSnapshot" - ], - "Resource": [ - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:volume/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:instance/*", - "arn:aws:ec2:REGION:AWS_ACCOUNT_ID:snapshot/*", - "arn:aws:kms:REGION:AWS_ACCOUNT_ID:key/KMS_KEY_ID" - ] - }, - { - "Effect": "Allow", - "Action": [ - "ec2:DescribeInstances", - "ec2:DescribeTags", - "ec2:DescribeVolumes", - "ec2:DescribeSnapshots" - ], - "Resource": "*" - } - ] -} -``` diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/node-pools.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/node-pools.md deleted file mode 100644 index 4f5700144d8..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/node-pools.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -title: Launching Kubernetes on New Nodes in an Infrastructure Provider -weight: 2205 ---- - -This section covers the following topics: - -- [RKE Clusters](#rke-clusters) - - [Node templates](#node-templates) - - [Node labels](#node-labels) - - [Node taints](#node-taints) - - [Administrator control of node templates](#administrator-control-of-node-templates) - - [Node pools](#node-pools) - - [Node pool taints](#node-pool-taints) - - [About node auto-replace](#about-node-auto-replace) - - [Enabling node auto-replace](#enabling-node-auto-replace) - - [Disabling node auto-replace](#disabling-node-auto-replace) - - [Cloud credentials](#cloud-credentials) - - [Node drivers](#node-drivers) -- [RKE2 Clusters](#rke2-clusters) - - [Node roles in RKE2](#node-roles-in-rke2) - -When you create an RKE or RKE2 cluster using a node template in Rancher, each resulting node pool is shown in a new **Machine Pools** tab. You can see the machine pools by doing the following: - -1. Click **☰ > Cluster Management**. -1. Click the name of the RKE or RKE2 cluster. - -## RKE Clusters - -Using Rancher, you can create pools of nodes based on a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates). This node template defines the parameters you want to use to launch nodes in your infrastructure providers or cloud providers. - -One benefit of installing Kubernetes on node pools hosted by an infrastructure provider is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected. - -The available cloud providers to create a node template are decided based on active [node drivers]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-drivers). - -### Node Templates - -A node template is the saved configuration for the parameters to use when provisioning nodes in a specific cloud provider. These nodes can be launched from the UI. Rancher uses [Docker Machine](https://docs.docker.com/machine/) to provision these nodes. The available cloud providers to create node templates are based on the active node drivers in Rancher. - -After you create a node template in Rancher, it's saved so that you can use this template again to create node pools. Node templates are bound to your login. After you add a template, you can remove them from your user profile. - -#### Node Labels - -You can add [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) on each node template, so that any nodes created from the node template will automatically have these labels on them. - -Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) - -#### Node Taints - -You can add [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) on each node template, so that any nodes created from the node template will automatically have these taints on them. - -Since taints can be added at a node template and node pool, if there is no conflict with the same key and effect of the taints, all taints will be added to the nodes. If there are taints with the same key and different effect, the taints from the node pool will override the taints from the node template. - -#### Administrator Control of Node Templates - -Administrators can control all node templates. Admins can now maintain all the node templates within Rancher. When a node template owner is no longer using Rancher, the node templates created by them can be managed by administrators so the cluster can continue to be updated and maintained. - -To access all node templates, an administrator will need to do the following: - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. - -**Result:** All node templates are listed. The templates can be edited or cloned by clicking the **⋮**. - -### Node Pools - -Using Rancher, you can create pools of nodes based on a [node template](#node-templates). - -A node template defines the configuration of a node, like what operating system to use, number of CPUs, and amount of memory. - -The benefit of using a node pool is that if a node is destroyed or deleted, you can increase the number of live nodes to compensate for the node that was lost. The node pool helps you ensure that the count of the node pool is as expected. - -Each node pool must have one or more nodes roles assigned. - -Each node role (i.e. etcd, controlplane, and worker) should be assigned to a distinct node pool. Although it is possible to assign multiple node roles to a node pool, this should not be done for production clusters. - -The recommended setup is to have: - -- a node pool with the etcd node role and a count of three -- a node pool with the controlplane node role and a count of at least two -- a node pool with the worker node role and a count of at least two - -**RKE1 downstream cluster nodes in an air-gapped environment:** - -By default, Rancher tries to run the Docker Install script when provisioning RKE1 downstream cluster nodes, such as in vSphere. However, the Rancher Docker installation script would fail in air-gapped environments. To work around this issue, you may choose to skip installing Docker when creating a Node Template where Docker is pre-installed onto a VM image. You can accomplish this by selecting **None** in the dropdown list for `Docker Install URL` under **Engine Options** in the Rancher UI. - -
**Engine Options Dropdown:**
-![Engine Options Dropdown]({{}}/img/rancher/node-template-engine-options-rke1.png) - -#### Node Pool Taints - -If you haven't defined [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) on your node template, you can add taints for each node pool. The benefit of adding taints at a node pool is beneficial over adding it at a node template is that you can swap out the node templates without worrying if the taint is on the node template. - -For each taint, they will automatically be added to any created node in the node pool. Therefore, if you add taints to a node pool that have existing nodes, the taints won't apply to existing nodes in the node pool, but any new node added into the node pool will get the taint. - -When there are taints on the node pool and node template, if there is no conflict with the same key and effect of the taints, all taints will be added to the nodes. If there are taints with the same key and different effect, the taints from the node pool will override the taints from the node template. - -#### About Node Auto-replace - -If a node is in a node pool, Rancher can automatically replace unreachable nodes. Rancher will use the existing node template for the given node pool to recreate the node if it becomes inactive for a specified number of minutes. - -> **Important:** Self-healing node pools are designed to help you replace worker nodes for stateless applications. It is not recommended to enable node auto-replace on a node pool of master nodes or nodes with persistent volumes attached, because VMs are treated ephemerally. When a node in a node pool loses connectivity with the cluster, its persistent volumes are destroyed, resulting in data loss for stateful applications. - -Node auto-replace works on top of the Kubernetes node controller. The node controller periodically checks the status of all the nodes (configurable via the `--node-monitor-period` flag of the `kube-controller`). When a node is unreachable, the node controller will taint that node. When this occurs, Rancher will begin its deletion countdown. You can configure the amount of time Rancher waits to delete the node. If the taint is not removed before the deletion countdown ends, Rancher will proceed to delete the node object. Rancher will then provision a node in accordance with the set quantity of the node pool. - -#### Enabling Node Auto-replace - -When you create the node pool, you can specify the amount of time in minutes that Rancher will wait to replace an unresponsive node. - -1. In the form for creating or editing a cluster, go to the **Node Pools** section. -1. Go to the node pool where you want to enable node auto-replace. In the **Recreate Unreachable After** field, enter the number of minutes that Rancher should wait for a node to respond before replacing the node. -1. Fill out the rest of the form for creating or editing the cluster. - -**Result:** Node auto-replace is enabled for the node pool. - -#### Disabling Node Auto-replace - -You can disable node auto-replace from the Rancher UI with the following steps: - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to disable node auto-replace and click **⋮ > Edit Config**. -1. In the **Node Pools** section, go to the node pool where you want to enable node auto-replace. In the **Recreate Unreachable After** field, enter 0. -1. Click **Save**. - -**Result:** Node auto-replace is disabled for the node pool. - -### Cloud Credentials - -Node templates can use cloud credentials to store credentials for launching nodes in your cloud provider, which has some benefits: - -- Credentials are stored as a Kubernetes secret, which is not only more secure, but it also allows you to edit a node template without having to enter your credentials every time. - -- After the cloud credential is created, it can be re-used to create additional node templates. - -- Multiple node templates can share the same cloud credential to create node pools. If your key is compromised or expired, the cloud credential can be updated in a single place, which allows all node templates that are using it to be updated at once. - -After cloud credentials are created, the user can start [managing the cloud credentials that they created]({{}}/rancher/v2.6/en/user-settings/cloud-credentials/). - -### Node Drivers - -If you don't find the node driver that you want to use, you can see if it is available in Rancher's built-in [node drivers and activate it]({{}}/rancher/v2.6/en/admin-settings/drivers/node-drivers/#activating-deactivating-node-drivers), or you can [add your own custom node driver]({{}}/rancher/v2.6/en/admin-settings/drivers/node-drivers/#adding-custom-node-drivers). - -## RKE2 Clusters - -Rancher v2.6 introduces provisioning for [RKE2](https://docs.rke2.io/) clusters directly from the Rancher UI. RKE2, also known as RKE Government, is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector. - -> **Note:** For RKE2 cluster templates, please refer to [this page]({{}}/rancher/v2.6/en/admin-settings/cluster-templates/#rke2-cluster-template) for additional information. - -### Node Roles - -The RKE2 CLI exposes two roles, `server` and `agent`, which represent the Kubernetes node-roles `etcd` + `controlplane` and `worker` respectively. With RKE2 integration in Rancher v2.6, RKE2 node pools can represent more fine-grained role assignments such that `etcd` and `controlplane` roles can be represented. - -The same functionality of using `etcd`, `controlplane` and `worker` nodes is possible in the RKE2 CLI by using flags and node tainting to control where workloads and the Kubernetes master were scheduled. The reason those roles were not implemented as first-class roles in the RKE2 CLI is that RKE2 is conceptualized as a set of raw building blocks that are best leveraged through an orchestration system such as Rancher. - -The implementation of the three node roles in Rancher means that Rancher managed RKE2 clusters are able to easily leverage all of the same architectural best practices that are recommended for RKE clusters. - -In our [recommended cluster architecture]({{}}/rancher/v2.6/en/cluster-provisioning/production/recommended-architecture/), we outline how many nodes of each role clusters should have: - -- At least three nodes with the role etcd to survive losing one node -- At least two nodes with the role controlplane for master component high availability -- At least two nodes with the role worker for workload rescheduling upon node failure \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix-node-template-config/nutanix-node-template-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix-node-template-config/nutanix-node-template-config.md deleted file mode 100644 index a4ae10d8ece..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix-node-template-config/nutanix-node-template-config.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Nutanix Node Template Configuration -weight: 2 ---- - -- [Account Access](#account-access) -- [Scheduling](#scheduling) -- [Instance Options](#instance-options) -- [Networks](#networks) -- [VM Categories](#vm-categories) -- [cloud-init](#cloud-init) - -# Account Access - -| Parameter | Required | Description | Default -|:-----------------------------|:--------:|:-----------------------------------------------------------------|:----- -| Management Endpoint | ✓ | Hostname/IP address of Prism Central | -| Username | ✓ | Username of the Prism Central user | -| Password | ✓ | Password of the Prism Central user | -| Allow insecure communication | | Set to true to allow insecure SSL communication to Prism Central | False - -# Scheduling - -Choose what Nutanix cluster the virtual machine will be scheduled to. - -| Parameter | Required | Description -|:----------|:--------:|:---------------------------------------------------------------------------- -| Cluster | ✓ | Name of the Nutanix cluster where the VM should be deployed (case sensitive) - -# Instance Options - -In the **Instance Options** section, configure the number of vCPUs, memory, and disk size for the VMs created by this template. - -| Parameter | Required | Description | Default -|:---------------------|:--------:|:--------------------------------------------------------------------------------------------|:------- -| CPUs | | Number of vCPUs allocated to the VM (cores) | 2 -| Memory | | Amount of RAM allocated to the VM (MB) | 2 GB -| Template Image | ✓ | Name of the Disk Image template to clone as the VM's primary disk (must support cloud-init) | -| VM Disk Size | | New size of the VM's primary disk (in GiB) | -| Additional Disk Size | | Size of an additional disk to add to the VM (in GiB) | -| Storage Container | | Storage container _UUID_ in which to provision an additional disk | -| Cloud Config YAML | | Cloud-init to provide to the VM (will be patched with Rancher root user) | -| Network | ✓ | Name(s) of the network(s) to attach to the VM | -| VM Categories | | Name(s) of any categories to be applied to the VM | - -The VM may use any modern Linux operating system that is configured with support for [cloud-init](https://cloudinit.readthedocs.io/en/latest/) using the [Config Drive v2 datasource](https://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html). - -# Networks - -The node template allows a VM to be provisioned with multiple networks. In the **Network** field, you can click **Add** to add any networks available to you in AOS. - -# VM Categories - -A category is a grouping of entities into a key value pair. Typically, VMs are assigned to a category based on some criteria. Policies can then be tied to those entities that are assigned (grouped by) a specific category value. - -# cloud-init - -[Cloud-init](https://cloudinit.readthedocs.io/en/latest/) allows you to initialize your nodes by applying configuration on the first boot. This may involve things such as creating users or authorizing SSH keys. - -To make use of cloud-init initialization, paste a cloud config using valid YAML syntax into the **Cloud Config YAML** field. Refer to the [cloud-init documentation](https://cloudinit.readthedocs.io/en/latest/topics/examples.html) for a commented set of examples of supported cloud config directives. - -Note that cloud-init based network configuration is not recommended and only supported via user data `runcmd` rather than by NoCloud or other network configuration datasources. - -Nutanix IP Address Management (IPAM) or another DHCP service is recommended. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix.md deleted file mode 100644 index f009dc078f8..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Creating a Nutanix AOS Cluster -shortTitle: Nutanix -description: Use Rancher to create a Nutanix AOS (AHV) cluster. It may consist of groups of VMs with distinct properties which allow for fine-grained control over the sizing of nodes. -metaDescription: Use Rancher to create a Nutanix AOS (AHV) cluster. It may consist of groups of VMs with distinct properties which allow for fine-grained control over the sizing of nodes. -weight: 2225 ---- - -[Nutanix Acropolis Operating System](https://www.nutanix.com/products/acropolis) (Nutanix AOS) is an operating system for the Nutanix hyper-converged infrastructure platform. AOS comes with a built-in hypervisor called [Acropolis Hypervisor](https://www.nutanix.com/products/ahv), or AHV. By using Rancher with Nutanix AOS (AHV), you can bring cloud operations on-premises. - -Rancher can provision nodes in AOS (AHV) and install Kubernetes on them. When creating a Kubernetes cluster in AOS, Rancher first provisions the specified number of virtual machines by communicating with the Prism Central API. Then it installs Kubernetes on top of the VMs. - -A Nutanix cluster may consist of multiple groups of VMs with distinct properties, such as the amount of memory or the number of vCPUs. This grouping allows for fine-grained control over the sizing of nodes for each Kubernetes role. - -- [Creating a Nutanix Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/nutanix/provisioning-nutanix-clusters/#creating-a-nutanix-aos-cluster) -- [Provisioning Storage]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/nutanix/provisioning-nutanix-clusters) - -# Creating a Nutanix Cluster - -In [this section,](./provisioning-nutanix-clusters) you'll learn how to use Rancher to install an [RKE]({{}}/rke/latest/en/) Kubernetes cluster in Nutanix AOS. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/provisioning-nutanix-clusters/provisioning-nutanix-clusters.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/provisioning-nutanix-clusters/provisioning-nutanix-clusters.md deleted file mode 100644 index de2647ddced..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/nutanix/provisioning-nutanix-clusters/provisioning-nutanix-clusters.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: Provisioning Kubernetes Clusters in Nutanix AOS -weight: 1 ---- - -To use Rancher to install an [RKE]({{}}/rke/latest/en/) Kubernetes cluster in Nutanix AOS (AHV): - -1. Locate Rancher's built-in Nutanix [node driver and activate it]({{}}/rancher/v2.6/en/admin-settings/drivers/node-drivers/#activating-deactivating-node-drivers). - -1. Create a node template, which Rancher will use to provision nodes in Nutanix AOS. - -1. Create a Nutanix AOS cluster in Rancher. When configuring the new cluster, you will define node pools for it. Each node pool will have a Kubernetes role of etcd, controlplane, or worker. Rancher will install RKE Kubernetes on the new nodes, and it will set up each node with the Kubernetes role defined by the node pool. - -For details on configuring the Nutanix AOS node template, refer to the [Nutanix AOS node template configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix-node-template-config/) - -For details on configuring RKE Kubernetes clusters in Rancher, refer to the [cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/rke-config-reference/) - -- [Preparation in Nutanix AOS](#preparation-in-nutanix-aos) -- [Creating a Nutanix AOS Cluster](#creating-a-nutanix-aos-cluster) - -# Preparation in Nutanix AOS - -The following sections describe the requirements for setting up Nutanix AOS so that Rancher can provision VMs and clusters. - -**Note:** The node templates are documented and tested with Nutanix AOS version 5.20.2 and 6.0.1. - -### Create Credentials in Nutanix AOS - -Before proceeding to create a cluster, you must ensure that you have a [Nutanix Prism Central user account](https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_0:wc-user-create-wc-t.html) with admin permissions. When you set up a node template, the template will need to use these credentials. - -### Network Permissions - -You must ensure that the hosts running the Rancher server are able to establish the following network connections: - -- To the Nutanix Prism Central API (usually port 9440/TCP). -- To port 22/TCP and 2376/TCP on the created VMs - -See [Node Networking Requirements]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) for a detailed list of port requirements applicable for creating nodes on an infrastructure provider. - -### VM-VM Anti-Affinity Policies - -Setting up [VM-VM Anti-Affinity Policies](https://portal.nutanix.com/page/documents/details?targetId=AHV-Admin-Guide-v6_1:ahv-vm-anti-affinity-t.html) is recommended. These rules allow VMs assigned the etcd and control-plane roles to operate on separate AHV hosts when they are assigned to different node pools. This practice ensures that the failure of a single physical machine does not affect the availability of those planes. - -# Creating a Nutanix AOS Cluster - -1. [Create a node template ](#1-create-a-node-template) -2. [Create a cluster with node pools using the node template](#2-create-a-cluster-with-node-pools-using-the-node-template) - -### 1. Create a node template - -Creating a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for Nutanix AOS will allow Rancher to provision new nodes in Nutanix AOS. Node templates can be reused for other clusters. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Click **Create**. -1. Click **Add Template**. -1. Click **Nutanix**. -1. Fill out a node template for Nutanix AOS. For help filling out the form, refer to the Nutanix AOS node template [configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/nutanix/nutanix-node-template-config/). -1. Click **Create**. - -### 2. Create a cluster with node pools using the node template - -Use Rancher to create a Kubernetes cluster in Nutanix AOS. - -1. Click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **Nutanix**. -1. Enter a **Cluster Name**, then click **Continue**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users who can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Use **Cluster Options** to choose the version of Kubernetes that will be installed, what network provider will be used, and whether you want to enable project network isolation. To see more cluster options, click on **Show advanced options**. For help configuring the cluster, refer to the [RKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/rke-config-reference/) -1. Add one or more node pools to your cluster. Each node pool uses a node template to provision new nodes. For more information about node pools, including best practices for assigning Kubernetes roles to the nodes, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-pools) -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - - -# Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. - -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-a-vm-template/creating-a-vm-template.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-a-vm-template/creating-a-vm-template.md deleted file mode 100644 index 1ed401c2ebd..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-a-vm-template/creating-a-vm-template.md +++ /dev/null @@ -1,160 +0,0 @@ ---- -title: Creating a vSphere Virtual Machine Template -weight: 4 ---- - -Creating virtual machines in a repeatable and reliable fashion can often be difficult. VMware vSphere offers the ability to build one VM that can then be converted to a template. The template can then be used to create identically configured VMs. Rancher leverages this capability within node pools to create identical RKE1 and RKE2 nodes. - -In order to leverage the template to create new VMs, Rancher has some [specific requirements](#requirements) that the VM must have pre-installed. After you configure the VM with these requirements, you will next need to [prepare the VM](#preparing-your-vm) before [creating the template](#creating-a-template). Finally, once preparation is complete, the VM can be [converted to a template](#converting-to-a-template) and [moved into a content library](#moving-to-a-content-library), ready for Rancher node pool usage. - -- [Requirements](#requirements) -- [Creating a Template](#creating-a-template) -- [Preparing Your VM](#preparing-your-vm) -- [Converting to a Template](#converting-to-a-template) -- [Moving to a content library](#moving-to-a-content-library) -- [Other Resources](#other-resources) - -# Requirements - -There is specific tooling required for both Linux and Windows VMs to be usable by the vSphere node driver. The most critical dependency is [cloud-init](https://cloud-init.io/) for Linux and [cloudbase-init](https://cloudbase.it/cloudbase-init/) for Windows. Both of these are used for provisioning the VMs by configuring the hostname and by setting up the SSH access and the default Rancher user. Users can add additional content to these as desired if other configuration is needed. In addition, other requirements are listed below for reference. - -**Note:** If you have any specific firewall rules or configuration, you will need to add this to the VM before creating a template. - -## Linux Dependencies - -The packages that need to be installed on the template are listed below. These will have slightly different names based on distribution; some distributions ship these by default, for example. - -* curl -* wget -* git -* net-tools -* unzip -* apparmor-parser -* ca-certificates -* cloud-init -* cloud-guest-utils -* cloud-image-utils -* growpart -* cloud-initramfs-growroot -* open-iscsi -* openssh-server -* [open-vm-tools](https://docs.vmware.com/en/VMware-Tools/11.3.0/com.vmware.vsphere.vmwaretools.doc/GUID-8B6EA5B7-453B-48AA-92E5-DB7F061341D1.html) - -## Windows Dependencies - -The list of packages that need to be installed on the template is as follows: - -* Windows Container Feature -* [cloudbase-init](https://cloudbase.it/cloudbase-init/#download) -* [Docker EE](https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server#install-docker) - RKE1 Only - -**Important to note: The configuration for Windows templates varies between RKE1 and RKE2:** -- RKE1 leverages Docker, so any RKE1 templates need to have Docker EE pre-installed as well -- RKE2 does not require Docker EE, and thus it does not need to be installed - -# Creating a Template - -You may either manually create your VM or you can utilize [other alternatives](#alternatives-to-manual-creation) to create your VM. - -## Manual Creation -1. Manually create your VM by following [these instructions](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE8AFBF1-75D1-4172-988C-378C35C9FAF2.html) from VMware. Once you have a VM running, you can manually install the dependencies listed above to configure the VM correctly for the vSphere node driver. -2. Customize as needed based on your specific environment and requirements. -3. Proceed with the final preparation before creating your template. - -## Alternatives to Manual Creation - -Other alternative options to create VMs are listed below: - -* [VMware PowerCLI](https://developer.vmware.com/powercli) -* [Packer](https://www.packer.io/) -* [SaltStack](https://saltproject.io/) -* [Ansible](https://www.ansible.com/) - -Packer is a frequently-used alternative. Refer to this [reference](https://github.com/vmware-samples/packer-examples-for-vsphere) for examples of its usage with vSphere. - -# Preparing Your VM - -After creating a VM with all the required dependencies (and any additional required items), you must perform the most critical step next: preparing the VM to be turned into a template. This preparation will reset critical data such as the VM hostname, IPs, etc., to prevent that information from being brought into a new VM. If you fail to perform this step, you could create a VM with the same hostname, IP address, etc. - -Note that these preparatory steps differ between Linux and Windows. - -## Linux Preparation - -The commands below will reset your VM in Linux: - -```Bash -# Cleaning logs. -if [ -f /var/log/audit/audit.log ]; then - cat /dev/null > /var/log/audit/audit.log -fi -if [ -f /var/log/wtmp ]; then - cat /dev/null > /var/log/wtmp -fi -if [ -f /var/log/lastlog ]; then - cat /dev/null > /var/log/lastlog -fi - -# Cleaning udev rules. -if [ -f /etc/udev/rules.d/70-persistent-net.rules ]; then - rm /etc/udev/rules.d/70-persistent-net.rules -fi - -# Cleaning the /tmp directories -rm -rf /tmp/* -rm -rf /var/tmp/* - -# Cleaning the SSH host keys -rm -f /etc/ssh/ssh_host_* - -# Cleaning the machine-id -truncate -s 0 /etc/machine-id -rm /var/lib/dbus/machine-id -ln -s /etc/machine-id /var/lib/dbus/machine-id - -# Cleaning the shell history -unset HISTFILE -history -cw -echo > ~/.bash_history -rm -fr /root/.bash_history - -# Truncating hostname, hosts, resolv.conf and setting hostname to localhost -truncate -s 0 /etc/{hostname,hosts,resolv.conf} -hostnamectl set-hostname localhost - -# Clean cloud-init -cloud-init clean -s -l -``` - -## Windows Preparation - -Windows has a utility called [sysprep](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation) that is used to generalize an image and reset the same items listed above for Linux. The command is as follows: - -```PowerShell -sysprep.exe /generalize /shutdown /oobe -``` - -# Converting to a Template - -1. Shut down and stop the VM. -2. Right-click on the VM in the inventory list and select **Template**. -3. Click on **Convert to Template**. - -**Result:** Once the process has completed, a template will be available for use. - -For additional information on converting a VM to a template, see the [VMware guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-5B3737CC-28DB-4334-BD18-6E12011CDC9F.html). - -# Moving to a Content library - -Rancher has the ability to use templates provided by a content library. Content libraries store and manage content within vSphere, and they also offer the ability to publish and share that content. - -Below are some helpful links on content libraries: - -* [Create a content library](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A0F1C13-7336-45CE-B211-610D39A6E1F4.html) -* [Clone the template to the content library](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AC1545F0-F8BA-4CD2-96EB-21B3DFAA1DC1.html) - -# Other Resources - -Here is a list of additional resources that may be useful: - -* [Tutorial for creating a Linux template](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/hybrid/server/best-practices/vmware-ubuntu-template) -* [Tutorial for creating a Windows template](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/manage/hybrid/server/best-practices/vmware-windows-template) diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-credentials/creating-credentials.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-credentials/creating-credentials.md deleted file mode 100644 index 55ac548274e..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-credentials/creating-credentials.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Creating Credentials in the vSphere Console -weight: 3 ---- - -This section describes how to create a vSphere username and password. You will need to provide these vSphere credentials to Rancher, which allows Rancher to provision resources in vSphere. - -The following table lists the permissions required for the vSphere user account: - -| Privilege Group | Operations | -|:----------------------|:-----------------------------------------------------------------------| -| Datastore | AllocateSpace
Browse
FileManagement (Low level file operations)
UpdateVirtualMachineFiles
UpdateVirtualMachineMetadata | -| Global | Set custom attribute | -| Network | Assign | -| Resource | AssignVMToPool | -| Virtual Machine | Config (All)
GuestOperations (All)
Interact (All)
Inventory (All)
Provisioning (All) | -| vSphere Tagging | Assign or Unassign vSphere Tag
Assign or Unassign vSphere Tag on Object | - -The following steps create a role with the required privileges and then assign it to a new user in the vSphere console: - -1. From the **vSphere** console, go to the **Administration** page. - -2. Go to the **Roles** tab. - -3. Create a new role. Give it a name and select the privileges listed in the permissions table above. - - {{< img "/img/rancher/rancherroles1.png" "image" >}} - -4. Go to the **Users and Groups** tab. - -5. Create a new user. Fill out the form and then click **OK**. Make sure to note the username and password, because you will need it when configuring node templates in Rancher. - - {{< img "/img/rancher/rancheruser.png" "image" >}} - -6. Go to the **Global Permissions** tab. - -7. Create a new Global Permission. Add the user you created earlier and assign it the role you created earlier. Click **OK**. - - {{< img "/img/rancher/globalpermissionuser.png" "image" >}} - - {{< img "/img/rancher/globalpermissionrole.png" "image" >}} - -**Result:** You now have credentials that Rancher can use to manipulate vSphere resources. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/provisioning-vsphere-clusters/provisioning-vsphere-clusters.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/provisioning-vsphere-clusters/provisioning-vsphere-clusters.md deleted file mode 100644 index 18b9d24a741..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/provisioning-vsphere-clusters/provisioning-vsphere-clusters.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: Provisioning Kubernetes Clusters in vSphere -weight: 1 ---- - -In this section, you'll learn how to use Rancher to install an [RKE]({{}}/rke/latest/en/) Kubernetes cluster in vSphere. - -First, you will set up your vSphere cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision nodes in vSphere. - -Then you will create a vSphere cluster in Rancher, and when configuring the new cluster, you will define node pools for it. Each node pool will have a Kubernetes role of etcd, controlplane, or worker. Rancher will install RKE Kubernetes on the new nodes, and it will set up each node with the Kubernetes role defined by the node pool. - -For details on configuring the vSphere node template, refer to the [vSphere node template configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/) - -For details on configuring RKE Kubernetes clusters in Rancher, refer to the [cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options) - -- [Preparation in vSphere](#preparation-in-vsphere) -- [Creating a vSphere Cluster](#creating-a-vsphere-cluster) - -# Preparation in vSphere - -This section describes the requirements for setting up vSphere so that Rancher can provision VMs and clusters. - -The node templates are documented and tested with the vSphere Web Services API version 6.5. - -### Create Credentials in vSphere - -Before proceeding to create a cluster, you must ensure that you have a vSphere user with sufficient permissions. When you set up a node template, the template will need to use these vSphere credentials. - -Refer to this [how-to guide]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/vsphere/creating-credentials) for instructions on how to create a user in vSphere with the required permissions. These steps result in a username and password that you will need to provide to Rancher, which allows Rancher to provision resources in vSphere. - -### Network Permissions - -It must be ensured that the hosts running the Rancher server are able to establish the following network connections: - -- To the vSphere API on the vCenter server (usually port 443/TCP). -- To the Host API (port 443/TCP) on all ESXi hosts used to instantiate virtual machines for the clusters (*only required when using the ISO creation method*). -- To port 22/TCP and 2376/TCP on the created VMs - -See [Node Networking Requirements]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) for a detailed list of port requirements applicable for creating nodes on an infrastructure provider. - -### Valid ESXi License for vSphere API Access - -The free ESXi license does not support API access. The vSphere servers must have a valid or evaluation ESXi license. - -### VM-VM Affinity Rules for Clusters with DRS - -If you have a cluster with DRS enabled, setting up [VM-VM Affinity Rules](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-7297C302-378F-4AF2-9BD6-6EDB1E0A850A.html) is recommended. These rules allow VMs assigned the etcd and control-plane roles to operate on separate ESXi hosts when they are assigned to different node pools. This practice ensures that the failure of a single physical machine does not affect the availability of those planes. - -# Creating a vSphere Cluster - -The a vSphere cluster is created in Rancher depends on the Rancher version. - -1. [Create your cloud credentials](#1-create-your-cloud-credentials) -2. [Create a node template with your cloud credentials](#2-create-a-node-template-with-your-cloud-credentials) -3. [Create a cluster with node pools using the node template](#3-create-a-cluster-with-node-pools-using-the-node-template) - -### 1. Create your cloud credentials - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click **VMware vSphere**. -1. Enter your vSphere credentials. For help, refer to **Account Access** in the [node template configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/) -1. Click **Create**. - -**Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. - -### 2. Create a node template with your cloud credentials - -Creating a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for vSphere will allow Rancher to provision new nodes in vSphere. Node templates can be reused for other clusters. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Click **Create**. -1. Click **Add Template**. -1. Click **vSphere**. -1. Fill out a node template for vSphere. For help filling out the form, refer to the vSphere node template [configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/). -1. Click **Create**. - -### 3. Create a cluster with node pools using the node template - -Use Rancher to create a Kubernetes cluster in vSphere. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **VMware vSphere**. -1. Enter a **Cluster Name** and use your vSphere cloud credentials. Click **Continue**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Use **Cluster Options** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options**. For help configuring the cluster, refer to the [RKE cluster configuration reference.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options) -1. If you want to dynamically provision persistent storage or other infrastructure later, you will need to enable the vSphere cloud provider by modifying the cluster YAML file. For details, refer to [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere) -1. Add one or more node pools to your cluster. Each node pool uses a node template to provision new nodes. For more information about node pools, including best practices for assigning Kubernetes roles to the nodes, see [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-pools) -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - - -# Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. -- **Provision Storage:** For an example of how to provision storage in vSphere using Rancher, refer to [this section.]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/examples/vsphere) In order to dynamically provision storage in vSphere, the vSphere provider must be [enabled.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/vsphere-node-template-config.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/vsphere-node-template-config.md deleted file mode 100644 index 3cc65593540..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/vsphere-node-template-config.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: VSphere Node Template Configuration -weight: 2 ---- - -- [Account Access](#account-access) -- [Scheduling](#scheduling) -- [Instance Options](#instance-options) -- [Networks](#networks) -- [Node tags and custom attributes](#node-tags-and-custom-attributes) -- [cloud-init](#cloud-init) - -# Account Access - -| Parameter | Required | Description | -|:----------------------|:--------:|:-----| -| Cloud Credentials | * | Your vSphere account access information, stored in a [cloud credential.]({{}}/rancher/v2.6/en/user-settings/cloud-credentials/) | - -Your cloud credential has these fields: - -| Credential Field | Description | -|-----------------|--------------| -| vCenter or ESXi Server | Enter the vCenter or ESXi hostname/IP. ESXi is the virtualization platform where you create and run virtual machines and virtual appliances. vCenter Server is the service through which you manage multiple hosts connected in a network and pool host resources. | -| Port | Optional: configure configure the port of the vCenter or ESXi server. | -| Username and password | Enter your vSphere login username and password. | - -# Scheduling - -Choose what hypervisor the virtual machine will be scheduled to. - -The fields in the **Scheduling** section should auto-populate with the data center and other scheduling options that are available to you in vSphere. - -| Field | Required | Explanation | -|---------|---------------|-----------| -| Data Center | * | Choose the name/path of the data center where the VM will be scheduled. | -| Resource Pool | | Name of the resource pool to schedule the VMs in. Resource pools can be used to partition available CPU and memory resources of a standalone host or cluster, and they can also be nested. Leave blank for standalone ESXi. If not specified, the default resource pool is used. | -| Data Store | * | If you have a data store cluster, you can toggle the **Data Store** field. This lets you select a data store cluster where your VM will be scheduled to. If the field is not toggled, you can select an individual disk. | -| Folder | | Name of a folder in the datacenter to create the VMs in. Must already exist. The VM folders in this dropdown menu directly correspond to your VM folders in vSphere. The folder name should be prefaced with `vm/` in your vSphere config file. | -| Host | | The IP of the host system to schedule VMs in. Leave this field blank for a standalone ESXi or for a cluster with DRS (Distributed Resource Scheduler). If specified, the host system's pool will be used and the **Resource Pool** parameter will be ignored. | - -# Instance Options - -In the **Instance Options** section, configure the number of vCPUs, memory, and disk size for the VMs created by this template. - -| Parameter | Required | Description | -|:----------------|:--------:|:-----------| -| CPUs | * | Number of vCPUS to assign to VMs. | -| Memory | * | Amount of memory to assign to VMs. | -| Disk | * | Size of the disk (in MB) to attach to the VMs. | -| Creation method | * | The method for setting up an operating system on the node. The operating system can be installed from an ISO or from a VM template. Depending on the creation method, you will also have to specify a VM template, content library, existing VM, or ISO. For more information on creation methods, refer to [About VM Creation Methods.](#about-vm-creation-methods) | -| Cloud Init | | URL of a `cloud-config.yml` file or URL to provision VMs with. This file allows further customization of the operating system, such as network configuration, DNS servers, or system daemons. The operating system must support `cloud-init`. | -| Networks | | Name(s) of the network to attach the VM to. | -| Configuration Parameters used for guestinfo | | Additional configuration parameters for the VMs. These correspond to the [Advanced Settings](https://kb.vmware.com/s/article/1016098) in the vSphere console. Example use cases include providing RancherOS [guestinfo]({{< baseurl >}}/os/v1.x/en/installation/cloud/vmware-esxi/#vmware-guestinfo) parameters or enabling disk UUIDs for the VMs (`disk.EnableUUID=TRUE`). | - - -### About VM Creation Methods - -In the **Creation method** field, configure the method used to provision VMs in vSphere. Available options include creating VMs that boot from a RancherOS ISO or creating VMs by cloning from an existing virtual machine or [VM template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F7BF0E6B-7C4F-4E46-8BBF-76229AEA7220.html). - -The existing VM or template may use any modern Linux operating system that is configured with support for [cloud-init](https://cloudinit.readthedocs.io/en/latest/) using the [NoCloud datasource](https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html). - -Choose the way that the VM will be created: - -- **Deploy from template: Data Center:** Choose a VM template that exists in the data center that you selected. -- **Deploy from template: Content Library:** First, select the [Content Library](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-254B2CE8-20A8-43F0-90E8-3F6776C2C896.html) that contains your template, then select the template from the populated list **Library templates**. -- **Clone an existing virtual machine:** In the **Virtual machine** field, choose an existing VM that the new VM will be cloned from. -- **Install from boot2docker ISO:** Ensure that the **OS ISO URL** field contains the URL of a VMware ISO release for RancherOS (`rancheros-vmware.iso`). Note that this URL must be accessible from the nodes running your Rancher server installation. - -# Networks - -The node template now allows a VM to be provisioned with multiple networks. In the **Networks** field, you can now click **Add Network** to add any networks available to you in vSphere. - -# Node Tags and Custom Attributes - -Tags allow you to attach metadata to objects in the vSphere inventory to make it easier to sort and search for these objects. - -For tags, all your vSphere tags will show up as options to select from in your node template. - -In the custom attributes, Rancher will let you select all the custom attributes you have already set up in vSphere. The custom attributes are keys and you can enter values for each one. - -> **Note:** Custom attributes are a legacy feature that will eventually be removed from vSphere. - -# cloud-init - -[Cloud-init](https://cloudinit.readthedocs.io/en/latest/) allows you to initialize your nodes by applying configuration on the first boot. This may involve things such as creating users, authorizing SSH keys or setting up the network. - -To make use of cloud-init initialization, create a cloud config file using valid YAML syntax and paste the file content in the the **Cloud Init** field. Refer to the [cloud-init documentation.](https://cloudinit.readthedocs.io/en/latest/topics/examples.html) for a commented set of examples of supported cloud config directives. - -Note that cloud-init is not supported when using the ISO creation method. diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere.md deleted file mode 100644 index e11d83949fb..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Creating a vSphere Cluster -shortTitle: vSphere -description: Use Rancher to create a vSphere cluster. It may consist of groups of VMs with distinct properties which allow for fine-grained control over the sizing of nodes. -metaDescription: Use Rancher to create a vSphere cluster. It may consist of groups of VMs with distinct properties which allow for fine-grained control over the sizing of nodes. -weight: 2225 ---- - -By using Rancher with vSphere, you can bring cloud operations on-premises. - -Rancher can provision nodes in vSphere and install Kubernetes on them. When creating a Kubernetes cluster in vSphere, Rancher first provisions the specified number of virtual machines by communicating with the vCenter API. Then it installs Kubernetes on top of them. - -A vSphere cluster may consist of multiple groups of VMs with distinct properties, such as the amount of memory or the number of vCPUs. This grouping allows for fine-grained control over the sizing of nodes for each Kubernetes role. - -- [vSphere Enhancements in Rancher v2.3](#vsphere-enhancements-in-rancher-v2-3) -- [Creating a vSphere Cluster](#creating-a-vsphere-cluster) -- [Provisioning Storage](#provisioning-storage) -- [Enabling the vSphere Cloud Provider](#enabling-the-vsphere-cloud-provider) - -# vSphere Enhancements in Rancher v2.3 - -The vSphere node templates have been updated, allowing you to bring cloud operations on-premises with the following enhancements: - -### Self-healing Node Pools - -One of the biggest advantages of provisioning vSphere nodes with Rancher is that it allows you to take advantage of Rancher's self-healing node pools, also called the [node auto-replace feature,]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#about-node-auto-replace) in your on-premises clusters. Self-healing node pools are designed to help you replace worker nodes for stateless applications. When Rancher provisions nodes from a node template, Rancher can automatically replace unreachable nodes. - -> **Important:** It is not recommended to enable node auto-replace on a node pool of master nodes or nodes with persistent volumes attached, because VMs are treated ephemerally. When a node in a node pool loses connectivity with the cluster, its persistent volumes are destroyed, resulting in data loss for stateful applications. - -### Dynamically Populated Options for Instances and Scheduling - -Node templates for vSphere have been updated so that when you create a node template with your vSphere credentials, the template is automatically populated with the same options for provisioning VMs that you have access to in the vSphere console. - -For the fields to be populated, your setup needs to fulfill the [prerequisites.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/vsphere/provisioning-vsphere-clusters/#prerequisites) - -### More Supported Operating Systems - -You can provision VMs with any operating system that supports `cloud-init`. Only YAML format is supported for the [cloud config.](https://cloudinit.readthedocs.io/en/latest/topics/examples.html) - -### Video Walkthrough of v2.3.3 Node Template Features - -In this YouTube video, we demonstrate how to set up a node template with the new features designed to help you bring cloud operations to on-premises clusters. - -{{< youtube id="dPIwg6x1AlU">}} - -# Creating a vSphere Cluster - -In [this section,](./provisioning-vsphere-clusters) you'll learn how to use Rancher to install an [RKE]({{}}/rke/latest/en/) Kubernetes cluster in vSphere. - -# Provisioning Storage - -For an example of how to provision storage in vSphere using Rancher, refer to [this section.]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/examples/vsphere) In order to dynamically provision storage in vSphere, the vSphere provider must be [enabled.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere) - -# Enabling the vSphere Cloud Provider - -When a cloud provider is set up in Rancher, the Rancher server can automatically provision new infrastructure for the cluster, including new nodes or persistent storage devices. - -For details, refer to the section on [enabling the vSphere cloud provider.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere) diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/options/options.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/options/options.md deleted file mode 100644 index fa55f4c6be3..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/options/options.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: RKE Cluster Configuration -weight: 2300 ---- - -This page has moved [here.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/rke-config-reference) diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rancher-agents/rancher-agents.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rancher-agents/rancher-agents.md deleted file mode 100644 index 225dc2402f2..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rancher-agents/rancher-agents.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Rancher Agents -weight: 2400 ---- - -There are two different agent resources deployed on Rancher managed clusters: - -- [cattle-cluster-agent](#cattle-cluster-agent) -- [cattle-node-agent](#cattle-node-agent) - -For a conceptual overview of how the Rancher server provisions clusters and communicates with them, refer to the [architecture]({{}}/rancher/v2.6/en/overview/architecture/) - -### cattle-cluster-agent - -The `cattle-cluster-agent` is used to connect to the Kubernetes API of [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) clusters. The `cattle-cluster-agent` is deployed using a Deployment resource. - -### cattle-node-agent - -The `cattle-node-agent` is used to interact with nodes in a [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) cluster when performing cluster operations. Examples of cluster operations are upgrading Kubernetes version and creating/restoring etcd snapshots. The `cattle-node-agent` is deployed using a DaemonSet resource to make sure it runs on every node. The `cattle-node-agent` is used as fallback option to connect to the Kubernetes API of [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) clusters when `cattle-cluster-agent` is unavailable. - -### Scheduling rules - -The `cattle-cluster-agent` uses a fixed fixed set of tolerations (listed below, if no controlplane nodes are visible in the cluster) or dynamically added tolerations based on taints applied to the controlplane nodes. This structure allows for [Taint based Evictions](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions) to work properly for `cattle-cluster-agent`. The default tolerations are described below. If controlplane nodes are present the cluster, the tolerations will be replaced with tolerations matching the taints on the controlplane nodes. - -| Component | nodeAffinity nodeSelectorTerms | nodeSelector | Tolerations | -| ---------------------- | ------------------------------------------ | ------------ | ------------------------------------------------------------------------------ | -| `cattle-cluster-agent` | `beta.kubernetes.io/os:NotIn:windows` | none | **Note:** These are the default tolerations, and will be replaced by tolerations matching taints applied to controlplane nodes.

`effect:NoSchedule`
`key:node-role.kubernetes.io/controlplane`
`value:true`

`effect:NoSchedule`
`key:node-role.kubernetes.io/control-plane`
`operator:Exists`

`effect:NoSchedule`
`key:node-role.kubernetes.io/master`
`operator:Exists` | -| `cattle-node-agent` | `beta.kubernetes.io/os:NotIn:windows` | none | `operator:Exists` | - -The `cattle-cluster-agent` Deployment has preferred scheduling rules using `preferredDuringSchedulingIgnoredDuringExecution`, favoring to be scheduled on nodes with the `controlplane` node. When there are no controlplane nodes visible in the cluster (this is usually the case when using [Clusters from Hosted Kubernetes Providers]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/)), you can add the label `cattle.io/cluster-agent=true` on a node to prefer scheduling the `cattle-cluster-agent` pod to that node. - -See [Kubernetes: Assigning Pods to Nodes](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) to find more information about scheduling rules. - -The `preferredDuringSchedulingIgnoredDuringExecution` configuration is shown in the table below: - -| Weight | Expression | -| ------ | ------------------------------------------------ | -| 100 | `node-role.kubernetes.io/controlplane:In:"true"` | -| 100 | `node-role.kubernetes.io/control-plane:In:"true"` | -| 100 | `node-role.kubernetes.io/master:In:"true"` | -| 1 | `cattle.io/cluster-agent:In:"true"` | - diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rke-clusters.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rke-clusters.md deleted file mode 100644 index 21f9d9de5d5..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/rke-clusters.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Launching Kubernetes with Rancher -weight: 4 ---- - -You can have Rancher launch a Kubernetes cluster using any nodes you want. When Rancher deploys Kubernetes onto these nodes, you can choose between [Rancher Kubernetes Engine]({{}}/rke/latest/en/) (RKE) or [RKE2](https://docs.rke2.io) distributions. Rancher can launch Kubernetes on any computers, including: - -- Bare-metal servers -- On-premise virtual machines -- Virtual machines hosted by an infrastructure provider - -Rancher can install Kubernetes on existing nodes, or it can dynamically provision nodes in an infrastructure provider and install Kubernetes on them. - -Rancher can also create pools of nodes. One benefit of installing Kubernetes on node pools hosted by an infrastructure provider is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected. - -## RKE - -### Requirements - -If you use RKE to set up a cluster, your nodes must meet the [requirements]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements) for nodes in downstream user clusters. - -### Launching Kubernetes on New Nodes in an Infrastructure Provider - -Using Rancher, you can create pools of nodes based on a [node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates). This node template defines the parameters you want to use to launch nodes in your cloud providers. - -One benefit of installing Kubernetes on node pools hosted by an infrastructure provider is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected. - -For more information, refer to the section on [launching Kubernetes on new nodes.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) - -### Launching Kubernetes on Existing Custom Nodes - -In this scenario, you want to install Kubernetes on bare-metal servers, on-prem virtual machines, or virtual machines that already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine. - -If you want to reuse a node from a previous custom cluster, [clean the node]({{}}/rancher/v2.6/en/cluster-admin/cleaning-cluster-nodes/) before using it in a cluster again. If you reuse a node that hasn't been cleaned, cluster provisioning may fail. - -For more information, refer to the section on [custom nodes.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/) - -# Programmatically Creating RKE Clusters - -The most common way to programmatically deploy RKE clusters through Rancher is by using the Rancher2 Terraform provider. The documentation for creating clusters with Terraform is [here.](https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster) - -## RKE2 - -Rancher v2.6 introduced provisioning for [RKE2](https://docs.rke2.io/) clusters directly from the Rancher UI. RKE2, also known as RKE Government, is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector. In Rancher v.2.6.4 and earlier, RKE2 provisioning was in tech preview. - -Note that in Rancher v2.6.5, RKE2 provisioning became GA. - -### Requirements - -If you use RKE2 to set up a cluster, your nodes must meet the [requirements](https://docs.rke2.io/install/requirements/) for nodes in downstream user clusters. - -### Launching Kubernetes on New Nodes in an Infrastructure Provider - -RKE2 provisioning is built on top of a new provisioning framework that leverages the upstream [Cluster API](https://github.com/kubernetes-sigs/cluster-api) project. With this new provisioning framework, you can: - -- Provision RKE2 clusters onto any provider for which Rancher has a node driver -- Fully configure RKE2 clusters within Rancher -- Choose CNI options Calico, Cilium, and Multus in addition to Canal - -RKE2 provisioning also includes installing RKE2 on clusters with Windows nodes. - -Windows features for RKE2 include: - -- Windows supports the vSphere node driver -- Calico CNI for Windows RKE2 custom clusters -- Project Network Isolation (PNI) for Calico -- Windows Containers with RKE2 powered by containerd -- Provisioning of Windows RKE2 clusters through Terraform -- Provisioning of Windows RKE2 custom clusters directly from the Rancher UI - -Windows Support for RKE2 Custom Clusters requires choosing Calico as the CNI. - -### Launching Kubernetes on Existing Custom Nodes - -RKE2 provisioning also allows you to install custom clusters on pre-provisioned VMs or bare-metal nodes. - -If you want to reuse a node from a previous custom cluster, clean the node before using it in a cluster again. If you reuse a node that hasn't been cleaned, cluster provisioning may fail. - -# Programmatically Creating RKE2 Clusters - -The most common way to programmatically deploy RKE2 clusters through Rancher is by using the Rancher2 Terraform provider. The documentation for creating clusters with Terraform is [here.](https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster_v2) \ No newline at end of file diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/azure-storageclass/azure-storageclass.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/azure-storageclass/azure-storageclass.md deleted file mode 100644 index 23e41953557..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/azure-storageclass/azure-storageclass.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Configuration for Storage Classes in Azure -weight: 3 ---- - -If you are using Azure VMs for your nodes, you can use [Azure files](https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv) as a StorageClass for the cluster. - -In order to have the Azure platform create the required storage resources, follow these steps: - -1. [Configure the Azure cloud provider.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/azure) -1. Configure `kubectl` to connect to your cluster. -1. Copy the `ClusterRole` and `ClusterRoleBinding` manifest for the service account: - - --- - apiVersion: rbac.authorization.k8s.io/v1 - kind: ClusterRole - metadata: - name: system:azure-cloud-provider - rules: - - apiGroups: [''] - resources: ['secrets'] - verbs: ['get','create'] - --- - apiVersion: rbac.authorization.k8s.io/v1 - kind: ClusterRoleBinding - metadata: - name: system:azure-cloud-provider - roleRef: - kind: ClusterRole - apiGroup: rbac.authorization.k8s.io - name: system:azure-cloud-provider - subjects: - - kind: ServiceAccount - name: persistent-volume-binder - namespace: kube-system - -1. Create these in your cluster using one of the follow command. - - ``` - # kubectl create -f - ``` diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/host-gateway-requirements.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/host-gateway-requirements.md deleted file mode 100644 index ee075c394de..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/host-gateway-requirements.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Networking Requirements for Host Gateway (L2bridge) -weight: 1000 ---- - -This section describes how to configure custom Windows clusters that are using *Host Gateway (L2bridge)* mode. - -### Disabling Private IP Address Checks - -If you are using *Host Gateway (L2bridge)* mode and hosting your nodes on any of the cloud services listed below, you must disable the private IP address checks for both your Linux or Windows hosts on startup. To disable this check for each node, follow the directions provided by each service below. - -Service | Directions to disable private IP address checks ---------|------------------------------------------------ -Amazon EC2 | [Disabling Source/Destination Checks](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html#EIP_Disable_SrcDestCheck) -Google GCE | [Enabling IP Forwarding for Instances](https://cloud.google.com/vpc/docs/using-routes#canipforward) (By default, a VM cannot forward a packet originated by another VM) -Azure VM | [Enable or Disable IP Forwarding](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface#enable-or-disable-ip-forwarding) - -### Cloud-hosted VM Routes Configuration - -If you are using the [**Host Gateway (L2bridge)**](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw) backend of Flannel, all containers on the same node belong to a private subnet, and traffic routes from a subnet on one node to a subnet on another node through the host network. - -- When worker nodes are provisioned on AWS, virtualization clusters, or bare metal servers, make sure they belong to the same layer 2 subnet. If the nodes don't belong to the same layer 2 subnet, `host-gw` networking will not work. - -- When worker nodes are provisioned on GCE or Azure, they are not on the same layer 2 subnet. Nodes on GCE and Azure belong to a routable layer 3 network. Follow the instructions below to configure GCE and Azure so that the cloud network knows how to route the host subnets on each node. - -To configure host subnet routing on GCE or Azure, first run the following command to find out the host subnets on each worker node: - -```bash -kubectl get nodes -o custom-columns=nodeName:.metadata.name,nodeIP:status.addresses[0].address,routeDestination:.spec.podCIDR -``` - -Then follow the instructions for each cloud provider to configure routing rules for each node: - -Service | Instructions ---------|------------- -Google GCE | For GCE, add a static route for each node: [Adding a Static Route](https://cloud.google.com/vpc/docs/using-routes#addingroute). -Azure VM | For Azure, create a routing table: [Custom Routes: User-defined](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview#user-defined). diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-clusters.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-clusters.md deleted file mode 100644 index 5db4add3d41..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-clusters.md +++ /dev/null @@ -1,281 +0,0 @@ ---- -title: Launching Kubernetes on Windows Clusters -weight: 2240 ---- - -When provisioning a [custom cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes) using Rancher, Rancher uses RKE (the Rancher Kubernetes Engine) to install Kubernetes on your existing nodes. - -In a Windows cluster provisioned with Rancher, the cluster must contain both Linux and Windows nodes. The Kubernetes controlplane can only run on Linux nodes, and the Windows nodes can only have the worker role. Windows nodes can only be used for deploying workloads. - -Some other requirements for Windows clusters include: - -- You can only add Windows nodes to a cluster if Windows support is enabled when the cluster is created. Windows support cannot be enabled for existing clusters. -- Kubernetes 1.15+ is required. -- The Flannel network provider must be used. -- Windows nodes must have 50 GB of disk space. - -For the full list of requirements, see [this section.](#requirements-for-windows-clusters) - -For a summary of Kubernetes features supported in Windows, see the Kubernetes documentation on [supported functionality and limitations for using Kubernetes with Windows](https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#supported-functionality-and-limitations) or the [guide for scheduling Windows containers in Kubernetes](https://kubernetes.io/docs/setup/production-environment/windows/user-guide-windows-containers/). - -This guide covers the following topics: - - - -- [Changes in Rancher v2.6](#changes-in-rancher-v2-6) -- [Requirements](#requirements-for-windows-clusters) -- [Tutorial: How to Create a Cluster with Windows Support](#tutorial-how-to-create-a-cluster-with-windows-support) -- [Configuration for Storage Classes in Azure](#configuration-for-storage-classes-in-azure) - - -# Changes in Rancher v2.6 - -Rancher v2.6 introduces provisioning for [RKE2](https://docs.rke2.io/) clusters directly from the Rancher UI. RKE2, also known as RKE Government, is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector. - -As of Rancher v2.6.5, provisioning for RKE2 is GA. - -The RKE2 provisioning feature also includes installing RKE2 on Windows clusters. Windows features for RKE2 include: - -- Windows Containers with RKE2 powered by containerd -- Added provisioning of Windows RKE2 custom clusters directly from the Rancher UI -- Calico CNI for Windows RKE2 custom clusters -- SAC releases of Windows Server (2004 and 20H2) are included in the technical preview - -Windows Support for RKE2 Custom Clusters requires choosing Calico as the CNI. - ->**Important:** Rancher will allow Windows workload pods to deploy on both Windows and Linux worker nodes by default. When creating mixed clusters in RKE2, you must edit the `nodeSelector` in the chart to direct the pods to be placed onto a compatible Windows node. Refer to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector) for more information on how to use `nodeSelector` to assign pods to nodes. - -# Requirements for Windows Clusters - -The general node requirements for networking, operating systems, and Docker are the same as the node requirements for a [Rancher installation]({{}}/rancher/v2.6/en/installation/requirements/). - -### OS and Docker Requirements - -Our support for Windows Server and Windows containers match the Microsoft official lifecycle for LTSC (Long-Term Servicing Channel) and SAC (Semi-Annual Channel). - -For the support lifecycle dates for Windows Server, see the [Microsoft Documentation.](https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-release-info) - -### Kubernetes Version - -Kubernetes v1.15+ is required. - -If you are using Kubernetes v1.21 with Windows Server 20H2 Standard Core, the patch "2019-08 Servicing Stack Update for Windows Server" must be installed on the node. - -### Node Requirements - -The hosts in the cluster need to have at least: - -- 2 core CPUs -- 5 GB memory -- 50 GB disk space - -Rancher will not provision the node if the node does not meet these requirements. - -### Networking Requirements - -Before provisioning a new cluster, be sure that you have already installed Rancher on a device that accepts inbound network traffic. This is required in order for the cluster nodes to communicate with Rancher. If you have not already installed Rancher, please refer to the [installation documentation]({{}}/rancher/v2.6/en/installation/) before proceeding with this guide. - -Rancher only supports Windows using Flannel as the network provider. - -There are two network options: [**Host Gateway (L2bridge)**](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw) and [**VXLAN (Overlay)**](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan). The default option is **VXLAN (Overlay)** mode. - -For **Host Gateway (L2bridge)** networking, it's best to use the same Layer 2 network for all nodes. Otherwise, you need to configure the route rules for them. For details, refer to the [documentation on configuring cloud-hosted VM routes.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/#cloud-hosted-vm-routes-configuration) You will also need to [disable private IP address checks]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/#disabling-private-ip-address-checks) if you are using Amazon EC2, Google GCE, or Azure VM. - -For **VXLAN (Overlay)** networking, the [KB4489899](https://support.microsoft.com/en-us/help/4489899) hotfix must be installed. Most cloud-hosted VMs already have this hotfix. - -If you are configuring DHCP options sets for an AWS virtual private cloud, note that in the `domain-name` option field, only one domain name can be specified. According to the DHCP options [documentation:](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_DHCP_Options.html) - -> Some Linux operating systems accept multiple domain names separated by spaces. However, other Linux operating systems and Windows treat the value as a single domain, which results in unexpected behavior. If your DHCP options set is associated with a VPC that has instances with multiple operating systems, specify only one domain name. - -### Rancher on vSphere with ESXi 6.7u2 and above - -If you are using Rancher on VMware vSphere with ESXi 6.7u2 or later with Red Hat Enterprise Linux 8.3, CentOS 8.3, or SUSE Enterprise Linux 15 SP2 or later, it is necessary to disable the `vmxnet3` virtual network adapter hardware offloading feature. Failure to do so will result in all network connections between pods on different cluster nodes to fail with timeout errors. All connections from Windows pods to critical services running on Linux nodes, such as CoreDNS, will fail as well. It is also possible that external connections may fail. This issue is the result of Linux distributions enabling the hardware offloading feature in `vmxnet3` and a bug in the `vmxnet3` hardware offloading feature that results in the discarding of packets for guest overlay traffic. To address this issue, it is necessary disable the `vmxnet3` hardware offloading feature. This setting does not survive reboot, so it is necessary to disable on every boot. The recommended course of action is to create a systemd unit file at `/etc/systemd/system/disable_hw_offloading.service`, which disables the `vmxnet3` hardware offloading feature on boot. A sample systemd unit file which disables the `vmxnet3` hardware offloading feature is as follows. Note that `` must be customized to the host `vmxnet3` network interface, e.g., `ens192`: - -``` -[Unit] -Description=Disable vmxnet3 hardware offloading feature - -[Service] -Type=oneshot -ExecStart=ethtool -K tx-udp_tnl-segmentation off -ExecStart=ethtool -K tx-udp_tnl-csum-segmentation off -StandardOutput=journal - -[Install] -WantedBy=multi-user.target -``` -Then set the appropriate permissions on the systemd unit file: -``` -chmod 0644 /etc/systemd/system/disable_hw_offloading.service -``` -Finally, enable the systemd service: -``` -systemctl enable disable_hw_offloading.service -``` - -### Architecture Requirements - -The Kubernetes cluster management nodes (`etcd` and `controlplane`) must be run on Linux nodes. - -The `worker` nodes, which is where your workloads will be deployed on, will typically be Windows nodes, but there must be at least one `worker` node that is run on Linux in order to run the Rancher cluster agent, DNS, metrics server, and Ingress related containers. - -We recommend the minimum three-node architecture listed in the table below, but you can always add additional Linux and Windows workers to scale up your cluster for redundancy: - - - -| Node | Operating System | Kubernetes Cluster Role(s) | Purpose | -| ------ | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | -| Node 1 | Linux (Ubuntu Server 18.04 recommended) | Control plane, etcd, worker | Manage the Kubernetes cluster | -| Node 2 | Linux (Ubuntu Server 18.04 recommended) | Worker | Support the Rancher Cluster agent, Metrics server, DNS, and Ingress for the cluster | -| Node 3 | Windows (Windows Server core version 1809 or above) | Worker | Run your Windows containers | - -### Container Requirements - -Windows requires that containers must be built on the same Windows Server version that they are being deployed on. Therefore, containers must be built on Windows Server core version 1809 or above. If you have existing containers built for an earlier Windows Server core version, they must be re-built on Windows Server core version 1809 or above. - -### Cloud Provider Specific Requirements - -If you set a Kubernetes cloud provider in your cluster, some additional steps are required. You might want to set a cloud provider if you want to want to leverage a cloud provider's capabilities, for example, to automatically provision storage, load balancers, or other infrastructure for your cluster. Refer to [this page]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) for details on how to configure a cloud provider cluster of nodes that meet the prerequisites. - -If you are using the GCE (Google Compute Engine) cloud provider, you must do the following: - -- Enable the GCE cloud provider in the `cluster.yml` by following [these steps.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/gce) -- When provisioning the cluster in Rancher, choose **Custom cloud provider** as the cloud provider in the Rancher UI. - -# Tutorial: How to Create a Cluster with Windows Support - -This tutorial describes how to create a Rancher-provisioned cluster with the three nodes in the [recommended architecture.](#guide-architecture) - -When you provision a cluster with Rancher on existing nodes, you will add nodes to the cluster by installing the [Rancher agent]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/) on each one. When you create or edit your cluster from the Rancher UI, you will see a **Customize Node Run Command** that you can run on each server to add it to your cluster. - -To set up a cluster with support for Windows nodes and containers, you will need to complete the tasks below. - - - -1. [Provision Hosts](#1-provision-hosts) -1. [Create the Cluster on Existing Nodes](#2-create-the-cluster-on-existing-nodes) -1. [Add Nodes to the Cluster](#3-add-nodes-to-the-cluster) -1. [Optional: Configuration for Azure Files](#4-optional-configuration-for-azure-files) - - -# 1. Provision Hosts - -To begin provisioning a cluster on existing nodes with Windows support, prepare your hosts. - -Your hosts can be: - -- Cloud-hosted VMs -- VMs from virtualization clusters -- Bare-metal servers - -You will provision three nodes: - -- One Linux node, which manages the Kubernetes control plane and stores your `etcd` -- A second Linux node, which will be another worker node -- The Windows node, which will run your Windows containers as a worker node - -| Node | Operating System | -| ------ | ------------------------------------------------------------ | -| Node 1 | Linux (Ubuntu Server 18.04 recommended) | -| Node 2 | Linux (Ubuntu Server 18.04 recommended) | -| Node 3 | Windows (Windows Server core version 1809 or above required) | - -If your nodes are hosted by a **Cloud Provider** and you want automation support such as loadbalancers or persistent storage devices, your nodes have additional configuration requirements. For details, see [Selecting Cloud Providers.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers) - -# 2. Create the Cluster on Existing Nodes - -The instructions for creating a Windows cluster on existing nodes are very similar to the general [instructions for creating a custom cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/) with some Windows-specific requirements. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, click **Create**. -1. Click **Custom**. -1. Enter a name for your cluster in the **Cluster Name** field. -1. In the **Kubernetes Version** dropdown menu, select v1.19 or above. -1. In the **Network Provider** field, select **Flannel**. -1. In the **Windows Support** section, click **Enabled**. -1. Optional: After you enable Windows support, you will be able to choose the Flannel backend. There are two network options: [**Host Gateway (L2bridge)**](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw) and [**VXLAN (Overlay)**](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan). The default option is **VXLAN (Overlay)** mode. -1. Click **Next**. - -> **Important:** For Host Gateway (L2bridge) networking, it's best to use the same Layer 2 network for all nodes. Otherwise, you need to configure the route rules for them. For details, refer to the [documentation on configuring cloud-hosted VM routes.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/#cloud-hosted-vm-routes-configuration) You will also need to [disable private IP address checks]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/host-gateway-requirements/#disabling-private-ip-address-checks) if you are using Amazon EC2, Google GCE, or Azure VM. - -# 3. Add Nodes to the Cluster - -This section describes how to register your Linux and Worker nodes to your cluster. You will run a command on each node, which will install the Rancher agent and allow Rancher to manage each node. - -### Add Linux Master Node - -In this section, we fill out a form on the Rancher UI to get a custom command to install the Rancher agent on the Linux master node. Then we will copy the command and run it on our Linux master node to register the node in the cluster. - -The first node in your cluster should be a Linux host has both the **Control Plane** and **etcd** roles. At a minimum, both of these roles must be enabled for this node, and this node must be added to your cluster before you can add Windows hosts. - -1. In the **Node Operating System** section, click **Linux**. -1. In the **Node Role** section, choose at least **etcd** and **Control Plane**. We recommend selecting all three. -1. Optional: If you click **Show advanced options,** you can customize the settings for the [Rancher agent]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/) and [node labels.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) -1. Copy the command displayed on the screen to your clipboard. -1. SSH into your Linux host and run the command that you copied to your clipboard. -1. When you are finished provisioning your Linux node(s), select **Done**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - - -It may take a few minutes for the node to be registered in your cluster. - -### Add Linux Worker Node - -In this section, we run a command to register the Linux worker node to the cluster. - -After the initial provisioning of your cluster, your cluster only has a single Linux host. Next, we add another Linux `worker` host, which will be used to support _Rancher cluster agent_, _Metrics server_, _DNS_ and _Ingress_ for your cluster. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **⋮ > Edit Config**. -1. Scroll down to **Node Operating System**. Choose **Linux**. -1. In the **Customize Node Run Command** section, go to the **Node Options** and select the **Worker** role. -1. Copy the command displayed on screen to your clipboard. -1. Log in to your Linux host using a remote Terminal connection. Run the command copied to your clipboard. -1. From **Rancher**, click **Save**. - -**Result:** The **Worker** role is installed on your Linux host, and the node registers with Rancher. It may take a few minutes for the node to be registered in your cluster. - -> **Note:** Taints on Linux Worker Nodes -> -> For each Linux worker node added into the cluster, the following taints will be added to Linux worker node. By adding this taint to the Linux worker node, any workloads added to the Windows cluster will be automatically scheduled to the Windows worker node. If you want to schedule workloads specifically onto the Linux worker node, you will need to add tolerations to those workloads. - -> | Taint Key | Taint Value | Taint Effect | -> | -------------- | ----------- | ------------ | -> | `cattle.io/os` | `linux` | `NoSchedule` | - -### Add a Windows Worker Node - -In this section, we run a command to register the Windows worker node to the cluster. - -You can add Windows hosts to the cluster by editing the cluster and choosing the **Windows** option. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **⋮ > Edit Config**. -1. Scroll down to **Node Operating System**. Choose **Windows**. Note: You will see that the **worker** role is the only available role. -1. Copy the command displayed on screen to your clipboard. -1. Log in to your Windows host using your preferred tool, such as [Microsoft Remote Desktop](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients). Run the command copied to your clipboard in the **Command Prompt (CMD)**. -1. From Rancher, click **Save**. -1. Optional: Repeat these instructions if you want to add more Windows nodes to your cluster. - -**Result:** The **Worker** role is installed on your Windows host, and the node registers with Rancher. It may take a few minutes for the node to be registered in your cluster. You now have a Windows Kubernetes cluster. - -### Optional Next Steps - -After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster: - -- **Access your cluster with the kubectl CLI:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI. -- **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through the Rancher server. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster. - -# Configuration for Storage Classes in Azure - -If you are using Azure VMs for your nodes, you can use [Azure files](https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv) as a StorageClass for the cluster. For details, refer to [this section.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/azure-storageclass) diff --git a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-parity/windows-parity.md b/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-parity/windows-parity.md deleted file mode 100644 index 658b48e8b18..00000000000 --- a/versioned_docs/version-2.6/cluster-provisioning/rke-clusters/windows-clusters/windows-parity/windows-parity.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Windows and Linux Cluster Feature Parity -weight: 3 ---- - -Windows clusters do not share the same feature support as Linux clusters. - -The following chart describes the feature parity between Windows and Linux on Rancher: - -**Component** | **Linux** | **Windows** ---- | --- | --- -**Distributions** | | -RKE | Supported | Supported -RKE2 | Supported | Supported -K3S | Supported | Not Supported -EKS | Supported | Not Supported -GKE | Supported | Not Supported -AKS | Supported | Not Supported -**Rancher Components** | | -Server | Supported | Not Supported -Agent | Supported | Supported -Fleet | Supported | Supported -EKS Operator | Supported | Not Supported -AKS Operator | Not Supported | Not Supported -GKE Operator | Not Supported | Not Supported -Alerting v1 | Supported | Supported -Monitoring v1 | Supported | Supported -Logging v1 | Supported | Supported -Monitoring/Alerting v2 | Supported | Supported -Logging v2 | Supported | Supported -Istio | Supported | Not Supported -Catalog v1 | Supported | Not Supported -Catalog v2 | Supported | Not Supported -OPA | Supported | Not Supported -Longhorn | Supported | Not Supported -CIS Scans | Supported | Not Supported -Backup/Restore Operator | Supported | Not Supported -**CNI / Add-ons** | | -Flannel | Supported | Supported -Canal | Supported | Not Supported -Calico | Supported | Supported (RKE2 Only) -Cilium | Supported | Not Supported -Multus | Supported | Not Supported -Traefik | Supported | Not Supported -NGINX Ingress | Supported | Not Supported - -For updated information on feature support, you may visit [rancher/windows](https://github.com/rancher/windows) on GitHub. diff --git a/versioned_docs/version-2.6/contributing/contributing.md b/versioned_docs/version-2.6/contributing/contributing.md deleted file mode 100644 index cb8d8332c8e..00000000000 --- a/versioned_docs/version-2.6/contributing/contributing.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Contributing to Rancher -weight: 27 ---- - -This section explains the repositories used for Rancher, how to build the repositories, and what information to include when you file an issue. - -For more detailed information on how to contribute to the development of Rancher projects, refer to the [Rancher Developer Wiki](https://github.com/rancher/rancher/wiki). The wiki has resources on many topics, including the following: - -- How to set up the Rancher development environment and run tests -- The typical flow of an issue through the development lifecycle -- Coding guidelines and development best practices -- Debugging and troubleshooting -- Developing the Rancher API - -On the Rancher Users Slack, the channel for developers is **#developer**. - -# Repositories - -All of repositories are located within our main GitHub organization. There are many repositories used for Rancher, but we'll provide descriptions of some of the main ones used in Rancher. - -Repository | URL | Description ------------|-----|------------- -Rancher | https://github.com/rancher/rancher | This repository is the main source code for Rancher 2.x. -Types | https://github.com/rancher/types | This repository is the repository that has all the API types for Rancher 2.x. -API Framework | https://github.com/rancher/norman | This repository is an API framework for building Rancher style APIs backed by Kubernetes Custom Resources. -User Interface | https://github.com/rancher/dashboard/ | This repository is the source of the Dashboard UI. -(Rancher) Docker Machine | https://github.com/rancher/machine | This repository is the source of the Docker Machine binary used when using Node Drivers. This is a fork of the `docker/machine` repository. -machine-package | https://github.com/rancher/machine-package | This repository is used to build the Rancher Docker Machine binary. -kontainer-engine | https://github.com/rancher/kontainer-engine | This repository is the source of kontainer-engine, the tool to provision hosted Kubernetes clusters. -RKE repository | https://github.com/rancher/rke | This repository is the source of Rancher Kubernetes Engine, the tool to provision Kubernetes clusters on any machine. -CLI | https://github.com/rancher/cli | This repository is the source code for the Rancher CLI used in Rancher 2.x. -(Rancher) Helm repository | https://github.com/rancher/helm | This repository is the source of the packaged Helm binary. This is a fork of the `helm/helm` repository. -Telemetry repository | https://github.com/rancher/telemetry | This repository is the source for the Telemetry binary. -loglevel repository | https://github.com/rancher/loglevel | This repository is the source of the loglevel binary, used to dynamically change log levels. - -To see all libraries/projects used in Rancher, see the [`go.mod` file](https://github.com/rancher/rancher/blob/master/go.mod) in the `rancher/rancher` repository. - -![Rancher diagram]({{}}/img/rancher/ranchercomponentsdiagram-2.6.svg)
-Rancher components used for provisioning/managing Kubernetes clusters. - -# Building - -Every repository should have a Makefile and can be built using the `make` command. The `make` targets are based on the scripts in the `/scripts` directory in the repository, and each target will use [Dapper](https://github.com/rancher/dapper) to run the target in an isolated environment. The `Dockerfile.dapper` will be used for this process, and includes all the necessary build tooling needed. - -The default target is `ci`, and will run `./scripts/validate`, `./scripts/build`, `./scripts/test` and `./scripts/package`. The resulting binaries of the build will be in `./build/bin` and are usually also packaged in a Docker image. - -# Bugs, Issues or Questions - -If you find any bugs or are having any trouble, please search the [reported issue](https://github.com/rancher/rancher/issues) as someone may have experienced the same issue or we are actively working on a solution. - -If you can't find anything related to your issue, contact us by [filing an issue](https://github.com/rancher/rancher/issues/new). Though we have many repositories related to Rancher, we want the bugs filed in the Rancher repository so we won't miss them! If you want to ask a question or ask fellow users about an use case, we suggest creating a post on the [Rancher Forums](https://forums.rancher.com). - -### Checklist for Filing Issues - -Please follow this checklist when filing an issue which will helps us investigate and fix the issue. More info means more data we can use to determine what is causing the issue or what might be related to the issue. - ->**Note:** For large amounts of data, please use [GitHub Gist](https://gist.github.com/) or similar and link the created resource in the issue. ->**Important:** Please remove any sensitive data as it will be publicly viewable. - -- **Resources:** Provide as much as detail as possible on the used resources. As the source of the issue can be many things, including as much of detail as possible helps to determine the root cause. See some examples below: - - **Hosts:** What specifications does the host have, like CPU/memory/disk, what cloud does it happen on, what Amazon Machine Image are you using, what DigitalOcean droplet are you using, what image are you provisioning that we can rebuild or use when we try to reproduce - - **Operating System:** What operating system are you using? Providing specifics helps here like the output of `cat /etc/os-release` for exact OS release and `uname -r` for exact kernel used - - **Docker:** What Docker version are you using, how did you install it? Most of the details of Docker can be found by supplying output of `docker version` and `docker info` - - **Environment:** Are you in a proxy environment, are you using recognized CA/self signed certificates, are you using an external loadbalancer - - **Rancher:** What version of Rancher are you using, this can be found on the bottom left of the UI or be retrieved from the image tag you are running on the host - - **Clusters:** What kind of cluster did you create, how did you create it, what did you specify when you were creating it -- **Steps to reproduce the issue:** Provide as much detail on how you got into the reported situation. This helps the person to reproduce the situation you are in. - - Provide manual steps or automation scripts used to get from a newly created setup to the situation you reported. -- **Logs:** Provide data/logs from the used resources. - - Rancher - - Docker install - - ``` - docker logs \ - --timestamps \ - $(docker ps | grep -E "rancher/rancher:|rancher/rancher " | awk '{ print $1 }') - ``` - - Kubernetes install using `kubectl` - - > **Note:** Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` if Rancher is installed on a Kubernetes cluster) or are using the embedded kubectl via the UI. - - ``` - kubectl -n cattle-system \ - logs \ - -l app=rancher \ - --timestamps=true - ``` - - Docker install using `docker` on each of the nodes in the RKE cluster - - ``` - docker logs \ - --timestamps \ - $(docker ps | grep -E "rancher/rancher@|rancher_rancher" | awk '{ print $1 }') - ``` - - Kubernetes Install with RKE Add-On - - > **Note:** Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` if the Rancher server is installed on a Kubernetes cluster) or are using the embedded kubectl via the UI. - - ``` - kubectl -n cattle-system \ - logs \ - --timestamps=true \ - -f $(kubectl --kubeconfig $KUBECONFIG get pods -n cattle-system -o json | jq -r '.items[] | select(.spec.containers[].name="cattle-server") | .metadata.name') - ``` - - System logging (these might not all exist, depending on operating system) - - `/var/log/messages` - - `/var/log/syslog` - - `/var/log/kern.log` - - Docker daemon logging (these might not all exist, depending on operating system) - - `/var/log/docker.log` -- **Metrics:** If you are experiencing performance issues, please provide as much of data (files or screenshots) of metrics which can help determining what is going on. If you have an issue related to a machine, it helps to supply output of `top`, `free -m`, `df` which shows processes/memory/disk usage. - -# Docs - -If you have any updates to our documentation, please make any pull request to our docs repo. - -- [Rancher 2.x Docs repository](https://github.com/rancher/docs): This repo is where all the docs for Rancher 2.x are located. They are located in the `content` folder in the repo. - -- [Rancher 1.x Docs repository](https://github.com/rancher/rancher.github.io): This repo is where all the docs for Rancher 1.x are located. They are located in the `rancher` folder in the repo. diff --git a/versioned_docs/version-2.6/deploy-across-clusters/deploy-across-clusters.md b/versioned_docs/version-2.6/deploy-across-clusters/deploy-across-clusters.md deleted file mode 100644 index bb41e0e6e00..00000000000 --- a/versioned_docs/version-2.6/deploy-across-clusters/deploy-across-clusters.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Deploying Applications across Clusters -weight: 12 ---- -### Fleet - -Rancher v2.5 introduced Fleet, a new way to deploy applications across clusters. - -Fleet is GitOps at scale. For more information, refer to the [Fleet section.](./fleet) - -### Multi-cluster Apps - -In Rancher before v2.5, the multi-cluster apps feature was used to deploy applications across clusters. The multi-cluster apps feature is deprecated, but still available in Rancher v2.5. - -Refer to the documentation [here.](./multi-cluster-apps) \ No newline at end of file diff --git a/versioned_docs/version-2.6/deploy-across-clusters/fleet/architecture/architecture.md b/versioned_docs/version-2.6/deploy-across-clusters/fleet/architecture/architecture.md deleted file mode 100644 index 620747b01ca..00000000000 --- a/versioned_docs/version-2.6/deploy-across-clusters/fleet/architecture/architecture.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Architecture -weight: 1 ---- - -Fleet can manage deployments from git of raw Kubernetes YAML, Helm charts, or Kustomize or any combination of the three. Regardless of the source, all resources are dynamically turned into Helm charts, and Helm is used as the engine to deploy everything in the cluster. This gives you a high degree of control, consistency, and auditability. Fleet focuses not only on the ability to scale, but to give one a high degree of control and visibility to exactly what is installed on the cluster. - -![Architecture]({{}}/img/rancher/fleet-architecture.svg) - diff --git a/versioned_docs/version-2.6/deploy-across-clusters/fleet/fleet.md b/versioned_docs/version-2.6/deploy-across-clusters/fleet/fleet.md deleted file mode 100644 index c1502c71664..00000000000 --- a/versioned_docs/version-2.6/deploy-across-clusters/fleet/fleet.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Fleet - GitOps at Scale -weight: 1 ---- - -Fleet is GitOps at scale. Fleet is designed to manage up to a million clusters. It's also lightweight enough that it works great for a [single cluster](https://fleet.rancher.io/single-cluster-install/) too, but it really shines when you get to a [large scale.](https://fleet.rancher.io/multi-cluster-install/) By large scale we mean either a lot of clusters, a lot of deployments, or a lot of teams in a single organization. - -Fleet is a separate project from Rancher, and can be installed on any Kubernetes cluster with Helm. - -- [Architecture](#architecture) -- [Accessing Fleet in the Rancher UI](#accessing-fleet-in-the-rancher-ui) -- [Windows Support](#windows-support) -- [GitHub Repository](#github-repository) -- [Using Fleet Behind a Proxy](#using-fleet-behind-a-proxy) -- [Helm Chart Dependencies](#helm-chart-dependencies) -- [Troubleshooting](#troubleshooting) -- [Documentation](#documentation) - -# Architecture - -For information about how Fleet works, see [this page.](./architecture) - -# Accessing Fleet in the Rancher UI - -Fleet comes preinstalled in Rancher and is managed by the **Continous Delivery** option in the Rancher UI. For additional information on Continuous Delivery and other Fleet troubleshooting tips, refer [here](https://fleet.rancher.io/troubleshooting/). - -Users can leverage continuous delivery to deploy their applications to the Kubernetes clusters in the git repository without any manual operation by following **gitops** practice. - -Follow the steps below to access Continuous Delivery in the Rancher UI: - -1. Click **☰ > Continuous Delivery**. - -1. Select your namespace at the top of the menu, noting the following: - - By default,`fleet-default` is selected which includes all downstream clusters that are registered through Rancher. - - You may switch to `fleet-local`, which only contains the `local` cluster, or you may create your own workspace to which you may assign and move clusters. - - You can then manage clusters by clicking on **Clusters** on the left navigation bar. - -1. Click on **Gitrepos** on the left navigation bar to deploy the gitrepo into your clusters in the current workspace. - -1. Select your [git repository](https://fleet.rancher.io/gitrepo-add/) and [target clusters/cluster group](https://fleet.rancher.io/gitrepo-structure/). You can also create the cluster group in the UI by clicking on **Cluster Groups** from the left navigation bar. - -1. Once the gitrepo is deployed, you can monitor the application through the Rancher UI. - -# Windows Support - -For details on support for clusters with Windows nodes, see [this page.](./windows) - - -# GitHub Repository - -The Fleet Helm charts are available [here.](https://github.com/rancher/fleet/releases/latest) - - -# Using Fleet Behind a Proxy - -For details on using Fleet behind a proxy, see [this page.](./proxy) - -# Helm Chart Dependencies - -In order for Helm charts with dependencies to deploy successfully, you must run a manual command (as listed below), as it is up to the user to fulfill the dependency list. If you do not do this and proceed to clone your repository and run `helm install`, your installation will fail because the dependencies will be missing. - -The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` OR run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters. - -# Troubleshooting - ---- -* **Known Issue:** clientSecretName and helmSecretName secrets for Fleet gitrepos are not included in the backup nor restore created by the [backup-restore-operator]({{}}/rancher/v2.6/en/backups/back-up-rancher/#1-install-the-rancher-backups-operator). We will update the community once a permanent solution is in place. - -* **Temporary Workaround:**
-By default, user-defined secrets are not backed up in Fleet. It is necessary to recreate secrets if performing a disaster recovery restore or migration of Rancher into a fresh cluster. To modify resourceSet to include extra resources you want to backup, refer to docs [here](https://github.com/rancher/backup-restore-operator#user-flow). - ---- - -# Documentation - -The Fleet documentation is at [https://fleet.rancher.io/.](https://fleet.rancher.io/) diff --git a/versioned_docs/version-2.6/deploy-across-clusters/fleet/proxy/proxy.md b/versioned_docs/version-2.6/deploy-across-clusters/fleet/proxy/proxy.md deleted file mode 100644 index 4e41e1115f9..00000000000 --- a/versioned_docs/version-2.6/deploy-across-clusters/fleet/proxy/proxy.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Using Fleet Behind a Proxy -weight: 3 ---- - -In this section, you'll learn how to enable Fleet in a setup that has a Rancher server with a public IP a Kubernetes cluster that has no public IP, but is configured to use a proxy. - -Rancher does not establish connections with registered downstream clusters. The Rancher agent deployed on the downstream cluster must be able to establish the connection with Rancher. - -To set up Fleet to work behind a proxy, you will need to set the **Agent Environment Variables** for the downstream cluster. These are cluster-level configuration options. - -Through the Rancher UI, you can configure these environment variables for any cluster type, including registered and custom clusters. The variables can be added while editing an existing cluster or while provisioning a new cluster. - -For public downstream clusters, it is sufficient to [set the required environment variables in the Rancher UI.](#setting-environment-variables-in-the-rancher-ui) - -For private nodes or private clusters, the environment variables need to be set on the nodes themselves. Then the environment variables are configured from the Rancher UI, typically when provisioning a custom cluster or when registering the private cluster. For an example of how to set the environment variables on Ubuntu node in a K3s Kubernetes cluster, see [this section.](#setting-environment-variables-on-private-nodes) - -# Required Environment Variables - -When adding Fleet agent environment variables for the proxy, replace with your private proxy IP. - -| Variable Name | Value | -|------------------|--------| -| `HTTP_PROXY` | http://:8888 | -| `HTTPS_PROXY` | http://:8888 -| `NO_PROXY` | 127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local | - -# Setting Environment Variables in the Rancher UI - -To add the environment variable to an existing cluster, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where you want to add environment variables and click **⋮ > Edit Config**. -1. Click **Advanced Options**. -1. Click **Add Environment Variable**. -1. Enter the [required environment variables](#required-environment-variables) -1. Click **Save**. - -**Result:** The Fleet agent works behind a proxy. - -# Setting Environment Variables on Private Nodes - -For private nodes and private clusters, the proxy environment variables need to be set on the nodes themselves, as well as configured from the Rancher UI. - -This example shows how the environment variables would be set up on an Ubuntu node in a K3s Kubernetes cluster: - -``` -ssh -o ForwardAgent=yes ubuntu@ -ssh -export proxy_private_ip= -export HTTP_PROXY=http://${proxy_private_ip}:8888 -export HTTPS_PROXY=http://${proxy_private_ip}:8888 -export NO_PROXY=127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local -export KUBECONFIG=/etc/rancher/k3s/k3s.yaml -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/deploy-across-clusters/fleet/windows/windows.md b/versioned_docs/version-2.6/deploy-across-clusters/fleet/windows/windows.md deleted file mode 100644 index a2cb842fc0b..00000000000 --- a/versioned_docs/version-2.6/deploy-across-clusters/fleet/windows/windows.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Windows Support -weight: 2 ---- - - -Prior to Rancher v2.5.6, the `agent` did not have native Windows manifests on downstream clusters with Windows nodes. This would result in a failing `agent` pod for the cluster. - -If you are upgrading from an older version of Rancher to v2.5.6+, you can deploy a working `agent` with the following workflow *in the downstream cluster*: - -1. Cordon all Windows nodes. -1. Apply the below toleration to the `agent` workload. -1. Uncordon all Windows nodes. -1. Delete all `agent` pods. New pods should be created with the new toleration. -1. Once the `agent` pods are running, and auto-update is enabled for Fleet, they should be updated to a Windows-compatible `agent` version. - -```yaml -tolerations: -- effect: NoSchedule - key: cattle.io/os - operator: Equal - value: linux -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/deploy-across-clusters/multi-cluster-apps/multi-cluster-apps.md b/versioned_docs/version-2.6/deploy-across-clusters/multi-cluster-apps/multi-cluster-apps.md deleted file mode 100644 index 65e1978953d..00000000000 --- a/versioned_docs/version-2.6/deploy-across-clusters/multi-cluster-apps/multi-cluster-apps.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -title: Multi-cluster Apps -weight: 2 ---- - -> As of Rancher v2.5, multi-cluster apps are deprecated. We now recommend using [Fleet]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet) for deploying apps across clusters. - -Typically, most applications are deployed on a single Kubernetes cluster, but there will be times you might want to deploy multiple copies of the same application across different clusters and/or projects. In Rancher, a _multi-cluster application_, is an application deployed using a Helm chart across multiple clusters. With the ability to deploy the same application across multiple clusters, it avoids the repetition of the same action on each cluster, which could introduce user error during application configuration. With multi-cluster applications, you can customize to have the same configuration across all projects/clusters as well as have the ability to change the configuration based on your target project. Since multi-cluster application is considered a single application, it's easy to manage and maintain this application. - -Any Helm charts from a global catalog can be used to deploy and manage multi-cluster applications. - -After creating a multi-cluster application, you can program a global DNS entry to make it easier to access the application. - -- [Prerequisites](#prerequisites) -- [Launching a multi-cluster app](#launching-a-multi-cluster-app) -- [Multi-cluster app configuration options](#multi-cluster-app-configuration-options) - - [Targets](#targets) - - [Upgrades](#upgrades) - - [Roles](#roles) -- [Application configuration options](#application-configuration-options) - - [Using a questions.yml file](#using-a-questions-yml-file) - - [Key value pairs for native Helm charts](#key-value-pairs-for-native-helm-charts) - - [Members](#members) - - [Overriding application configuration options for specific projects](#overriding-application-configuration-options-for-specific-projects) -- [Upgrading multi-cluster app roles and projects](#upgrading-multi-cluster-app-roles-and-projects) -- [Multi-cluster application management](#multi-cluster-application-management) -- [Deleting a multi-cluster application](#deleting-a-multi-cluster-application) - -# Prerequisites - -### Permissions - -To create a multi-cluster app in Rancher, you must have at least one of the following permissions: - -- A [project-member role]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles) in the target cluster(s), which gives you the ability to create, read, update, and delete the workloads -- A [cluster owner role]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles) for the clusters(s) that include the target project(s) - -### Enable Legacy Features - -Because multi-cluster apps were deprecated and replaced with Fleet in Rancher v2.5, you will need to enable multi-cluster apps with a feature flag. - -1. In the upper left corner, click **☰ > Global Settings**. -1. Click **Feature Flags**. -1. Go to the `legacy` feature flag and click **Activate**. - -# Launching a Multi-Cluster App - -1. In the upper left corner, click **☰ > Multi-cluster Apps**. -1. Click **Launch**. -1. Find the application that you want to launch. -1. (Optional) Review the detailed descriptions, which are derived from the Helm chart's `README`. -1. Under **Configuration Options** enter a **Name** for the multi-cluster application. By default, this name is also used to create a Kubernetes namespace in each [target project](#targets) for the multi-cluster application. The namespace is named as `-`. -1. Select a **Template Version**. -1. Complete the [multi-cluster applications specific configuration options](#multi-cluster-app-configuration-options) as well as the [application configuration options](#application-configuration-options). -1. Select the **Members** who can [interact with the multi-cluster application](#members). -1. Add any [custom application configuration answers](#overriding-application-configuration-options-for-specific-projects) that would change the configuration for specific project(s) from the default application configuration answers. -1. Review the files in the **Preview** section. When you're satisfied, click **Launch**. - -**Result**: Your application is deployed to your chosen namespace. You can view the application status from the project's: - -# Multi-cluster App Configuration Options - -Rancher has divided the configuration option for the multi-cluster application into several sections. - -### Targets - -In the **Targets** section, select the projects that you want the application to be deployed in. The list of projects is based on what projects you have access to. For each project that you select, it will be added to the list, which shows the cluster name and project name that were selected. To remove a target project, click on **-**. - -### Upgrades - -In the **Upgrades** section, select the upgrade strategy to use, when you decide to upgrade your application. - -* **Rolling Update (batched):** When selecting this upgrade strategy, the number of applications upgraded at a time is based on the selected **Batch size** and the **Interval** specifies how many seconds to wait before starting the next batch of updates. - -* **Upgrade all apps simultaneously:** When selecting this upgrade strategy, all applications across all projects will be upgraded at the same time. - -### Roles - -In the **Roles** section, you define the role of the multi-cluster application. Typically, when a user [launches catalog applications]({{}}/rancher/v2.6/en/helm-charts), that specific user's permissions are used for creation of all workloads/resources that is required by the app. - -For multi-cluster applications, the application is deployed by a _system user_ and is assigned as the creator of all underlying resources. A _system user_ is used instead of the actual user due to the fact that the actual user could be removed from one of the target projects. If the actual user was removed from one of the projects, then that user would no longer be able to manage the application for the other projects. - -Rancher will let you select from two options for Roles, **Project** and **Cluster**. Rancher will allow creation using any of these roles based on the user's permissions. - -- **Project** - This is the equivalent of a [project member]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles). If you select this role, Rancher will check that in all the target projects, the user has minimally the [project member]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles) role. While the user might not be explicitly granted the _project member_ role, if the user is an [administrator]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/), a [cluster owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles), or a [project owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles), then the user is considered to have the appropriate level of permissions. - -- **Cluster** - This is the equivalent of a [cluster owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles). If you select this role, Rancher will check that in all the target projects, the user has minimally the [cluster owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles) role. While the user might not be explicitly granted the _cluster owner_ role, if the user is an [administrator]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/), then the user is considered to have the appropriate level of permissions. - -When launching the application, Rancher will confirm if you have these permissions in the target projects before launching the application. - -> **Note:** There are some applications like _Grafana_ or _Datadog_ that require access to specific cluster-scoped resources. These applications will require the _Cluster_ role. If you find out later that the application requires cluster roles, the multi-cluster application can be upgraded to update the roles. - -# Application Configuration Options - -For each Helm chart, there are a list of desired answers that must be entered in order to successfully deploy the chart. When entering answers, you must format them using the syntax rules found in [Using Helm: The format and limitations of –set](https://helm.sh/docs/intro/using_helm/#the-format-and-limitations-of---set), as Rancher passes them as `--set` flags to Helm. - -> For example, when entering an answer that includes two values separated by a comma (i.e. `abc, bcd`), it is required to wrap the values with double quotes (i.e., ``"abc, bcd"``). - -### Using a questions.yml file - -If the Helm chart that you are deploying contains a `questions.yml` file, Rancher's UI will translate this file to display an easy to use UI to collect the answers for the questions. - -### Key Value Pairs for Native Helm Charts - -For native Helm charts (i.e., charts from the **Helm Stable** or **Helm Incubator** catalogs or a custom Helm chart repository, answers are provided as key value pairs in the **Answers** section. These answers are used to override the default values. - -### Members - -By default, multi-cluster applications can only be managed by the user who created it. In the **Members** section, other users can be added so that they can also help manage or view the multi-cluster application. - -1. Find the user that you want to add by typing in the member's name in the **Member** search box. - -2. Select the **Access Type** for that member. There are three access types for a multi-cluster project, but due to how the permissions of a multi-cluster application are launched, please read carefully to understand what these access types mean. - - - **Owner**: This access type can manage any configuration part of the multi-cluster application including the template version, the [multi-cluster applications specific configuration options](#Multi-cluster App Configuration Options), the [application specific configuration options](#application-configuration-options), the members who can interact with the multi-cluster application and the [custom application configuration answers](#overriding-application-configuration-options-for-specific-projects). Since a multi-cluster application is created with a different set of permissions from the user, any _owner_ of the multi-cluster application can manage/remove applications in [target projects](#targets) without explicitly having access to these project(s). Only trusted users should be provided with this access type. - - - **Member**: This access type can only modify the template version, the [application specific configuration options](#application-configuration-options) and the [custom application configuration answers](#overriding-application-configuration-options-for-specific-projects). Since a multi-cluster application is created with a different set of permissions from the user, any _member_ of the multi-cluster application can modify the application without explicitly having access to these project(s). Only trusted users should be provided with this access type. - - - **Read-only**: This access type cannot modify any configuration option for the multi-cluster application. Users can only view these applications. - - > **Note:** Please ensure only trusted users are given _Owner_ or _Member_ access as they will automatically be able to manage applications created for this multi-cluster application in target projects they might not have direct access to. - -### Overriding Application Configuration Options for Specific Projects - -The ability to use the same configuration to deploy the same application across multiple clusters/projects is one of the main benefits of multi-cluster applications. There might be a specific project that requires a slightly different configuration option, but you want to manage that application with all the other matching applications. Instead of creating a brand new application, you can override specific [application specific configuration options](#application-configuration-options) for specific projects. - -1. In the **Answer Overrides** section, click **Add Override**. - -2. For each override, you can select the following: - - - **Scope**: Select which target projects you want to override the answer in the configuration option. - - - **Question**: Select which question you want to override. - - - **Answer**: Enter the answer that you want to be used instead. - -# Upgrading Multi-Cluster App Roles and Projects - -- **Changing Roles on an existing Multi-Cluster app** -The creator and any users added with the access-type "owner" to a multi-cluster app, can upgrade its Roles. When adding a new Role, we check if the user has that exact role in all current target projects. These checks allow the same relaxations for global admins, cluster owners and project-owners as described in the installation section for the field `Roles`. - -- **Adding/Removing target projects** -1. The creator and any users added with access-type "owner" to a multi-cluster app, can add or remove its target projects. When adding a new project, we check if the caller of this request has all Roles defined on multi-cluster app, in the new projects they want to add. The roles checks are again relaxed for global admins, cluster-owners and project-owners. -2. We do not do these membership checks when removing target projects. This is because the caller's permissions could have with respect to the target project, or the project could have been deleted and hence the caller wants to remove it from targets list. - - -# Multi-Cluster Application Management - -One of the benefits of using a multi-cluster application as opposed to multiple individual applications of the same type, is the ease of management. Multi-cluster applications can be cloned, upgraded or rolled back. - -> **Prerequisite:** The `legacy` feature flag needs to be enabled. - -1. In the upper left corner, click **☰ > Multi-cluster Apps**. - -2. Choose the multi-cluster application you want to take one of these actions on and click the **⋮**. Select one of the following options: - - * **Clone**: Creates another multi-cluster application with the same configuration. By using this option, you can easily duplicate a multi-cluster application. - * **Upgrade**: Upgrade your multi-cluster application to change some part of the configuration. When performing an upgrade for multi-cluster application, the [upgrade strategy](#upgrades) can be modified if you have the correct [access type](#members). - * **Rollback**: Rollback your application to a specific version. If after an upgrade, there are issues for your multi-cluster application for one or more of your [targets](#targets), Rancher has stored up to 10 versions of the multi-cluster application. Rolling back a multi-cluster application reverts the application for **all** target clusters and projects, not just the targets(s) affected by the upgrade issue. - -# Deleting a Multi-Cluster Application - -> **Prerequisite:** The `legacy` feature flag needs to be enabled. - -1. In the upper left corner, click **☰ > Multi-cluster Apps**. - -2. Choose the multi-cluster application you want to delete and click the **⋮ > Delete**. When deleting the multi-cluster application, all applications and namespaces are deleted in all of the target projects. - - > **Note:** The applications in the target projects, that are created for a multi-cluster application, cannot be deleted individually. The applications can only be deleted when the multi-cluster application is deleted. diff --git a/versioned_docs/version-2.6/faq/deprecated-features/deprecated-features.md b/versioned_docs/version-2.6/faq/deprecated-features/deprecated-features.md deleted file mode 100644 index b0eb76250a4..00000000000 --- a/versioned_docs/version-2.6/faq/deprecated-features/deprecated-features.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Deprecated Features in Rancher -weight: 100 ---- - -### What is Rancher's Deprecation policy? - -We have published our official deprecation policy in the support [terms of service](https://rancher.com/support-maintenance-terms). - -### Where can I find out which features have been deprecated in Rancher? - -Rancher will publish deprecated features as part of the [release notes](https://github.com/rancher/rancher/releases) for Rancher found on GitHub. Please consult the following patch releases for deprecated features: - -| Patch Version | Release Date | -|---------------|---------------| -| [2.6.0](https://github.com/rancher/rancher/releases/tag/v2.6.0) | Aug 31, 2021 | -| [2.6.1](https://github.com/rancher/rancher/releases/tag/v2.6.1) | Oct 11, 2021 | -| [2.6.2](https://github.com/rancher/rancher/releases/tag/v2.6.2) | Oct 19, 2021 | -| [2.6.3](https://github.com/rancher/rancher/releases/tag/v2.6.3) | Dec 21, 2021 | -| [2.6.4](https://github.com/rancher/rancher/releases/tag/v2.6.4) | Mar 31, 2022 | -| [2.6.5](https://github.com/rancher/rancher/releases/tag/v2.6.5) | May 12, 2022 | - - -### What can I expect when a feature is marked for deprecation? - -In the release where functionality is marked as "Deprecated", it will still be available and supported allowing upgrades to follow the usual procedure. Once upgraded, users/admins should start planning to move away from the deprecated functionality before upgrading to the release it marked as removed. The recommendation for new deployments is to not use the deprecated feature. \ No newline at end of file diff --git a/versioned_docs/version-2.6/faq/dockershim/dockershim.md b/versioned_docs/version-2.6/faq/dockershim/dockershim.md deleted file mode 100644 index d9ce2fe6437..00000000000 --- a/versioned_docs/version-2.6/faq/dockershim/dockershim.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Dockershim -weight: 300 ---- - -The Dockershim is the CRI compliant layer between the Kubelet and the Docker daemon. As part of the Kubernetes 1.20 release, the [deprecation of the in-tree Dockershim was announced](https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/). Removal is currently scheduled for Kubernetes 1.24. For more information on the deprecation and its timelines, see the [Kubernetes Dockershim Deprecation FAQ](https://kubernetes.io/blog/2020/12/02/dockershim-faq/#when-will-dockershim-be-removed). - -RKE clusters, starting with Kubernetes 1.21, now support the external Dockershim to continue leveraging Docker as the CRI runtime. We now implement the upstream open source community Dockershim announced by [Mirantis and Docker](https://www.mirantis.com/blog/mirantis-to-take-over-support-of-kubernetes-dockershim-2/) to ensure RKE clusters can continue to leverage Docker. - -To enable the external Dockershim, configure the following option. - -``` -enable_cri_dockerd: true -``` - -For users looking to use another container runtime, Rancher has the edge-focused K3s and datacenter-focused RKE2 Kubernetes distributions that use containerd as the default runtime. Imported RKE2 and K3s Kubernetes clusters can then be upgraded and managed through Rancher even after the removal of in-tree Dockershim in Kubernetes 1.24. - -### FAQ - -
- -Q. Do I have to upgrade Rancher to get Rancher’s support of the upstream Dockershim? - -The upstream support of Dockershim begins for RKE in Kubernetes 1.21. You will need to be on Rancher 2.6 or above to have support for RKE with Kubernetes 1.21. See our [support matrix](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.6.0/) for details. - -
- -Q. I am currently on RKE with Kubernetes 1.20. Do I need to upgrade to RKE with Kubernetes 1.21 sooner to avoid being out of support for Dockershim? - -A. The version of Dockershim in RKE with Kubernetes 1.20 will continue to work and is not scheduled for removal upstream until Kubernetes 1.24. It will only emit a warning of its future deprecation, which Rancher has mitigated in RKE with Kubernetes 1.21. You can plan your upgrade to Kubernetes 1.21 as you would normally, but should consider enabling the external Dockershim by Kubernetes 1.22. The external Dockershim will need to be enabled before upgrading to Kubernetes 1.24, at which point the existing implementation will be removed. - -For more information on the deprecation and its timeline, see the [Kubernetes Dockershim Deprecation FAQ](https://kubernetes.io/blog/2020/12/02/dockershim-faq/#when-will-dockershim-be-removed). - -
- -Q: What are my other options if I don’t want to depend on the Dockershim? - -A: You can use a runtime like containerd with Kubernetes that does not require Dockershim support. RKE2 or K3s are two options for doing this. - -
- -Q: If I am already using RKE1 and want to switch to RKE2, what are my migration options? - -A: Rancher is exploring the possibility of an in-place upgrade path. Alternatively you can always migrate workloads from one cluster to another using kubectl. - -
diff --git a/versioned_docs/version-2.6/faq/faq.md b/versioned_docs/version-2.6/faq/faq.md deleted file mode 100644 index 92b3894af2a..00000000000 --- a/versioned_docs/version-2.6/faq/faq.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: FAQ -weight: 25 ---- - -This FAQ is a work in progress designed to answers the questions our users most frequently ask about Rancher v2.x. - -See [Technical FAQ]({{}}/rancher/v2.6/en/faq/technical/), for frequently asked technical questions. - -
- -**Does Rancher v2.x support Docker Swarm and Mesos as environment types?** - -When creating an environment in Rancher v2.x, Swarm and Mesos will no longer be standard options you can select. However, both Swarm and Mesos will continue to be available as Catalog applications you can deploy. It was a tough decision to make but, in the end, it came down to adoption. For example, out of more than 15,000 clusters, only about 200 or so are running Swarm. - -
- -**Is it possible to manage Azure Kubernetes Services with Rancher v2.x?** - -Yes. - -
- -**Does Rancher support Windows?** - -As of Rancher 2.3.0, we support Windows Server 1809 containers. For details on how to set up a cluster with Windows worker nodes, refer to the section on [configuring custom clusters for Windows.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/) - -
- -**Does Rancher support Istio?** - -As of Rancher 2.3.0, we support [Istio.]({{}}/rancher/v2.6/en/istio/) - -Furthermore, Istio is implemented in our micro-PaaS "Rio", which works on Rancher 2.x along with any CNCF compliant Kubernetes cluster. You can read more about it [here](https://rio.io/) - -
- -**Will Rancher v2.x support Hashicorp's Vault for storing secrets?** - -Secrets management is on our roadmap but we haven't assigned it to a specific release yet. - -
- -**Does Rancher v2.x support RKT containers as well?** - -At this time, we only support Docker. - -
- -**Does Rancher v2.x support Calico, Contiv, Contrail, Flannel, Weave net, etc., for embedded and registered Kubernetes?** - -Out-of-the-box, Rancher provides the following CNI network providers for Kubernetes clusters: Canal, Flannel, Calico and Weave. Always refer to the [Rancher Support Matrix](https://rancher.com/support-maintenance-terms/) for details about what is officially supported. - -
- -**Are you planning on supporting Traefik for existing setups?** - -We don't currently plan on providing embedded Traefik support, but we're still exploring load-balancing approaches. - -
- -**Can I import OpenShift Kubernetes clusters into v2.x?** - -Our goal is to run any upstream Kubernetes clusters. Therefore, Rancher v2.x should work with OpenShift, but we haven't tested it yet. - -
- -**Are you going to integrate Longhorn?** - -Yes. Longhorn was integrated into Rancher v2.5+. diff --git a/versioned_docs/version-2.6/faq/kubectl/kubectl.md b/versioned_docs/version-2.6/faq/kubectl/kubectl.md deleted file mode 100644 index cd74d7c0591..00000000000 --- a/versioned_docs/version-2.6/faq/kubectl/kubectl.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Installing and Configuring kubectl -weight: 100 ---- - -`kubectl` is a CLI utility for running commands against Kubernetes clusters. It's required for many maintenance and administrative tasks in Rancher 2.x. - -### Installation - -See [kubectl Installation](https://kubernetes.io/docs/tasks/tools/install-kubectl/) for installation on your operating system. - -### Configuration - -When you create a Kubernetes cluster with RKE, RKE creates a `kube_config_cluster.yml` in the local directory that contains credentials to connect to your new cluster with tools like `kubectl` or `helm`. - -You can copy this file as `$HOME/.kube/config` or if you are working with multiple Kubernetes clusters, set the `KUBECONFIG` environmental variable to the path of `kube_config_cluster.yml`. - -``` -export KUBECONFIG=$(pwd)/kube_config_cluster.yml -``` - -Test your connectivity with `kubectl` and see if you can get the list of nodes back. - -``` -kubectl get nodes - NAME STATUS ROLES AGE VERSION -165.227.114.63 Ready controlplane,etcd,worker 11m v1.10.1 -165.227.116.167 Ready controlplane,etcd,worker 11m v1.10.1 -165.227.127.226 Ready controlplane,etcd,worker 11m v1.10.1 -``` diff --git a/versioned_docs/version-2.6/faq/networking/cni-providers/cni-providers.md b/versioned_docs/version-2.6/faq/networking/cni-providers/cni-providers.md deleted file mode 100644 index a7104cc5dfc..00000000000 --- a/versioned_docs/version-2.6/faq/networking/cni-providers/cni-providers.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -title: Container Network Interface (CNI) Providers -description: Learn about Container Network Interface (CNI), the CNI providers Rancher provides, the features they offer, and how to choose a provider for you -weight: 2300 ---- - -## What is CNI? - -CNI (Container Network Interface), a [Cloud Native Computing Foundation project](https://cncf.io/), consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. - -Kubernetes uses CNI as an interface between network providers and Kubernetes pod networking. - -![CNI Logo]({{}}/img/rancher/cni-logo.png) - -For more information visit [CNI GitHub project](https://github.com/containernetworking/cni). - -## What Network Models are Used in CNI? - -CNI network providers implement their network fabric using either an encapsulated network model such as Virtual Extensible Lan ([VXLAN](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#vxlan)) or an unencapsulated network model such as Border Gateway Protocol ([BGP](https://en.wikipedia.org/wiki/Border_Gateway_Protocol)). - -### What is an Encapsulated Network? - -This network model provides a logical Layer 2 (L2) network encapsulated over the existing Layer 3 (L3) network topology that spans the Kubernetes cluster nodes. With this model you have an isolated L2 network for containers without needing routing distribution, all at the cost of minimal overhead in terms of processing and increased IP package size, which comes from an IP header generated by overlay encapsulation. Encapsulation information is distributed by UDP ports between Kubernetes workers, interchanging network control plane information about how MAC addresses can be reached. Common encapsulation used in this kind of network model is VXLAN, Internet Protocol Security (IPSec), and IP-in-IP. - -In simple terms, this network model generates a kind of network bridge extended between Kubernetes workers, where pods are connected. - -This network model is used when an extended L2 bridge is preferred. This network model is sensitive to L3 network latencies of the Kubernetes workers. If datacenters are in distinct geolocations, be sure to have low latencies between them to avoid eventual network segmentation. - -CNI network providers using this network model include Flannel, Canal, Weave, and Cilium. By default, Calico is not using this model, but it can be configured to do so. - -![Encapsulated Network]({{}}/img/rancher/encapsulated-network.png) - -### What is an Unencapsulated Network? - -This network model provides an L3 network to route packets between containers. This model doesn't generate an isolated l2 network, nor generates overhead. These benefits come at the cost of Kubernetes workers having to manage any route distribution that's needed. Instead of using IP headers for encapsulation, this network model uses a network protocol between Kubernetes workers to distribute routing information to reach pods, such as [BGP](https://en.wikipedia.org/wiki/Border_Gateway_Protocol). - -In simple terms, this network model generates a kind of network router extended between Kubernetes workers, which provides information about how to reach pods. - -This network model is used when a routed L3 network is preferred. This mode dynamically updates routes at the OS level for Kubernetes workers. It's less sensitive to latency. - -CNI network providers using this network model include Calico and Cilium. Cilium may be configured with this model although it is not the default mode. - -![Unencapsulated Network]({{}}/img/rancher/unencapsulated-network.png) - -## What CNI Providers are Provided by Rancher? - -### RKE Kubernetes clusters - -Out-of-the-box, Rancher provides the following CNI network providers for RKE Kubernetes clusters: Canal, Flannel, and Weave. - -You can choose your CNI network provider when you create new Kubernetes clusters from Rancher. - -#### Canal - -![Canal Logo]({{}}/img/rancher/canal-logo.png) - -Canal is a CNI network provider that gives you the best of Flannel and Calico. It allows users to easily deploy Calico and Flannel networking together as a unified networking solution, combining Calico’s network policy enforcement with the rich superset of Calico (unencapsulated) and/or Flannel (encapsulated) network connectivity options. - -In Rancher, Canal is the default CNI network provider combined with Flannel and VXLAN encapsulation. - -Kubernetes workers should open UDP port `8472` (VXLAN) and TCP port `9099` (health checks). If using Wireguard, you should open UDP ports `51820` and `51821`. For more details, refer to [the port requirements for user clusters]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/). - -{{< img "/img/rancher/canal-diagram.png" "Canal Diagram">}} - -For more information, see the [Canal GitHub Page.](https://github.com/projectcalico/canal) - -#### Flannel - -![Flannel Logo]({{}}/img/rancher/flannel-logo.png) - -Flannel is a simple and easy way to configure L3 network fabric designed for Kubernetes. Flannel runs a single binary agent named flanneld on each host, which is responsible for allocating a subnet lease to each host out of a larger, preconfigured address space. Flannel uses either the Kubernetes API or etcd directly to store the network configuration, the allocated subnets, and any auxiliary data (such as the host's public IP). Packets are forwarded using one of several backend mechanisms, with the default encapsulation being [VXLAN](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#vxlan). - -Encapsulated traffic is unencrypted by default. Flannel provides two solutions for encryption: - -* [IPSec](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#ipsec), which makes use of [strongSwan](https://www.strongswan.org/) to establish encrypted IPSec tunnels between Kubernetes workers. It is an experimental backend for encryption. -* [WireGuard](https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md#wireguard), which is a more faster-performing alternative to strongSwan. - -Kubernetes workers should open UDP port `8472` (VXLAN). See [the port requirements for user clusters]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) for more details. - -![Flannel Diagram]({{}}/img/rancher/flannel-diagram.png) - -For more information, see the [Flannel GitHub Page](https://github.com/flannel-io/flannel). - -#### Weave - -![Weave Logo]({{}}/img/rancher/weave-logo.png) - -Weave enables networking and network policy in Kubernetes clusters across the cloud. Additionally, it support encrypting traffic between the peers. - -Kubernetes workers should open TCP port `6783` (control port), UDP port `6783` and UDP port `6784` (data ports). See the [port requirements for user clusters]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) for more details. - -For more information, see the following pages: - -- [Weave Net Official Site](https://www.weave.works/) - -### RKE2 Kubernetes clusters - -Out-of-the-box, Rancher provides the following CNI network providers for RKE2 Kubernetes clusters: [Canal](#canal) (see above section), Calico, and Cilium. - -You can choose your CNI network provider when you create new Kubernetes clusters from Rancher. - -#### Calico - -![Calico Logo]({{}}/img/rancher/calico-logo.png) - -Calico enables networking and network policy in Kubernetes clusters across the cloud. By default, Calico uses a pure, unencapsulated IP network fabric and policy engine to provide networking for your Kubernetes workloads. Workloads are able to communicate over both cloud infrastructure and on-prem using BGP. - -Calico also provides a stateless IP-in-IP or VXLAN encapsulation mode that can be used, if necessary. Calico also offers policy isolation, allowing you to secure and govern your Kubernetes workloads using advanced ingress and egress policies. - -Kubernetes workers should open TCP port `179` if using BGP or UDP port `4789` if using VXLAN encapsulation. In addition, TCP port `5473` is needed when using Typha. See [the port requirements for user clusters]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) for more details. - ->**Important:** In Rancher v2.6.3, Calico probes fail on Windows nodes upon RKE2 installation. Note that this issue is resolved in v2.6.4. -> ->- To work around this issue, first navigate to `https:///v3/settings/windows-rke2-install-script`. -> ->- There, change the current setting: `https://raw.githubusercontent.com/rancher/wins/v0.1.3/install.ps1` to this new setting: `https://raw.githubusercontent.com/rancher/rke2/master/windows/rke2-install.ps1`. - -![Calico Diagram]({{}}/img/rancher/calico-diagram.svg) - -For more information, see the following pages: - -- [Project Calico Official Site](https://www.projectcalico.org/) -- [Project Calico GitHub Page](https://github.com/projectcalico/calico) - -#### Cilium - -![Cilium Logo]({{}}/img/rancher/cilium-logo.png) - -Cilium enables networking and network policies (L3, L4, and L7) in Kubernetes. By default, Cilium uses eBPF technologies to route packets inside the node and VXLAN to send packets to other nodes. Unencapsulated techniques can also be configured. - -Cilium recommends kernel versions greater than 5.2 to be able to leverage the full potential of eBPF. Kubernetes workers should open TCP port `8472` for VXLAN and TCP port `4240` for health checks. In addition, ICMP 8/0 must be enabled for health checks. For more information, check [Cilium System Requirements](https://docs.cilium.io/en/latest/operations/system_requirements/#firewall-requirements). - -##### Ingress Routing Across Nodes in Cilium -
-By default, Cilium does not allow pods to contact pods on other nodes. To work around this, enable the ingress controller to route requests across nodes with a `CiliumNetworkPolicy`. - -After selecting the Cilium CNI and enabling Project Network Isolation for your new cluster, configure as follows: - -``` -apiVersion: cilium.io/v2 -kind: CiliumNetworkPolicy -metadata: - name: hn-nodes - namespace: default -spec: - endpointSelector: {} - ingress: - - fromEntities: - - remote-node -``` - -## CNI Features by Provider - -The following table summarizes the different features available for each CNI network provider provided by Rancher. - -| Provider | Network Model | Route Distribution | Network Policies | Mesh | External Datastore | Encryption | Ingress/Egress Policies | -| ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | -| Canal | Encapsulated (VXLAN) | No | Yes | No | K8s API | Yes | Yes | -| Flannel | Encapsulated (VXLAN) | No | No | No | K8s API | Yes | No | -| Calico | Encapsulated (VXLAN,IPIP) OR Unencapsulated | Yes | Yes | Yes | Etcd and K8s API | Yes | Yes | -| Weave | Encapsulated | Yes | Yes | Yes | No | Yes | Yes | -| Cilium | Encapsulated (VXLAN) | Yes | Yes | Yes | Etcd and K8s API | Yes | Yes | - -- Network Model: Encapsulated or unencapsulated. For more information, see [What Network Models are Used in CNI?](#what-network-models-are-used-in-cni) - -- Route Distribution: An exterior gateway protocol designed to exchange routing and reachability information on the Internet. BGP can assist with pod-to-pod networking between clusters. This feature is a must on unencapsulated CNI network providers, and it is typically done by BGP. If you plan to build clusters split across network segments, route distribution is a feature that's nice-to-have. - -- Network Policies: Kubernetes offers functionality to enforce rules about which services can communicate with each other using network policies. This feature is stable as of Kubernetes v1.7 and is ready to use with certain networking plugins. - -- Mesh: This feature allows service-to-service networking communication between distinct Kubernetes clusters. - -- External Datastore: CNI network providers with this feature need an external datastore for its data. - -- Encryption: This feature allows cyphered and secure network control and data planes. - -- Ingress/Egress Policies: This feature allows you to manage routing control for both Kubernetes and non-Kubernetes communications. - - -## CNI Community Popularity - -The following table summarizes different GitHub metrics to give you an idea of each project's popularity and activity. This data was collected in January 2022. - -| Provider | Project | Stars | Forks | Contributors | -| ---- | ---- | ---- | ---- | ---- | -| Canal | https://github.com/projectcalico/canal | 679 | 100 | 21 | -| Flannel | https://github.com/flannel-io/flannel | 7k | 2.5k | 185 | -| Calico | https://github.com/projectcalico/calico | 3.1k | 741 | 224 | -| Weave | https://github.com/weaveworks/weave/ | 6.2k | 635 | 84 | -| Cilium | https://github.com/cilium/cilium | 10.6k | 1.3k | 352 | - -
- -## Which CNI Provider Should I Use? - -It depends on your project needs. There are many different providers, which each have various features and options. There isn't one provider that meets everyone's needs. - -Canal is the default CNI network provider. We recommend it for most use cases. It provides encapsulated networking for containers with Flannel, while adding Calico network policies that can provide project/namespace isolation in terms of networking. - -## How can I configure a CNI network provider? - -Please see [Cluster Options]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/) on how to configure a network provider for your cluster. For more advanced configuration options, please see how to configure your cluster using a [Config File]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) and the options for [Network Plug-ins]({{}}/rke/latest/en/config-options/add-ons/network-plugins/). diff --git a/versioned_docs/version-2.6/faq/networking/networking.md b/versioned_docs/version-2.6/faq/networking/networking.md deleted file mode 100644 index e9ebe37f4df..00000000000 --- a/versioned_docs/version-2.6/faq/networking/networking.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Networking -weight: 8005 ---- - -Networking FAQ's - -- [CNI Providers]({{}}/rancher/v2.6/en/faq/networking/cni-providers/) - diff --git a/versioned_docs/version-2.6/faq/removing-rancher/removing-rancher.md b/versioned_docs/version-2.6/faq/removing-rancher/removing-rancher.md deleted file mode 100644 index 8491f4b7818..00000000000 --- a/versioned_docs/version-2.6/faq/removing-rancher/removing-rancher.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Rancher is No Longer Needed -weight: 8010 ---- - -This page is intended to answer questions about what happens if you don't want Rancher anymore, if you don't want a cluster to be managed by Rancher anymore, or if the Rancher server is deleted. - -- [If the Rancher server is deleted, what happens to the workloads in my downstream clusters?](#if-the-rancher-server-is-deleted-what-happens-to-the-workloads-in-my-downstream-clusters) -- [If the Rancher server is deleted, how do I access my downstream clusters?](#if-the-rancher-server-is-deleted-how-do-i-access-my-downstream-clusters) -- [What if I don't want Rancher anymore?](#what-if-i-don-t-want-rancher-anymore) -- [What if I don't want my registered cluster managed by Rancher?](#what-if-i-don-t-want-my-registered-cluster-managed-by-rancher) -- [What if I don't want my RKE cluster or hosted Kubernetes cluster managed by Rancher?](#what-if-i-don-t-want-my-rke-cluster-or-hosted-kubernetes-cluster-managed-by-rancher) - -### If the Rancher server is deleted, what happens to the workloads in my downstream clusters? - -If Rancher is ever deleted or unrecoverable, all workloads in the downstream Kubernetes clusters managed by Rancher will continue to function as normal. - -### If the Rancher server is deleted, how do I access my downstream clusters? - -The capability to access a downstream cluster without Rancher depends on the type of cluster and the way that the cluster was created. To summarize: - -- **Registered clusters:** The cluster will be unaffected and you can access the cluster using the same methods that you did before the cluster was registered into Rancher. -- **Hosted Kubernetes clusters:** If you created the cluster in a cloud-hosted Kubernetes provider such as EKS, GKE, or AKS, you can continue to manage the cluster using your provider's cloud credentials. -- **RKE clusters:** To access an [RKE cluster,]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) the cluster must have the [authorized cluster endpoint]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) enabled, and you must have already downloaded the cluster's kubeconfig file from the Rancher UI. (The authorized cluster endpoint is enabled by default for RKE clusters.) With this endpoint, you can access your cluster with kubectl directly instead of communicating through the Rancher server's [authentication proxy.]({{}}/rancher/v2.6/en/overview/architecture/#1-the-authentication-proxy) For instructions on how to configure kubectl to use the authorized cluster endpoint, refer to the section about directly accessing clusters with [kubectl and the kubeconfig file.]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) These clusters will use a snapshot of the authentication as it was configured when Rancher was removed. - -### What if I don't want Rancher anymore? - -If you [installed Rancher on a Kubernetes cluster,]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) remove Rancher by using the [System Tools]({{}}/rancher/v2.6/en/system-tools/) with the `remove` subcommand. - -As of Rancher v2.5.8, uninstalling Rancher in high-availability (HA) mode will also remove all `helm-operation-*` pods and the following apps: - -- fleet -- fleet-agent -- rancher-operator -- rancher-webhook - -Custom resources (CRDs) and custom namespaces will still need to be manually removed. - -If you installed Rancher with Docker, you can uninstall Rancher by removing the single Docker container that it runs in. - -Imported clusters will not be affected by Rancher being removed. For other types of clusters, refer to the section on [accessing downstream clusters when Rancher is removed.](#if-the-rancher-server-is-deleted-how-do-i-access-my-downstream-clusters) - -### What if I don't want my registered cluster managed by Rancher? - -If a registered cluster is deleted from the Rancher UI, the cluster is detached from Rancher, leaving it intact and accessible by the same methods that were used to access it before it was registered in Rancher. - -To detach the cluster, - -1. In the upper left corner, click **☰ > Cluster Management**. -2. Go to the registered cluster that should be detached from Rancher and click **⋮ > Delete**. -3. Click **Delete**. - -**Result:** The registered cluster is detached from Rancher and functions normally outside of Rancher. - -### What if I don't want my RKE cluster or hosted Kubernetes cluster managed by Rancher? - -At this time, there is no functionality to detach these clusters from Rancher. In this context, "detach" is defined as the ability to remove Rancher components from the cluster and manage access to the cluster independently of Rancher. - -The capability to manage these clusters without Rancher is being tracked in this [issue.](https://github.com/rancher/rancher/issues/25234) - -For information about how to access clusters if the Rancher server is deleted, refer to [this section.](#if-the-rancher-server-is-deleted-how-do-i-access-my-downstream-clusters) diff --git a/versioned_docs/version-2.6/faq/security/security.md b/versioned_docs/version-2.6/faq/security/security.md deleted file mode 100644 index 6759f6d2946..00000000000 --- a/versioned_docs/version-2.6/faq/security/security.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Security -weight: 8007 - ---- - -**Is there a Hardening Guide?** - -The Hardening Guide is now located in the main [Security]({{}}/rancher/v2.6/en/security/) section. - -
- -**What are the results of Rancher's Kubernetes cluster when it is CIS benchmarked?** - -We have run the CIS Kubernetes benchmark against a hardened Rancher Kubernetes cluster. The results of that assessment can be found in the main [Security]({{}}/rancher/v2.6/en/security/) section. diff --git a/versioned_docs/version-2.6/faq/technical/technical.md b/versioned_docs/version-2.6/faq/technical/technical.md deleted file mode 100644 index ed4d3ec3f02..00000000000 --- a/versioned_docs/version-2.6/faq/technical/technical.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Technical -weight: 8006 ---- - -### How can I reset the administrator password? - -Docker Install: -``` -$ docker exec -ti reset-password -New password for default administrator (user-xxxxx): - -``` - -Kubernetes install (Helm): -``` -$ KUBECONFIG=./kube_config_cluster.yml -$ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher --no-headers | head -1 | awk '{ print $1 }') -c rancher -- reset-password -New password for default administrator (user-xxxxx): - -``` - - - -### I deleted/deactivated the last admin, how can I fix it? -Docker Install: -``` -$ docker exec -ti ensure-default-admin -New default administrator (user-xxxxx) -New password for default administrator (user-xxxxx): - -``` - -Kubernetes install (Helm): -``` -$ KUBECONFIG=./kube_config_cluster.yml -$ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- ensure-default-admin -New password for default administrator (user-xxxxx): - -``` -### How can I enable debug logging? - -See [Troubleshooting: Logging]({{}}/rancher/v2.6/en/troubleshooting/logging/) - -### My ClusterIP does not respond to ping - -ClusterIP is a virtual IP, which will not respond to ping. Best way to test if the ClusterIP is configured correctly, is by using `curl` to access the IP and port to see if it responds. - -### Where can I manage Node Templates? - -Node Templates can be accessed by opening your account menu (top right) and selecting `Node Templates`. - -### Why is my Layer-4 Load Balancer in `Pending` state? - -The Layer-4 Load Balancer is created as `type: LoadBalancer`. In Kubernetes, this needs a cloud provider or controller that can satisfy these requests, otherwise these will be in `Pending` state forever. More information can be found on [Cloud Providers]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) or [Create External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) - -### Where is the state of Rancher stored? - -- Docker Install: in the embedded etcd of the `rancher/rancher` container, located at `/var/lib/rancher`. -- Kubernetes install: in the etcd of the RKE cluster created to run Rancher. - -### How are the supported Docker versions determined? - -We follow the validated Docker versions for upstream Kubernetes releases. The validated versions can be found under [External Dependencies](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.10.md#external-dependencies) in the Kubernetes release CHANGELOG.md. - -### How can I access nodes created by Rancher? - -SSH keys to access the nodes created by Rancher can be downloaded via the **Nodes** view. Choose the node which you want to access and click on the vertical ⋮ button at the end of the row, and choose **Download Keys** as shown in the picture below. - -![Download Keys]({{}}/img/rancher/downloadsshkeys.png) - -Unzip the downloaded zip file, and use the file `id_rsa` to connect to you host. Be sure to use the correct username (`rancher` or `docker` for RancherOS, `ubuntu` for Ubuntu, `ec2-user` for Amazon Linux) - -``` -$ ssh -i id_rsa user@ip_of_node -``` - -### How can I automate task X in Rancher? - -The UI consists of static files, and works based on responses of the API. That means every action/task that you can execute in the UI, can be automated via the API. There are 2 ways to do this: - -* Visit `https://your_rancher_ip/v3` and browse the API options. -* Capture the API calls when using the UI (Most commonly used for this is [Chrome Developer Tools](https://developers.google.com/web/tools/chrome-devtools/#network) but you can use anything you like) - -### The IP address of a node changed, how can I recover? - -A node is required to have a static IP configured (or a reserved IP via DHCP). If the IP of a node has changed, you will have to remove it from the cluster and readd it. After it is removed, Rancher will update the cluster to the correct state. If the cluster is no longer in `Provisioning` state, the node is removed from the cluster. - -When the IP address of the node changed, Rancher lost connection to the node, so it will be unable to clean the node properly. See [Cleaning cluster nodes]({{}}/rancher/v2.6/en/cluster-admin/cleaning-cluster-nodes/) to clean the node. - -When the node is removed from the cluster, and the node is cleaned, you can readd the node to the cluster. - -### How can I add additional arguments/binds/environment variables to Kubernetes components in a Rancher Launched Kubernetes cluster? - -You can add additional arguments/binds/environment variables via the [Config File]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) option in Cluster Options. For more information, see the [Extra Args, Extra Binds, and Extra Environment Variables]({{}}/rke/latest/en/config-options/services/services-extras/) in the RKE documentation or browse the [Example Cluster.ymls]({{}}/rke/latest/en/example-yamls/). - -### How do I check if my certificate chain is valid? - -Use the `openssl verify` command to validate your certificate chain: - ->**Note:** Configure `SSL_CERT_DIR` and `SSL_CERT_FILE` to a dummy location to make sure the OS installed certificates are not used when verifying manually. - -``` -SSL_CERT_DIR=/dummy SSL_CERT_FILE=/dummy openssl verify -CAfile ca.pem rancher.yourdomain.com.pem -rancher.yourdomain.com.pem: OK -``` - -If you receive the error `unable to get local issuer certificate`, the chain is incomplete. This usually means that there is an intermediate CA certificate that issued your server certificate. If you already have this certificate, you can use it in the verification of the certificate like shown below: - -``` -SSL_CERT_DIR=/dummy SSL_CERT_FILE=/dummy openssl verify -CAfile ca.pem -untrusted intermediate.pem rancher.yourdomain.com.pem -rancher.yourdomain.com.pem: OK -``` - -If you have successfully verified your certificate chain, you should include needed intermediate CA certificates in the server certificate to complete the certificate chain for any connection made to Rancher (for example, by the Rancher agent). The order of the certificates in the server certificate file should be first the server certificate itself (contents of `rancher.yourdomain.com.pem`), followed by intermediate CA certificate(s) (contents of `intermediate.pem`). - -``` ------BEGIN CERTIFICATE----- -%YOUR_CERTIFICATE% ------END CERTIFICATE----- ------BEGIN CERTIFICATE----- -%YOUR_INTERMEDIATE_CERTIFICATE% ------END CERTIFICATE----- -``` - -If you still get errors during verification, you can retrieve the subject and the issuer of the server certificate using the following command: - -``` -openssl x509 -noout -subject -issuer -in rancher.yourdomain.com.pem -subject= /C=GB/ST=England/O=Alice Ltd/CN=rancher.yourdomain.com -issuer= /C=GB/ST=England/O=Alice Ltd/CN=Alice Intermediate CA -``` - -### How do I check `Common Name` and `Subject Alternative Names` in my server certificate? - -Although technically an entry in `Subject Alternative Names` is required, having the hostname in both `Common Name` and as entry in `Subject Alternative Names` gives you maximum compatibility with older browser/applications. - -Check `Common Name`: - -``` -openssl x509 -noout -subject -in cert.pem -subject= /CN=rancher.my.org -``` - -Check `Subject Alternative Names`: - -``` -openssl x509 -noout -in cert.pem -text | grep DNS - DNS:rancher.my.org -``` - -### Why does it take 5+ minutes for a pod to be rescheduled when a node has failed? - -This is due to a combination of the following default Kubernetes settings: - -* kubelet - * `node-status-update-frequency`: Specifies how often kubelet posts node status to master (default 10s) -* kube-controller-manager - * `node-monitor-period`: The period for syncing NodeStatus in NodeController (default 5s) - * `node-monitor-grace-period`: Amount of time which we allow running Node to be unresponsive before marking it unhealthy (default 40s) - * `pod-eviction-timeout`: The grace period for deleting pods on failed nodes (default 5m0s) - -See [Kubernetes: kubelet](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/) and [Kubernetes: kube-controller-manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) for more information on these settings. - -In Kubernetes v1.13, the `TaintBasedEvictions` feature is enabled by default. See [Kubernetes: Taint based Evictions](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/#taint-based-evictions) for more information. - -* kube-apiserver (Kubernetes v1.13 and up) - * `default-not-ready-toleration-seconds`: Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration. - * `default-unreachable-toleration-seconds`: Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration. - -### Can I use keyboard shortcuts in the UI? - -Yes, most parts of the UI can be reached using keyboard shortcuts. For an overview of the available shortcuts, press `?` anywhere in the UI. diff --git a/versioned_docs/version-2.6/faq/telemetry/telemetry.md b/versioned_docs/version-2.6/faq/telemetry/telemetry.md deleted file mode 100644 index 6ab582667e1..00000000000 --- a/versioned_docs/version-2.6/faq/telemetry/telemetry.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Telemetry -weight: 8008 ---- - -### What is Telemetry? - -Telemetry collects aggregate information about the size of Rancher installations, versions of components used, and which features are used. This information is used by Rancher Labs to help make the product better and is not shared with third-parties. - -### What information is collected? - -No specific identifying information like usernames, passwords, or the names or addresses of user resources will ever be collected. - -The primary things collected include: - - - Aggregate counts (smallest, average, largest, total) of nodes per-cluster and their size (e.g. CPU cores & RAM). - - Aggregate counts of logical resources like Clusters, Projects, Namespaces, and Pods. - - Counts of what driver was used to deploy clusters and nodes (e.g. GKE vs EC2 vs Imported vs Custom). - - Versions of Kubernetes components, Operating Systems and Docker that are deployed on nodes. - - Whether some optional components are enabled or not (e.g. which auth providers are used). - - The image name & version of Rancher that is running. - - A unique randomly-generated identifier for this installation. - -### Can I see the information that is being sent? - -If Telemetry is enabled, you can go to `https:///v1-telemetry` in your installation to see the current data. - -If Telemetry is not enabled, the process that collects the data is not running, so there is nothing being collected to look at. - -### How do I turn it on or off? - -After initial setup, an administrator can go to the `Settings` page in the `Global` section of the UI and click Edit to change the `telemetry-opt` setting to either `in` or `out`. diff --git a/versioned_docs/version-2.6/helm-charts/creating-apps/creating-apps.md b/versioned_docs/version-2.6/helm-charts/creating-apps/creating-apps.md deleted file mode 100644 index 3e8555a0f8c..00000000000 --- a/versioned_docs/version-2.6/helm-charts/creating-apps/creating-apps.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -title: Creating Apps -weight: 400 ---- - -Rancher's App Marketplace is based on Helm Repositories and Helm Charts. You can add HTTP based standard Helm Repositories as well as any Git Repository which contains charts. - -> For a complete walkthrough of developing charts, see the [Chart Template Developer's Guide](https://helm.sh/docs/chart_template_guide/) in the official Helm documentation. - -- [Chart types](#chart-types) - - [Helm charts](#helm-charts) - - [Rancher charts](#rancher-charts) -- [Chart directory structure](#chart-directory-structure) -- [Additional Files for Rancher Charts](#additional-files-for-rancher-charts) - - [questions.yml](#questions-yml) - - [Min/Max Rancher versions](#min-max-rancher-versions) - - [Question variable reference](#question-variable-reference) -- [Tutorial: Example Custom Chart Creation](#tutorial-example-custom-chart-creation) - -# Chart Types - -Rancher supports two different types of charts: Helm charts and Rancher charts. - -### Helm Charts - -Native Helm charts include an application along with other software required to run it. When deploying native Helm charts, you' can provide the chart's parameter values in a YAML editor. - -### Rancher Charts - -Rancher charts are native helm charts with two files that enhance user experience: `app-readme.md` and `questions.yaml`. Read more about them in [Additional Files for Rancher Charts.](#additional-files-for-rancher-charts) - -Rancher charts add simplified chart descriptions and configuration forms to make the application deployment easy. Rancher users do not need to read through the entire list of Helm variables to understand how to launch an application. - -# Chart Directory Structure - -You can provide Helm Charts in a standard, HTTP based Helm Repository. For more information see the [Chart Repository Guide](https://helm.sh/docs/topics/chart_repository) in the official Helm documentation. - -Alternatively you can organize your charts in a Git Repository and directly add this to the App Marketplace. - -The following table demonstrates the directory structure for a Git repository. The `charts` directory is the top level directory under the repository base. Adding the repository to Rancher will expose all charts contained within it. The `questions.yaml`, `README.md`, and `requirements.yml` files are specific to Rancher charts, but are optional for chart customization. - -``` -/ - │ - ├── charts/ - │ ├── / # This directory name will be surfaced in the Rancher UI as the chart name - │ │ ├── / # Each directory at this level provides different app versions that will be selectable within the chart in the Rancher UI - │ │ │ ├── Chart.yaml # Required Helm chart information file. - │ │ │ ├── questions.yaml # Form questions displayed within the Rancher UI. Questions display in Configuration Options.* - │ │ │ ├── README.md # Optional: Helm Readme file displayed within Rancher UI. This text displays in Detailed Descriptions. - │ │ │ ├── requirements.yml # Optional: YAML file listing dependencies for the chart. - │ │ │ ├── values.yml # Default configuration values for the chart. - │ │ │ ├── templates/ # Directory containing templates that, when combined with values.yml, generates Kubernetes YAML. -``` - -# Additional Files for Rancher Charts - -Before you create your own custom catalog, you should have a basic understanding about how a Rancher chart differs from a native Helm chart. Rancher charts differ slightly from Helm charts in their directory structures. Rancher charts include two files that Helm charts do not. - -- `app-readme.md` - - A file that provides descriptive text in the chart's UI header. - -- `questions.yml` - - A file that contains questions for a form. These form questions simplify deployment of a chart. Without it, you must configure the deployment using a values YAML config, which is more difficult. The following image displays the difference between a Rancher chart (which includes `questions.yml`) and a native Helm chart (which does not). - - -
Rancher Chart with questions.yml (top) vs. Helm Chart without (bottom)
- - ![questions.yml]({{}}/img/rancher/rancher-app-2.6.png) - ![values.yaml]({{}}/img/rancher/helm-app-2.6.png) - - -### Chart.yaml annotations - -Rancher supports additional annotations that you can add to the `Chart.yaml` file. These annotations allow you to define application dependencies or configure additional UI defaults: - -| Annotation | Description | Example | -| --------------------------------- | ----------- | ------- | -| catalog.cattle.io/auto-install | If set, will install the specified chart in the specified version before installing this chart | other-chart-name=1.0.0 | -| catalog.cattle.io/display-name | A display name that should be displayed in the App Marketplace instead of the chart name | Display Name of Chart | -| catalog.cattle.io/namespace | A fixed namespace where the chart should be deployed in. If set, this can't be changed by the user | fixed-namespace | -| catalog.cattle.io/release-name | A fixed release name for the Helm installation. If set, this can't be changed by the user | fixed-release-name | -| catalog.cattle.io/requests-cpu | Total amount of CPU that should be unreserverd in the cluster. If less CPU is available, a warning will be shown | 2000m | -| catalog.cattle.io/requests-memory | Total amount of memory that should be unreserverd in the cluster. If less memory is available, a warning will be shown | 2Gi | -| catalog.cattle.io/os | Restricts the OS where this chart can be installed. Possible values: `linux`, `windows`. Default: no restriction | linux | - -### questions.yml - -Inside the `questions.yml`, most of the content will be around the questions to ask the end user, but there are some additional fields that can be set in this file. - -### Min/Max Rancher versions - -For each chart, you can add the minimum and/or maximum Rancher version, which determines whether or not this chart is available to be deployed from Rancher. - -> **Note:** Even though Rancher release versions are prefixed with a `v`, there is *no* prefix for the release version when using this option. - -``` -rancher_min_version: 2.3.0 -rancher_max_version: 2.3.99 -``` - -### Question Variable Reference - -This reference contains variables that you can use in `questions.yml` nested under `questions:`. - -| Variable | Type | Required | Description | -| ------------- | ------------- | --- |------------- | -| variable | string | true | Define the variable name specified in the `values.yml` file, using `foo.bar` for nested objects. | -| label | string | true | Define the UI label. | -| description | string | false | Specify the description of the variable.| -| type | string | false | Default to `string` if not specified (current supported types are string, multiline, boolean, int, enum, password, storageclass, hostname, pvc, and secret).| -| required | bool | false | Define if the variable is required or not (true \| false)| -| default | string | false | Specify the default value. | -| group | string | false | Group questions by input value. | -| min_length | int | false | Min character length.| -| max_length | int | false | Max character length.| -| min | int | false | Min integer length. | -| max | int | false | Max integer length. | -| options | []string | false | Specify the options when the variable type is `enum`, for example: options:
- "ClusterIP"
- "NodePort"
- "LoadBalancer"| -| valid_chars | string | false | Regular expression for input chars validation. | -| invalid_chars | string | false | Regular expression for invalid input chars validation.| -| subquestions | []subquestion | false| Add an array of subquestions.| -| show_if | string | false | Show current variable if conditional variable is true. For example `show_if: "serviceType=Nodeport"` | -| show\_subquestion_if | string | false | Show subquestions if is true or equal to one of the options. for example `show_subquestion_if: "true"`| - ->**Note:** `subquestions[]` cannot contain `subquestions` or `show_subquestions_if` keys, but all other keys in the above table are supported. diff --git a/versioned_docs/version-2.6/helm-charts/helm-charts.md b/versioned_docs/version-2.6/helm-charts/helm-charts.md deleted file mode 100644 index aab00dd91dd..00000000000 --- a/versioned_docs/version-2.6/helm-charts/helm-charts.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -title: Helm Charts in Rancher -weight: 11 ---- - -In this section, you'll learn how to manage Helm chart repositories and applications in Rancher. Helm chart repositories are managed using **Apps & Marketplace**. It uses a catalog-like system to import bundles of charts from repositories and then uses those charts to either deploy custom Helm applications or Rancher's tools such as Monitoring or Istio. Rancher tools come as pre-loaded repositories which deploy as standalone Helm charts. Any additional repositories are only added to the current cluster. - -### Changes in Rancher v2.6 - -Starting in Rancher v2.6.0, a new versioning scheme for Rancher feature charts was implemented. The changes are centered around the major version of the charts and the +up annotation for upstream charts, where applicable. - -**Major Version:** The major version of the charts is tied to Rancher minor versions. When you upgrade to a new Rancher minor version, you should ensure that all of your **Apps & Marketplace** charts are also upgraded to the correct release line for the chart. - ->**Note:** Any major versions that are less than the ones mentioned in the table below are meant for 2.5 and below only. For example, you are advised to not use <100.x.x versions of Monitoring in 2.6.x+. - -**Feature Charts:** - -| **Name** | **Supported Minimum Version** | **Supported Maximum Version** | -| ---------------- | ------------ | ------------ | -| external-ip-webhook | 100.0.0+up1.0.0 | 100.0.1+up1.0.1 | -| harvester-cloud-provider | 100.0.2+up0.1.12 | 100.0.2+up0.1.12 | -| harvester-csi-driver | 100.0.2+up0.1.11 | 100.0.2+up0.1.11 | -| rancher-alerting-drivers | 100.0.0 | 100.0.2 | -| rancher-backup | 2.0.1 | 2.1.2 | -| rancher-cis-benchmark | 2.0.1 | 2.0.4 | -| rancher-gatekeeper | 100.0.0+up3.6.0 | 100.1.0+up3.7.1 | -| rancher-istio | 100.0.0+up1.10.4 | 100.2.0+up1.12.6 | -| rancher-logging | 100.0.0+up3.12.0 | 100.1.2+up3.17.4 | -| rancher-longhorn | 100.0.0+up1.1.2 | 100.1.1+up1.2.3 | -| rancher-monitoring | 100.0.0+up16.6.0 | 100.1.0+up19.0.3 -| rancher-sriov (experimental) | 100.0.0+up0.1.0 | 100.0.3+up0.1.0 | -| rancher-vsphere-cpi | 100.3.0+up1.2.1 | 100.3.0+up1.2.1 | -| rancher-vsphere-csi | 100.3.0+up2.5.1-rancher1 | 100.3.0+up2.5.1-rancher1 | -| rancher-wins-upgrader | 0.0.100 | 100.0.0+up0.0.1 | -| neuvector | 100.0.0+up2.2.0 | 100.0.0+up2.2.0 | - -
-**Charts based on upstream:** For charts that are based on upstreams, the +up annotation should inform you of what upstream version the Rancher chart is tracking. Check the upstream version compatibility with Rancher during upgrades also. - -- As an example, `100.x.x+up16.6.0` for Monitoring tracks upstream kube-prometheus-stack `16.6.0` with some Rancher patches added to it. - -- On upgrades, ensure that you are not downgrading the version of the chart that you are using. For example, if you are using a version of Monitoring > `16.6.0` in Rancher 2.5, you should not upgrade to `100.x.x+up16.6.0`. Instead, you should upgrade to the appropriate version in the next release. - - -### Charts - -From the top-left menu select _"Apps & Marketplace"_ and you will be taken to the Charts page. - -The charts page contains all Rancher, Partner, and Custom Charts. - -* Rancher tools such as Logging or Monitoring are included under the Rancher label -* Partner charts reside under the Partners label -* Custom charts will show up under the name of the repository - -All three types are deployed and managed in the same way. - -> Apps managed by the Cluster Manager (the global view in the legacy Rancher UI) should continue to be managed only by the Cluster Manager, and apps managed with Apps & Marketplace in the new UI must be managed only by Apps & Marketplace. - -### Repositories - -From the left sidebar select _"Repositories"_. - -These items represent helm repositories, and can be either traditional helm endpoints which have an index.yaml, or git repositories which will be cloned and can point to a specific branch. In order to use custom charts, simply add your repository here and they will become available in the Charts tab under the name of the repository. - -To add a private CA for Helm Chart repositories: - -- **HTTP-based chart repositories**: You must add a base64 encoded copy of the CA certificate in DER format to the spec.caBundle field of the chart repo, such as `openssl x509 -outform der -in ca.pem | base64 -w0`. Click **Edit YAML** for the chart repo and set, as in the following example:
- ``` - [...] - spec: - caBundle: - MIIFXzCCA0egAwIBAgIUWNy8WrvSkgNzV0zdWRP79j9cVcEwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMRQwEgYDVQQKDAtNeU9yZywgSW5jLjENMAsGA1UEAwwEcm9vdDAeFw0yMTEyMTQwODMyMTdaFw0yNDEwMDMwODMyMT - ... - nDxZ/tNXt/WPJr/PgEB3hQdInDWYMg7vGO0Oz00G5kWg0sJ0ZTSoA10ZwdjIdGEeKlj1NlPyAqpQ+uDnmx6DW+zqfYtLnc/g6GuLLVPamraqN+gyU8CHwAWPNjZonFN9Vpg0PIk1I2zuOc4EHifoTAXSpnjfzfyAxCaZsnTptimlPFJJqAMj+FfDArGmr4= - [...] - ``` - - -- **Git-based chart repositories**: You must add a base64 encoded copy of the CA certificate in DER format to the spec.caBundle field of the chart repo, such as `openssl x509 -outform der -in ca.pem | base64 -w0`. Click **Edit YAML** for the chart repo and set, as in the following example:
- ``` - [...] - spec: - caBundle: - MIIFXzCCA0egAwIBAgIUWNy8WrvSkgNzV0zdWRP79j9cVcEwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMRQwEgYDVQQKDAtNeU9yZywgSW5jLjENMAsGA1UEAwwEcm9vdDAeFw0yMTEyMTQwODMyMTdaFw0yNDEwMDMwODMyMT - ... - nDxZ/tNXt/WPJr/PgEB3hQdInDWYMg7vGO0Oz00G5kWg0sJ0ZTSoA10ZwdjIdGEeKlj1NlPyAqpQ+uDnmx6DW+zqfYtLnc/g6GuLLVPamraqN+gyU8CHwAWPNjZonFN9Vpg0PIk1I2zuOc4EHifoTAXSpnjfzfyAxCaZsnTptimlPFJJqAMj+FfDArGmr4= - [...] - ``` - - -> **Note:** Helm chart repositories with authentication -> -> As of Rancher v2.6.3, a new value `disableSameOriginCheck` has been added to the Repo.Spec. This allows users to bypass the same origin checks, sending the repository Authentication information as a Basic Auth Header with all API calls. This is not recommended but can be used as a temporary solution in cases of non-standard Helm chart repositories such as those that have redirects to a different origin URL. -> -> To use this feature for an existing Helm chart repository, click ⋮ > Edit YAML. On the `spec` portion of the YAML file, add `disableSameOriginCheck` and set it to `true`. -> -> ```yaml -[...] -spec: - disableSameOriginCheck: true -[...] -``` - -### Helm Compatibility - -Only Helm 3 compatible charts are supported. - - -### Deployment and Upgrades - -From the _"Charts"_ tab select a Chart to install. Rancher and Partner charts may have extra configurations available through custom pages or questions.yaml files, but all chart installations can modify the values.yaml and other basic settings. Once you click install, a Helm operation job is deployed, and the console for the job is displayed. - -To view all recent changes, go to the _"Recent Operations"_ tab. From there you can view the call that was made, conditions, events, and logs. - -After installing a chart, you can find it in the _"Installed Apps"_ tab. In this section you can upgrade or delete the installation, and see further details. When choosing to upgrade, the form and values presented will be the same as installation. - -Most Rancher tools have additional pages located in the toolbar below the _"Apps & Marketplace"_ section to help manage and use the features. These pages include links to dashboards, forms to easily add Custom Resources, and additional information. - -> If you are upgrading your chart using _"Customize Helm options before upgrade"_ , please be aware that using the _"--force"_ option may result in errors if your chart has immutable fields. This is because some objects in Kubernetes cannot be changed once they are created. To ensure you do not get this error you can: -> -> * use the default upgrade option ( i.e do not use _"--force"_ option ) -> * uninstall the existing chart and install the upgraded chart -> * delete the resources with immutable fields from the cluster before performing the _"--force"_ upgrade - -#### Changes in Rancher v2.6.3 - -The upgrade button has been removed for legacy apps from the **Apps & Marketplace > Installed Apps** page. - -If you have a legacy app installed and want to upgrade it: - -- The legacy [feature flag]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) must be turned on (if it's not turned on automatically because of having a legacy app before upgrading) -- You can upgrade the app from cluster explorer, from the left nav section **Legacy > Project > Apps** -- For multi-cluster apps, you can go to **≡ > Multi-cluster Apps** and upgrade the app from there - -### Limitations - -[Dashboard apps or Rancher feature charts](../helm-charts/) **cannot** be installed using the Rancher CLI. diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/aks/aks.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/aks/aks.md deleted file mode 100644 index b48aca076d9..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/aks/aks.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -title: Installing Rancher on Azure Kubernetes Service -shortTitle: AKS -weight: 4 ---- - -This page covers how to install Rancher on Microsoft's Azure Kubernetes Service (AKS). - -The guide uses command line tools to provision an AKS cluster with an ingress. If you prefer to provision your cluster using the Azure portal, refer to the [official documentation](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough-portal). - -If you already have an AKS Kubernetes cluster, skip to the step about [installing an ingress.](#5-install-an-ingress) Then install the Rancher Helm chart following the instructions on [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart) - -# Prerequisites - ->**Note** ->Deploying to Microsoft Azure will incur charges. - -- [Microsoft Azure Account](https://azure.microsoft.com/en-us/free/): A Microsoft Azure Account is required to create resources for deploying Rancher and Kubernetes. -- [Microsoft Azure Subscription](https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription#create-a-subscription-in-the-azure-portal): Use this link to follow a tutorial to create a Microsoft Azure subscription if you don't have one yet. -- [Micsoroft Azure Tenant](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant): Use this link and follow instructions to create a Microsoft Azure tenant. -- Your subscription has sufficient quota for at least 2 vCPUs. For details on Rancher server resource requirements, refer to [this section]({{}}/rancher/v2.6/en/installation/requirements/#rke-and-hosted-kubernetes) -- When installing Rancher with Helm in Azure, use the L7 load balancer to avoid networking issues. For more information, refer to the documentation on [Azure load balancer limitations](https://docs.microsoft.com/en-us/azure/load-balancer/components#limitations). - -# 1. Prepare your Workstation - -Install the following command line tools on your workstation: - -- The Azure CLI, **az:** For help, refer to these [installation steps.](https://docs.microsoft.com/en-us/cli/azure/) -- **kubectl:** For help, refer to these [installation steps.](https://kubernetes.io/docs/tasks/tools/#kubectl) -- **helm:** For help, refer to these [installation steps.](https://helm.sh/docs/intro/install/) - -# 2. Create a Resource Group - -After installing the CLI, you will need to log in with your Azure account. - -``` -az login -``` - -Create a [resource group](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal) to hold all relevant resources for your cluster. Use a location that applies to your use case. - -``` -az group create --name rancher-rg --location eastus -``` - -# 3. Create the AKS Cluster - -To create an AKS cluster, run the following command. Use a VM size that applies to your use case. Refer to [this article](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes) for available sizes and options. When choosing a Kubernetes version, be sure to first consult the [support matrix](https://rancher.com/support-matrix/) to find the highest version of Kubernetes that has been validated for your Rancher version. - -``` -az aks create \ - --resource-group rancher-rg \ - --name rancher-server \ - --kubernetes-version 1.20.7 \ - --node-count 3 \ - --node-vm-size Standard_D2_v3 -``` - -The cluster will take some time to be deployed. - -# 4. Get Access Credentials - -After the cluster is deployed, get the access credentials. - -``` -az aks get-credentials --resource-group rancher-rg --name rancher-server -``` - -This command merges your cluster's credentials into the existing kubeconfig and allows `kubectl` to interact with the cluster. - -# 5. Install an Ingress - -The cluster needs an Ingress so that Rancher can be accessed from outside the cluster. Installing an Ingress requires allocating a public IP address. Ensure you have sufficient quota, otherwise it will fail to assign the IP address. Limits for public IP addresses are applicable at a regional level per subscription. - -The following command installs an `nginx-ingress-controller` with a Kubernetes load balancer service. - -``` -helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx -helm repo update -helm upgrade --install \ - ingress-nginx ingress-nginx/ingress-nginx \ - --namespace ingress-nginx \ - --set controller.service.type=LoadBalancer \ - --version 3.12.0 \ - --create-namespace -``` - -# 6. Get Load Balancer IP - -To get the address of the load balancer, run: - -``` -kubectl get service ingress-nginx-controller --namespace=ingress-nginx -``` - -The result should look similar to the following: - -``` -NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) - AGE -ingress-nginx-controller LoadBalancer 10.0.116.18 40.31.180.83 80:31229/TCP,443:31050/TCP - 67s -``` - -Save the `EXTERNAL-IP`. - -# 7. Set up DNS - -External traffic to the Rancher server will need to be directed at the load balancer you created. - -Set up a DNS to point at the `EXTERNAL-IP` that you saved. This DNS will be used as the Rancher server URL. - -There are many valid ways to set up the DNS. For help, refer to the [Azure DNS documentation](https://docs.microsoft.com/en-us/azure/dns/) - -# 8. Install the Rancher Helm Chart - -Next, install the Rancher Helm chart by following the instructions on [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart) The Helm instructions are the same for installing Rancher on any Kubernetes distribution. - -Use that DNS name from the previous step as the Rancher server URL when you install Rancher. It can be passed in as a Helm option. For example, if the DNS name is `rancher.my.org`, you could run the Helm installation command with the option `--set hostname=rancher.my.org`. diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/amazon-eks/amazon-eks.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/amazon-eks/amazon-eks.md deleted file mode 100644 index 85e2f93bd56..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/amazon-eks/amazon-eks.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -title: Installing Rancher on Amazon EKS -shortTitle: Amazon EKS -weight: 4 ---- - -This page covers two ways to install Rancher on EKS. - -The first is a guide for deploying the Rancher server on an EKS cluster using CloudFormation. This guide was created in collaboration with Amazon Web Services to show how to deploy Rancher following best practices. - -The second is a guide for installing an EKS cluster with an ingress by using command line tools. This guide may be useful if you want to use fewer resources while trying out Rancher on EKS. - -If you already have an EKS Kubernetes cluster, skip to the step about [installing an ingress.](#5-install-an-ingress) Then install the Rancher Helm chart following the instructions on [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart) - -- [Automated Quickstart using AWS Best Practices](#automated-quickstart-using-aws-best-practices) -- [Creating an EKS Cluster for the Rancher Server](#creating-an-eks-cluster-for-the-rancher-server) - -# Automated Quickstart using AWS Best Practices - -Rancher and Amazon Web Services collaborated on a quick start guide for deploying Rancher on an EKS cluster following AWS best practices. The deployment guide is [here.](https://aws-quickstart.github.io/quickstart-eks-rancher/) - -The quick start guide provides three options for deploying Rancher on EKS: - -- **Deploy Rancher into a new VPC and new Amazon EKS cluster**. This option builds a new AWS environment consisting of the VPC, subnets, NAT gateways, security groups, bastion hosts, Amazon EKS cluster, and other infrastructure components. It then deploys Rancher into this new EKS cluster. -- **Deploy Rancher into an existing VPC and a new Amazon EKS cluster**. This option provisions Rancher in your existing AWS infrastructure. -- **Deploy Rancher into an existing VPC and existing Amazon EKS cluster**. This option provisions Rancher in your existing AWS infrastructure. - -Deploying this Quick Start for a new virtual private cloud (VPC) and new Amazon EKS cluster using default parameters builds the following Rancher environment in the AWS Cloud: - -- A highly available architecture that spans three Availability Zones.* -- A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.* -- In the public subnets: - - Managed network address translation (NAT) gateways to allow outbound internet access for resources.* - - Linux bastion hosts in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in public and private subnets.* -- In the private subnets: - - Kubernetes nodes in an Auto Scaling group.* - - A Network Load Balancer (not shown) for accessing the Rancher console. -- Rancher deployment using AWS Systems Manager automation. -- Amazon EKS service for the EKS cluster, which provides the Kubernetes control plane.* -- An Amazon Route 53 DNS record for accessing the Rancher deployment. - -\* The CloudFormation template that deploys the Quick Start into an existing Amazon EKS cluster skips the components marked by asterisks and prompts you for your existing VPC configuration. - -# Creating an EKS Cluster for the Rancher Server - -In this section, you'll install an EKS cluster with an ingress by using command line tools. This guide may be useful if you want to use fewer resources while trying out Rancher on EKS. - -> **Prerequisites:** -> -> - You should already have an AWS account. -> - It is recommended to use an IAM user instead of the root AWS account. You will need the IAM user's access key and secret key to configure the AWS command line interface. -> - The IAM user needs the minimum IAM policies described in the official [eksctl documentation.](https://eksctl.io/usage/minimum-iam-policies/) - -### 1. Prepare your Workstation - -Install the following command line tools on your workstation: - -- **The AWS CLI v2:** For help, refer to these [installation steps.](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) -- **eksctl:** For help, refer to these [installation steps.](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html) -- **kubectl:** For help, refer to these [installation steps.](https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html) -- **helm:** For help, refer to these [installation steps.](https://helm.sh/docs/intro/install/) - -### 2. Configure the AWS CLI - -To configure the AWS CLI, run the following command: - -``` -aws configure -``` - -Then enter the following values: - -| Value | Description | -|-------|-------------| -| AWS Access Key ID | The access key credential for the IAM user with EKS permissions. | -| AWS Secret Access Key | The secret key credential for the IAM user with EKS permissions. | -| Default region name | An [AWS region](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html#Concepts.RegionsAndAvailabilityZones.Regions) where the cluster nodes will be located. | -| Default output format | Enter `json`. | - -### 3. Create the EKS Cluster - -To create an EKS cluster, run the following command. Use the AWS region that applies to your use case. When choosing a Kubernetes version, be sure to first consult the [support matrix](https://rancher.com/support-matrix/) to find the highest version of Kubernetes that has been validated for your Rancher version. - -``` -eksctl create cluster \ - --name rancher-server \ - --version 1.20 \ - --region us-west-2 \ - --nodegroup-name ranchernodes \ - --nodes 3 \ - --nodes-min 1 \ - --nodes-max 4 \ - --managed -``` - -The cluster will take some time to be deployed with CloudFormation. - -### 4. Test the Cluster - -To test the cluster, run: - -``` -eksctl get cluster -``` - -The result should look like the following: - -``` -eksctl get cluster -2021-03-18 15:09:35 [ℹ] eksctl version 0.40.0 -2021-03-18 15:09:35 [ℹ] using region us-west-2 -NAME REGION EKSCTL CREATED -rancher-server-cluster us-west-2 True -``` - -### 5. Install an Ingress - -The cluster needs an Ingress so that Rancher can be accessed from outside the cluster. - -The following command installs an `nginx-ingress-controller` with a LoadBalancer service. This will result in an ELB (Elastic Load Balancer) in front of NGINX: - -``` -helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx -helm repo update -helm upgrade --install \ - ingress-nginx ingress-nginx/ingress-nginx \ - --namespace ingress-nginx \ - --set controller.service.type=LoadBalancer \ - --version 3.12.0 \ - --create-namespace -``` - -### 6. Get Load Balancer IP - -To get the address of the load balancer, run: - -``` -kubectl get service ingress-nginx-controller --namespace=ingress-nginx -``` - -The result should look similar to the following: - -``` -NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) - AGE -ingress-nginx-controller LoadBalancer 10.100.90.18 a904a952c73bf4f668a17c46ac7c56ab-962521486.us-west-2.elb.amazonaws.com 80:31229/TCP,443:31050/TCP - 27m -``` - -Save the `EXTERNAL-IP`. - -### 7. Set up DNS - -External traffic to the Rancher server will need to be directed at the load balancer you created. - -Set up a DNS to point at the external IP that you saved. This DNS will be used as the Rancher server URL. - -There are many valid ways to set up the DNS. For help, refer to the AWS documentation on [routing traffic to an ELB load balancer.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html) - -### 8. Install the Rancher Helm Chart - -Next, install the Rancher Helm chart by following the instructions on [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart) The Helm instructions are the same for installing Rancher on any Kubernetes distribution. - -Use that DNS name from the previous step as the Rancher server URL when you install Rancher. It can be passed in as a Helm option. For example, if the DNS name is `rancher.my.org`, you could run the Helm installation command with the option `--set hostname=rancher.my.org`. diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/chart-options/chart-options.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/chart-options/chart-options.md deleted file mode 100644 index 4436fcfe473..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/chart-options/chart-options.md +++ /dev/null @@ -1,273 +0,0 @@ ---- -title: Rancher Helm Chart Options -weight: 1 -aliases: - - /rancher/v2.6/en/installation/resources/chart-options ---- - -This page is a configuration reference for the Rancher Helm chart. - -For help choosing a Helm chart version, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/choosing-version/) - -For information on enabling experimental features, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) - -- [Common Options](#common-options) -- [Advanced Options](#advanced-options) -- [API Audit Log](#api-audit-log) -- [Setting Extra Environment Variables](#setting-extra-environment-variables) -- [TLS Settings](#tls-settings) -- [Customizing your Ingress](#customizing-your-ingress) -- [HTTP Proxy](#http-proxy) -- [Additional Trusted CAs](#additional-trusted-cas) -- [Private Registry and Air Gap Installs](#private-registry-and-air-gap-installs) -- [External TLS Termination](#external-tls-termination) - -### Common Options - -| Option | Default Value | Description | -| ------------------------- | ------------- | ---------------------------------------------------------------------------------- | -| `bootstrapPassword` | " " | `string` - Set the [bootstrap password](#bootstrap-password) for the first admin user. After logging in, the admin will need to reset their password. A randomly generated bootstrap password is used if this value is not set. -| `hostname` | " " | `string` - the Fully Qualified Domain Name for your Rancher Server | -| `ingress.tls.source` | "rancher" | `string` - Where to get the cert for the ingress. - "rancher, letsEncrypt, secret" | -| `letsEncrypt.email` | " " | `string` - Your email address | -| `letsEncrypt.environment` | "production" | `string` - Valid options: "staging, production" | -| `privateCA` | false | `bool` - Set to true if your cert is signed by a private CA | - -
- -### Advanced Options - -| Option | Default Value | Description | -| ------------------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `additionalTrustedCAs` | false | `bool` - See [Additional Trusted CAs](#additional-trusted-cas) | -| `addLocal` | "true" | `string` - Have Rancher detect and import the "local" Rancher server cluster. _Note: This option is no longer available in v2.5.0. Consider using the `restrictedAdmin` option to prevent users from modifying the local cluster._ | -| `antiAffinity` | "preferred" | `string` - AntiAffinity rule for Rancher pods - "preferred, required" | -| `auditLog.destination` | "sidecar" | `string` - Stream to sidecar container console or hostPath volume - "sidecar, hostPath" | -| `auditLog.hostPath` | "/var/log/rancher/audit" | `string` - log file destination on host (only applies when `auditLog.destination` is set to `hostPath`) | -| `auditLog.level` | 0 | `int` - set the [API Audit Log]({{}}/rancher/v2.6/en/installation/resources/advanced/api-audit-log) level. 0 is off. [0-3] | -| `auditLog.maxAge` | 1 | `int` - maximum number of days to retain old audit log files (only applies when `auditLog.destination` is set to `hostPath`) | -| `auditLog.maxBackup` | 1 | `int` - maximum number of audit log files to retain (only applies when `auditLog.destination` is set to `hostPath`) | -| `auditLog.maxSize` | 100 | `int` - maximum size in megabytes of the audit log file before it gets rotated (only applies when `auditLog.destination` is set to `hostPath`) | -| `busyboxImage` | "busybox" | `string` - Image location for busybox image used to collect audit logs | -| `certmanager.version` | "" | `string` - set cert-manager compatibility | -| `debug` | false | `bool` - set debug flag on rancher server | -| `extraEnv` | [] | `list` - set additional environment variables for Rancher | -| `imagePullSecrets` | [] | `list` - list of names of Secret resource containing private registry credentials | -| `ingress.configurationSnippet` | "" | `string` - Add additional Nginx configuration. Can be used for proxy configuration. | -| `ingress.extraAnnotations` | {} | `map` - additional annotations to customize the ingress | -| `ingress.enabled` | true | When set to false, Helm will not install a Rancher ingress. Set the option to false to deploy your own ingress. | -| `letsEncrypt.ingress.class` | "" | `string` - optional ingress class for the cert-manager acmesolver ingress that responds to the Let's Encrypt ACME challenges. Options: traefik, nginx. | | -| `noProxy` | "127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local,cattle-system.svc" | `string` - comma separated list of hostnames or ip address not to use the proxy | | -| `proxy` | "" | `string` - HTTP[S] proxy server for Rancher | -| `rancherImage` | "rancher/rancher" | `string` - rancher image source | -| `rancherImagePullPolicy` | "IfNotPresent" | `string` - Override imagePullPolicy for rancher server images - "Always", "Never", "IfNotPresent" | -| `rancherImageTag` | same as chart version | `string` - rancher/rancher image tag | -| `replicas` | 3 | `int` - Number of Rancher server replicas. Setting to -1 will dynamically choose 1, 2, or 3 based on the number of available nodes in the cluster. | -| `resources` | {} | `map` - rancher pod resource requests & limits | -| `restrictedAdmin` | `false` | `bool` - When this option is set to true, the initial Rancher user has restricted access to the local Kubernetes cluster to prevent privilege escalation. For more information, see the section about the [restricted-admin role.]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/#restricted-admin) | -| `systemDefaultRegistry` | "" | `string` - private registry to be used for all system container images, e.g., http://registry.example.com/ | -| `tls` | "ingress" | `string` - See [External TLS Termination](#external-tls-termination) for details. - "ingress, external" | -| `useBundledSystemChart` | `false` | `bool` - select to use the system-charts packaged with Rancher server. This option is used for air gapped installations. | - - - -### Bootstrap Password - -When Rancher starts for the first time, a password is randomly generated for the first admin user. When the admin first logs in to Rancher, the UI shows commands that can be used to retrieve the bootstrap password. The admin needs to run those commands and log in with the bootstrap password. Then Rancher gives the admin an opportunity to reset the password. - -If you want to use a specific bootstrap password instead of a randomly generated one, provide the password. - -```plain ---set bootstrapPassword="rancher" -``` - -The password, whether provided or generated, will be stored in a Kubernetes secret. After Rancher is installed, the UI will show instructions for how to retrieve the password using kubectl: - -``` -kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{ .data.bootstrapPassword|base64decode}}{{ "\n" }}' -``` - -### API Audit Log - -Enabling the [API Audit Log]({{}}/rancher/v2.6/en/installation/resources/advanced/api-audit-log) - -You can collect this log as you would any container log. Enable [logging]({{}}/rancher/v2.6/en/logging) for the `System` Project on the Rancher server cluster. - -```plain ---set auditLog.level=1 -``` - -By default enabling Audit Logging will create a sidecar container in the Rancher pod. This container (`rancher-audit-log`) will stream the log to `stdout`. You can collect this log as you would any container log. When using the sidecar as the audit log destination, the `hostPath`, `maxAge`, `maxBackups`, and `maxSize` options do not apply. It's advised to use your OS or Docker daemon's log rotation features to control disk space use. Enable [logging]({{}}/rancher/v2.6/en/logging) for the Rancher server cluster or System Project. - -Set the `auditLog.destination` to `hostPath` to forward logs to volume shared with the host system instead of streaming to a sidecar container. When setting the destination to `hostPath` you may want to adjust the other auditLog parameters for log rotation. - -### Setting Extra Environment Variables - -You can set extra environment variables for Rancher server using `extraEnv`. This list uses the same `name` and `value` keys as the container manifest definitions. Remember to quote the values. - -```plain ---set 'extraEnv[0].name=CATTLE_TLS_MIN_VERSION' ---set 'extraEnv[0].value=1.0' -``` - -### TLS Settings - -When you install Rancher inside of a Kubernetes cluster, TLS is offloaded at the cluster's ingress controller. The possible TLS settings depend on the used ingress controller. - -See [TLS settings]({{}}/rancher/v2.6/en/installation/resources/tls-settings) for more information and options. - -### Import `local` Cluster - -By default Rancher server will detect and import the `local` cluster it's running on. User with access to the `local` cluster will essentially have "root" access to all the clusters managed by Rancher server. - -> **Important:** If you turn addLocal off, most Rancher v2.5 features won't work, including the EKS provisioner. - -If this is a concern in your environment you can set this option to "false" on your initial install. - -This option is only effective on the initial Rancher install. See [Issue 16522](https://github.com/rancher/rancher/issues/16522) for more information. - -```plain ---set addLocal="false" -``` - -### Customizing your Ingress - -To customize or use a different ingress with Rancher server you can set your own Ingress annotations. - -Example on setting a custom certificate issuer: - -```plain ---set ingress.extraAnnotations.'cert-manager\.io/cluster-issuer'=issuer-name -``` - -Example on setting a static proxy header with `ingress.configurationSnippet`. This value is parsed like a template so variables can be used. - -```plain ---set ingress.configurationSnippet='more_set_input_headers X-Forwarded-Host {{ .Values.hostname }};' -``` - -### HTTP Proxy - -Rancher requires internet access for some functionality (helm charts). Use `proxy` to set your proxy server. - -Add your IP exceptions to the `noProxy` list. Make sure you add the Pod cluster IP range (default: `10.42.0.0/16`), Service cluster IP range (default: `10.43.0.0/16`), the internal cluster domains (default: `.svc,.cluster.local`) and any worker cluster `controlplane` nodes. Rancher supports CIDR notation ranges in this list. - -```plain ---set proxy="http://:@:/" ---set noProxy="127.0.0.0/8\,10.0.0.0/8\,172.16.0.0/12\,192.168.0.0/16\,.svc\,.cluster.local" -``` - -### Additional Trusted CAs - -If you have private registries, catalogs or a proxy that intercepts certificates, you may need to add additional trusted CAs to Rancher. - -```plain ---set additionalTrustedCAs=true -``` - -Once the Rancher deployment is created, copy your CA certs in pem format into a file named `ca-additional.pem` and use `kubectl` to create the `tls-ca-additional` secret in the `cattle-system` namespace. - -```plain -kubectl -n cattle-system create secret generic tls-ca-additional --from-file=ca-additional.pem=./ca-additional.pem -``` - -### Private Registry and Air Gap Installs - -For details on installing Rancher with a private registry, see the [air gap installation docs.]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) - -# External TLS Termination - -We recommend configuring your load balancer as a Layer 4 balancer, forwarding plain 80/tcp and 443/tcp to the Rancher Management cluster nodes. The Ingress Controller on the cluster will redirect http traffic on port 80 to https on port 443. - -You may terminate the SSL/TLS on a L7 load balancer external to the Rancher cluster (ingress). Use the `--set tls=external` option and point your load balancer at port http 80 on all of the Rancher cluster nodes. This will expose the Rancher interface on http port 80. Be aware that clients that are allowed to connect directly to the Rancher cluster will not be encrypted. If you choose to do this we recommend that you restrict direct access at the network level to just your load balancer. - -> **Note:** If you are using a Private CA signed certificate, add `--set privateCA=true` and see [Adding TLS Secrets - Using a Private CA Signed Certificate]({{}}/rancher/v2.6/en/installation/resources/tls-secrets/) to add the CA cert for Rancher. - -Your load balancer must support long lived websocket connections and will need to insert proxy headers so Rancher can route links correctly. - -### Configuring Ingress for External TLS when Using NGINX v0.25 - -In NGINX v0.25, the behavior of NGINX has [changed](https://github.com/kubernetes/ingress-nginx/blob/master/Changelog.md#0220) regarding forwarding headers and external TLS termination. Therefore, in the scenario that you are using external TLS termination configuration with NGINX v0.25, you must edit the `cluster.yml` to enable the `use-forwarded-headers` option for ingress: - -```yaml -ingress: - provider: nginx - options: - use-forwarded-headers: 'true' -``` - -### Required Headers - -- `Host` -- `X-Forwarded-Proto` -- `X-Forwarded-Port` -- `X-Forwarded-For` - -### Recommended Timeouts - -- Read Timeout: `1800 seconds` -- Write Timeout: `1800 seconds` -- Connect Timeout: `30 seconds` - -### Health Checks - -Rancher will respond `200` to health checks on the `/healthz` endpoint. - -### Example NGINX config - -This NGINX configuration is tested on NGINX 1.14. - -> **Note:** This NGINX configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - HTTP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/). - -- Replace `IP_NODE1`, `IP_NODE2` and `IP_NODE3` with the IP addresses of the nodes in your cluster. -- Replace both occurrences of `FQDN` to the DNS name for Rancher. -- Replace `/certs/fullchain.pem` and `/certs/privkey.pem` to the location of the server certificate and the server certificate key respectively. - -``` -worker_processes 4; -worker_rlimit_nofile 40000; - -events { - worker_connections 8192; -} - -http { - upstream rancher { - server IP_NODE_1:80; - server IP_NODE_2:80; - server IP_NODE_3:80; - } - - map $http_upgrade $connection_upgrade { - default Upgrade; - '' close; - } - - server { - listen 443 ssl http2; - server_name FQDN; - ssl_certificate /certs/fullchain.pem; - ssl_certificate_key /certs/privkey.pem; - - location / { - proxy_set_header Host $host; - proxy_set_header X-Forwarded-Proto $scheme; - proxy_set_header X-Forwarded-Port $server_port; - proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; - proxy_pass http://rancher; - proxy_http_version 1.1; - proxy_set_header Upgrade $http_upgrade; - proxy_set_header Connection $connection_upgrade; - # This allows the ability for the execute shell window to remain open for up to 15 minutes. Without this parameter, the default is 1 minute and will automatically close. - proxy_read_timeout 900s; - proxy_buffering off; - } - } - - server { - listen 80; - server_name FQDN; - return 301 https://$server_name$request_uri; - } -} -``` diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/gke/gke.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/gke/gke.md deleted file mode 100644 index 347c3c8ec90..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/gke/gke.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -title: Installing Rancher on a Google Kubernetes Engine Cluster -shortTitle: GKE -weight: 5 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -In this section, you'll learn how to install Rancher using Google Kubernetes Engine. - -If you already have a GKE Kubernetes cluster, skip to the step about [installing an ingress.](#7-install-an-ingress) Then install the Rancher Helm chart following the instructions on [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart) - -# Prerequisites - -- You will need a Google account. -- You will need a Google Cloud billing account. You can manage your Cloud Billing accounts using the Google Cloud Console. For more information about the Cloud Console, visit [General guide to the console.](https://support.google.com/cloud/answer/3465889?hl=en&ref_topic=3340599) -- You will need a cloud quota for at least one in-use IP address and at least 2 CPUs. For more details about hardware requirements for the Rancher server, refer to [this section.]({{}}/rancher/v2.6/en/installation/requirements/#rke-and-hosted-kubernetes) - -# 1. Enable the Kubernetes Engine API - -Take the following steps to enable the Kubernetes Engine API: - -1. Visit the [Kubernetes Engine page](https://console.cloud.google.com/projectselector/kubernetes?_ga=2.169595943.767329331.1617810440-856599067.1617343886) in the Google Cloud Console. -1. Create or select a project. -1. Open the project and enable the Kubernetes Engine API for the project. Wait for the API and related services to be enabled. This can take several minutes. -1. Make sure that billing is enabled for your Cloud project. For information on how to enable billing for your project, refer to the [Google Cloud documentation.](https://cloud.google.com/billing/docs/how-to/modify-project#enable_billing_for_a_project) - -# 2. Open the Cloud Shell - -Cloud Shell is a shell environment for managing resources hosted on Google Cloud. Cloud Shell comes preinstalled with the `gcloud` command-line tool and kubectl command-line tool. The `gcloud` tool provides the primary command-line interface for Google Cloud, and `kubectl` provides the primary command-line interface for running commands against Kubernetes clusters. - -The following sections describe how to launch the cloud shell from the Google Cloud Console or from your local workstation. - -### Cloud Shell - -To launch the shell from the [Google Cloud Console,](https://console.cloud.google.com) go to the upper-right corner of the console and click the terminal button. When hovering over the button, it is labeled **Activate Cloud Shell**. - -### Local Shell - -To install `gcloud` and `kubectl`, perform the following steps: - -1. Install the Cloud SDK by following [these steps.](https://cloud.google.com/sdk/docs/install) The Cloud SDK includes the `gcloud` command-line tool. The steps vary based on your OS. -1. After installing Cloud SDK, install the `kubectl` command-line tool by running the following command: - - ``` - gcloud components install kubectl - ``` - In a later step, `kubectl` will be configured to use the new GKE cluster. -1. [Install Helm 3](https://helm.sh/docs/intro/install/) if it is not already installed. -1. Enable Helm experimental [support for OCI images](https://github.com/helm/community/blob/master/hips/hip-0006.md) with the `HELM_EXPERIMENTAL_OCI` variable. Add the following line to `~/.bashrc` (or `~/.bash_profile` in macOS, or wherever your shell stores environment variables): - - ``` - export HELM_EXPERIMENTAL_OCI=1 - ``` -1. Run the following command to load your updated `.bashrc` file: - - ``` - source ~/.bashrc - ``` - If you are running macOS, use this command: - ``` - source ~/.bash_profile - ``` - - - -# 3. Configure the gcloud CLI - - Set up default gcloud settings using one of the following methods: - -- Using gcloud init, if you want to be walked through setting defaults. -- Using gcloud config, to individually set your project ID, zone, and region. - - - - -1. Run gcloud init and follow the directions: - - ``` - gcloud init - ``` - If you are using SSH on a remote server, use the --console-only flag to prevent the command from launching a browser: - - ``` - gcloud init --console-only - ``` -2. Follow the instructions to authorize gcloud to use your Google Cloud account and select the new project that you created. - - - - - - - -# 4. Confirm that gcloud is configured correctly - -Run: - -``` -gcloud config list -``` - -The output should resemble the following: - -``` -[compute] -region = us-west1 # Your chosen region -zone = us-west1-b # Your chosen zone -[core] -account = -disable_usage_reporting = True -project = - -Your active configuration is: [default] -``` - -# 5. Create a GKE Cluster - -The following command creates a three-node cluster. - -Replace `cluster-name` with the name of your new cluster. - -When choosing a Kubernetes version, be sure to first consult the [support matrix](https://rancher.com/support-matrix/) to find the highest version of Kubernetes that has been validated for your Rancher version. - -``` -gcloud container clusters create cluster-name --num-nodes=3 --cluster-version=1.20.8-gke.900 -``` - -# 6. Get Authentication Credentials - -After creating your cluster, you need to get authentication credentials to interact with the cluster: - -``` -gcloud container clusters get-credentials cluster-name -``` - -This command configures `kubectl` to use the cluster you created. - -# 7. Install an Ingress - -The cluster needs an Ingress so that Rancher can be accessed from outside the cluster. - -The following command installs an `nginx-ingress-controller` with a LoadBalancer service: - -``` -helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx -helm repo update -helm upgrade --install \ - ingress-nginx ingress-nginx/ingress-nginx \ - --namespace ingress-nginx \ - --set controller.service.type=LoadBalancer \ - --version 3.12.0 \ - --create-namespace -``` - -# 8. Get the Load Balancer IP - -To get the address of the load balancer, run: - -``` -kubectl get service ingress-nginx-controller --namespace=ingress-nginx -``` - -The result should look similar to the following: - -``` -NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE -ingress-nginx-controller LoadBalancer 10.3.244.156 35.233.206.34 80:31876/TCP,443:32497/TCP 81s -``` - -Save the `EXTERNAL-IP`. - -# 9. Set up DNS - -External traffic to the Rancher server will need to be directed at the load balancer you created. - -Set up a DNS to point at the external IP that you saved. This DNS will be used as the Rancher server URL. - -There are many valid ways to set up the DNS. For help, refer to the Google Cloud documentation about [managing DNS records.](https://cloud.google.com/dns/docs/records) - -# 10. Install the Rancher Helm chart - -Next, install the Rancher Helm chart by following the instructions on [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart) The Helm instructions are the same for installing Rancher on any Kubernetes distribution. - -Use the DNS name from the previous step as the Rancher server URL when you install Rancher. It can be passed in as a Helm option. For example, if the DNS name is `rancher.my.org`, you could run the Helm installation command with the option `--set hostname=rancher.my.org`. diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/install-rancher-on-k8s.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/install-rancher-on-k8s.md deleted file mode 100644 index d16d51e6555..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/install-rancher-on-k8s.md +++ /dev/null @@ -1,301 +0,0 @@ ---- -title: Install/Upgrade Rancher on a Kubernetes Cluster -description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation -weight: 2 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -In this section, you'll learn how to deploy Rancher on a Kubernetes cluster using the Helm CLI. - -- [Prerequisites](#prerequisites) -- [Install the Rancher Helm Chart](#install-the-rancher-helm-chart) - -# Prerequisites - -- [Kubernetes Cluster](#kubernetes-cluster) -- [CLI Tools](#cli-tools) -- [Ingress Controller (Only for Hosted Kubernetes)](#ingress-controller-for-hosted-kubernetes) - -### Kubernetes Cluster - -Set up the Rancher server's local Kubernetes cluster. - -Rancher can be installed on any Kubernetes cluster. This cluster can use upstream Kubernetes, or it can use one of Rancher's Kubernetes distributions, or it can be a managed Kubernetes cluster from a provider such as Amazon EKS. - -For help setting up a Kubernetes cluster, we provide these tutorials: - -- **RKE:** For the tutorial to install an RKE Kubernetes cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-rke/) For help setting up the infrastructure for a high-availability RKE cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha) -- **K3s:** For the tutorial to install a K3s Kubernetes cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-with-external-db) For help setting up the infrastructure for a high-availability K3s cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db) -- **RKE2:** For the tutorial to install an RKE2 Kubernetes cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-rke2) For help setting up the infrastructure for a high-availability RKE2 cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-rke2-ha) -- **Amazon EKS:** For details on how to install Rancher on Amazon EKS, including how to install an ingress so that the Rancher server can be accessed, refer to [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/amazon-eks) -- **AKS:** For details on how to install Rancher with Azure Kubernetes Service, including how to install an ingress so that the Rancher server can be accessed, refer to [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/aks) -- **GKE:** For details on how to install Rancher with Google Kubernetes Engine, including how to install an ingress so that the Rancher server can be accessed, refer to [this page.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/gke) - -### CLI Tools - -The following CLI tools are required for setting up the Kubernetes cluster. Please make sure these tools are installed and available in your `$PATH`. - -- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) - Kubernetes command-line tool. -- [helm](https://docs.helm.sh/using_helm/#installing-helm) - Package management for Kubernetes. Refer to the [Helm version requirements]({{}}/rancher/v2.6/en/installation/resources/helm-version) to choose a version of Helm to install Rancher. Refer to the [instructions provided by the Helm project](https://helm.sh/docs/intro/install/) for your specific platform. - -### Ingress Controller (For Hosted Kubernetes) - -To deploy Rancher on a hosted Kubernetes cluster such as EKS, GKE, or AKS, you should deploy a compatible Ingress controller first to configure [SSL termination on Rancher.](#3-choose-your-ssl-configuration) - -For an example of how to deploy an ingress on EKS, refer to [this section.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/amazon-eks/#5-install-an-ingress) - -# Install the Rancher Helm Chart - -Rancher is installed using the [Helm](https://helm.sh/) package manager for Kubernetes. Helm charts provide templating syntax for Kubernetes YAML manifest documents. With Helm, we can create configurable deployments instead of just using static files. - -For systems without direct internet access, see [Air Gap: Kubernetes install]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/install-rancher/). - -To choose a Rancher version to install, refer to [Choosing a Rancher Version.]({{}}/rancher/v2.6/en/installation/resources/choosing-version) - -To choose a version of Helm to install Rancher with, refer to the [Helm version requirements]({{}}/rancher/v2.6/en/installation/resources/helm-version) - -> **Note:** The installation instructions assume you are using Helm 3. - -To set up Rancher, - -1. [Add the Helm chart repository](#1-add-the-helm-chart-repository) -2. [Create a namespace for Rancher](#2-create-a-namespace-for-rancher) -3. [Choose your SSL configuration](#3-choose-your-ssl-configuration) -4. [Install cert-manager](#4-install-cert-manager) (unless you are bringing your own certificates, or TLS will be terminated on a load balancer) -5. [Install Rancher with Helm and your chosen certificate option](#5-install-rancher-with-helm-and-your-chosen-certificate-option) -6. [Verify that the Rancher server is successfully deployed](#6-verify-that-the-rancher-server-is-successfully-deployed) -7. [Save your options](#7-save-your-options) - -### 1. Add the Helm Chart Repository - -Use `helm repo add` command to add the Helm chart repository that contains charts to install Rancher. For more information about the repository choices and which is best for your use case, see [Choosing a Version of Rancher]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#helm-chart-repositories). - -{{< release-channel >}} - -``` -helm repo add rancher- https://releases.rancher.com/server-charts/ -``` - -### 2. Create a Namespace for Rancher - -We'll need to define a Kubernetes namespace where the resources created by the Chart should be installed. This should always be `cattle-system`: - -``` -kubectl create namespace cattle-system -``` - -### 3. Choose your SSL Configuration - -The Rancher management server is designed to be secure by default and requires SSL/TLS configuration. - -> **Note:** If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination). - -There are three recommended options for the source of the certificate used for TLS termination at the Rancher server: - -- **Rancher-generated TLS certificate:** In this case, you will need to install `cert-manager` into the cluster. Rancher utilizes `cert-manager` to issue and maintain its certificates. Rancher will generate a CA certificate of its own, and sign a cert using that CA. `cert-manager` is then responsible for managing that certificate. -- **Let's Encrypt:** The Let's Encrypt option also uses `cert-manager`. However, in this case, cert-manager is combined with a special Issuer for Let's Encrypt that performs all actions (including request and validation) necessary for getting a Let's Encrypt issued cert. This configuration uses HTTP validation (`HTTP-01`), so the load balancer must have a public DNS record and be accessible from the internet. -- **Bring your own certificate:** This option allows you to bring your own public- or private-CA signed certificate. Rancher will use that certificate to secure websocket and HTTPS traffic. In this case, you must upload this certificate (and associated key) as PEM-encoded files with the name `tls.crt` and `tls.key`. If you are using a private CA, you must also upload that certificate. This is due to the fact that this private CA may not be trusted by your nodes. Rancher will take that CA certificate, and generate a checksum from it, which the various Rancher components will use to validate their connection to Rancher. - - -| Configuration | Helm Chart Option | Requires cert-manager | -| ------------------------------ | ----------------------- | ------------------------------------- | -| Rancher Generated Certificates (Default) | `ingress.tls.source=rancher` | [yes](#4-install-cert-manager) | -| Let’s Encrypt | `ingress.tls.source=letsEncrypt` | [yes](#4-install-cert-manager) | -| Certificates from Files | `ingress.tls.source=secret` | no | - -### 4. Install cert-manager - -**Note:** New in v2.6.4, cert-manager versions 1.6.2 and 1.7.1 are compatible. We recommend v1.7.x because v 1.6.x will reach end-of-life on March 30, 2022. - -> You should skip this step if you are bringing your own certificate files (option `ingress.tls.source=secret`), or if you use [TLS termination on an external load balancer]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination). - -This step is only required to use certificates issued by Rancher's generated CA (`ingress.tls.source=rancher`) or to request Let's Encrypt issued certificates (`ingress.tls.source=letsEncrypt`). - -
- Click to Expand - -> **Important:** Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.11.0, please see our [upgrade documentation]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/). - -These instructions are adapted from the [official cert-manager documentation](https://cert-manager.io/docs/installation/kubernetes/#installing-with-helm). - -``` -# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart: -kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml - -# Add the Jetstack Helm repository -helm repo add jetstack https://charts.jetstack.io - -# Update your local Helm chart repository cache -helm repo update - -# Install the cert-manager Helm chart -helm install cert-manager jetstack/cert-manager \ - --namespace cert-manager \ - --create-namespace \ - --version v1.7.1 -``` - -Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: - -``` -kubectl get pods --namespace cert-manager - -NAME READY STATUS RESTARTS AGE -cert-manager-5c6866597-zw7kh 1/1 Running 0 2m -cert-manager-cainjector-577f6d9fd7-tr77l 1/1 Running 0 2m -cert-manager-webhook-787858fcdb-nlzsq 1/1 Running 0 2m -``` - -
- -### 5. Install Rancher with Helm and Your Chosen Certificate Option - -The exact command to install Rancher differs depending on the certificate configuration. - -However, irrespective of the certificate configuration, the name of the Rancher installation in the `cattle-system` namespace should always be `rancher`. - -> **Tip for testing and development:** This final command to install Rancher requires a domain name that forwards traffic to Rancher. If you are using the Helm CLI to set up a proof-of-concept, you can use a fake domain name when passing the `hostname` option. An example of a fake domain name would be `.sslip.io`, which would expose Rancher on an IP where it is running. Production installs would require a real domain name. - - - - -The default is for Rancher to generate a CA and uses `cert-manager` to issue the certificate for access to the Rancher server interface. - -Because `rancher` is the default option for `ingress.tls.source`, we are not specifying `ingress.tls.source` when running the `helm install` command. - -- Set the `hostname` to the DNS name you pointed at your load balancer. -- Set the `bootstrapPassword` to something unique for the `admin` user. -- If you are installing an alpha version, Helm requires adding the `--devel` option to the command. -- To install a specific Rancher version, use the `--version` flag, example: `--version 2.3.6` - -``` -helm install rancher rancher-/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org \ - --set bootstrapPassword=admin -``` - -Wait for Rancher to be rolled out: - -``` -kubectl -n cattle-system rollout status deploy/rancher -Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available... -deployment "rancher" successfully rolled out -``` - - - - -This option uses `cert-manager` to automatically request and renew [Let's Encrypt](https://letsencrypt.org/) certificates. This is a free service that provides you with a valid certificate as Let's Encrypt is a trusted CA. - ->**Note:** You need to have port 80 open as the HTTP-01 challenge can only be done on port 80. - -In the following command, - -- `hostname` is set to the public DNS record, -- Set the `bootstrapPassword` to something unique for the `admin` user. -- `ingress.tls.source` is set to `letsEncrypt` -- `letsEncrypt.email` is set to the email address used for communication about your certificate (for example, expiry notices) -- Set `letsEncrypt.ingress.class` to whatever your ingress controller is, e.g., `traefik`, `nginx`, `haproxy`, etc. -- If you are installing an alpha version, Helm requires adding the `--devel` option to the command. - -``` -helm install rancher rancher-/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org \ - --set bootstrapPassword=admin \ - --set ingress.tls.source=letsEncrypt \ - --set letsEncrypt.email=me@example.org \ - --set letsEncrypt.ingress.class=nginx -``` - -Wait for Rancher to be rolled out: - -``` -kubectl -n cattle-system rollout status deploy/rancher -Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available... -deployment "rancher" successfully rolled out -``` - - - - -In this option, Kubernetes secrets are created from your own certificates for Rancher to use. - -When you run this command, the `hostname` option must match the `Common Name` or a `Subject Alternative Names` entry in the server certificate or the Ingress controller will fail to configure correctly. - -Although an entry in the `Subject Alternative Names` is technically required, having a matching `Common Name` maximizes compatibility with older browsers and applications. - -> If you want to check if your certificates are correct, see [How do I check Common Name and Subject Alternative Names in my server certificate?]({{}}/rancher/v2.6/en/faq/technical/#how-do-i-check-common-name-and-subject-alternative-names-in-my-server-certificate) - -- Set the `hostname`. -- Set the `bootstrapPassword` to something unique for the `admin` user. -- Set `ingress.tls.source` to `secret`. -- If you are installing an alpha version, Helm requires adding the `--devel` option to the command. - -``` -helm install rancher rancher-/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org \ - --set bootstrapPassword=admin \ - --set ingress.tls.source=secret -``` - -If you are using a Private CA signed certificate , add `--set privateCA=true` to the command: - -``` -helm install rancher rancher-/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org \ - --set bootstrapPassword=admin \ - --set ingress.tls.source=secret \ - --set privateCA=true -``` - -Now that Rancher is deployed, see [Adding TLS Secrets]({{}}/rancher/v2.6/en/installation/resources/tls-secrets/) to publish the certificate files so Rancher and the Ingress controller can use them. - - - - -The Rancher chart configuration has many options for customizing the installation to suit your specific environment. Here are some common advanced scenarios. - -- [HTTP Proxy]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#http-proxy) -- [Private container image Registry]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#private-registry-and-air-gap-installs) -- [TLS Termination on an External Load Balancer]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination) - -See the [Chart Options]({{}}/rancher/v2.6/en/installation/resources/chart-options/) for the full list of options. - - -### 6. Verify that the Rancher Server is Successfully Deployed - -After adding the secrets, check if Rancher was rolled out successfully: - -``` -kubectl -n cattle-system rollout status deploy/rancher -Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available... -deployment "rancher" successfully rolled out -``` - -If you see the following error: `error: deployment "rancher" exceeded its progress deadline`, you can check the status of the deployment by running the following command: - -``` -kubectl -n cattle-system get deploy rancher -NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE -rancher 3 3 3 3 3m -``` - -It should show the same count for `DESIRED` and `AVAILABLE`. - -### 7. Save Your Options - -Make sure you save the `--set` options you used. You will need to use the same options when you upgrade Rancher to new versions with Helm. - -### Finishing Up - -That's it. You should have a functional Rancher server. - -In a web browser, go to the DNS name that forwards traffic to your load balancer. Then you should be greeted by the colorful login page. - -Doesn't work? Take a look at the [Troubleshooting]({{}}/rancher/v2.6/en/installation/resources/troubleshooting/) Page diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/rollbacks/rollbacks.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/rollbacks/rollbacks.md deleted file mode 100644 index fd46576cf20..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/rollbacks/rollbacks.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Rollbacks -weight: 3 ---- - -- [Rolling Back to Rancher v2.5.0+](#rolling-back-to-rancher-v2-5-0) -- [Rolling Back to Rancher v2.2-v2.4+](#rolling-back-to-rancher-v2-2-v2-4) -- [Rolling Back to Rancher v2.0-v2.1](#rolling-back-to-rancher-v2-0-v2-1) - -# Rolling Back to Rancher v2.5.0+ - -To roll back to Rancher v2.5.0+, use the **Rancher Backups** application and restore Rancher from backup. - -Rancher has to be started with the lower/previous version after a rollback. - -A restore is performed by creating a Restore custom resource. - -> **Important** -> -> * Follow the instructions from this page for restoring rancher on the same cluster where it was backed up from. In order to migrate rancher to a new cluster, follow the steps to [migrate rancher.]({{}}/rancher/v2.6/en/backups/migrating-rancher) -> * While restoring Rancher on the same setup, the Rancher deployment is manually scaled down before the restore starts, then the operator will scale it back up once the restore completes. As a result, Rancher and its UI will be unavailable until the restore is complete. While the UI is unavailable, use the original cluster kubeconfig with the restore YAML file: `kubectl create -f restore.yaml`. - -### Scale the Rancher Deployment to 0 - -1. In the upper left corner, click **☰ > local**. -1. From the menu on the left, click **Workload**. -1. Under **Workload**, click on **Deployments**. -1. At the top, click on the dropdown to adjust the filter. Select **cattle-system** as the filter. -1. Find the row for the `rancher` deployment and click **⋮ > Edit Config**. -1. Change **Replicas** to 0. -1. Scroll to the bottom and click **Save**. - -### Create the Restore Custom Resource - -1. Click **☰ > Cluster Management**. -1. Go to the local cluster and click **Explore**. -1. In the left navigation bar, click **Rancher Backups > Restore**. - * **Note:** If the Rancher Backups app is not visible, you will need to install it from the Charts page in **Apps & Marketplace**. Refer [here]({{}}/rancher/v2.6/en/helm-charts/#charts) for more information. -1. Click **Create**. -1. Create the Restore with the form or with YAML. For help creating the Restore resource using the online form, refer to the [configuration reference]({{}}/rancher/v2.6/en/backups/configuration/restore-config) and to the [examples.]({{}}/rancher/v2.6/en/backups/examples) -1. To use the YAML editor, you can click **Create > Create from YAML.** Enter the Restore YAML. The following is an example Restore custom resource: - - ```yaml - apiVersion: resources.cattle.io/v1 - kind: Restore - metadata: - name: restore-migration - spec: - backupFilename: backup-b0450532-cee1-4aa1-a881-f5f48a007b1c-2020-09-15T07-27-09Z.tar.gz - encryptionConfigSecretName: encryptionconfig - storageLocation: - s3: - credentialSecretName: s3-creds - credentialSecretNamespace: default - bucketName: rancher-backups - folder: rancher - region: us-west-2 - endpoint: s3.us-west-2.amazonaws.com - ``` - For help configuring the Restore, refer to the [configuration reference]({{}}/rancher/v2.6/en/backups/configuration/restore-config) and to the [examples.]({{}}/rancher/v2.6/en/backups/examples) - -1. Click **Create**. - -**Result:** The backup file is created and updated to the target storage location. The resources are restored in this order: - -1. Custom Resource Definitions (CRDs) -2. Cluster-scoped resources -3. Namespaced resources - -To check how the restore is progressing, you can check the logs of the operator. Follow these steps to get the logs: - -```yaml -kubectl get pods -n cattle-resources-system -kubectl logs -n cattle-resources-system -f -``` - -### Roll back to a previous Rancher version - -Rancher can be rolled back using the Helm CLI. To roll back to the previous version: - -```yaml -helm rollback rancher -n cattle-system -``` - -If the previous revision is not the intended target, you can specify a revision to roll back to. To see the deployment history: - -```yaml -helm history rancher -n cattle-system -``` - -When the target revision is determined, perform the rollback. This example will roll back to revision `3`: - -```yaml -helm rollback rancher 3 -n cattle-system -``` - -# Rolling Back to Rancher v2.2-v2.4+ - -To roll back to Rancher before v2.5, follow the procedure detailed here: [Restoring Backups — Kubernetes installs]({{}}/rancher/v2.0-v2.4/en/backups/restore/rke-restore/) Restoring a snapshot of the Rancher server cluster will revert Rancher to the version and state at the time of the snapshot. - -For information on how to roll back Rancher installed with Docker, refer to [this page.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-rollbacks) - -> Managed clusters are authoritative for their state. This means restoring the rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken. - -# Rolling Back to Rancher v2.0-v2.1 - -Rolling back to Rancher v2.0-v2.1 is no longer supported. The instructions for rolling back to these versions are preserved [here]({{}}/rancher/v2.0-v2.4/en/backups/restore/rke-restore/v2.0-v2.1) and are intended to be used only in cases where upgrading to Rancher v2.2+ is not feasible. diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/air-gap-upgrade/air-gap-upgrade.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/air-gap-upgrade/air-gap-upgrade.md deleted file mode 100644 index 3b0ef16a876..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/air-gap-upgrade/air-gap-upgrade.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Rendering the Helm Template in an Air Gapped Environment -shortTitle: Air Gap Upgrade -weight: 1 ---- - -> These instructions assume you have already followed the instructions for a Kubernetes upgrade on [this page,]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/upgrades/) including the prerequisites, up until step 3. Upgrade Rancher. - -### Rancher Helm Template Options - -Render the Rancher template using the same chosen options that were used when installing Rancher. Use the reference table below to replace each placeholder. Rancher needs to be configured to use the private registry in order to provision any Rancher launched Kubernetes clusters or Rancher tools. - -Based on the choice you made during installation, complete one of the procedures below. - -Placeholder | Description -------------|------------- -`` | The version number of the output tarball. -`` | The DNS name you pointed at your load balancer. -`` | The DNS name for your private registry. -`` | Cert-manager version running on k8s cluster. - - -### Option A: Default Self-signed Certificate - -``` -helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set certmanager.version= \ - --set rancherImage=/rancher/rancher \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts -``` - -### Option B: Certificates from Files using Kubernetes Secrets - -```plain -helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set rancherImage=/rancher/rancher \ - --set ingress.tls.source=secret \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts -``` - -If you are using a Private CA signed cert, add `--set privateCA=true` following `--set ingress.tls.source=secret`: - -```plain -helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set rancherImage=/rancher/rancher \ - --set ingress.tls.source=secret \ - --set privateCA=true \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts -``` - -### Apply the Rendered Templates - -Copy the rendered manifest directories to a system with access to the Rancher server cluster and apply the rendered templates. - -Use `kubectl` to apply the rendered manifests. - -```plain -kubectl -n cattle-system apply -R -f ./rancher -``` - -# Verify the Upgrade - -Log into Rancher to confirm that the upgrade succeeded. - ->**Having network issues following upgrade?** -> -> See [Restoring Cluster Networking]({{}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration). - -# Known Upgrade Issues - -A list of known issues for each Rancher version can be found in the release notes on [GitHub](https://github.com/rancher/rancher/releases) and on the [Rancher forums.](https://forums.rancher.com/c/announcements/12) diff --git a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/upgrades.md b/versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/upgrades.md deleted file mode 100644 index cfe481e2b94..00000000000 --- a/versioned_docs/version-2.6/installation/install-rancher-on-k8s/upgrades/upgrades.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -title: Upgrades -weight: 2 ---- -The following instructions will guide you through upgrading a Rancher server that was installed on a Kubernetes cluster with Helm. These steps also apply to air gap installs with Helm. - -For the instructions to upgrade Rancher installed with Docker, refer to [this page.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-upgrades) - -To upgrade the components in your Kubernetes cluster, or the definition of the [Kubernetes services]({{}}/rke/latest/en/config-options/services/) or [add-ons]({{}}/rke/latest/en/config-options/add-ons/), refer to the [upgrade documentation for RKE]({{}}/rke/latest/en/upgrades/), the Rancher Kubernetes Engine. - -- [Prerequisites](#prerequisites) -- [Upgrade Outline](#upgrade-outline) -- [Known Upgrade Issues](#known-upgrade-issues) -- [RKE Add-on Installs](#rke-add-on-installs) - -# Prerequisites - -### Access to kubeconfig - -Helm should be run from the same location as your kubeconfig file, or the same location where you run your kubectl commands from. - -If you installed Kubernetes with RKE, the config will have been created in the directory you ran `rke up` in. - -The kubeconfig can also be manually targeted for the intended cluster with the `--kubeconfig` tag (see: https://helm.sh/docs/helm/helm/) - -### Review Known Issues - -Review the list of known issues for each Rancher version, which can be found in the release notes on [GitHub](https://github.com/rancher/rancher/releases) and on the [Rancher forums.](https://forums.rancher.com/c/announcements/12) - -Note that upgrades _to_ or _from_ any chart in the [rancher-alpha repository]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#helm-chart-repositories/) aren't supported. - -### Helm Version - -The upgrade instructions assume you are using Helm 3. - -For migration of installs started with Helm 2, refer to the official [Helm 2 to 3 migration docs.](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) The [Helm 2 upgrade page here]({{}}/rancher/v2.0-v2.4/en/installation/upgrades-rollbacks/upgrades/ha/helm2)provides a copy of the older upgrade instructions that used Helm 2, and it is intended to be used if upgrading to Helm 3 is not feasible. - -### For air gap installs: Populate private registry - -For [air gap installs only,]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) collect and populate images for the new Rancher server version. Follow the guide to [populate your private registry]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry/) with the images for the Rancher version that you want to upgrade to. - -### For upgrades from a Rancher server with a hidden local cluster - -If you are upgrading to Rancher v2.5 from a Rancher server that was started with the Helm chart option `--add-local=false`, you will need to drop that flag when upgrading. Otherwise, the Rancher server will not start. The `restricted-admin` role can be used to continue restricting access to the local cluster. For more information, see [this section.]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/#upgrading-from-rancher-with-a-hidden-local-cluster) - -### For upgrades with cert-manager older than 0.8.0 - -[Let's Encrypt will be blocking cert-manager instances older than 0.8.0 starting November 1st 2019.](https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753) Upgrade cert-manager to the latest version by following [these instructions.]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager) - -# Upgrade Outline - -Follow the steps to upgrade Rancher server: - -- [1. Back up your Kubernetes cluster that is running Rancher server](#1-back-up-your-kubernetes-cluster-that-is-running-rancher-server) -- [2. Update the Helm chart repository](#2-update-the-helm-chart-repository) -- [3. Upgrade Rancher](#3-upgrade-rancher) -- [4. Verify the Upgrade](#4-verify-the-upgrade) - -# 1. Back up Your Kubernetes Cluster that is Running Rancher Server - -Use the [backup application]({{}}/rancher/v2.6/en/backups/back-up-rancher) to back up Rancher. - -You'll use the backup as a restore point if something goes wrong during upgrade. - -# 2. Update the Helm chart repository - -1. Update your local helm repo cache. - - ``` - helm repo update - ``` - -1. Get the repository name that you used to install Rancher. - - For information about the repos and their differences, see [Helm Chart Repositories]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#helm-chart-repositories). - - {{< release-channel >}} - - ``` - helm repo list - - NAME URL - stable https://charts.helm.sh/stable - rancher- https://releases.rancher.com/server-charts/ - ``` - - > **Note:** If you want to switch to a different Helm chart repository, please follow the [steps on how to switch repositories]({{}}/rancher/v2.6/en/installation/resources/choosing-version/#switching-to-a-different-helm-chart-repository). If you switch repositories, make sure to list the repositories again before continuing onto Step 3 to ensure you have the correct one added. - - -1. Fetch the latest chart to install Rancher from the Helm chart repository. - - This command will pull down the latest charts and save it in the current directory as a `.tgz` file. - - ```plain - helm fetch rancher-/rancher - ``` - You can fetch the chart for the specific version you are upgrading to by adding in the `--version=` tag. For example: - - ```plain - helm fetch rancher-/rancher --version=v2.4.11 - ``` - -# 3. Upgrade Rancher - -This section describes how to upgrade normal (Internet-connected) or air gap installations of Rancher with Helm. - -> **Air Gap Instructions:** If you are installing Rancher in an air gapped environment, skip the rest of this page and render the Helm template by following the instructions on [this page.](./air-gap-upgrade) - - -Get the values, which were passed with `--set`, from the current Rancher Helm chart that is installed. - -``` -helm get values rancher -n cattle-system - -hostname: rancher.my.org -``` - -> **Note:** There will be more values that are listed with this command. This is just an example of one of the values. - -If you are also upgrading cert-manager to the latest version from a version older than 0.11.0, follow [Option B: Reinstalling Rancher and cert-manager.](#option-b-reinstalling-rancher-and-cert-manager) - -Otherwise, follow [Option A: Upgrading Rancher.](#option-a-upgrading-rancher) - -### Option A: Upgrading Rancher - -Upgrade Rancher to the latest version with all your settings. - -Take all the values from the previous step and append them to the command using `--set key=value`: - -``` -helm upgrade rancher rancher-/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org -``` - -> **Note:** The above is an example, there may be more values from the previous step that need to be appended. - -Alternatively, it's possible to export the current values to a file and reference that file during upgrade. For example, to only change the Rancher version: - -``` -helm get values rancher -n cattle-system -o yaml > values.yaml - -helm upgrade rancher rancher-/rancher \ - --namespace cattle-system \ - -f values.yaml \ - --version=2.4.5 -``` - -### Option B: Reinstalling Rancher and cert-manager - -If you are currently running the cert-manager whose version is 1.5 or below, and want to upgrade both Rancher and cert-manager to a new version (1.6+ in the case of cert-manager), then you need to re-install both Rancher and cert-manager due to the API change in cert-manager 1.6. This will also be necessary if you are upgrading from a version of cert manager below 0.11 to a version of cert-manager above 0.11. - ->**Important:** -> ->- New in v2.6.4, cert-manager versions 1.6.2 and 1.7.1 are compatible. We recommend v1.7.x because v 1.6.x will reach end-of-life on March 30, 2022. -> ->- Note that if you are below version 1.5 and want to go to 1.7, you should first upgrade to 1.6 as an intermediate step. Follow the cert-manager docs [here](https://cert-manager.io/docs/installation/upgrading/upgrading-1.5-1.6/) to do a 1.5 to 1.6 upgrade, and [here](https://cert-manager.io/docs/installation/upgrading/upgrading-1.6-1.7/) to then do a 1.6 to 1.7 upgrade. For more details on upgrading cert-manager, refer to our [documentation]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager). - -1. Uninstall Rancher - - ``` - helm delete rancher -n cattle-system - ``` - -2. Uninstall and reinstall `cert-manager` according to the instructions on the [Upgrading Cert-Manager]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager) page. - -3. Reinstall Rancher to the latest version with all your settings. Take all the values from the step 1 and append them to the command using `--set key=value`. Note: There will be many more options from the step 1 that need to be appended. - - ``` - helm install rancher rancher-/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org - ``` - -# 4. Verify the Upgrade - -Log into Rancher to confirm that the upgrade succeeded. - ->**Having network issues following upgrade?** -> -> See [Restoring Cluster Networking]({{}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration). - -# Known Upgrade Issues - -A list of known issues for each Rancher version can be found in the release notes on [GitHub](https://github.com/rancher/rancher/releases) and on the [Rancher forums.](https://forums.rancher.com/c/announcements/12) diff --git a/versioned_docs/version-2.6/installation/installation.md b/versioned_docs/version-2.6/installation/installation.md deleted file mode 100644 index 9b7866d3bc9..00000000000 --- a/versioned_docs/version-2.6/installation/installation.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Installing/Upgrading Rancher -description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation -weight: 3 ---- - -This section provides an overview of the architecture options of installing Rancher, describing advantages of each option. - -# Terminology - -In this section, - -- **The Rancher server** manages and provisions Kubernetes clusters. You can interact with downstream Kubernetes clusters through the Rancher server's user interface. The Rancher management server can be installed on any Kubernetes cluster, including hosted clusters, such as Amazon EKS clusters. -- **RKE (Rancher Kubernetes Engine)** is a certified Kubernetes distribution and CLI/library which creates and manages a Kubernetes cluster. -- **K3s (Lightweight Kubernetes)** is also a fully compliant Kubernetes distribution. It is newer than RKE, easier to use, and more lightweight, with a binary size of less than 100 MB. -- **RKE2** is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector. - -Note the `restrictedAdmin` Helm chart option available for **the Rancher Server**. When this option is set to true, the initial Rancher user has restricted access to the local Kubernetes cluster to prevent privilege escalation. For more information, see the section about the [restricted-admin role.]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/#restricted-admin) - -# Overview of Installation Options - -Rancher can be installed on these main architectures: - -### High-availability Kubernetes Install with the Helm CLI - -We recommend using Helm, a Kubernetes package manager, to install Rancher on multiple nodes on a dedicated Kubernetes cluster. For RKE clusters, three nodes are required to achieve a high-availability cluster. For K3s clusters, only two nodes are required. - -### Automated Quickstart to Deploy Rancher on Amazon EKS - -Rancher and Amazon Web Services collaborated on a quick start guide for deploying Rancher on an EKS Kubernetes cluster following AWS best practices. The deployment guide is [here.](https://aws-quickstart.github.io/quickstart-eks-rancher/) - -### Single-node Kubernetes Install - -Rancher can be installed on a single-node Kubernetes cluster. In this case, the Rancher server doesn't have high availability, which is important for running Rancher in production. - -However, this option is useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path. In the future, you can add nodes to the cluster to get a high-availability Rancher server. - -### Docker Install - -For test and demonstration purposes, Rancher can be installed with Docker on a single node. A local Kubernetes cluster is installed in the single Docker container, and Rancher is installed on the local cluster. - -The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster.]({{}}/rancher/v2.6/en/backups/migrating-rancher) - -### Other Options - -There are also separate instructions for installing Rancher in an air gap environment or behind an HTTP proxy: - -| Level of Internet Access | Kubernetes Installation - Strongly Recommended | Docker Installation | -| ---------------------------------- | ------------------------------ | ---------- | -| With direct access to the Internet | [Docs]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) | [Docs]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker) | -| Behind an HTTP proxy | [Docs]({{}}/rancher/v2.6/en/installation/other-installation-methods/behind-proxy/) | These [docs,]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker) plus this [configuration]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/proxy/) | -| In an air gap environment | [Docs]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) | [Docs]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) | - -We recommend installing Rancher on a Kubernetes cluster, because in a multi-node cluster, the Rancher management server becomes highly available. This high-availability configuration helps maintain consistent access to the downstream Kubernetes clusters that Rancher will manage. - -For that reason, we recommend that for a production-grade architecture, you should set up a high-availability Kubernetes cluster, then install Rancher on it. After Rancher is installed, you can use Rancher to deploy and manage Kubernetes clusters. - -For testing or demonstration purposes, you can install Rancher in single Docker container. In this Docker install, you can use Rancher to set up Kubernetes clusters out-of-the-box. The Docker install allows you to explore the Rancher server functionality, but it is intended to be used for development and testing purposes only. - -Our [instructions for installing Rancher on Kubernetes]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s) describe how to first use K3s or RKE to create and manage a Kubernetes cluster, then install Rancher onto that cluster. - -When the nodes in your Kubernetes cluster are running and fulfill the [node requirements,]({{}}/rancher/v2.6/en/installation/requirements) you will use Helm to deploy Rancher onto Kubernetes. Helm uses Rancher's Helm chart to install a replica of Rancher on each node in the Kubernetes cluster. We recommend using a load balancer to direct traffic to each replica of Rancher in the cluster. - -For a longer discussion of Rancher architecture, refer to the [architecture overview,]({{}}/rancher/v2.6/en/overview/architecture) [recommendations for production-grade architecture,]({{}}/rancher/v2.6/en/overview/architecture-recommendations) or our [best practices guide.]({{}}/rancher/v2.6/en/best-practices/rancher-server/deployment-types) - -# Prerequisites -Before installing Rancher, make sure that your nodes fulfill all of the [installation requirements.]({{}}/rancher/v2.6/en/installation/requirements/) - -# Architecture Tip - -For the best performance and greater security, we recommend a separate, dedicated Kubernetes cluster for the Rancher management server. Running user workloads on this cluster is not advised. After deploying Rancher, you can [create or import clusters]({{}}/rancher/v2.6/en/cluster-provisioning/) for running your workloads. - -For more architecture recommendations, refer to [this page.]({{}}/rancher/v2.6/en/overview/architecture-recommendations) - -### More Options for Installations on a Kubernetes Cluster - -Refer to the [Helm chart options]({{}}/rancher/v2.6/en/installation/resources/chart-options/) for details on installing Rancher on a Kubernetes cluster with other configurations, including: - -- With [API auditing to record all transactions]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#api-audit-log) -- With [TLS termination on a load balancer]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination) -- With a [custom Ingress]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#customizing-your-ingress) - -In the Rancher installation instructions, we recommend using K3s or RKE to set up a Kubernetes cluster before installing Rancher on the cluster. Both K3s and RKE have many configuration options for customizing the Kubernetes cluster to suit your specific environment. For the full list of their capabilities, refer to their documentation: - -- [RKE configuration options]({{}}/rke/latest/en/config-options/) -- [K3s configuration options]({{}}/k3s/latest/en/installation/install-options/) - -### More Options for Installations with Docker - -Refer to the [docs about options for Docker installs]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker) for details about other configurations including: - -- With [API auditing to record all transactions]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#api-audit-log) -- With an [external load balancer]({{}}/rancher/v2.6/en/installation/resources/advanced/single-node-install-external-lb/) -- With a [persistent data store]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#persistent-data) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/air-gap.md b/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/air-gap.md deleted file mode 100644 index 51442964790..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/air-gap.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Air Gapped Helm CLI Install -weight: 1 ---- - -This section is about using the Helm CLI to install the Rancher server in an air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. - -The installation steps differ depending on whether Rancher is installed on an RKE Kubernetes cluster, a K3s Kubernetes cluster, or a single Docker container. - -For more information on each installation option, refer to [this page.]({{}}/rancher/v2.6/en/installation/) - -Throughout the installation instructions, there will be _tabs_ for each installation option. - -> **Important:** If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker Installation to a Kubernetes Installation. - -# Installation Outline - -1. [Set up infrastructure and private registry]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/prepare-nodes/) -2. [Collect and publish images to your private registry]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry/) -3. [Set up a Kubernetes cluster (Skip this step for Docker installations)]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/launch-kubernetes/) -4. [Install Rancher]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/install-rancher/) - -# Upgrades - -To upgrade Rancher with Helm CLI in an air gap environment, follow [this procedure.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/upgrades/) - -### [Next: Prepare your Node(s)]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/prepare-nodes/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/docker-install-commands/docker-install-commands.md b/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/docker-install-commands/docker-install-commands.md deleted file mode 100644 index 8c065fb3db3..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/docker-install-commands/docker-install-commands.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -title: Docker Install Commands -weight: 1 ---- - -The Docker installation is for Rancher users who want to test out Rancher. - -Instead of running on a Kubernetes cluster, you install the Rancher server component on a single node using a `docker run` command. Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server. - -The backup application can be used to migrate the Rancher server from a Docker install to a Kubernetes install using [these steps.]({{}}/rancher/v2.6/en/backups/migrating-rancher) - -For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster. - -| Environment Variable Key | Environment Variable Value | Description | -| -------------------------------- | -------------------------------- | ---- | -| `CATTLE_SYSTEM_DEFAULT_REGISTRY` | `` | Configure Rancher server to always pull from your private registry when provisioning clusters. | -| `CATTLE_SYSTEM_CATALOG` | `bundled` | Configure Rancher server to use the packaged copy of Helm system charts. The [system charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. These [Helm charts](https://github.com/rancher/system-charts) are located in GitHub, but since you are in an air gapped environment, using the charts that are bundled within Rancher is much easier than setting up a Git mirror. | - -> **Do you want to..**. -> -> - Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{}}/rancher/v2.6/en/installation/resources/custom-ca-root-certificate/). -> - Record all transactions with the Rancher API? See [API Auditing]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#api-audit-log). - -Choose from the following options: - -### Option A: Default Self-Signed Certificate - -
- Click to expand - -If you are installing Rancher in a development or testing environment where identity verification isn't a concern, install Rancher using the self-signed certificate that it generates. This installation option omits the hassle of generating a certificate yourself. - -Log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. - -| Placeholder | Description | -| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `` | Your private registry URL and port. | -| `` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to install. | - -Privileged access is [required.](#privileged-access-for-rancher) - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ # Set a default private registry to be used in Rancher - -e CATTLE_SYSTEM_CATALOG=bundled \ # Use the packaged Rancher system charts - --privileged \ - /rancher/rancher: -``` - -
- -### Option B: Bring Your Own Certificate: Self-Signed - -
- Click to expand - -In development or testing environments where your team will access your Rancher server, create a self-signed certificate for use with your install so that your team can verify they're connecting to your instance of Rancher. - -> **Prerequisites:** -> From a computer with an internet connection, create a self-signed certificate using [OpenSSL](https://www.openssl.org/) or another method of your choice. -> -> - The certificate files must be in PEM format. -> - In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -After creating your certificate, log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. Use the `-v` flag and provide the path to your certificates to mount them in your container. - -| Placeholder | Description | -| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `` | The path to the directory containing your certificate files. | -| `` | The path to your full certificate chain. | -| `` | The path to the private key for your certificate. | -| `` | The path to the certificate authority's certificate. | -| `` | Your private registry URL and port. | -| `` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to install. | - -Privileged access is [required.](#privileged-access-for-rancher) - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - -v //:/etc/rancher/ssl/cacerts.pem \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ # Set a default private registry to be used in Rancher - -e CATTLE_SYSTEM_CATALOG=bundled \ # Use the packaged Rancher system charts - --privileged \ - /rancher/rancher: -``` - -
- -### Option C: Bring Your Own Certificate: Signed by Recognized CA - -
- Click to expand - -In development or testing environments where you're exposing an app publicly, use a certificate signed by a recognized CA so that your user base doesn't encounter security warnings. - -> **Prerequisite:** The certificate files must be in PEM format. - -After obtaining your certificate, log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. Because your certificate is signed by a recognized CA, mounting an additional CA certificate file is unnecessary. - -| Placeholder | Description | -| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `` | The path to the directory containing your certificate files. | -| `` | The path to your full certificate chain. | -| `` | The path to the private key for your certificate. | -| `` | Your private registry URL and port. | -| `` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to install. | - -> **Note:** Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher. - -Privileged access is [required.](#privileged-access-for-rancher) - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --no-cacerts \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ # Set a default private registry to be used in Rancher - -e CATTLE_SYSTEM_CATALOG=bundled \ # Use the packaged Rancher system charts - --privileged - /rancher/rancher: -``` - -
- - - -> **Note:** If you don't intend to send telemetry data, opt out [telemetry]({{}}/rancher/v2.6/en/faq/telemetry/) during the initial login. - diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/install-rancher.md b/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/install-rancher.md deleted file mode 100644 index 6ee7535d612..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/install-rancher/install-rancher.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -title: 4. Install Rancher -weight: 400 ---- - -This section is about how to deploy Rancher for your air gapped environment in a high-availability Kubernetes installation. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. - -### Privileged Access for Rancher - -When the Rancher server is deployed in the Docker container, a local Kubernetes cluster is installed within the container for Rancher to use. Because many features of Rancher run as deployments, and privileged mode is required to run containers within containers, you will need to install Rancher with the `--privileged` option. - -# Docker Instructions - -If you want to continue the air gapped installation using Docker commands, skip the rest of this page and follow the instructions on [this page.](./docker-install-commands) - -# Kubernetes Instructions - -Rancher recommends installing Rancher on a Kubernetes cluster. A highly available Kubernetes install is comprised of three nodes running the Rancher server components on a Kubernetes cluster. The persistence layer (etcd) is also replicated on these three nodes, providing redundancy and data duplication in case one of the nodes fails. - -This section describes installing Rancher: - -- [1. Add the Helm Chart Repository](#1-add-the-helm-chart-repository) -- [2. Choose your SSL Configuration](#2-choose-your-ssl-configuration) -- [3. Render the Rancher Helm Template](#3-render-the-rancher-helm-template) -- [4. Install Rancher](#4-install-rancher) - -# 1. Add the Helm Chart Repository - -From a system that has access to the internet, fetch the latest Helm chart and copy the resulting manifests to a system that has access to the Rancher server cluster. - -1. If you haven't already, install `helm` locally on a workstation that has internet access. Note: Refer to the [Helm version requirements]({{}}/rancher/v2.6/en/installation/resources/helm-version) to choose a version of Helm to install Rancher. - -2. Use `helm repo add` command to add the Helm chart repository that contains charts to install Rancher. For more information about the repository choices and which is best for your use case, see [Choosing a Version of Rancher]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#helm-chart-repositories). - {{< release-channel >}} - ``` - helm repo add rancher- https://releases.rancher.com/server-charts/ - ``` - -3. Fetch the latest Rancher chart. This will pull down the chart and save it in the current directory as a `.tgz` file. - ```plain - helm fetch rancher-/rancher - ``` - - If you require a specific version of Rancher, you can fetch this with the Helm `--version` parameter like in the following example: - ```plain - helm fetch rancher-stable/rancher --version=v2.4.8 - ``` - -# 2. Choose your SSL Configuration - -Rancher Server is designed to be secure by default and requires SSL/TLS configuration. - -When Rancher is installed on an air gapped Kubernetes cluster, there are two recommended options for the source of the certificate. - -> **Note:** If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination). - -| Configuration | Chart option | Description | Requires cert-manager | -| ------------------------------------------ | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | -| Rancher Generated Self-Signed Certificates | `ingress.tls.source=rancher` | Use certificates issued by Rancher's generated CA (self signed)
This is the **default** and does not need to be added when rendering the Helm template. | yes | -| Certificates from Files | `ingress.tls.source=secret` | Use your own certificate files by creating Kubernetes Secret(s).
This option must be passed when rendering the Rancher Helm template. | no | - -# Helm Chart Options for Air Gap Installations - -When setting up the Rancher Helm template, there are several options in the Helm chart that are designed specifically for air gap installations. - -| Chart Option | Chart Value | Description | -| ----------------------- | -------------------------------- | ---- | -| `certmanager.version` | `` | Configure proper Rancher TLS issuer depending of running cert-manager version. | -| `systemDefaultRegistry` | `` | Configure Rancher server to always pull from your private registry when provisioning clusters. | -| `useBundledSystemChart` | `true` | Configure Rancher server to use the packaged copy of Helm system charts. The [system charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. These [Helm charts](https://github.com/rancher/system-charts) are located in GitHub, but since you are in an air gapped environment, using the charts that are bundled within Rancher is much easier than setting up a Git mirror. | - -# 3. Render the Rancher Helm Template - -Based on the choice your made in [2. Choose your SSL Configuration](#2-choose-your-ssl-configuration), complete one of the procedures below. - -# Option A: Default Self-Signed Certificate - - -By default, Rancher generates a CA and uses cert-manager to issue the certificate for access to the Rancher server interface. - -> **Note:** -> Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.11.0, please see our [upgrade cert-manager documentation]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/). - -### 1. Add the cert-manager repo - -From a system connected to the internet, add the cert-manager repo to Helm: - -```plain -helm repo add jetstack https://charts.jetstack.io -helm repo update -``` - -### 2. Fetch the cert-manager chart - -Fetch the latest cert-manager chart available from the [Helm chart repository](https://hub.helm.sh/charts/jetstack/cert-manager). - -**Note:** New in v2.6.4, cert-manager versions 1.6.2 and 1.7.1 are compatible. We recommend v1.7.x because v 1.6.x will reach end-of-life on March 30, 2022. - -```plain -helm fetch jetstack/cert-manager --version v1.7.1 -``` - -### 3. Render the cert-manager template - -Render the cert-manager template with the options you would like to use to install the chart. Remember to set the `image.repository` option to pull the image from your private registry. This will create a `cert-manager` directory with the Kubernetes manifest files. - -```plain -helm template cert-manager ./cert-manager-v1.7.1.tgz --output-dir . \ - --namespace cert-manager \ - --set image.repository=/quay.io/jetstack/cert-manager-controller \ - --set webhook.image.repository=/quay.io/jetstack/cert-manager-webhook \ - --set cainjector.image.repository=/quay.io/jetstack/cert-manager-cainjector \ - --set startupapicheck.image.repository=/quay.io/jetstack/cert-manager-ctl -``` - -### 4. Download the cert-manager CRD - -Download the required CRD file for cert-manager: - ```plain - curl -L -o cert-manager/cert-manager-crd.yaml https://github.com/jetstack/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml - ``` - -### 5. Render the Rancher template - -Render the Rancher template, declaring your chosen options. Use the reference table below to replace each placeholder. Rancher needs to be configured to use the private registry in order to provision any Rancher launched Kubernetes clusters or Rancher tools. - - -Placeholder | Description -------------|------------- -`` | The version number of the output tarball. -`` | The DNS name you pointed at your load balancer. -`` | The DNS name for your private registry. -`` | Cert-manager version running on k8s cluster. - -```plain -helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set certmanager.version= \ - --set rancherImage=/rancher/rancher \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts -``` - -**Optional**: To install a specific Rancher version, set the `rancherImageTag` value, example: `--set rancherImageTag=v2.5.8` - -# Option B: Certificates From Files using Kubernetes Secrets - - -### 1. Create secrets - -Create Kubernetes secrets from your own certificates for Rancher to use. The common name for the cert will need to match the `hostname` option in the command below, or the ingress controller will fail to provision the site for Rancher. - -### 2. Render the Rancher template - -Render the Rancher template, declaring your chosen options. Use the reference table below to replace each placeholder. Rancher needs to be configured to use the private registry in order to provision any Rancher launched Kubernetes clusters or Rancher tools. - -| Placeholder | Description | -| -------------------------------- | ----------------------------------------------- | -| `` | The version number of the output tarball. | -| `` | The DNS name you pointed at your load balancer. | -| `` | The DNS name for your private registry. | - -```plain - helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set rancherImage=/rancher/rancher \ - --set ingress.tls.source=secret \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts -``` - -If you are using a Private CA signed cert, add `--set privateCA=true` following `--set ingress.tls.source=secret`: - -```plain - helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set rancherImage=/rancher/rancher \ - --set ingress.tls.source=secret \ - --set privateCA=true \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts -``` - -**Optional**: To install a specific Rancher version, set the `rancherImageTag` value, example: `--set rancherImageTag=v2.3.6` - -Then refer to [Adding TLS Secrets]({{}}/rancher/v2.6/en/installation/resources/tls-secrets/) to publish the certificate files so Rancher and the ingress controller can use them. - -# 4. Install Rancher - -Copy the rendered manifest directories to a system that has access to the Rancher server cluster to complete installation. - -Use `kubectl` to create namespaces and apply the rendered manifests. - -If you choose to use self-signed certificates in [B. Choose your SSL Configuration](#b-choose-your-ssl-configuration), install cert-manager. - -### For Self-Signed Certificate Installs, Install Cert-manager - -
- Click to expand - -If you are using self-signed certificates, install cert-manager: - -1. Create the namespace for cert-manager. -```plain -kubectl create namespace cert-manager -``` - -1. Create the cert-manager CustomResourceDefinitions (CRDs). -```plain -kubectl apply -f cert-manager/cert-manager-crd.yaml -``` - - > **Note:** - > If you are running Kubernetes v1.15 or below, you will need to add the `--validate=false` flag to your `kubectl apply` command above, or else you will receive a validation error relating to the `x-kubernetes-preserve-unknown-fields` field in cert-manager’s CustomResourceDefinition resources. This is a benign error and occurs due to the way kubectl performs resource validation. - -1. Launch cert-manager. -```plain -kubectl apply -R -f ./cert-manager -``` - -
- -### Install Rancher with kubectl - -```plain -kubectl create namespace cattle-system -kubectl -n cattle-system apply -R -f ./rancher -``` -The installation is complete. - -> **Note:** If you don't intend to send telemetry data, opt out [telemetry]({{}}/rancher/v2.6/en/faq/telemetry/) during the initial login. Leaving this active in an air-gapped environment can cause issues if the sockets cannot be opened successfully. - -# Additional Resources - -These resources could be helpful when installing Rancher: - -- [Rancher Helm chart options]({{}}/rancher/v2.6/en/installation/resources/chart-options/) -- [Adding TLS secrets]({{}}/rancher/v2.6/en/installation/resources/tls-secrets/) -- [Troubleshooting Rancher Kubernetes Installations]({{}}/rancher/v2.6/en/installation/resources/troubleshooting/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md b/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md deleted file mode 100644 index 02959acaaad..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -title: '3. Install Kubernetes (Skip for Docker Installs)' -weight: 300 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -> Skip this section if you are installing Rancher on a single node with Docker. - -This section describes how to install a Kubernetes cluster according to our [best practices for the Rancher server environment.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#environment-for-kubernetes-installations) This cluster should be dedicated to run only the Rancher server. - -Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes providers. - -The steps to set up an air-gapped Kubernetes cluster on RKE or K3s are shown below. - - - - -In this guide, we are assuming you have created your nodes in your air gapped environment and have a secure Docker private registry on your bastion server. - -### Installation Outline - -1. [Prepare Images Directory](#1-prepare-images-directory) -2. [Create Registry YAML](#2-create-registry-yaml) -3. [Install K3s](#3-install-k3s) -4. [Save and Start Using the kubeconfig File](#4-save-and-start-using-the-kubeconfig-file) - -### 1. Prepare Images Directory -Obtain the images tar file for your architecture from the [releases](https://github.com/rancher/k3s/releases) page for the version of K3s you will be running. - -Place the tar file in the `images` directory before starting K3s on each node, for example: - -```sh -sudo mkdir -p /var/lib/rancher/k3s/agent/images/ -sudo cp ./k3s-airgap-images-$ARCH.tar /var/lib/rancher/k3s/agent/images/ -``` - -### 2. Create Registry YAML -Create the registries.yaml file at `/etc/rancher/k3s/registries.yaml`. This will tell K3s the necessary details to connect to your private registry. - -The registries.yaml file should look like this before plugging in the necessary information: - -``` ---- -mirrors: - customreg: - endpoint: - - "https://ip-to-server:5000" -configs: - customreg: - auth: - username: xxxxxx # this is the registry username - password: xxxxxx # this is the registry password - tls: - cert_file: - key_file: - ca_file: -``` - -Note, at this time only secure registries are supported with K3s (SSL with custom CA). - -For more information on private registries configuration file for K3s, refer to the [K3s documentation.]({{}}/k3s/latest/en/installation/private-registry/) - -### 3. Install K3s - -Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) - -To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script. - -Obtain the K3s binary from the [releases](https://github.com/rancher/k3s/releases) page, matching the same version used to get the airgap images tar. -Also obtain the K3s install script at https://get.k3s.io - -Place the binary in `/usr/local/bin` on each node. -Place the install script anywhere on each node, and name it `install.sh`. - -Install K3s on each server: - -``` -INSTALL_K3S_SKIP_DOWNLOAD=true ./install.sh -``` - -Install K3s on each agent: - -``` -INSTALL_K3S_SKIP_DOWNLOAD=true K3S_URL=https://myserver:6443 K3S_TOKEN=mynodetoken ./install.sh -``` - -Note, take care to ensure you replace `myserver` with the IP or valid DNS of the server and replace `mynodetoken` with the node-token from the server. -The node-token is on the server at `/var/lib/rancher/k3s/server/node-token` - ->**Note:** K3s additionally provides a `--resolv-conf` flag for kubelets, which may help with configuring DNS in air-gap networks. - -### 4. Save and Start Using the kubeconfig File - -When you installed K3s on each Rancher server node, a `kubeconfig` file was created on the node at `/etc/rancher/k3s/k3s.yaml`. This file contains credentials for full access to the cluster, and you should save this file in a secure location. - -To use this `kubeconfig` file, - -1. Install [kubectl,](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) a Kubernetes command-line tool. -2. Copy the file at `/etc/rancher/k3s/k3s.yaml` and save it to the directory `~/.kube/config` on your local machine. -3. In the kubeconfig file, the `server` directive is defined as localhost. Configure the server as the DNS of your load balancer, referring to port 6443. (The Kubernetes API server will be reached at port 6443, while the Rancher server will be reached at ports 80 and 443.) Here is an example `k3s.yaml`: - -``` -apiVersion: v1 -clusters: -- cluster: - certificate-authority-data: [CERTIFICATE-DATA] - server: [LOAD-BALANCER-DNS]:6443 # Edit this line - name: default -contexts: -- context: - cluster: default - user: default - name: default -current-context: default -kind: Config -preferences: {} -users: -- name: default - user: - password: [PASSWORD] - username: admin -``` - -**Result:** You can now use `kubectl` to manage your K3s cluster. If you have more than one kubeconfig file, you can specify which one you want to use by passing in the path to the file when using `kubectl`: - -``` -kubectl --kubeconfig ~/.kube/config/k3s.yaml get pods --all-namespaces -``` - -For more information about the `kubeconfig` file, refer to the [K3s documentation]({{}}/k3s/latest/en/cluster-access/) or the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) about organizing cluster access using `kubeconfig` files. - -### Note on Upgrading - -Upgrading an air-gap environment can be accomplished in the following manner: - -1. Download the new air-gap images (tar file) from the [releases](https://github.com/rancher/k3s/releases) page for the version of K3s you will be upgrading to. Place the tar in the `/var/lib/rancher/k3s/agent/images/` directory on each node. Delete the old tar file. -2. Copy and replace the old K3s binary in `/usr/local/bin` on each node. Copy over the install script at https://get.k3s.io (as it is possible it has changed since the last release). Run the script again just as you had done in the past with the same environment variables. -3. Restart the K3s service (if not restarted automatically by installer). - - - - -We will create a Kubernetes cluster using Rancher Kubernetes Engine (RKE). Before being able to start your Kubernetes cluster, you’ll need to install RKE and create a RKE config file. - -### 1. Install RKE - -Install RKE by following the instructions in the [RKE documentation.]({{}}/rke/latest/en/installation/) - -### 2. Create an RKE Config File - -From a system that can access ports 22/TCP and 6443/TCP on the Linux host node(s) that you set up in a previous step, use the sample below to create a new file named `rancher-cluster.yml`. - -This file is an RKE configuration file, which is a configuration for the cluster you're deploying Rancher to. - -Replace values in the code sample below with help of the _RKE Options_ table. Use the IP address or DNS names of the three nodes you created. - -> **Tip:** For more details on the options available, see the RKE [Config Options]({{}}/rke/latest/en/config-options/). - -
RKE Options
- -| Option | Required | Description | -| ------------------ | -------------------- | --------------------------------------------------------------------------------------- | -| `address` | ✓ | The DNS or IP address for the node within the air gapped network. | -| `user` | ✓ | A user that can run Docker commands. | -| `role` | ✓ | List of Kubernetes roles assigned to the node. | -| `internal_address` | optional1 | The DNS or IP address used for internal cluster traffic. | -| `ssh_key_path` | | Path to the SSH private key used to authenticate to the node (defaults to `~/.ssh/id_rsa`). | - -> 1 Some services like AWS EC2 require setting the `internal_address` if you want to use self-referencing security groups or firewalls. - -```yaml -nodes: - - address: 10.10.3.187 # node air gap network IP - internal_address: 172.31.7.22 # node intra-cluster IP - user: rancher - role: ['controlplane', 'etcd', 'worker'] - ssh_key_path: /home/user/.ssh/id_rsa - - address: 10.10.3.254 # node air gap network IP - internal_address: 172.31.13.132 # node intra-cluster IP - user: rancher - role: ['controlplane', 'etcd', 'worker'] - ssh_key_path: /home/user/.ssh/id_rsa - - address: 10.10.3.89 # node air gap network IP - internal_address: 172.31.3.216 # node intra-cluster IP - user: rancher - role: ['controlplane', 'etcd', 'worker'] - ssh_key_path: /home/user/.ssh/id_rsa - -private_registries: - - url: # private registry url - user: rancher - password: '*********' - is_default: true -``` - -### 3. Run RKE - -After configuring `rancher-cluster.yml`, bring up your Kubernetes cluster: - -``` -rke up --config ./rancher-cluster.yml -``` - -### 4. Save Your Files - -> **Important** -> The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster. - -Save a copy of the following files in a secure location: - -- `rancher-cluster.yml`: The RKE cluster configuration file. -- `kube_config_cluster.yml`: The [Kubeconfig file]({{}}/rke/latest/en/kubeconfig/) for the cluster, this file contains credentials for full access to the cluster. -- `rancher-cluster.rkestate`: The [Kubernetes Cluster State file]({{}}/rke/latest/en/installation/#kubernetes-cluster-state), this file contains the current state of the cluster including the RKE configuration and the certificates.

_The Kubernetes Cluster State file is only created when using RKE v0.2.0 or higher._ - - - - -> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file. - -### Issues or errors? - -See the [Troubleshooting]({{}}/rancher/v2.6/en/installation/resources/troubleshooting/) page. - -### [Next: Install Rancher](../install-rancher) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/populate-private-registry/populate-private-registry.md b/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/populate-private-registry/populate-private-registry.md deleted file mode 100644 index d5565aff805..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/populate-private-registry/populate-private-registry.md +++ /dev/null @@ -1,294 +0,0 @@ ---- -title: '2. Collect and Publish Images to your Private Registry' -weight: 200 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This section describes how to set up your private registry so that when you install Rancher, Rancher will pull all the required images from this registry. - -By default, all images used to [provision Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/) or launch any tools in Rancher, e.g. monitoring, pipelines, alerts, are pulled from Docker Hub. In an air gapped installation of Rancher, you will need a private registry that is located somewhere accessible by your Rancher server. Then, you will load the registry with all the images. - -Populating the private registry with images is the same process for installing Rancher with Docker and for installing Rancher on a Kubernetes cluster. - -The steps in this section differ depending on whether or not you are planning to use Rancher to provision a downstream cluster with Windows nodes or not. By default, we provide the steps of how to populate your private registry assuming that Rancher will provision downstream Kubernetes clusters with only Linux nodes. But if you plan on provisioning any [downstream Kubernetes clusters using Windows nodes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/), there are separate instructions to support the images needed. - -> **Prerequisites:** -> -> You must have a [private registry](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) available to use. -> -> If the registry has certs, follow [this K3s documentation](https://rancher.com/docs/k3s/latest/en/installation/private-registry/) about adding a private registry. The certs and registry configuration files need to be mounted into the Rancher container. - - - - -For Rancher servers that will only provision Linux clusters, these are the steps to populate your private registry. - -1. [Find the required assets for your Rancher version](#1-find-the-required-assets-for-your-rancher-version) -2. [Collect the cert-manager image](#2-collect-the-cert-manager-image) (unless you are bringing your own certificates or terminating TLS on a load balancer) -3. [Save the images to your workstation](#3-save-the-images-to-your-workstation) -4. [Populate the private registry](#4-populate-the-private-registry) - -### Prerequisites - -These steps expect you to use a Linux workstation that has internet access, access to your private registry, and at least 20 GB of disk space. - -If you will use ARM64 hosts, the registry must support manifests. As of April 2020, Amazon Elastic Container Registry does not support manifests. - -### 1. Find the required assets for your Rancher version - -1. Go to our [releases page,](https://github.com/rancher/rancher/releases) find the Rancher v2.x.x release that you want to install, and click **Assets**. Note: Don't use releases marked `rc` or `Pre-release`, as they are not stable for production environments. - -2. From the release's **Assets** section, download the following files, which are required to install Rancher in an air gap environment: - -| Release File | Description | -| ---------------- | -------------- | -| `rancher-images.txt` | This file contains a list of images needed to install Rancher, provision clusters and user Rancher tools. | -| `rancher-save-images.sh` | This script pulls all the images in the `rancher-images.txt` from Docker Hub and saves all of the images as `rancher-images.tar.gz`. | -| `rancher-load-images.sh` | This script loads images from the `rancher-images.tar.gz` file and pushes them to your private registry. | - -### 2. Collect the cert-manager image - -> Skip this step if you are using your own certificates, or if you are terminating TLS on an external load balancer. - -In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS certificates, you must add the [`cert-manager`](https://hub.helm.sh/charts/jetstack/cert-manager) image to `rancher-images.txt` as well. - -**Note:** New in v2.6.4, cert-manager versions 1.6.2 and 1.7.1 are compatible. We recommend v1.7.x because v 1.6.x will reach end-of-life on March 30, 2022. - -1. Fetch the latest `cert-manager` Helm chart and parse the template for image details: - - > **Note:** Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/). - - ```plain - helm repo add jetstack https://charts.jetstack.io - helm repo update - helm fetch jetstack/cert-manager --version v1.7.1 - helm template ./cert-manager-.tgz | awk '$1 ~ /image:/ {print $2}' | sed s/\"//g >> ./rancher-images.txt - ``` - -2. Sort and unique the images list to remove any overlap between the sources: - - ```plain - sort -u rancher-images.txt -o rancher-images.txt - ``` - -### 3. Save the images to your workstation - -1. Make `rancher-save-images.sh` an executable: - ``` - chmod +x rancher-save-images.sh - ``` - -1. Run `rancher-save-images.sh` with the `rancher-images.txt` image list to create a tarball of all the required images: - ```plain - ./rancher-save-images.sh --image-list ./rancher-images.txt - ``` - **Result:** Docker begins pulling the images used for an air gap install. Be patient. This process takes a few minutes. When the process completes, your current directory will output a tarball named `rancher-images.tar.gz`. Check that the output is in the directory. - -### 4. Populate the private registry - -Next, you will move the images in the `rancher-images.tar.gz` to your private registry using the scripts to load the images. - -Move the images in the `rancher-images.tar.gz` to your private registry using the scripts to load the images. - -The `rancher-images.txt` is expected to be on the workstation in the same directory that you are running the `rancher-load-images.sh` script. The `rancher-images.tar.gz` should also be in the same directory. - -1. Log into your private registry if required: - ```plain - docker login - ``` -1. Make `rancher-load-images.sh` an executable: - ``` - chmod +x rancher-load-images.sh - ``` - -1. Use `rancher-load-images.sh` to extract, tag and push `rancher-images.txt` and `rancher-images.tar.gz` to your private registry: - ```plain - ./rancher-load-images.sh --image-list ./rancher-images.txt --registry - ``` - - - - -For Rancher servers that will provision Linux and Windows clusters, there are distinctive steps to populate your private registry for the Windows images and the Linux images. Since a Windows cluster is a mix of Linux and Windows nodes, the Linux images pushed into the private registry are manifests. - -# Windows Steps - -The Windows images need to be collected and pushed from a Windows server workstation. - -1. Find the required assets for your Rancher version -2. Save the images to your Windows Server workstation -3. Prepare the Docker daemon -4. Populate the private registry - -### Prerequisites - -These steps expect you to use a Windows Server 1809 workstation that has internet access, access to your private registry, and at least 50 GB of disk space. - -The workstation must have Docker 18.02+ in order to support manifests, which are required when provisioning Windows clusters. - -Your registry must support manifests. As of April 2020, Amazon Elastic Container Registry does not support manifests. - - - -### 1. Find the required assets for your Rancher version - -1. Browse to our [releases page](https://github.com/rancher/rancher/releases) and find the Rancher v2.x.x release that you want to install. Don't download releases marked `rc` or `Pre-release`, as they are not stable for production environments. - -2. From the release's "Assets" section, download the following files: - -| Release File | Description | -|----------------------------|------------------| -| `rancher-windows-images.txt` | This file contains a list of Windows images needed to provision Windows clusters. | -| `rancher-save-images.ps1` | This script pulls all the images in the `rancher-windows-images.txt` from Docker Hub and saves all of the images as `rancher-windows-images.tar.gz`. | -| `rancher-load-images.ps1` | This script loads the images from the `rancher-windows-images.tar.gz` file and pushes them to your private registry. | - - - -### 2. Save the images to your Windows Server workstation - -1. Using `powershell`, go to the directory that has the files that were downloaded in the previous step. - -1. Run `rancher-save-images.ps1` to create a tarball of all the required images: - ```plain - ./rancher-save-images.ps1 - ``` - - **Result:** Docker begins pulling the images used for an air gap install. Be patient. This process takes a few minutes. When the process completes, your current directory will output a tarball named `rancher-windows-images.tar.gz`. Check that the output is in the directory. - - - -### 3. Prepare the Docker daemon - -Append your private registry address to the `allow-nondistributable-artifacts` config field in the Docker daemon (`C:\ProgramData\Docker\config\daemon.json`). Since the base image of Windows images are maintained by the `mcr.microsoft.com` registry, this step is required as the layers in the Microsoft registry are missing from Docker Hub and need to be pulled into the private registry. - - ``` - { - ... - "allow-nondistributable-artifacts": [ - ... - "" - ] - ... - } - ``` - - - -### 4. Populate the private registry - -Move the images in the `rancher-windows-images.tar.gz` to your private registry using the scripts to load the images. - -The `rancher-windows-images.txt` is expected to be on the workstation in the same directory that you are running the `rancher-load-images.ps1` script. The `rancher-windows-images.tar.gz` should also be in the same directory. - -1. Using `powershell`, log into your private registry if required: - ```plain - docker login - ``` - -1. Using `powershell`, use `rancher-load-images.ps1` to extract, tag and push the images from `rancher-images.tar.gz` to your private registry: - ```plain - ./rancher-load-images.ps1 --registry - ``` - -# Linux Steps - -The Linux images need to be collected and pushed from a Linux host, but _must be done after_ populating the Windows images into the private registry. These step are different from the Linux only steps as the Linux images that are pushed will actually manifests that support Windows and Linux images. - -1. Find the required assets for your Rancher version -2. Collect all the required images -3. Save the images to your Linux workstation -4. Populate the private registry - -### Prerequisites - -You must populate the private registry with the Windows images before populating the private registry with Linux images. If you have already populated the registry with Linux images, you will need to follow these instructions again as they will publish manifests that support Windows and Linux images. - -These steps expect you to use a Linux workstation that has internet access, access to your private registry, and at least 20 GB of disk space. - -The workstation must have Docker 18.02+ in order to support manifests, which are required when provisioning Windows clusters. - - - -### 1. Find the required assets for your Rancher version - -1. Browse to our [releases page](https://github.com/rancher/rancher/releases) and find the Rancher v2.x.x release that you want to install. Don't download releases marked `rc` or `Pre-release`, as they are not stable for production environments. Click **Assets**. - -2. From the release's **Assets** section, download the following files: - -| Release File | Description | -|----------------------------| -------------------------- | -| `rancher-images.txt` | This file contains a list of images needed to install Rancher, provision clusters and user Rancher tools. | -| `rancher-windows-images.txt` | This file contains a list of images needed to provision Windows clusters. | -| `rancher-save-images.sh` | This script pulls all the images in the `rancher-images.txt` from Docker Hub and saves all of the images as `rancher-images.tar.gz`. | -| `rancher-load-images.sh` | This script loads images from the `rancher-images.tar.gz` file and pushes them to your private registry. | - - - -### 2. Collect all the required images - -**For Kubernetes Installs using Rancher Generated Self-Signed Certificate:** In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS certificates, you must add the [`cert-manager`](https://hub.helm.sh/charts/jetstack/cert-manager) image to `rancher-images.txt` as well. You skip this step if you are using you using your own certificates. - -1. Fetch the latest `cert-manager` Helm chart and parse the template for image details: - > **Note:** Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/). - ```plain - helm repo add jetstack https://charts.jetstack.io - helm repo update - helm fetch jetstack/cert-manager --version v0.12.0 - helm template ./cert-manager-.tgz | awk '$1 ~ /image:/ {print $2}' | sed s/\"//g >> ./rancher-images.txt - ``` - -2. Sort and unique the images list to remove any overlap between the sources: - ```plain - sort -u rancher-images.txt -o rancher-images.txt - ``` - - - -### 3. Save the images to your workstation - -1. Make `rancher-save-images.sh` an executable: - ``` - chmod +x rancher-save-images.sh - ``` - -1. Run `rancher-save-images.sh` with the `rancher-images.txt` image list to create a tarball of all the required images: - ```plain - ./rancher-save-images.sh --image-list ./rancher-images.txt - ``` - -**Result:** Docker begins pulling the images used for an air gap install. Be patient. This process takes a few minutes. When the process completes, your current directory will output a tarball named `rancher-images.tar.gz`. Check that the output is in the directory. - - - -### 4. Populate the private registry - -Move the images in the `rancher-images.tar.gz` to your private registry using the `rancher-load-images.sh script` to load the images. - -The image list, `rancher-images.txt` or `rancher-windows-images.txt`, is expected to be on the workstation in the same directory that you are running the `rancher-load-images.sh` script. The `rancher-images.tar.gz` should also be in the same directory. - -1. Log into your private registry if required: - ```plain - docker login - ``` - -1. Make `rancher-load-images.sh` an executable: - ``` - chmod +x rancher-load-images.sh - ``` - -1. Use `rancher-load-images.sh` to extract, tag and push the images from `rancher-images.tar.gz` to your private registry: - -```plain -./rancher-load-images.sh --image-list ./rancher-images.txt \ - --windows-image-list ./rancher-windows-images.txt \ - --registry -``` - - - - -### [Next step for Kubernetes Installs - Launch a Kubernetes Cluster]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/launch-kubernetes/) - -### [Next step for Docker Installs - Install Rancher]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/install-rancher/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/prepare-nodes/prepare-nodes.md b/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/prepare-nodes/prepare-nodes.md deleted file mode 100644 index 4b181dfaee4..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/air-gap/prepare-nodes/prepare-nodes.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -title: '1. Set up Infrastructure and Private Registry' -weight: 100 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -In this section, you will provision the underlying infrastructure for your Rancher management server in an air gapped environment. You will also set up the private Docker registry that must be available to your Rancher node(s). - -An air gapped environment is an environment where the Rancher server is installed offline or behind a firewall. - -The infrastructure depends on whether you are installing Rancher on a K3s Kubernetes cluster, an RKE Kubernetes cluster, or a single Docker container. For more information on each installation option, refer to [this page.]({{}}/rancher/v2.6/en/installation/) - -Rancher can be installed on any Kubernetes cluster. The RKE and K3s Kubernetes infrastructure tutorials below are still included for convenience. - - - - -We recommend setting up the following infrastructure for a high-availability installation: - -- **Two Linux nodes,** typically virtual machines, in the infrastructure provider of your choice. -- **An external database** to store the cluster data. PostgreSQL, MySQL, and etcd are supported. -- **A load balancer** to direct traffic to the two nodes. -- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it. -- **A private Docker registry** to distribute Docker images to your machines. - -### 1. Set up Linux Nodes - -These hosts will be disconnected from the internet, but require being able to connect with your private registry. - -Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node) for setting up nodes as instances in Amazon EC2. - -### 2. Set up External Datastore - -The ability to run Kubernetes using a datastore other than etcd sets K3s apart from other Kubernetes distributions. This feature provides flexibility to Kubernetes operators. The available options allow you to select a datastore that best fits your use case. - -For a high-availability K3s installation, you will need to set up one of the following external databases: - -* [PostgreSQL](https://www.postgresql.org/) (certified against versions 10.7 and 11.5) -* [MySQL](https://www.mysql.com/) (certified against version 5.7) -* [etcd](https://etcd.io/) (certified against version 3.3.15) - -When you install Kubernetes, you will pass in details for K3s to connect to the database. - -For an example of one way to set up the database, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/rds) for setting up a MySQL database on Amazon's RDS service. - -For the complete list of options that are available for configuring a K3s cluster datastore, refer to the [K3s documentation.]({{}}/k3s/latest/en/installation/datastore/) - -### 3. Set up the Load Balancer - -You will also need to set up a load balancer to direct traffic to the Rancher replica on both nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server. - -When Kubernetes gets set up in a later step, the K3s tool will deploy a Traefik Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames. - -When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the Traefik Ingress controller to listen for traffic destined for the Rancher hostname. The Traefik Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster. - -For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer: - -- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment. -- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination) - -For an example showing how to set up an NGINX load balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/) - -For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/) - -> **Important:** -> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications. - -### 4. Set up the DNS Record - -Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer. - -Depending on your environment, this may be an A record pointing to the load balancer IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on. - -You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one. - -For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) - -### 5. Set up a Private Docker Registry - -Rancher supports air gap installs using a private registry. You must have your own private registry or other means of distributing Docker images to your machines. - -In a later step, when you set up your K3s Kubernetes cluster, you will create a [private registries configuration file]({{}}/k3s/latest/en/installation/private-registry/) with details from this registry. - -If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) - - - - -To install the Rancher management server on a high-availability RKE cluster, we recommend setting up the following infrastructure: - -- **Three Linux nodes,** typically virtual machines, in an infrastructure provider such as Amazon's EC2, Google Compute Engine, or vSphere. -- **A load balancer** to direct front-end traffic to the three nodes. -- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it. -- **A private Docker registry** to distribute Docker images to your machines. - -These nodes must be in the same region/data center. You may place these servers in separate availability zones. - -### Why three nodes? - -In an RKE cluster, Rancher server data is stored on etcd. This etcd database runs on all three nodes. - -The etcd database requires an odd number of nodes so that it can always elect a leader with a majority of the etcd cluster. If the etcd database cannot elect a leader, etcd can suffer from [split brain](https://www.quora.com/What-is-split-brain-in-distributed-systems), requiring the cluster to be restored from backup. If one of the three etcd nodes fails, the two remaining nodes can elect a leader because they have the majority of the total number of etcd nodes. - -### 1. Set up Linux Nodes - -These hosts will be disconnected from the internet, but require being able to connect with your private registry. - -Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/) for setting up nodes as instances in Amazon EC2. - -### 2. Set up the Load Balancer - -You will also need to set up a load balancer to direct traffic to the Rancher replica on both nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server. - -When Kubernetes gets set up in a later step, the RKE tool will deploy an NGINX Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames. - -When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the NGINX Ingress controller to listen for traffic destined for the Rancher hostname. The NGINX Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster. - -For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer: - -- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment. -- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination) - -For an example showing how to set up an NGINX load balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/) - -For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/) - -> **Important:** -> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications. - -### 3. Set up the DNS Record - -Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer. - -Depending on your environment, this may be an A record pointing to the LB IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on. - -You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one. - -For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) - -### 4. Set up a Private Docker Registry - -Rancher supports air gap installs using a secure Docker private registry. You must have your own private registry or other means of distributing Docker images to your machines. - -In a later step, when you set up your RKE Kubernetes cluster, you will create a [private registries configuration file]({{}}/rke/latest/en/config-options/private-registries/) with details from this registry. - -If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) - - - - -> The Docker installation is for Rancher users that are wanting to test out Rancher. Since there is only one node and a single Docker container, if the node goes down, you will lose all the data of your Rancher server. -> -> The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster.]({{}}/rancher/v2.6/en/backups/migrating-rancher) - -### 1. Set up a Linux Node - -This host will be disconnected from the Internet, but needs to be able to connect to your private registry. - -Make sure that your node fulfills the general installation requirements for [OS, Docker, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/) for setting up nodes as instances in Amazon EC2. - -### 2. Set up a Private Docker Registry - -Rancher supports air gap installs using a Docker private registry on your bastion server. You must have your own private registry or other means of distributing Docker images to your machines. - -If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/) - - - - -### [Next: Collect and Publish Images to your Private Registry]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/behind-proxy.md b/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/behind-proxy.md deleted file mode 100644 index 2214b1c3b25..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/behind-proxy.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Installing Rancher behind an HTTP Proxy -weight: 4 ---- - -In a lot of enterprise environments, servers or VMs running on premise do not have direct Internet access, but must connect to external services through a HTTP(S) proxy for security reasons. This tutorial shows step by step how to set up a highly available Rancher installation in such an environment. - -Alternatively, it is also possible to set up Rancher completely air-gapped without any Internet access. This process is described in detail in the [Rancher docs]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/). - -# Installation Outline - -1. [Set up infrastructure]({{}}/rancher/v2.6/en/installation/other-installation-methods/behind-proxy/prepare-nodes/) -2. [Set up a Kubernetes cluster]({{}}/rancher/v2.6/en/installation/other-installation-methods/behind-proxy/launch-kubernetes/) -3. [Install Rancher]({{}}/rancher/v2.6/en/installation/other-installation-methods/behind-proxy/install-rancher/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/install-rancher/install-rancher.md b/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/install-rancher/install-rancher.md deleted file mode 100644 index c147692a558..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/install-rancher/install-rancher.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: 3. Install Rancher -weight: 300 ---- - -Now that you have a running RKE cluster, you can install Rancher in it. For security reasons all traffic to Rancher must be encrypted with TLS. For this tutorial you are going to automatically issue a self-signed certificate through [cert-manager](https://cert-manager.io/). In a real-world use-case you will likely use Let's Encrypt or provide your own certificate. - -> **Note:** These installation instructions assume you are using Helm 3. - -### Install cert-manager - -Add the cert-manager helm repository: - -``` -helm repo add jetstack https://charts.jetstack.io -``` - -Create a namespace for cert-manager: - -``` -kubectl create namespace cert-manager -``` - -Install the CustomResourceDefinitions of cert-manager: - -**Note:** New in v2.6.4, cert-manager versions 1.6.2 and 1.7.1 are compatible. We recommend v1.7.x because v 1.6.x will reach end-of-life on March 30, 2022. - -``` -kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml -``` - -And install it with Helm. Note that cert-manager also needs your proxy configured in case it needs to communicate with Let's Encrypt or other external certificate issuers: - -``` -helm upgrade --install cert-manager jetstack/cert-manager \ - --namespace cert-manager --version v1.7.1 \ - --set http_proxy=http://${proxy_host} \ - --set https_proxy=http://${proxy_host} \ - --set no_proxy=127.0.0.0/8\\,10.0.0.0/8\\,cattle-system.svc\\,172.16.0.0/12\\,192.168.0.0/16\\,.svc\\,.cluster.local -``` - -Now you should wait until cert-manager is finished starting up: - -``` -kubectl rollout status deployment -n cert-manager cert-manager -kubectl rollout status deployment -n cert-manager cert-manager-webhook -``` - -### Install Rancher - -Next you can install Rancher itself. First add the helm repository: - -``` -helm repo add rancher-latest https://releases.rancher.com/server-charts/latest -``` - -Create a namespace: - -``` -kubectl create namespace cattle-system -``` - -And install Rancher with Helm. Rancher also needs a proxy configuration so that it can communicate with external application catalogs or retrieve Kubernetes version update metadata: - -``` -helm upgrade --install rancher rancher-latest/rancher \ - --namespace cattle-system \ - --set hostname=rancher.example.com \ - --set proxy=http://${proxy_host} \ - --set noProxy=127.0.0.0/8\\,10.0.0.0/8\\,cattle-system.svc\\,172.16.0.0/12\\,192.168.0.0/16\\,.svc\\,.cluster.local -``` - -After waiting for the deployment to finish: - -``` -kubectl rollout status deployment -n cattle-system rancher -``` - -You can now navigate to `https://rancher.example.com` and start using Rancher. - -> **Note:** If you don't intend to send telemetry data, opt out [telemetry]({{}}/rancher/v2.6/en/faq/telemetry/) during the initial login. Leaving this active in an air-gapped environment can cause issues if the sockets cannot be opened successfully. - -### Additional Resources - -These resources could be helpful when installing Rancher: - -- [Rancher Helm chart options]({{}}/rancher/v2.6/en/installation/resources/chart-options/) -- [Adding TLS secrets]({{}}/rancher/v2.6/en/installation/resources/tls-secrets/) -- [Troubleshooting Rancher Kubernetes Installations]({{}}/rancher/v2.6/en/installation/resources/troubleshooting/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/launch-kubernetes/launch-kubernetes.md b/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/launch-kubernetes/launch-kubernetes.md deleted file mode 100644 index 41428448b27..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/launch-kubernetes/launch-kubernetes.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -title: '2. Install Kubernetes' -weight: 200 ---- - -Once the infrastructure is ready, you can continue with setting up an RKE cluster to install Rancher in. - -### Installing Docker - -First, you have to install Docker and setup the HTTP proxy on all three Linux nodes. For this perform the following steps on all three nodes. - -For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell: - -``` -export proxy_host="10.0.0.5:8888" -export HTTP_PROXY=http://${proxy_host} -export HTTPS_PROXY=http://${proxy_host} -export NO_PROXY=127.0.0.0/8,10.0.0.0/8,cattle-system.svc,172.16.0.0/12,192.168.0.0/16 -``` - -Next configure apt to use this proxy when installing packages. If you are not using Ubuntu, you have to adapt this step accordingly: - -``` -cat <<'EOF' | sudo tee /etc/apt/apt.conf.d/proxy.conf > /dev/null -Acquire::http::Proxy "http://${proxy_host}/"; -Acquire::https::Proxy "http://${proxy_host}/"; -EOF -``` - -Now you can install Docker: - -``` -curl -sL https://releases.rancher.com/install-docker/19.03.sh | sh -``` - -Then ensure that your current user is able to access the Docker daemon without sudo: - -``` -sudo usermod -aG docker YOUR_USERNAME -``` - -And configure the Docker daemon to use the proxy to pull images: - -``` -sudo mkdir -p /etc/systemd/system/docker.service.d -cat <<'EOF' | sudo tee /etc/systemd/system/docker.service.d/http-proxy.conf > /dev/null -[Service] -Environment="HTTP_PROXY=http://${proxy_host}" -Environment="HTTPS_PROXY=http://${proxy_host}" -Environment="NO_PROXY=127.0.0.0/8,10.0.0.0/8,cattle-system.svc,172.16.0.0/12,192.168.0.0/16" -EOF -``` - -To apply the configuration, restart the Docker daemon: - -``` -sudo systemctl daemon-reload -sudo systemctl restart docker -``` - -#### Air-gapped proxy - -_New in v2.6.4_ - -You can now provision node driver clusters from an air-gapped cluster configured to use a proxy for outbound connections. - -In addition to setting the default rules for a proxy server, you will need to add additional rules, shown below, to provision node driver clusters from a proxied Rancher environment. - -You will configure your filepath according to your setup, e.g., `/etc/apt/apt.conf.d/proxy.conf`: - -``` -acl SSL_ports port 22 -acl SSL_ports port 2376 - -acl Safe_ports port 22 # ssh -acl Safe_ports port 2376 # docker port -``` - -### Creating the RKE Cluster - -You need several command line tools on the host where you have SSH access to the Linux nodes to create and interact with the cluster: - -* [RKE CLI binary]({{}}/rke/latest/en/installation/#download-the-rke-binary) - -``` -sudo curl -fsSL -o /usr/local/bin/rke https://github.com/rancher/rke/releases/download/v1.1.4/rke_linux-amd64 -sudo chmod +x /usr/local/bin/rke -``` - -* [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) - -``` -curl -LO "https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl" -chmod +x ./kubectl -sudo mv ./kubectl /usr/local/bin/kubectl -``` - -* [helm](https://helm.sh/docs/intro/install/) - -``` -curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 -chmod +x get_helm.sh -sudo ./get_helm.sh -``` - -Next, create a YAML file that describes the RKE cluster. Ensure that the IP addresses of the nodes and the SSH username are correct. For more information on the cluster YAML, have a look at the [RKE documentation]({{}}/rke/latest/en/example-yamls/). - -``` -nodes: - - address: 10.0.1.200 - user: ubuntu - role: [controlplane,worker,etcd] - - address: 10.0.1.201 - user: ubuntu - role: [controlplane,worker,etcd] - - address: 10.0.1.202 - user: ubuntu - role: [controlplane,worker,etcd] - -services: - etcd: - backup_config: - interval_hours: 12 - retention: 6 -``` - -After that, you can create the Kubernetes cluster by running: - -``` -rke up --config rancher-cluster.yaml -``` - -RKE creates a state file called `rancher-cluster.rkestate`, this is needed if you want to perform updates, modify your cluster configuration or restore it from a backup. It also creates a `kube_config_cluster.yaml` file, that you can use to connect to the remote Kubernetes cluster locally with tools like kubectl or Helm. Make sure to save all of these files in a secure location, for example by putting them into a version control system. - -To have a look at your cluster run: - -``` -export KUBECONFIG=kube_config_cluster.yaml -kubectl cluster-info -kubectl get pods --all-namespaces -``` - -You can also verify that your external load balancer works, and the DNS entry is set up correctly. If you send a request to either, you should receive HTTP 404 response from the ingress controller: - -``` -$ curl 10.0.1.100 -default backend - 404 -$ curl rancher.example.com -default backend - 404 -``` - -### Save Your Files - -> **Important** -> The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster. - -Save a copy of the following files in a secure location: - -- `rancher-cluster.yml`: The RKE cluster configuration file. -- `kube_config_cluster.yml`: The [Kubeconfig file]({{}}/rke/latest/en/kubeconfig/) for the cluster, this file contains credentials for full access to the cluster. -- `rancher-cluster.rkestate`: The [Kubernetes Cluster State file]({{}}/rke/latest/en/installation/#kubernetes-cluster-state), this file contains the current state of the cluster including the RKE configuration and the certificates. - -> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file. - -### Issues or errors? - -See the [Troubleshooting]({{}}/rancher/v2.6/en/installation/resources/troubleshooting/) page. - -### [Next: Install Rancher](../install-rancher) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/prepare-nodes/prepare-nodes.md b/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/prepare-nodes/prepare-nodes.md deleted file mode 100644 index 6d8aaf813e3..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/behind-proxy/prepare-nodes/prepare-nodes.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: '1. Set up Infrastructure' -weight: 100 ---- - -In this section, you will provision the underlying infrastructure for your Rancher management server with internete access through a HTTP proxy. - -To install the Rancher management server on a high-availability RKE cluster, we recommend setting up the following infrastructure: - -- **Three Linux nodes,** typically virtual machines, in an infrastructure provider such as Amazon's EC2, Google Compute Engine, or vSphere. -- **A load balancer** to direct front-end traffic to the three nodes. -- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it. - -These nodes must be in the same region/data center. You may place these servers in separate availability zones. - -### Why three nodes? - -In an RKE cluster, Rancher server data is stored on etcd. This etcd database runs on all three nodes. - -The etcd database requires an odd number of nodes so that it can always elect a leader with a majority of the etcd cluster. If the etcd database cannot elect a leader, etcd can suffer from [split brain](https://www.quora.com/What-is-split-brain-in-distributed-systems), requiring the cluster to be restored from backup. If one of the three etcd nodes fails, the two remaining nodes can elect a leader because they have the majority of the total number of etcd nodes. - -### 1. Set up Linux Nodes - -These hosts will connect to the internet through an HTTP proxy. - -Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/) for setting up nodes as instances in Amazon EC2. - -### 2. Set up the Load Balancer - -You will also need to set up a load balancer to direct traffic to the Rancher replica on both nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server. - -When Kubernetes gets set up in a later step, the RKE tool will deploy an NGINX Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames. - -When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the NGINX Ingress controller to listen for traffic destined for the Rancher hostname. The NGINX Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster. - -For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer: - -- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment. -- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination) - -For an example showing how to set up an NGINX load balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/) - -For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/) - -> **Important:** -> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications. - -### 3. Set up the DNS Record - -Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer. - -Depending on your environment, this may be an A record pointing to the LB IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on. - -You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one. - -For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) - - -### [Next: Set up a Kubernetes cluster]({{}}/rancher/v2.6/en/installation/other-installation-methods/behind-proxy/launch-kubernetes/) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/other-installation-methods.md b/versioned_docs/version-2.6/installation/other-installation-methods/other-installation-methods.md deleted file mode 100644 index 4a15c472dbe..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/other-installation-methods.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Other Installation Methods -weight: 3 ---- - -### Air Gapped Installations - -Follow [these steps]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) to install the Rancher server in an air gapped environment. - -An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. - -### Docker Installations - -The [single-node Docker installation]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker) is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster using Helm, you install the Rancher server component on a single node using a `docker run` command. - -The Docker installation is for development and testing environments only. - -Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server. - -The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster.]({{}}/rancher/v2.6/en/backups/migrating-rancher) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/advanced/advanced.md b/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/advanced/advanced.md deleted file mode 100644 index 6686fef83cd..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/advanced/advanced.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: Advanced Options for Docker Installs -weight: 5 ---- - -When installing Rancher, there are several advanced options that can be enabled: - -- [Custom CA Certificate](#custom-ca-certificate) -- [API Audit Log](#api-audit-log) -- [TLS Settings](#tls-settings) -- [Air Gap](#air-gap) -- [Persistent Data](#persistent-data) -- [Running `rancher/rancher` and `rancher/rancher-agent` on the Same Node](#running-rancher-rancher-and-rancher-rancher-agent-on-the-same-node) - -### Custom CA Certificate - -If you want to configure Rancher to use a CA root certificate to be used when validating services, you would start the Rancher container sharing the directory that contains the CA root certificate. - -Use the command example to start a Rancher container with your private CA certificates mounted. - -- The volume flag (`-v`) should specify the host directory containing the CA root certificates. -- The environment variable flag (`-e`) in combination with `SSL_CERT_DIR` and directory declares an environment variable that specifies the mounted CA root certificates directory location inside the container. -- Passing environment variables to the Rancher container can be done using `-e KEY=VALUE` or `--env KEY=VALUE`. -- Mounting a host directory inside the container can be done using `-v host-source-directory:container-destination-directory` or `--volume host-source-directory:container-destination-directory`. - -The example below is based on having the CA root certificates in the `/host/certs` directory on the host and mounting this directory on `/container/certs` inside the Rancher container. - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v /host/certs:/container/certs \ - -e SSL_CERT_DIR="/container/certs" \ - --privileged \ - rancher/rancher:latest -``` - -### API Audit Log - -The API Audit Log records all the user and system transactions made through Rancher server. - -The API Audit Log writes to `/var/log/auditlog` inside the rancher container by default. Share that directory as a volume and set your `AUDIT_LEVEL` to enable the log. - -See [API Audit Log]({{}}/rancher/v2.6/en/installation/resources/advanced/api-audit-log) for more information and options. - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v /var/log/rancher/auditlog:/var/log/auditlog \ - -e AUDIT_LEVEL=1 \ - --privileged \ - rancher/rancher:latest -``` - -### TLS settings - -To set a different TLS configuration, you can use the `CATTLE_TLS_MIN_VERSION` and `CATTLE_TLS_CIPHERS` environment variables. For example, to configure TLS 1.0 as minimum accepted TLS version: - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -e CATTLE_TLS_MIN_VERSION="1.0" \ - --privileged \ - rancher/rancher:latest -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -See [TLS settings]({{}}/rancher/v2.6/en/installation/resources/tls-settings) for more information and options. - -### Air Gap - -If you are visiting this page to complete an air gap installation, you must prepend your private registry URL to the server tag when running the installation command in the option that you choose. Add `` with your private registry URL in front of `rancher/rancher:latest`. - -**Example:** - - /rancher/rancher:latest - -### Persistent Data - -Rancher uses etcd as a datastore. When Rancher is installed with Docker, the embedded etcd is being used. The persistent data is at the following path in the container: `/var/lib/rancher`. - -You can bind mount a host volume to this location to preserve data on the host it is running on: - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v /opt/rancher:/var/lib/rancher \ - --privileged \ - rancher/rancher:latest -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -### Running `rancher/rancher` and `rancher/rancher-agent` on the Same Node - -In the situation where you want to use a single node to run Rancher and to be able to add the same node to a cluster, you have to adjust the host ports mapped for the `rancher/rancher` container. - -If a node is added to a cluster, it deploys the nginx ingress controller which will use port 80 and 443. This will conflict with the default ports we advise to expose for the `rancher/rancher` container. - -Please note that this setup is not recommended for production use, but can be convenient for development/demo purposes. - -To change the host ports mapping, replace the following part `-p 80:80 -p 443:443` with `-p 8080:80 -p 8443:443`: - -``` -docker run -d --restart=unless-stopped \ - -p 8080:80 -p 8443:443 \ - --privileged \ - rancher/rancher:latest -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/proxy/proxy.md b/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/proxy/proxy.md deleted file mode 100644 index 37d3d2cfc00..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/proxy/proxy.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: HTTP Proxy Configuration -weight: 251 ---- - -If you operate Rancher behind a proxy and you want to access services through the proxy (such as retrieving catalogs), you must provide Rancher information about your proxy. As Rancher is written in Go, it uses the common proxy environment variables as shown below. - -Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy. - -| Environment variable | Purpose | -| -------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) | -| HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) | -| NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s) | - -> **Note** NO_PROXY must be in uppercase to use network range (CIDR) notation. - -## Docker Installation - -Passing environment variables to the Rancher container can be done using `-e KEY=VALUE` or `--env KEY=VALUE`. Required values for `NO_PROXY` in a [Docker Installation]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/) are: - -- `localhost` -- `127.0.0.1` -- `0.0.0.0` -- `10.0.0.0/8` -- `cattle-system.svc` -- `.svc` -- `.cluster.local` - -The example below is based on a proxy server accessible at `http://192.168.0.1:3128`, and excluding usage the proxy when accessing network range `192.168.10.0/24` and every hostname under the domain `example.com`. - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -e HTTP_PROXY="http://192.168.10.1:3128" \ - -e HTTPS_PROXY="http://192.168.10.1:3128" \ - -e NO_PROXY="localhost,127.0.0.1,0.0.0.0,10.0.0.0/8,cattle-system.svc,192.168.10.0/24,.svc,.cluster.local,example.com" \ - --privileged \ - rancher/rancher:latest -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -### Air-gapped proxy configuration - -_New in v2.6.4_ - -You can now provision node driver clusters from an air-gapped cluster configured to use a proxy for outbound connections. - -In addition to setting the default rules for a proxy server as shown above, you will need to add additional rules, shown below, to provision node driver clusters from a proxied Rancher environment. - -You will configure your filepath according to your setup, e.g., `/etc/apt/apt.conf.d/proxy.conf`: - -``` -acl SSL_ports port 22 -acl SSL_ports port 2376 - -acl Safe_ports port 22 # ssh -acl Safe_ports port 2376 # docker port -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-docker.md b/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-docker.md deleted file mode 100644 index a52c192fe83..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-docker.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -title: Installing Rancher on a Single Node Using Docker -description: For development and testing environments only, use a Docker install. Install Docker on a single Linux host, and deploy Rancher with a single Docker container. -weight: 2 ---- - -Rancher can be installed by running a single Docker container. - -In this installation scenario, you'll install Docker on a single Linux host, and then deploy Rancher on your host using a single Docker container. - -> **Want to use an external load balancer?** -> See [Docker Install with an External Load Balancer]({{}}/rancher/v2.6/en/installation/resources/advanced/single-node-install-external-lb) instead. - -A Docker installation of Rancher is recommended only for development and testing purposes. The ability to migrate Rancher to a high-availability cluster depends on the Rancher version: - -The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster.]({{}}/rancher/v2.6/en/backups/migrating-rancher) - -### Privileged Access for Rancher - -When the Rancher server is deployed in the Docker container, a local Kubernetes cluster is installed within the container for Rancher to use. Because many features of Rancher run as deployments, and privileged mode is required to run containers within containers, you will need to install Rancher with the `--privileged` option. - -# Requirements for OS, Docker, Hardware, and Networking - -Make sure that your node fulfills the general [installation requirements.]({{}}/rancher/v2.6/en/installation/requirements/) - -# 1. Provision Linux Host - -Provision a single Linux host according to our [Requirements]({{}}/rancher/v2.6/en/installation/requirements) to launch your Rancher server. - -# 2. Choose an SSL Option and Install Rancher - -For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster. - -> **Do you want to..**. -> -> - Use a proxy? See [HTTP Proxy Configuration]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/proxy/) -> - Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#custom-ca-certificate/) -> - Complete an Air Gap Installation? See [Air Gap: Docker Install]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/) -> - Record all transactions with the Rancher API? See [API Auditing](./advanced/#api-audit-log) - -Choose from the following options: - -- [Option A: Default Rancher-generated Self-signed Certificate](#option-a-default-rancher-generated-self-signed-certificate) -- [Option B: Bring Your Own Certificate, Self-signed](#option-b-bring-your-own-certificate-self-signed) -- [Option C: Bring Your Own Certificate, Signed by a Recognized CA](#option-c-bring-your-own-certificate-signed-by-a-recognized-ca) -- [Option D: Let's Encrypt Certificate](#option-d-let-s-encrypt-certificate) -- [Option E: Localhost tunneling, no Certificate](#option-e-localhost-tunneling-no-certificate) - -### Option A: Default Rancher-generated Self-signed Certificate - -If you are installing Rancher in a development or testing environment where identity verification isn't a concern, install Rancher using the self-signed certificate that it generates. This installation option omits the hassle of generating a certificate yourself. - -Log into your host, and run the command below: - -```bash -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher:latest -``` - -### Option B: Bring Your Own Certificate, Self-signed -In development or testing environments where your team will access your Rancher server, create a self-signed certificate for use with your install so that your team can verify they're connecting to your instance of Rancher. - -> **Prerequisites:** -> Create a self-signed certificate using [OpenSSL](https://www.openssl.org/) or another method of your choice. -> -> - The certificate files must be in PEM format. -> - In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -After creating your certificate, run the Docker command below to install Rancher. Use the `-v` flag and provide the path to your certificates to mount them in your container. - -| Placeholder | Description | -| ------------------- | --------------------- | -| `` | The path to the directory containing your certificate files. | -| `` | The path to your full certificate chain. | -| `` | The path to the private key for your certificate. | -| `` | The path to the certificate authority's certificate. | - -Log into your host, and run the command below: - -```bash -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - -v //:/etc/rancher/ssl/cacerts.pem \ - --privileged \ - rancher/rancher:latest -``` - -### Option C: Bring Your Own Certificate, Signed by a Recognized CA - -In production environments where you're exposing an app publicly, you would use a certificate signed by a recognized CA so that your user base doesn't encounter security warnings. - -The Docker install is not recommended for production. These instructions are provided for testing and development purposes only. - -> **Prerequisites:** -> -> - The certificate files must be in PEM format. -> - In your certificate file, include all intermediate certificates provided by the recognized CA. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -After obtaining your certificate, run the Docker command below. - -- Use the `-v` flag and provide the path to your certificates to mount them in your container. Because your certificate is signed by a recognized CA, mounting an additional CA certificate file is unnecessary. -- Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher. - -| Placeholder | Description | -| ------------------- | ----------------------------- | -| `` | The path to the directory containing your certificate files. | -| `` | The path to your full certificate chain. | -| `` | The path to the private key for your certificate. | - -Log into your host, and run the command below: - -```bash -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - --privileged \ - rancher/rancher:latest \ - --no-cacerts -``` - -### Option D: Let's Encrypt Certificate - -> **Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/). - -For production environments, you also have the option of using [Let's Encrypt](https://letsencrypt.org/) certificates. Let's Encrypt uses an http-01 challenge to verify that you have control over your domain. You can confirm that you control the domain by pointing the hostname that you want to use for Rancher access (for example, `rancher.mydomain.com`) to the IP of the machine it is running on. You can bind the hostname to the IP address by creating an A record in DNS. - -The Docker install is not recommended for production. These instructions are provided for testing and development purposes only. - -> **Prerequisites:** -> -> - Let's Encrypt is an Internet service. Therefore, this option cannot be used in an internal/air gapped network. -> - Create a record in your DNS that binds your Linux host IP address to the hostname that you want to use for Rancher access (`rancher.mydomain.com` for example). -> - Open port `TCP/80` on your Linux host. The Let's Encrypt http-01 challenge can come from any source IP address, so port `TCP/80` must be open to all IP addresses. - -After you fulfill the prerequisites, you can install Rancher using a Let's Encrypt certificate by running the following command. - -| Placeholder | Description | -| ----------------- | ------------------- | -| `` | Your domain address | - -Log into your host, and run the command below: - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher:latest \ - --acme-domain -``` - -### Option E: Localhost tunneling, no Certificate - -If you are installing Rancher in a development or testing environment where you have a localhost tunneling solution running, such as [ngrok](https://ngrok.com/), avoid generating a certificate. This installation option doesn't require a certificate. - -- You will use `--no-cacerts` in the argument to disable the default CA certificate generated by Rancher. - -Log into your host, and run the command below: - -```bash -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher:latest \ - --no-cacerts -``` - -## Advanced Options - -When installing Rancher on a single node with Docker, there are several advanced options that can be enabled: - -- Custom CA Certificate -- API Audit Log -- TLS Settings -- Air Gap -- Persistent Data -- Running `rancher/rancher` and `rancher/rancher-agent` on the Same Node - -Refer to [this page](./advanced) for details. - -## Troubleshooting - -Refer to [this page](./troubleshooting) for frequently asked questions and troubleshooting tips. - -## What's Next? - -- **Recommended:** Review [Single Node Backup and Restore]({{}}/rancher/v2.6/en/backups/docker-installs). Although you don't have any data you need to back up right now, we recommend creating backups after regular Rancher use. -- Create a Kubernetes cluster: [Provisioning Kubernetes Clusters]({{}}/rancher/v2.6/en/cluster-provisioning/). diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-rollbacks/single-node-rollbacks.md b/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-rollbacks/single-node-rollbacks.md deleted file mode 100644 index 00e4e1bd25b..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-rollbacks/single-node-rollbacks.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Rolling Back Rancher Installed with Docker -weight: 1015 ---- - -If a Rancher upgrade does not complete successfully, you'll have to roll back to your Rancher setup that you were using before [Docker Upgrade]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-upgrades). Rolling back restores: - -- Your previous version of Rancher. -- Your data backup created before upgrade. - -## Before You Start - -During rollback to a prior version of Rancher, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). Here's an example of a command with a placeholder: - -``` -docker pull rancher/rancher: -``` - -In this command, `` is the version of Rancher you were running before your unsuccessful upgrade. `v2.0.5` for example. - -Cross reference the image and reference table below to learn how to obtain this placeholder data. Write down or copy this information before starting the procedure below. - -Terminal docker ps Command, Displaying Where to Find <PRIOR_RANCHER_VERSION> and <RANCHER_CONTAINER_NAME>![Placeholder Reference]({{}}/img/rancher/placeholder-ref-2.png) - -| Placeholder | Example | Description | -| -------------------------- | -------------------------- | ------------------------------------------------------- | -| `` | `v2.0.5` | The rancher/rancher image you used before upgrade. | -| `` | `festive_mestorf` | The name of your Rancher container. | -| `` | `v2.0.5` | The version of Rancher that the backup is for. | -| `` | `9-27-18` | The date that the data container or backup was created. | -
- -You can obtain `` and `` by logging into your Rancher Server by remote connection and entering the command to view the containers that are running: `docker ps`. You can also view containers that are stopped using a different command: `docker ps -a`. Use these commands for help anytime during while creating backups. - -## Rolling Back Rancher - -If you have issues upgrading Rancher, roll it back to its latest known healthy state by pulling the last version you used and then restoring the backup you made before upgrade. - ->**Warning!** Rolling back to a previous version of Rancher destroys any changes made to Rancher following the upgrade. Unrecoverable data loss may occur. - -1. Using a remote Terminal connection, log into the node running your Rancher Server. - -1. Pull the version of Rancher that you were running before upgrade. Replace the `` with that version. - - For example, if you were running Rancher v2.0.5 before upgrade, pull v2.0.5. - - ``` - docker pull rancher/rancher: - ``` - -1. Stop the container currently running Rancher Server. Replace `` with the name of your Rancher container. - - ``` - docker stop - ``` - You can obtain the name for your Rancher container by entering `docker ps`. - -1. Move the backup tarball that you created during completion of [Docker Upgrade]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-upgrades) onto your Rancher Server. Change to the directory that you moved it to. Enter `dir` to confirm that it's there. - - If you followed the naming convention we suggested in [Docker Upgrade]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-upgrades), it will have a name similar to (`rancher-data-backup--.tar.gz`). - -1. Run the following command to replace the data in the `rancher-data` container with the data in the backup tarball, replacing the placeholder. Don't forget to close the quotes. - - ``` - docker run --volumes-from rancher-data \ - -v $PWD:/backup busybox sh -c "rm /var/lib/rancher/* -rf \ - && tar zxvf /backup/rancher-data-backup--.tar.gz" - ``` - -1. Start a new Rancher Server container with the `` tag placeholder pointing to the data container. - ``` - docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher: - ``` - Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - - >**Note:** _Do not_ stop the rollback after initiating it, even if the rollback process seems longer than expected. Stopping the rollback may result in database issues during future upgrades. - -1. Wait a few moments and then open Rancher in a web browser. Confirm that the rollback succeeded and that your data is restored. - -**Result:** Rancher is rolled back to its version and data state before upgrade. diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md b/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md deleted file mode 100644 index dcd9d02587b..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md +++ /dev/null @@ -1,375 +0,0 @@ ---- -title: Upgrading Rancher Installed with Docker -weight: 1010 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -The following instructions will guide you through upgrading a Rancher server that was installed with Docker. - -> **Docker installs are not supported in production environments.** These instructions are provided for testing and development purposes only. If you have already deployed a Docker install in production and need to upgrade to a new Rancher version, we recommend [migrating to the Helm chart install]({{}}/rancher/v2.6/en/backups/migrating-rancher/) before upgrading. - -# Prerequisites - -- **Review the [known upgrade issues]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/upgrades/#known-upgrade-issues)** section in the Rancher documentation for the most noteworthy issues to consider when upgrading Rancher. A more complete list of known issues for each Rancher version can be found in the release notes on [GitHub](https://github.com/rancher/rancher/releases) and on the [Rancher forums](https://forums.rancher.com/c/announcements/12). Note that upgrades to or from any chart in the [rancher-alpha repository]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#helm-chart-repositories/) aren’t supported. -- **For [air gap installs only,]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) collect and populate images for the new Rancher server version**. Follow the guide to [populate your private registry]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry/) with the images for the Rancher version that you want to upgrade to. - -# Placeholder Review - -During upgrade, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). - -Here's an **example** of a command with a placeholder: - -``` -docker stop -``` - -In this command, `` is the name of your Rancher container. - -# Get Data for Upgrade Commands - -To obtain the data to replace the placeholders, run: - -``` -docker ps -``` - -Write down or copy this information before starting the upgrade. - -Terminal docker ps Command, Displaying Where to Find <RANCHER_CONTAINER_TAG> and <RANCHER_CONTAINER_NAME> - -![Placeholder Reference]({{}}/img/rancher/placeholder-ref.png) - -| Placeholder | Example | Description | -| -------------------------- | -------------------------- | --------------------------------------------------------- | -| `` | `v2.1.3` | The rancher/rancher image you pulled for initial install. | -| `` | `festive_mestorf` | The name of your Rancher container. | -| `` | `v2.1.3` | The version of Rancher that you're creating a backup for. | -| `` | `2018-12-19` | The date that the data container or backup was created. | -
- -You can obtain `` and `` by logging into your Rancher server by remote connection and entering the command to view the containers that are running: `docker ps`. You can also view containers that are stopped using a different command: `docker ps -a`. Use these commands for help anytime during while creating backups. - -# Upgrade Outline - -During upgrade, you create a copy of the data from your current Rancher container and a backup in case something goes wrong. Then you deploy the new version of Rancher in a new container using your existing data. Follow the steps to upgrade Rancher server: - -- [1. Create a copy of the data from your Rancher server container](#1-create-a-copy-of-the-data-from-your-rancher-server-container) -- [2. Create a backup tarball](#2-create-a-backup-tarball) -- [3. Pull the new Docker image](#3-pull-the-new-docker-image) -- [4. Start the new Rancher server container](#4-start-the-new-rancher-server-container) -- [5. Verify the Upgrade](#5-verify-the-upgrade) -- [6. Clean up your old Rancher server container](#6-clean-up-your-old-rancher-server-container) - -# 1. Create a copy of the data from your Rancher server container - -1. Using a remote Terminal connection, log into the node running your Rancher server. - -1. Stop the container currently running Rancher server. Replace `` with the name of your Rancher container. - - ``` - docker stop - ``` - -1. Use the command below, replacing each placeholder, to create a data container from the Rancher container that you just stopped. - - ``` - docker create --volumes-from --name rancher-data rancher/rancher: - ``` - -# 2. Create a backup tarball - -1. From the data container that you just created (rancher-data), create a backup tarball (rancher-data-backup-<RANCHER_VERSION>-<DATE>.tar.gz). - - This tarball will serve as a rollback point if something goes wrong during upgrade. Use the following command, replacing each placeholder. - - - ``` - docker run --volumes-from rancher-data -v "$PWD:/backup" --rm busybox tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher - ``` - - **Step Result:** When you enter this command, a series of commands should run. - -1. Enter the `ls` command to confirm that the backup tarball was created. It will have a name similar to `rancher-data-backup--.tar.gz`. - - ``` - [rancher@ip-10-0-0-50 ~]$ ls - rancher-data-backup-v2.1.3-20181219.tar.gz - ``` - -1. Move your backup tarball to a safe location external from your Rancher server. - -# 3. Pull the New Docker Image - -Pull the image of the Rancher version that you want to upgrade to. - -Placeholder | Description -------------|------------- -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. - -``` -docker pull rancher/rancher: -``` - -# 4. Start the New Rancher Server Container - -Start a new Rancher server container using the data from the `rancher-data` container. Remember to pass in all the environment variables that you had used when you started the original container. - ->**Important:** _Do not_ stop the upgrade after initiating it, even if the upgrade process seems longer than expected. Stopping the upgrade may result in database migration errors during future upgrades. - -If you used a proxy, see [HTTP Proxy Configuration.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/proxy/) - -If you configured a custom CA root certificate to access your services, see [Custom CA root certificate.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#custom-ca-certificate) - -If you are recording all transactions with the Rancher API, see [API Auditing]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#api-audit-log) - -To see the command to use when starting the new Rancher server container, choose from the following options: - -- Docker Upgrade -- Docker Upgrade for Air Gap Installs - - - - -Select which option you had installed Rancher server - -### Option A: Default Self-Signed Certificate - -
- Click to expand - -If you have selected to use the Rancher generated self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container. - -Placeholder | Description -------------|------------- -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. - -``` -docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher: -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -
- -### Option B: Bring Your Own Certificate: Self-Signed - -
- Click to expand - -If you have selected to bring your own self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificate that you had originally installed with. - ->**Reminder of the Cert Prerequisite:** The certificate files must be in PEM format. In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. - -Placeholder | Description -------------|------------- - `` | The path to the directory containing your certificate files. -`` | The path to your full certificate chain. -`` | The path to the private key for your certificate. -`` | The path to the certificate authority's certificate. -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. - -``` -docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - -v //:/etc/rancher/ssl/cacerts.pem \ - --privileged \ - rancher/rancher: -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -
- -### Option C: Bring Your Own Certificate: Signed by Recognized CA - -
- Click to expand - -If you have selected to use a certificate signed by a recognized CA, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificates that you had originally installed with. Remember to include `--no-cacerts` as an argument to the container to disable the default CA certificate generated by Rancher. - ->**Reminder of the Cert Prerequisite:** The certificate files must be in PEM format. In your certificate file, include all intermediate certificates provided by the recognized CA. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -Placeholder | Description -------------|------------- -`` | The path to the directory containing your certificate files. -`` | The path to your full certificate chain. -`` | The path to the private key for your certificate. -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. - -``` -docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - --privileged \ - rancher/rancher: \ - --no-cacerts -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) -
- -### Option D: Let's Encrypt Certificate - -
- Click to expand - ->**Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/). - -If you have selected to use [Let's Encrypt](https://letsencrypt.org/) certificates, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to provide the domain that you had used when you originally installed Rancher. - ->**Reminder of the Cert Prerequisites:** -> ->- Create a record in your DNS that binds your Linux host IP address to the hostname that you want to use for Rancher access (`rancher.mydomain.com` for example). ->- Open port `TCP/80` on your Linux host. The Let's Encrypt http-01 challenge can come from any source IP address, so port `TCP/80` must be open to all IP addresses. - -Placeholder | Description -------------|------------- -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. -`` | The domain address that you had originally started with - -``` -docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher: \ - --acme-domain -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -
- - - - -For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster. - -When starting the new Rancher server container, choose from the following options: - -### Option A: Default Self-Signed Certificate - -
- Click to expand - -If you have selected to use the Rancher generated self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container. - -Placeholder | Description -------------|------------- -`` | Your private registry URL and port. -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to to upgrade to. - -``` - docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ # Set a default private registry to be used in Rancher - -e CATTLE_SYSTEM_CATALOG=bundled \ # Use the packaged Rancher system charts - --privileged \ - /rancher/rancher: -``` - -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -
- -### Option B: Bring Your Own Certificate: Self-Signed - -
- Click to expand - -If you have selected to bring your own self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificate that you had originally installed with. - ->**Reminder of the Prerequisite:** The certificate files must be in PEM format. In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -Placeholder | Description -------------|------------- -`` | The path to the directory containing your certificate files. -`` | The path to your full certificate chain. -`` | The path to the private key for your certificate. -`` | The path to the certificate authority's certificate. -`` | Your private registry URL and port. -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - -v //:/etc/rancher/ssl/cacerts.pem \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ # Set a default private registry to be used in Rancher - -e CATTLE_SYSTEM_CATALOG=bundled \ # Use the packaged Rancher system charts - --privileged \ - /rancher/rancher: -``` -Privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -
- -### Option C: Bring Your Own Certificate: Signed by Recognized CA - -
- Click to expand - -If you have selected to use a certificate signed by a recognized CA, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificates that you had originally installed with. - - >**Reminder of the Prerequisite:** The certificate files must be in PEM format. In your certificate file, include all intermediate certificates provided by the recognized CA. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -Placeholder | Description -------------|------------- -`` | The path to the directory containing your certificate files. -`` | The path to your full certificate chain. -`` | The path to the private key for your certificate. -`` | Your private registry URL and port. -`` | The release tag of the [Rancher version]({{}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to upgrade to. - -> **Note:** Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher. - -``` -docker run -d --volumes-from rancher-data \ - --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --no-cacerts \ - -v //:/etc/rancher/ssl/cert.pem \ - -v //:/etc/rancher/ssl/key.pem \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ # Set a default private registry to be used in Rancher - -e CATTLE_SYSTEM_CATALOG=bundled \ # Use the packaged Rancher system charts - --privileged - /rancher/rancher: -``` -privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher) - -
- - - - -**Result:** You have upgraded Rancher. Data from your upgraded server is now saved to the `rancher-data` container for use in future upgrades. - -# 5. Verify the Upgrade - -Log into Rancher. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window. - ->**Having network issues in your user clusters following upgrade?** -> -> See [Restoring Cluster Networking]({{}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration). - - -# 6. Clean up Your Old Rancher Server Container - -Remove the previous Rancher server container. If you only stop the previous Rancher server container (and don't remove it), the container may restart after the next server reboot. - -# Rolling Back - -If your upgrade does not complete successfully, you can roll back Rancher server and its data back to its last healthy state. For more information, see [Docker Rollback]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-rollbacks/). diff --git a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/troubleshooting/troubleshooting.md b/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/troubleshooting/troubleshooting.md deleted file mode 100644 index 9a1fc02ee8d..00000000000 --- a/versioned_docs/version-2.6/installation/other-installation-methods/single-node-docker/troubleshooting/troubleshooting.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: Certificate Troubleshooting -weight: 4 ---- -### How Do I Know if My Certificates are in PEM Format? - -You can recognize the PEM format by the following traits: - -- The file begins with the following header: - ``` - -----BEGIN CERTIFICATE----- - ``` -- The header is followed by a long string of characters. -- The file ends with a footer: - -----END CERTIFICATE----- - -PEM Certificate Example: - -``` -----BEGIN CERTIFICATE----- -MIIGVDCCBDygAwIBAgIJAMiIrEm29kRLMA0GCSqGSIb3DQEBCwUAMHkxCzAJBgNV -... more lines -VWQqljhfacYPgp8KJUJENQ9h5hZ2nSCrI+W00Jcw4QcEdCI8HL5wmg== ------END CERTIFICATE----- -``` - -PEM Certificate Key Example: - -``` ------BEGIN RSA PRIVATE KEY----- -MIIGVDCCBDygAwIBAgIJAMiIrEm29kRLMA0GCSqGSIb3DQEBCwUAMHkxCzAJBgNV -... more lines -VWQqljhfacYPgp8KJUJENQ9h5hZ2nSCrI+W00Jcw4QcEdCI8HL5wmg== ------END RSA PRIVATE KEY----- -``` - -If your key looks like the example below, see [Converting a Certificate Key From PKCS8 to PKCS1.](#converting-a-certificate-key-from-pkcs8-to-pkcs1) - -``` ------BEGIN PRIVATE KEY----- -MIIGVDCCBDygAwIBAgIJAMiIrEm29kRLMA0GCSqGSIb3DQEBCwUAMHkxCzAJBgNV -... more lines -VWQqljhfacYPgp8KJUJENQ9h5hZ2nSCrI+W00Jcw4QcEdCI8HL5wmg== ------END PRIVATE KEY----- -``` - -### Converting a Certificate Key From PKCS8 to PKCS1 - -If you are using a PKCS8 certificate key file, Rancher will log the following line: - -``` -ListenConfigController cli-config [listener] failed with : failed to read private key: asn1: structure error: tags don't match (2 vs {class:0 tag:16 length:13 isCompound:true}) -``` - -To make this work, you will need to convert the key from PKCS8 to PKCS1 using the command below: - -``` -openssl rsa -in key.pem -out convertedkey.pem -``` - -You can now use `convertedkey.pem` as certificate key file for Rancher. - -### What is the Order of Certificates if I Want to Add My Intermediate(s)? - -The order of adding certificates is as follows: - -``` ------BEGIN CERTIFICATE----- -%YOUR_CERTIFICATE% ------END CERTIFICATE----- ------BEGIN CERTIFICATE----- -%YOUR_INTERMEDIATE_CERTIFICATE% ------END CERTIFICATE----- -``` - -### How Do I Validate My Certificate Chain? - -You can validate the certificate chain by using the `openssl` binary. If the output of the command (see the command example below) ends with `Verify return code: 0 (ok)`, your certificate chain is valid. The `ca.pem` file must be the same as you added to the `rancher/rancher` container. - -When using a certificate signed by a recognized Certificate Authority, you can omit the `-CAfile` parameter. - -Command: - -``` -openssl s_client -CAfile ca.pem -connect rancher.yourdomain.com:443 -... - Verify return code: 0 (ok) -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/requirements/dockershim/dockershim.md b/versioned_docs/version-2.6/installation/requirements/dockershim/dockershim.md deleted file mode 100644 index 610eb3233e8..00000000000 --- a/versioned_docs/version-2.6/installation/requirements/dockershim/dockershim.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Dockershim -weight: 300 ---- - -The Dockershim is the CRI compliant layer between the Kubelet and the Docker daemon. As part of the Kubernetes 1.20 release, the [deprecation of the in-tree Dockershim was announced](https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/). For more information on the deprecation and its timelines, see the [Kubernetes Dockershim Deprecation FAQ](https://kubernetes.io/blog/2020/12/02/dockershim-faq/#when-will-dockershim-be-removed). - -RKE clusters now support the external Dockershim to continue leveraging Docker as the CRI runtime. We now implement the upstream open source community external Dockershim announced by [Mirantis and Docker](https://www.mirantis.com/blog/mirantis-to-take-over-support-of-kubernetes-dockershim-2/) to ensure RKE clusters can continue to leverage Docker. - -To enable the external Dockershim, configure the following option. - -``` -enable_cri_dockerd: true -``` - -For users looking to use another container runtime, Rancher has the edge-focused K3s and datacenter-focused RKE2 Kubernetes distributions that use containerd as the default runtime. Imported RKE2 and K3s Kubernetes clusters can then be upgraded and managed through Rancher going forward. - -### FAQ - -
- -Q. Do I have to upgrade Rancher to get Rancher’s support of the upstream Dockershim? - -A The upstream support of Dockershim begins for RKE in Kubernetes 1.21. You will need to be on a version of Rancher that supports RKE 1.21. See our support matrix for details. - -
- -Q. I am currently on RKE with Kubernetes 1.20. Do I need to upgrade to RKE with Kubernetes 1.21 sooner to avoid being out of support for Dockershim? - -A. The version of Dockershim in RKE with Kubernetes 1.20 will continue to work and it is not deprecated until a later release. For information on the timeline, see the [Kubernetes Dockershim Deprecation FAQ](https://kubernetes.io/blog/2020/12/02/dockershim-faq/#when-will-dockershim-be-removed). It will only emit a warning of its future deprecation, which Rancher has mitigated in RKE with Kubernetes 1.21. You can plan your upgrade to 1.21 as you would normally. - -
- -Q: What are my other options if I don’t want to depend on the Dockershim? - -A: You can use a runtime like containerd with Kubernetes that does not require Dockershim support. RKE2 or K3s are two options for doing this. - -
- -Q: If I am already using RKE1 and want to switch to RKE2, what are my migration options? - -A: Today, you can stand up a new cluster and migrate workloads to a new RKE2 cluster that uses containerd. Rancher is exploring the possibility of an in-place upgrade path. - -
diff --git a/versioned_docs/version-2.6/installation/requirements/installing-docker/installing-docker.md b/versioned_docs/version-2.6/installation/requirements/installing-docker/installing-docker.md deleted file mode 100644 index 8b16d157505..00000000000 --- a/versioned_docs/version-2.6/installation/requirements/installing-docker/installing-docker.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Installing Docker -weight: 1 ---- - -Docker is required to be installed on nodes where the Rancher server will be installed with Helm or Docker. - -There are a couple of options for installing Docker. One option is to refer to the [official Docker documentation](https://docs.docker.com/install/) about how to install Docker on Linux. The steps will vary based on the Linux distribution. - -Another option is to use one of Rancher's Docker installation scripts, which are available for most recent versions of Docker. - -For example, this command could be used to install Docker 20.10 on Ubuntu: - -``` -curl https://releases.rancher.com/install-docker/20.10.sh | sh -``` - -Rancher has installation scripts for every version of upstream Docker that Kubernetes supports. To find out whether a script is available for installing a certain Docker version, refer to this [GitHub repository,](https://github.com/rancher/install-docker) which contains all of Rancher's Docker installation scripts. diff --git a/versioned_docs/version-2.6/installation/requirements/ports/common-ports-table/index.md b/versioned_docs/version-2.6/installation/requirements/ports/common-ports-table/index.md deleted file mode 100644 index d8cce1a548f..00000000000 --- a/versioned_docs/version-2.6/installation/requirements/ports/common-ports-table/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -headless: true ---- -| Protocol | Port | Description | -|:--------: |:----------------: |---------------------------------------------------------------------------------- | -| TCP | 22 | Node driver SSH provisioning | -| TCP | 179 | Calico BGP Port | -| TCP | 2376 | Node driver Docker daemon TLS port | -| TCP | 2379 | etcd client requests | -| TCP | 2380 | etcd peer communication | -| UDP | 8472 | Canal/Flannel VXLAN overlay networking | -| UDP | 4789 | Flannel VXLAN overlay networking on Windows cluster | -| TCP | 8443 | Rancher webhook | -| TCP | 9099 | Canal/Flannel livenessProbe/readinessProbe | -| TCP | 9100 | Default port required by Monitoring to scrape metrics from Linux node-exporters | -| TCP | 9443 | Rancher webhook | -| TCP | 9796 | Default port required by Monitoring to scrape metrics from Windows node-exporters | -| TCP | 6783 | Weave Port | -| UDP | 6783-6784 | Weave UDP Ports | -| TCP | 10250 | Metrics server communication with all nodes API | -| TCP | 10254 | Ingress controller livenessProbe/readinessProbe | -| TCP/UDP | 30000-32767 | NodePort port range | diff --git a/versioned_docs/version-2.6/installation/requirements/ports/ports.md b/versioned_docs/version-2.6/installation/requirements/ports/ports.md deleted file mode 100644 index efc5c827e9e..00000000000 --- a/versioned_docs/version-2.6/installation/requirements/ports/ports.md +++ /dev/null @@ -1,335 +0,0 @@ ---- -title: Port Requirements -description: Read about port requirements needed in order for Rancher to operate properly, both for Rancher nodes and downstream Kubernetes cluster nodes -weight: 300 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -To operate properly, Rancher requires a number of ports to be open on Rancher nodes and on downstream Kubernetes cluster nodes. - -- [Rancher Nodes](#rancher-nodes) - - [Ports for Rancher Server Nodes on K3s](#ports-for-rancher-server-nodes-on-k3s) - - [Ports for Rancher Server Nodes on RKE](#ports-for-rancher-server-nodes-on-rke) - - [Ports for Rancher Server Nodes on RKE2](#ports-for-rancher-server-nodes-on-rke2) - - [Ports for Rancher Server in Docker](#ports-for-rancher-server-in-docker) -- [Downstream Kubernetes Cluster Nodes](#downstream-kubernetes-cluster-nodes) - - [Ports for Rancher Launched Kubernetes Clusters using Node Pools](#ports-for-rancher-launched-kubernetes-clusters-using-node-pools) - - [Ports for Rancher Launched Kubernetes Clusters using Custom Nodes](#ports-for-rancher-launched-kubernetes-clusters-using-custom-nodes) - - [Ports for Hosted Kubernetes Clusters](#ports-for-hosted-kubernetes-clusters) - - [Ports for Registered Clusters](#ports-for-registered-clusters) -- [Other Port Considerations](#other-port-considerations) - - [Commonly Used Ports](#commonly-used-ports) - - [Local Node Traffic](#local-node-traffic) - - [Rancher AWS EC2 Security Group](#rancher-aws-ec2-security-group) - - [Opening SUSE Linux Ports](#opening-suse-linux-ports) - -# Rancher Nodes - -The following table lists the ports that need to be open to and from nodes that are running the Rancher server. - -The port requirements differ based on the Rancher server architecture. - -Rancher can be installed on any Kubernetes cluster. For Rancher installs on a K3s, RKE, or RKE2 Kubernetes cluster, refer to the tabs below. For other Kubernetes distributions, refer to the distribution's documentation for the port requirements for cluster nodes. - -> **Notes:** -> -> - Rancher nodes may also require additional outbound access for any external authentication provider which is configured (LDAP for example). -> - Kubernetes recommends TCP 30000-32767 for node port services. -> - For firewalls, traffic may need to be enabled within the cluster and pod CIDR. -> - Rancher nodes may also need outbound access to an external S3 location which is used for storing cluster backups (Minio for example). - -### Ports for Rancher Server Nodes on K3s - -
- Click to expand - -The K3s server needs port 6443 to be accessible by the nodes. - -The nodes need to be able to reach other nodes over UDP port 8472 when Flannel VXLAN is used. The node should not listen on any other port. K3s uses reverse tunneling such that the nodes make outbound connections to the server and all kubelet traffic runs through that tunnel. However, if you do not use Flannel and provide your own custom CNI, then port 8472 is not needed by K3s. - -If you wish to utilize the metrics server, you will need to open port 10250 on each node. - -> **Important:** The VXLAN port on nodes should not be exposed to the world as it opens up your cluster network to be accessed by anyone. Run your nodes behind a firewall/security group that disables access to port 8472. - -The following tables break down the port requirements for inbound and outbound traffic: - -
Inbound Rules for Rancher Server Nodes
- -| Protocol | Port | Source | Description -|-----|-----|----------------|---| -| TCP | 80 | Load balancer/proxy that does external SSL termination | Rancher UI/API when external SSL termination is used | -| TCP | 443 |
  • server nodes
  • agent nodes
  • hosted/registered Kubernetes
  • any source that needs to be able to use the Rancher UI or API
| Rancher agent, Rancher UI/API, kubectl | -| TCP | 6443 | K3s server nodes | Kubernetes API -| UDP | 8472 | K3s server and agent nodes | Required only for Flannel VXLAN. -| TCP | 10250 | K3s server and agent nodes | kubelet - -
Outbound Rules for Rancher Nodes
- -| Protocol | Port | Destination | Description | -| -------- | ---- | -------------------------------------------------------- | --------------------------------------------- | -| TCP | 22 | Any node IP from a node created using Node Driver | SSH provisioning of nodes using Node Driver | -| TCP | 443 | git.rancher.io | Rancher catalog | -| TCP | 2376 | Any node IP from a node created using Node driver | Docker daemon TLS port used by Docker Machine | -| TCP | 6443 | Hosted/Imported Kubernetes API | Kubernetes API server | - -
- -### Ports for Rancher Server Nodes on RKE - -
- Click to expand - -Typically Rancher is installed on three RKE nodes that all have the etcd, control plane and worker roles. - -The following tables break down the port requirements for traffic between the Rancher nodes: - -
Rules for traffic between Rancher nodes
- -| Protocol | Port | Description | -|-----|-----|----------------| -| TCP | 443 | Rancher agents | -| TCP | 2379 | etcd client requests | -| TCP | 2380 | etcd peer communication | -| TCP | 6443 | Kubernetes apiserver | -| TCP | 8443 | Nginx Ingress's Validating Webhook | -| UDP | 8472 | Canal/Flannel VXLAN overlay networking | -| TCP | 9099 | Canal/Flannel livenessProbe/readinessProbe | -| TCP | 10250 | Metrics server communication with all nodes | -| TCP | 10254 | Ingress controller livenessProbe/readinessProbe | - -The following tables break down the port requirements for inbound and outbound traffic: - -
Inbound Rules for Rancher Nodes
- -| Protocol | Port | Source | Description | -|-----|-----|----------------|---| -| TCP | 22 | RKE CLI | SSH provisioning of node by RKE | -| TCP | 80 | Load Balancer/Reverse Proxy | HTTP traffic to Rancher UI/API | -| TCP | 443 |
  • Load Balancer/Reverse Proxy
  • IPs of all cluster nodes and other API/UI clients
| HTTPS traffic to Rancher UI/API | -| TCP | 6443 | Kubernetes API clients | HTTPS traffic to Kubernetes API | - -
Outbound Rules for Rancher Nodes
- -| Protocol | Port | Destination | Description | -|-----|-----|----------------|---| -| TCP | 443 | `35.160.43.145`,`35.167.242.46`,`52.33.59.17` | Rancher catalog (git.rancher.io) | -| TCP | 22 | Any node created using a node driver | SSH provisioning of node by node driver | -| TCP | 2376 | Any node created using a node driver | Docker daemon TLS port used by node driver | -| TCP | 6443 | Hosted/Imported Kubernetes API | Kubernetes API server | -| TCP | Provider dependent | Port of the Kubernetes API endpoint in hosted cluster | Kubernetes API | - -
- -### Ports for Rancher Server Nodes on RKE2 - -
- Click to expand - -The RKE2 server needs port 6443 and 9345 to be accessible by other nodes in the cluster. - -All nodes need to be able to reach other nodes over UDP port 8472 when Flannel VXLAN is used. - -If you wish to utilize the metrics server, you will need to open port 10250 on each node. - -**Important:** The VXLAN port on nodes should not be exposed to the world as it opens up your cluster network to be accessed by anyone. Run your nodes behind a firewall/security group that disables access to port 8472. - -
Inbound Rules for RKE2 Server Nodes
- -| Protocol | Port | Source | Description -|-----|-----|----------------|---| -| TCP | 9345 | RKE2 agent nodes | Kubernetes API -| TCP | 6443 | RKE2 agent nodes | Kubernetes API -| UDP | 8472 | RKE2 server and agent nodes | Required only for Flannel VXLAN -| TCP | 10250 | RKE2 server and agent nodes | kubelet -| TCP | 2379 | RKE2 server nodes | etcd client port -| TCP | 2380 | RKE2 server nodes | etcd peer port -| TCP | 30000-32767 | RKE2 server and agent nodes | NodePort port range -| TCP | 5473 | Calico-node pod connecting to typha pod | Required when deploying with Calico -| HTTP | 8080 | Load balancer/proxy that does external SSL termination | Rancher UI/API when external SSL termination is used | -| HTTPS | 8443 |
  • hosted/registered Kubernetes
  • any source that needs to be able to use the Rancher UI or API
| Rancher agent, Rancher UI/API, kubectl. Not needed if you have LB doing TLS termination. | - -Typically all outbound traffic is allowed. - -
- -### Ports for Rancher Server in Docker - -
- Click to expand - -The following tables break down the port requirements for Rancher nodes, for inbound and outbound traffic: - -
Inbound Rules for Rancher Node
- -| Protocol | Port | Source | Description -|-----|-----|----------------|---| -| TCP | 80 | Load balancer/proxy that does external SSL termination | Rancher UI/API when external SSL termination is used -| TCP | 443 |
  • hosted/registered Kubernetes
  • any source that needs to be able to use the Rancher UI or API
| Rancher agent, Rancher UI/API, kubectl - -
Outbound Rules for Rancher Node
- -| Protocol | Port | Source | Description | -|-----|-----|----------------|---| -| TCP | 22 | Any node IP from a node created using Node Driver | SSH provisioning of nodes using Node Driver | -| TCP | 443 | git.rancher.io | Rancher catalog | -| TCP | 2376 | Any node IP from a node created using a node driver | Docker daemon TLS port used by Docker Machine | -| TCP | 6443 | Hosted/Imported Kubernetes API | Kubernetes API server | - -
- -# Downstream Kubernetes Cluster Nodes - -Downstream Kubernetes clusters run your apps and services. This section describes what ports need to be opened on the nodes in downstream clusters so that Rancher can communicate with them. - -The port requirements differ depending on how the downstream cluster was launched. Each of the tabs below list the ports that need to be opened for different [cluster types]({{}}/rancher/v2.6/en/cluster-provisioning/). - -The following diagram depicts the ports that are opened for each [cluster type]({{}}/rancher/v2.6/en/cluster-provisioning). - -
Port Requirements for the Rancher Management Plane
- -![Basic Port Requirements]({{}}/img/rancher/port-communications.svg) - ->**Tip:** -> ->If security isn't a large concern and you're okay with opening a few additional ports, you can use the table in [Commonly Used Ports](#commonly-used-ports) as your port reference instead of the comprehensive tables below. - -### Ports for Rancher Launched Kubernetes Clusters using Node Pools - -
- Click to expand - -The following table depicts the port requirements for [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) with nodes created in an [Infrastructure Provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/). - ->**Note:** ->The required ports are automatically opened by Rancher during creation of clusters in cloud providers like Amazon EC2 or DigitalOcean. - -{{< ports-iaas-nodes >}} - -
- -### Ports for Rancher Launched Kubernetes Clusters using Custom Nodes - -
- Click to expand - -The following table depicts the port requirements for [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) with [Custom Nodes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes/). - -{{< ports-custom-nodes >}} - -
- -### Ports for Hosted Kubernetes Clusters - -
- Click to expand - -The following table depicts the port requirements for [hosted clusters]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters). - -{{< ports-imported-hosted >}} - -
- -### Ports for Registered Clusters - -Note: Registered clusters were called imported clusters before Rancher v2.5. - -
- Click to expand - -The following table depicts the port requirements for [registered clusters]({{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/). - -{{< ports-imported-hosted >}} - -
- - -# Other Port Considerations - -### Commonly Used Ports - -These ports are typically opened on your Kubernetes nodes, regardless of what type of cluster it is. - -import CommonPortsTable from '/rancher/v2.6/en/shared-files/_common-ports-table.md'; - - - ----- - -### Local Node Traffic - -Ports marked as `local traffic` (i.e., `9099 TCP`) in the above requirements are used for Kubernetes healthchecks (`livenessProbe` and`readinessProbe`). -These healthchecks are executed on the node itself. In most cloud environments, this local traffic is allowed by default. - -However, this traffic may be blocked when: - -- You have applied strict host firewall policies on the node. -- You are using nodes that have multiple interfaces (multihomed). - -In these cases, you have to explicitly allow this traffic in your host firewall, or in case of public/private cloud hosted machines (i.e. AWS or OpenStack), in your security group configuration. Keep in mind that when using a security group as source or destination in your security group, explicitly opening ports only applies to the private interface of the nodes / instances. - -### Rancher AWS EC2 Security Group - -When using the [AWS EC2 node driver]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/) to provision cluster nodes in Rancher, you can choose to let Rancher create a security group called `rancher-nodes`. The following rules are automatically added to this security group. - -| Type | Protocol | Port Range | Source/Destination | Rule Type | -|-----------------|:--------:|:-----------:|------------------------|:---------:| -| SSH | TCP | 22 | 0.0.0.0/0 | Inbound | -| HTTP | TCP | 80 | 0.0.0.0/0 | Inbound | -| Custom TCP Rule | TCP | 443 | 0.0.0.0/0 | Inbound | -| Custom TCP Rule | TCP | 2376 | 0.0.0.0/0 | Inbound | -| Custom TCP Rule | TCP | 2379-2380 | sg-xxx (rancher-nodes) | Inbound | -| Custom UDP Rule | UDP | 4789 | sg-xxx (rancher-nodes) | Inbound | -| Custom TCP Rule | TCP | 6443 | 0.0.0.0/0 | Inbound | -| Custom UDP Rule | UDP | 8472 | sg-xxx (rancher-nodes) | Inbound | -| Custom TCP Rule | TCP | 10250-10252 | sg-xxx (rancher-nodes) | Inbound | -| Custom TCP Rule | TCP | 10256 | sg-xxx (rancher-nodes) | Inbound | -| Custom TCP Rule | TCP | 30000-32767 | 0.0.0.0/0 | Inbound | -| Custom UDP Rule | UDP | 30000-32767 | 0.0.0.0/0 | Inbound | -| All traffic | All | All | 0.0.0.0/0 | Outbound | - -### Opening SUSE Linux Ports - -SUSE Linux may have a firewall that blocks all ports by default. To open the ports needed for adding the host to a custom cluster, - - - - -1. SSH into the instance. -1. Start YaST in text mode: -``` -sudo yast2 -``` - -1. Navigate to **Security and Users** > **Firewall** > **Zones:public** > **Ports**. To navigate within the interface, follow the instructions [here](https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha-yast-text.html#sec-yast-cli-navigate). -1. To open the required ports, enter them into the **TCP Ports** and **UDP Ports** fields. In this example, ports 9796 and 10250 are also opened for monitoring. The resulting fields should look similar to the following: -```yaml -TCP Ports -22, 80, 443, 2376, 2379, 2380, 6443, 9099, 9796, 10250, 10254, 30000-32767 -UDP Ports -8472, 30000-32767 -``` - -1. When all required ports are enter, select **Accept**. - - - - - -1. SSH into the instance. -1. Edit /`etc/sysconfig/SuSEfirewall2` and open the required ports. In this example, ports 9796 and 10250 are also opened for monitoring: - ``` - FW_SERVICES_EXT_TCP="22 80 443 2376 2379 2380 6443 9099 9796 10250 10254 30000:32767" - FW_SERVICES_EXT_UDP="8472 30000:32767" - FW_ROUTE=yes - ``` -1. Restart the firewall with the new ports: - ``` - SuSEfirewall2 - ``` - - - - -**Result:** The node has the open ports required to be added to a custom cluster. diff --git a/versioned_docs/version-2.6/installation/requirements/requirements.md b/versioned_docs/version-2.6/installation/requirements/requirements.md deleted file mode 100644 index affe086b066..00000000000 --- a/versioned_docs/version-2.6/installation/requirements/requirements.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -title: Installation Requirements -description: Learn the node requirements for each node running Rancher server when you’re configuring Rancher to run either in a Docker or Kubernetes setup -weight: 1 ---- - -This page describes the software, hardware, and networking requirements for the nodes where the Rancher server will be installed. The Rancher server can be installed on a single node or a high-availability Kubernetes cluster. - -> It is important to note that if you install Rancher on a Kubernetes cluster, requirements are different from the [node requirements for downstream user clusters,]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/) which will run your apps and services. - -Make sure the node(s) for the Rancher server fulfill the following requirements: - -- [Operating Systems and Container Runtime Requirements](#operating-systems-and-container-runtime-requirements) - - [RKE Specific Requirements](#rke-specific-requirements) - - [K3s Specific Requirements](#k3s-specific-requirements) - - [RKE2 Specific Requirements](#rke2-specific-requirements) - - [Installing Docker](#installing-docker) -- [Hardware Requirements](#hardware-requirements) -- [CPU and Memory](#cpu-and-memory) - - [RKE and Hosted Kubernetes](#rke-and-hosted-kubernetes) - - [K3s Kubernetes](#k3s-kubernetes) - - [RKE2 Kubernetes](#rke2-kubernetes) - - [Docker](#docker) -- [Ingress](#ingress) - - [Ingress for RKE2](#ingress-for-rke2) - - [Ingress for EKS](#ingress-for-eks) -- [Disks](#disks) -- [Networking Requirements](#networking-requirements) - - [Node IP Addresses](#node-ip-addresses) - - [Port Requirements](#port-requirements) -- [Dockershim Support](#dockershim-support) - -For a list of best practices that we recommend for running the Rancher server in production, refer to the [best practices section.]({{}}/rancher/v2.6/en/best-practices/rancher-server/deployment-types/) - -The Rancher UI works best in Firefox or Chrome. - -# Operating Systems and Container Runtime Requirements - -Rancher should work with any modern Linux distribution. - -Docker is required for nodes that will run RKE Kubernetes clusters. It is not required for Kubernetes installs. - -Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) - -For details on which OS and Docker versions were tested with each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) - -All supported operating systems are 64-bit x86. - -The `ntp` (Network Time Protocol) package should be installed. This prevents errors with certificate validation that can occur when the time is not synchronized between the client and server. - -Some distributions of Linux may have default firewall rules that block communication with Helm. We recommend disabling firewalld. For Kubernetes v1.19, v1.20 and v1.21, firewalld must be turned off. - -If you don't feel comfortable doing so you might check suggestions in the [respective issue](https://github.com/rancher/rancher/issues/28840). Some users were successful [creating a separate firewalld zone with a policy of ACCEPT for the Pod CIDR](https://github.com/rancher/rancher/issues/28840#issuecomment-787404822). - -If you plan to run Rancher on ARM64, see [Running on ARM64 (Experimental).]({{}}/rancher/v2.6/en/installation/resources/advanced/arm64-platform/) - -### RKE Specific Requirements - -For the container runtime, RKE should work with any modern Docker version. - -Note that the following sysctl setting must be applied: - -``` -net.bridge.bridge-nf-call-iptables=1 -``` - -### K3s Specific Requirements - -For the container runtime, K3s should work with any modern version of Docker or containerd. - -Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script. - -If you are installing Rancher on a K3s cluster with **Raspbian Buster**, follow [these steps]({{}}/k3s/latest/en/advanced/#enabling-legacy-iptables-on-raspbian-buster) to switch to legacy iptables. - -If you are installing Rancher on a K3s cluster with Alpine Linux, follow [these steps]({{}}/k3s/latest/en/advanced/#additional-preparation-for-alpine-linux-setup) for additional setup. - - - -### RKE2 Specific Requirements - -For details on which OS versions were tested with RKE2, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) - -Docker is not required for RKE2 installs. - -### Installing Docker - -Docker is required for Helm chart installs, and it can be installed by following the steps in the official [Docker documentation.](https://docs.docker.com/) Rancher also provides [scripts]({{}}/rancher/v2.6/en/installation/requirements/installing-docker) to install Docker with one command. - -# Hardware Requirements - -The following sections describe the CPU, memory, and disk requirements for the nodes where the Rancher server is installed. - -# CPU and Memory - -Hardware requirements scale based on the size of your Rancher deployment. Provision each individual node according to the requirements. The requirements are different depending on if you are installing Rancher in a single container with Docker, or if you are installing Rancher on a Kubernetes cluster. - -### RKE and Hosted Kubernetes - -These CPU and memory requirements apply to each host in the Kubernetes cluster where the Rancher server is installed. - -These requirements apply to RKE Kubernetes clusters, as well as to hosted Kubernetes clusters such as EKS. - -| Deployment Size | Clusters | Nodes | vCPUs | RAM | -| --------------- | ---------- | ------------ | -------| ------- | -| Small | Up to 150 | Up to 1500 | 2 | 8 GB | -| Medium | Up to 300 | Up to 3000 | 4 | 16 GB | -| Large | Up to 500 | Up to 5000 | 8 | 32 GB | -| X-Large | Up to 1000 | Up to 10,000 | 16 | 64 GB | -| XX-Large | Up to 2000 | Up to 20,000 | 32 | 128 GB | - -Every use case and environment is different. Please [contact Rancher](https://rancher.com/contact/) to review yours. - -### K3s Kubernetes - -These CPU and memory requirements apply to each host in a [K3s Kubernetes cluster where the Rancher server is installed.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) - -| Deployment Size | Clusters | Nodes | vCPUs | RAM | Database Size | -| --------------- | ---------- | ------------ | -------| ---------| ------------------------- | -| Small | Up to 150 | Up to 1500 | 2 | 8 GB | 2 cores, 4 GB + 1000 IOPS | -| Medium | Up to 300 | Up to 3000 | 4 | 16 GB | 2 cores, 4 GB + 1000 IOPS | -| Large | Up to 500 | Up to 5000 | 8 | 32 GB | 2 cores, 4 GB + 1000 IOPS | -| X-Large | Up to 1000 | Up to 10,000 | 16 | 64 GB | 2 cores, 4 GB + 1000 IOPS | -| XX-Large | Up to 2000 | Up to 20,000 | 32 | 128 GB | 2 cores, 4 GB + 1000 IOPS | - -Every use case and environment is different. Please [contact Rancher](https://rancher.com/contact/) to review yours. - - -### RKE2 Kubernetes - -These CPU and memory requirements apply to each instance with RKE2 installed. Minimum recommendations are outlined here. - -| Deployment Size | Clusters | Nodes | vCPUs | RAM | -| --------------- | -------- | --------- | ----- | ---- | -| Small | Up to 5 | Up to 50 | 2 | 5 GB | -| Medium | Up to 15 | Up to 200 | 3 | 9 GB | - -### Docker - -These CPU and memory requirements apply to a host with a [single-node]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker) installation of Rancher. - -| Deployment Size | Clusters | Nodes | vCPUs | RAM | -| --------------- | -------- | --------- | ----- | ---- | -| Small | Up to 5 | Up to 50 | 1 | 4 GB | -| Medium | Up to 15 | Up to 200 | 2 | 8 GB | - -# Ingress - -Each node in the Kubernetes cluster that Rancher is installed on should run an Ingress. - -The Ingress should be deployed as DaemonSet to ensure your load balancer can successfully route traffic to all nodes. - -For RKE and K3s installations, you don't have to install the Ingress manually because it is installed by default. - -For hosted Kubernetes clusters (EKS, GKE, AKS) and RKE2 Kubernetes installations, you will need to set up the ingress. - -### Ingress for EKS -For an example of how to deploy an nginx-ingress-controller with a LoadBalancer service, refer to [this section.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/amazon-eks/#5-install-an-ingress) - -# Disks - -Rancher performance depends on etcd in the cluster performance. To ensure optimal speed, we recommend always using SSD disks to back your Rancher management Kubernetes cluster. On cloud providers, you will also want to use the minimum size that allows the maximum IOPS. In larger clusters, consider using dedicated storage devices for etcd data and wal directories. - -# Networking Requirements - -This section describes the networking requirements for the node(s) where the Rancher server is installed. - -> If a server containing Rancher has the `X-Frame-Options=DENY` header, some pages in the new Rancher UI will not be able to render after upgrading from the legacy UI. This is because some legacy pages are embedded as iFrames in the new UI. - -### Node IP Addresses - -Each node used should have a static IP configured, regardless of whether you are installing Rancher on a single node or on an HA cluster. In case of DHCP, each node should have a DHCP reservation to make sure the node gets the same IP allocated. - -### Port Requirements - -To operate properly, Rancher requires a number of ports to be open on Rancher nodes and on downstream Kubernetes cluster nodes. [Port Requirements]({{}}/rancher/v2.6/en/installation/requirements/ports) lists all the necessary ports for Rancher and Downstream Clusters for the different cluster types. - -# Dockershim Support - -For more information on Dockershim support, refer to [this page]({{}}/rancher/v2.6/en/installation/requirements/dockershim/). diff --git a/versioned_docs/version-2.6/installation/resources/advanced/advanced.md b/versioned_docs/version-2.6/installation/resources/advanced/advanced.md deleted file mode 100644 index f5e42195535..00000000000 --- a/versioned_docs/version-2.6/installation/resources/advanced/advanced.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Advanced -weight: 1000 ---- - -The documents in this section contain resources for less common use cases. \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/resources/advanced/api-audit-log/api-audit-log.md b/versioned_docs/version-2.6/installation/resources/advanced/api-audit-log/api-audit-log.md deleted file mode 100644 index c1442bc14e5..00000000000 --- a/versioned_docs/version-2.6/installation/resources/advanced/api-audit-log/api-audit-log.md +++ /dev/null @@ -1,559 +0,0 @@ ---- -title: Enabling the API Audit Log to Record System Events -weight: 4 ---- - -You can enable the API audit log to record the sequence of system events initiated by individual users. You can know what happened, when it happened, who initiated it, and what cluster it affected. When you enable this feature, all requests to the Rancher API and all responses from it are written to a log. - -You can enable API Auditing during Rancher installation or upgrade. - -## Enabling API Audit Log - -The Audit Log is enabled and configured by passing environment variables to the Rancher server container. See the following to enable on your installation. - -- [Docker Install]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#api-audit-log) - -- [Kubernetes Install]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#api-audit-log) - -## API Audit Log Options - -The usage below defines rules about what the audit log should record and what data it should include: - -| Parameter | Description | -| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `AUDIT_LEVEL` | `0` - Disable audit log (default setting).
`1` - Log event metadata.
`2` - Log event metadata and request body.
`3` - Log event metadata, request body, and response body. Each log transaction for a request/response pair uses the same `auditID` value.

See [Audit Level Logging](#audit-log-levels) for a table that displays what each setting logs. | -| `AUDIT_LOG_PATH` | Log path for Rancher Server API. Default path is `/var/log/auditlog/rancher-api-audit.log`. You can mount the log directory to host.

Usage Example: `AUDIT_LOG_PATH=/my/custom/path/`
| -| `AUDIT_LOG_MAXAGE` | Defined the maximum number of days to retain old audit log files. Default is 10 days. | -| `AUDIT_LOG_MAXBACKUP` | Defines the maximum number of audit log files to retain. Default is 10. | -| `AUDIT_LOG_MAXSIZE` | Defines the maximum size in megabytes of the audit log file before it gets rotated. Default size is 100M. | - -
- -### Audit Log Levels - -The following table displays what parts of API transactions are logged for each [`AUDIT_LEVEL`](#audit-level) setting. - -| `AUDIT_LEVEL` Setting | Request Metadata | Request Body | Response Metadata | Response Body | -| --------------------- | ---------------- | ------------ | ----------------- | ------------- | -| `0` | | | | | -| `1` | ✓ | | | | -| `2` | ✓ | ✓ | | | -| `3` | ✓ | ✓ | ✓ | ✓ | - -## Viewing API Audit Logs - -### Docker Install - -Share the `AUDIT_LOG_PATH` directory (Default: `/var/log/auditlog`) with the host system. The log can be parsed by standard CLI tools or forwarded on to a log collection tool like Fluentd, Filebeat, Logstash, etc. - -### Kubernetes Install - -Enabling the API Audit Log with the Helm chart install will create a `rancher-audit-log` sidecar container in the Rancher pod. This container will stream the log to standard output (stdout). You can view the log as you would any container log. - -The `rancher-audit-log` container is part of the `rancher` pod in the `cattle-system` namespace. - -#### CLI - -```bash -kubectl -n cattle-system logs -f rancher-84d886bdbb-s4s69 rancher-audit-log -``` - -#### Shipping the Audit Log - -You can enable Rancher's built in log collection and shipping for the cluster to ship the audit and other services logs to a supported collection endpoint. See [Rancher Tools - Logging]({{}}/rancher/v2.6/en/logging) for details. - -## Audit Log Samples - -After you enable auditing, each API request or response is logged by Rancher in the form of JSON. Each of the following code samples provide examples of how to identify each API transaction. - -### Metadata Level - -If you set your `AUDIT_LEVEL` to `1`, Rancher logs the metadata header for every API request, but not the body. The header provides basic information about the API transaction, such as the transaction's ID, who initiated the transaction, the time it occurred, etc. - -```json -{ - "auditID": "30022177-9e2e-43d1-b0d0-06ef9d3db183", - "requestURI": "/v3/schemas", - "sourceIPs": ["::1"], - "user": { - "name": "user-f4tt2", - "group": ["system:authenticated"] - }, - "verb": "GET", - "stage": "RequestReceived", - "stageTimestamp": "2018-07-20 10:22:43 +0800" -} -``` - -### Metadata and Request Body Level - -If you set your `AUDIT_LEVEL` to `2`, Rancher logs the metadata header and body for every API request. - -The code sample below depicts an API request, with both its metadata header and body. - -```json -{ - "auditID": "ef1d249e-bfac-4fd0-a61f-cbdcad53b9bb", - "requestURI": "/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx", - "sourceIPs": ["::1"], - "user": { - "name": "user-f4tt2", - "group": ["system:authenticated"] - }, - "verb": "PUT", - "stage": "RequestReceived", - "stageTimestamp": "2018-07-20 10:28:08 +0800", - "requestBody": { - "hostIPC": false, - "hostNetwork": false, - "hostPID": false, - "paused": false, - "annotations": {}, - "baseType": "workload", - "containers": [ - { - "allowPrivilegeEscalation": false, - "image": "nginx", - "imagePullPolicy": "Always", - "initContainer": false, - "name": "nginx", - "ports": [ - { - "containerPort": 80, - "dnsName": "nginx-nodeport", - "kind": "NodePort", - "name": "80tcp01", - "protocol": "TCP", - "sourcePort": 0, - "type": "/v3/project/schemas/containerPort" - } - ], - "privileged": false, - "readOnly": false, - "resources": { - "type": "/v3/project/schemas/resourceRequirements", - "requests": {}, - "limits": {} - }, - "restartCount": 0, - "runAsNonRoot": false, - "stdin": true, - "stdinOnce": false, - "terminationMessagePath": "/dev/termination-log", - "terminationMessagePolicy": "File", - "tty": true, - "type": "/v3/project/schemas/container", - "environmentFrom": [], - "capAdd": [], - "capDrop": [], - "livenessProbe": null, - "volumeMounts": [] - } - ], - "created": "2018-07-18T07:34:16Z", - "createdTS": 1531899256000, - "creatorId": null, - "deploymentConfig": { - "maxSurge": 1, - "maxUnavailable": 0, - "minReadySeconds": 0, - "progressDeadlineSeconds": 600, - "revisionHistoryLimit": 10, - "strategy": "RollingUpdate" - }, - "deploymentStatus": { - "availableReplicas": 1, - "conditions": [ - { - "lastTransitionTime": "2018-07-18T07:34:38Z", - "lastTransitionTimeTS": 1531899278000, - "lastUpdateTime": "2018-07-18T07:34:38Z", - "lastUpdateTimeTS": 1531899278000, - "message": "Deployment has minimum availability.", - "reason": "MinimumReplicasAvailable", - "status": "True", - "type": "Available" - }, - { - "lastTransitionTime": "2018-07-18T07:34:16Z", - "lastTransitionTimeTS": 1531899256000, - "lastUpdateTime": "2018-07-18T07:34:38Z", - "lastUpdateTimeTS": 1531899278000, - "message": "ReplicaSet \"nginx-64d85666f9\" has successfully progressed.", - "reason": "NewReplicaSetAvailable", - "status": "True", - "type": "Progressing" - } - ], - "observedGeneration": 2, - "readyReplicas": 1, - "replicas": 1, - "type": "/v3/project/schemas/deploymentStatus", - "unavailableReplicas": 0, - "updatedReplicas": 1 - }, - "dnsPolicy": "ClusterFirst", - "id": "deployment:default:nginx", - "labels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "name": "nginx", - "namespaceId": "default", - "projectId": "c-bcz5t:p-fdr4s", - "publicEndpoints": [ - { - "addresses": ["10.64.3.58"], - "allNodes": true, - "ingressId": null, - "nodeId": null, - "podId": null, - "port": 30917, - "protocol": "TCP", - "serviceId": "default:nginx-nodeport", - "type": "publicEndpoint" - } - ], - "restartPolicy": "Always", - "scale": 1, - "schedulerName": "default-scheduler", - "selector": { - "matchLabels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "type": "/v3/project/schemas/labelSelector" - }, - "state": "active", - "terminationGracePeriodSeconds": 30, - "transitioning": "no", - "transitioningMessage": "", - "type": "deployment", - "uuid": "f998037d-8a5c-11e8-a4cf-0245a7ebb0fd", - "workloadAnnotations": { - "deployment.kubernetes.io/revision": "1", - "field.cattle.io/creatorId": "user-f4tt2" - }, - "workloadLabels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "scheduling": { - "node": {} - }, - "description": "my description", - "volumes": [] - } -} -``` - -### Metadata, Request Body, and Response Body Level - -If you set your `AUDIT_LEVEL` to `3`, Rancher logs: - -- The metadata header and body for every API request. -- The metadata header and body for every API response. - -#### Request - -The code sample below depicts an API request, with both its metadata header and body. - -```json -{ - "auditID": "a886fd9f-5d6b-4ae3-9a10-5bff8f3d68af", - "requestURI": "/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx", - "sourceIPs": ["::1"], - "user": { - "name": "user-f4tt2", - "group": ["system:authenticated"] - }, - "verb": "PUT", - "stage": "RequestReceived", - "stageTimestamp": "2018-07-20 10:33:06 +0800", - "requestBody": { - "hostIPC": false, - "hostNetwork": false, - "hostPID": false, - "paused": false, - "annotations": {}, - "baseType": "workload", - "containers": [ - { - "allowPrivilegeEscalation": false, - "image": "nginx", - "imagePullPolicy": "Always", - "initContainer": false, - "name": "nginx", - "ports": [ - { - "containerPort": 80, - "dnsName": "nginx-nodeport", - "kind": "NodePort", - "name": "80tcp01", - "protocol": "TCP", - "sourcePort": 0, - "type": "/v3/project/schemas/containerPort" - } - ], - "privileged": false, - "readOnly": false, - "resources": { - "type": "/v3/project/schemas/resourceRequirements", - "requests": {}, - "limits": {} - }, - "restartCount": 0, - "runAsNonRoot": false, - "stdin": true, - "stdinOnce": false, - "terminationMessagePath": "/dev/termination-log", - "terminationMessagePolicy": "File", - "tty": true, - "type": "/v3/project/schemas/container", - "environmentFrom": [], - "capAdd": [], - "capDrop": [], - "livenessProbe": null, - "volumeMounts": [] - } - ], - "created": "2018-07-18T07:34:16Z", - "createdTS": 1531899256000, - "creatorId": null, - "deploymentConfig": { - "maxSurge": 1, - "maxUnavailable": 0, - "minReadySeconds": 0, - "progressDeadlineSeconds": 600, - "revisionHistoryLimit": 10, - "strategy": "RollingUpdate" - }, - "deploymentStatus": { - "availableReplicas": 1, - "conditions": [ - { - "lastTransitionTime": "2018-07-18T07:34:38Z", - "lastTransitionTimeTS": 1531899278000, - "lastUpdateTime": "2018-07-18T07:34:38Z", - "lastUpdateTimeTS": 1531899278000, - "message": "Deployment has minimum availability.", - "reason": "MinimumReplicasAvailable", - "status": "True", - "type": "Available" - }, - { - "lastTransitionTime": "2018-07-18T07:34:16Z", - "lastTransitionTimeTS": 1531899256000, - "lastUpdateTime": "2018-07-18T07:34:38Z", - "lastUpdateTimeTS": 1531899278000, - "message": "ReplicaSet \"nginx-64d85666f9\" has successfully progressed.", - "reason": "NewReplicaSetAvailable", - "status": "True", - "type": "Progressing" - } - ], - "observedGeneration": 2, - "readyReplicas": 1, - "replicas": 1, - "type": "/v3/project/schemas/deploymentStatus", - "unavailableReplicas": 0, - "updatedReplicas": 1 - }, - "dnsPolicy": "ClusterFirst", - "id": "deployment:default:nginx", - "labels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "name": "nginx", - "namespaceId": "default", - "projectId": "c-bcz5t:p-fdr4s", - "publicEndpoints": [ - { - "addresses": ["10.64.3.58"], - "allNodes": true, - "ingressId": null, - "nodeId": null, - "podId": null, - "port": 30917, - "protocol": "TCP", - "serviceId": "default:nginx-nodeport", - "type": "publicEndpoint" - } - ], - "restartPolicy": "Always", - "scale": 1, - "schedulerName": "default-scheduler", - "selector": { - "matchLabels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "type": "/v3/project/schemas/labelSelector" - }, - "state": "active", - "terminationGracePeriodSeconds": 30, - "transitioning": "no", - "transitioningMessage": "", - "type": "deployment", - "uuid": "f998037d-8a5c-11e8-a4cf-0245a7ebb0fd", - "workloadAnnotations": { - "deployment.kubernetes.io/revision": "1", - "field.cattle.io/creatorId": "user-f4tt2" - }, - "workloadLabels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "scheduling": { - "node": {} - }, - "description": "my decript", - "volumes": [] - } -} -``` - -#### Response - -The code sample below depicts an API response, with both its metadata header and body. - -```json -{ - "auditID": "a886fd9f-5d6b-4ae3-9a10-5bff8f3d68af", - "responseStatus": "200", - "stage": "ResponseComplete", - "stageTimestamp": "2018-07-20 10:33:06 +0800", - "responseBody": { - "actionLinks": { - "pause": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx?action=pause", - "resume": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx?action=resume", - "rollback": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx?action=rollback" - }, - "annotations": {}, - "baseType": "workload", - "containers": [ - { - "allowPrivilegeEscalation": false, - "image": "nginx", - "imagePullPolicy": "Always", - "initContainer": false, - "name": "nginx", - "ports": [ - { - "containerPort": 80, - "dnsName": "nginx-nodeport", - "kind": "NodePort", - "name": "80tcp01", - "protocol": "TCP", - "sourcePort": 0, - "type": "/v3/project/schemas/containerPort" - } - ], - "privileged": false, - "readOnly": false, - "resources": { - "type": "/v3/project/schemas/resourceRequirements" - }, - "restartCount": 0, - "runAsNonRoot": false, - "stdin": true, - "stdinOnce": false, - "terminationMessagePath": "/dev/termination-log", - "terminationMessagePolicy": "File", - "tty": true, - "type": "/v3/project/schemas/container" - } - ], - "created": "2018-07-18T07:34:16Z", - "createdTS": 1531899256000, - "creatorId": null, - "deploymentConfig": { - "maxSurge": 1, - "maxUnavailable": 0, - "minReadySeconds": 0, - "progressDeadlineSeconds": 600, - "revisionHistoryLimit": 10, - "strategy": "RollingUpdate" - }, - "deploymentStatus": { - "availableReplicas": 1, - "conditions": [ - { - "lastTransitionTime": "2018-07-18T07:34:38Z", - "lastTransitionTimeTS": 1531899278000, - "lastUpdateTime": "2018-07-18T07:34:38Z", - "lastUpdateTimeTS": 1531899278000, - "message": "Deployment has minimum availability.", - "reason": "MinimumReplicasAvailable", - "status": "True", - "type": "Available" - }, - { - "lastTransitionTime": "2018-07-18T07:34:16Z", - "lastTransitionTimeTS": 1531899256000, - "lastUpdateTime": "2018-07-18T07:34:38Z", - "lastUpdateTimeTS": 1531899278000, - "message": "ReplicaSet \"nginx-64d85666f9\" has successfully progressed.", - "reason": "NewReplicaSetAvailable", - "status": "True", - "type": "Progressing" - } - ], - "observedGeneration": 2, - "readyReplicas": 1, - "replicas": 1, - "type": "/v3/project/schemas/deploymentStatus", - "unavailableReplicas": 0, - "updatedReplicas": 1 - }, - "dnsPolicy": "ClusterFirst", - "hostIPC": false, - "hostNetwork": false, - "hostPID": false, - "id": "deployment:default:nginx", - "labels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "links": { - "remove": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx", - "revisions": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx/revisions", - "self": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx", - "update": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx", - "yaml": "https://localhost:8443/v3/project/c-bcz5t:p-fdr4s/workloads/deployment:default:nginx/yaml" - }, - "name": "nginx", - "namespaceId": "default", - "paused": false, - "projectId": "c-bcz5t:p-fdr4s", - "publicEndpoints": [ - { - "addresses": ["10.64.3.58"], - "allNodes": true, - "ingressId": null, - "nodeId": null, - "podId": null, - "port": 30917, - "protocol": "TCP", - "serviceId": "default:nginx-nodeport" - } - ], - "restartPolicy": "Always", - "scale": 1, - "schedulerName": "default-scheduler", - "selector": { - "matchLabels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - }, - "type": "/v3/project/schemas/labelSelector" - }, - "state": "active", - "terminationGracePeriodSeconds": 30, - "transitioning": "no", - "transitioningMessage": "", - "type": "deployment", - "uuid": "f998037d-8a5c-11e8-a4cf-0245a7ebb0fd", - "workloadAnnotations": { - "deployment.kubernetes.io/revision": "1", - "field.cattle.io/creatorId": "user-f4tt2" - }, - "workloadLabels": { - "workload.user.cattle.io/workloadselector": "deployment-default-nginx" - } - } -} -``` diff --git a/versioned_docs/version-2.6/installation/resources/advanced/arm64-platform/arm64-platform.md b/versioned_docs/version-2.6/installation/resources/advanced/arm64-platform/arm64-platform.md deleted file mode 100644 index 9bc042f366d..00000000000 --- a/versioned_docs/version-2.6/installation/resources/advanced/arm64-platform/arm64-platform.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: "Running on ARM64 (Experimental)" -weight: 3 ---- - -> **Important:** -> -> Running on an ARM64 platform is currently an experimental feature and is not yet officially supported in Rancher. Therefore, we do not recommend using ARM64 based nodes in a production environment. - -The following options are available when using an ARM64 platform: - -- Running Rancher on ARM64 based node(s) - - Only for Docker Install. Please note that the following installation command replaces the examples found in the [Docker Install]({{}}/rancher/v2.0-v2.4/en/installation/other-installation-methods/single-node-docker) link: - - ``` - # In the last line `rancher/rancher:vX.Y.Z`, be certain to replace "X.Y.Z" with a released version in which ARM64 builds exist. For example, if your matching version is v2.5.8, you would fill in this line with `rancher/rancher:v2.5.8`. - docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - --privileged \ - rancher/rancher:vX.Y.Z - ``` -> **Note:** To check if your specific released version is compatible with the ARM64 architecture, you may navigate to your -> version's release notes in the following two ways: -> -> - Manually find your version using https://github.com/rancher/rancher/releases. -> - Go directly to your version using the tag and the specific version number. If you plan to use v2.5.8, for example, you may -> navigate to https://github.com/rancher/rancher/releases/tag/v2.5.8. - -- Create custom cluster and adding ARM64 based node(s) - - Kubernetes cluster version must be 1.12 or higher - - CNI Network Provider must be [Flannel]({{}}/rancher/v2.6/en/faq/networking/cni-providers/#flannel) -- Importing clusters that contain ARM64 based nodes - - Kubernetes cluster version must be 1.12 or higher - -Please see [Cluster Options]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/) how to configure the cluster options. - -The following features are not tested: - -- Monitoring, alerts, notifiers, pipelines and logging -- Launching apps from the catalog diff --git a/versioned_docs/version-2.6/installation/resources/advanced/etcd/etcd.md b/versioned_docs/version-2.6/installation/resources/advanced/etcd/etcd.md deleted file mode 100644 index a605c7343aa..00000000000 --- a/versioned_docs/version-2.6/installation/resources/advanced/etcd/etcd.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Tuning etcd for Large Installations -weight: 2 ---- - -When running larger Rancher installations with 15 or more clusters it is recommended to increase the default keyspace for etcd from the default 2GB. The maximum setting is 8GB and the host should have enough RAM to keep the entire dataset in memory. When increasing this value you should also increase the size of the host. The keyspace size can also be adjusted in smaller installations if you anticipate a high rate of change of pods during the garbage collection interval. - -The etcd data set is automatically cleaned up on a five minute interval by Kubernetes. There are situations, e.g. deployment thrashing, where enough events could be written to etcd and deleted before garbage collection occurs and cleans things up causing the keyspace to fill up. If you see `mvcc: database space exceeded` errors, in the etcd logs or Kubernetes API server logs, you should consider increasing the keyspace size. This can be accomplished by setting the [quota-backend-bytes](https://etcd.io/docs/v3.4.0/op-guide/maintenance/#space-quota) setting on the etcd servers. - -### Example: This snippet of the RKE cluster.yml file increases the keyspace size to 5GB - -```yaml -# RKE cluster.yml ---- -services: - etcd: - extra_args: - quota-backend-bytes: 5368709120 -``` - -## Scaling etcd disk performance - -You can follow the recommendations from [the etcd docs](https://etcd.io/docs/v3.4.0/tuning/#disk) on how to tune the disk priority on the host. - -Additionally, to reduce IO contention on the disks for etcd, you can use a dedicated device for the data and wal directory. Based on etcd best practices, mirroring RAID configurations are unnecessary because etcd replicates data between the nodes in the cluster. You can use stripping RAID configurations to increase available IOPS. - -To implement this solution in an RKE cluster, the `/var/lib/etcd/data` and `/var/lib/etcd/wal` directories will need to have disks mounted and formatted on the underlying host. In the `extra_args` directive of the `etcd` service, you must include the `wal_dir` directory. Without specifying the `wal_dir`, etcd process will try to manipulate the underlying `wal` mount with insufficient permissions. - -```yaml -# RKE cluster.yml ---- -services: - etcd: - extra_args: - data-dir: '/var/lib/rancher/etcd/data/' - wal-dir: '/var/lib/rancher/etcd/wal/wal_dir' - extra_binds: - - '/var/lib/etcd/data:/var/lib/rancher/etcd/data' - - '/var/lib/etcd/wal:/var/lib/rancher/etcd/wal' -``` diff --git a/versioned_docs/version-2.6/installation/resources/advanced/firewall/firewall.md b/versioned_docs/version-2.6/installation/resources/advanced/firewall/firewall.md deleted file mode 100644 index 69c1afae91d..00000000000 --- a/versioned_docs/version-2.6/installation/resources/advanced/firewall/firewall.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Opening Ports with firewalld -weight: 1 ---- - -> We recommend disabling firewalld. For Kubernetes 1.19.x and higher, firewalld must be turned off. - -Some distributions of Linux [derived from RHEL,](https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#Rebuilds) including Oracle Linux, may have default firewall rules that block communication with Helm. - -For example, one Oracle Linux image in AWS has REJECT rules that stop Helm from communicating with Tiller: - -``` -Chain INPUT (policy ACCEPT) -target prot opt source destination -ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED -ACCEPT icmp -- anywhere anywhere -ACCEPT all -- anywhere anywhere -ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh -REJECT all -- anywhere anywhere reject-with icmp-host-prohibited - -Chain FORWARD (policy ACCEPT) -target prot opt source destination -REJECT all -- anywhere anywhere reject-with icmp-host-prohibited - -Chain OUTPUT (policy ACCEPT) -target prot opt source destination -``` - -You can check the default firewall rules with this command: - -``` -sudo iptables --list -``` - -This section describes how to use `firewalld` to apply the [firewall port rules]({{}}/rancher/v2.6/en/installation/requirements/ports) for nodes in a high-availability Rancher server cluster. - -# Prerequisite - -Install v7.x or later ofv`firewalld`: - -``` -yum install firewalld -systemctl start firewalld -systemctl enable firewalld -``` - -# Applying Firewall Port Rules - -In the Rancher high-availability installation instructions, the Rancher server is set up on three nodes that have all three Kubernetes roles: etcd, controlplane, and worker. If your Rancher server nodes have all three roles, run the following commands on each node: - -``` -firewall-cmd --permanent --add-port=22/tcp -firewall-cmd --permanent --add-port=80/tcp -firewall-cmd --permanent --add-port=443/tcp -firewall-cmd --permanent --add-port=2376/tcp -firewall-cmd --permanent --add-port=2379/tcp -firewall-cmd --permanent --add-port=2380/tcp -firewall-cmd --permanent --add-port=6443/tcp -firewall-cmd --permanent --add-port=8472/udp -firewall-cmd --permanent --add-port=9099/tcp -firewall-cmd --permanent --add-port=10250/tcp -firewall-cmd --permanent --add-port=10254/tcp -firewall-cmd --permanent --add-port=30000-32767/tcp -firewall-cmd --permanent --add-port=30000-32767/udp -``` -If your Rancher server nodes have separate roles, use the following commands based on the role of the node: - -``` -# For etcd nodes, run the following commands: -firewall-cmd --permanent --add-port=2376/tcp -firewall-cmd --permanent --add-port=2379/tcp -firewall-cmd --permanent --add-port=2380/tcp -firewall-cmd --permanent --add-port=8472/udp -firewall-cmd --permanent --add-port=9099/tcp -firewall-cmd --permanent --add-port=10250/tcp - -# For control plane nodes, run the following commands: -firewall-cmd --permanent --add-port=80/tcp -firewall-cmd --permanent --add-port=443/tcp -firewall-cmd --permanent --add-port=2376/tcp -firewall-cmd --permanent --add-port=6443/tcp -firewall-cmd --permanent --add-port=8472/udp -firewall-cmd --permanent --add-port=9099/tcp -firewall-cmd --permanent --add-port=10250/tcp -firewall-cmd --permanent --add-port=10254/tcp -firewall-cmd --permanent --add-port=30000-32767/tcp -firewall-cmd --permanent --add-port=30000-32767/udp - -# For worker nodes, run the following commands: -firewall-cmd --permanent --add-port=22/tcp -firewall-cmd --permanent --add-port=80/tcp -firewall-cmd --permanent --add-port=443/tcp -firewall-cmd --permanent --add-port=2376/tcp -firewall-cmd --permanent --add-port=8472/udp -firewall-cmd --permanent --add-port=9099/tcp -firewall-cmd --permanent --add-port=10250/tcp -firewall-cmd --permanent --add-port=10254/tcp -firewall-cmd --permanent --add-port=30000-32767/tcp -firewall-cmd --permanent --add-port=30000-32767/udp -``` - -After the `firewall-cmd` commands have been run on a node, use the following command to enable the firewall rules: - -``` -firewall-cmd --reload -``` - -**Result:** The firewall is updated so that Helm can communicate with the Rancher server nodes. diff --git a/versioned_docs/version-2.6/installation/resources/advanced/single-node-install-external-lb/single-node-install-external-lb.md b/versioned_docs/version-2.6/installation/resources/advanced/single-node-install-external-lb/single-node-install-external-lb.md deleted file mode 100644 index fc607486482..00000000000 --- a/versioned_docs/version-2.6/installation/resources/advanced/single-node-install-external-lb/single-node-install-external-lb.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -title: Docker Install with TLS Termination at Layer-7 NGINX Load Balancer -weight: 252 ---- - -For development and testing environments that have a special requirement to terminate TLS/SSL at a load balancer instead of your Rancher Server container, deploy Rancher and configure a load balancer to work with it conjunction. - -A layer-7 load balancer can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. - -This install procedure walks you through deployment of Rancher using a single container, and then provides a sample configuration for a layer-7 NGINX load balancer. - -## Requirements for OS, Docker, Hardware, and Networking - -Make sure that your node fulfills the general [installation requirements.]({{}}/rancher/v2.6/en/installation/requirements/) - -## Installation Outline - - - -- [1. Provision Linux Host](#1-provision-linux-host) -- [2. Choose an SSL Option and Install Rancher](#2-choose-an-ssl-option-and-install-rancher) -- [3. Configure Load Balancer](#3-configure-load-balancer) - - - -## 1. Provision Linux Host - -Provision a single Linux host according to our [Requirements]({{}}/rancher/v2.6/en/installation/requirements) to launch your Rancher Server. - -## 2. Choose an SSL Option and Install Rancher - -For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster. - -> **Do you want to..**. -> -> - Complete an Air Gap Installation? -> - Record all transactions with the Rancher API? -> -> See [Advanced Options](#advanced-options) below before continuing. - -Choose from the following options: - -
- Option A-Bring Your Own Certificate: Self-Signed - -If you elect to use a self-signed certificate to encrypt communication, you must install the certificate on your load balancer (which you'll do later) and your Rancher container. Run the Docker command to deploy Rancher, pointing it toward your certificate. - -> **Prerequisites:** -> Create a self-signed certificate. -> -> - The certificate files must be in PEM format. - -**To Install Rancher Using a Self-Signed Cert:** - -1. While running the Docker command to deploy Rancher, point Docker toward your CA certificate file. - - ``` - docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v /etc/your_certificate_directory/cacerts.pem:/etc/rancher/ssl/cacerts.pem \ - rancher/rancher:latest - ``` - -
-
- Option B-Bring Your Own Certificate: Signed by Recognized CA - -If your cluster is public facing, it's best to use a certificate signed by a recognized CA. - -> **Prerequisites:** -> -> - The certificate files must be in PEM format. - -**To Install Rancher Using a Cert Signed by a Recognized CA:** - -If you use a certificate signed by a recognized CA, installing your certificate in the Rancher container isn't necessary. We do have to make sure there is no default CA certificate generated and stored, you can do this by passing the `--no-cacerts` parameter to the container. - -1. Enter the following command. - - ``` - docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - rancher/rancher:latest --no-cacerts - ``` - -
- -## 3. Configure Load Balancer - -When using a load balancer in front of your Rancher container, there's no need for the container to redirect port communication from port 80 or port 443. By passing the header `X-Forwarded-Proto: https` header, this redirect is disabled. - -The load balancer or proxy has to be configured to support the following: - -- **WebSocket** connections -- **SPDY** / **HTTP/2** protocols -- Passing / setting the following headers: - - | Header | Value | Description | - |--------|-------|-------------| - | `Host` | Hostname used to reach Rancher. | To identify the server requested by the client. - | `X-Forwarded-Proto` | `https` | To identify the protocol that a client used to connect to the load balancer or proxy.

**Note:** If this header is present, `rancher/rancher` does not redirect HTTP to HTTPS. - | `X-Forwarded-Port` | Port used to reach Rancher. | To identify the protocol that client used to connect to the load balancer or proxy. - | `X-Forwarded-For` | IP of the client connection. | To identify the originating IP address of a client. -### Example NGINX configuration - -This NGINX configuration is tested on NGINX 1.14. - -> **Note:** This NGINX configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - HTTP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/). - -- Replace `rancher-server` with the IP address or hostname of the node running the Rancher container. -- Replace both occurrences of `FQDN` to the DNS name for Rancher. -- Replace `/certs/fullchain.pem` and `/certs/privkey.pem` to the location of the server certificate and the server certificate key respectively. - -``` -worker_processes 4; -worker_rlimit_nofile 40000; - -events { - worker_connections 8192; -} - -http { - upstream rancher { - server rancher-server:80; - } - - map $http_upgrade $connection_upgrade { - default Upgrade; - '' close; - } - - server { - listen 443 ssl http2; - server_name FQDN; - ssl_certificate /certs/fullchain.pem; - ssl_certificate_key /certs/privkey.pem; - - location / { - proxy_set_header Host $host; - proxy_set_header X-Forwarded-Proto $scheme; - proxy_set_header X-Forwarded-Port $server_port; - proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; - proxy_pass http://rancher; - proxy_http_version 1.1; - proxy_set_header Upgrade $http_upgrade; - proxy_set_header Connection $connection_upgrade; - # This allows the ability for the execute shell window to remain open for up to 15 minutes. Without this parameter, the default is 1 minute and will automatically close. - proxy_read_timeout 900s; - proxy_buffering off; - } - } - - server { - listen 80; - server_name FQDN; - return 301 https://$server_name$request_uri; - } -} -``` - -
- -## What's Next? - -- **Recommended:** Review [Single Node Backup and Restore]({{}}/rancher/v2.6/en/backups/docker-installs/). Although you don't have any data you need to back up right now, we recommend creating backups after regular Rancher use. -- Create a Kubernetes cluster: [Provisioning Kubernetes Clusters]({{}}/rancher/v2.6/en/cluster-provisioning/). - -
- -## FAQ and Troubleshooting - -For help troubleshooting certificates, see [this section.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting) - -## Advanced Options - -### API Auditing - -If you want to record all transactions with the Rancher API, enable the [API Auditing]({{}}/rancher/v2.6/en/installation/resources/advanced/api-audit-log) feature by adding the flags below into your install command. - - -e AUDIT_LEVEL=1 \ - -e AUDIT_LOG_PATH=/var/log/auditlog/rancher-api-audit.log \ - -e AUDIT_LOG_MAXAGE=20 \ - -e AUDIT_LOG_MAXBACKUP=20 \ - -e AUDIT_LOG_MAXSIZE=100 \ - -### Air Gap - -If you are visiting this page to complete an [Air Gap Installation]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap), you must pre-pend your private registry URL to the server tag when running the installation command in the option that you choose. Add `` with your private registry URL in front of `rancher/rancher:latest`. - -**Example:** - - /rancher/rancher:latest - -### Persistent Data - -Rancher uses etcd as a datastore. When Rancher is installed with Docker, the embedded etcd is being used. The persistent data is at the following path in the container: `/var/lib/rancher`. - -You can bind mount a host volume to this location to preserve data on the host it is running on: - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v /opt/rancher:/var/lib/rancher \ - --privileged \ - rancher/rancher:latest -``` - -As of Rancher v2.5, privileged access is [required.]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher-v2-5) - -This layer 7 NGINX configuration is tested on NGINX version 1.13 (mainline) and 1.14 (stable). - -> **Note:** This NGINX configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - TCP and UDP Load Balancer](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/). - -``` -upstream rancher { - server rancher-server:80; -} - -map $http_upgrade $connection_upgrade { - default Upgrade; - '' close; -} - -server { - listen 443 ssl http2; - server_name rancher.yourdomain.com; - ssl_certificate /etc/your_certificate_directory/fullchain.pem; - ssl_certificate_key /etc/your_certificate_directory/privkey.pem; - - location / { - proxy_set_header Host $host; - proxy_set_header X-Forwarded-Proto $scheme; - proxy_set_header X-Forwarded-Port $server_port; - proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; - proxy_pass http://rancher; - proxy_http_version 1.1; - proxy_set_header Upgrade $http_upgrade; - proxy_set_header Connection $connection_upgrade; - # This allows the ability for the execute shell window to remain open for up to 15 minutes. Without this parameter, the default is 1 minute and will automatically close. - proxy_read_timeout 900s; - proxy_buffering off; - } -} - -server { - listen 80; - server_name rancher.yourdomain.com; - return 301 https://$server_name$request_uri; -} -``` - -
- diff --git a/versioned_docs/version-2.6/installation/resources/bootstrap-password/bootstrap-password.md b/versioned_docs/version-2.6/installation/resources/bootstrap-password/bootstrap-password.md deleted file mode 100644 index f0875b5e8a2..00000000000 --- a/versioned_docs/version-2.6/installation/resources/bootstrap-password/bootstrap-password.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Bootstrap Password -weight: 800 ---- - -When Rancher starts for the first time, a password is randomly generated for the first admin user. When the admin first logs in to Rancher, the UI shows commands that can be used to retrieve the bootstrap password. The admin needs to run those commands and log in with the bootstrap password. Then Rancher gives the admin an opportunity to reset the password. - -The bootstrap password is randomly generated if it is not set during installation with a variable. For details on how to set the bootstrap password using a variable, see below. - -### Specifying the Bootstrap Password in Helm Installs - -For a Helm install, users can specify the bootstrap password variable by configuring it in the Helm chart values with `.Values.bootstrapPassword`. - -The password will be stored in a Kubernetes secret. After Rancher is installed, the UI will show instructions for how to retrieve the password using kubectl: - -``` -kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{ .data.bootstrapPassword|base64decode}}{{ "\n" }}' -``` - -### Specifying the Bootstrap Password in Docker Installs - -For a Docker install, you can specify the bootstrap password by passing `-e CATTLE_BOOTSTRAP_PASSWORD=password` to the Docker install command. - -The password will be stored in the Docker container logs. After Rancher is installed, the UI will show instructions for how to retrieve the password using the Docker container ID: - -``` -docker logs container-id 2>&1 | grep "Bootstrap Password:" -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/resources/choosing-version/choosing-version.md b/versioned_docs/version-2.6/installation/resources/choosing-version/choosing-version.md deleted file mode 100644 index 9c6f2c279d9..00000000000 --- a/versioned_docs/version-2.6/installation/resources/choosing-version/choosing-version.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Choosing a Rancher Version -weight: 1 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This section describes how to choose a Rancher version. - -For a high-availability installation of Rancher, which is recommended for production, the Rancher server is installed using a **Helm chart** on a Kubernetes cluster. Refer to the [Helm version requirements]({{}}/rancher/v2.6/en/installation/resources/helm-version) to choose a version of Helm to install Rancher. - -For Docker installations of Rancher, which is used for development and testing, you will install Rancher as a **Docker image**. - - - - -When installing, upgrading, or rolling back Rancher Server when it is [installed on a Kubernetes cluster]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/), Rancher server is installed using a Helm chart on a Kubernetes cluster. Therefore, as you prepare to install or upgrade a high availability Rancher configuration, you must add a Helm chart repository that contains the charts for installing Rancher. - -Refer to the [Helm version requirements]({{}}/rancher/v2.6/en/installation/resources/helm-version) to choose a version of Helm to install Rancher. - -### Helm Chart Repositories - -Rancher provides several different Helm chart repositories to choose from. We align our latest and stable Helm chart repositories with the Docker tags that are used for a Docker installation. Therefore, the `rancher-latest` repository will contain charts for all the Rancher versions that have been tagged as `rancher/rancher:latest`. When a Rancher version has been promoted to the `rancher/rancher:stable`, it will get added to the `rancher-stable` repository. - -| Type | Command to Add the Repo | Description of the Repo | -| -------------- | ------------ | ----------------- | -| rancher-latest | `helm repo add rancher-latest https://releases.rancher.com/server-charts/latest` | Adds a repository of Helm charts for the latest versions of Rancher. We recommend using this repo for testing out new Rancher builds. | -| rancher-stable | `helm repo add rancher-stable https://releases.rancher.com/server-charts/stable` | Adds a repository of Helm charts for older, stable versions of Rancher. We recommend using this repo for production environments. | -| rancher-alpha | `helm repo add rancher-alpha https://releases.rancher.com/server-charts/alpha` | Adds a repository of Helm charts for alpha versions of Rancher for previewing upcoming releases. These releases are discouraged in production environments. Upgrades _to_ or _from_ charts in the rancher-alpha repository to any other chart, regardless or repository, aren't supported. | - -
-Instructions on when to select these repos are available below in [Switching to a Different Helm Chart Repository](#switching-to-a-different-helm-chart-repository). - -> **Note:** All charts in the `rancher-stable` repository will correspond with any Rancher version tagged as `stable`. - -### Helm Chart Versions - -Rancher Helm chart versions match the Rancher version (i.e `appVersion`). Once you've added the repo you can search it to show available versions with the following command:
-    `helm search repo --versions` - -If you have several repos you can specify the repo name, ie. `helm search repo rancher-stable/rancher --versions`
-For more information, see https://helm.sh/docs/helm/helm_search_repo/ - -To fetch a specific version of your chosen repo, define the `--version` parameter like in the following example:
-    `helm fetch rancher-stable/rancher --version=2.4.8` - -### Switching to a Different Helm Chart Repository - -After installing Rancher, if you want to change which Helm chart repository to install Rancher from, you will need to follow these steps. - -> **Note:** Because the rancher-alpha repository contains only alpha charts, switching between the rancher-alpha repository and the rancher-stable or rancher-latest repository for upgrades is not supported. - -{{< release-channel >}} - -1. List the current Helm chart repositories. - - ```plain - helm repo list - - NAME URL - stable https://charts.helm.sh/stable - rancher- https://releases.rancher.com/server-charts/ - ``` - -2. Remove the existing Helm Chart repository that contains your charts to install Rancher, which will either be `rancher-stable` or `rancher-latest` depending on what you had initially added. - - ```plain - helm repo remove rancher- - ``` - -3. Add the Helm chart repository that you want to start installing Rancher from. - - ```plain - helm repo add rancher- https://releases.rancher.com/server-charts/ - ``` - -4. Continue to follow the steps to [upgrade Rancher]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/upgrades) from the new Helm chart repository. - - - - -When performing [Docker installs]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker), upgrades, or rollbacks, you can use _tags_ to install a specific version of Rancher. - -### Server Tags - -Rancher Server is distributed as a Docker image, which have tags attached to them. You can specify this tag when entering the command to deploy Rancher. Remember that if you use a tag without an explicit version (like `latest` or `stable`), you must explicitly pull a new version of that image tag. Otherwise, any image cached on the host will be used. - -| Tag | Description | -| -------------------------- | ------ | -| `rancher/rancher:latest` | Our latest development release. These builds are validated through our CI automation framework. These releases are not recommended for production environments. | -| `rancher/rancher:stable` | Our newest stable release. This tag is recommended for production. | -| `rancher/rancher:` | You can install specific versions of Rancher by using the tag from a previous release. See what's available at DockerHub. | - -> **Notes:** -> -> - The `master` tag or any tag with `-rc` or another suffix is meant for the Rancher testing team to validate. You should not use these tags, as these builds are not officially supported. -> - Want to install an alpha review for preview? Install using one of the alpha tags listed on our [announcements page](https://forums.rancher.com/c/announcements) (e.g., `v2.2.0-alpha1`). Caveat: Alpha releases cannot be upgraded to or from any other release. - - - diff --git a/versioned_docs/version-2.6/installation/resources/custom-ca-root-certificate/custom-ca-root-certificate.md b/versioned_docs/version-2.6/installation/resources/custom-ca-root-certificate/custom-ca-root-certificate.md deleted file mode 100644 index e3f3e9f05ed..00000000000 --- a/versioned_docs/version-2.6/installation/resources/custom-ca-root-certificate/custom-ca-root-certificate.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: About Custom CA Root Certificates -weight: 1 ---- - -If you're using Rancher in an internal production environment where you aren't exposing apps publicly, use a certificate from a private certificate authority (CA). - -Services that Rancher needs to access are sometimes configured with a certificate from a custom/internal CA root, also known as self signed certificate. If the presented certificate from the service cannot be validated by Rancher, the following error displays: `x509: certificate signed by unknown authority`. - -To validate the certificate, the CA root certificates need to be added to Rancher. As Rancher is written in Go, we can use the environment variable `SSL_CERT_DIR` to point to the directory where the CA root certificates are located in the container. The CA root certificates directory can be mounted using the Docker volume option (`-v host-source-directory:container-destination-directory`) when starting the Rancher container. - -Examples of services that Rancher can access: - -- Catalogs -- Authentication providers -- Accessing hosting/cloud API when using Node Drivers - -## Installing with the custom CA Certificate - -For details on starting a Rancher container with your private CA certificates mounted, refer to the installation docs: - -- [Docker install Custom CA certificate options]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#custom-ca-certificate) - -- [Kubernetes install options for Additional Trusted CAs]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#additional-trusted-cas) - diff --git a/versioned_docs/version-2.6/installation/resources/feature-flags/continuous-delivery/continuous-delivery.md b/versioned_docs/version-2.6/installation/resources/feature-flags/continuous-delivery/continuous-delivery.md deleted file mode 100644 index c3fb7f798ef..00000000000 --- a/versioned_docs/version-2.6/installation/resources/feature-flags/continuous-delivery/continuous-delivery.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Continuous Delivery -weight: 3 ---- - -As of Rancher v2.5, [Fleet]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet) comes preinstalled in Rancher, and as of Rancher v2.6, Fleet can no longer be fully disabled. However, the Fleet feature for GitOps continuous delivery may be disabled using the `continuous-delivery` feature flag. - -To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) - -Environment Variable Key | Default Value | Description ----|---|--- - `continuous-delivery` | `true` | This flag disables the GitOps continuous delivery feature of Fleet. | - -If Fleet was disabled in Rancher v2.5.x, it will become enabled if Rancher is upgraded to v2.6.x. Only the continuous delivery part of Fleet can be disabled. When `continuous-delivery` is disabled, the `gitjob` deployment is no longer deployed into the Rancher server's local cluster, and `continuous-delivery` is not shown in the Rancher UI. diff --git a/versioned_docs/version-2.6/installation/resources/feature-flags/enable-not-default-storage-drivers/enable-not-default-storage-drivers.md b/versioned_docs/version-2.6/installation/resources/feature-flags/enable-not-default-storage-drivers/enable-not-default-storage-drivers.md deleted file mode 100644 index 05affcc91ad..00000000000 --- a/versioned_docs/version-2.6/installation/resources/feature-flags/enable-not-default-storage-drivers/enable-not-default-storage-drivers.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Allow Unsupported Storage Drivers -weight: 1 ---- - -This feature allows you to use types for storage providers and provisioners that are not enabled by default. - -To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) - -Environment Variable Key | Default Value | Description ----|---|--- - `unsupported-storage-drivers` | `false` | This feature enables types for storage providers and provisioners that are not enabled by default. - -### Types for Persistent Volume Plugins that are Enabled by Default -Below is a list of storage types for persistent volume plugins that are enabled by default. When enabling this feature flag, any persistent volume plugins that are not on this list are considered experimental and unsupported: - -Name | Plugin ---------|---------- -Amazon EBS Disk | `aws-ebs` -AzureFile | `azure-file` -AzureDisk | `azure-disk` -Google Persistent Disk | `gce-pd` -Longhorn | `flex-volume-longhorn` -VMware vSphere Volume | `vsphere-volume` -Local | `local` -Network File System | `nfs` -hostPath | `host-path` - -### Types for StorageClass that are Enabled by Default -Below is a list of storage types for a StorageClass that are enabled by default. When enabling this feature flag, any persistent volume plugins that are not on this list are considered experimental and unsupported: - -Name | Plugin ---------|-------- -Amazon EBS Disk | `aws-ebs` -AzureFile | `azure-file` -AzureDisk | `azure-disk` -Google Persistent Disk | `gce-pd` -Longhorn | `flex-volume-longhorn` -VMware vSphere Volume | `vsphere-volume` -Local | `local` \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/resources/feature-flags/feature-flags.md b/versioned_docs/version-2.6/installation/resources/feature-flags/feature-flags.md deleted file mode 100644 index 25baf0c06a2..00000000000 --- a/versioned_docs/version-2.6/installation/resources/feature-flags/feature-flags.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -title: Enabling Experimental Features -weight: 17 ---- -Rancher includes some features that are experimental and disabled by default. You might want to enable these features, for example, if you decide that the benefits of using an [unsupported storage type]({{}}/rancher/v2.6/en/installation/resources/feature-flags/enable-not-default-storage-drivers) outweighs the risk of using an untested feature. Feature flags were introduced to allow you to try these features that are not enabled by default. - -The features can be enabled in three ways: - -- [Enable features when starting Rancher.](#enabling-features-when-starting-rancher) When installing Rancher with a CLI, you can use a feature flag to enable a feature by default. -- [Enable features from the Rancher UI](#enabling-features-with-the-rancher-ui) by going to the **Settings** page. -- [Enable features with the Rancher API](#enabling-features-with-the-rancher-api) after installing Rancher. - -Each feature has two values: - -- A default value, which can be configured with a flag or environment variable from the command line -- A set value, which can be configured with the Rancher API or UI - -If no value has been set, Rancher uses the default value. - -Because the API sets the actual value and the command line sets the default value, that means that if you enable or disable a feature with the API or UI, it will override any value set with the command line. - -For example, if you install Rancher, then set a feature flag to true with the Rancher API, then upgrade Rancher with a command that sets the feature flag to false, the default value will still be false, but the feature will still be enabled because it was set with the Rancher API. If you then deleted the set value (true) with the Rancher API, setting it to NULL, the default value (false) would take effect. - -> **Note:** There are some feature flags that may require a restart of the Rancher server container. These features that require a restart are marked in the table of these docs and in the UI. - -The following is a list of the feature flags available in Rancher: - -- `harvester`: This feature flag is available starting in v2.6.1. It is used to manage access to the Virtualization Management page where users can navigate directly to Harvester clusters and access the Harvester UI. For more information, see [this page]({{}}/rancher/v2.6/en/virtualization-admin/#feature-flag/). -- `rke2`: Used to enable the ability to provision RKE2 clusters. By default, this feature flag is enabled, which allows users to attempt to provision these type of clusters. -- `fleet`: The previous `fleet` feature flag is now required to be enabled as the Fleet capabilities are leveraged within the new provisioning framework. If you had this feature flag disabled in earlier versions, upon upgrading to Rancher v2.6, the flag will automatically be enabled. See this [page]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet) for more information. -- `continuous-delivery`: In Rancher v2.5.x, Fleet came with a GitOps feature that could not be disabled separately from Fleet. In Rancher v2.6, the `continuous-delivery` feature flag was introduced to allow the GitOps feature of Fleet to be disabled. For more information, see [this page.](./continuous-delivery). -- `legacy`: There are a set of features from previous versions that are slowly being phased out of Rancher for newer iterations of the feature. This is a mix of deprecated features as well as features that will eventually be moved to newer variations in Rancher. By default, this feature flag is disabled for new installations. If you are upgrading from a previous version, this feature flag would be enabled. -- `token-hashing`: Used to enable new token-hashing feature. Once enabled, existing tokens will be hashed and all new tokens will be hashed automatically using the SHA256 algorithm. Once a token is hashed it cannot be undone. Once this feature flag is enabled, it cannot be disabled. See [hashing of tokens]({{}}/rancher/v2.6/en/api/api-tokens) for more information. -- `unsupported-storage-drivers`: This feature [allows unsupported storage drivers.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/enable-not-default-storage-drivers). In other words, it enables types for storage providers and provisioners that are not enabled by default. -- `istio-virtual-service-ui`: This feature enables a [UI to create, read, update, and delete Istio virtual services and destination rules,]({{}}/rancher/v2.6/en/installation/resources/feature-flags/istio-virtual-service-ui) which are traffic management features of Istio. -- `multi-cluster-management`: Used for multi-cluster provisioning and management of Kubernetes clusters. This feature flag can only be set at install time and not changed afterwards. - -The below table shows the availability and default value for feature flags in Rancher: - -| Feature Flag Name | Default Value | Status | Available as of | Rancher Restart Required? | -| ----------------------------- | ------------- | ------------ | --------------- |---| -| `istio-virtual-service-ui` | `false` | Experimental | v2.3.0 | | -| `istio-virtual-service-ui` | `true` | GA* | v2.3.2 | | -| `unsupported-storage-drivers` | `false` | Experimental | v2.3.0 | | -| `fleet` | `true` | GA* | v2.5.0 | | -| `fleet` | `true` | Can no longer be disabled | v2.6.0 | N/A | -| `continuous-delivery` | `true` | GA* | v2.6.0 | | -| `token-hashing` | `false` for new installs, `true` for upgrades | GA* | v2.6.0 | | -| `legacy` | `false` for new installs, `true` for upgrades | GA* | v2.6.0 | | -| `multi-cluster-management` | `false` | GA* | v2.5.0 | | -| `harvester` | `true` | Experimental | v2.6.1 | | -| `rke2` | `true` | Experimental | v2.6.0 | | - -\* Generally Available. This feature is included in Rancher and it is not experimental. - -# Enabling Features when Starting Rancher - -When you install Rancher, enable the feature you want with a feature flag. The command is different depending on whether you are installing Rancher on a single node or if you are doing a Kubernetes Installation of Rancher. - -### Enabling Features for Kubernetes Installs - -> **Note:** Values set from the Rancher API will override the value passed in through the command line. - -When installing Rancher with a Helm chart, use the `--set` option. In the below example, two features are enabled by passing the feature flag names in a comma separated list: - -``` -helm install rancher rancher-latest/rancher \ - --namespace cattle-system \ - --set hostname=rancher.my.org \ - --set 'extraEnv[0].name=CATTLE_FEATURES' - --set 'extraEnv[0].value==true,=true' -``` - -Note: If you are installing an alpha version, Helm requires adding the `--devel` option to the command. - -### Rendering the Helm Chart for Air Gap Installations - -For an air gap installation of Rancher, you need to add a Helm chart repository and render a Helm template before installing Rancher with Helm. For details, refer to the [air gap installation documentation.]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/install-rancher) - -Here is an example of a command for passing in the feature flag names when rendering the Helm template. In the below example, two features are enabled by passing the feature flag names in a comma separated list. - -The Helm command is as follows: - -``` -helm template rancher ./rancher-.tgz --output-dir . \ - --no-hooks \ # prevent files for Helm hooks from being generated - --namespace cattle-system \ - --set hostname= \ - --set rancherImage=/rancher/rancher \ - --set ingress.tls.source=secret \ - --set systemDefaultRegistry= \ # Set a default private registry to be used in Rancher - --set useBundledSystemChart=true # Use the packaged Rancher system charts - --set 'extraEnv[0].name=CATTLE_FEATURES' - --set 'extraEnv[0].value==true,=true' -``` - -### Enabling Features for Docker Installs - -When installing Rancher with Docker, use the `--features` option. In the below example, two features are enabled by passing the feature flag names in a comma separated list: - -``` -docker run -d -p 80:80 -p 443:443 \ - --restart=unless-stopped \ - rancher/rancher:rancher-latest \ - --features==true,=true -``` - - -# Enabling Features with the Rancher UI - -1. In the upper left corner, click **☰ > Global Settings**. -1. Click **Feature Flags**. -1. To enable a feature, go to the disabled feature you want to enable and click **⋮ > Activate**. - -**Result:** The feature is enabled. - -### Disabling Features with the Rancher UI - -1. In the upper left corner, click **☰ > Global Settings**. -1. Click **Feature Flags**. You will see a list of experimental features. -1. To disable a feature, go to the enabled feature you want to disable and click **⋮ > Deactivate**. - -**Result:** The feature is disabled. - -# Enabling Features with the Rancher API - -1. Go to `/v3/features`. -1. In the `data` section, you will see an array containing all of the features that can be turned on with feature flags. The name of the feature is in the `id` field. Click the name of the feature you want to enable. -1. In the upper left corner of the screen, under **Operations,** click **Edit**. -1. In the **Value** drop-down menu, click **True**. -1. Click **Show Request**. -1. Click **Send Request**. -1. Click **Close**. - -**Result:** The feature is enabled. - -### Disabling Features with the Rancher API - -1. Go to `/v3/features`. -1. In the `data` section, you will see an array containing all of the features that can be turned on with feature flags. The name of the feature is in the `id` field. Click the name of the feature you want to enable. -1. In the upper left corner of the screen, under **Operations,** click **Edit**. -1. In the **Value** drop-down menu, click **False**. -1. Click **Show Request**. -1. Click **Send Request**. -1. Click **Close**. - -**Result:** The feature is disabled. diff --git a/versioned_docs/version-2.6/installation/resources/feature-flags/istio-virtual-service-ui/istio-virtual-service-ui.md b/versioned_docs/version-2.6/installation/resources/feature-flags/istio-virtual-service-ui/istio-virtual-service-ui.md deleted file mode 100644 index 0b5a1395ab6..00000000000 --- a/versioned_docs/version-2.6/installation/resources/feature-flags/istio-virtual-service-ui/istio-virtual-service-ui.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: UI for Istio Virtual Services and Destination Rules -weight: 2 ---- - -This feature enables a UI that lets you create, read, update and delete virtual services and destination rules, which are traffic management features of Istio. - -> **Prerequisite:** Turning on this feature does not enable Istio. A cluster administrator needs to [enable Istio for the cluster]({{}}/rancher/v2.6/en/istio/setup) in order to use the feature. - -To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) - -Environment Variable Key | Default Value | Status | Available as of ----|---|---|--- -`istio-virtual-service-ui` |`false` | Experimental | v2.3.0 -`istio-virtual-service-ui` | `true` | GA | v2.3.2 - -# About this Feature - -A central advantage of Istio's traffic management features is that they allow dynamic request routing, which is useful for canary deployments, blue/green deployments, or A/B testing. - -When enabled, this feature turns on a page that lets you configure some traffic management features of Istio using the Rancher UI. Without this feature, you need to use `kubectl` to manage traffic with Istio. - -The feature enables two UI tabs: one tab for **Virtual Services** and another for **Destination Rules**. - -- **Virtual services** intercept and direct traffic to your Kubernetes services, allowing you to direct percentages of traffic from a request to different services. You can use them to define a set of routing rules to apply when a host is addressed. For details, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/virtual-service/) -- **Destination rules** serve as the single source of truth about which service versions are available to receive traffic from virtual services. You can use these resources to define policies that apply to traffic that is intended for a service after routing has occurred. For details, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/destination-rule) - -To see these tabs, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster where Istio is installed and click **Explore**. -1. In the left navigation bar, click **Istio**. -1. You will see tabs for **Kiali** and **Jaeger**. From the left navigation bar, you can view and configure **Virtual Services** and **Destination Rules**. \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/resources/helm-version/helm-version.md b/versioned_docs/version-2.6/installation/resources/helm-version/helm-version.md deleted file mode 100644 index 0fd69cfb62f..00000000000 --- a/versioned_docs/version-2.6/installation/resources/helm-version/helm-version.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Helm Version Requirements -weight: 3 ---- - -This section contains the requirements for Helm, which is the tool used to install Rancher on a high-availability Kubernetes cluster. - -> The installation instructions have been updated for Helm 3. For migration of installs started with Helm 2, refer to the official [Helm 2 to 3 Migration Docs.](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) [This section]({{}}/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/) provides a copy of the older high-availability Rancher installation instructions that used Helm 2, and it is intended to be used if upgrading to Helm 3 is not feasible. - -- Helm v3.2.x or higher is required to install or upgrade Rancher v2.5. -- Helm v2.16.0 or higher is required for Kubernetes v1.16. For the default Kubernetes version, refer to the [release notes](https://github.com/rancher/rke/releases) for the version of RKE that you are using. -- Helm v2.15.0 should not be used, because of an issue with converting/comparing numbers. -- Helm v2.12.0 should not be used, because of an issue with `cert-manager`. diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-RKE/ha-RKE.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-RKE/ha-RKE.md deleted file mode 100644 index ce46ab810c0..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-RKE/ha-RKE.md +++ /dev/null @@ -1,169 +0,0 @@ ---- -title: Setting up a High-availability RKE Kubernetes Cluster -shortTitle: Set up RKE Kubernetes -weight: 3 ---- - - -This section describes how to install a Kubernetes cluster. This cluster should be dedicated to run only the Rancher server. - -> Rancher can run on any Kubernetes cluster, included hosted Kubernetes solutions such as Amazon EKS. The below instructions represent only one possible way to install Kubernetes. - -For systems without direct internet access, refer to [Air Gap: Kubernetes install.]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/) - -> **Single-node Installation Tip:** -> In a single-node Kubernetes cluster, the Rancher server does not have high availability, which is important for running Rancher in production. However, installing Rancher on a single-node cluster can be useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path. -> -> To set up a single-node RKE cluster, configure only one node in the `cluster.yml` . The single node should have all three roles: `etcd`, `controlplane`, and `worker`. -> -> In both single-node setups, Rancher can be installed with Helm on the Kubernetes cluster in the same way that it would be installed on any other cluster. - -# Installing Kubernetes - -### Required CLI Tools - -Install [kubectl,](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) a Kubernetes command-line tool. - -Also install [RKE,]({{}}/rke/latest/en/installation/) the Rancher Kubernetes Engine, a Kubernetes distribution and command-line tool. - -### 1. Create the cluster configuration file - -In this section, you will create a Kubernetes cluster configuration file called `rancher-cluster.yml`. In a later step, when you set up the cluster with an RKE command, it will use this file to install Kubernetes on your nodes. - -Using the sample below as a guide, create the `rancher-cluster.yml` file. Replace the IP addresses in the `nodes` list with the IP address or DNS names of the 3 nodes you created. - -If your node has public and internal addresses, it is recommended to set the `internal_address:` so Kubernetes will use it for intra-cluster communication. Some services like AWS EC2 require setting the `internal_address:` if you want to use self-referencing security groups or firewalls. - -RKE will need to connect to each node over SSH, and it will look for a private key in the default location of `~/.ssh/id_rsa`. If your private key for a certain node is in a different location than the default, you will also need to configure the `ssh_key_path` option for that node. - -```yaml -nodes: - - address: 165.227.114.63 - internal_address: 172.16.22.12 - user: ubuntu - role: [controlplane, worker, etcd] - - address: 165.227.116.167 - internal_address: 172.16.32.37 - user: ubuntu - role: [controlplane, worker, etcd] - - address: 165.227.127.226 - internal_address: 172.16.42.73 - user: ubuntu - role: [controlplane, worker, etcd] - -services: - etcd: - snapshot: true - creation: 6h - retention: 24h - -# Required for external TLS termination with -# ingress-nginx v0.22+ -ingress: - provider: nginx - options: - use-forwarded-headers: "true" -``` - -
Common RKE Nodes Options
- -| Option | Required | Description | -| ------------------ | -------- | -------------------------------------------------------------------------------------- | -| `address` | yes | The public DNS or IP address | -| `user` | yes | A user that can run docker commands | -| `role` | yes | List of Kubernetes roles assigned to the node | -| `internal_address` | no | The private DNS or IP address for internal cluster traffic | -| `ssh_key_path` | no | Path to SSH private key used to authenticate to the node (defaults to `~/.ssh/id_rsa`) | - -> **Advanced Configurations:** RKE has many configuration options for customizing the install to suit your specific environment. -> -> Please see the [RKE Documentation]({{}}/rke/latest/en/config-options/) for the full list of options and capabilities. -> -> For tuning your etcd cluster for larger Rancher installations, see the [etcd settings guide]({{}}/rancher/v2.6/en/installation/resources/advanced/etcd/). -> -> For more information regarding Dockershim support, refer to [this page]({{}}/rancher/v2.6/en/installation/requirements/dockershim/) - -### 2. Run RKE - -``` -rke up --config ./rancher-cluster.yml -``` - -When finished, it should end with the line: `Finished building Kubernetes cluster successfully`. - -### 3. Test Your Cluster - -This section describes how to set up your workspace so that you can interact with this cluster using the `kubectl` command-line tool. - -Assuming you have installed `kubectl`, you need to place the `kubeconfig` file in a location where `kubectl` can reach it. The `kubeconfig` file contains the credentials necessary to access your cluster with `kubectl`. - -When you ran `rke up`, RKE should have created a `kubeconfig` file named `kube_config_cluster.yml`. This file has the credentials for `kubectl` and `helm`. - -> **Note:** If you have used a different file name from `rancher-cluster.yml`, then the kube config file will be named `kube_config_.yml`. - -Move this file to `$HOME/.kube/config`, or if you are working with multiple Kubernetes clusters, set the `KUBECONFIG` environmental variable to the path of `kube_config_cluster.yml`: - -``` -export KUBECONFIG=$(pwd)/kube_config_cluster.yml -``` - -Test your connectivity with `kubectl` and see if all your nodes are in `Ready` state: - -``` -kubectl get nodes - -NAME STATUS ROLES AGE VERSION -165.227.114.63 Ready controlplane,etcd,worker 11m v1.13.5 -165.227.116.167 Ready controlplane,etcd,worker 11m v1.13.5 -165.227.127.226 Ready controlplane,etcd,worker 11m v1.13.5 -``` - -### 4. Check the Health of Your Cluster Pods - -Check that all the required pods and containers are healthy are ready to continue. - -- Pods are in `Running` or `Completed` state. -- `READY` column shows all the containers are running (i.e. `3/3`) for pods with `STATUS` `Running` -- Pods with `STATUS` `Completed` are run-once Jobs. For these pods `READY` should be `0/1`. - -``` -kubectl get pods --all-namespaces - -NAMESPACE NAME READY STATUS RESTARTS AGE -ingress-nginx nginx-ingress-controller-tnsn4 1/1 Running 0 30s -ingress-nginx nginx-ingress-controller-tw2ht 1/1 Running 0 30s -ingress-nginx nginx-ingress-controller-v874b 1/1 Running 0 30s -kube-system canal-jp4hz 3/3 Running 0 30s -kube-system canal-z2hg8 3/3 Running 0 30s -kube-system canal-z6kpw 3/3 Running 0 30s -kube-system kube-dns-7588d5b5f5-sf4vh 3/3 Running 0 30s -kube-system kube-dns-autoscaler-5db9bbb766-jz2k6 1/1 Running 0 30s -kube-system metrics-server-97bc649d5-4rl2q 1/1 Running 0 30s -kube-system rke-ingress-controller-deploy-job-bhzgm 0/1 Completed 0 30s -kube-system rke-kubedns-addon-deploy-job-gl7t4 0/1 Completed 0 30s -kube-system rke-metrics-addon-deploy-job-7ljkc 0/1 Completed 0 30s -kube-system rke-network-plugin-deploy-job-6pbgj 0/1 Completed 0 30s -``` - -This confirms that you have successfully installed a Kubernetes cluster that the Rancher server will run on. - -### 5. Save Your Files - -> **Important** -> The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster. - -Save a copy of the following files in a secure location: - -- `rancher-cluster.yml`: The RKE cluster configuration file. -- `kube_config_cluster.yml`: The [Kubeconfig file]({{}}/rke/latest/en/kubeconfig/) for the cluster, this file contains credentials for full access to the cluster. -- `rancher-cluster.rkestate`: The [Kubernetes Cluster State file]({{}}/rke/latest/en/installation/#kubernetes-cluster-state), this file contains credentials for full access to the cluster.

_The Kubernetes Cluster State file is only created when using RKE v0.2.0 or higher._ - -> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file. - -### Issues or errors? - -See the [Troubleshooting]({{}}/rancher/v2.6/en/installation/resources/troubleshooting/) page. - - -### [Next: Install Rancher]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) - diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-rke2/ha-rke2.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-rke2/ha-rke2.md deleted file mode 100644 index f69c494b175..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-rke2/ha-rke2.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -title: Setting up a High-availability RKE2 Kubernetes Cluster for Rancher -shortTitle: Set up RKE2 for Rancher -weight: 2 ---- -_Tested on v2.5.6_ - -This section describes how to install a Kubernetes cluster according to the [best practices for the Rancher server environment.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#environment-for-kubernetes-installations) - -# Prerequisites - -These instructions assume you have set up three nodes, a load balancer, and a DNS record, as described in [this section.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-rke2-ha) - -Note that in order for RKE2 to work correctly with the load balancer, you need to set up two listeners: one for the supervisor on port 9345, and one for the Kubernetes API on port 6443. - -Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) To specify the RKE2 version, use the INSTALL_RKE2_VERSION environment variable when running the RKE2 installation script. -# Installing Kubernetes - -### 1. Install Kubernetes and Set up the RKE2 Server - -RKE2 server runs with embedded etcd so you will not need to set up an external datastore to run in HA mode. - -On the first node, you should set up the configuration file with your own pre-shared secret as the token. The token argument can be set on startup. - -If you do not specify a pre-shared secret, RKE2 will generate one and place it at /var/lib/rancher/rke2/server/node-token. - -To avoid certificate errors with the fixed registration address, you should launch the server with the tls-san parameter set. This option adds an additional hostname or IP as a Subject Alternative Name in the server's TLS cert, and it can be specified as a list if you would like to access via both the IP and the hostname. - -First, you must create the directory where the RKE2 config file is going to be placed: - -``` -mkdir -p /etc/rancher/rke2/ -``` - -Next, create the RKE2 config file at `/etc/rancher/rke2/config.yaml` using the following example: - -``` -token: my-shared-secret -tls-san: - - my-kubernetes-domain.com - - another-kubernetes-domain.com -``` -After that, you need to run the install command and enable and start rke2: - -``` -curl -sfL https://get.rke2.io | INSTALL_RKE2_CHANNEL=v1.20 sh - -systemctl enable rke2-server.service -systemctl start rke2-server.service -``` -1. To join the rest of the nodes, you need to configure each additional node with the same shared token or the one generated automatically. Here is an example of the configuration file: - - token: my-shared-secret - server: https://:9345 - tls-san: - - my-kubernetes-domain.com - - another-kubernetes-domain.com -After that, you need to run the installer and enable, then start, rke2: - - curl -sfL https://get.rke2.io | sh - - systemctl enable rke2-server.service - systemctl start rke2-server.service - - -1. Repeat the same command on your third RKE2 server node. - -### 2. Confirm that RKE2 is Running - -Once you've launched the rke2 server process on all server nodes, ensure that the cluster has come up properly with - -``` -/var/lib/rancher/rke2/bin/kubectl \ - --kubeconfig /etc/rancher/rke2/rke2.yaml get nodes -You should see your server nodes in the Ready state. -``` - -Then test the health of the cluster pods: -``` -/var/lib/rancher/rke2/bin/kubectl \ - --kubeconfig /etc/rancher/rke2/rke2.yaml get pods --all-namespaces -``` - -**Result:** You have successfully set up a RKE2 Kubernetes cluster. - -### 3. Save and Start Using the kubeconfig File - -When you installed RKE2 on each Rancher server node, a `kubeconfig` file was created on the node at `/etc/rancher/rke2/rke2.yaml`. This file contains credentials for full access to the cluster, and you should save this file in a secure location. - -To use this `kubeconfig` file, - -1. Install [kubectl,](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) a Kubernetes command-line tool. -2. Copy the file at `/etc/rancher/rke2/rke2.yaml` and save it to the directory `~/.kube/config` on your local machine. -3. In the kubeconfig file, the `server` directive is defined as localhost. Configure the server as the DNS of your control-plane load balancer, on port 6443. (The RKE2 Kubernetes API Server uses port 6443, while the Rancher server will be served via the NGINX Ingress on ports 80 and 443.) Here is an example `rke2.yaml`: - -```yml -apiVersion: v1 -clusters: -- cluster: - certificate-authority-data: [CERTIFICATE-DATA] - server: [LOAD-BALANCER-DNS]:6443 # Edit this line - name: default -contexts: -- context: - cluster: default - user: default - name: default -current-context: default -kind: Config -preferences: {} -users: -- name: default - user: - password: [PASSWORD] - username: admin -``` - -**Result:** You can now use `kubectl` to manage your RKE2 cluster. If you have more than one kubeconfig file, you can specify which one you want to use by passing in the path to the file when using `kubectl`: - -``` -kubectl --kubeconfig ~/.kube/config/rke2.yaml get pods --all-namespaces -``` - -For more information about the `kubeconfig` file, refer to the [RKE2 documentation](https://docs.rke2.io/cluster_access/) or the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) about organizing cluster access using `kubeconfig` files. - -### 4. Check the Health of Your Cluster Pods - -Now that you have set up the `kubeconfig` file, you can use `kubectl` to access the cluster from your local machine. - -Check that all the required pods and containers are healthy are ready to continue: - -``` -/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml get pods -A -NAMESPACE NAME READY STATUS RESTARTS AGE -kube-system cloud-controller-manager-rke2-server-1 1/1 Running 0 2m28s -kube-system cloud-controller-manager-rke2-server-2 1/1 Running 0 61s -kube-system cloud-controller-manager-rke2-server-3 1/1 Running 0 49s -kube-system etcd-rke2-server-1 1/1 Running 0 2m13s -kube-system etcd-rke2-server-2 1/1 Running 0 87s -kube-system etcd-rke2-server-3 1/1 Running 0 56s -kube-system helm-install-rke2-canal-hs6sx 0/1 Completed 0 2m17s -kube-system helm-install-rke2-coredns-xmzm8 0/1 Completed 0 2m17s -kube-system helm-install-rke2-ingress-nginx-flwnl 0/1 Completed 0 2m17s -kube-system helm-install-rke2-metrics-server-7sggn 0/1 Completed 0 2m17s -kube-system kube-apiserver-rke2-server-1 1/1 Running 0 116s -kube-system kube-apiserver-rke2-server-2 1/1 Running 0 66s -kube-system kube-apiserver-rke2-server-3 1/1 Running 0 48s -kube-system kube-controller-manager-rke2-server-1 1/1 Running 0 2m30s -kube-system kube-controller-manager-rke2-server-2 1/1 Running 0 57s -kube-system kube-controller-manager-rke2-server-3 1/1 Running 0 42s -kube-system kube-proxy-rke2-server-1 1/1 Running 0 2m25s -kube-system kube-proxy-rke2-server-2 1/1 Running 0 59s -kube-system kube-proxy-rke2-server-3 1/1 Running 0 85s -kube-system kube-scheduler-rke2-server-1 1/1 Running 0 2m30s -kube-system kube-scheduler-rke2-server-2 1/1 Running 0 57s -kube-system kube-scheduler-rke2-server-3 1/1 Running 0 42s -kube-system rke2-canal-b9lvm 2/2 Running 0 91s -kube-system rke2-canal-khwp2 2/2 Running 0 2m5s -kube-system rke2-canal-swfmq 2/2 Running 0 105s -kube-system rke2-coredns-rke2-coredns-547d5499cb-6tvwb 1/1 Running 0 92s -kube-system rke2-coredns-rke2-coredns-547d5499cb-rdttj 1/1 Running 0 2m8s -kube-system rke2-coredns-rke2-coredns-autoscaler-65c9bb465d-85sq5 1/1 Running 0 2m8s -kube-system rke2-ingress-nginx-controller-69qxc 1/1 Running 0 52s -kube-system rke2-ingress-nginx-controller-7hprp 1/1 Running 0 52s -kube-system rke2-ingress-nginx-controller-x658h 1/1 Running 0 52s -kube-system rke2-metrics-server-6564db4569-vdfkn 1/1 Running 0 66s -``` - -**Result:** You have confirmed that you can access the cluster with `kubectl` and the RKE2 cluster is running successfully. Now the Rancher management server can be installed on the cluster. diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-with-external-db/ha-with-external-db.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-with-external-db/ha-with-external-db.md deleted file mode 100644 index bce53d8b157..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/ha-with-external-db/ha-with-external-db.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Setting up a High-availability K3s Kubernetes Cluster for Rancher -shortTitle: Set up K3s for Rancher -weight: 2 ---- - -This section describes how to install a Kubernetes cluster according to the [best practices for the Rancher server environment.]({{}}/rancher/v2.6/en/overview/architecture-recommendations/#environment-for-kubernetes-installations) - -For systems without direct internet access, refer to the air gap installation instructions. - -> **Single-node Installation Tip:** -> In a single-node Kubernetes cluster, the Rancher server does not have high availability, which is important for running Rancher in production. However, installing Rancher on a single-node cluster can be useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path. -> -> To set up a single-node K3s cluster, run the Rancher server installation command on just one node instead of two nodes. -> -> In both single-node setups, Rancher can be installed with Helm on the Kubernetes cluster in the same way that it would be installed on any other cluster. - -# Prerequisites - -These instructions assume you have set up two nodes, a load balancer, a DNS record, and an external MySQL database as described in [this section.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db/) - -Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script. -# Installing Kubernetes - -### 1. Install Kubernetes and Set up the K3s Server - -When running the command to start the K3s Kubernetes API server, you will pass in an option to use the external datastore that you set up earlier. - -1. Connect to one of the Linux nodes that you have prepared to run the Rancher server. -1. On the Linux node, run this command to start the K3s server and connect it to the external datastore: - ``` - curl -sfL https://get.k3s.io | sh -s - server \ - --datastore-endpoint="mysql://username:password@tcp(hostname:3306)/database-name" - ``` - To specify the K3s version, use the INSTALL_K3S_VERSION environment variable: - ```sh - curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=vX.Y.Z sh -s - server \ - --datastore-endpoint="mysql://username:password@tcp(hostname:3306)/database-name" - ``` - Note: The datastore endpoint can also be passed in using the environment variable `$K3S_DATASTORE_ENDPOINT`. - -1. Repeat the same command on your second K3s server node. - -### 2. Confirm that K3s is Running - -To confirm that K3s has been set up successfully, run the following command on either of the K3s server nodes: -``` -sudo k3s kubectl get nodes -``` - -Then you should see two nodes with the master role: -``` -ubuntu@ip-172-31-60-194:~$ sudo k3s kubectl get nodes -NAME STATUS ROLES AGE VERSION -ip-172-31-60-194 Ready master 44m v1.17.2+k3s1 -ip-172-31-63-88 Ready master 6m8s v1.17.2+k3s1 -``` - -Then test the health of the cluster pods: -``` -sudo k3s kubectl get pods --all-namespaces -``` - -**Result:** You have successfully set up a K3s Kubernetes cluster. - -### 3. Save and Start Using the kubeconfig File - -When you installed K3s on each Rancher server node, a `kubeconfig` file was created on the node at `/etc/rancher/k3s/k3s.yaml`. This file contains credentials for full access to the cluster, and you should save this file in a secure location. - -To use this `kubeconfig` file, - -1. Install [kubectl,](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) a Kubernetes command-line tool. -2. Copy the file at `/etc/rancher/k3s/k3s.yaml` and save it to the directory `~/.kube/config` on your local machine. -3. In the kubeconfig file, the `server` directive is defined as localhost. Configure the server as the DNS of your load balancer, referring to port 6443. (The Kubernetes API server will be reached at port 6443, while the Rancher server will be reached at ports 80 and 443.) Here is an example `k3s.yaml`: - -```yml -apiVersion: v1 -clusters: -- cluster: - certificate-authority-data: [CERTIFICATE-DATA] - server: [LOAD-BALANCER-DNS]:6443 # Edit this line - name: default -contexts: -- context: - cluster: default - user: default - name: default -current-context: default -kind: Config -preferences: {} -users: -- name: default - user: - password: [PASSWORD] - username: admin -``` - -**Result:** You can now use `kubectl` to manage your K3s cluster. If you have more than one kubeconfig file, you can specify which one you want to use by passing in the path to the file when using `kubectl`: - -``` -kubectl --kubeconfig ~/.kube/config/k3s.yaml get pods --all-namespaces -``` - -For more information about the `kubeconfig` file, refer to the [K3s documentation]({{}}/k3s/latest/en/cluster-access/) or the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) about organizing cluster access using `kubeconfig` files. - -### 4. Check the Health of Your Cluster Pods - -Now that you have set up the `kubeconfig` file, you can use `kubectl` to access the cluster from your local machine. - -Check that all the required pods and containers are healthy are ready to continue: - -``` -ubuntu@ip-172-31-60-194:~$ sudo kubectl get pods --all-namespaces -NAMESPACE NAME READY STATUS RESTARTS AGE -kube-system metrics-server-6d684c7b5-bw59k 1/1 Running 0 8d -kube-system local-path-provisioner-58fb86bdfd-fmkvd 1/1 Running 0 8d -kube-system coredns-d798c9dd-ljjnf 1/1 Running 0 8d -``` - -**Result:** You have confirmed that you can access the cluster with `kubectl` and the K3s cluster is running successfully. Now the Rancher management server can be installed on the cluster. diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/how-ha-works/how-ha-works.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/how-ha-works/how-ha-works.md deleted file mode 100644 index 796e300cfbb..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/how-ha-works/how-ha-works.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: About High-availability Installations -weight: 1 ---- - -We recommend using Helm, a Kubernetes package manager, to install Rancher on a dedicated Kubernetes cluster. This is called a high-availability Kubernetes installation because increased availability is achieved by running Rancher on multiple nodes. - -In a standard installation, Kubernetes is first installed on three nodes that are hosted in an infrastructure provider such as Amazon's EC2 or Google Compute Engine. - -Then Helm is used to install Rancher on top of the Kubernetes cluster. Helm uses Rancher's Helm chart to install a replica of Rancher on each of the three nodes in the Kubernetes cluster. We recommend using a load balancer to direct traffic to each replica of Rancher in the cluster, in order to increase Rancher's availability. - -The Rancher server data is stored on etcd. This etcd database also runs on all three nodes, and requires an odd number of nodes so that it can always elect a leader with a majority of the etcd cluster. If the etcd database cannot elect a leader, etcd can fail, requiring the cluster to be restored from backup. - -For information on how Rancher works, regardless of the installation method, refer to the [architecture section.]({{}}/rancher/v2.6/en/overview/architecture) - -### Recommended Architecture - -- DNS for Rancher should resolve to a layer 4 load balancer -- The Load Balancer should forward port TCP/80 and TCP/443 to all 3 nodes in the Kubernetes cluster. -- The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. -- The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. - -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
-![High-availability Kubernetes Installation of Rancher]({{}}/img/rancher/ha/rancher2ha.svg) -Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/ec2-node.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/ec2-node.md deleted file mode 100644 index c4211bae501..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/ec2-node.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Setting up Nodes in Amazon EC2 -weight: 3 ---- - -In this tutorial, you will learn one way to set up Linux nodes for the Rancher management server. These nodes will fulfill the node requirements for [OS, Docker, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -If the Rancher server will be installed on an RKE Kubernetes cluster, you should provision three instances. - -If the Rancher server will be installed on a K3s Kubernetes cluster, you only need to provision two instances. - -If the Rancher server is installed in a single Docker container, you only need one instance. - -### 1. Optional Preparation - -- **Create IAM role:** To allow Rancher to manipulate AWS resources, such as provisioning new storage or new nodes, you will need to configure Amazon as a cloud provider. There are several things you'll need to do to set up the cloud provider on EC2, but part of this process is setting up an IAM role for the Rancher server nodes. For the full details on setting up the cloud provider, refer to this [page.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/cloud-providers/) -- **Create security group:** We also recommend setting up a security group for the Rancher nodes that complies with the [port requirements for Rancher nodes.]({{}}/rancher/v2.6/en/installation/requirements/#port-requirements) - -### 2. Provision Instances - -1. Log into the [Amazon AWS EC2 Console](https://console.aws.amazon.com/ec2/) to get started. Make sure to take note of the **Region** where your EC2 instances (Linux nodes) are created, because all of the infrastructure for the Rancher management server should be in the same region. -1. In the left panel, click **Instances**. -1. Click **Launch Instance**. -1. In the section called **Step 1: Choose an Amazon Machine Image (AMI),** we will use Ubuntu 18.04 as the Linux OS, using `ami-0d1cd67c26f5fca19 (64-bit x86)`. Go to the Ubuntu AMI and click **Select**. -1. In the **Step 2: Choose an Instance Type** section, select the `t2.medium` type. -1. Click **Next: Configure Instance Details**. -1. In the **Number of instances** field, enter the number of instances. A high-availability K3s cluster requires only two instances, while a high-availability RKE cluster requires three instances. -1. Optional: If you created an IAM role for Rancher to manipulate AWS resources, select the new IAM role in the **IAM role** field. -1. Click **Next: Add Storage,** **Next: Add Tags,** and **Next: Configure Security Group**. -1. In **Step 6: Configure Security Group,** select a security group that complies with the [port requirements]({{}}/rancher/v2.6/en/installation/requirements/#port-requirements) for Rancher nodes. -1. Click **Review and Launch**. -1. Click **Launch**. -1. Choose a new or existing key pair that you will use to connect to your instance later. If you are using an existing key pair, make sure you already have access to the private key. -1. Click **Launch Instances**. - - -**Result:** You have created Rancher nodes that satisfy the requirements for OS, hardware, and networking. - -**Note:** If the nodes are being used for an RKE Kubernetes cluster, install Docker on each node in the next step. For a K3s Kubernetes cluster, the nodes are now ready to install K3s. - -### 3. Install Docker and Create User for RKE Kubernetes Cluster Nodes - -1. From the [AWS EC2 console,](https://console.aws.amazon.com/ec2/) click **Instances** in the left panel. -1. Go to the instance that you want to install Docker on. Select the instance and click **Actions > Connect**. -1. Connect to the instance by following the instructions on the screen that appears. Copy the Public DNS of the instance. An example command to SSH into the instance is as follows: -``` -sudo ssh -i [path-to-private-key] ubuntu@[public-DNS-of-instance] -``` -1. Run the following command on the instance to install Docker with one of Rancher's installation scripts: -``` -curl https://releases.rancher.com/install-docker/18.09.sh | sh -``` -1. When you are connected to the instance, run the following command on the instance to create a user: -``` -sudo usermod -aG docker ubuntu -``` -1. Repeat these steps so that Docker is installed on each node that will eventually run the Rancher management server. - -> To find out whether a script is available for installing a certain Docker version, refer to this [GitHub repository,](https://github.com/rancher/install-docker) which contains all of Rancher’s Docker installation scripts. - -**Result:** You have set up Rancher server nodes that fulfill all the node requirements for OS, Docker, hardware and networking. - -### Next Steps for RKE Kubernetes Cluster Nodes - -If you are going to install an RKE cluster on the new nodes, take note of the **IPv4 Public IP** and **Private IP** of each node. This information can be found on the **Description** tab for each node after it is created. The public and private IP will be used to populate the `address` and `internal_address` of each node in the RKE cluster configuration file, `rancher-cluster.yml`. - -RKE will also need access to the private key to connect to each node. Therefore, you might want to take note of the path to your private keys to connect to the nodes, which can also be included in the `rancher-cluster.yml` under the `ssh_key_path` directive for each node. diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db/infra-for-ha-with-external-db.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db/infra-for-ha-with-external-db.md deleted file mode 100644 index 4e13afe13a8..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db/infra-for-ha-with-external-db.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: 'Set up Infrastructure for a High Availability K3s Kubernetes Cluster' -weight: 1 ---- - -This tutorial is intended to help you provision the underlying infrastructure for a Rancher management server. - -The recommended infrastructure for the Rancher-only Kubernetes cluster differs depending on whether Rancher will be installed on a K3s Kubernetes cluster, an RKE Kubernetes cluster, or a single Docker container. - -For more information about each installation option, refer to [this page.]({{}}/rancher/v2.6/en/installation) - -> **Note:** These nodes must be in the same region. You may place these servers in separate availability zones (datacenter). - -To install the Rancher management server on a high-availability K3s cluster, we recommend setting up the following infrastructure: - -- **Two Linux nodes,** typically virtual machines, in the infrastructure provider of your choice. -- **An external database** to store the cluster data. We recommend MySQL. -- **A load balancer** to direct traffic to the two nodes. -- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it. - -### 1. Set up Linux Nodes - -Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node) for setting up nodes as instances in Amazon EC2. - -### 2. Set up External Datastore - -The ability to run Kubernetes using a datastore other than etcd sets K3s apart from other Kubernetes distributions. This feature provides flexibility to Kubernetes operators. The available options allow you to select a datastore that best fits your use case. - -For a high-availability K3s installation, you will need to set a [MySQL](https://www.mysql.com/) external database. Rancher has been tested on K3s Kubernetes clusters using MySQL version 5.7 as the datastore. - -When you install Kubernetes using the K3s installation script, you will pass in details for K3s to connect to the database. - -For an example of one way to set up the MySQL database, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/) for setting up MySQL on Amazon's RDS service. - -For the complete list of options that are available for configuring a K3s cluster datastore, refer to the [K3s documentation.]({{}}/k3s/latest/en/installation/datastore/) - -### 3. Set up the Load Balancer - -You will also need to set up a load balancer to direct traffic to the Rancher replica on both nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server. - -When Kubernetes gets set up in a later step, the K3s tool will deploy a Traefik Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames. - -When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the Traefik Ingress controller to listen for traffic destined for the Rancher hostname. The Traefik Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster. - -For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer: - -- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment. -- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{}}/rancher/v2.6/en/installation/resources/chart-options/#external-tls-termination) - -For an example showing how to set up an NGINX load balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/) - -For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/) - -> **Important:** -> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications. - -### 4. Set up the DNS Record - -Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer. - -Depending on your environment, this may be an A record pointing to the load balancer IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on. - -You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one. - -For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha/infra-for-ha.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha/infra-for-ha.md deleted file mode 100644 index 6c55c72f305..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha/infra-for-ha.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: 'Set up Infrastructure for a High Availability RKE Kubernetes Cluster' -weight: 2 ---- - -This tutorial is intended to help you create a high-availability RKE cluster that can be used to install a Rancher server. - -> **Note:** These nodes must be in the same region. You may place these servers in separate availability zones (datacenter). - -To install the Rancher management server on a high-availability RKE cluster, we recommend setting up the following infrastructure: - -- **Three Linux nodes,** typically virtual machines, in an infrastructure provider such as Amazon's EC2, Google Compute Engine, or vSphere. -- **A load balancer** to direct front-end traffic to the three nodes. -- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it. - -These nodes must be in the same region/data center. You may place these servers in separate availability zones. - -### Why three nodes? - -In an RKE cluster, Rancher server data is stored on etcd. This etcd database runs on all three nodes. - -The etcd database requires an odd number of nodes so that it can always elect a leader with a majority of the etcd cluster. If the etcd database cannot elect a leader, etcd can suffer from [split brain](https://www.quora.com/What-is-split-brain-in-distributed-systems), requiring the cluster to be restored from backup. If one of the three etcd nodes fails, the two remaining nodes can elect a leader because they have the majority of the total number of etcd nodes. - -### 1. Set up Linux Nodes - -Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/) for setting up nodes as instances in Amazon EC2. - -### 2. Set up the Load Balancer - -You will also need to set up a load balancer to direct traffic to the Rancher replica on any of the three nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server. - -When Kubernetes gets set up in a later step, the RKE tool will deploy an NGINX Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames. - -When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the NGINX Ingress controller to listen for traffic destined for the Rancher hostname. The NGINX Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster. - -For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer: - -- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment. -- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{}}/rancher/v2.6/en/installation/resources/chart-options/#external-tls-termination) - -For an example showing how to set up an NGINX load balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/) - -For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/) - -> **Important:** -> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications. - -### 3. Set up the DNS Record - -Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer. - -Depending on your environment, this may be an A record pointing to the LB IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on. - -You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one. - -For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-rke2-ha/infra-for-rke2-ha.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-rke2-ha/infra-for-rke2-ha.md deleted file mode 100644 index e03f8ccc868..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-rke2-ha/infra-for-rke2-ha.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: 'Set up Infrastructure for a High Availability RKE2 Kubernetes Cluster' -weight: 1 ---- - -This tutorial is intended to help you provision the underlying infrastructure for a Rancher management server. - -The recommended infrastructure for the Rancher-only Kubernetes cluster differs depending on whether Rancher will be installed on a RKE2 Kubernetes cluster, an RKE Kubernetes cluster, or a single Docker container. - -> **Note:** These nodes must be in the same region. You may place these servers in separate availability zones (datacenter). - -To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure: - -- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice. -- **A load balancer** to direct traffic to the two nodes. -- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it. - -### 1. Set up Linux Nodes - -Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{}}/rancher/v2.6/en/installation/requirements/) - -For an example of one way to set up Linux nodes, refer to this [tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node) for setting up nodes as instances in Amazon EC2. - -### 2. Set up the Load Balancer - -You will also need to set up a load balancer to direct traffic to the Rancher replica on all nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server. - -When Kubernetes gets set up in a later step, the RKE2 tool will deploy an Nginx Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames. - -When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the Nginx Ingress controller to listen for traffic destined for the Rancher hostname. The Nginx Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster. - -For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer: - -- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment. -- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{}}/rancher/v2.6/en/installation/resources/chart-options/#external-tls-termination) - -For an example showing how to set up an NGINX load balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/) - -For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/) - -> **Important:** -> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications. - -### 4. Set up the DNS Record - -Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer. - -Depending on your environment, this may be an A record pointing to the load balancer IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on. - -You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one. - -For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infrastructure-tutorials.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infrastructure-tutorials.md deleted file mode 100644 index 89f4a7ac795..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/infrastructure-tutorials.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Don't have infrastructure for your Kubernetes cluster? Try one of these tutorials. -shortTitle: Infrastructure Tutorials -weight: 5 ---- - -To set up infrastructure for a high-availability K3s Kubernetes cluster with an external DB, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha-with-external-db/) - - -To set up infrastructure for a high-availability RKE Kubernetes cluster, refer to [this page.]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha/) diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/nginx.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/nginx.md deleted file mode 100644 index e918b1c379b..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/nginx.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Setting up an NGINX Load Balancer -weight: 4 ---- - -NGINX will be configured as Layer 4 load balancer (TCP) that forwards connections to one of your Rancher nodes. - -In this configuration, the load balancer is positioned in front of your nodes. The load balancer can be any host capable of running NGINX. - -One caveat: do not use one of your Rancher nodes as the load balancer. - -> These examples show the load balancer being configured to direct traffic to three Rancher server nodes. If Rancher is installed on an RKE Kubernetes cluster, three nodes are required. If Rancher is installed on a K3s Kubernetes cluster, only two nodes are required. - -## Install NGINX - -Start by installing NGINX on the node you want to use as a load balancer. NGINX has packages available for all known operating systems. The versions tested are `1.14` and `1.15`. For help installing NGINX, refer to their [install documentation](https://www.nginx.com/resources/wiki/start/topics/tutorials/install/). - -The `stream` module is required, which is present when using the official NGINX packages. Please refer to your OS documentation on how to install and enable the NGINX `stream` module on your operating system. - -## Create NGINX Configuration - -After installing NGINX, you need to update the NGINX configuration file, `nginx.conf`, with the IP addresses for your nodes. - -1. Copy and paste the code sample below into your favorite text editor. Save it as `nginx.conf`. - -2. From `nginx.conf`, replace both occurrences (port 80 and port 443) of ``, ``, and `` with the IPs of your nodes. - - > **Note:** See [NGINX Documentation: TCP and UDP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/) for all configuration options. - -
Example NGINX config
- ``` - worker_processes 4; - worker_rlimit_nofile 40000; - - events { - worker_connections 8192; - } - - stream { - upstream rancher_servers_http { - least_conn; - server :80 max_fails=3 fail_timeout=5s; - server :80 max_fails=3 fail_timeout=5s; - server :80 max_fails=3 fail_timeout=5s; - } - server { - listen 80; - proxy_pass rancher_servers_http; - } - - upstream rancher_servers_https { - least_conn; - server :443 max_fails=3 fail_timeout=5s; - server :443 max_fails=3 fail_timeout=5s; - server :443 max_fails=3 fail_timeout=5s; - } - server { - listen 443; - proxy_pass rancher_servers_https; - } - - } - ``` - - -3. Save `nginx.conf` to your load balancer at the following path: `/etc/nginx/nginx.conf`. - -4. Load the updates to your NGINX configuration by running the following command: - - ``` - # nginx -s reload - ``` - -## Option - Run NGINX as Docker container - -Instead of installing NGINX as a package on the operating system, you can rather run it as a Docker container. Save the edited **Example NGINX config** as `/etc/nginx.conf` and run the following command to launch the NGINX container: - -``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -v /etc/nginx.conf:/etc/nginx/nginx.conf \ - nginx:1.14 -``` diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md deleted file mode 100644 index be1f6102b75..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md +++ /dev/null @@ -1,179 +0,0 @@ ---- -title: Setting up Amazon ELB Network Load Balancer -weight: 5 ---- - -This how-to guide describes how to set up a Network Load Balancer (NLB) in Amazon's EC2 service that will direct traffic to multiple instances on EC2. - -These examples show the load balancer being configured to direct traffic to three Rancher server nodes. If Rancher is installed on an RKE Kubernetes cluster, three nodes are required. If Rancher is installed on a K3s Kubernetes cluster, only two nodes are required. - -This tutorial is about one possible way to set up your load balancer, not the only way. Other types of load balancers, such as a Classic Load Balancer or Application Load Balancer, could also direct traffic to the Rancher server nodes. - -Rancher only supports using the Amazon NLB when terminating traffic in `tcp` mode for port 443 rather than `tls` mode. This is due to the fact that the NLB does not inject the correct headers into requests when terminated at the NLB. This means that if you want to use certificates managed by the Amazon Certificate Manager (ACM), you should use an ALB. - -# Setting up the Load Balancer - -Configuring an Amazon NLB is a multistage process: - -1. [Create Target Groups](#1-create-target-groups) -2. [Register Targets](#2-register-targets) -3. [Create Your NLB](#3-create-your-nlb) -4. [Add listener to NLB for TCP port 80](#4-add-listener-to-nlb-for-tcp-port-80) - -# Requirements - -These instructions assume you have already created Linux instances in EC2. The load balancer will direct traffic to these nodes. - -# 1. Create Target Groups - -Begin by creating two target groups for the **TCP** protocol, one with TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups. - -Your first NLB configuration step is to create two target groups. Technically, only port 443 is needed to access Rancher, but it's convenient to add a listener for port 80, because traffic to port 80 will be automatically redirected to port 443. - -Regardless of whether an NGINX Ingress or Traefik Ingress controller is used, the Ingress should redirect traffic from port 80 to port 443. - -1. Log into the [Amazon AWS Console](https://console.aws.amazon.com/ec2/) to get started. Make sure to select the **Region** where your EC2 instances (Linux nodes) are created. -1. Select **Services** and choose **EC2**, find the section **Load Balancing** and open **Target Groups**. -1. Click **Create target group** to create the first target group, regarding TCP port 443. - -> **Note:** Health checks are handled differently based on the Ingress. For details, refer to [this section.](#health-check-paths-for-nginx-ingress-and-traefik-ingresses) - -### Target Group (TCP port 443) - -Configure the first target group according to the table below. - -| Option | Setting | -|-------------------|-------------------| -| Target Group Name | `rancher-tcp-443` | -| Target type | `instance` | -| Protocol | `TCP` | -| Port | `443` | -| VPC | Choose your VPC | - -Health check settings: - -| Option | Setting | -|---------------------|-----------------| -| Protocol | TCP | -| Port | `override`,`80` | -| Healthy threshold | `3` | -| Unhealthy threshold | `3` | -| Timeout | `6 seconds` | -| Interval | `10 seconds` | - -Click **Create target group** to create the second target group, regarding TCP port 80. - -### Target Group (TCP port 80) - -Configure the second target group according to the table below. - -| Option | Setting | -|-------------------|------------------| -| Target Group Name | `rancher-tcp-80` | -| Target type | `instance` | -| Protocol | `TCP` | -| Port | `80` | -| VPC | Choose your VPC | - - -Health check settings: - -| Option |Setting | -|---------------------|----------------| -| Protocol | TCP | -| Port | `traffic port` | -| Healthy threshold | `3` | -| Unhealthy threshold | `3` | -| Timeout | `6 seconds` | -| Interval | `10 seconds` | - -# 2. Register Targets - -Next, add your Linux nodes to both target groups. - -Select the target group named **rancher-tcp-443**, click the tab **Targets** and choose **Edit**. - -{{< img "/img/rancher/ha/nlb/edit-targetgroup-443.png" "Edit target group 443">}} - -Select the instances (Linux nodes) you want to add, and click **Add to registered**. - -*** -**Screenshot Add targets to target group TCP port 443**
- -{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}} - -*** -**Screenshot Added targets to target group TCP port 443**
- -{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}} - -When the instances are added, click **Save** on the bottom right of the screen. - -Repeat those steps, replacing **rancher-tcp-443** with **rancher-tcp-80**. The same instances need to be added as targets to this target group. - -# 3. Create Your NLB - -Use Amazon's Wizard to create a Network Load Balancer. As part of this process, you'll add the target groups you created in [1. Create Target Groups](#1-create-target-groups). - -1. From your web browser, navigate to the [Amazon EC2 Console](https://console.aws.amazon.com/ec2/). - -2. From the navigation pane, choose **LOAD BALANCING** > **Load Balancers**. - -3. Click **Create Load Balancer**. - -4. Choose **Network Load Balancer** and click **Create**. Then complete each form. - -- [Step 1: Configure Load Balancer](#step-1-configure-load-balancer) -- [Step 2: Configure Routing](#step-2-configure-routing) -- [Step 3: Register Targets](#step-3-register-targets) -- [Step 4: Review](#step-4-review) - -### Step 1: Configure Load Balancer - -Set the following fields in the form: - -- **Name:** `rancher` -- **Scheme:** `internal` or `internet-facing`. The scheme that you choose for your NLB is dependent on the configuration of your instances and VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`. -- **Listeners:** The Load Balancer Protocol should be `TCP` and the corresponding Load Balancer Port should be set to `443`. -- **Availability Zones:** Select Your **VPC** and **Availability Zones**. - -### Step 2: Configure Routing - -1. From the **Target Group** drop-down, choose **Existing target group**. -1. From the **Name** drop-down, choose `rancher-tcp-443`. -1. Open **Advanced health check settings**, and configure **Interval** to `10 seconds`. - -### Step 3: Register Targets - -Since you registered your targets earlier, all you have to do is click **Next: Review**. - -### Step 4: Review - -Look over the load balancer details and click **Create** when you're satisfied. - -After AWS creates the NLB, click **Close**. - -# 4. Add listener to NLB for TCP port 80 - -1. Select your newly created NLB and select the **Listeners** tab. - -2. Click **Add listener**. - -3. Use `TCP`:`80` as **Protocol** : **Port** - -4. Click **Add action** and choose **Forward to..**. - -5. From the **Forward to** drop-down, choose `rancher-tcp-80`. - -6. Click **Save** in the top right of the screen. - -# Health Check Paths for NGINX Ingress and Traefik Ingresses - -K3s and RKE Kubernetes clusters handle health checks differently because they use different Ingresses by default. - -For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress. - -- **Traefik:** The health check path is `/ping`. By default `/ping` is always matched (regardless of Host), and a response from [Traefik itself](https://docs.traefik.io/operations/ping/) is always served. -- **NGINX Ingress:** The default backend of the NGINX Ingress controller has a `/healthz` endpoint. By default `/healthz` is always matched (regardless of Host), and a response from [`ingress-nginx` itself](https://github.com/kubernetes/ingress-nginx/blob/0cbe783f43a9313c9c26136e888324b1ee91a72f/charts/ingress-nginx/values.yaml#L212) is always served. - -To simulate an accurate health check, it is a best practice to use the Host header (Rancher hostname) combined with `/ping` or `/healthz` (for K3s or for RKE clusters, respectively) wherever possible, to get a response from the Rancher Pods, not the Ingress. diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/rds.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/rds.md deleted file mode 100644 index 80144a68e0d..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/rds.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Setting up a MySQL Database in Amazon RDS -weight: 4 ---- -This tutorial describes how to set up a MySQL database in Amazon's RDS. - -This database can later be used as an external datastore for a high-availability K3s Kubernetes cluster. - -1. Log into the [Amazon AWS RDS Console](https://console.aws.amazon.com/rds/) to get started. Make sure to select the **Region** where your EC2 instances (Linux nodes) are created. -1. In the left panel, click **Databases**. -1. Click **Create database**. -1. In the **Engine type** section, click **MySQL**. -1. In the **Version** section, choose **MySQL 5.7.22**. -1. In **Settings** section, under **Credentials Settings,** enter a master password for the **admin** master username. Confirm the password. -1. Expand the **Additional configuration** section. In the **Initial database name** field, enter a name. The name can have only letters, numbers, and underscores. This name will be used to connect to the database. -1. Click **Create database**. - -You'll need to capture the following information about the new database so that the K3s Kubernetes cluster can connect to it. - -To see this information in the Amazon RDS console, click **Databases,** and click the name of the database that you created. - -- **Username:** Use the admin username. -- **Password:** Use the admin password. -- **Hostname:** Use the **Endpoint** as the hostname. The endpoint is available in the **Connectivity & security** section. -- **Port:** The port should be 3306 by default. You can confirm it in the **Connectivity & security** section. -- **Database name:** Confirm the name by going to the **Configuration** tab. The name is listed under **DB name**. - -This information will be used to connect to the database in the following format: - -``` -mysql://username:password@tcp(hostname:3306)/database-name -``` - -For more information on configuring the datastore for K3s, refer to the [K3s documentation.]({{}}/k3s/latest/en/installation/datastore/) diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/k8s-tutorials.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/k8s-tutorials.md deleted file mode 100644 index d9947f5ace0..00000000000 --- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/k8s-tutorials.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Don't have a Kubernetes cluster? Try one of these tutorials." -weight: 4 ---- - -This section contains information on how to install a Kubernetes cluster that the Rancher server can be installed on. - -Rancher can run on any Kubernetes cluster. diff --git a/versioned_docs/version-2.6/installation/resources/local-system-charts/local-system-charts.md b/versioned_docs/version-2.6/installation/resources/local-system-charts/local-system-charts.md deleted file mode 100644 index 3e39fe26ca0..00000000000 --- a/versioned_docs/version-2.6/installation/resources/local-system-charts/local-system-charts.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Setting up Local System Charts for Air Gapped Installations -weight: 120 ---- - -The [System Charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. - -In an air gapped installation of Rancher, you will need to configure Rancher to use a local copy of the system charts. This section describes how to use local system charts using a CLI flag. - -# Using Local System Charts - -A local copy of `system-charts` has been packaged into the `rancher/rancher` container. To be able to use these features in an air gap install, you will need to run the Rancher install command with an extra environment variable, `CATTLE_SYSTEM_CATALOG=bundled`, which tells Rancher to use the local copy of the charts instead of attempting to fetch them from GitHub. - -Example commands for a Rancher installation with a bundled `system-charts` are included in the [air gap installation]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) instructions for Docker and Helm installs. - diff --git a/versioned_docs/version-2.6/installation/resources/resources.md b/versioned_docs/version-2.6/installation/resources/resources.md deleted file mode 100644 index 94fe05dda8c..00000000000 --- a/versioned_docs/version-2.6/installation/resources/resources.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Resources -weight: 5 ---- - -### Docker Installations - -The [single-node Docker installation]({{}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker) is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster using Helm, you install the Rancher server component on a single node using a `docker run` command. - -Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server. - -### Air Gapped Installations - -Follow [these steps]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap) to install the Rancher server in an air gapped environment. - -An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. - -### Advanced Options - -When installing Rancher, there are several advanced options that can be enabled during installation. Within each install guide, these options are presented. Learn more about these options: - -- [Custom CA Certificate]({{}}/rancher/v2.6/en/installation/resources/custom-ca-root-certificate/) -- [API Audit Log]({{}}/rancher/v2.6/en/installation/resources/advanced/api-audit-log/) -- [TLS Settings]({{}}/rancher/v2.6/en/installation/resources/tls-settings/) -- [etcd configuration]({{}}/rancher/v2.6/en/installation/resources/advanced/etcd/) -- [Local System Charts for Air Gap Installations]({{}}/rancher/v2.6/en/installation/resources/local-system-charts) | v2.3.0 | diff --git a/versioned_docs/version-2.6/installation/resources/tls-secrets/tls-secrets.md b/versioned_docs/version-2.6/installation/resources/tls-secrets/tls-secrets.md deleted file mode 100644 index c5b79f9b37d..00000000000 --- a/versioned_docs/version-2.6/installation/resources/tls-secrets/tls-secrets.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Adding TLS Secrets -weight: 2 ---- - -Kubernetes will create all the objects and services for Rancher, but it will not become available until we populate the `tls-rancher-ingress` secret in the `cattle-system` namespace with the certificate and key. - -Combine the server certificate followed by any intermediate certificate(s) needed into a file named `tls.crt`. Copy your certificate key into a file named `tls.key`. - -For example, [acme.sh](https://acme.sh) provides server certificate and CA chains in `fullchain.cer` file. -This `fullchain.cer` should be renamed to `tls.crt` & certificate key file as `tls.key`. - -Use `kubectl` with the `tls` secret type to create the secrets. - -``` -kubectl -n cattle-system create secret tls tls-rancher-ingress \ - --cert=tls.crt \ - --key=tls.key -``` - -> **Note:** If you want to replace the certificate, you can delete the `tls-rancher-ingress` secret using `kubectl -n cattle-system delete secret tls-rancher-ingress` and add a new one using the command shown above. If you are using a private CA signed certificate, replacing the certificate is only possible if the new certificate is signed by the same CA as the certificate currently in use. - -# Using a Private CA Signed Certificate - -If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server. - -Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace. - -``` -kubectl -n cattle-system create secret generic tls-ca \ - --from-file=cacerts.pem=./cacerts.pem -``` - -> **Note:** The configured `tls-ca` secret is retrieved when Rancher starts. On a running Rancher installation the updated CA will take effect after new Rancher pods are started. - -# Updating a Private CA Certificate - -Follow the steps on [this page]({{}}/rancher/v2.6/en/installation/resources/update-rancher-cert) to update the SSL certificate of the ingress in a Rancher [high availability Kubernetes installation]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) or to switch from the default self-signed certificate to a custom certificate. \ No newline at end of file diff --git a/versioned_docs/version-2.6/installation/resources/tls-settings/tls-settings.md b/versioned_docs/version-2.6/installation/resources/tls-settings/tls-settings.md deleted file mode 100644 index 7f3c128157e..00000000000 --- a/versioned_docs/version-2.6/installation/resources/tls-settings/tls-settings.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: TLS Settings -weight: 3 ---- - -Changing the default TLS settings depends on the chosen installation method. - -# Running Rancher in a highly available Kubernetes cluster - -When you install Rancher inside of a Kubernetes cluster, TLS is offloaded at the cluster's ingress controller. The possible TLS settings depend on the used ingress controller: - -* nginx-ingress-controller (default for RKE1 and RKE2): [Default TLS Version and Ciphers](https://kubernetes.github.io/ingress-nginx/user-guide/tls/#default-tls-version-and-ciphers). -* traefik (default for K3s): [TLS Options](https://doc.traefik.io/traefik/https/tls/#tls-options). - -# Running Rancher in a single Docker container - -The default TLS configuration only accepts TLS 1.2 and secure TLS cipher suites. You can change this by setting the following environment variables: - -| Parameter | Description | Default | Available options | -|-----|-----|-----|-----| -| `CATTLE_TLS_MIN_VERSION` | Minimum TLS version | `1.2` | `1.0`, `1.1`, `1.2`, `1.3` | -| `CATTLE_TLS_CIPHERS` | Allowed TLS cipher suites | `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`,
`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`,
`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305`,
`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`,
`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`,
`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305` | See [Golang tls constants](https://golang.org/pkg/crypto/tls/#pkg-constants) | diff --git a/versioned_docs/version-2.6/installation/resources/troubleshooting/troubleshooting.md b/versioned_docs/version-2.6/installation/resources/troubleshooting/troubleshooting.md deleted file mode 100644 index 40384c2e4ae..00000000000 --- a/versioned_docs/version-2.6/installation/resources/troubleshooting/troubleshooting.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -title: Troubleshooting the Rancher Server Kubernetes Cluster -weight: 276 ---- - -This section describes how to troubleshoot an installation of Rancher on a Kubernetes cluster. - -### Relevant Namespaces - -Most of the troubleshooting will be done on objects in these 3 namespaces. - -- `cattle-system` - `rancher` deployment and pods. -- `ingress-nginx` - Ingress controller pods and services. -- `cert-manager` - `cert-manager` pods. - -### "default backend - 404" - -A number of things can cause the ingress-controller not to forward traffic to your rancher instance. Most of the time its due to a bad ssl configuration. - -Things to check - -- [Is Rancher Running](#check-if-rancher-is-running) -- [Cert CN is "Kubernetes Ingress Controller Fake Certificate"](#cert-cn-is-kubernetes-ingress-controller-fake-certificate) - -### Check if Rancher is Running - -Use `kubectl` to check the `cattle-system` system namespace and see if the Rancher pods are in a Running state. - -``` -kubectl -n cattle-system get pods - -NAME READY STATUS RESTARTS AGE -pod/rancher-784d94f59b-vgqzh 1/1 Running 0 10m -``` - -If the state is not `Running`, run a `describe` on the pod and check the Events. - -``` -kubectl -n cattle-system describe pod - -... -Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal Scheduled 11m default-scheduler Successfully assigned rancher-784d94f59b-vgqzh to localhost - Normal SuccessfulMountVolume 11m kubelet, localhost MountVolume.SetUp succeeded for volume "rancher-token-dj4mt" - Normal Pulling 11m kubelet, localhost pulling image "rancher/rancher:v2.0.4" - Normal Pulled 11m kubelet, localhost Successfully pulled image "rancher/rancher:v2.0.4" - Normal Created 11m kubelet, localhost Created container - Normal Started 11m kubelet, localhost Started container -``` - -### Check the Rancher Logs - -Use `kubectl` to list the pods. - -``` -kubectl -n cattle-system get pods - -NAME READY STATUS RESTARTS AGE -pod/rancher-784d94f59b-vgqzh 1/1 Running 0 10m -``` - -Use `kubectl` and the pod name to list the logs from the pod. - -``` -kubectl -n cattle-system logs -f rancher-784d94f59b-vgqzh -``` - -### Cert CN is "Kubernetes Ingress Controller Fake Certificate" - -Use your browser to check the certificate details. If it says the Common Name is "Kubernetes Ingress Controller Fake Certificate", something may have gone wrong with reading or issuing your SSL cert. - -> **Note:** if you are using LetsEncrypt to issue certs it can sometimes take a few minutes to issue the cert. - -### Checking for issues with cert-manager issued certs (Rancher Generated or LetsEncrypt) - -`cert-manager` has 3 parts. - -- `cert-manager` pod in the `cert-manager` namespace. -- `Issuer` object in the `cattle-system` namespace. -- `Certificate` object in the `cattle-system` namespace. - -Work backwards and do a `kubectl describe` on each object and check the events. You can track down what might be missing. - -For example there is a problem with the Issuer: - -``` -kubectl -n cattle-system describe certificate -... -Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Warning IssuerNotReady 18s (x23 over 19m) cert-manager Issuer rancher not ready -``` - -``` -kubectl -n cattle-system describe issuer -... -Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Warning ErrInitIssuer 19m (x12 over 19m) cert-manager Error initializing issuer: secret "tls-rancher" not found - Warning ErrGetKeyPair 9m (x16 over 19m) cert-manager Error getting keypair for CA issuer: secret "tls-rancher" not found -``` - -### Checking for Issues with Your Own SSL Certs - -Your certs get applied directly to the Ingress object in the `cattle-system` namespace. - -Check the status of the Ingress object and see if its ready. - -``` -kubectl -n cattle-system describe ingress -``` - -If its ready and the SSL is still not working you may have a malformed cert or secret. - -Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. - -``` -kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller -... -W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found -``` - -### No matches for kind "Issuer" - -The SSL configuration option you have chosen requires cert-manager to be installed before installing Rancher or else the following error is shown: - -``` -Error: validation failed: unable to recognize "": no matches for kind "Issuer" in version "certmanager.k8s.io/v1alpha1" -``` - -Install cert-manager and try installing Rancher again. - - -### Canal Pods show READY 2/3 - -The most common cause of this issue is port 8472/UDP is not open between the nodes. Check your local firewall, network routing or security groups. - -Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. - -### nginx-ingress-controller Pods show RESTARTS - -The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-2-3) for troubleshooting. - - -### Failed to dial to /var/run/docker.sock: ssh: rejected: administratively prohibited (open failed) - -Some causes of this error include: - -* User specified to connect with does not have permission to access the Docker socket. This can be checked by logging into the host and running the command `docker ps`: - -``` -$ ssh user@server -user@server$ docker ps -CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -``` - -See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly. - -* When using RedHat/CentOS as operating system, you cannot use the user `root` to connect to the nodes because of [Bugzilla #1527565](https://bugzilla.redhat.com/show_bug.cgi?id=1527565). You will need to add a separate user and configure it to access the Docker socket. See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly. - -* SSH server version is not version 6.7 or higher. This is needed for socket forwarding to work, which is used to connect to the Docker socket over SSH. This can be checked using `sshd -V` on the host you are connecting to, or using netcat: -``` -$ nc xxx.xxx.xxx.xxx 22 -SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10 -``` - -### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: no key found - -The key file specified as `ssh_key_path` cannot be accessed. Make sure that you specified the private key file (not the public key, `.pub`), and that the user that is running the `rke` command can access the private key file. - -### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain - -The key file specified as `ssh_key_path` is not correct for accessing the node. Double-check if you specified the correct `ssh_key_path` for the node and if you specified the correct user to connect with. - -### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys - -If you want to use encrypted private keys, you should use `ssh-agent` to load your keys with your passphrase. If the `SSH_AUTH_SOCK` environment variable is found in the environment where the `rke` command is run, it will be used automatically to connect to the node. - -### Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? - -The node is not reachable on the configured `address` and `port`. diff --git a/versioned_docs/version-2.6/installation/resources/update-rancher-cert/update-rancher-cert.md b/versioned_docs/version-2.6/installation/resources/update-rancher-cert/update-rancher-cert.md deleted file mode 100644 index afb49caa9df..00000000000 --- a/versioned_docs/version-2.6/installation/resources/update-rancher-cert/update-rancher-cert.md +++ /dev/null @@ -1,251 +0,0 @@ ---- -title: Updating the Rancher Certificate -weight: 10 ---- - -# Updating a Private CA Certificate - -Follow these steps to update the SSL certificate of the ingress in a Rancher [high availability Kubernetes installation]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) or to switch from the default self-signed certificate to a custom certificate. - -A summary of the steps is as follows: - -1. Create or update the `tls-rancher-ingress` Kubernetes secret resource with the new certificate and private key. -2. Create or update the `tls-ca` Kubernetes secret resource with the root CA certificate (only required when using a private CA). -3. Update the Rancher installation using the Helm CLI. -4. Reconfigure the Rancher agents to trust the new CA certificate. -5. Select Force Update of Fleet clusters to connect fleet-agent to Rancher. - -The details of these instructions are below. - -## 1. Create/update the certificate secret resource - -First, concatenate the server certificate followed by any intermediate certificate(s) to a file named `tls.crt` and provide the corresponding certificate key in a file named `tls.key`. - -If you are switching the install from using the Rancher self-signed certificate or Let’s Encrypt issued certificates, use the following command to create the `tls-rancher-ingress` secret resource in your Rancher HA cluster: - -``` -$ kubectl -n cattle-system create secret tls tls-rancher-ingress \ - --cert=tls.crt \ - --key=tls.key -``` - -Alternatively, to update an existing certificate secret: - -``` -$ kubectl -n cattle-system create secret tls tls-rancher-ingress \ - --cert=tls.crt \ - --key=tls.key \ - --dry-run --save-config -o yaml | kubectl apply -f - -``` - -## 2. Create/update the CA certificate secret resource - -If the new certificate was signed by a private CA, you will need to copy the corresponding root CA certificate into a file named `cacerts.pem` and create or update the `tls-ca secret` in the `cattle-system` namespace. If the certificate was signed by an intermediate CA, then the `cacerts.pem` must contain both the intermediate and root CA certificates (in this order). - -To create the initial secret: - -``` -$ kubectl -n cattle-system create secret generic tls-ca \ - --from-file=cacerts.pem -``` - -To update an existing `tls-ca` secret: - -``` -$ kubectl -n cattle-system create secret generic tls-ca \ - --from-file=cacerts.pem \ - --dry-run --save-config -o yaml | kubectl apply -f - -``` - -## 3. Reconfigure the Rancher deployment - -> Before proceeding, generate an API token in the Rancher UI (User > API & Keys) and save the Bearer Token which you might need in step 4. - -This step is required if Rancher was initially installed with self-signed certificates (`ingress.tls.source=rancher`) or with a Let's Encrypt issued certificate (`ingress.tls.source=letsEncrypt`). - -It ensures that the Rancher pods and ingress resources are reconfigured to use the new server and optional CA certificate. - -To update the Helm deployment you will need to use the same (`--set`) options that were used during initial installation. Check with: - -``` -$ helm get values rancher -n cattle-system -``` - -Also get the version string of the currently deployed Rancher chart: - -``` -$ helm ls -A -``` - -Upgrade the Helm application instance using the original configuration values and making sure to specify `ingress.tls.source=secret` as well as the current chart version to prevent an application upgrade. - -If the certificate was signed by a private CA, add the `set privateCA=true` argument as well. Also make sure to read the documentation describing the initial installation using custom certificates. - -``` -helm upgrade rancher rancher-stable/rancher \ - --namespace cattle-system \ - --version \ - --set hostname=rancher.my.org \ - --set ingress.tls.source=secret \ - --set ... -``` - -When the upgrade is completed, navigate to `https:///v3/settings/cacerts` to verify that the value matches the CA certificate written in the `tls-ca` secret earlier. - -## 4. Reconfigure Rancher agents to trust the private CA - -This section covers three methods to reconfigure Rancher agents to trust the private CA. This step is required if either of the following is true: - -- Rancher was initially configured to use the Rancher self-signed certificate (`ingress.tls.source=rancher`) or with a Let's Encrypt issued certificate (`ingress.tls.source=letsEncrypt`) -- The root CA certificate for the new custom certificate has changed - -### Why is this step required? - -When Rancher is configured with a certificate signed by a private CA, the CA certificate chain is downloaded into Rancher agent containers. Agents compare the checksum of the downloaded certificate against the `CATTLE_CA_CHECKSUM` environment variable. This means that, when the private CA certificate is changed on Rancher server side, the environvment variable `CATTLE_CA_CHECKSUM` must be updated accordingly. - -### Which method should I choose? - -Method 1 is the easiest one but requires all clusters to be connected to Rancher after the certificates have been rotated. This is usually the case if the process is performed right after updating the Rancher deployment (Step 3). - -If the clusters have lost connection to Rancher but you have [Authorized Cluster Endpoints](https://rancher.com/docs/rancher/v2.6/en/cluster-admin/cluster-access/ace/) enabled, then go with method 2. - -Method 3 can be used as a fallback if method 1 and 2 are unfeasible. - -### Method 1: Kubectl command - -For each cluster under Rancher management (except the `local` Rancher management cluster) run the following command using the Kubeconfig file of the Rancher management cluster (RKE or K3S). - -``` -kubectl patch clusters.management.cattle.io -p '{"status":{"agentImage":"dummy"}}' --type merge -``` - -This command will cause all Agent Kubernetes resources to be reconfigured with the checksum of the new certificate. - - -### Method 2: Manually update checksum - -Manually patch the agent Kubernetes resources by updating the `CATTLE_CA_CHECKSUM` environment variable to the value matching the checksum of the new CA certificate. Generate the new checksum value like so: - -``` -$ curl -k -s -fL /v3/settings/cacerts | jq -r .value > cacert.tmp -$ sha256sum cacert.tmp | awk '{print $1}' -``` - -Using a Kubeconfig for each downstream cluster update the environment variable for the two agent deployments. - -``` -$ kubectl edit -n cattle-system ds/cattle-node-agent -$ kubectl edit -n cattle-system deployment/cattle-cluster-agent -``` - -### Method 3: Recreate Rancher agents - -With this method you are recreating the Rancher agents by running a set of commands on a controlplane node of each downstream cluster. - -First, generate the agent definitions as described here: https://gist.github.com/superseb/076f20146e012f1d4e289f5bd1bd4971 - -Then, connect to a controlplane node of the downstream cluster via SSH, create a Kubeconfig and apply the definitions: -https://gist.github.com/superseb/b14ed3b5535f621ad3d2aa6a4cd6443b - -## 5. Select Force Update of Fleet clusters to connect fleet-agent to Rancher - -Select 'Force Update' for the clusters within the [Continuous Delivery]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet/#accessing-fleet-in-the-rancher-ui) view of the Rancher UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher. - -### Why is this step required? - -Fleet agents in Rancher managed clusters store kubeconfig that is used to connect to the Rancher proxied kube-api in the fleet-agent secret of the fleet-system namespace. The kubeconfig contains a certificate-authority-data block containing the Rancher CA. When changing the Rancher CA, this block needs to be updated for a successful connection of the fleet-agent to Rancher. - -# Updating from a Private CA Certificate to a Common Certificate - ->It is possible to perform the opposite procedure as shown above: you may change from a private certificate to a common, or non-private, certificate. The steps involved are outlined below. - -## 1. Create/update the certificate secret resource - -First, concatenate the server certificate followed by any intermediate certificate(s) to a file named `tls.crt` and provide the corresponding certificate key in a file named `tls.key`. - -If you are switching the install from using the Rancher self-signed certificate or Let’s Encrypt issued certificates, use the following command to create the `tls-rancher-ingress` secret resource in your Rancher HA cluster: - -``` -$ kubectl -n cattle-system create secret tls tls-rancher-ingress \ - --cert=tls.crt \ - --key=tls.key -``` - -Alternatively, to update an existing certificate secret: - -``` -$ kubectl -n cattle-system create secret tls tls-rancher-ingress \ - --cert=tls.crt \ - --key=tls.key \ - --dry-run --save-config -o yaml | kubectl apply -f - -``` - -## 2. Delete the CA certificate secret resource - -You will delete the `tls-ca secret` in the `cattle-system` namespace as it is no longer needed. You may also optionally save a copy of the `tls-ca secret` if desired. - -To save the existing secret: - -``` -kubectl -n cattle-system get secret tls-ca -o yaml > tls-ca.yaml -``` - -To delete the existing `tls-ca` secret: - -``` -kubectl -n cattle-system delete secret tls-ca -``` - -## 3. Reconfigure the Rancher deployment - -> Before proceeding, [generate an API token in the Rancher UI]({{}}/rancher/v2.6/en/user-settings/api-keys/#creating-an-api-key) (User > API & Keys). - -This step is required if Rancher was initially installed with self-signed certificates (`ingress.tls.source=rancher`) or with a Let's Encrypt issued certificate (`ingress.tls.source=letsEncrypt`). - -It ensures that the Rancher pods and ingress resources are reconfigured to use the new server and optional CA certificate. - -To update the Helm deployment you will need to use the same (`--set`) options that were used during initial installation. Check with: - -``` -$ helm get values rancher -n cattle-system -``` - -Also get the version string of the currently deployed Rancher chart: - -``` -$ helm ls -A -``` - -Upgrade the Helm application instance using the original configuration values and making sure to specify the current chart version to prevent an application upgrade. - -Also make sure to read the documentation describing the initial installation using custom certificates. - -``` -helm upgrade rancher rancher-stable/rancher \ - --namespace cattle-system \ - --version \ - --set hostname=rancher.my.org \ - --set ... -``` - -On upgrade, you can either - -- remove `--set ingress.tls.source=secret \` from the Helm upgrade command, as shown above, or - -- remove the `privateCA` parameter or set it to `false` because the CA is valid: - -``` -set privateCA=false -``` - -## 4. Reconfigure Rancher agents for the non-private/common certificate - -`CATTLE_CA_CHECKSUM` environment variable on the downstream cluster agents should be removed or set to "" (an empty string). - -## 5. Select Force Update of Fleet clusters to connect fleet-agent to Rancher - -Select 'Force Update' for the clusters within the [Continuous Delivery]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet/#accessing-fleet-in-the-rancher-ui) view of the Rancher UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher. - -### Why is this step required? - -Fleet agents in Rancher managed clusters store kubeconfig that is used to connect to the Rancher proxied kube-api in the fleet-agent secret of the fleet-system namespace. The kubeconfig contains a certificate-authority-data block containing the Rancher CA. When changing the Rancher CA, this block needs to be updated for a successful connection of the fleet-agent to Rancher. diff --git a/versioned_docs/version-2.6/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md b/versioned_docs/version-2.6/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md deleted file mode 100644 index 393152b315d..00000000000 --- a/versioned_docs/version-2.6/installation/resources/upgrading-cert-manager/upgrading-cert-manager.md +++ /dev/null @@ -1,246 +0,0 @@ ---- -title: Upgrading Cert-Manager -weight: 4 ---- - -Rancher uses cert-manager to automatically generate and renew TLS certificates for HA deployments of Rancher. As of Fall 2019, three important changes to cert-manager are set to occur that you need to take action on if you have an HA deployment of Rancher: - -1. [Let's Encrypt will be blocking cert-manager instances older than 0.8.0 starting November 1st 2019.](https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753) -1. [Cert-manager is deprecating and replacing the certificate.spec.acme.solvers field](https://cert-manager.io/docs/installation/upgrading/upgrading-0.7-0.8/). This change has no exact deadline. -1. [Cert-manager is deprecating `v1alpha1` API and replacing its API group](https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/) - -To address these changes, this guide will do two things: - -1. Document the procedure for upgrading cert-manager -1. Explain the cert-manager API changes and link to cert-manager's official documentation for migrating your data - -> **Important:** -> If you are currently running the cert-manager whose version is 1.5 or below, and want to upgrade both Rancher and cert-manager to a new version (1.6+ in the case of cert-manager), then you need to re-install both Rancher and cert-manager due to the API change in cert-manager 1.6. This will also be necessary if you are upgrading from a version of cert manager below 0.11 to a version of cert-manager above 0.11. Follow the steps below: - -> 1. Take a one-time snapshot of your Kubernetes cluster running Rancher server -> 2. Uninstall Rancher, cert-manager, and the CustomResourceDefinition for cert-manager -> 3. Install the newer version of Rancher and cert-manager - -> The reason is that when Helm upgrades Rancher, it will reject the upgrade and show error messages if the running Rancher app does not match the chart template used to install it. Because cert-manager changed its API group and we cannot modify released charts for Rancher, there will always be a mismatch on the cert-manager's API version, therefore the upgrade will be rejected. - -# Upgrade Cert-Manager - -The namespace used in these instructions depends on the namespace cert-manager is currently installed in. If it is in kube-system use that in the instructions below. You can verify by running `kubectl get pods --all-namespaces` and checking which namespace the cert-manager-\* pods are listed in. Do not change the namespace cert-manager is running in or this can cause issues. - -In order to upgrade cert-manager, follow these instructions: - -### Option A: Upgrade cert-manager with Internet Access - -
- Click to expand - -1. [Back up existing resources](https://cert-manager.io/docs/tutorials/backup/) as a precaution - - ```plain - kubectl get -o yaml --all-namespaces \ - issuer,clusterissuer,certificates,certificaterequests > cert-manager-backup.yaml - ``` - - > **Important:** - > If you are upgrading from a version older than 0.11.0, Update the apiVersion on all your backed up resources from `certmanager.k8s.io/v1alpha1` to `cert-manager.io/v1alpha2`. If you use any cert-manager annotations on any of your other resources, you will need to update them to reflect the new API group. For details, refer to the documentation on [additional annotation changes.](https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/#additional-annotation-changes) - -1. [Uninstall existing deployment](https://cert-manager.io/docs/installation/uninstall/kubernetes/#uninstalling-with-helm) - - ```plain - helm uninstall cert-manager - ``` - - Delete the CustomResourceDefinition using the link to the version vX.Y.Z you installed - - ```plain - kubectl delete -f https://github.com/jetstack/cert-manager/releases/download/vX.Y.Z/cert-manager.crds.yaml - ``` - -1. Install the CustomResourceDefinition resources separately - - ```plain - kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/vX.Y.Z/cert-manager.crds.yaml - ``` - - > **Note:** - > If you are running Kubernetes v1.15 or below, you will need to add the `--validate=false` flag to your `kubectl apply` command above. Otherwise, you will receive a validation error relating to the `x-kubernetes-preserve-unknown-fields` field in cert-manager’s CustomResourceDefinition resources. This is a benign error and occurs due to the way kubectl performs resource validation. - -1. Create the namespace for cert-manager if needed - - ```plain - kubectl create namespace cert-manager - ``` - -1. Add the Jetstack Helm repository - - ```plain - helm repo add jetstack https://charts.jetstack.io - ``` - -1. Update your local Helm chart repository cache - - ```plain - helm repo update - ``` - -1. Install the new version of cert-manager - - ```plain - helm install \ - cert-manager jetstack/cert-manager \ - --namespace cert-manager \ - --version v0.12.0 - ``` - -1. [Restore back up resources](https://cert-manager.io/docs/tutorials/backup/#restoring-resources) - - ```plain - kubectl apply -f cert-manager-backup.yaml - ``` - -
- -### Option B: Upgrade cert-manager in an Air Gap Environment - -
- Click to expand - -### Prerequisites - -Before you can perform the upgrade, you must prepare your air gapped environment by adding the necessary container images to your private registry and downloading or rendering the required Kubernetes manifest files. - -1. Follow the guide to [Prepare your Private Registry]({{}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry) with the images needed for the upgrade. - -1. From a system connected to the internet, add the cert-manager repo to Helm - - ```plain - helm repo add jetstack https://charts.jetstack.io - helm repo update - ``` - -1. Fetch the latest cert-manager chart available from the [Helm chart repository](https://hub.helm.sh/charts/jetstack/cert-manager). - - ```plain - helm fetch jetstack/cert-manager --version v0.12.0 - ``` - -1. Render the cert manager template with the options you would like to use to install the chart. Remember to set the `image.repository` option to pull the image from your private registry. This will create a `cert-manager` directory with the Kubernetes manifest files. - - The Helm 3 command is as follows: - - ```plain - helm template cert-manager ./cert-manager-v0.12.0.tgz --output-dir . \ - --namespace cert-manager \ - --set image.repository=/quay.io/jetstack/cert-manager-controller - --set webhook.image.repository=/quay.io/jetstack/cert-manager-webhook - --set cainjector.image.repository=/quay.io/jetstack/cert-manager-cainjector - ``` - - The Helm 2 command is as follows: - - ```plain - helm template ./cert-manager-v0.12.0.tgz --output-dir . \ - --name cert-manager --namespace cert-manager \ - --set image.repository=/quay.io/jetstack/cert-manager-controller - --set webhook.image.repository=/quay.io/jetstack/cert-manager-webhook - --set cainjector.image.repository=/quay.io/jetstack/cert-manager-cainjector - ``` - -1. Download the required CRD file for cert-manager (old and new) - - ```plain - curl -L -o cert-manager/cert-manager-crd.yaml https://raw.githubusercontent.com/jetstack/cert-manager/release-0.12/deploy/manifests/00-crds.yaml - curl -L -o cert-manager/cert-manager-crd-old.yaml https://raw.githubusercontent.com/jetstack/cert-manager/release-X.Y/deploy/manifests/00-crds.yaml - ``` - -### Install cert-manager - -1. Back up existing resources as a precaution - - ```plain - kubectl get -o yaml --all-namespaces \ - issuer,clusterissuer,certificates,certificaterequests > cert-manager-backup.yaml - ``` - - > **Important:** - > If you are upgrading from a version older than 0.11.0, Update the apiVersion on all your backed up resources from `certmanager.k8s.io/v1alpha1` to `cert-manager.io/v1alpha2`. If you use any cert-manager annotations on any of your other resources, you will need to update them to reflect the new API group. For details, refer to the documentation on [additional annotation changes.](https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/#additional-annotation-changes) - -1. Delete the existing cert-manager installation - - ```plain - kubectl -n cert-manager \ - delete deployment,sa,clusterrole,clusterrolebinding \ - -l 'app=cert-manager' -l 'chart=cert-manager-v0.5.2' - ``` - - Delete the CustomResourceDefinition using the link to the version vX.Y you installed - - ```plain - kubectl delete -f cert-manager/cert-manager-crd-old.yaml - ``` - -1. Install the CustomResourceDefinition resources separately - - ```plain - kubectl apply -f cert-manager/cert-manager-crd.yaml - ``` - - > **Note:** - > If you are running Kubernetes v1.15 or below, you will need to add the `--validate=false` flag to your `kubectl apply` command above. Otherwise, you will receive a validation error relating to the `x-kubernetes-preserve-unknown-fields` field in cert-manager’s CustomResourceDefinition resources. This is a benign error and occurs due to the way kubectl performs resource validation. - -1. Create the namespace for cert-manager - - ```plain - kubectl create namespace cert-manager - ``` - -1. Install cert-manager - - ```plain - kubectl -n cert-manager apply -R -f ./cert-manager - ``` - -1. [Restore back up resources](https://cert-manager.io/docs/tutorials/backup/#restoring-resources) - - ```plain - kubectl apply -f cert-manager-backup.yaml - ``` - -
- -### Verify the Deployment - -Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the kube-system namespace for running pods: - -``` -kubectl get pods --namespace cert-manager - -NAME READY STATUS RESTARTS AGE -cert-manager-5c6866597-zw7kh 1/1 Running 0 2m -cert-manager-cainjector-577f6d9fd7-tr77l 1/1 Running 0 2m -cert-manager-webhook-787858fcdb-nlzsq 1/1 Running 0 2m -``` - -## Cert-Manager API change and data migration - ---- -_New in v2.6.4_ - -Rancher now supports cert-manager versions 1.6.2 and 1.7.1. We recommend v1.7.x because v 1.6.x will reach end-of-life on March 30, 2022. To read more, see the [cert-manager docs]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/#4-install-cert-manager). For instructions on upgrading cert-manager from version 1.5 to 1.6, see the upstream cert-manager documentation [here](https://cert-manager.io/docs/installation/upgrading/upgrading-1.5-1.6/). For instructions on upgrading cert-manager from version 1.6 to 1.7, see the upstream cert-manager documentation [here](https://cert-manager.io/docs/installation/upgrading/upgrading-1.6-1.7/). - ---- - -Cert-manager has deprecated the use of the `certificate.spec.acme.solvers` field and will drop support for it completely in an upcoming release. - -Per the cert-manager documentation, a new format for configuring ACME certificate resources was introduced in v0.8. Specifically, the challenge solver configuration field was moved. Both the old format and new are supported as of v0.9, but support for the old format will be dropped in an upcoming release of cert-manager. The cert-manager documentation strongly recommends that after upgrading you update your ACME Issuer and Certificate resources to the new format. - -Details about the change and migration instructions can be found in the [cert-manager v0.7 to v0.8 upgrade instructions](https://cert-manager.io/docs/installation/upgrading/upgrading-0.7-0.8/). - -The v0.11 release marks the removal of the v1alpha1 API that was used in previous versions of cert-manager, as well as our API group changing to be cert-manager.io instead of certmanager.k8s.io. - -We have also removed support for the old configuration format that was deprecated in the v0.8 release. This means you must transition to using the new solvers style configuration format for your ACME issuers before upgrading to v0.11. For more information, see the [upgrading to v0.8 guide](https://cert-manager.io/docs/installation/upgrading/upgrading-0.7-0.8/). - -Details about the change and migration instructions can be found in the [cert-manager v0.10 to v0.11 upgrade instructions](https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/). - -More info about [cert-manager upgrade information](https://cert-manager.io/docs/installation/upgrading/). - diff --git a/versioned_docs/version-2.6/istio/configuration-reference/canal-and-project-network/canal-and-project-network.md b/versioned_docs/version-2.6/istio/configuration-reference/canal-and-project-network/canal-and-project-network.md deleted file mode 100644 index a1718986b00..00000000000 --- a/versioned_docs/version-2.6/istio/configuration-reference/canal-and-project-network/canal-and-project-network.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Additional Steps for Project Network Isolation -weight: 4 ---- - -In clusters where: - -- You are using the Canal network plugin with Rancher before v2.5.8, or you are using Rancher v2.5.8+ with an any RKE network plug-in that supports the enforcement of Kubernetes network policies, such as Canal or the Cisco ACI plugin -- The Project Network Isolation option is enabled -- You install the Istio Ingress module - -The Istio Ingress Gateway pod won't be able to redirect ingress traffic to the workloads by default. This is because all the namespaces will be inaccessible from the namespace where Istio is installed. You have two options. - -The first option is to add a new Network Policy in each of the namespaces where you intend to have ingress controlled by Istio. Your policy should include the following lines: - -``` -- podSelector: - matchLabels: - app: istio-ingressgateway -``` - -The second option is to move the `istio-system` namespace to the `system` project, which by default is excluded from the network isolation. \ No newline at end of file diff --git a/versioned_docs/version-2.6/istio/configuration-reference/configuration-reference.md b/versioned_docs/version-2.6/istio/configuration-reference/configuration-reference.md deleted file mode 100644 index 1ed6fe50422..00000000000 --- a/versioned_docs/version-2.6/istio/configuration-reference/configuration-reference.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Configuration Options -weight: 3 ---- - -- [Egress Support](#egress-support) -- [Enabling Automatic Sidecar Injection](#enabling-automatic-sidecar-injection) -- [Overlay File](#overlay-file) -- [Selectors and Scrape Configs](#selectors-and-scrape-configs) -- [Enable Istio with Pod Security Policies](#enable-istio-with-pod-security-policies) -- [Additional Steps for Installing Istio on an RKE2 Cluster](#additional-steps-for-installing-istio-on-an-rke2-cluster) -- [Additional Steps for Project Network Isolation](#additional-steps-for-project-network-isolation) - -### Egress Support - -By default the Egress gateway is disabled, but can be enabled on install or upgrade through the values.yaml or via the [overlay file](#overlay-file). - -### Enabling Automatic Sidecar Injection - -Automatic sidecar injection is disabled by default. To enable this, set the `sidecarInjectorWebhook.enableNamespacesByDefault=true` in the values.yaml on install or upgrade. This automatically enables Istio sidecar injection into all new namespaces that are deployed. - -### Overlay File - -An Overlay File is designed to support extensive configuration of your Istio installation. It allows you to make changes to any values available in the [IstioOperator API](https://istio.io/latest/docs/reference/config/istio.operator.v1alpha1/). This will ensure you can customize the default installation to fit any scenario. - -The Overlay File will add configuration on top of the default installation that is provided from the Istio chart installation. This means you do not need to redefine the components that already defined for installation. - -For more information on Overlay Files, refer to the [Istio documentation.](https://istio.io/latest/docs/setup/install/istioctl/#configure-component-settings) - -### Selectors and Scrape Configs - -The Monitoring app sets `prometheus.prometheusSpec.ignoreNamespaceSelectors=false` which enables monitoring across all namespaces by default. This ensures you can view traffic, metrics and graphs for resources deployed in a namespace with `istio-injection=enabled` label. - -If you would like to limit Prometheus to specific namespaces, set `prometheus.prometheusSpec.ignoreNamespaceSelectors=true`. Once you do this, you will need to add additional configuration to continue to monitor your resources. - -For details, refer to [this section.](./selectors-and-scrape) - -### Enable Istio with Pod Security Policies - -Refer to [this section.](./enable-istio-with-psp) - -### Additional Steps for Installing Istio on an RKE2 Cluster - -Refer to [this section.](./rke2) - -### Additional Steps for Project Network Isolation - -Refer to [this section.](./canal-and-project-network) \ No newline at end of file diff --git a/versioned_docs/version-2.6/istio/configuration-reference/enable-istio-with-psp/enable-istio-with-psp.md b/versioned_docs/version-2.6/istio/configuration-reference/enable-istio-with-psp/enable-istio-with-psp.md deleted file mode 100644 index d0e996a19cd..00000000000 --- a/versioned_docs/version-2.6/istio/configuration-reference/enable-istio-with-psp/enable-istio-with-psp.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Enable Istio with Pod Security Policies -weight: 1 ---- - -If you have restrictive Pod Security Policies enabled, then Istio may not be able to function correctly, because it needs certain permissions in order to install itself and manage pod infrastructure. In this section, we will configure a cluster with PSPs enabled for an Istio install, and also set up the Istio CNI plugin. - -The Istio CNI plugin removes the need for each application pod to have a privileged `NET_ADMIN` container. For further information, see the [Istio CNI Plugin docs](https://istio.io/docs/setup/additional-setup/cni). Please note that the [Istio CNI Plugin is in alpha](https://istio.io/about/feature-stages/). - -> **Prerequisites:** -> -> - The cluster must be an RKE Kubernetes cluster. -> - The cluster must have been created with a default PodSecurityPolicy. -> -> To enable pod security policy support when creating a Kubernetes cluster in the Rancher UI, go to Advanced Options. In the Pod Security Policy Support section, click Enabled. Then select a default pod security policy. - -1. [Set the PodSecurityPolicy to unrestricted](#1-set-the-podsecuritypolicy-to-unrestricted) -2. [Enable the CNI](#2-enable-the-cni) -3. [Verify that the CNI is working.](#3-verify-that-the-cni-is-working) - -### 1. Set the PodSecurityPolicy to unrestricted - -An unrestricted PSP allows Istio to be installed. - -Set the PSP to `unrestricted` in the project where is Istio is installed, or the project where you plan to install Istio. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Find the **Project: System** and select the **⋮ > Edit Config**. -1. Change the Pod Security Policy option to be unrestricted, then click **Save**. - -### 2. Enable the CNI - -When installing or upgrading Istio through **Apps & Marketplace,** - -1. Click **Components**. -2. Check the box next to **Enabled CNI**. -3. Finish installing or upgrading Istio. - -The CNI can also be enabled by editing the `values.yaml`: - -``` -istio_cni.enabled: true -``` - -Istio should install successfully with the CNI enabled in the cluster. - -### 3. Verify that the CNI is working - -Verify that the CNI is working by deploying a [sample application](https://istio.io/latest/docs/examples/bookinfo/) or deploying one of your own applications. - diff --git a/versioned_docs/version-2.6/istio/configuration-reference/rke2/rke2.md b/versioned_docs/version-2.6/istio/configuration-reference/rke2/rke2.md deleted file mode 100644 index 03615c85b63..00000000000 --- a/versioned_docs/version-2.6/istio/configuration-reference/rke2/rke2.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Additional Steps for Installing Istio on an RKE2 Cluster -weight: 3 ---- - -When installing or upgrading the Istio Helm chart through **Apps & Marketplace,** - -1. If you are installing the chart, click **Customize Helm options before install** and click **Next**. -1. You will see options for configuring the Istio Helm chart. On the **Components** tab, check the box next to **Enabled CNI**. -1. Add a custom overlay file specifying `cniBinDir` and `cniConfDir`. For more information on these options, refer to the [Istio documentation.](https://istio.io/latest/docs/setup/additional-setup/cni/#helm-chart-parameters) An example is below: - - ```yaml - apiVersion: install.istio.io/v1alpha1 - kind: IstioOperator - spec: - components: - cni: - enabled: true - k8s: - overlays: - - apiVersion: "apps/v1" - kind: "DaemonSet" - name: "istio-cni-node" - patches: - - path: spec.template.spec.containers.[name:install-cni].securityContext.privileged - value: true - values: - cni: - image: rancher/mirrored-istio-install-cni:1.9.3 - excludeNamespaces: - - istio-system - - kube-system - logLevel: info - cniBinDir: /opt/cni/bin - cniConfDir: /etc/cni/net.d - ``` - -**Result:** Now you should be able to utilize Istio as desired, including sidecar injection and monitoring via Kiali. diff --git a/versioned_docs/version-2.6/istio/configuration-reference/selectors-and-scrape/selectors-and-scrape.md b/versioned_docs/version-2.6/istio/configuration-reference/selectors-and-scrape/selectors-and-scrape.md deleted file mode 100644 index a704bf081fb..00000000000 --- a/versioned_docs/version-2.6/istio/configuration-reference/selectors-and-scrape/selectors-and-scrape.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: Selectors and Scrape Configs -weight: 2 ---- - -The Monitoring app sets `prometheus.prometheusSpec.ignoreNamespaceSelectors=false`, which enables monitoring across all namespaces by default. - -This ensures you can view traffic, metrics and graphs for resources deployed in a namespace with `istio-injection=enabled` label. - -If you would like to limit Prometheus to specific namespaces, set `prometheus.prometheusSpec.ignoreNamespaceSelectors=true`. Once you do this, you will need to add additional configuration to continue to monitor your resources. - -- [Limiting Monitoring to Specific Namespaces by Setting ignoreNamespaceSelectors to True](#limiting-monitoring-to-specific-namespaces-by-setting-ignorenamespaceselectors-to-true) -- [Enabling Prometheus to Detect Resources in Other Namespaces](#enabling-prometheus-to-detect-resources-in-other-namespaces) -- [Monitoring Specific Namespaces: Create a Service Monitor or Pod Monitor](#monitoring-specific-namespaces-create-a-service-monitor-or-pod-monitor) -- [Monitoring Across Namespaces: Set ignoreNamespaceSelectors to False](#monitoring-across-namespaces-set-ignorenamespaceselectors-to-false) - -### Limiting Monitoring to Specific Namespaces by Setting ignoreNamespaceSelectors to True - -To limit monitoring to specific namespaces, you will edit the `ignoreNamespaceSelectors` Helm chart option. You will configure this option when installing or upgrading the Monitoring Helm chart: - -1. When installing or upgrading the Monitoring Helm chart, edit the values.yml and set`prometheus.prometheusSpec.ignoreNamespaceSelectors=true`. -1. Complete the install or upgrade. - -**Result:** Prometheus will be limited to specific namespaces which means one of the following configurations will need to be set up to continue to view data in various dashboards - -### Enabling Prometheus to Detect Resources in Other Namespaces - -There are two different ways to enable Prometheus to detect resources in other namespaces when `prometheus.prometheusSpec.ignoreNamespaceSelectors=true`: - -- **Monitoring specific namespaces:** Add a Service Monitor or Pod Monitor in the namespace with the targets you want to scrape. -- **Monitoring across namespaces:** Add an `additionalScrapeConfig` to your rancher-monitoring instance to scrape all targets in all namespaces. - -### Monitoring Specific Namespaces: Create a Service Monitor or Pod Monitor - -This option allows you to define which specific services or pods you would like monitored in a specific namespace. - -The usability tradeoff is that you have to create the service monitor or pod monitor per namespace since you cannot monitor across namespaces. - -> **Prerequisite:** Define a ServiceMonitor or PodMonitor for ``. An example ServiceMonitor is provided below. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the top navigation bar, open the kubectl shell. -1. If the ServiceMonitor or PodMonitor file is stored locally in your cluster, in `kubectl create -f .yaml`. -1. If the ServiceMonitor or PodMonitor is not stored locally, run `cat<< EOF | kubectl apply -f -`, paste the file contents into the terminal, then run `EOF` to complete the command. -1. Run `kubectl label namespace istio-injection=enabled` to enable the envoy sidecar injection. - -**Result:** `` can be scraped by prometheus. - -
Example Service Monitor for Istio Proxies
- -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: ServiceMonitor -metadata: - name: envoy-stats-monitor - namespace: istio-system - labels: - monitoring: istio-proxies -spec: - selector: - matchExpressions: - - {key: istio-prometheus-ignore, operator: DoesNotExist} - namespaceSelector: - any: true - jobLabel: envoy-stats - endpoints: - - path: /stats/prometheus - targetPort: 15090 - interval: 15s - relabelings: - - sourceLabels: [__meta_kubernetes_pod_container_port_name] - action: keep - regex: '.*-envoy-prom' - - action: labeldrop - regex: "__meta_kubernetes_pod_label_(.+)" - - sourceLabels: [__meta_kubernetes_namespace] - action: replace - targetLabel: namespace - - sourceLabels: [__meta_kubernetes_pod_name] - action: replace - targetLabel: pod_name -``` - -### Monitoring across namespaces: Set ignoreNamespaceSelectors to False - -This enables monitoring across namespaces by giving Prometheus additional scrape configurations. - -The usability tradeoff is that all of Prometheus' `additionalScrapeConfigs` are maintained in a single Secret. This could make upgrading difficult if monitoring is already deployed with additionalScrapeConfigs before installing Istio. - -1. When installing or upgrading the Monitoring Helm chart, edit the values.yml and set the `prometheus.prometheusSpec.additionalScrapeConfigs` array to the **Additional Scrape Config** provided below. -1. Complete the install or upgrade. - -**Result:** All namespaces with the `istio-injection=enabled` label will be scraped by prometheus. - -
Additional Scrape Config
- -``` yaml -- job_name: 'istio/envoy-stats' - scrape_interval: 15s - metrics_path: /stats/prometheus - kubernetes_sd_configs: - - role: pod - relabel_configs: - - source_labels: [__meta_kubernetes_pod_container_port_name] - action: keep - regex: '.*-envoy-prom' - - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port] - action: replace - regex: ([^:]+)(?::\d+)?;(\d+) - replacement: $1:15090 - target_label: __address__ - - action: labelmap - regex: __meta_kubernetes_pod_label_(.+) - - source_labels: [__meta_kubernetes_namespace] - action: replace - target_label: namespace - - source_labels: [__meta_kubernetes_pod_name] - action: replace - target_label: pod_name -``` diff --git a/versioned_docs/version-2.6/istio/disabling-istio/disabling-istio.md b/versioned_docs/version-2.6/istio/disabling-istio/disabling-istio.md deleted file mode 100644 index 57018718f62..00000000000 --- a/versioned_docs/version-2.6/istio/disabling-istio/disabling-istio.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Disabling Istio -weight: 4 ---- - -This section describes how to uninstall Istio in a cluster or disable a namespace, or workload. - -# Uninstall Istio in a Cluster - -To uninstall Istio, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Apps & Marketplace > Installed Apps**. -1. In the `istio-system` namespace, go to `rancher-istio` and click **⋮ > Delete**. -1. After `rancher-istio` is deleted, you can then select all the remaining apps in the `istio-system` namespace and click **Delete**. - -**Result:** The `rancher-istio` app in the cluster gets removed. The Istio sidecar cannot be deployed on any workloads in the cluster. - -**Note:** You can no longer disable and re-enable your Istio installation. If you would like to save your settings for a future install, view and save individual YAMLs to refer back to / reuse for future installations. - -**Troubleshooting Uninstall:** If you didn't follow the uninstall steps, you may encounter a warning during uninstall: - -`Error: uninstallation completed with 1 error(s): unable to build kubernetes objects for delete: unable to recognize "": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"` - -This could mean a few things. You either selected all the apps in the `istio-system` namespace and deleted them at the same time, or you deleted `rancher-istio` chart dependencies prior to deleting the `rancher-istio` chart. Since the uninstall did not complete properly, you will have resources remaining in the `istio-system` namespace that you will need to manually clean up. Another option to avoid manual clean up is to install `rancher-istio` again, then uninstall it in the correct order. - -# Disable Istio in a Namespace - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Go to the namespace where you want to enable Istio and click **⋮ > Enable Istio Auto Injection**. Alternately, click the namespace, and then on the namespace detail page, click **⋮ > Enable Istio Auto Injection**. - -**Result:** When workloads are deployed in this namespace, they will not have the Istio sidecar. - -# Remove the Istio Sidecar from a Workload - -Disable Istio in the namespace, then redeploy the workloads with in it. They will be deployed without the Istio sidecar. diff --git a/versioned_docs/version-2.6/istio/istio.md b/versioned_docs/version-2.6/istio/istio.md deleted file mode 100644 index e594a127fc9..00000000000 --- a/versioned_docs/version-2.6/istio/istio.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -title: Istio -weight: 14 ---- - -[Istio](https://istio.io/) is an open-source tool that makes it easier for DevOps teams to observe, secure, control, and troubleshoot the traffic within a complex network of microservices. - -As a network of microservices changes and grows, the interactions between them can become increasingly difficult to manage and understand. In such a situation, it is useful to have a service mesh as a separate infrastructure layer. Istio's service mesh lets you manipulate traffic between microservices without changing the microservices directly. - -Our integration of Istio is designed so that a Rancher operator, such as an administrator or cluster owner, can deliver Istio to a team of developers. Then developers can use Istio to enforce security policies, troubleshoot problems, or manage traffic for green/blue deployments, canary deployments, or A/B testing. - -This core service mesh provides features that include but are not limited to the following: - -- **Traffic Management** such as ingress and egress routing, circuit breaking, mirroring. -- **Security** with resources to authenticate and authorize traffic and users, mTLS included. -- **Observability** of logs, metrics, and distributed traffic flows. - -After [setting up istio]({{}}/rancher/v2.6/en/istio/setup) you can leverage Istio's control plane functionality through the Rancher UI, `kubectl`, or `istioctl`. - -Istio needs to be set up by a `cluster-admin` before it can be used in a project. - -- [What's New in Rancher v2.5](#what-s-new-in-rancher-v2-5) -- [Tools Bundled with Istio](#tools-bundled-with-istio) -- [Prerequisites](#prerequisites) -- [Setup Guide](#setup-guide) -- [Remove Istio](#remove-istio) -- [Migrate from Previous Istio Version](#migrate-from-previous-istio-version) -- [Accessing Visualizations](#accessing-visualizations) -- [Architecture](#architecture) -- [Additional steps for installing Istio on an RKE2 cluster](#additional-steps-for-installing-istio-on-an-rke2-cluster) - -# What's New in Rancher v2.5 - -The overall architecture of Istio has been simplified. A single component, Istiod, has been created by combining Pilot, Citadel, Galley and the sidecar injector. Node Agent functionality has also been merged into istio-agent. - -Addons that were previously installed by Istio (cert-manager, Grafana, Jaeger, Kiali, Prometheus, Zipkin) will now need to be installed separately. Istio will support installation of integrations that are from the Istio Project and will maintain compatibility with those that are not. - -A Prometheus integration will still be available through an installation of [Rancher Monitoring]({{}}/rancher/v2.6/en/monitoring-alerting/), or by installing your own Prometheus operator. Rancher's Istio chart will also install Kiali by default to ensure you can get a full picture of your microservices out of the box. - -Istio has migrated away from Helm as a way to install Istio and now provides installation through the istioctl binary or Istio Operator. To ensure the easiest interaction with Istio, Rancher's Istio will maintain a Helm chart that utilizes the istioctl binary to manage your Istio installation. - -This Helm chart will be available via the Apps and Marketplace in the UI. A user that has access to the Rancher Chart's catalog will need to set up Istio before it can be used in the project. - -# Tools Bundled with Istio - -Our [Istio](https://istio.io/) installer wraps the istioctl binary commands in a handy Helm chart, including an overlay file option to allow complex customization. - -It also includes the following: - -### Kiali - -Kiali is a comprehensive visualization aid used for graphing traffic flow throughout the service mesh. It allows you to see how they are connected, including the traffic rates and latencies between them. - -You can check the health of the service mesh, or drill down to see the incoming and outgoing requests to a single component. - -### Jaeger - -Our Istio installer includes a quick-start, all-in-one installation of [Jaeger,](https://www.jaegertracing.io/) a tool used for tracing distributed systems. - -Note that this is not a production-qualified deployment of Jaeger. This deployment uses an in-memory storage component, while a persistent storage component is recommended for production. For more information on which deployment strategy you may need, refer to the [Jaeger documentation.](https://www.jaegertracing.io/docs/latest/operator/#production-strategy) - -# Prerequisites - -Before enabling Istio, we recommend that you confirm that your Rancher worker nodes have enough [CPU and memory]({{}}/rancher/v2.6/en/istio/resources) to run all of the components of Istio. - -If you are installing Istio on RKE2 cluster, some additional steps are required. For details, see [this section.](#additional-steps-for-installing-istio-on-an-rke2-cluster) - -Note that Istio v2 (upstream Istio v1.7+) cannot be upgraded in an air gapped environment. - -# Setup Guide - -Refer to the [setup guide]({{}}/rancher/v2.6/en/istio/setup) for instructions on how to set up Istio and use it in a project. - -# Remove Istio - -To remove Istio components from a cluster, namespace, or workload, refer to the section on [uninstalling Istio.]({{}}/rancher/v2.6/en/istio/disabling-istio/) - -# Migrate From Previous Istio Version - -There is no upgrade path for Istio versions less than 1.7.x. To successfully install Istio through **Apps & Marketplace,** you will need to disable your existing Istio from the global view in the legacy Rancher UI. - -If you have a significant amount of additional Istio CRDs you might consider manually migrating CRDs that are supported in both versions of Istio. You can do this by running `kubectl get -n istio-system -o yaml`, save the output yaml and re-apply in the new version. - -Another option is to manually uninstall istio resources one at a time, but leave the resources that are supported in both versions of Istio and that will not be installed by the newest version. This method is more likely to result in issues installing the new version, but could be a good option depending on your situation. - -# Accessing Visualizations - -> By default, only cluster-admins have access to Kiali. For instructions on how to allow admin, edit or views roles to access them, see [this section.]({{}}/rancher/v2.6/en/istio/rbac/) - -After Istio is set up in a cluster, Grafana, Prometheus, and Kiali are available in the Rancher UI. - -To access the Grafana and Prometheus visualizations, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the visualizations and click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Grafana** or any of the other dashboards. - -To access the Kiali visualization, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see Kiali and click **Explore**. -1. In the left navigation bar, click **Istio**. -1. Click **Kiali**. From here you can access the **Traffic Graph** tab or the **Traffic Metrics** tab to see network visualizations and metrics. - -By default, all namespace will picked up by prometheus and make data available for Kiali graphs. Refer to [selector/scrape config setup](./configuration-reference/selectors-and-scrape) if you would like to use a different configuration for prometheus data scraping. - -Your access to the visualizations depend on your role. Grafana and Prometheus are only available for `cluster-admin` roles. The Kiali UI is available only to `cluster-admin` by default, but `cluster-admin` can allow other roles to access them by editing the Istio values.yaml. - -# Architecture - -Istio installs a service mesh that uses [Envoy](https://www.envoyproxy.io/learn/service-mesh) sidecar proxies to intercept traffic to each workload. These sidecars intercept and manage service-to-service communication, allowing fine-grained observation and control over traffic within the cluster. - -Only workloads that have the Istio sidecar injected can be tracked and controlled by Istio. - -When a namespace has Istio enabled, new workloads deployed in the namespace will automatically have the Istio sidecar. You need to manually enable Istio in preexisting workloads. - -For more information on the Istio sidecar, refer to the [Istio sidecare-injection docs](https://istio.io/docs/setup/kubernetes/additional-setup/sidecar-injection/) and for more information on Istio's architecture, refer to the [Istio Architecture docs](https://istio.io/latest/docs/ops/deployment/architecture/) - -### Multiple Ingresses - -By default, each Rancher-provisioned cluster has one NGINX ingress controller allowing traffic into the cluster. Istio also installs an ingress gateway by default into the `istio-system` namespace. The result is that your cluster will have two ingresses in your cluster. - -![In an Istio-enabled cluster, you can have two ingresses: the default Nginx ingress, and the default Istio controller.]({{}}/img/rancher/istio-ingress.svg) - - Additional Istio Ingress gateways can be enabled via the [overlay file]({{}}/rancher/v2.6/en/istio/configuration-reference/#overlay-file). - -### Egress Support - -By default the Egress gateway is disabled, but can be enabled on install or upgrade through the values.yaml or via the [overlay file]({{}}/rancher/v2.6/en/istio/configuration-reference/#overlay-file). - -# Additional Steps for Installing Istio on an RKE2 Cluster - -To install Istio on an RKE2 cluster, follow the steps in [this section.]({{}}/rancher/v2.6/en/istio/configuration-reference/rke2/) diff --git a/versioned_docs/version-2.6/istio/rbac/rbac.md b/versioned_docs/version-2.6/istio/rbac/rbac.md deleted file mode 100644 index 8b69fc87a4c..00000000000 --- a/versioned_docs/version-2.6/istio/rbac/rbac.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Role-based Access Control -weight: 3 ---- - -This section describes the permissions required to access Istio features. - -The rancher istio chart installs three `ClusterRoles` - -## Cluster-Admin Access - -By default, only those with the `cluster-admin` `ClusterRole` can: - -- Install istio app in a cluster -- Configure resource allocations for Istio - - -## Admin and Edit access - -By default, only Admin and Edit roles can: - -- Enable and disable Istio sidecar auto-injection for namespaces -- Add the Istio sidecar to workloads -- View the traffic metrics and traffic graph for the cluster -- Configure Istio's resources (such as the gateway, destination rules, or virtual services) - -## Summary of Default Permissions for Kubernetes Default roles - -Istio creates three `ClusterRoles` and adds Istio CRD access to the following default K8s `ClusterRole`: - -ClusterRole create by chart | Default K8s ClusterRole | Rancher Role | - ------------------------------:| ---------------------------:|---------:| - `istio-admin` | admin| Project Owner | - `istio-edit`| edit | Project Member | - `istio-view` | view | Read-only | - -Rancher will continue to use cluster-owner, cluster-member, project-owner, project-member, etc as role names, but will utilize default roles to determine access. For each default K8s `ClusterRole` there are different Istio CRD permissions and K8s actions (Create ( C ), Get ( G ), List ( L ), Watch ( W ), Update ( U ), Patch ( P ), Delete( D ), All ( * )) that can be performed. - - -|CRDs | Admin | Edit | View -|----------------------------| ------| -----| ----- -|
  • `config.istio.io`
    • `adapters`
    • `attributemanifests`
    • `handlers`
    • `httpapispecbindings`
    • `httpapispecs`
    • `instances`
    • `quotaspecbindings`
    • `quotaspecs`
    • `rules`
    • `templates`
| GLW | GLW | GLW -|
  • `networking.istio.io`
    • `destinationrules`
    • `envoyfilters`
    • `gateways`
    • `serviceentries`
    • `sidecars`
    • `virtualservices`
    • `workloadentries`
| * | * | GLW -|
  • `security.istio.io`
    • `authorizationpolicies`
    • `peerauthentications`
    • `requestauthentications`
| * | * | GLW \ No newline at end of file diff --git a/versioned_docs/version-2.6/istio/resources/resources.md b/versioned_docs/version-2.6/istio/resources/resources.md deleted file mode 100644 index bb40d0fc6b5..00000000000 --- a/versioned_docs/version-2.6/istio/resources/resources.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: CPU and Memory Allocations -weight: 1 ---- - -This section describes the minimum recommended computing resources for the Istio components in a cluster. - -The CPU and memory allocations for each component are [configurable.](#configuring-resource-allocations) - -Before enabling Istio, we recommend that you confirm that your Rancher worker nodes have enough CPU and memory to run all of the components of Istio. - -> **Tip:** In larger deployments, it is strongly advised that the infrastructure be placed on dedicated nodes in the cluster by adding a node selector for each Istio component. - -The table below shows a summary of the minimum recommended resource requests and limits for the CPU and memory of each core Istio component. - -In Kubernetes, the resource request indicates that the workload will not deployed on a node unless the node has at least the specified amount of memory and CPU available. If the workload surpasses the limit for CPU or memory, it can be terminated or evicted from the node. For more information on managing resource limits for containers, refer to the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/) - -| Workload | CPU - Request | Memory - Request | CPU - Limit | Memory - Limit | -|----------------------|---------------|------------|-----------------|-------------------| -| ingress gateway | 100m | 128mi | 2000m | 1024mi | -| egress gateway | 100m | 128mi | 2000m | 1024mi | -| istiod | 500m | 2048mi | No limit | No limit | -| proxy | 10m | 10mi | 2000m | 1024mi | -| **Totals:** | **710m** | **2314Mi** | **6000m** | **3072Mi** | - -# Configuring Resource Allocations - -You can individually configure the resource allocation for each type of Istio component. This section includes the default resource allocations for each component. - -To make it easier to schedule the workloads to a node, a cluster-admin can reduce the CPU and memory resource requests for the component. However, the default CPU and memory allocations are the minimum that we recommend. - -You can find more information about Istio configuration in the [official Istio documentation](https://istio.io/). - -To configure the resources allocated to an Istio component, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Apps & Marketplace**. -1. Click **Installed Apps**. -1. Go to the `istio-system` namespace. In one of the Istio workloads, such as `rancher-istio`, click **⋮ > Edit/Upgrade**. -1. Click **Upgrade** to edit the base components via changes to the values.yaml or add an [overlay file]({{}}/rancher/v2.6/en/istio/configuration-reference/#overlay-file). For more information about editing the overlay file, see [this section.](./#editing-the-overlay-file) -1. Change the CPU or memory allocations, the nodes where each component will be scheduled to, or the node tolerations. -1. Click **Upgrade**. to rollout changes - -**Result:** The resource allocations for the Istio components are updated. - -### Editing the Overlay File - -The overlay file can contain any of the values in the [Istio Operator spec.](https://istio.io/latest/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec) The overlay file included with the Istio application is just one example of a potential configuration of the overlay file. - -As long as the file contains `kind: IstioOperator` and the YAML options are valid, the file can be used as an overlay. - -In the example overlay file provided with the Istio application, the following section allows you to change Kubernetes resources: - -``` -# k8s: -# resources: -# requests: -# cpu: 200m -``` diff --git a/versioned_docs/version-2.6/istio/setup/deploy-workloads/deploy-workloads.md b/versioned_docs/version-2.6/istio/setup/deploy-workloads/deploy-workloads.md deleted file mode 100644 index cf91f928e8c..00000000000 --- a/versioned_docs/version-2.6/istio/setup/deploy-workloads/deploy-workloads.md +++ /dev/null @@ -1,356 +0,0 @@ ---- -title: 3. Add Deployments and Services with the Istio Sidecar -weight: 4 ---- - -> **Prerequisite:** To enable Istio for a workload, the cluster and namespace must have the Istio app installed. - -Enabling Istio in a namespace only enables automatic sidecar injection for new workloads. To enable the Envoy sidecar for existing workloads, you need to enable it manually for each workload. - -To inject the Istio sidecar on an existing workload in the namespace, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the visualizations and click **Explore**. -1. Click **Workload**. -1. Go to the workload where you want to inject the Istio sidecar and click **⋮ > Redeploy**. When the workload is redeployed, it will have the Envoy sidecar automatically injected. - -Wait a few minutes for the workload to upgrade to have the istio sidecar. Click it and go to the Containers section. You should be able to see `istio-proxy` alongside your original workload. This means the Istio sidecar is enabled for the workload. Istio is doing all the wiring for the sidecar envoy. Now Istio can do all the features automatically if you enable them in the yaml. - -### Add Deployments and Services - -There are a few ways to add new **Deployments** in your namespace: - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Workload**. -1. Click **Create**. -1. Click **Deployment**. -1. Fill out the form, or **Edit as Yaml**. -1. Click **Create**. - -To add a **Service** to your namespace: - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Service Discovery > Services**. -1. Click **Create**. -1. Select the type of service that you want. -1. Fill out the form, or **Edit as Yaml**. -1. Click **Create** - -You can also create deployments and services using the kubectl **shell** - -1. Run `kubectl create -f .yaml` if your file is stored locally in the cluster -1. Or run `cat<< EOF | kubectl apply -f -`, paste the file contents into the terminal, then run `EOF` to complete the command. - -### Example Deployments and Services - -Next we add the Kubernetes resources for the sample deployments and services for the BookInfo app in Istio's documentation. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the top navigation bar, open the kubectl shell. -1. Run `cat<< EOF | kubectl apply -f -` -1. Copy the below resources into the the shell. -1. Run `EOF` - -This will set up the following sample resources from Istio's example BookInfo app: - -Details service and deployment: - -- A `details` Service -- A ServiceAccount for `bookinfo-details` -- A `details-v1` Deployment - -Ratings service and deployment: - -- A `ratings` Service -- A ServiceAccount for `bookinfo-ratings` -- A `ratings-v1` Deployment - -Reviews service and deployments (three versions): - -- A `reviews` Service -- A ServiceAccount for `bookinfo-reviews` -- A `reviews-v1` Deployment -- A `reviews-v2` Deployment -- A `reviews-v3` Deployment - -Productpage service and deployment: - -This is the main page of the app, which will be visible from a web browser. The other services will be called from this page. - -- A `productpage` service -- A ServiceAccount for `bookinfo-productpage` -- A `productpage-v1` Deployment - -### Resource YAML - -```yaml -# Copyright 2017 Istio Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -################################################################################################## -# Details service -################################################################################################## -apiVersion: v1 -kind: Service -metadata: - name: details - labels: - app: details - service: details -spec: - ports: - - port: 9080 - name: http - selector: - app: details ---- -apiVersion: v1 -kind: ServiceAccount -metadata: - name: bookinfo-details ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: details-v1 - labels: - app: details - version: v1 -spec: - replicas: 1 - selector: - matchLabels: - app: details - version: v1 - template: - metadata: - labels: - app: details - version: v1 - spec: - serviceAccountName: bookinfo-details - containers: - - name: details - image: docker.io/istio/examples-bookinfo-details-v1:1.15.0 - imagePullPolicy: IfNotPresent - ports: - - containerPort: 9080 ---- -################################################################################################## -# Ratings service -################################################################################################## -apiVersion: v1 -kind: Service -metadata: - name: ratings - labels: - app: ratings - service: ratings -spec: - ports: - - port: 9080 - name: http - selector: - app: ratings ---- -apiVersion: v1 -kind: ServiceAccount -metadata: - name: bookinfo-ratings ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: ratings-v1 - labels: - app: ratings - version: v1 -spec: - replicas: 1 - selector: - matchLabels: - app: ratings - version: v1 - template: - metadata: - labels: - app: ratings - version: v1 - spec: - serviceAccountName: bookinfo-ratings - containers: - - name: ratings - image: docker.io/istio/examples-bookinfo-ratings-v1:1.15.0 - imagePullPolicy: IfNotPresent - ports: - - containerPort: 9080 ---- -################################################################################################## -# Reviews service -################################################################################################## -apiVersion: v1 -kind: Service -metadata: - name: reviews - labels: - app: reviews - service: reviews -spec: - ports: - - port: 9080 - name: http - selector: - app: reviews ---- -apiVersion: v1 -kind: ServiceAccount -metadata: - name: bookinfo-reviews ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: reviews-v1 - labels: - app: reviews - version: v1 -spec: - replicas: 1 - selector: - matchLabels: - app: reviews - version: v1 - template: - metadata: - labels: - app: reviews - version: v1 - spec: - serviceAccountName: bookinfo-reviews - containers: - - name: reviews - image: docker.io/istio/examples-bookinfo-reviews-v1:1.15.0 - imagePullPolicy: IfNotPresent - ports: - - containerPort: 9080 ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: reviews-v2 - labels: - app: reviews - version: v2 -spec: - replicas: 1 - selector: - matchLabels: - app: reviews - version: v2 - template: - metadata: - labels: - app: reviews - version: v2 - spec: - serviceAccountName: bookinfo-reviews - containers: - - name: reviews - image: docker.io/istio/examples-bookinfo-reviews-v2:1.15.0 - imagePullPolicy: IfNotPresent - ports: - - containerPort: 9080 ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: reviews-v3 - labels: - app: reviews - version: v3 -spec: - replicas: 1 - selector: - matchLabels: - app: reviews - version: v3 - template: - metadata: - labels: - app: reviews - version: v3 - spec: - serviceAccountName: bookinfo-reviews - containers: - - name: reviews - image: docker.io/istio/examples-bookinfo-reviews-v3:1.15.0 - imagePullPolicy: IfNotPresent - ports: - - containerPort: 9080 ---- -################################################################################################## -# Productpage services -################################################################################################## -apiVersion: v1 -kind: Service -metadata: - name: productpage - labels: - app: productpage - service: productpage -spec: - ports: - - port: 9080 - name: http - selector: - app: productpage ---- -apiVersion: v1 -kind: ServiceAccount -metadata: - name: bookinfo-productpage ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: productpage-v1 - labels: - app: productpage - version: v1 -spec: - replicas: 1 - selector: - matchLabels: - app: productpage - version: v1 - template: - metadata: - labels: - app: productpage - version: v1 - spec: - serviceAccountName: bookinfo-productpage - containers: - - name: productpage - image: docker.io/istio/examples-bookinfo-productpage-v1:1.15.0 - imagePullPolicy: IfNotPresent - ports: - - containerPort: 9080 ---- -``` - -### [Next: Set up the Istio Gateway]({{}}/rancher/v2.6/en/istio/setup/gateway) diff --git a/versioned_docs/version-2.6/istio/setup/enable-istio-in-cluster/enable-istio-in-cluster.md b/versioned_docs/version-2.6/istio/setup/enable-istio-in-cluster/enable-istio-in-cluster.md deleted file mode 100644 index 62ab5e95d28..00000000000 --- a/versioned_docs/version-2.6/istio/setup/enable-istio-in-cluster/enable-istio-in-cluster.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: 1. Enable Istio in the Cluster -weight: 1 ---- - ->**Prerequisites:** -> ->- Only a user with the `cluster-admin` [Kubernetes default role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) assigned can configure and install Istio in a Kubernetes cluster. ->- If you have pod security policies, you will need to install Istio with the CNI enabled. For details, see [this section.]({{}}/rancher/v2.6/en/istio/configuration-reference/enable-istio-with-psp) ->- To install Istio on an RKE2 cluster, additional steps are required. For details, see [this section.]({{}}/rancher/v2.6/en/istio/configuration-reference/rke2/) ->- To install Istio in a cluster where project network isolation is enabled, additional steps are required. For details, see [this section.]({{}}/rancher/v2.6/en/istio/configuration-reference/canal-and-project-network) - -1. Click **☰ > Cluster Management**. -1. Go to the where you want to enable Istio and click **Explore**. -1. Click **Apps & Marketplace**. -1. Click **Charts**. -1. Click **Istio**. -1. If you have not already installed your own monitoring app, you will be prompted to install the rancher-monitoring app. Optional: Set your Selector or Scrape config options on rancher-monitoring app install. -1. Optional: Configure member access and [resource limits]({{}}/rancher/v2.6/en/istio/resources/) for the Istio components. Ensure you have enough resources on your worker nodes to enable Istio. -1. Optional: Make additional configuration changes to values.yaml if needed. -1. Optional: Add additional resources or configuration via the [overlay file.]({{}}/rancher/v2.6/en/istio/configuration-reference/#overlay-file) -1. Click **Install**. - -**Result:** Istio is installed at the cluster level. - -# Additional Config Options - -For more information on configuring Istio, refer to the [configuration reference.]({{}}/rancher/v2.6/en/istio/configuration-reference) diff --git a/versioned_docs/version-2.6/istio/setup/enable-istio-in-namespace/enable-istio-in-namespace.md b/versioned_docs/version-2.6/istio/setup/enable-istio-in-namespace/enable-istio-in-namespace.md deleted file mode 100644 index 1c2b8e46baf..00000000000 --- a/versioned_docs/version-2.6/istio/setup/enable-istio-in-namespace/enable-istio-in-namespace.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: 2. Enable Istio in a Namespace -weight: 2 ---- - -You will need to manually enable Istio in each namespace that you want to be tracked or controlled by Istio. When Istio is enabled in a namespace, the Envoy sidecar proxy will be automatically injected into all new workloads that are deployed in the namespace. - -This namespace setting will only affect new workloads in the namespace. Any preexisting workloads will need to be re-deployed to leverage the sidecar auto injection. - -> **Prerequisite:** To enable Istio in a namespace, the cluster must have Istio installed. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Go to the namespace where you want to enable Istio and click **⋮ > Enable Istio Auto Injection**. Alternately, click the namespace, and then on the namespace detail page, click **⋮ > Enable Istio Auto Injection**. - -**Result:** The namespace now has the label `istio-injection=enabled`. All new workloads deployed in this namespace will have the Istio sidecar injected by default. - -### Verifying that Automatic Istio Sidecar Injection is Enabled - -To verify that Istio is enabled, deploy a hello-world workload in the namespace. Go to the workload and click the pod name. In the **Containers** section, you should see the `istio-proxy` container. - -### Excluding Workloads from Being Injected with the Istio Sidecar - -If you need to exclude a workload from getting injected with the Istio sidecar, use the following annotation on the workload: - -``` -sidecar.istio.io/inject: “false” -``` - -To add the annotation to a workload, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Workload**. -1. Go to the workload that should not have the sidecar and edit as yaml -1. Add the following key, value `sidecar.istio.io/inject: false` as an annotation on the workload -1. Click **Save**. - -**Result:** The Istio sidecar will not be injected into the workload. - -> **NOTE:** If you are having issues with a Job you deployed not completing, you will need to add this annotation to your pod using the provided steps. Since Istio Sidecars run indefinitely, a Job cannot be considered complete even after its task has completed. - - -### [Next: Add Deployments with the Istio Sidecar ]({{}}/rancher/v2.6/en/istio/setup/deploy-workloads) \ No newline at end of file diff --git a/versioned_docs/version-2.6/istio/setup/gateway/gateway.md b/versioned_docs/version-2.6/istio/setup/gateway/gateway.md deleted file mode 100644 index 5cd58e34e0e..00000000000 --- a/versioned_docs/version-2.6/istio/setup/gateway/gateway.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -title: 4. Set up the Istio Gateway -weight: 5 ---- - -The gateway to each cluster can have its own port or load balancer, which is unrelated to a service mesh. By default, each Rancher-provisioned cluster has one NGINX ingress controller allowing traffic into the cluster. - -You can use the Nginx Ingress controller with or without Istio installed. If this is the only gateway to your cluster, Istio will be able to route traffic from service to service, but Istio will not be able to receive traffic from outside the cluster. - -To allow Istio to receive external traffic, you need to enable Istio's gateway, which works as a north-south proxy for external traffic. When you enable the Istio gateway, the result is that your cluster will have two Ingresses. - -You will also need to set up a Kubernetes gateway for your services. This Kubernetes resource points to Istio's implementation of the ingress gateway to the cluster. - -You can route traffic into the service mesh with a load balancer or use Istio's NodePort gateway. This section describes how to set up the NodePort gateway. - -For more information on the Istio gateway, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/gateway/) - -![In an Istio-enabled cluster, you can have two Ingresses: the default Nginx Ingress, and the default Istio controller.]({{}}/img/rancher/istio-ingress.svg) - -# Enable an Istio Gateway - -The ingress gateway is a Kubernetes service that will be deployed in your cluster. The Istio Gateway allows for more extensive customization and flexibility. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Istio > Gateways**. -1. Click **Create from Yaml**. -1. Paste your Istio Gateway yaml, or **Read from File**. -1. Click **Create**. - -**Result:** The gateway is deployed, and will now route traffic with applied rules. - -# Example Istio Gateway - -We add the BookInfo app deployments in services when going through the Workloads example. Next we add an Istio Gateway so that the app is accessible from outside your cluster. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Istio > Gateways**. -1. Click **Create from Yaml**. -1. Copy and paste the Gateway yaml provided below. -1. Click **Create**. - -```yaml -apiVersion: networking.istio.io/v1alpha3 -kind: Gateway -metadata: - name: bookinfo-gateway -spec: - selector: - istio: ingressgateway # use istio default controller - servers: - - port: - number: 80 - name: http - protocol: HTTP - hosts: - - "*" ---- -``` - -Then to deploy the VirtualService that provides the traffic routing for the Gateway: - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Istio > VirtualServices**. -1. Copy and paste the VirtualService yaml provided below. -1. Click **Create**. - -```yaml -apiVersion: networking.istio.io/v1alpha3 -kind: VirtualService -metadata: - name: bookinfo -spec: - hosts: - - "*" - gateways: - - bookinfo-gateway - http: - - match: - - uri: - exact: /productpage - - uri: - prefix: /static - - uri: - exact: /login - - uri: - exact: /logout - - uri: - prefix: /api/v1/products - route: - - destination: - host: productpage - port: - number: 9080 -``` - -**Result:** You have configured your gateway resource so that Istio can receive traffic from outside the cluster. - -Confirm that the resource exists by running: -``` -kubectl get gateway -A -``` - -The result should be something like this: -``` -NAME AGE -bookinfo-gateway 64m -``` - -### Access the ProductPage Service from a Web Browser - -To test and see if the BookInfo app deployed correctly, the app can be viewed a web browser using the Istio controller IP and port, combined with the request name specified in your Kubernetes gateway resource: - -`http://:/productpage` - -To get the ingress gateway URL and port, - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Workload**. -1. Scroll down to the `istio-system` namespace. -1. Within `istio-system`, there is a workload named `istio-ingressgateway`. Under the name of this workload, you should see links, such as `80/tcp`. -1. Click one of those links. This should show you the URL of the ingress gateway in your web browser. Append `/productpage` to the URL. - -**Result:** You should see the BookInfo app in the web browser. - -For help inspecting the Istio controller URL and ports, try the commands the [Istio documentation.](https://istio.io/docs/tasks/traffic-management/ingress/ingress-control/#determining-the-ingress-ip-and-ports) - -# Troubleshooting - -The [official Istio documentation](https://istio.io/docs/tasks/traffic-management/ingress/ingress-control/#troubleshooting) suggests `kubectl` commands to inspect the correct ingress host and ingress port for external requests. - -### Confirming that the Kubernetes Gateway Matches Istio's Ingress Controller - -You can try the steps in this section to make sure the Kubernetes gateway is configured properly. - -In the gateway resource, the selector refers to Istio's default ingress controller by its label, in which the key of the label is `istio` and the value is `ingressgateway`. To make sure the label is appropriate for the gateway, do the following: - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Workload**. -1. Scroll down to the `istio-system` namespace. -1. Within `istio-system`, there is a workload named `istio-ingressgateway`. Click the name of this workload and go to the **Labels and Annotations** section. You should see that it has the key `istio` and the value `ingressgateway`. This confirms that the selector in the Gateway resource matches Istio's default ingress controller. - -### [Next: Set up Istio's Components for Traffic Management]({{}}/rancher/v2.6/en/istio/setup/set-up-traffic-management) diff --git a/versioned_docs/version-2.6/istio/setup/set-up-traffic-management/set-up-traffic-management.md b/versioned_docs/version-2.6/istio/setup/set-up-traffic-management/set-up-traffic-management.md deleted file mode 100644 index a323135e3d5..00000000000 --- a/versioned_docs/version-2.6/istio/setup/set-up-traffic-management/set-up-traffic-management.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: 5. Set up Istio's Components for Traffic Management -weight: 6 ---- - -A central advantage of traffic management in Istio is that it allows dynamic request routing. Some common applications for dynamic request routing include canary deployments and blue/green deployments. The two key resources in Istio traffic management are *virtual services* and *destination rules*. - -- [Virtual services](https://istio.io/docs/reference/config/networking/v1alpha3/virtual-service/) intercept and direct traffic to your Kubernetes services, allowing you to divide percentages of traffic from a request to different services. You can use them to define a set of routing rules to apply when a host is addressed. -- [Destination rules](https://istio.io/docs/reference/config/networking/v1alpha3/destination-rule/) serve as the single source of truth about which service versions are available to receive traffic from virtual services. You can use these resources to define policies that apply to traffic that is intended for a service after routing has occurred. - -This section describes how to add an example virtual service that corresponds to the `reviews` microservice in the sample BookInfo app. The purpose of this service is to divide traffic between two versions of the `reviews` service. - -In this example, we take the traffic to the `reviews` service and intercept it so that 50 percent of it goes to `v1` of the service and 50 percent goes to `v2`. - -After this virtual service is deployed, we will generate traffic and see from the Kiali visualization that traffic is being routed evenly between the two versions of the service. - -To deploy the virtual service and destination rules for the `reviews` service, -1. Click **☰ > Cluster Management**. -1. Go to the cluster where Istio is installed and click **Explore**. -1. In the cluster where Istio is installed, click **Istio > DestinationRules** in the left navigation bar. -1. Click **Create**. -1. Copy and paste the DestinationRule yaml provided below. -1. Click **Create**. -1. Click **Edit as YAML** and use this configuration: - - ```yaml - apiVersion: networking.istio.io/v1alpha3 - kind: DestinationRule - metadata: - name: reviews - spec: - host: reviews - subsets: - - name: v1 - labels: - version: v1 - - name: v2 - labels: - version: v2 - - name: v3 - labels: - version: v3 - ``` -1. Click **Create**. - -Then to deploy the VirtualService that provides the traffic routing that utilizes the DestinationRule: - -1. Click **VirtualService** in the side nav bar. -1. Click **Create from Yaml**. -1. Copy and paste the VirtualService yaml provided below. -1. Click **Create**. - -```yaml -apiVersion: networking.istio.io/v1alpha3 -kind: VirtualService -metadata: - name: reviews -spec: - hosts: - - reviews - http: - - route: - - destination: - host: reviews - subset: v1 - weight: 50 - - destination: - host: reviews - subset: v3 - weight: 50 ---- -``` - -**Result:** When you generate traffic to this service (for example, by refreshing the ingress gateway URL), the Kiali traffic graph will reflect that traffic to the `reviews` service is divided evenly between `v1` and `v3`. - -### [Next: Generate and View Traffic]({{}}/rancher/v2.6/en/istio/setup/view-traffic) diff --git a/versioned_docs/version-2.6/istio/setup/setup.md b/versioned_docs/version-2.6/istio/setup/setup.md deleted file mode 100644 index 27c126a8d77..00000000000 --- a/versioned_docs/version-2.6/istio/setup/setup.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Setup Guide -weight: 2 ---- - -This section describes how to enable Istio and start using it in your projects. - -If you use Istio for traffic management, you will need to allow external traffic to the cluster. In that case, you will need to follow all of the steps below. - -# Prerequisites - -This guide assumes you have already [installed Rancher,]({{}}/rancher/v2.6/en/installation) and you have already [provisioned a separate Kubernetes cluster]({{}}/rancher/v2.6/en/cluster-provisioning) on which you will install Istio. - -The nodes in your cluster must meet the [CPU and memory requirements.]({{}}/rancher/v2.6/en/istio/resources/) - -The workloads and services that you want to be controlled by Istio must meet [Istio's requirements.](https://istio.io/docs/setup/additional-setup/requirements/) - - -# Install - -> **Quick Setup** If you don't need external traffic to reach Istio, and you just want to set up Istio for monitoring and tracing traffic within the cluster, skip the steps for [setting up the Istio gateway]({{}}/rancher/v2.6/en/istio/setup/gateway) and [setting up Istio's components for traffic management.]({{}}/rancher/v2.6/en/istio/setup/set-up-traffic-management) - -1. [Enable Istio in the cluster.]({{}}/rancher/v2.6/en/istio/setup/enable-istio-in-cluster) -1. [Enable Istio in all the namespaces where you want to use it.]({{}}/rancher/v2.6/en/istio/setup/enable-istio-in-namespace) -1. [Add deployments and services that have the Istio sidecar injected.]({{}}/rancher/v2.6/en/istio/setup/deploy-workloads) -1. [Set up the Istio gateway. ]({{}}/rancher/v2.6/en/istio/setup/gateway) -1. [Set up Istio's components for traffic management.]({{}}/rancher/v2.6/en/istio/setup/set-up-traffic-management) -1. [Generate traffic and see Istio in action.]({{}}/rancher/v2.6/en/istio/setup/view-traffic/ ) diff --git a/versioned_docs/version-2.6/istio/setup/view-traffic/view-traffic.md b/versioned_docs/version-2.6/istio/setup/view-traffic/view-traffic.md deleted file mode 100644 index 0c1b5597b15..00000000000 --- a/versioned_docs/version-2.6/istio/setup/view-traffic/view-traffic.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: 6. Generate and View Traffic -weight: 7 ---- - -This section describes how to view the traffic that is being managed by Istio. - -# The Kiali Traffic Graph - -The Istio overview page provides a link to the Kiali dashboard. From the Kiali dashboard, you are able to view graphs for each namespace. The Kiali graph provides a powerful way to visualize the topology of your Istio service mesh. It shows you which services communicate with each other. - ->**Prerequisite:** To enable traffic to show up in the graph, ensure you have prometheus installed in the cluster. Rancher-istio installs Kiali configured by default to work with the rancher-monitoring chart. You can use rancher-monitoring or install your own monitoring solution. Optional: you can change configuration on how data scraping occurs by setting the [Selectors & Scrape Configs]({{}}/rancher/v2.6/en/istio/configuration-reference/selectors-and-scrape) options. - -To see the traffic graph, - -1. In the cluster where Istio is installed, click **Istio** in the left navigation bar. -1. Click the **Kiali** link. -1. Click on **Graph** in the side nav. -1. Change the namespace in the **Namespace** dropdown to view the traffic for each namespace. - -If you refresh the URL to the BookInfo app several times, you should be able to see green arrows on the Kiali graph showing traffic to `v1` and `v3` of the `reviews` service. The control panel on the right side of the graph lets you configure details including how many minutes of the most recent traffic should be shown on the graph. - -For additional tools and visualizations, you can go to Grafana, and Prometheus dashboards from the **Monitoring** **Overview** page diff --git a/versioned_docs/version-2.6/k8s-in-rancher/certificates/certificates.md b/versioned_docs/version-2.6/k8s-in-rancher/certificates/certificates.md deleted file mode 100644 index ae8ee6911d4..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/certificates/certificates.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Encrypting HTTP Communication -description: Learn how to add an SSL (Secure Sockets Layer) certificate or TLS (Transport Layer Security) certificate -weight: 3060 ---- - -When you create an ingress within Rancher/Kubernetes, you must provide it with a secret that includes a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by adding the certificate to the ingress deployment. - ->**Prerequisites:** You must have a TLS private key and certificate available to upload. - -### 1. Create a Secret - - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to deploy your ingress and click **More Resources > Core > Secrets**. -1. Click **Create**. -1. Click **TLS Certificate**. -1. Enter a name for the secret. Note: Your secret must have a unique name among the other certificates, registries, and secrets within your project/workspace. -1. In the **Private Key** field, either copy and paste your certificate's private key into the text box (include the header and footer), or click **Read from a file** to browse to the private key on your file system. If possible, we recommend using **Read from a file** to reduce likelihood of error. Note: Private key files end with an extension of `.key`. -1. In the **Certificate** field, either copy and paste your certificate into the text box (include the header and footer), or click **Read from a file** to browse to the certificate on your file system. If possible, we recommend using **Read from a file** to reduce likelihood of error. Note: Certificate files end with an extension of `.crt`. -1. Click **Create**. - -### 2. Add the Secret to an Ingress - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to deploy your ingress and click **Service Discovery > Ingresses**. -1. Click **Create**. -1. Select the **Namespace** of the ingress. -1. Enter a **Name** for the ingress. -1. In the **Certificates** tab, select the secret containing your certificate and private key. -1. Click **Create**. - -## What's Next? - -Now you can add the certificate when launching an ingress within the current project or namespace. For more information, see [Adding Ingress]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/ingress/). diff --git a/versioned_docs/version-2.6/k8s-in-rancher/configmaps/configmaps.md b/versioned_docs/version-2.6/k8s-in-rancher/configmaps/configmaps.md deleted file mode 100644 index 4c4653cd2f1..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/configmaps/configmaps.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: ConfigMaps -weight: 3061 ---- - -While most types of Kubernetes secrets store sensitive information, [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) store general configuration information, such as a group of config files. Because ConfigMaps don't store sensitive information, they can be updated automatically, and therefore don't require their containers to be restarted following update (unlike most secret types, which require manual updates and a container restart to take effect). - -ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. After you upload a config map, any workload can reference it as either an environment variable or a volume mount. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that has the workload that should reference a ConfigMap and click **Explore**. -1. In the left navigation bar, click **More Resources > Core > ConfigMaps**. -1. Click **Create**. -1. Enter a **Name** for the Config Map. - - >**Note:** Kubernetes classifies ConfigMaps as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your ConfigMaps must have a unique name among the other certificates, registries, and secrets within your workspace. - -1. Select the **Namespace** you want to add Config Map to. - -1. On the **Data** tab, add a key-value pair to your ConfigMap. Add as many values as you need. You can add multiple key value pairs to the ConfigMap by copying and pasting. Alternatively, use **Read from File** to add the data. Note: If you need to store sensitive data, [use a secret]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/), not a ConfigMap. -1. Click **Create**. - -**Result:** Your ConfigMap is added to the namespace. You can view it in the Rancher UI from the **Resources > Config Maps** view. - -## What's Next? - -Now that you have a ConfigMap added to a namespace, you can add it to a workload that you deploy from the namespace of origin. You can use the ConfigMap to specify information for you application to consume, such as: - -- Application environment variables. -- Specifying parameters for a Volume mounted to the workload. - -For more information on adding ConfigMaps to a workload, see [Deploying Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/deploy-workloads/). diff --git a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/horitzontal-pod-autoscaler.md b/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/horitzontal-pod-autoscaler.md deleted file mode 100644 index 81501e270a9..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/horitzontal-pod-autoscaler.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: The Horizontal Pod Autoscaler -description: Learn about the horizontal pod autoscaler (HPA). How to manage HPAs and how to test them with a service deployment -weight: 3026 ---- - -The [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) (HPA) is a Kubernetes feature that allows you to configure your cluster to automatically scale the services it's running up or down. - -Rancher provides some additional features to help manage HPAs, depending on the version of Rancher. - -You can create, manage, and delete HPAs using the Rancher UI. It only supports HPA in the `autoscaling/v2beta2` API. - -## Managing HPAs - -The way that you manage HPAs is different based on your version of the Kubernetes API: - -- **For Kubernetes API version autoscaling/V2beta1:** This version of the Kubernetes API lets you autoscale your pods based on the CPU and memory utilization of your application. -- **For Kubernetes API Version autoscaling/V2beta2:** This version of the Kubernetes API lets you autoscale your pods based on CPU and memory utilization, in addition to custom metrics. - -You can create, manage, and delete HPAs using the Rancher UI. From the Rancher UI you can configure the HPA to scale based on CPU and memory utilization. For more information, refer to [Managing HPAs with the Rancher UI]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui). To scale the HPA based on custom metrics, you still need to use `kubectl`. For more information, refer to [Configuring HPA to Scale Using Custom Metrics with Prometheus]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/#configuring-hpa-to-scale-using-custom-metrics-with-prometheus). - -Clusters created in Rancher v2.0.7 and higher automatically have all the requirements needed (metrics-server and Kubernetes cluster configuration) to use HPA. -## Testing HPAs with a Service Deployment - -You can see your HPA's current number of replicas by going to your project and clicking **Resources > HPA**. For more information, refer to [Get HPA Metrics and Status]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/). - -You can also use `kubectl` to get the status of HPAs that you test with your load testing tool. For more information, refer to [Testing HPAs with kubectl] -({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/). diff --git a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/hpa-background.md b/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/hpa-background.md deleted file mode 100644 index c2a8dfc53fc..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/hpa-background.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Background Information on HPAs -weight: 3027 ---- - -The [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) (HPA) is a Kubernetes feature that allows you to configure your cluster to automatically scale the services it's running up or down. This section provides explanation on how HPA works with Kubernetes. - -## Why Use Horizontal Pod Autoscaler? - -Using HPA, you can automatically scale the number of pods within a replication controller, deployment, or replica set up or down. HPA automatically scales the number of pods that are running for maximum efficiency. Factors that affect the number of pods include: - -- A minimum and maximum number of pods allowed to run, as defined by the user. -- Observed CPU/memory use, as reported in resource metrics. -- Custom metrics provided by third-party metrics application like Prometheus, Datadog, etc. - -HPA improves your services by: - -- Releasing hardware resources that would otherwise be wasted by an excessive number of pods. -- Increase/decrease performance as needed to accomplish service level agreements. - -## How HPA Works - -![HPA Schema]({{}}/img/rancher/horizontal-pod-autoscaler.jpg) - -HPA is implemented as a control loop, with a period controlled by the `kube-controller-manager` flags below: - -Flag | Default | Description | ----------|----------|----------| - `--horizontal-pod-autoscaler-sync-period` | `30s` | How often HPA audits resource/custom metrics in a deployment. - `--horizontal-pod-autoscaler-downscale-delay` | `5m0s` | Following completion of a downscale operation, how long HPA must wait before launching another downscale operations. - `--horizontal-pod-autoscaler-upscale-delay` | `3m0s` | Following completion of an upscale operation, how long HPA must wait before launching another upscale operation. - - -For full documentation on HPA, refer to the [Kubernetes Documentation](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). - -## Horizontal Pod Autoscaler API Objects - -HPA is an API resource in the Kubernetes `autoscaling` API group. The current stable version is `autoscaling/v1`, which only includes support for CPU autoscaling. To get additional support for scaling based on memory and custom metrics, use the beta version instead: `autoscaling/v2beta1`. - -For more information about the HPA API object, see the [HPA GitHub Readme](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md#horizontalpodautoscaler-object). diff --git a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/manage-hpa-with-kubectl.md b/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/manage-hpa-with-kubectl.md deleted file mode 100644 index 54cb32432b4..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/manage-hpa-with-kubectl.md +++ /dev/null @@ -1,208 +0,0 @@ ---- -title: Managing HPAs with kubectl -weight: 3029 ---- - -This section describes HPA management with `kubectl`. This document has instructions for how to: - -- Create an HPA -- Get information on HPAs -- Delete an HPA -- Configure your HPAs to scale with CPU or memory utilization -- Configure your HPAs to scale using custom metrics, if you use a third-party tool such as Prometheus for metrics - - -You can create, view, and delete HPAs from the Rancher UI. You can also configure them to scale based on CPU or memory usage from the Rancher UI. For more information, refer to [Managing HPAs with the Rancher UI]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui). For scaling HPAs based on other metrics than CPU or memory, you still need `kubectl`. - -##### Basic kubectl Command for Managing HPAs - -If you have an HPA manifest file, you can create, manage, and delete HPAs using `kubectl`: - -- Creating HPA - - - With manifest: `kubectl create -f ` - - - Without manifest (Just support CPU): `kubectl autoscale deployment hello-world --min=2 --max=5 --cpu-percent=50` - -- Getting HPA info - - - Basic: `kubectl get hpa hello-world` - - - Detailed description: `kubectl describe hpa hello-world` - -- Deleting HPA - - - `kubectl delete hpa hello-world` - -##### HPA Manifest Definition Example - -The HPA manifest is the config file used for managing an HPA with `kubectl`. - -The following snippet demonstrates use of different directives in an HPA manifest. See the list below the sample to understand the purpose of each directive. - -```yml -apiVersion: autoscaling/v2beta1 -kind: HorizontalPodAutoscaler -metadata: - name: hello-world -spec: - scaleTargetRef: - apiVersion: extensions/v1beta1 - kind: Deployment - name: hello-world - minReplicas: 1 - maxReplicas: 10 - metrics: - - type: Resource - resource: - name: cpu - targetAverageUtilization: 50 - - type: Resource - resource: - name: memory - targetAverageValue: 100Mi -``` - - -Directive | Description ----------|----------| - `apiVersion: autoscaling/v2beta1` | The version of the Kubernetes `autoscaling` API group in use. This example manifest uses the beta version, so scaling by CPU and memory is enabled. | - `name: hello-world` | Indicates that HPA is performing autoscaling for the `hello-word` deployment. | - `minReplicas: 1` | Indicates that the minimum number of replicas running can't go below 1. | - `maxReplicas: 10` | Indicates the maximum number of replicas in the deployment can't go above 10. - `targetAverageUtilization: 50` | Indicates the deployment will scale pods up when the average running pod uses more than 50% of its requested CPU. - `targetAverageValue: 100Mi` | Indicates the deployment will scale pods up when the average running pod uses more that 100Mi of memory. -
- -##### Configuring HPA to Scale Using Resource Metrics (CPU and Memory) - -Clusters created in Rancher v2.0.7 and higher have all the requirements needed (metrics-server and Kubernetes cluster configuration) to use Horizontal Pod Autoscaler. - -Run the following commands to check if metrics are available in your installation: - -``` -$ kubectl top nodes -NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% -node-controlplane 196m 9% 1623Mi 42% -node-etcd 80m 4% 1090Mi 28% -node-worker 64m 3% 1146Mi 29% -$ kubectl -n kube-system top pods -NAME CPU(cores) MEMORY(bytes) -canal-pgldr 18m 46Mi -canal-vhkgr 20m 45Mi -canal-x5q5v 17m 37Mi -canal-xknnz 20m 37Mi -kube-dns-7588d5b5f5-298j2 0m 22Mi -kube-dns-autoscaler-5db9bbb766-t24hw 0m 5Mi -metrics-server-97bc649d5-jxrlt 0m 12Mi -$ kubectl -n kube-system logs -l k8s-app=metrics-server -I1002 12:55:32.172841 1 heapster.go:71] /metrics-server --source=kubernetes.summary_api:https://kubernetes.default.svc?kubeletHttps=true&kubeletPort=10250&useServiceAccount=true&insecure=true -I1002 12:55:32.172994 1 heapster.go:72] Metrics Server version v0.2.1 -I1002 12:55:32.173378 1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default.svc" and version -I1002 12:55:32.173401 1 configs.go:62] Using kubelet port 10250 -I1002 12:55:32.173946 1 heapster.go:128] Starting with Metric Sink -I1002 12:55:32.592703 1 serving.go:308] Generated self-signed cert (apiserver.local.config/certificates/apiserver.crt, apiserver.local.config/certificates/apiserver.key) -I1002 12:55:32.925630 1 heapster.go:101] Starting Heapster API server... -[restful] 2018/10/02 12:55:32 log.go:33: [restful/swagger] listing is available at https:///swaggerapi -[restful] 2018/10/02 12:55:32 log.go:33: [restful/swagger] https:///swaggerui/ is mapped to folder /swagger-ui/ -I1002 12:55:32.928597 1 serve.go:85] Serving securely on 0.0.0.0:443 -``` - - -##### Configuring HPA to Scale Using Custom Metrics with Prometheus - -You can configure HPA to autoscale based on custom metrics provided by third-party software. The most common use case for autoscaling using third-party software is based on application-level metrics (i.e., HTTP requests per second). HPA uses the `custom.metrics.k8s.io` API to consume these metrics. This API is enabled by deploying a custom metrics adapter for the metrics collection solution. - -For this example, we are going to use [Prometheus](https://prometheus.io/). We are beginning with the following assumptions: - -- Prometheus is deployed in the cluster. -- Prometheus is configured correctly and collecting proper metrics from pods, nodes, namespaces, etc. -- Prometheus is exposed at the following URL and port: `http://prometheus.mycompany.io:80` - -Prometheus is available for deployment in the Rancher v2.0 catalog. Deploy it from Rancher catalog if it isn't already running in your cluster. - -For HPA to use custom metrics from Prometheus, package [k8s-prometheus-adapter](https://github.com/DirectXMan12/k8s-prometheus-adapter) is required in the `kube-system` namespace of your cluster. To install `k8s-prometheus-adapter`, we are using the Helm chart available at [banzai-charts](https://github.com/banzaicloud/banzai-charts). - -1. Initialize Helm in your cluster. - ``` - # kubectl -n kube-system create serviceaccount tiller - kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller - helm init --service-account tiller - ``` - -1. Clone the `banzai-charts` repo from GitHub: - ``` - # git clone https://github.com/banzaicloud/banzai-charts - ``` - -1. Install the `prometheus-adapter` chart, specifying the Prometheus URL and port number. - ``` - # helm install --name prometheus-adapter banzai-charts/prometheus-adapter --set prometheus.url="http://prometheus.mycompany.io",prometheus.port="80" --namespace kube-system - ``` - -1. Check that `prometheus-adapter` is running properly. Check the service pod and logs in the `kube-system` namespace. - - 1. Check that the service pod is `Running`. Enter the following command. - ``` - # kubectl get pods -n kube-system - ``` - From the resulting output, look for a status of `Running`. - ``` - NAME READY STATUS RESTARTS AGE - ... - prometheus-adapter-prometheus-adapter-568674d97f-hbzfx 1/1 Running 0 7h - ... - ``` - 1. Check the service logs to make sure the service is running correctly by entering the command that follows. - ``` - # kubectl logs prometheus-adapter-prometheus-adapter-568674d97f-hbzfx -n kube-system - ``` - Then review the log output to confirm the service is running. - -
- Prometheus Adaptor Logs - - ... - I0724 10:18:45.696679 1 round_trippers.go:436] GET https://10.43.0.1:443/api/v1/namespaces/default/pods?labelSelector=app%3Dhello-world 200 OK in 2 milliseconds - I0724 10:18:45.696695 1 round_trippers.go:442] Response Headers: - I0724 10:18:45.696699 1 round_trippers.go:445] Date: Tue, 24 Jul 2018 10:18:45 GMT - I0724 10:18:45.696703 1 round_trippers.go:445] Content-Type: application/json - I0724 10:18:45.696706 1 round_trippers.go:445] Content-Length: 2581 - I0724 10:18:45.696766 1 request.go:836] Response Body: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/default/pods","resourceVersion":"6237"},"items":[{"metadata":{"name":"hello-world-54764dfbf8-q6l82","generateName":"hello-world-54764dfbf8-","namespace":"default","selfLink":"/api/v1/namespaces/default/pods/hello-world-54764dfbf8-q6l82","uid":"484cb929-8f29-11e8-99d2-067cac34e79c","resourceVersion":"4066","creationTimestamp":"2018-07-24T10:06:50Z","labels":{"app":"hello-world","pod-template-hash":"1032089694"},"annotations":{"cni.projectcalico.org/podIP":"10.42.0.7/32"},"ownerReferences":[{"apiVersion":"extensions/v1beta1","kind":"ReplicaSet","name":"hello-world-54764dfbf8","uid":"4849b9b1-8f29-11e8-99d2-067cac34e79c","controller":true,"blockOwnerDeletion":true}]},"spec":{"volumes":[{"name":"default-token-ncvts","secret":{"secretName":"default-token-ncvts","defaultMode":420}}],"containers":[{"name":"hello-world","image":"rancher/hello-world","ports":[{"containerPort":80,"protocol":"TCP"}],"resources":{"requests":{"cpu":"500m","memory":"64Mi"}},"volumeMounts":[{"name":"default-token-ncvts","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"34.220.18.140","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}]},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-07-24T10:06:50Z"},{"type":"Ready","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-07-24T10:06:54Z"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-07-24T10:06:50Z"}],"hostIP":"34.220.18.140","podIP":"10.42.0.7","startTime":"2018-07-24T10:06:50Z","containerStatuses":[{"name":"hello-world","state":{"running":{"startedAt":"2018-07-24T10:06:54Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"rancher/hello-world:latest","imageID":"docker-pullable://rancher/hello-world@sha256:4b1559cb4b57ca36fa2b313a3c7dde774801aa3a2047930d94e11a45168bc053","containerID":"docker://cce4df5fc0408f03d4adf82c90de222f64c302bf7a04be1c82d584ec31530773"}],"qosClass":"Burstable"}}]} - I0724 10:18:45.699525 1 api.go:74] GET http://prometheus-server.prometheus.34.220.18.140.xip.io/api/v1/query?query=sum%28rate%28container_fs_read_seconds_total%7Bpod_name%3D%22hello-world-54764dfbf8-q6l82%22%2Ccontainer_name%21%3D%22POD%22%2Cnamespace%3D%22default%22%7D%5B5m%5D%29%29+by+%28pod_name%29&time=1532427525.697 200 OK - I0724 10:18:45.699620 1 api.go:93] Response Body: {"status":"success","data":{"resultType":"vector","result":[{"metric":{"pod_name":"hello-world-54764dfbf8-q6l82"},"value":[1532427525.697,"0"]}]}} - I0724 10:18:45.699939 1 wrap.go:42] GET /apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods/%2A/fs_read?labelSelector=app%3Dhello-world: (12.431262ms) 200 [[kube-controller-manager/v1.10.1 (linux/amd64) kubernetes/d4ab475/system:serviceaccount:kube-system:horizontal-pod-autoscaler] 10.42.0.0:24268] - I0724 10:18:51.727845 1 request.go:836] Request Body: {"kind":"SubjectAccessReview","apiVersion":"authorization.k8s.io/v1beta1","metadata":{"creationTimestamp":null},"spec":{"nonResourceAttributes":{"path":"/","verb":"get"},"user":"system:anonymous","group":["system:unauthenticated"]},"status":{"allowed":false}} - ... - -
- - - -1. Check that the metrics API is accessible from kubectl. - - - If you are accessing the cluster directly, enter your Server URL in the kubectl config in the following format: `https://:6443`. - ``` - # kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1 - ``` - If the API is accessible, you should receive output that's similar to what follows. - -
- API Response - - {"kind":"APIResourceList","apiVersion":"v1","groupVersion":"custom.metrics.k8s.io/v1beta1","resources":[{"name":"pods/fs_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_rss","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_period","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_throttled","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_time","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_read","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_sector_writes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_user","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/last_seen","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/tasks_state","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_quota","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/start_time_seconds","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_write","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_cache","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_periods","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_throttled_periods","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads_merged","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_working_set_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/network_udp_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_inodes_free","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_inodes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_time_weighted","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_failures","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_swap","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_shares","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_swap_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_current","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_failcnt","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes_merged","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/network_tcp_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_max_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_reservation_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_load_average_10s","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_system","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_sector_reads","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]}]} - -
- - - If you are accessing the cluster through Rancher, enter your Server URL in the kubectl config in the following format: `https:///k8s/clusters/`. Add the suffix `/k8s/clusters/` to API path. - ``` - # kubectl get --raw /k8s/clusters//apis/custom.metrics.k8s.io/v1beta1 - ``` - If the API is accessible, you should receive output that's similar to what follows. - -
- API Response - - {"kind":"APIResourceList","apiVersion":"v1","groupVersion":"custom.metrics.k8s.io/v1beta1","resources":[{"name":"pods/fs_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_rss","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_period","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_throttled","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_time","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_read","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_sector_writes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_user","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/last_seen","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/tasks_state","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_quota","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/start_time_seconds","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_write","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_cache","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_periods","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_throttled_periods","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads_merged","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_working_set_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/network_udp_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_inodes_free","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_inodes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_time_weighted","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_failures","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_swap","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_shares","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_swap_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_current","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_failcnt","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes_merged","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/network_tcp_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_max_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_reservation_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_load_average_10s","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_system","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_sector_reads","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]}]} - -
diff --git a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/manage-hpa-with-rancher-ui.md b/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/manage-hpa-with-rancher-ui.md deleted file mode 100644 index 15514596211..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/manage-hpa-with-rancher-ui.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Managing HPAs with the Rancher UI -weight: 3028 ---- - -The Rancher UI supports creating, managing, and deleting HPAs. You can configure CPU or memory usage as the metric that the HPA uses to scale. - -If you want to create HPAs that scale based on other metrics than CPU and memory, refer to [Configuring HPA to Scale Using Custom Metrics with Prometheus]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/#configuring-hpa-to-scale-using-custom-metrics-with-prometheus). - -## Creating an HPA - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster you want to create an HPA in and click **Explore**. -1. In the left navigation bar, click **Service Discovery > HorizontalPodAutoscalers**. -1. Click **Create**. -1. Select a **Namespace** for the HPA. -1. Enter a **Name** for the HPA. -1. Select a **Target Reference** as scale target for the HPA. -1. Specify the **Minimum Replicas** and **Maximum Replicas** for the HPA. -1. Configure the metrics for the HPA. You can choose memory or CPU usage as the metric that will cause the HPA to scale the service up or down. In the **Quantity** field, enter the percentage of the workload's memory or CPU usage that will cause the HPA to scale the service. To configure other HPA metrics, including metrics available from Prometheus, you need to [manage HPAs using kubectl]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/#configuring-hpa-to-scale-using-custom-metrics-with-prometheus). - -1. Click **Create** to create the HPA. - -> **Result:** The HPA is deployed to the chosen namespace. You can view the HPA's status from the project's Resources > HPA view. - -## Get HPA Metrics and Status - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that has the HPA and click **Explore**. -1. In the left navigation bar, click **Service Discovery > HorizontalPodAutoscalers**. The **HorizontalPodAutoscalers** page shows the number of current replicas. - -For more detailed metrics and status of a specific HPA, click the name of the HPA. This leads to the HPA detail page. - - -## Deleting an HPA - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that has the HPA you want to delete and click **Explore**. -1. In the left navigation bar, click **Service Discovery > HorizontalPodAutoscalers**. -1. Click **Resources > HPA**. -1. Find the HPA which you would like to delete and click **⋮ > Delete**. -1. Click **Delete** to confirm. - -> **Result:** The HPA is deleted from the current cluster. diff --git a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/testing-hpa.md b/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/testing-hpa.md deleted file mode 100644 index d4990e8516b..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/testing-hpa.md +++ /dev/null @@ -1,531 +0,0 @@ ---- -title: Testing HPAs with kubectl -weight: 3031 ---- - -This document describes how to check the status of your HPAs after scaling them up or down with your load testing tool. For information on how to check the status from the Rancher UI (at least version 2.3.x), refer to [Managing HPAs with the Rancher UI]({{}}/rancher/v2.6/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/). - -For HPA to work correctly, service deployments should have resources request definitions for containers. Follow this hello-world example to test if HPA is working correctly. - -1. Configure `kubectl` to connect to your Kubernetes cluster. - -1. Copy the `hello-world` deployment manifest below. - -
- Hello World Manifest - - ``` - apiVersion: apps/v1beta2 - kind: Deployment - metadata: - labels: - app: hello-world - name: hello-world - namespace: default - spec: - replicas: 1 - selector: - matchLabels: - app: hello-world - strategy: - rollingUpdate: - maxSurge: 1 - maxUnavailable: 0 - type: RollingUpdate - template: - metadata: - labels: - app: hello-world - spec: - containers: - - image: rancher/hello-world - imagePullPolicy: Always - name: hello-world - resources: - requests: - cpu: 500m - memory: 64Mi - ports: - - containerPort: 80 - protocol: TCP - restartPolicy: Always - --- - apiVersion: v1 - kind: Service - metadata: - name: hello-world - namespace: default - spec: - ports: - - port: 80 - protocol: TCP - targetPort: 80 - selector: - app: hello-world - ``` - -
- -1. Deploy it to your cluster. - - ``` - # kubectl create -f - ``` - -1. Copy one of the HPAs below based on the metric type you're using: - -
- Hello World HPA: Resource Metrics - - ``` - apiVersion: autoscaling/v2beta1 - kind: HorizontalPodAutoscaler - metadata: - name: hello-world - namespace: default - spec: - scaleTargetRef: - apiVersion: extensions/v1beta1 - kind: Deployment - name: hello-world - minReplicas: 1 - maxReplicas: 10 - metrics: - - type: Resource - resource: - name: cpu - targetAverageUtilization: 50 - - type: Resource - resource: - name: memory - targetAverageValue: 1000Mi - ``` - -
-
- Hello World HPA: Custom Metrics - - ``` - apiVersion: autoscaling/v2beta1 - kind: HorizontalPodAutoscaler - metadata: - name: hello-world - namespace: default - spec: - scaleTargetRef: - apiVersion: extensions/v1beta1 - kind: Deployment - name: hello-world - minReplicas: 1 - maxReplicas: 10 - metrics: - - type: Resource - resource: - name: cpu - targetAverageUtilization: 50 - - type: Resource - resource: - name: memory - targetAverageValue: 100Mi - - type: Pods - pods: - metricName: cpu_system - targetAverageValue: 20m - ``` - -
- -1. View the HPA info and description. Confirm that metric data is shown. - -
- Resource Metrics - - 1. Enter the following commands. - ``` - # kubectl get hpa - NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE - hello-world Deployment/hello-world 1253376 / 100Mi, 0% / 50% 1 10 1 6m - # kubectl describe hpa - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Mon, 23 Jul 2018 20:21:16 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 1253376 / 100Mi - resource cpu on pods (as a percentage of request): 0% (0) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True ReadyForNewScale the last scale time was sufficiently old as to warrant a new scale - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from memory resource - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - ``` - -
-
- Custom Metrics - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive the output that follows. - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Tue, 24 Jul 2018 18:36:28 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 3514368 / 100Mi - "cpu_system" on pods: 0 / 20m - resource cpu on pods (as a percentage of request): 0% (0) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True ReadyForNewScale the last scale time was sufficiently old as to warrant a new scale - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from memory resource - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - ``` - -
- -1. Generate a load for the service to test that your pods autoscale as intended. You can use any load-testing tool (Hey, Gatling, etc.), but we're using [Hey](https://github.com/rakyll/hey). - -1. Test that pod autoscaling works as intended.

- **To Test Autoscaling Using Resource Metrics:** - -
- Upscale to 2 Pods: CPU Usage Up to Target - - Use your load testing tool to scale up to two pods based on CPU Usage. - - 1. View your HPA. - ``` - # kubectl describe hpa - ``` - You should receive output similar to what follows. - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Mon, 23 Jul 2018 22:22:04 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 10928128 / 100Mi - resource cpu on pods (as a percentage of request): 56% (280m) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 2 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request) - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 13s horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - ``` - 1. Enter the following command to confirm you've scaled to two pods. - ``` - # kubectl get pods - ``` - You should receive output similar to what follows: - ``` - NAME READY STATUS RESTARTS AGE - hello-world-54764dfbf8-k8ph2 1/1 Running 0 1m - hello-world-54764dfbf8-q6l4v 1/1 Running 0 3h - ``` - -
-
- Upscale to 3 pods: CPU Usage Up to Target - - Use your load testing tool to upscale to 3 pods based on CPU usage with `horizontal-pod-autoscaler-upscale-delay` set to 3 minutes. - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive output similar to what follows - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Mon, 23 Jul 2018 22:22:04 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 9424896 / 100Mi - resource cpu on pods (as a percentage of request): 66% (333m) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 3 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request) - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 4m horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 16s horizontal-pod-autoscaler New size: 3; reason: cpu resource utilization (percentage of request) above target - ``` - 2. Enter the following command to confirm three pods are running. - ``` - # kubectl get pods - ``` - You should receive output similar to what follows. - ``` - NAME READY STATUS RESTARTS AGE - hello-world-54764dfbf8-f46kh 0/1 Running 0 1m - hello-world-54764dfbf8-k8ph2 1/1 Running 0 5m - hello-world-54764dfbf8-q6l4v 1/1 Running 0 3h - ``` - -
-
- Downscale to 1 Pod: All Metrics Below Target - - Use your load testing to scale down to 1 pod when all metrics are below target for `horizontal-pod-autoscaler-downscale-delay` (5 minutes by default). - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive output similar to what follows. - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Mon, 23 Jul 2018 22:22:04 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 10070016 / 100Mi - resource cpu on pods (as a percentage of request): 0% (0) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 1 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from memory resource - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 10m horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 6m horizontal-pod-autoscaler New size: 3; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 1s horizontal-pod-autoscaler New size: 1; reason: All metrics below target - ``` - -
- - **To Test Autoscaling Using Custom Metrics:** - -
- Upscale to 2 Pods: CPU Usage Up to Target - - Use your load testing tool to upscale two pods based on CPU usage. - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive output similar to what follows. - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Tue, 24 Jul 2018 18:01:11 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 8159232 / 100Mi - "cpu_system" on pods: 7m / 20m - resource cpu on pods (as a percentage of request): 64% (321m) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 2 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request) - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 16s horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - ``` - 1. Enter the following command to confirm two pods are running. - ``` - # kubectl get pods - ``` - You should receive output similar to what follows. - ``` - NAME READY STATUS RESTARTS AGE - hello-world-54764dfbf8-5pfdr 1/1 Running 0 3s - hello-world-54764dfbf8-q6l82 1/1 Running 0 6h - ``` - -
-
- Upscale to 3 Pods: CPU Usage Up to Target - - Use your load testing tool to scale up to three pods when the cpu_system usage limit is up to target. - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive output similar to what follows: - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Tue, 24 Jul 2018 18:01:11 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 8374272 / 100Mi - "cpu_system" on pods: 27m / 20m - resource cpu on pods (as a percentage of request): 71% (357m) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 3 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request) - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 3m horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 3s horizontal-pod-autoscaler New size: 3; reason: pods metric cpu_system above target - ``` - 1. Enter the following command to confirm three pods are running. - ``` - # kubectl get pods - ``` - You should receive output similar to what follows: - ``` - # kubectl get pods - NAME READY STATUS RESTARTS AGE - hello-world-54764dfbf8-5pfdr 1/1 Running 0 3m - hello-world-54764dfbf8-m2hrl 1/1 Running 0 1s - hello-world-54764dfbf8-q6l82 1/1 Running 0 6h - ``` - -
-
- Upscale to 4 Pods: CPU Usage Up to Target - - Use your load testing tool to upscale to four pods based on CPU usage. `horizontal-pod-autoscaler-upscale-delay` is set to three minutes by default. - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive output similar to what follows. - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Tue, 24 Jul 2018 18:01:11 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 8374272 / 100Mi - "cpu_system" on pods: 27m / 20m - resource cpu on pods (as a percentage of request): 71% (357m) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 3 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from cpu resource utilization (percentage of request) - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 5m horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 3m horizontal-pod-autoscaler New size: 3; reason: pods metric cpu_system above target - Normal SuccessfulRescale 4s horizontal-pod-autoscaler New size: 4; reason: cpu resource utilization (percentage of request) above target - ``` - 1. Enter the following command to confirm four pods are running. - ``` - # kubectl get pods - ``` - You should receive output similar to what follows. - ``` - NAME READY STATUS RESTARTS AGE - hello-world-54764dfbf8-2p9xb 1/1 Running 0 5m - hello-world-54764dfbf8-5pfdr 1/1 Running 0 2m - hello-world-54764dfbf8-m2hrl 1/1 Running 0 1s - hello-world-54764dfbf8-q6l82 1/1 Running 0 6h - ``` - -
-
- Downscale to 1 Pod: All Metrics Below Target - - Use your load testing tool to scale down to one pod when all metrics below target for `horizontal-pod-autoscaler-downscale-delay`. - - 1. Enter the following command. - ``` - # kubectl describe hpa - ``` - You should receive similar output to what follows. - ``` - Name: hello-world - Namespace: default - Labels: - Annotations: - CreationTimestamp: Tue, 24 Jul 2018 18:01:11 +0200 - Reference: Deployment/hello-world - Metrics: ( current / target ) - resource memory on pods: 8101888 / 100Mi - "cpu_system" on pods: 8m / 20m - resource cpu on pods (as a percentage of request): 0% (0) / 50% - Min replicas: 1 - Max replicas: 10 - Conditions: - Type Status Reason Message - ---- ------ ------ ------- - AbleToScale True SucceededRescale the HPA controller was able to update the target scale to 1 - ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from memory resource - ScalingLimited False DesiredWithinRange the desired count is within the acceptable range - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal SuccessfulRescale 10m horizontal-pod-autoscaler New size: 2; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 8m horizontal-pod-autoscaler New size: 3; reason: pods metric cpu_system above target - Normal SuccessfulRescale 5m horizontal-pod-autoscaler New size: 4; reason: cpu resource utilization (percentage of request) above target - Normal SuccessfulRescale 13s horizontal-pod-autoscaler New size: 1; reason: All metrics below target - ``` - 1. Enter the following command to confirm a single pods is running. - ``` - # kubectl get pods - ``` - You should receive output similar to what follows. - ``` - NAME READY STATUS RESTARTS AGE - hello-world-54764dfbf8-q6l82 1/1 Running 0 6h - ``` - -
diff --git a/versioned_docs/version-2.6/k8s-in-rancher/k8s-in-rancher.md b/versioned_docs/version-2.6/k8s-in-rancher/k8s-in-rancher.md deleted file mode 100644 index 0864b408ef3..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/k8s-in-rancher.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Kubernetes Resources -weight: 18 ---- - -You can view and manipulate all of the custom resources and CRDs in a Kubernetes cluster from the Rancher UI. - -## Workloads - -Deploy applications to your cluster nodes using [workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/), which are objects that contain pods that run your apps, along with metadata that set rules for the deployment's behavior. Workloads can be deployed within the scope of the entire clusters or within a namespace. - -When deploying a workload, you can deploy from any image. There are a variety of [workload types]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/#workload-types) to choose from which determine how your application should run. - -Following a workload deployment, you can continue working with it. You can: - -- [Upgrade]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/upgrade-workloads) the workload to a newer version of the application it's running. -- [Roll back]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/rollback-workloads) a workload to a previous version, if an issue occurs during upgrade. -- [Add a sidecar]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/add-a-sidecar), which is a workload that supports a primary workload. - -## Load Balancing and Ingress - -### Load Balancers - -After you launch an application, it's only available within the cluster. It can't be reached externally. - -If you want your applications to be externally accessible, you must add a load balancer to your cluster. Load balancers create a gateway for external connections to access your cluster, provided that the user knows the load balancer's IP address and the application's port number. - -Rancher supports two types of load balancers: - -- [Layer-4 Load Balancers]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/#layer-4-load-balancer) -- [Layer-7 Load Balancers]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/#layer-7-load-balancer) - -For more information, see [load balancers]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers). - -#### Ingress - -Load Balancers can only handle one IP address per service, which means if you run multiple services in your cluster, you must have a load balancer for each service. Running multiples load balancers can be expensive. You can get around this issue by using an ingress. - -Ingress is a set of rules that act as a load balancer. Ingress works in conjunction with one or more ingress controllers to dynamically route service requests. When the ingress receives a request, the ingress controller(s) in your cluster program the load balancer to direct the request to the correct service based on service subdomains or path rules that you've configured. - -For more information, see [Ingress]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/ingress). - -When using ingresses in a project, you can program the ingress hostname to an external DNS by setting up a Global DNS entry. - -## Service Discovery - -After you expose your cluster to external requests using a load balancer and/or ingress, it's only available by IP address. To create a resolveable hostname, you must create a service record, which is a record that maps an IP address, external hostname, DNS record alias, workload(s), or labelled pods to a specific hostname. - -For more information, see [Service Discovery]({{}}/rancher/v2.6/en/k8s-in-rancher/service-discovery). - -## Pipelines - -After your project has been [configured to a version control provider]({{}}/rancher/v2.6/en/project-admin/pipelines/#1-configure-version-control-providers), you can add the repositories and start configuring a pipeline for each repository. - -For more information, see [Pipelines]({{}}/rancher/v2.6/en/pipelines/). - -## Applications - -Besides launching individual components of an application, you can use the Rancher catalog to start launching applications, which are Helm charts. - -## Kubernetes Resources - -Within the context of a Rancher project or namespace, _resources_ are files and data that support operation of your pods. Within Rancher, certificates, registries, and secrets are all considered resources. However, Kubernetes classifies resources as different types of [secrets](https://kubernetes.io/docs/concepts/configuration/secret/). Therefore, within a single project or namespace, individual resources must have unique names to avoid conflicts. Although resources are primarily used to carry sensitive information, they have other uses as well. - -Resources include: - -- [Certificates]({{}}/rancher/v2.6/en/k8s-in-rancher/certificates/): Files used to encrypt/decrypt data entering or leaving the cluster. -- [ConfigMaps]({{}}/rancher/v2.6/en/k8s-in-rancher/configmaps/): Files that store general configuration information, such as a group of config files. -- [Secrets]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/): Files that store sensitive data like passwords, tokens, or keys. -- [Registries]({{}}/rancher/v2.6/en/k8s-in-rancher/registries/): Files that carry credentials used to authenticate with private registries. diff --git a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress-config/ingress-config.md b/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress-config/ingress-config.md deleted file mode 100644 index 7b5f1f48f13..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress-config/ingress-config.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Ingress Configuration -description: Ingress configuration -weight: 9999 ---- - -- [NGINX Ingress controller changes in Kubernetes v1.21](#nginx-ingress-controller-changes-in-Kubernetes-v1-21) -- [Automatically generate a xip.io hostname](#automatically-generate-a-xip-io-hostname) -- [Specify a hostname to use](#specify-a-hostname-to-use) -- [Use as the default backend](#use-as-the-default-backend) -- [Certificates](#certificates) -- [Labels and Annotations](#labels-and-annotations) - -### NGINX Ingress controller changes in Kubernetes v1.21 - -For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in hostNetwork but uses hostPorts for port 80 and port 443. This was done so the admission webhook can be configured to be accessed using ClusterIP so it can only be reached inside the cluster. - -# Ingress Rule Configuration - -- [Specify a hostname to use](#specify-a-hostname-to-use) -- [Use as the default backend](#use-as-the-default-backend) -- [Certificates](#certificates) -- [Labels and Annotations](#labels-and-annotations) - -### Specify a hostname to use - -If you use this option, ingress routes requests for a hostname to the service or workload that you specify. - -1. Enter the **Request Host** that your ingress will handle request forwarding for. For example, `www.mysite.com`. -1. Add a **Target Service**. -1. **Optional:** If you want specify a workload or service when a request is sent to a particular hostname path, add a **Path** for the target. For example, if you want requests for `www.mysite.com/contact-us` to be sent to a different service than `www.mysite.com`, enter `/contact-us` in the **Path** field. Typically, the first rule that you create does not include a path. -1. Enter the **Port** number that each target operates on. -### Certificates ->**Note:** You must have an SSL certificate that the ingress can use to encrypt/decrypt communications. For more information see [Adding SSL Certificates]({{}}/rancher/v2.6/en/k8s-in-rancher/certificates/). - -1. When creating an ingress, click the **Certificates** tab. -1. Click **Add Certificate**. -1. Select a **Certificate - Secret Name** from the drop-down list. -1. Enter the host using encrypted communication. -1. To add additional hosts that use the certificate, click **Add Hosts**. - -### Labels and Annotations - -Add [Labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) and/or [Annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) to provide metadata for your ingress. - -For a list of annotations available for use, see the [Nginx Ingress Controller Documentation](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/). diff --git a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress/ingress.md b/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress/ingress.md deleted file mode 100644 index bb69c198262..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/ingress/ingress.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Adding Ingresses -description: Ingresses can be added for workloads to provide load balancing, SSL termination and host/path-based routing. Learn how to add Rancher ingress -weight: 3042 ---- - -Ingresses can be added for workloads to provide load balancing, SSL termination and host/path based routing. When using ingresses in a project, you can program the ingress hostname to an external DNS by setting up a Global DNS entry. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster that you want to add an ingress to and click **Explore**. -1. Click **Service Discovery > Ingresses**. -1. Click **Create**. -1. Select an existing **Namespace** from the drop-down list. -1. Enter a **Name** for the ingress. -1. Create ingress forwarding **Rules**. For help configuring the rules, refer to [this section.](#ingress-rule-configuration) If any of your ingress rules handle requests for encrypted ports, add a certificate to encrypt/decrypt communications. -1. **Optional:** click **Add Rule** to create additional ingress rules. For example, after you create ingress rules to direct requests for your hostname, you'll likely want to create a default backend to handle 404s. -1. Click **Create** at the bottom right. - -**Result:** Your ingress is added to the project. The ingress begins enforcing your ingress rules. - diff --git a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers-and-ingress.md b/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers-and-ingress.md deleted file mode 100644 index 420411de1b7..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers-and-ingress.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Set Up Load Balancer and Ingress Controller within Rancher -description: Learn how you can set up load balancers and ingress controllers to redirect service requests within Rancher, and learn about the limitations of load balancers -weight: 3040 ---- - -Within Rancher, you can set up load balancers and ingress controllers to redirect service requests. - -## Load Balancers - -After you launch an application, the app is only available within the cluster. It can't be reached from outside the cluster. - -If you want your applications to be externally accessible, you must add a load balancer or ingress to your cluster. Load balancers create a gateway for external connections to access your cluster, provided that the user knows the load balancer's IP address and the application's port number. - -Rancher supports two types of load balancers: - -- [Layer-4 Load Balancers]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/#layer-4-load-balancer) -- [Layer-7 Load Balancers]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/#layer-7-load-balancer) - -For more information, see [load balancers]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers). - -### Load Balancer Limitations - -Load Balancers have a couple of limitations you should be aware of: - -- Load Balancers can only handle one IP address per service, which means if you run multiple services in your cluster, you must have a load balancer for each service. Running multiples load balancers can be expensive. - -- If you want to use a load balancer with a Hosted Kubernetes cluster (i.e., clusters hosted in GKE, EKS, or AKS), the load balancer must be running within that cloud provider's infrastructure. Please review the compatibility tables regarding support for load balancers based on how you've provisioned your clusters: - - - - [Support for Layer-4 Load Balancing]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/#support-for-layer-4-load-balancing) - - - [Support for Layer-7 Load Balancing]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/#support-for-layer-7-load-balancing) - -## Ingress - -As mentioned in the limitations above, the disadvantages of using a load balancer are: - -- Load Balancers can only handle one IP address per service. -- If you run multiple services in your cluster, you must have a load balancer for each service. -- It can be expensive to have a load balancer for every service. - -In contrast, when an ingress is used as the entrypoint into a cluster, the ingress can route traffic to multiple services with greater flexibility. It can map multiple HTTP requests to services without individual IP addresses for each service. - -Therefore, it is useful to have an ingress if you want multiple services to be exposed with the same IP address, the same Layer 7 protocol, or the same privileged node-ports: 80 and 443. - -Ingress works in conjunction with one or more ingress controllers to dynamically route service requests. When the ingress receives a request, the ingress controller(s) in your cluster direct the request to the correct service based on service subdomains or path rules that you've configured. - -Each Kubernetes Ingress resource corresponds roughly to a file in `/etc/nginx/sites-available/` containing a `server{}` configuration block, where requests for specific files and folders are configured. - -Your ingress, which creates a port of entry to your cluster similar to a load balancer, can reside within your cluster or externally. Ingress and ingress controllers residing in RKE-launched clusters are powered by [Nginx](https://www.nginx.com/). - -Ingress can provide other functionality as well, such as SSL termination, name-based virtual hosting, and more. - ->**Using Rancher in a High Availability Configuration?** -> ->Refrain from adding an Ingress to the `local` cluster. The Nginx Ingress Controller that Rancher uses acts as a global entry point for _all_ clusters managed by Rancher, including the `local` cluster. Therefore, when users try to access an application, your Rancher connection may drop due to the Nginx configuration being reloaded. We recommend working around this issue by deploying applications only in clusters that you launch using Rancher. - -- For more information on how to set up ingress in Rancher, see [Ingress]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/ingress). -- For complete information about ingress and ingress controllers, see the [Kubernetes Ingress Documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/) -- When using ingresses in a project, you can program the ingress hostname to an external DNS by setting up a Global DNS entry. diff --git a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md b/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md deleted file mode 100644 index 0e594f7efd9..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: "Layer 4 and Layer 7 Load Balancing" -description: "Kubernetes supports load balancing in two ways: Layer-4 Load Balancing and Layer-7 Load Balancing. Learn about the support for each way in different deployments" -weight: 3041 ---- -Kubernetes supports load balancing in two ways: Layer-4 Load Balancing and Layer-7 Load Balancing. - -## Layer-4 Load Balancer - -Layer-4 load balancer (or the external load balancer) forwards traffic to Nodeports. Layer-4 load balancer allows you to forward both HTTP and TCP traffic. - -Often, the Layer-4 load balancer is supported by the underlying cloud provider, so when you deploy RKE clusters on bare-metal servers and vSphere clusters, Layer-4 load balancer is not supported. However, a single [globally managed config-map](https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/) can be used to expose services on NGINX or third-party ingress. - -> **Note:** It is possible to deploy a cluster with a non-cloud load balancer, such as [MetalLB.](https://metallb.universe.tf/) However, that use case is more advanced than the Layer-4 load balancer supported by a cloud provider, and it is not configurable in Rancher or RKE. - -### Support for Layer-4 Load Balancing - -Support for layer-4 load balancer varies based on the underlying cloud provider. - -Cluster Deployment | Layer-4 Load Balancer Support -----------------------------------------------|-------------------------------- -Amazon EKS | Supported by AWS cloud provider -Google GKE | Supported by GCE cloud provider -Azure AKS | Supported by Azure cloud provider -RKE on EC2 | Supported by AWS cloud provider -RKE on DigitalOcean | Limited NGINX or third-party Ingress* -RKE on vSphere | Limited NGINX or third party-Ingress* -RKE on Custom Hosts
(e.g. bare-metal servers) | Limited NGINX or third-party Ingress* -Third-party MetalLB | Limited NGINX or third-party Ingress* - -\* Services can be exposed through a single [globally managed config-map.](https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/) - -## Layer-7 Load Balancer - -Layer-7 load balancer (or the ingress controller) supports host and path-based load balancing and SSL termination. Layer-7 load balancer only forwards HTTP and HTTPS traffic and therefore they listen on ports 80 and 443 only. Cloud providers such as Amazon and Google support layer-7 load balancer. In addition, RKE clusters deploys the Nginx Ingress Controller. - -### Support for Layer-7 Load Balancing - -Support for layer-7 load balancer varies based on the underlying cloud provider. - -Cluster Deployment | Layer-7 Load Balancer Support -----------------------------------------------|-------------------------------- -Amazon EKS | Supported by AWS cloud provider -Google GKE | Supported by GKE cloud provider -Azure AKS | Not Supported -RKE on EC2 | Nginx Ingress Controller -RKE on DigitalOcean | Nginx Ingress Controller -RKE on vSphere | Nginx Ingress Controller -RKE on Custom Hosts
(e.g. bare-metal servers) | Nginx Ingress Controller - -### Host Names in Layer-7 Load Balancer - -Some cloud-managed layer-7 load balancers (such as the ALB ingress controller on AWS) expose DNS addresses for ingress rules. You need to map (via CNAME) your domain name to the DNS address generated by the layer-7 load balancer. - -Other layer-7 load balancers, such as the Google Load Balancer or Nginx Ingress Controller, directly expose one or more IP addresses. Google Load Balancer provides a single routable IP address. Nginx Ingress Controller exposes the external IP of all nodes that run the Nginx Ingress Controller. You can do either of the following: - -1. Configure your own DNS to map (via A records) your domain name to the IP addresses exposes by the Layer-7 load balancer. -2. Ask Rancher to generate an xip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say `a.b.c.d`, and generate a host name `..a.b.c.d.xip.io`. - -The benefit of using xip.io is that you obtain a working entrypoint URL immediately after you create the ingress rule. Setting up your own domain name, on the other hand, requires you to configure DNS servers and wait for DNS to propagate. - -## Related Links - -- [Create an External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) diff --git a/versioned_docs/version-2.6/k8s-in-rancher/registries/registries.md b/versioned_docs/version-2.6/k8s-in-rancher/registries/registries.md deleted file mode 100644 index 0b075b620d0..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/registries/registries.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: Kubernetes Registry and Docker Registry -description: Learn about the Docker registry and Kubernetes registry, their use cases and how to use a private registry with the Rancher UI -weight: 3063 ---- -Registries are Kubernetes secrets containing credentials used to authenticate with [private Docker registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). - -The word "registry" can mean two things, depending on whether it is used to refer to a Docker or Kubernetes registry: - -- A **Docker registry** contains Docker images that you can pull in order to use them in your deployment. The registry is a stateless, scalable server side application that stores and lets you distribute Docker images. -- The **Kubernetes registry** is an image pull secret that your deployment uses to authenticate with a Docker registry. - -Deployments use the Kubernetes registry secret to authenticate with a private Docker registry and then pull a Docker image hosted on it. - -Currently, deployments pull the private registry credentials automatically only if the workload is created in the Rancher UI and not when it is created via kubectl. - -# Creating a Registry in Namespaces - ->**Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to add a registry and click **Explore**. -1. In the left navigation, click either **Storage > Secrets** or **More Resources > Core > Secrets**. -1. Click **Create**. -1. Click **Registry**. -1. Enter a **Name** for the registry. - - >**Note:** Kubernetes classifies secrets, certificates, and registries all as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your registry must have a unique name among all secrets within your workspace. - -1. Select a namespace for the registry. -1. Select the website that hosts your private registry. Then enter credentials that authenticate with the registry. For example, if you use DockerHub, provide your DockerHub username and password. -1. Click **Save**. - -**Result:** - -- Your secret is added to the namespace you chose. -- You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**. -- Any workload that you create in the Rancher UI will have the credentials to access the registry if the workload is within the registry's scope. - -# Creating a Registry in Projects - ->**Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use. - -Before v2.6, secrets were required to be in a project scope. Projects are no longer required, and you may use the namespace scope instead. As a result, the Rancher UI was updated to reflect this new functionality. However, you may still create a project-scoped registry if desired. Use the following steps to do so: - -1. In the upper left corner, click **☰ > Global Settings** in the dropdown. -1. Click **Feature Flags**. -1. Go to the `legacy` feature flag and click **Activate**. -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to add a registry and click **Explore**. -1. In the left navigation, click either **Storage > Secrets** or **More Resources > Core > Secrets**. -1. Click **Create**. -1. Click **Registry**. -1. In the top navigation bar, filter to see only one project. -1. Enter a **Name** for the registry. - - >**Note:** Kubernetes classifies secrets, certificates, and registries all as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your registry must have a unique name among all secrets within your workspace. - -1. Select a namespace for the registry. -1. Select the website that hosts your private registry. Then enter credentials that authenticate with the registry. For example, if you use DockerHub, provide your DockerHub username and password. -1. Click **Save**. - -**Result:** - -- Your secret is added to the individual project you chose. -- You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**. -- Any workload that you create in the Rancher UI will have the credentials to access the registry if the workload is within the registry's scope. - ->**Note:** Project-scoped registries on the local cluster are only visible when a single project is selected. - -# Using a Private Registry - -You can deploy a workload with an image from a private registry through the Rancher UI, or with `kubectl`. - -### Using the Private Registry with the Rancher UI - -To deploy a workload with an image from your private registry, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to deploy a workload and click **Explore**. -1. Click **Workload**. -1. Click **Create**. -1. Select the type of workload you want to create. -1. Enter a unique name for the workload and choose a namespace. -1. In the **Container Image** field, enter the URL of the path to the image in your private registry. For example, if your private registry is on Quay.io, you could use `quay.io//`. -1. Click **Create**. - -**Result:** Your deployment should launch, authenticate using the private registry credentials you added in the Rancher UI, and pull the Docker image that you specified. - -### Using the Private Registry with kubectl - -When you create the workload using `kubectl`, you need to configure the pod so that its YAML has the path to the image in the private registry. You also have to create and reference the registry secret because the pod only automatically gets access to the private registry credentials if it is created in the Rancher UI. - -The secret has to be created in the same namespace where the workload gets deployed. - -Below is an example `pod.yml` for a workload that uses an image from a private registry. In this example, the pod uses an image from Quay.io, and the .yml specifies the path to the image. The pod authenticates with the registry using credentials stored in a Kubernetes secret called `testquay`, which is specified in `spec.imagePullSecrets` in the `name` field: - -``` -apiVersion: v1 -kind: Pod -metadata: - name: private-reg -spec: - containers: - - name: private-reg-container - image: quay.io// - imagePullSecrets: - - name: testquay -``` - -In this example, the secret named `testquay` is in the default namespace. - -You can use `kubectl` to create the secret with the private registry credentials. This command creates the secret named `testquay`: - -``` -kubectl create secret docker-registry testquay \ - --docker-server=quay.io \ - --docker-username= \ - --docker-password= -``` - -To see how the secret is stored in Kubernetes, you can use this command: - -``` -kubectl get secret testquay --output="jsonpath={.data.\.dockerconfigjson}" | base64 --decode -``` - -The result looks like this: - -``` -{"auths":{"quay.io":{"username":"","password":"","auth":"c291bXlhbGo6dGVzdGFiYzEyMw=="}}} -``` - -After the workload is deployed, you can check if the image was pulled successfully: - -``` -kubectl get events -``` -The result should look like this: -``` -14s Normal Scheduled Pod Successfully assigned default/private-reg2 to minikube -11s Normal Pulling Pod pulling image "quay.io//" -10s Normal Pulled Pod Successfully pulled image "quay.io//" -``` - -For more information, refer to the Kubernetes documentation on [creating a pod that uses your secret.](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret) diff --git a/versioned_docs/version-2.6/k8s-in-rancher/secrets/secrets.md b/versioned_docs/version-2.6/k8s-in-rancher/secrets/secrets.md deleted file mode 100644 index 9c7f74220ea..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/secrets/secrets.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Secrets -weight: 3062 ---- - -[Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. - -> This page is about secrets in general. For details on setting up a private registry, refer to the section on [registries.]({{}}/rancher/v2.6/en/k8s-in-rancher/registries) - -When configuring a workload, you'll be able to choose which secrets to include. Like config maps, secrets can be referenced by workloads as either an environment variable or a volume mount. - -Mounted secrets will be updated automatically unless they are mounted as subpath volumes. For details on how updated secrets are propagated, refer to the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/configuration/secret/#mounted-secrets-are-updated-automatically) - -# Creating Secrets in Namespaces - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to add a secret and click **Explore**. -1. To navigate to secrets, you may click either **Storage > Secrets** or **More Resources > Core > Secrets**. -1. Click **Create**. -1. Select the type of secret you want to create. -1. Select a **Namespace** for the secret. -1. Enter a **Name** for the secret. - - >**Note:** Kubernetes classifies secrets, certificates, and registries all as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), and no two secrets in a namespace can have duplicate names. Therefore, to prevent conflicts, your secret must have a unique name among all secrets within your workspace. - -1. From **Data**, click **Add** to add a key-value pair. Add as many values as you need. - - >**Tip:** You can add multiple key value pairs to the secret by copying and pasting. - > - > {{< img "/img/rancher/bulk-key-values.gif" "Bulk Key Value Pair Copy/Paste">}} - -1. Click **Save**. - -**Result:** Your secret is added to the namespace you chose. You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**. - -Mounted secrets will be updated automatically unless they are mounted as subpath volumes. For details on how updated secrets are propagated, refer to the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/configuration/secret/#mounted-secrets-are-updated-automatically) - - -# Creating Secrets in Projects - -Before v2.6, secrets were required to be in a project scope. Projects are no longer required, and you may use the namespace scope instead. As a result, the Rancher UI was updated to reflect this new functionality. However, you may still create project-scoped secrets if desired. Note that you have to first enable the `legacy` feature flag and look at a single project to do so. Use the following steps to set up your project-level secret: - -1. In the upper left corner, click **☰ > Global Settings** in the dropdown. -1. Click **Feature Flags**. -1. Go to the `legacy` feature flag and click **Activate**. -1. In the upper left corner, click **☰ > Cluster Management** in the dropdown. -1. Go to the cluster that you created and click **Explore.** -1. Click **Legacy > Projects**. -1. In the top navigation bar, filter to see only one project. -1. In the left navigation bar, click **Secrets**. -1. Click **Add Secret**. - -**Result:** Your secret is added to the individual project you chose. You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**. - ->**Note:** Project-scoped secrets on the local cluster are only visible when a single project is selected. - -# What's Next? - -Now that you have a secret added to a namespace, you can add it to a workload that you deploy. - -For more information on adding secret to a workload, see [Deploying Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/deploy-workloads/). diff --git a/versioned_docs/version-2.6/k8s-in-rancher/service-discovery/service-discovery.md b/versioned_docs/version-2.6/k8s-in-rancher/service-discovery/service-discovery.md deleted file mode 100644 index 106bce3715d..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/service-discovery/service-discovery.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Services -weight: 3045 ---- - -Pod configuration is managed by Deployments, StatefulSets and Daemonsets, whereas services direct traffic to pods using selectors. - -For every workload (with at least one port configured) created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload's pods using the following naming convention: -`..svc.cluster.local`. - -You can create additional services so that a given namespace resolves with one or more external IP addresses, an external hostname, an alias to another DNS record, other workloads, or a set of pods that match a selector that you create. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to add a service and click **Explore**. -1. Click **Service Discovery > Services**. -1. Click **Create**. -1. Choose the type of service you want to create. -1. Select a **Namespace** from the drop-down list. -1. Enter a **Name** for the service. This name is used for DNS resolution. -1. Fill out the rest of the form. For help, refer to the upstream Kubernetes documentation about [services.](https://kubernetes.io/docs/concepts/services-networking/service/) -1. Click **Create**. - -**Result:** A new service is created. - -- You can view the record by from the project's **Service Discovery** tab. -- When you visit the new DNS name for the new record that you created (`..svc.cluster.local`), it resolves the chosen namespace. - -## Related Links - -- [Adding entries to Pod /etc/hosts with HostAliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/) diff --git a/versioned_docs/version-2.6/k8s-in-rancher/workloads/add-a-sidecar/add-a-sidecar.md b/versioned_docs/version-2.6/k8s-in-rancher/workloads/add-a-sidecar/add-a-sidecar.md deleted file mode 100644 index adc69309b6b..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/workloads/add-a-sidecar/add-a-sidecar.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Adding a Sidecar -weight: 3029 ---- -A _sidecar_ is a container that extends or enhances the main container in a pod. The main container and the sidecar share a pod, and therefore share the same network space and storage. You can add sidecars to existing workloads by using the **Add a Sidecar** option. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to add a sidecar and click **Explore**. -1. In the left navigation bar, click **Workload**. - -1. Find the workload that you want to extend. Select **⋮ > + Add Sidecar**. - -1. Enter a **Name** for the sidecar. - -1. In the **General** section, select a sidecar type. This option determines if the sidecar container is deployed before or after the main container is deployed. - - - **Standard Container:** - - The sidecar container is deployed after the main container. - - - **Init Container:** - - The sidecar container is deployed before the main container. - -1. From the **Container Image** field, enter the name of the container image that you want to deploy in support of the main container. During deployment, Rancher pulls this image from [Docker Hub](https://hub.docker.com/explore/). Enter the name exactly as it appears on Docker Hub. - -1. Set the remaining options. You can read about them in [Deploying Workloads](../deploy-workloads). - -1. Click **Launch**. - -**Result:** The sidecar is deployed according to your parameters. Following its deployment, you can view the sidecar by selecting **⋮ icon (...) > Edit** for the main deployment. - -## Related Links - -- [The Distributed System ToolKit: Patterns for Composite Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns/) diff --git a/versioned_docs/version-2.6/k8s-in-rancher/workloads/deploy-workloads/deploy-workloads.md b/versioned_docs/version-2.6/k8s-in-rancher/workloads/deploy-workloads/deploy-workloads.md deleted file mode 100644 index e6032e069b2..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/workloads/deploy-workloads/deploy-workloads.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Deploying Workloads -description: Read this step by step guide for deploying workloads. Deploy a workload to run an application in one or more containers. -weight: 3026 ---- - -Deploy a workload to run an application in one or more containers. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to upgrade a workload and click **Explore**. -1. In the left navigation bar, click **Workload**. -1. Click **Create**. -1. Choose the type of workload. -1. Select the namespace where the workload will be deployed. -1. Enter a **Name** for the workload. - -1. From the **Container Image** field, enter the name of the Docker image that you want to deploy to the project, optionally prefacing it with the registry host (e.g. `quay.io`, `registry.gitlab.com`, etc.). During deployment, Rancher pulls this image from the specified public or private registry. If no registry host is provided, Rancher will pull the image from [Docker Hub](https://hub.docker.com/explore/). Enter the name exactly as it appears in the registry server, including any required path, and optionally including the desired tag (e.g. `registry.gitlab.com/user/path/image:tag`). If no tag is provided, the `latest` tag will be automatically used. - -1. Either select an existing namespace, or click **Add to a new namespace** and enter a new namespace. - -1. Click **Add Port** to enter a port mapping, which enables access to the application inside and outside of the cluster . For more information, see [Services]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/#services). - -1. Configure the remaining options: - - - **Environment Variables** - - Use this section to either specify environment variables for your workload to consume on the fly, or to pull them from another source, such as a secret or [ConfigMap]({{}}/rancher/v2.6/en/k8s-in-rancher/configmaps/). - - - **Node Scheduling** - - **Health Check** - - **Volumes** - - Use this section to add storage for your workload. You can manually specify the volume that you want to add, use a persistent volume claim to dynamically create a volume for the workload, or read data for a volume to use from a file such as a [ConfigMap]({{}}/rancher/v2.6/en/k8s-in-rancher/configmaps/). - - When you are deploying a Stateful Set, you should use a Volume Claim Template when using Persistent Volumes. This will ensure that Persistent Volumes are created dynamically when you scale your Stateful Set. - - - **Scaling/Upgrade Policy** - - >**Amazon Note for Volumes:** - > - > To mount an Amazon EBS volume: - > - >- In [Amazon AWS](https://aws.amazon.com/), the nodes must be in the same Availability Zone and possess IAM permissions to attach/unattach volumes. - > - >- The cluster must be using the [AWS cloud provider](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#aws) option. For more information on enabling this option see [Creating an Amazon EC2 Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/ec2/) or [Creating a Custom Cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/custom-nodes). - - -1. Click **Show Advanced Options** and configure: - - - **Command** - - **Networking** - - **Labels & Annotations** - - **Security and Host Config** - -1. Click **Launch**. - -**Result:** The workload is deployed to the chosen namespace. You can view the workload's status from the project's **Workloads** view. diff --git a/versioned_docs/version-2.6/k8s-in-rancher/workloads/rollback-workloads/rollback-workloads.md b/versioned_docs/version-2.6/k8s-in-rancher/workloads/rollback-workloads/rollback-workloads.md deleted file mode 100644 index 1d8662a3d8a..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/workloads/rollback-workloads/rollback-workloads.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Rolling Back Workloads -weight: 3027 ---- - -Sometimes there is a need to rollback to the previous version of the application, either for debugging purposes or because an upgrade did not go as planned. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to upgrade a workload and click **Explore**. -1. In the left navigation bar, click **Workload**. -1. Find the workload that you want to rollback and select **⋮ > Rollback**. - -1. Choose the revision that you want to roll back to. Click **Rollback**. - -**Result:** Your workload reverts to the previous version that you chose. Wait a few minutes for the action to complete. diff --git a/versioned_docs/version-2.6/k8s-in-rancher/workloads/upgrade-workloads/upgrade-workloads.md b/versioned_docs/version-2.6/k8s-in-rancher/workloads/upgrade-workloads/upgrade-workloads.md deleted file mode 100644 index f6804adb2ea..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/workloads/upgrade-workloads/upgrade-workloads.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Upgrading Workloads -weight: 3028 ---- -When a new version of an application image is released on Docker Hub, you can upgrade any workloads running a previous version of the application to the new one. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to upgrade a workload and click **Explore**. -1. In the left navigation bar, click **Workload**. - -1. Find the workload that you want to upgrade and select **⋮ > Edit Config**. - -1. Update the **Container Image** and any options that you want to change. - -1. Review and edit the workload's **Scaling and Upgrade Policy**. - - These options control how the upgrade rolls out to containers that are currently running. For example, for scalable deployments, you can choose whether you want to stop old pods before deploying new ones, or vice versa, as well as the upgrade batch size. - -1. Click **Save**. - -**Result:** The workload begins upgrading its containers, per your specifications. Note that scaling up the deployment or updating the upgrade/scaling policy won't result in the pods recreation. diff --git a/versioned_docs/version-2.6/k8s-in-rancher/workloads/workloads.md b/versioned_docs/version-2.6/k8s-in-rancher/workloads/workloads.md deleted file mode 100644 index c1fdac0a8a7..00000000000 --- a/versioned_docs/version-2.6/k8s-in-rancher/workloads/workloads.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: "Kubernetes Workloads and Pods" -description: "Learn about the two constructs with which you can build any complex containerized application in Kubernetes: Kubernetes workloads and pods" -weight: 3025 ---- - -You can build any complex containerized application in Kubernetes using two basic constructs: pods and workloads. Once you build an application, you can expose it for access either within the same cluster or on the Internet using a third construct: services. - -### Pods - -[_Pods_](https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/) are one or more containers that share network namespaces and storage volumes. Most pods have only one container. Therefore when we discuss _pods_, the term is often synonymous with _containers_. You scale pods the same way you scale containers—by having multiple instances of the same pod that implement a service. Usually pods get scaled and managed by the workload. - -### Workloads - -_Workloads_ are objects that set deployment rules for pods. Based on these rules, Kubernetes performs the deployment and updates the workload with the current state of the application. -Workloads let you define the rules for application scheduling, scaling, and upgrade. - -#### Workload Types - -Kubernetes divides workloads into different types. The most popular types supported by Kubernetes are: - -- [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) - - _Deployments_ are best used for stateless applications (i.e., when you don't have to maintain the workload's state). Pods managed by deployment workloads are treated as independent and disposable. If a pod encounters disruption, Kubernetes removes it and then recreates it. An example application would be an Nginx web server. - -- [StatefulSets](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/) - - _StatefulSets_, in contrast to deployments, are best used when your application needs to maintain its identity and store data. An application would be something like Zookeeper—an application that requires a database for storage. - -- [DaemonSets](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) - - _Daemonsets_ ensures that every node in the cluster runs a copy of pod. For use cases where you're collecting logs or monitoring node performance, this daemon-like workload works best. - -- [Jobs](https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/) - - _Jobs_ launch one or more pods and ensure that a specified number of them successfully terminate. Jobs are best used to run a finite task to completion as opposed to managing an ongoing desired application state. - -- [CronJobs](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/) - - _CronJobs_ are similar to jobs. CronJobs, however, runs to completion on a cron-based schedule. - -### Services - -In many use cases, a workload has to be either: - -- Accessed by other workloads in the cluster. -- Exposed to the outside world. - -You can achieve these goals by creating a _Service_. Services are mapped to the underlying workload's pods using a [selector/label approach (view the code samples)](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#service-and-replicationcontroller). Rancher UI simplifies this mapping process by automatically creating a service along with the workload, using the service port and type that you select. - -#### Service Types - -There are several types of services available in Rancher. The descriptions below are sourced from the [Kubernetes Documentation](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types). - -- **ClusterIP** - - >Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster. This is the default `ServiceType`. - -- **NodePort** - - >Exposes the service on each Node’s IP at a static port (the `NodePort`). A `ClusterIP` service, to which the `NodePort` service will route, is automatically created. You’ll be able to contact the `NodePort` service, from outside the cluster, by requesting `:`. - -- **LoadBalancer** - - >Exposes the service externally using a cloud provider’s load balancer. `NodePort` and `ClusterIP` services, to which the external load balancer will route, are automatically created. - -## Workload Options - -This section of the documentation contains instructions for deploying workloads and using workload options. - -- [Deploy Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/deploy-workloads/) -- [Upgrade Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/upgrade-workloads/) -- [Rollback Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/rollback-workloads/) - -## Related Links - -### External Links - -- [Services](https://kubernetes.io/docs/concepts/services-networking/service/) diff --git a/versioned_docs/version-2.6/logging/architecture/architecture.md b/versioned_docs/version-2.6/logging/architecture/architecture.md deleted file mode 100644 index b72ddeacbd5..00000000000 --- a/versioned_docs/version-2.6/logging/architecture/architecture.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Architecture -weight: 1 ---- - -This section summarizes the architecture of the Rancher logging application. - -For more details about how the Banzai Cloud Logging operator works, see the [official documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture) - -### How the Banzai Cloud Logging Operator Works - -The Logging operator automates the deployment and configuration of a Kubernetes logging pipeline. It deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system. - -Fluent Bit queries the Kubernetes API and enriches the logs with metadata about the pods, and transfers both the logs and the metadata to Fluentd. Fluentd receives, filters, and transfers logs to multiple `Outputs`. - -The following custom resources are used to define how logs are filtered and sent to their `Outputs`: - -- A `Flow` is a namespaced custom resource that uses filters and selectors to route log messages to the appropriate `Outputs`. -- A `ClusterFlow` is used to route cluster-level log messages. -- An `Output` is a namespaced resource that defines where the log messages are sent. -- A `ClusterOutput` defines an `Output` that is available from all `Flows` and `ClusterFlows`. - -Each `Flow` must reference an `Output`, and each `ClusterFlow` must reference a `ClusterOutput`. - -The following figure from the [Banzai documentation](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture) shows the new logging architecture: - -
How the Banzai Cloud Logging Operator Works with Fluentd and Fluent Bit
- -![How the Banzai Cloud Logging Operator Works with Fluentd]({{}}/img/rancher/banzai-cloud-logging-operator.png) diff --git a/versioned_docs/version-2.6/logging/custom-resource-config/custom-resource-config.md b/versioned_docs/version-2.6/logging/custom-resource-config/custom-resource-config.md deleted file mode 100644 index 71a5cfda34b..00000000000 --- a/versioned_docs/version-2.6/logging/custom-resource-config/custom-resource-config.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Custom Resource Configuration -weight: 5 ---- - -The following Custom Resource Definitions are used to configure logging: - -- [Flow and ClusterFlow](./flows) -- [Output and ClusterOutput](./outputs) \ No newline at end of file diff --git a/versioned_docs/version-2.6/logging/custom-resource-config/flows/flows.md b/versioned_docs/version-2.6/logging/custom-resource-config/flows/flows.md deleted file mode 100644 index 2ad4991dc8f..00000000000 --- a/versioned_docs/version-2.6/logging/custom-resource-config/flows/flows.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Flows and ClusterFlows -weight: 1 ---- - -For the full details on configuring `Flows` and `ClusterFlows`, see the [Banzai Cloud Logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) - -- [Configuration](#configuration) -- [YAML Example](#yaml-example) - -# Configuration - -- [Flows](#flows) - - [Matches](#matches) - - [Filters](#filters) - - [Outputs](#outputs) -- [ClusterFlows](#clusterflows) - -# Flows - -A `Flow` defines which logs to collect and filter and which output to send the logs to. - -The `Flow` is a namespaced resource, which means logs will only be collected from the namespace that the `Flow` is deployed in. - -`Flows` can be configured by filling out forms in the Rancher UI. - -For more details about the `Flow` custom resource, see [FlowSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/) - -### Matches - -Match statements are used to select which containers to pull logs from. - -You can specify match statements to select or exclude logs according to Kubernetes labels, container and host names. Match statements are evaluated in the order they are defined and processed only until the first matching select or exclude rule applies. - -Matches can be configured by filling out the `Flow` or `ClusterFlow` forms in the Rancher UI. - -For detailed examples on using the match statement, see the [official documentation on log routing.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/) - -### Filters - -You can define one or more filters within a `Flow`. Filters can perform various actions on the logs, for example, add additional data, transform the logs, or parse values from the records. The filters in the `Flow` are applied in the order in the definition. - -For a list of filters supported by the Banzai Cloud Logging operator, see [this page.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/) - -Filters need to be configured in YAML. - -### Outputs - -This `Output` will receive logs from the `Flow`. Because the `Flow` is a namespaced resource, the `Output` must reside in same namespace as the `Flow`. - -`Outputs` can be referenced when filling out the `Flow` or `ClusterFlow` forms in the Rancher UI. - -# ClusterFlows - -Matches, filters and `Outputs` are configured for `ClusterFlows` in the same way that they are configured for `Flows`. The key difference is that the `ClusterFlow` is scoped at the cluster level and can configure log collection across all namespaces. - -`ClusterFlows` can be configured by filling out forms in the Rancher UI. - -After `ClusterFlow` selects logs from all namespaces in the cluster, logs from the cluster will be collected and logged to the selected `ClusterOutput`. - -# YAML Example - -The following example `Flow` transforms the log messages from the default namespace and sends them to an S3 `Output`: - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: Flow -metadata: - name: flow-sample - namespace: default -spec: - filters: - - parser: - remove_key_name_field: true - parse: - type: nginx - - tag_normaliser: - format: ${namespace_name}.${pod_name}.${container_name} - localOutputRefs: - - s3-output - match: - - select: - labels: - app: nginx -``` diff --git a/versioned_docs/version-2.6/logging/custom-resource-config/outputs/outputs.md b/versioned_docs/version-2.6/logging/custom-resource-config/outputs/outputs.md deleted file mode 100644 index 577af052f16..00000000000 --- a/versioned_docs/version-2.6/logging/custom-resource-config/outputs/outputs.md +++ /dev/null @@ -1,302 +0,0 @@ ---- -title: Outputs and ClusterOutputs -weight: 2 ---- - -For the full details on configuring `Outputs` and `ClusterOutputs`, see the [Banzai Cloud Logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/output/) - -- [Configuration](#configuration) -- [YAML Examples](#yaml-examples) - - [Cluster Output to ElasticSearch](#cluster-output-to-elasticsearch) - - [Output to Splunk](#output-to-splunk) - - [Output to Syslog](#output-to-syslog) - - [Unsupported Outputs](#unsupported-outputs) - -# Configuration - -- [Outputs](#outputs) -- [ClusterOutputs](#clusteroutputs) - -# Outputs - -The `Output` resource defines where your `Flows` can send the log messages. `Outputs` are the final stage for a logging `Flow`. - -The `Output` is a namespaced resource, which means only a `Flow` within the same namespace can access it. - -You can use secrets in these definitions, but they must also be in the same namespace. - -`Outputs` can be configured by filling out forms in the Rancher UI. - -For the details of `Output` custom resource, see [OutputSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/) - -The Rancher UI provides forms for configuring the following `Output` types: - -- Amazon ElasticSearch -- Azure Storage -- Cloudwatch -- Datadog -- Elasticsearch -- File -- Fluentd -- GCS -- Kafka -- Kinesis Stream -- LogDNA -- LogZ -- Loki -- New Relic -- Splunk -- SumoLogic -- Syslog - -The Rancher UI provides forms for configuring the `Output` type, target, and access credentials if applicable. - -For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/) - -# ClusterOutputs - -`ClusterOutput` defines an `Output` without namespace restrictions. It is only effective when deployed in the same namespace as the logging operator. - -`ClusterOutputs` can be configured by filling out forms in the Rancher UI. - -For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/) - -# YAML Examples - -Once logging is installed, you can use these examples to help craft your own logging pipeline. - -- [Cluster Output to ElasticSearch](#cluster-output-to-elasticsearch) -- [Output to Splunk](#output-to-splunk) -- [Output to Syslog](#output-to-syslog) -- [Unsupported Outputs](#unsupported-outputs) - -### Cluster Output to ElasticSearch - -Let's say you wanted to send all logs in your cluster to an `elasticsearch` cluster. First, we create a cluster `Output`. - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: ClusterOutput -metadata: - name: "example-es" - namespace: "cattle-logging-system" -spec: - elasticsearch: - host: elasticsearch.example.com - port: 9200 - scheme: http -``` - -We have created this `ClusterOutput`, without elasticsearch configuration, in the same namespace as our operator: `cattle-logging-system.`. Any time we create a `ClusterFlow` or `ClusterOutput`, we have to put it in the `cattle-logging-system` namespace. - -Now that we have configured where we want the logs to go, let's configure all logs to go to that `ClusterOutput`. - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: ClusterFlow -metadata: - name: "all-logs" - namespace: "cattle-logging-system" -spec: - globalOutputRefs: - - "example-es" -``` - -We should now see our configured index with logs in it. - - -### Output to Splunk - -What if we have an application team who only wants logs from a specific namespaces sent to a `splunk` server? For this case, we can use namespaced `Outputs` and `Flows`. - -Before we start, let's set up that team's application: `coolapp`. - -```yaml -apiVersion: v1 -kind: Namespace -metadata: - name: devteam ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: coolapp - namespace: devteam - labels: - app: coolapp -spec: - replicas: 2 - selector: - matchLabels: - app: coolapp - template: - metadata: - labels: - app: coolapp - spec: - containers: - - name: generator - image: paynejacob/loggenerator:latest -``` - -With `coolapp` running, we will follow a similar path as when we created a `ClusterOutput`. However, unlike `ClusterOutputs`, we create our `Output` in our application's namespace. - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: Output -metadata: - name: "devteam-splunk" - namespace: "devteam" -spec: - splunkHec: - hec_host: splunk.example.com - hec_port: 8088 - protocol: http -``` - -Once again, let's feed our `Output` some logs: - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: Flow -metadata: - name: "devteam-logs" - namespace: "devteam" -spec: - localOutputRefs: - - "devteam-splunk" -``` - - -### Output to Syslog - -Let's say you wanted to send all logs in your cluster to an `syslog` server. First, we create a `ClusterOutput`: - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: ClusterOutput -metadata: - name: "example-syslog" - namespace: "cattle-logging-system" -spec: - syslog: - buffer: - timekey: 30s - timekey_use_utc: true - timekey_wait: 10s - flush_interval: 5s - format: - type: json - app_name_field: test - host: syslog.example.com - insecure: true - port: 514 - transport: tcp -``` - -Now that we have configured where we want the logs to go, let's configure all logs to go to that `Output`. - -```yaml -apiVersion: logging.banzaicloud.io/v1beta1 -kind: ClusterFlow -metadata: - name: "all-logs" - namespace: cattle-logging-system -spec: - globalOutputRefs: - - "example-syslog" -``` - -### Unsupported Outputs - -For the final example, we create an `Output` to write logs to a destination that is not supported out of the box: - -> **Note on syslog** `syslog` is a supported `Output`. However, this example still provides an overview on using unsupported plugins. - -```yaml -apiVersion: v1 -kind: Secret -metadata: - name: syslog-config - namespace: cattle-logging-system -type: Opaque -stringData: - fluent-bit.conf: | - [INPUT] - Name forward - Port 24224 - - [OUTPUT] - Name syslog - InstanceName syslog-output - Match * - Addr syslog.example.com - Port 514 - Cluster ranchers - ---- -apiVersion: apps/v1 -kind: Deployment -metadata: - name: fluentbit-syslog-forwarder - namespace: cattle-logging-system - labels: - output: syslog -spec: - selector: - matchLabels: - output: syslog - template: - metadata: - labels: - output: syslog - spec: - containers: - - name: fluentbit - image: paynejacob/fluent-bit-out-syslog:latest - ports: - - containerPort: 24224 - volumeMounts: - - mountPath: "/fluent-bit/etc/" - name: configuration - volumes: - - name: configuration - secret: - secretName: syslog-config ---- -apiVersion: v1 -kind: Service -metadata: - name: syslog-forwarder - namespace: cattle-logging-system -spec: - selector: - output: syslog - ports: - - protocol: TCP - port: 24224 - targetPort: 24224 ---- -apiVersion: logging.banzaicloud.io/v1beta1 -kind: ClusterFlow -metadata: - name: all-logs - namespace: cattle-logging-system -spec: - globalOutputRefs: - - syslog ---- -apiVersion: logging.banzaicloud.io/v1beta1 -kind: ClusterOutput -metadata: - name: syslog - namespace: cattle-logging-system -spec: - forward: - servers: - - host: "syslog-forwarder.cattle-logging-system" - require_ack_response: false - ignore_network_errors_at_startup: false -``` - -Let's break down what is happening here. First, we create a deployment of a container that has the additional `syslog` plugin and accepts logs forwarded from another `fluentd`. Next we create an `Output` configured as a forwarder to our deployment. The deployment `fluentd` will then forward all logs to the configured `syslog` destination. diff --git a/versioned_docs/version-2.6/logging/helm-chart-options/helm-chart-options.md b/versioned_docs/version-2.6/logging/helm-chart-options/helm-chart-options.md deleted file mode 100644 index b05c1ff1528..00000000000 --- a/versioned_docs/version-2.6/logging/helm-chart-options/helm-chart-options.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: rancher-logging Helm Chart Options -shortTitle: Helm Chart Options -weight: 4 ---- - -- [Enable/Disable Windows Node Logging](#enable-disable-windows-node-logging) -- [Working with a Custom Docker Root Directory](#working-with-a-custom-docker-root-directory) -- [Adding NodeSelector Settings and Tolerations for Custom Taints](#adding-nodeselector-settings-and-tolerations-for-custom-taints) -- [Enabling the Logging Application to Work with SELinux](#enabling-the-logging-application-to-work-with-selinux) -- [Additional Logging Sources](#additional-logging-sources) -- [Systemd Configuration](#systemd-configuration) - -### Enable/Disable Windows Node Logging - -You can enable or disable Windows node logging by setting `global.cattle.windows.enabled` to either `true` or `false` in the `values.yaml`. - -By default, Windows node logging will be enabled if the Cluster Dashboard UI is used to install the logging application on a Windows cluster. - -In this scenario, setting `global.cattle.windows.enabled` to `false` will disable Windows node logging on the cluster. -When disabled, logs will still be collected from Linux nodes within the Windows cluster. - -> Note: Currently an [issue](https://github.com/rancher/rancher/issues/32325) exists where Windows nodeAgents are not deleted when performing a `helm upgrade` after disabling Windows logging in a Windows cluster. In this scenario, users may need to manually remove the Windows nodeAgents if they are already installed. - -### Working with a Custom Docker Root Directory - -If using a custom Docker root directory, you can set `global.dockerRootDirectory` in `values.yaml`. - -This will ensure that the Logging CRs created will use your specified path rather than the default Docker `data-root` location. - -Note that this only affects Linux nodes. - -If there are any Windows nodes in the cluster, the change will not be applicable to those nodes. - -### Adding NodeSelector Settings and Tolerations for Custom Taints - -You can add your own `nodeSelector` settings and add `tolerations` for additional taints by editing the logging Helm chart values. For details, see [this page.](../taints-tolerations) - -### Enabling the Logging Application to Work with SELinux - -> **Requirements:** Logging v2 was tested with SELinux on RHEL/CentOS 7 and 8. - -[Security-Enhanced Linux (SELinux)](https://en.wikipedia.org/wiki/Security-Enhanced_Linux) is a security enhancement to Linux. After being historically used by government agencies, SELinux is now industry standard and is enabled by default on CentOS 7 and 8. - -To use Logging v2 with SELinux, we recommend installing the `rancher-selinux` RPM according to the instructions on [this page.]({{}}/rancher/v2.6/en/security/selinux/#installing-the-rancher-selinux-rpm) - -Then, when installing the logging application, configure the chart to be SELinux aware by changing `global.seLinux.enabled` to `true` in the `values.yaml`. - -### Additional Logging Sources - -By default, Rancher collects logs for [control plane components](https://kubernetes.io/docs/concepts/overview/components/#control-plane-components) and [node components](https://kubernetes.io/docs/concepts/overview/components/#node-components) for all cluster types. - -In some cases, Rancher may be able to collect additional logs. - -The following table summarizes the sources where additional logs may be collected for each node types: - -| Logging Source | Linux Nodes (including in Windows cluster) | Windows Nodes | -| --- | --- | ---| -| RKE | ✓ | ✓ | -| RKE2 | ✓ | | -| K3s | ✓ | | -| AKS | ✓ | | -| EKS | ✓ | | -| GKE | ✓ | | - -To enable hosted Kubernetes providers as additional logging sources, enable **Enable enhanced cloud provider logging** option when installing or upgrading the Logging Helm chart. - -When enabled, Rancher collects all additional node and control plane logs the provider has made available, which may vary between providers - -If you're already using a cloud provider's own logging solution such as AWS CloudWatch or Google Cloud operations suite (formerly Stackdriver), it is not necessary to enable this option as the native solution will have unrestricted access to all logs. - -### Systemd Configuration - -In Rancher logging, `SystemdLogPath` must be configured for K3s and RKE2 Kubernetes distributions. - -K3s and RKE2 Kubernetes distributions log to journald, which is the subsystem of systemd that is used for logging. In order to collect these logs, the `systemdLogPath` needs to be defined. While the `run/log/journal` directory is used by default, some Linux distributions do not default to this path. For example, Ubuntu defaults to `var/log/journal`. To determine your `systemdLogPath` configuration, see steps below. - -**Steps for Systemd Configuration:** - -* Run `cat /etc/systemd/journald.conf | grep -E ^\#?Storage | cut -d"=" -f2` on one of your nodes. -* If `persistent` is returned, your `systemdLogPath` should be `/var/log/journal`. -* If `volatile` is returned, your `systemdLogPath` should be `/run/log/journal`. -* If `auto` is returned, check if `/var/log/journal` exists. - * If `/var/log/journal` exists, then use `/var/log/journal`. - * If `/var/log/journal` does not exist, then use `/run/log/journal`. - -> **Note:** If any value not described above is returned, Rancher Logging will not be able to collect control plane logs. To address this issue, you will need to perform the following actions on every control plane node: - -> * Set `Storage=volatile` in journald.conf. -> * Reboot your machine. -> * Set `systemdLogPath` to `/run/log/journal`. \ No newline at end of file diff --git a/versioned_docs/version-2.6/logging/logging.md b/versioned_docs/version-2.6/logging/logging.md deleted file mode 100644 index a22e38febac..00000000000 --- a/versioned_docs/version-2.6/logging/logging.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -title: Rancher Integration with Logging Services -shortTitle: Logging -description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster. -metaDescription: "Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster." -weight: 15 ---- - -The [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) now powers Rancher's logging solution in place of the former, in-house solution. - -For an overview of the changes in v2.5, see [this section.]({{}}/rancher/v2.6/en/logging/architecture/#changes-in-rancher-v2-5) For information about migrating from Logging V1, see [this page.](./migrating) - -- [Enabling Logging](#enabling-logging) -- [Uninstall Logging](#uninstall-logging) -- [Architecture](#architecture) -- [Role-based Access Control](#role-based-access-control) -- [Configuring the Logging Custom Resources](#configuring-the-logging-custom-resources) - - [Flows and ClusterFlows](#flows-and-clusterflows) - - [Outputs and ClusterOutputs](#outputs-and-clusteroutputs) -- [Configuring the Logging Helm Chart](#configuring-the-logging-helm-chart) - - [Windows Support](#windows-support) - - [Working with a Custom Docker Root Directory](#working-with-a-custom-docker-root-directory) - - [Working with Taints and Tolerations](#working-with-taints-and-tolerations) - - [Logging V2 with SELinux](#logging-v2-with-selinux) - - [Additional Logging Sources](#additional-logging-sources) -- [Troubleshooting](#troubleshooting) - -# Enabling Logging - -You can enable the logging for a Rancher managed cluster by going to the Apps page and installing the logging app. - -1. Go to the cluster where you want to install logging and click **Apps & Marketplace**. -1. Click the **Logging** app. -1. Scroll to the bottom of the Helm chart README and click **Install**. - -**Result:** The logging app is deployed in the `cattle-logging-system` namespace. - -# Uninstall Logging - -1. Go to the cluster where you want to install logging and click **Apps & Marketplace**. -1. Click **Installed Apps**. -1. Go to the `cattle-logging-system` namespace and check the boxes for `rancher-logging` and `rancher-logging-crd`. -1. Click **Delete**. -1. Confirm **Delete**. - -**Result** `rancher-logging` is uninstalled. - -# Architecture - -For more information about how the logging application works, see [this section.](./architecture) - - - -# Role-based Access Control - -Rancher logging has two roles, `logging-admin` and `logging-view`. For more information on how and when to use these roles, see [this page.](./rbac) - -# Configuring Logging Custom Resources - -To manage `Flows,` `ClusterFlows`, `Outputs`, and `ClusterOutputs`, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to configure logging custom resources and click **Explore**. -1. In the left navigation bar, click **Logging**. - -### Flows and ClusterFlows - -For help with configuring `Flows` and `ClusterFlows`, see [this page.](./custom-resource-config/flows) - -### Outputs and ClusterOutputs - -For help with configuring `Outputs` and `ClusterOutputs`, see [this page.](./custom-resource-config/outputs) - -# Configuring the Logging Helm Chart - -For a list of options that can be configured when the logging application is installed or upgraded, see [this page.](./helm-chart-options) - -### Windows Support - -Logging support for Windows clusters is available and logs can be collected from Windows nodes. - -For details on how to enable or disable Windows node logging, see [this section.](./helm-chart-options/#enable-disable-windows-node-logging) - -### Working with a Custom Docker Root Directory - -For details on using a custom Docker root directory, see [this section.](./helm-chart-options/#working-with-a-custom-docker-root-directory) - - -### Working with Taints and Tolerations - -For information on how to use taints and tolerations with the logging application, see [this page.](./taints-tolerations) - - -### Logging V2 with SELinux - -For information on enabling the logging application for SELinux-enabled nodes, see [this section.](./helm-chart-options/#enabling-the-logging-application-to-work-with-selinux) - -### Additional Logging Sources - -By default, Rancher collects logs for control plane components and node components for all cluster types. In some cases additional logs can be collected. For details, see [this section.](./helm-chart-options/#enabling-the-logging-application-to-work-with-selinux) - - -# Troubleshooting - -### The `cattle-logging` Namespace Being Recreated - -If your cluster previously deployed logging from the global view in the legacy Rancher UI, you may encounter an issue where its `cattle-logging` namespace is continually being recreated. - -The solution is to delete all `clusterloggings.management.cattle.io` and `projectloggings.management.cattle.io` custom resources from the cluster specific namespace in the management cluster. -The existence of these custom resources causes Rancher to create the `cattle-logging` namespace in the downstream cluster if it does not exist. - -The cluster namespace matches the cluster ID, so we need to find the cluster ID for each cluster. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster you want to get the ID of and click **Explore**. -2. Copy the `` portion from one of the URLs below. The `` portion is the cluster namespace name. - -```bash -# Cluster Management UI -https:///c// - -# Cluster Dashboard -https:///dashboard/c// -``` - -Now that we have the `` namespace, we can delete the CRs that cause `cattle-logging` to be continually recreated. -*Warning:* ensure that logging, the version installed from the global view in the legacy Rancher UI, is not currently in use. - -```bash -kubectl delete clusterloggings.management.cattle.io -n -kubectl delete projectloggings.management.cattle.io -n -``` diff --git a/versioned_docs/version-2.6/logging/migrating/migrating.md b/versioned_docs/version-2.6/logging/migrating/migrating.md deleted file mode 100644 index b0c8d2906e8..00000000000 --- a/versioned_docs/version-2.6/logging/migrating/migrating.md +++ /dev/null @@ -1,190 +0,0 @@ ---- -title: Migrating to Rancher v2.5 Logging -weight: 2 ---- -Starting in v2.5, the logging feature available within Rancher has been completely overhauled. The [logging operator](https://github.com/banzaicloud/logging-operator) from Banzai Cloud has been adopted; Rancher configures this tooling for use when deploying logging. - -Among the many features and changes in the new logging functionality is the removal of project-specific logging configurations. Instead, one now configures logging at the namespace level. Cluster-level logging remains available, but configuration options differ. - -- [Installation](#installation) - - [Terminology](#terminology) -- [Cluster Logging](#cluster-logging) -- [Project Logging](#project-logging) -- [Output Configuration](#output-configuration) - - [Elasticsearch](#elasticsearch) - - [Splunk](#splunk) - - [Kafka](#kafka) - - [Fluentd](#fluentd) - - [Syslog](#syslog) -- [Custom Log Fields](#custom-log-fields) -- [System Logging](#system-logging) - -# Installation - -To install logging in Rancher v2.5+, refer to the [installation instructions]({{}}/rancher/v2.6/en/logging/#enabling-logging). - -### Terminology - -In v2.5+, logging configuration in the **Cluster Dashboard**. To configure logging custom resources after the Logging application is installed, go to the left navigation bar and click **Logging**. It is from this menu option that logging for both cluster and namespace is configured. - -> Note: Logging is installed on a per-cluster basis. You will need to navigate between clusters to configure logging for each cluster. - -There are four key concepts to understand for v2.5+ logging: - -1. Outputs - - `Outputs` are a configuration resource that determine a destination for collected logs. This is where settings for aggregators such as ElasticSearch, Kafka, etc. are stored. `Outputs` are namespaced resources. - -2. Flows - - `Flows` are a configuration resource that determine collection, filtering, and destination rules for logs. It is within a flow that one will configure what logs to collect, how to mutate or filter them, and which `Outputs` to send the logs to. `Flows` are namespaced resources, and can connect either to an `Output` in the same namespace, or a `ClusterOutput`. - -3. ClusterOutputs - - `ClusterOutputs` serve the same functionality as `Outputs`, except they are a cluster-scoped resource. `ClusterOutputs` are necessary when collecting logs cluster-wide, or if you wish to provide an `Output` to all namespaces in your cluster. - -4. ClusterFlows - - `ClusterFlows` serve the same function as `Flows`, but at the cluster level. They are used to configure log collection for an entire cluster, instead of on a per-namespace level. `ClusterFlows` are also where mutations and filters are defined, same as `Flows` (in functionality). - -# Cluster Logging - -To configure cluster-wide logging for v2.5+ logging, one needs to set up a `ClusterFlow`. This object defines the source of logs, any transformations or filters to be applied, and finally the `Output` (or `Outputs`) for the logs. - -> Important: `ClusterFlows` must be defined within the `cattle-logging-system` namespace. `ClusterFlows` will not work if defined in any other namespace. - -In legacy logging, in order to collect logs from across the entire cluster, one only needed to enable cluster-level logging and define the desired `Output`. This basic approach remains in v2.5+ logging. To replicate legacy cluster-level logging, follow these steps: - -1. Define a `ClusterOutput` according to the instructions found under [Output Configuration](#output-configuration) -2. Create a `ClusterFlow`, ensuring that it is set to be created in the `cattle-logging-system` namespace - 1. Remove all _Include_ and _Exclude_ rules from the `Flow` definition. This ensures that all logs are gathered. - 2. You do not need to configure any filters if you do not wish - default behavior does not require their creation - 3. Define your cluster `Output` or `Outputs` - -This will result in logs from all sources in the cluster (all pods, and all system components) being collected and sent to the `Output` or `Outputs` you defined in the `ClusterFlow`. - -# Project Logging - -Logging in v2.5+ is not project-aware. This means that in order to collect logs from pods running in project namespaces, you will need to define `Flows` for those namespaces. - -To collect logs from a specific namespace, follow these steps: - -1. Define an `Output` or `ClusterOutput` according to the instructions found under [Output Configuration](#output-configuration) -2. Create a `Flow`, ensuring that it is set to be created in the namespace in which you want to gather logs. - 1. If you wish to define _Include_ or _Exclude_ rules, you may do so. Otherwise, removal of all rules will result in all pods in the target namespace having their logs collected. - 2. You do not need to configure any filters if you do not wish - default behavior does not require their creation - 3. Define your outputs - these can be either `ClusterOutput` or `Output` objects. - -This will result in logs from all sources in the namespace (pods) being collected and sent to the `Output` (or `Outputs`) you defined in your `Flow`. - -> To collect logs from a project, repeat the above steps for every namespace within the project. Alternatively, you can label your project workloads with a common label (e.g. `project=my-project`) and use a `ClusterFlow` to collect logs from all pods matching this label. - -# Output Configuration -In legacy logging, there are five logging destinations to choose from: Elasticsearch, Splunk, Kafka, Fluentd, and Syslog. With the exception of Syslog, all of these destinations are available in logging v2.5+. - - -### Elasticsearch - -| Legacy Logging | v2.5+ Logging | Notes | -|-----------------------------------------------|-----------------------------------|-----------------------------------------------------------| -| Endpoint | Target -> Host | Make sure to specify Scheme (https/http), as well as Port | -| X-Pack Security -> Username | Access -> User | | -| X-Pack Security -> Password | Access -> Password | Password must now be stored in a secret | -| SSL Configuration -> Client Private Key | SSL -> Client Key | Key must now be stored in a secret | -| SSL Configuration -> Client Certificate | SSL -> Client Cert | Certificate must now be stored in a secret | -| SSL Configuration -> Client Key Password | SSL -> Client Key Pass | Password must now be stored in a secret | -| SSL Configuration -> Enabled SSL Verification | SSL -> Certificate Authority File | Certificate must now be stored in a secret | - - -In legacy logging, indices were automatically created according to the format in the "Index Patterns" section. In v2.5 logging, default behavior has been changed to logging to a single index. You can still configure index pattern functionality on the `Output` object by editing as YAML and inputting the following values: - -``` -... -spec: - elasticsearch: - ... - logstash_format: true - logstash_prefix: - logstash_dateformat: "%Y-%m-%d" -``` - -Replace `` with the prefix for the indices that will be created. In legacy logging, this defaulted to the name of the cluster. - -### Splunk - -| Legacy Logging | v2.5+ Logging | Notes | -|------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------| -| HEC Configuration -> Endpoint | Target -> Host | Protocol (https/http) and port must be defined separately from the host | -| HEC Configuration -> Token | Access -> Token | Token must now be stored as a secret | -| HEC Configuration -> Index | Edit as YAML -> `index` | `index` field must be added as YAML key under `spec.splunkHec` | -| HEC Configuration -> Source | Edit as YAML -> `source` | `source` field must be added as YAML key under `spec.splunkHec` | -| SSL Configuration -> Client Private Key | Edit as YAML -> `client_key` | `client_key` field must be added as YAML key under `spec.splunkHec`. See (1) | -| SSL Configuration -> Client Certificate | Edit as YAML -> `client_cert` | `client_cert` field must be added as YAML key under `spec.splunkHec`. See (1) | -| SSL Configuration -> Client Key Password | _Not Supported_ | Specifying a password for the client private key is not currently supported. | -| SSL Configuration -> SSL Verify | Edit as YAML -> `ca_file` or `ca_path` | `ca_file` or `ca_path` field must be added as YAML key under `spec.splunkHec`. See (2) | - -_(1) `client_key` and `client_cert` values must be paths to the key and cert files, respectively. These files must be mounted into the `rancher-logging-fluentd` pod in order to be used._ - -_(2) Users can configure either `ca_file` (a path to a PEM-encoded CA certificate) or `ca_path` (a path to a directory containing CA certificates in PEM format). These files must be mounted into the `rancher-logging-fluentd` pod in order to be used._ - -### Kafka - -| Legacy Logging | v2.5+ Logging | Notes | -|-----------------------------------------|----------------------------|------------------------------------------------------| -| Kafka Configuration -> Endpoint Type | - | Zookeeper is no longer supported as an endpoint type | -| Kafka Configuration -> Endpoint | Target -> Brokers | Comma-separated list of brokers (host:port) | -| Kafka Configuration -> Topic | Target -> Default Topic | | -| SSL Configuration -> Client Private Key | SSL -> SSL Client Cert | Certificate must be stored as a secret | -| SSL Configuration -> Client Certificate | SSL -> SSL Client Cert Key | Key must be stored as a secret | -| SSL Configuration -> CA Certificate PEM | SSL -> SSL CA Cert | Certificate must be stored as a secret | -| SASL Configuration -> Username | Access -> Username | Username must be stored in a secret | -| SASL Configuration -> Password | Access -> Password | Password must be stored in a secret | -| SASL Configuration -> Scram Mechanism | Access -> Scram Mechanism | Input mechanism as string, e.g. "sha256" or "sha512" | - -### Fluentd - -As of v2.5.2, it is only possible to add a single Fluentd server using the "Edit as Form" option. To add multiple servers, edit the `Output` as YAML and input multiple servers. - -| Legacy Logging | v2.5+ Logging | Notes | -|------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------| -| Fluentd Configuration -> Endpoint | Target -> Host, Port | Input the host and port separately | -| Fluentd Configuration -> Shared Key | Access -> Shared Key | Shared key must be stored as a secret | -| Fluentd Configuration -> Username | Access -> Username | Username must be stored as a secret | -| Fluentd Configuration -> Password | Access -> Password | Password must be stored as a secret | -| Fluentd Configuration -> Hostname | Edit as YAML -> `host` | `host` field set as YAML key under `spec.forward.servers[n]` | -| Fluentd Configuration -> Weight | Edit as YAML -> `weight` | `weight` field set as YAML key under `spec.forward.servers[n]` | -| SSL Configuration -> Use TLS | - | Do not need to explicitly enable. Define client cert fields instead. | -| SSL Configuration -> Client Private Key | Edit as YAML -> `tls_private_key_path` | Field set as YAML key under `spec.forward`. See (1) | -| SSL Configuration -> Client Certificate | Edit as YAML -> `tls_client_cert_path` | Field set as YAML key under `spec.forward`. See (1) | -| SSL Configuration -> Client Key Password | Edit as YAML -> `tls_client_private_key_passphrase` | Field set as YAML key under `spec.forward`. See (1) | -| SSL Configuration -> SSL Verify | Edit as YAML -> `tls_insecure_mode` | Field set as YAML key under `spec.forward`. Default: `false` | -| SSL Configuration -> CA Certificate PEM | Edit as YAML -> `tls_cert_path` | Field set as YAML key under `spec.forward`. See (1) | -| Enable Gzip Compression | - | No longer supported in v2.5+ logging | - -_(1) These values are to be specified as paths to files. Those files must be mounted into the `rancher-logging-fluentd` pod in order to be used._ - -### Syslog - -As of v2.5.2, syslog is not currently supported for `Outputs` using v2.5+ logging. - -# Custom Log Fields - -In order to add custom log fields, you will need to add the following YAML to your `Flow` configuration: - -``` -... -spec: - filters: - - record_modifier: - records: - - foo: "bar" -``` - -(replace `foo: "bar"` with custom log fields you wish to add) - -# System Logging - -In legacy logging, collecting logs from system components was accomplished by checking a box labeled "Include System Log" when setting up cluster logging. In v2.5+ logging, system logs are gathered in one of two ways: - -1. Gather all cluster logs, not specifying any match or exclusion rules. This results in all container logs from the cluster being collected, which includes system logs. -2. Specifically target system logs by adding match rules for system components. Specific match rules depend on the component being collected. \ No newline at end of file diff --git a/versioned_docs/version-2.6/logging/rbac/rbac.md b/versioned_docs/version-2.6/logging/rbac/rbac.md deleted file mode 100644 index 063d09d6bf0..00000000000 --- a/versioned_docs/version-2.6/logging/rbac/rbac.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -shortTitle: Role-based Access Control -title: Role-based Access Control for Logging -weight: 3 ---- - -Rancher logging has two roles, `logging-admin` and `logging-view`. - -- `logging-admin` gives users full access to namespaced `Flows` and `Outputs` -- `logging-view` allows users to *view* namespaced `Flows` and `Outputs`, and `ClusterFlows` and `ClusterOutputs` - -> **Why choose one role over the other?** Edit access to `ClusterFlow` and `ClusterOutput` resources is powerful. Any user with it has edit access for all logs in the cluster. - -In Rancher, the cluster administrator role is the only role with full access to all `rancher-logging` resources. Cluster members are not able to edit or read any logging resources. Project owners and members have the following privileges: - -Project Owners | Project Members ---- | --- -able to create namespaced `Flows` and `Outputs` in their projects' namespaces | only able to view the `Flows` and `Outputs` in projects' namespaces -can collect logs from anything in their projects' namespaces | cannot collect any logs in their projects' namespaces - -Both project owners and project members require at least *one* namespace in their project to use logging. If they do not, then they may not see the logging button in the top nav dropdown. \ No newline at end of file diff --git a/versioned_docs/version-2.6/logging/taints-tolerations/taints-tolerations.md b/versioned_docs/version-2.6/logging/taints-tolerations/taints-tolerations.md deleted file mode 100644 index 00cee550a8d..00000000000 --- a/versioned_docs/version-2.6/logging/taints-tolerations/taints-tolerations.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Working with Taints and Tolerations -weight: 6 ---- - -"Tainting" a Kubernetes node causes pods to repel running on that node. - -Unless the pods have a `toleration` for that node's taint, they will run on other nodes in the cluster. - -[Taints and tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) can work in conjunction with the `nodeSelector` [field](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector) within the `PodSpec`, which enables the *opposite* effect of a taint. - -Using `nodeSelector` gives pods an affinity towards certain nodes. - -Both provide choice for the what node(s) the pod will run on. - -- [Default Implementation in Rancher's Logging Stack](#default-implementation-in-rancher-s-logging-stack) -- [Adding NodeSelector Settings and Tolerations for Custom Taints](#adding-nodeselector-settings-and-tolerations-for-custom-taints) - - -### Default Implementation in Rancher's Logging Stack - -By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes. -The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes. -Moreover, most logging stack pods run on Linux only and have a `nodeSelector` added to ensure they run on Linux nodes. - -This example Pod YAML file shows a nodeSelector being used with a toleration: - -```yaml -apiVersion: v1 -kind: Pod -# metadata... -spec: - # containers... - tolerations: - - key: cattle.io/os - operator: "Equal" - value: "linux" - effect: NoSchedule - nodeSelector: - kubernetes.io/os: linux -``` - -In the above example, we ensure that our pod only runs on Linux nodes, and we add a `toleration` for the taint we have on all of our Linux nodes. - -You can do the same with Rancher's existing taints, or with your own custom ones. - -### Adding NodeSelector Settings and Tolerations for Custom Taints - -If you would like to add your own `nodeSelector` settings, or if you would like to add `tolerations` for additional taints, you can pass the following to the chart's values. - -```yaml -tolerations: - # insert tolerations... -nodeSelector: - # insert nodeSelector... -``` - -These values will add both settings to the `fluentd`, `fluentbit`, and `logging-operator` containers. -Essentially, these are global settings for all pods in the logging stack. - -However, if you would like to add tolerations for *only* the `fluentbit` container, you can add the following to the chart's values. - -```yaml -fluentbit_tolerations: - # insert tolerations list for fluentbit containers only... -``` diff --git a/versioned_docs/version-2.6/longhorn/longhorn.md b/versioned_docs/version-2.6/longhorn/longhorn.md deleted file mode 100644 index fc3d2e2ac91..00000000000 --- a/versioned_docs/version-2.6/longhorn/longhorn.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Longhorn - Cloud native distributed block storage for Kubernetes -shortTitle: Longhorn Storage -weight: 19 ---- - -[Longhorn](https://longhorn.io/) is a lightweight, reliable and easy-to-use distributed block storage system for Kubernetes. - -Longhorn is free, open source software. Originally developed by Rancher Labs, it is now being developed as a sandbox project of the Cloud Native Computing Foundation. It can be installed on any Kubernetes cluster with Helm, with kubectl, or with the Rancher UI. You can learn more about its architecture [here.](https://longhorn.io/docs/latest/concepts/) - -With Longhorn, you can: - -- Use Longhorn volumes as persistent storage for the distributed stateful applications in your Kubernetes cluster -- Partition your block storage into Longhorn volumes so that you can use Kubernetes volumes with or without a cloud provider -- Replicate block storage across multiple nodes and data centers to increase availability -- Store backup data in external storage such as NFS or AWS S3 -- Create cross-cluster disaster recovery volumes so that data from a primary Kubernetes cluster can be quickly recovered from backup in a second Kubernetes cluster -- Schedule recurring snapshots of a volume, and schedule recurring backups to NFS or S3-compatible secondary storage -- Restore volumes from backup -- Upgrade Longhorn without disrupting persistent volumes - -
Longhorn Dashboard
-![Longhorn Dashboard]({{}}/img/rancher/longhorn-screenshot.png) - -### Installing Longhorn with Rancher - -1. Fulfill all [Installation Requirements.](https://longhorn.io/docs/latest/deploy/install/#installation-requirements) -1. Go to the cluster where you want to install Longhorn. -1. Click **Apps & Marketplace**. -1. Click **Charts**. -1. Click **Longhorn**. -1. Optional: To customize the initial settings, click **Longhorn Default Settings** and edit the configuration. For help customizing the settings, refer to the [Longhorn documentation.](https://longhorn.io/docs/latest/references/settings/) -1. Click **Install**. - -**Result:** Longhorn is deployed in the Kubernetes cluster. - -### Accessing Longhorn from the Rancher UI - -1. Go to the cluster where Longhorn is installed. In the left navigation menu, click **Longhorn**. -1. On this page, you can edit Kubernetes resources managed by Longhorn. To view the Longhorn UI, click the **Longhorn** button in the **Overview** section. - -**Result:** You will be taken to the Longhorn UI, where you can manage your Longhorn volumes and their replicas in the Kubernetes cluster, as well as secondary backups of your Longhorn storage that may exist in another Kubernetes cluster or in S3. - -### Uninstalling Longhorn from the Rancher UI - -1. Go to the cluster where Longhorn is installed and click **Apps & Marketplace**. -1. Click **Installed Apps**. -1. Go to the `longhorn-system` namespace and check the boxes next to the `longhorn` and `longhorn-crd` apps. -1. Click **Delete,** and confirm **Delete**. - -**Result:** Longhorn is uninstalled. - -### GitHub Repository - -The Longhorn project is available [here.](https://github.com/longhorn/longhorn) - -### Documentation - -The Longhorn documentation is [here.](https://longhorn.io/docs/) - -### Architecture - -Longhorn creates a dedicated storage controller for each volume and synchronously replicates the volume across multiple replicas stored on multiple nodes. - -The storage controller and replicas are themselves orchestrated using Kubernetes. - -You can learn more about its architecture [here.](https://longhorn.io/docs/latest/concepts/) - -
Longhorn Architecture
-![Longhorn Architecture]({{}}/img/rancher/longhorn-architecture.svg) diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/advanced.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/advanced.md deleted file mode 100644 index f0b2f96fbc5..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/advanced.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Advanced Configuration -weight: 500 ---- - -### Alertmanager - -For information on configuring the Alertmanager custom resource, see [this page.](./alertmanager) - -### Prometheus - -For information on configuring the Prometheus custom resource, see [this page.](./prometheus) - -### PrometheusRules - -For information on configuring the Prometheus custom resource, see [this page.](./prometheusrules) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/alertmanager/alertmanager.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/alertmanager/alertmanager.md deleted file mode 100644 index d149d442eb8..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/alertmanager/alertmanager.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Alertmanager Configuration -weight: 1 ---- - -It is usually not necessary to directly edit the Alertmanager custom resource. For most use cases, you will only need to edit the Receivers and Routes to configure notifications. - -When Receivers and Routes are updated, the monitoring application will automatically update the Alertmanager custom resource to be consistent with those changes. - -> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../../how-monitoring-works/#3-how-alertmanager-works) - -# About the Alertmanager Custom Resource - -By default, Rancher Monitoring deploys a single Alertmanager onto a cluster that uses a default Alertmanager Config Secret. - -You may want to edit the Alertmanager custom resource if you would like to take advantage of advanced options that are not exposed in the Rancher UI forms, such as the ability to create a routing tree structure that is more than two levels deep. - -It is also possible to create more than one Alertmanager in a cluster, which may be useful if you want to implement namespace-scoped monitoring. In this case, you should manage the Alertmanager custom resources using the same underlying Alertmanager Config Secret. - -### Deeply Nested Routes - -While the Rancher UI only supports a routing tree that is two levels deep, you can configure more deeply nested routing structures by editing the Alertmanager YAML. - -### Multiple Alertmanager Replicas - -As part of the chart deployment options, you can opt to increase the number of replicas of the Alertmanager deployed onto your cluster. The replicas can all be managed using the same underlying Alertmanager Config Secret. - -This Secret should be updated or modified any time you want to: - -- Add in new notifiers or receivers -- Change the alerts that should be sent to specific notifiers or receivers -- Change the group of alerts that are sent out - -By default, you can either choose to supply an existing Alertmanager Config Secret (i.e. any Secret in the `cattle-monitoring-system` namespace) or allow Rancher Monitoring to deploy a default Alertmanager Config Secret onto your cluster. - -By default, the Alertmanager Config Secret created by Rancher will never be modified or deleted on an upgrade or uninstall of the `rancher-monitoring` chart. This restriction prevents users from losing or overwriting their alerting configuration when executing operations on the chart. - -For more information on what fields can be specified in the Alertmanager Config Secret, please look at the [Prometheus Alertmanager docs.](https://prometheus.io/docs/alerting/latest/alertmanager/) - -The full spec for the Alertmanager configuration file and what it takes in can be found [here.](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheus/prometheus.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheus/prometheus.md deleted file mode 100644 index 3a514005498..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheus/prometheus.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Prometheus Configuration -weight: 1 ---- - -It is usually not necessary to directly edit the Prometheus custom resource because the monitoring application automatically updates it based on changes to ServiceMonitors and PodMonitors. - -> This section assumes familiarity with how monitoring components work together. For more information, see [this section.](../../../how-monitoring-works/) - -# About the Prometheus Custom Resource - -The Prometheus CR defines a desired Prometheus deployment. The Prometheus Operator observes the Prometheus CR. When the CR changes, the Prometheus Operator creates `prometheus-rancher-monitoring-prometheus`, a Prometheus deployment based on the CR configuration. - -The Prometheus CR specifies details such as rules and what Alertmanagers are connected to Prometheus. Rancher builds this CR for you. - -Monitoring V2 only supports one Prometheus per cluster. However, you might want to edit the Prometheus CR if you want to limit monitoring to certain namespaces. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheusrules/prometheusrules.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheusrules/prometheusrules.md deleted file mode 100644 index a09ebe54d8e..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/advanced/prometheusrules/prometheusrules.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Configuring PrometheusRules -weight: 3 ---- - -A PrometheusRule defines a group of Prometheus alerting and/or recording rules. - -> This section assumes familiarity with how monitoring components work together. For more information, see [this section.]({{}}/rancher/v2.6/en/monitoring-alerting/how-monitoring-works) - - -### Creating PrometheusRules in the Rancher UI - -> **Prerequisite:** The monitoring application needs to be installed. - -To create rule groups in the Rancher UI, - -1. Go to the cluster where you want to create rule groups. Click **Monitoring** and click **Prometheus Rules**. -1. Click **Create**. -1. Enter a **Group Name**. -1. Configure the rules. In Rancher's UI, we expect a rule group to contain either alert rules or recording rules, but not both. For help filling out the forms, refer to the configuration options below. -1. Click **Create**. - -**Result:** Alerts can be configured to send notifications to the receiver(s). - -### About the PrometheusRule Custom Resource - -When you define a Rule (which is declared within a RuleGroup in a PrometheusRule resource), the [spec of the Rule itself](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#rule) contains labels that are used by Alertmanager to figure out which Route should receive this Alert. For example, an Alert with the label `team: front-end` will be sent to all Routes that match on that label. - -Prometheus rule files are held in PrometheusRule custom resources. A PrometheusRule allows you to define one or more RuleGroups. Each RuleGroup consists of a set of Rule objects that can each represent either an alerting or a recording rule with the following fields: - -- The name of the new alert or record -- A PromQL expression for the new alert or record -- Labels that should be attached to the alert or record that identify it (e.g. cluster name or severity) -- Annotations that encode any additional important pieces of information that need to be displayed on the notification for an alert (e.g. summary, description, message, runbook URL, etc.). This field is not required for recording rules. - -For more information on what fields can be specified, please look at the [Prometheus Operator spec.](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#prometheusrulespec) - -Use the label selector field `ruleSelector` in the Prometheus object to define the rule files that you want to be mounted into Prometheus. - -For examples, refer to the Prometheus documentation on [recording rules](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/) and [alerting rules.](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) - -# Configuration - -### Rule Group - -| Field | Description | -|-------|----------------| -| Group Name | The name of the group. Must be unique within a rules file. | -| Override Group Interval | Duration in seconds for how often rules in the group are evaluated. | - - -### Alerting Rules - -[Alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) allow you to define alert conditions based on PromQL (Prometheus Query Language) expressions and to send notifications about firing alerts to an external service. - -| Field | Description | -|-------|----------------| -| Alert Name | The name of the alert. Must be a valid label value. | -| Wait To Fire For | Duration in seconds. Alerts are considered firing once they have been returned for this long. Alerts which have not yet fired for long enough are considered pending. | -| PromQL Expression | The PromQL expression to evaluate. Prometheus will evaluate the current value of this PromQL expression on every evaluation cycle and all resultant time series will become pending/firing alerts. For more information, refer to the [Prometheus documentation](https://prometheus.io/docs/prometheus/latest/querying/basics/) or our [example PromQL expressions.](../../../expression) | -| Labels | Labels to add or overwrite for each alert. | -| Severity | When enabled, labels are attached to the alert or record that identify it by the severity level. | -| Severity Label Value | Critical, warning, or none | -| Annotations | Annotations are a set of informational labels that can be used to store longer additional information, such as alert descriptions or runbook links. A [runbook](https://en.wikipedia.org/wiki/Runbook) is a set of documentation about how to handle alerts. The annotation values can be [templated.](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/#templating) | - -### Recording Rules - -[Recording rules](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/#recording-rules) allow you to precompute frequently needed or computationally expensive PromQL (Prometheus Query Language) expressions and save their result as a new set of time series. - -| Field | Description | -|-------|----------------| -| Time Series Name | The name of the time series to output to. Must be a valid metric name. | -| PromQL Expression | The PromQL expression to evaluate. Prometheus will evaluate the current value of this PromQL expression on every evaluation cycle and the result will be recorded as a new set of time series with the metric name as given by 'record'. For more information about expressions, refer to the [Prometheus documentation](https://prometheus.io/docs/prometheus/latest/querying/basics/) or our [example PromQL expressions.](../expression) | -| Labels | Labels to add or overwrite before storing the result. | diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/configuration.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/configuration.md deleted file mode 100644 index 876031fb4d7..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/configuration.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Configuration -weight: 5 ---- - -This page captures some of the most important options for configuring Monitoring V2 in the Rancher UI. - -For information on configuring custom scrape targets and rules for Prometheus, please refer to the upstream documentation for the [Prometheus Operator.](https://github.com/prometheus-operator/prometheus-operator) Some of the most important custom resources are explained in the Prometheus Operator [design documentation.](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/design.md) The Prometheus Operator documentation can help also you set up RBAC, Thanos, or custom configuration. - -# Setting Resource Limits and Requests - -The resource requests and limits for the monitoring application can be configured when installing `rancher-monitoring`. For more information about the default limits, see [this page.](./helm-chart-options/#configuring-resource-limits-and-requests) - ->**Note:** On an idle cluster, Monitoring V2 has significantly higher CPU usage (up to 70%) as compared to Monitoring V1. To improve performance and achieve similar results as in Monitoring V1, turn off the Prometheus adapter. - -# Prometheus Configuration - -It is usually not necessary to directly edit the Prometheus custom resource. - -Instead, to configure Prometheus to scrape custom metrics, you will only need to create a new ServiceMonitor or PodMonitor to configure Prometheus to scrape additional metrics. - - -### ServiceMonitor and PodMonitor Configuration - -For details, see [this page.](./servicemonitor-podmonitor) - -### Advanced Prometheus Configuration - -For more information about directly editing the Prometheus custom resource, which may be helpful in advanced use cases, see [this page.](./advanced/prometheus) - -# Alertmanager Configuration - -The Alertmanager custom resource usually doesn't need to be edited directly. For most common use cases, you can manage alerts by updating Routes and Receivers. - -Routes and receivers are part of the configuration of the alertmanager custom resource. In the Rancher UI, Routes and Receivers are not true custom resources, but pseudo-custom resources that the Prometheus Operator uses to synchronize your configuration with the Alertmanager custom resource. When routes and receivers are updated, the monitoring application will automatically update Alertmanager to reflect those changes. - -For some advanced use cases, you may want to configure alertmanager directly. For more information, refer to [this page.](./advanced/alertmanager) - -### Receivers - -Receivers are used to set up notifications. For details on how to configure receivers, see [this page.](./receiver) -### Routes - -Routes filter notifications before they reach receivers. Each route needs to refer to a receiver that has already been configured. For details on how to configure routes, see [this page.](./route) - -### Advanced - -For more information about directly editing the Alertmanager custom resource, which may be helpful in advanced use cases, see [this page.](./advanced/alertmanager) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/examples/examples.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/examples/examples.md deleted file mode 100644 index 8cb06b633d3..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/examples/examples.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Examples -weight: 400 ---- - - -### ServiceMonitor - -An example ServiceMonitor custom resource can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml) - -### PodMonitor - -An example PodMonitor can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/user-guides/getting-started/example-app-pod-monitor.yaml) An example Prometheus resource that refers to it can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/user-guides/getting-started/prometheus-pod-monitor.yaml) - -### PrometheusRule - -For users who are familiar with Prometheus, a PrometheusRule contains the alerting and recording rules that you would normally place in a [Prometheus rule file](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/). - -For a more fine-grained application of PrometheusRules within your cluster, the ruleSelector field on a Prometheus resource allows you to select which PrometheusRules should be loaded onto Prometheus based on the labels attached to the PrometheusRules resources. - -An example PrometheusRule is on [this page.](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/alerting.md) - -### Alertmanager Config - -For an example configuration, refer to [this section.](../advanced/alertmanager/#example-alertmanager-config) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/helm-chart-options/helm-chart-options.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/helm-chart-options/helm-chart-options.md deleted file mode 100644 index 78b4e977b87..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/helm-chart-options/helm-chart-options.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Helm Chart Options -weight: 8 ---- - -- [Configuring Resource Limits and Requests](#configuring-resource-limits-and-requests) -- [Trusted CA for Notifiers](#trusted-ca-for-notifiers) -- [Additional Scrape Configurations](#additional-scrape-configurations) -- [Configuring Applications Packaged within Monitoring V2](#configuring-applications-packaged-within-monitoring-v2) -- [Increase the Replicas of Alertmanager](#increase-the-replicas-of-alertmanager) -- [Configuring the Namespace for a Persistent Grafana Dashboard](#configuring-the-namespace-for-a-persistent-grafana-dashboard) - - -# Configuring Resource Limits and Requests - -The resource requests and limits can be configured when installing `rancher-monitoring`. - -The default values are in the [values.yaml](https://github.com/rancher/charts/blob/main/charts/rancher-monitoring/values.yaml) in the `rancher-monitoring` Helm chart. - -The default values in the table below are the minimum required resource limits and requests. - -| Resource Name | Memory Limit | CPU Limit | Memory Request | CPU Request | -| ------------- | ------------ | ----------- | ---------------- | ------------------ | -| alertmanager | 500Mi | 1000m | 100Mi | 100m | -| grafana | 200Mi | 200m | 100Mi | 100m | -| kube-state-metrics subchart | 200Mi | 100m | 130Mi | 100m | -| prometheus-node-exporter subchart | 50Mi | 200m | 30Mi | 100m | -| prometheusOperator | 500Mi | 200m | 100Mi | 100m | -| prometheus | 2500Mi | 1000m | 1750Mi | 750m | -| **Total** | **3950Mi** | **2700m** | **2210Mi** | **1250m** | - -At least 50Gi storage is recommended. - - -# Trusted CA for Notifiers - -If you need to add a trusted CA to your notifier, follow these steps: - -1. Create the `cattle-monitoring-system` namespace. -1. Add your trusted CA secret to the `cattle-monitoring-system` namespace. -1. Deploy or upgrade the `rancher-monitoring` Helm chart. In the chart options, reference the secret in **Alerting > Additional Secrets**. - -**Result:** The default Alertmanager custom resource will have access to your trusted CA. - - -# Additional Scrape Configurations - -If the scrape configuration you want cannot be specified via a ServiceMonitor or PodMonitor at the moment, you can provide an `additionalScrapeConfigSecret` on deploying or upgrading `rancher-monitoring`. - -A [scrape_config section](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config) specifies a set of targets and parameters describing how to scrape them. In the general case, one scrape configuration specifies a single job. - -An example of where this might be used is with Istio. For more information, see [this section.]({{}}/rancher/v2.6/en/istio/configuration-reference/selectors-and-scrape) - - -# Configuring Applications Packaged within Monitoring v2 - -We deploy kube-state-metrics and node-exporter with monitoring v2. Node exporter are deployed as DaemonSets. In the monitoring v2 helm chart, in the values.yaml, each of the things are deployed as sub charts. - -We also deploy grafana which is not managed by prometheus. - -If you look at what the helm chart is doing like in kube-state-metrics, there are plenty more values that you can set that aren’t exposed in the top level chart. - -But in the top level chart you can add values that override values that exist in the sub chart. - -### Increase the Replicas of Alertmanager - -As part of the chart deployment options, you can opt to increase the number of replicas of the Alertmanager deployed onto your cluster. The replicas can all be managed using the same underlying Alertmanager Config Secret. For more information on the Alertmanager Config Secret, refer to [this section.](../advanced/alertmanager/#multiple-alertmanager-replicas) - -### Configuring the Namespace for a Persistent Grafana Dashboard - -To specify that you would like Grafana to watch for ConfigMaps across all namespaces, set this value in the `rancher-monitoring` Helm chart: - -``` -grafana.sidecar.dashboards.searchNamespace=ALL -``` - -Note that the RBAC roles exposed by the Monitoring chart to add Grafana Dashboards are still restricted to giving permissions for users to add dashboards in the namespace defined in `grafana.dashboards.namespace`, which defaults to `cattle-dashboards`. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/receiver/receiver.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/receiver/receiver.md deleted file mode 100644 index 86530889905..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/receiver/receiver.md +++ /dev/null @@ -1,313 +0,0 @@ ---- -title: Receiver Configuration -shortTitle: Receivers -weight: 1 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus. - -> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../how-monitoring-works/#3-how-alertmanager-works) - -- [Creating Receivers in the Rancher UI](#creating-receivers-in-the-rancher-ui) -- [Receiver Configuration](#receiver-configuration) - - [Slack](#slack) - - [Email](#email) - - [PagerDuty](#pagerduty) - - [Opsgenie](#opsgenie) - - [Webhook](#webhook) - - [Custom](#custom) - - [Teams](#teams) - - [SMS](#sms) -- [Configuring Multiple Receivers](#configuring-multiple-receivers) -- [Example Alertmanager Config](../examples/#example-alertmanager-config) -- [Example Route Config for CIS Scan Alerts](#example-route-config-for-cis-scan-alerts) -- [Trusted CA for Notifiers](#trusted-ca-for-notifiers) - -# Creating Receivers in the Rancher UI - -> **Prerequisites:** -> ->- The monitoring application needs to be installed. ->- If you configured monitoring with an existing Alertmanager Secret, it must have a format that is supported by Rancher's UI. Otherwise you will only be able to make changes based on modifying the Alertmanager Secret directly. Note: We are continuing to make enhancements to what kinds of Alertmanager Configurations we can support using the Routes and Receivers UI, so please [file an issue](https://github.com/rancher/rancher/issues/new) if you have a request for a feature enhancement. - -To create notification receivers in the Rancher UI, - - - - -1. Go to the cluster where you want to create receivers. Click **Monitoring -> Alerting -> AlertManagerConfigs**. -1. Ciick **Create**. -1. Click **Add Receiver**. -1. Enter a **Name** for the receiver. -1. Configure one or more providers for the receiver. For help filling out the forms, refer to the configuration options below. -1. Click **Create**. - - - - -1. Go to the cluster where you want to create receivers. Click **Monitoring** and click **Receiver**. -2. Enter a name for the receiver. -3. Configure one or more providers for the receiver. For help filling out the forms, refer to the configuration options below. -4. Click **Create**. - - - - -**Result:** Alerts can be configured to send notifications to the receiver(s). - -# Receiver Configuration - -The notification integrations are configured with the `receiver`, which is explained in the [Prometheus documentation.](https://prometheus.io/docs/alerting/latest/configuration/#receiver) - -### Native vs. Non-native Receivers - -By default, AlertManager provides native integration with some receivers, which are listed in [this section.](https://prometheus.io/docs/alerting/latest/configuration/#receiver) All natively supported receivers are configurable through the Rancher UI. - -For notification mechanisms not natively supported by AlertManager, integration is achieved using the [webhook receiver.](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config) A list of third-party drivers providing such integrations can be found [here.](https://prometheus.io/docs/operating/integrations/#alertmanager-webhook-receiver) Access to these drivers, and their associated integrations, is provided through the Alerting Drivers app. Once enabled, configuring non-native receivers can also be done through the Rancher UI. - -Currently the Rancher Alerting Drivers app provides access to the following integrations: -- Microsoft Teams, based on the [prom2teams](https://github.com/idealista/prom2teams) driver -- SMS, based on the [Sachet](https://github.com/messagebird/sachet) driver - -The following types of receivers can be configured in the Rancher UI: - -- Slack -- Email -- PagerDuty -- Opsgenie -- Webhook -- Custom -- Teams -- SMS - -The custom receiver option can be used to configure any receiver in YAML that cannot be configured by filling out the other forms in the Rancher UI. - -# Slack - -| Field | Type | Description | -|------|--------------|------| -| URL | String | Enter your Slack webhook URL. For instructions to create a Slack webhook, see the [Slack documentation.](https://get.slack.help/hc/en-us/articles/115005265063-Incoming-WebHooks-for-Slack) | -| Default Channel | String | Enter the name of the channel that you want to send alert notifications in the following format: `#`. | -| Proxy URL | String | Proxy for the webhook notifications. | -| Enable Send Resolved Alerts | Bool | Whether to send a follow-up notification if an alert has been resolved (e.g. [Resolved] High CPU Usage). | - -# Email - -| Field | Type | Description | -|------|--------------|------| -| Default Recipient Address | String | The email address that will receive notifications. | -| Enable Send Resolved Alerts | Bool | Whether to send a follow-up notification if an alert has been resolved (e.g. [Resolved] High CPU Usage). | - -SMTP options: - -| Field | Type | Description | -|------|--------------|------| -| Sender | String | Enter an email address available on your SMTP mail server that you want to send the notification from. | -| Host | String | Enter the IP address or hostname for your SMTP server. Example: `smtp.email.com`. | -| Use TLS | Bool | Use TLS for encryption. | -| Username | String | Enter a username to authenticate with the SMTP server. | -| Password | String | Enter a password to authenticate with the SMTP server. | - -# PagerDuty - -| Field | Type | Description | -|------|------|-------| -| Integration Type | String | `Events API v2` or `Prometheus`. | -| Default Integration Key | String | For instructions to get an integration key, see the [PagerDuty documentation.](https://www.pagerduty.com/docs/guides/prometheus-integration-guide/) | -| Proxy URL | String | Proxy for the PagerDuty notifications. | -| Enable Send Resolved Alerts | Bool | Whether to send a follow-up notification if an alert has been resolved (e.g. [Resolved] High CPU Usage). | - -# Opsgenie - -| Field | Description | -|------|-------------| -| API Key | For instructions to get an API key, refer to the [Opsgenie documentation.](https://docs.opsgenie.com/docs/api-key-management) | -| Proxy URL | Proxy for the Opsgenie notifications. | -| Enable Send Resolved Alerts | Whether to send a follow-up notification if an alert has been resolved (e.g. [Resolved] High CPU Usage). | - -Opsgenie Responders: - -| Field | Type | Description | -|-------|------|--------| -| Type | String | Schedule, Team, User, or Escalation. For more information on alert responders, refer to the [Opsgenie documentation.](https://docs.opsgenie.com/docs/alert-recipients-and-teams) | -| Send To | String | Id, Name, or Username of the Opsgenie recipient. | - -# Webhook - -| Field | Description | -|-------|--------------| -| URL | Webhook URL for the app of your choice. | -| Proxy URL | Proxy for the webhook notification. | -| Enable Send Resolved Alerts | Whether to send a follow-up notification if an alert has been resolved (e.g. [Resolved] High CPU Usage). | - - - -# Custom - -The YAML provided here will be directly appended to your receiver within the Alertmanager Config Secret. - -# Teams - -### Enabling the Teams Receiver for Rancher Managed Clusters - -The Teams receiver is not a native receiver and must be enabled before it can be used. You can enable the Teams receiver for a Rancher managed cluster by going to the Apps page and installing the rancher-alerting-drivers app with the Teams option selected. - -1. In the Rancher UI, go to the cluster where you want to install rancher-alerting-drivers and click **Apps & Marketplace**. -1. Click the **Alerting Drivers** app. -1. Click the **Helm Deploy Options** tab. -1. Select the **Teams** option and click **Install**. -1. Take note of the namespace used as it will be required in a later step. - -### Configure the Teams Receiver - -The Teams receiver can be configured by updating its ConfigMap. For example, the following is a minimal Teams receiver configuration. - -```yaml -[Microsoft Teams] -teams-instance-1: https://your-teams-webhook-url -``` - -When configuration is complete, add the receiver using the steps in [this section](#creating-receivers-in-the-rancher-ui). - -Use the example below as the URL where: - -- `ns-1` is replaced with the namespace where the `rancher-alerting-drivers` app is installed - -```yaml -url: http://rancher-alerting-drivers-prom2teams.ns-1.svc:8089/v2/teams-instance-1 -``` - - - -# SMS - -### Enabling the SMS Receiver for Rancher Managed Clusters - -The SMS receiver is not a native receiver and must be enabled before it can be used. You can enable the SMS receiver for a Rancher managed cluster by going to the Apps page and installing the rancher-alerting-drivers app with the SMS option selected. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to install `rancher-alerting-drivers` and click **Explore**. -1. In the left navigation bar, click -1. Click the **Alerting Drivers** app. -1. Click the **Helm Deploy Options** tab -1. Select the **SMS** option and click **Install**. -1. Take note of the namespace used as it will be required in a later step. - -### Configure the SMS Receiver - -The SMS receiver can be configured by updating its ConfigMap. For example, the following is a minimal SMS receiver configuration. - -```yaml -providers: - telegram: - token: 'your-token-from-telegram' - -receivers: -- name: 'telegram-receiver-1' - provider: 'telegram' - to: - - '123456789' -``` - -When configuration is complete, add the receiver using the steps in [this section](#creating-receivers-in-the-rancher-ui). - -Use the example below as the name and URL, where: - -- the name assigned to the receiver, e.g. `telegram-receiver-1`, must match the name in the `receivers.name` field in the ConfigMap, e.g. `telegram-receiver-1` -- `ns-1` in the URL is replaced with the namespace where the `rancher-alerting-drivers` app is installed - -```yaml -name: telegram-receiver-1 -url http://rancher-alerting-drivers-sachet.ns-1.svc:9876/alert -``` - - - - -# Configuring Multiple Receivers - -By editing the forms in the Rancher UI, you can set up a Receiver resource with all the information Alertmanager needs to send alerts to your notification system. - -It is also possible to send alerts to multiple notification systems. One way is to configure the Receiver using custom YAML, in which case you can add the configuration for multiple notification systems, as long as you are sure that both systems should receive the same messages. - -You can also set up multiple receivers by using the `continue` option for a route, so that the alerts sent to a receiver continue being evaluated in the next level of the routing tree, which could contain another receiver. - - -# Example Alertmanager Configs - -### Slack -To set up notifications via Slack, the following Alertmanager Config YAML can be placed into the `alertmanager.yaml` key of the Alertmanager Config Secret, where the `api_url` should be updated to use your Webhook URL from Slack: - -```yaml -route: - group_by: ['job'] - group_wait: 30s - group_interval: 5m - repeat_interval: 3h - receiver: 'slack-notifications' -receivers: -- name: 'slack-notifications' - slack_configs: - - send_resolved: true - text: '{{ template "slack.rancher.text" . }}' - api_url: -templates: -- /etc/alertmanager/config/*.tmpl -``` - -### PagerDuty -To set up notifications via PagerDuty, use the example below from the [PagerDuty documentation](https://www.pagerduty.com/docs/guides/prometheus-integration-guide/) as a guideline. This example sets up a route that captures alerts for a database service and sends them to a receiver linked to a service that will directly notify the DBAs in PagerDuty, while all other alerts will be directed to a default receiver with a different PagerDuty integration key. - -The following Alertmanager Config YAML can be placed into the `alertmanager.yaml` key of the Alertmanager Config Secret. The `service_key` should be updated to use your PagerDuty integration key and can be found as per the "Integrating with Global Event Routing" section of the PagerDuty documentation. For the full list of configuration options, refer to the [Prometheus documentation](https://prometheus.io/docs/alerting/latest/configuration/#pagerduty_config). - -```yaml -route: - group_by: [cluster] - receiver: 'pagerduty-notifications' - group_interval: 5m - routes: - - match: - service: database - receiver: 'database-notifcations' - -receivers: -- name: 'pagerduty-notifications' - pagerduty_configs: - - service_key: 'primary-integration-key' - -- name: 'database-notifcations' - pagerduty_configs: - - service_key: 'database-integration-key' -``` - -# Example Route Config for CIS Scan Alerts - -While configuring the routes for `rancher-cis-benchmark` alerts, you can specify the matching using the key-value pair `job: rancher-cis-scan`. - -For example, the following example route configuration could be used with a Slack receiver named `test-cis`: - -```yaml -spec: - receiver: test-cis - group_by: -# - string - group_wait: 30s - group_interval: 30s - repeat_interval: 30s - match: - job: rancher-cis-scan -# key: string - match_re: - {} -# key: string -``` - -For more information on enabling alerting for `rancher-cis-benchmark`, see [this section.]({{}}/rancher/v2.6/en/cis-scans/#enabling-alerting-for-rancher-cis-benchmark) - - -# Trusted CA for Notifiers - -If you need to add a trusted CA to your notifier, follow the steps in [this section.](../helm-chart-options/#trusted-ca-for-notifiers) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/route/route.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/route/route.md deleted file mode 100644 index f6c704fec71..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/route/route.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Route Configuration -shortTitle: Routes -weight: 5 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver. - -When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes. - -For more information about configuring routes, refer to the [official Alertmanager documentation.](https://www.prometheus.io/docs/alerting/latest/configuration/#route) - -> This section assumes familiarity with how monitoring components work together. For more information, see [this section.]({{}}/rancher/v2.6/en/monitoring-alerting/how-monitoring-works) - -- [Route Restrictions](#route-restrictions) -- [Route Configuration](#route-configuration) - - [Receiver](#receiver) - - [Grouping](#grouping) - - [Matching](#matching) - -# Route Restrictions - -Alertmanager proxies alerts for Prometheus based on its receivers and a routing tree that filters alerts to certain receivers based on labels. - -Alerting drivers proxy alerts for Alertmanager to non-native receivers, such as Microsoft Teams and SMS. - -In the Rancher UI for configuring routes and receivers, you can configure routing trees with one root and then a depth of one more level, for a tree with a depth of two. But if you use a `continue` route when configuring Alertmanager directly, you can make the tree deeper. - -Each receiver is for one or more notification providers. So if you know that every alert for Slack should also go to PagerDuty, you can configure both in the same receiver. - -# Route Configuration - -### Note on Labels and Annotations - -Labels should be used for identifying information that can affect the routing of notifications. Identifying information about the alert could consist of a container name, or the name of the team that should be notified. - -Annotations should be used for information that does not affect who receives the alert, such as a runbook url or error message. - - -### Receiver -The route needs to refer to a [receiver](#receiver-configuration) that has already been configured. - -### Grouping - - - - -> **Note** As of Rancher v2.6.5 `Group By` now accepts a list of strings instead of key-value pairs. See the [upstream documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#route) for details. - -| Field | Default | Description | -|-------|--------------|---------| -| Group By | N/a | List of labels to group by. Labels must not be repeated (unique list). Special label "..." (aggregate by all possible labels), if provided, must be the only element in the list. | -| Group Wait | 30s | How long to wait to buffer alerts of the same group before sending initially. | -| Group Interval | 5m | How long to wait before sending an alert that has been added to a group of alerts for which an initial notification has already been sent. | -| Repeat Interval | 4h | How long to wait before re-sending a given alert that has already been sent. | - - - - -| Field | Default | Description | -|-------|--------------|---------| -| Group By | N/a | The labels by which incoming alerts are grouped together. For example, `[ group_by: '[' , ... ']' ]` Multiple alerts coming in for labels such as `cluster=A` and `alertname=LatencyHigh` can be batched into a single group. To aggregate by all possible labels, use the special value `'...'` as the sole label name, for example: `group_by: ['...']` Grouping by `...` effectively disables aggregation entirely, passing through all alerts as-is. This is unlikely to be what you want, unless you have a very low alert volume or your upstream notification system performs its own grouping. | -| Group Wait | 30s | How long to wait to buffer alerts of the same group before sending initially. | -| Group Interval | 5m | How long to wait before sending an alert that has been added to a group of alerts for which an initial notification has already been sent. | -| Repeat Interval | 4h | How long to wait before re-sending a given alert that has already been sent. | - - - - -### Matching - -The **Match** field refers to a set of equality matchers used to identify which alerts to send to a given Route based on labels defined on that alert. When you add key-value pairs to the Rancher UI, they correspond to the YAML in this format: - -```yaml -match: - [ : , ... ] -``` - -The **Match Regex** field refers to a set of regex-matchers used to identify which alerts to send to a given Route based on labels defined on that alert. When you add key-value pairs in the Rancher UI, they correspond to the YAML in this format: - -```yaml -match_re: - [ : , ... ] -``` diff --git a/versioned_docs/version-2.6/monitoring-alerting/configuration/servicemonitor-podmonitor/servicemonitor-podmonitor.md b/versioned_docs/version-2.6/monitoring-alerting/configuration/servicemonitor-podmonitor/servicemonitor-podmonitor.md deleted file mode 100644 index d2f848b6e67..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/configuration/servicemonitor-podmonitor/servicemonitor-podmonitor.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: ServiceMonitor and PodMonitor Configuration -shortTitle: ServiceMonitors and PodMonitors -weight: 7 ---- - -ServiceMonitors and PodMonitors are both pseudo-CRDs that map the scrape configuration of the Prometheus custom resource. - -These configuration objects declaratively specify the endpoints that Prometheus will scrape metrics from. - -ServiceMonitors are more commonly used than PodMonitors, and we recommend them for most use cases. - -> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../how-monitoring-works/) - -### ServiceMonitors - -This pseudo-CRD maps to a section of the Prometheus custom resource configuration. It declaratively specifies how groups of Kubernetes services should be monitored. - -When a ServiceMonitor is created, the Prometheus Operator updates the Prometheus scrape configuration to include the ServiceMonitor configuration. Then Prometheus begins scraping metrics from the endpoint defined in the ServiceMonitor. - -Any Services in your cluster that match the labels located within the ServiceMonitor `selector` field will be monitored based on the `endpoints` specified on the ServiceMonitor. For more information on what fields can be specified, please look at the [spec](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#servicemonitor) provided by Prometheus Operator. - -For more information about how ServiceMonitors work, refer to the [Prometheus Operator documentation.](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/running-exporters.md) - -### PodMonitors - -This pseudo-CRD maps to a section of the Prometheus custom resource configuration. It declaratively specifies how group of pods should be monitored. - -When a PodMonitor is created, the Prometheus Operator updates the Prometheus scrape configuration to include the PodMonitor configuration. Then Prometheus begins scraping metrics from the endpoint defined in the PodMonitor. - -Any Pods in your cluster that match the labels located within the PodMonitor `selector` field will be monitored based on the `podMetricsEndpoints` specified on the PodMonitor. For more information on what fields can be specified, please look at the [spec](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#podmonitorspec) provided by Prometheus Operator. diff --git a/versioned_docs/version-2.6/monitoring-alerting/dashboards/dashboards.md b/versioned_docs/version-2.6/monitoring-alerting/dashboards/dashboards.md deleted file mode 100644 index a6882eaba28..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/dashboards/dashboards.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Built-in Dashboards -weight: 3 ---- - -- [Grafana UI](#grafana-ui) -- [Alertmanager UI](#alertmanager-ui) -- [Prometheus UI](#prometheus-ui) - -# Grafana UI - -[Grafana](https://grafana.com/grafana/) allows you to query, visualize, alert on and understand your metrics no matter where they are stored. Create, explore, and share dashboards with your team and foster a data driven culture. - -To see the default dashboards for time series data visualization, go to the Grafana UI. - -### Customizing Grafana - -To view and customize the PromQL queries powering the Grafana dashboard, see [this page.](../guides/customize-grafana) - -### Persistent Grafana Dashboards - -To create a persistent Grafana dashboard, see [this page.](../guides/persist-grafana) - -### Access to Grafana - -For information about role-based access control for Grafana, see [this section.](../rbac/#role-based-access-control-for-grafana) - - -# Alertmanager UI - -When `rancher-monitoring` is installed, the Prometheus Alertmanager UI is deployed, allowing you to view your alerts and the current Alertmanager configuration. - -> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../how-monitoring-works/#how-alertmanager-works) - - -### Accessing the Alertmanager UI - -The Alertmanager UI lets you see the most recently fired alerts. - -> **Prerequisite:** The `rancher-monitoring` application must be installed. - -To see the Alertmanager UI, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the Alertmanager UI, click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Alertmanager**. - -**Result:** The Alertmanager UI opens in a new tab. For help with configuration, refer to the [official Alertmanager documentation.](https://prometheus.io/docs/alerting/latest/alertmanager/) - -For more information on configuring Alertmanager in Rancher, see [this page.](../configuration/advanced/alertmanager) - -
The Alertmanager UI
-![Alertmanager UI]({{}}/img/rancher/alertmanager-ui.png) - - -### Viewing Default Alerts - -To see alerts that are fired by default, go to the Alertmanager UI and click **Expand all groups**. - - -# Prometheus UI - -By default, the [kube-state-metrics service](https://github.com/kubernetes/kube-state-metrics) provides a wealth of information about CPU and memory utilization to the monitoring application. These metrics cover Kubernetes resources across namespaces. This means that in order to see resource metrics for a service, you don't need to create a new ServiceMonitor for it. Because the data is already in the time series database, you can go to the Prometheus UI and run a PromQL query to get the information. The same query can be used to configure a Grafana dashboard to show a graph of those metrics over time. - -To see the Prometheus UI, install `rancher-monitoring`. Then: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the Prometheus UI and click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Prometheus Graph**. - -
Prometheus Graph UI
-![Prometheus Graph UI]({{}}/img/rancher/prometheus-graph-ui.png) - -### Viewing the Prometheus Targets - -To see what services you are monitoring, you will need to see your targets. Targets are set up by ServiceMonitors and PodMonitors as sources to scrape metrics from. You won't need to directly edit targets, but the Prometheus UI can be useful for giving you an overview of all of the sources of metrics that are being scraped. - -To see the Prometheus Targets, install `rancher-monitoring`. Then: - - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the Prometheus targets and click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Prometheus Targets**. - -
Targets in the Prometheus UI
-![Prometheus Targets UI]({{}}/img/rancher/prometheus-targets-ui.png) - -### Viewing the PrometheusRules - -When you define a Rule (which is declared within a RuleGroup in a PrometheusRule resource), the [spec of the Rule itself](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#rule) contains labels that are used by Alertmanager to figure out which Route should receive a certain Alert. - -To see the PrometheusRules, install `rancher-monitoring`. Then: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the visualizations and click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Prometheus Rules**. - -You can also see the rules in the Prometheus UI: - -
Rules in the Prometheus UI
-![PrometheusRules UI]({{}}/img/rancher/prometheus-rules-ui.png) - -For more information on configuring PrometheusRules in Rancher, see [this page.](../configuration/advanced/prometheusrules) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/expression/expression.md b/versioned_docs/version-2.6/monitoring-alerting/expression/expression.md deleted file mode 100644 index 60eb9fc2b92..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/expression/expression.md +++ /dev/null @@ -1,428 +0,0 @@ ---- -title: PromQL Expression Reference -weight: 6 ---- - -The PromQL expressions in this doc can be used to configure alerts. - -For more information about querying the Prometheus time series database, refer to the official [Prometheus documentation.](https://prometheus.io/docs/prometheus/latest/querying/basics/) - - - -- [Cluster Metrics](#cluster-metrics) - - [Cluster CPU Utilization](#cluster-cpu-utilization) - - [Cluster Load Average](#cluster-load-average) - - [Cluster Memory Utilization](#cluster-memory-utilization) - - [Cluster Disk Utilization](#cluster-disk-utilization) - - [Cluster Disk I/O](#cluster-disk-i-o) - - [Cluster Network Packets](#cluster-network-packets) - - [Cluster Network I/O](#cluster-network-i-o) -- [Node Metrics](#node-metrics) - - [Node CPU Utilization](#node-cpu-utilization) - - [Node Load Average](#node-load-average) - - [Node Memory Utilization](#node-memory-utilization) - - [Node Disk Utilization](#node-disk-utilization) - - [Node Disk I/O](#node-disk-i-o) - - [Node Network Packets](#node-network-packets) - - [Node Network I/O](#node-network-i-o) -- [Etcd Metrics](#etcd-metrics) - - [Etcd Has a Leader](#etcd-has-a-leader) - - [Number of Times the Leader Changes](#number-of-times-the-leader-changes) - - [Number of Failed Proposals](#number-of-failed-proposals) - - [GRPC Client Traffic](#grpc-client-traffic) - - [Peer Traffic](#peer-traffic) - - [DB Size](#db-size) - - [Active Streams](#active-streams) - - [Raft Proposals](#raft-proposals) - - [RPC Rate](#rpc-rate) - - [Disk Operations](#disk-operations) - - [Disk Sync Duration](#disk-sync-duration) -- [Kubernetes Components Metrics](#kubernetes-components-metrics) - - [API Server Request Latency](#api-server-request-latency) - - [API Server Request Rate](#api-server-request-rate) - - [Scheduling Failed Pods](#scheduling-failed-pods) - - [Controller Manager Queue Depth](#controller-manager-queue-depth) - - [Scheduler E2E Scheduling Latency](#scheduler-e2e-scheduling-latency) - - [Scheduler Preemption Attempts](#scheduler-preemption-attempts) - - [Ingress Controller Connections](#ingress-controller-connections) - - [Ingress Controller Request Process Time](#ingress-controller-request-process-time) -- [Rancher Logging Metrics](#rancher-logging-metrics) - - [Fluentd Buffer Queue Rate](#fluentd-buffer-queue-rate) - - [Fluentd Input Rate](#fluentd-input-rate) - - [Fluentd Output Errors Rate](#fluentd-output-errors-rate) - - [Fluentd Output Rate](#fluentd-output-rate) -- [Workload Metrics](#workload-metrics) - - [Workload CPU Utilization](#workload-cpu-utilization) - - [Workload Memory Utilization](#workload-memory-utilization) - - [Workload Network Packets](#workload-network-packets) - - [Workload Network I/O](#workload-network-i-o) - - [Workload Disk I/O](#workload-disk-i-o) -- [Pod Metrics](#pod-metrics) - - [Pod CPU Utilization](#pod-cpu-utilization) - - [Pod Memory Utilization](#pod-memory-utilization) - - [Pod Network Packets](#pod-network-packets) - - [Pod Network I/O](#pod-network-i-o) - - [Pod Disk I/O](#pod-disk-i-o) -- [Container Metrics](#container-metrics) - - [Container CPU Utilization](#container-cpu-utilization) - - [Container Memory Utilization](#container-memory-utilization) - - [Container Disk I/O](#container-disk-i-o) - - - -# Cluster Metrics - -### Cluster CPU Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `1 - (avg(irate(node_cpu_seconds_total{mode="idle"}[5m])) by (instance))` | -| Summary | `1 - (avg(irate(node_cpu_seconds_total{mode="idle"}[5m])))` | - -### Cluster Load Average - -| Catalog | Expression | -| --- | --- | -| Detail |
load1`sum(node_load1) by (instance) / count(node_cpu_seconds_total{mode="system"}) by (instance)`
load5`sum(node_load5) by (instance) / count(node_cpu_seconds_total{mode="system"}) by (instance)`
load15`sum(node_load15) by (instance) / count(node_cpu_seconds_total{mode="system"}) by (instance)`
| -| Summary |
load1`sum(node_load1) by (instance) / count(node_cpu_seconds_total{mode="system"})`
load5`sum(node_load5) by (instance) / count(node_cpu_seconds_total{mode="system"})`
load15`sum(node_load15) by (instance) / count(node_cpu_seconds_total{mode="system"})`
| - -### Cluster Memory Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `1 - sum(node_memory_MemAvailable_bytes) by (instance) / sum(node_memory_MemTotal_bytes) by (instance)` | -| Summary | `1 - sum(node_memory_MemAvailable_bytes) / sum(node_memory_MemTotal_bytes)` | - -### Cluster Disk Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `(sum(node_filesystem_size_bytes{device!="rootfs"}) by (instance) - sum(node_filesystem_free_bytes{device!="rootfs"}) by (instance)) / sum(node_filesystem_size_bytes{device!="rootfs"}) by (instance)` | -| Summary | `(sum(node_filesystem_size_bytes{device!="rootfs"}) - sum(node_filesystem_free_bytes{device!="rootfs"})) / sum(node_filesystem_size_bytes{device!="rootfs"})` | - -### Cluster Disk I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
read`sum(rate(node_disk_read_bytes_total[5m])) by (instance)`
written`sum(rate(node_disk_written_bytes_total[5m])) by (instance)`
| -| Summary |
read`sum(rate(node_disk_read_bytes_total[5m]))`
written`sum(rate(node_disk_written_bytes_total[5m]))`
| - -### Cluster Network Packets - -| Catalog | Expression | -| --- | --- | -| Detail |
receive-droppedsum(rate(node_network_receive_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
receive-errssum(rate(node_network_receive_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
receive-packetssum(rate(node_network_receive_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
transmit-droppedsum(rate(node_network_transmit_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
transmit-errssum(rate(node_network_transmit_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
transmit-packetssum(rate(node_network_transmit_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
| -| Summary |
receive-droppedsum(rate(node_network_receive_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
receive-errssum(rate(node_network_receive_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
receive-packetssum(rate(node_network_receive_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
transmit-droppedsum(rate(node_network_transmit_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
transmit-errssum(rate(node_network_transmit_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
transmit-packetssum(rate(node_network_transmit_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
| - -### Cluster Network I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
receivesum(rate(node_network_receive_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
transmitsum(rate(node_network_transmit_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m])) by (instance)
| -| Summary |
receivesum(rate(node_network_receive_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
transmitsum(rate(node_network_transmit_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*"}[5m]))
| - -# Node Metrics - -### Node CPU Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `avg(irate(node_cpu_seconds_total{mode!="idle", instance=~"$instance"}[5m])) by (mode)` | -| Summary | `1 - (avg(irate(node_cpu_seconds_total{mode="idle", instance=~"$instance"}[5m])))` | - -### Node Load Average - -| Catalog | Expression | -| --- | --- | -| Detail |
load1`sum(node_load1{instance=~"$instance"}) / count(node_cpu_seconds_total{mode="system",instance=~"$instance"})`
load5`sum(node_load5{instance=~"$instance"}) / count(node_cpu_seconds_total{mode="system",instance=~"$instance"})`
load15`sum(node_load15{instance=~"$instance"}) / count(node_cpu_seconds_total{mode="system",instance=~"$instance"})`
| -| Summary |
load1`sum(node_load1{instance=~"$instance"}) / count(node_cpu_seconds_total{mode="system",instance=~"$instance"})`
load5`sum(node_load5{instance=~"$instance"}) / count(node_cpu_seconds_total{mode="system",instance=~"$instance"})`
load15`sum(node_load15{instance=~"$instance"}) / count(node_cpu_seconds_total{mode="system",instance=~"$instance"})`
| - -### Node Memory Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `1 - sum(node_memory_MemAvailable_bytes{instance=~"$instance"}) / sum(node_memory_MemTotal_bytes{instance=~"$instance"})` | -| Summary | `1 - sum(node_memory_MemAvailable_bytes{instance=~"$instance"}) / sum(node_memory_MemTotal_bytes{instance=~"$instance"}) ` | - -### Node Disk Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `(sum(node_filesystem_size_bytes{device!="rootfs",instance=~"$instance"}) by (device) - sum(node_filesystem_free_bytes{device!="rootfs",instance=~"$instance"}) by (device)) / sum(node_filesystem_size_bytes{device!="rootfs",instance=~"$instance"}) by (device)` | -| Summary | `(sum(node_filesystem_size_bytes{device!="rootfs",instance=~"$instance"}) - sum(node_filesystem_free_bytes{device!="rootfs",instance=~"$instance"})) / sum(node_filesystem_size_bytes{device!="rootfs",instance=~"$instance"})` | - -### Node Disk I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
read`sum(rate(node_disk_read_bytes_total{instance=~"$instance"}[5m]))`
written`sum(rate(node_disk_written_bytes_total{instance=~"$instance"}[5m]))`
| -| Summary |
read`sum(rate(node_disk_read_bytes_total{instance=~"$instance"}[5m]))`
written`sum(rate(node_disk_written_bytes_total{instance=~"$instance"}[5m]))`
| - -### Node Network Packets - -| Catalog | Expression | -| --- | --- | -| Detail |
receive-droppedsum(rate(node_network_receive_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
receive-errssum(rate(node_network_receive_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
receive-packetssum(rate(node_network_receive_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
transmit-droppedsum(rate(node_network_transmit_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
transmit-errssum(rate(node_network_transmit_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
transmit-packetssum(rate(node_network_transmit_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
| -| Summary |
receive-droppedsum(rate(node_network_receive_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
receive-errssum(rate(node_network_receive_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
receive-packetssum(rate(node_network_receive_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
transmit-droppedsum(rate(node_network_transmit_drop_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
transmit-errssum(rate(node_network_transmit_errs_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
transmit-packetssum(rate(node_network_transmit_packets_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
| - -### Node Network I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
receivesum(rate(node_network_receive_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
transmitsum(rate(node_network_transmit_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m])) by (device)
| -| Summary |
receivesum(rate(node_network_receive_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
transmitsum(rate(node_network_transmit_bytes_total{device!~"lo | veth.* | docker.* | flannel.* | cali.* | cbr.*",instance=~"$instance"}[5m]))
| - -# Etcd Metrics - -### Etcd Has a Leader - -`max(etcd_server_has_leader)` - -### Number of Times the Leader Changes - -`max(etcd_server_leader_changes_seen_total)` - -### Number of Failed Proposals - -`sum(etcd_server_proposals_failed_total)` - -### GRPC Client Traffic - -| Catalog | Expression | -| --- | --- | -| Detail |
in`sum(rate(etcd_network_client_grpc_received_bytes_total[5m])) by (instance)`
out`sum(rate(etcd_network_client_grpc_sent_bytes_total[5m])) by (instance)`
| -| Summary |
in`sum(rate(etcd_network_client_grpc_received_bytes_total[5m]))`
out`sum(rate(etcd_network_client_grpc_sent_bytes_total[5m]))`
| - -### Peer Traffic - -| Catalog | Expression | -| --- | --- | -| Detail |
in`sum(rate(etcd_network_peer_received_bytes_total[5m])) by (instance)`
out`sum(rate(etcd_network_peer_sent_bytes_total[5m])) by (instance)`
| -| Summary |
in`sum(rate(etcd_network_peer_received_bytes_total[5m]))`
out`sum(rate(etcd_network_peer_sent_bytes_total[5m]))`
| - -### DB Size - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(etcd_debugging_mvcc_db_total_size_in_bytes) by (instance)` | -| Summary | `sum(etcd_debugging_mvcc_db_total_size_in_bytes)` | - -### Active Streams - -| Catalog | Expression | -| --- | --- | -| Detail |
lease-watch`sum(grpc_server_started_total{grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}) by (instance) - sum(grpc_server_handled_total{grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}) by (instance)`
watch`sum(grpc_server_started_total{grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}) by (instance) - sum(grpc_server_handled_total{grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}) by (instance)`
| -| Summary |
lease-watch`sum(grpc_server_started_total{grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}) - sum(grpc_server_handled_total{grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"})`
watch`sum(grpc_server_started_total{grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}) - sum(grpc_server_handled_total{grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"})`
| - -### Raft Proposals - -| Catalog | Expression | -| --- | --- | -| Detail |
applied`sum(increase(etcd_server_proposals_applied_total[5m])) by (instance)`
committed`sum(increase(etcd_server_proposals_committed_total[5m])) by (instance)`
pending`sum(increase(etcd_server_proposals_pending[5m])) by (instance)`
failed`sum(increase(etcd_server_proposals_failed_total[5m])) by (instance)`
| -| Summary |
applied`sum(increase(etcd_server_proposals_applied_total[5m]))`
committed`sum(increase(etcd_server_proposals_committed_total[5m]))`
pending`sum(increase(etcd_server_proposals_pending[5m]))`
failed`sum(increase(etcd_server_proposals_failed_total[5m]))`
| - -### RPC Rate - -| Catalog | Expression | -| --- | --- | -| Detail |
total`sum(rate(grpc_server_started_total{grpc_type="unary"}[5m])) by (instance)`
fail`sum(rate(grpc_server_handled_total{grpc_type="unary",grpc_code!="OK"}[5m])) by (instance)`
| -| Summary |
total`sum(rate(grpc_server_started_total{grpc_type="unary"}[5m]))`
fail`sum(rate(grpc_server_handled_total{grpc_type="unary",grpc_code!="OK"}[5m]))`
| - -### Disk Operations - -| Catalog | Expression | -| --- | --- | -| Detail |
commit-called-by-backend`sum(rate(etcd_disk_backend_commit_duration_seconds_sum[1m])) by (instance)`
fsync-called-by-wal`sum(rate(etcd_disk_wal_fsync_duration_seconds_sum[1m])) by (instance)`
| -| Summary |
commit-called-by-backend`sum(rate(etcd_disk_backend_commit_duration_seconds_sum[1m]))`
fsync-called-by-wal`sum(rate(etcd_disk_wal_fsync_duration_seconds_sum[1m]))`
| - -### Disk Sync Duration - -| Catalog | Expression | -| --- | --- | -| Detail |
wal`histogram_quantile(0.99, sum(rate(etcd_disk_wal_fsync_duration_seconds_bucket[5m])) by (instance, le))`
db`histogram_quantile(0.99, sum(rate(etcd_disk_backend_commit_duration_seconds_bucket[5m])) by (instance, le))`
| -| Summary |
wal`sum(histogram_quantile(0.99, sum(rate(etcd_disk_wal_fsync_duration_seconds_bucket[5m])) by (instance, le)))`
db`sum(histogram_quantile(0.99, sum(rate(etcd_disk_backend_commit_duration_seconds_bucket[5m])) by (instance, le)))`
| - -# Kubernetes Components Metrics - -### API Server Request Latency - -| Catalog | Expression | -| --- | --- | -| Detail | `avg(apiserver_request_latencies_sum / apiserver_request_latencies_count) by (instance, verb) /1e+06` | -| Summary | `avg(apiserver_request_latencies_sum / apiserver_request_latencies_count) by (instance) /1e+06` | - -### API Server Request Rate - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(rate(apiserver_request_count[5m])) by (instance, code)` | -| Summary | `sum(rate(apiserver_request_count[5m])) by (instance)` | - -### Scheduling Failed Pods - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(kube_pod_status_scheduled{condition="false"})` | -| Summary | `sum(kube_pod_status_scheduled{condition="false"})` | - -### Controller Manager Queue Depth - -| Catalog | Expression | -| --- | --- | -| Detail |
volumes`sum(volumes_depth) by instance`
deployment`sum(deployment_depth) by instance`
replicaset`sum(replicaset_depth) by instance`
service`sum(service_depth) by instance`
serviceaccount`sum(serviceaccount_depth) by instance`
endpoint`sum(endpoint_depth) by instance`
daemonset`sum(daemonset_depth) by instance`
statefulset`sum(statefulset_depth) by instance`
replicationmanager`sum(replicationmanager_depth) by instance`
| -| Summary |
volumes`sum(volumes_depth)`
deployment`sum(deployment_depth)`
replicaset`sum(replicaset_depth)`
service`sum(service_depth)`
serviceaccount`sum(serviceaccount_depth)`
endpoint`sum(endpoint_depth)`
daemonset`sum(daemonset_depth)`
statefulset`sum(statefulset_depth)`
replicationmanager`sum(replicationmanager_depth)`
| - -### Scheduler E2E Scheduling Latency - -| Catalog | Expression | -| --- | --- | -| Detail | `histogram_quantile(0.99, sum(scheduler_e2e_scheduling_latency_microseconds_bucket) by (le, instance)) / 1e+06` | -| Summary | `sum(histogram_quantile(0.99, sum(scheduler_e2e_scheduling_latency_microseconds_bucket) by (le, instance)) / 1e+06)` | - -### Scheduler Preemption Attempts - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(rate(scheduler_total_preemption_attempts[5m])) by (instance)` | -| Summary | `sum(rate(scheduler_total_preemption_attempts[5m]))` | - -### Ingress Controller Connections - -| Catalog | Expression | -| --- | --- | -| Detail |
reading`sum(nginx_ingress_controller_nginx_process_connections{state="reading"}) by (instance)`
waiting`sum(nginx_ingress_controller_nginx_process_connections{state="waiting"}) by (instance)`
writing`sum(nginx_ingress_controller_nginx_process_connections{state="writing"}) by (instance)`
accepted`sum(ceil(increase(nginx_ingress_controller_nginx_process_connections_total{state="accepted"}[5m]))) by (instance)`
active`sum(ceil(increase(nginx_ingress_controller_nginx_process_connections_total{state="active"}[5m]))) by (instance)`
handled`sum(ceil(increase(nginx_ingress_controller_nginx_process_connections_total{state="handled"}[5m]))) by (instance)`
| -| Summary |
reading`sum(nginx_ingress_controller_nginx_process_connections{state="reading"})`
waiting`sum(nginx_ingress_controller_nginx_process_connections{state="waiting"})`
writing`sum(nginx_ingress_controller_nginx_process_connections{state="writing"})`
accepted`sum(ceil(increase(nginx_ingress_controller_nginx_process_connections_total{state="accepted"}[5m])))`
active`sum(ceil(increase(nginx_ingress_controller_nginx_process_connections_total{state="active"}[5m])))`
handled`sum(ceil(increase(nginx_ingress_controller_nginx_process_connections_total{state="handled"}[5m])))`
| - -### Ingress Controller Request Process Time - -| Catalog | Expression | -| --- | --- | -| Detail | `topk(10, histogram_quantile(0.95,sum by (le, host, path)(rate(nginx_ingress_controller_request_duration_seconds_bucket{host!="_"}[5m]))))` | -| Summary | `topk(10, histogram_quantile(0.95,sum by (le, host)(rate(nginx_ingress_controller_request_duration_seconds_bucket{host!="_"}[5m]))))` | - -# Rancher Logging Metrics - - -### Fluentd Buffer Queue Rate - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(rate(fluentd_output_status_buffer_queue_length[5m])) by (instance)` | -| Summary | `sum(rate(fluentd_output_status_buffer_queue_length[5m]))` | - -### Fluentd Input Rate - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(rate(fluentd_input_status_num_records_total[5m])) by (instance)` | -| Summary | `sum(rate(fluentd_input_status_num_records_total[5m]))` | - -### Fluentd Output Errors Rate - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(rate(fluentd_output_status_num_errors[5m])) by (type)` | -| Summary | `sum(rate(fluentd_output_status_num_errors[5m]))` | - -### Fluentd Output Rate - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(rate(fluentd_output_status_num_records_total[5m])) by (instance)` | -| Summary | `sum(rate(fluentd_output_status_num_records_total[5m]))` | - -# Workload Metrics - -### Workload CPU Utilization - -| Catalog | Expression | -| --- | --- | -| Detail |
cfs throttled seconds`sum(rate(container_cpu_cfs_throttled_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
user seconds`sum(rate(container_cpu_user_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
system seconds`sum(rate(container_cpu_system_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
usage seconds`sum(rate(container_cpu_usage_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
| -| Summary |
cfs throttled seconds`sum(rate(container_cpu_cfs_throttled_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
user seconds`sum(rate(container_cpu_user_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
system seconds`sum(rate(container_cpu_system_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
usage seconds`sum(rate(container_cpu_usage_seconds_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
| - -### Workload Memory Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(container_memory_working_set_bytes{namespace="$namespace",pod_name=~"$podName", container_name!=""}) by (pod_name)` | -| Summary | `sum(container_memory_working_set_bytes{namespace="$namespace",pod_name=~"$podName", container_name!=""})` | - -### Workload Network Packets - -| Catalog | Expression | -| --- | --- | -| Detail |
receive-packets`sum(rate(container_network_receive_packets_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
receive-dropped`sum(rate(container_network_receive_packets_dropped_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
receive-errors`sum(rate(container_network_receive_errors_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
transmit-packets`sum(rate(container_network_transmit_packets_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
transmit-dropped`sum(rate(container_network_transmit_packets_dropped_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
transmit-errors`sum(rate(container_network_transmit_errors_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
| -| Summary |
receive-packets`sum(rate(container_network_receive_packets_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
receive-dropped`sum(rate(container_network_receive_packets_dropped_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
receive-errors`sum(rate(container_network_receive_errors_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
transmit-packets`sum(rate(container_network_transmit_packets_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
transmit-dropped`sum(rate(container_network_transmit_packets_dropped_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
transmit-errors`sum(rate(container_network_transmit_errors_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
| - -### Workload Network I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
receive`sum(rate(container_network_receive_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
transmit`sum(rate(container_network_transmit_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
| -| Summary |
receive`sum(rate(container_network_receive_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
transmit`sum(rate(container_network_transmit_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
| - -### Workload Disk I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
read`sum(rate(container_fs_reads_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
write`sum(rate(container_fs_writes_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m])) by (pod_name)`
| -| Summary |
read`sum(rate(container_fs_reads_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
write`sum(rate(container_fs_writes_bytes_total{namespace="$namespace",pod_name=~"$podName",container_name!=""}[5m]))`
| - -# Pod Metrics - -### Pod CPU Utilization - -| Catalog | Expression | -| --- | --- | -| Detail |
cfs throttled seconds`sum(rate(container_cpu_cfs_throttled_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m])) by (container_name)`
usage seconds`sum(rate(container_cpu_usage_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m])) by (container_name)`
system seconds`sum(rate(container_cpu_system_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m])) by (container_name)`
user seconds`sum(rate(container_cpu_user_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m])) by (container_name)`
| -| Summary |
cfs throttled seconds`sum(rate(container_cpu_cfs_throttled_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m]))`
usage seconds`sum(rate(container_cpu_usage_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m]))`
system seconds`sum(rate(container_cpu_system_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m]))`
user seconds`sum(rate(container_cpu_user_seconds_total{container_name!="POD",namespace="$namespace",pod_name="$podName", container_name!=""}[5m]))`
| - -### Pod Memory Utilization - -| Catalog | Expression | -| --- | --- | -| Detail | `sum(container_memory_working_set_bytes{container_name!="POD",namespace="$namespace",pod_name="$podName",container_name!=""}) by (container_name)` | -| Summary | `sum(container_memory_working_set_bytes{container_name!="POD",namespace="$namespace",pod_name="$podName",container_name!=""})` | - -### Pod Network Packets - -| Catalog | Expression | -| --- | --- | -| Detail |
receive-packets`sum(rate(container_network_receive_packets_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
receive-dropped`sum(rate(container_network_receive_packets_dropped_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
receive-errors`sum(rate(container_network_receive_errors_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit-packets`sum(rate(container_network_transmit_packets_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit-dropped`sum(rate(container_network_transmit_packets_dropped_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit-errors`sum(rate(container_network_transmit_errors_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
| -| Summary |
receive-packets`sum(rate(container_network_receive_packets_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
receive-dropped`sum(rate(container_network_receive_packets_dropped_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
receive-errors`sum(rate(container_network_receive_errors_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit-packets`sum(rate(container_network_transmit_packets_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit-dropped`sum(rate(container_network_transmit_packets_dropped_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit-errors`sum(rate(container_network_transmit_errors_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
| - -### Pod Network I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
receive`sum(rate(container_network_receive_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit`sum(rate(container_network_transmit_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
| -| Summary |
receive`sum(rate(container_network_receive_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
transmit`sum(rate(container_network_transmit_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
| - -### Pod Disk I/O - -| Catalog | Expression | -| --- | --- | -| Detail |
read`sum(rate(container_fs_reads_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m])) by (container_name)`
write`sum(rate(container_fs_writes_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m])) by (container_name)`
| -| Summary |
read`sum(rate(container_fs_reads_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
write`sum(rate(container_fs_writes_bytes_total{namespace="$namespace",pod_name="$podName",container_name!=""}[5m]))`
| - -# Container Metrics - -### Container CPU Utilization - -| Catalog | Expression | -| --- | --- | -| cfs throttled seconds | `sum(rate(container_cpu_cfs_throttled_seconds_total{namespace="$namespace",pod_name="$podName",container_name="$containerName"}[5m]))` | -| usage seconds | `sum(rate(container_cpu_usage_seconds_total{namespace="$namespace",pod_name="$podName",container_name="$containerName"}[5m]))` | -| system seconds | `sum(rate(container_cpu_system_seconds_total{namespace="$namespace",pod_name="$podName",container_name="$containerName"}[5m]))` | -| user seconds | `sum(rate(container_cpu_user_seconds_total{namespace="$namespace",pod_name="$podName",container_name="$containerName"}[5m]))` | - -### Container Memory Utilization - -`sum(container_memory_working_set_bytes{namespace="$namespace",pod_name="$podName",container_name="$containerName"})` - -### Container Disk I/O - -| Catalog | Expression | -| --- | --- | -| read | `sum(rate(container_fs_reads_bytes_total{namespace="$namespace",pod_name="$podName",container_name="$containerName"}[5m]))` | -| write | `sum(rate(container_fs_writes_bytes_total{namespace="$namespace",pod_name="$podName",container_name="$containerName"}[5m]))` | diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/customize-grafana/customize-grafana.md b/versioned_docs/version-2.6/monitoring-alerting/guides/customize-grafana/customize-grafana.md deleted file mode 100644 index c6154f6ff50..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/customize-grafana/customize-grafana.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Customizing Grafana Dashboards -weight: 5 ---- - -In this section, you'll learn how to customize the Grafana dashboard to show metrics that apply to a certain container. - -### Prerequisites - -Before you can customize a Grafana dashboard, the `rancher-monitoring` application must be installed. - -To see the links to the external monitoring UIs, including Grafana dashboards, you will need at least a [project-member role.]({{}}/rancher/v2.6/en/monitoring-alerting/rbac/#users-with-rancher-cluster-manager-based-permissions) - -### Signing in to Grafana - -1. In the Rancher UI, go to the cluster that has the dashboard you want to customize. -1. In the left navigation menu, click **Monitoring.** -1. Click **Grafana.** The Grafana dashboard should open in a new tab. -1. Go to the log in icon in the lower left corner and click **Sign In.** -1. Log in to Grafana. The default Admin username and password for the Grafana instance is `admin/prom-operator`. (Regardless of who has the password, cluster administrator permission in Rancher is still required access the Grafana instance.) Alternative credentials can also be supplied on deploying or upgrading the chart. - - -### Getting the PromQL Query Powering a Grafana Panel - -For any panel, you can click the title and click **Explore** to get the PromQL queries powering the graphic. - -For this example, we would like to get the CPU usage for the Alertmanager container, so we click **CPU Utilization > Inspect.** - -The **Data** tab shows the underlying data as a time series, with the time in first column and the PromQL query result in the second column. Copy the PromQL query. - - ``` - (1 - (avg(irate({__name__=~"node_cpu_seconds_total|windows_cpu_time_total",mode="idle"}[5m])))) * 100 - - ``` - -You can then modify the query in the Grafana panel or create a new Grafana panel using the query. - -See also: - -- [Grafana docs on editing a panel](https://grafana.com/docs/grafana/latest/panels/panel-editor/) -- [Grafana docs on adding a panel to a dashboard](https://grafana.com/docs/grafana/latest/panels/add-a-panel/) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/enable-monitoring/enable-monitoring.md b/versioned_docs/version-2.6/monitoring-alerting/guides/enable-monitoring/enable-monitoring.md deleted file mode 100644 index ec66d77aba5..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/enable-monitoring/enable-monitoring.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Enable Monitoring -weight: 1 ---- - -As an [administrator]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/) or [cluster owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles), you can configure Rancher to deploy Prometheus to monitor your Kubernetes cluster. - -This page describes how to enable monitoring and alerting within a cluster using the new monitoring application. - -You can enable monitoring with or without SSL. - -# Requirements - -- Make sure that you are allowing traffic on port 9796 for each of your nodes because Prometheus will scrape metrics from here. -- Make sure your cluster fulfills the resource requirements. The cluster should have at least 1950Mi memory available, 2700m CPU, and 50Gi storage. A breakdown of the resource limits and requests is [here.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/helm-chart-options/#configuring-resource-limits-and-requests) -- When installing monitoring on an RKE cluster using RancherOS or Flatcar Linux nodes, change the etcd node certificate directory to `/opt/rke/etc/kubernetes/ssl`. -- For clusters provisioned with the RKE CLI and the address is set to a hostname instead of an IP address, set `rkeEtcd.clients.useLocalhost` to `true` during the Values configuration step of the installation. The YAML snippet will look like the following: - -```yaml -rkeEtcd: - clients: - useLocalhost: true -``` - -> **Note:** If you want to set up Alertmanager, Grafana or Ingress, it has to be done with the settings on the Helm chart deployment. It's problematic to create Ingress outside the deployment. - -# Setting Resource Limits and Requests - -The resource requests and limits can be configured when installing `rancher-monitoring`. To configure Prometheus resources from the Rancher UI, click **Apps & Marketplace > Monitoring** in the upper left corner. - -For more information about the default limits, see [this page.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/helm-chart-options/#configuring-resource-limits-and-requests) - -# Install the Monitoring Application - -### Enable Monitoring for use without SSL - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Cluster Tools** (bottom left corner). -1. Click **Install** by Monitoring. -1. Optional: Customize requests, limits and more for Alerting, Prometheus, and Grafana in the Values step. For help, refer to the [configuration reference.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/helm-chart-options/) - -**Result:** The monitoring app is deployed in the `cattle-monitoring-system` namespace. - -### Enable Monitoring for use with SSL - -1. Follow the steps on [this page]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/) to create a secret in order for SSL to be used for alerts. - - The secret should be created in the `cattle-monitoring-system` namespace. If it doesn't exist, create it first. - - Add the `ca`, `cert`, and `key` files to the secret. -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to enable monitoring for use with SSL and click **Explore**. -1. Click **Apps & Marketplace > Charts**. -1. Click **Monitoring**. -1. Click **Install** or **Update**, depending on whether you have already installed Monitoring. -1. Check the box for **Customize Helm options before install** and click **Next**. -1. Click **Alerting**. -1. In the **Additional Secrets** field, add the secrets created earlier. - -**Result:** The monitoring app is deployed in the `cattle-monitoring-system` namespace. - -When [creating a receiver,]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/advanced/alertmanager/#creating-receivers-in-the-rancher-ui) SSL-enabled receivers such as email or webhook will have a **SSL** section with fields for **CA File Path**, **Cert File Path**, and **Key File Path**. Fill in these fields with the paths to each of `ca`, `cert`, and `key`. The path will be of the form `/etc/alertmanager/secrets/name-of-file-in-secret`. - -For example, if you created a secret with these key-value pairs: - -```yaml -ca.crt=`base64-content` -cert.pem=`base64-content` -key.pfx=`base64-content` -``` - -Then **Cert File Path** would be set to `/etc/alertmanager/secrets/cert.pem`. diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/guides.md b/versioned_docs/version-2.6/monitoring-alerting/guides/guides.md deleted file mode 100644 index 1ef6fc5cce3..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/guides.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Monitoring Guides -shortTitle: Guides -weight: 4 ---- - -- [Enable monitoring](./enable-monitoring) -- [Uninstall monitoring](./uninstall) -- [Monitoring workloads](./monitoring-workloads) -- [Customizing Grafana dashboards](./customize-grafana) -- [Persistent Grafana dashboards](./persist-grafana) -- [Debugging high memory usage](./memory-usage) -- [Migrating from Monitoring V1 to V2](./migrating) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/memory-usage/memory-usage.md b/versioned_docs/version-2.6/monitoring-alerting/guides/memory-usage/memory-usage.md deleted file mode 100644 index 9583570c444..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/memory-usage/memory-usage.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Debugging High Memory Usage -weight: 8 ---- - -Every time series in Prometheus is uniquely identified by its [metric name](https://prometheus.io/docs/practices/naming/#metric-names) and optional key-value pairs called [labels.](https://prometheus.io/docs/practices/naming/#labels) - -The labels allow the ability to filter and aggregate the time series data, but they also multiply the amount of data that Prometheus collects. - -Each time series has a defined set of labels, and Prometheus generates a new time series for all unique combinations of labels. If a metric has two labels attached, two time series are generated for that metric. Changing any label value, including adding or removing a label, will create a new time series. - -Prometheus is optimized to store data that is index-based on series. It is designed for a relatively consistent number of time series and a relatively large number of samples that need to be collected from the exporters over time. - -Inversely, Prometheus is not optimized to accommodate a rapidly changing number of time series. For that reason, large bursts of memory usage can occur when monitoring is installed on clusters where many resources are being created and destroyed, especially on multi-tenant clusters. - -### Reducing Memory Bursts - -To reduce memory consumption, Prometheus can be configured to store fewer time series, by scraping fewer metrics or by attaching fewer labels to the time series. To see which series use the most memory, you can check the TSDB (time series database) status page in the Prometheus UI. - -Distributed Prometheus solutions such as [Thanos](https://thanos.io/) and [Cortex](https://cortexmetrics.io/) use an alternate architecture in which multiple small Prometheus instances are deployed. In the case of Thanos, the metrics from each Prometheus are aggregated into the common Thanos deployment, and then those metrics are exported to a persistent store, such as S3. This more robust architecture avoids burdening any single Prometheus instance with too many time series, while also preserving the ability to query metrics on a global level. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/migrating/migrating.md b/versioned_docs/version-2.6/monitoring-alerting/guides/migrating/migrating.md deleted file mode 100644 index 09178d20d66..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/migrating/migrating.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: Migrating to Rancher v2.5+ Monitoring -weight: 9 ---- - -If you previously enabled Monitoring, Alerting, or Notifiers in Rancher before v2.5, there is no automatic upgrade path for switching to the new monitoring/alerting solution. Before deploying the new monitoring solution via Cluster Explore, you will need to disable and remove all existing custom alerts, notifiers and monitoring installations for the whole cluster and in all projects. - -- [Monitoring Before Rancher v2.5](#monitoring-before-rancher-v2-5) -- [Monitoring and Alerting via Cluster Explorer in Rancher v2.5](#monitoring-and-alerting-via-cluster-explorer-in-rancher-v2-5) -- [Changes to Role-based Access Control](#changes-to-role-based-access-control) -- [Migrating from Monitoring V1 to Monitoring V2](#migrating-from-monitoring-v1-to-monitoring-v2) - - [Migrating Grafana Dashboards](#migrating-grafana-dashboards) - - [Migrating Alerts](#migrating-alerts) - - [Migrating Notifiers](#migrating-notifiers) - - [Migrating for RKE Template Users](#migrating-for-rke-template-users) - -# Monitoring Before Rancher v2.5 - -As of v2.2.0, the global view in the legacy Rancher UI allowed users to enable Monitoring & Alerting V1 (both powered by [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator)) independently within a cluster. - -When Monitoring is enabled, Monitoring V1 deploys [Prometheus](https://prometheus.io/) and [Grafana](https://grafana.com/docs/grafana/latest/getting-started/what-is-grafana/) onto a cluster to monitor the state of processes of your cluster nodes, Kubernetes components, and software deployments and create custom dashboards to make it easy to visualize collected metrics. - -Monitoring V1 could be configured on both a cluster-level and on a project-level and would automatically scrape certain workloads deployed as Apps on the Rancher cluster. - -When Alerts or Notifiers are enabled, Alerting V1 deploys [Prometheus Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) and a set of Rancher controllers onto a cluster that allows users to define alerts and configure alert-based notifications via Email, Slack, PagerDuty, etc. Users can choose to create different types of alerts depending on what needs to be monitored (e.g. System Services, Resources, CIS Scans, etc.); however, PromQL Expression-based alerts can only be created if Monitoring V1 is enabled. - -# Monitoring and Alerting via Cluster Explorer in Rancher 2.5 - -As of v2.5.0, Rancher's Cluster Explorer now allows users to enable Monitoring & Alerting V2 (both powered by [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator)) together within a cluster. - -Unlike in Monitoring & Alerting V1, both features are packaged in a single Helm chart found [here](https://github.com/rancher/charts/blob/main/charts/rancher-monitoring). The behavior of this chart and configurable fields closely matches [kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack), a Prometheus Community Helm chart, and any deviations from the upstream chart can be found in the [CHANGELOG.md](https://github.com/rancher/charts/blob/main/charts/rancher-monitoring/CHANGELOG.md) maintained with the chart. - -Monitoring V2 can only be configured on the cluster level. Project-level monitoring and alerting is no longer supported. - -For more information on how to configure Monitoring & Alerting V2, see [this page.]({{}}/rancher/v2.6/en/monitoring-alerting/configuration) - -# Changes to Role-based Access Control - -Project owners and members no longer get access to Grafana or Prometheus by default. If view-only users had access to Grafana, they would be able to see data from any namespace. For Kiali, any user can edit things they don’t own in any namespace. - -For more information about role-based access control in `rancher-monitoring`, refer to [this page.]({{}}/rancher/v2.6/en/monitoring-alerting/rbac) - -# Migrating from Monitoring V1 to Monitoring V2 - -While there is no automatic migration available, it is possible to manually migrate custom Grafana dashboards and alerts that were created in Monitoring V1 to Monitoring V2. - -Before you can install Monitoring V2, Monitoring V1 needs to be uninstalled completely. In order to uninstall Monitoring V1: - -* Remove all cluster and project specific alerts and alerts groups. -* Remove all notifiers. -* Disable all project monitoring installations under Cluster -> Project -> Tools -> Monitoring. -* Ensure that all project-monitoring apps in all projects have been removed and are not recreated after a few minutes -* Disable the cluster monitoring installation under Cluster -> Tools -> Monitoring. -* Ensure that the cluster-monitoring app and the monitoring-operator app in the System project have been removed and are not recreated after a few minutes. - -#### RKE Template Clusters - -To prevent V1 monitoring from being re-enabled, disable monitoring and in future RKE template revisions via modification of the RKE template yaml: - -```yaml -enable_cluster_alerting: false -enable_cluster_monitoring: false -``` - -#### Migrating Grafana Dashboards - -You can migrate any dashboard added to Grafana in Monitoring V1 to Monitoring V2. In Monitoring V1 you can export an existing dashboard like this: - -* Sign into Grafana -* Navigate to the dashboard you want to export -* Go to the dashboard settings -* Copy the [JSON Model](https://grafana.com/docs/grafana/latest/dashboards/json-model/) - -In the JSON Model, change all `datasource` fields from `RANCHER_MONITORING` to `Prometheus`. You can easily do this by replacing all occurrences of `"datasource": "RANCHER_MONITORING"` with `"datasource": "Prometheus"`. - -If Grafana is backed by a persistent volume, you can now [import](https://grafana.com/docs/grafana/latest/dashboards/export-import/) this JSON Model into the Monitoring V2 Grafana UI. -It is recommended to provide the dashboard to Grafana with a ConfigMap in the `cattle-dashboards` namespace that has the label `grafana_dashboard: "1"`: - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - name: custom-dashboard - namespace: cattle-dashboards - labels: - grafana_dashboard: "1" -data: - custom-dashboard.json: | - { - ... - } -``` - -Once this ConfigMap is created, the dashboard will automatically be added to Grafana. - -### Migrating Alerts - -It is only possible to directly migrate expression-based alerts to Monitoring V2. Fortunately, the event-based alerts that could be set up to alert on system component, node or workload events, are already covered out-of-the-box by the alerts that are part of Monitoring V2. So it is not necessary to migrate them. - -To migrate the following expression alert - -{{< img "/img/rancher/monitoring/migration/alert_2.4_to_2.5_source.png" "">}} - -you have to either create a PrometheusRule configuration like this in any namespace - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PrometheusRule -metadata: - name: custom-rules - namespace: default -spec: - groups: - - name: custom.rules - rules: - - alert: Custom Expression Alert - expr: prometheus_query > 5 - for: 5m - labels: - severity: critical - annotations: - summary: "The result of prometheus_query has been larger than 5 for 5m. Current value {{ $value }}" -``` - -or add the Prometheus Rule through the Cluster Explorer - -{{< img "/img/rancher/monitoring/migration/alert_2.4_to_2.5_target.png" "">}} - -For more details on how to configure PrometheusRules in Monitoring V2 see [Monitoring Configuration]({{}}/rancher/v2.6/en/monitoring-alerting/configuration/). - -### Migrating Notifiers - -There is no direct equivalent for how notifiers work in Monitoring V1. Instead you have to replicate the desired setup with Routes and Receivers in Monitoring V2. - - -### Migrating for RKE Template Users - -If the cluster is managed using an RKE template, you will need to disable monitoring in future RKE template revisions to prevent legacy monitoring from being re-enabled. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/monitoring-workloads/monitoring-workloads.md b/versioned_docs/version-2.6/monitoring-alerting/guides/monitoring-workloads/monitoring-workloads.md deleted file mode 100644 index 10de8484a9a..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/monitoring-workloads/monitoring-workloads.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Setting up Monitoring for a Workload -weight: 4 ---- - -- [Display CPU and Memory Metrics for a Workload](#display-cpu-and-memory-metrics-for-a-workload) -- [Setting up Metrics Beyond CPU and Memory](#setting-up-metrics-beyond-cpu-and-memory) - -If you only need CPU and memory time series for the workload, you don't need to deploy a ServiceMonitor or PodMonitor because the monitoring application already collects metrics data on resource usage by default. - -The steps for setting up monitoring for workloads depend on whether you want basic metrics such as CPU and memory for the workload, or whether you want to scrape custom metrics from the workload. - -If you only need CPU and memory time series for the workload, you don't need to deploy a ServiceMonitor or PodMonitor because the monitoring application already collects metrics data on resource usage by default. The resource usage time series data is in Prometheus's local time series database. - -Grafana shows the data in aggregate, but you can see the data for the individual workload by using a PromQL query that extracts the data for that workload. Once you have the PromQL query, you can execute the query individually in the Prometheus UI and see the time series visualized there, or you can use the query to customize a Grafana dashboard to display the workload metrics. For examples of PromQL queries for workload metrics, see [this section.](https://rancher.com/docs/rancher/v2.6/en/monitoring-alerting/expression/#workload-metrics) - -To set up custom metrics for your workload, you will need to set up an exporter and create a new ServiceMonitor custom resource to configure Prometheus to scrape metrics from your exporter. - -### Display CPU and Memory Metrics for a Workload - -By default, the monitoring application already scrapes CPU and memory. - -To get some fine-grained detail for a particular workload, you can customize a Grafana dashboard to display the metrics for a particular workload. - -### Setting up Metrics Beyond CPU and Memory - -For custom metrics, you will need to expose the metrics on your application in a format supported by Prometheus. - -Then we recommend that you should create a new ServiceMonitor custom resource. When this resource is created, the Prometheus custom resource will be automatically updated so that its scrape configuration includes the new custom metrics endpoint. Then Prometheus will begin scraping metrics from the endpoint. - -You can also create a PodMonitor to expose the custom metrics endpoint, but ServiceMonitors are more appropriate for the majority of use cases. diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/persist-grafana/persist-grafana.md b/versioned_docs/version-2.6/monitoring-alerting/guides/persist-grafana/persist-grafana.md deleted file mode 100644 index 40cd832e9bc..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/persist-grafana/persist-grafana.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: Persistent Grafana Dashboards -weight: 6 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -To allow the Grafana dashboard to persist after the Grafana instance restarts, add the dashboard configuration JSON into a ConfigMap. ConfigMaps also allow the dashboards to be deployed with a GitOps or CD based approach. This allows the dashboard to be put under version control. - -- [Creating a Persistent Grafana Dashboard](#creating-a-persistent-grafana-dashboard) -- [Known Issues](#known-issues) - -# Creating a Persistent Grafana Dashboard - - - - -> **Prerequisites:** -> -> - The monitoring application needs to be installed. -> - To create the persistent dashboard, you must have at least the **Manage Config Maps** Rancher RBAC permissions assigned to you in the project or namespace that contains the Grafana Dashboards. This correlates to the `monitoring-dashboard-edit` or `monitoring-dashboard-admin` Kubernetes native RBAC Roles exposed by the Monitoring chart. -> - To see the links to the external monitoring UIs, including Grafana dashboards, you will need at least a [project-member role.]({{}}/rancher/v2.6/en/monitoring-alerting/rbac/#users-with-rancher-cluster-manager-based-permissions) - -### 1. Get the JSON model of the dashboard that you want to persist - -To create a persistent dashboard, you will need to get the JSON model of the dashboard you want to persist. You can use a premade dashboard or build your own. - -To use a premade dashboard, go to [https://grafana.com/grafana/dashboards](https://grafana.com/grafana/dashboards), open up its detail page, and click on the **Download JSON** button to get the JSON model for the next step. - -To use your own dashboard: - -1. Click on the link to open Grafana. On the cluster detail page, click **Monitoring**. -1. Log in to Grafana. Note: The default Admin username and password for the Grafana instance is `admin/prom-operator`. Alternative credentials can also be supplied on deploying or upgrading the chart. - - > **Note:** Regardless of who has the password, in order to access the Grafana instance, you still need at least the Manage Services or View Monitoring permissions in the project that Rancher Monitoring is deployed into. Alternative credentials can also be supplied on deploying or upgrading the chart. -1. Create a dashboard using Grafana's UI. Once complete, go to the dashboard's settings by clicking on the gear icon in the top navigation menu. In the left navigation menu, click **JSON Model**. -1. Copy the JSON data structure that appears. - -### 2. Create a ConfigMap using the Grafana JSON model - -Create a ConfigMap in the namespace that contains your Grafana Dashboards (e.g. cattle-dashboards by default). - -The ConfigMap should look like this: - -```yaml -apiVersion: v1 -kind: ConfigMap -metadata: - labels: - grafana_dashboard: "1" - name: - namespace: cattle-dashboards # Change if using a non-default namespace -data: - .json: |- - -``` - -By default, Grafana is configured to watch all ConfigMaps with the `grafana_dashboard` label within the `cattle-dashboards` namespace. - -To specify that you would like Grafana to watch for ConfigMaps across all namespaces, refer to [this section.](#configuring-namespaces-for-the-grafana-dashboard-configmap) - -To create the ConfigMap in the Rancher UI, - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the visualizations and click **Explore**. -1. Click **More Resources > Core > ConfigMaps**. -1. Click **Create**. -1. Set up the key-value pairs similar to the example above. When entering the value for `.json`, click **Read from File** to upload the JSON data model as the value. -1. Click **Create**. - -**Result:** After the ConfigMap is created, it should show up on the Grafana UI and be persisted even if the Grafana pod is restarted. - -Dashboards that are persisted using ConfigMaps cannot be deleted or edited from the Grafana UI. - -If you attempt to delete the dashboard in the Grafana UI, you will see the error message "Dashboard cannot be deleted because it was provisioned." To delete the dashboard, you will need to delete the ConfigMap. - -### Configuring Namespaces for the Grafana Dashboard ConfigMap - -To specify that you would like Grafana to watch for ConfigMaps across all namespaces, set this value in the `rancher-monitoring` Helm chart: - -``` -grafana.sidecar.dashboards.searchNamespace=ALL -``` - -Note that the RBAC roles exposed by the Monitoring chart to add Grafana Dashboards are still restricted to giving permissions for users to add dashboards in the namespace defined in `grafana.dashboards.namespace`, which defaults to `cattle-dashboards`. - - - - -> **Prerequisites:** -> -> - The monitoring application needs to be installed. -> - You must have the cluster-admin ClusterRole permission. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to configure the Grafana namespace and click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Grafana**. -1. Log in to Grafana. Note: The default Admin username and password for the Grafana instance is `admin/prom-operator`. Alternative credentials can also be supplied on deploying or upgrading the chart. - - > **Note:** Regardless of who has the password, cluster administrator permission in Rancher is still required to access the Grafana instance. -1. Go to the dashboard that you want to persist. In the top navigation menu, go to the dashboard settings by clicking the gear icon. -1. In the left navigation menu, click **JSON Model**. -1. Copy the JSON data structure that appears. -1. Create a ConfigMap in the `cattle-dashboards` namespace. The ConfigMap needs to have the label `grafana_dashboard: "1"`. Paste the JSON into the ConfigMap in the format shown in the example below: - - ```yaml - apiVersion: v1 - kind: ConfigMap - metadata: - labels: - grafana_dashboard: "1" - name: - namespace: cattle-dashboards - data: - .json: |- - - ``` - -**Result:** After the ConfigMap is created, it should show up on the Grafana UI and be persisted even if the Grafana pod is restarted. - -Dashboards that are persisted using ConfigMaps cannot be deleted from the Grafana UI. If you attempt to delete the dashboard in the Grafana UI, you will see the error message "Dashboard cannot be deleted because it was provisioned." To delete the dashboard, you will need to delete the ConfigMap. - -To prevent the persistent dashboard from being deleted when Monitoring v2 is uninstalled, add the following annotation to the `cattle-dashboards` namespace: - -``` -helm.sh/resource-policy: "keep" -``` - - - - -# Known Issues - -For users who are using Monitoring V2 v9.4.203 or below, uninstalling the Monitoring chart will delete the `cattle-dashboards` namespace, which will delete all persisted dashboards, unless the namespace is marked with the annotation `helm.sh/resource-policy: "keep"`. - -This annotation will be added by default in the new monitoring chart released by Rancher v2.5.8, but it still needs to be manually applied for users of earlier Rancher versions. diff --git a/versioned_docs/version-2.6/monitoring-alerting/guides/uninstall/uninstall.md b/versioned_docs/version-2.6/monitoring-alerting/guides/uninstall/uninstall.md deleted file mode 100644 index b2e8ee0a55d..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/guides/uninstall/uninstall.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Uninstall Monitoring -weight: 2 ---- - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Apps & Marketplace**. -1. Click **Installed Apps**. -1. Go to the `cattle-monitoring-system` namespace and check the boxes for `rancher-monitoring-crd` and `rancher-monitoring`. -1. Click **Delete**. -1. Confirm **Delete**. - -**Result:** `rancher-monitoring` is uninstalled. - -> **Note on Persistent Grafana Dashboards:** For users who are using Monitoring V2 v9.4.203 or below, uninstalling the Monitoring chart will delete the cattle-dashboards namespace, which will delete all persisted dashboards, unless the namespace is marked with the annotation `helm.sh/resource-policy: "keep"`. This annotation is added by default in Monitoring V2 v14.5.100+ but can be manually applied on the cattle-dashboards namespace before an uninstall if an older version of the Monitoring chart is currently installed onto your cluster. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/how-monitoring-works/how-monitoring-works.md b/versioned_docs/version-2.6/monitoring-alerting/how-monitoring-works/how-monitoring-works.md deleted file mode 100644 index fcd70f138e8..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/how-monitoring-works/how-monitoring-works.md +++ /dev/null @@ -1,256 +0,0 @@ ---- -title: How Monitoring Works -weight: 1 ---- - -1. [Architecture Overview](#1-architecture-overview) -2. [How Prometheus Works](#2-how-prometheus-works) -3. [How Alertmanager Works](#3-how-alertmanager-works) -4. [Monitoring V2 Specific Components](#4-monitoring-v2-specific-components) -5. [Scraping and Exposing Metrics](#5-scraping-and-exposing-metrics) - -# 1. Architecture Overview - -_**The following sections describe how data flows through the Monitoring V2 application:**_ - -### Prometheus Operator - -Prometheus Operator observes ServiceMonitors, PodMonitors, and PrometheusRules being created. When the Prometheus configuration resources are created, Prometheus Operator calls the Prometheus API to sync the new configuration. As the diagram at the end of this section shows, the Prometheus Operator acts as the intermediary between Prometheus and Kubernetes, calling the Prometheus API to synchronize Prometheus with the monitoring-related resources in Kubernetes. - -### ServiceMonitors and PodMonitors - -ServiceMonitors and PodMonitors declaratively specify targets, such as Services and Pods, that need to be monitored. - -- Targets are scraped on a recurring schedule based on the configured Prometheus scrape interval, and the metrics that are scraped are stored into the Prometheus Time Series Database (TSDB). - -- In order to perform the scrape, ServiceMonitors and PodMonitors are defined with label selectors that determine which Services or Pods should be scraped and endpoints that determine how the scrape should happen on the given target, e.g., scrape/metrics in TCP 10252, proxying through IP addr x.x.x.x. - -- Out of the box, Monitoring V2 comes with certain pre-configured exporters that are deployed based on the type of Kubernetes cluster that it is deployed on. For more information, see [Scraping and Exposing Metrics](#5-scraping-and-exposing-metrics). - -### How PushProx Works - -- Certain internal Kubernetes components are scraped via a proxy deployed as part of Monitoring V2 called **PushProx**. The Kubernetes components that expose metrics to Prometheus through PushProx are the following: -`kube-controller-manager`, `kube-scheduler`, `etcd`, and `kube-proxy`. - -- For each PushProx exporter, we deploy one PushProx client onto all target nodes. For example, a PushProx client is deployed onto all controlplane nodes for kube-controller-manager, all etcd nodes for kube-etcd, and all nodes for kubelet. - -- We deploy exactly one PushProx proxy per exporter. The process for exporting metrics is as follows: - -1. The PushProx Client establishes an outbound connection with the PushProx Proxy. -1. The client then polls the proxy for scrape requests that have come into the proxy. -1. When the proxy receives a scrape request from Prometheus, the client sees it as a result of the poll. -1. The client scrapes the internal component. -1. The internal component responds by pushing metrics back to the proxy. - - -

Process for Exporting Metrics with PushProx:
- -![Process for Exporting Metrics with PushProx]({{}}/img/rancher/pushprox-process.svg) - -### PrometheusRules - -PrometheusRules allow users to define rules for what metrics or time series database queries should result in alerts being fired. Rules are evaluated on an interval. - -- **Recording rules** create a new time series based on existing series that have been collected. They are frequently used to precompute complex queries. -- **Alerting rules** run a particular query and fire an alert from Prometheus if the query evaluates to a non-zero value. - -### Alert Routing - -Once Prometheus determines that an alert needs to be fired, alerts are forwarded to **Alertmanager**. - -- Alerts contain labels that come from the PromQL query itself and additional labels and annotations that can be provided as part of specifying the initial PrometheusRule. - -- Before receiving any alerts, Alertmanager will use the **routes** and **receivers** specified in its configuration to form a routing tree on which all incoming alerts are evaluated. Each node of the routing tree can specify additional grouping, labeling, and filtering that needs to happen based on the labels attached to the Prometheus alert. A node on the routing tree (usually a leaf node) can also specify that an alert that reaches it needs to be sent out to a configured Receiver, e.g., Slack, PagerDuty, SMS, etc. Note that Alertmanager will send an alert first to **alertingDriver**, then alertingDriver will send or forward alert to the proper destination. - -- Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). - -
How data flows through the monitoring application:
- - -# 2. How Prometheus Works - -### Storing Time Series Data - -After collecting metrics from exporters, Prometheus stores the time series in a local on-disk time series database. Prometheus optionally integrates with remote systems, but `rancher-monitoring` uses local storage for the time series database. - -Once stored, users can query this TSDB using PromQL, the query language for Prometheus. - -PromQL queries can be visualized in one of two ways: - -1. By supplying the query in Prometheus's Graph UI, which will show a simple graphical view of the data. -1. By creating a Grafana Dashboard that contains the PromQL query and additional formatting directives that label axes, add units, change colors, use alternative visualizations, etc. - -### Defining Rules for Prometheus - -Rules define queries that Prometheus needs to execute on a regular `evaluationInterval` to perform certain actions, such as firing an alert (alerting rules) or precomputing a query based on others existing in its TSDB (recording rules). These rules are encoded in PrometheusRules custom resources. When PrometheusRule custom resources are created or updated, the Prometheus Operator observes the change and calls the Prometheus API to synchronize the set of rules that Prometheus is currently evaluating on a regular interval. - -A PrometheusRule allows you to define one or more RuleGroups. Each RuleGroup consists of a set of Rule objects that can each represent either an alerting or a recording rule with the following fields: - -- The name of the new alert or record -- A PromQL expression for the new alert or record -- Labels that should be attached to the alert or record that identify it (e.g. cluster name or severity) -- Annotations that encode any additional important pieces of information that need to be displayed on the notification for an alert (e.g. summary, description, message, runbook URL, etc.). This field is not required for recording rules. - -On evaluating a [rule](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#rule), Prometheus will execute the provided PromQL query, add additional provided labels (or annotations - only for alerting rules), and execute the appropriate action for the rule. For example, an Alerting Rule that adds `team: front-end` as a label to the provided PromQL query will append that label to the fired alert, which will allow Alertmanager to forward the alert to the correct Receiver. - -### Alerting and Recording Rules - -Prometheus doesn't maintain the state of whether alerts are active. It fires alerts repetitively at every evaluation interval, relying on Alertmanager to group and filter the alerts into meaningful notifications. - -The `evaluation_interval` constant defines how often Prometheus evaluates its alerting rules against the time series database. Similar to the `scrape_interval`, the `evaluation_interval` also defaults to one minute. - -The rules are contained in a set of rule files. Rule files include both alerting rules and recording rules, but only alerting rules result in alerts being fired after their evaluation. - -For recording rules, Prometheus runs a query, then stores it as a time series. This synthetic time series is useful for storing the results of an expensive or time-consuming query so that it can be queried more quickly in the future. - -Alerting rules are more commonly used. Whenever an alerting rule evaluates to a positive number, Prometheus fires an alert. - -The Rule file adds labels and annotations to alerts before firing them, depending on the use case: - -- Labels indicate information that identifies the alert and could affect the routing of the alert. For example, if when sending an alert about a certain container, the container ID could be used as a label. - -- Annotations denote information that doesn't affect where an alert is routed, for example, a runbook or an error message. - -# 3. How Alertmanager Works - -The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of the following tasks: - -- Deduplicating, grouping, and routing alerts to the correct receiver integration such as email, PagerDuty, or OpsGenie - -- Silencing and inhibition of alerts - -- Tracking alerts that fire over time - -- Sending out the status of whether an alert is currently firing, or if it is resolved - -### Alerts Forwarded by alertingDrivers - -When alertingDrivers are installed, this creates a `Service` that can be used as the receiver's URL for Teams or SMS, based on the alertingDriver's configuration. The URL in the Receiver points to the alertingDrivers; so the Alertmanager sends alert first to alertingDriver, then alertingDriver forwards or sends alert to the proper destination. - -### Routing Alerts to Receivers - -Alertmanager coordinates where alerts are sent. It allows you to group alerts based on labels and fire them based on whether certain labels are matched. One top-level route accepts all alerts. From there, Alertmanager continues routing alerts to receivers based on whether they match the conditions of the next route. - -While the Rancher UI forms only allow editing a routing tree that is two levels deep, you can configure more deeply nested routing structures by editing the Alertmanager Secret. - -### Configuring Multiple Receivers - -By editing the forms in the Rancher UI, you can set up a Receiver resource with all the information Alertmanager needs to send alerts to your notification system. - -By editing custom YAML in the Alertmanager or Receiver configuration, you can also send alerts to multiple notification systems. For more information, see the section on configuring [Receivers.](../configuration/receiver/#configuring-multiple-receivers) - -# 4. Monitoring V2 Specific Components - -Prometheus Operator introduces a set of [Custom Resource Definitions](https://github.com/prometheus-operator/prometheus-operator#customresourcedefinitions) that allow users to deploy and manage Prometheus and Alertmanager instances by creating and modifying those custom resources on a cluster. - -Prometheus Operator will automatically update your Prometheus configuration based on the live state of the resources and configuration options that are edited in the Rancher UI. - -### Resources Deployed by Default - -By default, a set of resources curated by the [kube-prometheus](https://github.com/prometheus-operator/kube-prometheus) project are deployed onto your cluster as part of installing the Rancher Monitoring Application to set up a basic Monitoring/Alerting stack. - -The resources that get deployed onto your cluster to support this solution can be found in the [`rancher-monitoring`](https://github.com/rancher/charts/tree/main/charts/rancher-monitoring) Helm chart, which closely tracks the upstream [kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) Helm chart maintained by the Prometheus community with certain changes tracked in the [CHANGELOG.md](https://github.com/rancher/charts/blob/main/charts/rancher-monitoring/CHANGELOG.md). - -### Default Exporters - -Monitoring V2 deploys three default exporters that provide additional metrics for Prometheus to store: - -1. `node-exporter`: exposes hardware and OS metrics for Linux hosts. For more information on `node-exporter`, refer to the [upstream documentation](https://prometheus.io/docs/guides/node-exporter/). - -1. `windows-exporter`: exposes hardware and OS metrics for Windows hosts (only deployed on Windows clusters). For more information on `windows-exporter`, refer to the [upstream documentation](https://github.com/prometheus-community/windows_exporter). - -1. `kube-state-metrics`: expose additional metrics that track the state of resources contained in the Kubernetes API (e.g., pods, workloads, etc.). For more information on `kube-state-metrics`, refer to the [upstream documentation](https://github.com/kubernetes/kube-state-metrics/tree/master/docs). - -ServiceMonitors and PodMonitors will scrape these exporters, as defined [here](#defining-what-metrics-are-scraped). Prometheus stores these metrics, and you can query the results via either Prometheus's UI or Grafana. - -See the [architecture](#1-architecture-overview) section for more information on recording rules, alerting rules, and Alertmanager. - -### Components Exposed in the Rancher UI - -When the monitoring application is installed, you will be able to edit the following components in the Rancher UI: - -| Component | Type of Component | Purpose and Common Use Cases for Editing | -|--------------|------------------------|---------------------------| -| ServiceMonitor | Custom resource | Sets up Kubernetes Services to scrape custom metrics from. Automatically updates the scrape configuration in the Prometheus custom resource. | -| PodMonitor | Custom resource | Sets up Kubernetes Pods to scrape custom metrics from. Automatically updates the scrape configuration in the Prometheus custom resource. | -| Receiver | Configuration block (part of Alertmanager) | Modifies information on where to send an alert (e.g., Slack, PagerDuty, etc.) and any necessary information to send the alert (e.g., TLS certs, proxy URLs, etc.). Automatically updates the Alertmanager custom resource. | -| Route | Configuration block (part of Alertmanager) | Modifies the routing tree that is used to filter, label, and group alerts based on labels and send them to the appropriate Receiver. Automatically updates the Alertmanager custom resource. | -| PrometheusRule | Custom resource | Defines additional queries that need to trigger alerts or define materialized views of existing series that are within Prometheus's TSDB. Automatically updates the Prometheus custom resource. | - -### PushProx - -PushProx allows Prometheus to scrape metrics across a network boundary, which prevents users from having to expose metrics ports for internal Kubernetes components on each node in a Kubernetes cluster. - -Since the metrics for Kubernetes components are generally exposed on the host network of nodes in the cluster, PushProx deploys a DaemonSet of clients that sit on the hostNetwork of each node and make an outbound connection to a single proxy that is sitting on the Kubernetes API. Prometheus can then be configured to proxy scrape requests through the proxy to each client, which allows it to scrape metrics from the internal Kubernetes components without requiring any inbound node ports to be open. - -Refer to [Scraping Metrics with PushProx](#scraping-metrics-with-pushprox) for more. - -# 5. Scraping and Exposing Metrics - -### Defining what Metrics are Scraped - -ServiceMonitors and PodMonitors define targets that are intended for Prometheus to scrape. The [Prometheus custom resource](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/design.md#prometheus) tells Prometheus which ServiceMonitors or PodMonitors it should use to find out where to scrape metrics from. - -The Prometheus Operator observes the ServiceMonitors and PodMonitors. When it observes that they are created or updated, it calls the Prometheus API to update the scrape configuration in the Prometheus custom resource and keep it in sync with the scrape configuration in the ServiceMonitors or PodMonitors. This scrape configuration tells Prometheus which endpoints to scrape metrics from and how it will label the metrics from those endpoints. - -Prometheus scrapes all of the metrics defined in its scrape configuration at every `scrape_interval`, which is one minute by default. - -The scrape configuration can be viewed as part of the Prometheus custom resource that is exposed in the Rancher UI. - -### How the Prometheus Operator Sets up Metrics Scraping - -The Prometheus Deployment or StatefulSet scrapes metrics, and the configuration of Prometheus is controlled by the Prometheus custom resources. The Prometheus Operator watches for Prometheus and Alertmanager resources, and when they are created, the Prometheus Operator creates a Deployment or StatefulSet for Prometheus or Alertmanager with the user-defined configuration. - -When the Prometheus Operator observes ServiceMonitors, PodMonitors, and PrometheusRules being created, it knows that the scrape configuration needs to be updated in Prometheus. It updates Prometheus by first updating the configuration and rules files in the volumes of Prometheus's Deployment or StatefulSet. Then it calls the Prometheus API to sync the new configuration, resulting in the Prometheus Deployment or StatefulSet to be modified in place. - -### How Kubernetes Component Metrics are Exposed - -Prometheus scrapes metrics from deployments known as [exporters,](https://prometheus.io/docs/instrumenting/exporters/) which export the time series data in a format that Prometheus can ingest. In Prometheus, time series consist of streams of timestamped values belonging to the same metric and the same set of labeled dimensions. - -### Scraping Metrics with PushProx - -Certain internal Kubernetes components are scraped via a proxy deployed as part of Monitoring V2 called PushProx. For detailed information on PushProx, refer [here](#how-pushprox-works) and to the above [architecture](#1-architecture-overview) section. - -### Scraping Metrics - -The following Kubernetes components are directly scraped by Prometheus: - -- kubelet* -- ingress-nginx** -- coreDns/kubeDns -- kube-api-server - -\* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. - -** For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. - - -### Scraping Metrics Based on Kubernetes Distribution - -Metrics are scraped differently based on the Kubernetes distribution. For help with terminology, refer [here](#terminology). For details, see the table below: - -
How Metrics are Exposed to Prometheus
- -| Kubernetes Component | RKE | RKE2 | KubeADM | K3s | -|-----|-----|-----|-----|-----| -| kube-controller-manager | rkeControllerManager.enabled |rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | -| kube-scheduler | rkeScheduler.enabled | rke2Scheduler.enabled |kubeAdmScheduler.enabled | k3sServer.enabled | -| etcd | rkeEtcd.enabled | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | -| kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | -| kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, exposed by rkeIngressNginx.enabled | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | -| coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | -| kube-api-server | Collects metrics directly exposed by kube-api-server |Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | - -\* For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. - -### Terminology - -- **kube-scheduler:** The internal Kubernetes component that uses information in the pod spec to decide on which node to run a pod. -- **kube-controller-manager:** The internal Kubernetes component that is responsible for node management (detecting if a node fails), pod replication and endpoint creation. -- **etcd:** The internal Kubernetes component that is the distributed key/value store which Kubernetes uses for persistent storage of all cluster information. -- **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. -- **kubelet:** The internal Kubernetes component that watches the API server for pods on a node and makes sure they are running. -- **ingress-nginx:** An Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer. -- **coreDns/kubeDns:** The internal Kubernetes component responsible for DNS. -- **kube-api-server:** The main internal Kubernetes component that is responsible for exposing APIs for the other master components. diff --git a/versioned_docs/version-2.6/monitoring-alerting/monitoring-alerting.md b/versioned_docs/version-2.6/monitoring-alerting/monitoring-alerting.md deleted file mode 100644 index cd2b721917d..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/monitoring-alerting.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -title: Monitoring and Alerting -shortTitle: Monitoring/Alerting -description: Prometheus lets you view metrics from your different Rancher and Kubernetes objects. Learn about the scope of monitoring and how to enable cluster monitoring -weight: 13 ---- - -Using the `rancher-monitoring` application, you can quickly deploy leading open-source monitoring and alerting solutions onto your cluster. - -- [Features](#features) -- [How Monitoring Works](#how-monitoring-works) -- [Default Components and Deployments](#default-components-and-deployments) -- [Role-based Access Control](#role-based-access-control) -- [Guides](#guides) -- [Windows Cluster Support](#windows-cluster-support) -- [Known Issues](#known-issues) - -### Features - -Prometheus lets you view metrics from your Rancher and Kubernetes objects. Using timestamps, Prometheus lets you query and view these metrics in easy-to-read graphs and visuals, either through the Rancher UI or Grafana, which is an analytics viewing platform deployed along with Prometheus. - -By viewing data that Prometheus scrapes from your cluster control plane, nodes, and deployments, you can stay on top of everything happening in your cluster. You can then use these analytics to better run your organization: stop system emergencies before they start, develop maintenance strategies, or restore crashed servers. - -The `rancher-monitoring` operator, introduced in Rancher v2.5, is powered by [Prometheus](https://prometheus.io/), [Grafana](https://grafana.com/grafana/), [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), the [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator), and the [Prometheus adapter.](https://github.com/DirectXMan12/k8s-prometheus-adapter) - -The monitoring application allows you to: - -- Monitor the state and processes of your cluster nodes, Kubernetes components, and software deployments -- Define alerts based on metrics collected via Prometheus -- Create custom Grafana dashboards -- Configure alert-based notifications via Email, Slack, PagerDuty, etc. using Prometheus Alertmanager -- Defines precomputed, frequently needed or computationally expensive expressions as new time series based on metrics collected via Prometheus -- Expose collected metrics from Prometheus to the Kubernetes Custom Metrics API via Prometheus Adapter for use in HPA - -# How Monitoring Works - -For an explanation of how the monitoring components work together, see [this page.](./how-monitoring-works) - -# Default Components and Deployments - -### Built-in Dashboards - -By default, the monitoring application deploys Grafana dashboards (curated by the [kube-prometheus](https://github.com/prometheus-operator/kube-prometheus) project) onto a cluster. - -It also deploys an Alertmanager UI and a Prometheus UI. For more information about these tools, see [Built-in Dashboards.](./dashboards) -### Default Metrics Exporters - -By default, Rancher Monitoring deploys exporters (such as [node-exporter](https://github.com/prometheus/node_exporter) and [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics)). - -These default exporters automatically scrape metrics for CPU and memory from all components of your Kubernetes cluster, including your workloads. - -### Default Alerts - -The monitoring application deploys some alerts by default. To see the default alerts, go to the [Alertmanager UI](./dashboards/#alertmanager-ui) and click **Expand all groups.** - -### Components Exposed in the Rancher UI - -For a list of monitoring components exposed in the Rancher UI, along with common use cases for editing them, see [this section.](./how-monitoring-works/#components-exposed-in-the-rancher-ui) - -# Role-based Access Control - -For information on configuring access to monitoring, see [this page.](./rbac) - -# Guides - -- [Enable monitoring](./guides/enable-monitoring) -- [Uninstall monitoring](./guides/uninstall) -- [Monitoring workloads](./guides/monitoring-workloads) -- [Customizing Grafana dashboards](./guides/customize-grafana) -- [Persistent Grafana dashboards](./guides/persist-grafana) -- [Debugging high memory usage](./guides/memory-usage) -- [Migrating from Monitoring V1 to V2](./guides/migrating) - -# Configuration - -### Configuring Monitoring Resources in Rancher - -> The configuration reference assumes familiarity with how monitoring components work together. For more information, see [How Monitoring Works.](./how-monitoring-works) - -- [ServiceMonitor and PodMonitor](./configuration/servicemonitor-podmonitor) -- [Receiver](./configuration/receiver) -- [Route](./configuration/route) -- [PrometheusRule](./configuration/advanced/prometheusrules) -- [Prometheus](./configuration/advanced/prometheus) -- [Alertmanager](./configuration/advanced/alertmanager) - -### Configuring Helm Chart Options - -For more information on `rancher-monitoring` chart options, including options to set resource limits and requests, see [this page.](./configuration/helm-chart-options) - -# Windows Cluster Support - -When deployed onto an RKE1 Windows cluster, Monitoring V2 will now automatically deploy a [windows-exporter](https://github.com/prometheus-community/windows_exporter) DaemonSet and set up a ServiceMonitor to collect metrics from each of the deployed Pods. This will populate Prometheus with `windows_` metrics that are akin to the `node_` metrics exported by [node_exporter](https://github.com/prometheus/node_exporter) for Linux hosts. - -To be able to fully deploy Monitoring V2 for Windows, all of your Windows hosts must have a minimum [wins](https://github.com/rancher/wins) version of v0.1.0. - -For more details on how to upgrade wins on existing Windows hosts, refer to the section on [Windows cluster support for Monitoring V2.](./windows-clusters) - - - -# Known Issues - -There is a [known issue](https://github.com/rancher/rancher/issues/28787#issuecomment-693611821) that K3s clusters require more default memory. If you are enabling monitoring on a K3s cluster, we recommend to setting `prometheus.prometheusSpec.resources.memory.limit` to 2500 Mi and `prometheus.prometheusSpec.resources.memory.request` to 1750 Mi. - -For tips on debugging high memory usage, see [this page.](./guides/memory-usage) diff --git a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/customizing-grafana/customizing-grafana.md b/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/customizing-grafana/customizing-grafana.md deleted file mode 100644 index f5cc1e5653d..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/customizing-grafana/customizing-grafana.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Customizing Grafana Dashboards -weight: 3 ---- - -Grafana dashboards are customized the same way whether it's for rancher-monitoring or for Prometheus Federator. - -For instructions, refer to [this page](../../../guides/customize-grafana/). \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/enable-prom-fed/enable-prom-fed.md b/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/enable-prom-fed/enable-prom-fed.md deleted file mode 100644 index ae4ff801de2..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/enable-prom-fed/enable-prom-fed.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Enable Prometheus Federator -weight: 1 ---- - -- [Requirements](#requirements) -- [Install the Prometheus Federator Application](#install-the-prometheus-federator-application) - -# Requirements - -By default, Prometheus Federator is configured and intended to be deployed alongside [rancher-monitoring](https://rancher.com/docs/rancher/v2.6/en/monitoring-alerting/), which deploys Prometheus Operator alongside a Cluster Prometheus that each Project Monitoring Stack is configured to federate namespace-scoped metrics from by default. - -For instructions on installing rancher-monitoring, refer to [this page](../../../guides/enable-monitoring/). - -The default configuration should already be compatible with your rancher-monitoring stack. However, to optimize the security and usability of Prometheus Federator in your cluster, we recommend making these additional configurations to rancher-monitoring: - -- [Ensure the cattle-monitoring-system namespace is placed into the System Project](#ensure-the-cattle-monitoring-system-namespace-is-placed-into-the-system-project-or-a-similarly-locked-down-project-that-has-access-to-other-projects-in-the-cluster). -- [Configure rancher-monitoring to only watch for resources created by the Helm chart itself](#configure-rancher-monitoring-to-only-watch-for-resources-created-by-the-helm-chart-itself). -- [Increase the CPU / memory limits of the Cluster Prometheus](#increase-the-cpu--memory-limits-of-the-cluster-prometheus). - -## Ensure the cattle-monitoring-system namespace is placed into the System Project (or a similarly locked down Project that has access to other Projects in the cluster) - -Prometheus Operator's security model expects that the namespace it is deployed into (e.g., `cattle-monitoring-system`) has limited access for anyone except Cluster Admins to avoid privilege escalation via execing into Pods (such as the Jobs executing Helm operations). In addition, deploying Prometheus Federator and all Project Prometheus stacks into the System Project ensures that each Project Prometheus is able to reach out to scrape workloads across all Projects, even if Network Policies are defined via Project Network Isolation. It also provides limited access for Project Owners, Project Members, and other users so that they're unable to access data that they shouldn't have access to (i.e., being allowed to exec into pods, set up the ability to scrape namespaces outside of a given Project, etc.). - -## Configure rancher-monitoring to only watch for resources created by the Helm chart itself - -Since each Project Monitoring Stack will watch the other namespaces and collect additional custom workload metrics or dashboards already, it's recommended to configure the following settings on all selectors to ensure that the Cluster Prometheus Stack only monitors resources created by the Helm Chart itself: - -``` -matchLabels: - release: "rancher-monitoring" -``` - -The following selector fields are recommended to have this value: -- `.Values.alertmanager.alertmanagerSpec.alertmanagerConfigSelector` -- `.Values.prometheus.prometheusSpec.serviceMonitorSelector` -- `.Values.prometheus.prometheusSpec.podMonitorSelector` -- `.Values.prometheus.prometheusSpec.ruleSelector` -- `.Values.prometheus.prometheusSpec.probeSelector` - -Once this setting is turned on, you can always create ServiceMonitors or PodMonitors that are picked up by the Cluster Prometheus by adding the label `release: "rancher-monitoring"` to them, in which case they will be ignored by Project Monitoring Stacks automatically by default, even if the namespace in which those ServiceMonitors or PodMonitors reside in are not system namespaces. - -> Note: If you don't want to allow users to be able to create ServiceMonitors and PodMonitors that aggregate into the Cluster Prometheus in Project namespaces, you can additionally set the namespaceSelectors on the chart to only target system namespaces (which must contain `cattle-monitoring-system` and `cattle-dashboards`, where resources are deployed into by default by rancher-monitoring; you will also need to monitor the `default` namespace to get apiserver metrics or create a custom ServiceMonitor to scrape apiserver metrics from the Service residing in the default namespace) to limit your Cluster Prometheus from picking up other Prometheus Operator CRs. In that case, it would be recommended to turn `.Values.prometheus.prometheusSpec.ignoreNamespaceSelectors=true` to allow you to define ServiceMonitors that can monitor non-system namespaces from within a system namespace. - -## Increase the CPU / memory limits of the Cluster Prometheus - -Depending on a cluster's setup, it's generally recommended to give a large amount of dedicated memory to the Cluster Prometheus to avoid restarts due to out-of-memory errors (OOMKilled) usually caused by churn created in the cluster that causes a large number of high cardinality metrics to be generated and ingested by Prometheus within one block of time. This is one of the reasons why the default Rancher Monitoring stack expects around 4GB of RAM to be able to operate in a normal-sized cluster. However, when introducing Project Monitoring Stacks that are all sending `/federate` requests to the same Cluster Prometheus and are reliant on the Cluster Prometheus being "up" to federate that system data on their namespaces, it's even more important that the Cluster Prometheus has an ample amount of CPU / memory assigned to it to prevent an outage that can cause data gaps across all Project Prometheis in the cluster. - -> Note: There are no specific recommendations on how much memory the Cluster Prometheus should be configured with since it depends entirely on the user's setup (namely the likelihood of encountering a high churn rate and the scale of metrics that could be generated at that time); it generally varies per setup. - -# Install the Prometheus Federator Application - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you want to install Prometheus Federator and click **Explore**. -1. Click **Apps -> Charts**. -1. Click the **Prometheus Federator** chart. -1. Click **Install**. -1. On the **Metadata** page, click **Next**. -1. In the **Project Release Namespace Project ID** field, the `System Project` is used as the default but can be overridden with another project with similarly [limited access](#ensure-the-cattle-monitoring-system-namespace-is-placed-into-the-system-project-or-a-similarly-locked-down-project-that-has-access-to-other-projects-in-the-cluster). - -### Display CPU and Memory Metrics for a Workload - -Displaying CPU and memory metrics with Prometheus Federator is done the same way as with rancher-monitoring. For instructions, refer [here](../../../guides/monitoring-workloads#display-cpu-and-memory-metrics-for-a-workload). - -### Setting up Metrics Beyond CPU and Memory - -Setting up metrics beyond CPU and memory with Prometheus Federator is done the same way as with rancher-monitoring. For instructions, refer [here](../../../guides/monitoring-workloads#setting-up-metrics-beyond-cpu-and-memory). - - diff --git a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/uninstall-prom-fed/uninstall-prom-fed.md b/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/uninstall-prom-fed/uninstall-prom-fed.md deleted file mode 100644 index 2db6cdda414..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/guides/uninstall-prom-fed/uninstall-prom-fed.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Uninstall Prometheus Federator -weight: 2 ---- - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. In the left navigation bar, click **Apps & Marketplace**. -1. Click **Installed Apps**. -1. Go to the `cattle-monitoring-system` namespace and check the boxes for `rancher-monitoring-crd` and `rancher-monitoring`. -1. Click **Delete**. -1. Confirm **Delete**. - -**Result:** `prometheus-federator` is uninstalled. diff --git a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/prometheus-federator.md b/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/prometheus-federator.md deleted file mode 100644 index cc88321bee4..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/prometheus-federator.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Prometheus Federator -weight: 7 ---- - -Prometheus Federator, also referred to as Project Monitoring v2, deploys a Helm Project Operator (based on the [rancher/helm-project-operator](https://github.com/rancher/helm-project-operator)), an operator that manages deploying Helm charts each containing a Project Monitoring Stack, where each stack contains: - -- [Prometheus](https://prometheus.io/) (managed externally by [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator)) -- [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) (managed externally by [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator)) -- [Grafana](https://github.com/helm/charts/tree/master/stable/grafana) (deployed via an embedded Helm chart) -- Default PrometheusRules and Grafana dashboards based on the collection of community-curated resources from [kube-prometheus](https://github.com/prometheus-operator/kube-prometheus/) -- Default ServiceMonitors that watch the deployed resources - -> **Important** Prometheus Federator is designed to be deployed alongside an existing Prometheus Operator deployment in a cluster that has already installed the Prometheus Operator CRDs. - -## How does the operator work? - -1. On deploying this chart, users can create ProjectHelmCharts CRs with `spec.helmApiVersion` set to `monitoring.cattle.io/v1alpha1` (also known as "Project Monitors" in the Rancher UI) in a **Project Registration Namespace (`cattle-project-`)**. -2. On seeing each ProjectHelmChartCR, the operator will automatically deploy a Project Prometheus stack on the Project Owner's behalf in the **Project Release Namespace (`cattle-project--monitoring`)** based on a HelmChart CR and a HelmRelease CR automatically created by the ProjectHelmChart controller in the **Operator / System Namespace**. -3. RBAC will automatically be assigned in the Project Release Namespace to allow users to view the Prometheus, Alertmanager, and Grafana UIs of the Project Monitoring Stack deployed; this will be based on RBAC defined on the Project Registration Namespace against the [default Kubernetes user-facing roles](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles). For more information, see the section on [configuring RBAC](./rbac/). - -### What is a Project? - -In Prometheus Federator, a Project is a group of namespaces that can be identified by a `metav1.LabelSelector`. By default, the label used to identify projects is `field.cattle.io/projectId`, the label used to identify namespaces that are contained within a given Rancher Project. - -### Configuring the Helm release created by a ProjectHelmChart - -The `spec.values` of this ProjectHelmChart's resources will correspond to the `values.yaml` override to be supplied to the underlying Helm chart deployed by the operator on the user's behalf; to see the underlying chart's `values.yaml` spec, either: - -- View the chart's definition located at [`rancher/prometheus-federator` under `charts/rancher-project-monitoring`](https://github.com/rancher/prometheus-federator/blob/main/charts/rancher-project-monitoring) (where the chart version will be tied to the version of this operator). -- Look for the ConfigMap named `monitoring.cattle.io.v1alpha1` that is automatically created in each Project Registration Namespace, which will contain both the `values.yaml` and `questions.yaml` that was used to configure the chart (which was embedded directly into the `prometheus-federator` binary). - -### Namespaces - -As a Project Operator based on [rancher/helm-project-operator](https://github.com/rancher/helm-project-operator), Prometheus Federator has three different classifications of namespaces that the operator looks out for: - -1. **Operator / System Namespace**: The namespace that the operator is deployed into (e.g., `cattle-monitoring-system`). This namespace will contain all HelmCharts and HelmReleases for all ProjectHelmCharts watched by this operator. **Only Cluster Admins should have access to this namespace.** -2. **Project Registration Namespace (`cattle-project-`)**: The set of namespaces that the operator watches for ProjectHelmCharts within. The RoleBindings and ClusterRoleBindings that apply to this namespace will also be the source of truth for the auto-assigned RBAC created in the Project Release Namespace. For details, refer to the [RBAC page](./rbac/). **Project Owners (admin), Project Members (edit), and Read-Only Members (view) should have access to this namespace.** - - > **Note:** Project Registration Namespaces will be auto-generated by the operator and imported into the Project it is tied to if `.Values.global.cattle.projectLabel` is provided, which is set to `field.cattle.io/projectId` by default. This indicates that a Project Registration Namespace should be created by the operator if at least one namespace is observed with that label. The operator will not let these namespaces be deleted unless either all namespaces with that label are gone (e.g., this is the last namespace in that project, in which case the namespace will be marked with the label `"helm.cattle.io/helm-project-operator-orphaned": "true"`, which signals that it can be deleted), or it is no longer watching that project because the project ID was provided under `.Values.helmProjectOperator.otherSystemProjectLabelValues`, which serves as a denylist for Projects. These namespaces will also never be auto-deleted to avoid destroying user data; it is recommended that users clean up these namespaces manually if desired on creating or deleting a project. - - > **Note:** If `.Values.global.cattle.projectLabel` is not provided, the Operator / System Namespace will also be the Project Registration Namespace. -3. **Project Release Namespace (`cattle-project--monitoring`):** The set of namespaces that the operator deploys Project Monitoring Stacks within on behalf of a ProjectHelmChart; the operator will also automatically assign RBAC to Roles created in this namespace by the Project Monitoring Stack based on bindings found in the Project Registration Namespace. **Only Cluster Admins should have access to this namespace; Project Owners (admin), Project Members (edit), and Read-Only Members (view) will be assigned limited access to this namespace by the deployed Helm Chart and Prometheus Federator.** - - > **Note:** Project Release Namespaces are automatically deployed and imported into the project whose ID is specified under `.Values.helmProjectOperator.projectReleaseNamespaces.labelValue`, which defaults to the value of `.Values.global.cattle.systemProjectId` if not specified, whenever a ProjectHelmChart is specified in a Project Registration Namespace. - - > **Note:** Project Release Namespaces follow the same orphaning conventions as Project Registration Namespaces (see note above). - - > **Note:** If `.Values.projectReleaseNamespaces.enabled` is false, the Project Release Namespace will be the same as the Project Registration Namespace. - -### Helm Resources (HelmChart, HelmRelease) - -On deploying a ProjectHelmChart, the Prometheus Federator will automatically create and manage two child custom resources that manage the underlying Helm resources in turn: - -- A HelmChart CR (managed via an embedded [k3s-io/helm-contoller](https://github.com/k3s-io/helm-controller) in the operator): This custom resource automatically creates a Job in the same namespace that triggers a `helm install`, `helm upgrade`, or `helm uninstall` depending on the change applied to the HelmChart CR. This CR is automatically updated on changes to the ProjectHelmChart (e.g., modifying the values.yaml) or changes to the underlying Project definition (e.g., adding or removing namespaces from a project). - -> **Important:** If a ProjectHelmChart is not deploying or updating the underlying Project Monitoring Stack for some reason, the Job created by this resource in the Operator / System namespace should be the first place you check to see if there's something wrong with the Helm operation. However, this is generally only accessible by a **Cluster Admin.** - -- A HelmRelease CR (managed via an embedded [rancher/helm-locker](https://github.com/rancher/helm-locker) in the operator): This custom resource automatically locks a deployed Helm release in place and automatically overwrites updates to underlying resources unless the change happens via a Helm operation (`helm install`, `helm upgrade`, or `helm uninstall` performed by the HelmChart CR). - -> **Note:** HelmRelease CRs emit Kubernetes Events that detect when an underlying Helm release is being modified and locks it back to place. To view these events, you can use `kubectl describe helmrelease -n `; you can also view the logs on this operator to see when changes are detected and which resources modifications were attempted on. - -Both of these resources are created for all Helm charts in the Operator / System namespaces to avoid escalation of privileges to underprivileged users. - -### Advanced Helm Project Operator Configuration - -For more information on advanced configurations, refer to [this page](https://github.com/rancher/prometheus-federator/blob/main/charts/prometheus-federator/0.0.1/README.md#advanced-helm-project-operator-configuration). - - - -### Prometheus Federator on the Local Cluster - -Prometheus Federator is a resource intensive application. Installing it to the local cluster is possible, but **not recommended**. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/rbac/rbac.md b/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/rbac/rbac.md deleted file mode 100644 index eb278431566..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/prometheus-federator/rbac/rbac.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Role-Based Access Control -shortTitle: RBAC -weight: 2 ---- - -This section describes the expectations for Role-Based Access Control (RBAC) for Prometheus Federator. - -As described in the section on [namespaces](../prometheus-federator#namespaces), Prometheus Federator expects that Project Owners, Project Members, and other users in the cluster with Project-level permissions (e.g. permissions in a certain set of namespaces identified by a single label selector) have minimal permissions in any namespaces except the Project Registration Namespace (which is imported into the project by default) and those that already comprise their projects. Therefore, in order to allow Project Owners to assign specific chart permissions to other users in their Project namespaces, the Helm Project Operator will automatically watch the following bindings: - -- ClusterRoleBindings -- RoleBindings in the Project Release Namespace - -On observing a change to one of those types of bindings, the Helm Project Operator will check whether the `roleRef` that the the binding points to matches a ClusterRole with the name provided under: - -- `helmProjectOperator.releaseRoleBindings.clusterRoleRefs.admin` -- `helmProjectOperator.releaseRoleBindings.clusterRoleRefs.edit` -- `helmProjectOperator.releaseRoleBindings.clusterRoleRefs.view` - -By default, these roleRefs will correspond to `admin`, `edit`, and `view` respectively, which are the [default Kubernetes user-facing roles](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles). - -> **Note** For Rancher RBAC users, these [default Kubernetes user-facing roles](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) directly correlate to the `Project Owner`, `Project Member`, and `Read-Only` default Project Role Templates. - -If the `roleRef` matches, the Helm Project Operator will filter the `subjects` of the binding for all Users and Groups and use that to automatically construct a RoleBinding for each Role in the Project Release Namespace with the same name as the role and the following labels: - -- `helm.cattle.io/project-helm-chart-role: {{ .Release.Name }}` -- `helm.cattle.io/project-helm-chart-role-aggregate-from: ` - -By default, `rancher-project-monitoring`, the underlying chart deployed by Prometheus Federator, creates three default Roles per Project Release Namespace that provide `admin`, `edit`, and `view` users to permissions to view the Prometheus, Alertmanager, and Grafana UIs of the Project Monitoring Stack to provide least privilege. However, if a Cluster Admin would like to assign additional permissions to certain users, they can either directly assign RoleBindings in the Project Release Namespace to certain users or create Roles with the above two labels on them to allow Project Owners to control assigning those RBAC roles to users in their Project Registration namespaces. \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/rbac/rbac.md b/versioned_docs/version-2.6/monitoring-alerting/rbac/rbac.md deleted file mode 100644 index e025b733e64..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/rbac/rbac.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -title: Role-based Access Control -shortTitle: RBAC -weight: 2 ---- -This section describes the expectations for RBAC for Rancher Monitoring. - -- [Cluster Admins](#cluster-admins) -- [Users with Kubernetes ClusterRole-based Permissions](#users-with-kubernetes-clusterrole-based-permissions) - - [Users with Kubernetes Admin/Edit Permissions](#users-with-kubernetes-admin-edit-permissions) - - [Users with Kubernetes View Permissions](#users-with-kubernetes-view-permissions) - - [Additional Monitoring Roles](#additional-monitoring-roles) - - [Additional Monitoring ClusterRoles](#additional-monitoring-clusterroles) -- [Users with Rancher Based Permissions](#users-with-rancher-based-permissions) - - [Differences in 2.5.x](#differences-in-2-5-x) - - [Assigning Additional Access](#assigning-additional-access) -- [Role-based Access Control for Grafana](#role-based-access-control-for-grafana) - -# Cluster Admins - -By default, only those with the cluster-admin `ClusterRole` should be able to: - -- Install the `rancher-monitoring` App onto a cluster and all other relevant configuration performed on the chart deploy - - e.g. whether default dashboards are created, what exporters are deployed onto the cluster to collect metrics, etc. -- Create / modify / delete Prometheus deployments in the cluster via Prometheus CRs -- Create / modify / delete Alertmanager deployments in the cluster via Alertmanager CRs -- Persist new Grafana dashboards or datasources via creating ConfigMaps in the appropriate namespace -- Expose certain Prometheus metrics to the k8s Custom Metrics API for HPA via a Secret in the `cattle-monitoring-system` namespace - -# Users with Kubernetes ClusterRole-based Permissions - -The `rancher-monitoring` chart installs the following three `ClusterRoles`. By default, they aggregate into the corresponding k8s `ClusterRoles`: - -| ClusterRole | Aggregates To Default K8s ClusterRole | -| ------------------------------| ---------------------------| -| `monitoring-admin` | `admin`| -| `monitoring-edit` | `edit` | -| `monitoring-view` | `view ` | - -These `ClusterRoles` provide different levels of access to the Monitoring CRDs based on the actions that can be performed: - -| CRDs (monitoring.coreos.com) | Admin | Edit | View | -| ------------------------------| ---------------------------| ---------------------------| ---------------------------| -|
  • `prometheuses`
  • `alertmanagers`
| Get, List, Watch | Get, List, Watch | Get, List, Watch | -|
  • `servicemonitors`
  • `podmonitors`
  • `prometheusrules`
| * | * | Get, List, Watch | - -On a high level, the following permissions are assigned by default as a result. - -### Users with Kubernetes Admin/Edit Permissions - -Only those with the the cluster-admin, admin or edit `ClusterRole` should be able to: - -- Modify the scrape configuration of Prometheus deployments via ServiceMonitor and PodMonitor CRs -- Modify the alerting / recording rules of a Prometheus deployment via PrometheusRules CRs - -### Users with Kubernetes View Permissions - -Only those with who have some Kubernetes `ClusterRole` should be able to: - -- View the configuration of Prometheuses that are deployed within the cluster -- View the configuration of Alertmanagers that are deployed within the cluster -- View the scrape configuration of Prometheus deployments via ServiceMonitor and PodMonitor CRs -- View the alerting/recording rules of a Prometheus deployment via PrometheusRules CRs - -### Additional Monitoring Roles - -Monitoring also creates additional `Roles` that are not assigned to users by default but are created within the cluster. They can be bound to a namespace by deploying a `RoleBinding` that references it. To define a `RoleBinding` with `kubectl` instead of through Rancher, click [here](#assigning-roles-and-clusterroles-with-kubectl). - -Admins should use these roles to provide more fine-grained access to users: - -| Role | Purpose | -| ------------------------------| ---------------------------| -| monitoring-config-admin | Allow admins to assign roles to users to be able to view / modify Secrets and ConfigMaps within the cattle-monitoring-system namespace. Modifying Secrets / ConfigMaps in this namespace could allow users to alter the cluster's Alertmanager configuration, Prometheus Adapter configuration, additional Grafana datasources, TLS secrets, etc. | -| monitoring-config-edit | Allow admins to assign roles to users to be able to view / modify Secrets and ConfigMaps within the cattle-monitoring-system namespace. Modifying Secrets / ConfigMaps in this namespace could allow users to alter the cluster's Alertmanager configuration, Prometheus Adapter configuration, additional Grafana datasources, TLS secrets, etc. | -| monitoring-config-view | Allow admins to assign roles to users to be able to view Secrets and ConfigMaps within the cattle-monitoring-system namespace. Viewing Secrets / ConfigMaps in this namespace could allow users to observe the cluster's Alertmanager configuration, Prometheus Adapter configuration, additional Grafana datasources, TLS secrets, etc. | -| monitoring-dashboard-admin | Allow admins to assign roles to users to be able to edit / view ConfigMaps within the cattle-dashboards namespace. ConfigMaps in this namespace will correspond to Grafana Dashboards that are persisted onto the cluster. | -| monitoring-dashboard-edit | Allow admins to assign roles to users to be able to edit / view ConfigMaps within the cattle-dashboards namespace. ConfigMaps in this namespace will correspond to Grafana Dashboards that are persisted onto the cluster. | -| monitoring-dashboard-view | Allow admins to assign roles to users to be able to view ConfigMaps within the cattle-dashboards namespace. ConfigMaps in this namespace will correspond to Grafana Dashboards that are persisted onto the cluster. | - -### Additional Monitoring ClusterRoles - -Monitoring also creates additional `ClusterRoles` that are not assigned to users by default but are created within the cluster. They are not aggregated by default but can be bound to a namespace by deploying a `RoleBinding` or `ClusterRoleBinding` that references it. To define a `RoleBinding` with `kubectl` instead of through Rancher, click [here](#assigning-roles-and-clusterroles-with-kubectl). - -| Role | Purpose | -| ------------------------------| ---------------------------| -| monitoring-ui-view | _Available as of Monitoring v2 14.5.100+_ Provides read-only access to external Monitoring UIs by giving a user permission to list the Prometheus, Alertmanager, and Grafana endpoints and make GET requests to Prometheus, Grafana, and Alertmanager UIs through the Rancher proxy. | - -### Assigning Roles and ClusterRoles with kubectl - -An alternative method to using Rancher to attach a `Role` or `ClusterRole` to a user or group is by defining bindings in YAML files that you create. You must first configure the `RoleBinding` with the YAML file, then you apply the config changes by running the `kubectl apply` command. - - -* **Roles**: Below is an example of a YAML file to help you configure `RoleBindings` in Kubernetes. You will need to fill in the name below, and name is case-sensitive. - -``` -# monitoring-config-view-role-binding.yaml -apiVersion: rbac.authorization.k8s.io/v1 -kind: RoleBinding -metadata: - name: monitoring-config-view - namespace: cattle-monitoring-system -roleRef: - kind: Role - name: monitoring-config-view - apiGroup: rbac.authorization.k8s.io -subjects: -- kind: User - name: u-b4qkhsnliz # this can be found via `kubectl get users -A` - apiGroup: rbac.authorization.k8s.io -``` - -* **kubectl**: Below is an example of a `kubectl` command used to apply the binding you've created in the YAML file. As noted, you will need to fill in your YAML filename accordingly. - - * **`kubectl apply -f monitoring-config-view-role-binding.yaml` - - -# Users with Rancher Based Permissions - -The relationship between the default roles deployed by Rancher (i.e. cluster-owner, cluster-member, project-owner, project-member), the default Kubernetes roles, and the roles deployed by the rancher-monitoring chart are detailed in the table below: - -
Default Rancher Permissions and Corresponding Kubernetes ClusterRoles
- -| Rancher Role | Kubernetes Role | Monitoring ClusterRole / Role | ClusterRoleBinding or RoleBinding? | -| --------- | --------- | --------- | --------- | -| cluster-owner | cluster-admin | N/A | ClusterRoleBinding | -| cluster-member | admin | monitoring-admin | ClusterRoleBinding | -| project-owner | admin | monitoring-admin | RoleBinding within Project namespace | -| project-member | edit | monitoring-edit | RoleBinding within Project namespace | - -In addition to these default Roles, the following additional Rancher project roles can be applied to members of your Cluster to provide additional access to Monitoring. These Rancher Roles will be tied to ClusterRoles deployed by the Monitoring chart: - -
Non-default Rancher Permissions and Corresponding Kubernetes ClusterRoles
- -| Rancher Role | Kubernetes ClusterRole | Available In Rancher From | Available in Monitoring v2 From | -|--------------------------|-------------------------------|-------|------| -| View Monitoring* | [monitoring-ui-view](#monitoring-ui-view) | 2.4.8+ | 9.4.204+ | - -\* A User bound to the **View Monitoring** Rancher Role only has permissions to access external Monitoring UIs if provided links to those UIs. In order to access the Monitoring Pane to get those links, the User must be a Project Member of at least one Project. - -### Differences in 2.5.x - -Users with the project-member or project-owners roles assigned will not be given access to either Prometheus or Grafana in Rancher 2.5.x since we only create Grafana or Prometheus on a cluster-level. - -In addition, while project owners will still be only able to add ServiceMonitors / PodMonitors that scrape resources within their project's namespace by default, PrometheusRules are not scoped to a single namespace / project. Therefore, any alert rules or recording rules created by project-owners within their project namespace will be applied across the entire cluster, although they will be unable to view / edit / delete any rules that were created outside the project's namespace. - -### Assigning Additional Access - -If cluster-admins would like to provide additional admin/edit access to users outside of the roles offered by the rancher-monitoring chart, the following table identifies the potential impact: - -|CRDs (monitoring.coreos.com) | Can it cause impact outside of a namespace / project? | Impact | -|----------------------------| ------| ----------------------------| -| `prometheuses`| Yes, this resource can scrape metrics from any targets across the entire cluster (unless the Operator itself is otherwise configured). | User will be able to define the configuration of new cluster-level Prometheus deployments that should be created in the cluster. | -| `alertmanagers`| No | User will be able to define the configuration of new cluster-level Alertmanager deployments that should be created in the cluster. Note: if you just want to allow users to configure settings like Routes and Receivers, you should just provide access to the Alertmanager Config Secret instead. | -|
  • `servicemonitors`
  • `podmonitors`
| No, not by default; this is configurable via `ignoreNamespaceSelectors` on the Prometheus CR. | User will be able to set up scrapes by Prometheus on endpoints exposed by Services / Pods within the namespace they are given this permission in. | -| `prometheusrules`| Yes, PrometheusRules are cluster-scoped. | User will be able to define alert or recording rules on Prometheus based on any series collected across the entire cluster. | - -| k8s Resources | Namespace | Can it cause impact outside of a namespace / project? | Impact | -|----------------------------| ------| ------| ----------------------------| -|
  • `secrets`
  • `configmaps`
| `cattle-monitoring-system` | Yes, Configs and Secrets in this namespace can impact the entire monitoring / alerting pipeline. | User will be able to create or edit Secrets / ConfigMaps such as the Alertmanager Config, Prometheus Adapter Config, TLS secrets, additional Grafana datasources, etc. This can have broad impact on all cluster monitoring / alerting. | -|
  • `secrets`
  • `configmaps`
| `cattle-dashboards` | Yes, Configs and Secrets in this namespace can create dashboards that make queries on all metrics collected at a cluster-level. | User will be able to create Secrets / ConfigMaps that persist new Grafana Dashboards only. | - - - -# Role-based Access Control for Grafana - -Rancher allows any users who are authenticated by Kubernetes and have access the Grafana service deployed by the Rancher Monitoring chart to access Grafana via the Rancher Dashboard UI. By default, all users who are able to access Grafana are given the [Viewer](https://grafana.com/docs/grafana/latest/permissions/organization_roles/#viewer-role) role, which allows them to view any of the default dashboards deployed by Rancher. - -However, users can choose to log in to Grafana as an [Admin](https://grafana.com/docs/grafana/latest/permissions/organization_roles/#admin-role) if necessary. The default Admin username and password for the Grafana instance will be `admin`/`prom-operator`, but alternative credentials can also be supplied on deploying or upgrading the chart. - -To see the Grafana UI, install `rancher-monitoring`. Then: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to see the visualizations and click **Explore**. -1. In the left navigation bar, click **Monitoring**. -1. Click **Grafana**. - -
Cluster Compute Resources Dashboard in Grafana
-![Cluster Compute Resources Dashboard in Grafana]({{}}/img/rancher/cluster-compute-resources-dashboard.png) - -
Default Dashboards in Grafana
-![Default Dashboards in Grafana]({{}}/img/rancher/grafana-default-dashboard.png) \ No newline at end of file diff --git a/versioned_docs/version-2.6/monitoring-alerting/windows-clusters/windows-clusters.md b/versioned_docs/version-2.6/monitoring-alerting/windows-clusters/windows-clusters.md deleted file mode 100644 index 3a2b0e3deda..00000000000 --- a/versioned_docs/version-2.6/monitoring-alerting/windows-clusters/windows-clusters.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Windows Cluster Support for Monitoring V2 -shortTitle: Windows Support -weight: 5 ---- - -_Available as of v2.5.8_ - -Starting at Monitoring V2 14.5.100 (used by default in Rancher 2.5.8), Monitoring V2 can now be deployed on a Windows cluster and will scrape metrics from Windows nodes using [prometheus-community/windows_exporter](https://github.com/prometheus-community/windows_exporter) (previously named `wmi_exporter`). - -- [Comparison to Monitoring V1](#comparison-to-monitoring-v1) -- [Cluster Requirements](#cluster-requirements) - - [Upgrading Existing Clusters to wins v0.1.0](#upgrading-existing-clusters-to-wins-v0-1-0) - -# Comparison to Monitoring V1 - -Unlike Monitoring V1 for Windows, metrics collected by `windows_exporter` will be labeled as `windows_` instead of `wmi_` in accordance to a naming change from upstream from `wmi_exporter` to `windows_exporter`. - -In addition, Monitoring V2 for Windows will no longer require users to keep port 9796 open on Windows hosts since the host metrics will published directly onto a port exposed on the windows-exporter Pod. This feature was powered by recent changes made by `wins` v0.1.0 to support publishing ports exposed on the hostNetwork on Pods that use wins to run a privileged Windows binary as a host process. - -# Cluster Requirements - -Monitoring V2 for Windows can only scrape metrics from Windows hosts that have a minimum `wins` version of v0.1.0. To be able to fully deploy Monitoring V2 for Windows, all of your hosts must meet this requirement. - -If you provision a fresh RKE1 cluster in Rancher 2.5.8, your cluster should already meet this requirement. - -### Upgrading Existing Clusters to wins v0.1.0 - -If the cluster was provisioned before Rancher 2.5.8 (even if the current Rancher version is 2.5.8), you will not be able to successfully deploy Monitoring V2 for Windows until you upgrade the wins version on each host to at least v0.1.0. - -To facilitate this upgrade, Rancher 2.5.8 has released a brand new Helm chart called `rancher-wins-upgrader`. - -> **Prerequisite:** Make sure Monitoring V1 for Windows is uninstalled. - -1. Deploy `rancher-wins-upgrader` with the following override: - ```yaml - # Masquerading bootstraps the wins-upgrader installation via - # a previously whitelisted process path since the normal install path, - # c:\etc\rancher\wins\wins-upgrade.exe is not normally whitelisted. - # In this case, we are using the previously whitelisted process - # path used by Monitoring V1. - masquerade: - enabled: true - as: c:\\etc\wmi-exporter\wmi-exporter.exe - ``` - > **Note for Non-Default Windows Prefix Path:** If you set up the RKE cluster with a `cluster.yml` that has a non-default `win_prefix_path`, you will need to update the `masquerade.as` field with your prefix path in place of `c:\\`. - > - > For example, if you have `win_prefix_path: 'c:\host\opt\'`, then you will need to set `as: c:\host\opt\etc\wmi-exporter\wmi-exporter.exe`. -2. Once all your hosts have been successfully upgraded, please ensure that you deploy the Helm chart once again with default values to avoid conflicts with the following settings: - ```yaml - masquerade: - enabled: false - ``` - -**Result:** The hosts are ready for Monitoring V2 to be installed. You may choose to uninstall the `rancher-wins-upgrader` chart or keep it in your cluster to facilitate future upgrades. - -For more information on how it can be used, please see the [README.md](https://github.com/rancher/wins/blob/master/charts/rancher-wins-upgrader/README.md) of the chart. diff --git a/versioned_docs/version-2.6/neuvector-integration/neuvector-integration.md b/versioned_docs/version-2.6/neuvector-integration/neuvector-integration.md deleted file mode 100644 index 1c58d6e200a..00000000000 --- a/versioned_docs/version-2.6/neuvector-integration/neuvector-integration.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: NeuVector Integration -weight: 22 ---- - -### NeuVector Integration in Rancher - -New in Rancher v2.6.5, [NeuVector 5.x](https://open-docs.neuvector.com/) is an open-source container-centric security platform that is now integrated into Rancher. NeuVector offers real-time compliance, visibility, and protection for critical applications and data during runtime. NeuVector provides a firewall, container process/file system monitoring, security auditing with CIS benchmarks, and vulnerability scanning. For more information on Rancher security, please see the [security documentation]({{}}/rancher/v2.6/en/security/). - -NeuVector can be enabled through a Helm chart that may be installed either through **Apps & Marketplace** or through the **Cluster Tools** button in the Rancher UI. Once the Helm chart is installed, users can easily [deploy and manage NeuVector clusters within Rancher](https://open-docs.neuvector.com/deploying/rancher#deploy-and-manage-neuvector-through-rancher-apps-marketplace). - -### Installing NeuVector with Rancher - -The Harvester Helm Chart is used to manage access to the NeuVector UI in Rancher where users can navigate directly to deploy and manage their NeuVector clusters. - -**To navigate to and install the NeuVector chart through Apps & Marketplace:** - -1. Click **☰ > Cluster Management**. -1. On the Clusters page, go to the cluster where you want to deploy NeuVector, and click **Explore**. -1. Go to **Apps & Marketplace > Charts**, and install **NeuVector** from the chart repo. -1. Different cluster types require different container runtimes. When configuring Helm chart values, go to the **Container Runtime** section, and select your runtime in accordance with the cluster type. Finally, click **Install** again. - -Some examples are as follows: - - - RKE1: `docker` - - K3s and RKE2: `k3scontainerd` - - AKS: `containerd` for v1.19 and up - - EKS: `docker` for v1.22 and below; `containerd` for v1.23 and up - - GKE: `containerd` (see the [Google docs](https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd) for more) - - >**Note:** Only one container runtime engine may be selected at a time during installation. - -**To navigate to and install the NeuVector chart through Cluster Tools:** - -1. Click **☰ > Cluster Management**. -1. On the Clusters page, go to the cluster where you want to deploy NeuVector, and click **Explore**. -1. Click on **Cluster Tools** at the bottom of the left navigation bar. -1. Repeat step 4 above to select your container runtime accordingly, then click **Install** again. - -### Accessing NeuVector from the Rancher UI - -1. Navigate to the cluster explorer of the cluster where NeuVector is installed. In the left navigation bar, click **NeuVector**. -1. Click the external link to go to the NeuVector UI. Once the link is selected, users must accept the `END USER LICENSE AGREEMENT` to access the NeuVector UI. - -### Uninstalling NeuVector from the Rancher UI - -**To uninstall from Apps & Marketplace:** - -1. Click **☰ > Cluster Management**. -1. Under **Apps & Marketplace**, click **Installed Apps**. -1. Under `cattle-neuvector-system`, select both the NeuVector app (and the associated CRD if desired), then click **Delete**. - -**To uninstall from Cluster Tools:** - -1. Click **☰ > Cluster Management**. -1. Click on **Cluster Tools** at the bottom-left of the screen, then click on the trash can icon under the NeuVector chart. Select `Delete the CRD associated with this app` if desired, then click **Delete**. - -### GitHub Repository - -The NeuVector project is available [here](https://github.com/neuvector/neuvector). - -### Documentation - -The NeuVector documentation is [here](https://open-docs.neuvector.com/). - -### Architecture - -The NeuVector security solution contains four types of security containers: Controllers, Enforcers, Managers, and Scanners. A special container called an All-in-One is also provided to combine the Controller, Enforcer, and Manager functions all in one container, primarily for Docker-native deployments. There is also an Updater which, when run, will update the CVE database. - -- **Controller:** Manages the NeuVector Enforcer container; provides REST APIs for the management console. -- **Enforcer:** Enforces security policies. -- **Manager:** Provides a web-UI and CLI console to manage the NeuVector platform. -- **All-in-One:** Includes the Controller, Enforcer, and Manager. -- **Scanner:** Performs the vulnerability and compliance scanning for images, containers, and nodes. -- **Updater:** Updates the CVE database for Neuvector (when run); redeploys scanner pods. - -
**NeuVector Security Containers:**
-![NeuVector Security Containers]({{}}/img/rancher/neuvector-security-containers.png) - -
**NeuVector Architecture:**
-![NeuVector Architecture]({{}}/img/rancher/neuvector-architecture.png) - -To learn more about NeuVector's architecture, please refer [here](https://open-docs.neuvector.com/basics/overview#architecture). - -### CPU and Memory Allocations - -Below are the minimum recommended computing resources for the NeuVector chart installation in a default deployment. Note that the resource limit is not set. - -| Container | CPU - Request | Memory - Request | -|------------|--------|---------| -| Controller | 3 (1GB 1vCPU needed per controller) | * -| Enforcer | On all nodes (500MB .5vCPU) | 1GB -| Manager | 1 (500MB .5vCPU) | * -| Scanner | 3 (100MB .5vCPU) | * - -\* Minimum 1GB of memory total required for Controller, Manager, and Scanner containers combined. - - -### Support Limitations - -* Only admins and cluster owners are currently supported. - -* Fleet multi-cluster deployment is not supported. - -* NeuVector is not supported on a Windows cluster. - -* NeuVector installation is not supported on hardened clusters. - -* NeuVector installation is not supported on SELinux clusters. - -* NeuVector installation is not supported on clusters in an air-gapped environment. - -### Other Limitations - -* Currently, NeuVector feature chart installation fails when a NeuVector partner chart already exists. To work around this issue, uninstall the NeuVector partner chart and reinstall the NeuVector feature chart. - -* Sometimes when the controllers are not ready, the NeuVector UI is not accessible from the Rancher UI. During this time, controllers will try to restart, and it takes a few minutes for the controllers to be active. - -* Container runtime is not auto-detected for different cluster types when installing the NeuVector chart. To work around this, you can specify the runtime manually. - diff --git a/versioned_docs/version-2.6/opa-gatekeper/opa-gatekeper.md b/versioned_docs/version-2.6/opa-gatekeper/opa-gatekeper.md deleted file mode 100644 index e9eee7e67c7..00000000000 --- a/versioned_docs/version-2.6/opa-gatekeper/opa-gatekeper.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: OPA Gatekeeper -weight: 16 ---- - -To ensure consistency and compliance, every organization needs the ability to define and enforce policies in its environment in an automated way. [OPA (Open Policy Agent)](https://www.openpolicyagent.org/) is a policy engine that facilitates policy-based control for cloud native environments. Rancher provides the ability to enable OPA Gatekeeper in Kubernetes clusters, and also installs a couple of built-in policy definitions, which are also called constraint templates. - -OPA provides a high-level declarative language that lets you specify policy as code and ability to extend simple APIs to offload policy decision-making. - -[OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper) is a project that provides integration between OPA and Kubernetes. OPA Gatekeeper provides: - -- An extensible, parameterized policy library. -- Native Kubernetes CRDs for instantiating the policy library, also called “constraints." -- Native Kubernetes CRDs for extending the policy library, also called "constraint templates." -- Audit functionality. - -To read more about OPA, please refer to the [official documentation.](https://www.openpolicyagent.org/docs/latest/) - -# How the OPA Gatekeeper Integration Works - -Kubernetes provides the ability to extend API server functionality via admission controller webhooks, which are invoked whenever a resource is created, updated or deleted. Gatekeeper is installed as a validating webhook and enforces policies defined by Kubernetes custom resource definitions. In addition to the admission control usage, Gatekeeper provides the capability to audit existing resources in Kubernetes clusters and mark current violations of enabled policies. - -OPA Gatekeeper is made available via Rancher's Helm system chart, and it is installed in a namespace named `gatekeeper-system.` - -# Enabling OPA Gatekeeper in a Cluster - -> In Rancher v2.5, the OPA Gatekeeper application was improved. The Rancher v2.4 feature can't be upgraded to the new version in Rancher v2.5. If you installed OPA Gatekeeper in Rancher v2.4, you will need to uninstall OPA Gatekeeper and its CRDs from the old UI, then reinstall it in Rancher v2.5. To uninstall the CRDs run the following command in the kubectl console `kubectl delete crd configs.config.gatekeeper.sh constrainttemplates.templates.gatekeeper.sh`. - -> **Prerequisite:** Only administrators and cluster owners can enable OPA Gatekeeper. - -The OPA Gatekeeper Helm chart can be installed from **Apps & Marketplace**. - -### Enabling OPA Gatekeeper - -1. In the upper left corner, click **☰ > Cluster Management**. -1. In the **Clusters** page, go to the cluster where you want to enable OPA Gatekeeper and click **Explore**. -1. In the left navigation bar, click **Apps & Marketplace**. -1. Click **Charts** and click **OPA Gatekeeper**. -1. Click **Install**. - -**Result:** OPA Gatekeeper is deployed in your Kubernetes cluster. - -# Constraint Templates - -[Constraint templates](https://github.com/open-policy-agent/gatekeeper#constraint-templates) are Kubernetes custom resources that define the schema and Rego logic of the OPA policy to be applied by Gatekeeper. For more information on the Rego policy language, refer to the [official documentation.](https://www.openpolicyagent.org/docs/latest/policy-language/) - -When OPA Gatekeeper is enabled, Rancher installs some templates by default. - -To list the constraint templates installed in the cluster, go to the left side menu under OPA Gatekeeper and click on **Templates**. - -Rancher also provides the ability to create your own constraint templates by importing YAML definitions. - -# Creating and Configuring Constraints - -[Constraints](https://github.com/open-policy-agent/gatekeeper#constraints) are Kubernetes custom resources that define the scope of objects to which a specific constraint template applies to. The complete policy is defined by constraint templates and constraints together. - -> **Prerequisites:** OPA Gatekeeper must be enabled in the cluster. - -To list the constraints installed, go to the left side menu under OPA Gatekeeper, and click on **Constraints**. - -New constraints can be created from a constraint template. - -Rancher provides the ability to create a constraint by using a convenient form that lets you input the various constraint fields. - -The **Edit as yaml** option is also available to configure the the constraint's yaml definition. - -### Exempting Rancher's System Namespaces from Constraints - -When a constraint is created, ensure that it does not apply to any Rancher or Kubernetes system namespaces. If the system namespaces are not excluded, then it is possible to see many resources under them marked as violations of the constraint. - -To limit the scope of the constraint only to user namespaces, always specify these namespaces under the **Match** field of the constraint. - -Also, the constraint may interfere with other Rancher functionality and deny system workloads from being deployed. To avoid this, exclude all Rancher-specific namespaces from your constraints. - -# Enforcing Constraints in your Cluster - -When the **Enforcement Action** is **Deny,** the constraint is immediately enabled and will deny any requests that violate the policy defined. By default, the enforcement value is **Deny**. - -When the **Enforcement Action** is **Dryrun,** then any resources that violate the policy are only recorded under the constraint's status field. - -To enforce constraints, create a constraint using the form. In the **Enforcement Action** field, choose **Deny**. - -# Audit and Violations in your Cluster - -OPA Gatekeeper runs a periodic audit to check if any existing resource violates any enforced constraint. The audit-interval (default 300s) can be configured while installing Gatekeeper. - -On the Gatekeeper page, any violations of the defined constraints are listed. - -Also under **Constraints,** the number of violations of the constraint can be found. - -The detail view of each constraint lists information about the resource that violated the constraint. - -# Disabling Gatekeeper - -1. Navigate to the cluster's Dashboard view -1. On the left side menu, expand the cluster menu and click on **OPA Gatekeeper**. -1. Click the **⋮ > Disable**. - -**Result:** Upon disabling OPA Gatekeeper, all constraint templates and constraints will also be deleted. - diff --git a/versioned_docs/version-2.6/overview/architecture-recommendations/architecture-recommendations.md b/versioned_docs/version-2.6/overview/architecture-recommendations/architecture-recommendations.md deleted file mode 100644 index 112388c36c9..00000000000 --- a/versioned_docs/version-2.6/overview/architecture-recommendations/architecture-recommendations.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Architecture Recommendations -weight: 3 ---- - -If you are installing Rancher on a single node, the main architecture recommendation that applies to your installation is that the node running Rancher should be [separate from downstream clusters.](#separation-of-rancher-and-user-clusters) - -This section covers the following topics: - -- [Separation of Rancher and User Clusters](#separation-of-rancher-and-user-clusters) -- [Why HA is Better for Rancher in Production](#why-ha-is-better-for-rancher-in-production) -- [Recommended Load Balancer Configuration for Kubernetes Installations](#recommended-load-balancer-configuration-for-kubernetes-installations) -- [Environment for Kubernetes Installations](#environment-for-kubernetes-installations) -- [Recommended Node Roles for Kubernetes Installations](#recommended-node-roles-for-kubernetes-installations) -- [Architecture for an Authorized Cluster Endpoint (ACE)](#architecture-for-an-authorized-cluster-endpoint-ace) - -# Separation of Rancher and User Clusters - -A user cluster is a downstream Kubernetes cluster that runs your apps and services. - -If you have a Docker installation of Rancher, the node running the Rancher server should be separate from your downstream clusters. - -If Rancher is intended to manage downstream Kubernetes clusters, the Kubernetes cluster that the Rancher server runs on should also be separate from the downstream user clusters. - -![Separation of Rancher Server from User Clusters]({{}}/img/rancher/rancher-architecture-separation-of-rancher-server.svg) - -# Why HA is Better for Rancher in Production - -We recommend installing the Rancher server on a high-availability Kubernetes cluster, primarily because it protects the Rancher server data. In a high-availability installation, a load balancer serves as the single point of contact for clients, distributing network traffic across multiple servers in the cluster and helping to prevent any one server from becoming a point of failure. - -We don't recommend installing Rancher in a single Docker container, because if the node goes down, there is no copy of the cluster data available on other nodes and you could lose the data on your Rancher server. - -### K3s Kubernetes Cluster Installations - -One option for the underlying Kubernetes cluster is to use K3s Kubernetes. K3s is Rancher's CNCF certified Kubernetes distribution. It is easy to install and uses half the memory of Kubernetes, all in a binary of less than 100 MB. Another advantage of K3s is that it allows an external datastore to hold the cluster data, allowing the K3s server nodes to be treated as ephemeral. - -
Architecture of a K3s Kubernetes Cluster Running the Rancher Management Server
-![Architecture of a K3s Kubernetes Cluster Running the Rancher Management Server]({{}}/img/rancher/k3s-server-storage.svg) - -### RKE Kubernetes Cluster Installations - -In an RKE installation, the cluster data is replicated on each of three etcd nodes in the cluster, providing redundancy and data duplication in case one of the nodes fails. - -
Architecture of an RKE Kubernetes Cluster Running the Rancher Management Server
-![Architecture of an RKE Kubernetes cluster running the Rancher management server]({{}}/img/rancher/rke-server-storage.svg) - -# Recommended Load Balancer Configuration for Kubernetes Installations - -We recommend the following configurations for the load balancer and Ingress controllers: - -* The DNS for Rancher should resolve to a Layer 4 load balancer (TCP). -* The Load Balancer should forward port TCP/80 and TCP/443 to all 3 nodes in the Kubernetes cluster. -* The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. -* The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. - -
Rancher installed on a Kubernetes cluster with layer 4 load balancer, depicting SSL termination at Ingress controllers
-![Rancher HA]({{}}/img/rancher/ha/rancher2ha.svg) - -# Environment for Kubernetes Installations - -It is strongly recommended to install Rancher on a Kubernetes cluster on hosted infrastructure such as Amazon's EC2 or Google Compute Engine. - -For the best performance and greater security, we recommend a dedicated Kubernetes cluster for the Rancher management server. Running user workloads on this cluster is not advised. After deploying Rancher, you can [create or import clusters]({{}}/rancher/v2.6/en/cluster-provisioning/) for running your workloads. - -# Recommended Node Roles for Kubernetes Installations - -The below recommendations apply when Rancher is installed on a K3s Kubernetes cluster or an RKE Kubernetes cluster. - -### K3s Cluster Roles - -In K3s clusters, there are two types of nodes: server nodes and agent nodes. Both servers and agents can have workloads scheduled on them. Server nodes run the Kubernetes master. - -For the cluster running the Rancher management server, we recommend using two server nodes. Agent nodes are not required. - -### RKE Cluster Roles - -If Rancher is installed on an RKE Kubernetes cluster, the cluster should have three nodes, and each node should have all three Kubernetes roles: etcd, controlplane, and worker. - -### Contrasting RKE Cluster Architecture for Rancher Server and for Downstream Kubernetes Clusters - -Our recommendation for RKE node roles on the Rancher server cluster contrasts with our recommendations for the downstream user clusters that run your apps and services. - -Rancher uses RKE as a library when provisioning downstream Kubernetes clusters. Note: The capability to provision downstream K3s clusters will be added in a future version of Rancher. - -For downstream Kubernetes clusters, we recommend that each node in a user cluster should have a single role for stability and scalability. - -![Kubernetes Roles for Nodes in Rancher Server Cluster vs. User Clusters]({{}}/img/rancher/rancher-architecture-node-roles.svg) - -RKE only requires at least one node with each role and does not require nodes to be restricted to one role. However, for the clusters that run your apps, we recommend separate roles for each node so that workloads on worker nodes don't interfere with the Kubernetes master or cluster data as your services scale. - -We recommend that downstream user clusters should have at least: - -- **Three nodes with only the etcd role** to maintain a quorum if one node is lost, making the state of your cluster highly available -- **Two nodes with only the controlplane role** to make the master component highly available -- **One or more nodes with only the worker role** to run the Kubernetes node components, as well as the workloads for your apps and services - -With that said, it is safe to use all three roles on three nodes when setting up the Rancher server because: - -* It allows one `etcd` node failure. -* It maintains multiple instances of the master components by having multiple `controlplane` nodes. -* No other workloads than Rancher itself should be created on this cluster. - -Because no additional workloads will be deployed on the Rancher server cluster, in most cases it is not necessary to use the same architecture that we recommend for the scalability and reliability of downstream clusters. - -For more best practices for downstream clusters, refer to the [production checklist]({{}}/rancher/v2.6/en/cluster-provisioning/production) or our [best practices guide.]({{}}/rancher/v2.6/en/best-practices/) - -# Architecture for an Authorized Cluster Endpoint (ACE) - -If you are using an [authorized cluster endpoint (ACE),]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) we recommend creating an FQDN pointing to a load balancer which balances traffic across your nodes with the `controlplane` role. - -If you are using private CA signed certificates on the load balancer, you have to supply the CA certificate, which will be included in the generated kubeconfig file to validate the certificate chain. See the documentation on [kubeconfig files]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/) and [API keys]({{}}/rancher/v2.6/en/user-settings/api-keys/#creating-an-api-key) for more information. - -As of Rancher v2.6.3, ACE support is available for registered RKE2 and K3s clusters. To view the manual steps to perform on the downstream cluster to enable the ACE, click [here]({{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/#authorized-cluster-endpoint-support-for-rke2-and-k3s-clusters). diff --git a/versioned_docs/version-2.6/overview/architecture/architecture.md b/versioned_docs/version-2.6/overview/architecture/architecture.md deleted file mode 100644 index a6c09157de9..00000000000 --- a/versioned_docs/version-2.6/overview/architecture/architecture.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Architecture -weight: 1 ---- - -This section focuses on the Rancher server, its components, and how Rancher communicates with downstream Kubernetes clusters. - -For information on the different ways that Rancher can be installed, refer to the [overview of installation options.]({{}}/rancher/v2.6/en/installation/#overview-of-installation-options) - -For a list of main features of the Rancher API server, refer to the [overview section.]({{}}/rancher/v2.6/en/overview/#features-of-the-rancher-api-server) - -For guidance about setting up the underlying infrastructure for the Rancher server, refer to the [architecture recommendations.]({{}}/rancher/v2.6/en/overview/architecture-recommendations) - -> This section assumes a basic familiarity with Docker and Kubernetes. For a brief explanation of how Kubernetes components work together, refer to the [concepts]({{}}/rancher/v2.6/en/overview/concepts) page. - -This section covers the following topics: - -- [Rancher server architecture](#rancher-server-architecture) -- [Communicating with downstream user clusters](#communicating-with-downstream-user-clusters) - - [The authentication proxy](#1-the-authentication-proxy) - - [Cluster controllers and cluster agents](#2-cluster-controllers-and-cluster-agents) - - [Node agents](#3-node-agents) - - [Authorized cluster endpoint (ACE)](#4-authorized-cluster-endpoint-ace) -- [Important files](#important-files) -- [Tools for provisioning Kubernetes clusters](#tools-for-provisioning-kubernetes-clusters) -- [Rancher server components and source code](#rancher-server-components-and-source-code) - -# Rancher Server Architecture - -The majority of Rancher 2.x software runs on the Rancher Server. Rancher Server includes all the software components used to manage the entire Rancher deployment. - -The figure below illustrates the high-level architecture of Rancher 2.x. The figure depicts a Rancher Server installation that manages two downstream Kubernetes clusters: one created by RKE and another created by Amazon EKS (Elastic Kubernetes Service). - -For the best performance and security, we recommend a dedicated Kubernetes cluster for the Rancher management server. Running user workloads on this cluster is not advised. After deploying Rancher, you can [create or import clusters]({{}}/rancher/v2.6/en/cluster-provisioning/) for running your workloads. - -The diagram below shows how users can manipulate both [Rancher-launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) clusters and [hosted Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/) clusters through Rancher's authentication proxy: - -
Managing Kubernetes Clusters through Rancher's Authentication Proxy
- -![Architecture]({{}}/img/rancher/rancher-architecture-rancher-api-server.svg) - -You can install Rancher on a single node, or on a high-availability Kubernetes cluster. - -A high-availability Kubernetes installation is recommended for production. - -A Docker installation of Rancher is recommended only for development and testing purposes. The ability to migrate Rancher to a high-availability cluster depends on the Rancher version. - -The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster]({{}}/rancher/v2.6/en/backups/migrating-rancher). - -The Rancher server, regardless of the installation method, should always run on nodes that are separate from the downstream user clusters that it manages. If Rancher is installed on a high-availability Kubernetes cluster, it should run on a separate cluster from the cluster(s) it manages. - -# Communicating with Downstream User Clusters - -This section describes how Rancher provisions and manages the downstream user clusters that run your apps and services. - -The below diagram shows how the cluster controllers, cluster agents, and node agents allow Rancher to control downstream clusters. - -
Communicating with Downstream Clusters
- -![Rancher Components]({{}}/img/rancher/rancher-architecture-cluster-controller.svg) - -The following descriptions correspond to the numbers in the diagram above: - -1. [The Authentication Proxy](#1-the-authentication-proxy) -2. [Cluster Controllers and Cluster Agents](#2-cluster-controllers-and-cluster-agents) -3. [Node Agents](#3-node-agents) -4. [Authorized Cluster Endpoint](#4-authorized-cluster-endpoint) - -### 1. The Authentication Proxy - -In this diagram, a user named Bob wants to see all pods running on a downstream user cluster called User Cluster 1. From within Rancher, he can run a `kubectl` command to see -the pods. Bob is authenticated through Rancher's authentication proxy. - -The authentication proxy forwards all Kubernetes API calls to downstream clusters. It integrates with authentication services like local authentication, Active Directory, and GitHub. On every Kubernetes API call, the authentication proxy authenticates the caller and sets the proper Kubernetes impersonation headers before forwarding the call to Kubernetes masters. - -Rancher communicates with Kubernetes clusters using a [service account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/), which provides an identity for processes that run in a pod. - -By default, Rancher generates a [kubeconfig file]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/) that contains credentials for proxying through the Rancher server to connect to the Kubernetes API server on a downstream user cluster. The kubeconfig file (`kube_config_cluster.yml`) contains full access to the cluster. - -### 2. Cluster Controllers and Cluster Agents - -Each downstream user cluster has a cluster agent, which opens a tunnel to the corresponding cluster controller within the Rancher server. - -There is one cluster controller and one cluster agent for each downstream cluster. Each cluster controller: - -- Watches for resource changes in the downstream cluster -- Brings the current state of the downstream cluster to the desired state -- Configures access control policies to clusters and projects -- Provisions clusters by calling the required Docker machine drivers and Kubernetes engines, such as RKE and GKE - -By default, to enable Rancher to communicate with a downstream cluster, the cluster controller connects to the cluster agent. If the cluster agent is not available, the cluster controller can connect to a [node agent](#3-node-agents) instead. - -The cluster agent, also called `cattle-cluster-agent`, is a component that runs in a downstream user cluster. It performs the following tasks: - -- Connects to the Kubernetes API of Rancher-launched Kubernetes clusters -- Manages workloads, pod creation and deployment within each cluster -- Applies the roles and bindings defined in each cluster's global policies -- Communicates between the cluster and Rancher server (through a tunnel to the cluster controller) about events, stats, node info, and health - -### 3. Node Agents - -If the cluster agent (also called `cattle-cluster-agent`) is not available, one of the node agents creates a tunnel to the cluster controller to communicate with Rancher. - -The `cattle-node-agent` is deployed using a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) resource to make sure it runs on every node in a Rancher-launched Kubernetes cluster. It is used to interact with the nodes when performing cluster operations. Examples of cluster operations include upgrading the Kubernetes version and creating or restoring etcd snapshots. - -### 4. Authorized Cluster Endpoint (ACE) - -An authorized cluster endpoint allows users to connect to the Kubernetes API server of a downstream cluster without having to route their requests through the Rancher authentication proxy. - -> The authorized cluster endpoint only works on Rancher-launched Kubernetes clusters. In other words, it only works in clusters where Rancher [used RKE]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters) to provision the cluster. The ACE is not available for clusters in a hosted Kubernetes provider, such as Amazon's EKS. - -> The [ACE is available for registered RKE2 and K3s clusters]({{}}/rancher/v2.6/en/cluster-provisioning/registered-clusters/#authorized-cluster-endpoint-support-for-rke2-and-k3s-clusters) as of Rancher v2.6.3. - -There are two main reasons why a user might need the authorized cluster endpoint: - -- To access a downstream user cluster while Rancher is down -- To reduce latency in situations where the Rancher server and downstream cluster are separated by a long distance - -The `kube-api-auth` microservice is deployed to provide the user authentication functionality for the authorized cluster endpoint. When you access the user cluster using `kubectl`, the cluster's Kubernetes API server authenticates you by using the `kube-api-auth` service as a webhook. - -Like the authorized cluster endpoint, the `kube-api-auth` authentication service is also only available for Rancher-launched Kubernetes clusters. - -> **Example scenario:** Let's say that the Rancher server is located in the United States, and User Cluster 1 is located in Australia. A user, Alice, also lives in Australia. Alice can manipulate resources in User Cluster 1 by using the Rancher UI, but her requests will have to be sent from Australia to the Rancher server in the United States, then be proxied back to Australia, where the downstream user cluster is. The geographical distance may cause significant latency, which Alice can reduce by using the authorized cluster endpoint. - -With this endpoint enabled for the downstream cluster, Rancher generates an extra Kubernetes context in the kubeconfig file in order to connect directly to the cluster. This file has the credentials for `kubectl` and `helm`. - -You will need to use a context defined in this kubeconfig file to access the cluster if Rancher goes down. Therefore, we recommend exporting the kubeconfig file so that if Rancher goes down, you can still use the credentials in the file to access your cluster. For more information, refer to the section on accessing your cluster with [kubectl and the kubeconfig file.]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl) - -# Important Files - -The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster: - -- `rancher-cluster.yml`: The RKE cluster configuration file. -- `kube_config_cluster.yml`: The Kubeconfig file for the cluster, this file contains credentials for full access to the cluster. You can use this file to authenticate with a Rancher-launched Kubernetes cluster if Rancher goes down. -- `rancher-cluster.rkestate`: The Kubernetes cluster state file. This file contains credentials for full access to the cluster. Note: This state file is only created when using RKE v0.2.0 or higher. - -> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file. - -For more information on connecting to a cluster without the Rancher authentication proxy and other configuration options, refer to the [kubeconfig file]({{}}/rancher/v2.6/en/cluster-admin/cluster-access/kubectl/) documentation. - -# Tools for Provisioning Kubernetes Clusters - -The tools that Rancher uses to provision downstream user clusters depends on the type of cluster that is being provisioned. - -### Rancher Launched Kubernetes for Nodes Hosted in an Infrastructure Provider - -Rancher can dynamically provision nodes in a provider such as Amazon EC2, DigitalOcean, Azure, or vSphere, then install Kubernetes on them. - -Rancher provisions this type of cluster using [RKE](https://github.com/rancher/rke) and [docker-machine.](https://github.com/rancher/machine) - -### Rancher Launched Kubernetes for Custom Nodes - -When setting up this type of cluster, Rancher installs Kubernetes on existing nodes, which creates a custom cluster. - -Rancher provisions this type of cluster using [RKE.](https://github.com/rancher/rke) - -### Hosted Kubernetes Providers - -When setting up this type of cluster, Kubernetes is installed by providers such as Google Kubernetes Engine, Amazon Elastic Container Service for Kubernetes, or Azure Kubernetes Service. - -Rancher provisions this type of cluster using [kontainer-engine.](https://github.com/rancher/kontainer-engine) - -### Registered Kubernetes Clusters - -In this type of cluster, Rancher connects to a Kubernetes cluster that has already been set up. Therefore, Rancher does not provision Kubernetes, but only sets up the Rancher agents to communicate with the cluster. - -# Rancher Server Components and Source Code - -This diagram shows each component that the Rancher server is composed of: - -![Rancher Components]({{}}/img/rancher/rancher-architecture-rancher-components.svg) - -The GitHub repositories for Rancher can be found at the following links: - -- [Main Rancher server repository](https://github.com/rancher/rancher) -- [Rancher UI](https://github.com/rancher/ui) -- [Rancher API UI](https://github.com/rancher/api-ui) -- [Norman,](https://github.com/rancher/norman) Rancher's API framework -- [Types](https://github.com/rancher/types) -- [Rancher CLI](https://github.com/rancher/cli) -- [Catalog applications](https://github.com/rancher/helm) - -This is a partial list of the most important Rancher repositories. For more details about Rancher source code, refer to the section on [contributing to Rancher.]({{}}/rancher/v2.6/en/contributing/#repositories) To see all libraries and projects used in Rancher, see the [`go.mod` file](https://github.com/rancher/rancher/blob/master/go.mod) in the `rancher/rancher` repository. diff --git a/versioned_docs/version-2.6/overview/concepts/concepts.md b/versioned_docs/version-2.6/overview/concepts/concepts.md deleted file mode 100644 index 5cd01b9460c..00000000000 --- a/versioned_docs/version-2.6/overview/concepts/concepts.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Kubernetes Concepts -weight: 4 ---- - -This page explains concepts related to Kubernetes that are important for understanding how Rancher works. The descriptions below provide a simplified overview of Kubernetes components. For more details, refer to the [official documentation on Kubernetes components.](https://kubernetes.io/docs/concepts/overview/components/) - -This section covers the following topics: - -- [About Docker](#about-docker) -- [About Kubernetes](#about-kubernetes) -- [What is a Kubernetes Cluster?](#what-is-a-kubernetes-cluster) -- [Roles for Nodes in Kubernetes Clusters](#roles-for-nodes-in-kubernetes-clusters) - - [etcd Nodes](#etcd-nodes) - - [Controlplane Nodes](#controlplane-nodes) - - [Worker Nodes](#worker-nodes) -- [About Helm](#about-helm) - -# About Docker - -Docker is the container packaging and runtime standard. Developers build container images from Dockerfiles and distribute container images from Docker registries. [Docker Hub](https://hub.docker.com) is the most popular public registry. Many organizations also set up private Docker registries. Docker is primarily used to manage containers on individual nodes. - ->**Note:** Although Rancher 1.6 supported Docker Swarm clustering technology, it is no longer supported in Rancher 2.x due to the success of Kubernetes. - -# About Kubernetes - -Kubernetes is the container cluster management standard. YAML files specify containers and other resources that form an application. Kubernetes performs functions such as scheduling, scaling, service discovery, health check, secret management, and configuration management. - -# What is a Kubernetes Cluster? - -A cluster is a group of computers that work together as a single system. - -A _Kubernetes Cluster_ is a cluster that uses the [Kubernetes container-orchestration system](https://kubernetes.io/) to deploy, maintain, and scale Docker containers, allowing your organization to automate application operations. - -# Roles for Nodes in Kubernetes Clusters - -Each computing resource in a Kubernetes cluster is called a _node_. Nodes can be either bare-metal servers or virtual machines. Kubernetes classifies nodes into three types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. - -A Kubernetes cluster consists of at least one etcd, controlplane, and worker node. - -### etcd Nodes - -Rancher uses etcd as a data store in both single node and high-availability installations. In Kubernetes, etcd is also a role for nodes that store the cluster state. - -The state of a Kubernetes cluster is maintained in [etcd.](https://kubernetes.io/docs/concepts/overview/components/#etcd) The etcd nodes run the etcd database. - -The etcd database component is a distributed key-value store used as Kubernetes storage for all cluster data, such as cluster coordination and state management. It is recommended to run etcd on multiple nodes so that there's always a backup available for failover. - -Although you can run etcd on just one node, etcd requires a majority of nodes, a quorum, to agree on updates to the cluster state. The cluster should always contain enough healthy etcd nodes to form a quorum. For a cluster with n members, a quorum is (n/2)+1. For any odd-sized cluster, adding one node will always increase the number of nodes necessary for a quorum. - -Three etcd nodes is generally sufficient for smaller clusters and five etcd nodes for large clusters. - -### Controlplane Nodes - -Controlplane nodes run the Kubernetes API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your cluster maintains your configuration. Because all cluster data is stored on your etcd nodes, control plane nodes are stateless. You can run control plane on a single node, although three or more nodes are recommended for redundancy. Additionally, a single node can share the control plane and etcd roles. - -### Worker Nodes - -Each [worker node](https://kubernetes.io/docs/concepts/architecture/nodes/) runs the following: - -- **Kubelets:** An agent that monitors the state of the node, ensuring your containers are healthy. -- **Workloads:** The containers and pods that hold your apps, as well as other types of deployments. - -Worker nodes also run storage and networking drivers, and ingress controllers when required. You create as many worker nodes as necessary to run your [workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/). - -# About Helm - -For high-availability installations of Rancher, Helm is the tool used to install Rancher on a Kubernetes cluster. - -Helm is the package management tool of choice for Kubernetes. Helm charts provide templating syntax for Kubernetes YAML manifest documents. With Helm we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at [https://helm.sh/](https://helm.sh). - -For more information on service accounts and cluster role binding, refer to the [Kubernetes documentation.](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) diff --git a/versioned_docs/version-2.6/overview/overview.md b/versioned_docs/version-2.6/overview/overview.md deleted file mode 100644 index 8840c78bf82..00000000000 --- a/versioned_docs/version-2.6/overview/overview.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Overview -weight: 1 ---- - -Rancher is a container management platform built for organizations that deploy containers in production. Rancher makes it easy to run Kubernetes everywhere, meet IT requirements, and empower DevOps teams. - -# Run Kubernetes Everywhere - -Kubernetes has become the container orchestration standard. Most cloud and virtualization vendors now offer it as standard infrastructure. Rancher users have the choice of creating Kubernetes clusters with Rancher Kubernetes Engine (RKE) or cloud Kubernetes services, such as GKE, AKS, and EKS. Rancher users can also import and manage their existing Kubernetes clusters created using any Kubernetes distribution or installer. - -# Meet IT Requirements - -Rancher supports centralized authentication, access control, and monitoring for all Kubernetes clusters under its control. For example, you can: - -- Use your Active Directory credentials to access Kubernetes clusters hosted by cloud vendors, such as GKE. -- Setup and enforce access control and security policies across all users, groups, projects, clusters, and clouds. -- View the health and capacity of your Kubernetes clusters from a single-pane-of-glass. - -# Empower DevOps Teams - -Rancher provides an intuitive user interface for DevOps engineers to manage their application workload. The user does not need to have in-depth knowledge of Kubernetes concepts to start using Rancher. Rancher catalog contains a set of useful DevOps tools. Rancher is certified with a wide selection of cloud native ecosystem products, including, for example, security tools, monitoring systems, container registries, and storage and networking drivers. - -The following figure illustrates the role Rancher plays in IT and DevOps organizations. Each team deploys their applications on the public or private clouds they choose. IT administrators gain visibility and enforce policies across all users, clusters, and clouds. - -![Platform]({{}}/img/rancher/platform.png) - -# Features of the Rancher API Server - -The Rancher API server is built on top of an embedded Kubernetes API server and an etcd database. It implements the following functionalities: - -### Authorization and Role-Based Access Control - -- **User management:** The Rancher API server [manages user identities]({{}}/rancher/v2.6/en/admin-settings/authentication/) that correspond to external authentication providers like Active Directory or GitHub, in addition to local users. -- **Authorization:** The Rancher API server manages [access control]({{}}/rancher/v2.6/en/admin-settings/rbac/) and [security]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/) policies. - -### Working with Kubernetes - -- **Provisioning Kubernetes clusters:** The Rancher API server can [provision Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/) on existing nodes, or perform [Kubernetes upgrades.]({{}}/rancher/v2.6/en/cluster-admin/upgrading-kubernetes) -- **Catalog management:** Rancher provides the ability to use a [catalog of Helm charts]({{}}/rancher/v2.6/en/helm-charts/) that make it easy to repeatedly deploy applications. -- **Managing projects:** A project is a group of multiple namespaces and access control policies within a cluster. A project is a Rancher concept, not a Kubernetes concept, which allows you to manage multiple namespaces as a group and perform Kubernetes operations in them. The Rancher UI provides features for [project administration]({{}}/rancher/v2.6/en/project-admin/) and for [managing applications within projects.]({{}}/rancher/v2.6/en/k8s-in-rancher/) -- **Pipelines:** Setting up a [pipeline]({{}}/rancher/v2.6/en/project-admin/pipelines/) can help developers deliver new software as quickly and efficiently as possible. Within Rancher, you can configure pipelines for each of your Rancher projects. -- **Istio:** Our [integration with Istio]({{}}/rancher/v2.6/en/istio/) is designed so that a Rancher operator, such as an administrator or cluster owner, can deliver Istio to developers. Then developers can use Istio to enforce security policies, troubleshoot problems, or manage traffic for green/blue deployments, canary deployments, or A/B testing. - -### Working with Cloud Infrastructure - -- **Tracking nodes:** The Rancher API server tracks identities of all the [nodes]({{}}/rancher/v2.6/en/cluster-admin/nodes/) in all clusters. -- **Setting up infrastructure:** When configured to use a cloud provider, Rancher can dynamically provision [new nodes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/) and [persistent storage]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) in the cloud. - -### Cluster Visibility - -- **Logging:** Rancher can integrate with a variety of popular logging services and tools that exist outside of your Kubernetes clusters. -- **Monitoring:** Using Rancher, you can monitor the state and processes of your cluster nodes, Kubernetes components, and software deployments through integration with Prometheus, a leading open-source monitoring solution. -- **Alerting:** To keep your clusters and applications healthy and driving your organizational productivity forward, you need to stay informed of events occurring in your clusters and projects, both planned and unplanned. - -# Editing Downstream Clusters with Rancher - -The options and settings available for an existing cluster change based on the method that you used to provision it. For example, only clusters [provisioned by RKE]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) have **Cluster Options** available for editing. - -After a cluster is created with Rancher, a cluster administrator can manage cluster membership, enable pod security policies, and manage node pools, among [other options.]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/) - -The following table summarizes the options and settings available for each cluster type: - -import ClusterCapabilitiesTable from '/rancher/v2.6/en/shared-files/_cluster-capabilities-table.md'; - - diff --git a/versioned_docs/version-2.6/pipelines/concepts/concepts.md b/versioned_docs/version-2.6/pipelines/concepts/concepts.md deleted file mode 100644 index 1f603f02810..00000000000 --- a/versioned_docs/version-2.6/pipelines/concepts/concepts.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Concepts -weight: 1 ---- - -The purpose of this page is to explain common concepts and terminology related to pipelines. - -- **Pipeline:** - - A _pipeline_ is a software delivery process that is broken into different stages and steps. Setting up a pipeline can help developers deliver new software as quickly and efficiently as possible. Within Rancher, you can configure pipelines for each of your Rancher projects. A pipeline is based on a specific repository. It defines the process to build, test, and deploy your code. Rancher uses the [pipeline as code](https://jenkins.io/doc/book/pipeline-as-code/) model. Pipeline configuration is represented as a pipeline file in the source code repository, using the file name `.rancher-pipeline.yml` or `.rancher-pipeline.yaml`. - -- **Stages:** - - A pipeline stage consists of multiple steps. Stages are executed in the order defined in the pipeline file. The steps in a stage are executed concurrently. A stage starts when all steps in the former stage finish without failure. - -- **Steps:** - - A pipeline step is executed inside a specified stage. A step fails if it exits with a code other than `0`. If a step exits with this failure code, the entire pipeline fails and terminates. - -- **Workspace:** - - The workspace is the working directory shared by all pipeline steps. In the beginning of a pipeline, source code is checked out to the workspace. The command for every step bootstraps in the workspace. During a pipeline execution, the artifacts from a previous step will be available in future steps. The working directory is an ephemeral volume and will be cleaned out with the executor pod when a pipeline execution is finished. - -Typically, pipeline stages include: - -- **Build:** - - Each time code is checked into your repository, the pipeline automatically clones the repo and builds a new iteration of your software. Throughout this process, the software is typically reviewed by automated tests. - -- **Publish:** - - After the build is completed, either a Docker image is built and published to a Docker registry or a catalog template is published. - -- **Deploy:** - - After the artifacts are published, you would release your application so users could start using the updated product. diff --git a/versioned_docs/version-2.6/pipelines/config/config.md b/versioned_docs/version-2.6/pipelines/config/config.md deleted file mode 100644 index 333d4aff51f..00000000000 --- a/versioned_docs/version-2.6/pipelines/config/config.md +++ /dev/null @@ -1,643 +0,0 @@ ---- -title: Pipeline Configuration Reference -weight: 1 ---- - -In this section, you'll learn how to configure pipelines. - -- [Step Types](#step-types) -- [Step Type: Run Script](#step-type-run-script) -- [Step Type: Build and Publish Images](#step-type-build-and-publish-images) -- [Step Type: Publish Catalog Template](#step-type-publish-catalog-template) -- [Step Type: Deploy YAML](#step-type-deploy-yaml) -- [Step Type: Deploy Catalog App](#step-type-deploy-catalog-app) -- [Notifications](#notifications) -- [Timeouts](#timeouts) -- [Triggers and Trigger Rules](#triggers-and-trigger-rules) -- [Environment Variables](#environment-variables) -- [Secrets](#secrets) -- [Pipeline Variable Substitution Reference](#pipeline-variable-substitution-reference) -- [Global Pipeline Execution Settings](#global-pipeline-execution-settings) - - [Executor Quota](#executor-quota) - - [Resource Quota for Executors](#resource-quota-for-executors) - - [Custom CA](#custom-ca) -- [Persistent Data for Pipeline Components](#persistent-data-for-pipeline-components) -- [Example rancher-pipeline.yml](#example-rancher-pipeline-yml) - -# Step Types - -Within each stage, you can add as many steps as you'd like. When there are multiple steps in one stage, they run concurrently. - -Step types include: - -- [Run Script](#step-type-run-script) -- [Build and Publish Images](#step-type-build-and-publish-images) -- [Publish Catalog Template](#step-type-publish-catalog-template) -- [Deploy YAML](#step-type-deploy-yaml) -- [Deploy Catalog App](#step-type-deploy-catalog-app) - - - -### Configuring Steps By UI - -If you haven't added any stages, click **Configure pipeline for this branch** to configure the pipeline through the UI. - -1. Add stages to your pipeline execution by clicking **Add Stage**. - - 1. Enter a **Name** for each stage of your pipeline. - 1. For each stage, you can configure [trigger rules](#triggers-and-trigger-rules) by clicking on **Show Advanced Options**. Note: this can always be updated at a later time. - -1. After you've created a stage, start [adding steps](#step-types) by clicking **Add a Step**. You can add multiple steps to each stage. - -### Configuring Steps by YAML - -For each stage, you can add multiple steps. Read more about each [step type](#step-types) and the advanced options to get all the details on how to configure the YAML. This is only a small example of how to have multiple stages with a singular step in each stage. - -```yaml -# example -stages: - - name: Build something - # Conditions for stages - when: - branch: master - event: [ push, pull_request ] - # Multiple steps run concurrently - steps: - - runScriptConfig: - image: busybox - shellScript: date -R - - name: Publish my image - steps: - - publishImageConfig: - dockerfilePath: ./Dockerfile - buildContext: . - tag: rancher/rancher:v2.0.0 - # Optionally push to remote registry - pushRemote: true - registry: reg.example.com -``` -# Step Type: Run Script - -The **Run Script** step executes arbitrary commands in the workspace inside a specified container. You can use it to build, test and do more, given whatever utilities the base image provides. For your convenience, you can use variables to refer to metadata of a pipeline execution. Please refer to the [pipeline variable substitution reference](#pipeline-variable-substitution-reference) for the list of available variables. - -### Configuring Script by UI - -1. From the **Step Type** drop-down, choose **Run Script** and fill in the form. - -1. Click **Add**. - -### Configuring Script by YAML -```yaml -# example -stages: -- name: Build something - steps: - - runScriptConfig: - image: golang - shellScript: go build -``` -# Step Type: Build and Publish Images - -The **Build and Publish Image** step builds and publishes a Docker image. This process requires a Dockerfile in your source code's repository to complete successfully. - -The option to publish an image to an insecure registry is not exposed in the UI, but you can specify an environment variable in the YAML that allows you to publish an image insecurely. - -### Configuring Building and Publishing Images by UI -1. From the **Step Type** drop-down, choose **Build and Publish**. - -1. Fill in the rest of the form. Descriptions for each field are listed below. When you're done, click **Add**. - - Field | Description | - ---------|----------| - Dockerfile Path | The relative path to the Dockerfile in the source code repo. By default, this path is `./Dockerfile`, which assumes the Dockerfile is in the root directory. You can set it to other paths in different use cases (`./path/to/myDockerfile` for example). | - Image Name | The image name in `name:tag` format. The registry address is not required. For example, to build `example.com/repo/my-image:dev`, enter `repo/my-image:dev`. | - Push image to remote repository | An option to set the registry that publishes the image that's built. To use this option, enable it and choose a registry from the drop-down. If this option is disabled, the image is pushed to the internal registry. | - Build Context

(**Show advanced options**)| By default, the root directory of the source code (`.`). For more details, see the Docker [build command documentation](https://docs.docker.com/engine/reference/commandline/build/). - -### Configuring Building and Publishing Images by YAML - -You can use specific arguments for Docker daemon and the build. They are not exposed in the UI, but they are available in pipeline YAML format, as indicated in the example below. Available environment variables include: - -Variable Name | Description -------------------------|------------------------------------------------------------ -PLUGIN_DRY_RUN | Disable docker push -PLUGIN_DEBUG | Docker daemon executes in debug mode -PLUGIN_MIRROR | Docker daemon registry mirror -PLUGIN_INSECURE | Docker daemon allows insecure registries -PLUGIN_BUILD_ARGS | Docker build args, a comma separated list - -
- -```yaml -# This example shows an environment variable being used -# in the Publish Image step. This variable allows you to -# publish an image to an insecure registry: - -stages: -- name: Publish Image - steps: - - publishImageConfig: - dockerfilePath: ./Dockerfile - buildContext: . - tag: repo/app:v1 - pushRemote: true - registry: example.com - env: - PLUGIN_INSECURE: "true" -``` - -# Step Type: Publish Catalog Template - -The **Publish Catalog Template** step publishes a version of a catalog app template (i.e. Helm chart) to a git hosted chart repository. It generates a git commit and pushes it to your chart repository. This process requires a chart folder in your source code's repository and a pre-configured secret in the dedicated pipeline namespace to complete successfully. Any variables in the [pipeline variable substitution reference](#pipeline-variable-substitution-reference) is supported for any file in the chart folder. - -### Configuring Publishing a Catalog Template by UI - -1. From the **Step Type** drop-down, choose **Publish Catalog Template**. - -1. Fill in the rest of the form. Descriptions for each field are listed below. When you're done, click **Add**. - - Field | Description | - ---------|----------| - Chart Folder | The relative path to the chart folder in the source code repo, where the `Chart.yaml` file is located. | - Catalog Template Name | The name of the template. For example, wordpress. | - Catalog Template Version | The version of the template you want to publish, it should be consistent with the version defined in the `Chart.yaml` file. | - Protocol | You can choose to publish via HTTP(S) or SSH protocol. | - Secret | The secret that stores your Git credentials. You need to create a secret in dedicated pipeline namespace in the project before adding this step. If you use HTTP(S) protocol, store Git username and password in `USERNAME` and `PASSWORD` key of the secret. If you use SSH protocol, store Git deploy key in `DEPLOY_KEY` key of the secret. After the secret is created, select it in this option. | - Git URL | The Git URL of the chart repository that the template will be published to. | - Git Branch | The Git branch of the chart repository that the template will be published to. | - Author Name | The author name used in the commit message. | - Author Email | The author email used in the commit message. | - - -### Configuring Publishing a Catalog Template by YAML - -You can add **Publish Catalog Template** steps directly in the `.rancher-pipeline.yml` file. - -Under the `steps` section, add a step with `publishCatalogConfig`. You will provide the following information: - -* Path: The relative path to the chart folder in the source code repo, where the `Chart.yaml` file is located. -* CatalogTemplate: The name of the template. -* Version: The version of the template you want to publish, it should be consistent with the version defined in the `Chart.yaml` file. -* GitUrl: The git URL of the chart repository that the template will be published to. -* GitBranch: The git branch of the chart repository that the template will be published to. -* GitAuthor: The author name used in the commit message. -* GitEmail: The author email used in the commit message. -* Credentials: You should provide Git credentials by referencing secrets in dedicated pipeline namespace. If you publish via SSH protocol, inject your deploy key to the `DEPLOY_KEY` environment variable. If you publish via HTTP(S) protocol, inject your username and password to `USERNAME` and `PASSWORD` environment variables. - -```yaml -# example -stages: -- name: Publish Wordpress Template - steps: - - publishCatalogConfig: - path: ./charts/wordpress/latest - catalogTemplate: wordpress - version: ${CICD_GIT_TAG} - gitUrl: git@github.com:myrepo/charts.git - gitBranch: master - gitAuthor: example-user - gitEmail: user@example.com - envFrom: - - sourceName: publish-keys - sourceKey: DEPLOY_KEY -``` - -# Step Type: Deploy YAML - -This step deploys arbitrary Kubernetes resources to the project. This deployment requires a Kubernetes manifest file to be present in the source code repository. Pipeline variable substitution is supported in the manifest file. You can view an example file at [GitHub](https://github.com/rancher/pipeline-example-go/blob/master/deployment.yaml). Please refer to the [pipeline variable substitution reference](#pipeline-variable-substitution-reference) for the list of available variables. - -### Configure Deploying YAML by UI - -1. From the **Step Type** drop-down, choose **Deploy YAML** and fill in the form. - -1. Enter the **YAML Path**, which is the path to the manifest file in the source code. - -1. Click **Add**. - -### Configure Deploying YAML by YAML - -```yaml -# example -stages: -- name: Deploy - steps: - - applyYamlConfig: - path: ./deployment.yaml -``` - -# Step Type :Deploy Catalog App - -The **Deploy Catalog App** step deploys a catalog app in the project. It will install a new app if it is not present, or upgrade an existing one. - -### Configure Deploying Catalog App by UI - -1. From the **Step Type** drop-down, choose **Deploy Catalog App**. - -1. Fill in the rest of the form. Descriptions for each field are listed below. When you're done, click **Add**. - - Field | Description | - ---------|----------| - Catalog | The catalog from which the app template will be used. | - Template Name | The name of the app template. For example, wordpress. | - Template Version | The version of the app template you want to deploy. | - Namespace | The target namespace where you want to deploy the app. | - App Name | The name of the app you want to deploy. | - Answers | Key-value pairs of answers used to deploy the app. | - - -### Configure Deploying Catalog App by YAML - -You can add **Deploy Catalog App** steps directly in the `.rancher-pipeline.yml` file. - -Under the `steps` section, add a step with `applyAppConfig`. You will provide the following information: - -* CatalogTemplate: The ID of the template. This can be found by clicking `Launch app` and selecting `View details` for the app. It is the last part of the URL. -* Version: The version of the template you want to deploy. -* Answers: Key-value pairs of answers used to deploy the app. -* Name: The name of the app you want to deploy. -* TargetNamespace: The target namespace where you want to deploy the app. - -```yaml -# example -stages: -- name: Deploy App - steps: - - applyAppConfig: - catalogTemplate: cattle-global-data:library-mysql - version: 0.3.8 - answers: - persistence.enabled: "false" - name: testmysql - targetNamespace: test -``` - -# Timeouts - -By default, each pipeline execution has a timeout of 60 minutes. If the pipeline execution cannot complete within its timeout period, the pipeline is aborted. - -### Configuring Timeouts by UI - -Enter a new value in the **Timeout** field. - -### Configuring Timeouts by YAML - -In the `timeout` section, enter the timeout value in minutes. - -```yaml -# example -stages: - - name: Build something - steps: - - runScriptConfig: - image: busybox - shellScript: ls -# timeout in minutes -timeout: 30 -``` - -# Notifications - -You can enable notifications to any notifiers based on the build status of a pipeline. Before enabling notifications, Rancher recommends setting up notifiers so it will be easy to add recipients immediately. - -### Configuring Notifications by UI - -1. Within the **Notification** section, turn on notifications by clicking **Enable**. - -1. Select the conditions for the notification. You can select to get a notification for the following statuses: `Failed`, `Success`, `Changed`. For example, if you want to receive notifications when an execution fails, select **Failed**. - -1. If you don't have any existing notifiers, Rancher will provide a warning that no notifiers are set up and provide a link to be able to go to the notifiers page. Follow the [instructions]({{}}/rancher/v2.0-v2.4/en/cluster-admin/tools/notifiers) to add a notifier. If you already have notifiers, you can add them to the notification by clicking the **Add Recipient** button. - - > **Note:** Notifiers are configured at a cluster level and require a different level of permissions. - -1. For each recipient, select which notifier type from the dropdown. Based on the type of notifier, you can use the default recipient or override the recipient with a different one. For example, if you have a notifier for _Slack_, you can update which channel to send the notification to. You can add additional notifiers by clicking **Add Recipient**. - -### Configuring Notifications by YAML - -In the `notification` section, you will provide the following information: - -* **Recipients:** This will be the list of notifiers/recipients that will receive the notification. - * **Notifier:** The ID of the notifier. This can be found by finding the notifier and selecting **View in API** to get the ID. - * **Recipient:** Depending on the type of the notifier, the "default recipient" can be used or you can override this with a different recipient. For example, when configuring a slack notifier, you select a channel as your default recipient, but if you wanted to send notifications to a different channel, you can select a different recipient. -* **Condition:** Select which conditions of when you want the notification to be sent. -* **Message (Optional):** If you want to change the default notification message, you can edit this in the yaml. Note: This option is not available in the UI. - -```yaml -# Example -stages: - - name: Build something - steps: - - runScriptConfig: - image: busybox - shellScript: ls -notification: - recipients: - - # Recipient - recipient: "#mychannel" - # ID of Notifier - notifier: "c-wdcsr:n-c9pg7" - - recipient: "test@example.com" - notifier: "c-wdcsr:n-lkrhd" - # Select which statuses you want the notification to be sent - condition: ["Failed", "Success", "Changed"] - # Ability to override the default message (Optional) - message: "my-message" -``` - -# Triggers and Trigger Rules - -After you configure a pipeline, you can trigger it using different methods: - -- **Manually:** - - After you configure a pipeline, you can trigger a build using the latest CI definition from Rancher UI. When a pipeline execution is triggered, Rancher dynamically provisions a Kubernetes pod to run your CI tasks and then remove it upon completion. - -- **Automatically:** - - When you enable a repository for a pipeline, webhooks are automatically added to the version control system. When project users interact with the repo by pushing code, opening pull requests, or creating a tag, the version control system sends a webhook to Rancher Server, triggering a pipeline execution. - - To use this automation, webhook management permission is required for the repository. Therefore, when users authenticate and fetch their repositories, only those on which they have webhook management permission will be shown. - -Trigger rules can be created to have fine-grained control of pipeline executions in your pipeline configuration. Trigger rules come in two types: - -- **Run this when:** This type of rule starts the pipeline, stage, or step when a trigger explicitly occurs. - -- **Do Not Run this when:** This type of rule skips the pipeline, stage, or step when a trigger explicitly occurs. - -If all conditions evaluate to `true`, then the pipeline/stage/step is executed. Otherwise it is skipped. When a pipeline is skipped, none of the pipeline is executed. When a stage/step is skipped, it is considered successful and follow-up stages/steps continue to run. - -Wildcard character (`*`) expansion is supported in `branch` conditions. - -This section covers the following topics: - -- [Configuring pipeline triggers](#configuring-pipeline-triggers) -- [Configuring stage triggers](#configuring-stage-triggers) -- [Configuring step triggers](#configuring-step-triggers) -- [Configuring triggers by YAML](#configuring-triggers-by-yaml) - -### Configuring Pipeline Triggers - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. From the repository for which you want to manage trigger rules, select the vertical **⋮ > Edit Config**. -1. Click on **Show Advanced Options**. -1. In the **Trigger Rules** section, configure rules to run or skip the pipeline. - - 1. Click **Add Rule**. In the **Value** field, enter the name of the branch that triggers the pipeline. - - 1. **Optional:** Add more branches that trigger a build. - -1. Click **Done**. - -### Configuring Stage Triggers - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. From the repository for which you want to manage trigger rules, select the vertical **⋮ > Edit Config**. -1. Find the **stage** that you want to manage trigger rules, click the **Edit** icon for that stage. -1. Click **Show advanced options**. -1. In the **Trigger Rules** section, configure rules to run or skip the stage. - - 1. Click **Add Rule**. - - 1. Choose the **Type** that triggers the stage and enter a value. - - | Type | Value | - | ------ | -------------------------------------------------------------------- | - | Branch | The name of the branch that triggers the stage. | - | Event | The type of event that triggers the stage. Values are: `Push`, `Pull Request`, `Tag` | - -1. Click **Save**. - -### Configuring Step Triggers - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. From the repository for which you want to manage trigger rules, select the vertical **⋮ > Edit Config**. -1. Find the **step** that you want to manage trigger rules, click the **Edit** icon for that step. -1. Click **Show advanced options**. -1. In the **Trigger Rules** section, configure rules to run or skip the step. - - 1. Click **Add Rule**. - - 1. Choose the **Type** that triggers the step and enter a value. - - | Type | Value | - | ------ | -------------------------------------------------------------------- | - | Branch | The name of the branch that triggers the step. | - | Event | The type of event that triggers the step. Values are: `Push`, `Pull Request`, `Tag` | - -1. Click **Save**. - - -### Configuring Triggers by YAML - -```yaml -# example -stages: - - name: Build something - # Conditions for stages - when: - branch: master - event: [ push, pull_request ] - # Multiple steps run concurrently - steps: - - runScriptConfig: - image: busybox - shellScript: date -R - # Conditions for steps - when: - branch: [ master, dev ] - event: push -# branch conditions for the pipeline -branch: - include: [ master, feature/*] - exclude: [ dev ] -``` - -# Environment Variables - -When configuring a pipeline, certain [step types](#step-types) allow you to use environment variables to configure the step's script. - -### Configuring Environment Variables by UI - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. From the pipeline for which you want to edit build triggers, select **⋮ > Edit Config**. -1. Within one of the stages, find the **step** that you want to add an environment variable for, click the **Edit** icon. -1. Click **Show advanced options**. -1. Click **Add Variable**, and then enter a key and value in the fields that appear. Add more variables if needed. -1. Add your environment variable(s) into either the script or file. -1. Click **Save**. - -### Configuring Environment Variables by YAML - -```yaml -# example -stages: - - name: Build something - steps: - - runScriptConfig: - image: busybox - shellScript: echo ${FIRST_KEY} && echo ${SECOND_KEY} - env: - FIRST_KEY: VALUE - SECOND_KEY: VALUE2 -``` - -# Secrets - -If you need to use security-sensitive information in your pipeline scripts (like a password), you can pass them in using Kubernetes [secrets]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/). - -### Prerequisite -Create a secret in the same project as your pipeline, or explicitly in the namespace where pipeline build pods run. -
- ->**Note:** Secret injection is disabled on [pull request events](#triggers-and-trigger-rules). - -### Configuring Secrets by UI - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. From the pipeline for which you want to edit build triggers, select **⋮ > Edit Config**. -1. Within one of the stages, find the **step** that you want to use a secret for, click the **Edit** icon. -1. Click **Show advanced options**. -1. Click **Add From Secret**. Select the secret file that you want to use. Then choose a key. Optionally, you can enter an alias for the key. -1. Click **Save**. - -### Configuring Secrets by YAML - -```yaml -# example -stages: - - name: Build something - steps: - - runScriptConfig: - image: busybox - shellScript: echo ${ALIAS_ENV} - # environment variables from project secrets - envFrom: - - sourceName: my-secret - sourceKey: secret-key - targetKey: ALIAS_ENV -``` - -# Pipeline Variable Substitution Reference - -For your convenience, the following variables are available for your pipeline configuration scripts. During pipeline executions, these variables are replaced by metadata. You can reference them in the form of `${VAR_NAME}`. - -Variable Name | Description -------------------------|------------------------------------------------------------ -`CICD_GIT_REPO_NAME` | Repository name (Github organization omitted). -`CICD_GIT_URL` | URL of the Git repository. -`CICD_GIT_COMMIT` | Git commit ID being executed. -`CICD_GIT_BRANCH` | Git branch of this event. -`CICD_GIT_REF` | Git reference specification of this event. -`CICD_GIT_TAG` | Git tag name, set on tag event. -`CICD_EVENT` | Event that triggered the build (`push`, `pull_request` or `tag`). -`CICD_PIPELINE_ID` | Rancher ID for the pipeline. -`CICD_EXECUTION_SEQUENCE` | Build number of the pipeline. -`CICD_EXECUTION_ID` | Combination of `{CICD_PIPELINE_ID}-{CICD_EXECUTION_SEQUENCE}`. -`CICD_REGISTRY` | Address for the Docker registry for the previous publish image step, available in the Kubernetes manifest file of a `Deploy YAML` step. -`CICD_IMAGE` | Name of the image built from the previous publish image step, available in the Kubernetes manifest file of a `Deploy YAML` step. It does not contain the image tag.

[Example](https://github.com/rancher/pipeline-example-go/blob/master/deployment.yaml) - -# Global Pipeline Execution Settings - -After configuring a version control provider, there are several options that can be configured globally on how pipelines are executed in Rancher. - -### Changing Pipeline Settings - -> **Prerequisite:** Because the pipelines app was deprecated in favor of Fleet, you will need to turn on the feature flag for legacy features before using pipelines. Note that pipelines in Kubernetes 1.21+ are no longer supported. -> -> 1. In the upper left corner, click **☰ > Global Settings**. -> 1. Click **Feature Flags**. -> 1. Go to the `legacy` feature flag and click **⋮ > Activate**. - -To edit these settings: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. - -- [Executor Quota](#executor-quota) -- [Resource Quota for Executors](#resource-quota-for-executors) -- [Custom CA](#custom-ca) - -### Executor Quota - -Select the maximum number of pipeline executors. The _executor quota_ decides how many builds can run simultaneously in the project. If the number of triggered builds exceeds the quota, subsequent builds will queue until a vacancy opens. By default, the quota is `2`. A value of `0` or less removes the quota limit. - -### Resource Quota for Executors - -Configure compute resources for Jenkins agent containers. When a pipeline execution is triggered, a build pod is dynamically provisioned to run your CI tasks. Under the hood, A build pod consists of one Jenkins agent container and one container for each pipeline step. You can [manage compute resources](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/) for every containers in the pod. - -Edit the **Memory Reservation**, **Memory Limit**, **CPU Reservation** or **CPU Limit**, then click **Update Limit and Reservation**. - -To configure compute resources for pipeline-step containers: - -You can configure compute resources for pipeline-step containers in the `.rancher-pipeline.yml` file. - -In a step, you will provide the following information: - -* **CPU Reservation (`CpuRequest`)**: CPU request for the container of a pipeline step. -* **CPU Limit (`CpuLimit`)**: CPU limit for the container of a pipeline step. -* **Memory Reservation (`MemoryRequest`)**: Memory request for the container of a pipeline step. -* **Memory Limit (`MemoryLimit`)**: Memory limit for the container of a pipeline step. - -```yaml -# example -stages: - - name: Build something - steps: - - runScriptConfig: - image: busybox - shellScript: ls - cpuRequest: 100m - cpuLimit: 1 - memoryRequest:100Mi - memoryLimit: 1Gi - - publishImageConfig: - dockerfilePath: ./Dockerfile - buildContext: . - tag: repo/app:v1 - cpuRequest: 100m - cpuLimit: 1 - memoryRequest:100Mi - memoryLimit: 1Gi -``` - ->**Note:** Rancher sets default compute resources for pipeline steps except for `Build and Publish Images` and `Run Script` steps. You can override the default value by specifying compute resources in the same way. - -### Custom CA - -If you want to use a version control provider with a certificate from a custom/internal CA root, the CA root certificates need to be added as part of the version control provider configuration in order for the pipeline build pods to succeed. - -1. Click **Edit cacerts**. - -1. Paste in the CA root certificates and click **Save cacerts**. - -**Result:** Pipelines can be used and new pods will be able to work with the self-signed-certificate. - -# Persistent Data for Pipeline Components - -The internal Docker registry and the Minio workloads use ephemeral volumes by default. This default storage works out-of-the-box and makes testing easy, but you lose the build images and build logs if the node running the Docker Registry or Minio fails. In most cases this is fine. If you want build images and logs to survive node failures, you can configure the Docker Registry and Minio to use persistent volumes. - -For details on setting up persistent storage for pipelines, refer to [this page.]({{}}/rancher/v2.6/en/pipelines/storage) - -# Example rancher-pipeline.yml - -An example pipeline configuration file is on [this page.]({{}}/rancher/v2.6/en/pipelines/example) diff --git a/versioned_docs/version-2.6/pipelines/example-repos/example-repos.md b/versioned_docs/version-2.6/pipelines/example-repos/example-repos.md deleted file mode 100644 index 9147e1f751b..00000000000 --- a/versioned_docs/version-2.6/pipelines/example-repos/example-repos.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Example Repositories -weight: 500 ---- - -Rancher ships with several example repositories that you can use to familiarize yourself with pipelines. We recommend configuring and testing the example repository that most resembles your environment before using pipelines with your own repositories in a production environment. Use this example repository as a sandbox for repo configuration, build demonstration, etc. Rancher includes example repositories for: - -- Go -- Maven -- php - -> **Prerequisites:** -> -> - The example repositories are only available if you have not [configured a version control provider]({{}}/rancher/v2.6/en/project-admin/pipelines). -> - Because the pipelines app was deprecated in favor of Fleet, you will need to turn on the feature flag for legacy features before using pipelines. -> - Note that pipelines in Kubernetes 1.21+ are no longer supported. -> -> 1. In the upper left corner, click **☰ > Global Settings**. -> 1. Click **Feature Flags**. -> 1. Go to the `legacy` feature flag and click **⋮ > Activate**. - -To start using these example repositories, - -1. [Enable the example repositories](#1-enable-the-example-repositories) -2. [View the example pipeline](#2-view-the-example-pipeline) -3. [Run the example pipeline](#3-run-the-example-pipeline) - -### 1. Enable the Example Repositories - -By default, the example pipeline repositories are disabled. Enable one (or more) to test out the pipeline feature and see how it works. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. In the **Pipelines** tab, click **Configure Repositories**. - - >**Note:** Example repositories only display if you haven't fetched your own repos. - -1. Click **Enable** for one of the example repos (e.g., `https://github.com/rancher/pipeline-example-go.git`). Then click **Done**. - -**Results:** - -- The example repository is enabled to work with a pipeline is available in the **Pipeline** tab. - -- The following workloads are deployed to a new namespace: - - - `docker-registry` - - `jenkins` - - `minio` - -### 2. View the Example Pipeline - -After enabling an example repository, review the pipeline to see how it is set up. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. In the **Pipelines** tab, click **Configure Repositories**. -1. Find the example repository, select **⋮ > Edit Config**. There are two ways to view the pipeline: - * **Rancher UI**: Click on **Edit Config** or **View/Edit YAML** to view the stages and steps of the pipeline. The YAML view shows the `./rancher-pipeline.yml` file. - -### 3. Run the Example Pipeline - -After enabling an example repository, run the pipeline to see how it works. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. In the **Pipelines** tab, go to the pipeline and select the vertical **⋮ > Run**. - - >**Note:** When you run a pipeline the first time, it takes a few minutes to pull relevant images and provision necessary pipeline components. - -**Result:** The pipeline runs. You can see the results in the logs. - -### What's Next? - -For detailed information about setting up your own pipeline for your repository, [configure a version control provider]({{}}/rancher/v2.6/en/project-admin/pipelines), enable a repository and finally configure your pipeline. diff --git a/versioned_docs/version-2.6/pipelines/example/example.md b/versioned_docs/version-2.6/pipelines/example/example.md deleted file mode 100644 index 3c0be119356..00000000000 --- a/versioned_docs/version-2.6/pipelines/example/example.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Example YAML File -weight: 501 ---- - -Pipelines can be configured either through the UI or using a yaml file in the repository, i.e. `.rancher-pipeline.yml` or `.rancher-pipeline.yaml`. - -In the [pipeline configuration reference]({{}}/rancher/v2.6/en/pipelines/config), we provide examples of how to configure each feature using the Rancher UI or using YAML configuration. - -Below is a full example `rancher-pipeline.yml` for those who want to jump right in. - -```yaml -# example -stages: - - name: Build something - # Conditions for stages - when: - branch: master - event: [ push, pull_request ] - # Multiple steps run concurrently - steps: - - runScriptConfig: - image: busybox - shellScript: echo ${FIRST_KEY} && echo ${ALIAS_ENV} - # Set environment variables in container for the step - env: - FIRST_KEY: VALUE - SECOND_KEY: VALUE2 - # Set environment variables from project secrets - envFrom: - - sourceName: my-secret - sourceKey: secret-key - targetKey: ALIAS_ENV - - runScriptConfig: - image: busybox - shellScript: date -R - # Conditions for steps - when: - branch: [ master, dev ] - event: push - - name: Publish my image - steps: - - publishImageConfig: - dockerfilePath: ./Dockerfile - buildContext: . - tag: rancher/rancher:v2.0.0 - # Optionally push to remote registry - pushRemote: true - registry: reg.example.com - - name: Deploy some workloads - steps: - - applyYamlConfig: - path: ./deployment.yaml -# branch conditions for the pipeline -branch: - include: [ master, feature/*] - exclude: [ dev ] -# timeout in minutes -timeout: 30 -notification: - recipients: - - # Recipient - recipient: "#mychannel" - # ID of Notifier - notifier: "c-wdcsr:n-c9pg7" - - recipient: "test@example.com" - notifier: "c-wdcsr:n-lkrhd" - # Select which statuses you want the notification to be sent - condition: ["Failed", "Success", "Changed"] - # Ability to override the default message (Optional) - message: "my-message" -``` diff --git a/versioned_docs/version-2.6/pipelines/pipelines.md b/versioned_docs/version-2.6/pipelines/pipelines.md deleted file mode 100644 index 8b0fcca0c71..00000000000 --- a/versioned_docs/version-2.6/pipelines/pipelines.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -title: Pipelines -weight: 10 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -> As of Rancher v2.5, Git-based deployment pipelines are now deprecated. We recommend handling pipelines with Rancher Continuous Delivery powered by [Fleet]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet). To get to Fleet in Rancher, click ☰ > Continuous Delivery. -> ->**Notice:** -> -> - Pipelines in Kubernetes 1.21+ are no longer supported. -> - Fleet does not replace Rancher pipelines; the distinction is that Rancher pipelines are now powered by Fleet. - -Rancher's pipeline provides a simple CI/CD experience. Use it to automatically checkout code, run builds or scripts, publish Docker images or catalog applications, and deploy the updated software to users. - -Setting up a pipeline can help developers deliver new software as quickly and efficiently as possible. Using Rancher, you can integrate with a GitHub repository to setup a continuous integration (CI) pipeline. - -After configuring Rancher and GitHub, you can deploy containers running Jenkins to automate a pipeline execution: - -- Build your application from code to image. -- Validate your builds. -- Deploy your build images to your cluster. -- Run unit tests. -- Run regression tests. - ->**Note:** Rancher's pipeline provides a simple CI/CD experience, but it does not offer the full power and flexibility of and is not a replacement of enterprise-grade Jenkins or other CI tools your team uses. - -This section covers the following topics: - -- [Concepts](#concepts) -- [How Pipelines Work](#how-pipelines-work) -- [Roles-based Access Control for Pipelines](#roles-based-access-control-for-pipelines) -- [Setting up Pipelines](#setting-up-pipelines) - - [Configure version control providers](#1-configure-version-control-providers) - - [Configure repositories](#2-configure-repositories) - - [Configure the pipeline](#3-configure-the-pipeline) -- [Pipeline Configuration Reference](#pipeline-configuration-reference) -- [Running your Pipelines](#running-your-pipelines) -- [Triggering a Pipeline](#triggering-a-pipeline) - - [Modifying the Event Triggers for the Repository](#modifying-the-event-triggers-for-the-repository) - -# Concepts - -For an explanation of concepts and terminology used in this section, refer to [this page.]({{}}/rancher/v2.6/en/pipelines/concepts) - -# How Pipelines Work - -After enabling the ability to use pipelines in a project, you can configure multiple pipelines in each project. Each pipeline is unique and can be configured independently. - -A pipeline is configured off of a group of files that are checked into source code repositories. Users can configure their pipelines either through the Rancher UI or by adding a `.rancher-pipeline.yml` into the repository. - -Before pipelines can be configured, you will need to configure authentication to your version control provider, e.g. GitHub, GitLab, Bitbucket. If you haven't configured a version control provider, you can always use [Rancher's example repositories]({{}}/rancher/v2.6/en/pipelines/example-repos/) to view some common pipeline deployments. - -When you configure a pipeline in one of your projects, a namespace specifically for the pipeline is automatically created. The following components are deployed to it: - - - **Jenkins:** - - The pipeline's build engine. Because project users do not directly interact with Jenkins, it's managed and locked. - - >**Note:** There is no option to use existing Jenkins deployments as the pipeline engine. - - - **Docker Registry:** - - Out-of-the-box, the default target for your build-publish step is an internal Docker Registry. However, you can make configurations to push to a remote registry instead. The internal Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users. Images are not persisted beyond the lifetime of the pipeline and should only be used in pipeline runs. If you need to access your images outside of pipeline runs, please push to an external registry. - - - **Minio:** - - Minio storage is used to store the logs for pipeline executions. - - >**Note:** The managed Jenkins instance works statelessly, so don't worry about its data persistency. The Docker Registry and Minio instances use ephemeral volumes by default, which is fine for most use cases. If you want to make sure pipeline logs can survive node failures, you can configure persistent volumes for them, as described in [data persistency for pipeline components]({{}}/rancher/v2.6/en/pipelines/storage). - -# Roles-based Access Control for Pipelines - -If you can access a project, you can enable repositories to start building pipelines. - -Only [administrators]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/), [cluster owners or members]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles), or [project owners]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles) can configure version control providers and manage global pipeline execution settings. - -Project members can only configure repositories and pipelines. - -# Setting up Pipelines - -### Prerequisite - -> **Prerequisite:** Because the pipelines app was deprecated in favor of Fleet, you will need to turn on the feature flag for legacy features before using pipelines. Note that pipelines in Kubernetes 1.21+ are no longer supported. -> -> 1. In the upper left corner, click **☰ > Global Settings**. -> 1. Click **Feature Flags**. -> 1. Go to the `legacy` feature flag and click **⋮ > Activate**. - -1. [Configure version control providers](#1-configure-version-control-providers) -2. [Configure repositories](#2-configure-repositories) -3. [Configure the pipeline](#3-configure-the-pipeline) - -### 1. Configure Version Control Providers - -Before you can start configuring a pipeline for your repository, you must configure and authorize a version control provider: - -- GitHub -- GitLab -- Bitbucket - -Select your provider's tab below and follow the directions. - - - - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Click the **Configuration** tab. -1. Follow the directions displayed to **Setup a Github application**. Rancher redirects you to Github to set up an OAuth App in Github. -1. From GitHub, copy the **Client ID** and **Client Secret**. Paste them into Rancher. -1. If you're using GitHub for enterprise, select **Use a private github enterprise installation**. Enter the host address of your GitHub installation. -1. Click **Authenticate**. - - - - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Click the **Configuration** tab. -1. Click **GitLab**. -1. Follow the directions displayed to **Setup a GitLab application**. Rancher redirects you to GitLab. -1. From GitLab, copy the **Application ID** and **Secret**. Paste them into Rancher. -1. If you're using GitLab for enterprise setup, select **Use a private gitlab enterprise installation**. Enter the host address of your GitLab installation. -1. Click **Authenticate**. - ->**Note:** -> 1. Pipeline uses Gitlab [v4 API](https://docs.gitlab.com/ee/api/v3_to_v4.html) and the supported Gitlab version is 9.0+. -> 2. If you use GitLab 10.7+ and your Rancher setup is in a local network, enable the **Allow requests to the local network from hooks and services** option in GitLab admin settings. - - - - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Click the **Configuration** tab. -1. Click **Bitbucket** and leave **Use Bitbucket Cloud** selected by default. -1. Follow the directions displayed to **Setup a Bitbucket Cloud application**. Rancher redirects you to Bitbucket to setup an OAuth consumer in Bitbucket. -1. From Bitbucket, copy the consumer **Key** and **Secret**. Paste them into Rancher. -1. Click **Authenticate**. - - - - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Click the **Configuration** tab. -1. Click **Bitbucket** and choose the **Use private Bitbucket Server setup** option. -1. Follow the directions displayed to **Setup a Bitbucket Server application**. -1. Enter the host address of your Bitbucket server installation. -1. Click **Authenticate**. - ->**Note:** -> Bitbucket server needs to do SSL verification when sending webhooks to Rancher. Please ensure that Rancher server's certificate is trusted by the Bitbucket server. There are two options: -> -> 1. Setup Rancher server with a certificate from a trusted CA. -> 1. If you're using self-signed certificates, import Rancher server's certificate to the Bitbucket server. For instructions, see the Bitbucket server documentation for [configuring self-signed certificates](https://confluence.atlassian.com/bitbucketserver/if-you-use-self-signed-certificates-938028692.html). -> - - - - -**Result:** After the version control provider is authenticated, you will be automatically re-directed to start configuring which repositories you want start using with a pipeline. - -### 2. Configure Repositories - -After the version control provider is authorized, you are automatically re-directed to start configuring which repositories that you want start using pipelines with. Even if someone else has set up the version control provider, you will see their repositories and can build a pipeline. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Click on **Configure Repositories**. - -1. A list of repositories are displayed. If you are configuring repositories the first time, click on **Authorize & Fetch Your Own Repositories** to fetch your repository list. - -1. For each repository that you want to set up a pipeline, click on **Enable**. - -1. When you're done enabling all your repositories, click on **Done**. - -**Results:** You have a list of repositories that you can start configuring pipelines for. - -### 3. Configure the Pipeline - -Now that repositories are added to your project, you can start configuring the pipeline by adding automated stages and steps. For your convenience, there are multiple built-in step types for dedicated tasks. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Find the repository that you want to set up a pipeline for. -1. Configure the pipeline through the UI or using a yaml file in the repository, i.e. `.rancher-pipeline.yml` or `.rancher-pipeline.yaml`. Pipeline configuration is split into stages and steps. Stages must fully complete before moving onto the next stage, but steps in a stage run concurrently. For each stage, you can add different step types. Note: As you build out each step, there are different advanced options based on the step type. Advanced options include trigger rules, environment variables, and secrets. For more information on configuring the pipeline through the UI or the YAML file, refer to the [pipeline configuration reference.]({{}}/rancher/v2.6/en/pipelines/config) - - * If you are going to use the UI, select the vertical **⋮ > Edit Config** to configure the pipeline using the UI. After the pipeline is configured, you must view the YAML file and push it to the repository. - * If you are going to use the YAML file, select the vertical **⋮ > View/Edit YAML** to configure the pipeline. If you choose to use a YAML file, you need to push it to the repository after any changes in order for it to be updated in the repository. When editing the pipeline configuration, it takes a few moments for Rancher to check for an existing pipeline configuration. - -1. Select which `branch` to use from the list of branches. - -1. Optional: Set up notifications. - -1. Set up the trigger rules for the pipeline. - -1. Enter a **Timeout** for the pipeline. - -1. When all the stages and steps are configured, click **Done**. - -**Results:** Your pipeline is now configured and ready to be run. - - -# Pipeline Configuration Reference - -Refer to [this page]({{}}/rancher/v2.6/en/pipelines/config) for details on how to configure a pipeline to: - -- Run a script -- Build and publish images -- Publish catalog templates -- Deploy YAML -- Deploy a catalog app - -The configuration reference also covers how to configure: - -- Notifications -- Timeouts -- The rules that trigger a pipeline -- Environment variables -- Secrets - - -# Running your Pipelines - -Run your pipeline for the first time. Find your pipeline and select the vertical **⋮ > Run**. - -During this initial run, your pipeline is tested, and the following pipeline components are deployed to your project as workloads in a new namespace dedicated to the pipeline: - -- `docker-registry` -- `jenkins` -- `minio` - -This process takes several minutes. When it completes, you can view each pipeline component from the project **Workloads** tab. - -# Triggering a Pipeline - -When a repository is enabled, a webhook is automatically set in the version control provider. By default, the pipeline is triggered by a **push** event to a repository, but you can modify the event(s) that trigger running the pipeline. - -Available Events: - -* **Push**: Whenever a commit is pushed to the branch in the repository, the pipeline is triggered. -* **Pull Request**: Whenever a pull request is made to the repository, the pipeline is triggered. -* **Tag**: When a tag is created in the repository, the pipeline is triggered. - -> **Note:** This option doesn't exist for Rancher's [example repositories]({{}}/rancher/v2.6/en/pipelines/example-repos/). - -### Modifying the Event Triggers for the Repository - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Go to the cluster where you want to configure pipelines and click **Explore**. -1. In the dropdown menu in the top navigation bar, select the project where you want to configure pipelines. -1. In the left navigation bar, click **Legacy > Project > Pipelines**. -1. Find the repository where you want to modify the event triggers. Select the vertical **⋮ > Setting**. -1. Select which event triggers (**Push**, **Pull Request** or **Tag**) you want for the repository. -1. Click **Save**. diff --git a/versioned_docs/version-2.6/pipelines/storage/storage.md b/versioned_docs/version-2.6/pipelines/storage/storage.md deleted file mode 100644 index e22bdc5b511..00000000000 --- a/versioned_docs/version-2.6/pipelines/storage/storage.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Configuring Persistent Data for Pipeline Components -weight: 600 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -The pipelines' internal Docker registry and the Minio workloads use ephemeral volumes by default. This default storage works out-of-the-box and makes testing easy, but you lose the build images and build logs if the node running the Docker Registry or Minio fails. In most cases this is fine. If you want build images and logs to survive node failures, you can configure the Docker Registry and Minio to use persistent volumes. - -This section assumes that you understand how persistent storage works in Kubernetes. For more information, refer to the section on [how storage works.]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/how-storage-works/) - ->**Prerequisites (for both parts A and B):** -> ->[Persistent volumes]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) must be available for the cluster. - -### A. Configuring Persistent Data for Docker Registry - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Workload**. - -1. Find the `docker-registry` workload and select **⋮ > Edit**. - -1. Scroll to the **Volumes** section and expand it. Make one of the following selections from the **Add Volume** menu, which is near the bottom of the section: - - - **Add Volume > Add a new persistent volume (claim)** - - **Add Volume > Use an existing persistent volume (claim)** - -1. Complete the form that displays to choose a persistent volume for the internal Docker registry. - - - - 1. Enter a **Name** for the volume claim. - 1. Select a volume claim **Source**: - - If you select **Use a Storage Class to provision a new persistent volume**, select a storage class and enter a **Capacity**. - - If you select **Use an existing persistent volume**, choose a **Persistent Volume** from the drop-down. - 1. From the **Customize** section, choose the read/write access for the volume. - 1. Click **Define**. - - - - - 1. Enter a **Name** for the volume claim. - 1. Choose a **Persistent Volume Claim** from the dropdown. - 1. From the **Customize** section, choose the read/write access for the volume. - 1. Click **Define**. - - - - -1. From the **Mount Point** field, enter `/var/lib/registry`, which is the data storage path inside the Docker registry container. - -1. Click **Upgrade**. - -### B. Configuring Persistent Data for Minio - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Workload**. -1. Go to the `minio` workload and select **⋮ > Edit**. - -1. Scroll to the **Volumes** section and expand it. Make one of the following selections from the **Add Volume** menu, which is near the bottom of the section: - - - **Add Volume > Add a new persistent volume (claim)** - - **Add Volume > Use an existing persistent volume (claim)** - -1. Complete the form that displays to choose a persistent volume for the internal Docker registry. - - - - 1. Enter a **Name** for the volume claim. - 1. Select a volume claim **Source**: - - If you select **Use a Storage Class to provision a new persistent volume**, select a storage class and enter a **Capacity**. - - If you select **Use an existing persistent volume**, choose a **Persistent Volume** from the drop-down. - 1. From the **Customize** section, choose the read/write access for the volume. - 1. Click **Define**. - - - - - 1. Enter a **Name** for the volume claim. - 1. Choose a **Persistent Volume Claim** from the drop-down. - 1. From the **Customize** section, choose the read/write access for the volume. - 1. Click **Define**. - - - - -1. From the **Mount Point** field, enter `/data`, which is the data storage path inside the Minio container. - -1. Click **Upgrade**. - -**Result:** Persistent storage is configured for your pipeline components. diff --git a/versioned_docs/version-2.6/project-admin/namespaces/namespaces.md b/versioned_docs/version-2.6/project-admin/namespaces/namespaces.md deleted file mode 100644 index c7f328842ab..00000000000 --- a/versioned_docs/version-2.6/project-admin/namespaces/namespaces.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Namespaces -weight: 2520 ---- - -Within Rancher, you can further divide projects into different [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/), which are virtual clusters within a project backed by a physical cluster. Should you require another level of organization beyond projects and the `default` namespace, you can use multiple namespaces to isolate applications and resources. - -Although you assign resources at the project level so that each namespace in the project can use them, you can override this inheritance by assigning resources explicitly to a namespace. - -Resources that you can assign directly to namespaces include: - -- [Workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/) -- [Load Balancers/Ingress]({{}}/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/) -- [Service Discovery Records]({{}}/rancher/v2.6/en/k8s-in-rancher/service-discovery/) -- [Persistent Volume Claims]({{}}/rancher/v2.6/en/cluster-admin/volumes-and-storage/) -- [Certificates]({{}}/rancher/v2.6/en/k8s-in-rancher/certificates/) -- [ConfigMaps]({{}}/rancher/v2.6/en/k8s-in-rancher/configmaps/) -- [Registries]({{}}/rancher/v2.6/en/k8s-in-rancher/registries/) -- [Secrets]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/) - -To manage permissions in a vanilla Kubernetes cluster, cluster admins configure role-based access policies for each namespace. With Rancher, user permissions are assigned on the project level instead, and permissions are automatically inherited by any namespace owned by the particular project. - -> **Note:** If you create a namespace with `kubectl`, it may be unusable because `kubectl` doesn't require your new namespace to be scoped within a project that you have access to. If your permissions are restricted to the project level, it is better to [create a namespace through Rancher]({{}}/rancher/v2.6/en/project-admin/namespaces) to ensure that you will have permission to access the namespace. - - -### Creating Namespaces - -Create a new namespace to isolate apps and resources in a project. - ->**Tip:** When working with project resources that you can assign to a namespace (i.e., [workloads]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/deploy-workloads/), [certificates]({{}}/rancher/v2.6/en/k8s-in-rancher/certificates/), [ConfigMaps]({{}}/rancher/v2.6/en/k8s-in-rancher/configmaps), etc.) you can create a namespace on the fly. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to create a namespace and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Go to the project where you want to add a namespace and click **Create Namespace**. Alternately, go to **Not in a Project** to create a namespace not associated with a project. - -1. **Optional:** If your project has [Resource Quotas]({{}}/rancher/v2.6/en/project-admin/resource-quotas) in effect, you can override the default resource **Limits** (which places a cap on the resources that the namespace can consume). - -1. Enter a **Name** and then click **Create**. - -**Result:** Your namespace is added to the project. You can begin assigning cluster resources to the namespace. - -### Moving Namespaces to Another Project - -Cluster admins and members may occasionally need to move a namespace to another project, such as when you want a different team to start using the application. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to move a namespace and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Go to the namespace you want to move and click **⋮ > Move**. - -1. Select the namespace(s) that you want to move to a different project. Then click **Move**. You can move multiple namespaces at one. - - >**Notes:** - > - >- Don't move the namespaces in the `System` project. Moving these namespaces can adversely affect cluster networking. - >- You cannot move a namespace into a project that already has a [resource quota]({{}}/rancher/v2.6/en/project-admin/resource-quotas)configured. - >- If you move a namespace from a project that has a quota set to a project with no quota set, the quota is removed from the namespace. - -1. Choose a new project for the new namespace and then click **Move**. Alternatively, you can remove the namespace from all projects by selecting **None**. - -**Result:** Your namespace is moved to a different project (or is unattached from all projects). If any project resources are attached to the namespace, the namespace releases them and then attached resources from the new project. - -### Editing Namespace Resource Quotas - -You can always override the namespace default limit to provide a specific namespace with access to more (or less) project resources. - -For more information, see how to [edit namespace resource quotas]({{}}/rancher/v2.6/en/project-admin//resource-quotas/override-namespace-default/). \ No newline at end of file diff --git a/versioned_docs/version-2.6/project-admin/pipelines/pipelines.md b/versioned_docs/version-2.6/project-admin/pipelines/pipelines.md deleted file mode 100644 index a64a73e6dcc..00000000000 --- a/versioned_docs/version-2.6/project-admin/pipelines/pipelines.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Rancher's CI/CD Pipelines -description: Use Rancher’s CI/CD pipeline to automatically checkout code, run builds or scripts, publish Docker images, and deploy software to users -weight: 4000 ---- -Using Rancher, you can integrate with a GitHub repository to setup a continuous integration (CI) pipeline. - -After configuring Rancher and GitHub, you can deploy containers running Jenkins to automate a pipeline execution: - -- Build your application from code to image. -- Validate your builds. -- Deploy your build images to your cluster. -- Run unit tests. -- Run regression tests. - -For details, refer to the [pipelines]({{}}/rancher/v2.6/en/pipelines) section. \ No newline at end of file diff --git a/versioned_docs/version-2.6/project-admin/pod-security-policies/pod-security-policies.md b/versioned_docs/version-2.6/project-admin/pod-security-policies/pod-security-policies.md deleted file mode 100644 index d7ce7a74ee3..00000000000 --- a/versioned_docs/version-2.6/project-admin/pod-security-policies/pod-security-policies.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Pod Security Policies -weight: 5600 ---- - -> These cluster options are only available for [clusters in which Rancher has launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/). - -You can always assign a pod security policy (PSP) to an existing project if you didn't assign one during creation. - -### Prerequisites - -- Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/). -- Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. For more information, see [the documentation about adding a pod security policy to a cluster]({{}}/rancher/v2.6/en/cluster-admin/pod-security-policy). - -### Applying a Pod Security Policy - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to move a namespace and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Find the project that you want to add a PSP to. From that project, select **⋮ > Edit Config**. -1. From the **Pod Security Policy** drop-down, select the PSP you want to apply to the project. - Assigning a PSP to a project will: - - - Override the cluster's default PSP. - - Apply the PSP to the project. - - Apply the PSP to any namespaces you add to the project later. - -1. Click **Save**. - -**Result:** The PSP is applied to the project and any namespaces added to the project. - ->**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked to determine if they comply with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. \ No newline at end of file diff --git a/versioned_docs/version-2.6/project-admin/project-admin.md b/versioned_docs/version-2.6/project-admin/project-admin.md deleted file mode 100644 index 42d36f0fb22..00000000000 --- a/versioned_docs/version-2.6/project-admin/project-admin.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Project Administration -weight: 9 ---- - -_Projects_ are objects introduced in Rancher that help organize namespaces in your Kubernetes cluster. You can use projects to create multi-tenant clusters, which allows a group of users to share the same underlying resources without interacting with each other's applications. - -In terms of hierarchy: - -- Clusters contain projects -- Projects contain namespaces - -Within Rancher, projects allow you to manage multiple namespaces as a single entity. In native Kubernetes, which does not include projects, features like role-based access rights or cluster resources are assigned to individual namespaces. In clusters where multiple namespaces require the same set of access rights, assigning these rights to each individual namespace can become tedious. Even though all namespaces require the same rights, there's no way to apply those rights to all of your namespaces in a single action. You'd have to repetitively assign these rights to each namespace! - -Rancher projects resolve this issue by allowing you to apply resources and access rights at the project level. Each namespace in the project then inherits these resources and policies, so you only have to assign them to the project once, rather than assigning them to each individual namespace. - -You can use projects to perform actions like: - -- [Assign users access to a group of namespaces]({{}}/rancher/v2.6/en/project-admin/project-members) -- Assign users [specific roles in a project]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles). A role can be owner, member, read-only, or [custom]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles/) -- [Set resource quotas]({{}}/rancher/v2.6/en/project-admin/resource-quotas/) -- [Manage namespaces]({{}}/rancher/v2.6/en/project-admin/namespaces/) -- [Configure tools]({{}}/rancher/v2.6/en/project-admin/tools/) -- [Set up pipelines for continuous integration and deployment]({{}}/rancher/v2.6/en/project-admin/pipelines) -- [Configure pod security policies]({{}}/rancher/v2.6/en/project-admin/pod-security-policies) - -### Authorization - -Non-administrative users are only authorized for project access after an [administrator]({{}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/), [cluster owner or member]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#cluster-roles), or [project owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles) adds them to the project's **Members** tab. - -Whoever creates the project automatically becomes a [project owner]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/#project-roles). - -## Switching between Projects - -To switch between projects, use the drop-down available in the navigation bar. Alternatively, you can switch between projects directly in the navigation bar. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to switch projects and click **Explore**. -1. In the top navigation bar, select the project that you want to open. diff --git a/versioned_docs/version-2.6/project-admin/project-members/project-members.md b/versioned_docs/version-2.6/project-admin/project-members/project-members.md deleted file mode 100644 index 32708445e60..00000000000 --- a/versioned_docs/version-2.6/project-admin/project-members/project-members.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Adding Users to Projects -weight: 2505 ---- - -If you want to provide a user with access and permissions to _specific_ projects and resources within a cluster, assign the user a project membership. - -You can add members to a project as it is created, or add them to an existing project. - ->**Tip:** Want to provide a user with access to _all_ projects within a cluster? See [Adding Cluster Members]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/) instead. - -### Adding Members to a New Project - -You can add members to a project as you create it (recommended if possible). For details on creating a new project, refer to the [cluster administration section.]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/) - -### Adding Members to an Existing Project - -Following project creation, you can add users as project members so that they can access its resources. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to add members to a project and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Go to the project where you want to add members and click **⋮ > Edit Config**. -1. In the **Members** tab, click **Add**. -1. Search for the user or group that you want to add to the project. - - If external authentication is configured: - - - Rancher returns users from your external authentication source as you type. - - - A drop-down allows you to add groups instead of individual users. The dropdown only lists groups that you, the logged in user, are included in. - - >**Note:** If you are logged in as a local user, external users do not display in your search results. - -1. Assign the user or group **Project** roles. - - [What are Project Roles?]({{}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/) - - >**Notes:** - > - >- Users assigned the `Owner` or `Member` role for a project automatically inherit the `namespace creation` role. However, this role is a [Kubernetes ClusterRole](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole), meaning its scope extends to all projects in the cluster. Therefore, users explicitly assigned the `Owner` or `Member` role for a project can create or delete namespaces in other projects they're assigned to, even with only the `Read Only` role assigned. - > - >- By default, the Rancher role of `project-member` inherits from the `Kubernetes-edit` role, and the `project-owner` role inherits from the `Kubernetes-admin` role. As such, both `project-member` and `project-owner` roles will allow for namespace management, including the ability to create and delete namespaces. - > - >- For `Custom` roles, you can modify the list of individual roles available for assignment. - > - > - To add roles to the list, [Add a Custom Role]({{}}/rancher/v2.6/en/admin-settings/rbac/default-custom-roles). - > - To remove roles from the list, [Lock/Unlock Roles]({{}}/rancher/v2.6/en/admin-settings/rbac/locked-roles/). - -**Result:** The chosen users are added to the project. - -- To revoke project membership, select the user and click **Delete**. This action deletes membership, not the user. -- To modify a user's roles in the project, delete them from the project, and then re-add them with modified roles. \ No newline at end of file diff --git a/versioned_docs/version-2.6/project-admin/resource-quotas/override-container-default/override-container-default.md b/versioned_docs/version-2.6/project-admin/resource-quotas/override-container-default/override-container-default.md deleted file mode 100644 index f059b7b51f1..00000000000 --- a/versioned_docs/version-2.6/project-admin/resource-quotas/override-container-default/override-container-default.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Setting Container Default Resource Limits -weight: 3 ---- - -When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required. - -To avoid setting these limits on each and every container during workload creation, a default container resource limit can be specified on the namespace. - -### Editing the Container Default Resource Limit - -Edit the container default resource limit when: - -- You have a CPU or Memory resource quota set on a project, and want to supply the corresponding default values for a container. -- You want to edit the default container resource limit. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to edit the default resource limit and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Find the project that you want to edit the container default resource limit. From that project, select **⋮ > Edit Config**. -1. Expand **Container Default Resource Limit** and edit the values. - -### Resource Limit Propagation - -When the default container resource limit is set at a project level, the parameter will be propagated to any namespace created in the project after the limit has been set. For any existing namespace in a project, this limit will not be automatically propagated. You will need to manually set the default container resource limit for any existing namespaces in the project in order for it to be used when creating any containers. - -You can set a default container resource limit on a project and launch any catalog applications. - -Once a container default resource limit is configured on a namespace, the default will be pre-populated for any containers created in that namespace. These limits/reservations can always be overridden during workload creation. - -### Container Resource Quota Types - -The following resource limits can be configured: - -| Resource Type | Description | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| CPU Limit | The maximum amount of CPU (in [millicores](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu)) allocated to the container.| -| CPU Reservation | The minimum amount of CPU (in millicores) guaranteed to the container. | -| Memory Limit | The maximum amount of memory (in bytes) allocated to the container. | -| Memory Reservation | The minimum amount of memory (in bytes) guaranteed to the container. \ No newline at end of file diff --git a/versioned_docs/version-2.6/project-admin/resource-quotas/override-namespace-default/override-namespace-default.md b/versioned_docs/version-2.6/project-admin/resource-quotas/override-namespace-default/override-namespace-default.md deleted file mode 100644 index cf26b09aa65..00000000000 --- a/versioned_docs/version-2.6/project-admin/resource-quotas/override-namespace-default/override-namespace-default.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Overriding the Default Limit for a Namespace -weight: 2 ---- - -Although the **Namespace Default Limit** propagates from the project to each namespace when created, in some cases, you may need to increase (or decrease) the quotas for a specific namespace. In this situation, you can override the default limits by editing the namespace. - -In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/) for `Namespace 3` so that the namespace can access more resources. - -Namespace Default Limit Override -![Namespace Default Limit Override]({{}}/img/rancher/rancher-resource-quota-override.svg) - -How to: [Editing Namespace Resource Quotas]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/) - -### Editing Namespace Resource Quotas - -If there is a resource quota configured for a project, you can override the namespace default limit to provide a specific namespace with access to more (or less) project resources. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to edit a namespace resource quota and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Find the namespace for which you want to edit the resource quota. Click **⋮ > Edit Config**. -1. Edit the resource limits. These limits determine the resources available to the namespace. The limits must be set within the configured project limits. - - For more information about each **Resource Type**, see [the type reference]({{}}/rancher/v2.6/en/project-admin/resource-quotas/quota-type-reference/). - - >**Note:** - > - >- If a resource quota is not configured for the project, these options will not be available. - >- If you enter limits that exceed the configured project limits, Rancher will not let you save your edits. - -**Result:** Your override is applied to the namespace's resource quota. diff --git a/versioned_docs/version-2.6/project-admin/resource-quotas/quota-type-reference/quota-type-reference.md b/versioned_docs/version-2.6/project-admin/resource-quotas/quota-type-reference/quota-type-reference.md deleted file mode 100644 index 7e5f66ed3e9..00000000000 --- a/versioned_docs/version-2.6/project-admin/resource-quotas/quota-type-reference/quota-type-reference.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Resource Quota Type Reference -weight: 4 ---- - -When you create a resource quota, you are configuring the pool of resources available to the project. You can set the following resource limits for the following resource types. - -| Resource Type | Description | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| CPU Limit* | The maximum amount of CPU (in [millicores](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu)) allocated to the project/namespace.1 | -| CPU Reservation* | The minimum amount of CPU (in millicores) guaranteed to the project/namespace.1 | -| Memory Limit* | The maximum amount of memory (in bytes) allocated to the project/namespace.1 | -| Memory Reservation* | The minimum amount of memory (in bytes) guaranteed to the project/namespace.1 | -| Storage Reservation | The minimum amount of storage (in gigabytes) guaranteed to the project/namespace. | -| Services Load Balancers | The maximum number of load balancers services that can exist in the project/namespace. | -| Services Node Ports | The maximum number of node port services that can exist in the project/namespace. | -| Pods | The maximum number of pods that can exist in the project/namespace in a non-terminal state (i.e., pods with a state of `.status.phase in (Failed, Succeeded)` equal to true). | -| Services | The maximum number of services that can exist in the project/namespace. | -| ConfigMaps | The maximum number of ConfigMaps that can exist in the project/namespace. | -| Persistent Volume Claims | The maximum number of persistent volume claims that can exist in the project/namespace. | -| Replications Controllers | The maximum number of replication controllers that can exist in the project/namespace. | -| Secrets | The maximum number of secrets that can exist in the project/namespace. | - ->***** When setting resource quotas, if you set anything related to CPU or Memory (i.e. limits or reservations) on a project / namespace, all containers will require a respective CPU or Memory field set during creation. A container default resource limit can be set at the same time to avoid the need to explicitly set these limits for every workload. See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits) for more details on why this is required. \ No newline at end of file diff --git a/versioned_docs/version-2.6/project-admin/resource-quotas/quotas-for-projects/quotas-for-projects.md b/versioned_docs/version-2.6/project-admin/resource-quotas/quotas-for-projects/quotas-for-projects.md deleted file mode 100644 index 7e2aaf3e869..00000000000 --- a/versioned_docs/version-2.6/project-admin/resource-quotas/quotas-for-projects/quotas-for-projects.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: How Resource Quotas Work in Rancher Projects -weight: 1 ---- - -Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). However, in Rancher, resource quotas have been extended so that you can apply them to projects. - -In a standard Kubernetes deployment, resource quotas are applied to individual namespaces. However, you cannot apply the quota to your namespaces simultaneously with a single action. Instead, the resource quota must be applied multiple times. - -In the following diagram, a Kubernetes administrator is trying to enforce a resource quota without Rancher. The administrator wants to apply a resource quota that sets the same CPU and memory limit to every namespace in his cluster (`Namespace 1-4`) . However, in the base version of Kubernetes, each namespace requires a unique resource quota. The administrator has to create four different resource quotas that have the same specs configured (`Resource Quota 1-4`) and apply them individually. - -Base Kubernetes: Unique Resource Quotas Being Applied to Each Namespace -![Native Kubernetes Resource Quota Implementation]({{}}/img/rancher/kubernetes-resource-quota.svg) - -Resource quotas are a little different in Rancher. In Rancher, you apply a resource quota to the project, and then the quota propagates to each namespace, whereafter Kubernetes enforces your limits using the native version of resource quotas. If you want to change the quota for a specific namespace, you can override it. - -The resource quota includes two limits, which you set while creating or editing a project: - - -- **Project Limits:** - - This set of values configures a total limit for each specified resource shared among all namespaces in the project. - -- **Namespace Default Limits:** - - This set of values configures the default quota limit available for each namespace for each specified resource. - When a namespace is created in the project without overrides, this limit is automatically bound to the namespace and enforced. - - -In the following diagram, a Rancher administrator wants to apply a resource quota that sets the same CPU and memory limit for every namespace in their project (`Namespace 1-4`). However, in Rancher, the administrator can set a resource quota for the project (`Project Resource Quota`) rather than individual namespaces. This quota includes resource limits for both the entire project (`Project Limit`) and individual namespaces (`Namespace Default Limit`). Rancher then propagates the `Namespace Default Limit` quotas to each namespace (`Namespace Resource Quota`) when created. - -Rancher: Resource Quotas Propagating to Each Namespace -![Rancher Resource Quota Implementation]({{}}/img/rancher/rancher-resource-quota.png) - -Let's highlight some more nuanced functionality for namespaces created **_within_** the Rancher UI. If a quota is deleted at the project level, it will also be removed from all namespaces contained within that project, despite any overrides that may exist. Further, updating an existing namespace default limit for a quota at the project level will not result in that value being propagated to existing namespaces in the project; the updated value will only be applied to newly created namespaces in that project. To update a namespace default limit for existing namespaces you can delete and subsequently recreate the quota at the project level with the new default value. This will result in the new default value being applied to all existing namespaces in the project. - -Before creating a namespace in a project, Rancher compares the amounts of the project's available resources and requested resources, regardless of whether they come from the default or overridden limits. -If the requested resources exceed the remaining capacity in the project for those resources, Rancher will assign the namespace the remaining capacity for that resource. - -However, this is not the case with namespaces created **_outside_** of Rancher's UI. For namespaces created via `kubectl`, Rancher -will assign a resource quota that has a **zero** amount for any resource that requested more capacity than what remains in the project. - -To create a namespace in an existing project via `kubectl`, use the `field.cattle.io/projectId` annotation. To override the default -requested quota limit, use the `field.cattle.io/resourceQuota` annotation. -``` -apiVersion: v1 -kind: Namespace -metadata: - annotations: - field.cattle.io/projectId: [your-cluster-ID]:[your-project-ID] - field.cattle.io/resourceQuota: '{"limit":{"limitsCpu":"100m", "limitsMemory":"100Mi", "configMaps": "50"}}' - name: my-ns -``` - -The following table explains the key differences between the two quota types. - -| Rancher Resource Quotas | Kubernetes Resource Quotas | -| ---------------------------------------------------------- | -------------------------------------------------------- | -| Applies to projects and namespace. | Applies to namespaces only. | -| Creates resource pool for all namespaces in project. | Applies static resource limits to individual namespaces. | -| Applies resource quotas to namespaces through propagation. | Applies only to the assigned namespace. diff --git a/versioned_docs/version-2.6/project-admin/resource-quotas/resource-quotas.md b/versioned_docs/version-2.6/project-admin/resource-quotas/resource-quotas.md deleted file mode 100644 index 75e1aea6b90..00000000000 --- a/versioned_docs/version-2.6/project-admin/resource-quotas/resource-quotas.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Project Resource Quotas -weight: 2515 ---- - -In situations where several teams share a cluster, one team may overconsume the resources available: CPU, memory, storage, services, Kubernetes objects like pods or secrets, and so on. To prevent this overconsumption, you can apply a _resource quota_, which is a Rancher feature that limits the resources available to a project or namespace. - -This page is a how-to guide for creating resource quotas in existing projects. - -Resource quotas can also be set when a new project is created. For details, refer to the section on [creating new projects.]({{}}/rancher/v2.6/en/cluster-admin/projects-and-namespaces/#creating-projects) - -Resource quotas in Rancher include the same functionality as the [native version of Kubernetes](https://kubernetes.io/docs/concepts/policy/resource-quotas/). In Rancher, resource quotas have been extended so that you can apply them to projects. For details on how resource quotas work with projects in Rancher, refer to [this page.](./quotas-for-projects) - -### Applying Resource Quotas to Existing Projects - -Edit resource quotas when: - -- You want to limit the resources that a project and its namespaces can use. -- You want to scale the resources available to a project up or down when a research quota is already in effect. - -1. In the upper left corner, click **☰ > Cluster Management**. -1. On the **Clusters** page, go to the cluster where you want to apply a resource quota and click **Explore**. -1. Click **Cluster > Projects/Namespaces**. -1. Find the project that you want to add a resource quota to. From that project, select **⋮ > Edit Config**. - -1. Expand **Resource Quotas** and click **Add Resource**. Alternatively, you can edit existing quotas. - -1. Select a Resource Type. For more information on types, see the [quota type reference.](./quota-type-reference) - -1. Enter values for the **Project Limit** and the **Namespace Default Limit**. - - | Field | Description | - | ----------------------- | -------------------------------------------------------------------------------------------------------- | - | Project Limit | The overall resource limit for the project. | - | Namespace Default Limit | The default resource limit available for each namespace. This limit is propagated to each namespace in the project. The combined limit of all project namespaces shouldn't exceed the project limit. | - -1. **Optional:** Add more quotas. - -1. Click **Create**. - -**Result:** The resource quota is applied to your project and namespaces. When you add more namespaces in the future, Rancher validates that the project can accommodate the namespace. If the project can't allocate the resources, you may still create namespaces, but they will be given a resource quota of 0. Subsequently, Rancher will not allow you to create any resources restricted by this quota. diff --git a/versioned_docs/version-2.6/project-admin/tools/tools.md b/versioned_docs/version-2.6/project-admin/tools/tools.md deleted file mode 100644 index a35a719eb11..00000000000 --- a/versioned_docs/version-2.6/project-admin/tools/tools.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Tools for Logging, Monitoring, and Visibility -weight: 2525 ---- - -Rancher contains a variety of tools that aren't included in Kubernetes to assist in your DevOps operations. Rancher can integrate with external services to help your clusters run more efficiently. Tools are divided into following categories: - - -- [Notifiers and Alerts](#notifiers-and-alerts) -- [Logging](#logging) -- [Monitoring](#monitoring) - - - -## Notifiers and Alerts - -Notifiers and alerts are two features that work together to inform you of events in the Rancher system. Before they can be enabled, the monitoring application must be installed. - -Notifiers are services that inform you of alert events. You can configure notifiers to send alert notifications to staff best suited to take corrective action. Notifications can be sent with Slack, email, PagerDuty, WeChat, and webhooks. - -Alerts are rules that trigger those notifications. Before you can receive alerts, you must configure one or more notifier in Rancher. The scope for alerts can be set at either the cluster or project level. - -## Logging - -Logging is helpful because it allows you to: - -- Capture and analyze the state of your cluster -- Look for trends in your environment -- Save your logs to a safe location outside of your cluster -- Stay informed of events like a container crashing, a pod eviction, or a node dying -- More easily debugg and troubleshoot problems - -Rancher can integrate with Elasticsearch, splunk, kafka, syslog, and fluentd. - -For details, refer to the [logging section.]({{}}/rancher/v2.6/en/logging) - -## Monitoring - -Using Rancher, you can monitor the state and processes of your cluster nodes, Kubernetes components, and software deployments through integration with [Prometheus](https://prometheus.io/), a leading open-source monitoring solution. For details, refer to the [monitoring section.]({{}}/rancher/v2.6/en/monitoring-alerting) diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-marketplace-qs/amazon-aws-marketplace-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-marketplace-qs/amazon-aws-marketplace-qs.md deleted file mode 100644 index bac47239b49..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-marketplace-qs/amazon-aws-marketplace-qs.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: Rancher AWS Marketplace Quick Start -description: Use Amazon EKS to deploy Rancher server. -weight: 110 ---- - -There is now an additional way for you to deploy the Rancher server in AWS by using Amazon EKS. To learn more, see our [Amazon Marketplace listing](https://aws.amazon.com/marketplace/pp/prodview-2yzbnvagmi4as). \ No newline at end of file diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-qs/amazon-aws-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-qs/amazon-aws-qs.md deleted file mode 100644 index f5e80d10091..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/amazon-aws-qs/amazon-aws-qs.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Rancher AWS Quick Start Guide -description: Read this step by step Rancher AWS guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached. -weight: 100 ---- -The following steps will quickly deploy a Rancher server on AWS in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached. - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Prerequisites - ->**Note** ->Deploying to Amazon AWS will incur charges. - -- [Amazon AWS Account](https://aws.amazon.com/account/): An Amazon AWS Account is required to create resources for deploying Rancher and Kubernetes. -- [Amazon AWS Access Key](https://docs.aws.amazon.com/general/latest/gr/managing-aws-access-keys.html): Use this link to follow a tutorial to create an Amazon AWS Access Key if you don't have one yet. -- [IAM Policy created](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-start): Defines the permissions an account attached with this policy has. -- Install [Terraform](https://www.terraform.io/downloads.html): Used to provision the server and cluster in Amazon AWS. - -### Example IAM Policy - -The AWS module just creates an EC2 KeyPair, an EC2 SecurityGroup and an EC2 instance. A simple policy would be: - -``` -{ - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "ec2:*", - "Resource": "*" - } - ] -} -``` - -## Getting Started - -1. Clone [Rancher Quickstart](https://github.com/rancher/quickstart) to a folder using `git clone https://github.com/rancher/quickstart`. - -2. Go into the AWS folder containing the terraform files by executing `cd quickstart/aws`. - -3. Rename the `terraform.tfvars.example` file to `terraform.tfvars`. - -4. Edit `terraform.tfvars` and customize the following variables: - - `aws_access_key` - Amazon AWS Access Key - - `aws_secret_key` - Amazon AWS Secret Key - - `rancher_server_admin_password` - Admin password for created Rancher server - -5. **Optional:** Modify optional variables within `terraform.tfvars`. -See the [Quickstart Readme](https://github.com/rancher/quickstart) and the [AWS Quickstart Readme](https://github.com/rancher/quickstart/tree/master/aws) for more information. -Suggestions include: - - `aws_region` - Amazon AWS region, choose the closest instead of the default (`us-east-1`) - - `prefix` - Prefix for all created resources - - `instance_type` - EC2 instance size used, minimum is `t3a.medium` but `t3a.large` or `t3a.xlarge` could be used if within budget - - `add_windows_node` - If true, an additional Windows worker node is added to the workload cluster - -6. Run `terraform init`. - -7. To initiate the creation of the environment, run `terraform apply --auto-approve`. Then wait for output similar to the following: - - ``` - Apply complete! Resources: 16 added, 0 changed, 0 destroyed. - - Outputs: - - rancher_node_ip = xx.xx.xx.xx - rancher_server_url = https://rancher.xx.xx.xx.xx.sslip.io - workload_node_ip = yy.yy.yy.yy - ``` - -8. Paste the `rancher_server_url` from the output above into the browser. Log in when prompted (default username is `admin`, use the password set in `rancher_server_admin_password`). -9. ssh to the Rancher Server using the `id_rsa` key generated in `quickstart/aws`. - -##### Result - -Two Kubernetes clusters are deployed into your AWS account, one running Rancher Server and the other ready for experimentation deployments. Please note that while this setup is a great way to explore Rancher functionality, a production setup should follow our high availability setup guidelines. SSH keys for the VMs are auto-generated and stored in the module directory. - -## What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{}}/rancher/v2.6/en/quick-start-guide/workload). - -## Destroying the Environment - -1. From the `quickstart/aws` folder, execute `terraform destroy --auto-approve`. - -2. Wait for confirmation that all resources have been destroyed. diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/deployment.md b/versioned_docs/version-2.6/quick-start-guide/deployment/deployment.md deleted file mode 100644 index fa4236b3a6f..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/deployment.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Deploying Rancher Server -weight: 100 ---- - -Use one of the following guides to deploy and provision Rancher and a Kubernetes cluster in the provider of your choice. - -- [AWS](./amazon-aws-qs) (uses Terraform) -- [AWS Marketplace](./amazon-aws-marketplace-qs) (uses Amazon EKS) -- [Azure](./microsoft-azure-qs) (uses Terraform) -- [DigitalOcean](./digital-ocean-qs) (uses Terraform) -- [GCP](./google-gcp-qs) (uses Terraform) -- [Hetzner Cloud](./hetzner-cloud-qs) (uses Terraform) -- [Vagrant](./quickstart-vagrant) -- [Equinix Metal](./equinix-metal-qs) - - -If you prefer, the following guide will take you through the same process in individual steps. Use this if you want to run Rancher in a different provider, on prem, or if you would just like to see how easy it is. - -- [Manual Install](./quickstart-manual-setup) diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/digital-ocean-qs/digital-ocean-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/digital-ocean-qs/digital-ocean-qs.md deleted file mode 100644 index 8afb42b9d33..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/digital-ocean-qs/digital-ocean-qs.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Rancher DigitalOcean Quick Start Guide -description: Read this step by step Rancher DigitalOcean guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached. -weight: 120 ---- -The following steps will quickly deploy a Rancher server on DigitalOcean in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached. - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Prerequisites - ->**Note** ->Deploying to DigitalOcean will incur charges. - -- [DigitalOcean Account](https://www.digitalocean.com): You will require an account on DigitalOcean as this is where the server and cluster will run. -- [DigitalOcean Access Key](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key): Use this link to create a DigitalOcean Access Key if you don't have one. -- [Terraform](https://www.terraform.io/downloads.html): Used to provision the server and cluster to DigitalOcean. - - -## Getting Started - -1. Clone [Rancher Quickstart](https://github.com/rancher/quickstart) to a folder using `git clone https://github.com/rancher/quickstart`. - -2. Go into the DigitalOcean folder containing the terraform files by executing `cd quickstart/do`. - -3. Rename the `terraform.tfvars.example` file to `terraform.tfvars`. - -4. Edit `terraform.tfvars` and customize the following variables: - - `do_token` - DigitalOcean access key - - `rancher_server_admin_password` - Admin password for created Rancher server - -5. **Optional:** Modify optional variables within `terraform.tfvars`. -See the [Quickstart Readme](https://github.com/rancher/quickstart) and the [DO Quickstart Readme](https://github.com/rancher/quickstart/tree/master/do) for more information. -Suggestions include: - - `do_region` - DigitalOcean region, choose the closest instead of the default (`nyc1`) - - `prefix` - Prefix for all created resources - - `droplet_size` - Droplet size used, minimum is `s-2vcpu-4gb` but `s-4vcpu-8gb` could be used if within budget - -6. Run `terraform init`. - -7. To initiate the creation of the environment, run `terraform apply --auto-approve`. Then wait for output similar to the following: - - ``` - Apply complete! Resources: 15 added, 0 changed, 0 destroyed. - - Outputs: - - rancher_node_ip = xx.xx.xx.xx - rancher_server_url = https://rancher.xx.xx.xx.xx.sslip.io - workload_node_ip = yy.yy.yy.yy - ``` - -8. Paste the `rancher_server_url` from the output above into the browser. Log in when prompted (default username is `admin`, use the password set in `rancher_server_admin_password`). -9. ssh to the Rancher Server using the `id_rsa` key generated in `quickstart/do`. - -#### Result - -Two Kubernetes clusters are deployed into your DigitalOcean account, one running Rancher Server and the other ready for experimentation deployments. Please note that while this setup is a great way to explore Rancher functionality, a production setup should follow our high availability setup guidelines. SSH keys for the VMs are auto-generated and stored in the module directory. - -### What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{}}/rancher/v2.6/en/quick-start-guide/workload). - -## Destroying the Environment - -1. From the `quickstart/do` folder, execute `terraform destroy --auto-approve`. - -2. Wait for confirmation that all resources have been destroyed. diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/equinix-metal-qs/equinix-metal-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/equinix-metal-qs/equinix-metal-qs.md deleted file mode 100644 index ad208bd3bf8..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/equinix-metal-qs/equinix-metal-qs.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -title: Rancher Equinix Metal Quick Start -weight: 250 ---- - -## This tutorial walks you through the following: - -- Provisioning an Equinix Metal Server -- Installation of Rancher 2.x -- Creation of your first cluster -- Deployment of an application, Nginx - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. The Docker install is not recommended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Quick Start Outline - -This Quick Start Guide is divided into different tasks for easier consumption. - - - - -1. [Provision a Equinix Metal Host](#1-provision-a-equinix-metal-host) - -1. [Install Rancher](#2-install-rancher) - -1. [Log In](#3-log-in) - -1. [Create the Cluster](#4-create-the-cluster) - - -
- -## Prerequisites - -- An [Equinix Metal account](https://metal.equinix.com/developers/docs/accounts/users/) -- An [Equinix Metal project](https://metal.equinix.com/developers/docs/accounts/projects/) - - -### 1. Provision a Equinix Metal Host - - Begin deoploying an Equinix Metal Host. Equinix Metal Servers can be provisioned by either the Equinix Metal console, api, or cli. You can find instructions on how to deploy with each deployment type on the [Equinix Metal deployment documentation](https://metal.equinix.com/developers/docs/deploy/on-demand/). Yopu can find additional documentation on Equinix Metal server types and prices below. - - [Equinix Metal Server Types](https://metal.equinix.com/developers/docs/servers/about/) - - [Equinix Metal Pricing](https://metal.equinix.com/developers/docs/servers/server-specs/) - - **Note:** - > When provisioning a new Equinix Metal Server via the CLI or API you will need to be able to provide the following information: project-id, plan, metro, and the operating-system - > When using a cloud-hosted virtual machine you need to allow inbound TCP communication to ports 80 and 443. Please see your cloud-host's documentation for information regarding port configuration. - > For a full list of port requirements, refer to [Docker Installation]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/). - > Provision the host according to our [Requirements]({{}}/rancher/v2.6/en/installation/requirements/). - -### 2. Install Rancher - -To install Rancher on your Equinix Metal host, connect to it and then use a shell to install. - -1. Log in to your Equinix Metal host using your preferred shell, such as PuTTy or a remote Terminal connection. - -2. From your shell, enter the following command: - - ``` - sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher - ``` - -**Result:** Rancher is installed. - -### 3. Log In - -Log in to Rancher to begin using the application. After you log in, you'll make some one-time configurations. - -1. Open a web browser and enter the IP address of your host: `https://`. - - Replace `` with your host IP address. - -2. When prompted, create a password for the default `admin` account there cowpoke! - -3. Set the **Rancher Server URL**. The URL can either be an IP address or a host name. However, each node added to your cluster must be able to connect to this URL.

If you use a hostname in the URL, this hostname must be resolvable by DNS on the nodes you want to add to you cluster. - -
- -### 4. Create the Cluster - -Welcome to Rancher! You are now able to create your first Kubernetes cluster. - -In this task, you can use the versatile **Custom** option. This option lets you add _any_ Linux host (cloud-hosted VM, on-prem VM, or bare-metal) to be used in a cluster. - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -2. Choose **Custom**. - -3. Enter a **Cluster Name**. - -4. Skip **Member Roles** and **Cluster Options**. We'll tell you about them later. - -5. Click **Next**. - -6. From **Node Role**, select _all_ the roles: **etcd**, **Control**, and **Worker**. - -7. **Optional**: Rancher auto-detects the IP addresses used for Rancher communication and cluster communication. You can override these using `Public Address` and `Internal Address` in the **Node Address** section. - -8. Skip the **Labels** stuff. It's not important for now. - -9. Copy the command displayed on screen to your clipboard. - -10. Log in to your Linux host using your preferred shell, such as PuTTy or a remote Terminal connection. Run the command copied to your clipboard. - -11. When you finish running the command on your Linux host, click **Done**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -#### Finished - -Congratulations! You have created your first cluster. - -#### What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{}}/rancher/v2.6/en/quick-start-guide/workload). diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/google-gcp-qs/google-gcp-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/google-gcp-qs/google-gcp-qs.md deleted file mode 100644 index b589f810c46..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/google-gcp-qs/google-gcp-qs.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Rancher GCP Quick Start Guide -description: Read this step by step Rancher GCP guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached. -weight: 130 ---- -The following steps will quickly deploy a Rancher server on GCP in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached. - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Prerequisites - ->**Note** ->Deploying to Google GCP will incur charges. - -- [Google GCP Account](https://console.cloud.google.com/): A Google GCP Account is required to create resources for deploying Rancher and Kubernetes. -- [Google GCP Project](https://cloud.google.com/appengine/docs/standard/nodejs/building-app/creating-project): Use this link to follow a tutorial to create a GCP Project if you don't have one yet. -- [Google GCP Service Account](https://cloud.google.com/iam/docs/creating-managing-service-account-keys): Use this link and follow instructions to create a GCP service account and token file. -- [Terraform](https://www.terraform.io/downloads.html): Used to provision the server and cluster in Google GCP. - - -## Getting Started - -1. Clone [Rancher Quickstart](https://github.com/rancher/quickstart) to a folder using `git clone https://github.com/rancher/quickstart`. - -2. Go into the GCP folder containing the terraform files by executing `cd quickstart/gcp`. - -3. Rename the `terraform.tfvars.example` file to `terraform.tfvars`. - -4. Edit `terraform.tfvars` and customize the following variables: - - `gcp_account_json` - GCP service account file path and file name - - `rancher_server_admin_password` - Admin password for created Rancher server - -5. **Optional:** Modify optional variables within `terraform.tfvars`. -See the [Quickstart Readme](https://github.com/rancher/quickstart) and the [GCP Quickstart Readme](https://github.com/rancher/quickstart/tree/master/gcp) for more information. -Suggestions include: - - `gcp_region` - Google GCP region, choose the closest instead of the default (`us-east4`) - - `gcp_zone` - Google GCP zone, choose the closest instead of the default (`us-east4-a`) - - `prefix` - Prefix for all created resources - - `machine_type` - Compute instance size used, minimum is `n1-standard-1` but `n1-standard-2` or `n1-standard-4` could be used if within budget - -6. Run `terraform init`. - -7. To initiate the creation of the environment, run `terraform apply --auto-approve`. Then wait for output similar to the following: - - ``` - Apply complete! Resources: 16 added, 0 changed, 0 destroyed. - - Outputs: - - rancher_node_ip = xx.xx.xx.xx - rancher_server_url = https://rancher.xx.xx.xx.xx.sslip.io - workload_node_ip = yy.yy.yy.yy - ``` - -8. Paste the `rancher_server_url` from the output above into the browser. Log in when prompted (default username is `admin`, use the password set in `rancher_server_admin_password`). -9. ssh to the Rancher Server using the `id_rsa` key generated in `quickstart/gcp`. - -#### Result - -Two Kubernetes clusters are deployed into your GCP account, one running Rancher Server and the other ready for experimentation deployments. Please note that while this setup is a great way to explore Rancher functionality, a production setup should follow our high availability setup guidelines. SSH keys for the VMs are auto-generated and stored in the module directory. - -### What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{< baseurl >}}/rancher/v2.6/en/quick-start-guide/workload). - -## Destroying the Environment - -1. From the `quickstart/gcp` folder, execute `terraform destroy --auto-approve`. - -2. Wait for confirmation that all resources have been destroyed. diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/hetzner-cloud-qs/hetzner-cloud-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/hetzner-cloud-qs/hetzner-cloud-qs.md deleted file mode 100644 index ea7a2bbf1b8..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/hetzner-cloud-qs/hetzner-cloud-qs.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Rancher Hetzner Cloud Quick Start Guide -description: Read this step by step Rancher Hetzner Cloud guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached. -weight: 140 ---- -The following steps will quickly deploy a Rancher server on Hetzner Cloud in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached. - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Prerequisites - ->**Note** ->Deploying to Hetzner Cloud will incur charges. - -- [Hetzner Cloud Account](https://www.hetzner.com): You will require an account on Hetzner as this is where the server and cluster will run. -- [Hetzner API Access Key](https://docs.hetzner.cloud/#getting-started): Use these instructions to create a Hetzner Cloud API Key if you don't have one. -- [Terraform](https://www.terraform.io/downloads.html): Used to provision the server and cluster to Hetzner. - - -## Getting Started - -1. Clone [Rancher Quickstart](https://github.com/rancher/quickstart) to a folder using `git clone https://github.com/rancher/quickstart`. - -2. Go into the Hetzner folder containing the terraform files by executing `cd quickstart/hcloud`. - -3. Rename the `terraform.tfvars.example` file to `terraform.tfvars`. - -4. Edit `terraform.tfvars` and customize the following variables: - - `hcloud_token` - Hetzner API access key - - `rancher_server_admin_password` - Admin password for created Rancher server - -5. **Optional:** Modify optional variables within `terraform.tfvars`. -See the [Quickstart Readme](https://github.com/rancher/quickstart) and the [Hetzner Quickstart Readme](https://github.com/rancher/quickstart/tree/master/hcloud) for more information. -Suggestions include: - - `prefix` - Prefix for all created resources - - `instance_type` - Instance type, minimum required is `cx21` - - `hcloud_location` - Hetzner Cloud location, choose the closest instead of the default (`fsn1`) - -6. Run `terraform init`. - -7. To initiate the creation of the environment, run `terraform apply --auto-approve`. Then wait for output similar to the following: - - ``` - Apply complete! Resources: 15 added, 0 changed, 0 destroyed. - - Outputs: - - rancher_node_ip = xx.xx.xx.xx - rancher_server_url = https://rancher.xx.xx.xx.xx.sslip.io - workload_node_ip = yy.yy.yy.yy - ``` - -8. Paste the `rancher_server_url` from the output above into the browser. Log in when prompted (default username is `admin`, use the password set in `rancher_server_admin_password`). -9. ssh to the Rancher Server using the `id_rsa` key generated in `quickstart/hcloud`. - -#### Result - -Two Kubernetes clusters are deployed into your Hetzner account, one running Rancher Server and the other ready for experimentation deployments. Please note that while this setup is a great way to explore Rancher functionality, a production setup should follow our high availability setup guidelines. SSH keys for the VMs are auto-generated and stored in the module directory. - -### What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{}}/rancher/v2.6/en/quick-start-guide/workload). - -## Destroying the Environment - -1. From the `quickstart/hcloud` folder, execute `terraform destroy --auto-approve`. - -2. Wait for confirmation that all resources have been destroyed. diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/microsoft-azure-qs/microsoft-azure-qs.md b/versioned_docs/version-2.6/quick-start-guide/deployment/microsoft-azure-qs/microsoft-azure-qs.md deleted file mode 100644 index ec8d16a475e..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/microsoft-azure-qs/microsoft-azure-qs.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Rancher Azure Quick Start Guide -description: Read this step by step Rancher Azure guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached. -weight: 115 ---- - -The following steps will quickly deploy a Rancher server on Azure in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached. - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Prerequisites - ->**Note** ->Deploying to Microsoft Azure will incur charges. - -- [Microsoft Azure Account](https://azure.microsoft.com/en-us/free/): A Microsoft Azure Account is required to create resources for deploying Rancher and Kubernetes. -- [Microsoft Azure Subscription](https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription#create-a-subscription-in-the-azure-portal): Use this link to follow a tutorial to create a Microsoft Azure subscription if you don't have one yet. -- [Micsoroft Azure Tenant](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant): Use this link and follow instructions to create a Microsoft Azure tenant. -- [Microsoft Azure Client ID/Secret](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal): Use this link and follow instructions to create a Microsoft Azure client and secret. -- [Terraform](https://www.terraform.io/downloads.html): Used to provision the server and cluster in Microsoft Azure. - - -## Getting Started - -1. Clone [Rancher Quickstart](https://github.com/rancher/quickstart) to a folder using `git clone https://github.com/rancher/quickstart`. - -2. Go into the Azure folder containing the terraform files by executing `cd quickstart/azure`. - -3. Rename the `terraform.tfvars.example` file to `terraform.tfvars`. - -4. Edit `terraform.tfvars` and customize the following variables: - - `azure_subscription_id` - Microsoft Azure Subscription ID - - `azure_client_id` - Microsoft Azure Client ID - - `azure_client_secret` - Microsoft Azure Client Secret - - `azure_tenant_id` - Microsoft Azure Tenant ID - - `rancher_server_admin_password` - Admin password for created Rancher server - -5. **Optional:** Modify optional variables within `terraform.tfvars`. -See the [Quickstart Readme](https://github.com/rancher/quickstart) and the [Azure Quickstart Readme](https://github.com/rancher/quickstart/tree/master/azure) for more information. -Suggestions include: - - `azure_location` - Microsoft Azure region, choose the closest instead of the default (`East US`) - - `prefix` - Prefix for all created resources - - `instance_type` - Compute instance size used, minimum is `Standard_DS2_v2` but `Standard_DS2_v3` or `Standard_DS3_v2` could be used if within budget - - `add_windows_node` - If true, an additional Windows worker node is added to the workload cluster - - `windows_admin_password` - The admin password of the windows worker node - -6. Run `terraform init`. - -7. To initiate the creation of the environment, run `terraform apply --auto-approve`. Then wait for output similar to the following: - - ``` - Apply complete! Resources: 16 added, 0 changed, 0 destroyed. - - Outputs: - - rancher_node_ip = xx.xx.xx.xx - rancher_server_url = https://rancher.xx.xx.xx.xx.sslip.io - workload_node_ip = yy.yy.yy.yy - ``` - -8. Paste the `rancher_server_url` from the output above into the browser. Log in when prompted (default username is `admin`, use the password set in `rancher_server_admin_password`). -9. ssh to the Rancher Server using the `id_rsa` key generated in `quickstart/azure`. - -#### Result - -Two Kubernetes clusters are deployed into your Azure account, one running Rancher Server and the other ready for experimentation deployments. Please note that while this setup is a great way to explore Rancher functionality, a production setup should follow our high availability setup guidelines. SSH keys for the VMs are auto-generated and stored in the module directory. - -### What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{< baseurl >}}/rancher/v2.6/en/quick-start-guide/workload). - -## Destroying the Environment - -1. From the `quickstart/azure` folder, execute `terraform destroy --auto-approve`. - -2. Wait for confirmation that all resources have been destroyed. diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-manual-setup/quickstart-manual-setup.md b/versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-manual-setup/quickstart-manual-setup.md deleted file mode 100644 index 9bf05e7da9e..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-manual-setup/quickstart-manual-setup.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -title: Helm CLI Quick Start -weight: 300 ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -These instructions capture a quick way to set up a proof-of-concept Rancher installation. - -These instructions assume you have a Linux virtual machine that you will communicate with from your local workstation. Rancher will be installed on the Linux machine. You will need to retrieve the IP address of that machine so that you can access Rancher from your local workstation. Rancher is designed to manage Kubernetes clusters remotely, so any Kubernetes cluster that Rancher manages in the future will also need to be able to reach this IP address. - -We don't recommend installing Rancher locally because it creates a networking problem. Installing Rancher on localhost does not allow Rancher to communicate with downstream Kubernetes clusters, so on localhost you wouldn't be able to test Rancher's cluster provisioning or cluster management functionality. - -Your Linux machine can be anywhere. It could be an Amazon EC2 instance, a Digital Ocean droplet, or an Azure virtual machine, to name a few examples. Other Rancher docs often use 'node' as a generic term for all of these. One possible way to deploy a Linux machine is by setting up an Amazon EC2 instance as shown in [this tutorial]({{}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/). - -The full installation requirements are [here]({{}}/rancher/v2.6/en/installation/requirements/). - - -## Install K3s on Linux - -Install a K3s cluster by running this command on the Linux machine: - -``` -curl -sfL https://get.k3s.io | sh -s - server -``` - -Save the IP of the Linux machine. - -## Save the kubeconfig to your workstation - -The kubeconfig file is important for accessing the Kubernetes cluster. Copy the file at `/etc/rancher/k3s/k3s.yaml` from the Linux machine and save it to your local workstation in the directory `~/.kube/config`. One way to do this is by using the `scp` tool and run this command on your local machine: - - - - -``` -scp root@:/etc/rancher/k3s/k3s.yaml ~/.kube/config -``` - - - - -By default, "scp" is not a recognized command, so we need to install a module first. - -In Windows Powershell: - -``` -Find-Module Posh-SSH -Install-Module Posh-SSH - -## Get the remote kubeconfig file -scp root@:/etc/rancher/k3s/k3s.yaml $env:USERPROFILE\.kube\config -``` - - - - -## Edit the Rancher server URL in the kubeconfig - -In the kubeconfig file, you will need to change the value of the `server` field to `:6443`. The Kubernetes API server will be reached at port 6443, while the Rancher server will be reached at ports 80 and 443. This edit is needed so that when you run Helm or kubectl commands from your local workstation, you will be able to communicate with the Kubernetes cluster that Rancher will be installed on. - - - - -One way to open the kubeconfig file for editing is to use Vim: - -``` -vi ~/.kube/config -``` - -Press `i` to put Vim in insert mode. To save your work, press `Esc`. Then press `:wq` and press `Enter`. - - - - -In Windows Powershell, you can use `notepad.exe` for editing the kubeconfig file: - -``` -notepad.exe $env:USERPROFILE\.kube\config -``` - -Once edited, either press `ctrl+s` or go to `File > Save` to save your work. - - - - -## Install Rancher with Helm - -Then from your local workstation, run the following commands. You will need to have [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) and [helm.](https://helm.sh/docs/intro/install/) installed. - -``` -helm repo add rancher-latest https://releases.rancher.com/server-charts/latest - -kubectl create namespace cattle-system - -kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.2/cert-manager.crds.yaml - -helm repo add jetstack https://charts.jetstack.io - -helm repo update - -helm install cert-manager jetstack/cert-manager \ - --namespace cert-manager \ - --create-namespace \ - --version v1.7.1 - -# Windows Powershell -helm install cert-manager jetstack/cert-manager ` - --namespace cert-manager ` - --create-namespace ` - --version v1.7.1 -``` - -The final command to install Rancher is below. The command requires a domain name that forwards traffic to the Linux machine. For the sake of simplicity in this tutorial, you can use a fake domain name to create your proof-of-concept. An example of a fake domain name would be `.sslip.io`. - -``` -helm install rancher rancher-latest/rancher \ - --namespace cattle-system \ - --set hostname=.sslip.io \ - --set replicas=1 \ - --set bootstrapPassword= - -# Windows Powershell -helm install rancher rancher-latest/rancher ` - --namespace cattle-system ` - --set hostname=.sslip.io ` - --set replicas=1 ` - --set bootstrapPassword= -``` -``` - -Now if you navigate to `.sslip.io` in a web browser, you should see the Rancher UI. - -To make these instructions simple, we used a fake domain name and self-signed certificates to do this installation. Therefore, you will probably need to add a security exception to your web browser to see the Rancher UI. Note that for production installs, you would need a high-availability setup with a load balancer, a real domain name and real certificates. - -These instructions also left out the full installation requirements and other installation options. If you have any issues with these steps, refer to the full [Helm CLI installation docs.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) - -To launch new Kubernetes clusters with your new Rancher server, you may need to set up cloud credentials in Rancher. For more information, see [Launching Kubernetes clusters with Rancher.]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) diff --git a/versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-vagrant/quickstart-vagrant.md b/versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-vagrant/quickstart-vagrant.md deleted file mode 100644 index 86b3bb420c3..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/deployment/quickstart-vagrant/quickstart-vagrant.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Vagrant Quick Start -weight: 200 ---- -The following steps quickly deploy a Rancher Server with a single node cluster attached. - ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -## Prerequisites - -- [Vagrant](https://www.vagrantup.com): Vagrant is required as this is used to provision the machine based on the Vagrantfile. -- [Virtualbox](https://www.virtualbox.org): The virtual machines that Vagrant provisions need to be provisioned to VirtualBox. -- At least 4GB of free RAM. - -### Note -- Vagrant will require plugins to create VirtualBox VMs. Install them with the following commands: - - `vagrant plugin install vagrant-vboxmanage` - - `vagrant plugin install vagrant-vbguest` - -## Getting Started - -1. Clone [Rancher Quickstart](https://github.com/rancher/quickstart) to a folder using `git clone https://github.com/rancher/quickstart`. - -2. Go into the folder containing the Vagrantfile by executing `cd quickstart/vagrant`. - -3. **Optional:** Edit `config.yaml` to: - - - Change the number of nodes and the memory allocations, if required. (`node.count`, `node.cpus`, `node.memory`) - - Change the password of the `admin` user for logging into Rancher. (`default_password`) - -4. To initiate the creation of the environment run, `vagrant up --provider=virtualbox`. - -5. Once provisioning finishes, go to `https://192.168.56.101` in the browser. The default user/password is `admin/adminPassword`. - -**Result:** Rancher Server and your Kubernetes cluster is installed on VirtualBox. - -### What's Next? - -Use Rancher to create a deployment. For more information, see [Creating Deployments]({{}}/rancher/v2.6/en/quick-start-guide/workload). - -## Destroying the Environment - -1. From the `quickstart/vagrant` folder execute `vagrant destroy -f`. - -2. Wait for the confirmation that all resources have been destroyed. diff --git a/versioned_docs/version-2.6/quick-start-guide/quick-start-guide.md b/versioned_docs/version-2.6/quick-start-guide/quick-start-guide.md deleted file mode 100644 index b6b0ba33866..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/quick-start-guide.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Rancher Deployment Quick Start Guides -metaDescription: Use this section to jump start your Rancher deployment and testing. It contains instructions for a simple Rancher setup and some common use cases. -short title: Use this section to jump start your Rancher deployment and testing. It contains instructions for a simple Rancher setup and some common use cases. -weight: 2 -aliases: - - /rancher/v2.x/en/quick-start-guide/ ---- ->**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation]({{}}/rancher/v2.6/en/installation/). - -Howdy buckaroos! Use this section of the docs to jump start your deployment and testing of Rancher 2.x! It contains instructions for a simple Rancher setup and some common use cases. We plan on adding more content to this section in the future. - -We have Quick Start Guides for: - -- [Deploying Rancher Server]({{}}/rancher/v2.6/en/quick-start-guide/deployment/): Get started running Rancher using the method most convenient for you. - -- [Deploying Workloads]({{}}/rancher/v2.6/en/quick-start-guide/workload/): Deploy a simple [workload](https://kubernetes.io/docs/concepts/workloads/) and expose it, letting you access it from outside the cluster. diff --git a/versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-ingress/quickstart-deploy-workload-ingress.md b/versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-ingress/quickstart-deploy-workload-ingress.md deleted file mode 100644 index 004950b7fe2..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-ingress/quickstart-deploy-workload-ingress.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Workload with Ingress Quick Start -weight: 100 ---- - -### Prerequisite - -You have a running cluster with at least 1 node. - -### 1. Deploying a Workload - -You're ready to create your first Kubernetes [workload](https://kubernetes.io/docs/concepts/workloads/). A workload is an object that includes pods along with other files and info needed to deploy your application. - -For this workload, you'll be deploying the application Rancher Hello-World. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. -1. Click **Workload**. -1. Click **Create**. -1. Click **Deployment**. -1. Enter a **Name** for your workload. -1. From the **Docker Image** field, enter `rancher/hello-world`. This field is case-sensitive. -1. Click **Add Port** and enter `80` in the **Private Container Port** field. Adding a port enables access to the application inside and outside of the cluster. For more information, see [Services]({{}}/rancher/v2.6/en/k8s-in-rancher/workloads/#services). -1. Click **Create**. - -**Result:** - -* Your workload is deployed. This process might take a few minutes to complete. -* When your workload completes deployment, it's assigned a state of **Active**. You can view this status from the project's **Workloads** page. - -
-### 2. Expose The Application Via An Ingress - -Now that the application is up and running, it needs to be exposed so that other services can connect. - -1. Click **☰ > Cluster Management**. -1. Go to the cluster that you created and click **Explore**. - -1. Click **Service Discovery > Ingresses**. - -1. Click **Create.** - -1. When choosing **Namespace**, ensure it is the same as the one used when you created your deployment. Otherwise, your deployment will not be available when you attempt to select **Target Service**, as in Step 8 below. - -1. Enter a **Name**, such as **hello**. - -1. Specify your **Path**, such as `/hello`. - -1. In the **Target Service** field, drop down the list and choose the name that you set for your service. - -1. In the **Port** field, drop down the list and select `80`. - -1. Click **Create** at the bottom right. - -**Result:** The application is assigned a `sslip.io` address and exposed. It may take a minute or two to populate. - - -### View Your Application - -From the **Deployments** page, find the **Endpoints** column for your deployment and click on an endpoint. The endpoints available will depend on how you configured the port you added to your deployment. For endpoints where you do not see a randomly assigned port, append the path you specified when creating the ingress to the IP address. For example, if your endpoint looks like `xxx.xxx.xxx.xxx` or `https://xxx.xxx.xxx.xxx` change it to `xxx.xxx.xxx.xxx/hello` or `https://xxx.xxx.xxx.xxx/hello`. - -Your application will open in a separate window. - -#### Finished - -Congratulations! You have successfully deployed a workload exposed via an ingress. - -#### What's Next? - -When you're done using your sandbox, destroy the Rancher Server and your cluster. See one of the following: - -- [Amazon AWS: Destroying the Environment]({{}}/rancher/v2.6/en/quick-start-guide/deployment/amazon-aws-qs/#destroying-the-environment) -- [DigitalOcean: Destroying the Environment]({{}}/rancher/v2.6/en/quick-start-guide/deployment/digital-ocean-qs/#destroying-the-environment) -- [Vagrant: Destroying the Environment]({{}}/rancher/v2.6/en/quick-start-guide/deployment/quickstart-vagrant/#destroying-the-environment) diff --git a/versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-nodeport/quickstart-deploy-workload-nodeport.md b/versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-nodeport/quickstart-deploy-workload-nodeport.md deleted file mode 100644 index f064b9dc50e..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/workload/quickstart-deploy-workload-nodeport/quickstart-deploy-workload-nodeport.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -title: Workload with NodePort Quick Start -weight: 200 ---- - -### Prerequisite - -You have a running cluster with at least 1 node. - -### 1. Deploying a Workload - -You're ready to create your first Kubernetes [workload](https://kubernetes.io/docs/concepts/workloads/). A workload is an object that includes pods along with other files and info needed to deploy your application. - -For this workload, you'll be deploying the application Rancher Hello-World. - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, go to the cluster where the workload should be deployed and click **Explore**. -1. Click **Workload**. -1. Click **Create**. -1. Enter a **Name** for your workload. -1. From the **Container Image** field, enter `rancher/hello-world`. This field is case-sensitive. -1. Click **Add Port**. -1. From the **Service Type** drop-down, make sure that **NodePort** is selected. - - ![As a dropdown, NodePort (On every node selected)]({{}}/img/rancher/nodeport-dropdown.png) - -1. From the **Publish the container port** field, enter port `80`. - - ![Publish the container port, 80 entered]({{}}/img/rancher/container-port-field.png) - -1. Click **Create**. - -**Result:** - -* Your workload is deployed. This process might take a few minutes to complete. -* When your workload completes deployment, it's assigned a state of **Active**. You can view this status from the project's **Workloads** page. - -
- -### 2. Viewing Your Application - -From the **Workloads** page, click the link underneath your workload. If your deployment succeeded, your application opens. - -### Attention: Cloud-Hosted Sandboxes - -When using a cloud-hosted virtual machine, you may not have access to the port running the container. In this event, you can test Nginx in an ssh session on the local machine using `Execute Shell`. Use the port number after the `:` in the link under your workload if available, which is `31568` in this example. - -```sh -gettingstarted@rancher:~$ curl http://localhost:31568 - - - - Rancher - - - - - -

Hello world!

-

My hostname is hello-world-66b4b9d88b-78bhx

-
-

k8s services found 2

- - INGRESS_D1E1A394F61C108633C4BD37AEDDE757 tcp://10.43.203.31:80
- - KUBERNETES tcp://10.43.0.1:443
- -
-
- - -
- - -
- - - -gettingstarted@rancher:~$ - -``` - -### Finished - -Congratulations! You have successfully deployed a workload exposed via a NodePort. - -#### What's Next? - -When you're done using your sandbox, destroy the Rancher Server and your cluster. See one of the following: - -- [Amazon AWS: Destroying the Environment]({{}}/rancher/v2.6/en/quick-start-guide/deployment/amazon-aws-qs/#destroying-the-environment) -- [DigitalOcean: Destroying the Environment]({{}}/rancher/v2.6/en/quick-start-guide/deployment/digital-ocean-qs/#destroying-the-environment) -- [Vagrant: Destroying the Environment]({{}}/rancher/v2.6/en/quick-start-guide/deployment/quickstart-vagrant/#destroying-the-environment) diff --git a/versioned_docs/version-2.6/quick-start-guide/workload/workload.md b/versioned_docs/version-2.6/quick-start-guide/workload/workload.md deleted file mode 100644 index a3be7493b6c..00000000000 --- a/versioned_docs/version-2.6/quick-start-guide/workload/workload.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Deploying Workloads -weight: 200 ---- - -These guides walk you through the deployment of an application, including how to expose the application for use outside of the cluster. - -- [Workload with Ingress](./quickstart-deploy-workload-ingress) -- [Workload with NodePort](./quickstart-deploy-workload-nodeport) diff --git a/versioned_docs/version-2.6/rancher-manager.md b/versioned_docs/version-2.6/rancher-manager.md deleted file mode 100644 index 346e997c019..00000000000 --- a/versioned_docs/version-2.6/rancher-manager.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -slug: / -weight: 1 -title: "Rancher 2.6" -shortTitle: "Rancher 2.6 (Latest)" -description: "Rancher adds significant value on top of Kubernetes: managing hundreds of clusters from one interface, centralizing RBAC, enabling monitoring and alerting. Read more." -metaTitle: "Rancher 2.6 Docs: What is New?" -metaDescription: "Rancher 2 adds significant value on top of Kubernetes: managing hundreds of clusters from one interface, centralizing RBAC, enabling monitoring and alerting. Read more." -insertOneSix: false -ctaBanner: 0 -aliases: - - /rancher/v2.x/en/ ---- -Rancher was originally built to work with multiple orchestrators, and it included its own orchestrator called Cattle. With the rise of Kubernetes in the marketplace, Rancher 2 exclusively deploys and manages Kubernetes clusters running anywhere, on any provider. - -Rancher can provision Kubernetes from a hosted provider, provision compute nodes and then install Kubernetes onto them, or import existing Kubernetes clusters running anywhere. - -One Rancher server installation can manage thousands of Kubernetes clusters and thousands of nodes from the same user interface. - -Rancher adds significant value on top of Kubernetes, first by centralizing authentication and role-based access control (RBAC) for all of the clusters, giving global admins the ability to control cluster access from one location. - -It then enables detailed monitoring and alerting for clusters and their resources, ships logs to external providers, and integrates directly with Helm via the Application Catalog. If you have an external CI/CD system, you can plug it into Rancher, but if you don't, Rancher even includes Fleet to help you automatically deploy and upgrade workloads. - -Rancher is a _complete_ container management platform for Kubernetes, giving you the tools to successfully run Kubernetes anywhere. diff --git a/versioned_docs/version-2.6/security/best-practices/best-practices.md b/versioned_docs/version-2.6/security/best-practices/best-practices.md deleted file mode 100644 index 4dc70b3d510..00000000000 --- a/versioned_docs/version-2.6/security/best-practices/best-practices.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Kubernetes Security Best Practices -weight: 5 ---- - -### Restricting cloud metadata API access - -Cloud providers such as AWS, Azure, DigitalOcean or GCP often expose metadata services locally to instances. By default, this endpoint is accessible by pods running on a cloud instance, including pods in hosted Kubernetes providers such as EKS, AKS, DigitalOcean Kubernetes or GKE, and can contain cloud credentials for that node, provisioning data such as kubelet credentials, or other sensitive data. To mitigate this risk when running on a cloud platform, follow the [Kubernetes security recommendations](https://kubernetes.io/docs/tasks/administer-cluster/securing-a-cluster/#restricting-cloud-metadata-api-access): limit permissions given to instance credentials, use network policies to restrict pod access to the metadata API, and avoid using provisioning data to deliver secrets. - -It is advised to consult your cloud provider's security best practices for further recommendations and specific details on how to restrict access to cloud instance metadata API. - -Further references: MITRE ATT&CK knowledge base on - [Unsecured Credentials: Cloud Instance Metadata API](https://attack.mitre.org/techniques/T1552/005/). diff --git a/versioned_docs/version-2.6/security/cve/cve.md b/versioned_docs/version-2.6/security/cve/cve.md deleted file mode 100644 index 3288b0da979..00000000000 --- a/versioned_docs/version-2.6/security/cve/cve.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Security Advisories and CVEs -weight: 300 -aliases: - - /rancher/v2.x/en/security/cve/ ---- - -Rancher is committed to informing the community of security issues in our products. Rancher will publish security advisories and CVEs (Common Vulnerabilities and Exposures) for issues we have resolved. New security advisories are also published in Rancher's GitHub [security page](https://github.com/rancher/rancher/security/advisories). - -| ID | Description | Date | Resolution | -|----|-------------|------|------------| -| [CVE-2022-21951](https://github.com/rancher/rancher/security/advisories/GHSA-vrph-m5jj-c46c) | This vulnerability only affects customers using [Weave](https://rancher.com/docs/rancher/v2.6/en/faq/networking/cni-providers/#weave) Container Network Interface (CNI) when configured through [RKE templates](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rke-templates/). A vulnerability was discovered in Rancher versions 2.5.0 up to and including 2.5.13, and 2.6.0 up to and including 2.6.4, where a user interface (UI) issue with RKE templates does not include a value for the Weave password when Weave is chosen as the CNI. If a cluster is created based on the mentioned template, and Weave is configured as the CNI, no password will be created for [network encryption](https://www.weave.works/docs/net/latest/tasks/manage/security-untrusted-networks/) in Weave; therefore, network traffic in the cluster will be sent unencrypted. | 24 May 2022 | [Rancher v2.6.5](https://github.com/rancher/rancher/releases/tag/v2.6.5) and [Rancher v2.5.14](https://github.com/rancher/rancher/releases/tag/v2.5.14) | -| [CVE-2021-36784](https://github.com/rancher/rancher/security/advisories/GHSA-jwvr-vv7p-gpwq) | A vulnerability was discovered in Rancher versions from 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3 which allows users who have create or update permissions on [Global Roles](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/) to escalate their permissions, or those of another user, to admin-level permissions. Global Roles grant users Rancher-wide permissions, such as the ability to create clusters. In the identified versions of Rancher, when users are given permission to edit or create Global Roles, they are not restricted to only granting permissions which they already posses. This vulnerability affects customers who utilize non-admin users that are able to create or edit Global Roles. The most common use case for this scenario is the `restricted-admin` role. | 14 Apr 2022 | [Rancher v2.6.4](https://github.com/rancher/rancher/releases/tag/v2.6.4) and [Rancher v2.5.13](https://github.com/rancher/rancher/releases/tag/v2.5.13) | -| [CVE-2021-4200](https://github.com/rancher/rancher/security/advisories/GHSA-hx8w-ghh8-r4xf) | This vulnerability only affects customers using the `restricted-admin` role in Rancher. A vulnerability was discovered in Rancher versions from 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3 where the `global-data` role in `cattle-global-data` namespace grants write access to the Catalogs. Since each user with any level of catalog access was bound to the `global-data` role, this grants write access to templates (`CatalogTemplates`) and template versions (`CatalogTemplateVersions`) for any user with any level of catalog access. New users created in Rancher are by default assigned to the `user` role (standard user), which is not designed to grant write catalog access. This vulnerability effectively elevates the privilege of any user to write access for the catalog template and catalog template version resources. | 14 Apr 2022 | [Rancher v2.6.4](https://github.com/rancher/rancher/releases/tag/v2.6.4) and [Rancher v2.5.13](https://github.com/rancher/rancher/releases/tag/v2.5.13) | -| [GHSA-wm2r-rp98-8pmh](https://github.com/rancher/rancher/security/advisories/GHSA-wm2r-rp98-8pmh) | This vulnerability only affects customers using [Fleet](https://rancher.com/docs/rancher/v2.6/en/deploy-across-clusters/fleet/) for continuous delivery with authenticated Git and/or Helm repositories. An issue was discovered in `go-getter` library in versions prior to [`v1.5.11`](https://github.com/hashicorp/go-getter/releases/tag/v1.5.11) that exposes SSH private keys in base64 format due to a failure in redacting such information from error messages. The vulnerable version of this library is used in Rancher through Fleet in versions of Fleet prior to [`v0.3.9`](https://github.com/rancher/fleet/releases/tag/v0.3.9). This issue affects Rancher versions 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3. The issue was found and reported by Dagan Henderson from Raft Engineering. | 14 Apr 2022 | [Rancher v2.6.4](https://github.com/rancher/rancher/releases/tag/v2.6.4) and [Rancher v2.5.13](https://github.com/rancher/rancher/releases/tag/v2.5.13) | -| [CVE-2021-36778](https://github.com/rancher/rancher/security/advisories/GHSA-4fc7-hc63-7fjg) | A vulnerability was discovered in Rancher versions from 2.5.0 up to and including 2.5.11 and from 2.6.0 up to and including 2.6.2, where an insufficient check of the same-origin policy when downloading Helm charts from a configured private repository can lead to exposure of the repository credentials to a third-party provider. This issue only happens when the user configures access credentials to a private repository in Rancher inside `Apps & Marketplace > Repositories`. The issue was found and reported by Martin Andreas Ullrich. | 14 Apr 2022 | [Rancher v2.6.3](https://github.com/rancher/rancher/releases/tag/v2.6.3) and [Rancher v2.5.12](https://github.com/rancher/rancher/releases/tag/v2.5.12) | -| [GHSA-hwm2-4ph6-w6m5](https://github.com/rancher/rancher/security/advisories/GHSA-hwm2-4ph6-w6m5) | A vulnerability was discovered in versions of Rancher starting 2.0 up to and including 2.6.3. The `restricted` pod security policy (PSP) provided in Rancher deviated from the upstream `restricted` policy provided in Kubernetes on account of which Rancher's PSP had `runAsUser` set to `runAsAny`, while upstream had `runAsUser` set to `MustRunAsNonRoot`. This allowed containers to run as any user, including a privileged user (`root`), even when Rancher's `restricted` policy was enforced on a project or at the cluster level. | 31 Mar 2022 | [Rancher v2.6.4](https://github.com/rancher/rancher/releases/tag/v2.6.4) | -| [CVE-2021-36775](https://github.com/rancher/rancher/security/advisories/GHSA-28g7-896h-695v) | A vulnerability was discovered in Rancher versions up to and including 2.4.17, 2.5.11 and 2.6.2. After removing a `Project Role` associated with a group from the project, the bindings that granted access to cluster-scoped resources for those subjects were not deleted. This was due to an incomplete authorization logic check. A user who was a member of the affected group with authenticated access to Rancher could exploit this vulnerability to access resources they shouldn't have had access to. The exposure level would depend on the original permission level granted to the affected project role. This vulnerability only affected customers using group based authentication in Rancher. | 31 Mar 2022 | [Rancher v2.6.3](https://github.com/rancher/rancher/releases/tag/v2.6.3), [Rancher v2.5.12](https://github.com/rancher/rancher/releases/tag/v2.5.12) and [Rancher v2.4.18](https://github.com/rancher/rancher/releases/tag/v2.4.18) | -| [CVE-2021-36776](https://github.com/rancher/rancher/security/advisories/GHSA-gvh9-xgrq-r8hw) | A vulnerability was discovered in Rancher versions starting 2.5.0 up to and including 2.5.9, that allowed an authenticated user to impersonate any user on a cluster through an API proxy, without requiring knowledge of the impersonated user's credentials. This was due to the API proxy not dropping the impersonation header before sending the request to the Kubernetes API. A malicious user with authenticated access to Rancher could use this to impersonate another user with administrator access in Rancher, thereby gaining administrator level access to the cluster. | 31 Mar 2022 | [Rancher v2.6.0](https://github.com/rancher/rancher/releases/tag/v2.6.0) and [Rancher v2.5.10](https://github.com/rancher/rancher/releases/tag/v2.5.10) | -| [CVE-2021-25318](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25318) | A vulnerability was discovered in Rancher versions 2.0 through the aforementioned fixed versions, where users were granted access to resources regardless of the resource's API group. For example, Rancher should have allowed users access to `apps.catalog.cattle.io`, but instead incorrectly gave access to `apps.*`. Resources affected in the **Downstream clusters** and **Rancher management cluster** can be found [here](https://github.com/rancher/rancher/security/advisories/GHSA-f9xf-jq4j-vqw4). There is not a direct mitigation besides upgrading to the patched Rancher versions. | 14 Jul 2021 | [Rancher v2.5.9](https://github.com/rancher/rancher/releases/tag/v2.5.9) and [Rancher v2.4.16](https://github.com/rancher/rancher/releases/tag/v2.4.16) | -| [CVE-2021-31999](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31999) | A vulnerability was discovered in Rancher 2.0.0 through the aforementioned patched versions, where a malicious Rancher user could craft an API request directed at the proxy for the Kubernetes API of a managed cluster to gain access to information they do not have access to. This is done by passing the "Impersonate-User" or "Impersonate-Group" header in the Connection header, which is then correctly removed by the proxy. At this point, instead of impersonating the user and their permissions, the request will act as if it was from the Rancher management server and incorrectly return the information. The vulnerability is limited to valid Rancher users with some level of permissions on the cluster. There is not a direct mitigation besides upgrading to the patched Rancher versions. | 14 Jul 2021 | [Rancher v2.5.9](https://github.com/rancher/rancher/releases/tag/v2.5.9) and [Rancher v2.4.16](https://github.com/rancher/rancher/releases/tag/v2.4.16) | -| [CVE-2021-25320](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25320) | A vulnerability was discovered in Rancher 2.2.0 through the aforementioned patched versions, where cloud credentials weren't being properly validated through the Rancher API. Specifically through a proxy designed to communicate with cloud providers. Any Rancher user that was logged-in and aware of a cloud-credential ID that was valid for a given cloud provider, could call that cloud provider's API through the proxy API, and the cloud-credential would be attached. The exploit is limited to valid Rancher users. There is not a direct mitigation outside of upgrading to the patched Rancher versions. | 14 Jul 2021 | [Rancher v2.5.9](https://github.com/rancher/rancher/releases/tag/v2.5.9) and [Rancher v2.4.16](https://github.com/rancher/rancher/releases/tag/v2.4.16) | -| [CVE-2021-25313](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25313) | A security vulnerability was discovered on all Rancher 2 versions. When accessing the Rancher API with a browser, the URL was not properly escaped, making it vulnerable to an XSS attack. Specially crafted URLs to these API endpoints could include JavaScript which would be embedded in the page and execute in a browser. There is no direct mitigation. Avoid clicking on untrusted links to your Rancher server. | 2 Mar 2021 | [Rancher v2.5.6](https://github.com/rancher/rancher/releases/tag/v2.5.6), [Rancher v2.4.14](https://github.com/rancher/rancher/releases/tag/v2.4.14), and [Rancher v2.3.11](https://github.com/rancher/rancher/releases/tag/v2.3.11) | -| [CVE-2019-14435](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14435) | This vulnerability allows authenticated users to potentially extract otherwise private data out of IPs reachable from system service containers used by Rancher. This can include but not only limited to services such as cloud provider metadata services. Although Rancher allow users to configure whitelisted domains for system service access, this flaw can still be exploited by a carefully crafted HTTP request. The issue was found and reported by Matt Belisle and Alex Stevenson at Workiva. | 5 Aug 2019 | [Rancher v2.2.7](https://github.com/rancher/rancher/releases/tag/v2.2.7) and [Rancher v2.1.12](https://github.com/rancher/rancher/releases/tag/v2.1.12) | -| [CVE-2019-14436](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14436) | The vulnerability allows a member of a project that has access to edit role bindings to be able to assign themselves or others a cluster level role granting them administrator access to that cluster. The issue was found and reported by Michal Lipinski at Nokia. | 5 Aug 2019 | [Rancher v2.2.7](https://github.com/rancher/rancher/releases/tag/v2.2.7) and [Rancher v2.1.12](https://github.com/rancher/rancher/releases/tag/v2.1.12) | -| [CVE-2019-13209](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13209) | The vulnerability is known as a [Cross-Site Websocket Hijacking attack](https://www.christian-schneider.net/CrossSiteWebSocketHijacking.html). This attack allows an exploiter to gain access to clusters managed by Rancher with the roles/permissions of a victim. It requires that a victim to be logged into a Rancher server and then access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the Kubernetes API with the permissions and identity of the victim. Reported by Matt Belisle and Alex Stevenson from Workiva. | 15 Jul 2019 | [Rancher v2.2.5](https://github.com/rancher/rancher/releases/tag/v2.2.5), [Rancher v2.1.11](https://github.com/rancher/rancher/releases/tag/v2.1.11) and [Rancher v2.0.16](https://github.com/rancher/rancher/releases/tag/v2.0.16) | -| [CVE-2019-12303](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12303) | Project owners can inject extra fluentd logging configurations that makes it possible to read files or execute arbitrary commands inside the fluentd container. Reported by Tyler Welton from Untamed Theory. | 5 Jun 2019 | [Rancher v2.2.4](https://github.com/rancher/rancher/releases/tag/v2.2.4), [Rancher v2.1.10](https://github.com/rancher/rancher/releases/tag/v2.1.10) and [Rancher v2.0.15](https://github.com/rancher/rancher/releases/tag/v2.0.15) | -| [CVE-2019-12274](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12274) | Nodes using the built-in node drivers using a file path option allows the machine to read arbitrary files including sensitive ones from inside the Rancher server container. | 5 Jun 2019 | [Rancher v2.2.4](https://github.com/rancher/rancher/releases/tag/v2.2.4), [Rancher v2.1.10](https://github.com/rancher/rancher/releases/tag/v2.1.10) and [Rancher v2.0.15](https://github.com/rancher/rancher/releases/tag/v2.0.15) | -| [CVE-2019-11202](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11202) | The default admin, that is shipped with Rancher, will be re-created upon restart of Rancher despite being explicitly deleted. | 16 Apr 2019 | [Rancher v2.2.2](https://github.com/rancher/rancher/releases/tag/v2.2.2), [Rancher v2.1.9](https://github.com/rancher/rancher/releases/tag/v2.1.9) and [Rancher v2.0.14](https://github.com/rancher/rancher/releases/tag/v2.0.14) | -| [CVE-2019-6287](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6287) | Project members continue to get access to namespaces from projects that they were removed from if they were added to more than one project. | 29 Jan 2019 | [Rancher v2.1.6](https://github.com/rancher/rancher/releases/tag/v2.1.6) and [Rancher v2.0.11](https://github.com/rancher/rancher/releases/tag/v2.0.11) | -| [CVE-2018-20321](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20321) | Any project member with access to the `default` namespace can mount the `netes-default` service account in a pod and then use that pod to execute administrative privileged commands against the Kubernetes cluster. | 29 Jan 2019 | [Rancher v2.1.6](https://github.com/rancher/rancher/releases/tag/v2.1.6) and [Rancher v2.0.11](https://github.com/rancher/rancher/releases/tag/v2.0.11) - Rolling back from these versions or greater have specific [instructions]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/rollbacks). | diff --git a/versioned_docs/version-2.6/security/hardening-guides/hardening-guides.md b/versioned_docs/version-2.6/security/hardening-guides/hardening-guides.md deleted file mode 100644 index 24f10ae4b38..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/hardening-guides.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Self-Assessment and Hardening Guides for Rancher v2.6 -shortTitle: Rancher v2.6 Hardening Guides -weight: 1 -aliases: - - /rancher/v2.6/en/security/rancher-2.5/ - - /rancher/v2.6/en/security/rancher-2.5/1.5-hardening-2.5/ - - /rancher/v2.6/en/security/rancher-2.5/1.5-benchmark-2.5/ - - /rancher/v2.6/en/security/rancher-2.5/1.6-hardening-2.5/ - - /rancher/v2.6/en/security/rancher-2.5/1.6-benchmark-2.5/ ---- - -Rancher provides specific security hardening guides for each supported Rancher's Kubernetes distributions. - -- [Rancher Kubernetes Distributions](#rancher-kubernetes-distributions) -- [Hardening Guides and Benchmark Versions](#hardening-guides-and-benchmark-versions) - - [RKE Guides](#rke-guides) - - [RKE2 Guides](#rke2-guides) - - [K3s Guides](#k3s) -- [Rancher with SELinux](#rancher-with-selinux) - -# Rancher Kubernetes Distributions - -Rancher uses the following Kubernetes distributions: - -- [**RKE**]({{}}/rke/latest/en/), Rancher Kubernetes Engine, is a CNCF-certified Kubernetes distribution that runs entirely within Docker containers. -- [**RKE2**](https://docs.rke2.io/) is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector. -- [**K3s**]({{}}/k3s/latest/en/) is a fully conformant, lightweight Kubernetes distribution. It is easy to install, with half the memory of upstream Kubernetes, all in a binary of less than 100 MB. - -To harden a Kubernetes cluster outside of Rancher's distributions, refer to your Kubernetes provider docs. - -# Hardening Guides and Benchmark Versions - -These guides have been tested along with the Rancher v2.6 release. Each self-assessment guide is accompanied with a hardening guide and tested on a specific Kubernetes version and CIS benchmark version. If a CIS benchmark has not been validated for your Kubernetes version, you can choose to use the existing guides until a newer version is added. - -### RKE Guides - -| Kubernetes Version | CIS Benchmark Version | Self Assessment Guide | Hardening Guides | -| ------------------ | --------------------- | --------------------- | ---------------- | -| Kubernetes v1.18 up to v1.23 | CIS v1.6 | [Link]({{}}/rancher/v2.6/en/security/hardening-guides/rke-1.6-benchmark-2.6) | [Link]({{}}/rancher/v2.6/en/security/hardening-guides/rke-1.6-hardening-2.6) | - -> **Notes** -> -> - CIS v1.20 benchmark version for Kubernetes v1.19 and v1.20 is not yet released as a profile in Rancher's CIS Benchmark chart. - -### RKE2 Guides - -| Type | Kubernetes Version | CIS Benchmark Version | Self Assessment Guide | Hardening Guides | -| ---- | ------------------ | --------------------- | --------------------- | ---------------- | -| Rancher provisioned RKE2 cluster | Kubernetes v1.21 up to v1.23 | CIS v1.6 | [Link]({{}}/rancher/v2.6/en/security/hardening-guides/rke2-1.6-benchmark-2.6) | [Link]({{}}/rancher/v2.6/en/security/hardening-guides/rke2-1.6-hardening-2.6) | -| Standalone RKE2 | Kubernetes v1.21 up to v1.23 | CIS v1.6 | [Link](https://docs.rke2.io/security/cis_self_assessment16/) | [Link](https://docs.rke2.io/security/hardening_guide/) | - -### K3s Guides - -| Kubernetes Version | CIS Benchmark Version | Self Assessment Guide | Hardening Guides | -| ------------------ | --------------------- | --------------------- | ---------------- | -| Kubernetes v1.21 and v1.22 | CIS v1.6 | [Link]({{}}/k3s/latest/en/security/self_assessment/) | [Link]({{}}/k3s/latest/en/security/hardening_guide/) | - -# Rancher with SELinux - -[Security-Enhanced Linux (SELinux)](https://en.wikipedia.org/wiki/Security-Enhanced_Linux) is a security enhancement to Linux. After being historically used by government agencies, SELinux is now industry standard and is enabled by default on RHEL and CentOS. - -To use Rancher with SELinux, we recommend installing the `rancher-selinux` RPM according to the instructions on [this page.]({{}}/rancher/v2.6/en/security/selinux/#installing-the-rancher-selinux-rpm) diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/Rancher_v2-6_CIS_v1-6_Benchmark_Assessment.pdf b/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/Rancher_v2-6_CIS_v1-6_Benchmark_Assessment.pdf deleted file mode 100644 index 25f33709b3f..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/Rancher_v2-6_CIS_v1-6_Benchmark_Assessment.pdf +++ /dev/null @@ -1,14862 +0,0 @@ -%PDF-1.7 -%🖤 -1 0 obj -<< -/Type /Pages -/Kids [ 6 0 R 8 0 R 38 0 R 76 0 R 114 0 R 152 0 R 186 0 R 222 0 R 258 0 R 292 0 R 304 0 R 311 0 R 315 0 R 317 0 R 320 0 R 325 0 R 327 0 R 351 0 R 376 0 R 409 0 R 442 0 R 466 0 R 505 0 R 510 0 R 513 0 R 516 0 R 518 0 R 521 0 R 523 0 R 526 0 R 529 0 R 531 0 R 534 0 R 536 0 R 539 0 R 542 0 R 544 0 R 547 0 R 550 0 R 552 0 R 555 0 R 557 0 R 561 0 R 564 0 R 567 0 R 569 0 R 572 0 R 574 0 R 577 0 R 580 0 R 582 0 R 585 0 R 588 0 R 590 0 R 593 0 R 595 0 R 598 0 R 601 0 R 603 0 R 606 0 R 609 0 R 611 0 R 614 0 R 616 0 R 619 0 R 622 0 R 624 0 R 627 0 R 629 0 R 632 0 R 635 0 R 637 0 R 640 0 R 643 0 R 645 0 R 662 0 R 676 0 R 679 0 R 682 0 R 685 0 R 688 0 R 691 0 R 694 0 R 696 0 R 700 0 R 702 0 R 705 0 R 707 0 R 710 0 R 712 0 R 715 0 R 717 0 R 719 0 R 722 0 R 724 0 R 727 0 R 729 0 R 732 0 R 734 0 R 736 0 R 739 0 R 741 0 R 743 0 R 745 0 R 748 0 R 750 0 R 753 0 R 757 0 R 766 0 R 774 0 R 776 0 R 781 0 R 786 0 R 792 0 R 796 0 R 800 0 R 806 0 R 810 0 R 814 0 R 817 0 R 819 0 R 844 0 R 855 0 R 858 0 R 862 0 R 865 0 R 882 0 R 889 0 R 891 0 R 893 0 R 895 0 R ] -/Count 131 ->> -endobj -2 0 obj -<< -/Title (RKE CIS v1.6 Benchmark - Self-Assessment Guide - Rancher v2.6) -/Creator (pandoc) -/Producer (WeasyPrint 54.3) ->> -endobj -3 0 obj -<< -/Type /Catalog -/Pages 1 0 R -/Outlines 1057 0 R -/Names << -/Dests << -/Names [ (TOC) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (api-server) [ 510 0 R /XYZ 41.740157 784.430079 0 ] (apply-security-context-to-your-pods-and-containers-manual) [ 893 0 R /XYZ 84.259843 324.051496 0 ] (authentication-and-authorization) [ 743 0 R /XYZ 41.740157 784.430079 0 ] (cb1) [ 317 0 R /XYZ 84.259843 207.170079 0 ] (cb1-1) [ 317 0 R /XYZ 101.433071 205.473057 0 ] (cb10) [ 351 0 R /XYZ 84.259843 342.035606 0 ] (cb10-1) [ 351 0 R /XYZ 101.433071 340.338585 0 ] (cb101) [ 624 0 R /XYZ 84.259843 504.320079 0 ] (cb101-1) [ 624 0 R /XYZ 101.433071 502.623057 0 ] (cb104) [ 629 0 R /XYZ 84.259843 772.370079 0 ] (cb104-1) [ 629 0 R /XYZ 101.433071 770.673057 0 ] (cb107) [ 632 0 R /XYZ 84.259843 313.070079 0 ] (cb107-1) [ 632 0 R /XYZ 101.433071 311.373057 0 ] (cb110) [ 637 0 R /XYZ 84.259843 560.570079 0 ] (cb110-1) [ 637 0 R /XYZ 101.433071 558.873057 0 ] (cb113) [ 640 0 R /XYZ 84.259843 110.570079 0 ] (cb113-1) [ 640 0 R /XYZ 101.433071 108.873057 0 ] (cb116) [ 645 0 R /XYZ 84.259843 418.070079 0 ] (cb116-1) [ 645 0 R /XYZ 101.433071 416.373057 0 ] (cb116-10) [ 645 0 R /XYZ 99.933071 189.008799 0 ] (cb116-11) [ 645 0 R /XYZ 99.933071 170.061778 0 ] (cb116-12) [ 645 0 R /XYZ 99.933071 151.114756 0 ] (cb116-13) [ 645 0 R /XYZ 99.933071 132.167735 0 ] (cb116-14) [ 645 0 R /XYZ 99.933071 113.220714 0 ] (cb116-15) [ 645 0 R /XYZ 99.933071 94.273692 0 ] (cb116-16) [ 662 0 R /XYZ 99.933071 799.173057 0 ] (cb116-17) [ 662 0 R /XYZ 99.933071 780.226036 0 ] (cb116-18) [ 662 0 R /XYZ 99.933071 761.279014 0 ] (cb116-19) [ 662 0 R /XYZ 99.933071 742.331993 0 ] (cb116-2) [ 645 0 R /XYZ 99.933071 397.426036 0 ] (cb116-20) [ 662 0 R /XYZ 99.933071 723.384971 0 ] (cb116-21) [ 662 0 R /XYZ 99.933071 704.437950 0 ] (cb116-22) [ 662 0 R /XYZ 99.933071 685.490928 0 ] (cb116-23) [ 662 0 R /XYZ 99.933071 666.543907 0 ] (cb116-24) [ 662 0 R /XYZ 99.933071 647.596885 0 ] (cb116-25) [ 662 0 R /XYZ 99.933071 628.649864 0 ] (cb116-3) [ 645 0 R /XYZ 99.933071 378.479014 0 ] (cb116-4) [ 645 0 R /XYZ 99.933071 340.584971 0 ] (cb116-5) [ 645 0 R /XYZ 99.933071 321.637950 0 ] (cb116-6) [ 645 0 R /XYZ 99.933071 302.690928 0 ] (cb116-7) [ 645 0 R /XYZ 99.933071 283.743907 0 ] (cb116-8) [ 645 0 R /XYZ 99.933071 264.796885 0 ] (cb116-9) [ 645 0 R /XYZ 99.933071 226.902842 0 ] (cb117) [ 662 0 R /XYZ 84.259843 569.399864 0 ] (cb117-1) [ 662 0 R /XYZ 101.433071 567.702842 0 ] (cb120) [ 662 0 R /XYZ 84.259843 196.152842 0 ] (cb120-1) [ 662 0 R /XYZ 101.433071 194.455821 0 ] (cb121) [ 676 0 R /XYZ 84.259843 550.251496 0 ] (cb121-1) [ 676 0 R /XYZ 101.433071 548.554475 0 ] (cb124) [ 679 0 R /XYZ 84.259843 571.820079 0 ] (cb124-1) [ 679 0 R /XYZ 101.433071 570.123057 0 ] (cb127) [ 682 0 R /XYZ 84.259843 575.570079 0 ] (cb127-1) [ 682 0 R /XYZ 101.433071 573.873057 0 ] (cb13) [ 376 0 R /XYZ 84.259843 711.620079 0 ] (cb13-1) [ 376 0 R /XYZ 101.433071 709.923057 0 ] (cb13-10) [ 376 0 R /XYZ 99.933071 501.505821 0 ] (cb13-11) [ 376 0 R /XYZ 99.933071 482.558799 0 ] (cb13-12) [ 376 0 R /XYZ 99.933071 463.611778 0 ] (cb13-13) [ 376 0 R /XYZ 99.933071 444.664756 0 ] (cb13-14) [ 376 0 R /XYZ 99.933071 425.717735 0 ] (cb13-15) [ 376 0 R /XYZ 99.933071 406.770714 0 ] (cb13-16) [ 376 0 R /XYZ 99.933071 387.823692 0 ] (cb13-17) [ 376 0 R /XYZ 99.933071 368.876671 0 ] (cb13-18) [ 376 0 R /XYZ 99.933071 349.929649 0 ] (cb13-19) [ 376 0 R /XYZ 99.933071 330.982628 0 ] (cb13-2) [ 376 0 R /XYZ 99.933071 690.976036 0 ] (cb13-20) [ 376 0 R /XYZ 99.933071 312.035606 0 ] (cb13-21) [ 376 0 R /XYZ 99.933071 293.088585 0 ] (cb13-22) [ 376 0 R /XYZ 99.933071 274.141563 0 ] (cb13-23) [ 376 0 R /XYZ 99.933071 255.194542 0 ] (cb13-24) [ 376 0 R /XYZ 99.933071 236.247520 0 ] (cb13-25) [ 376 0 R /XYZ 99.933071 217.300499 0 ] (cb13-26) [ 376 0 R /XYZ 99.933071 198.353477 0 ] (cb13-27) [ 376 0 R /XYZ 99.933071 179.406456 0 ] (cb13-28) [ 376 0 R /XYZ 99.933071 160.459434 0 ] (cb13-29) [ 376 0 R /XYZ 99.933071 141.512413 0 ] (cb13-3) [ 376 0 R /XYZ 99.933071 672.029014 0 ] (cb13-30) [ 376 0 R /XYZ 99.933071 122.565391 0 ] (cb13-31) [ 376 0 R /XYZ 99.933071 103.618370 0 ] (cb13-32) [ 409 0 R /XYZ 99.933071 799.173057 0 ] (cb13-33) [ 409 0 R /XYZ 99.933071 780.226036 0 ] (cb13-34) [ 409 0 R /XYZ 99.933071 761.279014 0 ] (cb13-35) [ 409 0 R /XYZ 99.933071 742.331993 0 ] (cb13-36) [ 409 0 R /XYZ 99.933071 723.384971 0 ] (cb13-37) [ 409 0 R /XYZ 99.933071 704.437950 0 ] (cb13-38) [ 409 0 R /XYZ 99.933071 685.490928 0 ] (cb13-39) [ 409 0 R /XYZ 99.933071 666.543907 0 ] (cb13-4) [ 376 0 R /XYZ 99.933071 634.134971 0 ] (cb13-40) [ 409 0 R /XYZ 99.933071 647.596885 0 ] (cb13-41) [ 409 0 R /XYZ 99.933071 628.649864 0 ] (cb13-42) [ 409 0 R /XYZ 99.933071 609.702842 0 ] (cb13-43) [ 409 0 R /XYZ 99.933071 590.755821 0 ] (cb13-44) [ 409 0 R /XYZ 99.933071 571.808799 0 ] (cb13-45) [ 409 0 R /XYZ 99.933071 552.861778 0 ] (cb13-46) [ 409 0 R /XYZ 99.933071 533.914756 0 ] (cb13-47) [ 409 0 R /XYZ 99.933071 514.967735 0 ] (cb13-48) [ 409 0 R /XYZ 99.933071 496.020714 0 ] (cb13-49) [ 409 0 R /XYZ 99.933071 477.073692 0 ] (cb13-5) [ 376 0 R /XYZ 99.933071 596.240928 0 ] (cb13-50) [ 409 0 R /XYZ 99.933071 458.126671 0 ] (cb13-51) [ 409 0 R /XYZ 99.933071 439.179649 0 ] (cb13-52) [ 409 0 R /XYZ 99.933071 420.232628 0 ] (cb13-53) [ 409 0 R /XYZ 99.933071 382.338585 0 ] (cb13-54) [ 409 0 R /XYZ 99.933071 363.391563 0 ] (cb13-55) [ 409 0 R /XYZ 99.933071 344.444542 0 ] (cb13-56) [ 409 0 R /XYZ 99.933071 325.497520 0 ] (cb13-57) [ 409 0 R /XYZ 99.933071 306.550499 0 ] (cb13-58) [ 409 0 R /XYZ 99.933071 287.603477 0 ] (cb13-59) [ 409 0 R /XYZ 99.933071 268.656456 0 ] (cb13-6) [ 376 0 R /XYZ 99.933071 577.293907 0 ] (cb13-60) [ 409 0 R /XYZ 99.933071 249.709434 0 ] (cb13-61) [ 409 0 R /XYZ 99.933071 230.762413 0 ] (cb13-7) [ 376 0 R /XYZ 99.933071 558.346885 0 ] (cb13-8) [ 376 0 R /XYZ 99.933071 539.399864 0 ] (cb13-9) [ 376 0 R /XYZ 99.933071 520.452842 0 ] (cb130) [ 685 0 R /XYZ 84.259843 560.570079 0 ] (cb130-1) [ 685 0 R /XYZ 101.433071 558.873057 0 ] (cb133) [ 688 0 R /XYZ 84.259843 556.820079 0 ] (cb133-1) [ 688 0 R /XYZ 101.433071 555.123057 0 ] (cb136) [ 691 0 R /XYZ 84.259843 369.020079 0 ] (cb136-1) [ 691 0 R /XYZ 101.433071 367.323057 0 ] (cb139) [ 696 0 R /XYZ 84.259843 565.251496 0 ] (cb139-1) [ 696 0 R /XYZ 101.433071 563.554475 0 ] (cb14) [ 409 0 R /XYZ 84.259843 171.512413 0 ] (cb14-1) [ 409 0 R /XYZ 101.433071 169.815391 0 ] (cb142) [ 696 0 R /XYZ 84.259843 102.004475 0 ] (cb142-1) [ 696 0 R /XYZ 101.433071 100.307453 0 ] (cb145) [ 702 0 R /XYZ 84.259843 514.251496 0 ] (cb145-1) [ 702 0 R /XYZ 101.433071 512.554475 0 ] (cb148) [ 707 0 R /XYZ 84.259843 309.320079 0 ] (cb148-1) [ 707 0 R /XYZ 101.433071 307.623057 0 ] (cb151) [ 712 0 R /XYZ 84.259843 103.070079 0 ] (cb151-1) [ 712 0 R /XYZ 101.433071 101.373057 0 ] (cb154) [ 719 0 R /XYZ 84.259843 613.970079 0 ] (cb154-1) [ 719 0 R /XYZ 101.433071 612.273057 0 ] (cb157) [ 724 0 R /XYZ 84.259843 403.070079 0 ] (cb157-1) [ 724 0 R /XYZ 101.433071 401.373057 0 ] (cb160) [ 729 0 R /XYZ 84.259843 178.070079 0 ] (cb160-1) [ 729 0 R /XYZ 101.433071 176.373057 0 ] (cb163) [ 736 0 R /XYZ 84.259843 628.970079 0 ] (cb163-1) [ 736 0 R /XYZ 101.433071 627.273057 0 ] (cb166) [ 745 0 R /XYZ 84.259843 595.251496 0 ] (cb166-1) [ 745 0 R /XYZ 101.433071 593.554475 0 ] (cb169) [ 750 0 R /XYZ 84.259843 267.651496 0 ] (cb169-1) [ 750 0 R /XYZ 101.433071 265.954475 0 ] (cb17) [ 442 0 R /XYZ 84.259843 543.320079 0 ] (cb17-1) [ 442 0 R /XYZ 101.433071 541.623057 0 ] (cb17-10) [ 442 0 R /XYZ 99.933071 333.205821 0 ] (cb17-11) [ 442 0 R /XYZ 99.933071 314.258799 0 ] (cb17-12) [ 442 0 R /XYZ 99.933071 295.311778 0 ] (cb17-13) [ 442 0 R /XYZ 99.933071 276.364756 0 ] (cb17-14) [ 442 0 R /XYZ 99.933071 257.417735 0 ] (cb17-15) [ 442 0 R /XYZ 99.933071 238.470714 0 ] (cb17-16) [ 442 0 R /XYZ 99.933071 219.523692 0 ] (cb17-17) [ 442 0 R /XYZ 99.933071 200.576671 0 ] (cb17-18) [ 442 0 R /XYZ 99.933071 181.629649 0 ] (cb17-19) [ 442 0 R /XYZ 99.933071 162.682628 0 ] (cb17-2) [ 442 0 R /XYZ 99.933071 522.676036 0 ] (cb17-20) [ 442 0 R /XYZ 99.933071 143.735606 0 ] (cb17-21) [ 442 0 R /XYZ 99.933071 124.788585 0 ] (cb17-22) [ 442 0 R /XYZ 99.933071 105.841563 0 ] (cb17-23) [ 466 0 R /XYZ 99.933071 799.173057 0 ] (cb17-24) [ 466 0 R /XYZ 99.933071 780.226036 0 ] (cb17-25) [ 466 0 R /XYZ 99.933071 761.279014 0 ] (cb17-26) [ 466 0 R /XYZ 99.933071 742.331993 0 ] (cb17-27) [ 466 0 R /XYZ 99.933071 723.384971 0 ] (cb17-28) [ 466 0 R /XYZ 99.933071 704.437950 0 ] (cb17-29) [ 466 0 R /XYZ 99.933071 685.490928 0 ] (cb17-3) [ 442 0 R /XYZ 99.933071 503.729014 0 ] (cb17-30) [ 466 0 R /XYZ 99.933071 666.543907 0 ] (cb17-31) [ 466 0 R /XYZ 99.933071 647.596885 0 ] (cb17-32) [ 466 0 R /XYZ 99.933071 628.649864 0 ] (cb17-33) [ 466 0 R /XYZ 99.933071 609.702842 0 ] (cb17-34) [ 466 0 R /XYZ 99.933071 590.755821 0 ] (cb17-35) [ 466 0 R /XYZ 99.933071 571.808799 0 ] (cb17-36) [ 466 0 R /XYZ 99.933071 552.861778 0 ] (cb17-37) [ 466 0 R /XYZ 99.933071 533.914756 0 ] (cb17-38) [ 466 0 R /XYZ 99.933071 514.967735 0 ] (cb17-39) [ 466 0 R /XYZ 99.933071 496.020714 0 ] (cb17-4) [ 442 0 R /XYZ 99.933071 465.834971 0 ] (cb17-40) [ 466 0 R /XYZ 99.933071 477.073692 0 ] (cb17-41) [ 466 0 R /XYZ 99.933071 458.126671 0 ] (cb17-42) [ 466 0 R /XYZ 99.933071 439.179649 0 ] (cb17-43) [ 466 0 R /XYZ 99.933071 420.232628 0 ] (cb17-44) [ 466 0 R /XYZ 99.933071 401.285606 0 ] (cb17-45) [ 466 0 R /XYZ 99.933071 382.338585 0 ] (cb17-46) [ 466 0 R /XYZ 99.933071 363.391563 0 ] (cb17-47) [ 466 0 R /XYZ 99.933071 344.444542 0 ] (cb17-48) [ 466 0 R /XYZ 99.933071 325.497520 0 ] (cb17-49) [ 466 0 R /XYZ 99.933071 306.550499 0 ] (cb17-5) [ 442 0 R /XYZ 99.933071 427.940928 0 ] (cb17-50) [ 466 0 R /XYZ 99.933071 287.603477 0 ] (cb17-51) [ 466 0 R /XYZ 99.933071 268.656456 0 ] (cb17-52) [ 466 0 R /XYZ 99.933071 249.709434 0 ] (cb17-53) [ 466 0 R /XYZ 99.933071 211.815391 0 ] (cb17-54) [ 466 0 R /XYZ 99.933071 192.868370 0 ] (cb17-55) [ 466 0 R /XYZ 99.933071 173.921348 0 ] (cb17-56) [ 466 0 R /XYZ 99.933071 154.974327 0 ] (cb17-57) [ 466 0 R /XYZ 99.933071 136.027305 0 ] (cb17-58) [ 466 0 R /XYZ 99.933071 117.080284 0 ] (cb17-59) [ 466 0 R /XYZ 99.933071 98.133262 0 ] (cb17-6) [ 442 0 R /XYZ 99.933071 408.993907 0 ] (cb17-60) [ 505 0 R /XYZ 99.933071 799.173057 0 ] (cb17-61) [ 505 0 R /XYZ 99.933071 780.226036 0 ] (cb17-7) [ 442 0 R /XYZ 99.933071 390.046885 0 ] (cb17-8) [ 442 0 R /XYZ 99.933071 371.099864 0 ] (cb17-9) [ 442 0 R /XYZ 99.933071 352.152842 0 ] (cb172) [ 753 0 R /XYZ 84.259843 607.820079 0 ] (cb172-1) [ 753 0 R /XYZ 101.433071 606.123057 0 ] (cb174) [ 753 0 R /XYZ 84.259843 298.679014 0 ] (cb174-1) [ 753 0 R /XYZ 101.433071 296.981993 0 ] (cb176) [ 757 0 R /XYZ 84.259843 715.370079 0 ] (cb176-1) [ 757 0 R /XYZ 101.433071 713.673057 0 ] (cb179) [ 757 0 R /XYZ 84.259843 375.479014 0 ] (cb179-1) [ 757 0 R /XYZ 101.433071 373.781993 0 ] (cb179-2) [ 757 0 R /XYZ 99.933071 354.834971 0 ] (cb179-3) [ 757 0 R /XYZ 99.933071 335.887950 0 ] (cb179-4) [ 757 0 R /XYZ 99.933071 279.046885 0 ] (cb179-5) [ 757 0 R /XYZ 99.933071 260.099864 0 ] (cb18) [ 505 0 R /XYZ 84.259843 720.976036 0 ] (cb18-1) [ 505 0 R /XYZ 101.433071 719.279014 0 ] (cb180) [ 757 0 R /XYZ 84.259843 200.849864 0 ] (cb180-1) [ 757 0 R /XYZ 101.433071 199.152842 0 ] (cb182) [ 766 0 R /XYZ 84.259843 655.220079 0 ] (cb182-1) [ 766 0 R /XYZ 101.433071 653.523057 0 ] (cb182-2) [ 766 0 R /XYZ 99.933071 634.576036 0 ] (cb182-3) [ 766 0 R /XYZ 99.933071 615.629014 0 ] (cb182-4) [ 766 0 R /XYZ 99.933071 558.787950 0 ] (cb182-5) [ 766 0 R /XYZ 99.933071 539.840928 0 ] (cb183) [ 766 0 R /XYZ 84.259843 480.590928 0 ] (cb183-1) [ 766 0 R /XYZ 101.433071 478.893907 0 ] (cb185) [ 776 0 R /XYZ 84.259843 490.251496 0 ] (cb185-1) [ 776 0 R /XYZ 101.433071 488.554475 0 ] (cb186) [ 776 0 R /XYZ 84.259843 429.304475 0 ] (cb186-1) [ 776 0 R /XYZ 101.433071 427.607453 0 ] (cb188) [ 776 0 R /XYZ 84.259843 116.807453 0 ] (cb188-1) [ 776 0 R /XYZ 101.433071 115.110432 0 ] (cb189) [ 781 0 R /XYZ 84.259843 772.370079 0 ] (cb189-1) [ 781 0 R /XYZ 101.433071 770.673057 0 ] (cb191) [ 781 0 R /XYZ 84.259843 459.873057 0 ] (cb191-1) [ 781 0 R /XYZ 101.433071 458.176036 0 ] (cb192) [ 781 0 R /XYZ 84.259843 398.926036 0 ] (cb192-1) [ 781 0 R /XYZ 101.433071 397.229014 0 ] (cb194) [ 786 0 R /XYZ 84.259843 799.370079 0 ] (cb194-1) [ 786 0 R /XYZ 101.433071 797.673057 0 ] (cb195) [ 786 0 R /XYZ 84.259843 738.423057 0 ] (cb195-1) [ 786 0 R /XYZ 101.433071 736.726036 0 ] (cb197) [ 786 0 R /XYZ 84.259843 410.926036 0 ] (cb197-1) [ 786 0 R /XYZ 101.433071 409.229014 0 ] (cb198) [ 786 0 R /XYZ 84.259843 349.979014 0 ] (cb198-1) [ 786 0 R /XYZ 101.433071 348.281993 0 ] (cb2) [ 320 0 R /XYZ 84.259843 730.370079 0 ] (cb2-1) [ 320 0 R /XYZ 101.433071 728.673057 0 ] (cb201) [ 792 0 R /XYZ 84.259843 230.570079 0 ] (cb201-1) [ 792 0 R /XYZ 101.433071 228.873057 0 ] (cb202) [ 792 0 R /XYZ 84.259843 169.623057 0 ] (cb202-1) [ 792 0 R /XYZ 101.433071 167.926036 0 ] (cb204) [ 796 0 R /XYZ 84.259843 583.970079 0 ] (cb204-1) [ 796 0 R /XYZ 101.433071 582.273057 0 ] (cb205) [ 796 0 R /XYZ 84.259843 523.023057 0 ] (cb205-1) [ 796 0 R /XYZ 101.433071 521.326036 0 ] (cb207) [ 800 0 R /XYZ 84.259843 700.370079 0 ] (cb207-1) [ 800 0 R /XYZ 101.433071 698.673057 0 ] (cb208) [ 800 0 R /XYZ 84.259843 639.423057 0 ] (cb208-1) [ 800 0 R /XYZ 101.433071 637.726036 0 ] (cb21) [ 510 0 R /XYZ 84.259843 565.251496 0 ] (cb21-1) [ 510 0 R /XYZ 101.433071 563.554475 0 ] (cb210) [ 800 0 R /XYZ 84.259843 296.926036 0 ] (cb210-1) [ 800 0 R /XYZ 101.433071 295.229014 0 ] (cb211) [ 800 0 R /XYZ 84.259843 235.979014 0 ] (cb211-1) [ 800 0 R /XYZ 101.433071 234.281993 0 ] (cb213) [ 806 0 R /XYZ 84.259843 640.370079 0 ] (cb213-1) [ 806 0 R /XYZ 101.433071 638.673057 0 ] (cb214) [ 806 0 R /XYZ 84.259843 579.423057 0 ] (cb214-1) [ 806 0 R /XYZ 101.433071 577.726036 0 ] (cb217) [ 810 0 R /XYZ 84.259843 428.570079 0 ] (cb217-1) [ 810 0 R /XYZ 101.433071 426.873057 0 ] (cb218) [ 810 0 R /XYZ 84.259843 131.823057 0 ] (cb218-1) [ 810 0 R /XYZ 101.433071 130.126036 0 ] (cb219) [ 814 0 R /XYZ 84.259843 799.370079 0 ] (cb219-1) [ 814 0 R /XYZ 101.433071 797.673057 0 ] (cb221) [ 819 0 R /XYZ 84.259843 768.620079 0 ] (cb221-1) [ 819 0 R /XYZ 101.433071 766.923057 0 ] (cb221-10) [ 819 0 R /XYZ 99.933071 596.399864 0 ] (cb221-11) [ 819 0 R /XYZ 99.933071 577.452842 0 ] (cb221-12) [ 819 0 R /XYZ 99.933071 482.717735 0 ] (cb221-13) [ 819 0 R /XYZ 99.933071 463.770714 0 ] (cb221-14) [ 819 0 R /XYZ 99.933071 444.823692 0 ] (cb221-15) [ 819 0 R /XYZ 99.933071 425.876671 0 ] (cb221-16) [ 819 0 R /XYZ 99.933071 406.929649 0 ] (cb221-17) [ 819 0 R /XYZ 99.933071 387.982628 0 ] (cb221-18) [ 819 0 R /XYZ 99.933071 350.088585 0 ] (cb221-19) [ 819 0 R /XYZ 99.933071 331.141563 0 ] (cb221-2) [ 819 0 R /XYZ 99.933071 747.976036 0 ] (cb221-20) [ 819 0 R /XYZ 99.933071 198.512413 0 ] (cb221-21) [ 819 0 R /XYZ 99.933071 179.565391 0 ] (cb221-22) [ 819 0 R /XYZ 99.933071 160.618370 0 ] (cb221-23) [ 819 0 R /XYZ 99.933071 103.777305 0 ] (cb221-24) [ 844 0 R /XYZ 99.933071 799.173057 0 ] (cb221-25) [ 844 0 R /XYZ 99.933071 780.226036 0 ] (cb221-26) [ 844 0 R /XYZ 99.933071 761.279014 0 ] (cb221-27) [ 844 0 R /XYZ 99.933071 742.331993 0 ] (cb221-28) [ 844 0 R /XYZ 99.933071 723.384971 0 ] (cb221-29) [ 844 0 R /XYZ 99.933071 704.437950 0 ] (cb221-3) [ 819 0 R /XYZ 99.933071 729.029014 0 ] (cb221-30) [ 844 0 R /XYZ 99.933071 685.490928 0 ] (cb221-31) [ 844 0 R /XYZ 99.933071 666.543907 0 ] (cb221-4) [ 819 0 R /XYZ 99.933071 710.081993 0 ] (cb221-5) [ 819 0 R /XYZ 99.933071 691.134971 0 ] (cb221-6) [ 819 0 R /XYZ 99.933071 672.187950 0 ] (cb221-7) [ 819 0 R /XYZ 99.933071 653.240928 0 ] (cb221-8) [ 819 0 R /XYZ 99.933071 634.293907 0 ] (cb221-9) [ 819 0 R /XYZ 99.933071 615.346885 0 ] (cb222) [ 844 0 R /XYZ 84.259843 607.293907 0 ] (cb222-1) [ 844 0 R /XYZ 101.433071 605.596885 0 ] (cb225) [ 855 0 R /XYZ 84.259843 434.451496 0 ] (cb225-1) [ 855 0 R /XYZ 101.433071 432.754475 0 ] (cb228) [ 858 0 R /XYZ 84.259843 799.370079 0 ] (cb228-1) [ 858 0 R /XYZ 101.433071 797.673057 0 ] (cb231) [ 858 0 R /XYZ 84.259843 448.229014 0 ] (cb231-1) [ 858 0 R /XYZ 101.433071 446.531993 0 ] (cb234) [ 862 0 R /XYZ 84.259843 799.370079 0 ] (cb234-1) [ 862 0 R /XYZ 101.433071 797.673057 0 ] (cb237) [ 865 0 R /XYZ 84.259843 394.701496 0 ] (cb237-1) [ 865 0 R /XYZ 101.433071 393.004475 0 ] (cb237-10) [ 865 0 R /XYZ 99.933071 222.481281 0 ] (cb237-11) [ 865 0 R /XYZ 99.933071 203.534260 0 ] (cb237-12) [ 865 0 R /XYZ 99.933071 165.640217 0 ] (cb237-13) [ 865 0 R /XYZ 99.933071 127.746174 0 ] (cb237-14) [ 865 0 R /XYZ 99.933071 108.799152 0 ] (cb237-15) [ 865 0 R /XYZ 99.933071 89.852131 0 ] (cb237-16) [ 882 0 R /XYZ 99.933071 799.173057 0 ] (cb237-17) [ 882 0 R /XYZ 99.933071 780.226036 0 ] (cb237-18) [ 882 0 R /XYZ 99.933071 761.279014 0 ] (cb237-19) [ 882 0 R /XYZ 99.933071 742.331993 0 ] (cb237-2) [ 865 0 R /XYZ 99.933071 374.057453 0 ] (cb237-3) [ 865 0 R /XYZ 99.933071 355.110432 0 ] (cb237-4) [ 865 0 R /XYZ 99.933071 336.163410 0 ] (cb237-5) [ 865 0 R /XYZ 99.933071 317.216389 0 ] (cb237-6) [ 865 0 R /XYZ 99.933071 298.269367 0 ] (cb237-7) [ 865 0 R /XYZ 99.933071 279.322346 0 ] (cb237-8) [ 865 0 R /XYZ 99.933071 260.375324 0 ] (cb237-9) [ 865 0 R /XYZ 99.933071 241.428303 0 ] (cb238) [ 882 0 R /XYZ 84.259843 683.081993 0 ] (cb238-1) [ 882 0 R /XYZ 101.433071 681.384971 0 ] (cb24) [ 513 0 R /XYZ 84.259843 125.570079 0 ] (cb24-1) [ 513 0 R /XYZ 101.433071 123.873057 0 ] (cb241) [ 895 0 R /XYZ 84.259843 768.620079 0 ] (cb241-1) [ 895 0 R /XYZ 101.433071 766.923057 0 ] (cb241-10) [ 895 0 R /XYZ 99.933071 596.399864 0 ] (cb241-11) [ 895 0 R /XYZ 99.933071 577.452842 0 ] (cb241-12) [ 895 0 R /XYZ 99.933071 520.611778 0 ] (cb241-13) [ 895 0 R /XYZ 99.933071 501.664756 0 ] (cb241-14) [ 895 0 R /XYZ 99.933071 482.717735 0 ] (cb241-15) [ 895 0 R /XYZ 99.933071 463.770714 0 ] (cb241-16) [ 895 0 R /XYZ 99.933071 444.823692 0 ] (cb241-17) [ 895 0 R /XYZ 99.933071 425.876671 0 ] (cb241-18) [ 895 0 R /XYZ 99.933071 406.929649 0 ] (cb241-2) [ 895 0 R /XYZ 99.933071 747.976036 0 ] (cb241-3) [ 895 0 R /XYZ 99.933071 729.029014 0 ] (cb241-4) [ 895 0 R /XYZ 99.933071 710.081993 0 ] (cb241-5) [ 895 0 R /XYZ 99.933071 691.134971 0 ] (cb241-6) [ 895 0 R /XYZ 99.933071 672.187950 0 ] (cb241-7) [ 895 0 R /XYZ 99.933071 653.240928 0 ] (cb241-8) [ 895 0 R /XYZ 99.933071 634.293907 0 ] (cb241-9) [ 895 0 R /XYZ 99.933071 615.346885 0 ] (cb242) [ 895 0 R /XYZ 84.259843 347.679649 0 ] (cb242-1) [ 895 0 R /XYZ 101.433071 345.982628 0 ] (cb27) [ 518 0 R /XYZ 84.259843 425.570079 0 ] (cb27-1) [ 518 0 R /XYZ 101.433071 423.873057 0 ] (cb3) [ 320 0 R /XYZ 84.259843 523.623057 0 ] (cb3-1) [ 320 0 R /XYZ 101.433071 521.926036 0 ] (cb30) [ 523 0 R /XYZ 84.259843 715.370079 0 ] (cb30-1) [ 523 0 R /XYZ 101.433071 713.673057 0 ] (cb33) [ 526 0 R /XYZ 84.259843 211.820079 0 ] (cb33-1) [ 526 0 R /XYZ 101.433071 210.123057 0 ] (cb36) [ 531 0 R /XYZ 84.259843 451.820079 0 ] (cb36-1) [ 531 0 R /XYZ 101.433071 450.123057 0 ] (cb39) [ 536 0 R /XYZ 84.259843 730.370079 0 ] (cb39-1) [ 536 0 R /XYZ 101.433071 728.673057 0 ] (cb42) [ 539 0 R /XYZ 84.259843 294.320079 0 ] (cb42-1) [ 539 0 R /XYZ 101.433071 292.623057 0 ] (cb45) [ 544 0 R /XYZ 84.259843 575.570079 0 ] (cb45-1) [ 544 0 R /XYZ 101.433071 573.873057 0 ] (cb48) [ 547 0 R /XYZ 84.259843 129.320079 0 ] (cb48-1) [ 547 0 R /XYZ 101.433071 127.623057 0 ] (cb51) [ 552 0 R /XYZ 84.259843 350.570079 0 ] (cb51-1) [ 552 0 R /XYZ 101.433071 348.873057 0 ] (cb54) [ 557 0 R /XYZ 84.259843 538.070079 0 ] (cb54-1) [ 557 0 R /XYZ 101.433071 536.373057 0 ] (cb55) [ 557 0 R /XYZ 84.259843 301.323057 0 ] (cb55-1) [ 557 0 R /XYZ 101.433071 299.626036 0 ] (cb56) [ 561 0 R /XYZ 84.259843 799.370079 0 ] (cb56-1) [ 561 0 R /XYZ 101.433071 797.673057 0 ] (cb59) [ 564 0 R /XYZ 84.259843 350.570079 0 ] (cb59-1) [ 564 0 R /XYZ 101.433071 348.873057 0 ] (cb6) [ 320 0 R /XYZ 84.259843 138.376036 0 ] (cb6-1) [ 320 0 R /XYZ 101.433071 136.679014 0 ] (cb62) [ 569 0 R /XYZ 84.259843 598.970079 0 ] (cb62-1) [ 569 0 R /XYZ 101.433071 597.273057 0 ] (cb65) [ 574 0 R /XYZ 84.259843 772.370079 0 ] (cb65-1) [ 574 0 R /XYZ 101.433071 770.673057 0 ] (cb68) [ 577 0 R /XYZ 84.259843 271.820079 0 ] (cb68-1) [ 577 0 R /XYZ 101.433071 270.123057 0 ] (cb71) [ 582 0 R /XYZ 84.259843 571.820079 0 ] (cb71-1) [ 582 0 R /XYZ 101.433071 570.123057 0 ] (cb74) [ 585 0 R /XYZ 84.259843 144.320079 0 ] (cb74-1) [ 585 0 R /XYZ 101.433071 142.623057 0 ] (cb77) [ 590 0 R /XYZ 84.259843 440.570079 0 ] (cb77-1) [ 590 0 R /XYZ 101.433071 438.873057 0 ] (cb80) [ 595 0 R /XYZ 84.259843 715.370079 0 ] (cb80-1) [ 595 0 R /XYZ 101.433071 713.673057 0 ] (cb83) [ 598 0 R /XYZ 84.259843 275.570079 0 ] (cb83-1) [ 598 0 R /XYZ 101.433071 273.873057 0 ] (cb86) [ 603 0 R /XYZ 84.259843 556.820079 0 ] (cb86-1) [ 603 0 R /XYZ 101.433071 555.123057 0 ] (cb89) [ 606 0 R /XYZ 84.259843 125.570079 0 ] (cb89-1) [ 606 0 R /XYZ 101.433071 123.873057 0 ] (cb9) [ 327 0 R /XYZ 84.259843 509.420079 0 ] (cb9-1) [ 327 0 R /XYZ 101.433071 507.723057 0 ] (cb9-10) [ 327 0 R /XYZ 99.933071 318.252842 0 ] (cb9-11) [ 327 0 R /XYZ 99.933071 299.305821 0 ] (cb9-12) [ 327 0 R /XYZ 99.933071 280.358799 0 ] (cb9-13) [ 327 0 R /XYZ 99.933071 261.411778 0 ] (cb9-14) [ 327 0 R /XYZ 99.933071 242.464756 0 ] (cb9-15) [ 327 0 R /XYZ 99.933071 223.517735 0 ] (cb9-16) [ 327 0 R /XYZ 99.933071 204.570714 0 ] (cb9-17) [ 327 0 R /XYZ 99.933071 185.623692 0 ] (cb9-18) [ 327 0 R /XYZ 99.933071 166.676671 0 ] (cb9-19) [ 327 0 R /XYZ 99.933071 147.729649 0 ] (cb9-2) [ 327 0 R /XYZ 99.933071 488.776036 0 ] (cb9-20) [ 327 0 R /XYZ 99.933071 128.782628 0 ] (cb9-21) [ 327 0 R /XYZ 99.933071 109.835606 0 ] (cb9-22) [ 327 0 R /XYZ 99.933071 90.888585 0 ] (cb9-23) [ 351 0 R /XYZ 99.933071 799.173057 0 ] (cb9-24) [ 351 0 R /XYZ 99.933071 780.226036 0 ] (cb9-25) [ 351 0 R /XYZ 99.933071 761.279014 0 ] (cb9-26) [ 351 0 R /XYZ 99.933071 742.331993 0 ] (cb9-27) [ 351 0 R /XYZ 99.933071 723.384971 0 ] (cb9-28) [ 351 0 R /XYZ 99.933071 704.437950 0 ] (cb9-29) [ 351 0 R /XYZ 99.933071 685.490928 0 ] (cb9-3) [ 327 0 R /XYZ 99.933071 469.829014 0 ] (cb9-30) [ 351 0 R /XYZ 99.933071 666.543907 0 ] (cb9-31) [ 351 0 R /XYZ 99.933071 647.596885 0 ] (cb9-32) [ 351 0 R /XYZ 99.933071 628.649864 0 ] (cb9-33) [ 351 0 R /XYZ 99.933071 609.702842 0 ] (cb9-34) [ 351 0 R /XYZ 99.933071 590.755821 0 ] (cb9-35) [ 351 0 R /XYZ 99.933071 571.808799 0 ] (cb9-36) [ 351 0 R /XYZ 99.933071 552.861778 0 ] (cb9-37) [ 351 0 R /XYZ 99.933071 533.914756 0 ] (cb9-38) [ 351 0 R /XYZ 99.933071 514.967735 0 ] (cb9-39) [ 351 0 R /XYZ 99.933071 496.020714 0 ] (cb9-4) [ 327 0 R /XYZ 99.933071 431.934971 0 ] (cb9-40) [ 351 0 R /XYZ 99.933071 477.073692 0 ] (cb9-41) [ 351 0 R /XYZ 99.933071 458.126671 0 ] (cb9-42) [ 351 0 R /XYZ 99.933071 439.179649 0 ] (cb9-43) [ 351 0 R /XYZ 99.933071 420.232628 0 ] (cb9-44) [ 351 0 R /XYZ 99.933071 401.285606 0 ] (cb9-5) [ 327 0 R /XYZ 99.933071 412.987950 0 ] (cb9-6) [ 327 0 R /XYZ 99.933071 394.040928 0 ] (cb9-7) [ 327 0 R /XYZ 99.933071 375.093907 0 ] (cb9-8) [ 327 0 R /XYZ 99.933071 356.146885 0 ] (cb9-9) [ 327 0 R /XYZ 99.933071 337.199864 0 ] (cb92) [ 611 0 R /XYZ 84.259843 440.570079 0 ] (cb92-1) [ 611 0 R /XYZ 101.433071 438.873057 0 ] (cb95) [ 616 0 R /XYZ 84.259843 685.370079 0 ] (cb95-1) [ 616 0 R /XYZ 101.433071 683.673057 0 ] (cb98) [ 619 0 R /XYZ 84.259843 238.070079 0 ] (cb98-1) [ 619 0 R /XYZ 101.433071 236.373057 0 ] (client-certificate-authentication-should-not-be-used-for-users-manual) [ 743 0 R /XYZ 84.259843 684.651496 0 ] (configure-image-provenance-using-imagepolicywebhook-admission-controller-manual) [ 891 0 R /XYZ 84.259843 684.651496 0 ] (consider-external-secret-storage-manual) [ 889 0 R /XYZ 84.259843 568.851496 0 ] (contentsbox) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (controller-manager) [ 676 0 R /XYZ 41.740157 784.430079 0 ] (controls) [ 311 0 R /XYZ 84.259843 612.381496 0 ] (create-administrative-boundaries-between-resources-using-namespaces-manual) [ 893 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-a-minimal-audit-policy-is-created-automated) [ 745 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-a-unique-certificate-authority-is-used-for-etcd-automated) [ 736 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-all-namespaces-have-network-policies-defined-automated) [ 865 0 R /XYZ 84.259843 538.851496 0 ] (ensure-that-default-service-accounts-are-not-actively-used.-automated) [ 817 0 R /XYZ 84.259843 206.451496 0 ] (ensure-that-encryption-providers-are-appropriately-configured-automated) [ 645 0 R /XYZ 84.259843 577.220079 0 ] (ensure-that-service-account-tokens-are-only-mounted-where-necessary-manual) [ 844 0 R /XYZ 84.259843 449.446885 0 ] (ensure-that-the---anonymous-auth-argument-is-set-to-false-automated) [ 510 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the---audit-log-maxage-argument-is-set-to-30-or-as-appropriate-automated) [ 598 0 R /XYZ 84.259843 445.970079 0 ] (ensure-that-the---audit-log-maxbackup-argument-is-set-to-10-or-as-appropriate-automated) [ 603 0 R /XYZ 84.259843 727.220079 0 ] (ensure-that-the---audit-log-maxsize-argument-is-set-to-100-or-as-appropriate-automated) [ 606 0 R /XYZ 84.259843 295.970079 0 ] (ensure-that-the---audit-log-path-argument-is-set-automated) [ 593 0 R /XYZ 84.259843 183.470079 0 ] (ensure-that-the---authorization-mode-argument-includes-node-automated) [ 539 0 R /XYZ 84.259843 464.720079 0 ] (ensure-that-the---authorization-mode-argument-includes-rbac-automated) [ 544 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated) [ 534 0 R /XYZ 84.259843 183.470079 0 ] (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated-1) [ 776 0 R /XYZ 84.259843 332.207453 0 ] (ensure-that-the---auto-tls-argument-is-not-set-to-true-automated) [ 712 0 R /XYZ 84.259843 258.470079 0 ] (ensure-that-the---basic-auth-file-argument-is-not-set-automated) [ 513 0 R /XYZ 84.259843 295.970079 0 ] (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated) [ 691 0 R /XYZ 84.259843 524.420079 0 ] (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated-1) [ 696 0 R /XYZ 84.259843 257.404475 0 ] (ensure-that-the---cert-file-and---key-file-arguments-are-set-as-appropriate-automated) [ 702 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated) [ 632 0 R /XYZ 84.259843 483.470079 0 ] (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated-1) [ 781 0 R /XYZ 84.259843 675.273057 0 ] (ensure-that-the---client-cert-auth-argument-is-set-to-true-automated) [ 707 0 R /XYZ 84.259843 464.720079 0 ] (ensure-that-the---encryption-provider-config-argument-is-set-as-appropriate-automated) [ 640 0 R /XYZ 84.259843 295.970079 0 ] (ensure-that-the---etcd-cafile-argument-is-set-as-appropriate-automated) [ 637 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the---etcd-certfile-and---etcd-keyfile-arguments-are-set-as-appropriate-automated) [ 624 0 R /XYZ 84.259843 689.720079 0 ] (ensure-that-the---event-qps-argument-is-set-to-0-or-a-level-which-ensures-appropriate-event-capture-automated) [ 796 0 R /XYZ 84.259843 208.126036 0 ] (ensure-that-the---hostname-override-argument-is-not-set-manual) [ 796 0 R /XYZ 84.259843 425.926036 0 ] (ensure-that-the---insecure-bind-address-argument-is-not-set-automated) [ 577 0 R /XYZ 84.259843 427.220079 0 ] (ensure-that-the---insecure-port-argument-is-set-to-0-automated) [ 582 0 R /XYZ 84.259843 727.220079 0 ] (ensure-that-the---kubeconfig-kubelet.conf-file-ownership-is-set-to-rootroot-automated) [ 753 0 R /XYZ 84.259843 163.687950 0 ] (ensure-that-the---kubeconfig-kubelet.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 753 0 R /XYZ 84.259843 454.079014 0 ] (ensure-that-the---kubelet-certificate-authority-argument-is-set-as-appropriate-automated) [ 531 0 R /XYZ 84.259843 652.220079 0 ] (ensure-that-the---kubelet-client-certificate-and---kubelet-client-key-arguments-are-set-as-appropriate-automated) [ 526 0 R /XYZ 84.259843 427.220079 0 ] (ensure-that-the---kubelet-https-argument-is-set-to-true-automated) [ 521 0 R /XYZ 84.259843 164.720079 0 ] (ensure-that-the---make-iptables-util-chains-argument-is-set-to-true-automated) [ 796 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the---peer-auto-tls-argument-is-not-set-to-true-automated) [ 729 0 R /XYZ 84.259843 333.470079 0 ] (ensure-that-the---peer-cert-file-and---peer-key-file-arguments-are-set-as-appropriate-automated) [ 719 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the---peer-client-cert-auth-argument-is-set-to-true-automated) [ 724 0 R /XYZ 84.259843 558.470079 0 ] (ensure-that-the---profiling-argument-is-set-to-false-automated) [ 590 0 R /XYZ 84.259843 595.970079 0 ] (ensure-that-the---profiling-argument-is-set-to-false-automated-1) [ 679 0 R /XYZ 84.259843 727.220079 0 ] (ensure-that-the---profiling-argument-is-set-to-false-automated-2) [ 696 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the---protect-kernel-defaults-argument-is-set-to-true-automated) [ 792 0 R /XYZ 84.259843 445.970079 0 ] (ensure-that-the---read-only-port-argument-is-set-to-0-automated) [ 781 0 R /XYZ 84.259843 301.829014 0 ] (ensure-that-the---request-timeout-argument-is-set-as-appropriate-automated) [ 611 0 R /XYZ 84.259843 595.970079 0 ] (ensure-that-the---root-ca-file-argument-is-set-as-appropriate-automated) [ 688 0 R /XYZ 84.259843 727.220079 0 ] (ensure-that-the---rotate-certificates-argument-is-not-set-to-false-automated) [ 800 0 R /XYZ 84.259843 138.881993 0 ] (ensure-that-the---secure-port-argument-is-not-set-to-0-automated) [ 585 0 R /XYZ 84.259843 314.720079 0 ] (ensure-that-the---service-account-key-file-argument-is-set-as-appropriate-automated) [ 619 0 R /XYZ 84.259843 408.470079 0 ] (ensure-that-the---service-account-lookup-argument-is-set-to-true-automated) [ 614 0 R /XYZ 84.259843 164.720079 0 ] (ensure-that-the---service-account-private-key-file-argument-is-set-as-appropriate-automated) [ 685 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the---streaming-connection-idle-timeout-argument-is-not-set-to-0-automated) [ 786 0 R /XYZ 84.259843 641.326036 0 ] (ensure-that-the---terminated-pod-gc-threshold-argument-is-set-as-appropriate-automated) [ 676 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated) [ 627 0 R /XYZ 84.259843 239.720079 0 ] (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated-1) [ 800 0 R /XYZ 84.259843 542.326036 0 ] (ensure-that-the---token-auth-file-parameter-is-not-set-automated) [ 518 0 R /XYZ 84.259843 595.970079 0 ] (ensure-that-the---use-service-account-credentials-argument-is-set-to-true-automated) [ 682 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the-admin.conf-file-ownership-is-set-to-rootroot-automated) [ 325 0 R /XYZ 84.259843 586.670079 0 ] (ensure-that-the-admin.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 325 0 R /XYZ 84.259843 702.470079 0 ] (ensure-that-the-admission-control-plugin-alwaysadmit-is-not-set-automated) [ 552 0 R /XYZ 84.259843 520.970079 0 ] (ensure-that-the-admission-control-plugin-alwayspullimages-is-set-manual) [ 557 0 R /XYZ 84.259843 708.470079 0 ] (ensure-that-the-admission-control-plugin-eventratelimit-is-set-automated) [ 547 0 R /XYZ 84.259843 314.720079 0 ] (ensure-that-the-admission-control-plugin-namespacelifecycle-is-set-automated) [ 564 0 R /XYZ 84.259843 520.970079 0 ] (ensure-that-the-admission-control-plugin-noderestriction-is-set-automated) [ 572 0 R /XYZ 84.259843 258.470079 0 ] (ensure-that-the-admission-control-plugin-podsecuritypolicy-is-set-automated) [ 569 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the-admission-control-plugin-securitycontextdeny-is-set-if-podsecuritypolicy-is-not-used-manual) [ 557 0 R /XYZ 84.259843 501.723057 0 ] (ensure-that-the-admission-control-plugin-serviceaccount-is-set-automated) [ 557 0 R /XYZ 84.259843 264.976036 0 ] (ensure-that-the-anonymous-auth-argument-is-set-to-false-automated) [ 776 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the-api-server-only-makes-use-of-strong-cryptographic-ciphers-automated) [ 662 0 R /XYZ 84.259843 411.552842 0 ] (ensure-that-the-api-server-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 315 0 R /XYZ 84.259843 553.851496 0 ] (ensure-that-the-api-server-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 315 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-audit-policy-covers-key-security-concerns-manual) [ 748 0 R /XYZ 84.259843 333.470079 0 ] (ensure-that-the-certificate-authorities-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 757 0 R /XYZ 84.259843 519.629014 0 ] (ensure-that-the-client-certificate-authorities-file-ownership-is-set-to-rootroot-automated) [ 766 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the-cluster-admin-role-is-only-used-where-required-manual) [ 817 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-cni-in-use-supports-network-policies-manual) [ 865 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-container-network-interface-file-ownership-is-set-to-rootroot-manual) [ 317 0 R /XYZ 84.259843 170.823057 0 ] (ensure-that-the-container-network-interface-file-permissions-are-set-to-644-or-more-restrictive-manual) [ 317 0 R /XYZ 84.259843 347.570079 0 ] (ensure-that-the-controller-manager-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 315 0 R /XYZ 84.259843 277.251496 0 ] (ensure-that-the-controller-manager-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 315 0 R /XYZ 84.259843 423.051496 0 ] (ensure-that-the-controller-manager.conf-file-ownership-is-set-to-rootroot-automated) [ 327 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the-controller-manager.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 325 0 R /XYZ 84.259843 209.270079 0 ] (ensure-that-the-etcd-data-directory-ownership-is-set-to-etcdetcd-automated) [ 320 0 R /XYZ 84.259843 365.776036 0 ] (ensure-that-the-etcd-data-directory-permissions-are-set-to-700-or-more-restrictive-automated) [ 320 0 R /XYZ 84.259843 694.023057 0 ] (ensure-that-the-etcd-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 317 0 R /XYZ 84.259843 478.370079 0 ] (ensure-that-the-etcd-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 317 0 R /XYZ 84.259843 609.170079 0 ] (ensure-that-the-kubelet---config-configuration-file-has-permissions-set-to-644-or-more-restrictive-automated) [ 766 0 R /XYZ 84.259843 383.493907 0 ] (ensure-that-the-kubelet---config-configuration-file-ownership-is-set-to-rootroot-automated) [ 766 0 R /XYZ 84.259843 195.693907 0 ] (ensure-that-the-kubelet-only-makes-use-of-strong-cryptographic-ciphers-automated) [ 810 0 R /XYZ 84.259843 392.223057 0 ] (ensure-that-the-kubelet-service-file-ownership-is-set-to-rootroot-automated) [ 750 0 R /XYZ 84.259843 553.851496 0 ] (ensure-that-the-kubelet-service-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 750 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-kubernetes-pki-certificate-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 351 0 R /XYZ 84.259843 184.188585 0 ] (ensure-that-the-kubernetes-pki-directory-and-file-ownership-is-set-to-rootroot-automated) [ 327 0 R /XYZ 84.259843 668.570079 0 ] (ensure-that-the-kubernetes-pki-key-file-permissions-are-set-to-600-automated) [ 442 0 R /XYZ 84.259843 702.470079 0 ] (ensure-that-the-proxy-kubeconfig-file-ownership-is-set-to-rootroot-automated) [ 753 0 R /XYZ 84.259843 763.220079 0 ] (ensure-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) [ 691 0 R /XYZ 84.259843 727.220079 0 ] (ensure-that-the-scheduler-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 317 0 R /XYZ 84.259843 739.970079 0 ] (ensure-that-the-scheduler-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 315 0 R /XYZ 84.259843 146.451496 0 ] (ensure-that-the-scheduler.conf-file-ownership-is-set-to-rootroot-automated) [ 325 0 R /XYZ 84.259843 340.070079 0 ] (ensure-that-the-scheduler.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 325 0 R /XYZ 84.259843 470.870079 0 ] (ensure-that-the-seccomp-profile-is-set-to-dockerdefault-in-your-pod-definitions-manual) [ 893 0 R /XYZ 84.259843 604.851496 0 ] (etcd-node-configuration-files) [ 702 0 R /XYZ 41.740157 784.430079 0 ] (extensible-admission-control) [ 891 0 R /XYZ 41.740157 784.430079 0 ] (general-policies) [ 893 0 R /XYZ 41.740157 784.430079 0 ] (header_bottom_text) [ 6 0 R /XYZ 85.009843 392.718898 0 ] (if-proxy-kubeconfig-file-exists-ensure-permissions-are-set-to-644-or-more-restrictive-automated) [ 750 0 R /XYZ 84.259843 423.051496 0 ] (kubelet) [ 776 0 R /XYZ 41.740157 784.430079 0 ] (logging) [ 745 0 R /XYZ 41.740157 784.430079 0 ] (master-node-configuration-files) [ 315 0 R /XYZ 41.740157 784.430079 0 ] (minimize-access-to-create-pods-manual) [ 817 0 R /XYZ 84.259843 307.251496 0 ] (minimize-access-to-secrets-manual) [ 817 0 R /XYZ 84.259843 523.851496 0 ] (minimize-the-admission-of-containers-wishing-to-share-the-host-ipc-namespace-automated) [ 855 0 R /XYZ 84.259843 238.710432 0 ] (minimize-the-admission-of-containers-wishing-to-share-the-host-network-namespace-automated) [ 858 0 R /XYZ 84.259843 603.629014 0 ] (minimize-the-admission-of-containers-wishing-to-share-the-host-process-id-namespace-automated) [ 855 0 R /XYZ 84.259843 589.851496 0 ] (minimize-the-admission-of-containers-with-added-capabilities-manual) [ 862 0 R /XYZ 84.259843 323.081993 0 ] (minimize-the-admission-of-containers-with-allowprivilegeescalation-automated) [ 858 0 R /XYZ 84.259843 252.487950 0 ] (minimize-the-admission-of-containers-with-capabilities-assigned-manual) [ 862 0 R /XYZ 84.259843 207.281993 0 ] (minimize-the-admission-of-containers-with-the-net_raw-capability-manual) [ 862 0 R /XYZ 84.259843 453.881993 0 ] (minimize-the-admission-of-privileged-containers-manual) [ 855 0 R /XYZ 84.259843 720.651496 0 ] (minimize-the-admission-of-root-containers-manual) [ 862 0 R /XYZ 84.259843 584.681993 0 ] (minimize-wildcard-use-in-roles-and-clusterroles-manual) [ 817 0 R /XYZ 84.259843 423.051496 0 ] (network-policies-and-cni) [ 865 0 R /XYZ 41.740157 784.430079 0 ] (overview) [ 304 0 R /XYZ 84.259843 704.822079 0 ] (pod-security-policies) [ 855 0 R /XYZ 41.740157 784.430079 0 ] (prefer-using-secrets-as-files-over-secrets-as-environment-variables-manual) [ 889 0 R /XYZ 84.259843 684.651496 0 ] (rbac-and-service-accounts) [ 817 0 R /XYZ 41.740157 784.430079 0 ] (rke-cis-v1.6-kubernetes-benchmark---rancher-v2.6-with-kubernetes-v1.18-to-v1.23) [ 304 0 R /XYZ 84.259843 784.970079 0 ] (scheduler) [ 696 0 R /XYZ 41.740157 784.430079 0 ] (secrets-management) [ 889 0 R /XYZ 41.740157 784.430079 0 ] (testing-controls-methodology) [ 304 0 R /XYZ 84.259843 166.076079 0 ] (the-default-namespace-should-not-be-used-automated) [ 893 0 R /XYZ 84.259843 193.251496 0 ] (title-block-header) [ 6 0 R /XYZ 84.259843 502.818898 0 ] (verify-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) [ 810 0 R /XYZ 84.259843 670.970079 0 ] (worker-node-configuration-files) [ 750 0 R /XYZ 41.740157 784.430079 0 ] ] ->> ->> ->> -endobj -4 0 obj -<< -/ExtGState << -/a1.0 << -/ca 1 ->> -/A1.0 << -/CA 1 ->> ->> -/XObject << ->> -/Pattern << ->> -/Shading << ->> -/Font 1078 0 R ->> -endobj -5 0 obj -<< -/Filter /FlateDecode -/Length 2625 ->> -stream -xMc ^/ Ȣ@6i4Š Zt3 ;&]ձw>2S="u$zDֳBQ]Cd?_ޜޞ$$;jxtV\MX X鄏gŽ/_uch-GM__u[(IDՠ5J)S&ST< o51+QUa^U fĢT0C[*D;4P wD)d zf!D3 &erΩ2ÖD.tŭ˰Ų X1]-ӈxW:"Y隅Ԫ;5褖Bft!7갢0I]-YR:ؒL"lqHVj%5mbt X` & f"%3`%ƀXJA V ^2 -ڂb .* lI LacRla *0X`[ uiX`ୋfpa0k5;cpX``bu-X`y͌08k; @`Z]S)bEjfJ -c38 +k ܍ vnp7&F $=t XK  YӠU2cAwb-qn1Asn Fe >+cFƂaf:pWcƂ"nHp .յ VƂKp -P] p$e, e,.X]IfGCujd,@\-YVD]Q0Ӂ"1dpotA00 -zhdƂ:|Tʉ Ȣ: Xf2[,FƂa BD)o  Rd,Bm%ecU1\S]N cA)+crP %:cAiK[Q9)lAXH:UƂa AƂ+,ءKbΥ癕z=Td,2A RRl& 0?=NH~l"͡:b j=ݬ–(X c,hC qD V .{Y Mxd6=,aKBBuAS#LB :1]-9cA˹盕aMDH|p75]D䛈lYn/o*ϸzVzd `/vB 9=4,kVT"&\O# w(3kٰ,9V5{Gد? ^qsOs?U9nZOۇ[;5~SB<~HKMѼo0W+ x'J_Bޡ׍H?f߾>\޵- .:Qork㨟 s*̖{u/}av6[]w:WGQ?}}>ق{;x{=\۳m|k߼]-"n6g >U،oG|iz+Z; vtC?ƾ`'ywoE*LYD ~l d= -B:M;<ZG=~9n!ߣYb$XQ ǏwRf[H3&p]ٸq u=ab!(O/Ao~]JyMjuj ӣP8G{~4./4}:ݦԍe /'tkϥOTOFSct mF)MDDѴc2~\u8zm#ˉֻLY[erus/5"6.ŹkorB\S*vZ4\oWYoC9d=WT)9.zJ6~vyq6e݆KK>V!;tg9bwm6yiü {N⎰1>Pnt;3ͥdvus4]<˜qw^͟Gl.%^}:cN:Zdlǽ~9\[ؑg"cܣ.=u'?7R>e"NމX?Rܿ¹l6a KuM>k_:01qnTF&Gxy63ܹYhЍwX8(֥%&QUזFFQ:l˲;3C̡> -[ыtٽ!;bްifr+K'ڧi <.sϱs/ŻFheڳ䬥B +>IV!u:6 dfeؔoa9Q*3X_NAL䇺ݱhfvw.d՜d%=jڐ=}=/CLeݖj~>e)Vkqc﷤ x -xݎJ~=?;yowC=~,*_^Yzk¸ң"_PK -endstream -endobj -6 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 5 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -7 0 obj -<< -/Filter /FlateDecode -/Length 3667 ->> -stream -x\]ܶ}_C?m6AmӢNP\pпCI$Zk9<3Cjk?'y;cû"-#)2磍v21Eooָ9JnMLJv? Y&NCM:rBlaB?p%|?Û桇HS6̖Dqp"HtIe:[;_/;u0{޺0A!L-[=pu4@lqDY4ȶi7cgjo!qC-.S:G8Ѕ8Aٕ?+y{A(qDoILRғqagD7$z3It__^M7$d %Q$XM:>JR\;(u#Qmj-$*p!.〲lv p[L= 8ơ -C)Kt]83:`'A)-z!B0D;S|?Bb4o/HlI&ћD$ Q83DoI$//t/I&ћDo}UWQo%|iqQ -\睛HQQI=x>OQbLV@YMK^ؙ{[{CP!eDgā.AF%^::DS8C8X:`jH^"7$zD;#I&ћDIRBtoI&G-t$AEoMpPnk0ev!͏" M%VlM] -FI;9(6cXYᐑ.#;2CAh!C.ir >aqXA+Q02ձ8Ly2eI8p(yL EY0X(p&À K@G.YpB1H)(mR5l B0|6D%C&7D40D5Qmt4clj&TH&gՔCR8X+Ya4Ɛ#5k5>VS"I9k5DAjJD4pQ j6c&8DD:q:hVS"꠱2'DAck5%bs$Č\Y)1EsZMIM9dɰ1Քd3gS8JkHF09Lj5%9lQQ9yl|jJNF8db)!IwJ!bߠDʛsZMI >{T[8p l |&KZMg-|6qZMA^L1yՔLeVSS X("'/N)#ņ᳃5>" 9g[ԣDաVSrDcՔ\LDA03ZMv -B!F{nﵪ]/LFFa'6]ޕ1;Xᐍ~yo~o^YZ^,Xs*#f#te/_~ _|߳$aw-i>\x] mm/e!~s5?~z 6$A5bP1*2kpe'V'ch5~РqKGtaX9#+26Ǿx^ř:^Oܝ+#Κ}4x_>> Up5pQ_@;|qK ^gq\wY-#W_gn+Apϊ\`?s_.rS\_ ϴ%/w֛,cwYV|0TCdNg->DMҹNN-Xd.)oNgV!BjILBhDܖdˏYly볊)Ęs79u46szRNmN'LfmՇWnͅSϋ-uJ>{x2v3GWp`a&㬖hbC oEkyc龛 k*̲ N^Ss;U -vz?|e{g_N;gO}ypyxgzkxոٙi{p{5W}-O.\7eo6> -endobj -9 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 671.061024 504.679134 638.361024 ] -/BS << -/W 0 ->> -/Dest (rke-cis-v1.6-kubernetes-benchmark---rancher-v2.6-with-kubernetes-v1.18-to-v1.23) ->> -endobj -10 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.750423 648.111024 496.429134 633.111024 ] -/BS << -/W 0 ->> -/Dest (rke-cis-v1.6-kubernetes-benchmark---rancher-v2.6-with-kubernetes-v1.18-to-v1.23) ->> -endobj -11 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 626.361024 504.679134 593.661024 ] -/BS << -/W 0 ->> -/Dest (controls) ->> -endobj -12 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 485.690364 618.411024 496.429134 603.411024 ] -/BS << -/W 0 ->> -/Dest (controls) ->> -endobj -13 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 581.661024 504.679134 548.961024 ] -/BS << -/W 0 ->> -/Dest (master-node-configuration-files) ->> -endobj -14 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 485.521907 573.711024 496.429134 558.711024 ] -/BS << -/W 0 ->> -/Dest (master-node-configuration-files) ->> -endobj -15 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 530.961024 498.679134 507.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -16 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 510.561024 491.179134 495.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -17 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 491.361024 498.679134 467.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -18 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 470.961024 491.179134 455.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -19 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 451.761024 498.679134 428.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -20 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 431.361024 491.179134 416.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -21 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 412.161024 498.679134 388.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -22 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 391.761024 491.179134 376.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -23 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 372.561024 498.679134 349.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -24 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 352.161024 491.179134 337.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -25 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 332.961024 498.679134 309.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -26 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 312.561024 491.179134 297.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -27 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 293.361024 498.679134 269.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -28 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 272.961024 491.179134 257.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -29 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 253.761024 498.679134 230.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -30 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 233.361024 491.179134 218.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -31 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 214.161024 498.679134 190.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -32 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 193.761024 491.179134 178.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -33 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 174.561024 498.679134 151.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-ownership-is-set-to-rootroot-manual) ->> -endobj -34 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 154.161024 491.179134 139.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-ownership-is-set-to-rootroot-manual) ->> -endobj -35 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 134.961024 498.679134 111.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-permissions-are-set-to-700-or-more-restrictive-automated) ->> -endobj -36 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 114.561024 491.179134 99.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-permissions-are-set-to-700-or-more-restrictive-automated) ->> -endobj -37 0 obj -<< -/Filter /FlateDecode -/Length 3687 ->> -stream -x\K sb=Ç<. d#"769T%ccf$SUzo@~.b8_>~%-}41 g LL S! LA@#ɢ3g ,:/&΁7\ L1yЋX1PĠ3ǐDgP A.ML@rc&J61ѻ90Μ$љ!0!ɢ3%,H CB!/:byK!0 :{HrJ6&:ʉcD(?DQ&G1b6G#.`cDgF (:P?$%(e#5ȧlƑ!r6| lA!0A lR9 R1QIHD.)"c1s`Nb`cDgJ1"$13x Rc1A :^dLSD'dKVhKR:(s 13 a@Pl,0Re7EXGd<d%0˔geqKe2ienvD>z^/߂siYEY>;~TgL/2z^/j7OwOp+1x7;4;o4_>y)4R?_2y}R?cnRx-j>oR&Ѽ,jYx\GԁdD]XIv?㦃'os';yYGgŷ ,~K:@h>ځ32G;jqq{ud2.?Kedͺ}G}bMnw_&d6k%F­1D.oNq{uDݟ0Xۯ*bM+>:VmgxsvEiHvߕH.\C$ Ւny+tUgV5/K4omdPР]nܸ:6;,\Gc@V<.䎯Bq{xmvc2D% {;+V.2`>SY*2Zgpe^pg={]m>ǝlXՆwBWmXu]e.xyeX3%)[$j;]k~]9T?--Iݮ2rA[n{W\P՞'g\dڱGf}W3ˮvضxm3:\>>Sj̝.=G^k3bKe@KJ.&YG$|? `:*Saex LM/X^͞ce)-s=Ģ3Lɥ˜|_R!'tڏ!'70&s} Dz ^Zy@2bM*WЛxNDA$;iSu43N1xugϞ~f(04Ϝh3V`4NcC-gA?2kYsO]!%@-gԷW:Hs?miUPtfWYk1UrZ54k]<Ҍ#+ -֊fK&@Ǿxr}^<{}\ o*<ȁriRΐf÷_7 GG +Dm7RKַ} /xu -endstream -endobj -38 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 37 0 R -/Resources 4 0 R -/Annots [ 39 0 R 40 0 R 41 0 R 42 0 R 43 0 R 44 0 R 45 0 R 46 0 R 47 0 R 48 0 R 49 0 R 50 0 R 51 0 R 52 0 R 53 0 R 54 0 R 55 0 R 56 0 R 57 0 R 58 0 R 59 0 R 60 0 R 61 0 R 62 0 R 63 0 R 64 0 R 65 0 R 66 0 R 67 0 R 68 0 R 69 0 R 70 0 R 71 0 R 72 0 R 73 0 R 74 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -39 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-ownership-is-set-to-etcdetcd-automated) ->> -endobj -40 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-ownership-is-set-to-etcdetcd-automated) ->> -endobj -41 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -42 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -43 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -44 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -45 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -46 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -47 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -48 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -49 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -50 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -51 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -52 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -53 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-directory-and-file-ownership-is-set-to-rootroot-automated) ->> -endobj -54 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-directory-and-file-ownership-is-set-to-rootroot-automated) ->> -endobj -55 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 473.570079 498.679134 450.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-certificate-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -56 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 453.170079 491.179134 438.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-certificate-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -57 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 433.970079 498.679134 410.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-key-file-permissions-are-set-to-600-automated) ->> -endobj -58 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 413.570079 491.179134 398.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-key-file-permissions-are-set-to-600-automated) ->> -endobj -59 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 394.370079 504.679134 361.670079 ] -/BS << -/W 0 ->> -/Dest (api-server) ->> -endobj -60 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.982112 386.420079 496.429134 371.420079 ] -/BS << -/W 0 ->> -/Dest (api-server) ->> -endobj -61 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 343.670079 498.679134 320.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---anonymous-auth-argument-is-set-to-false-automated) ->> -endobj -62 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 323.270079 491.179134 308.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---anonymous-auth-argument-is-set-to-false-automated) ->> -endobj -63 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 304.070079 498.679134 280.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---basic-auth-file-argument-is-not-set-automated) ->> -endobj -64 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 298.670079 491.179134 283.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---basic-auth-file-argument-is-not-set-automated) ->> -endobj -65 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 264.470079 498.679134 241.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---token-auth-file-parameter-is-not-set-automated) ->> -endobj -66 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 259.070079 491.179134 244.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---token-auth-file-parameter-is-not-set-automated) ->> -endobj -67 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 224.870079 498.679134 201.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-https-argument-is-set-to-true-automated) ->> -endobj -68 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 219.470079 491.179134 204.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-https-argument-is-set-to-true-automated) ->> -endobj -69 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 185.270079 498.679134 161.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-client-certificate-and---kubelet-client-key-arguments-are-set-as-appropriate-automated) ->> -endobj -70 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 164.870079 491.179134 149.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-client-certificate-and---kubelet-client-key-arguments-are-set-as-appropriate-automated) ->> -endobj -71 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 145.670079 498.679134 122.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-certificate-authority-argument-is-set-as-appropriate-automated) ->> -endobj -72 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 125.270079 491.179134 110.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-certificate-authority-argument-is-set-as-appropriate-automated) ->> -endobj -73 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 106.070079 498.679134 82.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated) ->> -endobj -74 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 85.670079 491.179134 70.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated) ->> -endobj -75 0 obj -<< -/Filter /FlateDecode -/Length 3500 ->> -stream -x\Mϯ$dI|qAF4VޚݝQ%VꮮfGV=7=~OJќx.ǟdg9'CȮMe|,.9?5r Yz̩2|ձ-Zf@V&s|Vf`ŞQhb`UVGWK*aNҫСfK*:FBcTWg1lUL 0`UV'<0Vg.K*:!ҫ -XzUաҫ -΅ҫ -,>{Lk߰njY20e)KVFⴜ"&9u zcZPmU\|l{i[O=|_훝lшj;K|}~ƍy7u?| 4|,JCOvw7O~Dx@O(Jx!|&3Eᡏ,jkB*zCx(knaQI|ׇǬۤs2Em@Ԗ22WsĸF =7E܌Qs\!!1vlO{ l mh1Ha1OlN]~2cqu?~<^W}#[}cK;v,qh7?Zz/է>ncW*^{ZXf\s9pb#1xssyt.ڦ5N:|Kc7Y9xX҄ہuoQqq93g+7Kl-b8>D.uuxXQqO^+_5g{x?C:?z'fK)| g#jkRyI/bs1RgcGW11XZ[v2ʫ}!6h>Ά>>ۥo' EgKXaZy⧍Najyxއ' 9D?#>E{GOO$sψ9ۘʃ'^/rn9&ruÈsѿ#ïG7/}\&OQxZ35,c$hOZ#4?9~OOgNjo񤖓}?jܒ޿.;h}0,Q@|[ jyxuwNx>/ƭqcc~ sV9~94hjNi| ] u%t}pfAťŽ)sZ^zcYE}_\JT}֫Ӵ9ZXs}>;Ƴc?[[: SOdpwlrk[ѣ}=McOqk }=~{64{hcݎ;Ad=K}=7~|Z絛w-H.>^ -?~+=vay7A_-GЮ 3WQguXcv]X=vu(7Ηvsl{u/aę)\{V,_ҺzS$6{@}GqU3RdK.7|c93ta.6Z{v -}s {[\!gfNdW >;}l{n=1ϕ,Fj^5Ǩ؇di16re5Ű<#-3+DYI5nx]-Q@2w<Ϯ%ˆ-gw+Ojk[O!i(S?N W׌7NFBKCH{r_Rg\c/\.œJvSMx~` -"'NSyK/ɏ߫'G˟u:U-;_05d6׊>X" -endstream -endobj -76 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 75 0 R -/Resources 4 0 R -/Annots [ 77 0 R 78 0 R 79 0 R 80 0 R 81 0 R 82 0 R 83 0 R 84 0 R 85 0 R 86 0 R 87 0 R 88 0 R 89 0 R 90 0 R 91 0 R 92 0 R 93 0 R 94 0 R 95 0 R 96 0 R 97 0 R 98 0 R 99 0 R 100 0 R 101 0 R 102 0 R 103 0 R 104 0 R 105 0 R 106 0 R 107 0 R 108 0 R 109 0 R 110 0 R 111 0 R 112 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -77 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-node-automated) ->> -endobj -78 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-node-automated) ->> -endobj -79 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-rbac-automated) ->> -endobj -80 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-rbac-automated) ->> -endobj -81 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-eventratelimit-is-set-automated) ->> -endobj -82 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-eventratelimit-is-set-automated) ->> -endobj -83 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwaysadmit-is-not-set-automated) ->> -endobj -84 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwaysadmit-is-not-set-automated) ->> -endobj -85 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwayspullimages-is-set-manual) ->> -endobj -86 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwayspullimages-is-set-manual) ->> -endobj -87 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-securitycontextdeny-is-set-if-podsecuritypolicy-is-not-used-manual) ->> -endobj -88 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-securitycontextdeny-is-set-if-podsecuritypolicy-is-not-used-manual) ->> -endobj -89 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-serviceaccount-is-set-automated) ->> -endobj -90 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-serviceaccount-is-set-automated) ->> -endobj -91 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-namespacelifecycle-is-set-automated) ->> -endobj -92 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-namespacelifecycle-is-set-automated) ->> -endobj -93 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 473.570079 498.679134 450.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-podsecuritypolicy-is-set-automated) ->> -endobj -94 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 453.170079 491.179134 438.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-podsecuritypolicy-is-set-automated) ->> -endobj -95 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 433.970079 498.679134 410.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-noderestriction-is-set-automated) ->> -endobj -96 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 413.570079 491.179134 398.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-noderestriction-is-set-automated) ->> -endobj -97 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 394.370079 498.679134 370.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-bind-address-argument-is-not-set-automated) ->> -endobj -98 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 373.970079 491.179134 358.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-bind-address-argument-is-not-set-automated) ->> -endobj -99 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 354.770079 498.679134 331.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-port-argument-is-set-to-0-automated) ->> -endobj -100 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 349.370079 491.179134 334.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-port-argument-is-set-to-0-automated) ->> -endobj -101 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 315.170079 498.679134 291.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---secure-port-argument-is-not-set-to-0-automated) ->> -endobj -102 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 309.770079 491.179134 294.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---secure-port-argument-is-not-set-to-0-automated) ->> -endobj -103 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 275.570079 498.679134 252.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated) ->> -endobj -104 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 270.170079 491.179134 255.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated) ->> -endobj -105 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 235.970079 498.679134 212.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-path-argument-is-set-automated) ->> -endobj -106 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 230.570079 491.179134 215.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-path-argument-is-set-automated) ->> -endobj -107 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 196.370079 498.679134 172.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxage-argument-is-set-to-30-or-as-appropriate-automated) ->> -endobj -108 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 175.970079 491.179134 160.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxage-argument-is-set-to-30-or-as-appropriate-automated) ->> -endobj -109 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 156.770079 498.679134 133.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxbackup-argument-is-set-to-10-or-as-appropriate-automated) ->> -endobj -110 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 136.370079 491.179134 121.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxbackup-argument-is-set-to-10-or-as-appropriate-automated) ->> -endobj -111 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 117.170079 498.679134 93.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxsize-argument-is-set-to-100-or-as-appropriate-automated) ->> -endobj -112 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 96.770079 491.179134 81.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxsize-argument-is-set-to-100-or-as-appropriate-automated) ->> -endobj -113 0 obj -<< -/Filter /FlateDecode -/Length 3631 ->> -stream -x\K,HI|qF Ƭ`:%,uKi̠gҧb$~'! )x?}8!8// rwHg43{M4D~r!+.O~vy3#/qDɂ$7pLa[2q)"m8\01 c.[80/"\0"좁 "3`21(2[961ʁY4Pb413|"&&̔3L.,2cHp1D3l(%`bφ 2;l<`FgbXY4` -lg7 g<̔D?>̈$9D PlO &8(g " ,7lcx)R2|,/0C`NC 6Fd&cEfĜ RCH dfd6FddX2(ރC A'>%1,p:c:(LAO9FP'6FdFhJ hJ?(uC#2s:6& )EǤ R/c4G15,"eGgm*I2iY4:s|g&u 3Ewt5U5|9iz IΥ!WT^J#AF Z\PI -Vt{բԺ/K;xikeҐzeaEOfE.ECOv+V-. ;T`ޫ}9!s=CTFn›%^C5D_C&D3BTK=5D_C5D?Q[!w tOUsݲDT3 fh08.ٵX*<}\0r &1c Chma -B& 22GgQgEّ=FCqHL EKlaxȐPg oML !`20e-Exo`%4Ĝ%s ޡ%sDЃ%s!Iɖ%$SDaBKۘ'=z2Mp`Li -`>ϡi q罇, =,(Z?/3۫p}>O`Va=ہ`Vawg;ޙ#5A0zpQ>PeIB#O9kI59/\2m#zg< ?^/]俛F0+2q?45?8guݲ]EN=u|<8EZ]*ȳf}YL>1lT}#_ dƮ}/gB8٭uLYpũcl8ݷXV]vvv6O{6~}Qvk6vm;suq·fc#V|KlJG::>e`xY~5yȱN):Xbۅ~<[A7s-`ˬ:uFZŞ[{f[>Zcmr]Y3)v/]{^[m8mOMkdcY'z0ζ:[#jL~̽67|uW{1kL}k}xQ~t_J7iΑ'*[Reh'2ne'`)"'_q 5Ѫ=7]?x*/)({FaH]?'1{_9_8r!·BF J\!խueSMmaO_JL N[r}fDLa>& -qY!jlgo%KQD%:\'KL07EתeQ"^Nl>R=4-/˩)rRE6` -|MQٮ+!T .W -rZܨY*6T.JwWhf'u -el&s@Ko r*yt+UĠ6rr_:5*F+[)UP3-PHF^*Iӹe\`X.֗L8V%6t؂Tʚ[Xy]#Vr&*4\iArR Uqrwj|;[|,^vW;+X\\?F:ٻVzc=>-;AZŽ~:e|͵h:8O0?'7b E~'CX*_c^2(H]zJ3d/WZl{m tj礙PT9MZ%XY F9LT5d 1CFMJ[D #iװYͺ^(aA7\#P[jo'Mm+Ԗ֩as$f!˕1gc/.ݒC&EI. ۲[ !oWi,SE y6ne;dd -endstream -endobj -114 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 113 0 R -/Resources 4 0 R -/Annots [ 115 0 R 116 0 R 117 0 R 118 0 R 119 0 R 120 0 R 121 0 R 122 0 R 123 0 R 124 0 R 125 0 R 126 0 R 127 0 R 128 0 R 129 0 R 130 0 R 131 0 R 132 0 R 133 0 R 134 0 R 135 0 R 136 0 R 137 0 R 138 0 R 139 0 R 140 0 R 141 0 R 142 0 R 143 0 R 144 0 R 145 0 R 146 0 R 147 0 R 148 0 R 149 0 R 150 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -115 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---request-timeout-argument-is-set-as-appropriate-automated) ->> -endobj -116 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---request-timeout-argument-is-set-as-appropriate-automated) ->> -endobj -117 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-lookup-argument-is-set-to-true-automated) ->> -endobj -118 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-lookup-argument-is-set-to-true-automated) ->> -endobj -119 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -120 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -121 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-certfile-and---etcd-keyfile-arguments-are-set-as-appropriate-automated) ->> -endobj -122 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-certfile-and---etcd-keyfile-arguments-are-set-as-appropriate-automated) ->> -endobj -123 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -124 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -125 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -126 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -127 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-cafile-argument-is-set-as-appropriate-automated) ->> -endobj -128 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-cafile-argument-is-set-as-appropriate-automated) ->> -endobj -129 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---encryption-provider-config-argument-is-set-as-appropriate-automated) ->> -endobj -130 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---encryption-provider-config-argument-is-set-as-appropriate-automated) ->> -endobj -131 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 473.570079 498.679134 450.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-encryption-providers-are-appropriately-configured-automated) ->> -endobj -132 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 453.170079 491.179134 438.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-encryption-providers-are-appropriately-configured-automated) ->> -endobj -133 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 433.970079 498.679134 410.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-only-makes-use-of-strong-cryptographic-ciphers-automated) ->> -endobj -134 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 413.570079 491.179134 398.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-only-makes-use-of-strong-cryptographic-ciphers-automated) ->> -endobj -135 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 394.370079 504.679134 361.670079 ] -/BS << -/W 0 ->> -/Dest (controller-manager) ->> -endobj -136 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 483.326107 386.420079 496.429134 371.420079 ] -/BS << -/W 0 ->> -/Dest (controller-manager) ->> -endobj -137 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 343.670079 498.679134 320.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---terminated-pod-gc-threshold-argument-is-set-as-appropriate-automated) ->> -endobj -138 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 323.270079 491.179134 308.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---terminated-pod-gc-threshold-argument-is-set-as-appropriate-automated) ->> -endobj -139 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 304.070079 498.679134 280.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-1) ->> -endobj -140 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 298.670079 491.179134 283.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-1) ->> -endobj -141 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 264.470079 498.679134 241.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---use-service-account-credentials-argument-is-set-to-true-automated) ->> -endobj -142 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 244.070079 491.179134 229.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---use-service-account-credentials-argument-is-set-to-true-automated) ->> -endobj -143 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 224.870079 498.679134 201.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-private-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -144 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 204.470079 491.179134 189.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-private-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -145 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 185.270079 498.679134 161.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---root-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -146 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 164.870079 491.179134 149.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---root-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -147 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 145.670079 498.679134 122.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) ->> -endobj -148 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 125.270079 491.179134 110.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) ->> -endobj -149 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 106.070079 498.679134 82.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated) ->> -endobj -150 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 85.670079 491.179134 70.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated) ->> -endobj -151 0 obj -<< -/Filter /FlateDecode -/Length 3797 ->> -stream -x]K|T>$A Y$0֝];%U(jz bbv[JUdU}Ň^sSCE0*<\o.?_ -ghүUI#{QdqI+)uQOǰ(_?$/ K&MA+}0UQEFeY+1EZM7g5`m4[l u۞g%lXGNitlq 6`~~ƍVsخm~k\d(~kׅ=vR7bcr?jO>IK;?'t'\cӗӛ'!OB>};[ݣIǓy:3]5&%jAGƍ&BO!dW:e/ - H&8AP F=Fh#@01B$!O'3I؇)RVR"Ǯ2)6Zic)]ySdn*|%m -arxЇ B߇-gHZϝS{s1~.*c~24͇g_~5>|Oዿ_|u iO4?ΏbW^'Cٓ͟R1WMWs' _B#׽\=\y+{:>B}rfoU2V;cbA/*pHӡ/F0 -whA -]EJ1 )OqaM#7o2 .Cv/U01Zζh|GmeYMlft~680,s-2tnqo-ͺ,;x?][~9/l]Ҭ/)r6 E~8VF_ՙ]c( S",z';.sa/qh 6(vKC̒@7<t]-L#g8WlLď@(YV(2ưﾰAm2n:/eyrx͖Q:E(M~SEgd}TiyheoAߧ>]u/RTcRQ"kLW߯^{Fްj|cޔ8J1GC<# -e4o_WXU\7ڶUm9~ge暵md'ZrY._M@WI3x]GO(9BfҢ#Mv;"j8p@\)3s8A.kqGiALu?fQLQ 1&oB^[:/ma11Y~zZE( N1 ۸r.ܗv] HmBO.?=G$'Q&P#>Zofew |6]BWwsK6W$aEsx1훔 OdEgܛbe1(U?rng-nIN6?_0R"}mw ب„_1(jL6םK*13Lp7q;.9d =aaC8G]uA}XbqirӤc -z,,rI0t7[8>?2-G6}i3,+ aq jaad*~L5֦K"k]Ȭ[O]4GQUkuŜhT(q@I .YϋY0D*\]r6 -U*x©bu||T&ġѮ|la#Pb=cCevug?]0tktBo|a4*f\*L򗊛@ -NUz0XV˄PsVDݑEJW5p+QUţMͺ -VSkuick*?50+U)ً1oDc˰I¡Fxq/m` ԏVю FEa.O\ZI~dF4Y6'Itd^|<[]Hf+!> -endobj -153 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 790.370079 504.679134 757.670079 ] -/BS << -/W 0 ->> -/Dest (scheduler) ->> -endobj -154 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.309749 782.420079 496.429134 767.420079 ] -/BS << -/W 0 ->> -/Dest (scheduler) ->> -endobj -155 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 739.670079 498.679134 716.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-2) ->> -endobj -156 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 734.270079 491.179134 719.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-2) ->> -endobj -157 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 700.070079 498.679134 676.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated-1) ->> -endobj -158 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 679.670079 491.179134 664.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated-1) ->> -endobj -159 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 660.470079 504.679134 627.770079 ] -/BS << -/W 0 ->> -/Dest (etcd-node-configuration-files) ->> -endobj -160 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.237972 652.520079 496.429134 637.520079 ] -/BS << -/W 0 ->> -/Dest (etcd-node-configuration-files) ->> -endobj -161 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 609.770079 498.679134 586.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---cert-file-and---key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -162 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 589.370079 491.179134 574.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---cert-file-and---key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -163 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 570.170079 498.679134 546.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -164 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 564.770079 491.179134 549.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -165 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 530.570079 498.679134 507.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -166 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 525.170079 491.179134 510.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -167 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 490.970079 498.679134 467.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-cert-file-and---peer-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -168 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 470.570079 491.179134 455.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-cert-file-and---peer-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -169 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 451.370079 498.679134 427.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -170 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 430.970079 491.179134 415.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -171 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 411.770079 498.679134 388.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -172 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 406.370079 491.179134 391.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -173 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 372.170079 498.679134 348.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-unique-certificate-authority-is-used-for-etcd-automated) ->> -endobj -174 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 351.770079 491.179134 336.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-unique-certificate-authority-is-used-for-etcd-automated) ->> -endobj -175 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 332.570079 504.679134 299.870079 ] -/BS << -/W 0 ->> -/Dest (authentication-and-authorization) ->> -endobj -176 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.986019 324.620079 496.429134 309.620079 ] -/BS << -/W 0 ->> -/Dest (authentication-and-authorization) ->> -endobj -177 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 281.870079 498.679134 258.470079 ] -/BS << -/W 0 ->> -/Dest (client-certificate-authentication-should-not-be-used-for-users-manual) ->> -endobj -178 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 261.470079 491.179134 246.470079 ] -/BS << -/W 0 ->> -/Dest (client-certificate-authentication-should-not-be-used-for-users-manual) ->> -endobj -179 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 242.270079 504.679134 209.570079 ] -/BS << -/W 0 ->> -/Dest (logging) ->> -endobj -180 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.506282 234.320079 496.429134 219.320079 ] -/BS << -/W 0 ->> -/Dest (logging) ->> -endobj -181 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 191.570079 498.679134 168.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-minimal-audit-policy-is-created-automated) ->> -endobj -182 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 186.170079 491.179134 171.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-minimal-audit-policy-is-created-automated) ->> -endobj -183 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 151.970079 498.679134 128.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-audit-policy-covers-key-security-concerns-manual) ->> -endobj -184 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 146.570079 491.179134 131.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-audit-policy-covers-key-security-concerns-manual) ->> -endobj -185 0 obj -<< -/Filter /FlateDecode -/Length 3770 ->> -stream -x\ˮ+6q?^$A AWd#2 gYk%J]яvos)vwflgFl.%lۇ4;k+:I!U}k'Rv&!wIh&{,ѶD¦bkzB{'M7!=ȡy -]FendY)ih g_i5#t"ܘߝ1[3j_Ywgt,,4Jvl.nCv> /o~iŝ6'Jm$Iz6nxK}:'O<"7cٌ< FsK[B* 9NVϥ-oOlWr1r.E?5!=nA.q1ir1ⱳ&`lP1Lrk5 8s$k ͱ:;Lg1IÀ28d!u 8MP0 *a˞ k0Hx7٘! F%~![%~3b8OF1FnDďrP1 ďKl٫ &ncmVL&bdi0q?ޥYgD^08skpf%~|g獊b,ďlRR1 f3%~|Š)짜"'%JJ`˜r^`C@kplUgƬl,ܔ?ǤbI"pƂb1%%ƈ21 iMɪIJyJeRIprqQ- *Ƃ31G%~؂Ob8{c 6ZClJ0qY0OxSTb1*؉d~9F<I$p%0L=g  j?gs0!gcP'8p Bxp6?_̺rD\B\20d揷c^ X5.TNF~ReF.\ JC3~f~ZjX [/McutsMAekH K/6tK-7Hgo@[?ԂCoB&L|Rr8;'Nj,#?3~[?5!ߔ ƍt{BF/Rc{?c21gR|*n(k)b4\0DgS5XCl4ÄHk#8A4 ѪqΒ_` z]~ k6+V`2-K2/ *,VDQ{v9 !<]珃[x{}xko>o17w'<^| 4(:"+ajhEş~*r^XEr{YO_Vq ,/<ͥFZUqdΞz\ԲN[IgXiWm/KsgU>_+ߛ3}gOwʾ;j,n+3A*J]҆ʙiIOjyX}NXebw橺z_Ɏ 1]َrGڳb}{s¬⪭]4՞4\? F&BI|0?!2X$d)7!'YVQ|l.'fLuSP1;NRmgv!7;[4 cC?k&۱b/6LSq@ydNX|ۍ~y׷E찳<1~Y9,Xoϵ_Rի-=ї/,b8^FC a$w^c&B>b]{ϽԥpŖZӃcPlj]g RI"Ci *O?7q/#*L5r DSRo;>5dV){qioP⚭mv9=F+an^g˷/lJd_:L-\[7b9 /˃UFimXq|M{E6vW -P] ]g +ÑF湾 rƗ++\2{/{% -/KN4ąBa64K@J%?IWK\mDeVv]e(hLv1Y4o H?9rPmjo{)m+6፥~ ˶}-"|[ \ԛJ6JBѦ Lcf,J)gii^iFdp-| Gg:%@d&UvjàN$)3|FyڔFlj% lv*?w)ZɣœI-HMpDx;C7ge3 p[N'/DvQs*03 Im4g>;)}_g -endstream -endobj -186 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 185 0 R -/Resources 4 0 R -/Annots [ 187 0 R 188 0 R 189 0 R 190 0 R 191 0 R 192 0 R 193 0 R 194 0 R 195 0 R 196 0 R 197 0 R 198 0 R 199 0 R 200 0 R 201 0 R 202 0 R 203 0 R 204 0 R 205 0 R 206 0 R 207 0 R 208 0 R 209 0 R 210 0 R 211 0 R 212 0 R 213 0 R 214 0 R 215 0 R 216 0 R 217 0 R 218 0 R 219 0 R 220 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -187 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 790.370079 504.679134 757.670079 ] -/BS << -/W 0 ->> -/Dest (worker-node-configuration-files) ->> -endobj -188 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.434505 782.420079 496.429134 767.420079 ] -/BS << -/W 0 ->> -/Dest (worker-node-configuration-files) ->> -endobj -189 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 739.670079 498.679134 716.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -190 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 719.270079 491.179134 704.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -191 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 700.070079 498.679134 676.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-ownership-is-set-to-rootroot-automated) ->> -endobj -192 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 679.670079 491.179134 664.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-ownership-is-set-to-rootroot-automated) ->> -endobj -193 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 660.470079 498.679134 637.070079 ] -/BS << -/W 0 ->> -/Dest (if-proxy-kubeconfig-file-exists-ensure-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -194 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 640.070079 491.179134 625.070079 ] -/BS << -/W 0 ->> -/Dest (if-proxy-kubeconfig-file-exists-ensure-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -195 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 620.870079 498.679134 597.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-proxy-kubeconfig-file-ownership-is-set-to-rootroot-automated) ->> -endobj -196 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 600.470079 491.179134 585.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-proxy-kubeconfig-file-ownership-is-set-to-rootroot-automated) ->> -endobj -197 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 581.270079 498.679134 557.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -198 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 560.870079 491.179134 545.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -199 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 541.670079 498.679134 518.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -200 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 521.270079 491.179134 506.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -201 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 502.070079 498.679134 478.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-certificate-authorities-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -202 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 481.670079 491.179134 466.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-certificate-authorities-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -203 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 462.470079 498.679134 439.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-client-certificate-authorities-file-ownership-is-set-to-rootroot-automated) ->> -endobj -204 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 442.070079 491.179134 427.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-client-certificate-authorities-file-ownership-is-set-to-rootroot-automated) ->> -endobj -205 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 422.870079 498.679134 399.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-has-permissions-set-to-644-or-more-restrictive-automated) ->> -endobj -206 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 402.470079 491.179134 387.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-has-permissions-set-to-644-or-more-restrictive-automated) ->> -endobj -207 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 383.270079 498.679134 359.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-ownership-is-set-to-rootroot-automated) ->> -endobj -208 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 362.870079 491.179134 347.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-ownership-is-set-to-rootroot-automated) ->> -endobj -209 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 343.670079 504.679134 310.970079 ] -/BS << -/W 0 ->> -/Dest (kubelet) ->> -endobj -210 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 484.911067 335.720079 496.429134 320.720079 ] -/BS << -/W 0 ->> -/Dest (kubelet) ->> -endobj -211 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 292.970079 498.679134 269.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-anonymous-auth-argument-is-set-to-false-automated) ->> -endobj -212 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 272.570079 491.179134 257.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-anonymous-auth-argument-is-set-to-false-automated) ->> -endobj -213 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 253.370079 498.679134 229.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated-1) ->> -endobj -214 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 232.970079 491.179134 217.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated-1) ->> -endobj -215 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 213.770079 498.679134 190.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated-1) ->> -endobj -216 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 193.370079 491.179134 178.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated-1) ->> -endobj -217 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 174.170079 498.679134 150.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---read-only-port-argument-is-set-to-0-automated) ->> -endobj -218 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 168.770079 491.179134 153.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---read-only-port-argument-is-set-to-0-automated) ->> -endobj -219 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 134.570079 498.679134 111.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---streaming-connection-idle-timeout-argument-is-not-set-to-0-automated) ->> -endobj -220 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 114.170079 491.179134 99.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---streaming-connection-idle-timeout-argument-is-not-set-to-0-automated) ->> -endobj -221 0 obj -<< -/Filter /FlateDecode -/Length 4007 ->> -stream -x\K$ sE{H⋃6H`9;6Yv`Uسӳg1;U,Jz_8/3)|xdM$? d=ESZtƐ fΟ?JzH&\OLN7Ȣ?peޕ;{c'K&;fI<,L\8f`eQaQAcg$"e 5`H$l&g()EY_.OG؜2h2(gQay6(cܽOlB'A4W Vu1au+Ƈ)C -A5}|4H6YS@o0L!u!2ْ -!``bOEM C -N4fѤa+kI%KDaMR0s,mIL9eBH -lΙ9jyRx9ӧ`}6٬19hI}59\l/dS-xLϙ^I`5}RY*'#Ld4yZΙg'pL*Ι)r%Yf0[Ι!GSs&ZA0> `8g&ZBΙ,Lή -)3nbZKIyF,ZN R4t{ Kj#g,KHښփ"JAt8d#BV@tqvB3vQJw.8yUn^xdKww(C7L K(,5e;q\f)\vpà{0*CckЅK $;U^e_~=Dh>q(J+J$!GB4x|BƳ}}g -y(~z{}#D*t-ȯngo\E?ѲG9oĘmONyBf -O >;Vt.[dCٺfEP\ȊeöNY9YәJ`CBtF_ 3fKmxCe/aΙ0.i<жҧ< ږؔ'Y)j:`ؙ)RM̱gchK8α^s,1(:G(3sǧ 9v,i:cH9vbDT|5rr€_Tbrh(F/$ -K}Y@8Z -e:{SyCz]pp8cCYAʊG>B}*DWF&#z#D!Bt^#D!ѻ -գZٲQǚ.;o)V0iΘ".[yG Ey堶1(f&mR,^ u혩܍uroO -J>϶v3x~<}wぼpW2f_ߜ~>UD Q4+3D;DD,@ς;Dp^zB}7+,7܌sgXr!__F8(;EgиWD|wv)"wp;z&s n^>xk1@hy»}克몌+&[n$k)o9똮׈p-A:+}sC*^+nEB/ڟeu{ѯSS][ðŖU _֪F^bu~]mX o, Kw*lmJXȅՏU-ZL,b*>q83\=}'tPm}E?:_ipiY}WRv{79 OЃ+yXq+OprcM7ο{?0vuuLJ_͍֔E;_Vdy{umO/^r+a8m|/}q^{eiuRxǭ-_6ֵEgߐ5;߸C|D#6y3ᙘ~5 Ư[5M.N|§ϙtI훆[{[.ޥ:Ɯ1nE+0?5s`>zvc% []LPbI+HXCUz5iFbNuu*Ju M5u -ƊYn5Ȟyf^muoZ[^ fH0/ȃ߭@8-m^g-Jdk6 -c7>DArE[mm_svV_bޭksC's[+Gۉ+ɣ7Adn0+o˴6TJ.k.6R6pm(DԾ-e@C2E}*Aޭ=ba:+oYo{zC[ࣉP?@yq02O7ͫpSn,vז5Y.W[̝'U螩ʵW -c -E0vP}=? xJDCY-gˇ<.AdB?S4]Hps-_;W<5C ogt}DG1іİg2OLr!C*mhq /|\sqC'=fw -ep{r}yJf(_BWBәC&y+'Z!n9&s~;LK9(Ԉ[Ӕ -ӠYlyTTj8MHQ ۺ.;5h +5QˍoB|7HΕF,?T^^;-6TNOYPhX+#tr*ygG~:QpIvr_5f*F kN-g9(7`]@ !%6;ym$I=nGc>+ť̈́$- - zMzX]N.)٧JIM 7]iEzRUv&,8s$ǎ+~7epK.Ag!Lbyѧܢg's?A6q/O4 G=9^w|ÿ9<g uE3o$Na#"K7y@kH UIaCA{2/+B^lƄ}=mp|iϢK>+cJ!NTC!n?J(|%NDQNc]72 -N4FWL~qxݍ{U9(Ԟ;IR -'9/a}|Pˋ1J \H4UBVBDlc)f,ˈJ4ITIv6j;1:;8{-& [w*Nh{ٸf۳E¨LhF;志ijkĥa']Ϲ;;Dg_>eM+6~mHI /ڽ@'o_]ne;ҧ6ҲCOcY*RN,6\??/ -endstream -endobj -222 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 221 0 R -/Resources 4 0 R -/Annots [ 223 0 R 224 0 R 225 0 R 226 0 R 227 0 R 228 0 R 229 0 R 230 0 R 231 0 R 232 0 R 233 0 R 234 0 R 235 0 R 236 0 R 237 0 R 238 0 R 239 0 R 240 0 R 241 0 R 242 0 R 243 0 R 244 0 R 245 0 R 246 0 R 247 0 R 248 0 R 249 0 R 250 0 R 251 0 R 252 0 R 253 0 R 254 0 R 255 0 R 256 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -223 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---protect-kernel-defaults-argument-is-set-to-true-automated) ->> -endobj -224 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---protect-kernel-defaults-argument-is-set-to-true-automated) ->> -endobj -225 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---make-iptables-util-chains-argument-is-set-to-true-automated) ->> -endobj -226 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---make-iptables-util-chains-argument-is-set-to-true-automated) ->> -endobj -227 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---hostname-override-argument-is-not-set-manual) ->> -endobj -228 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 705.770079 491.179134 690.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---hostname-override-argument-is-not-set-manual) ->> -endobj -229 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---event-qps-argument-is-set-to-0-or-a-level-which-ensures-appropriate-event-capture-automated) ->> -endobj -230 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---event-qps-argument-is-set-to-0-or-a-level-which-ensures-appropriate-event-capture-automated) ->> -endobj -231 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated-1) ->> -endobj -232 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated-1) ->> -endobj -233 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---rotate-certificates-argument-is-not-set-to-false-automated) ->> -endobj -234 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---rotate-certificates-argument-is-not-set-to-false-automated) ->> -endobj -235 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (verify-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) ->> -endobj -236 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (verify-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) ->> -endobj -237 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-only-makes-use-of-strong-cryptographic-ciphers-automated) ->> -endobj -238 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-only-makes-use-of-strong-cryptographic-ciphers-automated) ->> -endobj -239 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 473.570079 504.679134 440.870079 ] -/BS << -/W 0 ->> -/Dest (rbac-and-service-accounts) ->> -endobj -240 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.154476 465.620079 496.429134 450.620079 ] -/BS << -/W 0 ->> -/Dest (rbac-and-service-accounts) ->> -endobj -241 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 422.870079 498.679134 399.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cluster-admin-role-is-only-used-where-required-manual) ->> -endobj -242 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 402.470079 491.179134 387.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cluster-admin-role-is-only-used-where-required-manual) ->> -endobj -243 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 383.270079 498.679134 359.870079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-secrets-manual) ->> -endobj -244 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 377.870079 491.179134 362.870079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-secrets-manual) ->> -endobj -245 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 343.670079 498.679134 320.270079 ] -/BS << -/W 0 ->> -/Dest (minimize-wildcard-use-in-roles-and-clusterroles-manual) ->> -endobj -246 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 338.270079 491.179134 323.270079 ] -/BS << -/W 0 ->> -/Dest (minimize-wildcard-use-in-roles-and-clusterroles-manual) ->> -endobj -247 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 304.070079 498.679134 280.670079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-create-pods-manual) ->> -endobj -248 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 298.670079 491.179134 283.670079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-create-pods-manual) ->> -endobj -249 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 264.470079 498.679134 241.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-default-service-accounts-are-not-actively-used.-automated) ->> -endobj -250 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 244.070079 491.179134 229.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-default-service-accounts-are-not-actively-used.-automated) ->> -endobj -251 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 224.870079 498.679134 201.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-service-account-tokens-are-only-mounted-where-necessary-manual) ->> -endobj -252 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 204.470079 491.179134 189.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-service-account-tokens-are-only-mounted-where-necessary-manual) ->> -endobj -253 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 185.270079 504.679134 152.570079 ] -/BS << -/W 0 ->> -/Dest (pod-security-policies) ->> -endobj -254 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.622493 177.320079 496.429134 162.320079 ] -/BS << -/W 0 ->> -/Dest (pod-security-policies) ->> -endobj -255 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 134.570079 498.679134 111.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-privileged-containers-manual) ->> -endobj -256 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 129.170079 491.179134 114.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-privileged-containers-manual) ->> -endobj -257 0 obj -<< -/Filter /FlateDecode -/Length 3771 ->> -stream -x]K$ E{H⋃6H`9vvm9҃Vzfv,cv,'Ɯ5Bϗ' Ec0Ǒ2@1N5(֧݄R2̻FL&*ni$X;Q lxOdUlى=`.:= `BgXtNBp -q"E=9yPQ'2xoS -fƩ1ai t}q9q _채t4bi(}#8.Co+sԔth.GBqWy+Zb6 x*E;d0tpJ(<5wx\ lx@*~ȃ<: p1x0;<^h[,7wBw?;/ -&!z{^3X,z==D!BtO=D!zMt]醠ζumᢝ-q̷<tKl=)~[,ޓƒ-E-ӝ@> Z0(;a00vEK'-]Tw& 4\$VCO] ] ^~/ZiH. <5ChP'ۆ;\V橱{%!wC&*Uy6< yW'3`zrMcv<D`KSc`ENF{CbBTZ_=D!)BtO=D!zMt寠Z'xۺRv(-1way.ّ *X^Ͼ?ҵk:iJn||ק"v<;m6 ϯߟӏrG^;k ^7YSU8VrnP_? -9qޠ"@7bx 70.?f|umEݤ߾(ۂ*|7غ*D5/PRx*6J^N\}U#"ݔz>@2G4)eƋf'r/~ y>~ΑmE/dZamk1k\li^nhmc-r͞r\dpmc7Y#Wӣ6#f`bk>5-\G=Br fc}ʓzų=M}鶾)w`6ն#NyA=6|fU$E& CFewKȦ9-G,/tޒ_lYS|~[YǢM8k)Wh\|Wl&1s4ǣ7'E'yc)ggo|]&.:̘Su/ĔIAűv:ntPm;Cj4T*ki8#:nTIlVŋڒ}x{kd93am r#;hIK$!%Pש^ufdk?|MuYrc uAgJd[h#꺹M[ߴQ[&~٭D4钒D-7N:6H݌N,(ljRUGu2xD`y]"r(Ryxe<*Hhx5u"r;kd(G]-Ȟ(1AHe[DR?|/G LtvfC<"o`1,ޮPԲZ[6"H !TK()$*nM 9i xH!ki3ll|W|8Q"̖Q,CP~[is޹ty*UzTttnq/%ޟLL_#YmG=*C8P׶~7^toFR8&]O2/W:s ާ[yVIl>srf[(e[CX-@P`XdʹftYx9ZE(A.YaT(JVP/ -Rɬ ֠<4m*r5L*ڥx҆ lQF9M%*]=֡e_E(M&,Ο" D6ʧBaluf)T'QRa.q"ԶϰYt^4b4]h30b޳ɮD@BkjDkZ˩Okͱ˟(> -endobj -259 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-process-id-namespace-automated) ->> -endobj -260 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-process-id-namespace-automated) ->> -endobj -261 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-ipc-namespace-automated) ->> -endobj -262 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-ipc-namespace-automated) ->> -endobj -263 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-network-namespace-automated) ->> -endobj -264 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-network-namespace-automated) ->> -endobj -265 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-allowprivilegeescalation-automated) ->> -endobj -266 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-allowprivilegeescalation-automated) ->> -endobj -267 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-root-containers-manual) ->> -endobj -268 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 626.570079 491.179134 611.570079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-root-containers-manual) ->> -endobj -269 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-the-net_raw-capability-manual) ->> -endobj -270 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-the-net_raw-capability-manual) ->> -endobj -271 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-added-capabilities-manual) ->> -endobj -272 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-added-capabilities-manual) ->> -endobj -273 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-capabilities-assigned-manual) ->> -endobj -274 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-capabilities-assigned-manual) ->> -endobj -275 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 473.570079 504.679134 440.870079 ] -/BS << -/W 0 ->> -/Dest (network-policies-and-cni) ->> -endobj -276 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.070980 465.620079 496.429134 450.620079 ] -/BS << -/W 0 ->> -/Dest (network-policies-and-cni) ->> -endobj -277 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 422.870079 498.679134 399.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cni-in-use-supports-network-policies-manual) ->> -endobj -278 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 417.470079 491.179134 402.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cni-in-use-supports-network-policies-manual) ->> -endobj -279 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 383.270079 498.679134 359.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-all-namespaces-have-network-policies-defined-automated) ->> -endobj -280 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 362.870079 491.179134 347.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-all-namespaces-have-network-policies-defined-automated) ->> -endobj -281 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 343.670079 504.679134 310.970079 ] -/BS << -/W 0 ->> -/Dest (secrets-management) ->> -endobj -282 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.118587 335.720079 496.429134 320.720079 ] -/BS << -/W 0 ->> -/Dest (secrets-management) ->> -endobj -283 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 292.970079 498.679134 269.570079 ] -/BS << -/W 0 ->> -/Dest (prefer-using-secrets-as-files-over-secrets-as-environment-variables-manual) ->> -endobj -284 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 272.570079 491.179134 257.570079 ] -/BS << -/W 0 ->> -/Dest (prefer-using-secrets-as-files-over-secrets-as-environment-variables-manual) ->> -endobj -285 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 253.370079 498.679134 229.970079 ] -/BS << -/W 0 ->> -/Dest (consider-external-secret-storage-manual) ->> -endobj -286 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 247.970079 491.179134 232.970079 ] -/BS << -/W 0 ->> -/Dest (consider-external-secret-storage-manual) ->> -endobj -287 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 213.770079 504.679134 181.070079 ] -/BS << -/W 0 ->> -/Dest (extensible-admission-control) ->> -endobj -288 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.131038 205.820079 496.429134 190.820079 ] -/BS << -/W 0 ->> -/Dest (extensible-admission-control) ->> -endobj -289 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 163.070079 498.679134 139.670079 ] -/BS << -/W 0 ->> -/Dest (configure-image-provenance-using-imagepolicywebhook-admission-controller-manual) ->> -endobj -290 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 142.670079 491.179134 127.670079 ] -/BS << -/W 0 ->> -/Dest (configure-image-provenance-using-imagepolicywebhook-admission-controller-manual) ->> -endobj -291 0 obj -<< -/Filter /FlateDecode -/Length 2237 ->> -stream -xZK7ׯs(" % d r =_J%Rj26]")D =K~^M'kRQlcBSls&,wXJL]Vpr11 =%!@M0qJ5{0~eR0dp0VxLD0M^«U<)pE7hҼȲC #y6ޚ?+X.~n̏7?pz1ǭ_*Dn,]F:BX\3m ;g-17V;Nқi}/OXytܬex|IȗS8ۭJӗt|Iǿ}:>]HaGNǁj'!3Og48&x MB> L6o3}R6#tB>`9ӧXwhٹbo ez݉>h H'4M6} |FROhLLG'1 - )C>Ù>!\'1F.MMIwbz_tIwbrԤ;1rN;\NӒL݉ys|/BG+P6D3mb]]&A}ˇ bstʝ'̅UM_|w[ZWւp"" -Iк TH_,2 -Z+➯kרLJuxCEߔto>ױ_wݬzPyOxL&`i߾+yU$kѸ[W%;t|Su!:m m\yv{֯eG Yt}sj Vm^veׯFlqr&Rk|o yءq1M׹ζn[j ܛtE5ʫ&5W#߫W9̋}.[ϩMݵMW$n9Nq}s_vZ\_^H|ueJnx.joG),Iy(ǫ\>f6xKϏF-s|}v]`xkgYf!;)~ڝ 6Nř:7QoM-(M^[B8䈥tuK.qlOk0e fiCwͣ2[}ʰI+Uy~nns2hß2eey]îy?\ ӁR3J-n@{@gڟI0ߘ~#~/Tgc:~9(ߔՠӯ1}- y0`:a:^Vxy`B \tO[0'?b j@a˼&'l\EQEkpL - {*q,L(g -tϴ;e"![`N)U L)^-LyFf$/te:܂x* US [~2Buƚ:Je⢆`?nX=Y eug_è6pi)g;e)(5ô"Z+O{W h)HRuAUnlkjU&Sx*^-RR<0H \KGj-+A$/x$U)YXA8Jh8!zYyk~f!^F)p(FEa^* JǑdG;2>m]RRs;|G4ߓWN>VJmz'Ct»paPFU0A8dGTڏvv o5 tjU 'reEid>7c^GbPuC<޹%ϊ%*G5) 24ۨYR Wv@u;?Y͚ -EAMaA -}dw#g@E zѨ,RQ׆q;=u;,$='MHZ@ǨB Ba1XاYڊ󡕒][:hJVI -:XK,قA[ټj~(GgjǴ1sx~D,W6jɡKmwrTCh!tjYݕ<{/O$rڝM@vC (_(VGӊ=\ p׮?q""zT %2%ydO~r0O% -endstream -endobj -292 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 291 0 R -/Resources 4 0 R -/Annots [ 293 0 R 294 0 R 295 0 R 296 0 R 297 0 R 298 0 R 299 0 R 300 0 R 301 0 R 302 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -293 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 790.370079 504.679134 757.670079 ] -/BS << -/W 0 ->> -/Dest (general-policies) ->> -endobj -294 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.986019 782.420079 496.429134 767.420079 ] -/BS << -/W 0 ->> -/Dest (general-policies) ->> -endobj -295 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 739.670079 498.679134 716.270079 ] -/BS << -/W 0 ->> -/Dest (create-administrative-boundaries-between-resources-using-namespaces-manual) ->> -endobj -296 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 719.270079 491.179134 704.270079 ] -/BS << -/W 0 ->> -/Dest (create-administrative-boundaries-between-resources-using-namespaces-manual) ->> -endobj -297 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 700.070079 498.679134 676.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-seccomp-profile-is-set-to-dockerdefault-in-your-pod-definitions-manual) ->> -endobj -298 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 679.670079 491.179134 664.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-seccomp-profile-is-set-to-dockerdefault-in-your-pod-definitions-manual) ->> -endobj -299 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 660.470079 498.679134 637.070079 ] -/BS << -/W 0 ->> -/Dest (apply-security-context-to-your-pods-and-containers-manual) ->> -endobj -300 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 655.070079 491.179134 640.070079 ] -/BS << -/W 0 ->> -/Dest (apply-security-context-to-your-pods-and-containers-manual) ->> -endobj -301 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 620.870079 498.679134 597.470079 ] -/BS << -/W 0 ->> -/Dest (the-default-namespace-should-not-be-used-automated) ->> -endobj -302 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 615.470079 491.179134 600.470079 ] -/BS << -/W 0 ->> -/Dest (the-default-namespace-should-not-be-used-automated) ->> -endobj -303 0 obj -<< -/Filter /FlateDecode -/Length 4785 ->> -stream -x\ێq}g؀,y 5=̖%=V~$̌$YU]cbD2<dQ_~>iR1始W7foU+'sHlb&mvx)`rv)F +%,sf,3nϊP j8ca%a]vPD j#ai=Qr~ -pz`<ɔ0SN{xy -!x4ys񠋳)2^.6XEyŤh/BdKٕ(4e; J1yF'ki=y䦥<()D3%()x Yx ocJd2CAfTpaqr8&% -'e0`\ȑU<X] .3͎a5X ] ,![XSY3,[t`X`PS1,@\cX`H̰s-abGk}0 ,`׺XuZ1,p]kq&A$0du pj8.aXN25I9k"J s2,p]a]aXƙ2eXz l2hKx(dN&r`X:!|'q2oIx. -eXİ?-*5wɊao Fm -KyyR9% X2 P'$'$fX0P2,]Pt0,@_-hV'eUfY )Ű q 0/z31,Va%نތ .- -A4M[`֛@' dǰ P֛a 7-T֛nw}21pi`X7ٲ3SYq&cn(`/U{ -[Htjbe5@YS+m'E53bdƴpۚÖy0<60XׯBYp H>&.`݄h1ꓞMBx vZ8\g=ڇ} ;9[0">.Z}4j -YFroHv rqaeo,]jl-F}>Tjcf~ŽA>. KŨ'ޥw9Oa;&,I.9o F.E~VƁ=\>v/c2^tjkCbz. E^B2^xHDžxqנ:=\Yz~Vwd$]ƅ׻ "?A/};pagXc#xoхSWT jorQ΃uȪ@[Džm_Nh{)A?븰Z-D|Z=D+Y-{Mע7h;!z[~:+Ġ1nM+h&w?sșENלu-c嵋>y}\@X 3l3J#9'}DHW֋ZdW?0B5jl9O20)Eا=H2:#IE&Yrs.^\#Yg8;crNwltss6R'Og [i"c챚(8d9^p?i8Uo1/ _no59O[k®UX|h·׬WqU՞ٕ_Qe5V$|wN*iYQ~3m-WζYnrh歱jocnR͗^q#u(~ -oM jlgɤ8v근Wۮ8~ ;.[m:l?m0} Azzp=N}?qO弢S}l￧{*=øj P|E7wAhr'VjTz>"q7kFθ8˵#r|1XLGYvb9.Y)7{ZݶX][ k0x&ǥ6\gm+I5ͣ2{=Ŷ8e?'5<;>ΚCz(iJvSRI9B9فƉIúmWy{ubӛkmw.esjnnw=CEvgʝ9Ƕ VױvKwL&:0轙/c~~PPn ;+Φ )LAず~]Py(l3f64 AҟK(Ĝ=\7h:U.s"W!DBc~>F_g5/~=9rmo=MتЉu~ 56\COMP]Ƕ*?8m¸mVMoׯF/lm;;T{[^NO";l7רϟ -}*N=UWmqmMlE7oDEuz~%Bզ3%.Z^AuMώ׃37F/S}<] ˛:~_/0j_fr2/qyGM;B\?&鶧TiFH#F֔}=|ݩ:_^.L83=X&dףT b.xD'*qN6IB'6եkveNWUT.JBܨlq-Nt'UE;ELm5\8B]UomTJOu &b([?P"Pc#.)#;V(_SOI|Ԙ05+f@oԂ<ZJW~27yt:y@ -w[Jmt@.zxdݲ U4DU:ٷT~]Oߦ*^,hа]c.i6"+66%O"lTvb(tr\gkC.O2Vqo\2g7MMv]OuyqYQ -Lց,+Yygz\^Zmq;Y>lhu׮:ב!n\I݇lZmg bkd^M/ˡ2qjU#aDO㾪 (.ͰBmǩ.{cN&ˊg[ӧFo-p sTPS?mE] hҚXu -i-ʼnz)S"=eTJ؍-rkkݒm uld" nTGJ_ۍ׮*p];SO¿F՟ygD-j5v~yJ!C\yetIl<}~+!VE]^Ux#gQI9e|'|~2D0by-Mo*ok`clad=T -endstream -endobj -304 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 303 0 R -/Resources 4 0 R -/Annots [ 305 0 R 306 0 R 307 0 R 308 0 R 309 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -305 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 740.570079 409.271317 725.570079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://releases.rancher.com/documents/security/2.6/Rancher_v2-6_CIS_v1-6_Benchmark_Assessment.pdf) ->> ->> -endobj -306 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 311.068925 661.574079 462.272294 646.574079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke-1.6-hardening-2.6/) ->> ->> -endobj -307 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 646.574079 183.998124 631.574079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke-1.6-hardening-2.6/) ->> ->> -endobj -308 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 351.653153 216.824079 461.230790 201.824079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://www.cisecurity.org/benchmark/kubernetes/) ->> ->> -endobj -309 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 201.824079 165.615800 186.824079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://www.cisecurity.org/benchmark/kubernetes/) ->> ->> -endobj -310 0 obj -<< -/Filter /FlateDecode -/Length 3495 ->> -stream -x[K$ ˒H@8 b">9lu*I.Cf03]JHjӀ_˻w%y|?%]Rh[!PqX_wzO.9ѵcHן+ V2X)Rb+-f F**[M bp`UA\Y bbAR1XC7y3S4x! g˵f -xDGrᐂk.眪cȒ/AŃ,LX Y(7y%B@4W! <K2y'*x!$r1xdɃ,|xY8jDk&O%caY`| b,d ANp€XXqj@q)d@lqn, Yg (@FZX1[XGqoV]@HH`2QXX!1 rlaA -Bƍ]ȹYXHTdaA>x-,H@b$.da &9j wKda+G -GjaA"7 2p'" 2p3YF P׀5bŪHa>}idதM rB@@*8ZX+VJ 7J>ŃY&pa PXFZXP"d-,(dkշ@0dAhalaAIjrtM^/ JaT,,@/*r^` J, \-^,(-,@ ^YP ZXPcE%j^jaATaNHi `Gda4hsLdݬ -Y7,4YPYX|vR&[X{ Z7#[X~ZXȣDgm,f1dI(QLdAԌ&:Y Ybc ZoV PfDEo T7y\M d񀻨L@=7g6JYMȭ摁"[|G2 &:˚SU07 <0a;}GTP3kM6=FO ~$<|OwX7`DNb?^2"垨y]Y]SH:Պ1Zɧ7EQtQ0s5U^:9ՊJSooawǙ&4ݺ @)+u=bҖ~)wZ {p GW'\=|JL=Bx*\+'\!]5=+ WP{ҔC7&vu"K[,#>뷗ϾoW~ ;TS/EQ$v\g\c,>&＝x~;s2"sۚc"4e6x;]_zBMST8UՒanD&ږ ܶ!#)yDSde.{u[R}\se[ƛ=sjGv9]Gj-dzsk s׻ˬ6trgj?څ|N~>>sI[&c]z>m?`3RVJki} =Uk(-jZ{ϯ^O,=eW~͈X.d's2혦)y`t3V ){~xI#1[[~;e8  h/Xdc -T\(9`U򿈏7U[Y:;3)QR+Bj6vi4|+lt-[$,iʚ:O;?"EsM+;*1c\ {ڈea\;;KmG^.<#%E%&=/cM\]5TU0z0;%@/3 Auߊ9Õ ;kx 3xx,sq5hK(؍ܟmr~ ~-lqgg Y,0lx".g$.%ctZXp=M$5$WeQKBh<TIOGj-"9G%izÖ5V+2}V+ToНT2E/m' 5H&Y lgb&!/Orx /9 b9(wOsE;5Ly>*[Ol|OׯcE~f". -`GNtwdVƽ]~496|u2]u/ -?QYg2y'Y^F6Y"Ʀ 3Ǩ~&Ĵtqn 4!8 _kK[|p˺xRUM+R:ՍГR-ؖd1!"S"?kS.T!xҬz./ !Gׯ.r scBgS_9tKCs.RGYJ >\hUԺn$(aё(&\mXLym︚Z*XԟTbVɧ2xZY%eί-'H|\{d۫/AL-F~}L֨OFB]o Qs(9CX-\Qd`Dw<[G0 5W=-}|u~lB"I[((O V -endstream -endobj -311 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 310 0 R -/Resources 4 0 R -/Annots [ 312 0 R 313 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -312 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 443.985184 754.370079 487.998612 739.370079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://kubernetes.io/docs/tasks/tools/) ->> ->> -endobj -313 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 297.976884 739.370079 309.064286 724.370079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://stedolan.github.io/jq/) ->> ->> -endobj -314 0 obj -<< -/Filter /FlateDecode -/Length 3612 ->> -stream -x\M$ s%  F,Cúk# !?%Uw<GDQ#USU*Jɻ<[Zl)<B5 @ŕb u?='k-ǐο+ Q2D)Rbʆ()fF*(*P[MjpUA\E jAR1DC7eP3S4d! gK˵f -dDKFrᐂ%k.眪%c蒚,A%.LX ](7e%B@4CV 2K2e'*d!$S"b"t>5S]h0~,x"QՈ(M%K%¦ `-- -@9%b)[db%Ǖ6ǥE%ǹbYIbɱ) -hkZd]ЯV{\{3#tNJ EȘᰌNyy),Ͼ\]rsfG.,ZUO|Ǚ+E>V[F˒x>ȄnHa“F ܣuAfeӒ"e - -]u[|u_ ̷<`8uL&o7mGaȊ'l7<kIe TiPqn ,/;+Bcf&!aGkV8a2)đ4)RDNqlSzazџRT!4e<Ӭc,Ttm}U9tP@tr#YzN H"g,-xs}Tu6HzPfО(]=S^OfYf\M+QSLgmWe1UɇoxZQ%eϖْ:vcl{VHC'Sb|,j+#W - Qs(iyK9CX^SK%>둰| O[+.P)=w|#,/|[X."[Ey#I[TPG\>Y~. -endstream -endobj -315 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 314 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -316 0 obj -<< -/Filter /FlateDecode -/Length 3668 ->> -stream -x\MϯEV 0| Q#F M6U9i~twZfX&WEv3E+$˻ ¢9=IvT -8\c|{\/N^՚ުJ3ECU"φ*FsP%0Z-`,A RKT!!CU%{>*`R1*O`|t FO.xJ e|٥,>zKW]J)K'+yK%zt"\K‰K(-]TCWULP"o*XQ ],dwɦ+ - (VS,)X:ODΥ5fbo" &br(+)/YrvRX$ -;)R,:ə-5:I5[< "&`,&`,kꀅX\XPf` 0V-0Vz |+ L\X\\R AXrLdqwYjqA"P ,"j w=#R[:,.] H,.@|s຦:X\`q&1u cGC-.H]jqARd wI:`,.@^: -` -K%t]\-.H] P,.@,8X\s U)KhqA&"(d\9 `qAdzdX.@`2W9&`UK+tm -t>[\8boqR`[\w.Y\y W`Rȕy`Amq2]輷`A6hqA D Bc/ S[:!g $X&i)M&,.f;Z\6:`(tY,.(X Td|TJNd @Y\P}~3X,T&73mlqA`HQL iƺ'a vt XB jJ, ~y$Ptn`&KEf,.@Mdޞ@1#?Ew<1 PoDl5 ܋h3<4L,K2O Vd8z4Q%CF,YY,}sj|GO?|{?/,I7ȸ+|;L$A"\ r =hq=tSܿ-d V22􋭂\q2~5{u\6y Y[^;}ͷߢW7DRLA?4$ -deļ~s?zGFzG7\Hk=^ߗ.]v`i}Ѻwⷬ|FZ_^_E'Wp#ouv0tWoX7t\am;ˬi#V쭿FGF|">:PekGg~w:zs][}v4[,}oftNcm_qI Yӯ#NmlgY)w36^Iw}rd9-![lnIl[^?olixB3ceF{,{;w{"y4hfY ?E8mV56$QDt'Gcۿ#sF=r"q-?sz/f0m{yٟ}TD -z'GcۿHEF[̑"Q"#oGe(S:9۵ˮum?m=1g\-W;?T[ouw2+ Yz1{qz'Ǔcۍkku, ?Ly4q̃,n^>_S;Aۖckc洴تK0n+.ƍ+3XqM)hu4]w٢Eh1vo^-w$ߑ(T>x4Hi<.z}<u\>NA.R-$;z=ǎ7%I|9(TNϑî$3dreQ.- ]BDe@oZE}|)\܇Qnag$,7;Fw),o7}@l{Kv!O~T{zRz6Җc;w-qrDCQ_BJ5:=*)H`>R5 hڮYZ9yǫ Bάٛ6Le*^-;ehz-˚l231)-_|JY;'qRg!ߦ/;\k|k:O^߃ -k˄Z_^KE\B+ I_KC,2 -ׯ.Hh~$+R42}\PU偹kdžW&Uk)u(15e;>(L04u7Awӥ!gi[ݐOx9[KoMPԚj e<][>!]NӬcWai$^m d[[}rUƥY~@Υސ]@]i[n[\S&SQ;\on24Sai6>Ԫ_"v2Kw)}0}F'6xkY:e/yԝs>;2+bdIk$c+X)٧s, q|/H'w!N;ogq3-;|^&{~i qFgp) EVkg'}s}̊ӏ%A܉47g]_y5l:ns$W&fh}ucCZ4A}8l8CwyLGxY'2OEnC77T(A |DIBFQ::I7y*he.Liydٹ&[F1UA -sanXi1@?zy=yWȩvjYNxb{m'9ciB6G'iܩ4٦(:]@FM[ SZ/kfYF\L+S 鏳<+݈qt׳% P9Ѩsb|uʨMv[}h{!H)1k|)ƪ~_{M3^T !og)QG_s񄤝=a:0SGlPԇSSٗU2q1Nz@ԋYGfXޢg_iZd^ -endstream -endobj -317 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 316 0 R -/Resources 4 0 R -/Annots [ 318 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -318 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 205.473057 101.433071 186.723057 ] -/BS << -/W 0 ->> -/Dest (cb1-1) ->> -endobj -319 0 obj -<< -/Filter /FlateDecode -/Length 3955 ->> -stream -x\K$ ˔DÇ1bdm`!?UzUwwl`H=(Hƞ ?[ٚK|xD&¿bwQ_7%N&s8(L*x~:Ύ˵cΔ 矿{rJVWX!\ -+Z% FHJK bsYae9Yde1l IaY<B)<Lңs\\Qy <6XWL1dǐ%/@`IA9iY| kYS^, ExJfVy<)y {x֚*MI9)Y'9;)79CGNئԛIÂB4Y8xDQo:ְ~)fְxBOԛI% EQyISQz"dq5,(1J5,@zz$Lqp7 "3&2['oHtf3' {zf@_C2GaLKӧ*bfN`d3Ͷ󱟿?}{ǏIY0~ϱb_7&m'H$GHe -iMD(F-E"E2SWƻyQ*X앏od:B݋/ {_wyuޫ;R'9=ռTEY;$2mz] -ڼ}^y;G͛G} -=N|-qeNmsWC^~CC&6zl4eч־}\ۖ趍J}ijǩzoǐ'4ioȢ.nu۸GE&|X -ƭPFGN+Bɋ_;x'Y7ՌKÐ-;Ug_wg[L'r)I6h\i~z[+K@8~luFR%|FN>cV&Xv$e!vˇ9ֽ-xSZgI>+zhKۛ4cEW -z`MZlxu:v.}5;xWO1~2=vyԔ/N~ur [N_,k~QRBɎ,zfzg&mEΆj7eu?ɭ?LiMS{I{jSŕP %Ԕ5)/ -D`~ 0LW rwx' {g9d%l8pˆ -f:_ƒu6Ad!ͣ5oYӰDTBjM 6庖%)%d&iIvp,!CHͽ}21y,1caZTi{GQrY+%\G1U_z\$.^KT w+]Q8<'{uDZukQG/u)_ע2(7܋[ɻA{]88޻0}vzǗiN{kodۋkmkoZ=.5G-}>,m*퐿}v|:(6jK^qK?Z?6,۔9ٕͼ~ p}rv;|0%$y:2!~7vyF6[*?xرD=:I79<7,&/y^=W wU}>;XLIxsսnScPe [:Xs r]13x<ƿ} ᰍ?b}LWU(fczl@g۷VE3=?V`墵n()^Dxt8Y!3JWc!qW 8rpG~.HлCLn+DHՓ,/fU8pv|l=-p$2$;Xyib.N}U]ui[I>Tyյh"T[ O -rRS욼s7$Jo.']-JU]KeC -%y,c)/v)I~:+P#/ri/rW\o0?zn -endstream -endobj -320 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 319 0 R -/Resources 4 0 R -/Annots [ 321 0 R 322 0 R 323 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -321 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 728.673057 101.433071 709.923057 ] -/BS << -/W 0 ->> -/Dest (cb2-1) ->> -endobj -322 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 521.926036 101.433071 503.176036 ] -/BS << -/W 0 ->> -/Dest (cb3-1) ->> -endobj -323 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 136.679014 101.433071 117.929014 ] -/BS << -/W 0 ->> -/Dest (cb6-1) ->> -endobj -324 0 obj -<< -/Filter /FlateDecode -/Length 3542 ->> -stream -x]o ϯ82 9_@)Z h/^(vB./|.%Yu-X:Kp9ծǷ"ޕRs\Ks<{좯;pvƐoù鯿:s{?Wk ->z*aK U<]!&C%j`F0Cj -fHP=UfR _c6T`DCKpztTj.Cst.e[RJX:-tD/Blld`K(-]-ީDW1uyKWZDL]J.G]ba&K罋M6uXQ ]-b5u%2KǰEeȹc]L-]-!d1uo $B9Y -r%!g'5PIbQ $g0jtj8 l,-k` WXf-0h+ -Uo[!,0 3b\X,` T-0`tܳu9`],0b8ѱ/l@]-e,`V0Y,@P -Y,p7`dK27" bŁ?dV.r lbAw}E34h|bAw}|Ǎu /;RX]$*X]X,2jX]Ԗłn ΣX[,YRX+X x,HET PBł` A%2Y,@^tB, $,4AJS[ lG`m-bA)AbA)%PXfXP XP)9--Y,`b֥7łʄ&xƺt-T-%-(n$7A'K`Kbbe[Eټ] -2Y:piX7QZ{{xcF}f+8yǀވj2 * =yfbgYyiJOmQɁ ׻O-pș%EV, AuzN_ ;eˣ@XZ +,P1շss =0M65 -N6oz\Pg6۸(sttX*1D|Gvl(p L$ƿy}Yޘ퇞c3]B<~w^wFl~{hzC$/<>|)i?FAMJrYۭzE^eq=lcW_kL[r ۪c}͟oac޵Wן:ʰ0^6f< "*݀-ٻ 8-nOA/DڇH{[DؓˌiN*EoP@IYLט="|%1j\g+e Ǝa;zm15_ڭ˱ye.גu,}\WŇ8>̎_|\_ Ï1meݞ~uUvYk'\osp9Z>۬ΔƁZ c? {xazqK6[]Ҹ_\4AaHBFߋi3><.cqgu|ot=|=f";i-Y/{-}fZs֘5xˤif1KF}[Nʡ>xch-iDWnuϮyrV fѻtOEM= 7wd*(yω; ye %Z־Wt_f 3O -:yy&wdyfZZ.x -ۘ[z86_WȽ{v]+\e{S#L#IZ-?Ʈ˔1j(L04 7A=^KCM]omC>ay/5fNy7PdTZ >Or2_PZ0]?͚>|H]Nfg*VeZ)#ԹtTg}wZ#V5Wk*S܄rBM&)fuBoo24Wai6>߯]Y>au0AtmvIP.7a_60Ȅ!e-zׇN{k;A}8|8CyLGxy2O.ð>(߬|98,C#%.qMGJVt"Nq8 Xe35 A~u`*#NFn*&(y>;?Z7Fz&Tޥ_J;l)/i{s-Ok{3(-ds0$-㴵A& EddlJi-KC8Jwbg%j-j{phd1di>Ke&;-۱[=O!Ð4*SCˏǬ9Ve D->soPI }m7Kn<{'H'̔ۄ[(Ê}*8Qw?߰: YZXޢ/g<~sd\ţ -endstream -endobj -325 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 324 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -326 0 obj -<< -/Filter /FlateDecode -/Length 4635 ->> -stream -x\K$9nD,`` { /pc}Н۳ ="U]kE~pWL%E~z&梲O -Wg9J(TOr˹~smw]L)٠ -X֑ -CTX 1Bb1䠱 {V=@ k,JH -Yἵ*Xf -31_T^%LLxCx YBNx)'! E*H%⡝2dueYlN2dfW9{Ld5s&6I0I1)<Y EA@k<,?rVՋw%d>ʃ,| |,6E AFpIYp次pJ/p,I<4 YG AjXC1f]@Hհ 2.aASyŸ+~ -cѰ wHÂ|f kX5pb5,] AqH4,@|3tU^1aAf K4,kX `aAlJJQÂX,xHT^4$ Bd<‰5,@bm -aA򐅼װ yȂAd8d\CdL.V5^&'๤aAJlXK װo$]ҰbXÂT \E"=2s l 眆CddʌVDh%jV֙YÂHa+M ʃ, 0?`&9*P` r Y6e4,( Ӱh$Mְ0aR֛YÂBM,-e4,( YRY4oIXo4^,%FYof f`^ȲLvp7 "3MdxCB~38c`U2^DXMe*Ϊ|0a}"!!f$,p Fv=(ϗ?#^_SwڟGYX3K xej{,+!rm7\2Lo:ba(Ҿ{H{tAm߷n\N*2|_鏿G~[v_~V'I^~~у1k](^ײ@ Y m8m.kh~Ylcc@@?ӏf3Sk %ViMz=)cԳ_0 9fypZ}}6׵\\xתgN<ڮ$j]slߍM7my-A?5FavS'd Q'o݄Y+Z|[Кmc -w?S9f(ܷݰ'L,絟;4?Ƹgq? ׾[qTq?ژ1*9Ɗ܎ezpjX">H/k;֎EbSf=ßOu:.A=-eX.s_ƂMR׷\*?~*G!(5'}cX_햵ZFd=I:iڰ>( -&/{I[廥\F~uy7_Z[ Lu -V7[l&Q˷MWuLS $rXvCQbɍ]xuw[KGˋd -d]zQ0aZTn{qڒm{!h" iioP"wm)FBuSd{HΔcAGX9b &w;a$-!dh s·Qm(OHW]تv}αue#eXT?/^ Vr:B[^G)F#Fu3;!k#q>e]jyU)x}r,LW¤Rd7rP/ZοnCWCzv[k`v,9 ՖN__g f٥-C3v[tE@kL|dMWxHz)(:>NrSb#YsJ}V#jȶ3mUn_,dRVN',\$SCwX]?)+>ZKLf%CFZ;Hh&ǿ3 ADI,7[ǩ*8Y(o6Mq/g2$'o69JN2ʀ@QQɌ2 -5M(#҈M(91:&vK"ixϤadm&TjcFY5{xٌ\cT_ƱiVيSʓu>ur4yTa} K,j9,r*Dr68Z&PXm ITG Bίo'+8O8^KRĮ(S@?_[Oף} MT$椫~O㯗Xu ΃dy`HU8Ζ(isUf}֯oȣuZ狵u_ͥh|}/ \HןŮlǾ$cןL?FVMWe -Q}bsX!ftd5n%˻$,Wb eG!ّhsɻ vgչi[Y|F]-/*UhӚjhtjh%p't(lk1?͚`!fH˕VN!.jg*RyT-MCaꔻmz%&~nDk'wy0ߑ_.!) -Dl Y~5M*S8&%D|J鱣kpFI].n\Jy^klCT6ёt%nu,ӱr&&MeCr΢=v9v|ɩϸ\ty{76ޓsde9̧w6`A0R[;:ɫdZĽ]rac!!h$'om.wok8zwlݐH&'οFn3=O?.YCOxͣJsgb:Ⱦ<14o;-D[fdM^0Ѥ<sUG#$_&q%EGHTs:,Cbs']"?S!7)K<avn("Hi;GC{>0vөT/yz[4$gH-xs1DͣZ ̝rm:mhzjM-uYR9Šetg+1̳J-lzfsNctvdVhqݩ̐ -endstream -endobj -327 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 326 0 R -/Resources 4 0 R -/Annots [ 328 0 R 329 0 R 330 0 R 331 0 R 332 0 R 333 0 R 334 0 R 335 0 R 336 0 R 337 0 R 338 0 R 339 0 R 340 0 R 341 0 R 342 0 R 343 0 R 344 0 R 345 0 R 346 0 R 347 0 R 348 0 R 349 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -328 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 507.723057 101.433071 488.973057 ] -/BS << -/W 0 ->> -/Dest (cb9-1) ->> -endobj -329 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 488.776036 99.933071 470.026036 ] -/BS << -/W 0 ->> -/Dest (cb9-2) ->> -endobj -330 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 469.829014 99.933071 451.079014 ] -/BS << -/W 0 ->> -/Dest (cb9-3) ->> -endobj -331 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 431.934971 99.933071 413.184971 ] -/BS << -/W 0 ->> -/Dest (cb9-4) ->> -endobj -332 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 412.987950 99.933071 394.237950 ] -/BS << -/W 0 ->> -/Dest (cb9-5) ->> -endobj -333 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 394.040928 99.933071 375.290928 ] -/BS << -/W 0 ->> -/Dest (cb9-6) ->> -endobj -334 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 375.093907 99.933071 356.343907 ] -/BS << -/W 0 ->> -/Dest (cb9-7) ->> -endobj -335 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 356.146885 99.933071 337.396885 ] -/BS << -/W 0 ->> -/Dest (cb9-8) ->> -endobj -336 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 337.199864 99.933071 318.449864 ] -/BS << -/W 0 ->> -/Dest (cb9-9) ->> -endobj -337 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 318.252842 99.933071 299.502842 ] -/BS << -/W 0 ->> -/Dest (cb9-10) ->> -endobj -338 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 299.305821 99.933071 280.555821 ] -/BS << -/W 0 ->> -/Dest (cb9-11) ->> -endobj -339 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 280.358799 99.933071 261.608799 ] -/BS << -/W 0 ->> -/Dest (cb9-12) ->> -endobj -340 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 261.411778 99.933071 242.661778 ] -/BS << -/W 0 ->> -/Dest (cb9-13) ->> -endobj -341 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 242.464756 99.933071 223.714756 ] -/BS << -/W 0 ->> -/Dest (cb9-14) ->> -endobj -342 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 223.517735 99.933071 204.767735 ] -/BS << -/W 0 ->> -/Dest (cb9-15) ->> -endobj -343 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 204.570714 99.933071 185.820714 ] -/BS << -/W 0 ->> -/Dest (cb9-16) ->> -endobj -344 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 185.623692 99.933071 166.873692 ] -/BS << -/W 0 ->> -/Dest (cb9-17) ->> -endobj -345 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 166.676671 99.933071 147.926671 ] -/BS << -/W 0 ->> -/Dest (cb9-18) ->> -endobj -346 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 147.729649 99.933071 128.979649 ] -/BS << -/W 0 ->> -/Dest (cb9-19) ->> -endobj -347 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 128.782628 99.933071 110.032628 ] -/BS << -/W 0 ->> -/Dest (cb9-20) ->> -endobj -348 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 109.835606 99.933071 91.085606 ] -/BS << -/W 0 ->> -/Dest (cb9-21) ->> -endobj -349 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 90.888585 99.933071 72.138585 ] -/BS << -/W 0 ->> -/Dest (cb9-22) ->> -endobj -350 0 obj -<< -/Filter /FlateDecode -/Length 4932 ->> -stream -x]K$9nՃXa51`]ݵ  ="[] QT(lɹH_NIlX]T,%î_ $ -o'wu9W;oNnޔ_ -I9% -d]PH&%Q!Egph$9HN -Yἵ* Xc1Qygb.K^`b"NcpN1daGd5dF%`Ud9 ! +4bu%)oi޲hn$ŤVKqn1X4,`.UаϬa0z {zM])k?(Jbb"`W#d -c !#mDT,pp?ȐXdvf/2 -Q6OuY;;nqڸlqzw˚c$d6Uܫ+]!?*^'  ZIp^? -%($/?/%-Bt%`$fu[H=-DaGPĶ[f / sr?I@!EڽA19ăJcLLap "!:Km:RwN4Yo;5)DʜۗK?6= [J9{Dr;zC=ɶA[Ln3+>Dy]Y=N%_HPr V|JLjΨ{ 'ֆ]mg|X=vv i-G}ivӮ ,E3nWxZ"$L)(Ÿ#6o%{ĩg@]5X U~82ȓw>YoR>2W#yFI8X;=/yKѩ>X{(h rl,b>bcSFJU a͕iI1$zܽ'kk59*{-gd}ٯ&נ~{L?ÎD0r}Km%)xP( e2AbrYG>w&q)3pEZ}*\(O#sF.Hd,k->>81puuc)i9KI[,%)x#W=+jQd-Dv_B"P$fOvf]d~VkU 6e.{㢅L&g<;?5]mϸ2|~x58Ͳ% JybҚ -4EȲQ? {I'3-{-D FݏDKi}gH#ohip04VҶ\SpOhr6m |P"+Yy7{D=k <  X$^}dXއv)ڐGlǚ| `:SC58jl#y%n=Ї|W8×>%4^;0ȭ#YBbvla-㓾wwwNZ.߱Gxڽa -!tJﰏg?um%voPu/+1{/ͪ t}9AθqªoAƱ&ϐ!p"Xh9CǪcۚq* +ql 9cM>'VΒݚw ot,ťxhlrږ??Gd:H}^zZV_p}ѧMր7 )əO^4z{ˋ9. y)jō}.ZX=6kwC׫W|gmiw0uwW=R[XK( _Qzd>WWeWwzI%9Jޗ I-a2|^+Ӣ*eG*!5םV{͔B=lk~7^Vbex,WC'ݡ㫀H?׺l-f%ErcqpHsrW89UfўcM>eʷ|3N}yq;${P< ]cwEEw.\ʗɋ(CouC/'tKR 60 Uz)}BϓRrR -5a2;}59iR"QWZ=[qkѴ UR2IߟlĆq]e\#z7/'nI+,7՛ ķg;e {O0V&^*S?8*%g-щf/^\;6Ҩ; K<^.[nGlU: TJO@Ǻuam|:V΅ F1wU~[9*Yts;cη8wrpftTFŢu2MST8(oYkG'2qq_N9U7{YƋ9s:?Otvŏ{wl]ϞL5 ,ohlBObG]n^hn#ԹNžwaQr5=ֹr͡ GV6p1.K\IA%?5SeHSrOTk Fά[Y -B0_̌͝<7"rl {\oLJ;饡^e96#yBriЂVNy4[*)UQt@mecj2ťYzYcQyy>Υ*VԕQrpKK6ui6N+$md a(|.e0j߱7-7Ѐ9Y_RQ9^7)HЛu~^-ԟS҉ -endstream -endobj -351 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 350 0 R -/Resources 4 0 R -/Annots [ 352 0 R 353 0 R 354 0 R 355 0 R 356 0 R 357 0 R 358 0 R 359 0 R 360 0 R 361 0 R 362 0 R 363 0 R 364 0 R 365 0 R 366 0 R 367 0 R 368 0 R 369 0 R 370 0 R 371 0 R 372 0 R 373 0 R 374 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -352 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-23) ->> -endobj -353 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-24) ->> -endobj -354 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-25) ->> -endobj -355 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-26) ->> -endobj -356 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-27) ->> -endobj -357 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-28) ->> -endobj -358 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-29) ->> -endobj -359 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-30) ->> -endobj -360 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-31) ->> -endobj -361 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-32) ->> -endobj -362 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-33) ->> -endobj -363 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-34) ->> -endobj -364 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-35) ->> -endobj -365 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-36) ->> -endobj -366 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-37) ->> -endobj -367 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-38) ->> -endobj -368 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-39) ->> -endobj -369 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-40) ->> -endobj -370 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-41) ->> -endobj -371 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-42) ->> -endobj -372 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-43) ->> -endobj -373 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-44) ->> -endobj -374 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 340.338585 101.433071 321.588585 ] -/BS << -/W 0 ->> -/Dest (cb10-1) ->> -endobj -375 0 obj -<< -/Filter /FlateDecode -/Length 4737 ->> -stream -x]K$qׯ和 t0 ^Â/‡ B|dVTevOUӨ>"_IZ|+39嗋5)X%6'|R:Wbן@ɤ| ~.⯗忷u՛Rwb2)d*`YG -+QaEgph,{e%%12 NnYbXcA WBRXBUy2Wx.G睉x.yGdbb+&cu/@ƃ,L9iY(UyD/A! +WKивq1 p4,]gְoQZw/VÂE4,9@7,LWcK.`kX(lld`HNC5,]aA@aAZFڣ eaඊO#Y5)4p:Z+aSÂೆ ̦5,łOEaA @ʃ,X$֦P$Y{ ,H4,@F`CN E0dAa¬aA -1hUEor\ KiXpz F% x5,HU4,@(2#3x ְ.xiX=dA6aAh5,@\xle5,M0R<а#a&?lb ְ g/ͬaAΐ[alSIÂb! 2> Fd YaAqM/e5,(d1OBQI% EQyISQ&IE kXPbfְi%,ͤ.wC2i<.2Өa.0Df-7$g:3ˌ3+[% EJꚁI]4Y樮 鬺l`էy*bfNrnc;Ŗ'_7u8?qkob 2=2 Z]DT.ڿАYvHgcLF.+}/e}3^'%<ϗo?m~oe-ZʺX~A[.~܏,DM#M#ū͇TKWrkeJ]E OǵW2־OG7?o?&L\qfռ}9au-t ZqmGTK* KZkk;N"ZZ>گmT%_ϋ9utqy"?-[MFꥇ}#eokm{8ڬuL4/h--=.m""YVEƂX *>{:BX02^ܛ%A D ڄ뢆~1ln|?4Sa^Z= }3K\VSYeuL{C7R+22Yo~n.b#M^@VzU7NP+z_Vk?Cim{c^Ę -o{Hq0¥\an.=\ a Cpv@5^uw7:j;;lSFS[6N|Ƃ;S;e_zoVY/?u;$ dH:a|dm+LF`5*} D3Α;M˔yECoֽQJwiWy׎=zc~9BfI˽!(۽<6MfYI,y<N$?팩 r*V=o'Wd!3G:ϣTʓ^z>~ylZl-I&Dcslb!5r JrA;Uy V1Ck1gLYt6r<*8ퟬ4`U(ݳE#/댾}]ev;%ڕ _1[)> -볗O $ %cF(.<ldʉϙ?ӇN秕.7kYϻ!eJ^^א}j<'y5 )qq'l7n1MOtHCnl 5=r$9AqufDms?s<|ܴy,ÉŠoB6L@*cItB[bla]Yk}$9à{SUFᲇqWUO@ QGe^$FLzX#mwJEkraG~?9'&ߚ֖$e&[byc3Wkjy4fF#CSw&32ޒ9wet:Oɲ pc?$ -a5"f!bHu]3ô{k.v1rctvM)؟0X{ rvh-vntElʪFvo+(_'~okhWM'eyMv}ۀn(l!Eu#g1MUP'eۮ<-}u3d͇miql,= /Xlpq^F6b@99'"[J6W-VԚ8_z) CdA|3kl%g."ٱBfn B\h/@Q_.˺noC& m_:V-Yegi6^.JMfG< dGv"[dM'tAϪs>MrAT95մ lo4*Z> I!\75ΟFMNsYrSH/Z#z.Kغ!ϑLNf'ɲLDˣlh^n#ܙ'+ ̈́ė{"c3rI ɱ@M*\̷> -endobj -377 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 709.923057 101.433071 691.173057 ] -/BS << -/W 0 ->> -/Dest (cb13-1) ->> -endobj -378 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 690.976036 99.933071 672.226036 ] -/BS << -/W 0 ->> -/Dest (cb13-2) ->> -endobj -379 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 672.029014 99.933071 653.279014 ] -/BS << -/W 0 ->> -/Dest (cb13-3) ->> -endobj -380 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.134971 99.933071 615.384971 ] -/BS << -/W 0 ->> -/Dest (cb13-4) ->> -endobj -381 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 596.240928 99.933071 577.490928 ] -/BS << -/W 0 ->> -/Dest (cb13-5) ->> -endobj -382 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 577.293907 99.933071 558.543907 ] -/BS << -/W 0 ->> -/Dest (cb13-6) ->> -endobj -383 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 558.346885 99.933071 539.596885 ] -/BS << -/W 0 ->> -/Dest (cb13-7) ->> -endobj -384 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 539.399864 99.933071 520.649864 ] -/BS << -/W 0 ->> -/Dest (cb13-8) ->> -endobj -385 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 520.452842 99.933071 501.702842 ] -/BS << -/W 0 ->> -/Dest (cb13-9) ->> -endobj -386 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 501.505821 99.933071 482.755821 ] -/BS << -/W 0 ->> -/Dest (cb13-10) ->> -endobj -387 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 482.558799 99.933071 463.808799 ] -/BS << -/W 0 ->> -/Dest (cb13-11) ->> -endobj -388 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 463.611778 99.933071 444.861778 ] -/BS << -/W 0 ->> -/Dest (cb13-12) ->> -endobj -389 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 444.664756 99.933071 425.914756 ] -/BS << -/W 0 ->> -/Dest (cb13-13) ->> -endobj -390 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 425.717735 99.933071 406.967735 ] -/BS << -/W 0 ->> -/Dest (cb13-14) ->> -endobj -391 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 406.770714 99.933071 388.020714 ] -/BS << -/W 0 ->> -/Dest (cb13-15) ->> -endobj -392 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 387.823692 99.933071 369.073692 ] -/BS << -/W 0 ->> -/Dest (cb13-16) ->> -endobj -393 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 368.876671 99.933071 350.126671 ] -/BS << -/W 0 ->> -/Dest (cb13-17) ->> -endobj -394 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 349.929649 99.933071 331.179649 ] -/BS << -/W 0 ->> -/Dest (cb13-18) ->> -endobj -395 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 330.982628 99.933071 312.232628 ] -/BS << -/W 0 ->> -/Dest (cb13-19) ->> -endobj -396 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 312.035606 99.933071 293.285606 ] -/BS << -/W 0 ->> -/Dest (cb13-20) ->> -endobj -397 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 293.088585 99.933071 274.338585 ] -/BS << -/W 0 ->> -/Dest (cb13-21) ->> -endobj -398 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 274.141563 99.933071 255.391563 ] -/BS << -/W 0 ->> -/Dest (cb13-22) ->> -endobj -399 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 255.194542 99.933071 236.444542 ] -/BS << -/W 0 ->> -/Dest (cb13-23) ->> -endobj -400 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 236.247520 99.933071 217.497520 ] -/BS << -/W 0 ->> -/Dest (cb13-24) ->> -endobj -401 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 217.300499 99.933071 198.550499 ] -/BS << -/W 0 ->> -/Dest (cb13-25) ->> -endobj -402 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 198.353477 99.933071 179.603477 ] -/BS << -/W 0 ->> -/Dest (cb13-26) ->> -endobj -403 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 179.406456 99.933071 160.656456 ] -/BS << -/W 0 ->> -/Dest (cb13-27) ->> -endobj -404 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 160.459434 99.933071 141.709434 ] -/BS << -/W 0 ->> -/Dest (cb13-28) ->> -endobj -405 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 141.512413 99.933071 122.762413 ] -/BS << -/W 0 ->> -/Dest (cb13-29) ->> -endobj -406 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 122.565391 99.933071 103.815391 ] -/BS << -/W 0 ->> -/Dest (cb13-30) ->> -endobj -407 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 103.618370 99.933071 84.868370 ] -/BS << -/W 0 ->> -/Dest (cb13-31) ->> -endobj -408 0 obj -<< -/Filter /FlateDecode -/Length 4928 ->> -stream -x]M#qWhm$r&?梲O -gg9J(TOq?Wc?:M)ѻp7a1SAa#Iɇ3R4=Y bpAcA >+ 1=@ k,JH -Yἵ*Xf -31_T^%LLxCx YBNx)'! E*H%⡝2dueYlN2dfW9=`B&9`Q,ц K 5A_rVՋw%d>ʃ,| |,6E AFpIYp次pJ/p,I<4 YG AH0p܂6sw}^zQX5B@a3a -?ŧV5,]1|*qoeb,.&*Ұ wY`5,]G5pb5,] Aq4,f骼blYÂ,y 0 $*/Ӱ`l,P "p{Ѱ wm Ұ w-#Qyװq xp[ŧkFXwMEÂܕiSÂೆ -̦5,łOEaA @ʃ,X֦P$Y{ ,4,@D`C Y)jX$30kXBD>jMNksIÂ`*v 2NaHaϱ@L5,5,@ sdY jX}FKBYÂHa&RAIH~l"QykXt3kX3dkX۔|3iXP,dAħaAHa`)vYO=8JbE|pLmEBH".,.n"$bLܾȐXdvf/2zw'uAyTR#TNy^~4Y,Yi AY&DuLRI 9яDXx3%,o -×i.#14ϧ_O??;~ÏrNr-:/[5(:"MUyHu !FL|~Suyk# ش& |Q3&YVqxL=Nғ5 +!MID%cH֥;P'IL K׶4@iKh'YvM[2 )(N'"K~bAKwH-7~: I9RA^?lՇޖ)\ݾfD /SQmA}i-ΧՆ!;'ȗG}0U6;Ǻ C#v,S3ԕ(e6uz#G8KœҊ6q'䂁KD֬(Ū؃tsNf\eZodSymxu݀ybşɸf <5@\cu@a\s,Jɂ#!xͅ:\׋kv=9G*m#(Ð6Hz:)ٷ+-*8׵}>D,87U%j.&ZZT57&G/[vg9,Q6'{}"> -{'뼠YPT _Hmӗyf"mGF! R ǎ;ĨT]ۿ'fܷk-!] 7l5mń`%]KsHd^R>su^&$D6;F'ص֌?v70vmޓ)Y.qf p0e& +q6&w8}B6iב y>H7k,qq;lI==\&ڛ4ebAvЅjF9C6E=#C#>06d׋dSro} l1[[05*X=Sj!ds0> jFzbc2%r*jihO )׾l} ɾg -m]o\8 ,!vf'fc1鐿ja!`Dtb3Ogi?Cܽ9hggW_{h?ؚt]͂ V9߾/M -^hq|뀟l F:~ ؓmI2mޓd*Ò`6l@5˭c t)r o֐5m󣑄a*6y x"ãi ڔ)ҭ`!ʶaq[>fo=UunY| -m]򺘼P-6yK(7;nk}]E^~}o}Fo\}GԾ;D?r=Wj?{GH)g}C|Xkx`LEۇbx4r2$ZŰHQUЌ. d@;mA8xB^V i"/M{3V/l`UHSff4iQ^-}bSpfc: -佳ӯUy!Zy/n6#ӏ."f@P3:.LeN?'߷yOL ͺLIô71Mg1vgй*3Y0-fBf3X@iϿ8Uel޲Lܱ1oC|,p -v|Oy˻]7{~\6LV`n`CSdw^ =sk񞁞I~~?;`og磭6~o{K^ ;fчx=& \XXI8U>2r=WO2 )vp/d(C4Mp2c@Pd窼 Iމp~]F_\:D oo^aki2 ^/eZ_"OC8YRd; ?Y=p+o=|XԹUIۏԬRW qT޷+ܵSڹ\ZWW0JOȬm]/FɉTd^UA_坡tssUťlrttۙ J*DW'`Y}zn[߫]w*vG]mu;~9{)AΝpS"jg U@USZ&9LSN rdїž/ ̪NwQwCd7vWe8ޗvӆ&.,m2loTK߃<0CXa7b=o3WmuW#2l1H*ڝ?YAr୬a/$k~rG=VrE'$rVO|-Y)%1skitzz7R?8^\:Vݞ,wp!ir(!2KloW<$D;trZַ9MQunOp"-]S?T!6jJAҨa-8)BM3Q8/ļre-NjF*RW-()7+)~ݒ:6vwķlّ?N!)C -V4v{TD+M1/PU~qLJ~;l䭒FzlÚ^vPK/R^@nP tD5xlɮY]# iX9*LcCr΢=v;96ɩeW[,N:YVWi .@;~T 2֯ɴS</t$'礏Q;yۆa~Q\.FL1ȱzǡb#:4;6] Ex16nlQ~ؽ{Bmި#ݘPTq{y]C-|Z]mt^m)Nym:]'ٕZLLqqVZLѩ5QiJ ]YiwZD- -9~wldVhqݨKJ۾<wAbLmv%¿G|RjB++#.1QK:1:yF(nj7jL, uCC,$IЛPuRQ]BIht& -endstream -endobj -409 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 408 0 R -/Resources 4 0 R -/Annots [ 410 0 R 411 0 R 412 0 R 413 0 R 414 0 R 415 0 R 416 0 R 417 0 R 418 0 R 419 0 R 420 0 R 421 0 R 422 0 R 423 0 R 424 0 R 425 0 R 426 0 R 427 0 R 428 0 R 429 0 R 430 0 R 431 0 R 432 0 R 433 0 R 434 0 R 435 0 R 436 0 R 437 0 R 438 0 R 439 0 R 440 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -410 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb13-32) ->> -endobj -411 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb13-33) ->> -endobj -412 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb13-34) ->> -endobj -413 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb13-35) ->> -endobj -414 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb13-36) ->> -endobj -415 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb13-37) ->> -endobj -416 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb13-38) ->> -endobj -417 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb13-39) ->> -endobj -418 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb13-40) ->> -endobj -419 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb13-41) ->> -endobj -420 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb13-42) ->> -endobj -421 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb13-43) ->> -endobj -422 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb13-44) ->> -endobj -423 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb13-45) ->> -endobj -424 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb13-46) ->> -endobj -425 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb13-47) ->> -endobj -426 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb13-48) ->> -endobj -427 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb13-49) ->> -endobj -428 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb13-50) ->> -endobj -429 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb13-51) ->> -endobj -430 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb13-52) ->> -endobj -431 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb13-53) ->> -endobj -432 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb13-54) ->> -endobj -433 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb13-55) ->> -endobj -434 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb13-56) ->> -endobj -435 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb13-57) ->> -endobj -436 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb13-58) ->> -endobj -437 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb13-59) ->> -endobj -438 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb13-60) ->> -endobj -439 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb13-61) ->> -endobj -440 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 169.815391 101.433071 151.065391 ] -/BS << -/W 0 ->> -/Dest (cb14-1) ->> -endobj -441 0 obj -<< -/Filter /FlateDecode -/Length 4517 ->> -stream -x\K$ s+H#  bd8C~>Jfw쎓b =_N_:M)ѻp郰L)٠ -X֑ -CTX 1Bb׬1䠱 {V5@ k,JH -Yἵ*Xf -31_T^%LLxCx YBNx)'! E*H%⡝2dueYlN2dfW9kLd5s&6I0I1)<Y EA@k<,8(x&KN}bY0Yl>%ų>YCH_Xdxi@@, Uy -kX@D3iX@@[hX@[iX@[.jX@\i5, . T4, `.;5, .=iX@@] -kX@]5, .0p5UdkXt42iX]r6iX]װj`Q؊9[ e BK>H0p A]װ}԰b?Va=x4,@c#-Ѱ w]AS|he\.QÂuӧq WZ6.ƢaA"P  "װ w!RkcXKB3TQ V@JY`~d4,M,sTde5,x5,mz3iXP,dAƧaAHa`W?wdqqఀTo?OcX]S>DEٗ2?ur]wcD&ڑaլ9vslj߱t1N}iޑƶYw$֘ڷ<˜fnkMbf}-?LkF?ɧh/}X˴gb].ڷ c]i^kmXW?z?NeZg&DdWGCcc/W9&y;;ջ?.5ۉ$nk׶]9J%c3WgjA'E6yA-XlZ5K? l'}2?:9jŶOmܣ{%hmPۉ+=N'|y,{\1t@] -Jovj;MC0S"QliLK?/r˳nL2Bg&nP\m2tʦ>AiGŠ՞)#Z/@t=,'ea;nqUWkSo?o57KH(G Q|woeW˻)2PooM&L}E?C^. stp͗ 71!x̆2&6EXҩ)`3.i ^%ϻƂ;S;ezEݍ*<˹$wdb3bؓpID#=ThC\Wx|?-?K5)\UclbXeyE'؀7(mo;Zr{׎=\{c~ֹBf.S/{7cˡ{w@tY~My&K,rN;cjʿt%璼(IdrL.?JyF9T]oޏ-[mes9dk81xβv$yg|ZxI),BoL9;UyybtZg Y.Sj}kk\ mWuGrTJlQgIc Co]AyDwᰶ3O@ -Bse w4C4>z9ALtf`#SN|4?}|[2(!pnыv(hrϣQ|hjrct9C5gН\zGdLMlXQJB 7K}a̞s?#H|*r[TSەTh>h@6ߟn7҆KsFƺǿ ry4%RdK[2Ցm)۵c6%dJmYEA`!6/fؔj`9LhO`'&WV͈r  ki#\ZWuO땗 D}Ƚ2ݠ -}X۴=.Ѥ|%$n)帪-tRzi -|M0~?/q7~BXx zq~;:ɳ9Y e W)k^uzuE^β H,W+%봹hwQ~A^j CZ:?a/,=$afff"z`]eCVѤJsgb:ȾH w{"s3Hmp&} -pFH>OMI."F8uXd1 NE~aJ#Gn:R`͝<П^=ȱyP;wLj> -endobj -443 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 541.623057 101.433071 522.873057 ] -/BS << -/W 0 ->> -/Dest (cb17-1) ->> -endobj -444 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 522.676036 99.933071 503.926036 ] -/BS << -/W 0 ->> -/Dest (cb17-2) ->> -endobj -445 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 503.729014 99.933071 484.979014 ] -/BS << -/W 0 ->> -/Dest (cb17-3) ->> -endobj -446 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 465.834971 99.933071 447.084971 ] -/BS << -/W 0 ->> -/Dest (cb17-4) ->> -endobj -447 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 427.940928 99.933071 409.190928 ] -/BS << -/W 0 ->> -/Dest (cb17-5) ->> -endobj -448 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 408.993907 99.933071 390.243907 ] -/BS << -/W 0 ->> -/Dest (cb17-6) ->> -endobj -449 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 390.046885 99.933071 371.296885 ] -/BS << -/W 0 ->> -/Dest (cb17-7) ->> -endobj -450 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 371.099864 99.933071 352.349864 ] -/BS << -/W 0 ->> -/Dest (cb17-8) ->> -endobj -451 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 352.152842 99.933071 333.402842 ] -/BS << -/W 0 ->> -/Dest (cb17-9) ->> -endobj -452 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 333.205821 99.933071 314.455821 ] -/BS << -/W 0 ->> -/Dest (cb17-10) ->> -endobj -453 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 314.258799 99.933071 295.508799 ] -/BS << -/W 0 ->> -/Dest (cb17-11) ->> -endobj -454 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 295.311778 99.933071 276.561778 ] -/BS << -/W 0 ->> -/Dest (cb17-12) ->> -endobj -455 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 276.364756 99.933071 257.614756 ] -/BS << -/W 0 ->> -/Dest (cb17-13) ->> -endobj -456 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 257.417735 99.933071 238.667735 ] -/BS << -/W 0 ->> -/Dest (cb17-14) ->> -endobj -457 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 238.470714 99.933071 219.720714 ] -/BS << -/W 0 ->> -/Dest (cb17-15) ->> -endobj -458 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 219.523692 99.933071 200.773692 ] -/BS << -/W 0 ->> -/Dest (cb17-16) ->> -endobj -459 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 200.576671 99.933071 181.826671 ] -/BS << -/W 0 ->> -/Dest (cb17-17) ->> -endobj -460 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 181.629649 99.933071 162.879649 ] -/BS << -/W 0 ->> -/Dest (cb17-18) ->> -endobj -461 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 162.682628 99.933071 143.932628 ] -/BS << -/W 0 ->> -/Dest (cb17-19) ->> -endobj -462 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 143.735606 99.933071 124.985606 ] -/BS << -/W 0 ->> -/Dest (cb17-20) ->> -endobj -463 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 124.788585 99.933071 106.038585 ] -/BS << -/W 0 ->> -/Dest (cb17-21) ->> -endobj -464 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 105.841563 99.933071 87.091563 ] -/BS << -/W 0 ->> -/Dest (cb17-22) ->> -endobj -465 0 obj -<< -/Filter /FlateDecode -/Length 4916 ->> -stream -x]ϯq_&Y,{ Y# "ٗ+DRz-J'V,U(^,|W\R /\~X⿩bb /Άdؕ!P2O킿n.o?kM);~a2)dYa#lRVtXƂ[VdXP#xV-@ \XPN -Yἵ*+<&ӣ\|Qy <#21Nctbc.K4^.ɪB #aOɄ> 9d |.&D &Ē4 NЅCԐt \] Cа@6Z4, miX@`]԰PjX@@\1hX@\RѰ԰pauװr԰հ w X!IÂ%g 7`T 0jX[1>gaAl |4,]ϸmz^ÂG `(ch a=.X 0߃ITf<  -?ŧV5,`>WKqoX4,`.&*ҰϬa0`F0pfjuX 5,9@oY+Ɩ5,`.`kXY $QyccjXދkHÂܵaʃ.k*>`Xx]0km*DL$5,Qװ `JJQÂX,xT^4f Y*4,@`m -aAЅװ y肐AD8Djz]`.j~ "E d&4,HW5^&'๤aAJ`*v 2NaHa R.p 0k<]dkXH<4, ԰ ,3Z 0C#DWk`%Mi)UtLhXd5,@diʃ.AÂYÂ^ئIÂb "> Fd YaAq/%7)~[(J4,(0B]4oI7N/B_%F73o"WI].r2i<."Өa.o"r{ Lgf8b`U]2^VI]3_ɑE2Gu*Ϊx,l0/QECœd[D5hbϘ|_Vʖ?O!Jb"`Wf.`a -%RiJ:&Jb*t[^VtgoPQu=,(]ii*(i8Vz!- Hl@V3Dwy Q"JQpTDh//.pqF˧_.3ֆso;uR=aHkcd|*!S}/Hf|Z>ҖRe{#2P[* ھl",Ӫ oNu<ƶ}j(|Effh8kX,tZd5 sbHyyO!bU]os&;<"ɑLD=eu;|Hy:(|q -I h$v݉#7NŖXh 2Hfd4G)7uٶ#H nH＝<ј`3ǘ!຺fs "f$3ۍɺVZ؍׽V1ޚ7sl[5ޏ|N&bEn"?&4'[+|'lUL/rlA8n M)Fu(R2gGYm%^% ˴T+e\afm]q<_;f@"tLa8y}x5![.ǿ>*aي?WJ^gPiokF/ۣbD<(uO]Z!1> -J-Lˉs-#$=*zv5b"%Jeӝ}LGt{6"yh {ea5[% as)W}jH$nh$f^?*R[iuuܥ#1㶶:WۼZfqtmg,&k My {Rny/d&VO;>"\W7-٫smm'w6tHHϳ!:AsL%qGYL]f1,%ʞXlbDWmƒK%ߋlP܍}TxޜAry@[[ָo"}`LCT0׷}Vzd|@^vDkpKm`tSÑe2ޑ8u]y(-KT ivF'f -T{~z8]l+}"sx -:srG!&=(>Öy{k&cmt۲;h績Al͇z_ V1"M `>ɋiᅈe%QlI$:$#0!61GSxwy#2|HVN73MKc/<T){F;(j(吙yβU)]HA՝8䱉 t^yn*$=Ҿ>"x$W-?s-Wgo!v)e11]?G74])ZÉ1mO[EhrQVѭpi=ޱ -,%Uc+h\==X{ǬBC_w5iQüI` -FH;emVAV倠Ȝ޳t8}3K> b~dLy͑ d "g2],xI$n]c2mG2}E~rF311,oI9J~HV3 &c"O3KC{'v|˄gU%Gg1hir|9!:8_JeYspSGy.ΪW ~Hg E;1X[ t{?sA*۱E?`Vs0f}=ƚ?%i'ҝX-41#/F78>ƚP~3HL᏿ag|l6',Yzйk5H-ϘJ&{i[MxZ>|]KxLuߧz9}Ms؂KW~xj0zѮn:i2;#;,}67u{yGrՔ_k)$+giXӀr]M>z_Ndh|K~ȏ^ 8.٩vC{%SnK;-rnD19Tv/W׆"$ے3Y~8$bU`Va˶ -.Y^ykDm\#!aKY_: Vs/e}fR -̶ШST*/%뀄:N -KՈ\w&>_y1P˕BzڸTr-K7USЦ>I~ K59,cٍ_/'6ۅRVX^L'RWo%gQS^ -\ -\<Iɱ5"YN鱢Nzv݅l_.[n-]{lE' UcMv*Y l韊=.JFjo+rӓEי;z9V|ɩ3̫4[~^id uĦ@M[+:2-_i3i(I'?G](#>} /}ǽh+L&?N MGFv<}סKIWUnOևW;כ^GǦMKZn͐hvpڔU+)ڦtpqWˮ4[)7R^P #/izMwALE_qp}ei*ZRzj1Vө4]esh:qqC.|j\auhGMl.}a]& -مVkLNq[eR1EiGv"7eeƫ{sNl+Ycɬb/]m;^fۗ6BS$61ޔ<g|*s -Z~5up> -endobj -467 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb17-23) ->> -endobj -468 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb17-24) ->> -endobj -469 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb17-25) ->> -endobj -470 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb17-26) ->> -endobj -471 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb17-27) ->> -endobj -472 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb17-28) ->> -endobj -473 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb17-29) ->> -endobj -474 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb17-30) ->> -endobj -475 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb17-31) ->> -endobj -476 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb17-32) ->> -endobj -477 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb17-33) ->> -endobj -478 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb17-34) ->> -endobj -479 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb17-35) ->> -endobj -480 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb17-36) ->> -endobj -481 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb17-37) ->> -endobj -482 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb17-38) ->> -endobj -483 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb17-39) ->> -endobj -484 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb17-40) ->> -endobj -485 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb17-41) ->> -endobj -486 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb17-42) ->> -endobj -487 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb17-43) ->> -endobj -488 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb17-44) ->> -endobj -489 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb17-45) ->> -endobj -490 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb17-46) ->> -endobj -491 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb17-47) ->> -endobj -492 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb17-48) ->> -endobj -493 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb17-49) ->> -endobj -494 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb17-50) ->> -endobj -495 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb17-51) ->> -endobj -496 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb17-52) ->> -endobj -497 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb17-53) ->> -endobj -498 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb17-54) ->> -endobj -499 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb17-55) ->> -endobj -500 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb17-56) ->> -endobj -501 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb17-57) ->> -endobj -502 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb17-58) ->> -endobj -503 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb17-59) ->> -endobj -504 0 obj -<< -/Filter /FlateDecode -/Length 3174 ->> -stream -x[K ϯ":p(#Brrג`@!?3}I2vwdu/ __3~TPk+YwNOJ"F\\l]ҙIKHrMFJK ?.}u>Zο3J(JE,+PJLae<HE޲ -VǂcuXb[Vz,-98<B"\[l.%z=,H]djÂEݐ<,;Fa[`뺼aA*Gb ƁPzXH ܥ$aAqyEju x['Q@ -%=p4 2pҦ!V `@=,UC+%{XaA! A-a -ФU J,%B "Q}dBTBmяA/P UxXPbTz % xY* Q{<,(=,@ 5BTXef$TϬTJE &4.&<,}NA6AIaAaA%RifdAaAL0+ͨ .߬4!hm,4, %˃,($@'!KlaAa #jfq <pi7Qz=xSA}3u=1 @oBnu ؋lU3Z@Lt5H`2E=7>GTP3kl Eu?z9L雷H}zvRֿ/N"܀-(!kB >aPǑDd_ - yMbF)ݗۢO`J+K|!I5KHW F)sV}&əm(JpP [՞9m4EC %g8X8i Û|w6 /C$˱I=];Ócx"Ŋg4[i*QcCr) -0w:WdɣwV5N/ -g%thP|h"۱ʣa9(^zvumKqc8iNHQci:C%=nrzKՆyة=h2ݟ7dKiۣu-r$Uk:}=9 6ڽ>Uu{vX^rI"Њ =ty[8ZG`c[UKc#p{Z5V{h>9^yqëk3~<|g\ڛsDv6*:Zzfn}0rqÉӿ6rbO:dI6Z}Jh#^t|lcqcLnl~D%qW33ߒ)Agj*QR2[#2u\pN|B 1invy؞ I}l,9#ޝ\S]}H&PmPS9 N˜X͞|IǸ9;X- K1Ωk~2]]PCttPsvX,mMuxC;%8Tibz+QuIEq -ivnl?wHjȳ}`.e~bs/@4ZE]\U_5ݎ7.zi]<d^7a]?+W"u!$)ghlyq4֝<~%aqyCޱx%6&׾$Gnn`I0z{td^ƽ;|\(# {)k`k|?!{4"l b$[8f!F]`α{֠+M }$]ip!ẑeLzxwQ|mf/{֥z;'3%%qeCgJg{^Lź(. ۔BLsuz_WS\,e]Lҝ2%BGO϶!r`zRǍuO2_^#ۙPީ,'ș1K X}t9M.6bhiceǴ펫2jIytZ2V䛱nxZQ՝˼;#G-YZ^gΑi{=۞)H)if'ߧ>տ$j"Q30D텾u9*yNnOHɺT -"܃ўf,K5roe -x[ m/volѸ,*q^?-Qv/O -endstream -endobj -505 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 504 0 R -/Resources 4 0 R -/Annots [ 506 0 R 507 0 R 508 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -506 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb17-60) ->> -endobj -507 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb17-61) ->> -endobj -508 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 719.279014 101.433071 700.529014 ] -/BS << -/W 0 ->> -/Dest (cb18-1) ->> -endobj -509 0 obj -<< -/Filter /FlateDecode -/Length 4966 ->> -stream -x]Kqޟ_qn`E bĈ/,#`@"?_d5O`4U|?/}UIR]o/_.j^_I:)7V.N^3 lb& <:)`bQyAR -** MYR q[U.'/`3& 3nUf:((%`rA 錞B&FY;ג.O!$->+-:2I6$VC*%-D'` :_b`AxIq d'\X<D&Ʌ%JCgDVV+`Nk` H\`-l1J\`hnZ uJ ,f* ,צ$.\@)K\`)qbG ,X`$.]RwJ޵9El%.;NV'+qZad$.@NaXLJJ5I9 xDL.NV5MfnH\ƙ q2 wA!^` V+q -  rwqq|? /^ >f0o1s?ߏc=8AXȹ3  ol=rbQ8YB}W?Tjd eU5yWnv KS٩pzƺWD[mu^$G]+y/]NHoPq*YDcfFo7=Z&R~EDڃ|o/oCo{oO*tBCo Jz\rjwO_O7˱[jOoXV-h}r/iQE-jf -&'4yZW9(:=K鞧r͡Ql9<.WimWݧޑMbBu2 еnTbKJvm9տȎhP-> C}$Fe@B3f{k v_ʋq-zb{^c5 cOKxff>yMÐf6W'y71V0سi-zgVK<'ׅ(^n7p5.0]c0ƟI ubxK@WA Toζ2wHϕj !,3q 5Ǒz.ϳ!q!RAer!Yq1彭+vTdԑQ'};ñY䝑{;Zol6tC2Oy:dCm^gl#W [ maѠuu4~Λ 1v \CxQ\mqRWHODؓKQBsye.y}6ۺIaw݉!鹤T%9F޹#+={k:ǎ{2!8|kGVo!ydTһc5Z}F̱ߥWL8{wtL}^ۋ#~=}nsߝ+Y?Η'<\ַ.8wvG>W`_4i;>|g 1t=oڦ3 -OooC;l%ldC߹x޵v'RIE$c_Ͻe$NJDw7<φRrÙi_# hYUs5 VO_P?lǺ˛'<}"d3{dӻIt )A=#ti?.b8C=>R0\ؠ4Ի?_~5 ?U{(֔/{_ne˼Tڰ/P֫U@Lb.&KAMm8Z_wr|io(z]>*yp;Y)i Uԓ.~wL v?GLPnoH^2~Ra=N3R/TMdV!rSդ1} &Mv9 z {w*&[buqMo ]LӬkZYw oTkG(/PԢwj2ˌMk! 7l?ZCg6=5z,LH5 ]tKiTlRϚ)65 {F[1l=\-Ub1]]\ޢM;W(_DžIut)# * 3U&%)5HћYf塱<]it _:)!=nK<21y<"Fknkbƕ\}Jmz* ݷr84|z\k雽\*͍b~tQm1a7 ŝF_Nz4.iXomj -]kǍjla|&orbFWaÄ1bzZ_qc_]ub)ucPݴ\4mg6x2o>aϧ6^A/V7lHQ>C ˈ^(NY[2+i' -KuFЩ:קY^tV$-?;++{zxC$mޤ\FFxԖӰ>ms-/~{eس-Cnu1ʤg[x^UuhtVb6%[uKiq[LѥW=IKEK@9֩ŒII]Oil[[]g+k놄oR~} (?egD! LNGklJ!C}*:ׄ*jJl+U`+gJlc:mg -` jURKAoEfGB$ -endstream -endobj -510 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 509 0 R -/Resources 4 0 R -/Annots [ 511 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -511 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 563.554475 101.433071 544.804475 ] -/BS << -/W 0 ->> -/Dest (cb21-1) ->> -endobj -512 0 obj -<< -/Filter /FlateDecode -/Length 4928 ->> -stream -x]ˎ,qWZ~dcX yax]3-10¿$Ɍʪ{Fm> 3 -?iR1'5EX]Y+'sH lb& <su}6Sh돤rv)FUJi+b4>'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kSӃ3z -),"t:Ig^K<|tk甤-Φ(l*Q[LVEb,l-*(-鲝|NΉ J1muF'kzuQ-A,`H: [~$xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8Dmѓٝd_| &SV4!00}k4ߢh*0 /O2ׁ [rJ1%Oj|5dJ|~ʎeʾؿ;u]fP ">ҎDzrٚŶhNoO<滆(B#=kz>fl1[:P/;w2询zeZs\Gʱp`CXE-;zuOFNk Pzs'sĘjK煝Q -QF{ =nij7@/x$śQqy:4_q?w:G:rv5 >1;rg2?{@Wh;{``Cߍ8o٩Jܹvc҃+ysU"3 -9@l<F8OFg;<zgCV-ғ(J}6Tş -VfvʼlѦeHe~9>\eSlrA{<ZǮ(Y=z_΀;gh`D-=Wzj0ӕgW׽oб-ԑwqVl<5wؓ=ǯ#;JݤT=?C$3>/p(͸JAfW2'pe~m< zAy:$_qzʞqa-kRn9VbTц]+iyWL#c]ރyŞ,kXqFe}?I.1Wy^wVR4ǙQhg$L4?㡂_)=> ?z},ٿDy[gެ}K=pUNE6=F59j/?):MiKv OfPym9QctPW}7 N.ovV42Ǽ׻uWqG^[ZRǯfvԱ{rd?^Ifە근W̊oecóM[Ŗ%$7j^OY^h3FqɧcYp1wn9L*ѾC8Aު-<(nvhϭ>L٣ϤAڛ2o;[N{/,o!R:gt+X\:',0Vy *b=?O'(6$\>Vm XeLqcJLj׉4kefyl9vX"g[1^MzӋtdL {7*&[buqM7ׅ.lsi5; /'TkG(wԢwj2ˌMk! wЙMzAɵtDn)ͷ-UYs|7C Kf06Fb"h}Í/'HBj߹B -=.&NK<fLIy~+k'qyh$h{Z.c,NJHOR7eLs5HZꚘ(q%jbߠw;}^ʂfp.;߹8t0_2QLO.6v2&솁{ة|Lq/4g7 i}_urgQ-L֕dBtPL/86l8F]SO+%Y}JP\ -sle&W\O;b,KuO*+`I[~ vWWF?<>ɡ6jow.m #i#[Cfg<Q6e"RЛMtQi6z9{}R~,Q_ -endstream -endobj -513 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 512 0 R -/Resources 4 0 R -/Annots [ 514 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -514 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 123.873057 101.433071 105.123057 ] -/BS << -/W 0 ->> -/Dest (cb24-1) ->> -endobj -515 0 obj -<< -/Filter /FlateDecode -/Length 4716 ->> -stream -x]K|?1bdf{wlvJ->D$vXNcYKC;st$o)f{z{=Dre/Ng5蔴_>eT*!5v^YǨp1r*aQf0`90JF`6^* T0CFC*!X hq:%C'tZi%sNg`Br: [4Fp:bt`uE9- -]-@W`uE8!9]ԃVN ;ؠtRԬ# -3wLREqoqA -@A8.]В @?9.p]aw`5a2c ӁwDs:>r\4mr\< T.!z8.pQ@չז/ ,V[7`V` \  QfpaSL6h :ЪΩ!x5 IqfT,9.Zjr8.IqCLECP9-p9. [ r\T* 0Cc-tF:3p\U+M0%- ?ض`&9hk8.Ar3p\lQBq\lzs\lqAn 78tBp\ezS 0.i8.Z`%3nvD[,\V[4Ef܂;q:[T4Dh8.&C2VzyYt-|:ͻ2訹Ny7ưTS#@B|?BXlt*,B2h5t4fvZ -d z,(F$܄kgG)`J ~`0˝/5z=5i>L'R>~eZq>.Lr縔~,ߔS+(z/#Ft/APV̆T ]fbG+f|dGfDPzeL71 mFSedfIm9s]cVLo|_AjT#/ѐ&rᕤKfqW۶A1{7:ؑ4뮺g5+#O}|?UɷLz6B1Y.R[cdͥ7ԗ]iu]o>mdjKu;>Az 6y;>dۓ~ U=V>sY-,xy۟3C%䓏V>GEۗh;~ej+OMV-VkѦ5o33>m4ژR˓=+5{SUX]|nv9byoYws˨7\k)mrܰƾo³*Z[Ck$.m3G>\ċWzdzwP֎]:}}޳víRZ߉Us_Q{Q: nǿ]uO)Fa*"Ŝy~z: -[u9\vpiՕ:&poV ,ɦ"5ٿxJ3Pwv-ʼssL#jwD:);O_'Wvhz7K8~W\UL!rŶMONRܾ3к!ֽ=v6ݓXh"i+H"[߷s8D3wb󋚭 yMv#D-G -ѽ7JPtaP=)>?qPgtSY,uszWNI֋xs^=-n̦ݨ{{R&P=>Mvd1|,6]{ 9ҺXy,'$fӳOʷSݕ=fzxaэ?xĈ. R9ggr㙎5 BM -+9;Ω=E\O.?IF3P'F1&3ۊ_Nta SLefD'6>\8Qt7ߦlt()Vɥ^ raӕ˦Xlh괥qW,v)UuELGҁG\f릓UWݹ%Pn/KEU"teTRR1h0$ .trbMS> -%kL-_L)P!7<#hz:#BsH}-B^NX/'Զp zPWfq/EJ;04nTag@'+T@}U*F.Z@_V%ϘK'ͩsͤUUryDR -Ix'6ӊ !URJٮTV a ".42hDeq3i收*Ӓ.y|/,> -endobj -517 0 obj -<< -/Filter /FlateDecode -/Length 4933 ->> -stream -x]Kq赁+ /8pn#FLW%V9wpf0ӭ*>ŏW?hR15EgNĿZ8yCןH`71\.o.yL9_IS VPy?h|TAOhbΒ -f۪"p9yI31IP%a]v0D$GAF)QCs:IgR6YEt4)Dty -!$lYiIa)I[MQbU;Y%t%Q[TPZe;u:bO*IM+0I! -:[Yot8t ocJh54ZybLt%0$ -$01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq$. l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kSXdu8*J\FF ɤ$.p]wM 1h%.p]ik (Gxp`%.| ,wu'iդSxN>Q'qa˓!K\ L'̨F3jK\8L&]Q'SwAKF“J`Q'IK\2P x{ wVUa-6 @a+i2` -IU=,J,qAҴ)qA$0I8! -6c dB>Q&\{ DlqI\z6' - -$.@D0e[\E\8؂HQ0ٔsDW%]0SkQQ݄XK\Ԕ0%.O.I\3Nₘa dK: [dK\H:%.H  UfP`ZtN:3I\\(T+M0- ?`&9X$.Hr3I\l1H\lz3J\lA'qAVa0Y8tJI\uz8 0.i$.Va%0n ތd[R¢!^{?{"z-D&` ƞF֣:aP -0 Zf@lh-b*?}L>}d#Ә~^/Roit|k_f8 '<ӽvݽPظEwUO,_kr-6|yejF7O?^~i yUUIqfC<-x%`;Ax7;p ~|?Ydž8]Х;RtIyqyݓy *„zu{eMZIfE`mfGv,#}a#[wAu\C;=ĩqB*7TNT:#i;LG|yt#JRG -mRYdKCz9}l%/˧_QY>ۍ{w9yYNКV~+RM;Ei,=OQʷ'ih%`mץl_ u/L6(_{E۲+Sec{CiWVF-s/ |}+eJ}R|`|ĹsO#pN\nnu1HQg|=FmtX{vVЇ~X5V>*QӁv>CNy! |N{7C.Dzb -sTC8Aަ-<(_vi~&ў{}GI fdz:쎇Awv>md]SOp]r;~Xqw`%e>^8c EN -= z\v/he`tJ瑽CzJ`gT!$K}Dɴ7ܻu^"g=j]nNō[#2ҳ>8m=Vifuy:PF#S9wdghɇՖmIr-<;2R>ܘϼMf;l]9yd'AY7;#=rhS,q|N8r\ң]ӏHqtHM|r}h1Xmmlx|8Iu5.MɓwFh.2sCzǀs0 C<φ̤9tԚ8P"y_>YzGs=sLʻ@9~0\Cx wT` -\RGsTnF5XMxRswbNy:݉!Ǟc=vKGX-lx{~=&~Q^#j3e =~sywڰ"/C|=eۍF>x6>۳湻Al#\gCl>7&5#<2*V1fdCqa=]zw=?|n;4;u32Pa-1ߝ?ֶΑA#I>6|2ӡ8ݻ_9t}л+w=ب cgwݻ}C;Փy Z X?xX=᳅? ,F=^ְz7h֣ WG]I?`9{. SwrՖC4϶ne~j0ICa>P sav8[;@0?;W*χ(AV~=Y܆M7| 0NdҤ h5|wp&eݦgGN&~nʯO(z!5tV~Q -} -+вr8. -C=BIy/5HѻUf塱<]it _:)!=nK<21y<"Fknkbƕ\}Jmz* ݷr84|z\Ӌ\*T+bl+cnH;:Z;o=)_ f寗y3z!XMc.}_V_F50[Wb>ѯޤb*lÆ c:0v=^SƠiw2i52mb do\8z^\o.S>%_Y}JP\ -sle&W\O;b,KuO*[ 44~~/&:HڨI߸5d/9v~Vec϶ Z($RWeJD2UeXm -%[u$z)K=y4'z+aʭ3^l > -endobj -519 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 423.873057 101.433071 405.123057 ] -/BS << -/W 0 ->> -/Dest (cb27-1) ->> -endobj -520 0 obj -<< -/Filter /FlateDecode -/Length 4780 ->> -stream -x]]q}_V`1 y00;Fp7:9R3nUDK -iR1/'5EXD?Lz!Oz_wG͔s0ڟTN1ŨP)mSASYR q3\N^R gLT fXUeav -f죠 -vh!9kS@IgR6YEt4)Dty -!$lYiIa)I[MQbUŠuKJv99'2t*t3O>Y$֓6ÈB'( l gQ[UFY'Ɣjht[eŘDlAK `lQ1H4/I`b\6N"K 'hd?Vi茖*]j0rElI\` lA -Y ,-XЭSYK\`N qL%q (e ,8ׂ;%. ] (qZk] -XuZI\"-`d%.p]Uw1 8 +III\&)'q)@ cJ\k28q&H\L%z]P=tJ\&Dӟ0VN9H\:D]tD <J\$q8~Œj$.]m1SK:6YI\äH\m -uyR9% r,sL.bGVgM3A2Pt^>|/C{>,AW<0t_K;Z48we쭜1_7nUc<[=[n#6? -jkѶX KJX'q$̶]fL -c'k_!Dxg)-Qe+y*{{ýn|3 >ڙpH1󍇸g[U_㲋hڸd^V\,?vٳqᇮxh -Z/͔U2tI>Z9Z7bHwC-=$GW'j,&Gnn&Ȗ7.#u_!u#t_ EdDy Dؚw9"݆O2>㵶o2'{;{ x-mZnO3l|ƣ |Jks,ն;>nY\Aqǝy t+'C/5uE쀄VXl/p\s4}Wp:'߾?iLXEܢ#(h`qO/6K4-yѾ\]9c$7K70/ e7s:[WSvOj]ᵻZ*k{_l$8?ټ`ߝ+e+;{CV-ݫZQ1r9ͬ(lpǍh<Ol2t?KFi|b_Q/+Rs,/;U4K?cd)ԱT8zů'zG!&Sn.ǔgx34 5=ݩȖ_+^Mz{dL a/qSbB+T.6ڣB6yi5; /'TkG(;բjdהC\'At9 T-ڡ3#*LH5 tsiTlRϚkwS:mj /.lH6F?@=PZ%s#k#_O> -} -+вr8.\ahVaRoRbC)zKH?le#qyh.t tRBz"ݖBʚcI5XuC]i\Ʌ7(.N߆*^+ ݷr84|z\+_\*͍b~tQm1a7 ŝF_N9>Ȥr˩Lsz#XMo0^> i~NyܨqBg2ze)_Va6Lh.֩ m7U'R7M˅!]-kGxZ92o>a_m=9Tce+*a:ۧ3+GO:2CVa-$@JZӓws#v,/Y$p-?;+ {^oPGI7+#i#> -endobj -522 0 obj -<< -/Filter /FlateDecode -/Length 4848 ->> -stream -x]K8rs0=^a va_PCTY5w!;>BǏRWVSzE$>]A8|tןI`7/-)yHe1UJ*è!hW.Xmת3lS udTfYAYN3TrQ) ;iьN9i%|L: -#|)NENgaKRq:[Vr:bM duE`8]-]-@WduEz8]2¥h-KZ.#9RaD|`tx-H lt gBh449آu99 -KMr$6ȱI G:9a} -ӊ##ac`eu$qѰ 8.0hk8.0`[ p\`@V&qZ< 3%kP.8.0\t1kЮs\`*qQp\`Fqbi Ы8+B(9.]wu4Xvnj'5(#Yo -q;[@`N PpK8.p]01cl%TLUP-Ό[P' xwAp9.p]e0Ss:Ir\Pp8.&tY]2q4`V8. ?8.]w`5a2cΪLR9xWʐ8.]69.:r\`qV<>I:/p8.buqkL [ [2p\@$ ` SL&b<1*Zfu:8. -LŊR"bs\.q\3Sゐ` -D9-p9. RD [ r\uD%K9gF \E 0Li)YlMp\`q\&V[Ĩ)܌[o -8.H r9.C'%IEěr\qIf x!3no -. --p3nI7N,{7#p3o£g"ś].ft]x ބg3^)슁:̭쒁b -욁R.LDѳVT]6_cv SD93Ȅaaט%3ɦL?wy)XkO:W"ga4080uzG{6'~Uc 34xϗG֗˿ HiZC1ÈR_뗟zhKDiY YH*dשUz?\jYg&slhiIMiePA뷹0pNe&ե J46Mnm;ULbF3%m4 (]E9]4&K+ͮZr=+{LPrpfc[smfl#.Q][q,m!ȺetKfS6hi ~v cvro8z&\\0Ia+V֩i2 _Ղ$?w/d2ݏ?( `bs6+g$- 0s=d?MSގr.Bksqdr3.}!`W2_Qn2+h!m.PD0]}}94ЗëGDdoyZOE_Qn7y؟p.ͽ[Nti] ®SҬx/hp4 pfs& -RgLnTm#Fl—q9rkhW|FO FYFv8`=I٬Nvwy2tz*zߺrTM1['+Rr1=~ȟD|HOX ynCGO^=u/ 3Z:䲮qQrYtbQx.ӡX{vH.HEؓ=Q_#S)2Y?}}&nۺIf )G޹<φ' ZGq<φf+bvFF:TzF1ߝ?um[ʭu[}rdCu\ꙏ酝ݍԊtݳnuܨ?{Z?%% s.FD'<9^墔wV:_s\Zuchצ)bmfl4^3:S"7/o͜-_WEeZm)@yℼ|u6׹>.U>\`x^~-T˙Ym͘c=t<φtp8>ֳ[fϣ*#yUO-ݽi|38=u2!kOhEY~Yyuquk -婛#w9)<ۚOcth=c !g άtO^ӽ=JR:ِJZv7xqO\z-UHi#28cƉr0f j[qØx@W -n]Amu\}.;t9rZKđ[yy;5[y4/Vuq݆-CpEhVs[gb4{xV}U^zx^sV#ҕ"XUMV׍;T?D6Ms's_r|Q -jb2.'M~7XFl'$e-˪n Ҙ8!T FCw%eeId^SŌ9ZP:|5TVӶ[C2Pv5EצMXMNu_uvAfRzE)Uf:RvĈnF,E[tfwF;OXdkT1ۅM7jO*|3A,, nHSbAnJx8[Gb_\`RBӕ[Q64)gLGEF-U*%VHўUBc}e˵KP1۷{&=nM][l!횬T#*& -+SbkbW7;]NʼjM+wP{\Zn"͎b~,4ukufHgq^ 2nƽ]rMz}.ץ4?{4kYBWn]Oi"æj~Һ:kme#RUUU ]kN+t2]˸mh|oڄ=rq+m=_I98Mgڔ|%mS:VwqӮ,[I+MO۾+ ՝tnm.|]? 4-a~xx}g}$^ｴ^I+RO9&oZokZƞNN͵4lsWjlQi(*]@&M~V%_qd[)TIҷ{6{ůReƫޒɖ>wږٺn̶2l37Tln!{doR2b{&j&EUF!^lJγv^!)k'}MVٌApyޡHNJ\>[%P; e^ BEz!7kۂ Pn8_ -endstream -endobj -523 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 522 0 R -/Resources 4 0 R -/Annots [ 524 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -524 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 713.673057 101.433071 694.923057 ] -/BS << -/W 0 ->> -/Dest (cb30-1) ->> -endobj -525 0 obj -<< -/Filter /FlateDecode -/Length 4792 ->> -stream -x]K$9ׯ3&~?$ @ Fp@kAi gڎtFVe԰ite_U.}VJR/ߞ;)zꢨZ8yCoI`71NoN:lOrv)FUJi+b4>'bΒ -f۪"p9yI31IP%a]v0D$GAF)QCs:IgR6YEt4)Dty -!$lYiIa)I[MQbU;Y%t%Q[TPZe;u:bO*IM+00H! -:[Yot8H:1%aVY-03s ! -]l}wۚi)=N/D2V>-6e1DI&h VX# -(c'|Er?pK-V풙dI#ǿ_?DV~_o\:-~26^&P>-:uh#.}P0 ePӠ f~mn|v5kG9kPe JڑQcU>_9q@=eZ?f yfu\Kx ֍N=XeUޜC 5}ta'43:OFwKdI%zD7ʬDž.<~8\bU2BcuדKu -cs1^:B|ٔŹ<%lny:_ѣ#W(he@TIӒ%[͈F[,ƐNKC!r&Cjzy8;8Xِjnܱz2N|9J\-v9`׊1qW8qa螾 -qw<bo{Q`*LiW74ߑth~jF7m#nv9VĹ>V3&Un״?5xge=Xw#O_T]Afta}:_nAF9:φdy{?H$?bqzzng~G̨ul6vӣOmy:^i75ZzxdV:uﳡb䨗3+h3;ml7eoLeg;vPz{ y:xSO Cȸ: yUhcu?9X{Vx?q3&7n=؃u zFugO7W5첷! y jBYԖ qVl>y&4#af# -O7V'5|3 <~]+?<mIe$~eCCk}=yx ݹ'yw6_oi'ݥ-:zSEvYO-˒_^bK\V^>:?x|Zfn[eN=_G3-^ -j=k26tV8lp}ܹȵ@7vO>:vS[HveEzZcflSr&d2/\ui#oj_y꾦{,HK:ږ}NZ!ee(k1}U.8ņz?E&=R6uhS/ @hWRa EGs|2z>ѯ+vð1 gY4ˍmZƸii);Gks߱qlOlM͈+*Mtkl骿?{[?AqAg|;{~W <{埒G^םc{j\~Oөb1Y.`|)y470B_ vä25t!ķL/v[46O>" --[]* sS36[z[ٛ2R;7rr(=.D>oզqZ8ϻd0˒C -MQǸl9ąjp KRV ok:2oCef^6X/o:OyӸ/;uGڮϾqūƝ !,FF~6HV1~A'd<#6?XI:8FFa5T<筅W?7Sc~9K*ziPM`u UlO:@$"orzs|G 峏ZY ]Kw~ηk ,,ϳܴ#쫔>.cvQ5bk=e^>Qa3ߝB9?P3dUH6t9#b>әIYh}ީYZNWt/8.ߕeӰo':Y b 1 tȬ x2Ny,}z7Tjt"W4!jݫI/b:>Mv -ʿ7x`xSbB*]Wtis]f:wf_˚ȆrBvR:۬6UU}YfTnR_Kqm$Rilz6jt,LH˵ rKkTlR)65 {"6Q\iJ 7f#k3N> -} -+вv8. -S\F -ߤ[C-mIN=p Q&MRN]:dZj-厓r.ҜMYjF-ٖyN-L,MzI[e۾ݺm6\7$Tj~S.gu]T);#:mk*q%U:N;$uᘜ*j<ل7(mk~\-+akӜ /N*ېe]FZ*YJz}KTZ~K\9c}R~<Γ -endstream -endobj -526 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 525 0 R -/Resources 4 0 R -/Annots [ 527 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -527 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 210.123057 101.433071 191.373057 ] -/BS << -/W 0 ->> -/Dest (cb33-1) ->> -endobj -528 0 obj -<< -/Filter /FlateDecode -/Length 4698 ->> -stream -x]ˮܸWzs~,L8 ";:'~CTIwE[UX"%Jg7y-Y}|:}>q ǿ!`P3gcFS(\0 5u?9gG% Jaο|*qCT\(Be sNK`(0NK=W97 -fh)=0Ci'\`tBS*!qJp!$p$t0JN -f}9脓N)fFPS: [Lb֜t(8-;El@0휢h@ô tRPD8l1RLl蹤).P J -l V (.P[ͅ@pa&@q -(.@uU[ xWi).]#S+ 4xW (.]t#IqZ`I9+=htHc胊 ޕ@]i@w8 wA!v` IEqN$ xW D[1ქwGC̄@(.0]Ч0J xW(Ԕ+d.Cq 01]RS\`%IqFa=9 @ƌw1 ,x(.]:آ~ tDʸSP:.haJ ,x7XS\`Iq,6p:pl(.p"uE;MqkT8 [8 [2P\hO0Ak V);5 Gqsa(`.<:= x% `tBS\lAWC9N6t/a A eZNqFh%QՔN8xmYt).@7LLI` hOl 0dR[x/tS\=l\R\l p-n2q8 _ (&xD hb࢐:)&؉Y" X盞o£'C>7.ft]x` ϖsqh3NOF 8`l%C܋ʑ1s$2h31`XRp2lѧ:De1ӻxBûsL-$~O==3Dҟ0 d@sx,ZA a-y.#hq E#10ǡxGţ9[c:+wfy`HzNh52|p*&ZOo7響ܘވ-owK]I]FS=ʥah~n=%c5.㱝ޜ/Tw:{{882px܃B,[ \Ø~bK?]8R(m2`IUKmm͆4\;.3qt\/_Pgi Jx++QH1s=WnIzv3ᐻ":DwBf[@?s44uwnx3Pj[L㯶yuLs -G;o ܪ*44bXa}3ue'wѵ]R5|x)Z"vOt] 髍- /gBig"Ny>e-'ꘀڔኂsӼ4mKs(k{JQ].{gDy>onk,(>'(5W#|DjOʊ3u%&(h1>Y?OqPft3=õ;*$UyGx녿>wg!uW}"|T^=îppcyqǕRߌeW 05t f|JbE[τ잭fq kJlbhq^9lN9+q ø}u3`LyhO'4Y⺷(^"~9Že5!֚Nq?y>)a]@62?C>yܿSt51I?DjZ0!DN+xQLG6blrB]-',7BJhB^WR'{D-W-lz]ujV9ׄU]AөRJe2*dI)sNr"ox:Fcf}jqo' .tr"Ӎg3\NK֐jR|xB6(uqp~N6@jk+șr2:"~9G6+IЫ:o{^R9/t$;STa42C \9*ľJ6j@hWV%˘KxNSH*.$"IeEF]G -Kd+b2;M{*̊ -&mΗZrU`7|^M} -)bhW -0B}ĩfv۟Q#i22U"|[{]?yϿOu<:#Y'wIM%"5 yk]B) *RXfJ1+KSّmʀ}=TP%pP_}ѩ2$S(&-C:ZVqPUX613.$W}_MbYAFCUt l* \`U'֢.4L!{6(Ԟ/4_Xf£j8NNŵГԗlcSlRh(2]@Ɠ,%-UpŞ%}"iSJDSM#^TvL gWֹٗT*eii=W!xd37-}皧BPlNZ :xk!:nB%N;KBs0wx[0N2Jg }@ -YdH152Q>tqh°7>np CE<= ^3Z -endstream -endobj -529 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 528 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -530 0 obj -<< -/Filter /FlateDecode -/Length 4925 ->> -stream -x]M8r`a51aCuv.>%!*TV״ۅJE#|| RR_~~/9=cpϗ_.j^_I(?7V.N^g8M ׷ .y'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kSӃ3z -),"t:Ig^K<|tk甤-Φ(l*Q[LVEb,l-*(-鲝|NΉ J1muF'kzuQ-A,`H: [~$xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8Dmѓٝdr &_SV4!00}k41`CژYDlYuae+L%c+@SKR2+CdF-x5`Lt^w6Fh0jeHku?߆e -Q;HsyeHk({9{vّG.e \jKc9VTц8=h,umȘN`sy8Ӝ^yQN_xeKL9ϛ##f98!*>xFtKegNǺNӍx ?<φ_sK]yiH"-q:ۮVWcvg#110n,:}^Ym!SODdiM*=?ۿ' <{4#!<;̇IA?-cprL9;݆Ưl0ǘbp.s?[nґSyukUˍBav^(вv -sTC5l7d\ <.Ѡp.!Ô=L]n!S[r>UEv豣[x͇{w Z=\{|]2e!Ǧ_vuL>@x'ʲ@tV q\6w.ϳa?*}j6~|-<;2]f u۴oV|֦HǴ+b9$(fpGNls{gh(sp}K͘A#\C?o=lCtCox1 FҾ]Y䝑{;Zo,8u{<9tԚ8P"y_>Y|G -{缙wssy \zJ;3oc#9Z@}㥟j@>iO -kN x{7BbF=Le|aDw*scѺíŤg?x/K=-vgwWjz`W;dcvxdCxgAC{>[Z7JE+\gC-P58|8U} sJ/GyO!տyi{K{Gozz60*V5\Mr5A&͸_/e3z&XMQ/֗Q-L֕d "餘Q -۰aBwN=hh1]Ϯ:ה1nZ.݇Llt3@xo>aϗ6%VpuOWV$(iҡue/-[I4דw #v,/J+X_=^ɡ6jo7.m #i#> -endobj -532 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 450.123057 101.433071 431.373057 ] -/BS << -/W 0 ->> -/Dest (cb36-1) ->> -endobj -533 0 obj -<< -/Filter /FlateDecode -/Length 4910 ->> -stream -x]M8r؃51 `Еӵ ~AdJ){Bu"H*x| >+_rzJ)Η_N¿RbuP?7V.N^8M yӿ:l/rv)FUJi+b4>'t1gI3|t]"p9yI31IP%a]ZaI*J+ءR(tO$SHdQH:kZ)sg%-^;$lq6EI` V:bR.ɂ.+:آҒ.䜨Щӵ(?dtZOش3 -N -QϢxGҁ') jIa1щ:K `lQ1H4/I`b\6N"K 'hd?Vi茖*]j0sElI\` lA -Y ,-XЭSYK\`N qL%q (e ,8ׂ;%. ]L(qZk] -XuZI\֢-`d%.p]Uw1 ɤ$.p]wM 9h%.p]ik (Gxp`%.z ,wu'iդSxNp˓qab'BwPY Q&{ DlqI\z6' - -$.@D0e[E8؂HQ0ٔsDèJ`Aע.A1 K{)aK\(\f@1L M 2t Ȗ.tZK\ lA4(qA2 ̠$. -$Z9E$qAraPQL4&$.h%.MlsDlI\f %bؤf +؂O€Daq蔒 q`^~3I\~[wJ4z]c-z.^\mZDO[_iL)?a]vɎ{l.}69* O_/l,G~fc>XD8 *׀,7 &rշ˨Wʸ,..1ᶋ帔}yW[[[/36cSڮmhC|.Sx[T? ;˙<3D<[1 ;ʊFr*FWLn l[t_Y2g}۩Ǭ6amӑsm"vDy:9z_WG@-Y6ڦgQ[n-eYׁ Q$my: 60+N;r ?{L@iMPzӡt'<`# hKanHb.#t%:]s0Kènղ@ B_YLw t/󱤣:uQ z}~I<6 ݰR9yeգ:Va=c櫻|f\|cc<.|f`x7?X<nGMGrcw{wyewPu<RwaG1N`˚m wHP"<"wbU]W }y_:φ`~7r -b@Y^v5d[=:OޝuB7C=VƨDoj@yǃu;WN/=uE쀄-ˆ@n?p!GsI}'޾?i,ù\:φ\,~m(.Xޓ" t}݇?ynԲb܃uͷcn=}jv[jYV9]<{@#d}<:φ-=)]9oUrH1:O\K$Dq:rj]q88f=Ǿ^b{ӡw[îVT -Vf6ڼ{yǍh2l2t?vJ`C}|;z绲^ өoN| U<%`<RoC1mn]S1:O۱k%{5ZU -eot_.W]3B5{]׿Bǂ-ԙwqVl<57t$ GCRGRTwe'ٞ[(mjueVƵ8.7'u.>V|;Ƶ~SzvƶŅK-zu]αsqtyѢ^ff96k\cַ~-CG^*^82Ya_?f=:2p7\̪/eoÖe.GSlxz,}= iu;ңu&픾Wҿ[ve}q%3/kmr&d5;hJ|s+b/[O y~2l6);gxffּ<Ƽ"͌ktoL,\*eQe׃0:X>+Jkg?U#.G)zlrfpnnegD4Io[8H(ؿ, -y)S10u]`6/y83wwvKi3Rp_OSM獚vRkr0,- WP"Ntۉ^As}UpZ[NE.LǒGk5z4S-GO,Q3k1^MzkdL ao^qWbB-Tt]l\Gk?Ѕ.l̝NkG(Gզdג!I]NUvpf3+8fa@r\$[ZSJj#MP h1{)Q~\)@iqcwm&vG\|Zn'ҥĥf *|5HKHQ? &^:Nb/ˆK0K'%'mۈlȘҞ{ ^ Weݺhɶs8;KX2 k7%m]ۭ]W3놄^_|;s! !?%3Sj5\!,]bΝ\gHj *jzly_/e%vRCUfa\) viH/&zjTZP@JE -endstream -endobj -534 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 533 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -535 0 obj -<< -/Filter /FlateDecode -/Length 4829 ->> -stream -x]K$qׯM|Ȱװ``0]3-5_0̌|TuϨVӕ|D?FYL}UAHz1Oϗ_.jN῜bvopW( N'g0L׷ Y\.RF_b VP97`T^Ŕ$p UfPNR 2& -3,mת3L$`N.*`6J:t %у$QH:kH;-wQlqIiI`DJ1H:[JtNt]Q啖t.E"QS1ĵ(7htZش# -䃠3+DlqVIga Gҁ' 1 -jI`1DlAK `D `/H\# )/qO -:|ve:B$.c=$k #-p-%. 1I\G ơSJ₤#MC`\r%.HV!D'd=ǛADEuNS-8 &IybI\x3J\7&AӢmzn2,f5|g4F_Y/zw50{+y:]Xz1k8س>5W&ˀ1@?|o?>^R.F ">woe҇uY__"Sz7UMi҅1oƴ:ڑIg]YF=,3ϓ6SYgF~(_O?m_ۏͦ .*n;7kkN'üWzv5m|Z-xGc?GfQćftGz;Q!hx x<zʓ+,Żez|9۴卼L>VOg Dr[{c{3*fik??鐻|gOt 4q|<}[ʖYЭ]Ny:7IR~?>{H@i u49mպGOktF'<[Ɠ>\\Xp+1ֽג;8޲w~}QUeѧ<C-ON>D|~$Ny:|xXqWwqa}|>v,˷j9ӷԳm 9+>tuf]Vf{I5S7\Gօ9)<ۚOcth=c ͐pgVx'O,}V#{f v+[gou2!`5uF$[5@OtH~WW$nvdm>Ol9qz=,+rBRQԸSc 5|)4a~}yΪ8?{9reg4EVcu~UqІet4p ҕƎʒ.ݦsCF_j*"3sS_r|щnf.*)Mv &I1 ~Bv !-SZ7cQOGp~WIwJ"+Zw=%HqӕU ->m+e<k:[ UW]*h>46ojztք; K(WJUe3*U+)kP'AtT)ЙU`? -ctDn*՞ -5UlYSifJYnInQ|=@k;ܘvqTGb]\REZhr8&fHJyMR|jجy#r_YZڮt}{騄L5umkNR1I\+ꪘ)O^]Ltu:U+󺃻6֋Cqcr;-Ol3c]6@ -Mh-h+ f/> -endobj -537 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 728.673057 101.433071 709.923057 ] -/BS << -/W 0 ->> -/Dest (cb39-1) ->> -endobj -538 0 obj -<< -/Filter /FlateDecode -/Length 4874 ->> -stream -x]M$qׯ``@/<5Zvu fdFfe O+# >>,}UVR]o?^~)z%ꢨoW\!$qٛ/7\/u}5Sh3bQyAR -** MYR q[U.'/`3& 3nUf:((%`rA 錞B&FY;ג.O!$->+-:2I6$VC*%-D'` :_b`AxIq d'\X<D&Ʌ%JCgDVV+`Nk` H\`-l1J\`hnZ uJ ,f* ,צ$.\@)K\`)qbG ,X`$.]RwJ޵9El%.;NV'+qZad$.@NaXLJJ5I9 xDL.NV5MfnH\ƙ q2 wA!^` V+q -  j!̶σуUXJŦ6ԺþO. m_`ee4 -wsY_9BqU.2au1qNڧg.|Im{^vM'+;ú@ V [TA=d(<<\ꏐ;"ؙU6(C>"{e0Y?Nͻbo=0}gwiN/~ <Ψz[<2%?{ɛ3ۙQl43[Ox`u8vejzT{.ޮߕGfk{%`ǦĶoiR{)aqe)쿊;`moFPODdot6_bCCkvOyx 9'y-74zY=]y{KڬwHu|~+>R]:㹗 -p,5UeKi-UiΧna17q - !W[N?m ^#^ mv;vẇq-FGuLB3j{kv_s Mrq-OKߖmQX<`wZ34Ka7}0TiWzUҪʮ}0C)Uh뾨~ʟO~Jb.73^% ms"OF][ùNk}Gkh}(qj%bݺ8ۚƨ,Z?[^DNEe'uw |)O{ mf%~\Ƣe 0LD VZD=6n3B^nʩ*!Ô=LmA!S+s>R"mz s:[<ּ]2e!dǦK/12'Iİ=ςU`gm0DPe:eң4'BQa󵰍[uoEgQ||E@z?-6/7׼ߣ;GG#Oyum8Bk9錏=_`xGkk9|$.<R!j'/ҽ;REIu[x=k;|6K3toGk7{.2cG{pL% rnY<<y3)!< -:0~w'Bkɳ_mam]m%jrzX%O'1`Fv7xEpZP$}mMWH'yay%jyԕa P1Mr"rn}ح46ޔVYmeRڰƟ.˩*IZkp=NL:]MGNe ?T3(:,/?񢳛Na9K]q2_.tۍw$\>Ve@qcJf%k6:ЩȖS!rSդ1}Ar)ڄ@{ƻbmPظjkB6ӹ4D֝GQ"JZTQMfQI}M:ĵ~D Vբ:YY0U .tv-SJ=kt/n1H_ƈZLw[_pc6Ż6⣐wPB -+xҘ04NgMJS>h E^ &^;Cc'y@2wftRBz"ݖyl%e.cyDR> -endobj -540 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 292.623057 101.433071 273.873057 ] -/BS << -/W 0 ->> -/Dest (cb42-1) ->> -endobj -541 0 obj -<< -/Filter /FlateDecode -/Length 4751 ->> -stream -x]K丑ȳ~9a=,P3eè10PQWfu -p3A!`UU"~|"8CJ J>O$0At׷ o&X]N>XK{"%8-NY+9l&NaF:آc0.I.+:"T.R%d q N)MУH>0: [tgtXq:3!FjFl:XV[h[d %t&m9mX@$l>TiY1QŢ:bh؂[5Z8.0[+oT…5[ (PJpwr\`@5k h9.0]cwANV[` ¨h8.]dwэ4hUz cXr\`:``uA ,xW;\7rw V{ 78- X 0C 8pK8.p]01}l%TLUP5[ԲP' xwAp9.p]e0Rs:Ir\Pp8.&tY]2q4`V8. ?8.]w`5С2}ΪLR9xWʐ8.]69.:r\`qV<>I:/p8.buqkL [ [2p\@$XO0Z 󘏡V9"5ЩqAV`(V`.%":= xA0:e9. p\HD Ϝ)'x)qA԰ QG2#4撨jNg%3#zA"&i)YlMp\ɶL61au8qAa`曁$a <> d @IqARMm9.@f &xLM|3p\,lqpQXlӔ~ N|!*81E&t 9j2_.~{?/"eOAR[W:o7 0 aHc&vWJ;IOu-/1]?twoCY~;LxߘJW~[ұ\jtٖ۴̜;!_q8ݝccuWBݻP~.sSN ]=(]?}w) /H DIbf60/3Ŕwt_߹YK׬‡?wo2qstMB1d  L._ ncY[WPtP:K<)uvV+Eug3U.BZi ŜC.'b{=d 3y_$IzNGOH|us:u _oՑJ}yNuwnx\3:gGW,[¸y/GkquWiGx孳AMПiL2{j\⑩Ww92Σ*~79yljiVJ-s:ԮOf^oSd,?._Bkd.>K, Ms:n]wn9GwAKnh;ϟ!ӡ T;|eoMoe n}v_ӡvO72YmX, *ru˾Wxy/w9̺og}i>?*9oF{$}؈2D ~+3?}§܃#q6&6tpGyp7-  kb{gD;}ͭ햛E?5gzJGHDB֊yN rﬣK6zdYQ?]ho-հzyֺvZ]lצiBl1h}s:ʓgYo;5[0OMr/& ~%sw 3_ڗtm㦭Xxutv2ՙkw9Z78bH8`Od!>ѧ{=I$mMdi!us:nD3WcE -yN}O<{m2#?ۙl;rh;?Ch.,_@osu;~]zW];jSrM5tH%צi&3pY^prx{g!w܇9֓qރ_W}=i687<kݙl ףƠ{Rt}~n=u8*$5ygxEx><'s;>-pv2 -KOL>YN_k/֓^x@ug/~'OsG"U+\}C*/{X@oڙtH~.!'o͸1~x_m5L\@oc3{ BO=QsT*尌6pΣ߲֦ڠu^ (}`]"i:F ߅BY2?spz`shgP1ٝyNuț4艏\ Ki6_*ִ.Z7|mkvY=TAUѶBW]LS3nExj82϶M&_1aa -0VC9%(iҡɈ8l -LղȶRdmPYAFС:[Y6\E.i[&0F?ܽnd{I [+-FBx ~zXsyk sԮQ] ;9h1Hc6&pm6&恢d2Cɏr WZ -ŧҿ5V)Vt<oȵpdMY||HmMil^Gksg*k67K=wy(* F -Fk"w'z}z γ;GHr- !12(m7(Ҷ9۸--IU4'g!#D0Tѥasɓ -Ra 4|2?-/ -endstream -endobj -542 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 541 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -543 0 obj -<< -/Filter /FlateDecode -/Length 4930 ->> -stream -x]K8r#9X /ҔB'k'qAP8P-H8S)J\ lH\ l q<)ixbx[1> OQ0ycUIZEt k KM^0:M[0U$.R4E\i'[xi-qA4ޠDD^I\$Zґ83J\O*J\iHL)` hBN?6:bI\p3J\#l1H\lr$.H -㓸 )?,qh:$.H:"4$q%ǛQdMx¼Ms$.H[\Q[4%aނo$-&{7p3o£"ǛA.ft]x^\ ބg+ -3Y9⎁:▁b -➁r$nLDыXVJ6P_cyߢC72aZsdv'ټ??]~OsyM)+?BNM0 Lp;xͷa =+ A&]VP6y9SK`\:!F<`xl>AZuQ_o#և|JBp0FKaͶ^ =铍ă]2{&q| -;A46^?A|PbżK_/;i,]~)EYVEf4"_L[Z.]lv:j?Sg/:\lbIkݶ5צ+m`??tkHH*C4oht5ң]uz@j/ 7P\Pu D늱˿1ON[@Yew=i8nBcSuDx  DVm ' N61~߷@emS{wܳsZǴRZ5_oqݮ.]-e:.ek{mr>7FY_=՝˭$e7l1>\ D22_Q[ǹLu[,!J+vp(Gݖ-|#d[Nҫ>;vYoyEgĶ2l~f1 ʝ_lrSϥl6?.c}wvd4,0K]aΛ-:tnCmݍ}S1; B)s[viN_1k2jn>ǡ件~׭W3YǢT2~e}}JDa[ژeiz9j{7奛]Ha$ۺ,ǝkYq;єAahD8k0j&ݹ<φ"g*ךo![oEːw7m~=-;(N\'AY3#mEm^'&v(+ףR6 6__/{QYѦrtܧz=Ej0#\CjYAF3r1(YH\@}2eοDmVTxRة;>tȻC#=A_7lzha;_92C =x%YGfJ*~><z_+|FZGM{3 >m4$-yFu;myĞl y޾wȬXc dCmG8{A3=th>{7BZ+bfF;TFg1ߝ?ek[ʭu[;ϰP:vsy~YSe/==iGCA@ٝץd_=ِj -{ ټeϡ{\Cԏ[p{h=¥C;.;Kwwܻ?zg}xe&GEi2bѤsqbݧ+>(ǧGzw|fwKc9) ~'Ǩ=P{OU2ZO} YS0c{~{bo/V{OrU<ِܧ\Fvuwp\]'RvG>NHQ:2I[|2!|3zdruk*:(ȿ{Z?ee q{V4u{g#y}{IRv^~?{<+"#('<Jg.m(, k]n.w=lI'.ݺw8:AV6 u/p몯YiupP-8OWlp; -Iy|Tꎸ IC{z8(im`%>m%mnp~/ӲX6-H/ksךj9_A|dbIk_.:O't,\4ۅOh'ALԎָ#fQղHד: SSZ7c;΃_ך?WZ]'*l>;nX"[1^Mz)q˕U ->m+e+VuB&6T|*j:߄t7% p oTkG(峵KQw2ԕu@ ]M̪FO(jT ELH*|3AOIٗݺ#omG7G-b>nFx83..] - -zʭ^wOE;3U*e4UHUsם}ez@Shi!TAHϤ[S[I.!*yźJT셪U(NWS2;Znʝo8ÚJ#:;-/l4T|0RO6@ -Mh-l_"R>I&˟/y3>[^/_ʁ:nTe Su%W2xR>RutBC7-+h1_Sˮ2^ZvbSkzoC/VGcҖI'|m -}spζ%+Nږthtqˮ,[ɀ+]S?.:7/mQ[f,K}JwOb/3ګֆ,ү/c!!een䴩\ Z]e[R*Uet*Zb(6%[(R>Ei׏JD׏ߤrˊW%[ 9֩Q>wRKil[7.k5C|LU6);saBJU~Έo,Ԥ56kރCx#PJsw!){'}MUA&A+wْX[Cfg(SޅD2p߷f51Ai|h}# -endstream -endobj -544 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 543 0 R -/Resources 4 0 R -/Annots [ 545 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -545 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 573.873057 101.433071 555.123057 ] -/BS << -/W 0 ->> -/Dest (cb45-1) ->> -endobj -546 0 obj -<< -/Filter /FlateDecode -/Length 4939 ->> -stream -x]M$7rׯ``` [ /`}0|.%-Z3IF2#jzFӕ,>+|_rzJ)ΗO¿buQog\!$qٛ'7\yL9?)T*~ Ĝ%UEr -f8cJ0úVaI*J+ءR(tON)lh$SN{-BI9ҒS8 Dl1)ZIawKJv99'2t*Ŵ'UNVaDBt峨-*#,lqt ocJh54ZybLt%0$ -$01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq$. l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kSXdu8*J\FF ɤ$.p]wM 1h%.p]ik (Gxp`%.| ,wu'iդSxN>Q'qa˓!K\ L'̨F3jK\8L&]Q'SwAKF“J`Q'IK\2P x{ wVUa-6 @a+i2` -IU=,J,qAҴ)qA$0I8! -6c dB>Q&\{ DlqI\z6' - -$.@D0e[\E\8؂HQ0ٔsDW%]0SkQQ݄XK\Ԕ0%.O.I\3Nₘa dK: [dK\H:%.H  UfP`ZtN:3I\\(T+M0- ?`&9X$.Hr3I\l1H\lz3J\lA'qAVa0Y8tJI\uz8 0.i$.Va%0n ތd[A˦Vp2. -1]~0Q)aQ9|w&GD>h*^ody>Vۺ5SR-`kiv@Y> -ND1il6ʈו[%O'bż.C4Ow?A)gF}].7n ]=~!ә2f/7r@JARoK}o벩.*,е+e/l`x]cY9lbC 4nNIձ,/', HZgw-]z',2.Dc^ y6Paw~-ҹw?lE 2*qbH9pKorkz򰷋ά{/ZVVjC\unOuzjK_%ݽ V]3ӽm/~2;he׬Euth|u/Tm˵6djA/?:: -;mvRC9kE .xhΛIaLcy[h?GSE#G[D6#"kGC񝧇IJ[3<φHs#&ܙuYZw!xk/촍eW;} ={#|qG2OZhvĸ<sWSNYGڮfa{'#sUN_gM<#y}t==;UWйY)]X;ҾyLzpu0!\Hms98|?ly0A/Oޱ={бU$ʸҩ{ #GB8U2E-|Fi{6R{KFโy s{;<ӯ !^ꀤւL6O~=bT&ARy:^kN4ku{pw~{zzmճZU zfFs:]yvuq: jBY~gm#Y[(=كyבnR`Hx^jTv|QAf\leBګk26DH~.>ِǸVXn =e5pew^7C1hx{ĕXۼ+1.%Кk6yy 9'z7%-x4/pq $rF'M 6ӯho#O:>celwr`cetbf?6Ul< Q$&^*ᦒ7%$K$I]VKODR,sSPz@tErVoDݥ%J-3YdQb"ȼ<[ڰ_NҫA*Iz9ܘt0pRm8ZwrR-QtJ>\_,)3n"ky}*b=?O'b.U+鶜 &81%&H|kn52P~_ѱND:W,3識Z&0iUh Ԅ@{ƛbmPظj#ÛB6ӹ4D֝ׄ]ҋ'jQջF5eF&5eI]NUv̦gFwTZ\ IL[OŖ*zҡnSs }HbcDq-m*1ܘr.~?(+Bm:^Nj?ahV~LTᛔ|ЮA0WMv:Nve16r餄D-uJ\1WyźªWrF. +qӷJ/ }+Cw.5Fm2WLlnSj] a .4^u6v*G- fSa|\}C'wz<4n]LFJj*lÆ c:0v=^SƠiw2i52+|n {q\sUe:ۧ3+WO:2KVa$@J~ǻR]삅tii]e, B`/xNJ臇gbr#ڛK[HOr֗mαeYoP+˲g[ӇF-cIS϶$RWeJD2UeXm -K$z)KW=IKEK@9֩ŒII]Oil[[]g3k놄oR>9ϰ !?egD LNGklyJ!C*ĶJs}dCRNxMY&<]WklYMP9*o',ϋ viH/#&zZTZ~G>)?8Vp -endstream -endobj -547 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 546 0 R -/Resources 4 0 R -/Annots [ 548 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -548 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 127.623057 101.433071 108.873057 ] -/BS << -/W 0 ->> -/Dest (cb48-1) ->> -endobj -549 0 obj -<< -/Filter /FlateDecode -/Length 4840 ->> -stream -x]Ks|?1bdf{wmvJ]kiUQ"?~, -|!_0r!zg.?_bv۫VF'h?hw .ϗwx/,P :F[S 2K&˩`Q*03R/Uf(/ 2ZϨR `0F+F')9Udu:zpH+9]s6p:[lYb1th-*x,uJrfuQ$-N`Bq: [ ~8xj3Zn-t( -|-;0%p$L0c` hx@ h[qh [ F.-: -HqְEq 5"J 48. \)8.`\@rqjp'9.`]m@v  F - xWkdu8h4.:`eP! xWa8.0]1:?` j xWY7swUF9 #Xo -;[@`Ni Pؠp\`2bc4j!: ,xWthqfܢ\w1Qi ,x8.Q+5fjNޕ* - ,x~p$ 0 R."q$d<8.q -5+ V[tPÖpV+$zӁwޥiI0p8.p {q:| xe:bu x[Rx[2p\`7<- >0"`!Dc8.a=VtN Y]Nz 7bqRC?q̀N |-*`*g$lq<] (o゠VNp\kI453֙`@"&Xi)YlMp\Ŷ,6auE[qA``֛(` <> pơ(֛p\qIqAM,q bᢰ:)2&؉9آ :Gq 7ѳ!@Mφ 68xXo³k=3^h؈Z̭l@{1[y6f @Fb0+بU(` ,8a>!*8x̙MF ﾬ9j2l'L{)?BJm_a%n_*=,+1Uc5K0 ]f*bO9 kLl`JՃR9&`BwfyEpp -計D12 -3K7Ɋ1T[.|P?F뛟._oo>\{$}'B1_+0]鯞3nN}$U[<0_l~_#<5vZvK}=e7:-fgll ,mvmIu}7sPʠ$ey _jL[-8#_iW9O8i1a/mVw_N& LǷM[,t2E2|0鰬64jy06M}T]9 򭱘˼ R^`e}?-s:,M^nɽG5h/=VVQczj_mmT6ᓰ9@Xgcؚo*ĺ+r*:;/FgV6Ud"E6{0I[vM J;_?^:'Sw+5o\͞H [wJ_걬YyΕF9_#XԑW_.<[GIh ro!7ﵔ}۴>bKnm)穼x]MԨGsY-,x_bmΨ켒>jWEP` fǯ쟀t+"lj-jlZFN>3O{JzJnޜgwU#T0b9b/]޳z=bls19r}ZD8S;uwݿ?th{1#?O3.my_eqkˮBMhV=hUEً95jtem|o5:t{Ї ]&wT~|adӊ-VokNGy{TܷM>Su,ڴOc`(ɖ '0>x|OXkz݈ bW#_緅J9ΗlMN+z`wѧ{3Y$m{jdV;Ѱ$yf+|`+[F*3qӖ -ʜlnKU -w>b_z\ҹ^Rn,b~ȕTe5jH+>'q2nƽ]~iNi">8-!7\Eq% -[­3q;ѡ᠘92l2 W 5h(R _]Tb)eaPY6lĪ@WIݴ޺V,KN7j4E{; U|m%Son2-MZ63VR7mWhhUg4e.$pu{ld[izqO&<HZH[i1:]est:G,B,݌=]:4kaf-Fi٦d٬Eضm{4m{-Ry+ޒ.m݉6wRgٲn3;϶6L5UTlv!{dy(*Ȉ $ALFz5:כЄJγ;YFHr줭 1ۊ P}ESt#- -k&4TiN,"CLrihc:W@Q{ f+ -endstream -endobj -550 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 549 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -551 0 obj -<< -/Filter /FlateDecode -/Length 4902 ->> -stream -x]M$qׯMt ^ÂtͶ}`&HfdVVOϺ 4z2cW4KNO)始WWR.9$6N1{K:)`R9;*CTO1U>:㶪3\N^R gLT fXݪ20Q;I3tQPi;QJ5N)A=Mu:v -i%]B>I:[|VZysJgSt`-&E+"l1Nt ]ItN>'D]N:䓵Ji=y`ӊ:(tR|u[e$-?">VI1P^U2P^VQ3P _Z#0+]LPj%n(/1yoQ!bL1,Ny3&SV4!00}k4oiTm, "\,LxȍP 0=te0Vfnyke[xIp[#H f^ ΐcWL Y4d6ٶJbRgb4AKS?,h0U0 ͆fP">ʭdX1ӷKf>b:/7 OQ`~o\~NuX!Yd7Z9A:Czӷ4Kkv."Q+S^3#nz.KO;>vtC^?}5ʪi-R z.[4C~f]vH>rQ2緞SC}C9ޜȅ5L<9;[":vQV+emZ6{pSGz2ϳ+CgQO[d02gz r>si^X_;V9]#?5xG;\Cߝ or9t\lNavzo<$=:|'[D@86蹜M>}2ֱ0ܓkX|J7Ca" {2ϳǴV- =|fV:4cspKU2E=s  [JYy<Jc] $Ud9\7(ji,FUn2%!\Cq\ύiZGֈBA+>eLmh>wth=][ϽQR7Zg-3C40ּ2D!;B5{]ߠcAM[#ʲg1ڊ͑GBifl߱'{2ϳ!ǯ#;JݤT=?Ȼz)2c@WDiƅV -Z6+`>[-kq~(7'uq.>|Za=9zʞ5peǮs9CC*0}|~4Kvw42߱{2a.0Ӝ^yQN_xeKL9{gɛ3ۙQl43[/x`u8vx\]+?p7 >n [U^fkzTqCbiXL 6qK/٥'=y8-^A9˶`zzxs[N[ -v`RޱCZ -21/FLB3{kvtָ?|sm+bO[ڟf7(Ȯi^>ݮwn9L*CC7S=-<(_v<hϽ>L٣Ϥ&ڻ2e'㡟Fwh?m&zEŇJ!t%0Թyd)۸/z}/G7Big7Oywq Y?sy I0NOydò=_n7?Γ[]L֐E=0|7FҠj٬Z̆0 6c;`5sj]}oam<Drszc=Gh<48BG{m_bl6}}7SCG>Ss7$Xm9}|`WH9@VZyv!͗Hg:_c_yQ< *bN>Dw2ϓM?Q<{HAfG18|p{9>sy ZCB'!%,mm_̳u(-+ص>%Ozھ=?.oX^x7 f^sP$}MWHo#܋ryayQ=nŭFFؙXQ~Cwrgi~T?תqW,(V~=gna\]ڰƟ.US7+U^7fLiݦu'gŠZ;,֚^iZ_,*Eg7}R}󪈓]vpع~1 d7lќZ>(ě?_[C}Ft&Msł9ފjҋ!Mv -:bn^i{=] VXu]l\G;~B6ӹ4D֝GQ&JM]2ruk$nAE;tfӳ^TZ\ EL[OŖ*zҡNn&H_BƈZL絾Vlwm$vG!\|ZVn'ҥ6Ь2z[)?SoRbA)zplⵓ<4q=-saK'%'mVR2&G$c- uMLVӸ U5uoP~[ UZeA3VnƝo\[kz}t0_2QLO.6v2&솁[ةOe4.iXo`5}{]~wǍjla|&I']:U؆ hui}ECǍa|zvՉԍAur>dbӠke|m {qt?Z \}J"qEI3,#.xdnL$w+,.XA\fyUVZ 44~~_LuQ{qikIR[.9JVoP+˲g[ӇF-cIS϶$RWeJD2UeXm -K$z)K=y4'z+aʭ3^l )?Qu% -endstream -endobj -552 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 551 0 R -/Resources 4 0 R -/Annots [ 553 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -553 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 348.873057 101.433071 330.123057 ] -/BS << -/W 0 ->> -/Dest (cb51-1) ->> -endobj -554 0 obj -<< -/Filter /FlateDecode -/Length 4706 ->> -stream -x]Ks|_@C1HAlu(QWXdݪ"cD*d}pO9#O19?U -rzsu.:{G^UU\U;QԌʘ9e,%`qhr07 -fRQyI=W$N3d0QI;At*:tiYGHN:k` Br:[$Yآ(4sEv+$ 3uJx3fuQh$-V`Bq: [,GA]%sE (;9P>th@ӑ -$tJrDl1d9&z.-:Z$@kآHs\p\A$@oIHqLqjo h.@u -I - 5r:s\vj)E7RU;r\t{qwqw\>9. 2n*#U,J7- X 0C4(SpK8.0]01}lI,+=ՅN:8oQ˝6p\`4 ;ޕ#5J p\8t:)]V:wAK`V:Ir\2P ,x{wњ kCe4N(0 -t]!\wquQ<08.\>Vg; Xl!G`V` \ tAfpa[)r\&| jYyfu:8.p: Œ̥:Nq0:I[U8.PyϜI'xIqW ^y2#4撨jNG"3=l]E M0S:'ۆL~04mUnz -J( 8t[q\qh:!8.c8-0A8t-. --poIo8-*8|=qpx03Mx^x+}qz6b @c+2^Vo#Al*Ra?F3NOucw"sL/$ct=O`O{ [$=~Y^`F[4:NJAĿ{wPG+h>x0)s}+` -x|% ziA!yߣ"]1o84ds㪼;}Su._eoUok'u$7)zosZY,`K@S5MM MR4尰jW0?pt{aȯMN4prilkUMnuTeAd*WۙlLg ytӚjY Vsd[cx% }-I5P|^^) «w_ӡVy3;e]Ahk4&,!7#A}oӒ+afkw#_9,hףZ7ݚiY@lq #v_!v<k?ݜ_̑͑^1IO\[M#R(9:r9r}bNh}<8>ߙlhV~ 9#fg}bE̫g}V8X.p|Ҹ|I:9R WȊ-|Z]%̗\h!<6C2*y3鐹᯾":x| ljhիTf G}V5Z)2؈~g/X6יXwzsŋy:s637;oeϠ![$!5 _R%DӘ-?!Ah>OW8bQ4foCUm?Vnh-Lus:nGK=jF< U]oej[m_9)SߩXŲ@}i}fvۣy73-;;؎~z>-o{$N+HzWVig!x#~O]G▓[uLMmq@Ayi_6 <]s6>s^;qwGW|{"jk5oju \3[FɎ3ucNFr?TϓU}?#Nrv%qB3_ڗtm㪭pYxu4vj6beX3e6Z672rG5{@{M}|Gtog!xW}Zzgm3 }`gӡww}OHyU<qǝyΆF.=a -YC_smj;dz.kK]@Ods:{3f=.%{5~Sfss:_Qb*5kF|>3\׫rHR]^;ss:n1բ8أvص\Vg-z%] qVw; ՇdN;[wgӡy}t6^NFa*-TaA>"gݙt{'OsG"U+\}C*/{X@oڙtH~,&'o͸1~x[u5L*t۝yΆp B=PrT*氄6PQo~p kǪVoJXW3ProvON0P5[ؙtHt+ خ{=kw`w9Z70-YՔbWM#[[oEm\W?Y5mD(uO3tc mͮjeS(?{w86qҸFɰL!ikkahGY8]ܴW+N -.sa߾/_qI64Ca}'UjOp{DyIf}EB~+9ո;&Ͳ1?]d.$a'SыJE|;#&;Q8,)aî mJm:1 pmOe&e; HtpbFVE'Gq wz<cN[ -,7RJhBQ%{d=.W-lz]ujV9ׄ N[3+{R*e2*dI)sPn'Ft0¯D*ИY_Zm$BJLjn6X-r*_TŔus3FۛW}Ds*R[ _F̈́b&A,H/t$`0Y!)C*eWIbi%rYJڪsu}I/ts\ciUe܅d^$LS̨Ha~2WBd(?ON*Nfew-b2nLVO[?Q+$ED*a1 PąF{qꭙҏ?K'FK?)mTegH>icaW":#Yܕ]ړ0wJ"5 yWk*E!RfY[ MJ2tU͘᭩<6eu8F-U8/tU8Iː-*#BqX0&fF@'U)t)%itH\K61[=[K.Es]Ӧn\n;KM#^tvL gWNֹٗJJdsiVA[[%&4ThN"CcC&ۉ N :Il# f -endstream -endobj -555 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 554 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -556 0 obj -<< -/Filter /FlateDecode -/Length 4245 ->> -stream -x\Kϯs(@1bDHAF - 琿M浻rZv*NwۣWeS%E:>>̔ZbuQ75`K>M6᯿:s]TJt6U䧔S2AQ*)%vKT9ګ`PAS9U OK4`83F!N0E=j:g+.AgtO1 Vӕ)#` XM%X"逅|N.ި:`q9yM:Ee`weU,&銟BD@gr{3a -{鬝|ӫ:(LRLK4:` 8M灅xu{㭦 \"U,|\FXA.#\e \&Jk4J(7:g5"XE Uu i\#qE%S|KF <0s$ <(T4.\ԸtܓCtxЮ5.]Oh\@]QS Xmx[4. .Ӹ:l4. ˆ4. KT]uCvn i\@]G.j\G?Fո=tk\&D޵۟V%j\6cT]lŕu +O6ƢqAb.3k\: xzԚk]1.↠qa4.6YUue2%g x4..< &Qui#Y @ƓAqAb{/D k\:`i\:,[eM#XSh:𮱘aM5& "xM bb(i\3M%qA,:|.N$Ae:`D /Y;qArADSX.j~@HQ0ٔ )Dcn t2t6i\M؊ȥEq~pIΒ ؊k: ,5.@ d,5..#ˌF%ajMG̬qA8qq 2M0ЄNH~l"Qui\t3k\384.or4.(Xi\PL8Lָ41o:ҸͬqA&Rӕ3άPoުp/v/H`"Q=5 -5걁"'̧O*̜x˂cgc?pUOڏEPK+,W0ѷ=9ޘ!>HeЍAbrg訍(YZas`:!)F~xsrBPձS~4wy%Fpn뼺]e:RhNа 2 -+.0daD_裂HAVb]PgRG|gQp|߾ ;{<1ś,u0%Z>7ϟ"%z\C\5(F*l-mk{Yi7X8u\s}٦g666Q -R{QߏyvΚaϷUy?7.{f݅Ni2Oov Zߋܓ(6#ч6hҦåX+Qףo󥹴u۬ik.|镹n&ӺF/wkd3Y]@mmE/sާ{C}uc/u;wz%Gv濷.r+;oy:r5\JPXxg]xrkm \n_ N?(\oߓF 83/Eo :|?1SYL㚭ẕ7+{<[x.޷;R+ t<rnq Z>K[4"C<;-c<ӯmPafG>z.heNظ +T]x|hxel~ط=9v*[{Gp/ۥW DٗGk~s5Â)4֙?7b:e~dEedwoi~Yj?umż<> 1E1fw;.dR6vfgh'Sm.,jvXقA$h.9kY?^YAakm \xGw[o^8^ncyqHu$Z6&$kaqSLxcgb0:^$39Ї VZ&v/ByvXd -}Qu7qd-:_qX|K*kCJiQ{܂0BFJ!3jGa{LEK?%ۥ{e/:z]v`q^N,Oaeo>&Bvt_ - iм⑶X(2mٵ?ݞP?*nǸNMU"9-Vo:N(˒};%;Y<3ٷKmlKm(Y+/8β€mF;j6{>%C7v=b}4}rZJ:{9hםI*npߓ񍢮do$:_Lm6LI޺H-ޓixnO_gX^$yϰH^";-K9L.%yI^6Ҁ$x-c`Q$j|].[X .={Yڳog"lxqڳorփVpB@f~"k$>4ǐ.ٔ_ £W! OEm"ب^ضy[69OM35e>Rf ?ίKOu?Q-o0U8>lO~3)bGF1 EǦMv:XxpٖDm# |B ?Jwܱ"Dhb"淫/WCl G$ˎGūbЈQcin84ʺ$tcԭI;ZSͺZ PKC+'<)A~eZӄz1kd,͑+":rKkTZ>w+H.Jǵs>& q;!~:+8 h2)7Sai6?WT~] W^]6:YRelJgl6Jy&^[l%&T<&Nk^La>+4nCw姕x };V{q$ũϸ;ޮ&<Սbv:bgn7: 0ăFNq,2m=~zG*\2[Q4+.:thɉRtXLvHI7='9"K?t4YtQ" ׋} -`i.}>0vӥ^es/my|r. -iՖAvJMm. 3M[L S\5gJCtҍ]Ynx=Z= -ҝ%{,YFIdiwmb4Q-J>v:ST'#6WK`&m&(\>;ٟc"MWB4 W+F}P͙P}_}ĩ"sЛdXT'? -endstream -endobj -557 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 556 0 R -/Resources 4 0 R -/Annots [ 558 0 R 559 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -558 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 536.373057 101.433071 517.623057 ] -/BS << -/W 0 ->> -/Dest (cb54-1) ->> -endobj -559 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 299.626036 101.433071 280.876036 ] -/BS << -/W 0 ->> -/Dest (cb55-1) ->> -endobj -560 0 obj -<< -/Filter /FlateDecode -/Length 4816 ->> -stream -x]ɎHrWybB *HAʬztI_4.]Օʠ/F͌ R_~~/bL/5o,8opW( N'g0L u )y_YEv1UJi+B0 *bJ -f@֪3(E'`UkU&hT0C'VCD QD:Ad `$ti޻(si"%` $-[%`J[ F' [(`JKd"KЩZg\VI:lZQIAK8#Άjxu[esŘ@`%0% - -$0! I$`(RX4PV@>-UőjBXDX[P@ka!+q"qݒJZ % 3k' ,(PJXpwJ\`AXA ֵ ,hRX%$. 𮵨)` ,qq:Z k -xH\YC/q25Q5[ ֠k2xא(Gxdw`%.~-wu'iՠc8𮎘>Q0º($qb8.3J\ xW[ԒMR8.'q0h8`tE]TQ- *ID]$-qxPC%.]lIUZ Q; Dl@MQ``5F`` \  IxɆ$.#èJ:o@ע.B!ЀXK\XjXv$.i $؂"q!xN8ӅNk -%.&"JЈ%1ԒǙQH~`WQ,D`JQ[@`~8v A0GH QaQF` qARId @)%qA! .9ތ$o"m qA"࢈:) x$ɄeAKQٍbS~361S4os`x] cs }wTaB&jrccMA/ l+3"NИ(EKopK5& 0<_Dƣ‡Yw]80qo2#N4lmsp8qbFhw[C;jcUG) H4w?ˡ.ۍ}0F]?|??㿡Oo;l[F:uz;;{맟vġɲ?BMbُ  -Qeu{/YsTў6Behͧ3Acz׹weg1>~˷Ϟ1>#@1$yU{DPaNXyG9sȴ!_''<2.ZY{(Q_p'G Ke5e_(93(Gsu23 a^$'"ɖKo/1/S)2Ym6nۺI!IK>mA!w!g2,GzffW;g/Šw#vsdg>4J~UG\dgC/yߖ |fZE˷y}f-FHn\0Kw<ؓuyo޾ws˪X}%=?Y鐻2:oշp{ӡy];쬌6;gW1ߜ?em[-u[xS>y64}?vza˹<3};yUʐПi'2kcK22:OCPuSy?mrEV#Ԟt=ȧ~7z*t=mX2vYXwzReu:OЃF3vIcvL(㫉+~3Mjy+s(.tX\?:ahi2m_zw\-u_G:φZ*-Nh~6Y1~Z]0ck~}b++zy_UGWH/Oy:\Zfvqu];R=boɮی2A[/ \CA>tݒ\\jsaiSAǗ Oo_<@YJMlDtӡyt(,-X+~<+"#nu <uW)hG0*b.DAZ73qY?[#5:YfQXc4s31p&#úXqadeunG~WE[ ]?ے9 yc^m>su_ֽsMs'\0t7-W -[Ap#w!W}~VCi)YJt=]o=d|ӻ7xGdCq7[rM:$-M&~c7{7Oy6ju_:n(n {~M ԗYGYv6~wj|^zXqGN_u$+eJCuoOs{ʟZ',1K{UFyND?%pY?'a6Ǭ94?vѾnٍ\>4r)" iT~ǀ-,+[F*v qӕT[žp{+e5[m0Fs'UlTjgRJ8Nn.2i}2ns3 Z[ͯl.}? }LQ-LօA_Je4BC Wh(1 _S*璺0.V6bSkmF_Q,Gnӡ'7 epОcٺ%_&qE-"Fqte 3m'e~jr_AF:ltg lۃamia`> -`i"}oXZO/˞cl[GegSFu-hqbZm.N)换d*J!jyX3(ST_ڑvAtUYn7x[r-C=;UK_2 -2.R%mey6A_=SUUɻ3R3fFto~FM:Xc"5PlR%7ϝ3$9wZ4a;X4>4OxJ 4Vc~sLKSU࠴*H?H -endstream -endobj -561 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 560 0 R -/Resources 4 0 R -/Annots [ 562 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -562 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb56-1) ->> -endobj -563 0 obj -<< -/Filter /FlateDecode -/Length 4959 ->> -stream -x]M8r؃51 `Е= ~Ad -)սBu" >>)J -??hR1/5EX]U+'sH3 lb& <su}5ShOrv)FUJi+b4>'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kSӃ3z -),"t:Ig^K<|tk甤-Φ(l*Q[LVEb,l-*(-鲝|NΉ J1muF'kzuQ-A,`H: [~$xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8Dmѓٝd_|gL?7eh%C|a`2#h-`CژYDlYuae+L%c+@`,{J` ͒և59"&A˶vz$[F1y {?{ a[F,`@=郍mdҡÙ(ML~0L " Hcr2]%31hϗ??+S`o\~NuX!Yd7Z9A:Czӷ4Kkv."Q+S^3#nz.KO;>vtC^?xç5ʪi-R z.[4C~f]vH>rQ2緞SC}C9ޜȅ5L<9;[":vQV+emZ6{pLdg,V rxÎ:= kkOW&OzF937|L]=HA~Y"oV=5pewl;"*Z*\C;#G=Y{ lQzȜq3"ya5b~[v:Whaη;sy}w_#sْˆl޾!yHzru2!NkD@86蹜M>}2ֱ0ܓkX|J0{=kcMo >3+9om8̊*N"ڹTnqܭk,qzʞqa-kRnn9VbTцGiyWL#c'<1ůaQuG\&1ĔcGw/y3vF[y;!*>xFtKegN=u/=t+w瑧Yڎtԙ};Mjw/110,Wq`$XOKv9G_jJOOGOI;4kZ;cOzbںz#_ҒQGIr*Z -lW|zʉ;DziWgK,Ļi_/XݡP~/Y|\X]<5:,M M^qKO6c_KGm9n)+ځiyR|XWp1z6z7(gBʞ\+̟k[{[~Q0P0\̻KP&-}XwwG4 5fK{b-s[e_.U7u2l -ms 3)~jYu5-i9n&Ks׌~sj\-ç57s%O_ϖfr&+o+ǓZz];szWc@Ϛrؚ'>#f/==|˒0.r{Ѳy -sTGE -+mkz3yDc.Pۥdu=r0e>r-w=d+KvC8;['yz Qno k>.cCq@x'w;ςUgmCPi;936Oyil7.n7:ev97nH7[fFeY|vIxH3)Miyr< :]tQuM6mL{[EMvpvʖ>٧ -4Xњs6Oy6&MAau 䗿kQC/zY/v7/;kl9y8d'AY7ޓq\;ƃj{g:X&:| e9>sy Yzɝ[ھӏՑz`vlk8,ENW=H]B3n6a/X[ń~+T.6ڣ]u uuMk"#j(}ZTQMfQI}M:ĵ~D Aբ:Y{kga@r-]"[JbKz\=MPSh;\Q~\[knFxxFb]|RWqe6qR/]Suf[?*|5Hћ{Uf塱<]it _:)!=nK<21y<"Fknkbƕ\}Jmz* ݷr84|z\k\*͍b~tQm1a7 ŝFߊN$>Ȥv˥LszC'򢫬%Al/i^i^# i&}06“\esl9UoP+˲g[ӇF-cIS϶$RWeJD2UeXm -K$z)K=y4'z+aʭ3^l > -endobj -565 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 348.873057 101.433071 330.123057 ] -/BS << -/W 0 ->> -/Dest (cb59-1) ->> -endobj -566 0 obj -<< -/Filter /FlateDecode -/Length 4805 ->> -stream -x]ˎ,Wڀ|_ xda˜EߒZƠe@Nd%Ɋ|TUv^huga0gh/bL闓SoL1'V3 lBr& .oy}6CJhwǏ";r*AT !n1%I3\ C3(E'`U3L$`N.*`6J:t %у$QH:kH;-wQlqIiI`DJ1H:[JtNt]Q啖t.E"QS1[QnpZ%iEF:Ag`W.:2?Ip6(Vã*%-u/1E/QF$q adH"@&B )H<`h-Vu&؂X [ Y ,ؖ ,TX-)%. \$.`\=I\`ARs-S pXuH\`Aw-i%qwENQ[` J\@]UFFz Ĩ$. 𮉊$. D]05 ]㔑@?J'+q{茕 n?aLwuD4-Zy' xwAQpH\bt]mw78 A۠+ҠR8.hH\YxPL" i @ƃ*qbzOxrJ\:b~ t˜:(t]ÒTHx.O%.`#q4>):?I\%` l[1[2H\`H޷<-> OQ0yЪΛ!е qA4`*`-5D z @K 4I\lPS ơSJ₤#֛$.f Y&x¸Mz3H\8(iJ¸'a vtD$y%.&V rh] Vm+M$e:9i[o[A #~u㾠mQn—=V~b6H栗)S2Yw927wUy4#`ãy? n'qDmj9j}է}ûf^/sdHhc\gQCNߏPS}kyPLsv3d$qU1R%XF4M32:z:Tj=6ߋ}}nڲ&_ܙsRrNP:j9j7T% ^O^៩W_e{m_X8)ؗk^瓗%ORQG[]ַ<_s8f =;Gf%_.=b ^ű|g7eoEv97O{uO25SD0+ -ƟWX2/7- 2lܻ"ڙh$t3+Iwc3#yW#4DFBV=G(L?]h(Bofw9\bת cu\M |Y8+úkIy -#-{痩M>ۺu2Xmڗk`(ɖ '^7x>d|k_kz*{6ok&.Xgy(xJYo| w9ֽ5ݻ7ӈ遨K*+&w8`ێ]ONrv5ƗڻW`gáu5C½{ D3't/vDlIvU;9RF48z|7;F޾"3n{(|蟵}q?ۙpUi?_-<^6OZ3л~#Z;s44 ta7[rMY5tHWMwqJfnñ ȵv9r=}ӏFhL?۩OŹZw9r%Կ'qAO@,=9>?/qPgtsUݼuwvWNIj?m>{g!uW}|܊| vYpo|O_v(#6ֳ7τٳ3%.eu\j'7娩cL ]8ioΘFQޝyo~5; ~뭟u?e2KLynJ?/=K^zgEz*c \F?#az=ڵ8)P5vOHQ"FI6Ps{H>zX xI)99 oڝ×J"4НOSUܼ<}.סsq+ -ןﱜ4V8?/U?+Mu7e\nxqІ>{C:Sӹݦdž煜QʿTʊ\öG/7S_ <'QMKh0;,T,9a]aH}JI5̏U8i\r6>TNd3z BVw=48S6CX 6m-fk*6|\i:_t9 Mw /'Tk{(3LsQu*2唥C 7*M̢ozO -ct)Dn*͕ -%UYSnjJF4Q69{*617QUvrAH*W( -mSnGUR_YhTኔgCSWj%<6xH!4i.Bl^:*!=nI]Zl&mc*1낺"f -SlbW6W;]{[žp[+5lX-68Q/f\IUfZY#(Σe:Ȥriu&o5z]O?{Q-L֙TŞga6PCUcM2k. -!Ȉ(ULԤ5݉ރC8Pyc';ikBw d -x[0 hzN%%} *ͩȐvD2Rѥ8r1ȓJۼq>?h -endstream -endobj -567 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 566 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -568 0 obj -<< -/Filter /FlateDecode -/Length 5029 ->> -stream -x]K$9nX^x`Нݵ I QյQSE}"(+A)?~zSS -#~ku!Sp#/zk]G͔s0XN1Ũ`)mS!, θ-+B XVEm 1LNbA }XZAmyD9g~ -PzxFO!eE^OG#BtkOAxx휒x%^,6X% IJY ^,$ -JKl's"/RL[Q~Z% -SJ‚M$,x3IXBOX7AEA8MYX$ě@' N‚śI7ы)Df]L 4HXěl^x}&3EI(@* Us -K14,SVJL(/19STgHX}9z1SlΏϷ~{^~S2e[()^M=ζ $CB܅Ԁ%FBb+v^ If g̭E1W6· -'+JyZT>KݷN6 -O\^BoM~=6V&_Or~z324ӽ^~w{\b)(yCOyC_P(kwuߥ^ҩ}ү?WYݧ]G*umC+q<CW?15YU3ı>"Sj/PǏ@2FpRult2E}hGٶ,G%i-mC9BܓC}e\lP&]:<,m}L5.eTRV8}v2.>Oěm֖VuVt4ԧ"o# f[lc-lgĘ3|u} v /GY+a{ew䑎f`uő=89Ixx?i*F: -(_w2x' e68:=j뛼t?.[`:ge^< "WrC嘗OfPa N.ۦ_"> -'cR)p'1!`vVA D>g::-+{VT߇wη s>F5> +n)g^jtlrŭu^ui 9οUT9nx8a=]z-TMcXl{s-~DIn+3lgÇ97vԿM^UE=tx;XfıU_$Vb!2WD uWk=]}5'bcw㏞x,`ePaZ-9h1?+VoklM'.l<5˪fE3-t{#`v#w!XpJz5V}ӾcW/y:ɧ~ofΪ~t7z,ۆ^b߼qsr"qvYIQ .GT<&nex?8}j#} }Nӥ.y:=Sl-|'<{LoַM8wwj9N*r'0U^=!W ikuN/etp]7Rة^|طd݁%ͨX0/cuײ'|γY0EW8W-O -ĵLkWJ֫$R<^/SeEZ&ZDfr.<0&teR:m(ZwjtZAta)k_n:_*WBN>t덮wٹ~ Gڂi <~R~>4ZJtcAo4z5L_k&<& -]ЈA{SXwl\G5Mu\uM-k"#nH}tzmjרFLܨl< M jlJڙ!V.rq-6SJjtS)^=te5>ks!>n޵ɯ7Ҿc|%Zn#'Ss?aiV]I7*!O]3)?Nhm6ZI8I^KlK'%'mVT2FG cM a%'*dLuErTjݷv;94|f\ M.J|͍d2T;dn;c.@;r] [cǾȤq˭lszCw ץ2??oy7iغ"󝌾^&]$Tb[6hN֩>n k׫쵤n}!#fF[@| Zl̷M߰G[Gw6U*<1u[5'*ڷtpa#0wVbANI~ǧR_쁹h;m7]ie\`xNNJAw/oEPWQ7+L1۞cuGuv ,[{99}it­2jՖw*mi(\*LaVRFD-St_=Dg%lRukޒmT/|$ݨۭ uABLU7%߅Y;RdFtwSXGkl>B8Kqd!cr֪ e^ T2FZVަ!5an{xƭ, )T/س&^|xܤOʿ= -endstream -endobj -569 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 568 0 R -/Resources 4 0 R -/Annots [ 570 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -570 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 597.273057 101.433071 578.523057 ] -/BS << -/W 0 ->> -/Dest (cb62-1) ->> -endobj -571 0 obj -<< -/Filter /FlateDecode -/Length 4815 ->> -stream -x]M丑ȳ9bw5v݃CUNE=#%!*ʪngBu"H*|| >+|_$=Ř/'5X ;6L!9C^߿:ﺎ>)%o;sVB A9AR -* ]LIR V`$ c0RvJ0M -f䂠 -vh!At/錞|L&FY;@iI&ｋ`KJK:[&RAybU ;IEtEQ[WZ%;D]N:䢵Ji=9`ӊ:( \uYe$-Ip6(VgUVK:[ $` _ba -^̠)&!LE & -J4`ȧ U:%" -8X [3WHk` -H\`-l1d%.`[Z$.[RIK\`paqm$qJI εN ,H=H\`y#qZ^ ޵޵5El%.;NVG+qwVAb 0p%.V&&*&` uax8tAZ)#qw /q2 wA!N` V+q  xW',œ[M:&/qui-r'!o{^cOX|˯Jh4!40 }ktX禎AK-/;o?,?vU69h| -#el29ĕV.V9vz0O?~o?/ѧo: MsCC٥ P\Z]0wFX9w}^N_N=f/?W:v8"\.OO?~i r7z{% nf>#x<,>̗axڜ^;Fsslyn趉58Q!lQ1j؁yey>tY&h'.KϬ\ܱe//4*֮_ly!uዮcMcg\dV1>ҏDzvٚŶ˂la,wcp2eT3}>wPcuUף7yt?ou#6<#C)ϯ"`GC1IخᶝeG1v{7M9^3cDv_%6oAK|}ޢRLIEXzáF7_ nPz+D}s=).x#Qu<RonqMwP8M,io/e߹|cB s?Vy#&YuUZ2P_y|dWF#wΣ!ވU?;hy նŔ,;qh[[{u7b#}>_ o50F%O}Ayǃu71 T~W~Z5Ʒy8{а.A~}O}50i,ss\:\:LR=:"|u@h9ڗ9_{[rL2^2uih/(<RoĪOBXh'{.:i|`]+Nֈεj+ׅ>}bgy8ľNjw#NG乷dsSs^vc҃;u˹~H\蹝M>}c@l6vӣWly8޸7ta"݉2tjb(~W簊6[7q#ڴTAp(q_jz!d̥Hh-$kp+Ũ&eH=Xѐ~;W; yn׭}$'ܻ۽;r<ZǮm^(Yݫ:ZW,{!Q_5ʽcFu/t,)ߝBY~ 31ۊ́GBfηP9كuבƌ*kޕe{e9_qn2[sв!k26D 9<ǸVn =5peW^7初CbTц]+n뮘Ft#{Σa:~ׯaQouGffv)7Ϳ2{ג"]sx\ _[xFt+:*X%(2~ٽ:?RϷ{FnWWtI;X͘(˥nc~}R΀U=)HCdgD29CtZ"[a6ge]fڳx#_f=."޷!=yyZq`܁%X]d?t6[|sYlW_WՇ|Ǥ-deFKO.?>59mPm;ﴴ/ؖ  \?1q1j>/6eny^PYƚ?3lyպϤ6ԋ]^h!h}U|*O/,sJ}6k`cBJa.uIs}Ug7'u?e-흳Ky_pUԹ|vԵ^OzrX*Ɲ:;~߆j{֯:6.lBρ.hufibi+/ʙr[CٚZ+xNzܯs||?6.lk=:yZ[=ۂ>5zhAQ&RRNZF*k-j_UGK]iG9Q񛲹ݺhɶq8;KX2 -2k7)ʶj{fݠnܦ]wܙ YT)CP>XP~WR%os=w͐ ?c"kU; P -T}\-)Kos46jr$a[&Wޘ_@>OISK -endstream -endobj -572 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 571 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -573 0 obj -<< -/Filter /FlateDecode -/Length 4943 ->> -stream -x]ɎWY [ Çi Fˀ/̅Rխ1it1"`˗A)?_JBޙˏ1x+/$*{>Zöo_\5#j)i?}"у ˨"TBjFeིQ99cT0zRar*a -* mKUKé`3*)`TB:"ъI;8 tJ.DYNz7JN tXit9-i` -^s:[F'2[`pBr1.B'KvAk,YV&yF`6:bPNNڇVE[ -9-Jy` &c`x`2 LX@85G*9BB$GZkZ`` -p\5lQFs\h@n 5B: 4f - 4Wg8.Р\@)r\qb{ 4XW[8.Р]m@w5Yl9.;Zqj)<e8.XTUA xWylXU]ewQeB,,S46(%X5 d ޕ =FYA:9.]lT } vTqJӁw ޅ`9. o.!p\`%qvA0 $9.~(=r\jq -kòe4A(0 -t]!|wiyq + \0Cq\ࢀ.s-^@`AYo8.c=D^^ #͆pa[)r\&B4o1*sjtts\K K @0:i8.`p\h -9N6t゠` A -2;4bI 53qA0n W,D`JV[@`~(ض A0m !( -7!%&ś(` <> pơ(Me8.x3p\@YQ;7= 8MY$ě`'N`ś7ѳ)@g]L q\ěl^x+EPʦ gsK14,cVM/11ԦgO', sbzؘ˯^勔)?Q`i] 9 }T!|&Jr#cA d+˴"N(XKb_~ŲF޵OӿÎ`ic%ñF/3v /W_0_^.5a@>?|!. iR Aw7Csg6 N.|QіC"btLur(-ð̡i~7_`Q~دZ9ʭ[."?] & S?d_mt3-ڗO)Wk^mx)j'Gl:4R;m$N4G#ikguLum\v.7)+s?Ͻ4o&?FO@k6N*;I=[ dUn(3QYxlDe/Tfکj7ex|jlmƲmnv*ޏcuNeƧW˰τIiʨf,>d׿l]oԧ^]pЮU,xXamrSu_iyy^1o>PyIds RJXƋOwVnfC(;v-p =%kEF_+(j8B6 -9 -efZ"\`qHEʵ;+X5Qú3d)Ҵ:Cގdkfv|-,xb˶?gTćJv^ϾjyGj"(n vǯ쯊t}fZE犑Mk33>m4kFrk:Q -bxi|ƼDogUʛu>[F8s;uw9s:4o tǃv炘f jeK*GnY+ d&9ݶ@VY43oݠ=pWZlZ*}i;;rYAmooXӡv'VnU=pot{,ݝ^b=}p/ٹ"vw=xݨx}em;)*t+iW^4w=z\-4; }y ~O}PPu-N^m>cuN9n9v#.UmGgG-Tڡ|ɶۄ0wGs:D\%,7~6W%9]c޹{vߍo^);W_ܡu$/}kI%jr -+Wl;I>pokl| -s:_1ِpG2swݓ}'?f6ˤ=f~`!u'pQ<~7;f~yYo{ɳ$znlC\`[duYg^e6$1L+9rC>Uz)Ŕ/K){U~@G"TM[H0BNpcyzXA$Ge[vB=fMo{r6bx^"tEo:3P62OL-+5{~,ԟ=&f'B_$8|Půza ꠘGQ22,x/ ULcil豥FB:={K1$WAOGBO-ڠik]ԢڥP4U2I(C窰l?U-nu/}eT]%L7F"dS.K6̢of^#1 -C)b.LjnԚ-3KP<Ք -u34Fӻ5"t8;<"4Q bMYUz)m+W -unQR?aif=)1O MHNhm|Z+cײpI fB\ϔ'-ˈͤ͐5ryDR oic3r'UDjgRJIWka'zcX._6A睖7\*1JP[gv'WBbzieiheemFCǕj{.) ʢma#VJfd֍bqd:7uu>9z>$[tpN-4#*Zthj*mMZ63vR7Th9h:Ug66e,"pu{6ldizO&HZH_[i91:astz}^uJ[Y{89uiTZ6PMl۩ɲYy(tȲҢ6ZtƁ%_|*iJDΊ[vW%] ׳d%#sm"5βefwmijCa_6Õ?)3"C}6j#V:Z[!ގMhR%wΝ,3$9wKzI:o+q_4_W=I U[(%7-Sz -ؚ@UPy>I?$OD -endstream -endobj -574 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 573 0 R -/Resources 4 0 R -/Annots [ 575 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -575 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 770.673057 101.433071 751.923057 ] -/BS << -/W 0 ->> -/Dest (cb65-1) ->> -endobj -576 0 obj -<< -/Filter /FlateDecode -/Length 4848 ->> -stream -x]K$9ׯ3&~?$ @ FpXq^/i;Y]ݳ[VMUF9lgY+SJ9w|{#^џrq:ߒ)fob8pɓ?yL9_IS VPy?h|TAOŜ%UEr -f8cJ0úVaI*J+ءR(tON)lh$SN{-BI9ҒS8 Dl1)ZIawKJv99'2t*Ŵ'UNVԡGBt峨-*#,lqt ocJBo5ԻZybLt%0$ -@$01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq蹢$. l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kSXdu8*J\FF ɤ$.p]wM >h%.p]q 5^ x8$.P&.(lJ\:c%.@aAX"qO`I$.]|.O:B'Bw1PY `>J`Aע.A1 Cs)K\(\f@1t 0M 2t Ȗ.tZK\ lA4(qA2 ̠$.$\-霢yf 0Q(q f`JQ[@}h%.MLsDlI\f %bؤf +؂O€Daq蔒 q_|3I\|S$xio" -#3Yhƙ[%h59h31LA\5 -Vⲁ"sNWU"&3Ct=I6o~{ۿO?)+eO#@(+tѷۀ DRd! 's7RE72;o?,d:rc^h-pas`RäCcf7yn!se[xW+8FJ(g[/yx=B6hw6ڶJ2'beb4A;WfyGlh<Ib&*/>@}d#*?|~' 雟)pϿxv~w:,i{ʴʨz5c">/%%J7a4"XCF8a\vO 7T.ӗ! x`CxvoT3Ezlkwy4k~W~yŮI:޷ҤvRnRNYW(߾F-@(}!:jJK)itme=uo6ē紞|˗mٔƅm%_q^5&]~n"Kjbw'};7.k)Z#7>-<:,&nKS[l AӟK_g#s/Ckv)O =[N -ʙg2#?3ps{,6.zd=m> -jgL״&-mXWwF4 ifsCen˷>!J/;Q%Sٵvh6voo׶`X#5s5E52=NGkl"5&q;LC~}B}a6_=&o{_ٰD46ncjְyvp}z33F5;p}\o0R~yWEg1||˖)Yiy,=ߣ3ٛ' (fp eyt#Lf|Tf -<֣-[VWAjG<|/_D;ړ+ص>%Oy?W6@vTKG9s5ez4lj[Aڥy?> tOyby \δE=OevD^$7V!_g=Q$MgDߍyFYb|.eoS#t=<bpJ^gXܴ%o6K m!\8ʯK̞g^brf9eB87^pg:;5)tm6];9O|R- q:D4+XWۓn"=r¿*dE vopZY Av))1PǾCSn(Mj"[Ξ+VLw&W2dL&:3koUU{4\]Y״}C Q"JlZTQMfQI}MĵvD JբY dz0U .tr-RJ=kt/.l3>l\kknFx9yzb|RWqe6qR/]SufLIy~+k'qyh$h{Z.c,NJHOR7eLs5HZꚘ(q%jbߠw;}^ʂfp.;_8t`w0_2QLO.6v2&솁KةQ|Lq/0g7ߟQ>i'w]=xǍjla|$_+JEUغ hui}ECǍa|zvՉԍAur>dbӠkeW-yk{hߐʮV.S>$Y}HP\ -sle&W\O;b,Ku*+w 44{C$mޤ/\nd-a}[jjeYl rz衅[]p2iٖWlUi(]@MaVR8^-ҿsO{*͉Jؤrע% ݩŒII]Oil[[]G3 =2U=ߤ;saBJUʈN'0P;WU -{KlylWH 19kU /P -VTmO9[V-P9Y*?V*Q4Uk&+-_V'o( -endstream -endobj -577 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 576 0 R -/Resources 4 0 R -/Annots [ 578 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -578 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 270.123057 101.433071 251.373057 ] -/BS << -/W 0 ->> -/Dest (cb68-1) ->> -endobj -579 0 obj -<< -/Filter /FlateDecode -/Length 4736 ->> -stream -x][q~_x?pl#Ff 󐿟j"t3>>ݪ"cD*!zGϗ_.Rx+oH19?UIª肽 va_]6ͣZ贲׿TdK˨"TRFe^[Ǩ9̰4UfP S :03 ye3Wĩ`3*%aR:"ft -JwN+Bԑyל<)8]98tXE$9l!uZZa1)%,iXzyFa6:bԜOXC`zNH8-Z{bu1vEzQzHq^PđFPQ =F*HbqL`l!\V[L$ -Hq1Em hnIFqߒT…5 (E 8׀;9.0 ]twq4k(8 xאxdu( -%=E7Up8.VAr\@]$q\@]1:/ ]m渀@z]P=tp\„[q愈`+BtX -h>Vqߢr.r\`  FTq*Ӂw ޅ`9.q7$ꢐ1 ,x9.(,d:/$qXH8.qJk + n-&h @ni8Bj0Jt])}wӰqI0P @"z8.pQB9cqXP-8"8.9.e -7;=- ;? O0ocUNtts\= Ŋ̥D@/q̀N>t 0s:[ds\O:8. Y`\UHyf U3M0%- >im9.MLsXl18.Af آLMqAQ:d @IqATMM_f &xLƥ lpQXl~ N|lё8.Υfnِ@HMφ 68xo³k=3^Ҍ3 [ِbl@| L,cVT H/1q=Ԇ1f.2[2B{|/{y) -_.84 a#y>V#hq %#10>bNO 7JL_`c,hCub'@~I~h9lx0i{^/RZ)ܿ-Gת#}g,*r4VrI/C'=?fb5X553aVC\w:|.7}w_`<;ÅQ-q*eyvn֌~Z35ͪRW~O; t|לn~C$C0f̫,@eiP^넖ybsiڡg:}yNXZۅVH7ⶐ6r:z-\,qdnXX<+&ikiMB -4YGY@m M7tPnv_ӡv#oxjF56Er%K:KA;靳`BSAבVS -:~`ڤ;.k[5_i3ZwZ]lצӌՑ%EӌA'1Ky #Moc_|TijӾϑ& \7ڒ9! w 3_ڗtm㦭"ʻ菇1M9mhm0]`Fs:Dm%lo|fy~UV s6TٍU`9ܺ7cQyNM\ +uQ{ⲓhZ?l^Rq51ƪvą9ֶZ{|5>ewDv97|wZOϡw~jѦ]>YNv9z7|O߻];jSrM5tHGMWqezñozlp ֺ3鐻=F n gOsԭ")F*gp߮#IM~=zϽ3鐺᫾0cEpGk>Z mDžkKmg }ݙt}n=|w@xݙlh>-pv2 -SmᥧZ&,O_k߬'/8} -;ZA:Vxykƍzhu61dzt۝yNcozYՌU!-e2"~+nX@?6=Acxs6ƍuGxV{İr߀G$l[`g!uAs0lcvZG<ޮ>ݙthxÐ@AfVSi\5oi]d`֮׽N1f.+3z~ 6:[OV_x -%>ݙt^_I#=Qk㑇Z۳웕fHK{~n5A5D$0-ݦONw3Z盏-<鯇q W8}+'w*Wtbxvot_d=H9nHjTeuLwX$h8ܤJi35 xZ)"TOʷ{2ls 6_ìa'5']JD>^>SARP꺐sNjaYMӆ[헛1/C|QDD$P :T%K'SHEv{ -9pcOmդ6gK̰̉OČ9KFqQ83bufkԦ֌bed#slNWŚ=*@WUa1:4N}Ӝk5􍕦}LsQv,2攥A#]w2Mh̢oZ-w $*bNLjn6X--KP\Ք -uJ3FO[7}Ds*vr[Fτb=V6C"Jӣ_YJߩibᇢ^='I}]aj@iR̶d'-KMM5ry -yLŪ)\ -e6b[6W;m{>S m)]ηVKa`> oF8A?Te'k0BW}ĹvH?qo^aN#~8^ץ4?G>kYBnۑ,vNYXM#~Pڌ2k5{N -ma#Zfbqdm:`M8ƤmU8h/LM8JI-&#Bq؜0V&f&@')U짶)L:WsиTa-:ˆh6A[0qbcvMv$i"}k’/5á1\AJY{89kTׂ&-Fi=)ey(t̲R61[[KU׶m*m*n6G-ξ^)/ks)Ք&h{m.!zf#}瞧BpQn7\crwsJ{ -Mp> -endobj -581 0 obj -<< -/Filter /FlateDecode -/Length 4971 ->> -stream -x]ˎ8rWz|F/ anޚQm OPCTq_Tg*yxAL}U")<]o\~)8rEV]09|t_X`3_.p'o.ΣfJ*S!('TJ[Aq^Py=ST02UA):I3Ș("̰ݪ0A: (%`"Fi7y4tFO>&D]N#鬝| KEIG%%-N)I[  3wL-$%qop qI+@WԥI%.p]В"Dԅ @'?T$.]嬕wuF#q0l1 guRL!J%xW$.]6%.&J\'xFiJ!x |Ru~µ ((K -$q)%.Xc$.e4o1<-l(qlH<1ft-"t:H\MA/q~bwI& B-*`*g.4l-q<]贖 oPh"L$. XM-Hq%.'v%.0A u4!qm'qsDl$.p%.e$.69 $[I\M4R$o(qA -&B7zc9_-}]ͥl-TǾѹ m]Υ ǵ_}O#GTo6rsyoym^ٳ?vv/]&[iwڽsu^Yi7}ŵZK|lem9c6~odek2ֻnS~< -?ѡpސ`(ѡ =˝V?8*,!PIJK4YqQn9=GCIDYZLJL~wZĮnsc*QW -lB=,וF>rsOh0"ajM^حct#EN"~^;^t ,Wl'}~3'3</.$T>4)49Ѥ sAy]Az*2B>Tѓi9&{"\ zp9%~htj\3,ekm7 c彭vd<Gr}wmfɓP_} x Q}[W<)Nс{yy>ؓ#dwKG6#uߟ#3Կz;Q)h}}t=+w}zZGCr/,?ݳ9dĆ;F<φذo>ј;x7Uz`Oy:Vt>' ZG4y~= ٹ"fgdCyoYd/[G>VnI^}4thc7ބ({X<]+nﭐm?zveyIFf|z2ϳ!3o}³*t$h=aSWV}Ho^?x"dCF38#GEi~awZ~h 2qztNQ4odý]'sRrN=P{*-Lxpe'o-A[0cg~Z {Z0D:zB|y2ϳ!/<wǎc]qvH>Z>"uAwe \C|3zdr|_k*:(xzZ?ee yq+˳Wyxib|S#-m:7əTךjG/󱛹[%D>!8roGp fUղRAvO))+uGqn8+BR%ͧ Bz+W^q˕*lR2Um {4C[7a5o:uIx͜.֎7QʧJUe3*U+)kP'AtT)ЙU ; ctDn)՞ -5UlYSifJ٭;\%tcDu-3Cj_l:ₐ5P@ڮ*Iy}`Yd|& -W< -)>]JxlVzCR h --m\:پ/tkb+idɾVjҷ^Zod͗~}Y)P-vcV' Zh'-ےR*-E TC/J;b+S4v}Ft}MZ.x[r=C;RV_2 -2Rj)mmuevA> -endobj -583 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 570.123057 101.433071 551.373057 ] -/BS << -/W 0 ->> -/Dest (cb71-1) ->> -endobj -584 0 obj -<< -/Filter /FlateDecode -/Length 4858 ->> -stream -x]]$9}_QHCB< `@ -ơSJ€֛I\qI$qA -M,qmf ;:؂) &Ib @$q 7ы[֛Q. ft]DA\`VZ+degw cn U ȗH2q*Z -xm8a}[Tp3SFf 辭9z2l_O?^VvFPR;W&=o[mL$EG1w#5hqt##1ѿrN#7Eh~0Q)aQ9|w&GD>h*^odyVۺ5SR-`kiv@Y -ND1il6ʈו[%Շ`b[n|!n>R+#x肿߼tq]r ,-44{a.Tz]{]MuQ9f%]){)f;;gkPbv˿?|}5HJD~e\}8ayNG;snʗ;a!Ew8%j70u0ϳ -+#$cݽnd(w)Q ^Gʱta]_y3), Uבz,!z\w hj=|#V}dm)_X>3> wPz9,ny:ވ]oCC=ZƨDIӅM;h|``CtKeM]; eV_-el_d?k{<r8bqnB>)Ockk={,~m;IQ.ؾ'sֈ(;G:(/lD;I,oN CMutH~bE8sڗ9?'97CV8ck{--vFm+>t}8#]-ތZd4b܃y z)~s#wmW=\S*{gM<#y}t'=;UWйY)]X;>yLzpu0!\H~ms98|?ly0A/Oޱ={бU$ʸҩ{ #GB8U2E-|Fi[6R{KFโy s{;%КkaSyz 9'z-7vvܓR=Yai/,γLo=![o-ig2;T] pQReXo;_In H唶W?+v$mP-G}bQ,FLB36{kuḁbL2m%{\iKl7(Xi^M&-}Xw wnG4 ifsCen5_/rשUs;]`fS`m~5}3zO$]l&֜9/U$͆}j7#>)8ʬotK}G nr%g.DrSy?ϻd0ʒCM^ZF˜DgzN= V 2;q9/zd:/Lrتw˝pځ(a.xL}a2[,jVO9@(sLV)ò l~ffyb}7xLʯs;g5I҆M7p -W]V!Mл@M󙎖M:]MGNZ*Y3vK%ÿǒM.b TcQv`8A\_ pZYNU]0u))1=c_}ќfIl9sX"g[1^MzKDdL {7*&[buqMN7ׅ.lsi5; /'TkG(WԢwj2ˌMk! WЙMzɵtDn)ͷ-UYs|7CݦxAva;ފƈZL*1ܘr.~;(+Bm:^?ahVKTᛔ|ЮAWMv:Nve16r餄D-uJ\1WyźªWrF. o+qӷU,hwиcqM7{[ Ux)T+bl+cnH;qʡS>Ȥr۩LszCˀ >G;=F50[Wb>˜A1ܩ -۰aBwN=hh1]Ϯ:ה1nZ.݇Llt32x27}ž/mm-$j.xsp)̊%S:ΰUe+3 zT`a]ڮs}EWYiK ^ӼҼG0 i&}06“\eslYg=ʲlC eԳ- )?D -endstream -endobj -585 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 584 0 R -/Resources 4 0 R -/Annots [ 586 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -586 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 142.623057 101.433071 123.873057 ] -/BS << -/W 0 ->> -/Dest (cb74-1) ->> -endobj -587 0 obj -<< -/Filter /FlateDecode -/Length 4741 ->> -stream -x]Mq赁'00~AGADe8PA& -q0kTqsZtN Y]Nz 7bqRC@?q̀N |-*`(g$lq<] (o゠fNp\sIT53晁`@"&i)YlMp\ɶL61auE[qA``曞(` <> pơ(p\~IqAML~ bᢰ:)2&؉9آ :Gq 7ѳ!@Mφ 68xo³k=3^h؈Zl@{1Zy6f @4Gb03بU(` ̬8a>!*8xEFt >9J2lϗ_{/#eOASW*-o2vOZ*b A62 -,,?-usLlNAW KE̱feY`\4:*P 8,ib -Cm2ď͟~?/`%? $tMߣ3tlmt~)O(_ֽT夓zorHMT~.o>M9I?ѳN-$;[Hv|k־1?/T:<56m?4Qa|qQO:T+&YɂڋTNi`X~U f15d-cV$*y+ߢPxd NLo3's=˕*}e|cee0L}pt>l#߯SKe>253bD'el;(3Kt hjT_J+`F4U [+,[%1B6Hw,e%;sdfI< \euZ1~QݏԾ!߽dI{XUм:!f}yN>1Y/yR[cնdͥw]ї)43YtضunuDs:mKeMWj$yfnd}Ψ\^˷|D"( -/ЫT+f-{|WȋXT덼>3fO)<3۲79wFlg!v<x7Ezϵ?s:lwDwBa@ߙth{W1;=bĖgm+yyso' /hح5R<3VuwgjGnxrugalleVH눬xdٿxL3PV-y}7{ԁ?zu9RVqoonEe'K8g\UL!}uąsm؝yN -ݱgO>"*Ug! pQ<#o_ls6D'YZ|,D:;] զM]>YNkyN;~]z͇Z@qozjpn| ڙt_}E7 Uܓ5kFLj)a.AlSj;g'O?MWCmFrqK`FNtb6 \6źd3儦N[NX2Ю*IHl)W+lz]ujV9 խҖ}Tv2]ԦALn'Ft0D:Acf}j$ H&)#]tln)S5/+u4K=\ϥQ Z okrO,ⷋLj[BZfq/EJ+_IFU,% -2>*Pe%rYp5 /ig%`ԹҪ*<"LK̨bT?+kHF"o q -œnye|>}6lC*ȣ])@ -E\hmޚى&N?K'F/qSڪNKږG|bAq%2[̭ q=&ơSL'a6PX&4q\M. -23ZhKVbjoM-fGٶ)tšM;h%pP_C2$_S−!]«8OêX,[I UO)4UTn3eOdUTI>uqacvMv4S{|a$̈́Kx薇yW:HP>NNŵ04ls[jlQh(2]@&,'ܜ-UxŁ%}"K]Ӷn\nJKM#^tvl g_Nٗ չԔ:eeiVa!xd#}gD!ToPv@mJ_#;9p| U> -endobj -589 0 obj -<< -/Filter /FlateDecode -/Length 4902 ->> -stream -x]]q}_C b"y0ӻc#k:9Ed*ճs gӪGxxX(*_rzJ)ஷ.?_¿buQoW\!O$qٛo7\oo'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kSӃ3z -),"t:Ig^K<|tk甤-Φ(l*Q[LVEb,l-*(-鲝|NΉ J1muF'kzuQ-A,`H: [~$xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8DmѓٝdrgL׿Weh%C|a`2#h Xb,{(1Us7Km62 n?ld,rc%hOZ*X%krDL탖me>b2' >m İhFW4^|V/7ނ ;ƞF֣:t(eO-M| - xDil64Qn>]@>}d#Ә~^/Rork,iv׽vݽPxIcm(o+oeZeTb)U֖ס-6[23 -m:{[乗QiZ|4~OkpUN4\o/xJف o[Oxg/3d -v)+CHU M&'<x9$MoUd=5im꥓̊*N"ڹTnqܭk=sycĽ0Tn0 i;LG|yt#JRG -mRYdKC|Za={vّG.e \jKc9VbTц8=h,umȘ~NX۪u{MCsmC:gq3$]imJ+bN֣>2xs~1ZnFҾ]Y䝑{;Zolvpa!= y.!3rxy#%MsG Kc9,.Ѽs~;bl(LEqY/le /!u>Y; -ouxeο8+iO -[N x}ݯ3CQ)dtW<,?|w-hEP?Jnޚn=vlz2ӡ8 h({t/}л+w= ígw!ҏ~D~Gz2!N꡽Ǐ -{kw1q.ӳV;[>r}>?-RHoַћxOo%r w܁a=>})U/"[Au6] .~|:ϦESc/PV厞gr9jGIYy۱sOvؔj>ˎ^f2k6%7}gҤ }5JoM:]MGN%?Tj(z6ft+X\:n"g ;U'S/B߁s;b.U+ 3n`81%goEGkk(ݔNDqX"g[1^MzH.WBcx^`xWbB*V]WЅt:ͺj֜.֎7QJoEUdהC\'AtT-ڡ3x -$N.b4z*Tgݔuz~e_vcEb6Fbz>J 7f#]k#.> -} -+вr8. -C LIy-WBcNXI.]:ƆY/Hn[I˘cdҌ{R9cg_ )?.4T -endstream -endobj -590 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 589 0 R -/Resources 4 0 R -/Annots [ 591 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -591 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 438.873057 101.433071 420.123057 ] -/BS << -/W 0 ->> -/Dest (cb77-1) ->> -endobj -592 0 obj -<< -/Filter /FlateDecode -/Length 4876 ->> -stream -x]M8r؃51 `Еӵ ~AdJ){Bu"b<>CJI~~/9=cp/_Oj^_):(Y+'sH lb& su}6ShR9;*CTO1UN1gI3|t]"p9yI31IP%a]ZaI*J+ءR(tO$SHdQH:kZ)sg%-^;$lq6EI` V:bR.ɂ.+:آҒ.䜨Щӵ(?dtZOش3 -N -QϢxGҁ') jIa1щ:K `lQ1H4/I`b\6N"K 'hd?Vi茖*]j0sElI\` lA -Y ,-XЭSYK\`N qL%q (e ,8ׂ;%. ]L(qZk] -XuZI\֢-`d%.p]Uw1 ɤ$.p]wM 9h%.p]q - 5^ x8$.P&.(lJ\:c%.@cAX"qO`I$.]>Q'1¼(O:,qbx.3I\ `?QtL)E]NG btb-qRS¤?Q$q̀N; b-*`)Ad.4lA-q"]贖 ؂hPdvAI\{I sID&i)ElMH\fK\6:b %C$qAJ(#qI(qAVYd @)%qA M$.f [&x¼6~3J\lQDlAДy N~$l1I\CfaŔ@f]L4H\7J{{LLb@z=V1eX3P _#Ie -b*ZiE<8a>U"$3Ct(6o?c=N) pGq6 -DRd! |s7R?,?m>cDŽ3y9a:Z|g4:jPfC!TnU>Ŋ9X/vƟ?r?ÿF^O;\Y.y]sZs-'z-/rT_}9u7[)~? ѶY8k<Ok a3wD7{{5 z%C\i22n(KKLb7l9.e_>jkk2fqJ۵ ~hOe -/Ӷsrɰyγ; k_Mtz@xo$Z"oD^yd8*vEe%#{vnc;8m:&mA8!!XCɝuI;xD KtҼY`Ha*mjyFA}/붌^ O_A8K:@:JBC߱:OcuIbGx8cs(")Jy:ėGVcDvAm; )Ce}[5<x2=XټkpiՍZv87C;W!|,NaT^U6ɴb>h -NWv<q2zt_<v"G}|uÌ bX>[vY0]v`cuQ&B#>U:OQ_w2va@`gC1WgXlڸdQ徰sv~Gw]6ڛٸ XJ)dmth݉!Aϭwwfnf0C]rY12[Lʻ@cu;ٰ#?0e6;O_$A(vWcu;1ƪ{OV+ -rھ˼`@v`gCۉU?h[im X,@/2|ޞ`CNz!!YsƨDoj@yǃu;WN/=uE쀄YeRn 7ݟ8X{ -ֿ9Bɤ>_o4\@`gC?LRGtD -E ,Iu@{FKFrs߿>+g$-%!x8a]K\(׹y:ĪرexǨxuZ½`]+Nֈέj+ׅss; >t}݇?ynԲb܃uͷcn=}jv[jYV9]<{@#d}<:φ-=)]Xb* $`Cr%?"W89.8|^cL@/O^=XлsoarwU+*Fwph3mދ=Fig6SkWpӡt羂{]q/_7q{rYTdu සʁ|!mn]S1:O۱k%{5ZU -eot_.W]3B5{]׿Bǂ-ԙwqVl=X|;~I􍏆:<䥨N=Q(>V)^JAieVƵ8.7'u.>V|;Ƶ~SzvƶŅK-zu]α>v$0^+qc6>uȏz {γa:~ׯaQw|?I.1woyZwVR4ǕQhg$L⡂a_vok~y:vwڝ.y+<6s '96 -ƥk|{ (yP znVT4sydGvmSUuk/>Bs#eď q|iTU3 /C5M獚]rRq60{,-Zd_^8zo'zcGLjm9* @SKZ_V)GP}_#ڝlyHܱ D͠tjҋ^&ff{ bmkbuqMhC·N3ײ&2w^N֎7QJ/qM5,3*7%C\ 6̦g^WaTZ\ I,曧b+z\GҡnSxAva\C9lS|%\ /'LⷓBi߹B -=.&NKG'L* 3U&%)k &^:Nb/ˆK0K'%'mۈlȘI&ӟOe3֛jzQQGɝc^Ǎjla|%ZbzeiÄ1bzY_qc_^]ub%ucPݴ\2i5ڲ7a[ ^{>ЍwTpOl_ϬIQѾC (Y[2;iCO; -K}FС:חYt`E[~vwWF?B-mAN=pQ&MRN]: E Tc),갔3N(StH{6{%\vע% ٩^ŒI^I]/iogvzdz5U!{du,T̈N]RXzpB8zctJs;wr!19kUwل7(5U_/WJ<@H uSWr$a"RЛ}Qi9aOYJ -endstream -endobj -593 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 592 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -594 0 obj -<< -/Filter /FlateDecode -/Length 4808 ->> -stream -x]K8r#9X /<U]0j /(!)ȬvP]R ?F*_$=Ę˯5/dU+ -Gw6 !9}˿_:jׯ";r*AT !.1%I3\ CkUT0* KA۵* 4I* J+ءR("kvG{Igc2It0NK4x]t[\RZ94tl u`%]-]-@WuEy%]KH%T q3 .Z$փ6Ì l%Q[UFYBt gCl5Q¼E/$qb8.3J\ xW[ԒMR8.'q0h8`}tE]TQ- -*ID]$-qxPC%.],IUZ Q; Dl@MQ``5F`` \  IxɆ$.#CJ:o@ע.B!ЀXK\Xjv$.i $؂"q!xN8ӅNk -%.&"JЈ%ՒǙQH~`WQLD`JQ[@`|8v A0GH QaQF` qARId @)%qA! 0/9ތ$o"m qA"࢈:) x$E53ȄiAkъٍbc~}y]Δ [9Od|5"L8ۆ >RASҍR6]=7L2PAcmΧ - >6oW4u] uLN!=[^oǬv}0&Ͽ\~??1Z?]o&R./>/&7|FN/1,{e/׋S8s0KMONm.םk3|s꽌 U~p]rO~]655!ugwɗ77?=կ.;>uqֿapu2yhr6s.aY=ׅqч4s Yn#vmH6v25yzJp΍ӛsCpÚeS½u"ىpE^pM=,hJcCm]&,?w/%o.me3ȝ|[gEL5)Eyfoq\ wGܠ߂qz Y6T.1debƎ|V-gyXqFZ/891[!!s1E{8L9Cl8D7ᰲY #'n˿a<uNE/In&7U/ԕ-7[(!FDٹ:Ofvp{(d-`nJ/ijV -2_HXo%8:w M Ym|o}~KR<R!ERtj\sg]v d㺺}َ28ę4]_ug3I3O}|%Vo +#D0 dCХV{GJg|ҭ| jVC -G ʑg\C9 uH.BH]rH\zG{슾d~_ܷg㶭3r]tCR1BG޹:Or9a+u#Z6>KmGV#mߟ#hC^o>k7 IE7{γ+,FZG˷|y|f23ܖaT'#54bOy:O~4'z=bVcu>ΧqDwA@??YмBZ+bvfF*#̳-%b9ڶƑ-n|R}4lh~žszzgtw##/xrugaTbleuH;Y>.'<2O^?Uw?7|6g]nld;B:Oڃ|G}ûOWE ݒкX -.f>\7uyדgX!H١_M+&5"t/Q\Yz E߭}KWG=WPT%_ /ÏųjwGg`*.\ -:C|y!>"]uadgwldiImFm-O"\CA>tݓsanSEǗwO̷ӷul9K ]lDtӡyt(e;IY{Wx#3yW#4DF('<Jy6R.%38* ->9-kݍ,Q:O7'}Ս \31ֽǒ-{鼯]=j,/c0ɖ \'g\nY|t:nc?Yu,Xo wdmtx7끧#Oy:D%,7gG'<SǼs~L3NdNy:}򊿙o3yY%WKWS(O8aۉ]wNJg[iu73$lOIJ܋Z?g6ˤm l:OԃlyF$yf| u 3_eRS@w ?MQv*ޣ1u[V9ifU/qS{hl1޺uku!~w$[){d/O읩q3 jyi]yS7Fr/a4?HӾJ= ;{f{)Fװ_/>oA6#4CqTt6;Z_7jZK)~?N4p3/PYM9h 1`NY8}T\K*Ð%1Փf9G8wFyرaA^|jГ_p;j -oVԗm'lڪNB5Ć=7D]盰w5=fR.JTw2ԕu@ ]0UߍoN> -crDXn:#jت͔uk G49l8{2*v1+&~ v++녶;oGҤ?ajoT᪔'T!۳*wR/uHMKP1J(Ϥ[KI.!*yźJT셪U(NWS1;z&;{q#yjo=o"免b~,4QukufHgqacdҊ{咗9wvVczK_e~^Oeq7:+h,EXM'4~ʺ5{)+텮a'6Fۮg܎|tlڂ=rqS-r_A98Mgے|N#.ږthtqП]Y637R~(,tnڦ.|]?OLo4~xz}x'},^ｴ^K+R96oZ&oz.=[65kA4jS7JE6k,. SEVM~V%_q{)TIGvGůyˊW%[ 9Sd% }*Vٺm]Vkw 3U[|; R'gFtloBM:Xc [UBέ@K]g?wΐIߒ欜*h~l;XѝWxIuj4~D~bsQ= *V-;V,}ux -endstream -endobj -595 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 594 0 R -/Resources 4 0 R -/Annots [ 596 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -596 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 713.673057 101.433071 694.923057 ] -/BS << -/W 0 ->> -/Dest (cb80-1) ->> -endobj -597 0 obj -<< -/Filter /FlateDecode -/Length 4869 ->> -stream -x]M$qׯM0t0 CZÂtͶWJ}`&HfdVvMniTe? 3 -hR15EX]9$6N1{K򟿺mG_͔s0_bQyAR -** MYR q[U.'/`3& 3nUf:((%`rA 錞B&FY;ג.O!$->+-:2?I6$VC*%-D'` :_b`AxIq d'\X<D&Ʌ%JCgDVV+`Nk` H\`-l1J\`hnZ uJ ,f* ,צ$.\@)K\`)qbG ,X`$.]RwJ޵9El%.;NV'+qZad$.@NaXLJJ5I9 xDL.NV5MfnH\ƙ q2 wA!^` V+q -  I43ߙ VX#" Hcr2]%31h_ow~z7h{;r\=oe`9 CUw,iJ^z4,eQզ׵\$M$,:!{ ˳W.\q~WZ(^g?Oӷ~Z - i 51!ttCO 6ԺþO. m핡Hw˧'<?D〬^"G$|e^ӓC;ȵ=Ӭe1ry:Cݟ~qOиNA~+M{RB˴>F{2ӡ8vm=FIY}:첷!Š 7q: jBYT qVl<5`<φ`w5(vCR#Rd9wGQq! -ieVxߗd~.>|Za='=;cZyܗs=?Ĩ ϏFcnF'<1ůaQuG\&1ĔcGw/y3vF[y;!*>xFtKegNXM_=t+w瑧Yڞt;X逩3c;Mjw/110,Wq=b=.w`stx6o?}Jڡ5]>yy 9'z74z{;y^9,r?:CfbS'^{GO8pyZ]ZZL\YR,rMW֖+ s>ylIO^VaiZm -ilMveOsBZzz˶`鋣t8ɶknsiwP-+P萚 Y({Fg+zznFbY|-zb{^ރ܎敍 S:wÖ&-}XwG4 ifsCeno#8WzU.#_ٵ~h6ֶwbG?ldX6ƹ1g+nY_c~)vPOqc" -?rdWĚwm"#}ږ!:"yrK'5x-褮rz)iY0wn9L*)Cf7QO[yTJrT -A^ngRnn `]rPxzn-gfxNBy/78K,9 y:^䤤= bgA*{62u4TZF ){ n$}CcS84KmoҰ9#[~t>!0/$M9P2 [sy }t^6|0[^qu=yHEey,O=/}#B$s1̓ye젏PGR@#A{HJ<#<>hޏsyC/,;:^͒'<;ztgCNy6dj8p'r񼟟>Z<ł^Oq9,zSȲNkػj(=ꪇ÷68 "" -kU_eK n,\ϫR}K/۠ek9rӶJ2(v3Em4oV~d16lK([r± -i҆~Dw#NƴNnp-[EK%ÿ&T}WEL sf1 5d7ik -|7h14ct&D¹bAAoz5EL&\f -m5a/X[ń~+T.6ڣЅt:ͺ5uvAvR:UkTYfTnR_Sq"Qhlzkt,LH5 ]tKiTlRϚ)to_vc7y# #֏k1Gl}ÍoHⷋBj߹B -=.&NKcЬ2:57)1O]ۯz%46x$.ubOܥclI t[汕cI5XuC]U4BU@u]VnoCիVY šq㚎qnrV&67 VFٮWƄ0Bw}+:Z;M}I3KW xԥ4wz <4n]LFaN7m &4~6{MB}ĦAh<-ھ|ik\o.S>%_Y}JP\ -sle&W\O;b,KuO*+`I[~ vWWF?<C$mޤo\FFxԖ˰ls-jeY6l r衅[]p2iٖWlUi(]@MaVRZD/St_=D{%lRukђmpulddnRS*uʚ!Gg#cg3BH_ѩh-RG?]b[%sw!{'&tUQӯ:&A+XQlYMzNsj3T~֫U viHg)MCQiY^zj/١T -endstream -endobj -598 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 597 0 R -/Resources 4 0 R -/Annots [ 599 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -599 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 273.873057 101.433071 255.123057 ] -/BS << -/W 0 ->> -/Dest (cb83-1) ->> -endobj -600 0 obj -<< -/Filter /FlateDecode -/Length 4737 ->> -stream -x][q~_x?pl#Ff 󐿟j"t3>>ݪ"cD*!zGϗ_.Rx+oH19?UIª肽 va_]6ͣZ贲׿TdK˨"TRFe^[Ǩ9̰4UfP S :03 ye3Wĩ`3*%aR:"ft -JwN+Bԑyל<)8]98tXE$9l!uZZa1)%,iXzyFa6:bԜOXC`zNH8-Z{bu1vEzQzHq^PđFPQ =F*HbqL`l!\V[L$ -Hq1Em hnIFqߒT…5 (E 8׀;9.0 ]twq4k(8 xאxdu( -%=E7Up8.VAr\@]$q\@]1:/ ]m渀@z]P=tp\„[q愈`+BtX -h>Vqߢr.r\`  FTq*Ӂw ޅ`9.q7$ꢐ1 ,x9.(,d:/$qXH8.qJk + n-&h @ni8Bj0Jt])}wӰqI0P @"z8.pQB9cqXP-8"8.9.e -7;=- ;? O0ocUNtts\= Ŋ̥D@/q̀N>t 0s:[ds\O:8. Y`\UHyf U3M0%- >im9.MLsXl18.Af آLMqAQ:d @IqATMM_f &xLƥ lpQXl~ N|lё8.Υfnِ@HMφ 68xo³k=3^Ҍ3 [ِbl@| L,cVT H/1q=Ԇ1f.2[2B{|/{y) -_.84 a#y>V#hq %#10>bNO 7JL_`c,hCub'@~I~h9lx0i{^/RZ)ܿ-Gת#}g,*r4VrI/C'=?fb5X553aVC\w:|.7}w_`<;ÅQ-q*eyvn֌~Z35ͪRW~O; t|לn~C$C0f̫,@eiP^넖ybsiڡg:}yNXZۅVH7ⶐ6r:z-\,qdnXX<+&ikiMB -4YGY@m M7tPnv_ӡv#oxjF56Er%K:KA;靳`BSAבVS -:~`ڤ;.k[5_i3ZwZ]lצӌՑ%EӌA'1Ky #Moc_|TijӾϑ& \7ڒ9! w 3_ڗtm㦭"ʻ菇1M9mhm0]`Fs:Dm%lo|fy~UV s6TٍU`9ܺ7cQyNM\ +uQ{ⲓhZ?l^Rq51ƪvą9ֶZ{|5>ewDv97|wZOϡw~jѦ]>YNv9z7|O߻];jSrM5tHGMWqezñozlp ֺ3鐻=F n gOsԭ")F*gp߮#IM~=zϽ3鐺᫾0cEpGk>Z mDžkKmg }ݙt}n=|w@xݙlh>-pv2 -SmᥧZ&,O_k߬'/8} -;ZA:Vxykƍzhu61dzt۝yNcozYՌU!-e2"~+nX@?6=Acxs6ƍuGxV{İr߀G$l[`g!uAs0lcvZG<ޮ>ݙthxÐ@AfVSi\5oi]d`֮׽N1f.+3z~ 6:[OV_x -%>ݙt^_I#=Qk㑇Z۳웕fHK{~n5A5D$0-ݦONw3Z盏-<鯇q W8}+'w*Wtbxvot_d=H9nHjTeuLwX$h8ܤJi35 xZ)"TOʷ{2ls 6_ìa'5']JD>^>SARP꺐sNjaYMӆ[헛1/C|QDD$P :T%K'SHEv{ -9pcOmդ6gK̰̉OČ9KFqQ83bufkԦ֌bed#slNWŚ=*@WUa1:4N}Ӝk5􍕦}LsQv,2攥A#]w2Mh̢oZ-w $*bNLjn6X--KP\Ք -uJ3FO[7}Ds*vr[Fτb=V6C"Jӣ_YJߩibᇢ^='I}]aj@iR̶d'-KMM5ry -yLŪ)\ -e6b[6W;m{>S m)]ηVKa`> oF8A?Te'k0BW}ĹvH?qo^aN#~8^ץ4?G>kYBnۑ,vNYXM#~Pڌ2k5{N -ma#Zfbqdm:`M8ƤmU8h/LM8JI-&#Bq؜0V&f&@')U짶)L:WsиTa-:ˆh6A[0qbcvMv$i"}k’/5á1\AJY{89kTׂ&-Fi=)ey(t̲R61[[KU׶m*m*n6G-ξ^)/ks)Ք&h{m.!zf#}瞧BpQn7\crwsJ{ -Mp> -endobj -602 0 obj -<< -/Filter /FlateDecode -/Length 4927 ->> -stream -x]K$9ׯJ!= `+V8LLP/#쨷*#t8stĿ1始IS,.wUT]$ "$\OrW.)y_Ie1UJ*è!hWULS kU6Eǩ`:23 ʬU f,*JK`hFptZ N.@tr%wYTXx#Yl1N`w芬H/KFeu :C\tEc$SJ8`Ӱ:(4N/]bu9-8x™#[5n#th,-h|-2xЃ:a h6r,c6рNNXF*H(bsYl1r\`4lA - -ЭIq\`V*qLq- (% 8׀;9.0 ]tq5klJr\` '-0`GaT4XQ2p\`F=1J ,xWGi9.]0  ]w՞E$ wA!` iqn&4 xW% L[ wUD$TǙ~ / }w1P x9. U#5*$q\8oBI@%!S8.hIs\QX&auAHC9.] ޕ qֻK3ӧ|%QyW){ۥClW}8Pmiʏrf!_yuey @٩zKj7SeٱQO4@ #`"cwl~/G_m@4u]G=ढ़Vт{2ϣW]BHҾ6VCk,HAzl1ON[pYqwح}=ة)'շQ5Ԧ dD6 bsK?O߷Ph:'R͖-zy)#z*W8z0ywJ?yuQW<0:}#?w6MycL66r}齧{g{C7ܴ놎fK?_ŷBΝ szMS~i?<ڻi6w4BĹ> ->rT\=;hC,Am'`lMd/-9̽'/1ٰ|M~&ҷYg\aֶ9m1|#z%sןtןqMK7һ~o*TgsC(\_{o\iǙY`ljVKjm'󓑣&n⵳&2 tc_|5\8:3s7 .mМ e:y&OisT\w2ϫ]1s^LHsl@8Sܙ.laLq9X8à -dQ$E`螏rۘg9HmIX Z=tyᡲvu؅+li-;5y/_yzQnj7y5zY -eazgF3m>B<>*Gkȋ jy7ib܆54CO,%,ԥ}ko6PF[1$y5Imm-nj ;֊V" u<,{OS}dV)>"rwǝee*@G-vd5C=i_u]Ở󤍞Z=jo ngg ^W>'my2!rh8bCjS`ྏw, eKM+:-?{B> -y8ٙg=g.{HEؒ=Q^ݲ&<<rl }]ˮF\_af +FY=?V˺v]H2jzv<zA\9>?6̈ǡeYhRslV44LL[# 汋gr[<:Ŏ{2!v?|s{fo_ W,} 9<mE8Km9??му+bvzF:TZz/ΟEq}u[}Vhhq -YeOoO׽ݝ݊GϮGy_?.ȌWOy8dīX?}CLy][.5ӄ)-m^rh.ΈNy87-7Kx.X+[zJ[@HDB('<J<0N;ma1B;CEAև1^X -[wM=Y <|Vp3騬U0AFG]pܒ7R)Йt[oq~O/Uٍeƙ)a--%t׫){;(@֗u>H@N/v/s;{/y\uX5OVT|]h:ꭠ]:asUTvn?[SM5Í`ܬŜ?^TO>ȧ,\4˅v|WYeU=n ҘҸr.\wdN3}ծԆ򻒍N$2<`F^T{),0󕯦KUnh-X Z(Xb^|V{שKZ.(֌VJ煗[jYe3*U+)kNva_rkƬI lMJ:Ft滹R-k*o4Xnݱ&~#ҔK1QZ7z%]=_..0] - -z[Q64)ަoEFgV'pUJ̓([!EζV*^::󀲡ܥBdc iNR1HR*ꪘ(re/ĮBe!nvUy6ҋCmqEW{};-lvc)]+6@ -Mh%KoD?RNƍ/yi:EgQi?.r4kYBWn]~A%/a6PێXŖ4q\뎯m.2^;tq;ȼmڀ=]R9:-V᢯.cә6$_[⊒!Zoˮ,[I 'm.0.M6.\. B`_7/4-a~uzs&HZJ_ziI+R/9&P:oPAN-4lsjlQh(*]@&1%8^ -5hҿv}T'U*-ݷx5Z25r=Cl)k,sWm)M˶˲h{a!Ees)ϰ -*ʈr VM%:X1`cTrw -IY;KBsk ~S7tnU~oϖ$[, 5Ry 0/@SE 9CAo RVcI_H7 -endstream -endobj -603 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 602 0 R -/Resources 4 0 R -/Annots [ 604 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -604 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 555.123057 101.433071 536.373057 ] -/BS << -/W 0 ->> -/Dest (cb86-1) ->> -endobj -605 0 obj -<< -/Filter /FlateDecode -/Length 4924 ->> -stream -x]M$qׯM0t0 ZCtͶJ}`&HfdUVultwe? 3 -R1O'5EX]Y+'sH# lb& K_::>)`?R9;*CTO1U>:㶪3\N^R gLT fXݪ20Q;I3tQPi;QJ5N)A=Mu:v -i%]B>I:[|VZysJgSt`-&E+"l1Nt ]ItN>'D]N:䓵Ji=y`ӊ:(tR|u[e$-%xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8Dmѓٝd_|gL?SVk%C|a`2#hE U a#yȈlyae9 'ӑ@{~0Q)aQ9|w&GD>h*^ody>Vۺ5SR-`kiv@Y> -ND1il6ʈו[%O'bż.C4O˿Rʇ|orE^eF󊿘Y ?6{%1n){ϐ]r_X> Oyv/7,,<(KcJTԎ>OkȔ>} pa\w0먻:8̠@Dq|uie5md'p/y6@aw QGz_6TF9A/.cPu,ӡ⩟weD_E?;H!˴渎cy)å k=yEgijEJ_z6tՆN7B:Xem;vImwtkۋZY(QVТ:Zy:ވҺ鱆˵6djA?:: -;mvRC9KE3K5]n1*Ry6q-4㟣"ib#w-"P-G\C#u"wVB(n<"oĄ;8^[Y.;Qo}à!y7bՏ@ZA8۶zc1 |=zR֚`C833jaJ4]$+>x0ϳވOhm2RYSWHzWp /cwk8{=}_3 4mP?_o_?4Źt=({tD -E lߓv9ErkDyڣ}wKh6"Ɲ$xIs'KC!r&BAwy:ވU? cexW\>iJoصa\Cmi6j]!ʈuij<bݍxydvx3jA1d{e9_qn2[)h٬ZFn̯}a>Q;Hs%Кka=yz 9'z-74z{<<=y^w.ŬoXl+yCoo/(S݁OK 'x=1¬gkx~vU#YOӓeiiXxے,༴.iHKOQ}ٖ,oFGnQK6v_e]3`3! e_Lf.AMrUgf yvL4lD9Cg6inúw?aH3+b-s[mɾ}vae>X۪u%/_gƺ8if=fc-1O8'sulp^QY'o0|^:{P|sd\>Fe 0LVDmn\DDz+KTD{na}&)p>}'nrr,t.DrS8ϻd0ʒCHM^ZǸh9I#|@,o$)zoY]_,*#t</QEGۉ^(1栘Gr-+;NyL R-ړfM5ltЯS5-G B z+֫I/bz)Or)45a/X[ń~+T.6ڣЅt:ͺ5u5j(}*ZTQMfQI}M:ĵ~D Nբ:Yс0U .tr-SJ=kt|_va32ƈZLK*1ܘr.~;(+Bm:^6?ahVGMgMJS>h EG^ &^;Cc'y@2wftRBz"ݖyl%e.cyDRȤr˩LszCˀ0>C?'w}=_}Ǎjla|&bzYZaÄ1bzZ_qc_]ub)ucPݴ\4mgeb d7}ž/mm-dj.xsp)̊%S:ΰUe+3 zT`a]ڮs}EWYiK ^ӼҼG0~_LuQ{qikIR[.9,4jeY6l r衅[]p2iٖWlUi(]@MaVRZD/St_=D{%lRukђmpulddnRS*u̚!Gg#cg3BH3S# &j5dV!]b[%w繾w!{'&tUQeޠȷ*a9[Vbs5iNmv"e]FZ*a-jogo=wѦ -endstream -endobj -606 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 605 0 R -/Resources 4 0 R -/Annots [ 607 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -607 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 123.873057 101.433071 105.123057 ] -/BS << -/W 0 ->> -/Dest (cb89-1) ->> -endobj -608 0 obj -<< -/Filter /FlateDecode -/Length 4708 ->> -stream -x]KHׯ3Қ|?$ @qEZ8v>YU=it9"/ g9UC;sx"o);z{肽Hreן]#j)iD*QEԌ{err-ȩ`F T0(Uxת3S gTR`u0Dvpht\*:i=8o.98-6 -,l`s:[ӂt(Ndt]tQ6cX]N:%`ւI9X`S:(tN'lduj8-?GADe8PA& -q0kTqsV\[ Xl1p\z: -Z) -p8.G0D ]]O01xCr:A׬.@'=ޛSk!`s\]f@' >  0 A3t.tRr\l7qAPL'8. $AqA0n W 4&8.@br\X:آ EqAE qIMqAQd @ qAMe8.f j&x̸zs\ lpQXlq NzlQp\fnِ֛@g]L q\ 7rk{ l@z-V6d <3 _Z#Aepl*Ra?fV0E<&#w%H61^HYpn [s ݓ*%AstG Kawj%y]oɜ7+Sp{0z/0t`&`=0+ 8Qb\fW.MS6_Jm ~؍w?^~oo |/H/ S/[7eqmkfNYt6eU޹TɊݷ_+CͭZwc - 1@?c,%aG 0֫#HMipcU`pOT8lX, B$^cgg%@H&dĨ%r/قhIq;˕7Vi?4ەی - =ՎCe-Ku\@Vs1e}yNb6%~I"^UoVXzf㖽6 ϱԕ\ԧuhL9*/}𹿮Meξo 5ڗlHUb9HJ҉5grmw5mdlcҾю44ؑ4뮺g5#O}+vٖ?UɷLz6wy3V !f}yN>]Mlqևe-j{;Ku)2Yu}:lۺv>|HUpܙt;!۞˖^Ls=ja;ݟ9g>TJ@o#J|AQs}yΆ^}W6vEd7=[ZF[GӨfEផܖ)᪎G.c7b;i|g׼gT,қ}5|g!wGg%ZG)mr܎ƾrÓ' `#d+'/sژyGy_s:dx|O{՗t:㪯c7X>;m\}KͶfL+ z`wdg!)qxg)5so*޿s6T]c޹w_ou^yNU\;}Q=qY%WW?K+*vXa[G\'')^Voߍݙth=p Őpނ{DXh-"iH"[߷s:D3wb닚m yΆMv#D-G{yN_?WզM]>YIk:W-W5okq;nշ>lᚼjhܛ߼&jñ}ٝyΆ5BdܾgANm΍Z;}oXƠ{Rt}fg]9m$?[/Ϲ;jUo+{7ً./B@lg!݇dNZ|3Ќ%gS/mޫ(C7W[#+}lbC9eޢ,GoZջ3@l&+*/FtW$EO/l[}<-nݨ{{R&P=>Ms;2m>n^oqNn˚? s}4S~z'|;]cw{Vō) 2yuf-'>^В sS ^tztgu1i/2ڟFtŘl+~ъ3N1 "edJe +۔bsR飲n(M #R"=0Uɵ^ ra˦Xlh괥P,v-UuELGqF\f릓UWݹ']Pn/KEU"teTRR1hhILNS:Ftl)S5/m4K=[ǥQZ okH,○Lj[BZr8"' $Y*ld -J%46xHe1\ HKڪu{ D9unjJc2H*R,3겘(,OZ(mB\y2'+\n̝/tRV7[a> ofZ1A?JX<ە*a1 PąF_Fq 2nƽ]~ӜVE|pZ%Ao!44JdP[z&cC NlY;l+SuKۺWr#ںW*-f-ξܝ()/sg))u6˺l{nC\LEfW)GΔBp͇HFrwsC'zPyc'I5;x0xz5E} -͉Udh<9}Q|ihxw?mșEd/ -endstream -endobj -609 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 608 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -610 0 obj -<< -/Filter /FlateDecode -/Length 4919 ->> -stream -x]M$qׯM0 @ i F~LȬAAoUF#|| 2Y%r zEM+WR.9$6N1{ :㶪3\N^R gLT fXݪ20Q;I3tQPi;QJ5N)A=Mu:v -i%]B>I:[|VZysJgSt`-&E+"l1Nt ]ItN>'D]N:䓵Ji=y`ӊ:(tR|u[e$-$xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8DmѓٝdrgL׿7eJj -dtG|64XPb6n.ld&<ȍP?jSJwXcE`h>1A/Z˜$p5`â!&!y/v~^@=郍G3uBP -0 Zf@lh-b*>]@>}d#Ә~?^J?\k&C0s^?kݫ U4v݆FVPFիKRmQ=-ْQhס"ϽZ_Mcͷ?OZpn\|  w=(=f.ao=}~G̐ul(Cڥ ]#UH7.Cl搄7UD3sפ!N2+h3;e>{h26RpZ8Jy:cCRr€ւL0=m([@cӍ(I-+*SGO;Her.9w<Ro76FXyV؞.sfnC{0JdCqzuQݽL|c 膞bFԚWh6X!u5֯ҮadQY6<6;F[9vH(2z|/dgC9_GzGK?ƀ8 -7Ҍ lVH{u-#|Z/,0$ǹdCqkl㟧مgG5pu,XzQEPGiyWL#c;'<l1ůaQuG\&1ĔcG12bFi 3hg$L4_P/qFc]؞\]+?܎敍 ӱGyMC"ĩdw7{2-AJG/,ZNح0Ie:>TXo Dc.PۥDH=r0e>r |bzȔG-vCv;[N=[-Yz\{ |]2eɅ|Mqc+sR@x'YOΫA Pi;NL`ޚsGyNy_>|}3>_\׸7m[Ni,ܘE_,}ޑNJtĜcK>5xy~ofY}w;#OvvXqpSmI5>08½y6df!Rk:Bt@|=8wPc? @9Fֳlz†wZxΙ`ɯ?jwbDmQ_Ny:މ+ǃzÊzG|o7yQA0mcc|h%goswU'#64bOy6xibo]>z#bsm6Oy:Ǩvt>'+Z4'<M/b*lÆ c:0v=^SƠiw2i52mb do=_8zކ^K]o.S>%_Y}JP\ -sle&W\O;b,KuO*+`I[~ vWWF{x}s/&:HڨI߸5d-a}[U{eس-Cnu1ʤg[x^UuhtVb6%[uKiq[LѥW=IKEK@9֩ŒII]Oil[[]g+k놄oR3v<.+;#:cv:Zc/,8яDVyN;$uׄ*jLل7(}+-+I9@46;Cf j4F&I&>)O{ -endstream -endobj -611 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 610 0 R -/Resources 4 0 R -/Annots [ 612 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -612 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 438.873057 101.433071 420.123057 ] -/BS << -/W 0 ->> -/Dest (cb92-1) ->> -endobj -613 0 obj -<< -/Filter /FlateDecode -/Length 4784 ->> -stream -x]K|?1bdv8C~D.=kmN"cĖYsCJ9wt)[F?Dr%Org-rF/ߓ!T*~ Ĝ%w0%p$A`uQkU&j'`> -*`6J:Fi?tztF!eE]NG#BtkIOtx휒t%]-6X%`IJ[ z' [$` -JKls.CRL:Ji=x`ӊ:( R|u[e$-?AsЍGom>cw B}-39jfCTnNl| ;/ѻ_~_<~֥Y5\feZp|[,i=]f]t,H#ܥ,WҞE{z=Z{ק-A7z4nt_CZtx?ymܯ+H*pvsucbzb}Öd)z_]$ݙh&*-eh4F=SLiwnGIR)”%j|vg - -J; [1+~z<,4_АQz; fÿܻ`6zd]Q"#qGrn$=ntwpՕ:&6C;V!t-(Oa%2򹖟5iiOuІf[ -'P4!oE;d|5oi?96H;O_u+VyHDﺣ1g@퓌 (_A/2[=OQ|TNIbyҗjNXy~y?p{g!uW}/-;z}qiOzN gح}[1Ԛ +m6} -bgw9b_wx~=7wg9q_uzz]*}e[tt}"=gݙpSyH t^.[?Ha'ݹڙpH~]D[ -硫l>c+e;;gCv-w}W(~*sXAY)^o~ѦyLe~윗yҸqoGo|WVzx~'| 2Ua|Lֳv9Rw~;w<}$'.\xϓ01؝y֍ TdZ-e\ב鼁t~qj0-ӍgWP랗1fR;w8lmUWs8_y}"|#RTקlϭ'pOV׶rCZk ղ~)z| -iІ^vn O$3=?es|A5:EWL/cs Rj'S.Dsع67$?Zӕ+5=Oi}y7#GKk(/NDv|T DΠz5YLhKB5Ňb3@Ӷ[M PظbwzԮ MXM]&%P/ U*kTYfTR_Rqu$?Whz6j~I -\MK:At9|XS5o4T;^]آ饓l([>.ŁFJ 7Jx9yWgb|RqeVqR /MJ>ajW)1A -)zHjܬe'qy.ttRBz"ݚBʺc.IUXuE]\ɅW(,N_*^* r8T|XG\b\" T*ibj*cfH2[+;?I&ӏq3֛jz?H5~yr?mLQ-Lօd̴SL,:m8FMSK :n kײF% }C&6F[3bud^;6m.mib.xspζ%̊%mK:ΰUe 3 dCa.vM2ˋ., \`/xNJ臧׫}69@JU¥a$'Kxuͱg(P-˲gӦFs-cIS6'RWdJBQ2UdXl -s-cKM#iGvReūޒpuddRR"-.55CBLUR>̝)OR12S{Aj5v|J!C62B%w; 18kUxل(U,/gJl} ͩ1d>e"-ܒӛ%Qi9:3o> ~; -endstream -endobj -614 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 613 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -615 0 obj -<< -/Filter /FlateDecode -/Length 4953 ->> -stream -x]K$9ׯ3"V Fp@zzf^/~3Q=C-Ӫ?"ϟ#YNyJ`B\tRIRoR?Y]IU]_.o8퓿\?yUM1:%_Ie2QY;ycTNN9̰(Vyab -f -0C/Zap*!J -!cbtN8 QEV硓^q:'獴9g3F!9-V#8l1:xN`vZ:آל։.+:".` ЉZlZp:)' ljVNr)ℍX-ӰӁ'!0UBKNgaRް:؂@9"(#h"^8@y? G*8P!N{рv2.z)1`:آ@+؂h [hZ8.Р[#@o …  4(Phpwr\A ) 4hW8.]mwFNV[` As\`Z -qb) Ыp8.V&wUUSƠw%p37xWY8.0]e@?˻q{M -n +#?fL&we@8Ig-ZyE ,xwApUq\`Rct]w7X I$$bX.hIq\YxL I @Ɠqbz8Zs\auEq0l1 gu -LB9xW9.p]69.p*p\'xw(܄sqXP- XOQqWE+qW.(}l\xɦ[x 霚]xo&LŒRS?q̀N |-*`*g$lq<] (o゠L'8. XM錠83p\U& --~l"auE[qAqAE qI -(Dn2q ʀxS 0.) D-o"cmԎMqA4EauNSd-8 &؉9آ :GfnMx@xӳ]L q\ěl^x+E]1^]2^V]3 _E28v*R ̬8a^}ꗨ1gO1, sdz#ټ>._?a˧_'~m1TDTA g[D{>6#%h1/1k=Ka1,̤+3z*Hv7y{[Gb&׋y:M#3:88س5Wݵ&K1@x?z_ -&A5(3>|l[(᛿]}C\N bzh8BuERq$KžKiPw$dc;N:=c|KKd˦ˠ|5ͧfߦ79m;d.6Hj 4M.bF6 -/SePmrݥfKjm5-Ɏ&áJUk/ڧktM!_bkdl)OgSjk|fCj_NzlGڶ볱O>w;!{oeH՜faoеٮEmgW1[2J75+tuSr//QΎB .BNpN-a"~SU@Wuk|w;aBx"PaC'pq܈xh59֞;Aq |%RKnF JC3t={rޙ8ëGPN+nC{O7p"7ky*`pmc u@=³CdqH} -Ǡ'е+I"4Ezp34H>ospFD}⩟wFPemȪV-G e ÈofNRmV̧Ռ@:zIX߳a|>-iD*( 82Pey6im\|s{UgW*ke/Ur2S6x9TXFțdABe,˾˳F?z% -6笎s!4w,ceJ~(ʔk'Qv.σmƹyҊ%'/ &Iw(+R~8 T-E}jyyhm)g?S䖲bәRvs~Vގsyn9H9Jщ5g mdcKedyԱ#)__uםXTSA6={W+Tպgez|9ٴ卼>3VOccHnޒ0@l#\C쾿0>kc[/2*>:q{ 2ϣ!o+:o_odC߻G<nvP]=/͟E~m[ʭu[;~.d%>y84[w{ΥyM<]gHO,,BB2>uH;ҽj^@<g7AMko>ãwkjOy47[op =t_Gjxwܻ?zzQ rDRZR3n_JD|vxGzTOm,V4OnmѶ];sh'&=v2áOO_SA-떋[_TaFAi}xyYЭ]Ny87.J}'n~<+!iy٨K9D#(*>mպU5YywOpahՍ \V)bP{wb`tDEt[󙖿ʢO4AC-e[ -'P0#/E>v3.Uެ\`x^~-TɿL=gLgxӑ'<z7~:7PeoOy8TibL$֏Hi̻Az^& "1vKV&9cټ` U(.7@ -vN@}g[wgӗYZ=*;"$N+SKļqliw9Xڄ+Ym3|\7Js}'tfa= bQ5K;˴ p&DWu8md6Z^7rTS ڂ_Nڟ?")wc$4˅ލb1:)&a>,#K*{))D>pa>T\ %Y`A3sŌ9\$/&\56VӶ[CԢڵPt52ڑmG1o:uI|ם{ գ[-JQu2ԖCL'F|a_RAgV}k7, H%#zriBK7Su RefucDr^EpV5u$6z&m\!l^/]UDKR8ahLTa'HS!EV *^6R/wu k.}l^D5umkNc1HR,+ꪘ(O^(mBuZQ+s6ҋ}qI[W{k9MlfC]6@ -Mh%hD*mq34!PcӒ{]\eyWܺ3+{NLGM,CKk wRٺn̶2L35Tlv.gR2"C{&j#V:/U!^yMJnγv^!)k'}Mh-7&@]Q學|(KFs=W̴@TO=SMNoya~c| X -endstream -endobj -616 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 615 0 R -/Resources 4 0 R -/Annots [ 617 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -617 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 683.673057 101.433071 664.923057 ] -/BS << -/W 0 ->> -/Dest (cb95-1) ->> -endobj -618 0 obj -<< -/Filter /FlateDecode -/Length 4799 ->> -stream -x]M8r`^x`Е= ~Ad -)U39 wR$ >>CL}UNR]o?^~)zꢨZ8yCI`71\.o.諙rF_ SL1*/2TJ[AAP=9K*3n0%p$A`uQۭ* T0CgVCD QY#负$SHdQH:kZ)sg%-^;$lq6EI` V:bR.dA` ЕDlQAiIsrNeTi3O>Y$֓6Ì ( l gQ[UFY#Ɣjhv[eŘDlK `lQ1H4/I`b\6N"K 'hd?Vi茖*]j0sElI\` lA -Y ,-XЭSYK\`N qL%q (e ,8ׂ;%. ]L(qZk] -XuZI\֢-`d%.p]Uw1 8 +III\&)'q%@ sJ\ƣ 5^ x8$.P&.(lJ\:c%.@cAX"qO`I$.]0|.O:¼'BwPY `?J`Aע.A1 K{)aK\(\f@1L M 2t Ȗ.tZK\ lA4(qA2 ̠$. -$\-霢}f 0Q(q v`JQ[@`|h%.MlsDlI\f %bؤf +؂O€Daq蔒 q`^~3I\~[RAKҍG+a8$Ea|0QiaS5:wMвUWbyw -fګo L֓u>dۦK!tXȅZO {g4Xa30͆VSP$Aʭ - ubٷKf>;/7?N)o~]_8)2)_~fZ e6 ڥh_WtwB;W_g?AVvJ3P;8Zgqy[1C8akH=L롍W_  $N0o;'MbCln#x-Av-c/K["=̘BzmRJQ; -{ӡqYsԇ1$|tah\zӡNp: M(#~Qfm^˓ñ;e!)Y%Cic䞫t=c.6(ï_oE#/2w8Xⲹ:Yِkůc+4UFAnc$ifDX#׭אNX CMwNy:މU? cesڗ[Nkڡ]+Nֈ;V ;}>}bgOy:މg$@/Hiww4?㞬th>qv7UFƛ7C+\aZV3&Un״?5xg>@dgC-{2Un;Ҿ]a<&=:Yu9_%?"W8zng~G̨ul6vӳkOy:Ǵv- =|ev:5P1rKU6ߋ{26Sp^;(}]'<JＯ`q5S=2R$Ud9%28*7swzγ!ǵ`'`5[GbͽgMn;h} {ӡ8vm#FIكj]wmdh`Dyef1hCMm3B5{]ߠcAM̢lxߌ3̶bsdv@NdCq:טQZeCR#Rd9>3\c p(͸JAfweVx?tH>q<zʑqamkR˞n9v=QEƧrOb,:φi';ǴFugTF3-sS?gɛ3ەQj43[/x`u𗸢~et\ܮߕGfk{K -MǏŜm4\cms`̯,k|$HKBΤM*#??,OIӵg-KifmC=yy.뉅^jwnܱv]OOl >O?mQK>~ّҞe@ ʙg6ר&?W;1P}%{\eKӂCfQ0!wO.C̈́-M[ưey!k4 ifsCmn_gmmWzy~Uʪʮ}0C)UlplfC?2y:Z3WW|{l^Ŏ=knF`˸j|[~ymkvaob5Ii@<д,Иa9L*U +D9 q}|ۢyQhѿޫ \Yo!ܫÔ=Lۂ_{C|;qΖl"U`hm0Ecf:ni{ .F'h*FǤwΓle司O}u=W@Y?k7юx.a5.; x.x% ٧aC5[sz'<T},o|> Ϲmnm#2_ۓvl q[,3+srfcG7$(c'_h}[(ߙ4;i?}>׻/s)?.gEQt^=p w܁c]*X]ppz5Ae 6!0G|ý0HYecL3KG/«El0,7-6')ʇҲIeɍ~M -0{VI0bfrN.g5&mMl)+ u.ם+0~joPtP6Z_,*ESZL1`ao';b./Uk7Ny,5S-/{7TjtS-g+7VLW^-iUh { w*&[bb=N n ]LlkYp o֎7QJgצwj2ˌMk6 ]w60MFN𝅩ɵrDXniͷTUs|7CݦxAvcQ"} #֗k1eXpc6Ż6PwV-oIutiLUUF3U&%)/k3U &^;Cc'y@2wftRBy"Vyl%e.cyDRj5|J!C}1MtJ]8w͐ cr֪)eޠݕr.BjӜd|fIH[E>BKAoQJ4JZOև8 -endstream -endobj -619 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 618 0 R -/Resources 4 0 R -/Annots [ 620 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -620 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 236.373057 101.433071 217.623057 ] -/BS << -/W 0 ->> -/Dest (cb98-1) ->> -endobj -621 0 obj -<< -/Filter /FlateDecode -/Length 4672 ->> -stream -x]K丑ȳ^cm؇sl,j }ߏJ!*ʬQBu"R1b*!zGۏ.Rx+o(19۫U{1 >ZöϿmjZ贲׿TdK˨"TRFe^[Ǩ9ܰ4UnP S :07 ye7Wĩ3*%R:8"ft -JwN+Bԑyל<)8]98tXE$9|!uZZa1)%,iXzyFዓ6:bԜOXC`zNH8/Z{bu1vEzQzHq^PđFPQ =F*HbqL`|!\V_L$ /(q1Em hnIFqߒT…5 (E 8׀;9.0 ]twq4k(8 xאxX:s\vFqwi Ъ8t+B 9. 8. X胆j[FnRs\@]Mq\d.(|r\:m8.ɄFXq愈`+BtX -h>Vqߢr.r\`  FTq*Ӂw E`9.Bq7$ꢐ1 ,x9.(,d:/$qXHġ8.qJk + a/&h @niBj0Jt])}wӰqIpP -@"z8.pQB9cqXP/"8.9. d -7;=/ ;? H0ocUNtts\= Ŋ̥D@/Rq܀N>t 0s:_ds\H:8.  Y`\UHyf )T3M0%/ >im9.MLsX|18.Af LMqAQ:d @IqATMM_f &xLƥ |QX|A~ N||ё8.Υfa曈ٔ@HMϦ 68xo"k=3^Ҍ3 [ٔbl@|MM,cVTMH/1q=Ԧ1fn2[2B{~3_qyŐ)? -P_消n84#6  -8&ݒҿs8pyS.1/!7x| NhPD C\)iR7.=Z1^b2L^?x?~߀ѧJJߨ7hMM$P3Zו_#F]W&X>ۏrhAHNnmOG[CWW;%O^~i -!&H |3y_ήTDܼʩis6u,tg'3Z7{YNӡy=ţ7:Ĭ65[8ū=bޝ?ܷʑ[z61iZX'@mlN8v\ R<3auWgj9Fx%|lle4HۑY=5.- xu鐹&:{|lZF"is6Ԛ|곱x TQo }Ēϒz0_z,_6s6tȻ|nT"n4deQ_reDX?FFrqh,|ח.{߾oxTjjI -ĝvPJ-Hhzr]u[EVV/Dž4?w'KX6h==w(.^Ԅr鐷񜾛:Ӳ/Giv>-{$N+H5ė>eȻN!6OĔ{u$o9yԧ(~xz:ǎ|x^Rǁ5˽36C߾xsY;q>vG&Vx2<Nӡjc;[fQ} tHxZlB_'/}gIe|ۑ>$kX;mΆV!ڂ={D_蟙M2i Hm2[{otHȆ=g&y˚- ;mN}dyj5' -~ N!x#V}O(CӮ,'{lߛw];mNƍta5[rM5tH9צLfn>6C'ڭ'օ>ozlq֝6C%&(1hh)>Y?qPftȧ틜}}*$5z3"<{ِ6bLkyU{Gk{YZ{=}bgwڜϭ><_|$sĸ;mN{U_xj;^CY=Hj=y}Ywڜ}SܑL -:Wбx$(lH\?$"Wp7&롵l\c mӽOlwڜ wU3*zjWѦy[\q4 [絀9J7vwe7IWoObJk-tH?9XYUݸ'hX#Mjf"oոrnĚC!f&\pRi?V FOU<,dçdًAIб}HC5'͕b; Ts z)TOok7 =|f}԰tA(6:iݿ״STn65T.X[TJ˴b%rs0ih/*HCA*~jxp8 ǏT.Xd7p/iXNnlmdoY9d.dsftj.Nw/i x+e!'l=a5+# es*֔QiWRu -mթsY\.饯4-OkW"3SHm.YJ;1ۅ~# YMD\–fKKR*TӘkRnBxF6(iH?N.@nkvTzb^gJfBӜx't,K[Ta41AQTڣՋYJj宰q5ײMu) fRA2ҥ&ҦٽDROmSt #ҡ:l{,)شI^O= I k+-7x9r5TegJSF -hrbj6E)&E d3r wZ%ҿ5mV)hVqy+ђ)mZĒֺH4Y66MGksTq52J>MJ!3B5)o!6Ta> -endobj -623 0 obj -<< -/Filter /FlateDecode -/Length 4988 ->> -stream -x]Ks|?1bdfzwlvKTI/:촪(?~,RZ~/93OObV_JHY -'+  |ʻ }s2<)F=TFO>x/,P :F&ȩ`F T0(Uxת3S gTR`u0DvrptJN.DYNz鴞7JN' tXit9-i` -^s:[]-@W`uE8!9]ԓVN ;٠tRNԬ# - pơ(֛p\qIqAM,q b:؂)2&؉9آ :Gq 7ѳ[֛.ft]D\`Ȗ[ xeg`w bne g ȗH28v*Rx̬8a}귨1gO}]sdz#ټ?/07iH)A|a""hviEBxO2f-M72;?,,d:rc]h/`~0Q*`Q9|s&{D\?H檾+֛󼻭.^Woz^X9أh]RRy%Lc,hrCͧ IY$݇5[1|DxS?7?/$ ,Y7VJ9zsޒL^Z&6yIg/]e^_m(~mg*vVvk}cj;vζlg}oN_X2n,owr]w+-E?t0U &=Wp"2+tKy|Ք6>wi?>[y=[q|0ϣY]"*.˞z̞$;HHҨ}C?=hLuuַs<idLzQu F\&1;ǔc{12bi 3A$qpi>._ҷo xG~cy1߅GIDrXSG[ P6\6쿆!:N*KQ^xzC1Pړd}crM۩~kjR~EJ%3ugH].}ƨZ͇g$ ! )mQƴo2ewߨOl<;]kWJir7#.|%83mF,]DWu.) K_oqXF؜dڶgcFC]ۅ(X;96`ء(`nWcm.NZ [6Ny\~L Nج0ID:3Tw'W%Rte.7 ;n naa3>_ktsoo.&(vic:EI>@xDZˬ`}^N[o`NG:7TFY:1U2cydr^'ii&(#_o2xnSargYj;ϥVtS=7P3qW_h nWqx -lh8PޘrjC+`DumLhcN:&[-5h/|OCo+cϟ{g qetp FDٱ<f6Fj3Yn`t_9S}jyq̊6ɔ3m/J>b&&R<R.re+X:]87U[d[l/1,FRn_u]yȓݗ.ع帉Xw <2CV#k%>{ Ky/Q[g5ƒy3-&쒏:rs 7Է8<_1V3*҇m[<ۙ+1gy8]!Ǟ2zv5m|ZZX7xΨ̇ji v1TSAS6={%1+"4lj-klڊFsĴ5\{{s;G<ذo>L 5-2*>y`C~n9]zum=s`C~ܻGD\32ݡ4ZF|v,m#o+-nbRzܑ{<ح=Rϼe=]JG|vVYK4/m x`GCf.i=bG~xnoޚN]A<+o o^y|c2<6Y];գCW;pzQ <VEqAtQ1~H{G@-6ߊH:x,~-4N; Ei<jĩGK?^{5AO̫g.+LmPU-< ٳx0괥 nһ&ez߰paDx[,&y#gk^L/L_?$IvA&~=[ #6=|ELQԲOGD8Զ%{ӳ5-FD:p"k1^L2 ¤󕫦Ѓ>U -4}V`xU,v-]uMLGқo\V{ɮKZ^NVWVJO/E*Qe3*V-)kOrb_RAgV}kY -LMK:Ft9riB) :T3KO_ҍǥP}-B^Nԑį'ԶqzPwVq /MCqf;<*lTH{xUf/]ey@vWA0tk걅sY'G$Uc)uULVSbkb[7;m.,t6ڋ}qI/Ur;%MlfC]6@ -Mh5hD_S>A͸ӏ4)m=봤.y|奴ĪBWIy/k ־i|Kdzq -}spN)+Jڦth2/]Y0WR]O+4]ta]3m.Ԋ. B`_W0F=dWFI+Wk/ #i%<^ӥ[^9Gzmen䴡B 1IC˖ؾRSdJDQ2QdD_lr9[qKjq`kLѤ?}T'ھW*-[f-ξN5 Դuee=w0"SѲUʻ3v!T'^㎉HN'sC_MJnγw!){'}Mh-XMx"^WtE_E660[Cjg(}VLDRSOS諀hi}~ 9 -endstream -endobj -624 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 623 0 R -/Resources 4 0 R -/Annots [ 625 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -625 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 502.623057 101.433071 483.873057 ] -/BS << -/W 0 ->> -/Dest (cb101-1) ->> -endobj -626 0 obj -<< -/Filter /FlateDecode -/Length 4876 ->> -stream -x]M8r؃51 `Pӵ ~Ad -e*{Bu" ->>CJI~~/9=cp/_Oj^_):(Y+'sH lb&y/uL9/IS VPy?h|TAO8Ŝ%UEr -f8cJ0úVaI*J+ءR(tON)lh$SN{-BI9ҒS8 Dl1)ZIawKJv99'2t*Ŵ'UNVaFaBt峨-*#,lqt ocJl54ZybLt`%0$ - $01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq$.l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kQSXdu8*J\FF ɤ$.p]wM 9h%.p]q - 5^ x8$.P&.(lJ\:c%.@cAX"qO`I$.]0|.O:¼'BwPY `?J`Aע.A1 K{)aK\(\f@1L M 2t Ȗ.tZK\ lA4(qA2 ̠$. -$\-霢}f 0Q(q v`JQ[@`|h%.MlsDlI\f %bؤf +؂O€Daq蔒 q`^~3I\~[Ŋ9X/vƟ?r?ÿFN;\_oyZ!boťlmk92> odKYCmv_.ƯY~ Gެm}*2zip0rje^;UQ߰&)|"#t]Ӷ/%s{tyuW998Wi4+ƆWt󱤣:ƭ$%\v_Y=m+^e*nXl@uҌ_FQy6TQ_weF݈ ~hd\utH1I𺣫ecnv,gvΗ.msoawK6IyVKi3e OXCtPzw f=)ʅuo4RYb˛IyUבz!F6$#Eyf2"mXz#V}bE8xuZ½`]+Nֈεj+ׅss;>t}݇?yͨEF =XǸM]uU*D|k|ȯ6w@`Cߍ8oT]Afta}^vc҃;u˹~H\蹝M>}clgQŧGtqo8ZîEegCQamf{;mZfTQ`gCiq_jz!d̥Hj_rjs~WQvɹ[H=VzA@ÐvGu{pw@`Cص%{5ZU -eo#3D#j]i]ܻ:fj\Aǂ-ԙwqVl½\cms`̯o\ʷHD;Ozv4hM*#??Y24kZ Ӽ<؆x\ֳ7rѽu:m\Q;x]o{/ y?{Cn{w#DyнX[ʌul?ۆ#vK[ͣ^VOO_-a-=]ӚyNJz0|弯ܳCsYafNlLBe~> &/O$rqiw_RVϐ>;|P+씶l_vUņz>E&ط<_q\pFZ 6k6b\ }Uq`cRA_ -<2禗vC͂RZTfֹ{M]_甚m5ͦW}G_DN^WVR8Xw_lRW@ɾMz -I%}ۮi2ۂ)(Oofj,r#>>L?c&H6 RF-RUXn^IjA\^T -0gW֡(_2rӖWF a^^k–ٳԼrVa3By2.oG&mI&1iIYh}ީY^:k+Jѫ)KR2 "tS1`yg*dA9; v7$\>֖-. qcI3}Yj}h|=k5zS-O3;VLg&KiQhPm7x`xSbB*]WЅt:͆5 5n("Jm/]2rZ k$.'AM; fӳQgTZ\ I,HV*zҡnSs ^ɱ9l>J 7f#k3|JWqe6qR/]JE?ajV=q7)1O]5Nhn6I\8^K0c+)s\#j놺&& -i\Ʌ7(YMUv4ovqhcqMhvR67 vFծwƄ0BwRu6v*O]\>I&ӟOe3֛jzQGɝ>B^M֕dtPLë6m8F]S/+:n k׫N쵤n }!]-" ^l{Ǧ/'n,|Z~:8L]g|fM∊%ZgXEFq:ݲHIs=PX0m׹򦫬+ްӼӼG0q_LuQ{~vb$m'Km9 ö3=ڲlC :eԫ-> -endobj -628 0 obj -<< -/Filter /FlateDecode -/Length 4760 ->> -stream -x]Kqׯ=aaafZk`H2$h=]G0/#,R_~~/bL嗋SKO 䣻 vþ?~sy}5CJhwWVB A9AR -*.* JI*ADAaZ` $AF)QC5Ncн3z1$t:Igi%].J:-.)-lqHI:B6IaV:bb.I.+:آҒ.H$t*UNVaEa|tx咨-*#,l!H:!Fa^VY-l1&-|-*x%L%C h%01 h$7OA4tFKD`lq%&V-6ZbJ\`H\`AoIi/qL%qI kX.{uF ڵkI+ k-j:K\vVZ22`VK\ &F%qwMT$qwM €5h%. q8i5dQ78- X Cghl0pK$.p] kl5蘼#OԥAn1ʃ>I\ب F;j I\8 ]QbwAKFƒ`QIK\2P ]?tç|'rǧ1W - ͝U4898p8&X PuzðШj(4(N$ߢ Ď ^j)^6|aH3/#6Q6s -#D_(-#H]=S]ֲóp y a|6ϛrK'xhf`ӥiv}Td'͙g2= =׏Ee֍OTekέ&b,:+{4}"0gH)y'g7Up<}0|EUBW&X(幟jeY%}3X=5rΞӪb[X&mua=/# TƉg/]$lV9*_?a^f2qS֬=~2O'D0Q;Yv9t둵}~BdV5﫡y#g3bQxӡXg:$lqKc.ODr&{.GvE_cd2oٸm'(|BWwwγ!|LHj',y!ZX񎴳}̢^x%@o#j3$ _G:Ooϋ=bd)WE|bGFH _zm {!v|1=7nYtdC0.h=\}2??Yޕ?zA^yX}v0WYd/kGnj'*)G:O}?vzaϹ<3 ;y+ 3d+/Cډ}i'<2޵?Uw?7|6g]np\eݟlyד׍g!H!3&XA4‹8˻6f׏N|/wn˥m_z\-G:O?Uhwr_V:Ƶ{!ߟ{wL5{R=Ӵrsy:Ovօ]\;RKޓ]$} weٱsuwguOrv} M_Fw\=22Oy*9W4t˳:φppw:φxp8>6}o t:ko;wʹ@dC.wh/:Y"yuqu9r׍ uk5>Yz}WC½qwOO,}V#fG&u߷:Yِaw|`˚m ;Oy:D&˻F·\·n@vdCAӿYMNς(Ny:>d|ӻ+4=68L`S -"+OZ?q?| MۮlS? z[jbS:eTnZՇ}0iVE_4GwHW!i4V.Bl?^:*úxնllurhzvتM\)٬ӲQTLYm1T K>(R>EiJDϊ_vˎW%[ 9Sd% }*Vٺo]vkw 3U[|Y;RR'gFtlFM:XckUBf@K]g?wΐIc kUoل7(ұk[xJ j4~M~kNYQ= * -;C|?m>?F` -endstream -endobj -629 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 628 0 R -/Resources 4 0 R -/Annots [ 630 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -630 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 770.673057 101.433071 751.923057 ] -/BS << -/W 0 ->> -/Dest (cb104-1) ->> -endobj -631 0 obj -<< -/Filter /FlateDecode -/Length 4950 ->> -stream -x]M$qׯM#:!aAafZ+`I2]ӻ* FOWF#|| 23Yc -.?^¿buQԿopW(LN',a -əo7\o/:[rIgt~$x0ZMVY-l1&-|-*x0K&J$0N)J,`b(+рIn"Vi茖*KL`5l!\Q[l" -H qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ] qZk)z ,xגVxZu8Y޵Z ad$.@NXLJH)@ԅ cJ\@]i5dQb489- X 0Cg(l2K$.p]0 cl5阼#OԥIx\O8.&*+q> 3wL-$%q"npF qI+@WԥI%.p]В"Dԅ @'8T$.]嬕w!uF#q0l1`uRL!J%xW$.,߂ߟ)vk3wgX@P@S/Saw#W6ڵ/Z$iLʑa>5@#Cܞlpiwn|'*s[#P$ Z#"@z4/ߐF[,N ?H!rІ]Zzwp2!9LG~uR2niޜkʼn1liӶܦza!`[CGv@L{2!N07~ #ƥvgÅ?ZF-;h~ =|~RF7m=nr9VQ{QKl4v*&<zcMo >3+P1rKU2ߋ{h2  [JYy<Jc]q/u@REkA&qŨ&)A<φT{hluk 2n(6v=ؓyDZk5J\pg 5 ,mȽP^7XPS~weYgm#Y =ٓy_j73$U

cطlmFi~eo|b]eFl6_ߖv~*:#=;To<^I(5 F^>sv/MnbuncEX]1oxKٹ0t^,s -- q!fY2wnO* -·sכ߻%&qW E{v~J}&)ZvC?w[Oa߶}r~Zqh0"!ǦKK/1.DN -=/. l]v/rO*-#{ą2ε -tᨓydݸ/*w}d7|Z9[ͦhy,SpI\ i cfCRr1#R)g͹Ny:3Bqy|h.EŴZ9!͗`rY6E_,KsPRL#䣠'< [Z=)mGǒIky~Li|Yn熝@mmHHZWxݳk;|6K3toGk7{ef.2a>{<9[^[y??!}tOy4u;(93)G>#< -ŋg- zDd?:~9Y-8˧#;an;[ۃz8kK"W*x5@b -½=|]~9pc!n/QeΚnd5ec)Rn:YnYܴ,}^Fn7q7kmt_NDeMʅ)3 Oʒݦu'g[+T>:eZ_,,E"9󪈣]v3@? -pGG"ݞ,H8LiLiݤA34&w5[>TMd sł9ފsդq87S &O ULBŪbCm]LӬkZXw oTkG('עwj2ˌJMj!I.;U&tfӳ^XD-]"[JsBK{T=MP9^#:! #֏kq~ 7f#]oԮsrz\hYMUKX]YeLI3IWf徱IzZ.B,JHIn[I˘ȤvLs:&VoAQ|걻> -endobj -633 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 311.373057 101.433071 292.623057 ] -/BS << -/W 0 ->> -/Dest (cb107-1) ->> -endobj -634 0 obj -<< -/Filter /FlateDecode -/Length 4712 ->> -stream -x]ˎ,qWZP|_1 21,x yaxѷfZ#`߇YG2#շ 6vea0YTW D;~z[CŠ^$/./I`jo]._yUV{iUJ*èkS#֓ r*AZF`!\a8PzF$PZJVC$ьNYi%\::#'e9g#bT$-dtg$-:x t -xHD.J:'pm9. bu?yO洫Ń;>Ui{|dKoL~<==HFYw9>S#t~C.o{X"(3ِ~J$Gɷf?o6f}o&.O>ݙt}zW5vWHamzGe;nX@?5#A}^ (=`gӡtc_#oGo+}İs?9*I _;;'6kmSţ5s6ƍo2(lj*9p+{oGmW?5醽}D(u3tb c? WZ|LexQvtM{}H34D7fpRC%Tw0S]b)erBLCڔ?9 oǺ{2ls6}7zqy^@U꺐s8גj+[F*oqӖ -ʜjnKU -wb_z\犽Yx&6 !WRZٮVa *46h-4|{2nƽ]r9mJ稶^/]y\pDdSN2lXf4y\놯fsJUTm+ .4-cW#l ~i͡|Vᢽ\3uJ6E*%S:h eSaMLl+)M짶+Lh܈ti4e]4I-T[i}xx=.$-^oXft2kȃP)4c'Zh# 5ۘRM*E d}ɍr wVŧҿ-m^)h^q<oȶpdMY|\H4Y6uUC\Lefg)ߑsE!TgPDMm1;9p=&Tp[-=LhҜE0csK6Eq^*6T4콤Id?Þ- -endstream -endobj -635 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 634 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -636 0 obj -<< -/Filter /FlateDecode -/Length 4907 ->> -stream -x]Kqׯ=a!AafZk`H2LF֠it1"_F$,}UAHz1Oϗ_.j -N_.?7V&3lBr& }:jo";r+XM!Ă.-+@ JI,AD!햕 $F)A5OC^=Ly<ijv/M{%Ax8M$d!zDd11X vEdQ^iR$y <Cr*VaFH><YrIAgx~$p0[ nxHA_B! -^̠qIDɐ&ډ"E LL`%0MSp* XYy ,+ M$a5$,X-[$,[RIKX`p!qm$a•kX.{uF صkI+ k-j<8YܵZ id$,U'25Q5K 栕a 5N kx (Gpp`%,z ,wu'iդc8எ0Kи0oI{$,p],TV|F VT#ajZwIJE$,;LX&"/M*(aX'$"/Lp$-axRC%,],IUZ P`G Ed>VPH1N|DtKqO?_~۟~xৗI)_7TAqʹZFrV/4Y"mr;fyl׶[Q(ȝ:_~)XRfu12_aԗ A_?tͧKL*$iP/{8oJ:J/kT/Nn">;G2/[GeAw)>/q(}r.u2Xܩ"l Q/U[#HBЦM̖Hw,횵aZݝ5~tn-(2eYM<aiw_󱥬 '۲||3J}QYE2LsMS.<:Yf^6~ JkGJannW.sԬlaՂC~V-^rيʍmRnlW⼊.mt׍UwZ|%͛/ʴ~Aݷ]glm&vOGVKU׬IoYڕwVe\+;6ۜmS:oJ?0VuUDSDRkU f#0I%e5tXK?i?hlEZt/G);ދv~J6jh7PC&?:E;oC8> -٭cnrѴl;o<ˇ|yT 4O`EBu7]ZǘD|wz^^p wN̾zu0K+,蝬$yz>~^c~I2$ШXM_>>m=Ctc=#7;5c{gxΪe!~Y|oKSJ.=twoZ>䬁)͖Msuwߤ 0_<\Pwo~+[6xcI/;WI۲l}Q{0ٛlej"#go{N=z6G~M+2+Tzj2{:^!luځ5& -k36㺺|Yefy։3i_u]Y;3Oqqߺc=!? Kgtiw1tԪzͭ>?!}gVy/l93)G=f y:/</VtUFV|[J#5Zw WwQ}YW8)mA x'<Đ%Z,Y|ڏ-lpGZ#~M ޜ;D7 -iz{:q?w\{zWzǺw6?<8}vgo}*x#1b)X:b1߼rpG4:O'īE9+J &~tG/={>_SZ=0RbNJnBIyukAdoW£74n~C,V1~oyqMz -bxoTۋ#2ss!gҤ˓uf ]W{>~;ŗ!N?<쟾#<][o{a-Sw=ϟ22N߆qx8KMٌdsѽv;9b<{L-VD 4EQNy6/N%iGrH7F.iQPaUnж;S`o ka9[)8h|JRj6=,r`YS&PuJ!F vn+~~}.j,g>zayՔP dPkߚ )kдWsYk5_>JAͯv˫SUy$]zmI,>KMgE띚_jzaRl/::䓦U&GS.'@&jC|T-B”ƒMjiƕp}W pJ!@;̣W^|Z{r(:h%/lڪDuȆP'υ+oQ-L_[3I2F!i u:xC]ǍZuՀAuDtؑMu]mC Z{mҖ|dk -pp϶%5+.ږtptq7ˮ$[wRUSo -}u]-}ӅGAla}i% ׻ `jJ}u`L'Sm˺|CMC-=[65ZhAG;jlՖ -miY(*\ -L~VԒGE-S4{M*UߔvˊW%[ ׻shSd%@}JVڶoZ]Vk7 jVmJ 2w:.TQXIkl1Dm<\gdCRN`UA"]S;jICzLP9_$Q *Yz#IPZ>j$  -endstream -endobj -637 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 636 0 R -/Resources 4 0 R -/Annots [ 638 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -638 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 558.873057 101.433071 540.123057 ] -/BS << -/W 0 ->> -/Dest (cb110-1) ->> -endobj -639 0 obj -<< -/Filter /FlateDecode -/Length 4922 ->> -stream -x]M$qׯM0 @ m F~LȪZA~AfS~/9=cpˏNj^_I(?7V.N^G8M .yu}6Shrv)FUJi+b4>'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kSӃ3z -),"t:Ig^K<|tk甤-Φ(l*Q[LVEb,l-*(-鲝|NΉ J1muF'kzuQ-A,`H: [~$xۘ0Z nt-|L-*0&%LI$`\rIbb 'rx* X[ X [F-6; -H q8+q:E u*k ,)$. \$.`\r,qZp%.`]냑vKA ޵N+ xZu8Yk8.:A`e2)) x$$.p]18a Z xx4A+#qgQb4x9- X 0Cg(l2K$.]1 cl5锃OIGx\Cx.&*+q> 3wL-d%q"nF qI+@WI$.]ВD @'8T%.]孕 wC#`MF5a -c BҁwFK:R1K\4mJ\" LN!)$.YAOԅ ^₨ ,Q[\t Ih`5Fh` B LY#p RL6UI̔"Z%t F7a*`-5% z @K 贓 f؂"q)DN ҅Nk -%.H&a%SL$& -%.0JL)` hB-X`e-; R2L[2ތd[I\U(L4Rd4NKZo& UXob'l7EMY$7N.9Zo& f`^Hތvxg0"2 MD^x}D|&+8c@seg@F7 `&V)VJ6P_cn ߢ -CĜ"52cX8Dmѓٝd| &~zU)?BI_a5oQ4HCBH2"n-.nd$?w~XYtƺ(^F4°~0Q)aQ9|w&GD>h*^ody>Vۺ5SR-`kiv@Y> -ND1il6ʈו[%ͧ`b[n|!nӏ_w ?}z=_o4M_wYrk:C,h^33<׆tkIGy[^Rg.#Ӿu`ŖeiL?Oߝ~i ߇cYރ/.,fuW?cc.|flߊp `g|ExgeSAm2p U<!x0YFUQϸLkH9r=\j!Q Jy֓]tf[^QAWkjJWm4-|>)<Η.m۩Kj{l,eg{]^dvB),Jz,ӡFֽP=L5^=7!S *})$աVi?W ^XrWM,xUWz0ϳ!\nqMG1NӏH3o89k=Bpk?y#&ܙuYZw!xkt~wrٶŔY>3> wPz9,ny:ވ]oCWC=ZƨDIӅM2<t&C/5uE쀄Y}업ؾ~9\{3D~DH;H}.ŧGl7 {kXHO+P1r*sXE)^߲'nDg#vPs<Jo|=ƵzvsO){vǶDžK-/XzQEƻw%R]1vyy:L{~ׯaQouG\&1Ĕ/_{{YJg?Df10| -V3 -o_l4| <~o -]wړ.y+<6s }{{)aq}Rk|;jzP'%;! jJOoOI;4kZ;aiFkC;ywN}>זyNORaizmNNtbf'Rsym9qftdknsi5;0qءz[V(yANʙ WHep4w_yϯ/ť/KZ^d KlD_Տm7-#q֛KuC/mo5>(Y|犫ZOXl6+>QX\g0N1;:ujfs{5_WzgXҪʮ}0C)0{u;k~? n6a={zƸ5[ȸn|ϒee,oW+Ͳq+NP\s[8rA#:r9FP}0C}`)VnJch7 .Y/aY6wn9L*Cu -7{-͓BVnʉ!Ô=Ln {C`w<zg˩tvM.<(K>6}^zj ?.qFZ<\7 4۞xiD Q$&HJ5{)45. -78Vt_ss-soG,7-Ng1HPԷġ|X_Ofj ߎ)×u9_4iCo9cF!fg:9)t6];9{~jW)z|]_,*#̪kIT~4NcnI|T,".ǔjtiQ P~_qND;W,3識Z&>iUh7a/X[ń~+T.6ڣ(Ѕt:ͺ5u5j(}BZTQMfQI}M:ĵ~D Fբ:Yѱ0U .tr-SJ=ktӂ_vaAUƈZL -Ub1mo'Ծsz\hYMTK ' *C*|5HWBcNXI.]:ƆY/Hn[I˘F50[Wb>+A1r -۰aBwN=hh1]Ϯ:ה1nZ.݇Llt32x2>aϗ6t -9L]g|fE⊒)ZgXF\Bq*ݲH^Is=xWX]0.m׹>򢫬%Al/i^i^#zw/&:HڨI߸5d-a}{:xZY=ۂ>4zhVLz%畺*[UZ'F*k%jSXU'K]i{9^ TnZd[9co)[,Y๛ʶuuu=fnH葩&Cؙ RSvFt5DtƖWժ8ƢKl> -endobj -641 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 108.873057 101.433071 90.123057 ] -/BS << -/W 0 ->> -/Dest (cb113-1) ->> -endobj -642 0 obj -<< -/Filter /FlateDecode -/Length 4695 ->> -stream -x]K8r#{X` { /

>tgw¨10ćPJUS.TW*c0U"!<]o?_~!8cŨ ]08|tןY`3__/l^7YW3v׿~c!T *rn8/p)I*Z̠dLTfX -ڮU fIR \TZmu0DY#<K:I.@t>vZҥ{#Ғ-dctXo-&+l1h$"l-+-\D.AbkQnpZ%iEF:Ag`W.:2O8bFmՒc:؂Ηxآ(#h`^80P2$vHQb@!XLr$JCgDVG^ba a:bI\` lA -lK@tK*i ,X.TX0$.\@)I\`)qb ,X:o$.]KK\`"-`h%. *H\@] ##qzu`bTxDExL. V[fnqH\@]CK\ %z]P=tJ\D ӟ0VK\:D]t@ ?_~{y)?˜g ޷[h {$-WR5J ]ПSB$z4;n?|_ئ粱 3` ϗO'?Gb &s`c ӵc_8ǶNNFtts4`\DhyjZ,oi빉q pbpX&}dܝUS|jr+Ahqc7ӏ??[m_AC4woU0|mj>.s><ˈ˴~].y?Ov3D s:|w{)Ĵv `Xf[P 8Z4Fprpʺ -!Za§< (pӰW3Kr/jn˿auκ]Yn̬Ͽ_翩Ieٮu 4ݘ1F{TW^mFZ(3VĨc(;$(f;(%hfR_ʭfDmP3r%1ͷ -_>]AfAؖ˟K;klSݴsH5qs:]>u+Y֜qknK,m!c-#KONIk}6s1 m >= {P_ctELɲ/nqO涻5CqLE4J~QGfH*Gͤ_s64}wx\sgdѡVnJOKPz܏tح-rϼe=]wݻ+#w{G[]j sOt=\wP֏]]s6c޳vV)$E_㹷 V_Q{Q9Jwˣ)e="WEA ?/,QPMOw\Fvkx^yN׻}صXW7+_gdt-8O^ade6G5[WET/J~%s{܇iQ|s:|xXqWpn}|>:;mR̶fL+^#9S\r|{fٿ*J`ӡjgߘwwyDቨ;gw̭ؼcu{Y}{1G7އphf:fzzowfN`<7w|;5/H/ MKʯoGx5@f -w#o,:)ϳ#0wJkUh'kneVe|#/rZ?f9e\wcy.=OIF="G^= ?+%M 9")3##GLJ6s_ &njG/ &A1 珪E:',X9 Oiݠ揩/>󻜍] 䁩bA^|jгH|1l3@jk]P5Ul3uJ*,MiMhvAR>-[ר"QH]NY:J? Erф,|I3K9 ]tsiT(b͚rWS*m, /6}m{*61+⨌*~ v+k)xR}6}2>)3ASSj%<6xH!4i.Bl^:*!=nI]Zl!mc*낺"f -SlbWW;]{[žpk+5T-68Q/f\IUfZY#(ΣA?A&͸_.4g3 |`u!͏ ]%w3F0[v&jA1]e4BC W5h(1 _Sͮ*町0.Vj6bSkmZ޺V,[Nӥ7j,E{;Ug|m'S:dh eSa-d@g -u5NmY6E.m/ڂI=O7l#ڋci!> -endobj -644 0 obj -<< -/Filter /FlateDecode -/Length 5008 ->> -stream -x]I%q_&%dcX||~%10_0K2#i?xU/#/K]?")<?~)89!Opw(LN'g&0L~ }ۿ_&qaB˓>IXpTV|F <wx]mw78 `F aۤLWI%,p]^xRH"C'8T܅{OxrJXr ˈBSil׮"Rod/Y.k=i? *Aq8e5L/#ӣ-8ij/wVWb~ɖn?M롌W﫦YdIp+>~=3潏jl888y͐1g{ :=SW>ϳR7QTRvzmTތ{-Y/𦷊ezz=v=nm0sÙk3;ed7eЗnv-Ӻv >/[wR``IZeT<;Mf-+kUGKBTE,Z[򽎬 -E]yUV֑؞.sfC{>>8٬Ǯ^V'b|[< =3` Vk^:bj.`!ecXvⲬۈ3mYе⺝U~c<ǯ#~I$YR#`1E ;Y9h̐ZFl^+ DX{_t|Za>[{vG,,e XjKcQWbTQ0=hum65ދyΦOVy>=5tQO#n.]Bʱ~q6#xã'pCT|xF:ʶ:K(};E-%5|b<ړ]~Wzq]s$z}>6lJl&B10,Wqz1=P]On KjsOCN+4<{-_5aZ;u>Kgeg~O~ΓWKǪ2u4麘.uvg9y5}IWK놖PVkhHJnﯻשAJSx\dE.XRlmrJdy|.,jmYBy< "^I(;[ksrOu60_]Κ=4}eK -K3W ԭgXh+-PqlYd]3ԟ,/ziyT>: K[v,:ԑRNik/>8]dP~g9mTSZԵؐ];y`_ײlOϧ؋o}05Jy{wk#0.NѭZ;nۆ2Aj.$?%DlAbkk!zF㙰dѐWƼI#B_ 9VϣĦlv0b.E.qwXȳ]kYF1_E)f9 2y/bڋ1,NPAٳ1z~o8RmKulu~$OV6Qqҏ -OB0SA}=<~09=0eƶ[]ELn%ZsV0pZ(IQuwۛ.CpU+/7a w:0{NF˯p/p1ӠbԌ2̸n,P&AЮ~ZK~7|~Z0%H^E,;Rȫvٙa@FzRti;:54uXb뤭W=2?zQ껞V6'^X3 WG+I%]|Ƥ۝|uwϾ~_ 9+7Tt-i|J 䠣^s|-N5)NP擄x{/yo -&:P<#>%[~]7밳)\v݅Ճ6ߞl;3y;$>[bU*7!4$Fŷ [w~)(oGsѰHzSg!IoPP^<_iUnІzsAHV(WL'ڮJKXTYh|U*#O\̀UcJ龢IZN]$W3Uc+jRAǚU2CXOʞ]5PuVugȾbkO5_Xv6_h$RI#H1ZYGlk&Z)i|mL_o8D>A\7q*Z+rxwb6PcK5T?nLԲ%+'Îla̦w@| Z̷Ms-,`H9xgKwE≓6..#BUd+1 JY~r]CFm> -endobj -646 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 416.373057 101.433071 397.623057 ] -/BS << -/W 0 ->> -/Dest (cb116-1) ->> -endobj -647 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 397.426036 99.933071 378.676036 ] -/BS << -/W 0 ->> -/Dest (cb116-2) ->> -endobj -648 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 378.479014 99.933071 359.729014 ] -/BS << -/W 0 ->> -/Dest (cb116-3) ->> -endobj -649 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 340.584971 99.933071 321.834971 ] -/BS << -/W 0 ->> -/Dest (cb116-4) ->> -endobj -650 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 321.637950 99.933071 302.887950 ] -/BS << -/W 0 ->> -/Dest (cb116-5) ->> -endobj -651 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 302.690928 99.933071 283.940928 ] -/BS << -/W 0 ->> -/Dest (cb116-6) ->> -endobj -652 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 283.743907 99.933071 264.993907 ] -/BS << -/W 0 ->> -/Dest (cb116-7) ->> -endobj -653 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 264.796885 99.933071 246.046885 ] -/BS << -/W 0 ->> -/Dest (cb116-8) ->> -endobj -654 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 226.902842 99.933071 208.152842 ] -/BS << -/W 0 ->> -/Dest (cb116-9) ->> -endobj -655 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 189.008799 99.933071 170.258799 ] -/BS << -/W 0 ->> -/Dest (cb116-10) ->> -endobj -656 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 170.061778 99.933071 151.311778 ] -/BS << -/W 0 ->> -/Dest (cb116-11) ->> -endobj -657 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 151.114756 99.933071 132.364756 ] -/BS << -/W 0 ->> -/Dest (cb116-12) ->> -endobj -658 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 132.167735 99.933071 113.417735 ] -/BS << -/W 0 ->> -/Dest (cb116-13) ->> -endobj -659 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 113.220714 99.933071 94.470714 ] -/BS << -/W 0 ->> -/Dest (cb116-14) ->> -endobj -660 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 94.273692 99.933071 75.523692 ] -/BS << -/W 0 ->> -/Dest (cb116-15) ->> -endobj -661 0 obj -<< -/Filter /FlateDecode -/Length 4427 ->> -stream -x\K$I ׯ3aKB{@"VziEZ8*WeNOҎa#3˝-~qٙK|pdM -jEe)d+1BdR > ./?mw]8듰L)٠ -X֑ -CTX,1BbϷ1䠱 {V-@ k,JH -Yἵ*Xf -31_T^%LLxCx YBNx)'! E*H%⡝2dueYlN2dfW9[Ld5s&6II1)<Y EA@k<,rVՋw%d>ʃ,| |,6E AFpIYp次pJ/p,I<4 YG AjXC1f]@Hհ 2.aASyŸ+~ -cѰ wHÂ|f kX5pb5,] AqH4,@|3tU^1aAf K4,kX `aAlJJQÂX,xHT^4$ Bd<‰5,@bm -aA򐅼װ yȂAd8djyY`.j}@2 )DcЪƋVy<4,H BӰpz F% x5,HU4,@(2#3x ְ.xiX=dA6aAUf B5[3TQ *M ʃ, ?Rl PD ְ g/fְ gװ)fҰXȂOÂb4Y8xjXP\FYԛYÂB&Jo.+e/f^UȽƻґ;~3T m֖!:Q =w}VRz -(sM~fIъ M8!/f$7xn=_/GLϬeW_{0n, b3 e۝(7KiM@ ?d||Y>sZχ$'޸Hcȏ̬ :glwgG~6a%9YC+?UF5l r eni%U?^rf_;:ȡB߀tXSx*d᪚{;ʾ R:dx9C䯐ȣDqr޻ zr {R Yۅ]!t0j*!{m({/gmOm':\OSF{^vGAH|톇+Gd^LA*zm`>N3zNJְ%==@,E= -Hn~rscFt5֛TlEs&9t[P: G*d9ylH@ۿal #|rt7r|Vl[r*]O+Pwx/'Θ7Izõ*ZULvV.G>r薽Iڨ.ߙ4Qæ_,Vz.99F+KݓXw@C19\m'd_VUⱸs r,JwnS0ˮPn7'dN18-R"~O3x4@p@fЕ* _pU6ձD#x)o\f26{ qn-No|ӶIhӳTjwڲt'*ZW JRa~WR++0#} EwMfϫ[H*au ~{wL*j*9_MZm0^#$ϗ8Xz#!ڱ}ޛھyf,IVv_Ζ#OzXRR-DZ`/~9gÚ8٬'t_,mYC[F*m%m:9dZp~+G䵯4aI,^V=f9Q/Kt4 V-9.KڊkD[M1ڏ-!VVbǮtlr+|=z |lj$O[xZ HaZ$s:'o갏E% b-Xtrziqߔ%Tsm]Z!G[rOI&7[GzOZ7݆$sƼߵ~鎮BGVew7wվ綆j"C9ôխkW}a#OCYF淗[&ςw?>qEBھ6:f8"w?c:F\jvWo\Vk,OiG-:e]o\"W龜 67.{WXX_Wo}8۫qC{5DQZ_=T{gÞ}NŃVL) hl7&liM %yN|nRiUݎz#cT){~S {hj%] \- Ζz< -+P]L:z˾!O!ve1} k1xS,RGyLwm}nlOp0|qs}&ɻ&o8K*ޯ(Wꫂ|ݚ~MKu;rXq|3wS7rb'-os>~m'y6yxYcT]÷)w\}ol/@h$r%vm\U;YJdeyan|n(Vo +䗓|+d YGb0LnPc׏DB]FM0@J|`X!gtdY5n%7rdCUwcq,O b%iAZ[? vgչi[[|D0-]S_Tŷv4*Z˾!I!]N -ۆflfO&oS. {)ImN*i~2LrWBLvIbhK,D}m/: LiNvˠS'fɻhwЩovVI3=vaMh;˥mvJno5N*4:xlɮ[]' 5t 9tS~ِj}&s}A;_fr;.owFd1&dyOl" -<`vt/^ќwhEQOrkԂ7N< <)7f(:\fLqRWU-S gMyWü+񦭌"^ϖ'@a64VgG˞Kfޝʣ%5ܼE đ-ܴ|w>WZSOF\_G@-/rz0isctT}ܞy&la"|W. e1 վGTVSr44`ޜ /O~T$Iz|UN`k. -endstream -endobj -662 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 661 0 R -/Resources 4 0 R -/Annots [ 663 0 R 664 0 R 665 0 R 666 0 R 667 0 R 668 0 R 669 0 R 670 0 R 671 0 R 672 0 R 673 0 R 674 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -663 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb116-16) ->> -endobj -664 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb116-17) ->> -endobj -665 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb116-18) ->> -endobj -666 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb116-19) ->> -endobj -667 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb116-20) ->> -endobj -668 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb116-21) ->> -endobj -669 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb116-22) ->> -endobj -670 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb116-23) ->> -endobj -671 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb116-24) ->> -endobj -672 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb116-25) ->> -endobj -673 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 567.702842 101.433071 548.952842 ] -/BS << -/W 0 ->> -/Dest (cb117-1) ->> -endobj -674 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 194.455821 101.433071 175.705821 ] -/BS << -/W 0 ->> -/Dest (cb120-1) ->> -endobj -675 0 obj -<< -/Filter /FlateDecode -/Length 4938 ->> -stream -x]Ɏ$IWii @ Zp@@NDMMvfbnǦ -iR1IM+WR,wD?"Sp~9!OrN_g3|$SL1*/2TJ[AAP=9K*3n0%p$A`uQۭ* T0CgVCD QY#负$SHdQH:kZ)sg%-^;$lq6EI` V:bR.dA` ЕDlQAiIsrNeTi3O>Y$֓6ÈB'( l gQ[UFY'Ɣjht[eŘDlAK `lQ1H4/I`b\6N"K 'hd?Vi茖*]j0rElI\` lA -Y ,-XЭSYK\`N qL%q (e ,8ׂ;%. ] (qZk] -XuZI\"-`d%.p]Uw1 8 +III\&)'q)@ cJ\ƣ 5^ x8$.P&.(lJ\:c%.@aAX"qO`I$.]}.O:¸'Bw1QY p`)e$.>`=J`Aע.A1 Sk)aK\(\f@1  0M 2t Ȗ.tZK\ lA4(qA2 ̠$. $\-霢uf 0Q(q V`JQ[@h%.M,sDlI\f %bؤf +؂O€Daq蔒 q`\z3I\zK$xiXo" -#3Yhř[-l=5i3LA5 -Vⶁ"sNwU"!k^I6/{?O?*;e폰i&?,&~8!2]-hZĈcUUk6&0 HWb{QQ0hjxGGtg^&H%bZw= -62KݺD -¡^v5zdF\t..eM2"/(-Ŵznik#\@hr? ,:MӦ!%CH1%^}hq!P!ԥѣɿM.EyC YцO:ȸ߸?|;39b6ߝOdW{xgɺ@'mBm~67,CuU<+QZ7s!KS٩pzƺWD[mup֖QFJ|ӺC}5rl]p*YDcfFo7~-W;ɹT_e%>~W zO+T0XiPJ|{d~>vf -(i۽oTqF؆Mdڢe'勇wvJKY^,EStu@wu2Hh3#r6ͯqe?_y`[JI4WfR닐Vz7~=G2l.q]vtBE2aX<>kh4LEENk+a9)kήDW;Oᇟ,|":}^ZRDz@e0L8*lS@@F u ]> -%[]* s+7˙P%.JX Mr^ ݪԗaL-D[dL7 Gy< ,p:ޥ]1J>]A\U5HCǵϵwE]KmQ\JK3mIwX]邵} hfgeO5\cE˒Zm+ڱ]65OCn$ -%y~=Z(gՇmdT6Sx<Bã=^z1<75vϵmgp_GB^r [V[GFIϻ7e> -Yxt?ᐼc5ޚG:ФW룦W23^Ln$ڿ+DWК^<Zc^,m:H,.5~iy F,z|g\OGZ>qkռ6'oeFJTa~j뽑pdQW6bOGcym7uܵy}v^c3pչBdIvJ -B iZJwǻWP8F}0áp?V(HYcQE~E|v0~|{uo LT#gǐ^$(izK򹑟ՑӾ(:rCS/|;hfQTe<~лFʎq˲rL]ع;ۯ{y<c7nD&C] 3uڼs"ʿy8T:0#y7$%<co03X{ewtt`GCOtϙ+kgpʭ&|V e,q|=l+·n~^{X,g.٧y7h?5.mPwJW|^A+by7J~?#8\z*]zjiGC?K+y8/]/ub׹ŴWiq*7̭LP=0Q(XA={#ς^Wko7wѣW=z!#2;@o&56_\"e66 P#==tݰz^NR@MMOn,o83Qo-7YY^n jL[U֔|*1ոIڳ1;siæ?By.ϲW!MnMLNN:ݺMGA{ E/Hϯb5N:_^P8v0/'zË΍G T,ƥGɬRZ?sT{C:wpq=^.|^b~j Q}10 0ăF_Ns 2iƽz*ӜSu|vr_Q-LօdtPLo/k>l8FCH> -endobj -677 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 548.554475 101.433071 529.804475 ] -/BS << -/W 0 ->> -/Dest (cb121-1) ->> -endobj -678 0 obj -<< -/Filter /FlateDecode -/Length 4772 ->> -stream -x]K$qׯ~Ȑְ``];-_0JfTfVh4z2HA2?(1NjI)VY'wUT] "$_t9&ׯ.]QW-RZ>b1TQ9'B3*n1%N3\nUfVȨ"06(U% -fRv(-%!Zr£=Jtbu:43F`S. ｋt8etŚ8-`p[4Z'1[`RqdKZV1ĭNK'\4Fr:6 ÈB'4l%V[b΄ѪitisE`YlAs =ls$8!H@G#lc!tr80RAGFg=F`Ia p\` lp\`hnLRy fJ Do9.0\@)q\`qb X89.0]cwU 59Yl9.; -w 0Wp9.VQr\`:Jq4Xvsw V{ l48>- X ӆ&4 xW%?fLs\*X]*řqVqQ x9. xTq*OJ'q"npB!M( 貺$d-i `V8. 8ޅ{Oxtp\"auDq0l1`UH t]Ü+eHx.M | @(Xs\)qO:| \; Xlr\Z$"A5A  "I!fpa RL&b㕑f]1^.Hp/U` $ȗH2zvnJ%e EKTp1M& 9z2s'ٲ>?_~{/o+eG!@ȩ-+ ѷ&LE¾d!B&*bYr#uae7&Ñ"O+zP.bJف&-~8ϡAXoo*և|u[1au7F%?@luy1xcfFVNSd \ {0W4Xb2#I)( iWb-V,kr0񝂣˯w?]7oQk׹r}+׺\F$B"4E*j9-eڷd/K9]TW~':Jszo+VG6Z_.K,`V1\/?V)ª68uo TҸ|NPǽ ];45Ke R!);n`m}>hwGc.<6̰w6Xkt6:_{tDȈv&YՎ;vPR!C۵!ʛ]:_(S4*]Gn#ۖ0=.yRIP,k4)_.-l,YVyR?`*cSSJpCRd%n6_c^1ŌoJ Brrohj[Nn>!䞬GF^ZL {kduTi댦b_*=gd')˽Uz>n~QHym8\u}Ď%zx抗e.,w=HiObW ҬiVs;eKrCΌ0Q#+e+n}l1BBMU{xcn!w›< 1dMb!ɦl?zT>fp|K'ܭ0y!m,MV -C*vG'ͷ%jL(y{֞΋g\~8Y͝gczSiTMaP牶Ly[8gGzvF uk+Jh*Fy.oq둝{}N=5dYc7ȺomHŠ -(h_Pm'_<ِGϵ o7 *vY)M/ k*oAE_/m\gg9ݐcwm}$hf{;~rݽU޺4j,ddTLuS[<@|,>W1Lmcmv BC6TlBy:]><㹗_Ρ}Y<(庞G[;6*9Zrx3lHj+xbܳ'8M|e0G]y{>$CNw<ċgu5di_:3\_l)a!/h}; u2ӡj?x}D^/8&wyQ^qX;:p2ӡ`鑝3{;8eq2f L+۰97a}d=? q@Hݧy `]NmPvY7[Z;@w2ӡ`=K֛Nΰs)&v驝}ӆڙCg8 KNy:_'/=zjw\c{\;I+Dhs2! ~8FG{=ϊ[M[-sDs ~xklgêa//=lO ͦpUaԗe\t}Iƛx@ x׸oгzx;'( -o8M7p}r&q?.o|id/(^R;Hʯ/^$Oee&æ|^gJt[A F!](UTnhu3cKUNt`/֘u(E%+$mQ׋.~[ۏG8|,L0$!HsJYgÑ *{~W wVD&Tӫ^ -Ut}\f -Hۄ@;be t[bm=N/mM绰>6U.wVJg`עjjdf0*5)[OvaZEg6kt"HK5#]t4z*TgM)&gdؒ@_1iǵNh}-.ζԮstz 6q/]J'e-04apMJ̓?( Eg^ &^7(u,ʆvh.B^*J&=nKZl%lT#j&& -Ӹrjbנw;]NʼZ]wz\V*efg1A?JXzeRNY\Gkc'2.d7tJ7y.u?{.~\qJB,3=ӂ>4zhaW#FiJ7VjlUiu. UJ &_fwV --ҿ-^i^Tnx-Z2-r#C;SX222?nRS*muWo{nvC|Le6)?;KiKUʈ(n8j&ރC,}AFqX*y8v5;5FEߓǛE:V E%c , uEIy1/Kz_ -z#}K?6F^W'LR -endstream -endobj -679 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 678 0 R -/Resources 4 0 R -/Annots [ 680 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -680 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 570.123057 101.433071 551.373057 ] -/BS << -/W 0 ->> -/Dest (cb124-1) ->> -endobj -681 0 obj -<< -/Filter /FlateDecode -/Length 4788 ->> -stream -x]M丑ȳ,k a.FR*3i`P~AJbW%r zEM++)VEGF@v%Ov_]Σf9D*gbT^Pe)Fム -zBsT0GgVaK*I* 뢶[U&j'`> -*`6J:Fi?8=H:ɢ.BtN!:S'I`JK:[vNI:l.uŤh%]-ɂ.+:آҒ.䜨ЩVg|VI:'lZQN -QϢxGҁ') jIa1щ:؂Ηآb(#h"^88lD&%$0)O.F+р~r!G-UŻ 1հa:b؂X [XZ$.[oA …J Ƶ)8 ,(PXpwJ\`AQ ֵ> ,h׺$.]봒wENQ[` J\V(qb Ыp$.V&wMRN5SƠwGk28q&H\L%F]P=tJ\&Dӟ0VN9H\:D]tDžq /O:,qbx.3I\0 -8D̙)R#3Ct=I6ϗ_`_ n[6 8,GR1w4hpd#0ѿRJ"7ASK`R"Csd7$4TGR_-Uť\M.u?rlϴQ:Tomko7_m_\Fcu|^>>PNx Cg..ϓ/+r%$ݦؖS`{BiwP?o}S3;6]C|%=cp fI]pKim^0֓/JZWX|S8v,4l%ʫ͡ikm.HK>xjsK2< $ jΫOc_k?ST6[}:inCESd0NHDlYЭo-dw-ξ`t䛽EQbxT_!"-Nح0,YPa:5e}}\pnEJrT s/SH>Y]hx}UpizOmq:Gϙ<gssxkL%b߯|_|ГBHs| @`ٽllV!Lt%?7;y2ϓ*o:xS#o\p~)Sf8vy e*G{'_jgD}}D6%D``CdfS<9P= es'< Gh_BVY哂<֭||.6K0_>9n6r,t3m< ں٘bF9lqo{m} =]G -*=wȭvA8Ƿ_{ kK\睗4jw%kYs]o!0"8{=l^~9gঊy3c|'}ُkvݿ|:@눠% [ҍ*=|g룑p7Q;h뱧m<xuϏl;D/k ffCs@dIϞjA!ZJ?zDF}2ӡ8Pؐ2cPq~G|v2q|6>2ּz4ámuHwh1<#(Z"RG,e@gǷnQ(7#;{g?s՝vgp'}ӆڑC8 wǝt~?~齧vW5ZT2V?'<į=Hl~^ϳa'~behE;'<R:j7]8NCFrL2>^Hױңe/lvhq9(z3D̎Ejx|2ۃ^z8\g6 m$G:k]z2ð>H%J3rqXOʻ8+<+AWx^Q6R5^knW=/Sڰ/]*I:DE1_鼼ӵtq,R-'+:<,/?ᢳ|r*dE]To'DpZYN3'SSZ?k?^$=Ck6:mͩȖ!rSդ1&\f -Zۄ@{ƻbmPظj4B6ӹ4D֝GQ&J*͍b~t1S*cnH;qOԯ}I3KVә<"ͷ]r9F50[Wb>_H'+ &4~6{MB}ĦAh<-ܾ|ik:Z \}J"qEI3,#.xdnL$w+,.XA\fyUVZ 44~~_LuQ{qikIR[.9QoP+˲g[ӇF-cIS϶$RWeJD2UeXm -K$z)K=y4'z+aʭ3^l > -endobj -683 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 573.873057 101.433071 555.123057 ] -/BS << -/W 0 ->> -/Dest (cb127-1) ->> -endobj -684 0 obj -<< -/Filter /FlateDecode -/Length 4747 ->> -stream -x][,7~_1H1_$$q=)+osLڝ*_Ueۣ)VSI -]A8|t`௯n䯗uu"%! J`Ies"qX  FTa*wNE8,;oBI.KB9,p]H#) B"w1' AG @9,ъ' B>AY,`9,@`-IÂ!њÂ! B }wa RH&bÂĔ^V[?o뵘Ak {6'ڴ j -c\ #HcĿ~w)Uv;Nah/ݟ^.Dg -=]˧OYiԆHK*$}ϥƭNZ{Z>sU5[?+wʎ6rZjӬXw_\~n@yޓH#FB>w.j)ڤj}.JSl=Fn]n9rLYe*@Ox!յaTTB)~/rSϰnmXtH%-F[tھ~CN[nbr9P3ERV\k}/YYGu-`ѤAJj}BMci-lZHz鉌lEŔ^ګud=>{KpJkU5?TSKƞ´3ʻK(҇v>e[.snGRYez]3} r+ZO-[y~h;S.66}~=Qqnhs@2s݁Y{~N 7a͞]:ϨMZ*2f1|ď mr9,-.F'i NMVDL'd an塆ni1n hhC-j0q@7)ѽmc[lVnEr;IlԐ-Y͎)dX[jrϳїIV7:_a8幩9@ o - SL9wѯ]*Fzi v7dwM=oBt0Gv07jG~zCP6_m ^馸}5Zw=n> Fy c͟ LVzĮp>GVF8MGڇG}yȊQ] EϥC>u5>-u䇱jRybY|4xY{ٹG4+~VФ>+RMeEN|-U9]ґt\rxpS E%+H||M'^,mː4 \VU̇J{ Y.r]m w5qfeMd)_K 9ڒRBȣ07QF1m/gIVFD%ʡNֶʣʦ:߉MQuj0M`#՚RZTծfR6;1 CL֢-,Ʌ#ٖ.t ¦+fRŞ5UwQ@_0iLo4[8/ζɯԮctFm(t*̵\kVGpJȓ/m.Ei^ F^+i:ӀԥBh>;KEɤ'mVAe=*T5Y5kd#QV!P]'ʯ+rӵd̫]+}ב؟ڈ>+9lv&ZI'ӑ8}Ze P\{kC'z;7>_aNLo=F]ђ8eC ݰuEG2^xLQ Dmd{ZWZxm{vفT AUDu8us]̠w@|M[SGgDСU*܌m<ӇP$(izȈP.JLrȱzߎ0Tp3tk:av,r+$x3lXiZv/"ڠQ_GjkQTo9&P;oP+ }ϴ wZ5l%+ .@J U&_UGVKi7Z)эVTnZdZFwulddh~ݨ4ۮ뮣uhʞmR w<*a -FZ2z  a> -endobj -686 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 558.873057 101.433071 540.123057 ] -/BS << -/W 0 ->> -/Dest (cb130-1) ->> -endobj -687 0 obj -<< -/Filter /FlateDecode -/Length 4783 ->> -stream -x]K$qׯM| Hװ` ;-A5_0JfTVVhh=]Gd Wo4St}E-))6YwՊt]d KH}rL~_]gG_͒7]UdCPNP%ʹ%㼠z-$` dh -0Rt -f1QPEa)hW%a&I3trAPi;QJEdnptF/>&D]N#]| KEIG%%-N)I[ Q\; Dl@ ^MQ``5F`` B ,I#p[)J\&[b" 8*Yb]@ b-qRKDp$q̀N!t 0- 2t Ȗ.tZK\ lA4(qA4L$.$\-H<3J\/*J\n&RЄhl; 0dQ[# b4<݌[2< $[I\_8L4R$14$q%7*71mAD!DuAS-8 M$ y(q 7ыKA\.ft]D^\`V+ degW al U ȗH2zq*Z -xv>KTp3cL9z2{#ٺ>?]~*!&W&o۷2s>MAeɍMa6ܘy^  T#[^n-ud?:`˕V:t}nSSro[ŭ3N6oWlr^m}g֮ۜ#v,96Wn.3};bAyinVɪO҆^vybce$꽏mz\T?K]Mvs7t/èC0 ڰrWޘ#%6O:yMv)W \FFLC܅繝.`}m&gSsְ%s=.P{bmƌI^nfRXS{C&?ESp7ձ 0Mo]p8O&[0թam:SN܁V}^"G[yܑ̆F\TZ9D y,/̸Oۀb[>pg{OfVAě+!a$Sƛ8ozW)8@LZӬ:EN@fB /@oDKKJ.=Ux=~p1`cK<uwoh]9TO믨 [&o)f[6[9[oS\'A[78Ս͉unoVZx[i2*pmϦȭvA u=[]7iB9r:!45nCp0[V<B>ó-[J*%YmydcAf4f~{|2!r=;? rz$$ۚ;ٹGcHܖn yώ'<cݾ][INFn^M-}yd= $̏~Ǒ76n5|wy:Ǩ?_,hfͱW'<ÝXv|6vFr+|Zg 'eFJ7s-[>Fh = ymw97D棣^q%wѽyQDZ/02ߙ{a -<φtg鑝3[;85q3{fu`?6;_n}t=? qH{O'<*K=z/ְMC>@g]ǟ-k_ o1w2!|ҏ=%~%Od~Ny6$ku'@칺GÇz NK3g[fcZ|QEj ]z:Ngm.>nWl<ΑR{U%ecZ_ܛ-1Q^̯WU{Jg+F:سy4s]3t:/U>.WO OCyyQYҵtvș*'+><:^?-}>Yeq4/| b1 G"WnXҜҺzp`~4 w5F&bA^|jE'Ŗ+LHc^`xWn/TCu]lڣ$:߅uzhք9Tkg(kQջF5JMj I^7Mh̦ZO\ZT ׋ZK*zҡncs {UCQ~܊܇*1;Q]~qAH:W(W7 -PnGҥ|j ]L@ -פ<)>׳_Jo6I7!BO;K0;KG%gm6eCkq͇6{[5l4VFѮW6a .4ŵ6v/{'F˟/y3>[gQ|߿\ou7iܺ#CE<)omXǞU4qܘgWkJT7(t݇4mϸ|i{l>Zvp!:+Nڇth q1ˡ-ۘɀ+igil -u CcUbH؎cJw/nb=ڛ}ci#79[R-=aiӜڭ /y]*wtYz#HPZ>1Ir% -endstream -endobj -688 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 687 0 R -/Resources 4 0 R -/Annots [ 689 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -689 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 555.123057 101.433071 536.373057 ] -/BS << -/W 0 ->> -/Dest (cb133-1) ->> -endobj -690 0 obj -<< -/Filter /FlateDecode -/Length 4601 ->> -stream -x\K$ ^C1HF8C~>JK~ژ LwzP$Rʞ ~?.9駓YR0%v R8[Ci ?2%RVdzo5^,%RyEbR 3ha\0Pq~LYCB)y \ Œ4Ƃ@@QCo! a< iXdA ,hK ȂLQ ْ )DǠUݒZelҰ %ZXK-^钆9;^nf r,8 LYiXPL\8Mְ01ta%77SmכIÂB% EQyISQ-0 MƋҰͬa 7ѫ[כI.dx]dQ\`V[oHtfgVw 7 [؋h=5i1Q5@Xu'E 13'd d}1 ?}{ߧONYHjiB~i -}[ G4e(G!!(n[n,"_vrCl*U/k:aIՁ9$~q"'ܿX]֡)P&|tY y57ۤ8NĠ -{o,ؠ$bIb |D #8"2+7'&źg/, 7?>W_y:}O->)!l׏۵ۮ:IcqҰL1֬N_F4]Ѿ\ɸ/;icNw Lkty[Oqq yݘfww6qXamDW}:ٰ¾mƺ%*EH=f0n7@O(YwD]Vمrݗ_Oz2k^rvk-<o>з>Q>=\_}wQйt^u6ݥ,Um]Xkl=1*),Cd 5m - ґSԫ -2nËr\b6.iXDϛ|N0{crZSXZIXE1. W:A !W^aGӼvOn~~f;ocWY\+4縮uWug}л' 8ͯ(7}>B5~ٖ(ɛYOv®rBulg%9>8:I0LJStO&ɘ?Gu>1 -e{~Vj1^djttb~:EL|cPYۏWw^B>QeTμmEX[p>N4u௺B[׭/<qӭڔUynq)6j׀>orX;/hM]S 77,u,&YhnwsSs#jE]WV .d$:l[,u?q0J;n&W{7CK[**;ut_Y.4E,y1ʏ1awɖnr^#׼ 7*߆Ԉ9WmML-(XqFl#[ P*8L(!';ux Sɹ~{:/:e5#hF)ց]qoN}}k-9es<[ -q:ۆ]]-i]v#xCXiKmu69oxq:iuc[;nӽ*L+)j6=m뗀ny}u^xxū׀Mm@]΂UE1xwF6O<}e&<ֱsvqT~SkiיNBҩn'xR4/X9rSH'ZJTUKe] -QLH1Go_d>mmw >8ϧa` $ыv;9/z05$WSX.oWWǎ:iRelJgl6Jy^klG*Tx RKjS;T_/_;4b䌩1R ]H> -endobj -692 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 367.323057 101.433071 348.573057 ] -/BS << -/W 0 ->> -/Dest (cb136-1) ->> -endobj -693 0 obj -<< -/Filter /FlateDecode -/Length 3527 ->> -stream -x\K$ s˒H b"99v<6QUzT51vFoH=X"TW;Zp/39xxt&ǦQYN&s8~%J)_oלÿcћRwwb2)d*`YG -+QaEgph,{>g%%12 NYbXcA WBRXBUy2Wx.M;sE%\.8WL1dǐ%4^,1[YrxP$ ω4^,S^, iB&̬ -x6|6s&)ñ$ :Ӏ,d 5$ Y ְH0p\>Xaw=a  w!AO V{ Fd YaAqg Rof -Yԛ(-L,)ʃ,H$ԛ@'!/aAQͬa ԛ#,fR 4pi԰ ԛlxCB~3TY=1ހتX`/UR ,Wj$bQ=5@XY&,OU9$̜" ܂ct ݖ?|{߇_ՓrHjoF~7Ⱦ. KU4Hβl*C, \D,ZṣjkV7[N}ESR?I[Y`S%7U7zv[ -M ƪnXk;Bw:ף~\xv|/`op{0kë Y5;lZjCt5j_:똲ޫ>LV(x~<[%o;ڧ79,zHڽ,ڽJRظS񼆏/ki8{:gM3_St~gBVsGd~VXZk,^eۘ N_ez:Af4S_9rRpz==>4W7-ѺYF1#NSɨT qRIΫxoX9eS,1gYMv9V1[ZFe\q];"U,QfA [\O Uڢ -n>ȆWʔf|փ\ y 0B7.:Γ$ՐT?kO9t ]W{5~:zgwۈcd#өnl]SFև>^s|Vn:SUǃ+ldgnl%grgX!3;B\>ֱN@dʾ'cׯON}EІɽpl['w- +D,W]Z6b%&3cB dʼnΉvZn=7yܷ.b}:7iR5eiO}QLFPSC]O -tP_65C?iM9^~SHo-tM+e: -JM #-9mƟO; LiNvˠJ|k6ܱ)/P:U~qMJf'o7iǎ:4NR6;V/{P-4:xlɮ[]' X9m r!9CwU{[,CwcΗƝBN6߈xOmAGDyK%7oT9_'"á9O|䉰9r;y-Kغ!ϑLwyFn3=O?.YCOxczsgb{8}7]hڙpxbOd>W7#`/MjeHn^oR1_yh4%ZutpOј'EsZ 6bA΋yVZScJ#I#S7Z R`EFE7g}96jN}„ORmmh4;'95Fjl5ak0/ʍYF3&S\mW]J=V&Y+"^ϖ'@a64Ύ= --Σ;GOjyv2xGfjǰpMYN!^UOF\ PKcnp -endstream -endobj -694 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 693 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -695 0 obj -<< -/Filter /FlateDecode -/Length 4517 ->> -stream -x][d9 ~_QHrqn$,avz|9I|Nn=:v.|S;Z|O!gJ9`M~s<:KDWSOL}Nǧ=O?mw]<;fQ0lª`YV&gJ`j,3y:geAD1 -]8gU#1\Ya9 9VAKs$(=iʃ,| |,6'  㒆>gCՓCTC9 |RN`!K!AprUd 4,!@OAÂ%XpK: K.Ĵ n(4,\Rհ sSÂrnkXJҰ w9awC@MY`Mp%hX@lְXF^̪& `+Ɨb5, /4, p*/aw}4 z ' `(ch z8Y߃烆hx%D஫pʚZWjҰ w]j\ƕu -Rհ wᨂ , <װ w]x]հ w7D `!а8 UyZ X [$*/Ӱ`l,P pjX6aAZBأ K(^5a*kHa5p\5,H]v_4,Qװ 25aA<|*/y` 刅"{p챐‚|[xo l=r")4Px5.fkZHG_O7׬9ug#x.8v*hot{I:/.+E˟'>_U[oJwܟ  /+洷ZY:F.Fokk%CT'|@'w?~?mxϬDZԺ̟d-=0*;}59 CWZzѭi}eanCE7W~iiKzݸ<쪁.oHS)[թK,f^IH+zlsjOkoi&ap ~Xg iܞ#$>tNFpj&Gs,m&x6<ϒ*WKKmn-kZ52ɲPo'c/kĤaXi,O U86Fu˰'d{w bC.[e?/C$͹ǘW5}W[#,G1ֲչKȥւP[D)3 vlm_k~.X, 9>F&yo\]|EG?&Z,뢚Bo}X毿旿p<qSw^ =ĖIaMV>"Ñk&2 __o#m Yi1~Uv'RRUgej7W[4njȷS!n*ЮVZ w?dm=vj$8Mқ糓P]8oyr -U^XYdTL"مctЄKAyg+uVУvȸ.>8];||K`}}w7#e`7Z[\ZNf}òEV . Lm,/"X1>_;6˃ZY^G+ M>{&~eeSǰU|f>EFMoD /{o JvgΫP_(9q,y`nLi's8ǽi,!݊,zlg'(2`"tXL{;n_JXJ=wZ޷'[ᕻ𗤧r>{~g_s=R"7#-rVo ‰Y}$s>@g_v=GNEϿ\k<0Ѿ8rg`݇`Ɛ#|eVqEnEϸ=&P 7\:[e5(]E*w4wӃoە:YB4 3ɿ_A<[\mr>-l6<_zLd8ȷisMxf(wk -! -# I Ί7.XAD+dO] եIK91b:Ot'ʷJv {1!4I!Έ_4a2_͵K7$j/NZ3G2֮)4PIڙ/kĆvKtp̵-nt@*Kgqb$1vi/KWfFqPyGäv4;9[%IzCYVL=l Aq~?2:w[7dr'ılѓIve^5v{/8u(~wAh&^!vZ鰗 (_֥ƒ钏I vokOqe^n GM.+%%`ә*yw+ʞ0B_Exf_ѫU1([CpOϾx̜*_Rl/1>Nl -endstream -endobj -696 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 695 0 R -/Resources 4 0 R -/Annots [ 697 0 R 698 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -697 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 563.554475 101.433071 544.804475 ] -/BS << -/W 0 ->> -/Dest (cb139-1) ->> -endobj -698 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 100.307453 101.433071 81.557453 ] -/BS << -/W 0 ->> -/Dest (cb142-1) ->> -endobj -699 0 obj -<< -/Filter /FlateDecode -/Length 3427 ->> -stream -x՜K )l@*8HĈ99H#`@!_?vw=fؕll4i*֏U"Rsλ=-%.^T)N.⏻q'Wk|T%g U6T1)&C-j`FBr0Cj -fQ1Tf -3(T0#Ԙ U#x&CKd(T*US ,KYB R,N`K>X[bll*-]-ѩxW1u',]ek1u:_r9ב.foBpɦ+ -#ؒ|Dd^K1V+fEBLEJd!+),PN**H(@:ə- PNR(X `[$``:U,0X [HboX,0x+>$ LoA\.I,0 W ebXbY,``$ o@]f4ultt -[,p 2"U?L +J ܥbL]vXl@]+r=Y,p8 @HZ,@bsbAwCE34hBbAwCBƈBJbAwbAwbwd -zE-\@`5uZłKdQHb`GT 3K֛X9F1Pl=ݷ|?grR^ RZXT1wsB"qY¾gTQr&@q;rS͑0qaFDմfh|Y6] ,2-Fo?ovx }֌I:?hzt]5=S ߿]ƌfdIi㱃-xb/mq HbpB+wlܥuE s`BNq?~?mL1B>|**i&a4hȾ]z;~l ^[}?ٖVc׋c`=D{o}U^ ?qaF""u21n^2l*5jD"}5 - mѝ )p;B*v/1,lп~儩O|Q9(|8y[ͮƶUtm}K~88° -VF3%Us_9lW<֌Ykr @@?볐.tF;'4N#J{UWHyf0gF\e9yqޛrO͕umyO{U9V*m}yܶrr'9ip_/^(wV2XA6ތyqZΤԓ;cOf~)n{:/Ff(U7B˶uO&ս_-֡UuvOdԟ5}iao7ml,utWa^/΋>KO8^⩝dcoxX :/ΛW_o>3'{gm_6w*?Qyq^u='zz}W̧F=βr<`newyi%s?udfX/G nGî:}Jf^qbln{I}˞05G:\cچ5mu%'ZP+lj86DauZanUN}Ҏշmz}"w~Clp6wiy#,y ߤ8\H,M[X:/\%ھ8YJ}fVtL]tu9E\] NrC,N -%N?M%9CIb[5}@|+kdž5S8{6~Q8ޮR7%f3AˎGś~sbfOХ!Coe)OyMxء[>>R}<5F|dTJ >O3|kZ0]?͚> -Ks$j+g;Z3{26Ô\e6io>MkyIg͵/ЙW?b6J -B⇿ )2m4L+*b*y7AKcnjtkiNF He -9w+oW}ĎӐM\y -cq^Ŋ6>7#ʏGagK:Kar8s,v{{7a lr*V/!&ߣl!}\mv:۱Ȭ{[q7>?g]a_ydwZPgxdrXՄ}LB C(78N4ZFu?JNе01]O#'/Kn7nXlVb\SҢ#C+4U(.Luȹ>jSt1zC'#M7rS<_ K;GF?{y}o&TޥߘJ;l)/^lwPo=Kcrt1$-V ΝJuEdzٔjmX;.(S HyV yVYYmE-qOyܝ%{.Y Ykwd}q-ېaHYg9k|*^H()ij /"ݥ,e:*yrg''$d m#bjv[z\|~ zrˬ[E:k[v%.'udyTC -endstream -endobj -700 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 699 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -701 0 obj -<< -/Filter /FlateDecode -/Length 4782 ->> -stream -x]K$I ׯ3&p$$,avz}>GfD83]J;i?_YN9xxt0S -jEe )4[bǏLiJ%/_u{tS)pfRNU2+\ -+ C,EcAў 4 S~*%K b²rXgʃ ;gb.MNy?D6XWc K(jY%2IE7*KA;Ee*h+~ -%)y΄)dƳv -MQ,ф Ki<Y?8|YV퍷/@<ȂEbR 41.iR8@e?QebIxcsVo K!*BxYP@!#aE%SxKF <b <Hx@.LhXةaݓCtx5,]OhX@]QSA@5, ஷ&iX@]Ӱ:l4, ˆ4, KXT^^!h+7p4, #5,LF]@Hհ=xkX&DÂܵ˟@5,]1}*L6AB˓hXX 'NÂܵ+ZW!hXs, MtU^LYÂ,9 -O&IT^`HVdjXXދkD!=*4,@\Viq@ -53ƤaAaALLpY8! -vLSI)jX!ʋɀY*P" XOŗaAr;aAr!b}dADɦ\4,H!"V5^tSNkIÂhRl5,@.5e8% x4,HU4,R4e\YȂ [DYaAvѠedhX$Tp5,'5, R<аvаM9*@8 Yq69LYiXPL8Lְ01o:Ұ~fְx|)G7 K@ -0 &IE -iXPb|3kX0&"zuK sn(@&Ed5,MDZno!!>ә3ά@oڪn`/V/HDfkeLkmE)TʲߜޜNS쾐C9ޛI)7,n2SM%|M˙(ﭻ@?yv[7Xzw/.kPU -_W,Ee]+}A;T|wc`[h" ,>Wx?`= cl=wat E4ה7gnŹ*P qݠK(n4U1Zg8wka\j\ -'t.Is†[ji.3>&񎾔oU2J.WiQq"CSxoJдnzmlioU'ߡUjHyh/ H\4XFd0;$FD=._5vZFJn,0@6CYu۷=ye\󘅍rxgaXV>Ţ!`vr)n7ˋNZ_8nio?kQai&S'c;i2?9Z#=MJӛ|xTY?,v+,o۷VQjmuz ͮ,mBe -Hni;]HmkY>B;Vg.N6ndum _~4J i, y." Ϋ%xё㯬 B mC!KY5z|YDFljKA4E0OKLK\ש]6=. &N&eʄ-hbT&59zQ\x\ж4tsN&πlu@"XsROμKfR{^7KmV7vӎjHKg$6n6m~`Yo%6F0e@?d3R:48+_wx'Y4fSȡEΣDSj}2o*|tg~|]-$xdcfZ|K8hכ[tQU-,RqW:bUCl򗬪iv]Hf殡ѥٛƵE0,aFjqM[Yו1,l-WY_g,8t# Yp|.>5]j9mka KtN|mn1r]3֙y[r_ʵ_f.-fݐfT[ou+N.1yn8ԣ3֗Fd~cGt9f{ÌmNbY^?K",1WĊ7y8k+gŧ xfwirjԭ5yJ7Ɵ8]=53)bwqaX(2%~-57y8k==PqbV~!qs{XѬ6_cY9Ky-m}ƒGI!B}-ﾱYXTl-iƉs[&Ff+fcmsjyTO9-B7=4[Ɠbi7[g@&vݝ)XJ,Jk?$ݔlh=7)z],Nb\<^Uw✈V+{+߻b>oay,#$n,_'OuYmu"ĎwZespY۞2mW3{Jf\zs.EZwd |'uOuV.ێv:+wZ{mhSяKʲ~zqmq>HG۟iyN\ -ȏx\7E!u~#'$ 磃ŔTCD $`RqX!f{2Lv!'䗫E:q4HhpTJbn5y,?.b]Ίoe]yx:[T~}kiיNBҩB}?cGʴ b317C^r -tP->Sʣji S+^-_#|qM;\,툧R6ڑ#[ -Ivr6^OΟ\gS?X&MWN^+IcG4`)B]6nR_ t؊*T&HgLo:vXmNfkX) 9tS~Yj0h ǎ/[~v+lOua-M?NٙڍqP/ܼا}N?us>8[9ztQ=e?t}{м;ul]Jo7@F dGЬ Q `o%mGP۹uu ̈́ F=ܹ |k~t -r8̃ǒ|M⊋%\r".d!JL6HIW=Or*<%.D~h,FE{y!&+;-+y_^=ȱyS;wꋤ1N2/yz[^ApZBڨQm)dhNB4hdK:j)bP!5t%9+qWm+^|44FgFKfeNQ7ھoZVۣ ALͨv%_AdZSwFlBM6yMB2Dak׹wr'LDޛd/` T{_^uH)@0{l/E{u_&N̯nJcv'o& -endstream -endobj -702 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 701 0 R -/Resources 4 0 R -/Annots [ 703 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -703 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 512.554475 101.433071 493.804475 ] -/BS << -/W 0 ->> -/Dest (cb145-1) ->> -endobj -704 0 obj -<< -/Filter /FlateDecode -/Length 4699 ->> -stream -x]K3|_@C1HA;8C~>ŇR=:촪HD~XUZ,!zGN?VTbq0g% C/|ڻ um_8sYGie?}TdK˨"TRFe^[Ǩ9̰4UfP S :03 ye֪3Wĩ`3*%aR:"ft -NwN+Bԑyל<)8]98tXE$9l!uZZa1)%,iXfyFa6:bԜOXC`fNH8-Z{bu1vEzQfHq^PđFPQ =F*HbqL`l!\V[L$ -(q1Em hnIFqߒT…5 (E 8׀;9.0 ]Lwq4k(8 xאxdu( -%=4`Tp8.VAr\@]$q\@]:/0 ]m渀@z]P=tp\Ƅ[q愈叙`+BtX ->Vqfޢr.r\`X  VTq*Ӂw ޅ`9.q7$ꢐ1 ,x9.*,d:/$qXH8.qJk + n-&h @ii8Bj0Jt])}wӲqI0P @"z8.pQB9cqXP-8"8.9.e -7SL&B$[x Y]Ny 'Xq\XJLz @"K q\#lTK9SN6tS゠a A 2+4bIt5#qA 'q "M0%- 0>)ض A0ct -7!-5f7=Qx|DDr9.C'%Qě8.Lf x!3oq)D-. --p"3oI7N\7p3o£gS!śMwm3q:.)7X|c74X"8jPD _)iQNl%Z^"&m~8_}0zr/1G$/ULU z-("/T' -Xȧ^Vwo*5riC7t+a;뵮穌:wxIcDQag#Ay2erRR71}; Nr|ɟs{4#ߔ+3gҰvu:6sMpsnܦ]w[0NY J82Q"7;8s4 #ҹ~=^-jR=ι8(DS9r@W:C/]aph7 -7!X9e?6~h#!uzY]{1#}n~-G ilfb&-ߵ6m%S\G"k8nvp[6ָV6VpK{鹦ћCzڟ n]Z{S(D:ۄ/@(ģIW?|X8s;hs44*8:N*Z@"uF+/KtΔz{r;ms&o dR:(m6VpHq~ :ekG76a;rum!cیhߴ]ُcyfisͱ>NuwBWVf [@c=s84^wo,U˯bZfO~v}nqi|hB9zNhItc+`5+ #Ɍ6n}Vlk6z3ߖ0jf ]چ 9w|GF ǧR$󾳽F]Ỷ?d{}:C㎟1U_i()rYu&@w;1-f{R <-SI xLчUgJts_}ЃZ婹X0m:Cnu.mv(p=b>9fڶGrMit#  9zw6Jѽ}.W?UY:C1 ~xfht4Xh(;53-o2n_f*>ߺ =S]_M ~wu5^&%XF4<~#iCA:JhwnAZoۇRGF]/#_.#)Ǎ=K7J|tqcu>#T8gqr'cb~Vq)͕[Gk|ѝub떼_gt|`hQ6j۹N{;co_np?#{{Yvn*}2"w;kO#qYYsyzk/S&;SϏ^7=Ο}ΟvG: ?Җ+x-ŗo3ps4|/1~x1Ύ8?KUgg۞gLO/Xl`!wPqȦ>ٿ;9vv y}3gNإ7XpH^jacz/j$/=Yyuq59'ɪ 7Wګٸ/Uh ,Lj?n[0a⻣=d7-Is8=P$ofI:C'xL$3y6g;{uౝ}M|ƣ Gol qcPm/&s4ǾIMT= 4ޑws84WO}5[8ܛNe};s8^cOn/-j茶ޑks8d7J,P̠{b$7_ke/tI}d*0==9t.uW":4t(yCT]~S;!q>_ZS};gj6`5ǓգI酮gG"s!MM5XJoƕeyEI6s"(.o8|PůSbDBp(K[r"{z -9qcGmդ6WKo! *3Btj-NW/MAS6CXlmV+#] es*֔Qa\ۮS7yM|iM/}eܻZiEjs2 TƉ=27M̢oF-" HT\=rsk/BsWS*M(Ȧ>>ں#KK#Z7z%|>Y*3_O3m -i3Zi- +^4m}|̲*l&>(*J1G$inZ+C\(l]ٶTLDt鱅Fc6/T!Xq?+[FtUl _j-S`'s-V+ڊ}q^JW-6ia^IX˲Փ5jH+N<[ ;Mv>[qOߟeN#>8;V[K2_':1벎kYBn]ە,; LF*V e׺ke%\RUE -mF t2M+#rh4&.[rp%4T.Вn*m clafd{~j¤s5MQ]fۦl\` jO0F=dg@j/VZ.,I R3aYs9[{egSFu-hqbZm.`ۓR-NB,+-ln8OQ߷=mQ)hQqݼoȶpd-Y|\[H4Y>7-ϝWssT q3];:]+̈ -5XIy9&w'8rjOI\zd!ɹLAH ^ |(KP9 at *>6N!W{TѴ"}2p -endstream -endobj -705 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 704 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -706 0 obj -<< -/Filter /FlateDecode -/Length 5044 ->> -stream -x]M丑ȳs0=5CWER wR ~W4Stt"#~jEar:? v%v_].fJ1N! J)msSyA[LIA V$ c PRv+JPMj -zh("A^=Le2$vӒ,M{%Ad8M$t!$zDt11XIA$A EtQ^iIR$e 2Cʌr*IM+00H>2]rIAgd~$x0[MVY-t1&(.|.*x0K&J$0N)J,`b(+рIn"ViȌ*KL`5t!\Q]l" . qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ]L qZk)z ,xגVxZe8Y޵Z id$.NXLJH „9h%. qrwSF2^e(B@+q*  xW'?aN&wu4-zy' xJ\(q8~E58𮶰Ԓ MR8.'q0i8MZ,M*(q“`Q&IK\2P Sv%.CIG7 I\yכQd֛X 6YכADEeNS-8 M$$ yכQXo£C17.fd]x^\` VZ+ da+(F ! -b@|I @M,0j% m8a>lf &okdcןa|W%RV4_av5nՠٻ2fCjifj퇕P5+X  b4 )Xl%.sW ]-;Ie>^׼u.]Y;?v{mWcʞ-J6SR2)|'Hg**G&-(hkE̿t.ZqvԇOa~ÿ?O?RY)N3߸_.D߰k=~ke.{ϧzr~sB/,Jޢ&e9o-nݎ-ow.ܷɺ6jݺV~ZއsE)u<|yü[d?q;mjz꫟3m5뽹H۴oU=5Loee(睨 -LIEC,,l`|dEF #jP/'Ê8#j`Y[Au1f32O>:FI9re%1=Wﳵ{HiF>F2O;N?#sNo6@lx^f ,zz=͏=W{nFkX4p8,s漵ᨗ3+h3;ut7p /l2t3n[2J ;ϢdgC9UwĽ0Tn0 fre7(z}A*QMFS$se~Z_usY# -y[x?a]ʹ x82Ocߵ%e ~cAji+Fo`Dyef>hCMm#Bկ{]ߠcAM uYgmE{Bq}M"'<בƈ*j<(ƟR7d|QAf\tNf2pexzldgC=ql=l{\X3nkC>Ch66idL?=Y0}';lKugTF3qs%?罍uz%pW|dFFte%Z~2~,t瑧ZiRbms`,Alkwmϻlm|dC坘-﹗ejKKbttcy"yN^hfe@C\d6ąW[Ykw3CdDՓe Qt{u0۞Uƨq O5"Kɺ4=im%NV`<&Pysl=*uO\!{ZOu\ FZ>)sG_yj7'Xڵظ)s?>[>Ha[OڷӁ==T28TP^s<~OvK[eZз]2|u^2?\k}^NڱV4ӹ{un@/O&j_Le5{XD6o -V9o\a9 t 8>ϗq4cz9|O嵞|p8uo9Y桗>aqM_+2@^ ejTʇ Vz[TB -h`EjtJS,gxx/sSr3Qb'd{w?`ql ͇Iwt7m]*o)?Лh -6~ޤh0"c-a6FQ0xƋNa 徬!{NֈSR>OdharƝ V,$u儅}SAsosuK,qFz($)n.æmQvCkjSۖ]⌊Nͨ6[B0ͨ4e&WBM4bCG)fǾ {n6,t)t*N˦UU+}ۑE_Ţ!^:܌3 ~R1J̿!=DxгIcwQ|94#e;V#e6k e]]-T/:7q9.8g;^n;qYW=Q/E6^ ~n7`~ve!1IRp\H@蔈țVu8Ktb)&m  mSΙf (j j)-p+Ɵ/91"vH|hTt6]:Z_wJZqCCeXŒ2?]t)%.㫒\Lvߎ@B2Qj i7lҘӺI-vKLwX>Td˹sB"JzMw&$o]|S%op^!^n%mbdCUO$n]{bSwf_bUiN%.h֎obj>׾VU{רfR qn!;U& fQ˧ωZT Io͵ --WESJㅴ{$asDq`hc"Í$.Loܮsrz<Ѳz[rT/=5O5-µ<僦|>rْם}cz@SyYwfyaq%Ϥr[.c!U2I5X'놺)OJh'UrӵTkkwɾqOmu>ebhLЏlTv1)No%N夗cdŽ]r)fXg C{=,xF50[Wܒo'76mX!F=YǞU44;n kU'S7M]CltgAm|t=_zsi|t -vpv|eU*g&R2 .xd J HH?񡰹-v܈|iU״r, \`/xŤyi}QS7n,6“SmfslyNC.mNNݵ(KؒFTMk5_n)w^ -ͧ=Nt|T&oZ-9N͗B[*mۦu^mPWwTbn!{de(Ȉx}j[1QE!&Pdw9l#$5v[pLd -:龀UUS.xK!4iNm"CJ eK]6;1ESPZ~?G^V" -endstream -endobj -707 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 706 0 R -/Resources 4 0 R -/Annots [ 708 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -708 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 307.623057 101.433071 288.873057 ] -/BS << -/W 0 ->> -/Dest (cb148-1) ->> -endobj -709 0 obj -<< -/Filter /FlateDecode -/Length 4677 ->> -stream -x]K|_@C1HA3m`6C~>JCT]hm`vZU$U"?~*IMu\@J駓JJ$yaUt'G;_w=uYVIEFུ*B%aT -u)KS IRa`9  -0ÐWf0C{E -fh=Rv(-%!hFpt.DYNyΓEᜳlQ*NgaUD2s:[3thNdt]tR6#9RaFagt8i#-H l!p:5>f44Yآ'V[0h[w`KhEM ` - yo8 -rs<`N+-FeuDh؂[4 ؖ dT-I8.0 \)9.0`\q\`@Rs tNs\`@w )qwAMV[` ¨`8. Qs\@]L#qFU`E$AKsp\@]mq Vj I; 7X- X C hLh%XX9 *Dq婢cuQ(g-zY("p\`q8^`EX2X9xW(9.] A(8`}J. -CwAKB0 @Rqby8p\:b~ t̜*Sp:TaNޕG x7-8:p\`q $%tpX8x e:B8.c-aњa \ }l\` L s:[ds\O:8. (I B#DWs:) r"` S:㓂mqsXl18.Ap3p\lRs\lxs\%lqAN$78tRr\U@o 716MqA$bᢰ:)2xlё8.Υx3p\7&I66324F˕zA3+WfҴ}^/w }4ڿзҼׇ_˥׻9[l'ˣKR1>© yy -9vb*}TCe),}u{kp!г xDSaR&l rg!Roo/GQ!oqDíiϾg;ۣu~b~`#nU6ghPb_15ts Ѵ[WpoD/G]}:ZHK.lew9~YuԵ+g?s4~_ALzueC2צh_{ر9B V*}{nڢf{Ee&:+Ɇ-JuЖɗa -v9ʮ|FF7h~™.H24MUuk] 2+#Ps/+#g#8vjΞՐq)ӭv˪&Į}+~V˶qBj|LIB+ -D[WpK{a;nћzڟcqp]{S4DӯYm"'#ZASA(Cm=7t7\ćqٓ|D0=he™CscOnjGAp'y7+oϱѐf=k%ٵtVas8dnlw?ioZn -L?z96g=ՉW|nNWU\-[;OyFs84~"/T-)_~믇yŬlO]7ƥWU.m|hB-s8no]qtݮ~죆vE5a}$g:GCfw&]n)]zl&mK$Uc.VuE(,OV(8]יiTɜjnKU -wb_F\⊽Yx6 !,]=Y# γ:ɸr4,sX=m.u|ָkYBnە,vӮYXM#~Pڌk5{. -ma#Zg<:6uM8Ƥ-ڲU8h/L]M8JE-"Fq؜0Vff&@')]v(L:WsиTem:ˆh6A0qfcqLvy$i"}m’/5á5ǜAJ[{89ujTׂf-Fiզ=)ey(t̲Ң6ZKUcӶ҉(+^Lql g_N֒ŗ ̵jIesy=7AW=SYEɻ3\3dFT[Sb&6ܝ8҆ўB*2Cs'0^o+&BMSӮ|(KP9 a *>6;^*6U4d. -endstream -endobj -710 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 709 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -711 0 obj -<< -/Filter /FlateDecode -/Length 5059 ->> -stream -x]ˎqWZP~,Ȑǰ`BvʹG O$dȮAѷf<d)~tQS -JAQ_rq:?)fob]pȋ]uL9?)T*~ p9K*3n0%p$A`uQۭ* T0CgVCD QY#负=H:ɢ.BtN!:S'I`JK:[vNI:l.uŤh%]-]-@WuE%]9QS)(?dtZOش+ -3%(ElVIgaÏOxSVmՒcu/1 E QVD$qqr8LK.I,`R\VBX3Z"`wAbauf'q5$.g%.`[H\`ANe-q: 3kSpXP.%.\ tܣk}0XЮu)H\`i%qZ'wVQ22`V'0H\L&%%qk"\֠w)Hk28q&H\L%F]P:c%.@cAX"q 'iդSxN>Q'1º(O:,qQY #j[mX q]Mj?y9V;?vhNswunKۙ^׶q2;hZy:ֳPG.Y37!S *})$V9g'?3G(}dº6n5cCsu#4럣"ib#w-"P5W\CpgEd<]G(=:Oȃp^Zw١xkF|γ!Ī;hyGob};q(]"w[:Oރp>5g;1*ƤpN;h| xӡ >a?RSWHfWpkñ;MtȽ~Z3 4mP?~J}70Xs֓u \2IQ+4'e9ErkD*Fwph3;mGѦeJe~>>p_:O҃ -W36WJYOb,:φp_΂]ugTF=Mbv)޵HWh Q=o43[P0^G):O߃ܮ8V%`Ǧ7cNĶ~p/v+2`F/y`Aߖym1t<{Y~Q-뷕1K g*s*:f4/%kaC^x[c_ՍZ<&ax z!]}wF^shkDmi{bK5*o{$貟|!Tlv)3Pܶ[ʾ(zp%DVΜNy:}BƽȰ*{Yo3dV -llwǵlѝK_< !a4y*wo Z1;z6o>P%njkoӕ}1o䣷YO#!qKm6.ۺv;m6rسM,H̽G9nª}OA}̊@ZFKo)g^G=gGJ{v~.Ώf,-F gt6hH29Q8,癖r˱`oiye6>+<՛yFf5AÊf6y~RW+>q[_ƽ -} -+вv8.ϟ4NTᛔ|ЮA^Џz'6x=H\8i,.c,/PHn#!cyDR> -endobj -713 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 101.373057 101.433071 82.623057 ] -/BS << -/W 0 ->> -/Dest (cb151-1) ->> -endobj -714 0 obj -<< -/Filter /FlateDecode -/Length 4658 ->> -stream -x]Y$9~_QHk|/iX1Cw6"-<>yTuϐ0i<_)Hwt}"A->^$/.I`jﮯ_/f44Yآ'V[h[w`KhEM ` - yo8 -rs<`N+-FeuDh؂[4 ؖ dT-I8.0 \)9.0`\q\`@Rs pNs\`@w )qwANV[` ¨`8. Qs\@] #qzU`E$AScp\@]mq - Vj I; 7X- X 0C (Lh%X𮊘1 *Dq婢cuQ(g-ZY("p\`q8^`FX29xW(9.] A(8`~J. -CwAKB0 @Rqbz8p\:b~ t̘*Sp:TaNޕG x7M8:p\`q $%tpX8x e:B8.c-aњa \ }l\`   0s:[ds\O:8. (I 0C#DSs:) r"` S:mqsXl18.Ap3p\lRs\lxs\%lqAN$78tRr\U@o 716MqA$bᢰ:)2xlё8.Υx3p\7&dİ x%Jq} dX) -g ޷s ݓ6Uc5JEd1~;b $֣e2mT6B;3040姿^.Rg|@߄')56%_i)̎ɡיQ04)%-!B{m־3[zjb}H#g'i+*c F! - _H}NM=}[)Mˤsw*'u:9dV2rAn& X=B#H,hu(kO~֎OL-2 0X8`huni FL8C`Ӎز1v~o0'O\ۊ.8}Oz'}|iMMYn٤+cAwA2XUl#m1SUZzC<'AU5nu--<0`s,=&mޠnnlg+tHts ];u稦#03'NHNt>7eR?ػNkGK~?"? QtOզ+h>MwY9thΆE{*Of0]avcyNڝ55Ԯ!S1LLwދ9iW]:LE+9o1&:+ɆZ(eSϣ=s6mP6tWm/p}buӷlx -jX;tJϙyVjdv@+=:݊qIͶg>QekΠ}+|^?=w0y}=V>rt>t7x_Zv"5HixzyL}0wC]{l+A'' jVkl4dW>~V˲[ }cJ:H7r>V; -7ʛ_8tH;va؞hg/s6d O:M{ZᙩY5ǦB5X7ݣṸJoGamxӧ7.MrҺS^rBTߓX$WʷSݍ=4.nKB ՑH~xMWiHnSCCJaJiF6sJy:6S"] ^{׉_/i=bDB'SHEvz -9lR~HDfxX1#DNtRIv* LGb]Z ik5XR(XSGmJӹ*,MiosKxZK_Yi-[W"3QHmNY:J?1ۅ~%sф,.30d QIs:Ftl)_R5斯TP m4I}z#pGtVRN L]Pn.H׋Lj[B Vhr8Ȋ*M C3*l&~(*JԣZIEnI]Zl&mK$Uc.VuE(,OV(mL\e2RnؗWiӤbo)|ކzq~ȕTe5jH+9TcvE*PuNצHuJtm8l*ղ m%vIu5MQfۢl8& \`j+3{^odG@j/VZN,I R3as̰?QJY{89uhTׂf-Fi٦lVi( -]@&Mnʖe8/>EmiJiD[MxK8@g'kKFEJ5ɲe4;϶4g*k6H=2v=ToXQnӆ7\crwsJz -RyN+$y !b+q_:pg=Y4ܑmD{XʡOV2կ&SE?ܼ{a -endstream -endobj -715 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 714 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -716 0 obj -<< -/Filter /FlateDecode -/Length 4929 ->> -stream -x]K丑ȳ~؝ =,Е3ecQxR$CTYc.dg*c0DI!~tQC -Q>_rq:?!fob]_wȓ]W3׿@*gbT^Pe!Fム -z),`θ* T0UEm 3LNR }TZmu0D9g~h B&FY;ג.!$->+-'D]N:Ji=x`ӊ:(tR|u[e$-Q{ DlqI\z6' - -p$.G0d [\E\8OQ0ِsDCJ`Aע.A1Sk!aK\]f@1  0 3tɖ.tZK\ l7(qA2 ̠$. $Z9E$qAra WQ 4&$.@bK\X:b %C$qAJ(#qI(qAVYd @)%qA M$.f [&x¸6z3J\lpQDlӔq Nz$l1I\Cfn֛Ő@f]L 4H\7Jk{LLb@z=V1d3P _Z#Ae -b*Za?p>U"$3w_-]IvO_~{]^1Fʟ0v0 LFw{xoehb&" a3yȈ8HL17VokXCq | -#̶il6NJfNVcagӏ_۷˿0z_) hotUnoGWy5TH:~\J.2d,cǰJ9I7q7[yPyvz=^Vo/4އ%LLcYރ/Q,m wC-VVwa]a.CNP-min|zuh*|zu7>O~rnmů VMs6b%\B%+v_!Bꊀz}zaHm'Րܷ'zӨW#-}z - -zmPps{=tuˮ #^=Yza;vghKnژJ7h,ؾ6ks:D8}GP6ފ#W^zr(5 *hot0P@צC 8ﱊ(?2"2z*O|K<}FQ".s'wïI f|c?=WzG؆k7jm=t=kVt>ڬ;.#t['|yN۾A?Vǵz*Ťzʐ~,(OY%6򹖟5ii?C-7LN<>.G/;cyN/>f}P;.s?GgGn>rv6 kw>EN?b#y}OY9vԿG{$RJ\㿲RH~yN\J$Dq:?u\]~x<fcw&?=z`7 {[>`ӡtg_#wG++=Ib9s?+rz׃yNԃwʁÐvyx{GZ,11W[U^# =6]ϻlz ҡ!QŅgK]ޝY;}ꑥd[*Xaq:GMs'~g'~0P=Ggr6kȭ["]u.<έmjy܇3yNO\غT^V1]di&uw۱m\_3o_m(nzFpO7edڎ -$;H]䣼*J=Äatsrw~?q?ܗӣzˣѵfNݸL,UAB{۞)mƲc9,]zB񮟕狀=c/Ɵ.a|߯B^(r甔utZ_Wr-dbkj"[G(N4ۅ: -䠘OUr$8Oi}y+εpOP~_ۀ*>{ł9^ՠ'17 v: -O -lw*&Kb5qMozMΛN/iMdݹ%]PoZ*kTYfTR_Rq"Qhάzkֵ0 .tvMSJ-k.-LiP6 hFz9#ʖsq(}ÍYoHlⷋBj߸B=.*NIr_EFﬢT᫔g]wJhlV񼑸5~4.ӜdV;qץ4?w]y }7:ޠEX huji}ACǍa|ZvՈԕAuromĦBhZoo]+VG}&-'j,X~:8LMg۔|eE−)ZgXFBq*ͲH^ImzT;`nڦsmEx, \`xNJ觇׻}29@JUƥHZ O0ctPokZecV' Z(mJyfdjlY3Nb+S4yK{+=HKzK:@9S-e% V <먴*Yd+ -endstream -endobj -717 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 716 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -718 0 obj -<< -/Filter /FlateDecode -/Length 4732 ->> -stream -x]Kqׯ=aaAAavZk`Hdy$y=]GddI2K_~/bL狚SK,.2w 䣻 v˱?qe}5SJhw'fB A9R -, CLIbA Ж $ cRvJM b -rhȃ t/|L&FY;@i&ｋ KJK<Y&RAybU" @;IE"(Kvr)!nyFEkzrM+0I><YrIAgx~$pZ nxHALCXA㒄&! LE -& -J0`ȧ U<% -8X Y+WAHk -HX`-d1d%,@[HX`oIi/aBL%aI ȅ)% ,0;%,], aZ獄k)z ,pגVpZy,aq:Z k -pHXY`^dbTpDEp&A+aw$ 5N kx `(Gpp`%,X dHX: kh5阼#OIh\XO8.wQ`j$,p]m%pW$,p] NäHX6iyiR)F pd$,T0I!wޓx"="h$,@\N)$pWḭ*nS`pBl$,'B>'\; Dd@ MQ‚` 5F‚` B LI#s,%,M1IXG>J[T3cA&, Btr^)6_~/_䝲a<'ֈ'v|!Dm=uXX6XHbtmRdH2k3yd\Y/p//+?DޖB>Á ;,Nl/(֠Qm7~9X*w뇟.o~o݇ N_D*D8q9]ҝR0~E/3z)./L_ni54&(rQ8r}~84jubT*.t5G\f]ǖ_V)m<ڮz$ We[Q/6q-c@2m[>ݦU59{OɡXy>Dx+ -m煐X^K[G a6F:_%/O_?6`^z} R:~.}y9#gLe=&>~-|o3cse}U[Zڑ.ZR [}s_0=;I}OebvW\ʐO:עaK.ޮh;AoEc-5RWrd{7Nr&jY -«G+`-dx'l29#R)*ڄXT{U.uM^c:,c_?Xl%΢[rC5O&{S[\>OhlB ^j#-[ދv~Js&XvlW{=H=Bigc#J#:Ԧ٥m)h6ڤ=DBt]*r^o"ټbc^Nt{A6(䛲o:͚rIUrĘ7SA\I!ֱ`8圷9VيWWawW벼*:5l]޺Oa?͟mILiŻ}__|Kzg}z]ȶ$ՠ[)%^u(Nj7Fv:O[[ -Z$/}^(c[~򙆶rz;t[m\~.ycUpB,"%shUY,ؾ Қp+[kX -~:_6IZ&$utwu\˪N[~w1sqY]1m 9z]JZ~ek6r cmW}m~e߱!)懖>'<njͻWX$z3Y˿kzGxγYߏŗt{_zɴj_a;Oy: <_zt,of '5/uӬ\>TV{ڢG{Vr,qᬵ uS|א#;Y٬,|fwfzYL{ݏݪD^o}jwy~jW=ujr;+oxR`e쨝Sv[c8{m^NAmky}'<%y_cky6}ܱ񝖓dރq'roZ2=fZ9:fZ܈>^AbXoTٌӳڮ[:s|P^ohm|n"~nw0/ɤ4ȁW&gG][ -|({|RuL}3?Pd`ާNf9"fz>~(F>|&WɇE l<9]y i:ݫ|&NCQQYutVީV|IsjoX [2^MKd˕o!loW<$k]'h>Dwb}T5a=n&R(TծQfRZMyH@Nզ ì31VCV.rv˕\J^5UwQ/nndX#֏K2 -Zn̆x8j+..] -D;Qu{T~;nYi|&?CkTFAS3)>Ҷ_Nxm6RI#7!IB/;KlvԗJ(ϠJ7-zHU<KnV aU? +GBNv͔.kKթ֙׃n'o#9|>I;|%޲c5M?N:٨zg Po\WkC'Ε/2.d7g3|.}_}]g?nTC ӰuA=9KKOѱGM:Xcܩ=0{Ja:{'w2Z4],14UP8 l uѝ*C v8U䯧FV|H7oI?S -endstream -endobj -719 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 718 0 R -/Resources 4 0 R -/Annots [ 720 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -720 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 612.273057 101.433071 593.523057 ] -/BS << -/W 0 ->> -/Dest (cb154-1) ->> -endobj -721 0 obj -<< -/Filter /FlateDecode -/Length 4685 ->> -stream -x]Ks|? b"99zl9$>D$vX`vZUT"?~*QMqJ?>8ϗϧ/'Μ7 Ypzs1t|a]ߜ=#Β`0*qCT\(Be sNK`(0NKT97 -fh)=0Ci'R`tBS*!qJp!$p$t0FN -f}9脓N)fFPS: [Lb֜t(8-;Elh@0휢h@ô tRPD8l1RLl).PJ -l V (.P[ͅ@pa&@q -(.@uU[ xWi).]P#S+ 4xW (.] #Iqz`I9+=htHc ޕ@]i@w8 wA!v` IEqN$ xWLĘ[1ქwGC̄D(.0]Ч0J xW(Ԕ+d.Cq 01]RS\`%Iqfa=9 @ƌw1 ,x(.]:آ~ tĘʸSP:.aJ ,x7NXS\`Iq,6p:pl(.p"uE;MqkT8 [8 [2P\ ` BSL|Кg,1*y&u:(.pN3LłRcS\g]f@'4.  01/S:[dS\O:!(.K(r 0C#DSS:c).ڲ*R\aHLI` hO ~l"!uEMq2a`3ƛa <> ,ơ )* 88̙ś }9J1Rl̏Lsz͐)K?PZÿ0m} ܾh,ԉFP)f˫|Y|<[ -G:+sGm-ʨ #;r+:Y1@ae>KZϧWܘo׸XT$EC|v*\CZkrr~Sou1դ{h|Nr Rۏs ^ ;r^JA7r4 f?L]@cMjah&8lC\4~7}ITUĒ=Psa 4љ): hPP[ϡDYot;hdY/}(yր8Q-TьQ9.)]Atf um#ᐩ79P7md,c{o襄;b$g<[泜^˩;+ٵ5m6$vy~H#z֍ƾ:Csw{ dR>>֌սǥvtmںǥk ¾o졷лO^/qe3`23=9ɄK˵Z}+)6_#sfhc]vYhh;>=ićR=2Oy<4W⻺=4V>,p/cZp}u?bM_q(*,#\J].#_n_"Bt{hg!v7&} bTJv(t -cC!ޛy1~Kt'^1z=Y^b ?<`D\g!Nmuv(p-bޜ?qiی#o)&jx#u9z}T{w3MDÓ.M.П -iy2kCvg:;~K7YAi:CN'yȰkhmĥ -rF~lz3h怶 -|:GCQ4q/#m'd4ͽР]1{~ѣע]=Rimz{OK95+]?ue\&`IW&>Z {s8nF(sl.bIO~4PQEy4h&l_ɵQ;fz:SCYkroϮ $[iŕoٻ:Pv뚼_p4`i^6E;(kG _3#f=pY/Ysyz{1efOɨ{)]⯤W;L}RV~.0^# v%qBq9ă/q4 \/_;^ҭ}\U}lG\D}>Ǝ8HσJN]&L/XlZg!n{7lgT$PZ杫{fQ;qa^g!e'{U_-rXYޮRoP^],)G\UN!I2bŶUϕRv3V*:CmY׈_ ׮-]iOr}DlI7Adhs473^/kTs8D$׬ -~@A ٽ:Cpʾ{M -/ժM]>Qb:CoBjq勛n;v9zև)\ vwd.kK]A oBw9rػgڬօoovjq :Cuo~ E U3fg)j֌}w_i3IUv=۾sw9Rw|wLX}[[ck뽬Vo1"p?Yh ;Nx~a]e7uΕ7{%v6 o}ez^&-úezVDH^A y:C}.yL:7cuJtZH-:C}9wT>֌ ᇷPolZcfbF~ΠMk3+2dw tE2Z {*#{D}_ -ra;|i!xBf9A ،fhKſ2il!4e;k<'m^ bōtʞaэ_NvcH q뙐q#ڳ,s5\iM -+5{Rӎ~LwS -yBgHQHY+k!OFrEl2gbC`O-b"n0abӭ8Bߧy+0B}ifv}X5^N?iN*#>X%ް%EI6#q3[̭3q=ŝ}8,yTB+/bKYАq)+֥:/ĞJ̠"kk)mXej!4{LJ7˨] -*S:%b2CeUIqX]0ffF@MuWxr#*:]I6EU.kQ_4!yx6(Ԟϵ4Xf£j8ƞNNŵгԗjSS_T'itO|FlS,{\)M+M+vQ67x[R25];^Jf_2[R]J$[^[ϯfsubgK5(y2v:M*~̈eNLZ8%9Dw[ qSm}*vd!IJNo+&> -endobj -723 0 obj -<< -/Filter /FlateDecode -/Length 4981 ->> -stream -x]K$qׯM=aaAafZk``&Hf{zWy]G$#]wSJ9wt~ku"Sppɓ7^w3|%SL1*/2TJ[AAP=sT0GgVaK*I* 뢶[U&j'`> -*`6J:Fi?4ztFO!eE]NG#鬝BtkIOtx휒t%]-6X%`IJ[ Z' [$` -JKl's.CRL[Q~Z%鴞:2hz4S'MDai\?3Y>` <"€46E}[%o Ŋy]2i8G?t???wpjq4}},庤}YdfIi{\u//e2IukS/@zO{w?WfLo,߂_9AtnjgE.aTZ` {]w] - -PŦ!:TVP:X伾u:Ziru+O),UafKΝbg*fGHm=v~mmd(t˨\!+m$O\وslpzTI2Ҍ<Z!{YL|csC \1#j Ct3 Doбzf^kYT oq}0(v|Gz"=~ _qn2[)hޫkղvm<zArz_tH>q-CZCcSٳ ώ?ra-kRX3ܟcu!FmCR]1i<q4qmf`~PP牘~dOlv6~UBo ߎ+hr|YF?TԂC~Id|EWb&{m%c7Uzv7j?V)w-p7Uojdc*,愕Zzl.=i -]Z˶`%=س-CmPZȎP^J03 ^P^^]=Q:0Ƽ 慡ެwH~᫷Cjllk6 l{۱~ޞݫ]b?-mSJv|白imևfv{3]a~?Fq_|m <:61l9rFUWg.y i|;HEݸnC;a&遙J5|ߕEK46O]P9Ry,ў>L٣ϤG-VֳbzK'wdS,=(+ikZ]WNп5DNkd0Ǣ_H h1l,rؽc LϺ !u%,OO7dT!]$ӷuq]׺m$}\;wHIXƇ#-!d]%luk`5=&)==WQ&]Mπy)˓Ҏqy/Vd#5KHy -aX>E=TxF1ց^[\IzQ/mSe[.KfKVi,v[>;Val( l2 !W/yTu)}T1'/dOu̜;Ro-Aibu4w9A<c+嘋^b_ )QFS~Gx1ϳ)NJ>;ZfF Vs_fO[~K m|ؕ_?nA']y-ӡo(YśV"iqԦ;h1壐<OgC<.!y}l6<jOvi zIEujgòV֙9VeI>{aMmov4Q0kޱS޹N/5f tIN V7eUX.I_8`Inwwy{``pe2/{Q;VfPCT_{sPS96A#2ȥL`zpٳ:W/ٲom , uS%[e,HSEN=KAoJO2qZ-@_9 -endstream -endobj -724 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 723 0 R -/Resources 4 0 R -/Annots [ 725 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -725 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 401.373057 101.433071 382.623057 ] -/BS << -/W 0 ->> -/Dest (cb157-1) ->> -endobj -726 0 obj -<< -/Filter /FlateDecode -/Length 4701 ->> -stream -x]Kϯs|_@C1"$ k#XsǞӏ])-[LWjWU엺J}_ %BE -o% %&{|*I^X]I`jmş/:EN+{"#|^ZF0*k:F!ȩ`i0b -fցQa+3WE"N3TQ) ;Id4SV8ttZ CtIYp(*"` 9-`p:[4z'2[`tRqhEda -N)aM00H3: [kt8x3[uF,l-|-;0D%&t0t7 h90RAGFKc` a:b"q\`4lA - lK@ tK2* r.̔0 8.0\@)r\`qb{ XX9.0]Cq\`一Ơ&-0`GaT0x(9. .*Cq"t j4xW[Jqw5iq"?ˇq=tp\ƄFXqiP!: ,xW By83oB99.]8*q>x9.]e9xW(9.] A( %]V!p\`%qL c!r\pޕ xWV[L ӖV` -Nޕ -#Rq&qI0P -@"z8.pQB9mqXP-"8.9. d -7 RL&B$[| Y]Ny 'W8.@.%&= x% `t8.`p\W$FdlAq"] h؂h゠L'9.F.t$S8.D -9.4A du4q'%ۖ$?H6:b,q\Nf آL J؂(Ha2q |S) D#o"cm4.回H"DauASd-8 &؉9آ#q\KfaMD@Hg 68x7rZWqv@z-|+d V]3 ߔ#0ep*Jxfp[}j3O1-}9j1P>󏗯^7JYS҄ -@G Epa4XIFXTq- ]?&ݛ/~=&0(`c*hp Cub'@qI߽5в٘dpo>][ d}JmAkvu8nq{,!62!ߕPWʹz?OqQНc[ZD`ʤfk:E鿧z S_oy})@8(n~ -"ŽYߝ FÐ}w +P9xcO<*.1SIp:coe5MbC6}(9-Dg]703A[ -\&> (;ms:ݏ6n3JF7{4™ d$1^QAg2٫zk=Y:C꼉j} oX(ue:o!jx6+A^oh}_X!Pu-gzuΆ^#މw!<+d8 Y@ٟSos:ޏ5x>F,+JPwch:Ix3W>VK녦1% (!l[!l%.Y'qU7ޘuЃdk¥vilƏm:d0lhMzBέi[ӡ~l8'7t'--`s>{]3eއƞjGAp'969h/l}WݛMY0:CJv2y|ww8qmcx'wBWzycȺndv3zvиr>,|R,|b?ef9_v vH5ллָc4&gnvZjHNx2#ͭŊU[3p _I]IChWbΗ V8>7ͮT2|ni]wd[<:CJ -9XA+v\S/ϝg3b<nWbї{rG3Fv*t/ -\C:C{]~->r^}c݁k79;vu({G>²anۄ#d\dSh>$c\@>hcӡwZɰ>w؜Aw3]Gnp|u/kH;o>kJk$fG+k/kf~/2.\{4_fl5}62诙jXXW FXl+1jMKDጣfz"i<Q3׾swAZoRGF/3 ])T ,&O|tq +p/k]#T8?gqbHS爡˽Y]&K|o]1y N_];HbcʗDM (nb˭Wos:ģеgO ]~yrLi\M692ö&Vu܎==>LqjåX3ԸQG#+*r9rŚ)]H@,z|K~6{<VtZkTJ)p Y&qYj u B| OT>C[m;>$.o'~Ҿ3acfwѨ}d!$酥WG"ym7ARyPsxRj|L/K/EEQ(qy/-Ĉ(N,m|EK+3ƍ?G\-=d.dvQө8j7a-WL. amڲZqUlv.XSG7csUXLoN5ßj =5+rjYd1*%ˀP'Fxa_4a00d Q)s9Fxaˍ2R -j=_MP7t<#hfHN.@kb*~Xϔ+kixҔ<~ajfYzOFH ?Htխ47xI!Z.}l_ȢtKciel^"BS*+Da -WB(?ON[*wTw[ڭbW2*t[m0c^NXa5 PŕFq|?$<洱:3*C(]Ҫײ.:,q:l7Pga6PSCUB-k3׺ke%\RUE -mF t2M;ǮK ұia7&,[pT|mV*Z]:hfX-t}ڡ0i_FFMSuTlt GAlڍaRN> HBEJˁ%i!<^jM7,>\FJ[{9ujЂ&-Fi)edQLfYigX-wpā%_b*iێJDێMfW%S ףd%#sm"Zd|4w0jd*k5;+y̝[n+kIy5p'8eOY*]|${p2Fz- E\W4M=oEҾ`*ʐf\ʦOëeU^*v(]W- V] -endstream -endobj -727 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 726 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -728 0 obj -<< -/Filter /FlateDecode -/Length 4935 ->> -stream -x]M$qׯM0 @ m F~L욞ZA~D,}UFR]o?^~)zꢨZ8yCI`71\.o.諙rF_ SL1*/2TJ[AAP=sT0GgVaK*I* 뢶[U&j'`> -*`6J:Fi?8=H:ɢ.BtN!:S'I`JK:[vNI:l.uŤh%]-ɂ.+:آҒ.䜨ЩVg|VI:'lZQA -QϢxGҁ') jIa1щ:؂آb(3h"^88lD&%$0)O.F+р~r!G-UŻ 1հa:b؂X [XZ$.[oA …J Ƶ)8 ,(PXpwJ\`AQ ֵ> ,h׺$.]봒wEMQ[` J\V(qb 0p$.V&wMRN5K栕w-H+7xxe$.p]L@?J/+q{茕Ma3?aN&rwu< ^tYBe%.]g?aE5xX%xW$.] ^a$.6i芺< Z2`T8HZJ\X޳r{DlH\:L[aN#XSH:aIU*f xM B$I Q $7!+0K\%`NS9I\ lH\ lA q")kD.Dɦ *邙R]&,Z쥦I/q~pIv [0U$.R4%\i؂ [Di-qA2Ѡ$2+4psID&i)ElMH\Ͷl6uz'qAJIₔ`QF`Q€` "> -ơSJ€I\yI$qA -Mlymf ;:؂) &Ib @$q 7ы)D( >$xio" -#3YhǙČzb@{ZE1g@G0;ĬU( -xm8a>U"&3Ct)6o?c/) n[-UW,!#bFjt##ѿrN6Er)Q6&*;l?0fv]!_-]l}wh[h_dQ|l.t?MaRiv;| -;cZel64oPnUw.`Ŋ9.4V㯟~1^/~Z_>ί P6;ޯl3{_븡҆AJZh^{?de1Ydc;D]\%p.05$tVFի[ɟ? |M#"St'<uA{]˴~A.rNÌy.6*|sؖ#tup6gܻ1$|ta'4\CAp: &yk (j۟.$prYHsVP>ry:ޏc,6(ï_oE#/2kx,JHqNy6skX}=:"|й9ȭAu,^>-Q£_،k2 ж{av:OԃX;V/ZƉ:G}[7'ZqFulesotO_wٓuA/dvxdCKwSe4j)hq3"ua5c~[vM;<1#?e'<AsTAftc}}2ֱ0΢A/O>=Y{?݌ְki+өφ^:Ϭ8^n>>g3[}Ot(=\jz!d̥Hh-ts\K>e5?9p,FUn2%zγ!ݏk`'`5[Gu{pw@dCص%eΞnuɲ!Š 7ոu]5%[3ڲ}3<0ۊ͑'gr'<ǯ#U6)0$U<(EƟ15ƀ8 -7Ҍ lvH{}-3|Zܰ$\C -3ֶ.湜c}!Fm~|~o6>iDL'<AwXiM/~ <Ψz0-sSgɛ3ەQhg$L2߯㡂_Sݓu]+?=|g\cu“{mR-{O8zZyɣS Tczj葠~Pyγ2|gOzQ[A=ݏVDs/!7#M p\w! b$7E^kJU~6E̐Y llwǵlѝK_VO[ۉ4y*.q!;:USTF?6vVS[v/7|XmeKmQ=~sD!KSun6n/R(? %?}V`羽,"{n3 -tX~=cץ_AZ|Hqv3m;)١И13o yuL]X|ۮfXlk-m2 fLt_׷>>hIoRV4{mn}O(j_~l}f8q '~~&v}Of]ީso* o0xw/VCA-9&iѩ i=w>MT ?%tcdiBT$FTɴT'!;yN1ѣoO_A=fvdsaUwYkfD06a[E:RUEBaDz! -6Wˆ~ެT/3c N&gI!dX{[x _kf*àrߎ%u9^4iCsETKOcqIYh}ݩYuVHt.sV~ M5y UXR(~З8A\O1IU-[Ƣn`8$_-o{Zn0[j![s;VLw&gdL@ { bmPظjʛB6ӹ4ZD6 M]Ԧwj2ˌMk6 ]760MF ɵrDXniͷTUs|7CݦxAvcHߤ戲ZL6*1ܘv.~(+Bm:^4*L*#*|75HѱwBsNXI.]:ƆY/PHn[I˘F50[WbbB*lӆ c:0v^KƠiw2i52;|{(EWpol_I\QѾC (.Y[2;i' -K} FХ:חYt`E[~vwWF?̝ΐJ՟ѩj5|J!C}VtJ]~d!cr֪+qeޠ -T\ZV-BjӜdw"[IH[E -TKAoonJ˟O^Ouf -endstream -endobj -729 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 728 0 R -/Resources 4 0 R -/Annots [ 730 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -730 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 176.373057 101.433071 157.623057 ] -/BS << -/W 0 ->> -/Dest (cb160-1) ->> -endobj -731 0 obj -<< -/Filter /FlateDecode -/Length 4694 ->> -stream -x]K8r#>X X va%!*ʪUϺ )E"?~K_ %B/7)7 $yaUtNㅏV{wMv{GݵieTdK˨"TRFe^[Ǩ9̰4-UfP S :03 ye3Wĩ`3*%aR:"ft -FwN+Bԑyל<)8]98tXE$9l!,uZZa1)%,iXF:yFa6:bԜOXC`FNH8-Z{bu1vEzQFHq^PđFPQ =F*HbqL`l!\V[L$ -Hq1Em hnIFqߒT…5 (E 8׀;9.0 ] wq4k(8 xאxdu( -%=0Wp8.VAr\@]$q\@]1:/0 ]m渀@z]P=tp\„[q愈`+BtX ->Vhqfܢr.r\`  fTq*Ӂw ޅ`9.q7$ꢐ1 ,x9.,,d:/$qXH8.qJk + n-&h @aˌi8Bj0Jt])}wӴqI0P @"z8.pQB9sqXP-8"8.9.e -7SL&B$[x Y]Ny 'Xq\XJ z @"K q\#lPS9SN6tS゠a A 234bI45#qA 'q "M0%- ?)ض A0ct -7!-5f7=Qx|DDr9.C'%Qě8.Lf x!3nq)D-. --p"3nI7N\7p3o£gB7=\޵L8A ϖ%zg23+k1K܋ʳkb$vf" ]5 -첁'OV2 $DŽ똆ӏm}Ht0/U>ih5SZ[ ~9a "U٠iYS?ĥ %-ڜrcSSel:ubwv]A.uMnS`ZⓎK? >fi>Oߓ^I?o)KllvN:zd_S>zI~-dJ]bR/R{:"f6P[0Тr y {n['st_vNŔ> e3t^N#ϴ -pCKˋzcy._:?&j4VΦ,s94}WC܅"C=f0 - acyZ5}->~VG~gz^}0吼A#OogJۭ~>n"a$41>^rO5xfv`e\i -ȟv|Q+cz7G"Ʈ"JUVLwbV2t}\۾{kp!yQޅ>%&=y,I;~K4vwțxp~=k\i5Z:XoYL"v\;I*}oC}g -sx|jw5s9le̼g+l2{RC@snŸf| VekΠ}+|~gX;rH>Z+mi9:{s5q?вlAJã1{z+ߚOuQ~rٮFmyW>`ˡ;*7}gY:L8wa,껉V=y._1[ϙ_VʋaI!X!.ޫ(~Abuƃys b6x]=|ݑo,{^6@γ)e4mg1>?`ˡwYɰ߻ql .#~@w2kH\'ߧ~U'}{g>h\;k׌ 7^cޟ~!Qw'7Z<ԏ\>s5*v`n9jGŠֽгp}3]z퍗 z>7nJ=Z7j;2PzI6OCK?Mxi+ƴ@lv7(M^Si Lp@bi뎵-rKn<ϐTy}CaKR}ؒӖE\n eMC9!3Tߓ2H>TwcM#k [Шa25OݑHxOiHnSCCJaw_JiWK ڞL:益$R'7gxINvKs#&8 CY"-}S+tKiKP|5)Ҧ)$s"3l2Vө8]j N0ә+XmHmZ`͸+VF6Bʦ*֔QiCt -mөsZPo4mʭeƨX6,Bˍ sф,T0d QIs:FrcMS -5k-_MP74<#hcs3FɇsK=Z7z!|Y*#n3m -i3Zi- +^4GYITa41p@*mUj%ilZ+C\ B/mKɤO[RI&k>fIUA]' -Slb[6W;m{̩[Ůp[+Uk[m0/F8A?JX2a5 PŕFq2n}6LsXqJ[^//yqײ.:3Yh: F*V eO;Y.+甪0*Vhk6b]iZn_V,{NjL,[rp)NВn2-MZ6334}ڮ0q#ҩ:l[t W$ lړ`Rmqfc>HBEJ˅%i!<^jS7?-s~?B,ӌ=S:4kA4lSVJY64O. YVJ&7e2\q`[Jܶm{4m{-{&dpdMY|\H4Yu\UC\Lef)G!* +#*1QF{LNpBieOY*9g{dBNښ^o+&AMQoƘ|(K:PnFisX *>6;$^OBld?dZ -endstream -endobj -732 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 731 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -733 0 obj -<< -/Filter /FlateDecode -/Length 4770 ->> -stream -x]]q}_̏!1r`a cn&D]N#| KEIG%%-N)I[ K,ɸ맟.?;`O -S/oӸvqKa{,3sϓܩ>44mrŴ\9O͎RwKOe2tL|=׽/Wl7q巟 = ّl9.ey >NXށMW˲n U|v~uqHrGݗnrʫK%ݟsթzH8FS$292>vtmanwsQZrݽhӱJ_ǹiy9X=t=hVtڢ;.ѷOxbbzX͸76_\{%]c5mvos/,.M~ȫZm)i\t" x`xI1뫇OȜn}|>:;~,+m͘2c8cs:Dn2*Ymyba=Ts:T<޼p#jgo㫫yN *~ʡ z]uo .izyuD{nsٻ8R IE`>5!AϵhܷF#!.oMX*g"p=^G#ggTGcp 2=W85Ƴ}Du_WQ3~7b ed#<1FO ugP1كyN#_2H*-STvr(\!J3.dfeBڪkղv ҡ!.Q ‹ZڵjqID|`!yժcN?Ǩ߾{veR-{8zjiƥ\\@;>v^뙝vf?ߤ:巈N싹+tw u5˰1(2B+G)o_{sgLKazt5seb!B\Hrdbjeac9~Dzc9,]2r~Qfe8vê z|q&biȑ QYҥs|15B___]1Ȑ];N4$2WLhE^{HV Y8T,%aaH}JT |4MJ}J";~T DN|jг8/vmbmPPGwԦMXMMY&']P4UZר*̨TB"ShBgV=^I K% ]tsiTb˚J7Sm /6!leǥ(}"ÍY oGu$6!k\\ZVnGҤOEJUif -fv*c徲I-)t"gҭk-ɘ> -endobj -735 0 obj -<< -/Filter /FlateDecode -/Length 4743 ->> -stream -x]K$qׯcdkX}|讝`X/GfFef̬Jӕ|D?~`UU;R.?_^_)(779$.~˱?~ues*`3ȩb^Peq{APp9K*#Yڪ"̠dmT f8mUfhHR }TFcu0D9+WNRYEL9"o$]V!$txC%l! El):IawKJ蠍ND]N:9-Qt3 -%hElN[I` Gҁ') vIaDlK `l1H$1*ʖ$)J$)+I4`Wrxi58 [< -+`$q$.pXr8--8-l$.p[&H\@0SK\.r,q:p%.p`]烕v q:2Z:3I\@]gtFV)i k& k#Q栓kxג ( -h -r8[@`: ИK$.] slLA5 '2-LYB$.]gZ [TpX3S̘Sl.~{\~UvN9m7J&m [?Ri@mfi2,f rgX pn{Do~E# -ZuH0ЯMSdcVFo.nHf~7b>]~w~wbDA8iy3 *ZS^'9|SYί~𚺼c.momC 6&6,l 籭SΣ?7Z q֙^ls saqq><@(뷩=㶝8)hv,m];BgR {mԠ %Ͷϓ;K{fW_/Ol߰5j4Y?ϸOPn7\hv >u^ro~ a) V,ކ92JO?y\} K#dz^ջ>.}fyձ97Jzo>p[U'2}=/^7q>Oy6{!^|J4VA[M˗6rDkD&]C+콃NG:ONq z;oW2S_q#ek߶0FMWv+m5k{kʏ<Ԣ{Il2G:O3>dgCg+ 8ίy{ Q35'<gCeTn~!x9%{}ӡ`o mif4Ar;#"Gy:OXT:Ľ3f+jcs!(3aA顎Wi'vƍ_!y8S:YbQZz~oSJrLճ!4Ve,?suƃk"pWB+Sς]XS9ɑtsuqWrD0BނG_ɞf'<<{ P|w2ܗ=I~|Z'<"A Z*c_p' ;{vOy:i6{ǓuWs+ ܛ -\͟-^OrYKK8T6:EͱYɱoy$fnOQ߾wPdC~wjtQzhtViW}jJG?z=}jWFM:φs\ԮV'VX`GjǸY<1v۪_a'H\Amcy}'<oc6ok>kQ$EH~7G=<(mf DE Sݞu5cOf>8,ȑ<4f-fy2򹒙/xIOv|P(7$/h _)\i׃B{MƟ/Ai1:$e,O5M|eҎL6SmwjowA|gb.s.&b캈&+'ALO:p~[[dڡYUv+F%Wz~O׻VCpzs`Xf0[1߽Vf$L67Hc`x(6NB꡻.T1| ns]f:3 -k0{ݺ]굩] F&dj$nAMQi'a@V.rvͭ6RJjt/nse#՗K1Z7v#]<Ҿsz 6q/]O[N05'MS^jyUf/4Cc<`(L LBy&Vyl!\6c1I5XMC]3U47(/Nߦ׭`nƝ87|r;` -oeaj']lu[zgRNE\gkc'O2iŽ]x)˜uIZ12E_K=vZǭnla.J_4NgMAhi.6 mvku'Z45M; -} ָ3~Gx[y2_:6}.]9>O9Vb\s}IM⊋%ZCE\r0wf2 N~q_F:t v0ӼG0}69FM>Jۍ,u2,/ۚ![uv0\ r-.Fԫ)U٢ӺP4LWYk1V\q[Lѥ=QiN㨄MYnx-Zr-#c;KX2 0nR%]meuAݐ#SݫMGxTXDg]>BJ4l<\gdCRNƞ0W/&CCSkjYNswo=DzA.#U{b f6 -endstream -endobj -736 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 735 0 R -/Resources 4 0 R -/Annots [ 737 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -737 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 627.273057 101.433071 608.523057 ] -/BS << -/W 0 ->> -/Dest (cb163-1) ->> -endobj -738 0 obj -<< -/Filter /FlateDecode -/Length 4678 ->> -stream -x]Ks|? b"99zl9Z|*ITX`vZU|ȏ%)?_ `gę3A=~9 3"XoΟ@9悑ΞO?ӿyYQs9nU EaIc  i*3tR -'Tf(턚̐NhJ3D0P ;NfI2:p)ŬJxJa \P:[КS:آwe'uEz(--@'u[.(]P5 q\'a+)aD#tXn-FqIlt hqt+3EJIlAS -lR"/Q c:HMi=S `QX xWxt L881nLX(.0]LT}z 3wLMBNqo0L%u= Z`f܃IHcd8P ,x{wQ n-K @aKi8K0rt]]wIquQ =0 XYpR\`. ׆!0,R[fAOqEIIq.Xl\-).1ZYɼ]:p8bAqRcS\g]f@'4.  01/S:[dS\O:!(.KU`ZMM4LOqזEW 4&(.@Ŷ,6!uEMq2.7=%f\o: -(.ܲ&S\s XoJMqe\oz XobG۠l\o: -. --p1nIXo(-2h q).&ъk 4_VcbXKs?| -}|:㷠05~Ct8?|@Z@:Q2^iZ35a.uŲ&:]S~erLp>^+{R92֭KLz%7<pC2mR/ iAfb=Γs4`b̦MbLգi HG\ $ҁ/Y]R>2*..Ӓ,UWZk;/w2҈^@ؗph>ko^Fcѥ:֐ڎnZ[r.t\/лLwπQČrONx2!Rr@iY3Uϸz3zgx6zg}1Ԃv[hs84nӺ?e;#J^gO^u9J7bw[=ɫF_Bk%.mPX7zTyt΢}-kϠڶKzڙpQi_R%DGOh{AuecG:Rim|[OK95+?]}WzeةhĤo 6l3Ы} 9}foqb'P?{ymH׬QEy4h&l_ɵχy m~ꩡKro$[iŕo5@[Vt_5U} \;ڒ8!q9_>h|^|96[]}lb}sp?*mV uC43DTҳ1>iTv9n_wv86]zyUW|v_TO\zgIyUҞ$#l z⵫Ѹ;E^c jHػ'2ch=$M#7G:}o,gܻ/jF#rg!ҽ${v ލ ^g!og߽&~jѦ.(_@of s,նy -y+vo;v97Ӆг>LᚼjhKMmwqǕe~ñ _uÛНy\=Kof/%{5~жSf+nv9r]4Tq]쟧83:DcڝޕF~}q7B MP86MOWB1er|ZF~7J~R0=tnrEb8[τܞfq x^Jmbhhq^9 %O -xpbLe'4Iz'^"~>S]5!֚Nqy.K0.ZBRǏ!L(MߤlS"57s"sq{('z+M16 a)PiK%X(^ \ȫXd'妳EMNTݟJWurB>xg**Y*B2wD.'BOEktfWO5 -}BJG.'2X=r*_ŔusFG}Wcq*R_s_F΄y$8")\M^-TUYyK$04, R<3nTfO:j]I[5p.cn/9>nN[l"̋$c*uY),OZȓMD\4y2+*\n̝ϵlo.|^M}*)blW*0B}ifv}X5^N?iN*#>X%♳%EI9g['z&'Nq<< 󰩄RW_—&!RV|Kv^=AEBSڰ ])T2fExiZ1;2M*Qxd./:UsU$b2Ceu* Ųu% -.*7"^eN.$pU}QE]iC}GmQ=Kki(̈́GKpiyQxoi\ƞNNŵГԗlcSWlRi(2]@Ɠ,Mv̖ecO>ET{%7{rӌ% Sٕ%e%=!u,%JyzZwmmb-)/,MwعiT3DF/ǂb)!;Zpu;P<뱓y$NL+ŝLx"l+UlP9> )P ʗ..Mǣd(6'!KW> -endstream -endobj -739 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 738 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -740 0 obj -<< -/Filter /FlateDecode -/Length 3553 ->> -stream -x͜K)l@4*1bDpAXk#XsϿfήddXtdWENϺ2;sIϗO'kR],YN&s8%J)Oo?:M)ѻpL)٠ -T֑ -CTTb) -fĞ3䠩`{UQU`O5p%$E,pZUC,3yE炉31_T]%LLtCt [BNt)'Ma EH%1:Eeʪh+dB̪@gsGLd5s&7IaEabRtD-t[?rVVM Ī`5[lpIcOpAg29kN4  ǒ4uy,l 5-` X@"4hܲ-Ncl]X@.̴ ĥYcp\;54K!z稱]bg50K5\& IcXF^cf9[ lYc>!dIc> `w=bf.t DcAw]AS4he\.QcAw]b\ˆ+l\EcAwHcAwϬ7^cAw!Rk:pb5pyCXw0 7,\WcK  ,yfD%Gr ccj,.{X]4Dp2U[({kòU4Uc=H]0Úܵ6ܕ &d^cAlJJQcA,:|.\B,U[8$֦P -Ƃa RLqȾl-5d&f)D0.zp2t.i,H BXX x#c,E&{d$ BƂa Ag2X$Zӱ}fX9I5`` R:Lh,f;h,MlsTl r r-zMo&d| Fd8tj,(.cYc֥7ƂBMlu[(~3i,( [RU[4e݂IoN._XcAQYc 7ѫGYI=.wC44j,lxCB~+8zb`ހتX*g=zh3Q=5@XYi۷8NW C n׼}8n2y{;V,fkK۵^-QLmoeޡ߸! >L]6þb}n6>}9zwoO߾;ߒ·;O}U>_ 7ņajp4?\ojvAw5~5ݶ$ǥ4l 1R'۬cptݺy}u<> GwWڜ{Jh0\;~b -K7Ͻ u&ؼ`kZY8ն؜,myxŃyu̷y;+̡qO#?qE~N:ª« J}m/VƵqPf'':Γo'4xZ~^n?5x(7?% i{ոIǺ;>_@: Xb2i1ϨD}b[>6)o!kd%#A[hg4ne~CNF>Uc+?upgv~ngNI-|eM'' /em ̇+[;ֻծV;v_p%=S;:Fٕuո6%2"~ߟRQ"K1݄ۜqT}kVzu^G=õ}4Ǒݘ3ǼGG\n5{mic5zOlyb*7Bg+^3A.ZOy}u^W>=~,3P:kY~5m:v]". k֊oߗYy=)9{i/HUGu+Lx9,]tTpZtåuuݼ0Arlqs'<ǏGg]1n>hRAٝqon8Br?[%aC/VnMeXU% 0uu[(SNȽ~i'׭֟ԗ#w퇭0CpO<'_%,ϵ.E  -]1jmtZ>CEE<_&oeY;e_'>>qo-|cNwnz^/!yZvpzH>MJ-".Fq9tXe;3!NЋ> -endobj -742 0 obj -<< -/Filter /FlateDecode -/Length 3203 ->> -stream -x[Mϯ(~|q# %(C~^4ꙷV>bVWlXz,*WZ]&>5rRuXz¯~=g9K ;Ir3u|HD5BD%8 w&JGQ[f"!16"jP#I QԡFAj+=BʠIBvF/L+NeP#JuWJɍe蒃g2"U&+% VUaNd A_|`\M:d(>RLDe(LRDKStG&KEdjk$ZFw)0Y.1V2g  t0 -@9%V'= -#ؒ&@lI@I@$])@ARtI]]PqAJ%Jb\oa\@{`\Ca\@P3.H`Ԋ0.H\Rg\ ɸ tqA\"M -M<濾' ] --1.n -2..(2.:aa\_q5ϸ@ya\ XPYuĸ@1cl#FqŁ<e\10.б[za\aPaq t*1.]gc\wXQ# +5wCqA"oȌ . `\ץ|oqA"70 UG - @#e\PX;9%iA"5!lIL#Yu>) fθwud\P1.Ypd\P^ka\P )rf\P= ʢ2"U v=ƸFbd\P#tA7@ tAȸLZa\Ps~ Ve]k*kʸVqX\C3.;M@ Ȃ0. T`)r-"3g]d3.@ Y Z.ذ,qVh%aj&ƸIq*2.@` 2`\vf\6PtIYu] ߬ .t_Ɍ @yϸfKo6=y7#qSfe\d(T]4u$7NLVK¸Ƹi@fLLEfZ&2[ \qag'ԛ#jU陁@M,[XV! x/1y=*p5UdGXXnc| 9j;)?Y4َ`{ -!3hz{p;ؖzc76tv6bFb HWٝe5AנWW:̾ӏ菶eMJŲA|0ߜ\־:`u.QC1Sm2jhkne+jpGXϣ.=Zч,ix.B|qjƇjù; Z*ԇ&ZaD%r5U/e֙c ;%^|EgU،/|/A| 秜?>AR D:@W=}0I,\Ez};Zi(ŶH[3wƼ9\m=ݭ"7|[r~ndB~6!7Bp9<0Oe{4^={ol>I6COnj?ZM[o)?n+2ւVGaדފ7`~%aOBf_">c -GIc1d ޻zT{jPlz7ᐼ#Mw 2 za,pnM􏺱xA8ƻ+E>hjX+QO4sBd4=_Ѵ`2̚ -m8z}#D9Suj>,TY4<.&ѫzUĈOeεooH\%{W<\ςɴ;旿,[T́;U}e0 1WuWhWҝ1k)IM8az݄†}&WZ%݂t^zpY lweruxK.Sٮ^Mau6:Yps[p)RXhdlŽ~9m\L9v=KAlڬ+:󯓜2nx-lW2>ac(ڪ7u&QҪkITy(þ4;i;WNEҾLZLK&kMl8قmX!JqxyU.#>ѫEѴ˱8לteV2fBcr(X5h[Tvt,.Щ l#nJu Z:YFvVC]mwx3[J3֝_5g.VU3 o9=V۳,ELz,?"ءGNFB[PK)/%}+"zٽJ3G%~K/uٞ0NR5߼rǺCzH_d폞7 ,V*8&MziFOc =v)#l} -endstream -endobj -743 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 742 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -744 0 obj -<< -/Filter /FlateDecode -/Length 4971 ->> -stream -x]ˎ云W.`| 6]ʾecP=@ OPCRU>B %Qc -ϗ/5/d 䣻~f CH}a.;ϣfHUdCPNP%ʹ!㼠z)$` dh -0Rt -f1QPEa)hV%a&I3trAPi;QJEdnht/|L&FY;@iIｋ`KJK:[&RAybU Šu芢(Kvp)!uFEkzpu(t\uYe$-?Ip6(xajI`1DlAK `-UőjB\Q[l" -H qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ]{uF ڵkI+ k-r:K\vVZޅ Ыp%.V&*&`uaZ kNA)#qw /q2 wA!N` V+q -  xW' OwuD4Q; Dl@ MQ``5F`` B  I#p[)J\&b" 8ZUy3u:$. Z̥?p$q̀N!hK: [dK\H:%.  YW`\M-H<3J\*J\7LL)` hBO`i-֑1nF b-F Mo -$.H&K\N) o~(qA -MLM|3H\8( hJ߂0;I:[L" <ߌ |$yK`&IEd%.曈lLVFqFq@zVq@{1Zq@|y$.L,W 0Blh SD13> Duђٍd_|G ?RV46 q/GD M WU,]:1\У.0|'b~ŷ^~|/_ϗ?Wo/2J9}>7k_?pw};oWwojOE(i\F9>$F4I==l -S3Gvwޚ}7=wҲZK-Vi5ApjS5/XCKvرqqg hayaR nS٩=ϱ6AܓǡvKoד}1J|6F+Bsc42c4 -!%a]|b((}|hDᳲY|04%'iJǿHiL4}.^2ߠ\ΡdAY3AYaf+:UʟZ/1`2l[q+!cՂϜ>]v M ,6G~.+6+9,H%?Ry8]>]Ԛ3vf1vϸknb\6/QQ> ߽tK_Ajh@așA1((ȟ7\=22Oy+˳3y}ͣk$R~O<Ŋz<O@i ut7<҃쬣Jm,Ƴ꽘8/QV^pY -~tF -kt2..ZuWl"q[F^ax,8Oa6壖>eѧ8Zl)y∼sy _ZX䮳d?i:y,XDžj9ЗlMSJY ](>E+fiٸbw)8/jxܭgOcs3N_ ]<7ߨڨc|qZ?~3^ ƕө>~Z5AZSbOy+/=ceEAWO)㠼%]M׍J_jK_pc_rD-"Eeq4堉_.vDmˉ1 E`Qd7#oóHpZM?6Ӹr6ߕlk1}{NJ!rz٫AOb~Pt){O -lڪNBUĆ=wM盰75=jR"JyZW*kTΨTBӴ~JфάxwQ K% ]tSiTb˚J7Sm /nV0_\;ԾVÍY oG8͵NW(W mWnGҤ4kT᪔'T!㷣V f:$vͥC QI-6vMC*1IUuE]3\ U15P~S2;Znʝ/8jo-|FK1C?Jب:ڵ:a3 čF_xke'~[ٜLqo\0g3G]w7eSq7:#-ߊM'4~Һ:5{I+텮a'6Fۮe܎hȼoڀ=rr+fXtpζ!#Nچthtqî,ɀ+MS0mQf,E!I=ѯv7d/JUK뉱,c6y[ ղl{95ZhA4lSWJE6 . SEVK &?e+͒8jLѤ[RWi2hpTKYc(|JEuڝ5C|LUV)_qI)U+#:׫`&*z!~YnW쯝lݣ 1*h~l XUދ,gKJ<@Xj4T_uǼ@TO]ȯ jcвYC-*X -endstream -endobj -745 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 744 0 R -/Resources 4 0 R -/Annots [ 746 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -746 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 593.554475 101.433071 574.804475 ] -/BS << -/W 0 ->> -/Dest (cb166-1) ->> -endobj -747 0 obj -<< -/Filter /FlateDecode -/Length 4469 ->> -stream -x]K$qׯM|dkX`0];-5_d&HVdUvckM;# ~"b۳weS%E:_~:|2S -YS8[Ci -?)RVdzo5]-%Ru1ŤQfļqKiH#D.R &%i i\#Rk:uh\dh\6Y誺2 Zr -O&IT]$qx2C5.]qAki->; @ii$q` -M5#ƤqArԸ &q ; b5.@O Ad ,U[(HKָ 9Ӹ 9؂AdSȾl\dɦ\4.H!b=j覜@ת.Cg)фPl5.Zjʘ'N4.YҸ ؂qBє2sMga l BgddʌFDh%jMGיYLqTQL4&4.b;h\X:i\fָ gӸfҸ؂ObiqѸ،# 0/y5.(`%2oL-)-H2oIXo4]-%F^of f`^ȼLvx70"3MdހxCB~+38c`@U20^D/Me*֨|8a}[TpH9ML Bv)ϧ~D=OwE0&W`oh~7BH6"n-nl$;_0w[Q|X*c:Z*_`mD_ Ц?Պe] -/&~:PXFWQODrBoֽ,U\r!)@ DoY/Do76uЖ-Oʜ=@!);:Vs5 HC }jep\Ӊa»܍Px`pu (XiDehB\G+?^ճ_un[&u$2*}DPZڰUҶLj?dOLmz_ڽ`kemOnQT@[LvF:OVky; -0r Vig@B>̶;LZ=Ką2GQ.nk~՞86Ry:NqMmG NSˏH\#!p )r5 ]D.#jn?Vy''܉coVeP(-gAA3_/lvwr/cm9ς<avoE~ӡNzw93gܺ1+Q|tq'4>xӡN~:fZyM]; e_meb_eAn~:OyXBӶ -ɷo~\^:φ\,m;II . -ľ'KD[D;GY£_ČwDݶŐĥmz|! Uy:U?*cK>?'9768Ĉέ=VVƅ{{+>t}<3]-Zv@{ӡv)s#Om7Qω䌩w3˻sÏi&|g=XGwԿE{N t^.ϝgi_oa2'=:Xy{J$-إ<|?l}ǀlgQ_WGtb8ZêE{e\Խφ[!*NE=ƍj:G1S{kWpӡ{{;;r޳ì_Gc[bl Xgt^un;uLtDivuRwDjw{mfuٌ嵷FiS}6ޯkO17{{Yg? |2,oRa+-,-r' -^R89$i' idpwT9`WuK.VeCnrLd5$O ZG>lm_۩i?T*lTC{ƟOq>Χ"'ddg剭fgGN[iGRqdb-_s]ft_˺$rB~R>6ULyaTiPK6NrRߙ4a0^srSDZnm-JTUK|7CxEvY1s] /@m&v)$t\aBzngҥ|~fIcBIy_,5HiwsNX4XJpMaVfgm6R2!O$c+ uMVӸR -M5uqhP~ۈMUv{hvql&ũ]*́F1C?NؙzgB )tqѷY\gkc܂>ɴ{949+%z'ˬ˞e%;5n݈e$sA1_m#A]ls/*ZwN5{-iڦ}(ĮAY/<n/["cr͡χ.Vp!o|g$hВq!ťt6f2 e'l?ɡܗi_feU6߅( 0Yiأq_MuQ{Ii16ӥ~s/jmy1|Krm.$F4jk ;*tZE LS)ժ[;ΪR)/AJsbr5lɷ(H8~wldVdQnR%}]M۾k=۠nH왩Uɇv!Rk6@M6ydr#eU:NwHމ 1&YKP oP -T+Qzb[zvOV@(QLT9 f͛- - -endstream -endobj -748 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 747 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -749 0 obj -<< -/Filter /FlateDecode -/Length 4217 ->> -stream -x\Kϯs|_C1"ć i,VIVwJ+^VXvgO)L)5':_ޞޝOkhY&JhXP(.5,@` Ty0aÛa6?lb KaA)EÂR ^&7BT|T V -4,@\~hXP~[<%nkHT,%ʃ,($7N/A_IÂ7(3DE of+IwQ& p&*[moo1>әwE=1ވܪX`/UV ,Hβ$iLgc E=FLXNU;d̒yaAǞc6 W-c?|w%A -}ߞlQ&A~2ݑ`=Z4$ؖ{Ö`it1Z&A~8al;DN\ɃEϩv4^NSAzm΁.l\zvnkk-M$ (+.eCYd>t n|h>$騚ŇCEPA=9vL'҇C:={yܟ%rT?e7kx M97|O -,V,{{bAJ@>s)%'6&Posyq5mHRlI}W>}nDlGAߗL;ͼak}HOe-51̫ -XGMa_vGdJ.o|}~_ - ϬuZG 6zFk5~£y~91'O:, ~yux(Ƽ{;oVQ2@qS'Rt)b}Ϻ;=.s&嫅ޥ>׶>c~iyb_qǮK[mkknmRM^Ӽ>3j?5ۮ6$ /UCgc_$'diVWui]bڬ Oaȴ/[sIO{vȐ}#zYir%Bn9-™!]n!uTqn[f}_m:Vmno4tJsX]է6qM{o4c:˜ù ۹'NtU柎/qD. -[ygq^ ܷy?v]#d8?N!rW rA9|h_a9w;ˢmhjF h\Xgeͮ#oQ}d<$y#8ǘ)G9/DZ{8ĥAm=зX8-qJba>-ֹ{0r|Seǐ8V̵;d/+84C#7vi -B?"KM]Ϙl(9Qg76^KtE;D 㤓ooo݌_lŰbO^y#^.KCHG}E5҅8-a9ӗ_gl؁BۊW~H#<2olGhrD{*%,RvKi7FKَWxIvp$ݩ8;9?WuqJH9{;C>?wH ycI v&wD-k -ag;|%~cۊ˖ߍu-?[Rv`=WyLo͸˒_O3刞䒪U<5&xQ~k0$(O]ӝVsO8]mOBY77Kt;Umxy4'_Bf|wJ Vb`S1kΉL`3?5[l 暢Jrw(˯LJIf'Wɰ1q{m$?>Y#d& h&CkBʮ6WWGjKQhO.+DLH[V2^!JL]f1 ɶsQ Vhty4Ct:'ۢw/'LoeCuz;hAU5 4줐&ۇ&sX#hW{;t9TZ(CWhPܒak[r4"qۍqb$1q/KWB`w8<탣RtplVIꐦGyr9r*tG롱 ULs1H ؒAfX) &9W~ؐqjc䄻1$a;>߉hOf/}Ivd9 N -j9a(Y8C wV]p-;YKqyo \~`WТ$p{~; -endstream -endobj -750 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 749 0 R -/Resources 4 0 R -/Annots [ 751 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -751 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 265.954475 101.433071 247.204475 ] -/BS << -/W 0 ->> -/Dest (cb169-1) ->> -endobj -752 0 obj -<< -/Filter /FlateDecode -/Length 3999 ->> -stream -x\Ko$ϯs|"A F,vhsW{J3#+8^A*>Wnw?&gKNtrnpoqGoJIOEdFU.(M>&KX#ft -G1{VX 1eYbHcA WbVXBUy\4 JO;2x.{I\tRdG%4^,YY(px ʃ,sxxh(<,.Vy&4^ &&Ry<˙yF93TN6)e!K</@NĐtƋL*`5 ؜4 2K OxXCPA_T:Ӏ X)iHd!\YB! ,haASа m ֢aAܒ-NÂ%뒆 18 S*`nvjX8Y 1y `7' p7p7TyaAg1`W 0iX[1jX@]ϖ4, p*/aw}4 z ' `(ch z8Y߃烆x%D+pʙZ%iX}*qBƥT4,]8aA>Y`GD |D.↨a8ga*[5,]װ^Xl`HNC5,H]aA k aʃ,kñU4Uc=Bwk<வhX65,HY5,Qװ 1sҰ  B> قY*P& X -kX=d kX=dAȠa"So5=,05? ȂHQ BaA 7*sYÂ; Kơװo$\ҰbHÂ\ pE="s l 眆! A 3d5,F. UkZ:ﭛcW<ﭛc1rↃnTy;`=r0Y-Gf0%~$}Z/QuBPD!p--mib_1$|U괊6r{"Y8a~EqRVi;^IU"U;RwOv7ɒOE[de}X찢n!:bmnS[n~WzS~= ;/U9߮m>q94uu\kk=5܏9uJs5h{-H+ߊ.5vY9X֠k) 2|gg*'vkZdl|nr$dxOYaϧU#VwͲu9dwl!EĻ@Uhg䝬v7Zpsl;'to1muqvr̺:}&8]#& j{)n\6|nF%3B3v[\+ -hdmvv;3cr$ |ws}j)pʎeI7y=pU ;5%0[NOT?K^npy5kp[5^-`ԃ`Wn(EnqDEnA|L)2p?Y%|ƶR2/:*225kkz[WbClů~ ~n9+B] st[9k\?UIK>7_+_iG(xl)?gr M!\BfMngCs9(>[ni}EIE2l,w}+Y19XJgc,1v&Ne:K{%2EGDz ;R˾A溹^]fcz3g,m'Tfcyi5# M>2'W](r?yJZةf5~?[‹3)YqyEq+:[o'EKN v:'xtC{1Yn˿[B=hX9(x53z׻q;I( wNەl,@wni䰛[dgS#9c[6~8Zv{L})Gylm ׶UE#=>V <),os.ꆿIׇm%opI!#7~},rMٷ˳V>HغC1߮ ,+DL,ƭdyA^.JLMf \4W.؉ωvn=5yMwɳ]>dxd1}n ۍ& 0F*֎Nq2?!z)Y9r7ׁnϚ-~ێc<{2yQ H4b?6x~kuu;Dt fi| \8)SM*\%^.8 +i:\:䧎4am'iފ sMS!ahyF <0yҲG}9 0S„OzZ7kwhz3-hs1DmmI66G4h}dJkbV{L1?Κt%yWY[y-ٜX-{, --ͽ;Fhsvm2hFdjGxYU!VVFC}唀!$LS}.N+$v2τ0N^FΘjUԻ.i -x1sT껳jѻeTQ^$eyONݦRآ -endstream -endobj -753 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 752 0 R -/Resources 4 0 R -/Annots [ 754 0 R 755 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -754 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 606.123057 101.433071 587.373057 ] -/BS << -/W 0 ->> -/Dest (cb172-1) ->> -endobj -755 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 296.981993 101.433071 278.231993 ] -/BS << -/W 0 ->> -/Dest (cb174-1) ->> -endobj -756 0 obj -<< -/Filter /FlateDecode -/Length 4883 ->> -stream -x]K$ׯ|_B^2XcACOi¢e@`QU5-i<# ~d昳WJ)@OZEX]_hʛ?Up~;cs9;7똳U9kO"bQ{ ,UsXGgEA9y1$p۳2İѐĂ&(j- &rV$5*lȋh%s*D2HB>I<,>k#\e:"9_E! -JyHH9 yP}ֆdwXa?%K$һВ(IڡygŤ&T{gwl{Y"Gbً=^XGqaw}8Zn4,t~8?ӷNӞ ~ [bk2}p8h}Zui_S^k7/굮|ez>rD}sҰGOjfBMռ!zZ+b~e^jVŧ^a~LmQ?֡ݤ1g.4kӸT_׺+2ť_?cc=6s)}\Zten2n &_xcL+E\wtT[`q&ŝ#ڜ:Oc4QL-GipuFԽC!j../DFZ]@|Je_6PJXjwHtlݦMekkf?I 9ٴ[S]4]fzn`1ʫe[?tkg#jr:F_Y9+Aђί$%Ғi T7Sic)oh1dø@5͔eg(<8h MΗcrfNPMYgʋ/WMOcwzNtMZ1Zo̷6]of4<KYs" 7,վo]F47gk߻-3Уzs %^&rIl:i)4+LB /]U4~M֐Փ\r j!6L\BCo];_o# ]ҶNF5LZK,|[i u>6f- }C"ec*Q|mͬ0t3lLw]Z]?3y 軷sSpr+d)&esX3=-9H_C<ڷ}W[MNYүY<{2^v0%/qv|Y~guK_w-g ,mjGkiiuss:íLPajr 7y^Y޺HKqU`Aupu~ïQ_r ]ic`a";g0DIJ.#G:v=@h^TCmOlܜBueM*g(}K*e`77 Upbk 60D.w,֘}].R a`yݲԒv e#:,bkp1VEף vXRS9jZE5,qäϞ; "7`3$g $6e,e/~RI\ɒjGS3LM-{(} w|+ˡ}žSL {`Vؐ'5e>J0+j>́LMίy`at2N{LKyU&ڔO€whkS8dbRþ(iykRGH1&D4=[ ?Ŝ^~9|9Z%Rqp|6?t'5?Ev6wŁ&x.=O_;g?-KpXv-]@WaR1zuh=+~ء.)ܤzAvpREgfVG&yV*%շ4x -GT$~ d~+əwȤJi3E|fyRi/j˄pbO$~Xyg.d q$Q2Wb.@(mےX~8hoY~ҭ+O/ D fOke*߻W=wh沣Ql~OSwlc=-]ua4t"^Nmo"՚jڅhn*wo%P't9 įtk0?3e!fHVN ]Nbښ3{4!0ue:Eۅmf2 s';PоLtSAoXo*|2/ICjtkJ顣IfGE1v3]c+ꤲsAǚlu2CXOʙn}7yRwd;ȡcL} ۝l/ec-M?Nۍ& 0F -֎N^:^Nߟ6ggveBo':W{ʲ[vl]睌$P/hiA6i>n4쭤j:w&Élf e|܌ {tmp8.|Iy8LƖ|[:dad;gi -}MnhlsӍVF1 拹a2sy% 罊 -`jN}}`L'S] ˾縒Chwh妵纓3p-hu1DMZ-NVhzj2$j)vbP5YJ]Ynx[r91:=Jv_2 0T%]um=Oà!HS_#j?%3bx?dG^!įTunN;{2N-t4?"SS e-1sWB`Iȡ"ޱӛŵQ/)i N|\Pʣ -endstream -endobj -757 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 756 0 R -/Resources 4 0 R -/Annots [ 758 0 R 759 0 R 760 0 R 761 0 R 762 0 R 763 0 R 764 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -758 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 713.673057 101.433071 694.923057 ] -/BS << -/W 0 ->> -/Dest (cb176-1) ->> -endobj -759 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 373.781993 101.433071 355.031993 ] -/BS << -/W 0 ->> -/Dest (cb179-1) ->> -endobj -760 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 354.834971 99.933071 336.084971 ] -/BS << -/W 0 ->> -/Dest (cb179-2) ->> -endobj -761 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 335.887950 99.933071 317.137950 ] -/BS << -/W 0 ->> -/Dest (cb179-3) ->> -endobj -762 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 279.046885 99.933071 260.296885 ] -/BS << -/W 0 ->> -/Dest (cb179-4) ->> -endobj -763 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 260.099864 99.933071 241.349864 ] -/BS << -/W 0 ->> -/Dest (cb179-5) ->> -endobj -764 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 199.152842 101.433071 180.402842 ] -/BS << -/W 0 ->> -/Dest (cb180-1) ->> -endobj -765 0 obj -<< -/Filter /FlateDecode -/Length 4700 ->> -stream -x\[$7n~_ X$,, y00nEp|T.Užl2gN EQ)]L\RO'2)#~S8[d-1Bɤ\=Onس3Dg/oboRN*` -+ QaEk0R4Y bpAcA v.+ 1<'돬1\ -!),K:"A;gPzxΚ+*/gxޛ1BV,3i<>'!Tdq9y vː֕UdHVoB*G9#Q0!{OZ`^aEabRxD -EAi<Y?8|YYNV'o5^,%Vy!R +.iR2\k 79k(r1``8' x,BUyְ;ȂxY{ <Жa-x-Sx-x.$ <x@.LhXةab' ; ׀eiBwb5p( "pWܦ1 e A4,MI)jX OEaA" KANakS|$Ys$Y2hX[@?`ȂHQ ɅYÂ"cЪƋVy<4,H \հ{)5, 4,Yְ Ȃa\ƳAtV A eFҰ{IZ1>3kX9 5,2NH `B̏l`mʃ,>9;nf r,Mo& -AD|Fd iXPl~ӱXOob7!K@ [`@'!+aAQYo"W7z\ Ȥ񀻈Lx~'oHtfgVO [#[%̀GR &v9p`ZR x>GT3sA, FtRl9˟N_=N~SOڏ{v/9v|Lmf!(쳬TTIHei뱛 g [ - Ejp7c`1[>>_ I;${m)MjB #]Suf~4YeEpČEW^yw>~8 -y\wpB Z5IO .?x?@ >-\D؀|e+31/]o"KYZZ'^Zo?M_KO2M7yc,~k[d÷i̚nVq}0k]!"_leV>P:Oܝz*eUJ\g5z`'[|hJ>.rۉ^BzxhMp:%GL1:m|s'&Αp-I!/OYa}Z:q|Ѥ6.zVd{rSy?}_=.uϛEO_oenl|sr+6e ]:'a:CDAip1"8_Z/!tcLw5y8cl'DT=n?| Ӧ.K_7Ldo3g16^Zm {X44üt::?Z1R=B7yWxjlʺj[Y޶wuR9{ ifP4o-aF.)كuDE d%,h~0 D䰶'+m L{;. oOfrW`uJ;429-&2Q%t6%u/WjK8`_d".m3h>I 6 !M!d}Ԕk[S3L]RoO;ʐ"BN>+aM/j8 5|SPa#7 ]dI\Oocu{B -#-n:Xʛ'}T-2MɺYv_+0&浚Q}o4gkR2N]UWL1`͊ $ )>X)Y,2[IA1ck;wV)m.8R@&Mt˱ǒ. 캻݆=6Gկѭޜu}&z<1YiWj(g/Ws4.׉6yI}ٞ]eƟF2uR(ui-3;)$oBTT4峬r^yieenwuM_&[-[Y!4Q1e'~}ݲ;췭1i>㕵aꋶksSκMcaŞϸːŶ9{chƋ"& 햽voy˷{aKw)2+e_?#[ΑH6ulym|)IqU=ư}edk î8mzNyXaMMl}Y2[1S_esMnne^YR2ymlU=_YaS/%D{a-SOr13 Jή= I^A -yx;d!.'+Q׾֏ËՄF#C&_ fj|rұBDhd=5^֧E h粣Q.zHAvڇ8]YuvV֥i:o/'tw*/jM5:4? U:5}BϓBWԚfLfO&`XrSHZnm-JTUKe] -2EIK8,Okʓݸr類a`fz3Ovra/Ϫ*,F/ TN,wPщN*iǎ:i@r쁊S6;K9~,/Kwm&z*M<[VaM?+g"5! n3wd;ȱcLN}ƭQ۝l/ձ,['{Dy{%Iޒ>EyϧNnH9Fo'>S{#up[7ٓdyb#e3O?6YCMxͣ: `o%mGP۹31 NdMW84n/;-@sf8ѷ/hRaSxånQ{Wc[Bީ3Ltq}m |rofyT[ SnMQtLqRGU-S gMyV<+PVmGK@a64FGd%BsNQ7ڱoݼyALiT /+kG}Vԓ;%wZj1CX,8OG%O׹}vr> -endobj -767 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 653.523057 101.433071 634.773057 ] -/BS << -/W 0 ->> -/Dest (cb182-1) ->> -endobj -768 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.576036 99.933071 615.826036 ] -/BS << -/W 0 ->> -/Dest (cb182-2) ->> -endobj -769 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 615.629014 99.933071 596.879014 ] -/BS << -/W 0 ->> -/Dest (cb182-3) ->> -endobj -770 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 558.787950 99.933071 540.037950 ] -/BS << -/W 0 ->> -/Dest (cb182-4) ->> -endobj -771 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 539.840928 99.933071 521.090928 ] -/BS << -/W 0 ->> -/Dest (cb182-5) ->> -endobj -772 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 478.893907 101.433071 460.143907 ] -/BS << -/W 0 ->> -/Dest (cb183-1) ->> -endobj -773 0 obj -<< -/Filter /FlateDecode -/Length 2689 ->> -stream -xMo$+ltU F!a=X0fs̼+$5fVq/=~󮔚]_{®;~rx좯ˇ&r!mïZ?m%ZS2u,*T╨bt9*y!T0#f 0jL3,BTfeϪ -3BT0ט A`i :]¤' ޥRC ρT]gRJ0X3]-ћ Ӓ.M*T[BtN%[ -I♮Q]NJ.Ϻ Ţ*L罋؛Ju(,RD`KXDt -[ LNDͥo ͻU3]-!d:؂g HN  ׸rvV1ΊFPa ,8 @DKash5  TaK0e,Pְ[ 5@[ X d -b+Usd,P@ ՘cj%1(慱]U:؂ X::E U/]Q`,:XB)X`n(b#것*c!bwCX`n Q#4w2༇.(c^Ƃ4h| `:1o1ΧT "J " |0D ]0DpqCd,vpc7[ꪓZ -cAwXSII.;l$X;AX] U +`X:-iNHtx0Ӂ"2$p)7A(0! -9'ƂT:|Tʑ Ȣ:b X0[4Ƃ` BDzD4=-.4?0؂H$s1䘐aV.W2pMu: r63 rNX.1 1 -[*8\ ٌ̙t󞱠؂h,3 cNh䒘j3iyfa,(\  &4AJ-c֧%ۑM9T[4cA)$0`o|33T- $d`:Ƃ `˖oƂ|)۪囙lQ ho$䛠%1ԔZY f DDOJ73.wcEd P@Ȗƌ+K8 17lW@ߖ#K̲$zkcJ/@_cĄiJgfmnaG1'c}n_7eۗ ~pa_5RKv5a_^ ٫H,3'֞QF,,#7o &foxF-=~ʩGz+g?>NٮGyQǟ/?;s w<ǘӺiijݙ^^o`Kq/^/˸.6s\s左=>2%[oX}c-\^()MkupϨƐSw~zpQݑq+C=yl/g;2u\6muoٗQiق-ҟ~VssG~Oj!elwӶ.B2k}-O>Z'Zlz|Ry?lLGmkF8Og|.AvptLh^?8=Ki |u g{Et7=%kcש!/[}ި]WEHeU4cAl]7"Z 9˪lԫ]7Z|[+G2>Ӕյ'}Nin&.>"ũ@_kDs߄'uCoO3'+$ -uyeJSv*6{:O*O:f[u9=Η/B7c˔-\y Rb?v7\ҍ@wSV݉q*6{,e)NUNJv0]|^mlN)N8m?P"}].|_6Q9d" މד}Z>S>60؂)e֍}7s<6{AЮ8puef,@揮<mx -u8(y$_WԪ#Z KC֗tXewf v2oRhk),aD+ -B`] ͯ;{_^xOS&h*k<.սK+t34ޥrk -]e6;+ĵS벻NA1ptxc6Y}ąR1Ŕt\WeLb\W%=m'ވt@qyNfK"Kk!YSoﻟe6 I32,>"}mn!Xߌ2oqPtg2))!>V~wp*ٷ &ܠX^e7B&Wv|D[ L[[ڧYe~ ~ -e?>56> -endstream -endobj -774 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 773 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -775 0 obj -<< -/Filter /FlateDecode -/Length 4239 ->> -stream -x\K$G3ȗd#qk "-|U3wGx|SULn)ˇ-9#~s<;DWSBy5Ώ'wu??}/&ÒK V\0X1.9 Vr Xł1#+C %Z,U F‘U!ώ-p5fr8Od 1o\\,wK*Ws[EgR1dŋ%:fxC/AJp=dYdEX0Qsff?=(A -}?k"?\^`kb;hIx㞎4!Z+Vȏ' H1s:MLsI+yTԹ9Ԏ/0G=&@%c[Hw{o2ije;D C75,-RFTjUJjvp{TϽ-; i:,c:'ۦBd)*h}Miz˘N %Ӆu.zN5c)p'+; 3'LMS} -X%//>%^R޳?ߧ|/ >3^r>S%)'%p?ULK+ⓗ孪|Mە~=|ωڝ7DX,Ϙݗ'иyylLwf,+-3mI"m_t][c9.%E/!ڿclAMSnim/s&krj,^*XL!WziY\dlNI FfsF1m~}}'uu7uܒ#䠹X‹LD`5nzYt/t߸I[4ei1ևot+;UDۺ_a?*qg N]͟\ z~|^BIq7-]gjƆMB>Kænt'>s3XʷO8zv#.!.lx}=&|oMoo|6qx/sVz|rM}Ń<WXOiYw\BH>ދg>r7:d3ow>a?'iߧ7(NLV]:qt!ϜH8΋\s-_U:4:Gw eW+YTwϗՙV6gO9]+Dxq=a;xJkyqٓ<0_u-7jr3iwZ-Z9z z;G-Άn,|ik&C79R;ڮ=d _~4Ø&OGlhUf5?EPAS,VS1Bݓaؚ ^NG$Nr:N]Ow M\&+TAi_՜DbsJ4P- 8γRy֗+dvT2Eϵ' 5cOvY g`&RMr#O9Hc䔻1$ŝa;U>߉5Y\I&d8(LF:I^ֿ vS|^Gg]o?wu4lݑN&o+w q8F=+؟dWfؽa+ٝ&n \MSzf J#z0Mtp2yang5$e:BK5aԓ ՋMd.u sCwZ[j8 =0;=icvDN=:}P5u,Lljhi9$ڃwjhT셑И.*jݶQOʝo.@N#.SںuSKytVJ*V;ȖHv> -endobj -777 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 488.554475 101.433071 469.804475 ] -/BS << -/W 0 ->> -/Dest (cb185-1) ->> -endobj -778 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 427.607453 101.433071 408.857453 ] -/BS << -/W 0 ->> -/Dest (cb186-1) ->> -endobj -779 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 115.110432 101.433071 96.360432 ] -/BS << -/W 0 ->> -/Dest (cb188-1) ->> -endobj -780 0 obj -<< -/Filter /FlateDecode -/Length 3952 ->> -stream -x\K$ ˒HÇ b99;6QUzT1:AtzPdW;Z~'39xzwx&bsQYN&s8%J)sv97<ÿ}ћRw[a1SAa#Iɇ3Xb) bĞ1䠱 {VўU O5p%$,pZA,3y炉Pzxޙ/*/xD&&vibb!k<,Xd j<”Ƌ"YY|NdNQxʃ,6Z -P2+ٜm0!Y MRy(lRL -ChCQy% W'odiYO 6_C!MQx\0dx@g29k(s1i0K0Kp; BQCr*Pa C4аx& h˰ p˶8 xE  1ĥY”%`Ѕ' K!z K%vVʃ,0` \& K&  7`W 0jX[1>gaw}aw} KNnkX]>jXC1F]@Hհ=x4,`#,Ѱ w]4ʸ\2O4-l\EÂAE.3kX78Q':_!hXs08ߌ0]W-9kX%aNac3D%CrEaAx/D DDe=*P n4Uc=Bwk<வhXrljX|ְD^ÂٔXhp4,HRykX*YÂ! yaA!Lq\! "E d&f RǠU p2x.iXNR&5, 4,9ְ WѰGsAtsNÂ! A 2հ'4rIZ㱕<3kX9 5, R<а#vаM9*P` rnf r,z `o& ,4,(6 5,ge䛞5,_J5,(do"SP|3iXP(* h*o4^,%F73o"WKYͤ 4pi԰7jLgf8Z1ހU-X`/N ,Wr$h1YV pZ6_cÄ4"!IY]h~ǟsxVگGI/n1L^=גm97n+0B.EQUI% ^ܶ2j|S:* :;gW<{guA^y}}^\֘[=Nu :lbD#m#x/}~8|%:6dkqDX>}t "ׯک^…ؽbSeDY[* G*^5HaD6~(tȄJmU_>)Lps(k/ʫy'j8GVr6%$2]{3>oyܮU/~o1[yI6;̧EuR5Ȩ.6"bhrjuEǤ^E*0g֝`.f ۫6gAb7&_mEhb'fDvgnsہF$,ɓ+Ւ\ū+v5 |}醾%V+VY6Oc:OX|dc-{s/qJ_|Y߷ -ޯu O [,3iKT@ґKk.QF&ugO|Po}p)AOFX~qBīȧg - >6sxF9^ -r[l$lRytgOƀOX y^i;3W?m'Vrbwן՟ܻx?Sh2L=Ԡ#ןY>Pi~;gʣ?/\?U^zJM@^mEK xKqV_BsI;~W}) -5W1mޚ'񓮭\]Ej07^Wٳ/g?ʵ5w[iV]yO u{ȭq:UpWo6uagM[^ov/ 1DGLwtf>v_ѝqM0MG=1B \6:Q6hIA4h}dkj)bP5]J ][x=ZٜX-{,Z{w*hy;w;m2xGdjGk,{ho> -endobj -782 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 770.673057 101.433071 751.923057 ] -/BS << -/W 0 ->> -/Dest (cb189-1) ->> -endobj -783 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 458.176036 101.433071 439.426036 ] -/BS << -/W 0 ->> -/Dest (cb191-1) ->> -endobj -784 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 397.229014 101.433071 378.479014 ] -/BS << -/W 0 ->> -/Dest (cb192-1) ->> -endobj -785 0 obj -<< -/Filter /FlateDecode -/Length 4580 ->> -stream -x\Kȍȳ ǃ ; nx=tew0jCTjjl+Eƃ )UR/?\^_i(?779$ .r˹qus*`+ȩb^`eq{A`Ĝ%,YbPN^bA 6 1E 1l4$ > -,!Z<xƫg -),"x&Z -7/O H<Y!KQ"ċB;Y%J"蠍ND^O<9-QD< -%hEdN[ G') jٻvFybm$YYt 㒄6FEْ69E6eE1: lB8mF! !3"L8 Y@ %'aE%xK bj ץ@8@.L)KX)aݣ|8$,p]GFKX@]SA@GLrp%, .JX]U alEٔܵIܵGȋ ->$, XtrwVZAh1B@8N , J`Uk3Q‚I(6 R N/a^q$aϐ1C8T%,%,@ 1$ Y JXlB8KB4I‚DAq(a&RANH~l"yy %f %bf kȂO‚0Y8xZKXMBiI%I‚4Mxf8ߌd,!ȃ,$@' $aA$a 䛈Œ@|3@&Ed$,MDRn>">3$V 4lK؋*5 I,@Ld)U`- 40a>%s83SEf!9h4[c嗟q^_JY10~Gk.b3pp|o"]I闛t8"(~1wBm&o >mB^oC3QFԄކ嚾֡SЮ>6~iPPE ;ʢ?/3cȋX:ọϐ˯+0\ o<ЌNy7բȩ_m?*xwb?fCL 'Ocֹ|k9h~^c}y>l"nlz% O,-K0Uf-9\P h%ͤegE FϏA-ן믛l -Nĉֶm.lͺmnnIwrbHeъMdoQ˱^԰fAĿ}8*}u=ۺzd ovY}[fcO5 f2cmgxMaxrkW4gIv6uaԼF6N%yh7,Q eGrtO=Rv] ?4!.p[N"g]b*{iYzNSxϕ.Kw lqۼ]G^>nȅn7^vX7.G4ծuFOȰȂxHWd{'2#.( u 1?__uy[>1myaޜhcXKx=G1Ƀ_1iiW4{e}:Sm2£"ߡ-S_iҷ΢X% Awcʫ i|1V m"W첆vR7-áv}FtGLӦ0yk_6J>ҰNxx16h~x7z4LkmyHo~X8v(Rq^.vʄRX=];P|F›`g*'7U@@Ǐ0-u}>~p*p~&柳V:~)=0}>Zq;}mR67* 5\bݵJqcmn_q+p;|yĉ{?Xg3GcjĐkl8wgy!6+Õ6)zM_ߊ&(MR9o'4,yw;Yyst&2­A6n#?;KBGpgyhf,?({ly|4+]߷54ml5;af5۹~&9ڙuuC\Μ-a[O(Č>ժ=My{Σ;V8Ōg3}> @ǵhu9[q69Pܖp\G~뗅o^)p5S'AG~/G7g՚Uŵ۞_>lLߚk_u C\GP#^6k~Jd|f<ŶX}blw9t -C;5+3={ -WO$)\e mʗMyaIoR\_NڑifNzj0o o/ .jʆ1hlk&;{ \|Z7ӛn215U_S>&/rWcN^+i:$iPm'u2I t{뮱uRD cM6:!cLML7Ⱦˊ'NorY-?LQm/t}{r#oێ+|+ I2LDKIoqk']`o-MGPӹ3NdM7io-@8KiIy9LƑ|7G:d4ad'gi -sMSnhЍVV15Ay`2y% G{94`jN}}aL'S] ~Ssޡ>| g-hu1DM[mIVhj$j)bP6kϻҕ] > -endobj -787 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb194-1) ->> -endobj -788 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 736.726036 101.433071 717.976036 ] -/BS << -/W 0 ->> -/Dest (cb195-1) ->> -endobj -789 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 409.229014 101.433071 390.479014 ] -/BS << -/W 0 ->> -/Dest (cb197-1) ->> -endobj -790 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 348.281993 101.433071 329.531993 ] -/BS << -/W 0 ->> -/Dest (cb198-1) ->> -endobj -791 0 obj -<< -/Filter /FlateDecode -/Length 4809 ->> -stream -x]ˮ$qWZadcX0]+10¿C&̨- /oef[_~~'^bL嗋ZSSJl.U+ -Gw9 lXBr& .y?u,)y_b VP9`T^/Ŕ$p UfPNR 2& -3,m3L$`N.*`6J:t-Nd `$ti޻(si"%` $-[%`J[ ]-@WuEy%]KH%T q3-.Z$֋6Ì l%Q[UFYBt gCl5yv[esŘ@`%0% - Z2/I`BX(HDP(iD&| -X3Z"`#/1հ0sEl$.CV %E %|KJ{ ,f* ,FOXP.$.\ t1݃k7XЮ%.]KZI\@]kQSXbuxj$. .^`e11* k" kQA+qw-H+7x8e$. !%.P.(lJ\:c%.@cAX"qO`E%.p]1|.-:¼}wPY x%./XQ-VjI&) xqpX4 -Z.-*(qX$.,d(ġx.$q*ga-6 @i+i2` -IU#,J$qeSD `(H\#-)/qO -:|/ve:B$.@`$k  "XF-p-%.-1I\G>J:o@ע.B!ЂXK\\j.I\3$qAHSE,EK4%-%.@ D[ J\MDXKՒT3CE 0Mi)ElMH\ɶM9XGhr%.e$.6s$.H - ⓸ )0Y8tJI\tDiH˜oF U7 6Y qA":؂) |$$1:߯~=Wۊ$m -I:S9B.e7a6G''|GbrQ&y073O}b}/;5o㮟~o1/Dj?h\wQL\XDt۶ʛ܇a[_Ru ;}j8ltr?8|_?t-Jrbo)=ݹ*߂R::TMCHM^lhu׫7g&6[H.vx1 -MOzf7m Z5 J9p<:JmIDvV2 -!RTl}-ѽo}]gјUmF-oBTCrsu^tțem_~^.MyG޽z^X^fr7`+-v*;E0 C.WG>W|h69 -z9/Qi߷̨$\N!ri7h;~:hkvD':O_Fo!t.#հS%h!ROy5jCěAqeOfDl딨 <ǟ<*򙻴:Ϛ>:͝) +]$B\n!\C⃘(Qq HGUedo+)nf.#lަ8t꿴fgms#>4M1cΉ~;=[iS:(O+8x]Q?WF8VQz{C+*L\MukI6bn[m3G>K&5e>FHoW[Giޟ(|$Ny58~u˲vٚjۭo,<~My:Yt+}y$2žB_ѬgyUuˡ8|}/̧W'ޥ=Yu[/{S'zl7mj*'9X?Q<0YA{ʇOħYCۅw@[)uÞokgw|~!\Cqv˱߲~i1Stzە.ղǦ;Hu'<8a;xmGBO'kzݓ͂o}=(cZe'<-OxǨqzGI:~ҟLZY-3,h=!zƾONGj&; -e]1GN>o۵FZd]>O~WY)G;VzjiG[ѻ>ڵ}=l(eBO9sG]>G~xUxy{n"Djye!6[e_/};oS{h垏jK}<)`[>-#\Ih`bYﷴY߈m(eT_1>vbv6u"gcwu;Ng8̯2y5K3-nZ?GŰ+mmص|Їa!=DWخOMLmUc*׷wۨZ>z}6}z?ou/6}Zm׀ӫqИ3wUm2Wa瑟{}ݥܶYwjNU] m7j]2ݧ,+'fry_Ϭgڻuġvm1g츶>p|ܙ+Z_w y1 <7̻cΎv5i]7^}]U'm>9|ϹG~8O#ьE4Demfc>YL|\};&|ki΁/Pyխ,;uvR>e갅b2ҺQaNzTLD\0^L|$z'Ȼ Si>;*G/dP~:D} $h I%ێ;Oڼ]88~Fn6>ޔOґ[Wע'̍ oAR>i괌=Gx:=ٓu^dl`?#쫷2=s+wϒ8@Lv|DbYt?,/ڗ߯zh2(*K .;5yR_O'>Z2?_t: 8UcY Dc8 G"wܚ6 KKbql~Z|LVȖb֎!jzW|m\l *&t{b fGu!si6 l8 (iwq7eF.ud$nAjM٨Val@^.rv\KQ55Ss|_vc[!戲VwUXpcvQCP PA -kxfÜ+U.S>hI]u:$y@Set_:*|&^{l#e.cy:ylź35tBՌ@wC:nNקS3]ow}ί\|^0߄,Џ!6v3&x"nSh8&.eXgr·K_e~d:nTg ӹu#+Y>Z<ƛO&4hue]CC_Ǎa|MJΠk 252ϸmbdulƂ^vssUස8tv,W$rѱCKUo4,ۘ; -b,ȗvh,&+w 7Lw6Fxz}W}YکKri,'Km˾ؒ;<۲l䌩1B \p2ij;&tN&-f՚[GKC'iG;Q񻲹ݶhq8qwjddR%mmm۠aܮ#sg3BHOq牅tƖEE!OVuN;$mXZtvdB+XS?⑫%%sͩPf] !?W9LտaR~6),\ -endstream -endobj -792 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 791 0 R -/Resources 4 0 R -/Annots [ 793 0 R 794 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -793 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 228.873057 101.433071 210.123057 ] -/BS << -/W 0 ->> -/Dest (cb201-1) ->> -endobj -794 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 167.926036 101.433071 149.176036 ] -/BS << -/W 0 ->> -/Dest (cb202-1) ->> -endobj -795 0 obj -<< -/Filter /FlateDecode -/Length 4072 ->> -stream -x\K ϯs`A FA[6U9|zt7gvvrhi,wy_fgr.)dM -jEe)d+1{!P2vss׶;{SJ.AXL&lPX,Ha`R!* XƂ!#+A .9h,g!qrtdc1\ Ia9 9VAL^`"5w&K5]pc!K(iYc0"dHVAiY` Z` 죆0j6=,X a3i -Ÿ@+r>WKивq1 p4,]gְoQZw/VÂE4,9@7,LWcK.`kX(lld`HNC5,]aA@aAZFڣ eaඊO#Y5)4p:Z+aSÂೆ ̦5,łOEaA @ʃ,X$֦P$Y{ ,H4,@F`C Y)jX$30kXBD=jMNksI ; PK װo$]ҰbXÂT \E"=2s l 眆CddQeFa"4jIZ㱕:3kX9I5,R<а#vаM9*P` rRnf r,z `Ro& ,4,(6I5,geԛ5,_J5,(dQoSPz3iXP(* i*Po4^,%F7H3Po"WԛI=.dx]dQ\Df3ꉁV{zf`R#e*Ϊ|>GT3sE#5hFW-c?x-'RXK%.o1*L$^HGHe롛Pp[ۊ Efd7Tp+OB13D}^\>/.k3jYyU!kt$G!>7'WrD7O_|͟o7N~ 6^/o%i67=Xyi {BnW-[?~m2V:,?o^ߥ2۶,4]EsCYbv!̪ ~jM];lo5V5=ؗEuuq^X/#@YEWXT)D ƩkUX|KaZEתlr@-9Xes]b˞UUL!Ylc뵏}ҧ5mcofGM]MtAT7=o]URK;vWWvOy tn> _p%^-y{~?ʍ6?o"ױnmsM2f}m W۵M6s >& -qֿ=nzZŽv7{F7q$x ʳ+Op}ZB$ -\rUǒ`{lng;ň>JÇnqU5 k)͞ou6-Ӥouf_.UIw^StFv:[r'-MMiTsr'VrC%H]651s>ϪTx9Zz /GQ[2ʎ}AmE5QS(W^:Uk5Va K4M݄-PWb1mueh ^T`+ATG]3 #R+BsǛtgƀX].>ـAī{ٸb ݐZb"&Li'o3ƻFв jUޱ&ܠMZwf:1;| ʧaKn4ikmIFkͭ'*r;%+E}7QuOcΖw޶LJcsώN*vcF9a";m5[?n,E_0t‹,ǩVy=0w=nz)o ;wu{c;aӼ_˟F(c~' t^WN"؋:B7 lM]c{ ?Ӄz;!S[[znmӻ@osWm̢?+q䥱c Q͘n u4_bt0T7i6^~5O;5u[F4原k\~^O%NR5 5*AK\6|s<͡D>f}VP y38 \R&GgDZ/q/Llw=A7Jz ++)~>U_{ 1K y6ya{ vjmF~n&y6թۮcc6;FTxm*ڝoF֗?%/oROku#-m%g.$X!3YGbp]N\-)~QZrfJvd'b84 {n8y.b}Vi[ ҞR6TӮFPSCk7>)I!mhfvkbB͐+BvhTZ()w+˔&G,[$h}mSp -IiVLo&4n'g;ePSnk6<//P:U~pMJ^mWcN*iǎ:iqm'ur*t{뮱 uRDO' cKv:Y cLML7ȡÆ< UE7{r0Sq')uy76ޓsdnL6`A0P[;:w/ɴ{9taS@$'Y;m^'>qo;ZKd҆Fn3=O?.YCOxͣZsgb:Ⱦw4i& ^vZ%a7TN'$d a&'_[Fy1 վLV)+{p{k__&)kH,߮?7oP -endstream -endobj -796 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 795 0 R -/Resources 4 0 R -/Annots [ 797 0 R 798 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -797 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 582.273057 101.433071 563.523057 ] -/BS << -/W 0 ->> -/Dest (cb204-1) ->> -endobj -798 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 521.326036 101.433071 502.576036 ] -/BS << -/W 0 ->> -/Dest (cb205-1) ->> -endobj -799 0 obj -<< -/Filter /FlateDecode -/Length 4101 ->> -stream -x\K#W4*Ç1bdֲF0`C~juIuRWQ,z[hɹӻ5)X-6-^)d+1;!P2..揇mw]8򣰘L)٠ -X֑ -CTX,1Bb{V\rX -+C h*' brr8oʃ sD(=j'x xh( Y`]YAxL(YlNy6s&<(lRL -ChCQy% O't%d>ʃ,| |,6E p>%ų>YCH_Xdxi@@, ְx5,]G|.↠a8ga*[rְ wK^xac3D%CrEaA½ "p" "p2Y({ ׀ciz Zx]kSѰ wmjX|ְD^ÂٔXhp4,HRykX*YÂ! yaA!Lq\! "E d&f RǠU p2x.iXbar)q5, 4,9ְ Ȃa\sAtsNÂ! A 2հ$TJ5, R<а#vаM9*P` rnf r,z `o& ,4,(6 5,ge䛞5,|3kXP"DBQͤaAa<Ȃ(|"d5,(1J5,@|ZȒo&\ Ȥ񀻈L@V-7$g:3KƙՊVd`VIXHjb"QZ6_cÄsi-QECIYp,9f3\o|?Z)Okbs/o12L^H_GHe -&Bݖ"Cb!+ͼH*SG1C@v^z]WwyuYIrD䲖B>IH| bͿϫ+tͿϫD*g[3՝}^]>/+^|CTWJp}|.k<<7&2U;d1Z8Uyl_++5Uq޶9*/c|S»Og/ q"`RU#U%_0YϪ1׿_&* r3'&r:Wv~ބ"E5nm2uH]lIW]gJ{U_I=S0\j&_xrӀbRvırN-#%!kژm:V^y/1/~lk"]ƾxrۼĜiEi^.]Ťug=ܥt7>~ '^}hf+3\9xqnR?.Kb{Q-59q=!V~ߟS?1U_t5h1D?; -w7==nqiWD$ܣfZ\k҆3Z k7m-hS#b \VwUӧ[Q'ς%:MYlj$zȝ5q6P!59\F=plrUD -f[oܟ,.Tޥ}=, EPh<L'oƺt͜2L${3ơriY::S/گgFn; FI=VŅ n tgśq) [^-f_#+{tSikg.xܽV_3T*R*;}]b59bO`xKOq;>@Űcs uhUÆ!=*a&7wV;)"ӭi% ]q),+*7hsg*mgWLokK>jBTV9hwWVG| _YN_B熳HY_ἻzgOƀ1ykWVUVsrd*feu;ʪd XgWm*[UV{슚۟|W?`iϫǮdq34j]Zi6{v9JoIV#}Ysz+;yYUZVm5^߳,wzHKutwYmg)=$ \;25E z1U!9JeIZ馗浲@?ՉlBC~E+ Zh-=n"O?fc a>#myyHFYymsUxgU+ʳ$_X.Zu䮋Oc}Vrb>BfG G;b7Nɔ˖pt}0"Q?nr>ވ-"zF'q,gC*QB28pv|.İ'eI;2\ngꢯsn]%Q#}]oʠrl}RHB9ˮɃNgbģ]頶kSiʳk隟LS<NM?nkĎnx: (:LJeAvˤUi0Vr?Hy4{:|nSR"15rx?~^lݐWO&?Z$ˏt86 l5 ?< 콥w%ÅzGf B#н|I}q䉹..2OM|\ĕ4.\KG\rL6bA Ջn\F%MO7iuK^['-y_|>xߛȱhǕ:&x:e^CZG#șGcXmt٭5iIp1b2֭8ZJ#ԟWMuWú+qVoDK4s%BkAْ:m?7o, qFvv /¿(Upy?fsHRɳܮ+$v΄0LdEx> -endobj -801 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 698.673057 101.433071 679.923057 ] -/BS << -/W 0 ->> -/Dest (cb207-1) ->> -endobj -802 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 637.726036 101.433071 618.976036 ] -/BS << -/W 0 ->> -/Dest (cb208-1) ->> -endobj -803 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 295.229014 101.433071 276.479014 ] -/BS << -/W 0 ->> -/Dest (cb210-1) ->> -endobj -804 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 234.281993 101.433071 215.531993 ] -/BS << -/W 0 ->> -/Dest (cb211-1) ->> -endobj -805 0 obj -<< -/Filter /FlateDecode -/Length 4920 ->> -stream -x]K$qׯM|  Ȑְ``S3-_JfdVv.AoUF$?~`fUSt|墖)VYGwՊt]f KH}eG_͒7]UdCPNP%ʹ%㼠zAST02UA):I3Ș("̰ݪ0A: (%`"FixttF/>&D]N#]| KEIG%%-N)I[ ):I\%` l[1[2H\`I޷ESLD$qApzUyu:$.,ZRKĤ$q̀N!L -3tɖ.tZK\ l7(qA4QW`F,t8ΌD ` S:M9XGh8܌[2o -$.H/&K\N) 7 I\yf Yx!0oo E8MI$ě`'IaI$qA(q ě-f .$x7JLVF8c@keXg@#0eU( m84nQy!`͌0-}9z2??]~]^w? [XO&aWK.a60#y؈X6H,Xnӵ}ka1۬Ѫ^ -ceh|'[{q~=X~=J^du偑^Bc=;%txߍX 7ߧ/Ow'hN Y To駱< -xZE# QJHG/w9W~bBI)\f6QKZCj9YK:)oIuUr{_6M C.r4) =b/Mw}~TvkS]ihEɯPԦ2jCw؜BahPwiG]_}z -rJ >HC$K)NvF c[Ɖqanr+_.{O=hѺׁLin,S1שqRs˿tOnŐ0c\coo綿x -8:݊f1{?g*c(ryoe/gʍ:a4n&| /65;;ӗRVں¶x6AC?,̆D:6}~){4|[1w4} 5z!8hBR(m2!([v0zvkF?بpwμTgȖk VoOVS:4¡KՆzvڀAlmpl $y{rovy@(:D EN Vl-!f]qR]k\u܏v8wG6ئσ夌 ޲zQ ^ݎlܼm$M7UGvd}09Z#do 7e'>97&ͩW5Mr[u,k;2۵^8m}8+z =N1yu;B=bγ7wY1\qBh,ٿ\ zd76jіx2ϓ1s9(^ϲrXM&Sc[pEX;|~.^1YAuT)Gt2ϓ X{K,lb^_g'͟y>裍{84_[ɽLh4g2_e[#lXme0\w3 /5>A$ >F޹<φ<9hFC)g$:<+UuQa mRӚ'03PU%fډ^7g4Cgެ͌Syb/ǏŘU;FdgCaxg>j-"vS hD5?_%+uY#٬˯m5z?F_iܒw>|6*{uG;3O8>a-9yt;5yEG=|&!l͸Knẹ3fNowmy`ثة~k5TݸO~#~p=x71JNy6fx#LVmy{n|߇\e7_ndw?y2!K>*{|)}k\N#!dDNvvwo߆z!v'<:`zoxwAwy2!Z"pд-ɌM?+1r93!={9ֵ)wl"g}Ny6$>Q<˝Q݇"VwʈGs`,G=?7=فO?4g7>@#5|ǹEeIaӹu'g>dlS>~pQNp:8zo~ӗ1bNYXV隰n ǰ9u*_S+_ӸI{~Wa`j"úW,뭘[]|pw\lp {4ڪAB5Tņ=|FژY05 p oTkg(kQwj2;Քm@ ]M̦F] ctDH*|7C,Q%a([|XRkܘvqfb]\RUB;Qut)o:cu;U&e_45HWsם4}cz@Si!4̎3ԭVҡyH<&Fknkb?+GF.v o+qӵTžq(m5!m[^h3cj]lv@ -]i-lmĿPI&˟/y3>[Gb^7uܨqJĦAh;;ަ^l̷M_6X>Z9]g|'K:d Paꖭd@gi -u /cU[1$ lNj`cie`7{1FM6J[XO|חmͱ`:y{0lsr.FسnlUi](]@Mdݒ[^ -ͧ?=QiQ\n]dF8:S6_2 -2?nR)mmuu͠n&#sG<@TJUXIkl!*@8l;v5a8V?)&Ez?7&gKJl:@4=5L{D2p?!eAǿm|j %0 -endstream -endobj -806 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 805 0 R -/Resources 4 0 R -/Annots [ 807 0 R 808 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -807 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 638.673057 101.433071 619.923057 ] -/BS << -/W 0 ->> -/Dest (cb213-1) ->> -endobj -808 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 577.726036 101.433071 558.976036 ] -/BS << -/W 0 ->> -/Dest (cb214-1) ->> -endobj -809 0 obj -<< -/Filter /FlateDecode -/Length 4510 ->> -stream -x\K$mׯMŃ  Ȱװ` S`X`f[R it%HFV|g_&\RO`\ToJK%p >-v?qm{uK)pWf_RNU2+\ -+K,EcAё 4 S*%K b²rXgʃ ;g]b.MNyD6XWc K(jY%2IE7*KA;Ee*h+~ %)y΄%dƳv M`,ф Ki<Y?8|Y٭w7jYK !ŤAv¸aKiHB.R %i8Y ,BUyҰ;ȂxYy <Ж-x-b5,[26jXhX>GҰrJEN <@=iX>DazQd=UdkXt\^zk6r 0jX_Y\FlH҂=5, X.awae5B@9a[ p?eOK԰ wmT^Ylƕ} -/6ƢaA"Py p5,/NÂܵZw+FÂE4,;, o5p]WSrְ wKNDd K jX0^ P "phX&xaABڣ N5a*{bBw5pטT4,]5, `aA̴򩼸:hX  %ҰR|$Ys$Y2hX`)ٷZ@ZdAalɅHÂ"1hUEVy<4,Hbaj%ckX_8]ҰbgIÂT EKv5,H5,@ dY jX]FШ%jG̬aApa *M ʃ, `.(~PlQyҰ gfְ gӰfҰȂOÂbiqѰ،zӑؗ\of 77Q)fҰd HQTdAT} LB txB @^=\o& -IwF pzVoHtf3'[#EJꙁr@LT9`Z/1:`z$"!!fċ,~l=/|B/Ͽ'e"A +0w@m|jӦ2Ųvb!FV¢7*?f:: FE8JNY 9AVUH;pup)>W9[>%,ܴS2=Fˁ_``;68ET>6 IҏK!>2:/(N E@n{8 mPFqs9\;}Y5s9@q~4˹̠">s@9nl:p:|'_uZT'!C_{/Nӧ7߃2R˃2qC]tc>yPy5+8 ]wzncӸ;/5e_fzgZ|޾I~:Ow:}4=m&Wl^۪7t^v.2 *GOqjm3궞2Ho<4pǨVNvAUcc uچ׎"6jc#=. _I.Wk7ʹvEw=ÝVuUf s=qXUﾊ$4znpr!gރoZ|ڢTB+mf;W+%_URzqd&M!d)#Vc*c[^O=7msZDϷ,qkN3XoH򳰊.5su\֯2Xu է+e*s&J;O;y/vūUuoݩN~g|=(cڮgNj~]uUڄu.S5ߣ$Lm]v=W:Ksշ:<#`hávr!mV{l22_]6`]Hp/ -7cm|2tl~wg3=wCs=AG}?=L}p^mlZYT_~۱T^r[y>7ߑ2GU1M&3翮8Pyݎ ƺ\1R._\7a_apP77,r\/r瓱ڂx8v1i1=V_oYWkc{GoM>\ C jXӖ}-s5Խ%SbM3۷F3rSUnKBT;Ipc]Éɚ{rp;]}уlOi{{8@-zQ)V{ Sn ϭM7|Dح~w6o8~>J?|]yfѺz|_yss|n?ols\e]?Pgk)="Xq#vs?Ǎo{%%T c.r>怟0 6e>֋C~~787kZz-!.-f2N=W-߶R_]4pW%gMW{i `QWM 5 O6[1S♹ywb÷oq,@#C![{ɮ,r=Py6RiA $%Gm}myup Lʏgv٪h{ӳ Ѫ ;Syi⢵Nj囥fVˌL%g/& D -hyьȎ*v[kL8o0.z7~ȘLoc -==yf/ˋoWqb9 ɶsU2NA GM.H IKYa%a3iR5D}]g ʠr3}h1_X_sw$Jon]- K*Ϯk~2]rv'P- [,K':L0$z1 g3eRS4~_" *#O`ib^IxoVIꐦKi) Bg6T2AO 5cK!g`$.0\eCrUE+=q'9|4,n$C1NF{2~L3#q -P /w@xD87qo?]js>8ԣ-u ]a p[7dŌd~Qc'm#Oͳm0siv7{K;$CAvuB3xiq$2 4 -ҥ…\.bH\q%':BK1amd ճ$My.q!G3ʡ;B4A -lQn7cL>/:x:˸1_oީ1{Ϗ$gnZB٭5rRͤ=P t1ubRWU-SL꟤PbVD2qȯf~f2V&*/# -endstream -endobj -810 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 809 0 R -/Resources 4 0 R -/Annots [ 811 0 R 812 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -811 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 426.873057 101.433071 408.123057 ] -/BS << -/W 0 ->> -/Dest (cb217-1) ->> -endobj -812 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 130.126036 101.433071 111.376036 ] -/BS << -/W 0 ->> -/Dest (cb218-1) ->> -endobj -813 0 obj -<< -/Filter /FlateDecode -/Length 2870 ->> -stream -xK )H6HdE!xvxsϟեGu3~lqXn>^rӇM#%-t~o)K>?rmt7s ;SRKTR -ĔUGlST4꽪 m5y*1VGUahaW5 RqTL#!*q -=]kDO'rQNZ9FlIJ2l,`KE<]-]-` ebO$VU]]jH)*B9$:D)GaK\lIB lQ<8Dkt X,Ga !Kb)A[TJЪգ@-h)a 4q@@$ a"r]l $4X [m@[ U@\I ĕcp@\;=p/ ԕvEkX (wEp-p`c@]a* EEX? +!J ܍c` pu% c1܍wrpI~:[XcAwasb -\[X]X>W̸97 F%  |V`|=$p;w96X] c!0\յ@V *HJ#8P<dpǂ "quEjX:HVEӁXaO mz,z,YpXVJXA䱠 ruEz,@b걠D"1z,( eX 4F -[)z,Bm Jʨ0.P p*t\<[1{,@-*c,]X3cXPlAx,VjDf XL:f5d j23y,ZS锬ά ` *M`cNJM9HRF+7ǂZaKifX X(K=y,h\QoFXzz,hB7Q9q$[Y<4- )-H`Mez,h9[Y= @=VoM dt.27z= ?*ЛGb*V#0eU(cOU;왵C6"5l&iv=ӷo/N"au(0kG@ MP܏Dlly|,f2s:,BIv-[~uK]q\ƗhؿHbF}cZ aCo 洘I-d X备ƿy8!G%u%)6߿y><v^b|Ļ>xק[}d'g"7׼ }FFdGjc_l\gaёѥ}>K<76l#y$. ﶷnWW ɴ !A{=,k{X%DO퓾v5{> ?ep[C]I[vrr_6&sVhGvgu[boa['F`oap=M#݊N:bj&?K7io["TiF׏S͒eԃ_Y \v3؞bbٯ0T١mg,ӽ8j dL]a:u,o˲ /' +'Wj齫>(7Lڐr,urD#|Ekbjv(qH:ڵ]Nn4VVuOSKȶ9ڥž_b<@_kTorBwS*N4YA*!4eJQHS2+iH<Rv,3 C|Uuԛ2.ť ]+9 tE^Z7 5q!6\ԍpS+?4B5,i;yilgl]x66>GlN)}=Zw 2oǽ~>mrh^֬E7x?3>i"Nf?0(tEusmSǸZ4[ (*LsqYI/78]a_/?;Vb}\֩%.qeMF\rMfC7u] -%K:umO4A -,ڱ:h;뾛{t}HVx0R.r9=x d=I ZbEZm{]voQK)iٞTFN1?3UUwm߾lIFVw.hdudy{Hu.[c> -endobj -815 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb219-1) ->> -endobj -816 0 obj -<< -/Filter /FlateDecode -/Length 4003 ->> -stream -x\K$ 賁^_HE|rݵX琿Ībt zdIE~Tw}3Ԝxt|&G&:hY&J<~bB&s:>gs(|sw];XP՘ykUD+<MѓΤR}Uy< L.:WMJ)G%V4^.Y](t )X]|Aea -tw]lN`b-D*gK.{xΙ *IJYyl*` Ѕ1Rh"t>ʃ.| |.6' AqII_BEC_FCf uyA%RҐ 8B\]B% .а )hXoѰ nVaAޒuIÂV % W`nvjXaAꆘ$ p7p7 X  pa5,aҰb|)VbIA  #enஏkX@]O>iXG1V]@Hհ<4,@cƣ,Ѱ w]ESbhe\IÂuӧqWV6.aA"Q "pY4,dTaALWaAnCaq򪱵 "p5,@6IT^6p$aXԡ$.{հ wm AÂܵGAPkC*1bXx]0km$.M Rf/@A*kX -sҰ U J> قY*P& PXjѰ {װ {肒AT:T]ATLD䘰U5^d+๬aAdXKװo\ҰjHÂ\ BE"S<*s l P眆CT_LVdh%ajGיEÂBpa+M ʃ. 0?؎`&9*HyY4,(x5,oz3kXP-tAŧaApa`$騚ŇCEPӔIРAϮu4^#\.:c d+ ۿkɂ/O>|Ra1bigkߝ}%煀| %~4k7%CTJyK_3֏o?!ޖ zا3=B":XO}۟.WӇ5wN'z|ʹnb:7*&{fbMl%Qk}(eW㾛 /Zwz<eYzw7#dȶ|v4h!6\ףKEۧ^1~O o?'.>,4ywX4{outk7`$h5Ҫ!E:Pt[|žbKz94+4ɒOUiyiiSIk6lv\ybgoF{Խ}8=ϙQE/O=u6 S]Ç5lVh_>leu]$9t1j˴âGk.<9nؚ|O ݿl:#rK%blr.=2]Bk5Ɨ[%K4?r|WXvvC/[[7M*wGlރÀk6Ā76//Xb瞮CE~nm>,$=_}&U{waβ8DޗL'._ ۹/GGxv߷x gLBʋϼG[Tj۰Ⱦٱ:{+QtOGe?"GeDtQFWs Rm -b۰nm2@};!Fjw~ط,ĐhёGK/[TVa+ԫ6,qޓG?[ շ0}DZ4rϵىo|@My!'}~۹/ xv5•9}:߯rUV/pt/8%ucG$r~u?Ccp&w ]Oy9>aᲵ=˾KxU$~|*nT}ط}b\ٸoWxc}'*Y'x \`W$-j̼[wzn -i_fqP!܌,m܋,;^LlWmXw6T2Qm}rܡw;}G.z r͎Ycc>HBWۮ_B KKeRqqǷ˝{{tVqr "cUY^z[iT4 @df^.f~ =$}C/`FqK<=g2_}uab~6ǰχqqAq'pLdCr=)3isxCjy1g59["M'dR/ -CԶxI! 2vEn*v:7!|L}4|~ dPh;V83=Go["br*1uA $`1Vt7ɞ>\K8Tsbb:OtGʏ?u nM&sŬCdgbDCv9t:rKkqTReZ*CWh'Qg~,]}IBu̵-ox:D8tXacw=I A.vˤp\L4~"*#Oh?F7f'6:YQ\.^XEAwHdkWAjǚ 2CXJI] t7q<#T콳䄻$nj;~&r;>߉hKf/Ivdٙ N - G3ʦ;B@6LNvZW(Jqx={ShGIc<aZ|ЃwZhDQИ -j-QvJ'N-SZNfi#.)&7i(ge1YI;YngQ-QEyNQKكJS2tھoZݳQ "iVvw__;ԚTm;#̧C{-)CߍgeO -fǯHUx>M'U>\|]ݵwd8̼TW.z ' ӲV[("Dx} -endstream -endobj -817 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 816 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -818 0 obj -<< -/Filter /FlateDecode -/Length 5439 ->> -stream -x]K$qׯ0t0 ^ÂCO[k``e2QQٞ ">ҝ-W&gr.)'k[Wsj,%î矄I} iI`NJyk40bWNZw&⋚B01cc䬥xb ^B VM/>%;EIҕ4buZZ K&R -lNy-!X-9Ð͠aFabRgaw}aw} -PӒ p3^A]kX@]O>jXA1Z]@xjX}44,@e,Ѱ@)she\.QSӊq =[q1  E4,`.3kX7Ш^Mw/Vn` а8 Uӊ%g  X@ $jZ2$aXءD.{Ѱ w-aAZ٣kiiz ܵ#wMEÂaALBY0h`{ b&SRbOMϬaA 0 KM/H֦5,H5,Hdа)ַxaBaA Eor\ii.iXba|)15,14,HsaA*SE"=,s-́Esd^` jX}%ZY3SQLx@J5 &4, 7GM/IÂYÂ^ȦIÂb ,> Fd HVÂ2MO`^5,(߄IÂBaiFSQ-0 &IKҰ(fְfMXjH pp IK2&,[ͷ^N,gV#Эj{3_Ԡ؄g5ZEja.ѧ>D! :3'yɂiAϱd W]c/P?W5R6q@Qk\ZUADG,L:t&n˹,coF}*D׻|n/'%]Bӯ?u~y? d-g o?=6?=\ܟ~/?my+ІmI6\ t%q*L\[cw.PN} -'V ^ ԅ}niN&A888$Rp"^-ͳE-jZ" ^Z A"cF' ĚhD{[2ee9t y8 ٽnd2(8/\^0`TaL*,? "A#% O@y{ yBMt܈E^Dl H5İ z$B!v*o떛Q A{8=Yz}̓,~ m47ѹiSjo ?O~qn/\'m/dYˬkZD&H,+4*<1ѯE/x:tfCu>njYUJ7qPk^(ֽ^$* ڵLw}DĥMHmz$p]}3og}Ғ&dǟ)gp{yIKޚ@F{DzqEl[^wfk._5f SmL6,~TYsշlKVxCM|r'6> ehui4"҇ڔeg&a$ȟMJ!m);D難*8S)xtBLG`Ҳ=/̬k oԽf߾=fKFƟ `A!i^+t S6.#!+eefJ WJهE}^&T,GyS -psI׻UnO23YNP\49+d]sں|f%\wϭfrWE썋"#*IucqҜ 82{t\rkdŝE+h{BK_ESpG~5L!P@=Qj_ڽ?=]}=]4Np=Au%$&6vua8E_m~`ĺz_ߵ:pC A$' ,<唩 iD}(y#bS> ؔm8_IkhehkMC?nOE\=]]ᕋ׺EĨk-e2)Ij,<#yʎO8 nSؗ0a^/vƗr9RverEq=-dLxe1/v÷`n|_mcz}cf}C}3H촐}`kqN|)$k(rw62O3EX`SWPeoyPVJ-[ӱiD7o:?[c$Wg_b;<,".Vc.b+UtrK Y0%w Yޗ|vC[Q|^MoJ(ɍ_K%(.MՓđN5{$PN[n4Q} Ot4z{ۂBxS~yL퉀JWn]S?ށw ϧXow*6f eS$#6lPasJѺ[.$+=uX)u:-/P}攭燅qoB&F>$ qն`> .v)tN;繘JvTOM +DnOMdn+r -ϻT<$`;"kn!{quq!6sy}fÖRkQsUszhc4*9ۀP'zR?عjPw&ܸ,H9Bz=ڸTjR=zȭZC{qrlk;; Zv'%7/Xayz9E^05g|@@7 OQ)Y^Fdn6zzlCZ8JKޮ\JMfr*t[c+je]nnUkkRas4vf-dn"/|r@=ĝ[ 96ɩO4~[תhKs# YY|Zcqa y6tU_Ii_NUhwUI.*仂x+c`Y8[)7Һ^~(dDЙ4Zl_Loe br}eŏ}b93@ j<c\?6ꎇy.= - YbZꡗюbSjtV .@3՘fTlYl։܏Jzg׬ 9-og͖ --aۦu۳=wA #qLRw9¿G#-FF\^>ZE- PCnsOI&]2c';[p -&'_Y@B9N誚6+V}:@ -0>U0D1(_^d*a *R/C< -endstream -endobj -819 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 818 0 R -/Resources 4 0 R -/Annots [ 820 0 R 821 0 R 822 0 R 823 0 R 824 0 R 825 0 R 826 0 R 827 0 R 828 0 R 829 0 R 830 0 R 831 0 R 832 0 R 833 0 R 834 0 R 835 0 R 836 0 R 837 0 R 838 0 R 839 0 R 840 0 R 841 0 R 842 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -820 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 766.923057 101.433071 748.173057 ] -/BS << -/W 0 ->> -/Dest (cb221-1) ->> -endobj -821 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 747.976036 99.933071 729.226036 ] -/BS << -/W 0 ->> -/Dest (cb221-2) ->> -endobj -822 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 729.029014 99.933071 710.279014 ] -/BS << -/W 0 ->> -/Dest (cb221-3) ->> -endobj -823 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 710.081993 99.933071 691.331993 ] -/BS << -/W 0 ->> -/Dest (cb221-4) ->> -endobj -824 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 691.134971 99.933071 672.384971 ] -/BS << -/W 0 ->> -/Dest (cb221-5) ->> -endobj -825 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 672.187950 99.933071 653.437950 ] -/BS << -/W 0 ->> -/Dest (cb221-6) ->> -endobj -826 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 653.240928 99.933071 634.490928 ] -/BS << -/W 0 ->> -/Dest (cb221-7) ->> -endobj -827 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.293907 99.933071 615.543907 ] -/BS << -/W 0 ->> -/Dest (cb221-8) ->> -endobj -828 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 615.346885 99.933071 596.596885 ] -/BS << -/W 0 ->> -/Dest (cb221-9) ->> -endobj -829 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 596.399864 99.933071 577.649864 ] -/BS << -/W 0 ->> -/Dest (cb221-10) ->> -endobj -830 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 577.452842 99.933071 558.702842 ] -/BS << -/W 0 ->> -/Dest (cb221-11) ->> -endobj -831 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 482.717735 99.933071 463.967735 ] -/BS << -/W 0 ->> -/Dest (cb221-12) ->> -endobj -832 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 463.770714 99.933071 445.020714 ] -/BS << -/W 0 ->> -/Dest (cb221-13) ->> -endobj -833 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 444.823692 99.933071 426.073692 ] -/BS << -/W 0 ->> -/Dest (cb221-14) ->> -endobj -834 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 425.876671 99.933071 407.126671 ] -/BS << -/W 0 ->> -/Dest (cb221-15) ->> -endobj -835 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 406.929649 99.933071 388.179649 ] -/BS << -/W 0 ->> -/Dest (cb221-16) ->> -endobj -836 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 387.982628 99.933071 369.232628 ] -/BS << -/W 0 ->> -/Dest (cb221-17) ->> -endobj -837 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 350.088585 99.933071 331.338585 ] -/BS << -/W 0 ->> -/Dest (cb221-18) ->> -endobj -838 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 331.141563 99.933071 312.391563 ] -/BS << -/W 0 ->> -/Dest (cb221-19) ->> -endobj -839 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 198.512413 99.933071 179.762413 ] -/BS << -/W 0 ->> -/Dest (cb221-20) ->> -endobj -840 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 179.565391 99.933071 160.815391 ] -/BS << -/W 0 ->> -/Dest (cb221-21) ->> -endobj -841 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 160.618370 99.933071 141.868370 ] -/BS << -/W 0 ->> -/Dest (cb221-22) ->> -endobj -842 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 103.777305 99.933071 85.027305 ] -/BS << -/W 0 ->> -/Dest (cb221-23) ->> -endobj -843 0 obj -<< -/Filter /FlateDecode -/Length 3630 ->> -stream -x\K ϯYE | Q#F䰚hmrJNt`ȏduǟ"ޕRs\K]ca$k*A ]1t|:YstWcpvL`Uȳb2X;b b,A.YbH-bA 1XKV!{Xט 'Ƀ $,^.,KY|R,O K-^,ыŃ,%[Y81<Jf!Kv+ULdDUvW%/Pt0E&x,,]ψC% "pyC< ߜ'ɫj)D.`)XX(IL^v0$oaP pZX-,H]=&p  nk4UGHaK a‚! ",,HCgC;ZX 2yEXXU‚ `aA)\Ⱦ\@ 2E dT rLǠU+pm -x>[X8boaj)WK@ XX+dXXPJ@fn6-lD6Vb>@8 ET5M(:oVOyhZW:j y)?+!_>~hS wq wV+zϕn4/innImw 򒤠O_&ewe/^O?(T}?@_M"]([dV^Z'aP @n'q UsbWMbJM~*}d6 {}n]<Yn7)ww/0)}|b&N|vǵ7ӒEqƢ -;M3?/6|JkXxfp<;S"ZKewVWixT鮵_`u[]UldulV9.-q_af=\Kvu͝.дfo+T4Dïl9m7YmxAG ~nT]ZAti nGozLoƣ>=*ʗ}qb.4i5~L<f5KgYkѓK2w'>ԗ.Ya_#<' Z,GOf$"脗s/D>o,"|cf.xcrc gL?P5~;d: ӤwwWu-n^}qOr}}k /wZi36}~؞|e`σ ǜ]nĘn<n1JNⳁ;_LpRTU `Cln@O-zmWVRiV JNÕv-p{.!-o;7Bu郾L4^z7, -m~Q?>3r"knŃlD >-.,B.5AY%Xh'$QHQhM2v7:>azJ':z] bdd{r~#(dVdqL(s1x&b$Ҵ !pe{b}V yk9ɤj֦j i< U;5}CA: ԦlfOA IzNޫi~2LKWA;MI_/M>B.d?^S&\Oc ?b6zǁDB^5*f[$wة<˅nR&hE7;y:ꈥ/ys6;2+]c;ꤲkOAǞuBXOʙHM,7ȱӎ}8( ѧܼ~U]'"a scc^R.?rS{-j:Z;;MN~ǩL /olx^N[OwLC9t '+ә{"{3vs\_kR1ex4%Zutp%Lј'EsZvbA΋tի2oZScJ#Ƀ'#S7rS<7ϋ֝<ЯvOM<@;iSj> -endobj -845 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb221-24) ->> -endobj -846 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb221-25) ->> -endobj -847 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb221-26) ->> -endobj -848 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb221-27) ->> -endobj -849 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb221-28) ->> -endobj -850 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb221-29) ->> -endobj -851 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb221-30) ->> -endobj -852 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb221-31) ->> -endobj -853 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 605.596885 101.433071 586.846885 ] -/BS << -/W 0 ->> -/Dest (cb222-1) ->> -endobj -854 0 obj -<< -/Filter /FlateDecode -/Length 4350 ->> -stream -x\K$9ׯ3~IhH`L  |L?23vWtWep3 ?ɹ˧5)X%6Gpv Ο@ɤ|.Omw]8L)٠ -X֑ -CTX 1BbGV\rX -+C *' brr8oʃ sD(=j'x xh( Y`]YAxL(YlN6s&[ְ>a PyI!h+7p5,`g5,U. $djXkX `aAlJJQÂX,xT^4$ Bd<‰5,@`m -aA򐅼װ yȂAD8DjzY`.j~@2 )DcЪƋVy<4,H bar)K@ kX -dhXd\9Ȃ [D9aAѠgdjX$TJ5,Mi)UdLhXd;hX&Y(9{I79CoM7BD|VÂ2M/%7)~[(J4,( YBY4oI7N/B_XÂY7ѫ[YͤnwC2i<."Өa.o"r{ ̒qfuzVu{Z%u|%GR7 &2],`:nX/1>`²4oQECš -}9F1zز?￟~9}Y)k?bA0 =D\'LVĺkQDFtpbO[:\SwZzm^Ld;rn& >ˮDž'e맔_J?iŸ)9OYD] &מB]?^"1_ˬ4[i/~4k[+zMf:ޭF&wmVx7UUuX:'=g4^֙kqn%ڥfx iC>In}c;UVB?'zU:SecVѲEi[dq<9OltK8;ᰳ"я8Lvz+Ugv=g?r{Tpoư˵6hLğ>cY+[+zM >L_ I1އa BS_ʸ&+k}-{_׾4kBNVcdsvWRr{x>k֟0UgC-9>'7c?L3.uh o>Aװ]m#M髷5&\dSΙK<ӭ r 5T&ؒ-ǭE5Q8#OK7o~?$?BРAkc W+rpy%ض@isňQx_^Nku҅j9mj;ʙa'獎V r%d1 -]'yk[`6}Kvg -s(/ĭO2GMw e(5w߭1ڻ)Tʓ\* 4,ؠn4_e#.` lCޜL`4`;ƎAQkJz^yǦ15r+ܪ!{|;uP&$LPLqFRfn!zg=6݀0#tYqVyr@"gU} \̀ﺸu6ԾwvOsx؂MbY: ݒʓ<ۈF<7y: F`CH4ynQf[+o[`.OW4@#D4JƎa6 Q'%PqVkG ܀Y0.u7s՜*֓Â>/s9'P8nsE`uZIb 9e' -7:.wEXljz?m{Ur*oqIۇ떊XQ0XQ4?vLy; ۱8[%yv$^G|ÀCMǾo'B'[lQJ1 nJKS?~leŅc,mlڏi[} -:^qnlq}d+dXcLOUfh[ygm4)jB/%υ&b>7ܦ,W]օazOP&#QٜLOM`:L_{Ne=ܳ!1)t]}UEِK9ˣ6m*^s/{2:ZsOXݐV2'?$g<d!_mo]_c0QNJJ -_B,Շ6Z5yKoWK -5;eָ,/ʆ֫E ,C{< 7ɎD GdM'/ 誋EUoe}rB>TyLkiAm$TJ >O -I_4c2;5y!fH˕VN!]Njg*RyT-MCaꔻe -VnK,Pk'{ a` f"Mvr^5*fwЩNGN6߈,[',;|zgqPOܼc}N?Nu8JsE7Ͽkuێc(qR=a -endstream -endobj -855 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 854 0 R -/Resources 4 0 R -/Annots [ 856 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -856 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 432.754475 101.433071 414.004475 ] -/BS << -/W 0 ->> -/Dest (cb225-1) ->> -endobj -857 0 obj -<< -/Filter /FlateDecode -/Length 4386 ->> -stream -x\K WXU A A,l{'F0`琿!ӭnw0;-,ɖdτ-lM%E>_=}w"bu1o -gKL%pV>TKr˱cΔ ? I9% - -E+LJ.DKX#$vg%%1ع2߳ -pɲƂ,AT!f &BQ9kb.MNyobb+&c -Y K̤ 4^,>zRy5^,) -/CXWVy"YW %3xiXx] -iX0chXX骼baA8 e Kd5,BaAx/D.5,]b=*4,@\ViBwb5p( "pWM b@@(iX3R԰ !ʋAÂD @ʃ,X֦5,Hx4,H dа)ѷ@0dAa¬aA -39U^& RbjX\d8x#ᒆ<Y*(2!2x ְ.xjXdA4aAvYf$ pB#5YÂHa&RAIH~l"Qyְ g'fְ giX۔|3iXP ӰP4&kXHÂb3M/%O7)~[||3iXP(* h*o4^,%F73o"WKYͤ 4pi԰7j=xCB|3dY7lUKiԚ|%GRej*ԲX033'Yd[0sffs}~?*e=GI+n㩘~#Bt-@q)8qؖs`C^",6GU{,TJuEVyw!CbtX[VԀyy9{@ysYxl?&`a!o5~c!}S24dG4O_T -?/Nb$|nWr~&]Za÷_/~aϧ~Mğ~ߐ:.\??27b*8鐧?B~)}ᨤ5=[A\N$ oudnuR&b:O[He.-~',EtĈlp3RȩY@ciĮB[I a`O]w}m ۯmY}X#T,L))c]7IJ&. Y -f 6vl.vyͿ鲴ㆎ@mc222^l[cdߧ[Vcp1ny#6c}` em᡹l[C81^Q`gҺ -cuW7)DBkŎzqVf몾i6fC8 ZtY*oϝabip8^*84)惩-oqш8}'pF`Cz>Ȳ7-0lW4*@#GBJ na1 r-ޯ?KIqi^d pBtԠUs"A<S"l|w.{0"̹|N0_ yk^}TlBͤ2V-z 79ǾO}ccׇ9Wن0nW~E[7J4iXe+멑Ԓ6my~SEs--Lys\v08+LO8r~H5]]~Mk+h,rAE6W3"D̸1,s:0y/ k>'c|V=[y}iq]Uo]niߌUy}C}.[" 1C?5<-7Ti4VGZWu: ՑfK;k7mzY v^n9\}?N~1sGz-'out޵{[zuSP|@oCA WFP]C&x`غȥ BX8ri{,׿z޶)bm:,&Dk`=4#C99vA!!yeWJgO7%s^nHUm:qrXJ5;7~z?[}Ga?!HV/ {D#kERm VJ g{ݯ?%k*G Ie96yo٘5}ׅd5+zzkUk8Z?O -܉&?~DZDs_\qx,/Ou%7D,%Ae)׶e-!>/4uy8*%,O~J䠾J9%bk{%Tv?/]Ϻt_/_եXye),7_.p -bn>כMn ߵa -!$k]u~R l:U|pVq02 {{Zҡ`5~X.v)NϜN^LtlK9sӶK '%Xm,4-$>+d~ qHm, Fۖhu.HPɝL'V,'c(\&JUf<7@ {" u*'b'6Gak[F0R_TGU TiP[ O -rRS?<>s5$nJm.'2Zh;Zܻ.J7ue|m,1Ukʃݸrneْ_N!)C - -FmL^:5*fɳ QyIO"k%P5 XN.RQ_6^@n[Q TxR > -endobj -859 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb228-1) ->> -endobj -860 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 446.531993 101.433071 427.781993 ] -/BS << -/W 0 ->> -/Dest (cb231-1) ->> -endobj -861 0 obj -<< -/Filter /FlateDecode -/Length 4391 ->> -stream -x\K$ s˔D b$"99;6qu*=3;6fԃȏɹˏ'2)3~S8[d-1Bɤ\]͟N_>L)p郰؛S -Xd -BTX,1BbGV\rX -+C #@ ,k,aKH -䰎HAbN`"5&K4&&jbb!k<,xLIE'Y\N^%⠝2dueY(xśP2+QNsLޓƳئWy(lRL -AH<<9! G'O9+Ļ=ydq.ʃ,| \, #aKpqp次pJ^WX,xj@ x Y /aw 4,8x-Z4,[b5,[&5,\Ix ϑ5,\RѰs=SЅ'  @,Y8HM%kXdiXdAʠa2S,o<,0>`ȂLQ ɅYÂ"1hUEgr\ MjXZd8x#钆<Y* 쐙k< YdkXLGT3sE#5hi>= "`W I.V !k !-`q=t!n˹[!lԕ~%BhB6/ bHQ_f6JD}asB*/NoޟHYw>4;ut~߿{Ӿ憁|}_JK#r=͌oFOY6Ce6. ޷9$9t809qr0L AbYz|%sd]hĹzJ=HN\Bx2l3kȵȉ,7P =[n lj:5+<=cԸJ<)W}o~3|5ц,Ȝu\Ǥb/fElu3c3gK:y΋<7VI{5 VP^n!i%CtТZ-Qo>ZvϴnłzUq1SVrT+u;mZqp7Fwr7kUJFA/f%Ӗqxx*8Yֵ5lT,ky:X:s8.Z>;cPk[^KZ<>6M_^iY'.'xR_y%9GN mPsorq^r%d;9i/f̻ldnvXQQb![t7: m Ům(@ l/n> ͇N/UWMQE4d檾A_W:i=띠kE9"l}_Mŭ>X(v6\5v5Y{ō<9K.rjAb,RS>gL#H&T2Ӡ~>[ZA^yrɍ[+v=rc!{"|>(%ɫݯ۵;.r,[R%axiGjzW'S2}e^{>|$gH-xs1Dͣ ̓rm&mÅ> -endobj -863 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb234-1) ->> -endobj -864 0 obj -<< -/Filter /FlateDecode -/Length 4891 ->> -stream -x][~_D A 8yXq8A0|T.Užx ^xH](HԲ;ZyWfgr.)`M -~R8:WbOBdR >mOuw]8QXL&lPX,Ha`R!* XƂ!=+A .9h,g!qrgc1\ Ia9 9VAL^`"5w&K5]pc!K(iYc0"dHVAiY[ְ>!daw} z G `(cl  z:Y ރI4f< p?ŧV5,]1}*qoeb,.iXϬa0 z p":_!hXs0 oY+Ɩ5,]װQ $QyccjXEÂܵHÂܵGA^5mFjRh`ȂLQ ɅYÂ"cЪƋVy<4,H BӰk)K@ kX -dhXPdGfdAa2]Ӱ {ȂlPÂ3VjX$T:3kX9I5,` Ty0aGA,~2GA -aA^YÂ!^ئ7Bd|VÂ2֛5,_z3kXPb%ⷅ7!K@ -0 MƋְ(ͬa 7ѫ[Y֛I.dx]dQ<`V[[oHtfgVw ,7 [؋h= 5i1Q5@XYuλOU9$̜dnc c_uSmqR4f!8@L7dL׸%]J<&2@'c5+}ym+=6QOH&H7FL kHKaUH]||ݯ??ZdQ^y|fРo@{\tGR'~?\CN*t9kh.ܽ?qNUxErk߹_A߼[~w@(?UҤV(Qum!O8ZORn*?}޹[=ͤФ_f3.U, t䓶mXOv"9poa-TA^ÞV-P؟-XME>j3Vm=MT=;f[kvv[kGdκkyaw5@We>^;ou#^Ck+-]mJ[! O~W6ݘ[?~~:ey_.K]h;;I洗nXu}en?L}Z.aiy^l$(2Ռ$$2֑.ن'T_ڥ8t WLҾs_Ǻb1``u>kyRhY/06CA k-vYYw]io~JꁯAI :౷Wʿ,|BK,18%f - 75U3DGGⵉoo.XjrCͪR}2(N7y(qK -"/ۣ; p]kL;zr=-ttbANY7>C1R vvHM7L.pۘ}-cS%/Y@A%ٝuޞ9%062`@*,ek3c1ϒaP)`čw/q1sJcV/0 CNc0h8G'!ܘ8R* ޷y{ڑRqfj,|xm[ԴyBfVrqlb!S׍o4laKiD{A-rϽ,WgK&P"}YA8q!5v8ۙu'erj_1<ˆYuxR%ys.@/]TRi׋#TbDz\T_:oX5g);]7w_36F'7ܒPtÌ9֯K4ہ3ckksnk7oɛ>fbK,ڞTN֥&h5lVڇ%3QK'p_7dQة`Ӥ -V]TxvVv߅/*,X16fCݘ]o,ڵcݓv6y{;WfVdRgbUKꌻ[7^6ӵ9?2Gmk bF?yΛ␆3ܷ kmqn=v Lyq3~W{/׈'nF }Ft vxLɞeF!/%_'vEI 7]D|檷9 &dcl;]:oǕY-'"F}D}F5Nn[ZD1z`m|#:>%bJxB#ʉS vA.$:m܏3.g$y[ lлoVj7TJ&RČ(hls՞_t%9MYVN^}-H1!vxN} Y. fr 'hX7wy;_ŨǿY7:om>R ߈˕ ; po$U8$O;NC7zKm8/#y)G)[i6Wj?R7HVKu?$}{䧃 -,m! mJR0v88_h~hضBTo9wQ3=YF!(!6A \v48*$;1vn=7yܗU>M4M5niK}Rrfki8h4 U:5}BϓB/lk1?͚]v&fH˕VN!jg*RyT-MCaꔻi:ҞBG,ksmd7~G<\8/VH'n'g;ePSnk6$"t Oป6F'⛝VLuXӀ4Nr)uU ]c+ꤲJO@ǚu@XOʙhnC7y;n2رi&>Nv'oS l% Ķw6`A0T[;:1q8qOj$K;?sغ"ϑL!w^Fn3=O?.YCOxͣJsgb:Ⱦ W{"s3 %xM*c9tCC-|z3\czmtQm)NV@4hdK:j)bP6k:̳ҕYnx=[ٜ%{.Zkw*hywi<#3Zؕ|wK&ROqy\@-<!,Wr'Vɳ\;|0MNe]'0mTW{jŪCzs+A\=-u?&Y*ʿBf@> W𲍲B ( -endstream -endobj -865 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 864 0 R -/Resources 4 0 R -/Annots [ 866 0 R 867 0 R 868 0 R 869 0 R 870 0 R 871 0 R 872 0 R 873 0 R 874 0 R 875 0 R 876 0 R 877 0 R 878 0 R 879 0 R 880 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -866 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 393.004475 101.433071 374.254475 ] -/BS << -/W 0 ->> -/Dest (cb237-1) ->> -endobj -867 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 374.057453 99.933071 355.307453 ] -/BS << -/W 0 ->> -/Dest (cb237-2) ->> -endobj -868 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 355.110432 99.933071 336.360432 ] -/BS << -/W 0 ->> -/Dest (cb237-3) ->> -endobj -869 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 336.163410 99.933071 317.413410 ] -/BS << -/W 0 ->> -/Dest (cb237-4) ->> -endobj -870 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 317.216389 99.933071 298.466389 ] -/BS << -/W 0 ->> -/Dest (cb237-5) ->> -endobj -871 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 298.269367 99.933071 279.519367 ] -/BS << -/W 0 ->> -/Dest (cb237-6) ->> -endobj -872 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 279.322346 99.933071 260.572346 ] -/BS << -/W 0 ->> -/Dest (cb237-7) ->> -endobj -873 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 260.375324 99.933071 241.625324 ] -/BS << -/W 0 ->> -/Dest (cb237-8) ->> -endobj -874 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 241.428303 99.933071 222.678303 ] -/BS << -/W 0 ->> -/Dest (cb237-9) ->> -endobj -875 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 222.481281 99.933071 203.731281 ] -/BS << -/W 0 ->> -/Dest (cb237-10) ->> -endobj -876 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 203.534260 99.933071 184.784260 ] -/BS << -/W 0 ->> -/Dest (cb237-11) ->> -endobj -877 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 165.640217 99.933071 146.890217 ] -/BS << -/W 0 ->> -/Dest (cb237-12) ->> -endobj -878 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 127.746174 99.933071 108.996174 ] -/BS << -/W 0 ->> -/Dest (cb237-13) ->> -endobj -879 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 108.799152 99.933071 90.049152 ] -/BS << -/W 0 ->> -/Dest (cb237-14) ->> -endobj -880 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 89.852131 99.933071 71.102131 ] -/BS << -/W 0 ->> -/Dest (cb237-15) ->> -endobj -881 0 obj -<< -/Filter /FlateDecode -/Length 3174 ->> -stream -x͛K )ez$ -bĈd#Xsϟ=]$׫&f~Ū3+?U9J݇m%{tf\ R,|?Wk~sch-GNߙJ%Z -%Gՠ"GR(%2bk -fQoUfhS : -3D ˭XX=b\ !USpztC-6WW=HE9k!眪SؒK%*y:آR˰E-tDx9 -[]ĞIHRouRHU<sHMquQ\]-Rsu% EO'E$VgFBž.:؂3l=`ǀXJՃ@j(k Zx-ͭxb"{ -IGaآHSa -x,-QchX Rc*qX .$J@\RX ` t/ ԕvEkX (wEP1WX0 -bEՀ8 +!J ܍c` pu%`wc-x+7E -Fc%?f.t Cc iǂri*pmcAwb\] \qgˁsn J<$p 5z,H. VjOrl C`$ &kZ  ,EXUՕ@bq  2y,.%%E`y tΜF(%{:p4ܵecA.&c Ȃǂ\5Rǂ:|.\' H@-ZcФU%cA)d1ow{[.@a 2E YMcAI1xj]]ǂR4`)fKI.y,бz,( `x,RjDf XL:f5d jefX{I)>z, 0M)]l&<`|l<`&9HRFnV–HcbcA#؂cA,MXCG䱠q~3KoVMMly$~x,h -[RW[45gނIoN.ÖcAc 7ѻG=.wS<4{,l= ?v=1 7amu jU3|mL,kvO B|Lop9}Z2¡`ͬnaZ(b<}f;)?ͶN6EbpWakNB 0SM#XH,Xny|ɰlf$3۝/v -:_#;+D5|qn5&:_ܯkI/mEcܽѱ_' -?i/O)HpmS .gK;lKv PZrX_bяE[lH_ lWH7N_/߿GZC*0rhPdz+ޚg5?ϪI^%۰0@]j_JCB#W`Nzgx 6m{M2YU~}"a큤\-HQΪ{~2C]p#|K(6}.qowc&N)tCoW2vWajvۿT!5l_XGH3y5;9G'<X,K1+9 Al#=t8yDº+W!u#3hty 4ڝSlosv60):˦ cq4K (*LӇ8Ѝ,g#»+/Dsf.ؗK7GvreN%4++:th5.q6˥6-;iv2\o:b}-Ka2u:ٵ.b)X֋av1gnr3CzJǍtϗvc͑LOі,sOF3L-p"^ j: dem{펫2r)itZGe81oZ}ْ(\,9rZ{Hu.[}܆NCLiVK7%?2w.uN!Rg;:_B\$W0Tsf{-yѺg''$d T -3&CўV,Mu5roexݓ[ m/olѸ,U_Kzv[ݣȎQPaU -endstream -endobj -882 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 881 0 R -/Resources 4 0 R -/Annots [ 883 0 R 884 0 R 885 0 R 886 0 R 887 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -883 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb237-16) ->> -endobj -884 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb237-17) ->> -endobj -885 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb237-18) ->> -endobj -886 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb237-19) ->> -endobj -887 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 681.384971 101.433071 662.634971 ] -/BS << -/W 0 ->> -/Dest (cb238-1) ->> -endobj -888 0 obj -<< -/Filter /FlateDecode -/Length 3342 ->> -stream -x[K$ 賁%z|q#!aX琿:3]"(#Rϛ?ˇǓw%y5 ~K:ťrMBJK?7E]zӿm9r Obrj`@+%WJL`0,H#߳ -Vłc5Xb@1b l Fh!Gޛ<)\ҳŋb3yP#rpH5sN1dI K -AZ,^,ɛ<k!W KvUMdȥVM^Ry'*x!$"b"d>5Yh0~,p"Q(MK%&`--9% b)[d b%Ǖ6ǥ%ǹ bYX6*aM`ߍMd-K[k]KC ǵRb%RlUzUZnjŶ;*pGlG]<6GtdMZpAaCնl-9UwچiC&Zڱ{yJ.3vG7W{uߙeW/p>-V_^g:RG^wxO9x{dR >;_["GN_ß|p7އ߀"g)m !o-zhO~w n]w|ެ"8eT~&|OK{;LEٟuVDI>C]n[WqoyXlӼ㲍7e<Sw7ކw/&{|scW]4i/}*08'e ևqO&9ЖK[|OA?&Ǯ+.K'iNqtC6<=܌z_6{rW~;O?LuYٜ%s2>]x}-< - G6=sՋ躷tضom+ӆLi{/ =!%ZO#dZ -ǪMK%'~;P }?/CN_ }(X,9ޛGf.˦,ސ.{Ѿ{RVVtÍwްF! M.D~uqk' ~v%Jsm3i<ɒ̵UM#^NQ܏bk> DRNr^ԡ*] -AETAx܇Z5$y[\V]PʴYPQ_@w֞;P!#9Ldn4끼LUac"牝WM.sŃ\n~6%1"G?L`E^0z ;q9q/_N=EJa=p|qx'Zĉd͞L|g(bdꪛ58k^Q3L iP4Hi&=Ahq&2_6+`oE0$ʆT(XVH>.Q+Q5DAw-bAAE~KA2*4Bx¬z,T czv}9IjꜘP'T|,ΘCg) ]}=IrZmTQjWHzPà#PL lϸZ*3X_^ĤW%Օ~Gě(is.kv~՜d5hYT^5i#ڞ4x WfWtWs||%f?d$uCHҾ aK᪎J^s/sꑰ| ]w[+ ݬysJ/SٱDXd(m&Iz|%G^h~p = -endstream -endobj -889 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 888 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -890 0 obj -<< -/Filter /FlateDecode -/Length 3187 ->> -stream -x[Mϯ$>AC4lry虷V>tbbc gWWk+Yϗ'JJn6W9x-.k:7@+-Œݮů:L8GZ!D*R|"BD)RbDC[c"F}&&c% -5DKGQe"Z*D<{*"^U"2,k -dD&qhHɚ9d -]RtIA3tQ2t,ʠKE@4"U 5qUU*kZ,RLKM2D)"%Ԩ $(~ ` }i 2xצM+(GkdyȐQYvO @YT]($֮I J.# R\ Ⱦ]@ 2E`2W*を2c*j]SY,T`-*qYĸj@qAi¸S9$q2]B`\P#tA6ȸƊUf 0Cc- S3z[gVUTq+M0%A-,~2ʠ$e\Pkfe\P+t>2.oz0.h c\|v&3.C=*֛Q .mY4XobGIfa\$(T]45$7NLKlʸlʸi֛@fLLEfMdlmA ?j+Jw <7an[܋٪=54XYLw 0B<6_c ݧu* -Z aǚc'~L{zնS7)hF ym^+t/ rkcY -v#`9䵽ۂ^,VwpJhnu;ٓNϦu}/1:5A*Ӛ ~sCea[>z>48-` -}.>TQNyͭC@ggS:̾]"Ru9?^=Xg='`/|SΏUǫ!|/| >dK9ȗ{ ?X}~4೩S{K_lK~֏ߝ/>xkOkR  ?ў5YQVU׫Lt|J{}wk.4 8 jb}D1ۻ(귯7˵n?ch7et\k?ӺzuFeܛg^{4ݴ5܆r&Sx݇Y<~O7alIO=G>|nt{οGkv n٭ws僝ʚ }t7߬:Lz6xg7ni#zHO1(KHNs#uozL}7}7"1v2gYvGr~Q}ӈ5*v>^߽޷ԶXne;v߭"#{[}ϨN"#<{Xʆ3IzF q#ƶI5ldSF~ 7j7ܨ}fwt7\o԰!>< Sޙ܄Յh+Yl }fp~8Qj?Њ_]nFW;oo&|=iB%>_Q1tr -bY]IIs/c꽱S c5L@<#l.찝ȬNI8_ G{?L'8T_MecYcYYDs`n]E6K1N|{Պem ݑtk.'Zn-*Tntu, Z#KxG1־.~@,9tDℷc4§z+(K~DM옽7H5.n6b9࣑V<Qfe]J> RHw;k?΃> -endobj -892 0 obj -<< -/Filter /FlateDecode -/Length 4332 ->> -stream -x\K$ s~|q#!awF0`C~>=;FNTIE~$]?љZ[x|r$ǪoIGgc1ɵ\3B1%_6M^޴K>+Sj)6)uAadJ)+ ؚƂD1bIcA}UXbX\سE1\KEa9 9VAc -%36T^B0Dk&眪Ƌ%54^,h5d!KC[ Ca/k -L,%h0[21@<4 5$Dxʃ,E ,aAǠaAFXpmsm.kXjXaA”.ܽhX!eaAXDnSA@G\ DnphXp#avkDய6jX bA K"7p'5,]}ְb?Va=x>hXGZaA4ʸڲ *O5 -4-l\MÂE -$.jX7^ÂuZwoVÂEސ4,9@7,LW5c[$.`kX(llb`HNC5,]aAk#YB n4Uc=Bwk<வiX65,ȅjX `aAѴRYlN Bd<K԰iU ,{ ,H4,@F`C S԰HfjQÂ21hUeoj\ -+ BӰpz % x.jXPdhXPdGfdAa2]ӰzȂlPÂ+l5,@F- UkhάԘ MPi)UdLhXb;iX&YBܬ -Y6,4 YiXl6&kXZ 7}԰~Ifհz%-d7-BEA$MM[`MːŷaA˙ͪa ԛ#JfQ 4piְ ԛlxSA~3+UU=1ބتX`/UQ ,j$bY=5@XY&OU9Zh nݏcv ~Ol#۾a?k ?\n0}yKx:2<#}ZQN9Ko!Jb醜;<ǝ乒'ASMh=~FcLmT -݊tl A[Yj]١[o5vZdm'F\tI+Xt*rB&S}q#Lh&$H~Xt¦bBV7!+L1$Jʪ \jjGq/K:;/ڙk;E'zs79_帿rBk~s7{s;OuR xosS}$ߩM@:<|懟Z*~~TZ䖿 #~xo^R?<y7(dM |$Y޹o4o\ʋ$,M*kuЦOI|~/#ѪcܗV+ɁqAkrIE'q(їb>7enMx2 AeY.:䖾L݃Ҿ?_YdONv} 4E {'^˂>.G:;1֞cֹ[xݎb!xSG4oexD*%V:yaF{\ hGu? -ȹ[cLK]fpFyﻤQ̣sos`IھX2K߹sЯ8a"_{VڳEm>یSKIq1l?nçs{g'q'q-S|Kֲ҉\_:㵅E,/fGXas;gWwzE2lcj\fy=r +)9"c|c?U1Iu~μ@}8MXfg]#%}!ToZdKBN[޺JV&ޯӳ/_]D^5d]JU?v:W^!ok_6xu;|~][}^z:kcF;mE[%6{خ-sQ^?:~wU;Lލ'UɨD0s~!ި,ZU8&]F-sc|VCr{=v)/ՄuO5=uէɼ&_s -vUiOAF~/26sa3Q wؾlاF.<}\32MJ9>Z.nHW] -sh#gcXKb/yy+-?[8>(ǛX'?U8c[*se>Yk͙K8]>I1O:V│c9PwR뜚S8T.ɱxOMc{oDW=uV;>eN׳kTze>[(D?zv'7W2 g8 -|ímska]^AȒ+BTezwJ?? -|w=6}:' ߮fZ"lb2v}r= -gwUzjw| -Ǚ{lO>%TOxɈ;}Bv2VpE+}Xd{2?z=pu ↪Kvo)zz+gVYw ur}D)7Cjt ?_V/qD/ͷ&sYG%bQ|^n7|4zKL?tS-rߣߍOϪ'Fy|I2Cc|>b?͙x mraDH5 Ҏd!:62z-6z^ X!+Avrܘ%*g{LҎ(N`!\_īFE˝B<˓8Dsb/RtaK}R !T=džıO -0#Z[3Yh4SMO/] VzW\珍]Xf -endstream -endobj -893 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 892 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -894 0 obj -<< -/Filter /FlateDecode -/Length 4324 ->> -stream -x\K$qׯHF25,X@>>̔z$V> Vɬ̞iI5Gd0#??S8RjN||]ZEc,9; 59.W9_Ornz_g'5 翼(咳U 9J2X)8b bH 1Xc,@ U!F́-U -rɃ ,^ .-KW]JIc"'Exd %&Ēej -duY|UrR ɫ=/zqR lLv)e!KRMddaX‚A@Ƀ,֮R-Y(F r,,,@Dj@mb Y)ZX$s2[X%!V-^d+laAȥ\4\b‚\! pEDD/@ / J,-,( LxhPcyfpr*ZXmLHi `&ba$HsLd!a Jn J,G `of ,,,>9 -,罅5䛑-,|XXP#DgJIlaAe"QLdAT} LB tx Ԕ4, @, 7Y.J2Y<."da.o"r{f8Y1^o5K o͚jd &2˒̪*eE%s%MVl Ft?r=hvO_=O_*e'&H7R rm8F0A3a4 !Q!r] ťB#lE*s@0y),%[7y'YW%Ѹ(g%!膯Qn`w<$K7ywYi!OBX/yM!JG! B5~G!?tl!C,履Oo_[Χ?`⑯sYxYt?_O?sE =l=]TժgKӺe1hY؜oOvtѩWըq 2Hw>U2"\ݪ_~?Vj >e d$.j˲+R}.C?,ˤo/HhQƆ /Nǜ.}sqH!?S@aˏ?]*qC煞GJEH -!SӦߡ,1`&_$ -;=]{;eZteYʌWz8hݕ[ܻ|Ʊǽ%E߻r+˨5M˘"XbW{ 9zKц/*żn͌︽_vL *p*BL7b2̨2[^lclsa{;U^ͺ0mͶàs|olÝ,pHs5UceGą)G[3EM/YpY$eDZznGz|H_ -z2 9BC;)P9Ǵ \mTȎz~d$"_jz+:{Q&"ЏmDZZ3ME\IQ9>B)=x.ٱ>൲T},jb}3U3/{:m #q|2~>5M|wK뿕a}kodḏ14W94d)ŸC;0?M(w{#N &ǾѷmA/-=ߗ=c$-K՛>4YZߟC -}Ho)iêl)qT;Ä\TvhM sô[A9L0`}rx.ɵLwXK d0fC7}?O03NLj%R,Z0ƹ~IOOPs[;#^OvYXE?3LgZYvǂ^8RX9w3χz>>GDkO= p%>;E=F u?/4B1rMGe4x>g_E]˯aߧz?[ʯF,r$璞[ǡ.8*"*86!_nRUSc%vu0}yO -vuQna{h{Eucux@AAp; Z6z}M~;}؎ţϛ~Ͼkw{V㤜jo:wim?8֭R*v-{aDSUƪqG_ɾ fhIɞt| z(ejSU{ߟ0v@_ 0 db6zboN?FOZ|dVKDu3i}jzޓ RY|>/)ekփČ9~JYݰrdu!fmqoqHIn&|fq%n=@ڌXKYyjpǺ|4{k=5D;AOu&;#D;hkvR8K5]GF_<&,^ׂz:6, 5q -WKvŏ8@½қNπѴSzfb?NnƗeI^6и2rJ흱c98sug}`VN<0nº~VD߅t+Y)nȫ21Y -w%39rw;|'^c[~铬dwMU0J^anG2&˥W?@8uC=~3T9H֓8D9cݭzަ4Sey -D2kߍIJY*je }Q7%Qd} -endstream -endobj -895 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 894 0 R -/Resources 4 0 R -/Annots [ 896 0 R 897 0 R 898 0 R 899 0 R 900 0 R 901 0 R 902 0 R 903 0 R 904 0 R 905 0 R 906 0 R 907 0 R 908 0 R 909 0 R 910 0 R 911 0 R 912 0 R 913 0 R 914 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -896 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 766.923057 101.433071 748.173057 ] -/BS << -/W 0 ->> -/Dest (cb241-1) ->> -endobj -897 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 747.976036 99.933071 729.226036 ] -/BS << -/W 0 ->> -/Dest (cb241-2) ->> -endobj -898 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 729.029014 99.933071 710.279014 ] -/BS << -/W 0 ->> -/Dest (cb241-3) ->> -endobj -899 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 710.081993 99.933071 691.331993 ] -/BS << -/W 0 ->> -/Dest (cb241-4) ->> -endobj -900 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 691.134971 99.933071 672.384971 ] -/BS << -/W 0 ->> -/Dest (cb241-5) ->> -endobj -901 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 672.187950 99.933071 653.437950 ] -/BS << -/W 0 ->> -/Dest (cb241-6) ->> -endobj -902 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 653.240928 99.933071 634.490928 ] -/BS << -/W 0 ->> -/Dest (cb241-7) ->> -endobj -903 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.293907 99.933071 615.543907 ] -/BS << -/W 0 ->> -/Dest (cb241-8) ->> -endobj -904 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 615.346885 99.933071 596.596885 ] -/BS << -/W 0 ->> -/Dest (cb241-9) ->> -endobj -905 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 596.399864 99.933071 577.649864 ] -/BS << -/W 0 ->> -/Dest (cb241-10) ->> -endobj -906 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 577.452842 99.933071 558.702842 ] -/BS << -/W 0 ->> -/Dest (cb241-11) ->> -endobj -907 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 520.611778 99.933071 501.861778 ] -/BS << -/W 0 ->> -/Dest (cb241-12) ->> -endobj -908 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 501.664756 99.933071 482.914756 ] -/BS << -/W 0 ->> -/Dest (cb241-13) ->> -endobj -909 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 482.717735 99.933071 463.967735 ] -/BS << -/W 0 ->> -/Dest (cb241-14) ->> -endobj -910 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 463.770714 99.933071 445.020714 ] -/BS << -/W 0 ->> -/Dest (cb241-15) ->> -endobj -911 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 444.823692 99.933071 426.073692 ] -/BS << -/W 0 ->> -/Dest (cb241-16) ->> -endobj -912 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 425.876671 99.933071 407.126671 ] -/BS << -/W 0 ->> -/Dest (cb241-17) ->> -endobj -913 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 406.929649 99.933071 388.179649 ] -/BS << -/W 0 ->> -/Dest (cb241-18) ->> -endobj -914 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 345.982628 101.433071 327.232628 ] -/BS << -/W 0 ->> -/Dest (cb242-1) ->> -endobj -915 0 obj -<< -/Title (RKE CIS v1.6 Benchmark - Self-Assessment Guide - Rancher v2.6) -/Dest [ 6 0 R /XYZ 85.009843 502.818898 0 ] -/Count 141 -/First 916 0 R -/Last 1052 0 R -/Parent 1057 0 R ->> -endobj -916 0 obj -<< -/Title (RKE CIS v1.6 Kubernetes Benchmark - Rancher v2.6 with Kubernetes v1.18 to v1.23) -/Dest [ 304 0 R /XYZ 84.259843 784.970079 0 ] -/Count 2 -/First 917 0 R -/Last 918 0 R -/Parent 915 0 R -/Next 919 0 R ->> -endobj -917 0 obj -<< -/Title (Overview) -/Dest [ 304 0 R /XYZ 84.259843 704.822079 0 ] -/Count 0 -/Parent 916 0 R -/Next 918 0 R ->> -endobj -918 0 obj -<< -/Title (Testing controls methodology) -/Dest [ 304 0 R /XYZ 84.259843 166.076079 0 ] -/Count 0 -/Prev 917 0 R -/Parent 916 0 R ->> -endobj -919 0 obj -<< -/Title (Controls) -/Dest [ 311 0 R /XYZ 84.259843 612.381496 0 ] -/Count 0 -/Prev 916 0 R -/Parent 915 0 R -/Next 920 0 R ->> -endobj -920 0 obj -<< -/Title (1.1 Master Node Configuration Files) -/Dest [ 315 0 R /XYZ 41.740157 784.430079 0 ] -/Count 21 -/Prev 919 0 R -/First 921 0 R -/Last 941 0 R -/Parent 915 0 R -/Next 942 0 R ->> -endobj -921 0 obj -<< -/Title (1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 315 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 920 0 R -/Next 922 0 R ->> -endobj -922 0 obj -<< -/Title (1.1.2 Ensure that the API server pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 315 0 R /XYZ 84.259843 553.851496 0 ] -/Count 0 -/Prev 921 0 R -/Parent 920 0 R -/Next 923 0 R ->> -endobj -923 0 obj -<< -/Title (1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 315 0 R /XYZ 84.259843 423.051496 0 ] -/Count 0 -/Prev 922 0 R -/Parent 920 0 R -/Next 924 0 R ->> -endobj -924 0 obj -<< -/Title (1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 315 0 R /XYZ 84.259843 277.251496 0 ] -/Count 0 -/Prev 923 0 R -/Parent 920 0 R -/Next 925 0 R ->> -endobj -925 0 obj -<< -/Title (1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 315 0 R /XYZ 84.259843 146.451496 0 ] -/Count 0 -/Prev 924 0 R -/Parent 920 0 R -/Next 926 0 R ->> -endobj -926 0 obj -<< -/Title (1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 317 0 R /XYZ 84.259843 739.970079 0 ] -/Count 0 -/Prev 925 0 R -/Parent 920 0 R -/Next 927 0 R ->> -endobj -927 0 obj -<< -/Title (1.1.7 Ensure that the etcd pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 317 0 R /XYZ 84.259843 609.170079 0 ] -/Count 0 -/Prev 926 0 R -/Parent 920 0 R -/Next 928 0 R ->> -endobj -928 0 obj -<< -/Title (1.1.8 Ensure that the etcd pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 317 0 R /XYZ 84.259843 478.370079 0 ] -/Count 0 -/Prev 927 0 R -/Parent 920 0 R -/Next 929 0 R ->> -endobj -929 0 obj -<< -/Title (1.1.9 Ensure that the Container Network Interface file permissions are set to 644 or more restrictive \(Manual\)) -/Dest [ 317 0 R /XYZ 84.259843 347.570079 0 ] -/Count 0 -/Prev 928 0 R -/Parent 920 0 R -/Next 930 0 R ->> -endobj -930 0 obj -<< -/Title (1.1.10 Ensure that the Container Network Interface file ownership is set to root:root \(Manual\)) -/Dest [ 317 0 R /XYZ 84.259843 170.823057 0 ] -/Count 0 -/Prev 929 0 R -/Parent 920 0 R -/Next 931 0 R ->> -endobj -931 0 obj -<< -/Title (1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive \(Automated\)) -/Dest [ 320 0 R /XYZ 84.259843 694.023057 0 ] -/Count 0 -/Prev 930 0 R -/Parent 920 0 R -/Next 932 0 R ->> -endobj -932 0 obj -<< -/Title (1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd \(Automated\)) -/Dest [ 320 0 R /XYZ 84.259843 365.776036 0 ] -/Count 0 -/Prev 931 0 R -/Parent 920 0 R -/Next 933 0 R ->> -endobj -933 0 obj -<< -/Title (1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 702.470079 0 ] -/Count 0 -/Prev 932 0 R -/Parent 920 0 R -/Next 934 0 R ->> -endobj -934 0 obj -<< -/Title (1.1.14 Ensure that the admin.conf file ownership is set to root:root \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 586.670079 0 ] -/Count 0 -/Prev 933 0 R -/Parent 920 0 R -/Next 935 0 R ->> -endobj -935 0 obj -<< -/Title (1.1.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 470.870079 0 ] -/Count 0 -/Prev 934 0 R -/Parent 920 0 R -/Next 936 0 R ->> -endobj -936 0 obj -<< -/Title (1.1.16 Ensure that the scheduler.conf file ownership is set to root:root \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 340.070079 0 ] -/Count 0 -/Prev 935 0 R -/Parent 920 0 R -/Next 937 0 R ->> -endobj -937 0 obj -<< -/Title (1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 209.270079 0 ] -/Count 0 -/Prev 936 0 R -/Parent 920 0 R -/Next 938 0 R ->> -endobj -938 0 obj -<< -/Title (1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root \(Automated\)) -/Dest [ 327 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 937 0 R -/Parent 920 0 R -/Next 939 0 R ->> -endobj -939 0 obj -<< -/Title (1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root \(Automated\)) -/Dest [ 327 0 R /XYZ 84.259843 668.570079 0 ] -/Count 0 -/Prev 938 0 R -/Parent 920 0 R -/Next 940 0 R ->> -endobj -940 0 obj -<< -/Title (1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 351 0 R /XYZ 84.259843 184.188585 0 ] -/Count 0 -/Prev 939 0 R -/Parent 920 0 R -/Next 941 0 R ->> -endobj -941 0 obj -<< -/Title (1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 \(Automated\)) -/Dest [ 442 0 R /XYZ 84.259843 702.470079 0 ] -/Count 0 -/Prev 940 0 R -/Parent 920 0 R ->> -endobj -942 0 obj -<< -/Title (1.2 API Server) -/Dest [ 510 0 R /XYZ 41.740157 784.430079 0 ] -/Count 35 -/Prev 920 0 R -/First 943 0 R -/Last 977 0 R -/Parent 915 0 R -/Next 978 0 R ->> -endobj -943 0 obj -<< -/Title (1.2.1 Ensure that the --anonymous-auth argument is set to false \(Automated\)) -/Dest [ 510 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 942 0 R -/Next 944 0 R ->> -endobj -944 0 obj -<< -/Title (1.2.2 Ensure that the --basic-auth-file argument is not set \(Automated\)) -/Dest [ 513 0 R /XYZ 84.259843 295.970079 0 ] -/Count 0 -/Prev 943 0 R -/Parent 942 0 R -/Next 945 0 R ->> -endobj -945 0 obj -<< -/Title (1.2.3 Ensure that the --token-auth-file parameter is not set \(Automated\)) -/Dest [ 518 0 R /XYZ 84.259843 595.970079 0 ] -/Count 0 -/Prev 944 0 R -/Parent 942 0 R -/Next 946 0 R ->> -endobj -946 0 obj -<< -/Title (1.2.4 Ensure that the --kubelet-https argument is set to true \(Automated\)) -/Dest [ 521 0 R /XYZ 84.259843 164.720079 0 ] -/Count 0 -/Prev 945 0 R -/Parent 942 0 R -/Next 947 0 R ->> -endobj -947 0 obj -<< -/Title (1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate \(Automated\)) -/Dest [ 526 0 R /XYZ 84.259843 427.220079 0 ] -/Count 0 -/Prev 946 0 R -/Parent 942 0 R -/Next 948 0 R ->> -endobj -948 0 obj -<< -/Title (1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate \(Automated\)) -/Dest [ 531 0 R /XYZ 84.259843 652.220079 0 ] -/Count 0 -/Prev 947 0 R -/Parent 942 0 R -/Next 949 0 R ->> -endobj -949 0 obj -<< -/Title (1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow \(Automated\)) -/Dest [ 534 0 R /XYZ 84.259843 183.470079 0 ] -/Count 0 -/Prev 948 0 R -/Parent 942 0 R -/Next 950 0 R ->> -endobj -950 0 obj -<< -/Title (1.2.8 Ensure that the --authorization-mode argument includes Node \(Automated\)) -/Dest [ 539 0 R /XYZ 84.259843 464.720079 0 ] -/Count 0 -/Prev 949 0 R -/Parent 942 0 R -/Next 951 0 R ->> -endobj -951 0 obj -<< -/Title (1.2.9 Ensure that the --authorization-mode argument includes RBAC \(Automated\)) -/Dest [ 544 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 950 0 R -/Parent 942 0 R -/Next 952 0 R ->> -endobj -952 0 obj -<< -/Title (1.2.10 Ensure that the admission control plugin EventRateLimit is set \(Automated\)) -/Dest [ 547 0 R /XYZ 84.259843 314.720079 0 ] -/Count 0 -/Prev 951 0 R -/Parent 942 0 R -/Next 953 0 R ->> -endobj -953 0 obj -<< -/Title (1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set \(Automated\)) -/Dest [ 552 0 R /XYZ 84.259843 520.970079 0 ] -/Count 0 -/Prev 952 0 R -/Parent 942 0 R -/Next 954 0 R ->> -endobj -954 0 obj -<< -/Title (1.2.12 Ensure that the admission control plugin AlwaysPullImages is set \(Manual\)) -/Dest [ 557 0 R /XYZ 84.259843 708.470079 0 ] -/Count 0 -/Prev 953 0 R -/Parent 942 0 R -/Next 955 0 R ->> -endobj -955 0 obj -<< -/Title (1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used \(Manual\)) -/Dest [ 557 0 R /XYZ 84.259843 501.723057 0 ] -/Count 0 -/Prev 954 0 R -/Parent 942 0 R -/Next 956 0 R ->> -endobj -956 0 obj -<< -/Title (1.2.14 Ensure that the admission control plugin ServiceAccount is set \(Automated\)) -/Dest [ 557 0 R /XYZ 84.259843 264.976036 0 ] -/Count 0 -/Prev 955 0 R -/Parent 942 0 R -/Next 957 0 R ->> -endobj -957 0 obj -<< -/Title (1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set \(Automated\)) -/Dest [ 564 0 R /XYZ 84.259843 520.970079 0 ] -/Count 0 -/Prev 956 0 R -/Parent 942 0 R -/Next 958 0 R ->> -endobj -958 0 obj -<< -/Title (1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set \(Automated\)) -/Dest [ 569 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 957 0 R -/Parent 942 0 R -/Next 959 0 R ->> -endobj -959 0 obj -<< -/Title (1.2.17 Ensure that the admission control plugin NodeRestriction is set \(Automated\)) -/Dest [ 572 0 R /XYZ 84.259843 258.470079 0 ] -/Count 0 -/Prev 958 0 R -/Parent 942 0 R -/Next 960 0 R ->> -endobj -960 0 obj -<< -/Title (1.2.18 Ensure that the --insecure-bind-address argument is not set \(Automated\)) -/Dest [ 577 0 R /XYZ 84.259843 427.220079 0 ] -/Count 0 -/Prev 959 0 R -/Parent 942 0 R -/Next 961 0 R ->> -endobj -961 0 obj -<< -/Title (1.2.19 Ensure that the --insecure-port argument is set to 0 \(Automated\)) -/Dest [ 582 0 R /XYZ 84.259843 727.220079 0 ] -/Count 0 -/Prev 960 0 R -/Parent 942 0 R -/Next 962 0 R ->> -endobj -962 0 obj -<< -/Title (1.2.20 Ensure that the --secure-port argument is not set to 0 \(Automated\)) -/Dest [ 585 0 R /XYZ 84.259843 314.720079 0 ] -/Count 0 -/Prev 961 0 R -/Parent 942 0 R -/Next 963 0 R ->> -endobj -963 0 obj -<< -/Title (1.2.21 Ensure that the --profiling argument is set to false \(Automated\)) -/Dest [ 590 0 R /XYZ 84.259843 595.970079 0 ] -/Count 0 -/Prev 962 0 R -/Parent 942 0 R -/Next 964 0 R ->> -endobj -964 0 obj -<< -/Title (1.2.22 Ensure that the --audit-log-path argument is set \(Automated\)) -/Dest [ 593 0 R /XYZ 84.259843 183.470079 0 ] -/Count 0 -/Prev 963 0 R -/Parent 942 0 R -/Next 965 0 R ->> -endobj -965 0 obj -<< -/Title (1.2.23 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate \(Automated\)) -/Dest [ 598 0 R /XYZ 84.259843 445.970079 0 ] -/Count 0 -/Prev 964 0 R -/Parent 942 0 R -/Next 966 0 R ->> -endobj -966 0 obj -<< -/Title (1.2.24 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate \(Automated\)) -/Dest [ 603 0 R /XYZ 84.259843 727.220079 0 ] -/Count 0 -/Prev 965 0 R -/Parent 942 0 R -/Next 967 0 R ->> -endobj -967 0 obj -<< -/Title (1.2.25 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate \(Automated\)) -/Dest [ 606 0 R /XYZ 84.259843 295.970079 0 ] -/Count 0 -/Prev 966 0 R -/Parent 942 0 R -/Next 968 0 R ->> -endobj -968 0 obj -<< -/Title (1.2.26 Ensure that the --request-timeout argument is set as appropriate \(Automated\)) -/Dest [ 611 0 R /XYZ 84.259843 595.970079 0 ] -/Count 0 -/Prev 967 0 R -/Parent 942 0 R -/Next 969 0 R ->> -endobj -969 0 obj -<< -/Title (1.2.27 Ensure that the --service-account-lookup argument is set to true \(Automated\)) -/Dest [ 614 0 R /XYZ 84.259843 164.720079 0 ] -/Count 0 -/Prev 968 0 R -/Parent 942 0 R -/Next 970 0 R ->> -endobj -970 0 obj -<< -/Title (1.2.28 Ensure that the --service-account-key-file argument is set as appropriate \(Automated\)) -/Dest [ 619 0 R /XYZ 84.259843 408.470079 0 ] -/Count 0 -/Prev 969 0 R -/Parent 942 0 R -/Next 971 0 R ->> -endobj -971 0 obj -<< -/Title (1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate \(Automated\)) -/Dest [ 624 0 R /XYZ 84.259843 689.720079 0 ] -/Count 0 -/Prev 970 0 R -/Parent 942 0 R -/Next 972 0 R ->> -endobj -972 0 obj -<< -/Title (1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate \(Automated\)) -/Dest [ 627 0 R /XYZ 84.259843 239.720079 0 ] -/Count 0 -/Prev 971 0 R -/Parent 942 0 R -/Next 973 0 R ->> -endobj -973 0 obj -<< -/Title (1.2.31 Ensure that the --client-ca-file argument is set as appropriate \(Automated\)) -/Dest [ 632 0 R /XYZ 84.259843 483.470079 0 ] -/Count 0 -/Prev 972 0 R -/Parent 942 0 R -/Next 974 0 R ->> -endobj -974 0 obj -<< -/Title (1.2.32 Ensure that the --etcd-cafile argument is set as appropriate \(Automated\)) -/Dest [ 637 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 973 0 R -/Parent 942 0 R -/Next 975 0 R ->> -endobj -975 0 obj -<< -/Title (1.2.33 Ensure that the --encryption-provider-config argument is set as appropriate \(Automated\)) -/Dest [ 640 0 R /XYZ 84.259843 295.970079 0 ] -/Count 0 -/Prev 974 0 R -/Parent 942 0 R -/Next 976 0 R ->> -endobj -976 0 obj -<< -/Title (1.2.34 Ensure that encryption providers are appropriately configured \(Automated\)) -/Dest [ 645 0 R /XYZ 84.259843 577.220079 0 ] -/Count 0 -/Prev 975 0 R -/Parent 942 0 R -/Next 977 0 R ->> -endobj -977 0 obj -<< -/Title (1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers \(Automated\)) -/Dest [ 662 0 R /XYZ 84.259843 411.552842 0 ] -/Count 0 -/Prev 976 0 R -/Parent 942 0 R ->> -endobj -978 0 obj -<< -/Title (1.3 Controller Manager) -/Dest [ 676 0 R /XYZ 41.740157 784.430079 0 ] -/Count 7 -/Prev 942 0 R -/First 979 0 R -/Last 985 0 R -/Parent 915 0 R -/Next 986 0 R ->> -endobj -979 0 obj -<< -/Title (1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate \(Automated\)) -/Dest [ 676 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 978 0 R -/Next 980 0 R ->> -endobj -980 0 obj -<< -/Title (1.3.2 Ensure that the --profiling argument is set to false \(Automated\)) -/Dest [ 679 0 R /XYZ 84.259843 727.220079 0 ] -/Count 0 -/Prev 979 0 R -/Parent 978 0 R -/Next 981 0 R ->> -endobj -981 0 obj -<< -/Title (1.3.3 Ensure that the --use-service-account-credentials argument is set to true \(Automated\)) -/Dest [ 682 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 980 0 R -/Parent 978 0 R -/Next 982 0 R ->> -endobj -982 0 obj -<< -/Title (1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate \(Automated\)) -/Dest [ 685 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 981 0 R -/Parent 978 0 R -/Next 983 0 R ->> -endobj -983 0 obj -<< -/Title (1.3.5 Ensure that the --root-ca-file argument is set as appropriate \(Automated\)) -/Dest [ 688 0 R /XYZ 84.259843 727.220079 0 ] -/Count 0 -/Prev 982 0 R -/Parent 978 0 R -/Next 984 0 R ->> -endobj -984 0 obj -<< -/Title (1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true \(Automated\)) -/Dest [ 691 0 R /XYZ 84.259843 727.220079 0 ] -/Count 0 -/Prev 983 0 R -/Parent 978 0 R -/Next 985 0 R ->> -endobj -985 0 obj -<< -/Title (1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1 \(Automated\)) -/Dest [ 691 0 R /XYZ 84.259843 524.420079 0 ] -/Count 0 -/Prev 984 0 R -/Parent 978 0 R ->> -endobj -986 0 obj -<< -/Title (1.4 Scheduler) -/Dest [ 696 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 978 0 R -/First 987 0 R -/Last 988 0 R -/Parent 915 0 R -/Next 989 0 R ->> -endobj -987 0 obj -<< -/Title (1.4.1 Ensure that the --profiling argument is set to false \(Automated\)) -/Dest [ 696 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 986 0 R -/Next 988 0 R ->> -endobj -988 0 obj -<< -/Title (1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1 \(Automated\)) -/Dest [ 696 0 R /XYZ 84.259843 257.404475 0 ] -/Count 0 -/Prev 987 0 R -/Parent 986 0 R ->> -endobj -989 0 obj -<< -/Title (2 Etcd Node Configuration Files) -/Dest [ 702 0 R /XYZ 41.740157 784.430079 0 ] -/Count 7 -/Prev 986 0 R -/First 990 0 R -/Last 996 0 R -/Parent 915 0 R -/Next 997 0 R ->> -endobj -990 0 obj -<< -/Title (2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate \(Automated\)) -/Dest [ 702 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 989 0 R -/Next 991 0 R ->> -endobj -991 0 obj -<< -/Title (2.2 Ensure that the --client-cert-auth argument is set to true \(Automated\)) -/Dest [ 707 0 R /XYZ 84.259843 464.720079 0 ] -/Count 0 -/Prev 990 0 R -/Parent 989 0 R -/Next 992 0 R ->> -endobj -992 0 obj -<< -/Title (2.3 Ensure that the --auto-tls argument is not set to true \(Automated\)) -/Dest [ 712 0 R /XYZ 84.259843 258.470079 0 ] -/Count 0 -/Prev 991 0 R -/Parent 989 0 R -/Next 993 0 R ->> -endobj -993 0 obj -<< -/Title (2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate \(Automated\)) -/Dest [ 719 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 992 0 R -/Parent 989 0 R -/Next 994 0 R ->> -endobj -994 0 obj -<< -/Title (2.5 Ensure that the --peer-client-cert-auth argument is set to true \(Automated\)) -/Dest [ 724 0 R /XYZ 84.259843 558.470079 0 ] -/Count 0 -/Prev 993 0 R -/Parent 989 0 R -/Next 995 0 R ->> -endobj -995 0 obj -<< -/Title (2.6 Ensure that the --peer-auto-tls argument is not set to true \(Automated\)) -/Dest [ 729 0 R /XYZ 84.259843 333.470079 0 ] -/Count 0 -/Prev 994 0 R -/Parent 989 0 R -/Next 996 0 R ->> -endobj -996 0 obj -<< -/Title (2.7 Ensure that a unique Certificate Authority is used for etcd \(Automated\)) -/Dest [ 736 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 995 0 R -/Parent 989 0 R ->> -endobj -997 0 obj -<< -/Title (3.1 Authentication and Authorization) -/Dest [ 743 0 R /XYZ 41.740157 784.430079 0 ] -/Count 1 -/Prev 989 0 R -/First 998 0 R -/Last 998 0 R -/Parent 915 0 R -/Next 999 0 R ->> -endobj -998 0 obj -<< -/Title (3.1.1 Client certificate authentication should not be used for users \(Manual\)) -/Dest [ 743 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 997 0 R ->> -endobj -999 0 obj -<< -/Title (3.2 Logging) -/Dest [ 745 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 997 0 R -/First 1000 0 R -/Last 1001 0 R -/Parent 915 0 R -/Next 1002 0 R ->> -endobj -1000 0 obj -<< -/Title (3.2.1 Ensure that a minimal audit policy is created \(Automated\)) -/Dest [ 745 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 999 0 R -/Next 1001 0 R ->> -endobj -1001 0 obj -<< -/Title (3.2.2 Ensure that the audit policy covers key security concerns \(Manual\)) -/Dest [ 748 0 R /XYZ 84.259843 333.470079 0 ] -/Count 0 -/Prev 1000 0 R -/Parent 999 0 R ->> -endobj -1002 0 obj -<< -/Title (4.1 Worker Node Configuration Files) -/Dest [ 750 0 R /XYZ 41.740157 784.430079 0 ] -/Count 10 -/Prev 999 0 R -/First 1003 0 R -/Last 1012 0 R -/Parent 915 0 R -/Next 1013 0 R ->> -endobj -1003 0 obj -<< -/Title (4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 750 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 1002 0 R -/Next 1004 0 R ->> -endobj -1004 0 obj -<< -/Title (4.1.2 Ensure that the kubelet service file ownership is set to root:root \(Automated\)) -/Dest [ 750 0 R /XYZ 84.259843 553.851496 0 ] -/Count 0 -/Prev 1003 0 R -/Parent 1002 0 R -/Next 1005 0 R ->> -endobj -1005 0 obj -<< -/Title (4.1.3 If proxy kubeconfig file exists ensure permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 750 0 R /XYZ 84.259843 423.051496 0 ] -/Count 0 -/Prev 1004 0 R -/Parent 1002 0 R -/Next 1006 0 R ->> -endobj -1006 0 obj -<< -/Title (4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root \(Automated\)) -/Dest [ 753 0 R /XYZ 84.259843 763.220079 0 ] -/Count 0 -/Prev 1005 0 R -/Parent 1002 0 R -/Next 1007 0 R ->> -endobj -1007 0 obj -<< -/Title (4.1.5 Ensure that the --kubeconfig kubelet.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 753 0 R /XYZ 84.259843 454.079014 0 ] -/Count 0 -/Prev 1006 0 R -/Parent 1002 0 R -/Next 1008 0 R ->> -endobj -1008 0 obj -<< -/Title (4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root \(Automated\)) -/Dest [ 753 0 R /XYZ 84.259843 163.687950 0 ] -/Count 0 -/Prev 1007 0 R -/Parent 1002 0 R -/Next 1009 0 R ->> -endobj -1009 0 obj -<< -/Title (4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 757 0 R /XYZ 84.259843 519.629014 0 ] -/Count 0 -/Prev 1008 0 R -/Parent 1002 0 R -/Next 1010 0 R ->> -endobj -1010 0 obj -<< -/Title (4.1.8 Ensure that the client certificate authorities file ownership is set to root:root \(Automated\)) -/Dest [ 766 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 1009 0 R -/Parent 1002 0 R -/Next 1011 0 R ->> -endobj -1011 0 obj -<< -/Title (4.1.9 Ensure that the kubelet --config configuration file has permissions set to 644 or more restrictive \(Automated\)) -/Dest [ 766 0 R /XYZ 84.259843 383.493907 0 ] -/Count 0 -/Prev 1010 0 R -/Parent 1002 0 R -/Next 1012 0 R ->> -endobj -1012 0 obj -<< -/Title (4.1.10 Ensure that the kubelet --config configuration file ownership is set to root:root \(Automated\)) -/Dest [ 766 0 R /XYZ 84.259843 195.693907 0 ] -/Count 0 -/Prev 1011 0 R -/Parent 1002 0 R ->> -endobj -1013 0 obj -<< -/Title (4.2 Kubelet) -/Dest [ 776 0 R /XYZ 41.740157 784.430079 0 ] -/Count 13 -/Prev 1002 0 R -/First 1014 0 R -/Last 1026 0 R -/Parent 915 0 R -/Next 1027 0 R ->> -endobj -1014 0 obj -<< -/Title (4.2.1 Ensure that the anonymous-auth argument is set to false \(Automated\)) -/Dest [ 776 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 1013 0 R -/Next 1015 0 R ->> -endobj -1015 0 obj -<< -/Title (4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow \(Automated\)) -/Dest [ 776 0 R /XYZ 84.259843 332.207453 0 ] -/Count 0 -/Prev 1014 0 R -/Parent 1013 0 R -/Next 1016 0 R ->> -endobj -1016 0 obj -<< -/Title (4.2.3 Ensure that the --client-ca-file argument is set as appropriate \(Automated\)) -/Dest [ 781 0 R /XYZ 84.259843 675.273057 0 ] -/Count 0 -/Prev 1015 0 R -/Parent 1013 0 R -/Next 1017 0 R ->> -endobj -1017 0 obj -<< -/Title (4.2.4 Ensure that the --read-only-port argument is set to 0 \(Automated\)) -/Dest [ 781 0 R /XYZ 84.259843 301.829014 0 ] -/Count 0 -/Prev 1016 0 R -/Parent 1013 0 R -/Next 1018 0 R ->> -endobj -1018 0 obj -<< -/Title (4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0 \(Automated\)) -/Dest [ 786 0 R /XYZ 84.259843 641.326036 0 ] -/Count 0 -/Prev 1017 0 R -/Parent 1013 0 R -/Next 1019 0 R ->> -endobj -1019 0 obj -<< -/Title (4.2.6 Ensure that the --protect-kernel-defaults argument is set to true \(Automated\)) -/Dest [ 792 0 R /XYZ 84.259843 445.970079 0 ] -/Count 0 -/Prev 1018 0 R -/Parent 1013 0 R -/Next 1020 0 R ->> -endobj -1020 0 obj -<< -/Title (4.2.7 Ensure that the --make-iptables-util-chains argument is set to true \(Automated\)) -/Dest [ 796 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 1019 0 R -/Parent 1013 0 R -/Next 1021 0 R ->> -endobj -1021 0 obj -<< -/Title (4.2.8 Ensure that the --hostname-override argument is not set \(Manual\)) -/Dest [ 796 0 R /XYZ 84.259843 425.926036 0 ] -/Count 0 -/Prev 1020 0 R -/Parent 1013 0 R -/Next 1022 0 R ->> -endobj -1022 0 obj -<< -/Title (4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture \(Automated\)) -/Dest [ 796 0 R /XYZ 84.259843 208.126036 0 ] -/Count 0 -/Prev 1021 0 R -/Parent 1013 0 R -/Next 1023 0 R ->> -endobj -1023 0 obj -<< -/Title (4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate \(Automated\)) -/Dest [ 800 0 R /XYZ 84.259843 542.326036 0 ] -/Count 0 -/Prev 1022 0 R -/Parent 1013 0 R -/Next 1024 0 R ->> -endobj -1024 0 obj -<< -/Title (4.2.11 Ensure that the --rotate-certificates argument is not set to false \(Automated\)) -/Dest [ 800 0 R /XYZ 84.259843 138.881993 0 ] -/Count 0 -/Prev 1023 0 R -/Parent 1013 0 R -/Next 1025 0 R ->> -endobj -1025 0 obj -<< -/Title (4.2.12 Verify that the RotateKubeletServerCertificate argument is set to true \(Automated\)) -/Dest [ 810 0 R /XYZ 84.259843 670.970079 0 ] -/Count 0 -/Prev 1024 0 R -/Parent 1013 0 R -/Next 1026 0 R ->> -endobj -1026 0 obj -<< -/Title (4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers \(Automated\)) -/Dest [ 810 0 R /XYZ 84.259843 392.223057 0 ] -/Count 0 -/Prev 1025 0 R -/Parent 1013 0 R ->> -endobj -1027 0 obj -<< -/Title (5.1 RBAC and Service Accounts) -/Dest [ 817 0 R /XYZ 41.740157 784.430079 0 ] -/Count 6 -/Prev 1013 0 R -/First 1028 0 R -/Last 1033 0 R -/Parent 915 0 R -/Next 1034 0 R ->> -endobj -1028 0 obj -<< -/Title (5.1.1 Ensure that the cluster-admin role is only used where required \(Manual\)) -/Dest [ 817 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 1027 0 R -/Next 1029 0 R ->> -endobj -1029 0 obj -<< -/Title (5.1.2 Minimize access to secrets \(Manual\)) -/Dest [ 817 0 R /XYZ 84.259843 523.851496 0 ] -/Count 0 -/Prev 1028 0 R -/Parent 1027 0 R -/Next 1030 0 R ->> -endobj -1030 0 obj -<< -/Title (5.1.3 Minimize wildcard use in Roles and ClusterRoles \(Manual\)) -/Dest [ 817 0 R /XYZ 84.259843 423.051496 0 ] -/Count 0 -/Prev 1029 0 R -/Parent 1027 0 R -/Next 1031 0 R ->> -endobj -1031 0 obj -<< -/Title (5.1.4 Minimize access to create pods \(Manual\)) -/Dest [ 817 0 R /XYZ 84.259843 307.251496 0 ] -/Count 0 -/Prev 1030 0 R -/Parent 1027 0 R -/Next 1032 0 R ->> -endobj -1032 0 obj -<< -/Title (5.1.5 Ensure that default service accounts are not actively used. \(Automated\)) -/Dest [ 817 0 R /XYZ 84.259843 206.451496 0 ] -/Count 0 -/Prev 1031 0 R -/Parent 1027 0 R -/Next 1033 0 R ->> -endobj -1033 0 obj -<< -/Title (5.1.6 Ensure that Service Account Tokens are only mounted where necessary \(Manual\)) -/Dest [ 844 0 R /XYZ 84.259843 449.446885 0 ] -/Count 0 -/Prev 1032 0 R -/Parent 1027 0 R ->> -endobj -1034 0 obj -<< -/Title (5.2 Pod Security Policies) -/Dest [ 855 0 R /XYZ 41.740157 784.430079 0 ] -/Count 9 -/Prev 1027 0 R -/First 1035 0 R -/Last 1043 0 R -/Parent 915 0 R -/Next 1044 0 R ->> -endobj -1035 0 obj -<< -/Title (5.2.1 Minimize the admission of privileged containers \(Manual\)) -/Dest [ 855 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 1034 0 R -/Next 1036 0 R ->> -endobj -1036 0 obj -<< -/Title (5.2.2 Minimize the admission of containers wishing to share the host process ID namespace \(Automated\)) -/Dest [ 855 0 R /XYZ 84.259843 589.851496 0 ] -/Count 0 -/Prev 1035 0 R -/Parent 1034 0 R -/Next 1037 0 R ->> -endobj -1037 0 obj -<< -/Title (5.2.3 Minimize the admission of containers wishing to share the host IPC namespace \(Automated\)) -/Dest [ 855 0 R /XYZ 84.259843 238.710432 0 ] -/Count 0 -/Prev 1036 0 R -/Parent 1034 0 R -/Next 1038 0 R ->> -endobj -1038 0 obj -<< -/Title (5.2.4 Minimize the admission of containers wishing to share the host network namespace \(Automated\)) -/Dest [ 858 0 R /XYZ 84.259843 603.629014 0 ] -/Count 0 -/Prev 1037 0 R -/Parent 1034 0 R -/Next 1039 0 R ->> -endobj -1039 0 obj -<< -/Title (5.2.5 Minimize the admission of containers with allowPrivilegeEscalation \(Automated\)) -/Dest [ 858 0 R /XYZ 84.259843 252.487950 0 ] -/Count 0 -/Prev 1038 0 R -/Parent 1034 0 R -/Next 1040 0 R ->> -endobj -1040 0 obj -<< -/Title (5.2.6 Minimize the admission of root containers \(Manual\)) -/Dest [ 862 0 R /XYZ 84.259843 584.681993 0 ] -/Count 0 -/Prev 1039 0 R -/Parent 1034 0 R -/Next 1041 0 R ->> -endobj -1041 0 obj -<< -/Title (5.2.7 Minimize the admission of containers with the NET_RAW capability \(Manual\)) -/Dest [ 862 0 R /XYZ 84.259843 453.881993 0 ] -/Count 0 -/Prev 1040 0 R -/Parent 1034 0 R -/Next 1042 0 R ->> -endobj -1042 0 obj -<< -/Title (5.2.8 Minimize the admission of containers with added capabilities \(Manual\)) -/Dest [ 862 0 R /XYZ 84.259843 323.081993 0 ] -/Count 0 -/Prev 1041 0 R -/Parent 1034 0 R -/Next 1043 0 R ->> -endobj -1043 0 obj -<< -/Title (5.2.9 Minimize the admission of containers with capabilities assigned \(Manual\)) -/Dest [ 862 0 R /XYZ 84.259843 207.281993 0 ] -/Count 0 -/Prev 1042 0 R -/Parent 1034 0 R ->> -endobj -1044 0 obj -<< -/Title (5.3 Network Policies and CNI) -/Dest [ 865 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 1034 0 R -/First 1045 0 R -/Last 1046 0 R -/Parent 915 0 R -/Next 1047 0 R ->> -endobj -1045 0 obj -<< -/Title (5.3.1 Ensure that the CNI in use supports Network Policies \(Manual\)) -/Dest [ 865 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 1044 0 R -/Next 1046 0 R ->> -endobj -1046 0 obj -<< -/Title (5.3.2 Ensure that all Namespaces have Network Policies defined \(Automated\)) -/Dest [ 865 0 R /XYZ 84.259843 538.851496 0 ] -/Count 0 -/Prev 1045 0 R -/Parent 1044 0 R ->> -endobj -1047 0 obj -<< -/Title (5.4 Secrets Management) -/Dest [ 889 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 1044 0 R -/First 1048 0 R -/Last 1049 0 R -/Parent 915 0 R -/Next 1050 0 R ->> -endobj -1048 0 obj -<< -/Title (5.4.1 Prefer using secrets as files over secrets as environment variables \(Manual\)) -/Dest [ 889 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 1047 0 R -/Next 1049 0 R ->> -endobj -1049 0 obj -<< -/Title (5.4.2 Consider external secret storage \(Manual\)) -/Dest [ 889 0 R /XYZ 84.259843 568.851496 0 ] -/Count 0 -/Prev 1048 0 R -/Parent 1047 0 R ->> -endobj -1050 0 obj -<< -/Title (5.5 Extensible Admission Control) -/Dest [ 891 0 R /XYZ 41.740157 784.430079 0 ] -/Count 1 -/Prev 1047 0 R -/First 1051 0 R -/Last 1051 0 R -/Parent 915 0 R -/Next 1052 0 R ->> -endobj -1051 0 obj -<< -/Title (5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller \(Manual\)) -/Dest [ 891 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 1050 0 R ->> -endobj -1052 0 obj -<< -/Title (5.7 General Policies) -/Dest [ 893 0 R /XYZ 41.740157 784.430079 0 ] -/Count 4 -/Prev 1050 0 R -/First 1053 0 R -/Last 1056 0 R -/Parent 915 0 R ->> -endobj -1053 0 obj -<< -/Title (5.7.1 Create administrative boundaries between resources using namespaces \(Manual\)) -/Dest [ 893 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 1052 0 R -/Next 1054 0 R ->> -endobj -1054 0 obj -<< -/Title (5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions \(Manual\)) -/Dest [ 893 0 R /XYZ 84.259843 604.851496 0 ] -/Count 0 -/Prev 1053 0 R -/Parent 1052 0 R -/Next 1055 0 R ->> -endobj -1055 0 obj -<< -/Title (5.7.3 Apply Security Context to Your Pods and Containers \(Manual\)) -/Dest [ 893 0 R /XYZ 84.259843 324.051496 0 ] -/Count 0 -/Prev 1054 0 R -/Parent 1052 0 R -/Next 1056 0 R ->> -endobj -1056 0 obj -<< -/Title (5.7.4 The default namespace should not be used \(Automated\)) -/Dest [ 893 0 R /XYZ 84.259843 193.251496 0 ] -/Count 0 -/Prev 1055 0 R -/Parent 1052 0 R ->> -endobj -1057 0 obj -<< -/Count 142 -/First 915 0 R -/Last 915 0 R ->> -endobj -1058 0 obj -<< -/Length1 41480 -/Filter /FlateDecode -/Length 7851 ->> -stream -x| xUԭ^tg_:{– AlbpM Ba#IP""b@ @DQDdgܞ 8L@ƤNU'!8㛙{osV})`D鹹o{ c7#sv)KoʻeB'״RsӄIϽR*@}$ݿ|󰉣C3 2!-cw/`MԾ}܂R|Yzav t.ut׬R0cmuҢ:xfAa_G]L'ʨ s޻[r]4~(XQJO-4Ώ;I(¿ ,Ҽ">_]1ԮWK!qQezǵobרn8tķ5K0u]pWu:CZ9^P/`< {{B```````````````````k VBHM5=7LJPCW/_@dÍ0n0&@l(ŝp 361a,<᏿p$ 9~^G#O]u)uٙ7YSEd#&*Rb?uM6vѵ7a2UuS=mFH3:cė:P͍'w:֎ߨxYLĿ:_=8L|:Pm6_/y >s4gݻB϶NQqOpOm2p,zR_[UMlQ >XxfnF7 *`-MGGS;>܆k*TO5fTDQ= }ү!׭ ֩v>Hl>8 XEX:* q5Iju"r/U\)V‰\ -}XLBeB,xKU׎Kl؂T\؆em a%*SX 8[e8E*TP*NW`06*NUqd҆-0 ]I8уCLx qyVE7;xov8ҝ*cptTQxu8Gx#/nlqX8Twx}Nޅ9CD3`x@ f;@7fgYExm4f`5V5VLOLf1/I} OKIT$'aIVVLP1^Ÿ@%>c]-Ę6& 1*#I*Fap FB -Q1&GEA*hKE'eXvl"@EUE**4LQF%)xzQ%?2zX4 Wg;}u>} -Qko\S4N`l dR/{e6 2HmRt^: 2餔/L&n;7_.81>28_b&H#$;|'>]ya;-nVF=ILXBO-Qw3%> -3 VD^A9h43I 0 /t⌎v&m]4`VSsURS~ `>Tڛ9r[JkXΗHMi5h6}~Kd4*T'Mc4O+%wS>uPM+ŷ4qS⹚=Ŀ8RH} W5'!X&9 / $RO66UPE:6ah~2@ 4@ 4@ 4@ 4@ 4@ 4@ 4@ 4@ 4@/kVu5[0(d -q.1} 8Nzb yD|vmTU{VrHkM)UqHSެȑ18=1pfnJQ"[iױ&Oc1P:EVb(QuӾA*4L-PG #04)$p -! w<|4޽^z gQc'1=;_nӭt N!.p "|0R.EȅX^^0r["bENlumR|l̐X ~Qo[.g ؘD:29.jHL';OI8!G4'{̓Dsht@lF0߾f5cq{T}s>eBڡ^dy,bc8ж'~r!)!IϦ_OCl)Ξw I8Я}Ij)$)sZNuhQM 0 b/1 PsΝn%FjEW}^c|Y 4*0C))\Fl2ϳb^ߏ %{J/m䛰N -g,exxޢ^j|;k:ZsF;pO[_V>@u8W ^sVky.iUxPX{d`HKNC9HW]:^A.Hi]0R|,{x'R[XGׯTr|kV/?QuxzCɂ;^[=:ϊdҿ0V /gS=Q}O=v]Fb[zQIq-I -|VR+=glHlAV]Ώu ߵ 4 gx^Ko9Z@t ҰgOB|Ѻ/ LK2I07)Y"Od9ɔ$,\^,IĒ5Fy)FsP!AHwz5~ +{/Y{o7R}B-fu;ęw!~Kʕ+WiSIiI2—`v+Vd11-ZT &HXc"Lfo -sǥ8>z.xrsgoof/>0{3cwO~72w/]oKt/$B $1 NCMu!6bA=2NӭN菞N -4:hy^zTztzL7=6=nh/y}輘wQPʆ򡞡)MI3@ +%c{dG*MMRE>Ƀw>ws135ln;9v{c1 ůՏnؿgiw$ fSY%l-dY(qn-xYeՂF^9Gt9Gb5'S-Ԕ8fqK{S^4}ûCCt] C3ɕvgmqk|V=̑8]{+ީ*NR¦|D -\0E\NT㲽aR3jCxֳ/JWs?z|-y΋, -^%~<)Ң6RNdI})>c -WIU!̛qL5 /ߤKR`ey_:9:5l<#q pt:⒐B#[de"$e 9UFy)%agyN%0/2T ύ׃v{{1'圣"Jj _N83L낧~\Q_QRG# Uh^C޷ _g<6|˶^~R3kݧ]HQ>~ֶc=׭=-m3-}c|Ar mMufW Q'?4 -SRaTXm -GUv)ygrs^={W#w?rԋVbNxؗorC۸u~ +[$Xio2,JAn[/O9yA[4$H !8&ftǟin|hUЀHr8ұQ4Cڭ1-w>R WRwU{*TwMWr"IqǍLѨ:}UC-}SHLrn%i@nmyeu/K)k4wOpJtJL756!yeumuK{3Ĺlhc :0 1#(srZԻR+R֤֧^J r,-Yq׎9jC>?N}힢7 -V˷k')/ ݓ2qotϦʚrؼ[vGkZ>_rvd-JJ2p5-Co=Z4 "IYl +WW-{3*+U7o}W4＇|n_n⋼ba,d#r[Ǔz4רs=fVyE3 ~̞kjqWde[l?.q wj_O6^! ?8B 2wy8Gx=r&$0io,=O~K/ _!w^3"+_wr^W|=m#3gp bU R l4r(٧)8ES,Q,+`!+rz*O^XVQb)CrkӨlYD)5T*ljáY=x%ӂ(*%$ПbshZnH_#£1C$D "Zٮ+$"&'e X-\gdq:Z3]90{`ϼRHx<~%|&ήG&'E%kn7k[:wI08C݊ a܋31] B#:y-igrCmWG_O{E=<}.=gC)Lվ2$tCZA0u -c~W]@(U͊F(RX - `6̂bX^H^ȀtLM^NcBL(ЏzG<?jB/ֳVޚIי4g14/ݳDi1}`(9ގ#v7ͻ Kj3:G^Ze4f:;yi~ ^:Uʈ"z9ԫZifuA:H'Nxg>R%–ʞv3AQ9(cyF.|FRNRGBY$qFt2ΔXGx&I0Xޠim? >"wDSp_V5m$3s<{\gm$r -4/S(Jq}0ZQvk, ]tn5bsks;{J/+y/ Iw{WOWAIޙv.(M=t; i.ΠًfaȲídSEqHi\ٮfnd&4Qd5 ʹx[ mdh)fcH*_5B"b%f'5pP .`zj-ܺ︯`At)X0wL_P0jf+x*.jf,3@Mq<S> -stream -x9yxSU眛&-Phڦ P&鞦M=ݒ%;m)ԲU*ꌈ́<A?(.7#3Qtt|3r~&--?枞{9wo9#fAzsi˸ڱ -yBpEgVJU74Ba3ֿ]#$r#;kRsja \lR h"4wh c{|a'Ŕ^_O\"4]{o HyDy`5`s /A@7[F({& Z -Q<A -*jPj>u|͏?1P||E;-(g -a| )M R0dZ;1 DBQ -CrX|''잰aB a0 -hT`JCe '*Pb -P$kl\TB4jm@GD`\(Dk5j j d uڊp_:ЕmT>Y-(+ o)^ *V8eBKTgE|#; -D-", -S5Q_<[WJa5x?/rs_`1ԵQA):xihB[%$j8ظ8Vjt}wqW#5fl4dޫyמن+klkjo"?Bd"FÊd˟ #X)+HD1vH&i)d3U-mM#[E -sߚfמG1=pD@SMDP(j6XsVCnYxm2Y[y: 5Ȱ:GG5aͶ:pNkA~*rMCpr̊Y,%=E(ٿPdwi$2vded:_Zv'kWwlY֗kJcd녅Kz,5Y -v Q:G"8 L:!b@|gÿZY]]mk5]9RMR'uu~c{`,{@nfjʕ ^4&5^ύ]AK Z7"T'N.dT -! -nv9]:Ϊ_p[txVUhp}Zq:kv|;W[ɲJIL - 2EzWAj)"7䦜P!JKVHs OmwYv\w6?ftڻ<|voZE-dkL='=}4kJzߑpߊ'v1P{Rs=rq$WH%IH!ߜL&xwNٺڈϨ*X֭RYB7tiͮ! S%ii@Zf-s 67ljwA)2RpKNI0Xd\[Z|{A]JIZOkp2OFJIiSE"lWVS{q-# &h,͚$ ++9Nٕ -GVwם(p7S`$bn ^tY3^B"TWV*VAT :p2l&z|0欚rSCR4ʚ۠@T=Y6t>[2Y?~Q'p[#u+~t Rޣ5Pmf/蜯 g5׀̓A7@j\ ;}F^paR^p?(~grC<; a0 kʊnduK; &˳{g%]nM@J0!q$+yS}ⳁ^oXӗktK^TTb4[XMNɼ⮃J -餩k9SK= nv +`ܵy}ѣm?sicz&#`_bb|]-G p23v < -Sp$Ov9 ̡A - - M=- z29Á-##?_ӦroτNh>Cmo!@}h Ԇ D<JB䆑hKy>E+t\Nb%ʆ -{wP#fMtWͰvƦZrSp|7(4s BR5`N2 ةp7O9-߀ih.6n_<|`2-Uh>}f*,<H! -endstream -endobj -1060 0 obj -<< -/Length1 47128 -/Filter /FlateDecode -/Length 11769 ->> -stream -x} xEpU]==w23$3 2b p!"`pA@s1bVA\p]ED?A]7".Փ@`uwz$ 8,kȍV>E ð6wA^ _{Vx>-8֫aB^j/tKim3[~iRGȠw~;fr{ aCJ'Lɦ'rBrbA$/ {ۄsK ]s&dʼn%C=ayDp~'NuxGjߙZ6m"diw_a˱bl^|~Ư "4bwqvp*|?E\`[$Cg&R W׿-7{j;d  -F\$= EPVcMoӢg8| -cliҞI/Q#F%cx<(<£~9kc퉡^~{,糉اf9\_K* g^J=RgGid#RJ6l"l?oM!~,Q -@Y&eYK=(%N杼o^Ǚ:|45P;Gn~P\uVj Ofb3Kxf3kYH ZZZC/?/5\^]yߧ9U;TG}kyǿu |Ug欀3_>S&SD8>|aaCp=p?A -p1?GG3O?y88az~Hw_w*Dw -ᝈvx8 -x#^p@:5sΰ$/^&W|^c8a ^^[K^x1(`v$ ~5Ok9l\2Tr<+`[<#`l6 ش7 耍e2jC W֧: -_+5WʚaDVvx[X/L -|uErZ~ x`i~'`G<,! -X@/@p{s`J{,Cw X `y5pW 0-|;Y|v J50c.5/k k`Z L)& $`8@xo2n`E^^ya -G -w#aa5px*VC f? M&? tÍi0B~n:x?7u@{{z@ ^0Qcׇ!#;7λ=pN񐗛s wѰPcQ%I'ÔiJ7er[VJ{H}e2O9#$et<$d yP?-`Dߝ]a~ ' lYI0M0Dxr95RøA֐t%? -J?A _ O23L6yLF|A?z,!]$t.th9S)r2(قk/R:IT7n>r -煣Ql[CNtRL}tRd$5e9'yCg!?x<'?)*9hUrJhO#+i?" NdfK ?Eld O!-hKc05q9Md4gjۆ k2rykY9;mSTPltjzBV-GVCh߰í[l=mW:c㤳Ή;01a c01a c01a c01a c01a c?!,.VFWp]tXE/g{j~ƿ -d^8M;tF[%o+I x ޵UgKP}qDI:su.2қnCNuPO?&{~XI3hUijg77DDLL:.&+HAZD]a ٮkjDNț\>nN8ww<"6ёt:rf+~ž7%#Y$UJ%ry"q,sZ+*yġ4~קCL~uv/wofq9s'[\h$%L ،4KhKrr{~WBDg!)nQTG/B}{-=û~+6u!,dE &-qӪMw}/s8d@V+jpe,_C\~_O ej CW廣q™Z\~6%,#퓢6\4<{f~}VozzӚ TNCA8ϾiV^J']Y8tt, ӨP:0"AaVvNaNmIR5A>`u)3ǻVyG| ;]* F-Zyxnn)l,*S\| -[bI]TiqtTZvd}U4#4g+)\U|%& 5!Ws1ZwGM'?ϻd#6w,nFZiҗϡ6'"xRS+Sl++\֦ -$? aig\IP4PC&EHjIjԌs|l BiI cA]=֌= ^ϔo PZZ g@.^ =̺Ǘeȟ8ӋvwE-i ZxڪDnIΖI =)9h$LC -y6p5v5`܎y+fN5k3$&=x ?C}F;vĨqlӧϞ=lvEֶWzs_Ŷ./?[*uxQc'(Ĩ-J+JJZߪpJؒ@%M=FsNތvlw H;NQ[WwqV|M63i?()E(- QO+wN~wL!V߉vnѢ{o-B""m%;*L!U҆H',$R$-Ȱ5ǂW"!**7R5\,U - -(6]S5 W% -Bv4::g35rt vPԨ Bg"6\qZzW{k}a0\oS'$OPl?Psr -!.TgGtլ]AZؠ3ƋhƄG<_fϚ_Sa=DJa7,;Xe/q~bioB[.$K'>cZXFVI.qf]$3ZFUotj >jW bEg/jc3T]Ǧ t@Kh)p]'qobA_F䩚o4x~} Ә -͔09h\A~tc!('!!-/~W#]IL*-tB쨽ӟ}CӋgO?#Q2XJHa%_%~rIfFeQM^Y7M[6_:m|`K-CWĈuã (}#|UH]lGkajt@G?%ՌP͆OuٺBo x &H R'ZlpRnO_fId9փ׆|6F+b|VDCKgBsh?ϤյH.;BujϱurUrX> Yit]+",RKlOg,,2MN CDCfXP+F{z^5(GՕ]Lf|,ՙSs5Z 0nc-ÍRf`˴e3Re$)TGraLs&Pm>1Nm^O{H\KD/y'tߢV5ړ'NGR-y/T?qZX{ł6ou~\N1j0Pկ^G{~P:\d@'E=EgI߰8V6R&Y੔Iv/LBbRkU^4H#BvےJ;{K5#$ wTu$eqM*|LLzHNL'%%''y|==}CC}J%4eg>s#eN4w`pytM ";>P:L#~;OcU#љQ#go=<iIŠ'mXxHV׺WH3d I;<O>(#RJ=Yˁ*;2<FFG&&˂ClC+۞H[X\bbbߖ-m[`[p[Et ""j9qff4)Qнgow⿖.w?rϏ ụ -"vn7$rri7k@Z(;N#0ͼCġFuگx*ttBuN6ѯ8y ./ TvD{63*,d\ Tʸ<b4O̯_R0C?k) ֐8yGքXU1Mh"$* <ޤ7}zK5wK!.Ї颺D.:hF\R:-OME_ʑdF@<ܚ -#O7peRٰ960ܨj6+/X-.y|ٿ* ەvyË3pwa#pgޝw0#&fy`T!&qfunUm> {5dMeR90v(9<[Ͷdk9zGwG_=~V`#VV>XloH-ca2RMԧӭle90GSzm>AKl/hl/L7i73`tX/ -QzC&eEW6=يH F4)/YG:[Fyإ((, i\"l+B30!Carig6n2 &hH `C薺_<fqR~f -aBl p!Nۇ~{Xʛ<0y2RW?`%N8ssK?^e# hn{d%l;FKt. h--=`ah:w3 >z2dsW9iف"[ƥK[X,1m}`GZU%ulnʕ@ouj3m,}%uX]lW>w3ߺu7h;j+iYݳ7wzS۶ԝtU)HvI6xW9%oJ<qDnOr!+B42wPe)(M&MV`O`gzѫ9w̙kQjO_o]~3=N-/:ė -nDrPRV(+?z\q76 ($K;tzMqG$kLr\O\r nPr.iOxds6̍ {V&>~'i/N"v -|c\#q(6c~L[8D7G!vIa"y%E™ g]glLyJZ:)m~;f?Q謝%f̝ {ٰ7ER@[XT=T0Ԯ"J)Wы;($# {wܿ..A?dߙ!r 2lx=.YAr&*e9[lXϚ[7(Ptq{lT{7{G?TgIǍ5jsu;gϟo(zC%zq[je0Drlu56X[<@r#vPd1!&evm;]rHiٻ QucҠ}ay|;k7 eP%|+gwl1X={?y^"t-]_w EFԾ@@~ D&&ɾ3!d/|!o`smF݅&"Y8]jIt KCi;StRHM{Mh :!wz5+{ -^)?pH2&VEO(ۉ=0kl8ܗuCY{JҜ)[}̓u+EF];Yg{}FE*6LBTM$^G6ŭJ{8@ok~b4V)7zK,ف9 ̙=lTqZ|&^a޳6<+J;z ^')ChDƙ.+qc vbѦITv9sm _fEC<|vvVmzgwJO;gki2M5幙?´HkN; Ь:\q!&ܲ355U:=Nt9݃ -bE D8\LYzXQ{_ر?%^'"+Z/ҋbV;bx/VWt5VV5Vx ͯG0&P z9JQm ^1QGtu?/G=[_yrytcL5* }@c2o$Wqܥ8c9kųԖZ+5lk%#;-lYt6*CpG)+R"R7Y2rmQnEj[-u<=a[ž-336 -D}Q{=wcHe6VB}訽VxsQp)z`A{ ΍2RĪj:'Z,*U7e%O-8%a(a1(PQv7ѿseq;?A 7}0T}&ܥ aT,eV_*.q?쇣Qis׿A?z=Si`ij%E7vJkn.ZG#^+~?YȖ*Kd[Vh+*&rTo|D_1k9^F^vB3FS鼳yx*YǺt;]wOI*yĉVfCϵNȉܜa\Ot9V] QhMe\?}a*k`|aͧ6ݏ.1ijⴎ78D9jk>^kiΛ-Ʈ<5ϒw$=i?= DW;g+qqھڱmm3g{aRWY_xvez|x:uk!Td~#oI@Ky[(B^u<I Hx6pMQ tթ{?sϫ~F -I2aײܢk.\p5v|6;)xUC%P/ZBlxnXc+E5ukI + rO ēdsd%z*RT{g }H `#GjiO"ĔgnZB;pUi0Z oȝ܎:.(HKkJK?q楹Q JfV% m̋AmPZad4b'v+p^Ftۑx)S&ec;w-|*L&'%G5j -4⸲VLxUrRo؅1H͉fV)_ŵ 5iݠ+&Lb/ﾘ\汷sR{kYϻ/HAZZdhg|+H.$<޼g! M -oh{9B+{Kԅ;SCru+TWբjjD3QG#hw!g(En$$\ -UMgW]+lCz*y֦KNWJqb7LK9`!# 4޼ćwkF4ګHlV\sH7\$On e%3$2L$̯яCIFWcE6L/J _/]?7)z\S\evMOmz O傫[W;['cYpU"͛n8o^ -%EFY&Io+RĖ\Ce9׿ty -iҧH%cɲӦecgO"OĒXΝ1,PRfL!&O6Kb͔dⲠ,';xDlYS6xY6ctl9t,'o:iBU[!QM;qBe{S|y> -stream -x|yxTŶo {s;ݝN$B&4<a<*C &P"ǃA<!=9\q@#z= -݉N]VZހ0B;̔=/ ӫw~ ;:dx.FAc 8h_Cf4nh:oB|qS,j "DҦ/1o,s ̘h!aCm1wi&EW6@|pঢ় Q{2,xS'wmφN4̛B#5\[?y޴o(8 ?ï/|t.'=HeE&->n7P/;? GE gh*X4s7aѽڙɨ 6AT= qgU1S'x8$zIG!8￡{!?E%;<$/ݹef띜:,`aP'Pxy 2ڻMP\sӡr(BCK"x?UC}?o -Cwqš1T(kx!cZyWq ZُfTA}GlԄVAk@_#spBkGI =h<߹u u@@&w~ ySD:Z_} -cMp_3"CCݹ3PGQO_S: Z[{=^Uނpw/u胿~N.O[uI9Hcb(@¾ ؎ô `omoF[ao{-b=ʀR@Z]ь2F[A;L]NY&/G7F7bhz/\O9U-s*/Fb zN@b3uw]-W跌~u _Gү2~/ߢrK F/2gsF?s O⧌~^/~/uMhB3zCU<*=y* 3^m,fr.'}[b=یa5^ab>-pG1z֕dF_/Mte5o2ѿh 6d&.re})ErR - ;}nx"p,yngt ѭFZX薎Ư+}tba3>qx/lbYF7B{a0{ ;]epJ}i+]ZFK]*at}ʚ/>5dIy9]bt.e Fgtcq.Ax@;*,E~QFat! T$:9t62[ta:i1:uGdxdF'1: c_DǽKBcSB;HFtggt-CbSAEZio'z6`uB~OouA$4Ӟu(yo:\ u-#-4 S -~8C/נe0 אM%ꜲU@Eth @//8\Sp ܄nBO5;޶xEWe$CbMOphN.N'9x~AGgx/ۖՉqZлdkf.]fݚ|yBH!Ɗ;XzSh5LOHf[\oۗx"UeZpzgޭ-kڝT]K-Zt(67EC0Ԉ(5#+ELAEĔv&K 抮-S S",7\bNtUeٺ-#V?{v^;N_T) ?~IE4^.uiE1@sЯ -ZL7hSq :pw=d!G,w =hz `Je{`X -!8@yo$0z+Oy6QMIʘ$!+\dgaaI5:%KfG7]x'BV8/紴!~O}cz7x Gf 'ƭS ݵ0}޽|Łƍ= Q>do [E -:vNj2";ѽN^5dgozrVQJ2 )َ" vo!c,n lhS M Bo6o,b8^8^ XaY|մ%H39NlxΜ+).{Ʒj؋ν8tM}o?eM[օmc[Ļr۶Omƾ]{z3ٛlQvq^n d⃙ߣyEmD>>QH>Qt>*PO**xM)HZC'zQ0 e*͕wex̨6b=Aɒ#x4S4l7[n=+Ʒ[x5[m.Gx$37TuR{U SLp1#*]<4/_!f E ֊{z#?xa?jfU6nX9rqgבzu/T7X,r:87pWRJ]0t)-;]?BmfveqԿf䉆jWx>jLw?@?~ׁĆ$wH,!NtcIwFחm$xaAZV|SwФ"<bovvm} 1mfŀq0:#KMJwtPAh Z%GOpdSP򥆨gгz&U붓6ݝ_ ZƑi-y}kZrxKa(Q4#P8g3;v5x]}5IB\T h*b˴5W -T $IƖy.t;)LNr)^%W6;B%xQNy&,؟I8sI55Jk߫t -;E$ijpѠ) ͒ EFc,N%ALPIyR -uEdDY3$"Rth< By2.ON03 03 eM8Or[f--/֓ZꀛEZ7hj=4u,lJq#9(B1Hxn L<IZfvEK.ldaS)a^d@kkHU @gav8l+[bbv.V<L d 2 -&#Ho]ѓtb> Nۓ<bTV],~(<ϔ :Aoa_ĔbL[3-:5WUi\Bl)Ö҈ji5O06:]Wjkɹ_ZZnh\phq??㵸b[Ś C~ 06Veڃ+28Z\ @D˿+{~z6 sbj˙ͫWoge7ǏV-EYIiz.\6`jXABr(S[\Pn尮JKt" .$ -aXU"˽7P 0f;`}@%9TC8V/pDUjEQ&3k]ҢƛΚk eqڂLw wj]# :xOZ6F\}K/|pqgL-Ħ/>|nԚB~?<@Lz'ƣ般bb<#`]V:zYUX<>&RF tc@@ \F%HeFe92ji;s.%1ǚcN(5efU57-l4^~n:3ޕMJI_u>N~Tǝ02򛤠~ߑi6wOF ^V1AfjCU,x챦5 -" ֽ x'8  %#G=5N̞U`.;0ڭ[Wf`Wouҥkpt-0IlIk7t QIxx R7V;:q*$3ijl 6l ) 貿x?TU*Qք aOE&>J Ȁ}ȐT^A1,ٞ^FWnm^ਹ{ ]+ф#Ĩ<$pgu # IJΧO0d.4K"vU: #<QHq4Vf(3 KxPLkfXƟ(9ĥ#E l z <ZQĶ>-.DJH?#?~t^**WWa -@;EAqm/& O%z=kV̊D(^> hP?,"TEh@F~ - x'){-[}dU-˩Fk s7 MnN[{A`i>sOydST >!a{fVzԢ7><%R-u[3^|'V( kqp>!mo\ȤudZȨD - -lf͢drI#k_I3"4NeEghYF.-=]֮V2b6W 9z<`MvFMY*8PϚ -bbӼiqըWjZ3YvWG@Nmi̬2`H}t]_/{ ^iѱK2Y8mCU4흇EYݩ.1qذMӷS4 -#\-3Umndq$) 8`'-X`-XIHSO+֮^kVmö駿XTձ~t᳦_ O+PG=;1jz -FǁHލRRQ *u /2]={m$DF0߅r|3C[4CL379wv:?]]{p,:l@%(#L2TQQCMߗ˅Or6sA|~k}:cUQNOkW.-]z-=KyQ+v`+]|gZ)84Z[/b̈v)%/f ؀ -WEkZ :Ur0rPɄG^+<:o6c:a{,dw; a؀;_ٷXD[R`R+2$SItd4<{ >)MOfظ|!|/$:d+XN~u^ЌTz|pktX_Z}n'2QGma2Oxj'{ э$Cf;˕+ ji1yf'䮩ufe1%+K6]QRw훁O~ku$9v1Q;ܧ,0w2Vpc6"5ut&ʿ0/A'F_veحYC?AR4fȃYYZW{^!-Im7R"[^42~CFVjA݆IVXlɺ|yJ8x^`>.㘺:aR yb#1B-")ZL1M1 _74TV,Do -q|ӯo?}׫\~ͲwQAst=N Ich[(ˠÒ 63Z!•  mpcaQp]J$f+d:YL*KtKKIbܕv+(i?y4ZCg YDZ"Gݗ{h_2^lLK_j]b@ "NZ*u+{TiHp1cG|oO%\?o? ;!uOt:AFё0cnfe4:<85(w}YG-<"<:-$\ݮ\^&iR4}^x3ϕ΋ȋ̋ʋb!.}4N1؃;[F -#`\3Qm~Tch.ڸ a{0rWͷWJxd})I->þxpj ul#Ҽ+ њT/ ݝpH%C/_678vF,]sC rtMۗ:_5utq:1lZ^/p -䮈/ -LLQcJub3݋4wk>cA`{L;ل \>Sá;VR)v5IGF -[U*>f+?,}mߡ Ek &L=n'Kn=2"p0 Ih= |$ cc"E-kos ۟&(R""qG=[s@[6U3zM''3pޕ8Gɉf%Zm2NǠM"htj>Ɛp{ JC.s\9SfF*Qцd.g'K'?էU7ƨ$YAzԾhu6%TtBX*I]@n sǫy} 'H~K=]wLogu Hr5HR^ "K@ l': ȇK:u* -9A,`A'H4B8y*C#OdzY1Т:.B'u0RUCr\&\DaR˷-umG8jodj':G\V lA`MFd2[ŒȤ+[M¬g4mw߉ik+jQ uioX6&̝l*ϓJ29C ^p>w356{h\683av|( _O-*2Q=Ϸ>, c;1O8sGS~dAv ? ڑ_1=!F8ga{ ?a@$gT½ -q;~sv=a򣓧Kf<:mJ;yA,?6ާX -endstream -endobj -1062 0 obj -<< -/Type /FontDescriptor -/FontName /LXRMZQ+DejaVuSans -/FontFamily (DejaVu Sans) -/Flags 4 -/FontBBox [ 0 -14 557 560 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 560 -/StemV 80 -/StemH 80 -/FontFile2 1058 0 R ->> -endobj -1063 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /LXRMZQ+DejaVuSans -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 317 ] 16 [ 360 317 ] 20 [ 636 636 ] 25 [ 636 ] 36 [ 684 686 698 ] 40 [ 631 ] 42 [ 774 ] 44 [ 294 ] 46 [ 655 ] 53 [ 694 634 ] 68 [ 612 ] 70 [ 549 634 615 352 ] 75 [ 633 277 ] 78 [ 579 277 974 633 611 ] 85 [ 411 520 392 633 591 ] ] -/FontDescriptor 1062 0 R ->> -endobj -1064 0 obj -<< -/Length 772 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -32 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0003> <0020> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0048> <0065> -<0051> <006e> -<0046> <0063> -<004b> <0068> -<0050> <006d> -<0044> <0061> -<0055> <0072> -<004e> <006b> -<0010> <002d> -<004f> <006c> -<0049> <0066> -<0024> <0041> -<0056> <0073> -<0057> <0074> -<002a> <0047> -<0058> <0075> -<004c> <0069> -<0047> <0064> -<0015> <0032> -<0052> <006f> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1065 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /LXRMZQ+DejaVuSans -/Encoding /Identity-H -/DescendantFonts [ 1063 0 R ] -/ToUnicode 1064 0 R ->> -endobj -1066 0 obj -<< -/Type /FontDescriptor -/FontName /ENPKVN+Poppins -/FontFamily (Poppins) -/Flags 4 -/FontBBox [ -27 -132 753 704 ] -/ItalicAngle 0 -/Ascent 1049 -/Descent -349 -/CapHeight 704 -/StemV 80 -/StemH 80 -/FontFile2 1059 0 R ->> -endobj -1067 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /ENPKVN+Poppins -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 266 ] 5 [ 291 ] 7 [ 621 ] 10 [ 158 453 453 485 ] 15 [ 197 550 209 475 627 319 574 588 628 627 634 545 630 629 212 ] 32 [ 722 ] 36 [ 673 612 771 706 512 503 777 691 245 ] 46 [ 598 431 860 702 785 578 787 607 586 540 674 675 975 ] 60 [ 583 540 422 ] 64 [ 422 ] 66 [ 732 256 675 675 606 675 619 328 675 639 245 247 514 245 1029 639 639 675 675 372 521 363 639 560 819 478 562 454 ] 95 [ 290 ] 204 [ 218 ] ] -/FontDescriptor 1066 0 R ->> -endobj -1068 0 obj -<< -/Length 1430 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -79 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0003> <0020> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0048> <0065> -<0051> <006e> -<0046> <0063> -<004b> <0068> -<0050> <006d> -<0044> <0061> -<0055> <0072> -<004e> <006b> -<0010> <002d> -<004f> <006c> -<0049> <0066> -<0024> <0041> -<0056> <0073> -<0057> <0074> -<002a> <0047> -<0058> <0075> -<004c> <0069> -<0047> <0064> -<0015> <0032> -<0016> <0033> -<0045> <0062> -<005a> <0077> -<001b> <0038> -<0052> <006f> -<0030> <004d> -<0031> <004e> -<004a> <0067> -<0029> <0046> -<0017> <0034> -<0033> <0050> -<001a> <0037> -<0018> <0035> -<0013> <0030> -<005d> <007a> -<002f> <004c> -<003a> <0057> -<005c> <0079> -<001c> <0039> -<005b> <0078> -<0027> <0044> -<0032> <004f> -<0037> <0054> -<0053> <0070> -<000f> <002c> -<001d> <003a> -<002b> <0048> -<0039> <0056> -<003c> <0059> -<000b> <0028> -<000c> <0029> -<004d> <006a> -<0054> <0071> -<000a> <0027> -<005f> <007c> -<0012> <002f> -<000d> <002a> -<0020> <003d> -<0042> <005f> -<0043> <0060> -<0005> <0022> -<003e> <005b> -<0040> <005d> -<00cc> <2019> -<0007> <0024> -<0038> <0055> -<003d> <005a> -<0034> <0051> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1069 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /ENPKVN+Poppins -/Encoding /Identity-H -/DescendantFonts [ 1067 0 R ] -/ToUnicode 1068 0 R ->> -endobj -1070 0 obj -<< -/Type /FontDescriptor -/FontName /DYCYPS+DejaVuSans -/FontFamily (DejaVu Sans) -/Flags 4 -/FontBBox [ -9 -92 733 729 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 729 -/StemV 80 -/StemH 80 -/FontFile2 1060 0 R ->> -endobj -1071 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /DYCYPS+DejaVuSans -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 348 ] 11 [ 457 457 ] 16 [ 415 379 365 695 695 695 695 695 695 695 695 695 695 399 ] 36 [ 773 762 733 830 683 ] 44 [ 372 ] 46 [ 774 637 995 836 ] 51 [ 732 ] 53 [ 770 720 682 ] 57 [ 773 1103 ] 60 [ 724 ] 66 [ 500 ] 68 [ 674 715 592 715 678 435 715 711 342 ] 78 [ 665 342 1041 711 687 715 715 493 595 478 711 651 923 645 651 582 ] 5038 [ 741 ] ] -/FontDescriptor 1070 0 R ->> -endobj -1072 0 obj -<< -/Length 1182 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -61 beginbfchar -<0014> <0031> -<0016> <0033> -<0017> <0034> -<0018> <0035> -<0011> <002e> -<0003> <0020> -<0028> <0045> -<0051> <006e> -<0056> <0073> -<0058> <0075> -<0055> <0072> -<0048> <0065> -<0057> <0074> -<004b> <0068> -<0044> <0061> -<0024> <0041> -<0033> <0050> -<002c> <0049> -<0059> <0076> -<0053> <0070> -<0052> <006f> -<0047> <0064> -<0046> <0063> -<004c> <0069> -<13ae> <00660069> -<004f> <006c> -<0050> <006d> -<0019> <0036> -<000b> <0028> -<000c> <0029> -<0015> <0032> -<005a> <0077> -<001d> <003a> -<004a> <0067> -<001a> <0037> -<001b> <0038> -<001c> <0039> -<0026> <0043> -<0031> <004e> -<004e> <006b> -<0049> <0066> -<0030> <004d> -<0013> <0030> -<005c> <0079> -<0010> <002d> -<002e> <004b> -<0045> <0062> -<005d> <007a> -<0035> <0052> -<0025> <0042> -<002f> <004c> -<0036> <0053> -<005b> <0078> -<0027> <0044> -<0054> <0071> -<0039> <0056> -<0037> <0054> -<0042> <005f> -<003a> <0057> -<0012> <002f> -<003c> <0059> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1073 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /DYCYPS+DejaVuSans -/Encoding /Identity-H -/DescendantFonts [ 1071 0 R ] -/ToUnicode 1072 0 R ->> -endobj -1074 0 obj -<< -/Type /FontDescriptor -/FontName /IJJFHS+DejaVuSansMono -/FontFamily (DejaVu Sans Mono) -/Flags 4 -/FontBBox [ 0 -155 598 728 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 728 -/StemV 80 -/StemH 80 -/FontFile2 1061 0 R ->> -endobj -1075 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /IJJFHS+DejaVuSansMono -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 602 602 602 602 602 602 602 602 602 602 602 ] 15 [ 602 602 601 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 601 602 602 602 602 602 602 602 602 ] 46 [ 602 602 602 601 602 602 602 602 602 602 602 602 602 602 602 ] 62 [ 602 602 602 ] 66 [ 601 ] 68 [ 601 601 601 601 601 602 602 602 601 602 601 601 601 602 601 601 602 601 601 601 601 602 601 602 602 602 602 602 602 ] ] -/FontDescriptor 1074 0 R ->> -endobj -1076 0 obj -<< -/Length 1570 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -89 beginbfchar -<0031> <004e> -<0052> <006f> -<0057> <0074> -<0024> <0041> -<0053> <0070> -<004f> <006c> -<004c> <0069> -<0046> <0063> -<0044> <0061> -<0045> <0062> -<0048> <0065> -<0058> <0075> -<0050> <006d> -<0047> <0064> -<0056> <0073> -<0055> <0072> -<0003> <0020> -<0010> <002d> -<0051> <006e> -<0020> <003d> -<0008> <0025> -<001f> <003c> -<004b> <0068> -<0012> <002f> -<0049> <0066> -<0021> <003e> -<0038> <0055> -<001d> <003a> -<002a> <0047> -<0059> <0076> -<000a> <0027> -<001a> <0037> -<0013> <0030> -<0054> <0071> -<004e> <006b> -<0042> <005f> -<005a> <0077> -<0011> <002e> -<0006> <0023> -<0004> <0021> -<0037> <0054> -<004a> <0067> -<005c> <0079> -<0007> <0024> -<0014> <0031> -<002c> <0049> -<0033> <0050> -<0027> <0044> -<0035> <0052> -<003e> <005b> -<0005> <0022> -<005e> <007b> -<0060> <007d> -<0040> <005d> -<001e> <003b> -<005b> <0078> -<000b> <0028> -<000c> <0029> -<002f> <004c> -<000d> <002a> -<005f> <007c> -<0015> <0032> -<0009> <0026> -<0019> <0036> -<0017> <0034> -<002b> <0048> -<0036> <0053> -<0028> <0045> -<0030> <004d> -<0032> <004f> -<0029> <0046> -<003f> <005c> -<0022> <003f> -<005d> <007a> -<0016> <0033> -<003b> <0058> -<000f> <002c> -<0025> <0042> -<0026> <0043> -<001c> <0039> -<003a> <0057> -<001b> <0038> -<0018> <0035> -<003c> <0059> -<004d> <006a> -<0039> <0056> -<0034> <0051> -<0023> <0040> -<002e> <004b> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1077 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /IJJFHS+DejaVuSansMono -/Encoding /Identity-H -/DescendantFonts [ 1075 0 R ] -/ToUnicode 1076 0 R ->> -endobj -1078 0 obj -<< -/LXRMZQ 1065 0 R -/ENPKVN 1069 0 R -/DYCYPS 1073 0 R -/IJJFHS 1077 0 R ->> -endobj -xref -0 1079 -0000000000 65535 f -0000000015 00000 n -0000001112 00000 n -0000001250 00000 n -0000040655 00000 n -0000040789 00000 n -0000043487 00000 n -0000043686 00000 n -0000047426 00000 n -0000047832 00000 n -0000048037 00000 n -0000048244 00000 n -0000048379 00000 n -0000048515 00000 n -0000048673 00000 n -0000048832 00000 n -0000049065 00000 n -0000049299 00000 n -0000049514 00000 n -0000049730 00000 n -0000049971 00000 n -0000050213 00000 n -0000050436 00000 n -0000050660 00000 n -0000050892 00000 n -0000051125 00000 n -0000051339 00000 n -0000051554 00000 n -0000051781 00000 n -0000052009 00000 n -0000052218 00000 n -0000052428 00000 n -0000052657 00000 n -0000052887 00000 n -0000053098 00000 n -0000053310 00000 n -0000053529 00000 n -0000053748 00000 n -0000057509 00000 n -0000057974 00000 n -0000058175 00000 n -0000058377 00000 n -0000058592 00000 n -0000058808 00000 n -0000059005 00000 n -0000059203 00000 n -0000059422 00000 n -0000059642 00000 n -0000059843 00000 n -0000060045 00000 n -0000060273 00000 n -0000060502 00000 n -0000060712 00000 n -0000060923 00000 n -0000061138 00000 n -0000061354 00000 n -0000061585 00000 n -0000061817 00000 n -0000062020 00000 n -0000062224 00000 n -0000062361 00000 n -0000062499 00000 n -0000062693 00000 n -0000062888 00000 n -0000063078 00000 n -0000063269 00000 n -0000063460 00000 n -0000063652 00000 n -0000063844 00000 n -0000064037 00000 n -0000064276 00000 n -0000064516 00000 n -0000064731 00000 n -0000064947 00000 n -0000065154 00000 n -0000065361 00000 n -0000068935 00000 n -0000069413 00000 n -0000069609 00000 n -0000069806 00000 n -0000070002 00000 n -0000070199 00000 n -0000070398 00000 n -0000070598 00000 n -0000070798 00000 n -0000070999 00000 n -0000071197 00000 n -0000071396 00000 n -0000071630 00000 n -0000071865 00000 n -0000072064 00000 n -0000072264 00000 n -0000072467 00000 n -0000072671 00000 n -0000072873 00000 n -0000073076 00000 n -0000073276 00000 n -0000073477 00000 n -0000073673 00000 n -0000073870 00000 n -0000074059 00000 n -0000074250 00000 n -0000074442 00000 n -0000074635 00000 n -0000074825 00000 n -0000075016 00000 n -0000075202 00000 n -0000075389 00000 n -0000075601 00000 n -0000075814 00000 n -0000076029 00000 n -0000076245 00000 n -0000076458 00000 n -0000076671 00000 n -0000080377 00000 n -0000080880 00000 n -0000081082 00000 n -0000081285 00000 n -0000081487 00000 n -0000081690 00000 n -0000081901 00000 n -0000082113 00000 n -0000082334 00000 n -0000082556 00000 n -0000082785 00000 n -0000083015 00000 n -0000083216 00000 n -0000083418 00000 n -0000083616 00000 n -0000083815 00000 n -0000084028 00000 n -0000084242 00000 n -0000084441 00000 n -0000084641 00000 n -0000084852 00000 n -0000085064 00000 n -0000085210 00000 n -0000085357 00000 n -0000085571 00000 n -0000085786 00000 n -0000085978 00000 n -0000086171 00000 n -0000086382 00000 n -0000086594 00000 n -0000086813 00000 n -0000087033 00000 n -0000087232 00000 n -0000087432 00000 n -0000087640 00000 n -0000087849 00000 n -0000088045 00000 n -0000088241 00000 n -0000092113 00000 n -0000092584 00000 n -0000092721 00000 n -0000092859 00000 n -0000093051 00000 n -0000093244 00000 n -0000093443 00000 n -0000093643 00000 n -0000093800 00000 n -0000093958 00000 n -0000094171 00000 n -0000094385 00000 n -0000094581 00000 n -0000094778 00000 n -0000094970 00000 n -0000095163 00000 n -0000095386 00000 n -0000095610 00000 n -0000095811 00000 n -0000096013 00000 n -0000096210 00000 n -0000096408 00000 n -0000096605 00000 n -0000096803 00000 n -0000096963 00000 n -0000097124 00000 n -0000097321 00000 n -0000097519 00000 n -0000097654 00000 n -0000097790 00000 n -0000097973 00000 n -0000098157 00000 n -0000098349 00000 n -0000098542 00000 n -0000102387 00000 n -0000102874 00000 n -0000103033 00000 n -0000103193 00000 n -0000103414 00000 n -0000103636 00000 n -0000103839 00000 n -0000104043 00000 n -0000104266 00000 n -0000104490 00000 n -0000104694 00000 n -0000104899 00000 n -0000105130 00000 n -0000105362 00000 n -0000105575 00000 n -0000105789 00000 n -0000106018 00000 n -0000106248 00000 n -0000106466 00000 n -0000106685 00000 n -0000106921 00000 n -0000107158 00000 n -0000107376 00000 n -0000107595 00000 n -0000107730 00000 n -0000107866 00000 n -0000108059 00000 n -0000108253 00000 n -0000108464 00000 n -0000108676 00000 n -0000108879 00000 n -0000109083 00000 n -0000109274 00000 n -0000109466 00000 n -0000109680 00000 n -0000109894 00000 n -0000113976 00000 n -0000114463 00000 n -0000114666 00000 n -0000114870 00000 n -0000115075 00000 n -0000115281 00000 n -0000115471 00000 n -0000115662 00000 n -0000115899 00000 n -0000116137 00000 n -0000116368 00000 n -0000116600 00000 n -0000116804 00000 n -0000117009 00000 n -0000117217 00000 n -0000117426 00000 n -0000117634 00000 n -0000117843 00000 n -0000117996 00000 n -0000118150 00000 n -0000118347 00000 n -0000118545 00000 n -0000118706 00000 n -0000118868 00000 n -0000119050 00000 n -0000119233 00000 n -0000119398 00000 n -0000119564 00000 n -0000119761 00000 n -0000119959 00000 n -0000120161 00000 n -0000120364 00000 n -0000120513 00000 n -0000120663 00000 n -0000120845 00000 n -0000121028 00000 n -0000124874 00000 n -0000125345 00000 n -0000125566 00000 n -0000125788 00000 n -0000126002 00000 n -0000126217 00000 n -0000126435 00000 n -0000126654 00000 n -0000126858 00000 n -0000127063 00000 n -0000127239 00000 n -0000127416 00000 n -0000127615 00000 n -0000127815 00000 n -0000128010 00000 n -0000128206 00000 n -0000128404 00000 n -0000128603 00000 n -0000128755 00000 n -0000128908 00000 n -0000129095 00000 n -0000129283 00000 n -0000129477 00000 n -0000129672 00000 n -0000129818 00000 n -0000129965 00000 n -0000130167 00000 n -0000130370 00000 n -0000130537 00000 n -0000130705 00000 n -0000130861 00000 n -0000131018 00000 n -0000131225 00000 n -0000131433 00000 n -0000133745 00000 n -0000134040 00000 n -0000134184 00000 n -0000134329 00000 n -0000134531 00000 n -0000134734 00000 n -0000134948 00000 n -0000135163 00000 n -0000135348 00000 n -0000135534 00000 n -0000135712 00000 n -0000135891 00000 n -0000140751 00000 n -0000141006 00000 n -0000141262 00000 n -0000141529 00000 n -0000141795 00000 n -0000142002 00000 n -0000142208 00000 n -0000145778 00000 n -0000146009 00000 n -0000146207 00000 n -0000146396 00000 n -0000150083 00000 n -0000150286 00000 n -0000154029 00000 n -0000154252 00000 n -0000154386 00000 n -0000158416 00000 n -0000158655 00000 n -0000158789 00000 n -0000158923 00000 n -0000159057 00000 n -0000162674 00000 n -0000162877 00000 n -0000167587 00000 n -0000167978 00000 n -0000168112 00000 n -0000168244 00000 n -0000168376 00000 n -0000168508 00000 n -0000168640 00000 n -0000168772 00000 n -0000168904 00000 n -0000169036 00000 n -0000169168 00000 n -0000169301 00000 n -0000169434 00000 n -0000169567 00000 n -0000169700 00000 n -0000169833 00000 n -0000169966 00000 n -0000170099 00000 n -0000170232 00000 n -0000170365 00000 n -0000170498 00000 n -0000170631 00000 n -0000170763 00000 n -0000170894 00000 n -0000175901 00000 n -0000176300 00000 n -0000176433 00000 n -0000176566 00000 n -0000176699 00000 n -0000176832 00000 n -0000176965 00000 n -0000177098 00000 n -0000177231 00000 n -0000177364 00000 n -0000177497 00000 n -0000177630 00000 n -0000177763 00000 n -0000177896 00000 n -0000178029 00000 n -0000178162 00000 n -0000178295 00000 n -0000178428 00000 n -0000178561 00000 n -0000178694 00000 n -0000178827 00000 n -0000178960 00000 n -0000179093 00000 n -0000179226 00000 n -0000179361 00000 n -0000184173 00000 n -0000184636 00000 n -0000184771 00000 n -0000184904 00000 n -0000185037 00000 n -0000185170 00000 n -0000185303 00000 n -0000185436 00000 n -0000185569 00000 n -0000185702 00000 n -0000185835 00000 n -0000185969 00000 n -0000186103 00000 n -0000186237 00000 n -0000186371 00000 n -0000186505 00000 n -0000186639 00000 n -0000186773 00000 n -0000186907 00000 n -0000187041 00000 n -0000187175 00000 n -0000187309 00000 n -0000187443 00000 n -0000187577 00000 n -0000187711 00000 n -0000187845 00000 n -0000187979 00000 n -0000188113 00000 n -0000188247 00000 n -0000188381 00000 n -0000188515 00000 n -0000188649 00000 n -0000188782 00000 n -0000193785 00000 n -0000194248 00000 n -0000194382 00000 n -0000194516 00000 n -0000194650 00000 n -0000194784 00000 n -0000194918 00000 n -0000195052 00000 n -0000195186 00000 n -0000195320 00000 n -0000195454 00000 n -0000195588 00000 n -0000195722 00000 n -0000195856 00000 n -0000195990 00000 n -0000196124 00000 n -0000196258 00000 n -0000196392 00000 n -0000196526 00000 n -0000196660 00000 n -0000196794 00000 n -0000196928 00000 n -0000197062 00000 n -0000197196 00000 n -0000197330 00000 n -0000197464 00000 n -0000197598 00000 n -0000197732 00000 n -0000197866 00000 n -0000198000 00000 n -0000198134 00000 n -0000198268 00000 n -0000198403 00000 n -0000202995 00000 n -0000203386 00000 n -0000203521 00000 n -0000203654 00000 n -0000203787 00000 n -0000203920 00000 n -0000204053 00000 n -0000204186 00000 n -0000204319 00000 n -0000204452 00000 n -0000204585 00000 n -0000204719 00000 n -0000204853 00000 n -0000204987 00000 n -0000205121 00000 n -0000205255 00000 n -0000205389 00000 n -0000205523 00000 n -0000205657 00000 n -0000205791 00000 n -0000205925 00000 n -0000206059 00000 n -0000206193 00000 n -0000206326 00000 n -0000211317 00000 n -0000211828 00000 n -0000211962 00000 n -0000212096 00000 n -0000212230 00000 n -0000212364 00000 n -0000212498 00000 n -0000212632 00000 n -0000212766 00000 n -0000212900 00000 n -0000213034 00000 n -0000213168 00000 n -0000213302 00000 n -0000213436 00000 n -0000213570 00000 n -0000213704 00000 n -0000213838 00000 n -0000213972 00000 n -0000214106 00000 n -0000214240 00000 n -0000214374 00000 n -0000214508 00000 n -0000214642 00000 n -0000214776 00000 n -0000214910 00000 n -0000215044 00000 n -0000215178 00000 n -0000215312 00000 n -0000215446 00000 n -0000215580 00000 n -0000215714 00000 n -0000215848 00000 n -0000215982 00000 n -0000216116 00000 n -0000216250 00000 n -0000216384 00000 n -0000216518 00000 n -0000216651 00000 n -0000216783 00000 n -0000220032 00000 n -0000220271 00000 n -0000220405 00000 n -0000220539 00000 n -0000220674 00000 n -0000225715 00000 n -0000225938 00000 n -0000226073 00000 n -0000231076 00000 n -0000231299 00000 n -0000231434 00000 n -0000236225 00000 n -0000236428 00000 n -0000241436 00000 n -0000241659 00000 n -0000241794 00000 n -0000246649 00000 n -0000246852 00000 n -0000251775 00000 n -0000251998 00000 n -0000252133 00000 n -0000257000 00000 n -0000257223 00000 n -0000257358 00000 n -0000262131 00000 n -0000262334 00000 n -0000267334 00000 n -0000267557 00000 n -0000267692 00000 n -0000272677 00000 n -0000272880 00000 n -0000277784 00000 n -0000278007 00000 n -0000278142 00000 n -0000283091 00000 n -0000283314 00000 n -0000283449 00000 n -0000288275 00000 n -0000288478 00000 n -0000293483 00000 n -0000293706 00000 n -0000293841 00000 n -0000298855 00000 n -0000299078 00000 n -0000299213 00000 n -0000304128 00000 n -0000304331 00000 n -0000309308 00000 n -0000309531 00000 n -0000309666 00000 n -0000314447 00000 n -0000314650 00000 n -0000318970 00000 n -0000319201 00000 n -0000319336 00000 n -0000319471 00000 n -0000324362 00000 n -0000324585 00000 n -0000324720 00000 n -0000329754 00000 n -0000329977 00000 n -0000330112 00000 n -0000334992 00000 n -0000335195 00000 n -0000340299 00000 n -0000340522 00000 n -0000340657 00000 n -0000345547 00000 n -0000345750 00000 n -0000350768 00000 n -0000350991 00000 n -0000351126 00000 n -0000356049 00000 n -0000356272 00000 n -0000356407 00000 n -0000361218 00000 n -0000361421 00000 n -0000366467 00000 n -0000366690 00000 n -0000366825 00000 n -0000371758 00000 n -0000371981 00000 n -0000372116 00000 n -0000376932 00000 n -0000377135 00000 n -0000382112 00000 n -0000382335 00000 n -0000382470 00000 n -0000387421 00000 n -0000387624 00000 n -0000392507 00000 n -0000392730 00000 n -0000392865 00000 n -0000397809 00000 n -0000398032 00000 n -0000398167 00000 n -0000402979 00000 n -0000403182 00000 n -0000408184 00000 n -0000408407 00000 n -0000408542 00000 n -0000413541 00000 n -0000413764 00000 n -0000413899 00000 n -0000418682 00000 n -0000418885 00000 n -0000423879 00000 n -0000424102 00000 n -0000424237 00000 n -0000429096 00000 n -0000429299 00000 n -0000434327 00000 n -0000434550 00000 n -0000434685 00000 n -0000439559 00000 n -0000439782 00000 n -0000439917 00000 n -0000444664 00000 n -0000444867 00000 n -0000449930 00000 n -0000450153 00000 n -0000450289 00000 n -0000455240 00000 n -0000455443 00000 n -0000460278 00000 n -0000460501 00000 n -0000460637 00000 n -0000465662 00000 n -0000465885 00000 n -0000466021 00000 n -0000470808 00000 n -0000471011 00000 n -0000475993 00000 n -0000476216 00000 n -0000476352 00000 n -0000481349 00000 n -0000481572 00000 n -0000481707 00000 n -0000486477 00000 n -0000486680 00000 n -0000491763 00000 n -0000492098 00000 n -0000492234 00000 n -0000492368 00000 n -0000492502 00000 n -0000492636 00000 n -0000492770 00000 n -0000492904 00000 n -0000493038 00000 n -0000493172 00000 n -0000493306 00000 n -0000493441 00000 n -0000493576 00000 n -0000493711 00000 n -0000493846 00000 n -0000493980 00000 n -0000494113 00000 n -0000498615 00000 n -0000498926 00000 n -0000499061 00000 n -0000499196 00000 n -0000499331 00000 n -0000499466 00000 n -0000499601 00000 n -0000499736 00000 n -0000499871 00000 n -0000500006 00000 n -0000500141 00000 n -0000500276 00000 n -0000500412 00000 n -0000500548 00000 n -0000505561 00000 n -0000505784 00000 n -0000505920 00000 n -0000510767 00000 n -0000510990 00000 n -0000511126 00000 n -0000515989 00000 n -0000516212 00000 n -0000516348 00000 n -0000521170 00000 n -0000521393 00000 n -0000521529 00000 n -0000526387 00000 n -0000526610 00000 n -0000526746 00000 n -0000531422 00000 n -0000531645 00000 n -0000531781 00000 n -0000535383 00000 n -0000535586 00000 n -0000540178 00000 n -0000540409 00000 n -0000540545 00000 n -0000540680 00000 n -0000544182 00000 n -0000544385 00000 n -0000549242 00000 n -0000549465 00000 n -0000549601 00000 n -0000554375 00000 n -0000554578 00000 n -0000559697 00000 n -0000559920 00000 n -0000560056 00000 n -0000564808 00000 n -0000565011 00000 n -0000570145 00000 n -0000570368 00000 n -0000570503 00000 n -0000575236 00000 n -0000575439 00000 n -0000580443 00000 n -0000580646 00000 n -0000585453 00000 n -0000585676 00000 n -0000585812 00000 n -0000590572 00000 n -0000590775 00000 n -0000595831 00000 n -0000596054 00000 n -0000596190 00000 n -0000600966 00000 n -0000601169 00000 n -0000606179 00000 n -0000606402 00000 n -0000606538 00000 n -0000611307 00000 n -0000611510 00000 n -0000616355 00000 n -0000616558 00000 n -0000621376 00000 n -0000621599 00000 n -0000621735 00000 n -0000626488 00000 n -0000626691 00000 n -0000630319 00000 n -0000630522 00000 n -0000633800 00000 n -0000634003 00000 n -0000639049 00000 n -0000639272 00000 n -0000639408 00000 n -0000643952 00000 n -0000644155 00000 n -0000648447 00000 n -0000648670 00000 n -0000648806 00000 n -0000652880 00000 n -0000653111 00000 n -0000653247 00000 n -0000653383 00000 n -0000658341 00000 n -0000658612 00000 n -0000658748 00000 n -0000658884 00000 n -0000659018 00000 n -0000659152 00000 n -0000659286 00000 n -0000659420 00000 n -0000659556 00000 n -0000664331 00000 n -0000664594 00000 n -0000664730 00000 n -0000664864 00000 n -0000664998 00000 n -0000665132 00000 n -0000665266 00000 n -0000665402 00000 n -0000668166 00000 n -0000668369 00000 n -0000672683 00000 n -0000672922 00000 n -0000673058 00000 n -0000673194 00000 n -0000673329 00000 n -0000677356 00000 n -0000677595 00000 n -0000677731 00000 n -0000677867 00000 n -0000678003 00000 n -0000682658 00000 n -0000682905 00000 n -0000683041 00000 n -0000683177 00000 n -0000683313 00000 n -0000683449 00000 n -0000688333 00000 n -0000688564 00000 n -0000688700 00000 n -0000688836 00000 n -0000692983 00000 n -0000693214 00000 n -0000693350 00000 n -0000693486 00000 n -0000697662 00000 n -0000697909 00000 n -0000698045 00000 n -0000698181 00000 n -0000698317 00000 n -0000698453 00000 n -0000703448 00000 n -0000703679 00000 n -0000703815 00000 n -0000703951 00000 n -0000708536 00000 n -0000708767 00000 n -0000708903 00000 n -0000709039 00000 n -0000711984 00000 n -0000712207 00000 n -0000712343 00000 n -0000716421 00000 n -0000716624 00000 n -0000722138 00000 n -0000722537 00000 n -0000722673 00000 n -0000722807 00000 n -0000722941 00000 n -0000723075 00000 n -0000723209 00000 n -0000723343 00000 n -0000723477 00000 n -0000723611 00000 n -0000723745 00000 n -0000723880 00000 n -0000724015 00000 n -0000724150 00000 n -0000724285 00000 n -0000724420 00000 n -0000724555 00000 n -0000724690 00000 n -0000724825 00000 n -0000724960 00000 n -0000725095 00000 n -0000725230 00000 n -0000725365 00000 n -0000725500 00000 n -0000725634 00000 n -0000729339 00000 n -0000729626 00000 n -0000729761 00000 n -0000729896 00000 n -0000730031 00000 n -0000730166 00000 n -0000730301 00000 n -0000730436 00000 n -0000730571 00000 n -0000730706 00000 n -0000730842 00000 n -0000735267 00000 n -0000735490 00000 n -0000735626 00000 n -0000740087 00000 n -0000740318 00000 n -0000740454 00000 n -0000740590 00000 n -0000745056 00000 n -0000745279 00000 n -0000745415 00000 n -0000750381 00000 n -0000750716 00000 n -0000750852 00000 n -0000750986 00000 n -0000751120 00000 n -0000751254 00000 n -0000751388 00000 n -0000751522 00000 n -0000751656 00000 n -0000751790 00000 n -0000751924 00000 n -0000752059 00000 n -0000752194 00000 n -0000752329 00000 n -0000752464 00000 n -0000752598 00000 n -0000752731 00000 n -0000755980 00000 n -0000756235 00000 n -0000756370 00000 n -0000756505 00000 n -0000756640 00000 n -0000756775 00000 n -0000756911 00000 n -0000760328 00000 n -0000760531 00000 n -0000763793 00000 n -0000763996 00000 n -0000768403 00000 n -0000768606 00000 n -0000773005 00000 n -0000773372 00000 n -0000773508 00000 n -0000773642 00000 n -0000773776 00000 n -0000773910 00000 n -0000774044 00000 n -0000774178 00000 n -0000774312 00000 n -0000774446 00000 n -0000774580 00000 n -0000774715 00000 n -0000774850 00000 n -0000774985 00000 n -0000775120 00000 n -0000775255 00000 n -0000775390 00000 n -0000775525 00000 n -0000775660 00000 n -0000775795 00000 n -0000775931 00000 n -0000776127 00000 n -0000776353 00000 n -0000776479 00000 n -0000776625 00000 n -0000776765 00000 n -0000776962 00000 n -0000777196 00000 n -0000777427 00000 n -0000777683 00000 n -0000777922 00000 n -0000778169 00000 n -0000778399 00000 n -0000778641 00000 n -0000778866 00000 n -0000779110 00000 n -0000779338 00000 n -0000779573 00000 n -0000779791 00000 n -0000780022 00000 n -0000780236 00000 n -0000780471 00000 n -0000780689 00000 n -0000780933 00000 n -0000781160 00000 n -0000781392 00000 n -0000781639 00000 n -0000781844 00000 n -0000782020 00000 n -0000782215 00000 n -0000782420 00000 n -0000782626 00000 n -0000782833 00000 n -0000783087 00000 n -0000783317 00000 n -0000783540 00000 n -0000783751 00000 n -0000783962 00000 n -0000784177 00000 n -0000784393 00000 n -0000784607 00000 n -0000784857 00000 n -0000785072 00000 n -0000785291 00000 n -0000785509 00000 n -0000785725 00000 n -0000785937 00000 n -0000786142 00000 n -0000786349 00000 n -0000786554 00000 n -0000786755 00000 n -0000786982 00000 n -0000787212 00000 n -0000787441 00000 n -0000787658 00000 n -0000787875 00000 n -0000788101 00000 n -0000788337 00000 n -0000788581 00000 n -0000788797 00000 n -0000789010 00000 n -0000789238 00000 n -0000789452 00000 n -0000789664 00000 n -0000789847 00000 n -0000790061 00000 n -0000790265 00000 n -0000790490 00000 n -0000790723 00000 n -0000790936 00000 n -0000791158 00000 n -0000791355 00000 n -0000791529 00000 n -0000791719 00000 n -0000791916 00000 n -0000792108 00000 n -0000792319 00000 n -0000792527 00000 n -0000792731 00000 n -0000792966 00000 n -0000793179 00000 n -0000793388 00000 n -0000793583 00000 n -0000793780 00000 n -0000793963 00000 n -0000794138 00000 n -0000794323 00000 n -0000794517 00000 n -0000794718 00000 n -0000794942 00000 n -0000795164 00000 n -0000795405 00000 n -0000795628 00000 n -0000795877 00000 n -0000796109 00000 n -0000796356 00000 n -0000796593 00000 n -0000796847 00000 n -0000797070 00000 n -0000797248 00000 n -0000797444 00000 n -0000797671 00000 n -0000797890 00000 n -0000798099 00000 n -0000798331 00000 n -0000798552 00000 n -0000798775 00000 n -0000798983 00000 n -0000799238 00000 n -0000799486 00000 n -0000799709 00000 n -0000799936 00000 n -0000800148 00000 n -0000800343 00000 n -0000800543 00000 n -0000800722 00000 n -0000800922 00000 n -0000801105 00000 n -0000801320 00000 n -0000801525 00000 n -0000801716 00000 n -0000801901 00000 n -0000802140 00000 n -0000802372 00000 n -0000802608 00000 n -0000802830 00000 n -0000803024 00000 n -0000803241 00000 n -0000803454 00000 n -0000803655 00000 n -0000803849 00000 n -0000804039 00000 n -0000804236 00000 n -0000804424 00000 n -0000804629 00000 n -0000804799 00000 n -0000804997 00000 n -0000805192 00000 n -0000805363 00000 n -0000805568 00000 n -0000805801 00000 n -0000806004 00000 n -0000806185 00000 n -0000806249 00000 n -0000814191 00000 n -0000818994 00000 n -0000830855 00000 n -0000843251 00000 n -0000843485 00000 n -0000843911 00000 n -0000844737 00000 n -0000844890 00000 n -0000845121 00000 n -0000845718 00000 n -0000847203 00000 n -0000847353 00000 n -0000847588 00000 n -0000848127 00000 n -0000849364 00000 n -0000849517 00000 n -0000849761 00000 n -0000850356 00000 n -0000851981 00000 n -0000852138 00000 n -trailer -<< -/Size 1079 -/Root 3 0 R -/Info 2 0 R ->> -startxref -852230 -%%EOF diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/rke-1.6-benchmark-2.6.md b/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/rke-1.6-benchmark-2.6.md deleted file mode 100644 index 3f561e5ff67..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-benchmark-2.6/rke-1.6-benchmark-2.6.md +++ /dev/null @@ -1,3100 +0,0 @@ ---- -title: RKE CIS v1.6 Benchmark - Self-Assessment Guide - Rancher v2.6 -weight: 101 -aliases: - - /rancher/v2.6/en/security/hardening-guides/1.6-benchmark-2.6/ ---- - -### RKE CIS v1.6 Kubernetes Benchmark - Rancher v2.6 with Kubernetes v1.18 to v1.23 - -[Click here to download a PDF version of this document](https://releases.rancher.com/documents/security/2.6/Rancher_v2-6_CIS_v1-6_Benchmark_Assessment.pdf). - -#### Overview - -This document is a companion to the [Rancher v2.6 RKE security hardening guide]({{}}/rancher/v2.6/en/security/hardening-guides/rke-1.6-hardening-2.6/). The hardening guide provides prescriptive guidance for hardening a production installation of Rancher, and this benchmark guide is meant to help you evaluate the level of security of the hardened cluster against each control in the benchmark. - -This guide corresponds to specific versions of the hardening guide, Rancher, CIS Benchmark and Kubernetes: - -| Hardening Guide Version | Rancher Version | CIS Benchmark Version | Kubernetes Version | -| ----------------------- | --------------- | --------------------- | ------------------- | -| Hardening Guide CIS v1.6 Benchmark | Rancher v2.6 | CIS v1.6 | Kubernetes v1.18 up to v1.23 | - -Because Rancher and RKE install Kubernetes services as Docker containers, many of the control verification checks in the CIS Kubernetes Benchmark do not apply and will have a result of `Not Applicable`. This guide will walk through the various controls and provide updated example commands to audit compliance in Rancher created clusters. - -This document is to be used by Rancher operators, security teams, auditors and decision makers. - -For more detail about each audit, including rationales and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). - -#### Testing controls methodology - -Rancher and RKE install Kubernetes services via Docker containers. Configuration is defined by arguments passed to the container at the time of initialization, not via configuration files. - -Where control audits differ from the original CIS benchmark, the audit commands specific to Rancher are provided for testing. When performing the tests, you will need access to the command line on the hosts of all RKE nodes. The commands also make use of the [kubectl](https://kubernetes.io/docs/tasks/tools/) (with a valid configuration file) and [jq](https://stedolan.github.io/jq/) tools, which are required in the testing and evaluation of test results. - -> NOTE: Only `automated` tests (previously called `scored`) are covered in this guide. - -### Controls -## 1.1 Master Node Configuration Files -### 1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for kube-apiserver. -All configuration is passed in as arguments at container run time. - -### 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for kube-apiserver. -All configuration is passed in as arguments at container run time. - -### 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for controller-manager. -All configuration is passed in as arguments at container run time. - -### 1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for controller-manager. -All configuration is passed in as arguments at container run time. - -### 1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for scheduler. -All configuration is passed in as arguments at container run time. - -### 1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for scheduler. -All configuration is passed in as arguments at container run time. - -### 1.1.7 Ensure that the etcd pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for etcd. -All configuration is passed in as arguments at container run time. - -### 1.1.8 Ensure that the etcd pod specification file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for etcd. -All configuration is passed in as arguments at container run time. - -### 1.1.9 Ensure that the Container Network Interface file permissions are set to 644 or more restrictive (Manual) - - -**Result:** warn - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 - -**Audit:** - -```bash -stat -c permissions=%a -``` - -### 1.1.10 Ensure that the Container Network Interface file ownership is set to root:root (Manual) - - -**Result:** warn - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root - -**Audit:** - -```bash -stat -c %U:%G -``` - -### 1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -On the etcd server node, get the etcd data directory, passed as an argument --data-dir, -from the below command: -ps -ef | grep etcd Run the below command (based on the etcd data directory found above). For example, -chmod 700 /var/lib/etcd - -**Audit:** - -```bash -stat -c %a /node/var/lib/etcd -``` - -**Expected Result**: - -```console -'700' is equal to '700' -``` - -**Returned Value**: - -```console -700 -``` - -### 1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd (Automated) - - -**Result:** pass - -**Remediation:** -On the etcd server node, get the etcd data directory, passed as an argument --data-dir, -from the below command: -ps -ef | grep etcd -Run the below command (based on the etcd data directory found above). -For example, chown etcd:etcd /var/lib/etcd - -A system service account is required for etcd data directory ownership. -Refer to Rancher's hardening guide for more details on how to configure this ownership. - -**Audit:** - -```bash -stat -c %U:%G /node/var/lib/etcd -``` - -**Expected Result**: - -```console -'etcd:etcd' is present -``` - -**Returned Value**: - -```console -etcd:etcd -``` - -### 1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE does not store the kubernetes default kubeconfig credentials file on the nodes. - -### 1.1.14 Ensure that the admin.conf file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE does not store the kubernetes default kubeconfig credentials file on the nodes. - -### 1.1.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for scheduler. -All configuration is passed in as arguments at container run time. - -### 1.1.16 Ensure that the scheduler.conf file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for scheduler. -All configuration is passed in as arguments at container run time. - -### 1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for controller-manager. -All configuration is passed in as arguments at container run time. - -### 1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn't require or maintain a configuration file for controller-manager. -All configuration is passed in as arguments at container run time. - -### 1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown -R root:root /etc/kubernetes/pki/ - -**Audit Script:** `check_files_owner_in_dir.sh` - -```bash -#!/usr/bin/env bash - -# This script is used to ensure the owner is set to root:root for -# the given directory and all the files in it -# -# inputs: -# $1 = /full/path/to/directory -# -# outputs: -# true/false - -INPUT_DIR=$1 - -if [[ "${INPUT_DIR}" == "" ]]; then - echo "false" - exit -fi - -if [[ $(stat -c %U:%G ${INPUT_DIR}) != "root:root" ]]; then - echo "false" - exit -fi - -statInfoLines=$(stat -c "%n %U:%G" ${INPUT_DIR}/*) -while read -r statInfoLine; do - f=$(echo ${statInfoLine} | cut -d' ' -f1) - p=$(echo ${statInfoLine} | cut -d' ' -f2) - - if [[ $(basename "$f" .pem) == "kube-etcd-"* ]]; then - if [[ "$p" != "root:root" && "$p" != "etcd:etcd" ]]; then - echo "false" - exit - fi - else - if [[ "$p" != "root:root" ]]; then - echo "false" - exit - fi - fi -done <<< "${statInfoLines}" - - -echo "true" -exit - -``` - -**Audit Execution:** - -```bash -./check_files_owner_in_dir.sh /node/etc/kubernetes/ssl -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -### 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod -R 644 /etc/kubernetes/pki/*.crt - -**Audit Script:** `check_files_permissions.sh` - -```bash -#!/usr/bin/env bash - -# This script is used to ensure the file permissions are set to 644 or -# more restrictive for all files in a given directory or a wildcard -# selection of files -# -# inputs: -# $1 = /full/path/to/directory or /path/to/fileswithpattern -# ex: !(*key).pem -# -# $2 (optional) = permission (ex: 600) -# -# outputs: -# true/false - -# Turn on "extended glob" for use of '!' in wildcard -shopt -s extglob - -# Turn off history to avoid surprises when using '!' -set -H - -USER_INPUT=$1 - -if [[ "${USER_INPUT}" == "" ]]; then - echo "false" - exit -fi - - -if [[ -d ${USER_INPUT} ]]; then - PATTERN="${USER_INPUT}/*" -else - PATTERN="${USER_INPUT}" -fi - -PERMISSION="" -if [[ "$2" != "" ]]; then - PERMISSION=$2 -fi - -FILES_PERMISSIONS=$(stat -c %n\ %a ${PATTERN}) - -while read -r fileInfo; do - p=$(echo ${fileInfo} | cut -d' ' -f2) - - if [[ "${PERMISSION}" != "" ]]; then - if [[ "$p" != "${PERMISSION}" ]]; then - echo "false" - exit - fi - else - if [[ "$p" != "644" && "$p" != "640" && "$p" != "600" ]]; then - echo "false" - exit - fi - fi -done <<< "${FILES_PERMISSIONS}" - - -echo "true" -exit - -``` - -**Audit Execution:** - -```bash -./check_files_permissions.sh /node/etc/kubernetes/ssl/!(*key).pem -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -### 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod -R 600 /etc/kubernetes/ssl/*key.pem - -**Audit Script:** `check_files_permissions.sh` - -```bash -#!/usr/bin/env bash - -# This script is used to ensure the file permissions are set to 644 or -# more restrictive for all files in a given directory or a wildcard -# selection of files -# -# inputs: -# $1 = /full/path/to/directory or /path/to/fileswithpattern -# ex: !(*key).pem -# -# $2 (optional) = permission (ex: 600) -# -# outputs: -# true/false - -# Turn on "extended glob" for use of '!' in wildcard -shopt -s extglob - -# Turn off history to avoid surprises when using '!' -set -H - -USER_INPUT=$1 - -if [[ "${USER_INPUT}" == "" ]]; then - echo "false" - exit -fi - - -if [[ -d ${USER_INPUT} ]]; then - PATTERN="${USER_INPUT}/*" -else - PATTERN="${USER_INPUT}" -fi - -PERMISSION="" -if [[ "$2" != "" ]]; then - PERMISSION=$2 -fi - -FILES_PERMISSIONS=$(stat -c %n\ %a ${PATTERN}) - -while read -r fileInfo; do - p=$(echo ${fileInfo} | cut -d' ' -f2) - - if [[ "${PERMISSION}" != "" ]]; then - if [[ "$p" != "${PERMISSION}" ]]; then - echo "false" - exit - fi - else - if [[ "$p" != "644" && "$p" != "640" && "$p" != "600" ]]; then - echo "false" - exit - fi - fi -done <<< "${FILES_PERMISSIONS}" - - -echo "true" -exit - -``` - -**Audit Execution:** - -```bash -./check_files_permissions.sh /node/etc/kubernetes/ssl/*key.pem -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -## 1.2 API Server -### 1.2.1 Ensure that the --anonymous-auth argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---anonymous-auth=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.2 Ensure that the --basic-auth-file argument is not set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and configure alternate mechanisms for authentication. Then, -edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and remove the `--basic-auth-file=` parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--basic-auth-file' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.3 Ensure that the --token-auth-file parameter is not set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and configure alternate mechanisms for authentication. Then, -edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and remove the `--token-auth-file=` parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--token-auth-file' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.4 Ensure that the --kubelet-https argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and remove the --kubelet-https parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--kubelet-https' is not present OR '--kubelet-https' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection between the -apiserver and kubelets. Then, edit API server pod specification file -/etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the -kubelet client certificate and key parameters as below. ---kubelet-client-certificate= ---kubelet-client-key= - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--kubelet-client-certificate' is present AND '--kubelet-client-key' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and setup the TLS connection between -the apiserver and kubelets. Then, edit the API server pod specification file -/etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the -`--kubelet-certificate-authority` parameter to the path to the cert file for the certificate authority. -`--kubelet-certificate-authority=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--kubelet-certificate-authority' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --authorization-mode parameter to values other than AlwaysAllow. -One such example could be as below. ---authorization-mode=RBAC - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'Node,RBAC' not have 'AlwaysAllow' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.8 Ensure that the --authorization-mode argument includes Node (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --authorization-mode parameter to a value that includes Node. ---authorization-mode=Node,RBAC - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'Node,RBAC' has 'Node' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.9 Ensure that the --authorization-mode argument includes RBAC (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --authorization-mode parameter to a value that includes RBAC, -for example: ---authorization-mode=Node,RBAC - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'Node,RBAC' has 'RBAC' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.10 Ensure that the admission control plugin EventRateLimit is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set the desired limits in a configuration file. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -and set the below parameters. ---enable-admission-plugins=...,EventRateLimit,... ---admission-control-config-file= - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit' has 'EventRateLimit' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and either remove the --enable-admission-plugins parameter, or set it to a -value that does not include AlwaysAdmit. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit' not have 'AlwaysAdmit' OR '--enable-admission-plugins' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.12 Ensure that the admission control plugin AlwaysPullImages is set (Manual) - - -**Result:** warn - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to include -AlwaysPullImages. ---enable-admission-plugins=...,AlwaysPullImages,... - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -### 1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Manual) - - -**Result:** warn - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to include -SecurityContextDeny, unless PodSecurityPolicy is already in place. ---enable-admission-plugins=...,SecurityContextDeny,... - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -### 1.2.14 Ensure that the admission control plugin ServiceAccount is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and create ServiceAccount objects as per your environment. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and ensure that the --disable-admission-plugins parameter is set to a -value that does not include ServiceAccount. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--disable-admission-plugins' is not present OR '--disable-admission-plugins' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --disable-admission-plugins parameter to -ensure it does not include NamespaceLifecycle. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--disable-admission-plugins' is not present OR '--disable-admission-plugins' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and create Pod Security Policy objects as per your environment. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to a -value that includes PodSecurityPolicy: ---enable-admission-plugins=...,PodSecurityPolicy,... -Then restart the API Server. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit' has 'PodSecurityPolicy' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.17 Ensure that the admission control plugin NodeRestriction is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to a -value that includes NodeRestriction. ---enable-admission-plugins=...,NodeRestriction,... - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit' has 'NodeRestriction' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.18 Ensure that the --insecure-bind-address argument is not set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and remove the --insecure-bind-address parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--insecure-bind-address' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.19 Ensure that the --insecure-port argument is set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---insecure-port=0 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'0' is equal to '0' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.20 Ensure that the --secure-port argument is not set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and either remove the --secure-port parameter or -set it to a different (non-zero) desired port. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -6443 is greater than 0 OR '--secure-port' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.21 Ensure that the --profiling argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---profiling=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.22 Ensure that the --audit-log-path argument is set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --audit-log-path parameter to a suitable path and -file where you would like audit logs to be written, for example: ---audit-log-path=/var/log/apiserver/audit.log - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--audit-log-path' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.23 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --audit-log-maxage parameter to 30 or as an appropriate number of days: ---audit-log-maxage=30 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -30 is greater or equal to 30 -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.24 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --audit-log-maxbackup parameter to 10 or to an appropriate -value. ---audit-log-maxbackup=10 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -10 is greater or equal to 10 -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.25 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --audit-log-maxsize parameter to an appropriate size in MB. -For example, to set it as 100 MB: ---audit-log-maxsize=100 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -100 is greater or equal to 100 -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.26 Ensure that the --request-timeout argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -and set the below parameter as appropriate and if needed. -For example, ---request-timeout=300s - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--request-timeout' is not present OR '--request-timeout' is not present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.27 Ensure that the --service-account-lookup argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---service-account-lookup=true -Alternatively, you can delete the --service-account-lookup parameter from this file so -that the default takes effect. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--service-account-lookup' is not present OR 'true' is equal to 'true' -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.28 Ensure that the --service-account-key-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --service-account-key-file parameter -to the public key file for service accounts: -`--service-account-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--service-account-key-file' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the etcd certificate and key file parameters. -`--etcd-certfile=` -`--etcd-keyfile=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--etcd-certfile' is present AND '--etcd-keyfile' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection on the apiserver. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the TLS certificate and private key file parameters. -`--tls-cert-file=` -`--tls-private-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--tls-cert-file' is present AND '--tls-private-key-file' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.31 Ensure that the --client-ca-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection on the apiserver. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the client certificate authority file. -`--client-ca-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--client-ca-file' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.32 Ensure that the --etcd-cafile argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the etcd certificate authority file parameter. -`--etcd-cafile=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--etcd-cafile' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.33 Ensure that the --encryption-provider-config argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and configure a EncryptionConfig file. -Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the --encryption-provider-config parameter to the path of that file: --encryption-provider-config= - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--encryption-provider-config' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 1.2.34 Ensure that encryption providers are appropriately configured (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and configure a EncryptionConfig file. -In this file, choose aescbc, kms or secretbox as the encryption provider. - -**Audit Script:** `check_encryption_provider_config.sh` - -```bash -#!/usr/bin/env bash - -# This script is used to check the encrption provider config is set to aesbc -# -# outputs: -# true/false - -# TODO: Figure out the file location from the kube-apiserver commandline args -ENCRYPTION_CONFIG_FILE="/node/etc/kubernetes/ssl/encryption.yaml" - -if [[ ! -f "${ENCRYPTION_CONFIG_FILE}" ]]; then - echo "false" - exit -fi - -for provider in "$@" -do - if grep "$provider" "${ENCRYPTION_CONFIG_FILE}"; then - echo "true" - exit - fi -done - -echo "false" -exit - -``` - -**Audit Execution:** - -```bash -./check_encryption_provider_config.sh aescbc -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -- aescbc: true -``` - -### 1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Automated) - - -**Result:** warn - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM -_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM -_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM -_SHA384 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -## 1.3 Controller Manager -### 1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node and set the --terminated-pod-gc-threshold to an appropriate threshold, -for example: ---terminated-pod-gc-threshold=10 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'--terminated-pod-gc-threshold' is present -``` - -**Returned Value**: - -```console -root 121366 121346 1 12:27 ? 00:01:13 kube-controller-manager --cluster-cidr=10.42.0.0/16 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --allocate-node-cidrs=true --configure-cloud-routes=false --leader-elect=true --pod-eviction-timeout=5m0s --authentication-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --feature-gates=RotateKubeletServerCertificate=true --bind-address=127.0.0.1 --enable-hostpath-provisioner=false --address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --cloud-provider= --service-account-private-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --service-cluster-ip-range=10.43.0.0/16 --authorization-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --root-ca-file=/etc/kubernetes/ssl/kube-ca.pem --node-monitor-grace-period=40s --profiling=false --terminated-pod-gc-threshold=1000 --v=2 --allow-untagged-cloud=true --use-service-account-credentials=true -``` - -### 1.3.2 Ensure that the --profiling argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node and set the below parameter. ---profiling=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 121366 121346 1 12:27 ? 00:01:13 kube-controller-manager --cluster-cidr=10.42.0.0/16 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --allocate-node-cidrs=true --configure-cloud-routes=false --leader-elect=true --pod-eviction-timeout=5m0s --authentication-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --feature-gates=RotateKubeletServerCertificate=true --bind-address=127.0.0.1 --enable-hostpath-provisioner=false --address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --cloud-provider= --service-account-private-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --service-cluster-ip-range=10.43.0.0/16 --authorization-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --root-ca-file=/etc/kubernetes/ssl/kube-ca.pem --node-monitor-grace-period=40s --profiling=false --terminated-pod-gc-threshold=1000 --v=2 --allow-untagged-cloud=true --use-service-account-credentials=true -``` - -### 1.3.3 Ensure that the --use-service-account-credentials argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node to set the below parameter. ---use-service-account-credentials=true - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'true' is not equal to 'false' -``` - -**Returned Value**: - -```console -root 121366 121346 1 12:27 ? 00:01:13 kube-controller-manager --cluster-cidr=10.42.0.0/16 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --allocate-node-cidrs=true --configure-cloud-routes=false --leader-elect=true --pod-eviction-timeout=5m0s --authentication-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --feature-gates=RotateKubeletServerCertificate=true --bind-address=127.0.0.1 --enable-hostpath-provisioner=false --address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --cloud-provider= --service-account-private-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --service-cluster-ip-range=10.43.0.0/16 --authorization-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --root-ca-file=/etc/kubernetes/ssl/kube-ca.pem --node-monitor-grace-period=40s --profiling=false --terminated-pod-gc-threshold=1000 --v=2 --allow-untagged-cloud=true --use-service-account-credentials=true -``` - -### 1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node and set the --service-account-private-key-file parameter -to the private key file for service accounts. -`--service-account-private-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'--service-account-private-key-file' is present -``` - -**Returned Value**: - -```console -root 121366 121346 1 12:27 ? 00:01:13 kube-controller-manager --cluster-cidr=10.42.0.0/16 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --allocate-node-cidrs=true --configure-cloud-routes=false --leader-elect=true --pod-eviction-timeout=5m0s --authentication-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --feature-gates=RotateKubeletServerCertificate=true --bind-address=127.0.0.1 --enable-hostpath-provisioner=false --address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --cloud-provider= --service-account-private-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --service-cluster-ip-range=10.43.0.0/16 --authorization-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --root-ca-file=/etc/kubernetes/ssl/kube-ca.pem --node-monitor-grace-period=40s --profiling=false --terminated-pod-gc-threshold=1000 --v=2 --allow-untagged-cloud=true --use-service-account-credentials=true -``` - -### 1.3.5 Ensure that the --root-ca-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node and set the --root-ca-file parameter to the certificate bundle file`. -`--root-ca-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'--root-ca-file' is present -``` - -**Returned Value**: - -```console -root 121366 121346 1 12:27 ? 00:01:13 kube-controller-manager --cluster-cidr=10.42.0.0/16 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --allocate-node-cidrs=true --configure-cloud-routes=false --leader-elect=true --pod-eviction-timeout=5m0s --authentication-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --feature-gates=RotateKubeletServerCertificate=true --bind-address=127.0.0.1 --enable-hostpath-provisioner=false --address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --cloud-provider= --service-account-private-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --service-cluster-ip-range=10.43.0.0/16 --authorization-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --root-ca-file=/etc/kubernetes/ssl/kube-ca.pem --node-monitor-grace-period=40s --profiling=false --terminated-pod-gc-threshold=1000 --v=2 --allow-untagged-cloud=true --use-service-account-credentials=true -``` - -### 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true. ---feature-gates=RotateKubeletServerCertificate=true - -Cluster provisioned by RKE handles certificate rotation directly through RKE. - -### 1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml -on the master node and ensure the correct value for the --bind-address parameter - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'127.0.0.1' is equal to '127.0.0.1' OR '--bind-address' is not present -``` - -**Returned Value**: - -```console -root 121366 121346 1 12:27 ? 00:01:13 kube-controller-manager --cluster-cidr=10.42.0.0/16 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --allocate-node-cidrs=true --configure-cloud-routes=false --leader-elect=true --pod-eviction-timeout=5m0s --authentication-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --feature-gates=RotateKubeletServerCertificate=true --bind-address=127.0.0.1 --enable-hostpath-provisioner=false --address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --cloud-provider= --service-account-private-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --service-cluster-ip-range=10.43.0.0/16 --authorization-kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-controller-manager.yaml --root-ca-file=/etc/kubernetes/ssl/kube-ca.pem --node-monitor-grace-period=40s --profiling=false --terminated-pod-gc-threshold=1000 --v=2 --allow-untagged-cloud=true --use-service-account-credentials=true -``` - -## 1.4 Scheduler -### 1.4.1 Ensure that the --profiling argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Scheduler pod specification file /etc/kubernetes/manifests/kube-scheduler.yaml file -on the master node and set the below parameter. ---profiling=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-scheduler | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 121587 121567 0 12:27 ? 00:00:12 kube-scheduler --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-scheduler.yaml --address=127.0.0.1 --leader-elect=true --profiling=false --v=2 --bind-address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 -``` - -### 1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Scheduler pod specification file /etc/kubernetes/manifests/kube-scheduler.yaml -on the master node and ensure the correct value for the --bind-address parameter - -**Audit:** - -```bash -/bin/ps -ef | grep kube-scheduler | grep -v grep -``` - -**Expected Result**: - -```console -'127.0.0.1' is equal to '127.0.0.1' OR '--bind-address' is not present -``` - -**Returned Value**: - -```console -root 121587 121567 0 12:27 ? 00:00:12 kube-scheduler --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-scheduler.yaml --address=127.0.0.1 --leader-elect=true --profiling=false --v=2 --bind-address=127.0.0.1 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 -``` - -## 2 Etcd Node Configuration Files -### 2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the etcd service documentation and configure TLS encryption. -Then, edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml -on the master node and set the below parameters. -`--cert-file=` -`--key-file=` - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--cert-file' is present AND '--key-file' is present -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 2 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.2 Ensure that the --client-cert-auth argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the master -node and set the below parameter. ---client-cert-auth="true" - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--client-cert-auth' is present OR 'true' is equal to 'true' -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 2 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.3 Ensure that the --auto-tls argument is not set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the master -node and either remove the --auto-tls parameter or set it to false. - --auto-tls=false - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--auto-tls' is not present OR '--auto-tls' is not present -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 1 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the etcd service documentation and configure peer TLS encryption as appropriate -for your etcd cluster. -Then, edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the -master node and set the below parameters. -`--peer-client-file=` -`--peer-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--peer-cert-file' is present AND '--peer-key-file' is present -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 5 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.5 Ensure that the --peer-client-cert-auth argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the master -node and set the below parameter. ---peer-client-cert-auth=true - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--peer-client-cert-auth' is present OR 'true' is equal to 'true' -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 4 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.6 Ensure that the --peer-auto-tls argument is not set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the master -node and either remove the --peer-auto-tls parameter or set it to false. ---peer-auto-tls=false - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--peer-auto-tls' is not present OR '--peer-auto-tls' is present -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 4 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.7 Ensure that a unique Certificate Authority is used for etcd (Automated) - - -**Result:** pass - -**Remediation:** -[Manual test] -Follow the etcd documentation and create a dedicated certificate authority setup for the -etcd service. -Then, edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the -master node and set the below parameter. -`--trusted-ca-file=` - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--trusted-ca-file' is present -``` - -**Returned Value**: - -```console -etcd 120679 120657 1 12:27 ? 00:01:17 /usr/local/bin/etcd --trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --heartbeat-interval=500 --election-timeout=5000 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd-=https://:2380 --peer-trusted-ca-file=/etc/kubernetes/ssl/kube-ca.pem --peer-cert-file=/etc/kubernetes/ssl/kube-etcd-.pem --peer-key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --peer-client-cert-auth=true --data-dir=/var/lib/rancher/etcd/ --initial-advertise-peer-urls=https://:2380 --initial-cluster-state=new --advertise-client-urls=https://:2379 --client-cert-auth=true --enable-v2=true --name=etcd- --listen-client-urls=https://:2379 --listen-peer-urls=https://:2380 --key-file=/etc/kubernetes/ssl/kube-etcd--key.pem --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 root 120728 120707 0 12:27 ? 00:00:00 /opt/rke-tools/rke-etcd-backup etcd-backup save --cacert /etc/kubernetes/ssl/kube-ca.pem --cert /etc/kubernetes/ssl/kube-node.pem --key /etc/kubernetes/ssl/kube-node-key.pem --name etcd-rolling-snapshots --endpoints=:2379 --retention=72h --creation=12h root 121142 121120 7 12:27 ? 00:06:27 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json root 214939 214868 3 13:56 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -## 3.1 Authentication and Authorization -### 3.1.1 Client certificate authentication should not be used for users (Manual) - - -**Result:** warn - -**Remediation:** -Alternative mechanisms provided by Kubernetes such as the use of OIDC should be -implemented in place of client certificates. - -## 3.2 Logging -### 3.2.1 Ensure that a minimal audit policy is created (Automated) - - -**Result:** pass - -**Remediation:** -Create an audit policy file for your cluster. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--audit-policy-file' is present -``` - -**Returned Value**: - -```console -root 121142 121120 7 12:27 ? 00:06:28 kube-apiserver --audit-log-maxsize=100 --etcd-keyfile=/etc/kubernetes/ssl/kube-node-key.pem --service-cluster-ip-range=10.43.0.0/16 --encryption-provider-config=/etc/kubernetes/ssl/encryption.yaml --requestheader-username-headers=X-Remote-User --bind-address=0.0.0.0 --advertise-address= --requestheader-allowed-names=kube-apiserver-proxy-client --etcd-certfile=/etc/kubernetes/ssl/kube-node.pem --requestheader-client-ca-file=/etc/kubernetes/ssl/kube-apiserver-requestheader-ca.pem --allow-privileged=true --requestheader-extra-headers-prefix=X-Remote-Extra- --admission-control-config-file=/etc/kubernetes/admission.yaml --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --service-account-lookup=true --runtime-config=policy/v1beta1/podsecuritypolicy=true --authorization-mode=Node,RBAC --audit-log-maxage=30 --profiling=false --storage-backend=etcd3 --etcd-cafile=/etc/kubernetes/ssl/kube-ca.pem --etcd-servers=https://:2379 --kubelet-certificate-authority=/etc/kubernetes/ssl/kube-ca.pem --secure-port=6443 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --insecure-port=0 --api-audiences=unknown --audit-policy-file=/etc/kubernetes/audit-policy.yaml --etcd-prefix=/registry --kubelet-client-certificate=/etc/kubernetes/ssl/kube-apiserver.pem --kubelet-client-key=/etc/kubernetes/ssl/kube-apiserver-key.pem --proxy-client-key-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client-key.pem --service-account-issuer=rke --service-account-signing-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --requestheader-group-headers=X-Remote-Group --cloud-provider= --proxy-client-cert-file=/etc/kubernetes/ssl/kube-apiserver-proxy-client.pem --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kube-apiserver.pem --tls-private-key-file=/etc/kubernetes/ssl/kube-apiserver-key.pem --anonymous-auth=false --audit-log-path=/var/log/kube-audit/audit-log.json --audit-log-maxbackup=10 --service-account-key-file=/etc/kubernetes/ssl/kube-service-account-token-key.pem --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,NodeRestriction,Priority,TaintNodesByCondition,PersistentVolumeClaimResize,PodSecurityPolicy,EventRateLimit --audit-log-format=json -``` - -### 3.2.2 Ensure that the audit policy covers key security concerns (Manual) - - -**Result:** warn - -**Remediation:** -Consider modification of the audit policy in use on the cluster to include these items, at a -minimum. - -## 4.1 Worker Node Configuration Files -### 4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn’t require or maintain a configuration file for the kubelet service. -All configuration is passed in as arguments at container run time. - -### 4.1.2 Ensure that the kubelet service file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Cluster provisioned by RKE doesn’t require or maintain a configuration file for the kubelet service. -All configuration is passed in as arguments at container run time. - -### 4.1.3 If proxy kubeconfig file exists ensure permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chmod 644 $proykubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /node/etc/kubernetes/ssl/kubecfg-kube-proxy.yaml; then stat -c %a /node/etc/kubernetes/ssl/kubecfg-kube-proxy.yaml; fi' -``` - -**Expected Result**: - -```console -'644' is present OR '640' is present OR '600' is equal to '600' OR '444' is present OR '440' is present OR '400' is present OR '000' is present -``` - -**Returned Value**: - -```console -600 -``` - -### 4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, chown root:root /etc/kubernetes/ssl/kubecfg-kube-proxy.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /etc/kubernetes/ssl/kubecfg-kube-proxy.yaml; then stat -c %U:%G /etc/kubernetes/ssl/kubecfg-kube-proxy.yaml; fi' -``` - -**Expected Result**: - -```console -'root:root' is not present OR '/etc/kubernetes/ssl/kubecfg-kube-proxy.yaml' is not present -``` - -### 4.1.5 Ensure that the --kubeconfig kubelet.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chmod 644 /etc/kubernetes/ssl/kubecfg-kube-node.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /etc/kubernetes/ssl/kubecfg-kube-node.yaml; then stat -c permissions=%a /etc/kubernetes/ssl/kubecfg-kube-node.yaml; fi' -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -### 4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chown root:root /etc/kubernetes/ssl/kubecfg-kube-node.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /node/etc/kubernetes/ssl/kubecfg-kube-node.yaml; then stat -c %U:%G /node/etc/kubernetes/ssl/kubecfg-kube-node.yaml; fi' -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the following command to modify the file permissions of the -`--client-ca-file chmod 644 ` - -**Audit Script:** `check_cafile_permissions.sh` - -```bash -#!/usr/bin/env bash - -CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}') -if test -z $CAFILE; then CAFILE=$kubeletcafile; fi -if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi - -``` - -**Audit Execution:** - -```bash -./check_cafile_permissions.sh -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -### 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the following command to modify the ownership of the --client-ca-file. -`chown root:root ` - -**Audit Script:** `check_cafile_ownership.sh` - -```bash -#!/usr/bin/env bash - -CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}') -if test -z $CAFILE; then CAFILE=$kubeletcafile; fi -if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi - -``` - -**Audit Execution:** - -```bash -./check_cafile_ownership.sh -``` - -**Expected Result**: - -```console -'root:root' is not present -``` - -### 4.1.9 Ensure that the kubelet --config configuration file has permissions set to 644 or more restrictive (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Run the following command (using the config file location identified in the Audit step) -chmod 644 /var/lib/kubelet/config.yaml - -Clusters provisioned by RKE doesn’t require or maintain a configuration file for the kubelet. -All configuration is passed in as arguments at container run time. - -### 4.1.10 Ensure that the kubelet --config configuration file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Run the following command (using the config file location identified in the Audit step) -chown root:root /var/lib/kubelet/config.yaml - -Clusters provisioned by RKE doesn’t require or maintain a configuration file for the kubelet. -All configuration is passed in as arguments at container run time. - -## 4.2 Kubelet -### 4.2.1 Ensure that the anonymous-auth argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set authentication: anonymous: enabled to -false. -If using executable arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---anonymous-auth=false -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present -``` - -### 4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set authorization: mode to Webhook. If -using executable arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_AUTHZ_ARGS variable. ---authorization-mode=Webhook -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present -``` - -### 4.2.3 Ensure that the --client-ca-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set authentication: x509: clientCAFile to -the location of the client CA file. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_AUTHZ_ARGS variable. -`--client-ca-file=` -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present -``` - -### 4.2.4 Ensure that the --read-only-port argument is set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set readOnlyPort to 0. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---read-only-port=0 -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present OR '' is not present -``` - -### 4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set streamingConnectionIdleTimeout to a -value other than 0. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---streaming-connection-idle-timeout=5m -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'30m' is not equal to '0' OR '--streaming-connection-idle-timeout' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 121813 121792 4 12:27 ? 00:03:37 kubelet --fail-swap-on=false --resolv-conf=/etc/resolv.conf --authorization-mode=Webhook --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-node.yaml --v=2 --volume-plugin-dir=/var/lib/kubelet/volumeplugins --address=0.0.0.0 --make-iptables-util-chains=true --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --hostname-override= --tls-cert-file=/etc/kubernetes/ssl/kube-kubelet-.pem --network-plugin=cni --streaming-connection-idle-timeout=30m --root-dir=/var/lib/kubelet --event-qps=0 --feature-gates=RotateKubeletServerCertificate=true --protect-kernel-defaults=true --cloud-provider= --tls-private-key-file=/etc/kubernetes/ssl/kube-kubelet--key.pem --cgroups-per-qos=True --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --pod-infra-container-image=rancher/mirrored-pause:3.5 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --anonymous-auth=false --authentication-token-webhook=true --node-ip= --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --read-only-port=0 --cgroup-driver=cgroupfs --resolv-conf=/run/systemd/resolve/resolv.conf -``` - -### 4.2.6 Ensure that the --protect-kernel-defaults argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set protectKernelDefaults: true. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---protect-kernel-defaults=true -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present -``` - -### 4.2.7 Ensure that the --make-iptables-util-chains argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set makeIPTablesUtilChains: true. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -remove the --make-iptables-util-chains argument from the -KUBELET_SYSTEM_PODS_ARGS variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present OR '' is not present -``` - -### 4.2.8 Ensure that the --hostname-override argument is not set (Manual) - - -**Result:** Not Applicable - -**Remediation:** -Edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf -on each worker node and remove the --hostname-override argument from the -KUBELET_SYSTEM_PODS_ARGS variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -Clusters provisioned by RKE set the --hostname-override to avoid any hostname configuration errors - -### 4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set eventRecordQPS: to an appropriate level. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present -``` - -### 4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set tlsCertFile to the location -of the certificate file to use to identify this Kubelet, and tlsPrivateKeyFile -to the location of the corresponding private key file. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameters in KUBELET_CERTIFICATE_ARGS variable. -`--tls-cert-file=` -`--tls-private-key-file=` -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present AND '' is not present -``` - -### 4.2.11 Ensure that the --rotate-certificates argument is not set to false (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to add the line rotateCertificates: true or -remove it altogether to use the default value. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS -variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'--rotate-certificates' is not present OR '--rotate-certificates' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 121813 121792 4 12:27 ? 00:03:37 kubelet --fail-swap-on=false --resolv-conf=/etc/resolv.conf --authorization-mode=Webhook --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-node.yaml --v=2 --volume-plugin-dir=/var/lib/kubelet/volumeplugins --address=0.0.0.0 --make-iptables-util-chains=true --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --hostname-override= --tls-cert-file=/etc/kubernetes/ssl/kube-kubelet-.pem --network-plugin=cni --streaming-connection-idle-timeout=30m --root-dir=/var/lib/kubelet --event-qps=0 --feature-gates=RotateKubeletServerCertificate=true --protect-kernel-defaults=true --cloud-provider= --tls-private-key-file=/etc/kubernetes/ssl/kube-kubelet--key.pem --cgroups-per-qos=True --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --pod-infra-container-image=rancher/mirrored-pause:3.5 --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --anonymous-auth=false --authentication-token-webhook=true --node-ip= --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --read-only-port=0 --cgroup-driver=cgroupfs --resolv-conf=/run/systemd/resolve/resolv.conf -``` - -### 4.2.12 Verify that the RotateKubeletServerCertificate argument is set to true (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf -on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable. ---feature-gates=RotateKubeletServerCertificate=true -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -Clusters provisioned by RKE handles certificate rotation directly through RKE. - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -### 4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set TLSCipherSuites: to -TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 -or to a subset of these values. -If using executable arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the --tls-cipher-suites parameter as follows, or to a subset of these values. ---tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/kubelet/config.yaml -``` - -**Expected Result**: - -```console -'' is not present -``` - -## 5.1 RBAC and Service Accounts -### 5.1.1 Ensure that the cluster-admin role is only used where required (Manual) - - -**Result:** warn - -**Remediation:** -Identify all clusterrolebindings to the cluster-admin role. Check if they are used and -if they need this role or if they could use a role with fewer privileges. -Where possible, first bind users to a lower privileged role and then remove the -clusterrolebinding to the cluster-admin role : -kubectl delete clusterrolebinding [name] - -### 5.1.2 Minimize access to secrets (Manual) - - -**Result:** warn - -**Remediation:** -Where possible, remove get, list and watch access to secret objects in the cluster. - -### 5.1.3 Minimize wildcard use in Roles and ClusterRoles (Manual) - - -**Result:** warn - -**Remediation:** -Where possible replace any use of wildcards in clusterroles and roles with specific -objects or actions. - -### 5.1.4 Minimize access to create pods (Manual) - - -**Result:** warn - -**Remediation:** -Where possible, remove create access to pod objects in the cluster. - -### 5.1.5 Ensure that default service accounts are not actively used. (Automated) - - -**Result:** pass - -**Remediation:** -Create explicit service accounts wherever a Kubernetes workload requires specific access -to the Kubernetes API server. -Modify the configuration of each default service account to include this value -automountServiceAccountToken: false - -**Audit Script:** `check_for_default_sa.sh` - -```bash -#!/bin/bash - -set -eE - -handle_error() { - echo "false" -} - -trap 'handle_error' ERR - -count_sa=$(kubectl get serviceaccounts --all-namespaces -o json | jq -r '.items[] | select(.metadata.name=="default") | select((.automountServiceAccountToken == null) or (.automountServiceAccountToken == true))' | jq .metadata.namespace | wc -l) -if [[ ${count_sa} -gt 0 ]]; then - echo "false" - exit -fi - -for ns in $(kubectl get ns --no-headers -o custom-columns=":metadata.name") -do - for result in $(kubectl get clusterrolebinding,rolebinding -n $ns -o json | jq -r '.items[] | select((.subjects[].kind=="ServiceAccount" and .subjects[].name=="default") or (.subjects[].kind=="Group" and .subjects[].name=="system:serviceaccounts"))' | jq -r '"\(.roleRef.kind),\(.roleRef.name)"') - do - read kind name <<<$(IFS=","; echo $result) - resource_count=$(kubectl get $kind $name -n $ns -o json | jq -r '.rules[] | select(.resources[] != "podsecuritypolicies")' | wc -l) - if [[ ${resource_count} -gt 0 ]]; then - echo "false" - exit - fi - done -done - - -echo "true" -``` - -**Audit Execution:** - -```bash -./check_for_default_sa.sh -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -### 5.1.6 Ensure that Service Account Tokens are only mounted where necessary (Manual) - - -**Result:** warn - -**Remediation:** -Modify the definition of pods and service accounts which do not need to mount service -account tokens to disable it. - -## 5.2 Pod Security Policies -### 5.2.1 Minimize the admission of privileged containers (Manual) - - -**Result:** warn - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that -the .spec.privileged field is omitted or set to false. - -### 5.2.2 Minimize the admission of containers wishing to share the host process ID namespace (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.hostPID field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.hostPID == null) or (.spec.hostPID == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.3 Minimize the admission of containers wishing to share the host IPC namespace (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.hostIPC field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.hostIPC == null) or (.spec.hostIPC == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.4 Minimize the admission of containers wishing to share the host network namespace (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.hostNetwork field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.hostNetwork == null) or (.spec.hostNetwork == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.5 Minimize the admission of containers with allowPrivilegeEscalation (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.allowPrivilegeEscalation field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.allowPrivilegeEscalation == null) or (.spec.allowPrivilegeEscalation == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.6 Minimize the admission of root containers (Manual) - - -**Result:** warn - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.runAsUser.rule is set to either MustRunAsNonRoot or MustRunAs with the range of -UIDs not including 0. - -### 5.2.7 Minimize the admission of containers with the NET_RAW capability (Manual) - - -**Result:** warn - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.requiredDropCapabilities is set to include either NET_RAW or ALL. - -### 5.2.8 Minimize the admission of containers with added capabilities (Manual) - - -**Result:** warn - -**Remediation:** -Ensure that allowedCapabilities is not present in PSPs for the cluster unless -it is set to an empty array. - -### 5.2.9 Minimize the admission of containers with capabilities assigned (Manual) - - -**Result:** warn - -**Remediation:** -Review the use of capabilites in applications runnning on your cluster. Where a namespace -contains applicaions which do not require any Linux capabities to operate consider adding -a PSP which forbids the admission of containers which do not drop all capabilities. - -## 5.3 Network Policies and CNI -### 5.3.1 Ensure that the CNI in use supports Network Policies (Manual) - - -**Result:** warn - -**Remediation:** -If the CNI plugin in use does not support network policies, consideration should be given to -making use of a different plugin, or finding an alternate mechanism for restricting traffic -in the Kubernetes cluster. - -### 5.3.2 Ensure that all Namespaces have Network Policies defined (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and create NetworkPolicy objects as you need them. - -**Audit Script:** `check_for_network_policies.sh` - -```bash -#!/bin/bash - -set -eE - -handle_error() { - echo "false" -} - -trap 'handle_error' ERR - -for namespace in $(kubectl get namespaces --all-namespaces -o json | jq -r '.items[].metadata.name'); do - policy_count=$(kubectl get networkpolicy -n ${namespace} -o json | jq '.items | length') - if [[ ${policy_count} -eq 0 ]]; then - echo "false" - exit - fi -done - -echo "true" - -``` - -**Audit Execution:** - -```bash -./check_for_network_policies.sh -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -## 5.4 Secrets Management -### 5.4.1 Prefer using secrets as files over secrets as environment variables (Manual) - - -**Result:** warn - -**Remediation:** -if possible, rewrite application code to read secrets from mounted secret files, rather than -from environment variables. - -### 5.4.2 Consider external secret storage (Manual) - - -**Result:** warn - -**Remediation:** -Refer to the secrets management options offered by your cloud provider or a third-party -secrets management solution. - -## 5.5 Extensible Admission Control -### 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller (Manual) - - -**Result:** warn - -**Remediation:** -Follow the Kubernetes documentation and setup image provenance. - -## 5.7 General Policies -### 5.7.1 Create administrative boundaries between resources using namespaces (Manual) - - -**Result:** warn - -**Remediation:** -Follow the documentation and create namespaces for objects in your deployment as you need -them. - -### 5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions (Manual) - - -**Result:** warn - -**Remediation:** -Seccomp is an alpha feature currently. By default, all alpha features are disabled. So, you -would need to enable alpha features in the apiserver by passing "--feature- -gates=AllAlpha=true" argument. -Edit the /etc/kubernetes/apiserver file on the master node and set the KUBE_API_ARGS -parameter to "--feature-gates=AllAlpha=true" -KUBE_API_ARGS="--feature-gates=AllAlpha=true" -Based on your system, restart the kube-apiserver service. For example: -systemctl restart kube-apiserver.service -Use annotations to enable the docker/default seccomp profile in your pod definitions. An -example is as below: -apiVersion: v1 -kind: Pod -metadata: - name: trustworthy-pod - annotations: - seccomp.security.alpha.kubernetes.io/pod: docker/default -spec: - containers: - - name: trustworthy-container - image: sotrustworthy:latest - -### 5.7.3 Apply Security Context to Your Pods and Containers (Manual) - - -**Result:** warn - -**Remediation:** -Follow the Kubernetes documentation and apply security contexts to your pods. For a -suggested list of security contexts, you may refer to the CIS Security Benchmark for Docker -Containers. - -### 5.7.4 The default namespace should not be used (Automated) - - -**Result:** pass - -**Remediation:** -Ensure that namespaces are created to allow for appropriate segregation of Kubernetes -resources and that all new resources are created in a specific namespace. - -**Audit Script:** `check_for_default_ns.sh` - -```bash -#!/bin/bash - -set -eE - -handle_error() { - echo "false" -} - -trap 'handle_error' ERR - -count=$(kubectl get all -n default -o json | jq .items[] | jq -r 'select((.metadata.name!="kubernetes"))' | jq .metadata.name | wc -l) -if [[ ${count} -gt 0 ]]; then - echo "false" - exit -fi - -echo "true" - - -``` - -**Audit Execution:** - -```bash -./check_for_default_ns.sh -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf b/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf deleted file mode 100644 index 8984cc57c5e..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf +++ /dev/null @@ -1,8259 +0,0 @@ -%PDF-1.7 -%🖤 -1 0 obj -<< -/Type /Pages -/Kids [ 6 0 R 8 0 R 30 0 R 45 0 R 53 0 R 67 0 R 77 0 R 99 0 R 129 0 R 164 0 R 194 0 R 232 0 R 270 0 R 310 0 R 350 0 R 390 0 R 425 0 R 464 0 R 499 0 R 534 0 R 557 0 R 591 0 R ] -/Count 22 ->> -endobj -2 0 obj -<< -/Title (RKE Hardening Guide with CIS v1.6 Benchmark) -/Creator (pandoc) -/Producer (WeasyPrint 54.3) ->> -endobj -3 0 obj -<< -/Type /Catalog -/Pages 1 0 R -/Outlines 611 0 R -/Names << -/Dests << -/Names [ (TOC) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (cb1) [ 45 0 R /XYZ 84.259843 441.572079 0 ] (cb1-1) [ 45 0 R /XYZ 101.433071 439.875057 0 ] (cb1-2) [ 45 0 R /XYZ 99.933071 420.928036 0 ] (cb1-3) [ 45 0 R /XYZ 99.933071 401.981014 0 ] (cb1-4) [ 45 0 R /XYZ 99.933071 383.033993 0 ] (cb1-5) [ 45 0 R /XYZ 99.933071 364.086971 0 ] (cb10) [ 390 0 R /XYZ 84.259843 416.811778 0 ] (cb10-1) [ 390 0 R /XYZ 101.433071 415.114756 0 ] (cb10-10) [ 390 0 R /XYZ 99.933071 244.591563 0 ] (cb10-100) [ 499 0 R /XYZ 99.933071 590.755821 0 ] (cb10-101) [ 499 0 R /XYZ 99.933071 571.808799 0 ] (cb10-102) [ 499 0 R /XYZ 99.933071 552.861778 0 ] (cb10-103) [ 499 0 R /XYZ 99.933071 533.914756 0 ] (cb10-104) [ 499 0 R /XYZ 99.933071 514.967735 0 ] (cb10-105) [ 499 0 R /XYZ 99.933071 496.020714 0 ] (cb10-106) [ 499 0 R /XYZ 99.933071 477.073692 0 ] (cb10-107) [ 499 0 R /XYZ 99.933071 458.126671 0 ] (cb10-108) [ 499 0 R /XYZ 99.933071 439.179649 0 ] (cb10-109) [ 499 0 R /XYZ 99.933071 420.232628 0 ] (cb10-11) [ 390 0 R /XYZ 99.933071 225.644542 0 ] (cb10-110) [ 499 0 R /XYZ 99.933071 401.285606 0 ] (cb10-111) [ 499 0 R /XYZ 99.933071 382.338585 0 ] (cb10-112) [ 499 0 R /XYZ 99.933071 363.391563 0 ] (cb10-113) [ 499 0 R /XYZ 99.933071 344.444542 0 ] (cb10-114) [ 499 0 R /XYZ 99.933071 325.497520 0 ] (cb10-115) [ 499 0 R /XYZ 99.933071 306.550499 0 ] (cb10-116) [ 499 0 R /XYZ 99.933071 287.603477 0 ] (cb10-117) [ 499 0 R /XYZ 99.933071 173.921348 0 ] (cb10-118) [ 499 0 R /XYZ 99.933071 154.974327 0 ] (cb10-119) [ 499 0 R /XYZ 99.933071 136.027305 0 ] (cb10-12) [ 390 0 R /XYZ 99.933071 206.697520 0 ] (cb10-120) [ 499 0 R /XYZ 99.933071 117.080284 0 ] (cb10-121) [ 499 0 R /XYZ 99.933071 98.133262 0 ] (cb10-122) [ 534 0 R /XYZ 99.933071 799.173057 0 ] (cb10-123) [ 534 0 R /XYZ 99.933071 685.490928 0 ] (cb10-124) [ 534 0 R /XYZ 99.933071 666.543907 0 ] (cb10-125) [ 534 0 R /XYZ 99.933071 647.596885 0 ] (cb10-126) [ 534 0 R /XYZ 99.933071 628.649864 0 ] (cb10-127) [ 534 0 R /XYZ 99.933071 609.702842 0 ] (cb10-128) [ 534 0 R /XYZ 99.933071 590.755821 0 ] (cb10-129) [ 534 0 R /XYZ 99.933071 571.808799 0 ] (cb10-13) [ 390 0 R /XYZ 99.933071 187.750499 0 ] (cb10-14) [ 390 0 R /XYZ 99.933071 168.803477 0 ] (cb10-15) [ 390 0 R /XYZ 99.933071 149.856456 0 ] (cb10-16) [ 390 0 R /XYZ 99.933071 130.909434 0 ] (cb10-17) [ 390 0 R /XYZ 99.933071 111.962413 0 ] (cb10-18) [ 390 0 R /XYZ 99.933071 93.015391 0 ] (cb10-19) [ 425 0 R /XYZ 99.933071 799.173057 0 ] (cb10-2) [ 390 0 R /XYZ 99.933071 396.167735 0 ] (cb10-20) [ 425 0 R /XYZ 99.933071 780.226036 0 ] (cb10-21) [ 425 0 R /XYZ 99.933071 761.279014 0 ] (cb10-22) [ 425 0 R /XYZ 99.933071 742.331993 0 ] (cb10-23) [ 425 0 R /XYZ 99.933071 723.384971 0 ] (cb10-24) [ 425 0 R /XYZ 99.933071 704.437950 0 ] (cb10-25) [ 425 0 R /XYZ 99.933071 685.490928 0 ] (cb10-26) [ 425 0 R /XYZ 99.933071 666.543907 0 ] (cb10-27) [ 425 0 R /XYZ 99.933071 647.596885 0 ] (cb10-28) [ 425 0 R /XYZ 99.933071 628.649864 0 ] (cb10-29) [ 425 0 R /XYZ 99.933071 609.702842 0 ] (cb10-3) [ 390 0 R /XYZ 99.933071 377.220714 0 ] (cb10-30) [ 425 0 R /XYZ 99.933071 571.808799 0 ] (cb10-31) [ 425 0 R /XYZ 99.933071 552.861778 0 ] (cb10-32) [ 425 0 R /XYZ 99.933071 533.914756 0 ] (cb10-33) [ 425 0 R /XYZ 99.933071 514.967735 0 ] (cb10-34) [ 425 0 R /XYZ 99.933071 496.020714 0 ] (cb10-35) [ 425 0 R /XYZ 99.933071 477.073692 0 ] (cb10-36) [ 425 0 R /XYZ 99.933071 458.126671 0 ] (cb10-37) [ 425 0 R /XYZ 99.933071 439.179649 0 ] (cb10-38) [ 425 0 R /XYZ 99.933071 420.232628 0 ] (cb10-39) [ 425 0 R /XYZ 99.933071 401.285606 0 ] (cb10-4) [ 390 0 R /XYZ 99.933071 358.273692 0 ] (cb10-40) [ 425 0 R /XYZ 99.933071 382.338585 0 ] (cb10-41) [ 425 0 R /XYZ 99.933071 363.391563 0 ] (cb10-42) [ 425 0 R /XYZ 99.933071 344.444542 0 ] (cb10-43) [ 425 0 R /XYZ 99.933071 325.497520 0 ] (cb10-44) [ 425 0 R /XYZ 99.933071 306.550499 0 ] (cb10-45) [ 425 0 R /XYZ 99.933071 287.603477 0 ] (cb10-46) [ 425 0 R /XYZ 99.933071 268.656456 0 ] (cb10-47) [ 425 0 R /XYZ 99.933071 249.709434 0 ] (cb10-48) [ 425 0 R /XYZ 99.933071 230.762413 0 ] (cb10-49) [ 425 0 R /XYZ 99.933071 211.815391 0 ] (cb10-5) [ 390 0 R /XYZ 99.933071 339.326671 0 ] (cb10-50) [ 425 0 R /XYZ 99.933071 192.868370 0 ] (cb10-51) [ 425 0 R /XYZ 99.933071 173.921348 0 ] (cb10-52) [ 425 0 R /XYZ 99.933071 154.974327 0 ] (cb10-53) [ 425 0 R /XYZ 99.933071 136.027305 0 ] (cb10-54) [ 425 0 R /XYZ 99.933071 117.080284 0 ] (cb10-55) [ 425 0 R /XYZ 99.933071 98.133262 0 ] (cb10-56) [ 464 0 R /XYZ 99.933071 799.173057 0 ] (cb10-57) [ 464 0 R /XYZ 99.933071 780.226036 0 ] (cb10-58) [ 464 0 R /XYZ 99.933071 761.279014 0 ] (cb10-59) [ 464 0 R /XYZ 99.933071 742.331993 0 ] (cb10-6) [ 390 0 R /XYZ 99.933071 320.379649 0 ] (cb10-60) [ 464 0 R /XYZ 99.933071 723.384971 0 ] (cb10-61) [ 464 0 R /XYZ 99.933071 704.437950 0 ] (cb10-62) [ 464 0 R /XYZ 99.933071 685.490928 0 ] (cb10-63) [ 464 0 R /XYZ 99.933071 666.543907 0 ] (cb10-64) [ 464 0 R /XYZ 99.933071 647.596885 0 ] (cb10-65) [ 464 0 R /XYZ 99.933071 628.649864 0 ] (cb10-66) [ 464 0 R /XYZ 99.933071 609.702842 0 ] (cb10-67) [ 464 0 R /XYZ 99.933071 590.755821 0 ] (cb10-68) [ 464 0 R /XYZ 99.933071 571.808799 0 ] (cb10-69) [ 464 0 R /XYZ 99.933071 552.861778 0 ] (cb10-7) [ 390 0 R /XYZ 99.933071 301.432628 0 ] (cb10-70) [ 464 0 R /XYZ 99.933071 533.914756 0 ] (cb10-71) [ 464 0 R /XYZ 99.933071 514.967735 0 ] (cb10-72) [ 464 0 R /XYZ 99.933071 496.020714 0 ] (cb10-73) [ 464 0 R /XYZ 99.933071 477.073692 0 ] (cb10-74) [ 464 0 R /XYZ 99.933071 458.126671 0 ] (cb10-75) [ 464 0 R /XYZ 99.933071 439.179649 0 ] (cb10-76) [ 464 0 R /XYZ 99.933071 420.232628 0 ] (cb10-77) [ 464 0 R /XYZ 99.933071 401.285606 0 ] (cb10-78) [ 464 0 R /XYZ 99.933071 382.338585 0 ] (cb10-79) [ 464 0 R /XYZ 99.933071 363.391563 0 ] (cb10-8) [ 390 0 R /XYZ 99.933071 282.485606 0 ] (cb10-80) [ 464 0 R /XYZ 99.933071 344.444542 0 ] (cb10-81) [ 464 0 R /XYZ 99.933071 325.497520 0 ] (cb10-82) [ 464 0 R /XYZ 99.933071 306.550499 0 ] (cb10-83) [ 464 0 R /XYZ 99.933071 287.603477 0 ] (cb10-84) [ 464 0 R /XYZ 99.933071 268.656456 0 ] (cb10-85) [ 464 0 R /XYZ 99.933071 249.709434 0 ] (cb10-86) [ 464 0 R /XYZ 99.933071 230.762413 0 ] (cb10-87) [ 464 0 R /XYZ 99.933071 117.080284 0 ] (cb10-88) [ 464 0 R /XYZ 99.933071 98.133262 0 ] (cb10-89) [ 499 0 R /XYZ 99.933071 799.173057 0 ] (cb10-9) [ 390 0 R /XYZ 99.933071 263.538585 0 ] (cb10-90) [ 499 0 R /XYZ 99.933071 780.226036 0 ] (cb10-91) [ 499 0 R /XYZ 99.933071 761.279014 0 ] (cb10-92) [ 499 0 R /XYZ 99.933071 742.331993 0 ] (cb10-93) [ 499 0 R /XYZ 99.933071 723.384971 0 ] (cb10-94) [ 499 0 R /XYZ 99.933071 704.437950 0 ] (cb10-95) [ 499 0 R /XYZ 99.933071 685.490928 0 ] (cb10-96) [ 499 0 R /XYZ 99.933071 666.543907 0 ] (cb10-97) [ 499 0 R /XYZ 99.933071 647.596885 0 ] (cb10-98) [ 499 0 R /XYZ 99.933071 628.649864 0 ] (cb10-99) [ 499 0 R /XYZ 99.933071 609.702842 0 ] (cb11) [ 534 0 R /XYZ 84.259843 331.262799 0 ] (cb11-1) [ 534 0 R /XYZ 101.433071 329.565778 0 ] (cb11-10) [ 534 0 R /XYZ 99.933071 159.042585 0 ] (cb11-11) [ 534 0 R /XYZ 99.933071 140.095563 0 ] (cb11-12) [ 534 0 R /XYZ 99.933071 121.148542 0 ] (cb11-13) [ 534 0 R /XYZ 99.933071 102.201520 0 ] (cb11-14) [ 557 0 R /XYZ 99.933071 799.173057 0 ] (cb11-15) [ 557 0 R /XYZ 99.933071 780.226036 0 ] (cb11-16) [ 557 0 R /XYZ 99.933071 761.279014 0 ] (cb11-17) [ 557 0 R /XYZ 99.933071 742.331993 0 ] (cb11-18) [ 557 0 R /XYZ 99.933071 723.384971 0 ] (cb11-19) [ 557 0 R /XYZ 99.933071 704.437950 0 ] (cb11-2) [ 534 0 R /XYZ 99.933071 310.618756 0 ] (cb11-20) [ 557 0 R /XYZ 99.933071 685.490928 0 ] (cb11-21) [ 557 0 R /XYZ 99.933071 666.543907 0 ] (cb11-22) [ 557 0 R /XYZ 99.933071 647.596885 0 ] (cb11-23) [ 557 0 R /XYZ 99.933071 628.649864 0 ] (cb11-24) [ 557 0 R /XYZ 99.933071 609.702842 0 ] (cb11-25) [ 557 0 R /XYZ 99.933071 590.755821 0 ] (cb11-26) [ 557 0 R /XYZ 99.933071 571.808799 0 ] (cb11-3) [ 534 0 R /XYZ 99.933071 291.671735 0 ] (cb11-4) [ 534 0 R /XYZ 99.933071 272.724714 0 ] (cb11-5) [ 534 0 R /XYZ 99.933071 253.777692 0 ] (cb11-6) [ 534 0 R /XYZ 99.933071 234.830671 0 ] (cb11-7) [ 534 0 R /XYZ 99.933071 215.883649 0 ] (cb11-8) [ 534 0 R /XYZ 99.933071 196.936628 0 ] (cb11-9) [ 534 0 R /XYZ 99.933071 177.989606 0 ] (cb12) [ 557 0 R /XYZ 84.259843 446.115778 0 ] (cb12-1) [ 557 0 R /XYZ 101.433071 444.418756 0 ] (cb12-10) [ 557 0 R /XYZ 99.933071 273.895563 0 ] (cb12-11) [ 557 0 R /XYZ 99.933071 254.948542 0 ] (cb12-12) [ 557 0 R /XYZ 99.933071 236.001520 0 ] (cb12-13) [ 557 0 R /XYZ 99.933071 217.054499 0 ] (cb12-14) [ 557 0 R /XYZ 99.933071 198.107477 0 ] (cb12-15) [ 557 0 R /XYZ 99.933071 179.160456 0 ] (cb12-16) [ 557 0 R /XYZ 99.933071 160.213434 0 ] (cb12-17) [ 557 0 R /XYZ 99.933071 141.266413 0 ] (cb12-18) [ 557 0 R /XYZ 99.933071 122.319391 0 ] (cb12-19) [ 557 0 R /XYZ 99.933071 103.372370 0 ] (cb12-2) [ 557 0 R /XYZ 99.933071 425.471735 0 ] (cb12-20) [ 591 0 R /XYZ 99.933071 780.226036 0 ] (cb12-21) [ 591 0 R /XYZ 99.933071 742.331993 0 ] (cb12-22) [ 591 0 R /XYZ 99.933071 723.384971 0 ] (cb12-23) [ 591 0 R /XYZ 99.933071 704.437950 0 ] (cb12-3) [ 557 0 R /XYZ 99.933071 406.524714 0 ] (cb12-4) [ 557 0 R /XYZ 99.933071 387.577692 0 ] (cb12-5) [ 557 0 R /XYZ 99.933071 368.630671 0 ] (cb12-6) [ 557 0 R /XYZ 99.933071 349.683649 0 ] (cb12-7) [ 557 0 R /XYZ 99.933071 330.736628 0 ] (cb12-8) [ 557 0 R /XYZ 99.933071 311.789606 0 ] (cb12-9) [ 557 0 R /XYZ 99.933071 292.842585 0 ] (cb2) [ 53 0 R /XYZ 84.259843 753.620079 0 ] (cb2-1) [ 53 0 R /XYZ 101.433071 751.923057 0 ] (cb2-2) [ 53 0 R /XYZ 99.933071 732.976036 0 ] (cb3) [ 53 0 R /XYZ 84.259843 654.779014 0 ] (cb3-1) [ 53 0 R /XYZ 101.433071 653.081993 0 ] (cb3-2) [ 53 0 R /XYZ 99.933071 634.134971 0 ] (cb3-3) [ 53 0 R /XYZ 99.933071 615.187950 0 ] (cb3-4) [ 53 0 R /XYZ 99.933071 596.240928 0 ] (cb4) [ 53 0 R /XYZ 84.259843 282.344928 0 ] (cb4-1) [ 53 0 R /XYZ 101.433071 280.647907 0 ] (cb5) [ 53 0 R /XYZ 84.259843 217.647907 0 ] (cb5-1) [ 53 0 R /XYZ 101.433071 215.950885 0 ] (cb5-2) [ 53 0 R /XYZ 99.933071 197.003864 0 ] (cb5-3) [ 53 0 R /XYZ 99.933071 178.056842 0 ] (cb5-4) [ 53 0 R /XYZ 99.933071 159.109821 0 ] (cb5-5) [ 53 0 R /XYZ 99.933071 140.162799 0 ] (cb6) [ 67 0 R /XYZ 84.259843 749.870079 0 ] (cb6-1) [ 67 0 R /XYZ 101.433071 748.173057 0 ] (cb6-2) [ 67 0 R /XYZ 99.933071 729.226036 0 ] (cb6-3) [ 67 0 R /XYZ 99.933071 710.279014 0 ] (cb6-4) [ 67 0 R /XYZ 99.933071 672.384971 0 ] (cb6-5) [ 67 0 R /XYZ 99.933071 634.490928 0 ] (cb7) [ 77 0 R /XYZ 84.259843 716.781496 0 ] (cb7-1) [ 77 0 R /XYZ 101.433071 715.084475 0 ] (cb7-10) [ 77 0 R /XYZ 99.933071 544.561281 0 ] (cb7-11) [ 77 0 R /XYZ 99.933071 525.614260 0 ] (cb7-12) [ 77 0 R /XYZ 99.933071 506.667238 0 ] (cb7-13) [ 77 0 R /XYZ 99.933071 487.720217 0 ] (cb7-14) [ 77 0 R /XYZ 99.933071 468.773195 0 ] (cb7-2) [ 77 0 R /XYZ 99.933071 696.137453 0 ] (cb7-3) [ 77 0 R /XYZ 99.933071 677.190432 0 ] (cb7-4) [ 77 0 R /XYZ 99.933071 658.243410 0 ] (cb7-5) [ 77 0 R /XYZ 99.933071 639.296389 0 ] (cb7-6) [ 77 0 R /XYZ 99.933071 620.349367 0 ] (cb7-7) [ 77 0 R /XYZ 99.933071 601.402346 0 ] (cb7-8) [ 77 0 R /XYZ 99.933071 582.455324 0 ] (cb7-9) [ 77 0 R /XYZ 99.933071 563.508303 0 ] (cb8) [ 77 0 R /XYZ 84.259843 372.023195 0 ] (cb8-1) [ 77 0 R /XYZ 101.433071 370.326174 0 ] (cb8-2) [ 77 0 R /XYZ 99.933071 351.379152 0 ] (cb8-3) [ 77 0 R /XYZ 99.933071 332.432131 0 ] (cb8-4) [ 77 0 R /XYZ 99.933071 294.538088 0 ] (cb8-5) [ 77 0 R /XYZ 99.933071 275.591066 0 ] (cb9) [ 99 0 R /XYZ 84.259843 652.281496 0 ] (cb9-1) [ 99 0 R /XYZ 101.433071 650.584475 0 ] (cb9-10) [ 99 0 R /XYZ 99.933071 423.220217 0 ] (cb9-100) [ 194 0 R /XYZ 99.933071 590.755821 0 ] (cb9-101) [ 194 0 R /XYZ 99.933071 571.808799 0 ] (cb9-102) [ 194 0 R /XYZ 99.933071 552.861778 0 ] (cb9-103) [ 194 0 R /XYZ 99.933071 533.914756 0 ] (cb9-104) [ 194 0 R /XYZ 99.933071 514.967735 0 ] (cb9-105) [ 194 0 R /XYZ 99.933071 496.020714 0 ] (cb9-106) [ 194 0 R /XYZ 99.933071 477.073692 0 ] (cb9-107) [ 194 0 R /XYZ 99.933071 458.126671 0 ] (cb9-108) [ 194 0 R /XYZ 99.933071 439.179649 0 ] (cb9-109) [ 194 0 R /XYZ 99.933071 420.232628 0 ] (cb9-11) [ 99 0 R /XYZ 99.933071 404.273195 0 ] (cb9-110) [ 194 0 R /XYZ 99.933071 401.285606 0 ] (cb9-111) [ 194 0 R /XYZ 99.933071 344.444542 0 ] (cb9-112) [ 194 0 R /XYZ 99.933071 325.497520 0 ] (cb9-113) [ 194 0 R /XYZ 99.933071 306.550499 0 ] (cb9-114) [ 194 0 R /XYZ 99.933071 287.603477 0 ] (cb9-115) [ 194 0 R /XYZ 99.933071 268.656456 0 ] (cb9-116) [ 194 0 R /XYZ 99.933071 249.709434 0 ] (cb9-117) [ 194 0 R /XYZ 99.933071 230.762413 0 ] (cb9-118) [ 194 0 R /XYZ 99.933071 211.815391 0 ] (cb9-119) [ 194 0 R /XYZ 99.933071 192.868370 0 ] (cb9-12) [ 99 0 R /XYZ 99.933071 385.326174 0 ] (cb9-120) [ 194 0 R /XYZ 99.933071 173.921348 0 ] (cb9-121) [ 194 0 R /XYZ 99.933071 154.974327 0 ] (cb9-122) [ 194 0 R /XYZ 99.933071 136.027305 0 ] (cb9-123) [ 194 0 R /XYZ 99.933071 117.080284 0 ] (cb9-124) [ 194 0 R /XYZ 99.933071 98.133262 0 ] (cb9-125) [ 232 0 R /XYZ 99.933071 799.173057 0 ] (cb9-126) [ 232 0 R /XYZ 99.933071 780.226036 0 ] (cb9-127) [ 232 0 R /XYZ 99.933071 761.279014 0 ] (cb9-128) [ 232 0 R /XYZ 99.933071 742.331993 0 ] (cb9-129) [ 232 0 R /XYZ 99.933071 704.437950 0 ] (cb9-13) [ 99 0 R /XYZ 99.933071 366.379152 0 ] (cb9-130) [ 232 0 R /XYZ 99.933071 685.490928 0 ] (cb9-131) [ 232 0 R /XYZ 99.933071 666.543907 0 ] (cb9-132) [ 232 0 R /XYZ 99.933071 647.596885 0 ] (cb9-133) [ 232 0 R /XYZ 99.933071 628.649864 0 ] (cb9-134) [ 232 0 R /XYZ 99.933071 609.702842 0 ] (cb9-135) [ 232 0 R /XYZ 99.933071 590.755821 0 ] (cb9-136) [ 232 0 R /XYZ 99.933071 571.808799 0 ] (cb9-137) [ 232 0 R /XYZ 99.933071 552.861778 0 ] (cb9-138) [ 232 0 R /XYZ 99.933071 533.914756 0 ] (cb9-139) [ 232 0 R /XYZ 99.933071 514.967735 0 ] (cb9-14) [ 99 0 R /XYZ 99.933071 347.432131 0 ] (cb9-140) [ 232 0 R /XYZ 99.933071 477.073692 0 ] (cb9-141) [ 232 0 R /XYZ 99.933071 458.126671 0 ] (cb9-142) [ 232 0 R /XYZ 99.933071 439.179649 0 ] (cb9-143) [ 232 0 R /XYZ 99.933071 420.232628 0 ] (cb9-144) [ 232 0 R /XYZ 99.933071 401.285606 0 ] (cb9-145) [ 232 0 R /XYZ 99.933071 382.338585 0 ] (cb9-146) [ 232 0 R /XYZ 99.933071 363.391563 0 ] (cb9-147) [ 232 0 R /XYZ 99.933071 344.444542 0 ] (cb9-148) [ 232 0 R /XYZ 99.933071 325.497520 0 ] (cb9-149) [ 232 0 R /XYZ 99.933071 306.550499 0 ] (cb9-15) [ 99 0 R /XYZ 99.933071 328.485109 0 ] (cb9-150) [ 232 0 R /XYZ 99.933071 287.603477 0 ] (cb9-151) [ 232 0 R /XYZ 99.933071 268.656456 0 ] (cb9-152) [ 232 0 R /XYZ 99.933071 249.709434 0 ] (cb9-153) [ 232 0 R /XYZ 99.933071 230.762413 0 ] (cb9-154) [ 232 0 R /XYZ 99.933071 211.815391 0 ] (cb9-155) [ 232 0 R /XYZ 99.933071 192.868370 0 ] (cb9-156) [ 232 0 R /XYZ 99.933071 173.921348 0 ] (cb9-157) [ 232 0 R /XYZ 99.933071 154.974327 0 ] (cb9-158) [ 232 0 R /XYZ 99.933071 136.027305 0 ] (cb9-159) [ 232 0 R /XYZ 99.933071 117.080284 0 ] (cb9-16) [ 99 0 R /XYZ 99.933071 309.538088 0 ] (cb9-160) [ 232 0 R /XYZ 99.933071 98.133262 0 ] (cb9-161) [ 270 0 R /XYZ 99.933071 799.173057 0 ] (cb9-162) [ 270 0 R /XYZ 99.933071 780.226036 0 ] (cb9-163) [ 270 0 R /XYZ 99.933071 761.279014 0 ] (cb9-164) [ 270 0 R /XYZ 99.933071 742.331993 0 ] (cb9-165) [ 270 0 R /XYZ 99.933071 723.384971 0 ] (cb9-166) [ 270 0 R /XYZ 99.933071 704.437950 0 ] (cb9-167) [ 270 0 R /XYZ 99.933071 685.490928 0 ] (cb9-168) [ 270 0 R /XYZ 99.933071 666.543907 0 ] (cb9-169) [ 270 0 R /XYZ 99.933071 647.596885 0 ] (cb9-17) [ 99 0 R /XYZ 99.933071 290.591066 0 ] (cb9-170) [ 270 0 R /XYZ 99.933071 628.649864 0 ] (cb9-171) [ 270 0 R /XYZ 99.933071 609.702842 0 ] (cb9-172) [ 270 0 R /XYZ 99.933071 590.755821 0 ] (cb9-173) [ 270 0 R /XYZ 99.933071 571.808799 0 ] (cb9-174) [ 270 0 R /XYZ 99.933071 552.861778 0 ] (cb9-175) [ 270 0 R /XYZ 99.933071 533.914756 0 ] (cb9-176) [ 270 0 R /XYZ 99.933071 514.967735 0 ] (cb9-177) [ 270 0 R /XYZ 99.933071 496.020714 0 ] (cb9-178) [ 270 0 R /XYZ 99.933071 477.073692 0 ] (cb9-179) [ 270 0 R /XYZ 99.933071 458.126671 0 ] (cb9-18) [ 99 0 R /XYZ 99.933071 271.644045 0 ] (cb9-180) [ 270 0 R /XYZ 99.933071 439.179649 0 ] (cb9-181) [ 270 0 R /XYZ 99.933071 420.232628 0 ] (cb9-182) [ 270 0 R /XYZ 99.933071 401.285606 0 ] (cb9-183) [ 270 0 R /XYZ 99.933071 382.338585 0 ] (cb9-184) [ 270 0 R /XYZ 99.933071 363.391563 0 ] (cb9-185) [ 270 0 R /XYZ 99.933071 344.444542 0 ] (cb9-186) [ 270 0 R /XYZ 99.933071 325.497520 0 ] (cb9-187) [ 270 0 R /XYZ 99.933071 306.550499 0 ] (cb9-188) [ 270 0 R /XYZ 99.933071 287.603477 0 ] (cb9-189) [ 270 0 R /XYZ 99.933071 268.656456 0 ] (cb9-19) [ 99 0 R /XYZ 99.933071 252.697023 0 ] (cb9-190) [ 270 0 R /XYZ 99.933071 249.709434 0 ] (cb9-191) [ 270 0 R /XYZ 99.933071 230.762413 0 ] (cb9-192) [ 270 0 R /XYZ 99.933071 211.815391 0 ] (cb9-193) [ 270 0 R /XYZ 99.933071 192.868370 0 ] (cb9-194) [ 270 0 R /XYZ 99.933071 173.921348 0 ] (cb9-195) [ 270 0 R /XYZ 99.933071 154.974327 0 ] (cb9-196) [ 270 0 R /XYZ 99.933071 136.027305 0 ] (cb9-197) [ 270 0 R /XYZ 99.933071 117.080284 0 ] (cb9-198) [ 270 0 R /XYZ 99.933071 98.133262 0 ] (cb9-199) [ 310 0 R /XYZ 99.933071 799.173057 0 ] (cb9-2) [ 99 0 R /XYZ 99.933071 612.690432 0 ] (cb9-20) [ 99 0 R /XYZ 99.933071 233.750002 0 ] (cb9-200) [ 310 0 R /XYZ 99.933071 780.226036 0 ] (cb9-201) [ 310 0 R /XYZ 99.933071 761.279014 0 ] (cb9-202) [ 310 0 R /XYZ 99.933071 742.331993 0 ] (cb9-203) [ 310 0 R /XYZ 99.933071 723.384971 0 ] (cb9-204) [ 310 0 R /XYZ 99.933071 704.437950 0 ] (cb9-205) [ 310 0 R /XYZ 99.933071 685.490928 0 ] (cb9-206) [ 310 0 R /XYZ 99.933071 666.543907 0 ] (cb9-207) [ 310 0 R /XYZ 99.933071 647.596885 0 ] (cb9-208) [ 310 0 R /XYZ 99.933071 628.649864 0 ] (cb9-209) [ 310 0 R /XYZ 99.933071 609.702842 0 ] (cb9-21) [ 99 0 R /XYZ 99.933071 214.802980 0 ] (cb9-210) [ 310 0 R /XYZ 99.933071 590.755821 0 ] (cb9-211) [ 310 0 R /XYZ 99.933071 571.808799 0 ] (cb9-212) [ 310 0 R /XYZ 99.933071 552.861778 0 ] (cb9-213) [ 310 0 R /XYZ 99.933071 533.914756 0 ] (cb9-214) [ 310 0 R /XYZ 99.933071 514.967735 0 ] (cb9-215) [ 310 0 R /XYZ 99.933071 496.020714 0 ] (cb9-216) [ 310 0 R /XYZ 99.933071 477.073692 0 ] (cb9-217) [ 310 0 R /XYZ 99.933071 458.126671 0 ] (cb9-218) [ 310 0 R /XYZ 99.933071 439.179649 0 ] (cb9-219) [ 310 0 R /XYZ 99.933071 420.232628 0 ] (cb9-22) [ 99 0 R /XYZ 99.933071 195.855959 0 ] (cb9-220) [ 310 0 R /XYZ 99.933071 401.285606 0 ] (cb9-221) [ 310 0 R /XYZ 99.933071 382.338585 0 ] (cb9-222) [ 310 0 R /XYZ 99.933071 363.391563 0 ] (cb9-223) [ 310 0 R /XYZ 99.933071 344.444542 0 ] (cb9-224) [ 310 0 R /XYZ 99.933071 325.497520 0 ] (cb9-225) [ 310 0 R /XYZ 99.933071 306.550499 0 ] (cb9-226) [ 310 0 R /XYZ 99.933071 287.603477 0 ] (cb9-227) [ 310 0 R /XYZ 99.933071 268.656456 0 ] (cb9-228) [ 310 0 R /XYZ 99.933071 249.709434 0 ] (cb9-229) [ 310 0 R /XYZ 99.933071 230.762413 0 ] (cb9-23) [ 99 0 R /XYZ 99.933071 176.908937 0 ] (cb9-230) [ 310 0 R /XYZ 99.933071 211.815391 0 ] (cb9-231) [ 310 0 R /XYZ 99.933071 192.868370 0 ] (cb9-232) [ 310 0 R /XYZ 99.933071 173.921348 0 ] (cb9-233) [ 310 0 R /XYZ 99.933071 154.974327 0 ] (cb9-234) [ 310 0 R /XYZ 99.933071 136.027305 0 ] (cb9-235) [ 310 0 R /XYZ 99.933071 117.080284 0 ] (cb9-236) [ 310 0 R /XYZ 99.933071 98.133262 0 ] (cb9-237) [ 350 0 R /XYZ 99.933071 799.173057 0 ] (cb9-238) [ 350 0 R /XYZ 99.933071 780.226036 0 ] (cb9-239) [ 350 0 R /XYZ 99.933071 761.279014 0 ] (cb9-24) [ 99 0 R /XYZ 99.933071 157.961916 0 ] (cb9-240) [ 350 0 R /XYZ 99.933071 742.331993 0 ] (cb9-241) [ 350 0 R /XYZ 99.933071 723.384971 0 ] (cb9-242) [ 350 0 R /XYZ 99.933071 704.437950 0 ] (cb9-243) [ 350 0 R /XYZ 99.933071 685.490928 0 ] (cb9-244) [ 350 0 R /XYZ 99.933071 666.543907 0 ] (cb9-245) [ 350 0 R /XYZ 99.933071 647.596885 0 ] (cb9-246) [ 350 0 R /XYZ 99.933071 628.649864 0 ] (cb9-247) [ 350 0 R /XYZ 99.933071 609.702842 0 ] (cb9-248) [ 350 0 R /XYZ 99.933071 590.755821 0 ] (cb9-249) [ 350 0 R /XYZ 99.933071 571.808799 0 ] (cb9-25) [ 99 0 R /XYZ 99.933071 139.014895 0 ] (cb9-250) [ 350 0 R /XYZ 99.933071 552.861778 0 ] (cb9-251) [ 350 0 R /XYZ 99.933071 533.914756 0 ] (cb9-252) [ 350 0 R /XYZ 99.933071 514.967735 0 ] (cb9-253) [ 350 0 R /XYZ 99.933071 496.020714 0 ] (cb9-254) [ 350 0 R /XYZ 99.933071 477.073692 0 ] (cb9-255) [ 350 0 R /XYZ 99.933071 458.126671 0 ] (cb9-256) [ 350 0 R /XYZ 99.933071 439.179649 0 ] (cb9-257) [ 350 0 R /XYZ 99.933071 420.232628 0 ] (cb9-258) [ 350 0 R /XYZ 99.933071 401.285606 0 ] (cb9-259) [ 350 0 R /XYZ 99.933071 382.338585 0 ] (cb9-26) [ 99 0 R /XYZ 99.933071 120.067873 0 ] (cb9-260) [ 350 0 R /XYZ 99.933071 363.391563 0 ] (cb9-261) [ 350 0 R /XYZ 99.933071 344.444542 0 ] (cb9-262) [ 350 0 R /XYZ 99.933071 325.497520 0 ] (cb9-263) [ 350 0 R /XYZ 99.933071 306.550499 0 ] (cb9-264) [ 350 0 R /XYZ 99.933071 287.603477 0 ] (cb9-265) [ 350 0 R /XYZ 99.933071 268.656456 0 ] (cb9-266) [ 350 0 R /XYZ 99.933071 249.709434 0 ] (cb9-267) [ 350 0 R /XYZ 99.933071 230.762413 0 ] (cb9-268) [ 350 0 R /XYZ 99.933071 211.815391 0 ] (cb9-269) [ 350 0 R /XYZ 99.933071 192.868370 0 ] (cb9-27) [ 99 0 R /XYZ 99.933071 101.120852 0 ] (cb9-270) [ 350 0 R /XYZ 99.933071 173.921348 0 ] (cb9-271) [ 350 0 R /XYZ 99.933071 154.974327 0 ] (cb9-272) [ 350 0 R /XYZ 99.933071 136.027305 0 ] (cb9-273) [ 350 0 R /XYZ 99.933071 117.080284 0 ] (cb9-274) [ 350 0 R /XYZ 99.933071 98.133262 0 ] (cb9-275) [ 390 0 R /XYZ 99.933071 799.173057 0 ] (cb9-276) [ 390 0 R /XYZ 99.933071 780.226036 0 ] (cb9-277) [ 390 0 R /XYZ 99.933071 761.279014 0 ] (cb9-278) [ 390 0 R /XYZ 99.933071 742.331993 0 ] (cb9-279) [ 390 0 R /XYZ 99.933071 723.384971 0 ] (cb9-28) [ 129 0 R /XYZ 99.933071 799.173057 0 ] (cb9-280) [ 390 0 R /XYZ 99.933071 704.437950 0 ] (cb9-281) [ 390 0 R /XYZ 99.933071 685.490928 0 ] (cb9-282) [ 390 0 R /XYZ 99.933071 666.543907 0 ] (cb9-283) [ 390 0 R /XYZ 99.933071 647.596885 0 ] (cb9-284) [ 390 0 R /XYZ 99.933071 628.649864 0 ] (cb9-285) [ 390 0 R /XYZ 99.933071 609.702842 0 ] (cb9-286) [ 390 0 R /XYZ 99.933071 590.755821 0 ] (cb9-287) [ 390 0 R /XYZ 99.933071 571.808799 0 ] (cb9-288) [ 390 0 R /XYZ 99.933071 552.861778 0 ] (cb9-29) [ 129 0 R /XYZ 99.933071 780.226036 0 ] (cb9-3) [ 99 0 R /XYZ 99.933071 574.796389 0 ] (cb9-30) [ 129 0 R /XYZ 99.933071 761.279014 0 ] (cb9-31) [ 129 0 R /XYZ 99.933071 742.331993 0 ] (cb9-32) [ 129 0 R /XYZ 99.933071 723.384971 0 ] (cb9-33) [ 129 0 R /XYZ 99.933071 704.437950 0 ] (cb9-34) [ 129 0 R /XYZ 99.933071 685.490928 0 ] (cb9-35) [ 129 0 R /XYZ 99.933071 666.543907 0 ] (cb9-36) [ 129 0 R /XYZ 99.933071 647.596885 0 ] (cb9-37) [ 129 0 R /XYZ 99.933071 628.649864 0 ] (cb9-38) [ 129 0 R /XYZ 99.933071 609.702842 0 ] (cb9-39) [ 129 0 R /XYZ 99.933071 590.755821 0 ] (cb9-4) [ 99 0 R /XYZ 99.933071 555.849367 0 ] (cb9-40) [ 129 0 R /XYZ 99.933071 571.808799 0 ] (cb9-41) [ 129 0 R /XYZ 99.933071 552.861778 0 ] (cb9-42) [ 129 0 R /XYZ 99.933071 533.914756 0 ] (cb9-43) [ 129 0 R /XYZ 99.933071 514.967735 0 ] (cb9-44) [ 129 0 R /XYZ 99.933071 496.020714 0 ] (cb9-45) [ 129 0 R /XYZ 99.933071 477.073692 0 ] (cb9-46) [ 129 0 R /XYZ 99.933071 458.126671 0 ] (cb9-47) [ 129 0 R /XYZ 99.933071 439.179649 0 ] (cb9-48) [ 129 0 R /XYZ 99.933071 420.232628 0 ] (cb9-49) [ 129 0 R /XYZ 99.933071 401.285606 0 ] (cb9-5) [ 99 0 R /XYZ 99.933071 536.902346 0 ] (cb9-50) [ 129 0 R /XYZ 99.933071 382.338585 0 ] (cb9-51) [ 129 0 R /XYZ 99.933071 363.391563 0 ] (cb9-52) [ 129 0 R /XYZ 99.933071 344.444542 0 ] (cb9-53) [ 129 0 R /XYZ 99.933071 325.497520 0 ] (cb9-54) [ 129 0 R /XYZ 99.933071 306.550499 0 ] (cb9-55) [ 129 0 R /XYZ 99.933071 287.603477 0 ] (cb9-56) [ 129 0 R /XYZ 99.933071 173.921348 0 ] (cb9-57) [ 129 0 R /XYZ 99.933071 154.974327 0 ] (cb9-58) [ 129 0 R /XYZ 99.933071 136.027305 0 ] (cb9-59) [ 129 0 R /XYZ 99.933071 117.080284 0 ] (cb9-6) [ 99 0 R /XYZ 99.933071 499.008303 0 ] (cb9-60) [ 129 0 R /XYZ 99.933071 98.133262 0 ] (cb9-61) [ 164 0 R /XYZ 99.933071 799.173057 0 ] (cb9-62) [ 164 0 R /XYZ 99.933071 780.226036 0 ] (cb9-63) [ 164 0 R /XYZ 99.933071 761.279014 0 ] (cb9-64) [ 164 0 R /XYZ 99.933071 742.331993 0 ] (cb9-65) [ 164 0 R /XYZ 99.933071 723.384971 0 ] (cb9-66) [ 164 0 R /XYZ 99.933071 704.437950 0 ] (cb9-67) [ 164 0 R /XYZ 99.933071 685.490928 0 ] (cb9-68) [ 164 0 R /XYZ 99.933071 571.808799 0 ] (cb9-69) [ 164 0 R /XYZ 99.933071 552.861778 0 ] (cb9-7) [ 99 0 R /XYZ 99.933071 480.061281 0 ] (cb9-70) [ 164 0 R /XYZ 99.933071 533.914756 0 ] (cb9-71) [ 164 0 R /XYZ 99.933071 514.967735 0 ] (cb9-72) [ 164 0 R /XYZ 99.933071 496.020714 0 ] (cb9-73) [ 164 0 R /XYZ 99.933071 477.073692 0 ] (cb9-74) [ 164 0 R /XYZ 99.933071 458.126671 0 ] (cb9-75) [ 164 0 R /XYZ 99.933071 439.179649 0 ] (cb9-76) [ 164 0 R /XYZ 99.933071 420.232628 0 ] (cb9-77) [ 164 0 R /XYZ 99.933071 401.285606 0 ] (cb9-78) [ 164 0 R /XYZ 99.933071 382.338585 0 ] (cb9-79) [ 164 0 R /XYZ 99.933071 363.391563 0 ] (cb9-8) [ 99 0 R /XYZ 99.933071 461.114260 0 ] (cb9-80) [ 164 0 R /XYZ 99.933071 249.709434 0 ] (cb9-81) [ 164 0 R /XYZ 99.933071 230.762413 0 ] (cb9-82) [ 164 0 R /XYZ 99.933071 211.815391 0 ] (cb9-83) [ 164 0 R /XYZ 99.933071 192.868370 0 ] (cb9-84) [ 164 0 R /XYZ 99.933071 173.921348 0 ] (cb9-85) [ 164 0 R /XYZ 99.933071 154.974327 0 ] (cb9-86) [ 164 0 R /XYZ 99.933071 136.027305 0 ] (cb9-87) [ 164 0 R /XYZ 99.933071 117.080284 0 ] (cb9-88) [ 164 0 R /XYZ 99.933071 98.133262 0 ] (cb9-89) [ 194 0 R /XYZ 99.933071 799.173057 0 ] (cb9-9) [ 99 0 R /XYZ 99.933071 442.167238 0 ] (cb9-90) [ 194 0 R /XYZ 99.933071 780.226036 0 ] (cb9-91) [ 194 0 R /XYZ 99.933071 761.279014 0 ] (cb9-92) [ 194 0 R /XYZ 99.933071 742.331993 0 ] (cb9-93) [ 194 0 R /XYZ 99.933071 723.384971 0 ] (cb9-94) [ 194 0 R /XYZ 99.933071 704.437950 0 ] (cb9-95) [ 194 0 R /XYZ 99.933071 685.490928 0 ] (cb9-96) [ 194 0 R /XYZ 99.933071 666.543907 0 ] (cb9-97) [ 194 0 R /XYZ 99.933071 647.596885 0 ] (cb9-98) [ 194 0 R /XYZ 99.933071 628.649864 0 ] (cb9-99) [ 194 0 R /XYZ 99.933071 609.702842 0 ] (configure-default-service-account) [ 53 0 R /XYZ 84.259843 561.590928 0 ] (configure-etcd-user-and-group) [ 45 0 R /XYZ 84.259843 283.686971 0 ] (configure-kernel-runtime-parameters) [ 45 0 R /XYZ 84.259843 539.222079 0 ] (configure-network-policy) [ 67 0 R /XYZ 84.259843 599.840928 0 ] (contentsbox) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (create-etcd-user-and-group) [ 45 0 R /XYZ 84.259843 169.788971 0 ] (ensure-that-all-namespaces-have-network-policies-defined) [ 67 0 R /XYZ 84.259843 564.092928 0 ] (header_bottom_text) [ 6 0 R /XYZ 85.009843 422.718898 0 ] (known-issues) [ 45 0 R /XYZ 84.259843 799.370079 0 ] (overview) [ 30 0 R /XYZ 84.259843 272.631496 0 ] (reference-hardened-cloud-config-configuration) [ 534 0 R /XYZ 84.259843 537.158799 0 ] (reference-hardened-cloud-config-for-red-hat-enterprise-linux-8-rhel-8-and-ubuntu-20.04-lts) [ 557 0 R /XYZ 84.259843 511.863778 0 ] (reference-hardened-cloud-config-for-suse-linux-enterprise-server-15-sles-15-and-opensuse-leap-15) [ 534 0 R /XYZ 84.259843 397.010799 0 ] (reference-hardened-rke-cluster.yml-configuration) [ 77 0 R /XYZ 84.259843 191.441066 0 ] (reference-hardened-rke-template-configuration) [ 390 0 R /XYZ 84.259843 518.211778 0 ] (set-automountserviceaccounttoken-to-false-for-default-service-accounts) [ 53 0 R /XYZ 84.259843 522.092928 0 ] (title-block-header) [ 6 0 R /XYZ 84.259843 502.818898 0 ] ] ->> ->> ->> -endobj -4 0 obj -<< -/ExtGState << -/a1.0 << -/ca 1 ->> -/A1.0 << -/CA 1 ->> ->> -/XObject << ->> -/Pattern << ->> -/Shading << ->> -/Font 632 0 R ->> -endobj -5 0 obj -<< -/Filter /FlateDecode -/Length 2586 ->> -stream -x]c +|`J"AASAPb3$6cw?iƘ9⑨x^DiCk;?9=IYsks!^Z>qP{N/'yܻ_N~v5B%|嵫LCmJ&D%C)*1{g*%{TUaeR#3jGUFc*{Dv$Bu0D4]̡` ӥJS].tT92]ܘ`K.Ö̈́`iLW`-Ue -[f]-FuEDrofTסVۣ.I -2|S; -T*%R$w-Y%1Ë5[nLaKJը`R-R CvPp.1Zd ifQ VeH=+2DRd P- -#FbعT[c&؂%2(hknMzd,P$pa0(cpX` -bWu5XZ+ -Ea,0pWWRl3AcSw5Je,0p(1`U0WBjM MMTAe,0p7e<nʒ M -c%?Bp<-,c=tI p0dp7v?A[/܍ Gu=Ċ'b) TX]151dp7*"5Ӂ1ua,.Xw c[ץX]`)1 -i Gq䡌ExܕXP]1=T[%5aے=d5H)ܕf:pWvƂzd,(1,81fZ JQ] hgƂ*d `Uc,@bXPlє j-H }]h}`"cHZ7c,ì2]IUt2j82 - .1 1[U BK̙.$ٌt%؂l*c"4jIL5әx "c *M` 0Xb;3A2`fc,h-y Z-Ic|X c,RɌ8t"=6ԛ /l]&Jˏ_!ώp~us8Q]n &v@o2hC]zэc4㛇/_*}᫅#\7! /X?ᒯftLS9"z<:Tr[>g?{xLPoy>*<.4+u`"ĕ%>U-U)Hwp]AqTلQ(pKlSWpO]ܖMu[ NVK/TTVcvŇL7s.u"qkbNj_m8~}#w[+Ug.c)յ͉'cnm{Dt_Hߤ y=/\IX!y.Sd˒"?MyS9ޠhyZkߛS|?ILhuݦ+:}v؄ws۔mڇy {q^7Ŏ1?Pnt˝xٙV2+qs> -endobj -7 0 obj -<< -/Filter /FlateDecode -/Length 3524 ->> -stream -x]Moϯ " A;wHSi^M5 mK~îbիGi^}[rzM)I+'?5ޭD^ULѩᤕ] G%vӿEO^uZŇ5d]|Z5?q9|}?Olh֬f1&1.eh%pk'{|I/bQB6!m -{ý5ѳGD\Pkж&XGT?߲H!JƱd'Qx^it"}#HSSSu?2.uEZEXME rD+R @#%KQYK2bLGۦ`9zș[<C dj xDq) [k\Q=A# QT?/(G0X)))уDoEbOdєI//tGҝ}#=.΢SVpBʝM$p,$ꜯ+-HׇTB@=6#ѣGT?߲H!Hv.J& +̀J ((.:HXJ4#>{ }_p)ѐ:CQmn7`8{L-d  -qQ2HfHC%Uָ٣@zFtC~D9tRY&DDD^%*z.DDDH})>;-tKq)Ŭ(N$~ qWJM$p,$> l4\HpxEۦ`<L-K~{گhRLcJbzcqiw"]qH:Tv{AIpk[_8|6y_6t\/P|򉊗e18,|ʆ/ -|-Cz\z~ V;A4"ZMCv.NÉ*z J`raM p6|%\P5[NbtjUKWUfܶMvkӀ){qʠpl\`"guŇg٠öl/|V菠w rmkanغ@mk"x>[{wQfjvjNڲOMwvDf{X3kT ɵv@Sn7bk\3]R%m9Q&`¡0PV ;cBZzZस^YrO^_ -2lڵ Ifemq h-Kj/nk2&PH1A ֭\6V"j'þ򽀹I: 7 6v#:jmbsp)T0lT1a~ZiUYd|Msz6,մ8[׍> -endobj -9 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 671.061024 504.679134 638.361024 ] -/BS << -/W 0 ->> -/Dest (overview) ->> -endobj -10 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 489.361263 663.111024 496.429134 648.111024 ] -/BS << -/W 0 ->> -/Dest (overview) ->> -endobj -11 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 626.361024 504.679134 593.661024 ] -/BS << -/W 0 ->> -/Dest (configure-kernel-runtime-parameters) ->> -endobj -12 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.881526 618.411024 496.429134 603.411024 ] -/BS << -/W 0 ->> -/Dest (configure-kernel-runtime-parameters) ->> -endobj -13 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 581.661024 504.679134 548.961024 ] -/BS << -/W 0 ->> -/Dest (configure-etcd-user-and-group) ->> -endobj -14 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 146.805601 573.711024 177.256773 554.961024 ] -/BS << -/W 0 ->> -/Dest (configure-etcd-user-and-group) ->> -endobj -15 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.881526 573.711024 496.429134 558.711024 ] -/BS << -/W 0 ->> -/Dest (configure-etcd-user-and-group) ->> -endobj -16 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 536.961024 504.679134 504.261024 ] -/BS << -/W 0 ->> -/Dest (configure-default-service-account) ->> -endobj -17 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 146.805601 529.011024 197.845152 510.261024 ] -/BS << -/W 0 ->> -/Dest (configure-default-service-account) ->> -endobj -18 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.893245 529.011024 496.429134 514.011024 ] -/BS << -/W 0 ->> -/Dest (configure-default-service-account) ->> -endobj -19 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 492.261024 504.679134 459.561024 ] -/BS << -/W 0 ->> -/Dest (configure-network-policy) ->> -endobj -20 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.809749 484.311024 496.429134 469.311024 ] -/BS << -/W 0 ->> -/Dest (configure-network-policy) ->> -endobj -21 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 447.561024 504.679134 414.861024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke-cluster.yml-configuration) ->> -endobj -22 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 234.738707 439.611024 313.229430 420.861024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke-cluster.yml-configuration) ->> -endobj -23 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 489.877620 439.611024 496.429134 424.611024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke-cluster.yml-configuration) ->> -endobj -24 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 402.861024 504.679134 370.161024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke-template-configuration) ->> -endobj -25 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 484.970394 394.911024 496.429134 379.911024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke-template-configuration) ->> -endobj -26 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 358.161024 504.679134 325.461024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-cloud-config-configuration) ->> -endobj -27 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 210.896178 350.211024 288.867613 335.211024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-cloud-config-configuration) ->> -endobj -28 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.993831 350.211024 496.429134 335.211024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-cloud-config-configuration) ->> -endobj -29 0 obj -<< -/Filter /FlateDecode -/Length 4932 ->> -stream -x][$~_QφG c,}Y})15ʌ̪NSӕ!e(BK۳weS%E:_>>̔p07'5`K >MzCzNϱg7 M䧔S2Ai*h2+M!L)h'X1B"Gۦ15A r.+MbxJo -pɒ1l IirXgA wJ SѣsqEmKhimO1 Vk+S1d K(jmKd6B>'-BQ km 8X(m YL4Vk+~ -%mm&ms&L!{o6kj2 -NIis%P6qZ, 8|YV퍷Z[,%R !ŤA2hb\04Qq~LYCD)y \ Œ4ƢY ,BBmҰ;ȂxYy <Ж-x-b5,[26jXhX>GҰrJEN <@4,@]Ӱv=azFz36Ȃְ8y$ 4r0jXX\FlH)@mKrkX@]6sw]0N:rQ1j5,X 0ߣy lr(K4,][0)9 l.QÂܵSd,-<kXϬa0~Œ4,]1Skm]Ѱ wQ7 EaV&Srְ wKN“@-M$ax2C5,]LEÂ5{ "p 4,@]6(V'ZpXxXkӦ11e *iX3M%aA,m(Զ88hX AJa -5,Hx4,HdаT,ouyY. *E dS.DU覜j[FMDbaRSFkX\Ұb͒@Pkmְ.ڬհ ;ȂjPÂ2VhXkIZk#̬aA8qa+M Y?`&9jd4,r3kX3dqiXfҰȂOÂbeqaAMG /y5,(`%G^o& -AEm,($7NZ[,%F^of Pf`^ȼLvp7 Ee5,֛lLo̼ꎁ̭ꖁbJꞁI4XY`ZE5궁 &vUD8$̙9iAۚw;nc|gNYuOq^X#bqtBI4qz+S$6ؚr0)TW^NP#;9n#=bD@B-ԋGЯ5cF^ntu7ňR/?Nt.{jֲDs$o*3β4Pve -1N,1Y1ws`wbAy2"K qy+Ųn#!N,z^(,9I"}QKˁGgVYZ!Q#GgvœOfoәU,_A/=^3;C鯷a ?V?Y0j >:|,|}?=s -ַ~~i9з|9WЯ;/KρOg5ȡxߥp_k[tf -_z}1K;]xoךdr7\<K`]O_wϛűO2񚿗[y1?>e7,~A`sG?ݱ5PllPv73eP!,ϙ*xG|#d;w⫹o6>,2,> 6W:1klfmb3P6gK۶q+myv}x(mNK̥1C< m> 6j}9ιT>pq\tէdth\1um>dep?TF3 b|+Ş5H"8>lc0hɺ/g-VDq|pW/;y}_bcce>˳Ə"mQ%hnXɣ8 %wX#XגW_9ݝyl9̙۹{Ff?SwjYwͷy|njܗQ^mn #sˡfG5V׷l\ɲ됏ц}`#Ww-rRezbLiVe8cfi36y2 _a]lZ[ -_Zaxs2zyXp܃}žׯm̜\Vу-ΖS~J0H2+%p,6t4'[%WM|gh[SñΒ:;[#O,G:{ku>K+\\k'C𨽢"S9/oߜoú8le=&F6N7|:~o"3E }W&Fn@z)Y***7+'0>̈́<̆6uG!MǼ{7x*})W1x߭eSq->(gS0^0G˽mZȦu B.]a>Q^sXL~tۿYl.gb'tIlPQӋ Y#c=0m<g*$]A"1b-=O=]}6;5lr&7&Jli#wͽoq^S?t`=mCPZ%1t -k ʊyo};U9 jRcB|,q]VrDH8. &' -cQFmԧYɺf-D^HdeGf/"ǚLmިWIm1Naۜ|P["|+rzj҂iK JE L5ӪYfjjNt^iF +qӗUK@Asڙ޳ՒYEyvR+m;6c,Ԡ.H앩駅MWkrGݲz ;6וF~0oc1C_"(-9l=9HMth(wӊQUzʖN$oic<_y~s^? < -endstream -endobj -30 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 29 0 R -/Resources 4 0 R -/Annots [ 31 0 R 32 0 R 33 0 R 34 0 R 35 0 R 36 0 R 37 0 R 38 0 R 39 0 R 40 0 R 41 0 R 42 0 R 43 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -31 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 445.281496 409.271317 430.281496 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://releases.rancher.com/documents/security/2.6/Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf) ->> ->> -endobj -32 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 418.281496 162.214732 403.281496 ] -/BS << -/W 0 ->> -/Dest (overview) ->> -endobj -33 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 403.281496 332.953990 388.281496 ] -/BS << -/W 0 ->> -/Dest (configure-kernel-runtime-parameters) ->> -endobj -34 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 386.659914 295.486949 371.659914 ] -/BS << -/W 0 ->> -/Dest (configure-etcd-user-and-group) ->> -endobj -35 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 169.605601 388.281496 200.056773 369.531496 ] -/BS << -/W 0 ->> -/Dest (configure-etcd-user-and-group) ->> -endobj -36 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 367.909914 319.724254 352.909914 ] -/BS << -/W 0 ->> -/Dest (configure-default-service-account) ->> -endobj -37 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 169.605601 369.531496 220.645152 350.781496 ] -/BS << -/W 0 ->> -/Dest (configure-default-service-account) ->> -endobj -38 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 350.781496 255.796275 335.781496 ] -/BS << -/W 0 ->> -/Dest (configure-network-policy) ->> -endobj -39 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 317.031496 400.593883 302.031496 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke-template-configuration) ->> -endobj -40 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 302.031496 397.449596 287.031496 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-cloud-config-configuration) ->> -endobj -41 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 233.696178 302.031496 311.667613 287.031496 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-cloud-config-configuration) ->> -endobj -42 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 293.575760 126.231496 442.798661 111.231496 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/1.6-benchmark-2.6/) ->> ->> -endobj -43 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 111.231496 285.368241 96.231496 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/1.6-benchmark-2.6/) ->> ->> -endobj -44 0 obj -<< -/Filter /FlateDecode -/Length 5113 ->> -stream -x\Yɑ~?<%r30 hc?[ W*8U-:TdDKe;[yBΔRso'kro鱹XR6T B6F.euv;{Sk.7Q0lTd]Pb49 X6b&OǦ 65 (Ml.*ّ6\Yir|8oF,QJ&AIkΤR}U2\Z[&erimդbjKtDVk/Jx )X ֖tV m&봶LHmh%cڜ36(()e̓dcUK kmhmr)n NkLjx5 ؜42K UO * -R 45J5k8Cw ^"% /PI :hXx4,@[hXdӰ oɺaAMaA→HÂȅ)U 07;5,]laAꆘ$ p7p7T X  pkXaҰb|)VbI e=4, ஏX湁>Zaw=a  w!Q V{a&3a*ܟVƕ4,]W>!qeBƥT5,]8aA>x5,]ੵ6jX0hXfmZ X [$j[60$aXġ$.{հ wm AÂܵGm/x נ VV@ - k4wUÂeaALE0h{ R!SsNjцOmKQÂlA, P& XjѰ {װ {AD:Djz^`.j~@@2S*9&c֖)paAdȥLװo8\Ұl͑l L̵6^dkXHmiXP~>?X`"߈Ԭwj1)> ȶVUVXTA߈F\$C߷ya.55:̵ky.193=YVBʜo&;u{l[7mZrQQ/,xy4aR~Kto微Gy]mbsN'!w5^x\(#l[ѤfWw9;R\7~u:E>?U9F9lLu`"{K]W1K~wME|~ u.+Jhc3F@hf`~K%O7[, حs3ixQSmGYf Oy[cp;!2aP{J h?U)#6{4..SL ;~S"ѧǼrm:`Xu7 B*#yTq%UYz(ֽx;7!DB%7]D< -Pdj9 [\E#fWs -^%sz*CFÄj͒9*,*yݵ|IFb cpfZ>=aU<RJNd(t9 Avv -!\9 P/Q.䙟9y޾7R6xjשݧY1[=Hknji!/aKH,MjW.8}Kn|*I5ݰQAq? y1摲}ЫG̥MLn16K;}ߤR=$~oyoZ+'m1A[,߯m~+{a/͍DJI#Vk)Za:hpr\)r(svHy-n K]Qi#1]in}k_{[p8a3LY'dלD]K!C|} #_%SXeP1oEwq^/YU8$  q0X J1o\u@Ma>JШ@*xDy5! >EbxF1P*qB_5X!; 3>sX/~۴u}G;bOE:J ecc&IWk2*7^,J6 䎲;R :tC;(TWkNukvlnj5Q<UgpWn\: ^2JQ{Ψ>#5o#dYF})}W},(GNA}o)qG{9&5ۏ'j:S!M?T_q"gSpm,OolI{mMvdiyZBtZIߵgiKlayVordT\xy Љ|Vq`\3Y8-&aĠ>p{v?o>]qsŊϭ>`Khn?I@s0%ڐވb7bFQfJ@7vek/Dmx6θc^sSTbmu˝mtXxAv/Cn)Pr ﵷv?Iclùo֚^=IKnM8_j;`g=$Mb\lgڕ]Wp :ED!dRxSم\|F -ӎ gƶ湟WcƯ#mwBd^5ońv+1uA;'A$#ъMΏO ѥIK9g[ {JKtvZLAP =)I!}j2GК2nH4O!]Nj6[ʣWCkdez(C -"qY) ̯j]OiI~9Ŭ+l'A;N{T7MTؚ7Pg. ռ$[!IzCȃ;P1wf)tG! ULō1u%au3Rmg8LeC|ƱU7KN{Nr"yhfc^axYldnL'cI0n_?&D)H -?&%w'Dkvغ!KOc˃df'm#O+o0i{O7ԍVIS._7G 󵺙{ }q| ҹ…\.l %Ŕӥ 9). l&=OR%.DatrN[V! BN59W0zo,:}P_$u,tjX.r7wJh #ș[c6*ek)uQ vژ1wRŲR#ԟbZIK'G=Ҝ\=G,YZfi{۞2h2fdjx*{Q_zm*[Q嶤 !PE"JO]8V6zC "͎?>zAL?LV]sPJ:%veT?68-l -xm P` -endstream -endobj -45 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 44 0 R -/Resources 4 0 R -/Annots [ 46 0 R 47 0 R 48 0 R 49 0 R 50 0 R 51 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -46 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 191.048717 658.622079 244.661998 643.622079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/admin-settings/pod-security-policies/) ->> ->> -endobj -47 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 439.875057 101.433071 421.125057 ] -/BS << -/W 0 ->> -/Dest (cb1-1) ->> -endobj -48 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.928036 99.933071 402.178036 ] -/BS << -/W 0 ->> -/Dest (cb1-2) ->> -endobj -49 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.981014 99.933071 383.231014 ] -/BS << -/W 0 ->> -/Dest (cb1-3) ->> -endobj -50 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 383.033993 99.933071 364.283993 ] -/BS << -/W 0 ->> -/Dest (cb1-4) ->> -endobj -51 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 364.086971 99.933071 345.336971 ] -/BS << -/W 0 ->> -/Dest (cb1-5) ->> -endobj -52 0 obj -<< -/Filter /FlateDecode -/Length 4935 ->> -stream -x]K$7rׯHF:.0 2]#Z3̨gO*#  9jß\R˯.֤`\TM,'\9\%J)^?^gw9x?\k[])%z ,&rJ6(uB0)VtXƂ!#+A .9h,g!qrtdc1\ Ia9 9VAL^`"5w&K5]pc!K(iYc0"dHVAiYBAFpIYp次pJ/p,I<4 YG AUy -kX@D3iX@@[hX@[iX@[.jX@\i5, . T4, `.;5, .{Ұװ9jX@]bg5,`.j<ְheҰlҰF^F `+l5,`ϖ5,`Op*/AҰ>4 z G `(ch  z8Y߃I4f< p?eN%jX.cT^1.AʼhXpTaA>x5,]G|.↠a8ga*[rְ wK^xac3D%CrEaA½ "p" "p2Y({ ׀iiz Zx]kSѰ wmjX|ְD^ÂٔXhp4,HRykX*YÂ! yaA!Lq\! "E d&f RǠU p2x.iXbar)15, 4,9ְ Ȃa\sAtsNÂ! A 2հ$TJ5,` R<а#vаM9*P` rnf r,z `o& ,4,(6 5,ge䛞5,|3kXP"DBQͤaAa<Ȃ(|"d5,(1J5,@|$%Lrp7 "2&"[-ސ,gVW ,7K o5 I]4,sTW VtV]6_c|ei^0d`D=Fe}|'5F/oq]MB#BO#B2tuM+-mE"C0S7"Up+Oy#YٖRf!CԆNUJoٹ%U+n&IMHh%hT{Λkvw(I:o tb2e6?x5NIUJoٹ4ia/7xn_/~/??_/?d6O'"G$_:zLX{Ƶ>q^zeiBkTcE7*ݣeGkyǪ+-L?h!x#e؟]6yi)P?(IB;qbal n 'jP,rLܲ%&Ge r4E;!6](۟?1) 񛺖7P5o -5$kQڈوlTtsuQIt.[2*qum~.Vw*IJtK;n?^{n u\?w{yK&b<}q8Q>q;<[d-tA_Fg.jm0HၡLj:~ewFoo)|w9`'e:lsԩ)O-9kATltjL 5> p+h_i p2t~~g1 CuڔW/@9MAZjX w?7!;1]@-Y5K-uC䭉Tc۬26>Y`mۼ}Y g tYxMn6r)M?bzcAx{e异"C^GU y-9Z_" x\/ _=}0ޯ=n;PykD9R({G7©*_zիDWӮџOƷe@#9j鞗&Kȝ JvuZwɡ Lm';~""?ӆΌmkÝ#pw#ݤHvl%9:W1)!''eGt2'`V2C'ģeX/bśkѩSszxD#e#xRӻiY'm}5E<*φGz1=׳jsw촧b8(P (atA5۰cy.ͧIݔZ - kM]#>{FTokն[t(7!u(4u^4C/u%L,fձk_W{ږuwBncVYepf em6j62h뮭{W`w;yn{Vz @OS_'\i{c^./ڃ49?C(wgQY] SVfGfIm[V _OC}/nVH;ҏxwekN#FvGj:'pv87ͫ1\W{ͫGvάG%&&iU=${\EG"Kv_=[owqxu]<bIӨG3-7k71];ձ;0s:W[i[ؑ#HuOҋp}_$ar#L5rƒ%?$u>hM%$!J8G9gRh]yXZٱR5kfs/1q귐APmyZ89)m?帅i:}{ u) >TuygK=cX9fryޅ|#O='|=f" _[޳Uɼ'XT-9?>U,pe~"L'n6"F?9#/IWSo+azԔjn5گjoԆP[M!S_mN|n.շXD,kXi*WyKD!ZW7j֗!K_2I^QcXV׋d\$Vrb?^]vd!_mo]"}Iv:Pdjcm+D)crָ,D^.JMfG< K b8 {n8yLW].:7 + /O_.ԏ*UB֚jhtjh%p'rQ4c0;5?ν4C^r -墖kLH^*i~2LrWB{Na%y4G,[<Z`!Sw_.L䏗a` f"Mvr^̪*LF7a*B -/IIl5F'27;y;갦i%Kbtlt؆:l%nu,ӱr&&M< };n2رLN}v:6ޓsd%7l;C0 XmvtUd}Rݜ%M{s2^ev[7ٓ{YI<(ӈ}LDˣlhM쭤:w&ÉzGfN=ܱ{vs`(/jRb\ᒯSå~Q\N!FL1ȹz硐b -#nzS4_ ;-y?yz}"6ڡS?~cB퀧S^e9ThlwhEܣ䌩1B \6:QshNpmbj2ŵZSKj)bP>k:̣ҕQnx=ZٜӸ;;JX2+8T%ю}mm$ԎjPST+.+D\"O6 ayEi<-q<]qey=a8 *EFy̘j^XS3`j[veTQLOfyn{\,ԟa# -endstream -endobj -53 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 52 0 R -/Resources 4 0 R -/Annots [ 54 0 R 55 0 R 56 0 R 57 0 R 58 0 R 59 0 R 60 0 R 61 0 R 62 0 R 63 0 R 64 0 R 65 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -54 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 751.923057 101.433071 733.173057 ] -/BS << -/W 0 ->> -/Dest (cb2-1) ->> -endobj -55 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 732.976036 99.933071 714.226036 ] -/BS << -/W 0 ->> -/Dest (cb2-2) ->> -endobj -56 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 653.081993 101.433071 634.331993 ] -/BS << -/W 0 ->> -/Dest (cb3-1) ->> -endobj -57 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.134971 99.933071 615.384971 ] -/BS << -/W 0 ->> -/Dest (cb3-2) ->> -endobj -58 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 615.187950 99.933071 596.437950 ] -/BS << -/W 0 ->> -/Dest (cb3-3) ->> -endobj -59 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 596.240928 99.933071 577.490928 ] -/BS << -/W 0 ->> -/Dest (cb3-4) ->> -endobj -60 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 280.647907 101.433071 261.897907 ] -/BS << -/W 0 ->> -/Dest (cb4-1) ->> -endobj -61 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 215.950885 101.433071 197.200885 ] -/BS << -/W 0 ->> -/Dest (cb5-1) ->> -endobj -62 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 197.003864 99.933071 178.253864 ] -/BS << -/W 0 ->> -/Dest (cb5-2) ->> -endobj -63 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 178.056842 99.933071 159.306842 ] -/BS << -/W 0 ->> -/Dest (cb5-3) ->> -endobj -64 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 159.109821 99.933071 140.359821 ] -/BS << -/W 0 ->> -/Dest (cb5-4) ->> -endobj -65 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 140.162799 99.933071 121.412799 ] -/BS << -/W 0 ->> -/Dest (cb5-5) ->> -endobj -66 0 obj -<< -/Filter /FlateDecode -/Length 4904 ->> -stream -x\[$q~_1DR p I=6rIVw9+[BUMv._/j -9SJ͉.?^v栱s:KDWS5o;]WَqWojM_0%gV˺b49VrKUcAӑ!5 *#PvȪgG brr8oʃ (xIPzxޙT*/x!EI)ŢjƋ%:" 5^,! /9h Yb Zh䓆pj5D,X ALf< "pU?%Vƕ4,]W`>Wивq)U "p*hXϢa0 z "pdjuZ "puC԰` - ߌp]WhX%aH#9 Ƣհ wޫ kc$%=*5,@]Viz Z k<வjX65,H hX `aA*djIÂT-x(T^28d Bdk߸p.}^hw{ÿaί ^\iV:^L,vJ-EƄ<~Emk{ȇ*;Q62SE%bbqPʬnnڥ#j~J94:|e"/3)ل>Ns%Q7&M\d9 ]A{GMwit nౖ( -pmm9C~^= qk=ӓ| mq+>lNwv\%6 $p7s.m^㶪b]sҍY֓Q?! i.c>Dơ qȋ̓XoqqU^3yz]i -X}SB۫ΰeEf ;vE<7'`~ -Wc[ -u1_\5榶L`AwS1ۍ|T<ܚN鞼;b 0xWo- -qzMe]mم`?Cn33-gZFpH>ȉ$[?OI1iɗ3?{s'$䘟;Ly!maN3(%Ut!%&0Br0v9䷇GG/Flj\O@Lܭ*lzBϧ'r\Fj^䄧QR#48U@=)Wܣ-X1xt#kنG"֭|~E hBM?yf0SXoѺUV7(=o{xXoal=<݅ 4U[$n#yn/FnSpS`} ݼpi-s=ox@;/Na:]u!Ymt7>WuPhZuz[O VOzڤqYȭ=S=Bn[vEh_v]y_Eΐya['vqVC)>jE֝!GX-"O}zokۿmWN~rZ;_>q7HgKyB B'zYWWro*vޅ ]Άy|3(,Z_Y)N9Zi#v9;8*wWw{F3M7Z坝F<=8?_vlerܙ~ɣwqqz_cO[3T?᠟4d>MbM҇ノ9.n+e޺v~RYv WrEF:{GW Ww>%{e磯s38яVNc5c<`ƿKt,7IbMNĝٺeWmƓۣ%ٺω_掘>6u\s~[1yBPݮ)]]{Ͳ}`X{uigt8pyr{U]b'xXSSyAkm -NsF>䌑3_]\f^Vnf "E%"lE/Ԑs9g| -΄^7~1m]ăwr%"7{1;I#]5#}W=덽}|t! ;1mrҩy;GńEAik\⾆v嶏o9}_eZ!}}^jwu\ݾw[]@XFwѓύ(ͦxWKsMngo53ef{tI|LC V$?i VEF}Lj'Iw Tog N+({{ =d^Z6~}.G,4j*!{# &_1%==cf~T35ߕeUnҭ]Wk߷%d~0o)dI2ןvEn{.Wg~i9#p>>';ޘk/.Vܑ̫ƭdQelƄ$ϝ΁.XAGdO]ǟ_K8Ds\9ψ .7Suz;hAU53AhI!. -ۧ&s|[ynu8,Ye]S +x)s1bC%'@-oxD8o -H bA.vˤU4~^"*#Oos><䭒$= !MϠ;P=.- dh$o3Pv\,9q;i`$aq_yw%6ړK${;ݼ N -ut~ދ8P\N6bCʋ ճ$MZ@|&fSwZ[8%prbru#"z0u@IXSppSCc b/"g,-hs }TPE6bhƌ˔a]-mER5ŤEj:J %Fit8oTKa@QsQKAyfi{mb4I2sX> -endobj -68 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 748.173057 101.433071 729.423057 ] -/BS << -/W 0 ->> -/Dest (cb6-1) ->> -endobj -69 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 729.226036 99.933071 710.476036 ] -/BS << -/W 0 ->> -/Dest (cb6-2) ->> -endobj -70 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 710.279014 99.933071 691.529014 ] -/BS << -/W 0 ->> -/Dest (cb6-3) ->> -endobj -71 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 672.384971 99.933071 653.634971 ] -/BS << -/W 0 ->> -/Dest (cb6-4) ->> -endobj -72 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.490928 99.933071 615.740928 ] -/BS << -/W 0 ->> -/Dest (cb6-5) ->> -endobj -73 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 287.395585 321.344928 323.513505 306.344928 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://github.com/projectcalico/canal) ->> ->> -endobj -74 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 291.344928 111.294999 276.344928 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://www.suse.com/c/rancher_blog/comparing-kubernetes-cni-providers-flannel-calico-canal-and-weave/) ->> ->> -endobj -75 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 308.171464 172.723346 401.561844 157.723346 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://kubernetes.io/docs/concepts/services-networking/network-policies/) ->> ->> -endobj -76 0 obj -<< -/Filter /FlateDecode -/Length 5549 ->> -stream -x]K9rׯ#x`d`,ւiF|eFUVI}3I22#H&ۜ5~g_"R1I5'R3E6&_ࢊ'>w똳U9ko)F텢"mP佊 9KE`G/`rR kPhܾ(  IE`d"Ze`D9+2kTHf,D+9B$TU'HexC2B.E,MIeXH' e X^tF*NIJ2bڗYOiaN,GAI! -eX^V*sW*NxSղw;T2K`x1HRKeK%J -ؔ$+ -9J8A58 ^< /$aHXx$,p@[HXoI aM-aHȅ)e 0;%,p]{uVuh je,aQ9uFG  7@ -v$,(6i6bˢ: k=^Ak+aw- a E w!^ V(N4, `Ui ʀ@RpW%,]6%, 6IX`+aAHrA‚5eAKX5%$ak]ND ^D ^2HX@e[L E RHR& | RʂU)Ų2%,b#ar)K  fWCJTf l  /%,H6! Z%!j4I‚DAq(a&R,/ NH~l"$aAJ$aAJj+al(aAYaqi-aA6 % o& 7 ~]|3JX x(bxAД&!:IeL8L @^HoFq3I*"2 &"[)^Ʌ3$h@*Nh`/F(h/HDf8kaFxv>ST1f/1we~o9}9}]) @Qڳ u9!"R S ׆Lgg"Bl3B3<0@2ПA'ě[:btqF<u!r65 - RtJ|KTaܕn0̬t`?Oeh!cnB%`@(C3;V`:@/nC7HCӭlj: u!r4@W=ұ#"-.UC0s0]zȄq㕾 L W)%Dct5oEzoⶋi츋IJ/- 3'Bzd 6,B,8/_QӇ} =%<_!:s]Ds;9לdeuYxʑ4\s_4rj([N`:# 9[$ƕY\OkQ?4 enϋ8 &ΦYSv8qӞjhC} ,oW$% QV&[^WC+S-*o 2_ЦF?Q=Dj@BW"BRo|8R]UގSZJmQ}ޜG8OÀSsF*14sW( 0fzIO0B7xi_RxIi2!_PS{c^K\)&bJeZQs ޗb~I5OBkG{mqc;]UގoA>O~W>CVw҇*oFd~Au΍>}tf9{ -gðE԰V~,,ke*+Y~ݰjWWBfel@"4ΞrͼoR~:4mΪ|S:=t]0|lv2Q&ԘL,{lM.f^$}7jcy.'M&-VZ/OV~'MgԲ^m7k^lUGC5>&G[& E锒okTԽ -u/B]O3r_׽acg`0ɺ;VC >fqS_%_ܕѰm?]]Fۏ~x^  P!Z}u^bFheNFqﾾ\]!ݱ6aW=S0XoiDŽGcbBz[ - }ijH#T9!ݒ~y{ [UZ 3PjH<U9^$iKۀ4?`ټUuwykyUA2,O ]̍ۤuGPR4T>NQvs}mv*Y}ĸ%V>+R'kNpY(xѿ+qOy$N=\'LwVV #{<+Q2=P\&48ג>2:Z6O4Lr96Kpk?F -33= d,ʷmZ&NڜLF؍)sr&lI/=txb&[H۠QuMV3hT<ݎBRbD|nSØNu6'67.onWslw?/M7QrЎkU*AYVU>x5ԹZf>pj@j(8unEMHN!u^EljN?s*:7w&di|l8-}lO; j]ö[i]G-zxP2NJ_ErBivy*Ҟ/tS>q+U kz=-:k}OqbM~|`, S]1mKX[_OS_N{= Yߔg>8gOdxw穙U4ƛvi,ﲕYQ+Amhjb-k}.I[G O@M)>Nt*;-9sY(_nxSv Ky%_ss~|pOץET7aGU׫Gt2xͰgq۾ԕ?0Q:=tZ,߬!캓i'~h95ДcuHX>Z,rAL!][mJr o)$E|9@9O[2o'>O2QG2K"Ӏ.'x'Wz쉺ɇo}ܑnSu夷cZg'ֻX)#b%i|7+z讓m(:3>k[ ݺ-YIص*] ޕrdS5= I ~keAk|BLՐ=sr[[MS=z\%YR@ S+G0٪XU: vcwSN~>(<;Vh_Mo$FNK1'\4F -ߨl/e`-M?N:?:1B'w}. W~d҈{9T90?Tn p}׉8nuC ۰u"#nt'WH%6dZCęqu݁>iV:}@tqd e#|nܺr+>Wr>$&qǏ!daMlA434q_FeԇٱJ+o1<؍7cü?_^߬P= ycj> -endobj -78 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 715.084475 101.433071 696.334475 ] -/BS << -/W 0 ->> -/Dest (cb7-1) ->> -endobj -79 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 696.137453 99.933071 677.387453 ] -/BS << -/W 0 ->> -/Dest (cb7-2) ->> -endobj -80 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 677.190432 99.933071 658.440432 ] -/BS << -/W 0 ->> -/Dest (cb7-3) ->> -endobj -81 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 658.243410 99.933071 639.493410 ] -/BS << -/W 0 ->> -/Dest (cb7-4) ->> -endobj -82 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 639.296389 99.933071 620.546389 ] -/BS << -/W 0 ->> -/Dest (cb7-5) ->> -endobj -83 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 620.349367 99.933071 601.599367 ] -/BS << -/W 0 ->> -/Dest (cb7-6) ->> -endobj -84 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 601.402346 99.933071 582.652346 ] -/BS << -/W 0 ->> -/Dest (cb7-7) ->> -endobj -85 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 582.455324 99.933071 563.705324 ] -/BS << -/W 0 ->> -/Dest (cb7-8) ->> -endobj -86 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 563.508303 99.933071 544.758303 ] -/BS << -/W 0 ->> -/Dest (cb7-9) ->> -endobj -87 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 544.561281 99.933071 525.811281 ] -/BS << -/W 0 ->> -/Dest (cb7-10) ->> -endobj -88 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 525.614260 99.933071 506.864260 ] -/BS << -/W 0 ->> -/Dest (cb7-11) ->> -endobj -89 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 506.667238 99.933071 487.917238 ] -/BS << -/W 0 ->> -/Dest (cb7-12) ->> -endobj -90 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 487.720217 99.933071 468.970217 ] -/BS << -/W 0 ->> -/Dest (cb7-13) ->> -endobj -91 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 468.773195 99.933071 450.023195 ] -/BS << -/W 0 ->> -/Dest (cb7-14) ->> -endobj -92 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 370.326174 101.433071 351.576174 ] -/BS << -/W 0 ->> -/Dest (cb8-1) ->> -endobj -93 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 351.379152 99.933071 332.629152 ] -/BS << -/W 0 ->> -/Dest (cb8-2) ->> -endobj -94 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 332.432131 99.933071 313.682131 ] -/BS << -/W 0 ->> -/Dest (cb8-3) ->> -endobj -95 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 294.538088 99.933071 275.788088 ] -/BS << -/W 0 ->> -/Dest (cb8-4) ->> -endobj -96 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 275.591066 99.933071 256.841066 ] -/BS << -/W 0 ->> -/Dest (cb8-5) ->> -endobj -97 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 298.350419 124.541066 391.740800 109.541066 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rke/latest/en/installation/) ->> ->> -endobj -98 0 obj -<< -/Filter /FlateDecode -/Length 5345 ->> -stream -x]]q}_ˏ"Abd;<%~H*3"L"K")QR/X\W)*orH.z_1叿R\9XITL1j/$e$i$U!)[YJ>mR`Y3EIfhHJ&($ ;ZL!Y!xAJFm"LRs*D2HiY|a7DZJ-Rlqi1 aEd!-+iEmωHLH)m^䜖ҌQtb< -faK>i;m4[4w1%[-{HiXIL-|l-:AyIlI"DIbD6{E!G6HF"a 13blq$.p KN%E%|K fj ץ@8P.%.p\tQu>X hQ -8#%. s` ,qQ9uFG  7Wp$.VMIK\@]4I\@]1iQ޵ ]뵕l@Q-F]P=Ҭ)D5ß`+eRxI>1-+ߢ !K\ LFT+qZJK\8(@oh@WLJ$.]В L"E  @J# w1g xW{$.]M{4⒕q ංO#XUڂ)46a) u.$. -Q $R9 qAiĴp%.` E.' -Z -$.@DA-N` " RLR& ZUJ VL FRK8\f ͐1T̥4[dK\HiH\,lA4(qA ̠%.$ZJ#$qA8Tn&RL- ?<`&9blq$.Ht3I\lJ\l|3J\5lA'qAAq,qhiZK\M|ӒKo& Әob'mvQL#D` ,-8 M`$qAIo"7\$w p&"[inA>">8bAcdfAO '5LAW4IIȳ1>c&rm? :y2įc_.F>MFxg?rA46vI,b+ |ӿ'ˇ1 -J_3ncⷝ|$>Ϻp\S -sY|h۲~t=]z//i <۞+Z9{/4g~ -1d0}Jy Mn(Gz-ۜOhJ[ o=7m E7"~42H E~)WP{Nikcj[Q(g"9&D!Yw9X5-o Lv3}W{־0:سEu?EL1/yf.RX;Եw J~H:jϩ< -k֔8ii|2~..*00Ⱦ6ok^ʾ~&3 ;~I{JWtlyg+wվG3N;VŬySiYM'~0஁w1SyNQ:A:Z58[X!K -.|7v\Ӈ}*iztFD}uveH]U|zDw{fC -V+/%AX[^~yf@Q0VigO,)M9O<l4s E% >C$keVr=ъA`|zfEYOE^J+s#aqs:01}WZTr -`uj:.LMǀ>dd!>pŧN<8ޏyy6 sG PޭAb#n@lF.RTd1H;s:O1~-;{oe%e(y8˾`+m3 6ObеIl;i=Ycv2EwRyW1|;oQw;J8i}+pD_&ODt$qQwGX[+9p`ЍwF.x1XB@/"X`n7ޢN|X -S|nlyѿ k-|rL+I`4ޓ|L+I˩jضc`XHGA FпP.˩!g>ZcTF_.ռ'vJ7GChF nA( -|t#\tNy@yټ+-*)[=lJ{6V?OG;Fs'ye͏j> @hx4rmYpV1jy}^Vxe|YXyXY~iajQI^ RrFAHmkR)IԢ q`|.s~ۉͶuî̶g`7JZ-xQ5Ft~@/B~W6[TFV~R}y m}drؾ'"bƕ\tvuRiG=(pwD۪qa};: =Buc\'D_se1<;ڠuIu_";q"R&srFǕُr=NVS=sPU)yts?U ҃-6aͦدWc>WLͿ|@tҎLmnS\w4w\7D'e/ik_.&=L1E̛0k?cCEs$fSȴm*svO9DNQ}UsIc^1v!4ي_@f󧀒rUhPmHc^`W<DPuj[Ӆ.lMgymvAn-}ZTm] F&5gj$nAE:ǸOTD-_"Kb˕j-MPw5 +m4K#lϥ8pԾio9^|rVr8鎗.6\l{ -ߤ<凡)>Ⱦ_J7xH<4!87)ʎavl/>lIn-M6cVth&f -ӸrjľAu!v^ʂ[]wzW Ux+ T+b^i nH;qN8WٝLqo\0gg#;cdCTimܺ#-'ڪ 4~6[;5uu݉4AMK ָemՊ-޾t,Px;L=!:+ڇtq1ˡ-[ɀ+iM2^ a_F}rCn &3VF{}w&,mޤKRW.9LRje\ rkЂ#Fijs?VJU. UJզ0f)wV-ҿ-^i^ \nZZG8~wlddanR9]meuAݐ#S&7߷xf)+&`&gUO8dҰ5F]kBw(rNG)MxEB>N0ղot:mOXw۲.fu&^;'\,?spo -endstream -endobj -99 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 98 0 R -/Resources 4 0 R -/Annots [ 100 0 R 101 0 R 102 0 R 103 0 R 104 0 R 105 0 R 106 0 R 107 0 R 108 0 R 109 0 R 110 0 R 111 0 R 112 0 R 113 0 R 114 0 R 115 0 R 116 0 R 117 0 R 118 0 R 119 0 R 120 0 R 121 0 R 122 0 R 123 0 R 124 0 R 125 0 R 126 0 R 127 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -100 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 289.074296 784.370079 316.109452 769.370079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rke/latest/en/config-options/nodes/) ->> ->> -endobj -101 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 650.584475 101.433071 631.834475 ] -/BS << -/W 0 ->> -/Dest (cb9-1) ->> -endobj -102 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 612.690432 99.933071 593.940432 ] -/BS << -/W 0 ->> -/Dest (cb9-2) ->> -endobj -103 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 574.796389 99.933071 556.046389 ] -/BS << -/W 0 ->> -/Dest (cb9-3) ->> -endobj -104 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 555.849367 99.933071 537.099367 ] -/BS << -/W 0 ->> -/Dest (cb9-4) ->> -endobj -105 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 536.902346 99.933071 518.152346 ] -/BS << -/W 0 ->> -/Dest (cb9-5) ->> -endobj -106 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 499.008303 99.933071 480.258303 ] -/BS << -/W 0 ->> -/Dest (cb9-6) ->> -endobj -107 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 480.061281 99.933071 461.311281 ] -/BS << -/W 0 ->> -/Dest (cb9-7) ->> -endobj -108 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 461.114260 99.933071 442.364260 ] -/BS << -/W 0 ->> -/Dest (cb9-8) ->> -endobj -109 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 442.167238 99.933071 423.417238 ] -/BS << -/W 0 ->> -/Dest (cb9-9) ->> -endobj -110 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 423.220217 99.933071 404.470217 ] -/BS << -/W 0 ->> -/Dest (cb9-10) ->> -endobj -111 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 404.273195 99.933071 385.523195 ] -/BS << -/W 0 ->> -/Dest (cb9-11) ->> -endobj -112 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 385.326174 99.933071 366.576174 ] -/BS << -/W 0 ->> -/Dest (cb9-12) ->> -endobj -113 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 366.379152 99.933071 347.629152 ] -/BS << -/W 0 ->> -/Dest (cb9-13) ->> -endobj -114 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 347.432131 99.933071 328.682131 ] -/BS << -/W 0 ->> -/Dest (cb9-14) ->> -endobj -115 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 328.485109 99.933071 309.735109 ] -/BS << -/W 0 ->> -/Dest (cb9-15) ->> -endobj -116 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 309.538088 99.933071 290.788088 ] -/BS << -/W 0 ->> -/Dest (cb9-16) ->> -endobj -117 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 290.591066 99.933071 271.841066 ] -/BS << -/W 0 ->> -/Dest (cb9-17) ->> -endobj -118 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 271.644045 99.933071 252.894045 ] -/BS << -/W 0 ->> -/Dest (cb9-18) ->> -endobj -119 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 252.697023 99.933071 233.947023 ] -/BS << -/W 0 ->> -/Dest (cb9-19) ->> -endobj -120 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 233.750002 99.933071 215.000002 ] -/BS << -/W 0 ->> -/Dest (cb9-20) ->> -endobj -121 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 214.802980 99.933071 196.052980 ] -/BS << -/W 0 ->> -/Dest (cb9-21) ->> -endobj -122 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 195.855959 99.933071 177.105959 ] -/BS << -/W 0 ->> -/Dest (cb9-22) ->> -endobj -123 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 176.908937 99.933071 158.158937 ] -/BS << -/W 0 ->> -/Dest (cb9-23) ->> -endobj -124 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 157.961916 99.933071 139.211916 ] -/BS << -/W 0 ->> -/Dest (cb9-24) ->> -endobj -125 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 139.014895 99.933071 120.264895 ] -/BS << -/W 0 ->> -/Dest (cb9-25) ->> -endobj -126 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 120.067873 99.933071 101.317873 ] -/BS << -/W 0 ->> -/Dest (cb9-26) ->> -endobj -127 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 101.120852 99.933071 82.370852 ] -/BS << -/W 0 ->> -/Dest (cb9-27) ->> -endobj -128 0 obj -<< -/Filter /FlateDecode -/Length 5053 ->> -stream -x]ˮ丑W@|_ b xc -m/slh¿J)*fPu 1D>D KdTJ9:_~>r*z?S$#E6&?s*foc8eߜocV~f9S 6Nyb>`1gI3|$K( K"A&A`h\/0FCf 2v(!YAf - ɬQ!eEYD+ɜS!FeBIlYIa7DZr)J[\pZdXNd ]Id)(ːS/+ӒM'УH! -2 [YﴕdJ2w1%ZN;#0XUy0nP8a.dr%βL!Yo6Y=PoдIM$щAׁy$xB -x_d(u6mR=DGd &n",i- A!WqUWq]"ފ=ZY^!R^G1)xWt=ǕLFB XWK+c`iKcCo UhfL^G6eRhlfo6߿S -7RԨv[NxP8`M>Yz/ǝ7l?5Z*ØM5,ٕx)46vak8qߞD4# }S{}N=AZƝq /&؂<WC'w3Baw۲az$lH~Ha:szN νr麐:R8C0+P wk +*N\nu/*zk͎m:BvtηsB_e{}q`/ &?o uAǯo Un۲'Ł~(#:ǁwޢ1["[tkdw&~|;Xo=o?ڠqCօ|;hk{M$d (孉AÀ(j~gzͤB^Z_=@HtO< ~yuӼ|@BO,f?׬ ]6(YV̭$m`ڥV\ު}WڹYׅEތWqmoMޡ@$Mue<1',=eVc9Wݳ%Yo]-gʴlFmݳ^j[|)b)F:ǁ[}ښҕ`2:M׾o9m:絳#u`P{Ӝ= C?]|0U62ns]w6]nt4l ߪv)ޖiSWܦmRmmЪ -i:ǁwx#7C&J)h݁ل1sxxv~)Dy= %>:0~ނǘq-j\~'wiQ#/O/Z iwHoe]vx+u>V7׵s?;Bw۲縄^{q B17|{dg q:{txP8vfS[\օ|۳Uk|/K'w36gqVѠqyW.ggkg?z(U4s%~KJ -u*m|;ηgx?hP06rwM)8H0jjo+p|9|b # -,?3Ya~.sn B]3[K#I'xCŜ~> ?#yoN>dN^%&.*t^\o|4o/WkB"45d>:6)7_jf$.76rEq3wv,OMqK2\kmjz[uiƦ9%^N(ݦյrRV4k/9kPm'!rSGm)sYML k -endstream -endobj -129 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 128 0 R -/Resources 4 0 R -/Annots [ 130 0 R 131 0 R 132 0 R 133 0 R 134 0 R 135 0 R 136 0 R 137 0 R 138 0 R 139 0 R 140 0 R 141 0 R 142 0 R 143 0 R 144 0 R 145 0 R 146 0 R 147 0 R 148 0 R 149 0 R 150 0 R 151 0 R 152 0 R 153 0 R 154 0 R 155 0 R 156 0 R 157 0 R 158 0 R 159 0 R 160 0 R 161 0 R 162 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -130 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-28) ->> -endobj -131 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-29) ->> -endobj -132 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-30) ->> -endobj -133 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-31) ->> -endobj -134 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-32) ->> -endobj -135 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-33) ->> -endobj -136 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-34) ->> -endobj -137 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-35) ->> -endobj -138 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-36) ->> -endobj -139 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-37) ->> -endobj -140 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-38) ->> -endobj -141 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-39) ->> -endobj -142 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-40) ->> -endobj -143 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-41) ->> -endobj -144 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-42) ->> -endobj -145 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-43) ->> -endobj -146 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-44) ->> -endobj -147 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-45) ->> -endobj -148 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-46) ->> -endobj -149 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-47) ->> -endobj -150 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-48) ->> -endobj -151 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-49) ->> -endobj -152 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-50) ->> -endobj -153 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-51) ->> -endobj -154 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-52) ->> -endobj -155 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-53) ->> -endobj -156 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-54) ->> -endobj -157 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-55) ->> -endobj -158 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-56) ->> -endobj -159 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-57) ->> -endobj -160 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-58) ->> -endobj -161 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-59) ->> -endobj -162 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-60) ->> -endobj -163 0 obj -<< -/Filter /FlateDecode -/Length 4897 ->> -stream -x]]ܸ}_!Y/`0Cd`Y`ߵ,aRժ;cӪb%H$w?ɹ痟OI⿩`RS8;WbE@ɤ|:싿wmٛRwOb2)d*PYG*QQEgph*{ު}VTn'G[U>9TpÕykU &ѣ\|Qu :#21 Nc Y1| :MKpV4]/ɪ:s"MGE ЕU|:MWȄU]攷:o j:L6IaDbRtD/t_4x"PY^F7Yr.:GbS(#/iS2\0x׳(ch - z8_@`Γ8K4.]W0)cle\.Quݧq -[q1 xi\Ϭq8`F#Ԛ|.↠q` 0g]UW-9k\%qfac3D% 9 @"ո w1 "x" "x2U_({ @aiz0Zt]kSѸ weԸ &q41))E b!Su8h\, 'ָ)T^ B }/5.\5.H!b=Vtћ@ת.C)T4.Zd z @F% t5.H`h\d\9 [D9qAѠg2ո34֒hjMV֙YHq V`JU_@d4.M,sT|e5.x5.6e4.( Ӹh$Lָ4qƥ7,֛X)PfҸ0| QT|ATq Nz"|5.(1z3k\0MD@fR 4xiԸXo"3]eř [- l= 5i7Q5 -궁" '\v-8$̙9E FtK1Q?~<}ݴSV88: 2$C8q"IZ7ILŘn˹pkLW}X)8tE6_Wba|`6c=m`v4""JQz- -a4W١mߘϧD>/߹[?ݩ1u)VuiÇimΗ#wM(?wb['?4%[\!Q.^û5r0.j%p |V.=s:g}S4+Œ`&A1Q[Gp@1ۭtwWAIo0 O{"֕0c+SWbU.+o6~0$SHнl z x=[{E.A5C^#X{8S$e: -;p5 +@ >6?,@kӹaT측9N&ERdU%kfk!F"gt\Qxr_VGf@[{ eiXl[ְl]G 9 짠ڒu%+l.8>*uAevLwh-۽6^#vv(w]U>jt2O^M5Tjud.6 -*>X%-֭RɝČ@%}&}nrGWndng?^F^/r)gV q.˗N S.";#uruq(i1+b̤[u.8uiYo|-f{I8>ޘq'i!s U%_/d;(m|z7ic=D )S2|~Gܠa,_LYWkmؓޗs 9GS39ᭌULXt>]]Lv+u#֍h>ߑ1hs. "DOU%_=ߞ䍭 NiϨgȐ]*t!K+0x.Y[֕^䧠>سe"E#o88OB-ai~[_mo( ֗i~6ǁ[@ -ֿ=Ĉ(Bϖ:6CT4i~M!i~6ǁor]ɷֽ͒'Kjk/Kjkscϒ9HW.ܪggImkۓ%ޗ% 1wi!Wܯ9EaxGw|uUbƒ hDŽjQ}| ںUV̊-\I./Yux/Pq`KA`K+%Bd=0uG0eꨟO\#(cE-;e{-~=X#b?m;z]^ KR0vY)ԟ>ԫP̈́>z$ؽTaV,Wo^Ulh>͕.'rXa -mW"ױֲ,!lMe}jZJ[XTum2*Mj!Iwk]E.\ĭ\I-7-JT^LKmŕ[+filvcRG6wI؈_O!)6TB.xY/ *1ȿM*3p %R&^7R/uXk6R;پ\Jy!VJ5Y'O'$c-v uM,Vۧqe/ TCJP U]λc^Z;@N󷝷|L_VmRY'\),F_'q$z?A͸/iSGr>ZrE?> -endobj -165 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-61) ->> -endobj -166 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-62) ->> -endobj -167 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-63) ->> -endobj -168 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-64) ->> -endobj -169 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-65) ->> -endobj -170 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-66) ->> -endobj -171 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-67) ->> -endobj -172 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-68) ->> -endobj -173 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-69) ->> -endobj -174 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-70) ->> -endobj -175 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-71) ->> -endobj -176 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-72) ->> -endobj -177 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-73) ->> -endobj -178 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-74) ->> -endobj -179 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-75) ->> -endobj -180 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-76) ->> -endobj -181 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-77) ->> -endobj -182 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-78) ->> -endobj -183 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-79) ->> -endobj -184 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-80) ->> -endobj -185 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-81) ->> -endobj -186 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-82) ->> -endobj -187 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-83) ->> -endobj -188 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-84) ->> -endobj -189 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-85) ->> -endobj -190 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-86) ->> -endobj -191 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-87) ->> -endobj -192 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-88) ->> -endobj -193 0 obj -<< -/Filter /FlateDecode -/Length 5033 ->> -stream -x]ߏ8n~X$R>,pl䡧s7^˒eUVAw)QE#)*wï\Ro/֤`or27!P2_˾p5zSJ.\1SA)*(LJ>D(:[,E+!}Q\rЊ { 1}Q>9֊ +!)EBU e&`"=jeޙ/jYBK^+#21 N++&VƐ%봲YcZdaI+"Y H+KctR! +eF봲B&̬ٜ`B&Zs&6I-ÌbR)ñ$ :yY8jH@0fZY! *hX@Y<eXe[e뢆VRaraJESb' K!z K%vVS-,0` \& K& i5,V 0jX[1>gaw}aw} P˒$ nA]װ}԰b?Va=3'ɂi[αT;nc/p׿$A/P7L1DIB"EHXDHbrmZdH,2;3ӝq/2UQe}d/ot- ȱN'Y>BRt$@D-*^QU?]0o+ޜ1^?v/_gt?֥lX! ~nug4ҚC ڵrZ&s>׺~"#؆0-8@n`<0P@ty{;im9F ?01wqdfM#֎d3}dӿ΃^h!R؁%w^`BRpMg? -JcDyJ ?S,GF4s#|Ќ@Ѫ=$|YcdT~vCf`;P12ul`܋sPG 9Qʼjmw ,"ˑV#9%yO[u2d`7qS7`p>6`v#V'3,a"6'!༬ے;2Mʑp -Ũvlb "GLl1=#_iWWUHu9|_dr%/ -fwyZ  @m.qݍG#9yfs"rbB"GY1Rm GҪimN׼l$q6uh.N/!t ȝtk{K&e|tAr4Vv}Yy[ehT၇յ븉bZ2=s˓ʸ<** :) y@>V~)Ǐl3]ݗ絝wr=;˝Qq?cɯ_$IG+-wdc<1_Ԯd -|(IuDNW>ʽ匼Fr1S1X^NNԈ2sfq۸5 ALEYBEEuǎ06"FAJD4Xcر-Ok{z50pHBsWUz*Dtel \@Xp<*j3x7r,PEސ$;oc%y6 #x 놴}<]6tF3'NK9PpG)XΣ,ݬ74S` Zwgx(ɉ dyN3y:9Xw -~~{GEnִ$w1u.rW*EN yΣmK9uǥ^AM%˝k} ɴ7?mFql{(=qNtb9HWl|LAd %A@NxB>\?9vއ(Ii3>vcVn'c,Q`m|mG}+$ze8 ydsqLVlZun>WsKR~oKwaa /_98}|Up9O0sβVN.e_? X#zdd_@*ԻPUvo+DpF'[$7@R64_& -p4 uCl\aO]w Yu}XAlC:׺>u|D|[RT_mQ'TiPk6pӓBz(lmZViMNEs5$nJ^/j4Z:(SnЦ1I*#59-vw׋ltۑ.!)Â6TԵ.PSCYirAEhTAfR\-l P܎Sj6ۏV/j[Q!TxɮY]# iXm-LmE^ m:3]ȱa[ONMNnv;ɱ,k' YrViuE0B^`m"I^PIy/Ī|gE-Ο|6 [Wޓ7A|Q%i=w]^j ͏{5/vZ5u'e ;ou#_7ooToN^T㵫Toy)%_&q%UR#.FquXVbAWI_EF%-eپJav}e%"7}9 Sۍ N2/ϡ=:yjmQ79XB ^]6Q6W}\iNhpb2řtYb~C6JՕvk(朖KKf{F&Uھo^] ^Kdj.{ܹlVZpy)!,_8wKO<^دl5'0MNS 帠k~&[zn%nEg7veTQ$T:uǭ6?ܦ -endstream -endobj -194 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 193 0 R -/Resources 4 0 R -/Annots [ 195 0 R 196 0 R 197 0 R 198 0 R 199 0 R 200 0 R 201 0 R 202 0 R 203 0 R 204 0 R 205 0 R 206 0 R 207 0 R 208 0 R 209 0 R 210 0 R 211 0 R 212 0 R 213 0 R 214 0 R 215 0 R 216 0 R 217 0 R 218 0 R 219 0 R 220 0 R 221 0 R 222 0 R 223 0 R 224 0 R 225 0 R 226 0 R 227 0 R 228 0 R 229 0 R 230 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -195 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-89) ->> -endobj -196 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-90) ->> -endobj -197 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-91) ->> -endobj -198 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-92) ->> -endobj -199 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-93) ->> -endobj -200 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-94) ->> -endobj -201 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-95) ->> -endobj -202 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-96) ->> -endobj -203 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-97) ->> -endobj -204 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-98) ->> -endobj -205 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-99) ->> -endobj -206 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-100) ->> -endobj -207 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-101) ->> -endobj -208 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-102) ->> -endobj -209 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-103) ->> -endobj -210 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-104) ->> -endobj -211 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-105) ->> -endobj -212 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-106) ->> -endobj -213 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-107) ->> -endobj -214 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-108) ->> -endobj -215 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-109) ->> -endobj -216 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-110) ->> -endobj -217 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-111) ->> -endobj -218 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-112) ->> -endobj -219 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-113) ->> -endobj -220 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-114) ->> -endobj -221 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-115) ->> -endobj -222 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-116) ->> -endobj -223 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-117) ->> -endobj -224 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-118) ->> -endobj -225 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-119) ->> -endobj -226 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-120) ->> -endobj -227 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-121) ->> -endobj -228 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-122) ->> -endobj -229 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-123) ->> -endobj -230 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-124) ->> -endobj -231 0 obj -<< -/Filter /FlateDecode -/Length 4460 ->> -stream -x]M$ sI}Fr0p9^8C~K*U5fW3Zx;e \r`U|`˙b2X)8^x\ɀkW ‚ K4\b‚\! L"W At ‚BѠ --,F.x5,INCE `&4&&,,~4َ A4AbaA)fB,,|3[XP=dAgaAila`<-, $vfGϰIlaA<Ȃv LB tx P jJo f DDoN 79]܍d񀻈L@=7fg6hY攁[es|5G2' &2˒YU07 <\aeiJ>d} -D=Xb?}?N~5͔ϒ4j"Tn(:(5uT\!`qtS!n k!LO&})-뼕 C4k& bA=M`[Hi,P+)v zY f42C/Kӧ__s݇_~g|sK|2OϘFϭg=wF~.:MD@AJAC/6!PxzI>o ->L=@ %?P:u$,RGSED3UI=sy$v鎚(vVL!}5s5!"aoc1>-ߵf!~V7߭2F[QW>4:Ǻnܟ]vj:a9ӹvj/ Yc*Уqj́ δ;q3H_)PWA67Gڨ{ln7}U4!Hqv}u3HhGsP;FKL" :r䙞.x̰T˧ u:<igX׳t|#eTHH%G%S**h{cAl#qݬo`=ڴVλMs19AHiFiۯ{J?-Hw%ѴW!;G! .,~{+rQo.yH!G!Q'g2`XIET؞;.:O_T*= -w9Ng|%M8}&jʇvh6]ն+^Kæ2u9n4oܖD{nx\K')h+:bľ:u.ӷ?F:pkraO 0Ի5PnD\Z08&Myg㨙ຘJsk|6YjtRnW8j=ʇ4}}t|fU;9|u;.%n,RSɐr[۩ _Mh_RDŽ|0Ӧ0;hag Fݘ mmRƧO&R͐ TO/sEDgA6 }/( -(qOFݸddXoHU;GU xbU -d{.O7n_o[(!!9R~AzRtOx:Q諾V*ݲfݺ#ay9Lw';ߧ$$"Ұ(4%v°?oDzwrDo&)$Lޭ`;gpGKSR6QF -;G QfDZ-d2٨@7Ag[`i:QKQGW.0յP MAn1:u? !IkO1M}3Y8*ӝ~IpYHRngtwT̥ѢM nip;gp(p[7Y0j(ܬGpBTΤe_㨅u'q׎C\s47nKB}-KjHGXIJ>zf_=*4-w6[}]۠3(ecݾW8WtYfd^q7^[iݻ-{^ubj. BT=N-qºC.o d48 G -Z%cgtmT\ k yuбtonl+fe+Y'ğ-"C xW㨸>.=-jܙ\z4Sqjquӝӑ!K}+ -r%^|?4k7yh_BͥuL<'Sy/A3ٖ&j:ARv讐sc -tu貁kOAǚd?+GoBv 9"/rn0 ]ȩcH]Av1߈Oc-Y~i7Y价[n6 - yܬ0Yirsđ4M1Z -I_.~|G غ"LO/;zx#v$/Plj_ ACĸ@>t)3iӋ=Y6G5p1>.%&qEPcnXVboһ^Q.0B/yfǦmzB`/Ɔ%7+y _m^XȩYR;wHx6˴>.=9i,.1:PRm.ǛJnE |s)ZLO\^=X?=GNVUYmy-q8t~)cbXSe)ɍv}oY߻y/UWklRg3{`j?ӌF(ˑp2Oŗ!mg)Njܟhs㝠'>{;`njxjxu1љ;2k_E --E>S> -endobj -233 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-125) ->> -endobj -234 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-126) ->> -endobj -235 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-127) ->> -endobj -236 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-128) ->> -endobj -237 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-129) ->> -endobj -238 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-130) ->> -endobj -239 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-131) ->> -endobj -240 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-132) ->> -endobj -241 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-133) ->> -endobj -242 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-134) ->> -endobj -243 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-135) ->> -endobj -244 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-136) ->> -endobj -245 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-137) ->> -endobj -246 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-138) ->> -endobj -247 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-139) ->> -endobj -248 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-140) ->> -endobj -249 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-141) ->> -endobj -250 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-142) ->> -endobj -251 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-143) ->> -endobj -252 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-144) ->> -endobj -253 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-145) ->> -endobj -254 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-146) ->> -endobj -255 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-147) ->> -endobj -256 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-148) ->> -endobj -257 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-149) ->> -endobj -258 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-150) ->> -endobj -259 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-151) ->> -endobj -260 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-152) ->> -endobj -261 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-153) ->> -endobj -262 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-154) ->> -endobj -263 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-155) ->> -endobj -264 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-156) ->> -endobj -265 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-157) ->> -endobj -266 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-158) ->> -endobj -267 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-159) ->> -endobj -268 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-160) ->> -endobj -269 0 obj -<< -/Filter /FlateDecode -/Length 4166 ->> -stream -x]o$ ~߿b DDJ"A)-pKP -\gW.7N0hk)pH_G/~ 'RKçw%y|-%6 ;t KfIOJJM..⏇?mpC:AYLH)> -dRrĔ VXłpkV\%Y,1A\]*Ĉ%łb!zo ghBrJ/j -xDGrᐂū.1dI K -A&)/CMdRjuɃ,>`*TUE\"oBp mL< -FEȒ}&$da|[`C-,H@-p7-,H] 4XXkU‚,E ;/@WR`l' Dc %@$j)@装ho ,,,>; -,罅5/5 *yH 5,T, !Ƀ,$@'!KlaAYMaMD搀hYn@&Ed-,MDVn >#ЛзC؋ުc99h1YJ6G Э9l -NOUFs(3KV#9Z(v×oo&I]$Vp1 BEBxOUX<c"Cb9 Yތ"S0e[y-Y=2 -0'X^c//A d;z=o -7:?4B/ћ3ͧ×Ok<~W_gf9MS.h7 ߏo9V^2U06&rI~ K Dȅ.K4h]UyG.eΈZID1 NG^9Lyl&86z/~e:1O7)uL/Dduϫ~~T_t=U_ohU}t7iz0qx6(fV$tH\%Z"m8Ue7&:QMC'<"] ع*Q,2Noju0#?ک*Q@萝LrV]FD‘od(RBS[E:%]8s~xŦ~ x6Y\g8Eu2fFԝ1o/Zl=f8 <OO#|}7lCɞdC%vMPh_.aHq~LI"bq{cc&F#>M*\Ͱ{I^e^Iw t~.MNL{O65cFx@ cGIIeϽR:>Ӟ -== tu CH;Yg?U&n͋1\4ue mOCv]HU-OُIF1;}* ~AO I\,H\72[:c#=s6Z5Yg?QԞ^yYp-Hx{L'`/3kepdݘxH_u60)іg-Y4zRsh\JW! =7{,m9n[ ,k4L/yI_XO2!$/y-OUُ"rTlmyAcF/sULEJʝ-V~fkg K+XGf}_)~8506H=ƵF&g=Szz{.[NK|BB2⧞ˤY<Y>|uχ|^*zЍS/'u'MaQP8>Qs9s/u>U:c8!)Γ YG%/ɏ=O 28IVҙ \zY珵ߜRS{Z5=AەӃ "jpMַ.z&8:_.JMfXvZ&Yg+Wb&q+Yw vGՅl,9#>X>T= ݪi7NAکn'p0_vkt:s"JkHV =r绥nKZ6ͯM+ޠ-::S2;qKjfk$kWćA"?R1J+|jMo$pN tNTNUY>MJOZևovVI#=waKZvPW(Q_AQ^AP Rx -R<[]'+5t ǭԛㆼʙ&SJ;Grzn1۽~"Jީ#R;TZ.9oλjߋߣ䬮@ڹ@ʍyh(:\߱4ZSbjb8j:VJLUUYozD=Jcs.d%ŠvZټ}vmk*H^#SVKW%¿{|Tb*վ t9/9CX-,NjC> -endobj -271 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-161) ->> -endobj -272 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-162) ->> -endobj -273 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-163) ->> -endobj -274 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-164) ->> -endobj -275 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-165) ->> -endobj -276 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-166) ->> -endobj -277 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-167) ->> -endobj -278 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-168) ->> -endobj -279 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-169) ->> -endobj -280 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-170) ->> -endobj -281 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-171) ->> -endobj -282 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-172) ->> -endobj -283 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-173) ->> -endobj -284 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-174) ->> -endobj -285 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-175) ->> -endobj -286 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-176) ->> -endobj -287 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-177) ->> -endobj -288 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-178) ->> -endobj -289 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-179) ->> -endobj -290 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-180) ->> -endobj -291 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-181) ->> -endobj -292 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-182) ->> -endobj -293 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-183) ->> -endobj -294 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-184) ->> -endobj -295 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-185) ->> -endobj -296 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-186) ->> -endobj -297 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-187) ->> -endobj -298 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-188) ->> -endobj -299 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-189) ->> -endobj -300 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-190) ->> -endobj -301 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-191) ->> -endobj -302 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-192) ->> -endobj -303 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-193) ->> -endobj -304 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-194) ->> -endobj -305 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-195) ->> -endobj -306 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-196) ->> -endobj -307 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-197) ->> -endobj -308 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-198) ->> -endobj -309 0 obj -<< -/Filter /FlateDecode -/Length 4937 ->> -stream -x]M丑篨I?6fn졧I(bRY7&ErRp&!) rИaII0d$aZi0D;GVH3^4zҬQ!eŴ4FBt)-OR->k#ysZJ-Rl@ZL-6E"lh,%t%1 蠍I2tiL+f&iQ4 [YL-8bJh1-+¸E++Bw1Q LfT+qL-wZޅ%. q7e4+esJx.hJ\YX&Ӣ cJ\޳=1 PA0*mRxW:f xM BdM@/J\S9 qAipĴp%.`N8*SND [Z -p$.G-p[)J\&S);'qAZUJ VL F0 KA/q^$q@q [0T$.Tg.'[xH3Fda A M234bI44ǙIbWQ D`J1 &$.@p%.@`a[; Rn& R-V[ M7Yx|dƑ$ěI\qf FOǛQ`"8MY$ě`')-97p3o£ǛQ\. fL@ V5Ggrb3+1K܋*k1h3Y `ZEⲁs'W%8D̙)Mf -}!}}&ߗ7elk~rkCft7J:ڨ"tB6"f->HLŘnKŬMl3S"R0* -uβz1>y+PG'e3"rQ̝z[e Q}^vvc6wh\_>|{T}g}xڽ]=~#Ҽ}Vgvˇúw;\0z4ʻhoDp̵O]>űM)l"u'4D?MUZz^@[sΘ0ץ'4r^ Mak6T\{/78; G&ӹN"^CSIfGCmG˝"~m -v3tv78PɯIS\vly*mn@ҁCEb3#rht\2T JXfӐv3w-\_42نmem~K^.x(&m&֧pZv~ iiQyI,pP5H /}nrVZF`5E8E`#dN,Թ,fd1 Ui`) -MyrkπLqg`R0&f+2< 0ls:ׁEvL -5v,FYy _EWa%4?}&w>+F퉶v0P%=H)`63oR:I5p* -te~yaړ{Γ͏7 *%P՜e@#.E;պЏ_Ͳk7Ҩ} Jqg=I@ c&τҪwdFcC⽪ABba4"g0ӹ =9 U_ C&p\O0d˟{q+~.⌠=ndo@M<ᒑp'uOF\V,nд;hvG=@1jx qt.(&X6=bPB>u1wQFF唴r3I@_I'CsUh\vo i~}įs" -3ז=9t :gi :V7@2h=Wo&u4>@g~D --@k*nF`im6j=@e>Z矿N\PAu$.]Z:>GȎǞ -;P &|\٦> I@u̙ܵ.tDwVOۚa~cR:J&u0~ 73ү = m`ُ K+֛~ciYj};j=`M0ۤuE)h]x;}D5!ClC݇m>lo)L\`Ok>D -Po5y.0j{. |%?sXrN!j]aX!B-hyQ{&Dh!\ ggܤuIpt& WNg mEl9 6oԞު'iݜu@@tsVuW [n>QpLykf6\Թf(rB~Orw…#¨},\dʙ¤e5t8sCѺY}M0x$\ ʄDTN>݅դu`E&XmDB H,e!Jll.h=g(l(hIe؜݁ G:ׁtB?~ͧN֡cG66 {@Odٷ&uogiU! -;Z_8)l⨚-m;>֨}},A=O|ëIk"GR5-9JP?J*`?>-F". -Y`)b629Pkow 2[?'q;>:vdXHNH%Sz ⑏~9e?>ޏI,yIAy&?p׭o4Bh|gDgN2'>=۔2/_,o!BQxt7>Kyrۊn-'^I1 Zou^zQmNJ?~͵p˯/w~QS励{XB3QwO!$U a+y[M#&Pw51\jzt%]w _o7QMZZZ"Ψ\~Y;~D7A^樠w_ $W% zSJM5/-LiPT^6zH##_=Nn |!棐7~^/*NIcZ -Cs*|2_oV *^7R/u Rcl^&i!?n][l%횬Ǽ$Uc-6uUO^#P] -巕PVLw_mP?Rv_ebs[1C?-41TV a &n4VhO˗_ f_oe- ˿ͽa}ܺ3I2M˒Nh]GMlR4yڎ]S׍ؗ2з6ĶBZ_7X6a/i9^Ϙ,Vᢿ\FmJ~gmS:Rqˮ,[ɀ+M+.:7/6E/r]_6VV^#09,#ګci%> -endobj -311 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-199) ->> -endobj -312 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-200) ->> -endobj -313 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-201) ->> -endobj -314 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-202) ->> -endobj -315 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-203) ->> -endobj -316 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-204) ->> -endobj -317 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-205) ->> -endobj -318 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-206) ->> -endobj -319 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-207) ->> -endobj -320 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-208) ->> -endobj -321 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-209) ->> -endobj -322 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-210) ->> -endobj -323 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-211) ->> -endobj -324 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-212) ->> -endobj -325 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-213) ->> -endobj -326 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-214) ->> -endobj -327 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-215) ->> -endobj -328 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-216) ->> -endobj -329 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-217) ->> -endobj -330 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-218) ->> -endobj -331 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-219) ->> -endobj -332 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-220) ->> -endobj -333 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-221) ->> -endobj -334 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-222) ->> -endobj -335 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-223) ->> -endobj -336 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-224) ->> -endobj -337 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-225) ->> -endobj -338 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-226) ->> -endobj -339 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-227) ->> -endobj -340 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-228) ->> -endobj -341 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-229) ->> -endobj -342 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-230) ->> -endobj -343 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-231) ->> -endobj -344 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-232) ->> -endobj -345 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-233) ->> -endobj -346 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-234) ->> -endobj -347 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-235) ->> -endobj -348 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-236) ->> -endobj -349 0 obj -<< -/Filter /FlateDecode -/Length 4965 ->> -stream -x]ˮWڀi'`xa$p# :E~?"Ej ϴHY"OUd>7+9R1/_/ZETbu1e&䯿pE1\_/ks2jU#g9R1Ũ YޫBV0 -5|tYj5IJP\4geaqR0G!habΑW'ļ CJyAb^BLJK@ 'qASE",%Dl}:vS8@ +X~F&Tvpc^RՈ~170"s8pD @U`0f_v*`~x0xq0-LK !@"AK;»9chc ~Ds2B-D6–, U2½BxoÁz$8lt9.>Șy eY}>؆|h 1s6 J14CI@!QLn1Rw.z(:j2@4&sEaY[D2ɏ^y81,RN7 -]u{QRގ#2~ϻ?puT5V7oeNh/=.K@oGD2RS~3􏋈vDDH˝RRAçx'=Әi;Z)j>:<0+}߂EZ)fzQ.[c{oYGkI~~dxyi& U[ƹu&=>[S֑^^c/ (#AѲa@ɜP<{ 3}_+#Xx=1i1^k:w/Uŏvсs2 !3t[0sumV'}X^xxUAr9 %x֕k҆궩>]G^ͣ?!etl2?.UTV7.l6Qz}l6Qz]P:dqvцG+ۃ2@T\U5qUriE\*a̯k81#.k#.BԪ{wd!?{my ɯЙ"$WN$9|qgjUik"c#q_ہCyw9K;+,T0 ʜpNULko7(`q9iކs|vV[tǰ9%6sm;DȪ}y͌^;X `1 UZMo|pU銾gWs.ȹ^عhA~(|Q߃2 ?дq[\hVcW?W -A~&Jv|xPmV}{̢}n<@ JKe2O_1ʜBizRE Ncxa"AY+N&14>D2"b -eһls #'{c':8~e6dL{ >*ï̐y C쳪t׽'7j=N pz=`l3+lpɜ:YSNgKXW~k6\};G W/}p ;`&+,` ʜLuLgiUa0}֐yP^^ 3:lA̳uOU0q:|W/}.A~Pl"rt)oP7:qYk^faø۳arUVF>È(}kEtNҫټ7X(]P̽_ǷZzK#O[CQ=Xzvp*G Sqt_ڏ; i2faPsߴ7_/azCif>YqWLn3uޑ>>k-#I'*xvb.4P\8 -{d@߾d~6rB2< ;̉O]SATy[\+'_~Z_}w:rؽ5,$B2>mN7%EU5qеe -ɼ$>Q7-R֟9mיfKYK|Yڦ՗RU]ZIF\S})Yq^.BTroFߝKLH˥r͵:RJh.=@Rx!m959\'2}.§׋Bipzm"5,1,iqF2L?,WK#<7kPYI=5]*ꎱb/PI=JmI$Ucl*j2SXʕm.J%W(=}^ƂikKr&:?Q6//asd~*,ɼXSk@ -KBSrasd}|̜%oe dFdCo/my͎[]Vn]%x%N&Ѻdqkv^4AMm҇Mе;/^`..eZh1צJ\qŤ#Fml̋f+5m#Yq[EF%-yn1m%m\`j/ڊi+}<~*28R{M}mSqj%<9˰62yuQ3:9X\ h1ڤEl.F]I[5Z E VkE0n8OoGvoG%tebD-rwz)Y}$V$mnXksnQ$,^|WMs٬HʟiEä30D4}OX!? ]j8y+eͣm á -8|5ZǺ[:’Bs[љ> 慝z9T/;?`xZ>(5 -endstream -endobj -350 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 349 0 R -/Resources 4 0 R -/Annots [ 351 0 R 352 0 R 353 0 R 354 0 R 355 0 R 356 0 R 357 0 R 358 0 R 359 0 R 360 0 R 361 0 R 362 0 R 363 0 R 364 0 R 365 0 R 366 0 R 367 0 R 368 0 R 369 0 R 370 0 R 371 0 R 372 0 R 373 0 R 374 0 R 375 0 R 376 0 R 377 0 R 378 0 R 379 0 R 380 0 R 381 0 R 382 0 R 383 0 R 384 0 R 385 0 R 386 0 R 387 0 R 388 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -351 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-237) ->> -endobj -352 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-238) ->> -endobj -353 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-239) ->> -endobj -354 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-240) ->> -endobj -355 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-241) ->> -endobj -356 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-242) ->> -endobj -357 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-243) ->> -endobj -358 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-244) ->> -endobj -359 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-245) ->> -endobj -360 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-246) ->> -endobj -361 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-247) ->> -endobj -362 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-248) ->> -endobj -363 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-249) ->> -endobj -364 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-250) ->> -endobj -365 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-251) ->> -endobj -366 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-252) ->> -endobj -367 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-253) ->> -endobj -368 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-254) ->> -endobj -369 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-255) ->> -endobj -370 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-256) ->> -endobj -371 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-257) ->> -endobj -372 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-258) ->> -endobj -373 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-259) ->> -endobj -374 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-260) ->> -endobj -375 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-261) ->> -endobj -376 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-262) ->> -endobj -377 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-263) ->> -endobj -378 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-264) ->> -endobj -379 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-265) ->> -endobj -380 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-266) ->> -endobj -381 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-267) ->> -endobj -382 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-268) ->> -endobj -383 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-269) ->> -endobj -384 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-270) ->> -endobj -385 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-271) ->> -endobj -386 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-272) ->> -endobj -387 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-273) ->> -endobj -388 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-274) ->> -endobj -389 0 obj -<< -/Filter /FlateDecode -/Length 5119 ->> -stream -x]]䶑}_,HE d3bLg&Ap'{J-~HnpiYd<<")=|cN9E:_~<)9Ml )9)R) ,iI0搔$k`uƨi0y0E4zҜ"gմ4`<ki[B6VK %X"򜴴[|FM-lqh1lXM-&e?DjZF4g{Y;`ӫiQ褘4[ YM-yB'fe:x\"5 5p5 -4p)Mi$O 85p9Lsx4g5"x [#WM->dи{k\h\AdոoبqLqzqJYN DqzqzFzM5 'ok\@]oMҸFNF 1 ؐu S&Aqw]-h37x4. #5.P&Q.($lj\ik\&D޵ӟ2V5.]>5-O6ŕqVlYD5.]'k\0: xzZx׺l4.] Aap4.6Yiy2Y-9 0 O$jZ$qx2C5.]LY5{ "x5 xvA2NƁ)4a- kLDL$ ^Ӹ 2M9qAipԴ8:h\ Jq)$[s$[2h\`޷ESԸL6q&Ҹ x E7q]i44.H&LVRck\]Ҹf ͒)  0Mkiָ.Ҭոl7q;FK42gLqWQ D`J5 &4.@H4.@`a[| q3lqi\lJ4.Ӹ 8qhih\-#tqƥěqA&B^1VeJ1>LuE7]yJՊJ_gnyYEReun1?>a"+4.0ʘlD ʜ1T#X*tr{ZY.@QNyE [l(6ge s"FO'i]=RlY܂^es$V2lŲcy>1mk} .M.]웯;~c:?Ɓ3yl]܈B:RS`Xanu >c_F۔*ePnܗRGͼk2-s1ׁdMAK\CUt36=yEk?)w8XBlXo%hg#lHedu lSޒ0dbSimV1>:]Lc|]蓻<@ɞU"5QzPu`&{߲Yτ٪zhn]'|Vo`\{\iEzs6sb"ֆT^j s` -> OHׅu<)#-'k8[Eqqylxc:/9%S6ckϊڸ_y88:4vrv̒Gx:e;iO օ]ot/+F^pƓ\1RGŗlf-?MҴ̓ҬߙRɺݔQu^AvngsU Ϻ`]X.Hկ˯6F^-Op0&g}PZ$@6pڮ=Kֶ=NkK=VGő]0ֵ+/K?Ͷ1{λG;ܥ޸i*Y_=}e"\Օ䀽zr>"9^&Of>'n fv+b[ٱoKZ,.h -nauL:/ fxe\Q\pQҎSNw8 6r|tKjPnvn8*`F4Rf^^CQo(> t1XiN˶R`G$g8C40c:4 I?HoyfhG0r}Qrbw;J*wkV9@{V'4JK2!k|wk9l|{'˵5un~ a SG\Y^q4 t^gVcjӯwvk n5&Ƶn l| 6:x`،EvrfbCc:/$[VZȚ#GfP,6|<ڔl}4iB{-%a似(0q:Dٜ2Y^KqNj?{V>^{r5w$I}3A9:Z-Qj7mdIȩhcj?a'ObY&yɆ'7.y -8 DiAt^~8\iu礜qhȯH^q b -ZPօ>bvmCw_#Gڏ?4,KqGT^`^ch8S^{-h* rc$t[vKCR点$7މbb4 cR`T}0E66.xqyC/ -K&7C@cvaY+xv֦EfLuP5j֛g p>:+7Ү}DG5)\7=0˃'ygS˃:ws=8zbџK&_ݙ@n ̑`4赝kD-vVj/|py@f#/hS_Zƥfꁷz;D(6!)lG#""#;jO*L[ce~n]= Z$eᓞ"WvR_,^~o֪v<\^59/<n0Y;U_uOM93ˁI^phjYd"Ҕ9}r#X׏cEMFxJ{XB3ڽXLv*䗫XM*lRŲ؄a/4]uM,+F%ss}ٮK^'PJT̽UZי*QJCY;j?)I~cJфά]+qB.@/|rR-S⦚K7S=׆WdI$Ӎǵ8J6턗S:;40@*fҤ|YdBQ{P<KRRv*YF屲i- nIQvJ}{aV ܵVҮ:y+{)F&o+q3ԡL,ır[/Nǭ[0_ybXϥ& -|jeRhFoNmi3<9[‚[!Pސ{ǝl*L&_oÃb"æ:h-u|MM4b/9meP[S{ahm؉]kpGxٴbud~jߴ zIh V.Vᢿ\rKmJ>wEJ):E\ⲫ07Vf - JjӋw!Qfl. \`_++{=~r/&2DZJzi1Vӥ~:9,P-wcW' Zh'妶d}TdJDQ2SdTlZiYmT}&[ҡڈ+zK:@sjwgZK"vRl_7. j晚v9;UZ3hXnD-u\qw8Fp7$nakׄ{|nqBWT2H]M[z%FsoNL*\DXug^jɫB -endstream -endobj -390 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 389 0 R -/Resources 4 0 R -/Annots [ 391 0 R 392 0 R 393 0 R 394 0 R 395 0 R 396 0 R 397 0 R 398 0 R 399 0 R 400 0 R 401 0 R 402 0 R 403 0 R 404 0 R 405 0 R 406 0 R 407 0 R 408 0 R 409 0 R 410 0 R 411 0 R 412 0 R 413 0 R 414 0 R 415 0 R 416 0 R 417 0 R 418 0 R 419 0 R 420 0 R 421 0 R 422 0 R 423 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -391 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-275) ->> -endobj -392 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-276) ->> -endobj -393 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-277) ->> -endobj -394 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-278) ->> -endobj -395 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-279) ->> -endobj -396 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-280) ->> -endobj -397 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-281) ->> -endobj -398 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-282) ->> -endobj -399 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-283) ->> -endobj -400 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-284) ->> -endobj -401 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-285) ->> -endobj -402 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-286) ->> -endobj -403 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-287) ->> -endobj -404 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-288) ->> -endobj -405 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 443.811778 177.650223 428.811778 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/installation) ->> ->> -endobj -406 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 415.114756 101.433071 396.364756 ] -/BS << -/W 0 ->> -/Dest (cb10-1) ->> -endobj -407 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 396.167735 99.933071 377.417735 ] -/BS << -/W 0 ->> -/Dest (cb10-2) ->> -endobj -408 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 377.220714 99.933071 358.470714 ] -/BS << -/W 0 ->> -/Dest (cb10-3) ->> -endobj -409 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 358.273692 99.933071 339.523692 ] -/BS << -/W 0 ->> -/Dest (cb10-4) ->> -endobj -410 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 339.326671 99.933071 320.576671 ] -/BS << -/W 0 ->> -/Dest (cb10-5) ->> -endobj -411 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 320.379649 99.933071 301.629649 ] -/BS << -/W 0 ->> -/Dest (cb10-6) ->> -endobj -412 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 301.432628 99.933071 282.682628 ] -/BS << -/W 0 ->> -/Dest (cb10-7) ->> -endobj -413 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 282.485606 99.933071 263.735606 ] -/BS << -/W 0 ->> -/Dest (cb10-8) ->> -endobj -414 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 263.538585 99.933071 244.788585 ] -/BS << -/W 0 ->> -/Dest (cb10-9) ->> -endobj -415 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 244.591563 99.933071 225.841563 ] -/BS << -/W 0 ->> -/Dest (cb10-10) ->> -endobj -416 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 225.644542 99.933071 206.894542 ] -/BS << -/W 0 ->> -/Dest (cb10-11) ->> -endobj -417 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 206.697520 99.933071 187.947520 ] -/BS << -/W 0 ->> -/Dest (cb10-12) ->> -endobj -418 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 187.750499 99.933071 169.000499 ] -/BS << -/W 0 ->> -/Dest (cb10-13) ->> -endobj -419 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 168.803477 99.933071 150.053477 ] -/BS << -/W 0 ->> -/Dest (cb10-14) ->> -endobj -420 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 149.856456 99.933071 131.106456 ] -/BS << -/W 0 ->> -/Dest (cb10-15) ->> -endobj -421 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 130.909434 99.933071 112.159434 ] -/BS << -/W 0 ->> -/Dest (cb10-16) ->> -endobj -422 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 111.962413 99.933071 93.212413 ] -/BS << -/W 0 ->> -/Dest (cb10-17) ->> -endobj -423 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 93.015391 99.933071 74.265391 ] -/BS << -/W 0 ->> -/Dest (cb10-18) ->> -endobj -424 0 obj -<< -/Filter /FlateDecode -/Length 4795 ->> -stream -x]ߏ8n~X$R>,pl407s7^磫$6V<.D'Ujɹ_/]ITbq1r2W!P2V}˿?Kw]L)٠ -X֑ -CTXb) jĞ5䠱{VіUO5p%$,pZE,3y炉31_T^%LLxCx ]BNxЅ)' E*H%;Ee*h+dB*gs[Ld5s&7IaDH1)<] EA@k<.rVFM *]l`% |Jg |&Ù>)ñ$ :Ӏ,t 5$ ]#WA*ayAϤamޢanaoٺapհ#kX@\RѰ԰IR^awհDTyaѐˤaw٤aw1F +l5,`ϖ5,`OT^2aw}-h37p5,`g5,U. $tjXcDWk<dFBE 0LR<аvа,6QyЅkXfְ gװ)ͤaAF#aqհg 0.e5,(dO7K@ [`֛@'/aAQ֛YXo"WSY֛IMwC2i<."Өa.Dd-7$g:3ˊ3 [ՔbJj|e& &V9YL`: ,o0}ST0g$7Y0,}[sh-?^~{)SV8:\:,QRmoL#<`d,ec'ڑH /ȉဘO.Dov٩ѵ^?zo?Oh$WߩQZ)pUoE2aƫF):_bW?GhLOcoKwݫ8*U;zj]d7vh׮r|cxfԍA5Zʣ+!"fK@<yn(?&r-L!{Ч2SJ_H ".ȣI?9i,1,鷡ywa>|r-nu|VgJ=QzIè6 ʜe克{nY6M.ʳB%~l]:3ƚI|)M\y`S[({c2q H]w=QЌQ7 mc۶7A@@$ -3sZiyJ^usamP<%"GZ4{(ui:7HټKNi}ཱི͊AӸYtse#/\{\$cǚo+l -*:$HCLd6$ t˃q{lԬ".4̋ΏlJ7Sj kളLfzW,v8q^S lRCTx1gP<u]?yNgztx6%Db~֣,g9aLyT1٢6mZyh2H7\[lW+چ/a;.WOo*X^r?Jh ʜ咕DvKve#/d&3/Wg۶mGBya3I!L36>8SɛM=2g]%9>v̘y&ȔryQw48|]'k:V.(f}m[LeS`4<"F$c,Ј0%y49M\Cu7&0D%)"Gz;NGɜII_}~ݶXOGE7YnE4(snD)xjMR;/Q)N^ ʜǼY:J7vͽz+VEu]:=^,yVSiYO<ޙڋ+afj^g9ce5$Dc;w=y^I{R?Ѯ +>Y6E`H<Pq G*弥wP<]eqyeJ$s.9MOięw#bGZs+b -#Ok&:,r` Snu|wy9uz:əx?; ~t e%ttFĚ}@9ٮk r+'P;<Me-;B^=|o ][Qv|q]t&qKcTQRn {wuGrZ)$+"Kx2Gq/d_/PQ|vZȲ\.rZ=+dL+~,Ge++".I*P?PFCSe3U߽5!ݖ,wol~*!VA+\,xHL [횛rQ-lbS:י3{ 5M9㵪ڻ6uJF d37;)׋B֪ &ވ:rSHܽ,Z<*SnЦ>S|I7F,ՏKr T[c1_/%mC~3VP]'RWo#g;LfY *B -L7j竹줞m;}lt벎JUO@ǒ5@Xퟆ=V%L͕YІj:wޙv,oJ|&6^smd&{f8+P3M:Z:ԏ f.4)xf#99KP _To6 [~&o^Ƀd&Jlæ#z`&< <}<kI5nO svd\;z&C|]b d6}zsYZᢿ\G|ĕtpw+e`5[)7Һ^$mu]!4xf+mB`/>Oo]XGP7[Om7&x:˸lsM[{EأCc-xqhGͳؽ@J[4Z'Jk5Sn8ZL1St:1VRoZD- -;\ŒY^Qy.Immϊ92Xؔ| -;7U@+Uq瘨%4}1CX$qR˼f6jΣo 0Ld"Ux3b^:@I0g7˨iIs$AoI֩))y>~0_ -endstream -endobj -425 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 424 0 R -/Resources 4 0 R -/Annots [ 426 0 R 427 0 R 428 0 R 429 0 R 430 0 R 431 0 R 432 0 R 433 0 R 434 0 R 435 0 R 436 0 R 437 0 R 438 0 R 439 0 R 440 0 R 441 0 R 442 0 R 443 0 R 444 0 R 445 0 R 446 0 R 447 0 R 448 0 R 449 0 R 450 0 R 451 0 R 452 0 R 453 0 R 454 0 R 455 0 R 456 0 R 457 0 R 458 0 R 459 0 R 460 0 R 461 0 R 462 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -426 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb10-19) ->> -endobj -427 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb10-20) ->> -endobj -428 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb10-21) ->> -endobj -429 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb10-22) ->> -endobj -430 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb10-23) ->> -endobj -431 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb10-24) ->> -endobj -432 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb10-25) ->> -endobj -433 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb10-26) ->> -endobj -434 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb10-27) ->> -endobj -435 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb10-28) ->> -endobj -436 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb10-29) ->> -endobj -437 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb10-30) ->> -endobj -438 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb10-31) ->> -endobj -439 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb10-32) ->> -endobj -440 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb10-33) ->> -endobj -441 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb10-34) ->> -endobj -442 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb10-35) ->> -endobj -443 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb10-36) ->> -endobj -444 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb10-37) ->> -endobj -445 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb10-38) ->> -endobj -446 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb10-39) ->> -endobj -447 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb10-40) ->> -endobj -448 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb10-41) ->> -endobj -449 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb10-42) ->> -endobj -450 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb10-43) ->> -endobj -451 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb10-44) ->> -endobj -452 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb10-45) ->> -endobj -453 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb10-46) ->> -endobj -454 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb10-47) ->> -endobj -455 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb10-48) ->> -endobj -456 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb10-49) ->> -endobj -457 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb10-50) ->> -endobj -458 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb10-51) ->> -endobj -459 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb10-52) ->> -endobj -460 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb10-53) ->> -endobj -461 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb10-54) ->> -endobj -462 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb10-55) ->> -endobj -463 0 obj -<< -/Filter /FlateDecode -/Length 4641 ->> -stream -x]Ϗ中_QH" Xx9$@l4r$x !~>,YvꞚy>iLW,Z>vg~ev&"/?~>YſbbS8;Wb矄@ɤ|~m./?uw]8듰L)٠ -X֑ -CTX+ 1[V>9XÕykU &ӣ\|Qy <#21 Nc Y1d : KpVA4^,ɪ ɂY*pb XB%kX Fd YaAqg 0.%7)P|3iXP(* h*ʸ&!:iY|a Jof f DDN d7:] Ȥ񀻈L@V-7$g:3Kƙ ꔁ[%u|%GR' &2YU0U ,`u0GQu\' ~rޔ񷼐Ϗ?ѳGWZ1~(?k!gzBce,; -. =#{E@qztF{֕蔟g]zl) Už*jFU EvdsA.㙼;6+-(&Zn|9z#UѲmGƋ2M1=L U֏|!9Rnq+"۸R$oŘJ~ckah{{=o,KUHϓD RN;;]>X8]LŒ%G9auʯLH`<,3V8u ˏvp:!!<|xs&@r1b۠cqȪwvҽw fevzH闱*wLoSݿ)H6;=sF_AQ6OBre,|rcFM#rmмYTUw_֛TlAOқmD2efUj G =sI] |VmM8Gҡ1_*;hw'!,oO8F*/D$SuXtMp\-^)a3-2:k:uwyMz u${?):r웑"lB{*sF[#G*muOm~|^OWLapMXFv6/f>kВsc>{y_sut_:|6KTۙ>o rW~TOv+޲ᶶ>eltrT@~wxq/+1 ox>?{?_t)g y|ÊTs[\ 0?y\w(ʫNv6XCݢ÷Rכ̩koۮiԝeRVyO;rȸy9y+F}a#n6\vMyɖ2-<+$ `ߘh@gLΥ0:ԗa| gq#3:zC=_V2->2Bi:uuՎ9j쮕aҺnt2e )OlSIm oeZNjl3rd2'yz5̏m26%MAHwaw:%|gu!3lVV, cgrnJYFH`4ӎ# JMEv46ɨsvuD3q~!ۚemVEBtj LT_:;5YPX L:Z:udǽqܜ%ڍ>ZroO|]=ǽmhȽ'.&* 蹃R6Tkh~yn`%]CP׸=1,}ؑ}3] -|n}phh*.e^xswK\Iť˾,d+1 FZ׋ܫ #/nuMOALEcv}e%"}9 Sۃ N2/ϡ:xjnQ rm\ rhS)jLO^J-X{:ZizěrZD- -9RŒYžvR*m^]{ ^Kdjj=cZg3{?ӌˑpl;9F`ZH)7y}vfy-Alrt^(Vo=ʔsfFg;7O$}-7˟I֩S> -endobj -465 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb10-56) ->> -endobj -466 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb10-57) ->> -endobj -467 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb10-58) ->> -endobj -468 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb10-59) ->> -endobj -469 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb10-60) ->> -endobj -470 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb10-61) ->> -endobj -471 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb10-62) ->> -endobj -472 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb10-63) ->> -endobj -473 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb10-64) ->> -endobj -474 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb10-65) ->> -endobj -475 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb10-66) ->> -endobj -476 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb10-67) ->> -endobj -477 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb10-68) ->> -endobj -478 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb10-69) ->> -endobj -479 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb10-70) ->> -endobj -480 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb10-71) ->> -endobj -481 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb10-72) ->> -endobj -482 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb10-73) ->> -endobj -483 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb10-74) ->> -endobj -484 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb10-75) ->> -endobj -485 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb10-76) ->> -endobj -486 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb10-77) ->> -endobj -487 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb10-78) ->> -endobj -488 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb10-79) ->> -endobj -489 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb10-80) ->> -endobj -490 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb10-81) ->> -endobj -491 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb10-82) ->> -endobj -492 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb10-83) ->> -endobj -493 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb10-84) ->> -endobj -494 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb10-85) ->> -endobj -495 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb10-86) ->> -endobj -496 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb10-87) ->> -endobj -497 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb10-88) ->> -endobj -498 0 obj -<< -/Filter /FlateDecode -/Length 5126 ->> -stream -x]K|_ბb,$f;6vJ-RT=z! ؝Q%ȏ_UQd6/Q)||U'l4EMɟ?E1OoqV<ӿ:lU#S1ŨPQW1Z`.1gfHEfPN^*dmp[ea!fPd40Vk h"g2U@RY,(3JeΩx#eBI*#6R-i KQ* 2bStRY-[$ʲS>'",LeV{sZ*3Fy`ӉeQ2 [Y,-i+9B+') vk#e/1 E Qfb^8ƨ([H&(QX(F'р^QQ ʬi)HL l!\ L8 [PA`%'q"qݒF%m 3R (P8pwJ\@Qu>X hQ -8#%. s` ,qQ9uFG id%.*0H\(6i6eQa: k=.A]뵕l@Q-F]PeI\)D5O`+eRxI>,+¼E/+Bw᨜ L3EȌiAk1Us7]~>}5w8# An;uFdIH1 87/e*FyтM _uæ-CNM:t Z 7У!Y:d&yaȂ{]hqے-rnXK.{Y8n[͞is}pvUON[h=b@4G6mtVbqǾ%gF @,5YXqB݀4,@Jrخʕ5r+WP綛Ofhaky c+p.sΞs/Z!h\S"oHCVУWV[P99,FWgdxG>pN#pCf6_#Ase'lU$uWB9x70J Yt<]G>n0(Vl wq;{K532Zr|kb|vOD6H&p{O !#$C9 yY2 !=7b D捛,p޵` pQ@1K=p|20 /,n&:ǁE,bWtF_zfI(5{x:s.)cxztHo"ͯ Y2J{ovq#ҁu[{ҁv7[߷H`K|_}xf@ނbqaHU9m&v@ ?%r6 چf$h@؀t2BH }ua֧s=ey=xϳbk}Z 12Ne-Yl1nݫ9e~m@*$\~. MJXǏK --Z*L S8VG1k2~xh"c$\4ioݗEyIսqZ{CwEZ🊟t;ua&듥;~-%e{[[|^?9̠{ 'j[n5Y6Xk߷9M a:ǁ$?◐>n7:`~bN+]-OUWzZhvsV0 6$٪S8, ν)[͌xaZV;jWS87/xE5: k~eI FW%Q ]ҜP~msG"PvO"0vzl3Z o7lAO0PAWzP7: >@jјg{F%ޫ;4;Dn! oetl 5\Դgm)#uōцx-|0mz=6UcNq َg.*a 0]кw&gvGqM>ϸgt6/p.)+ ʒ~_>#Or۹|1LSR:u3Y3Hkn7:{]lbY 55)Bӛwֶl߈=75XdBbm|{dg qx=&d|g:'B wl^՞7ҵ^Z~xbޭLз9_9{v0U9jˮMۺ9lN w'xKo67צY^kMT0z?EkڟB}:B+MD4 +D r7^R'|'.`XunY>49ֽKYI&&z:Gg4ysHyGھN*x,,~67y3x&S~La30??4JLr7$ GpFI*TêSGm%a2[>ky -endstream -endobj -499 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 498 0 R -/Resources 4 0 R -/Annots [ 500 0 R 501 0 R 502 0 R 503 0 R 504 0 R 505 0 R 506 0 R 507 0 R 508 0 R 509 0 R 510 0 R 511 0 R 512 0 R 513 0 R 514 0 R 515 0 R 516 0 R 517 0 R 518 0 R 519 0 R 520 0 R 521 0 R 522 0 R 523 0 R 524 0 R 525 0 R 526 0 R 527 0 R 528 0 R 529 0 R 530 0 R 531 0 R 532 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -500 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb10-89) ->> -endobj -501 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb10-90) ->> -endobj -502 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb10-91) ->> -endobj -503 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb10-92) ->> -endobj -504 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb10-93) ->> -endobj -505 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb10-94) ->> -endobj -506 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb10-95) ->> -endobj -507 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb10-96) ->> -endobj -508 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb10-97) ->> -endobj -509 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb10-98) ->> -endobj -510 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb10-99) ->> -endobj -511 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb10-100) ->> -endobj -512 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb10-101) ->> -endobj -513 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb10-102) ->> -endobj -514 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb10-103) ->> -endobj -515 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb10-104) ->> -endobj -516 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb10-105) ->> -endobj -517 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb10-106) ->> -endobj -518 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb10-107) ->> -endobj -519 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb10-108) ->> -endobj -520 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb10-109) ->> -endobj -521 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb10-110) ->> -endobj -522 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb10-111) ->> -endobj -523 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb10-112) ->> -endobj -524 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb10-113) ->> -endobj -525 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb10-114) ->> -endobj -526 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb10-115) ->> -endobj -527 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb10-116) ->> -endobj -528 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb10-117) ->> -endobj -529 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb10-118) ->> -endobj -530 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb10-119) ->> -endobj -531 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb10-120) ->> -endobj -532 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb10-121) ->> -endobj -533 0 obj -<< -/Filter /FlateDecode -/Length 5072 ->> -stream -x]K$9nՃ(>x5pc oÇܩ]=f}GęꚝD#))Tl&gKNt|dMjC% 9l+gI}N'<ٿwYqgoJI9gRɺb49Rr],E#Ӟ ll.IlH# WbVH΂Ui`\4 4w&qEe\-24Z1)K,i^# Px )X^<2x@Xh%XH,gӼ&rV9g"t34()eK4-—FNĐevFL* @^lN`% |Ά' <CLb(/P*YÁ`hi@,x4$fJ/dа )hXmѰ naAޒuIÂV HÂȅ* 07;5,]LaAꆘY J4ְhawYby U=L@Wgp׳% 3LJs0hX@]rw}^zI(XBa*3n -̟2VqIDcO2F\eR*D. Uа wa0z "pXjuX "p~C԰` `ߌP]V-D.`kX+l,ITZ6P$aX$.{Ѱ wm AÂܵG^5a*sΪHрA km.$஘M RA/kXL9iX .JKQÂlY* P& X -kX=x kX=xˠa<So5</P5> OQ BaA FU%o8U沆9)v 2Iaވa͑L ` {x́89 ؃xgDjX XCJ0%#&4* &4,|$؎ A0GIf/&kX ^@7% ^iXPl2&kXZ cě4,x5,("DěYÂB%EQiNSQ-0 &I% iXPRx5,x$ofu Iw& x[ot"KꊁFVu{af`#`%'ufDge ?F;L>KT a39K' 1nd߿ՕQ/7Epa+`=e\, 00?5XxvpfjhnBy}suQ;1 CF{Ї4Lo/Q܆ް MXLoTo,!r.lQXZe 4]ϧ_@^OI\s_OL1ƖTĸDŲ d٦zg.}N ->0Dxe!y_~V*}JTXQ '!?Pm8)X*44ҟ5_m'g~1]FzҵOpH/w4ƭ]^{uoN2?^⤏7¶O8v$KZӝ/-1Vc;?ЏI?Qug& zehm}/u]^9~o4|Mi8ƣcnszd/|ECQZ+{gGN`x-$YiIC ȡQm'5;2 [5ϿwaNW'y2wxu祄ôMgܴ]f8Q3'O^ޝ́EnuH%>:~;'yޓ>?fQsH$W͜Ľu{}S+4d+ƀ G{?FF>7Jg/.Xv{c]zwGE|X'v.xn_m^rE6[f_kf>Y^f/QC1\}[hyD/0 *REsd .!ˋ.cO6w_>ӾK򮐱EnJx__roT7Qou-6'G7Sn;vrS - EV #Ճ)uL)qIފ֏]Wyj|RiR]Ǖ7;t]yE4F/zt`QbŴ];r qʿLhX ~R:Gqr!Di/98XyD|ɽ;#?ESɚ;7Mbrz"_k>Xi#~"ɴ_{p[e#?-~V2_E0˃of -*p ,:X$[Ff/urTHhvxm,W%vc$) \$&^Y3rj!\%{ 7Jֻ'P)Sc~XRI\c/Wښ,MzII&$KU-L 8&[b׏>H؊ɕNdAzѵa%%'KqKDl:+158*9p|,/#1HZ^?.s$vs[^PPf6*zT驱.'%rRj0;}z)Io-vI型GF~2q>Je:>iH&99-Ozw1%=Ŭ+ll7'ޞvH fK*bOuhDfO^Ҝ:6; ˹<^_@#JlJϥ' cd6>+Dۘ@s#9vUJ|>U%7{Ա뜜ĝN:/հ6YT[##YVƦ@a$Zl$_cir۩95'ޒ;}MzW;mG ߱u<[2&˵-O)#6t;4-:uNc dU׻0LxٌbwdU6`_C뜕CP0wqJzRP9ّtO3}۴nY Q,r 3we6ZUW4gaCsBS%7_hksKlvtPҋvm, AoYYBEC@r֓Y~AN]Y/O` -endstream -endobj -534 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 533 0 R -/Resources 4 0 R -/Annots [ 535 0 R 536 0 R 537 0 R 538 0 R 539 0 R 540 0 R 541 0 R 542 0 R 543 0 R 544 0 R 545 0 R 546 0 R 547 0 R 548 0 R 549 0 R 550 0 R 551 0 R 552 0 R 553 0 R 554 0 R 555 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -535 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb10-122) ->> -endobj -536 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb10-123) ->> -endobj -537 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb10-124) ->> -endobj -538 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb10-125) ->> -endobj -539 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb10-126) ->> -endobj -540 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb10-127) ->> -endobj -541 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb10-128) ->> -endobj -542 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb10-129) ->> -endobj -543 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 329.565778 101.433071 310.815778 ] -/BS << -/W 0 ->> -/Dest (cb11-1) ->> -endobj -544 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 310.618756 99.933071 291.868756 ] -/BS << -/W 0 ->> -/Dest (cb11-2) ->> -endobj -545 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 291.671735 99.933071 272.921735 ] -/BS << -/W 0 ->> -/Dest (cb11-3) ->> -endobj -546 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 272.724714 99.933071 253.974714 ] -/BS << -/W 0 ->> -/Dest (cb11-4) ->> -endobj -547 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 253.777692 99.933071 235.027692 ] -/BS << -/W 0 ->> -/Dest (cb11-5) ->> -endobj -548 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 234.830671 99.933071 216.080671 ] -/BS << -/W 0 ->> -/Dest (cb11-6) ->> -endobj -549 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 215.883649 99.933071 197.133649 ] -/BS << -/W 0 ->> -/Dest (cb11-7) ->> -endobj -550 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 196.936628 99.933071 178.186628 ] -/BS << -/W 0 ->> -/Dest (cb11-8) ->> -endobj -551 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 177.989606 99.933071 159.239606 ] -/BS << -/W 0 ->> -/Dest (cb11-9) ->> -endobj -552 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 159.042585 99.933071 140.292585 ] -/BS << -/W 0 ->> -/Dest (cb11-10) ->> -endobj -553 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 140.095563 99.933071 121.345563 ] -/BS << -/W 0 ->> -/Dest (cb11-11) ->> -endobj -554 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 121.148542 99.933071 102.398542 ] -/BS << -/W 0 ->> -/Dest (cb11-12) ->> -endobj -555 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 102.201520 99.933071 83.451520 ] -/BS << -/W 0 ->> -/Dest (cb11-13) ->> -endobj -556 0 obj -<< -/Filter /FlateDecode -/Length 4911 ->> -stream -x]K$q23"_a,@/hX f P|TUtWp( b"EWev&"/?~:Yş)abR8;Wb@ɤ|[=N_yٛRwdRNUV&%ŠKX#$e%%12 N1|r +!),g!֪<b+<LDG睉x.yGdbb+&cu/@ƃ,L9iY(UyD/A) -/CXWVyF4^!JfVyH0p湁>Xaw=a  w!A V{ ɂY*pb XB%kXcK5[gf 2G#&i)UdLhX`;hXH֡dΪȀsl*af*ͤJxjŀ6 ?!*dـ+~u,!)*8+"/~ `Eo?Qs8ȍHѸޞ?xw[Tk | PNpK^?LHĊ-݃tN^F 0OO;맥Vr0MCpG};<]%?`0m\ϸsP3J:F]#7áO:(]m !!d1y>0PJu:`U^#UeH-55M5J0}NnY`ܖkGI2`rmLiAs;1cyt0jLRd/6 W}˞=;a+;%#!YgCRsoKDH#+aBܞ:yL%U(2^Mʼn_}ɐjQh2*6˲.4Me~ՖG{{'cn|TG"gpO[|24KC}2 T]+Jw|.tTyV$News<ɸl >J2e,l UCHsU#|#4Z M etl$c@a[f6HwM;5\5B-;M~YcVM__OO*H&Jƿos;oAFa.o#]{dgrPR}=L_f.'w)=|0ϯ Dr7':li .wݯfi2l-2źMMǓ3J%&*R{Qr, MY egSϱ<ϣLОoqNld[y5 %Ŧ޲r߹Ga/"'0cٝ;i|ͅ%w?f -W|40ؖ}Sh:?8 -<:HNv\JTeۿ T|,X'Ğ76 oN>s EwGz_Ka&~Dhy)-, ;imэ\Þmi\acj|߻x~!URf=/9-?4]*yqreǦYhx9=Է;|x0&DVOop3cyxq}Ƴ(8_m -o.>~r./Q{ߴg -=J Km79=I1w GP-o*UEElVi4U5ԔM!.'E3|!qKWj:t9BTjrZjwQSn Ц6I~qb#%Y7]<؍/' xC~;+l7i(ҩ)צB׬4PBEhTAfRrhHle#PPQvJfr*t[b d=*T%5kd> +GBN͔.gh]5VYtVn'džo#95;+l/c5YL?J:Yͫb F&r /4{949OKDc4ÿ>ͫoغ L~(#$gTb6rO54?ܳ5kw$ކ7 wU+@;#՗Ju;K>EIv.!#B8TXd 1 JZӋ> -endobj -558 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb11-14) ->> -endobj -559 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb11-15) ->> -endobj -560 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb11-16) ->> -endobj -561 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb11-17) ->> -endobj -562 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb11-18) ->> -endobj -563 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb11-19) ->> -endobj -564 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb11-20) ->> -endobj -565 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb11-21) ->> -endobj -566 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb11-22) ->> -endobj -567 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb11-23) ->> -endobj -568 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb11-24) ->> -endobj -569 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb11-25) ->> -endobj -570 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb11-26) ->> -endobj -571 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 444.418756 101.433071 425.668756 ] -/BS << -/W 0 ->> -/Dest (cb12-1) ->> -endobj -572 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 425.471735 99.933071 406.721735 ] -/BS << -/W 0 ->> -/Dest (cb12-2) ->> -endobj -573 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 406.524714 99.933071 387.774714 ] -/BS << -/W 0 ->> -/Dest (cb12-3) ->> -endobj -574 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 387.577692 99.933071 368.827692 ] -/BS << -/W 0 ->> -/Dest (cb12-4) ->> -endobj -575 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 368.630671 99.933071 349.880671 ] -/BS << -/W 0 ->> -/Dest (cb12-5) ->> -endobj -576 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 349.683649 99.933071 330.933649 ] -/BS << -/W 0 ->> -/Dest (cb12-6) ->> -endobj -577 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 330.736628 99.933071 311.986628 ] -/BS << -/W 0 ->> -/Dest (cb12-7) ->> -endobj -578 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 311.789606 99.933071 293.039606 ] -/BS << -/W 0 ->> -/Dest (cb12-8) ->> -endobj -579 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 292.842585 99.933071 274.092585 ] -/BS << -/W 0 ->> -/Dest (cb12-9) ->> -endobj -580 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 273.895563 99.933071 255.145563 ] -/BS << -/W 0 ->> -/Dest (cb12-10) ->> -endobj -581 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 254.948542 99.933071 236.198542 ] -/BS << -/W 0 ->> -/Dest (cb12-11) ->> -endobj -582 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 236.001520 99.933071 217.251520 ] -/BS << -/W 0 ->> -/Dest (cb12-12) ->> -endobj -583 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 217.054499 99.933071 198.304499 ] -/BS << -/W 0 ->> -/Dest (cb12-13) ->> -endobj -584 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 198.107477 99.933071 179.357477 ] -/BS << -/W 0 ->> -/Dest (cb12-14) ->> -endobj -585 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 179.160456 99.933071 160.410456 ] -/BS << -/W 0 ->> -/Dest (cb12-15) ->> -endobj -586 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 160.213434 99.933071 141.463434 ] -/BS << -/W 0 ->> -/Dest (cb12-16) ->> -endobj -587 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 141.266413 99.933071 122.516413 ] -/BS << -/W 0 ->> -/Dest (cb12-17) ->> -endobj -588 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 122.319391 99.933071 103.569391 ] -/BS << -/W 0 ->> -/Dest (cb12-18) ->> -endobj -589 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 103.372370 99.933071 84.622370 ] -/BS << -/W 0 ->> -/Dest (cb12-19) ->> -endobj -590 0 obj -<< -/Filter /FlateDecode -/Length 3169 ->> -stream -x͛K )ezFr0"8Hd#Xsϟ=]ve&b++U9Jˇ M=~K2i [RBi)|Z]sZˑR BQ5QJ);ؚhԇ3`XU塪XX=b\ !US"\[l@%z:rbOB9UO%5bO`KbUtEOad!W[b- -l*lwUW[({&!tTK}B"CoÊ$"lɔ-I(z:-ON$):5t XLGa !+(<RbUGX[R@l)hnClI=uuEz,[Pcl* Uxn{,Vpa&y,WjV•sX .{X =+ZwE<(+=Awx,Pp(z,aX_ VXn ܍[+kP<(۹ݘ(z,Pp7j (!7wX( XK<$p?gMVk Zw-F9pcAwQǂcF eN]<$pqCXwcuu-PcAwp -H08cAw7ܥ$ {\l= YVEӁĘaO mz,z,QpXVJXA䱠 ruEz,@`걠D"1z,( dX 4F -[)z,Bm J0.P p*t\<[1{,@.*>Xf@걠4؂[Qc؂ c"]=[ z,";4rI Så{]߮,^<}ӻux0&+vƶŚO:|1d SŮ!livBFz^/gBFH -V*Urw9Ðj)Ƕ1^XdS_M1J%LGWlFxT4FK9#mi:_C&5!77̎$;9`'tw<{̉|'4:lY<m+ tEN -;$v(}6±ow Ew19H+Y u|WZ!vX?ΗჰM:̞"Z^Oߝ,c|$#MØ -x& |Jm>&}(PmŎmRsR=S1:{>V깕3y{P62{gh^&-}=KŖᒷ#l޾Ƥ\BV[ 6v$bߢ܇#5>R cd!ɖm_igeu{6qf/r:b)6~I-l>$Jh璒m4._ԟ^]z!َo;BPlOOw Uwy lPײYbZ顐2^66a:tL/2O .V{WjeF2YjCz1!:]WԛVL/f_n݄;rsDwZ3UF:>ӔR;mvi7>5B/l37t)NBYJ_>TX]f_ 7T!5låy7;9AZyPG`-2\\u8 tE^Z7 5q!6\ԍ@wS+4jYhw`*.cپv»mcӳ\N8fgp(L&u?sy;˶EI,l_2~׿-`Adj}^\±laSuM>kiAPU.8\7,#ޝFq2vn}pvdߒvp>nܒKsKVR7k]:lӲk'c~]Bf #VN66eS,Ez6v8F󾛜 -0@ޯ`&sj7}mɲd9siB7.:کv١ӾQ \@F]6Z,ݦWò=quGbJ^G:21v7%PZݹ̧YrĒՑ,)]o=w: 32Y-=(Iss:=JD|;r(P Q{gh]8^\3'c T -۟n&C>XWk>l*Dg{wq[,U? za\#.Oҳ -endstream -endobj -591 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 590 0 R -/Resources 4 0 R -/Annots [ 592 0 R 593 0 R 594 0 R 595 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -592 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb12-20) ->> -endobj -593 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb12-21) ->> -endobj -594 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb12-22) ->> -endobj -595 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb12-23) ->> -endobj -596 0 obj -<< -/Title (RKE Hardening Guide with CIS v1.6 Benchmark) -/Dest [ 6 0 R /XYZ 85.009843 502.818898 0 ] -/Count 14 -/First 597 0 R -/Last 608 0 R -/Parent 611 0 R ->> -endobj -597 0 obj -<< -/Title (Overview) -/Dest [ 30 0 R /XYZ 84.259843 272.631496 0 ] -/Count 1 -/First 598 0 R -/Last 598 0 R -/Parent 596 0 R -/Next 599 0 R ->> -endobj -598 0 obj -<< -/Title (Known Issues) -/Dest [ 45 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Parent 597 0 R ->> -endobj -599 0 obj -<< -/Title (Configure Kernel Runtime Parameters) -/Dest [ 45 0 R /XYZ 84.259843 539.222079 0 ] -/Count 0 -/Prev 597 0 R -/Parent 596 0 R -/Next 600 0 R ->> -endobj -600 0 obj -<< -/Title (Configure etcd user and group) -/Dest [ 45 0 R /XYZ 84.259843 283.686971 0 ] -/Count 1 -/Prev 599 0 R -/First 601 0 R -/Last 601 0 R -/Parent 596 0 R -/Next 602 0 R ->> -endobj -601 0 obj -<< -/Title (Create etcd user and group) -/Dest [ 45 0 R /XYZ 84.259843 169.788971 0 ] -/Count 0 -/Parent 600 0 R ->> -endobj -602 0 obj -<< -/Title (Configure default Service Account) -/Dest [ 53 0 R /XYZ 84.259843 561.590928 0 ] -/Count 1 -/Prev 600 0 R -/First 603 0 R -/Last 603 0 R -/Parent 596 0 R -/Next 604 0 R ->> -endobj -603 0 obj -<< -/Title (Set automountServiceAccountToken to false for default service accounts) -/Dest [ 53 0 R /XYZ 84.259843 522.092928 0 ] -/Count 0 -/Parent 602 0 R ->> -endobj -604 0 obj -<< -/Title (Configure Network Policy) -/Dest [ 67 0 R /XYZ 84.259843 599.840928 0 ] -/Count 1 -/Prev 602 0 R -/First 605 0 R -/Last 605 0 R -/Parent 596 0 R -/Next 606 0 R ->> -endobj -605 0 obj -<< -/Title (Ensure that all Namespaces have Network Policies defined) -/Dest [ 67 0 R /XYZ 84.259843 564.092928 0 ] -/Count 0 -/Parent 604 0 R ->> -endobj -606 0 obj -<< -/Title (Reference Hardened RKE cluster.yml Configuration) -/Dest [ 77 0 R /XYZ 84.259843 191.441066 0 ] -/Count 0 -/Prev 604 0 R -/Parent 596 0 R -/Next 607 0 R ->> -endobj -607 0 obj -<< -/Title (Reference Hardened RKE Template Configuration) -/Dest [ 390 0 R /XYZ 84.259843 518.211778 0 ] -/Count 0 -/Prev 606 0 R -/Parent 596 0 R -/Next 608 0 R ->> -endobj -608 0 obj -<< -/Title (Reference Hardened cloud-config Configuration) -/Dest [ 534 0 R /XYZ 84.259843 537.158799 0 ] -/Count 2 -/Prev 607 0 R -/First 609 0 R -/Last 610 0 R -/Parent 596 0 R ->> -endobj -609 0 obj -<< -/Title (Reference Hardened cloud-config for SUSE Linux Enterprise Server 15 \(SLES 15\) and openSUSE Leap 15) -/Dest [ 534 0 R /XYZ 84.259843 397.010799 0 ] -/Count 0 -/Parent 608 0 R -/Next 610 0 R ->> -endobj -610 0 obj -<< -/Title (Reference Hardened cloud-config for Red Hat Enterprise Linux 8 \(RHEL 8\) and Ubuntu 20.04 LTS) -/Dest [ 557 0 R /XYZ 84.259843 511.863778 0 ] -/Count 0 -/Prev 609 0 R -/Parent 608 0 R ->> -endobj -611 0 obj -<< -/Count 15 -/First 596 0 R -/Last 596 0 R ->> -endobj -612 0 obj -<< -/Length1 10704 -/Filter /FlateDecode -/Length 7088 ->> -stream -xz xTE:n^t'Kga дaS &MH ,b` - - #"$#qGcDfu&& |ݓ[SUV (Q %;{ݫ'gfDP}ꀜ{Ft}63p&nz GUw1r9+m ߧ:o/.`T=qz^1~ }0%"҃pda3{̝J=JDm_{eQ0 /?c(ۇ3&SJT<}Ckw9j{y ,Gi>P@}=#ozA7 E%[>qq_ų -{LEm1tk|Q2>fKa{S6E:?5hi,lh0(5Zd@(짡j4E*p)>y[&tv9X'-zr -0 -a[Y?臨U=Έ*(1v8j -"˟h9 -y!$3iФpa 'mpXD~`ǽ{bo>{ۅӢo]Sn6x6|&**q6E6T؜OmrBq7ZpUbĪAUn]Kµv\ӈO>"zx^z+VU> />.qnb1cw`rpr+SCy>.#N-R'.#NGX"e}-^PZ… KGzD8_Cvgù#qv#4Fو$ΐ` N8WLS$N^R(@bĉ'H녹x KW8cXFc__hhQ}qG0q 1Lb8n*n%q 8xC AbUؿ -Iww6b#xI̒xm.qo(nsa%{`/o6b ƌtp`{DbZbobJwH V,9bN^9;%D'/&0)+D/&x"!V'16ch1.ǨF-DcD%5bǾJP18"1G[bD!$:iξXh` mm FD5B$ܨB -I%Y-]9$Zq OKZ8Kpvfjz0Z~X -suvUԶy,[6ҨpD#Y2T9 Wj+TJsJRp-vқoP|s}B1a -O'xw4;Rw-YR>ZNsϱ-<0{.T@.Ҿ(ex!4:G7A"䝩VOsM0*.p h摰]Uݦ8EN:kPB5p&~Ȗ*q.e ssaޤQ |ڻ:u>Oe+%4h< =f;JHe6VÃw8mObᡑAE7\oWup2S|nLvsYqV5mdz,VR3{$0OBB\,njT!.I ۗoݺ^f멻<{O>*aaw=o{ȑgk_䷿/ '8&zTK@ģ|XOiWGE0aj:`v2e("CM7@_Tgd14OV -ʴʶ ɖ+7 =ӗM]2~&I`1 .oaJsv7鼮6]6ߢvu.$.A8K7k&NTP8RASivW,*BE'م`*,%ܦD}R7N]W~G;_λ1 I񀇹y0(^2/OD5%#3Xf|󂖫M 0!Iw.UѺaNI(ܥx裷؛ mk*+-' {?~|GSN`"'V£"ZQNy %EZQa& w5clhj'/`E rr]JkF L&J|O2%BB 3{ħ+K~`v>o6zhb!M@lgƢ B;_:x)?{g,S ,ҾRlc/%FYCvx>D;Eu Av0k(߾А4d&DtG)))Q))1)Y_/DDDD$'.(,*.Y::ZbdжAmr#srsc#cE.Z(M53.~,q*#-FXՔ`~쓽6f]l?>ȂczN(t Ż Nl{lEntrB!rž,`Ωԅ9շ9'~50(luXu`9IŶ:)2霗Oz9w,c]:js]yw|ܚ5vYaW~4~ysʕBʈ[nb_zG}-?_EDܥӫ;qŐ)ׄuI>LL>Lrֶ¸CuMv6ziNٯ#sL4YJ~{<)>ecۛUwou&쳫ǔ(LS [s41z|Vg1皋"h"O܉ZzUWmL,d? -7;6i=p yD,:ky!W'Jמ.s+y$LTtߙd̵URBlH5_:O[tyzڟOvr㏼xn֜U;f{|g]]V`ł}3[=ڳJIܐjh.ݔA6ۺQ<5HIu\]]KωBlENlp5)!Wy*:>[S3CZYeo:Q~TO"Bp3UX42bQiafcq<cUcM^-o2nZ-ŞbSZ?s?K?8(pu)GaieOeN50Y'يs`CB:2aS!m\jk]h+okq5_*VNɶG#W7Ѷ^_W#$V 2Xb/>K%*?VcUT[#IRQeT9h,ڕveֲ -nVwB|S`LMDH<RҨ40/̆zgAtB`w A4 AĨP^@cRO_0kƍYGLsi.#{3T7D3#E;i|͞gJ 0ZYKȠJsh?m;hy_>\B4 N{#{l7F傓3RJtcn0pC 75UXhT fπƗ`|V2̚#:V1`}:&_;xZ9ߛeuQ-Zk?+7ui]F~?0T;OztL%?/Fz'LK@a$ǣ`,1M0: -a Pi@h4zpQV4nAi7VTөA]ԕvԕV꺾H߲1toQFCe}cn1w Y_8a XMwu6tYy`Iެ3`ɄYyS`ļ%N.EY’IET4`,7p&Liy3`ɃyEzJdzɰd4hRtX2k œ]8cuAsGvF\qя?mu6<2Ώk߶r;7kWS -nD1rcS -endstream -endobj -613 0 obj -<< -/Length1 6944 -/Filter /FlateDecode -/Length 4153 ->> -stream -xYyxSו>Y2^d,KX'ɻ,[v"yw[mpbRд$L&5I_L iB4̌L &:i:S:COsΟ}3s{y2h1Ho..r78#$,oE\LRU !-ЮkĞF(d>wt 56"$2">m -E7am+tʙ=0_mEkÏ}ch"4vt7x|˰ޣR\:}$W-{ <GT:>?]_a>;G돏->b1ǡ)B.'rGP@迁BsJ3|e< e9B_#0N( -R}@kGi~ӗe*BD11AI BKLj5̘>}u[l-?G(W@:Gq$hY&(HFQـ.rP#@<* ௠=/t -+x:gGd%Gc(Gn1X̯xҁI}A,!Ў%0z$܁o!)h>FoQafJ S6:8ZAaD@-PXg5JdbTbQ%d"oR:v kWZ,ՠS"ɸǧ’Yw%yF>#_1=S4="s-X. - N~nHJ'd_[!ׄap%y,QhTtNą. - zB2vSN&f)H\i~Nao@YP4Ѩ#RY"$b%_o[mOփcGOx6L̬ -̔h5Qjq%z{jz}ugcX6˽r {shʓ#ɶsal5[??#EkwqATӨ*Z%+rbB*UBO1.A(b46N -hVjt=hHFYBSoq|f*hm?# aqg=d9~#( B )'\.2 6䘌vB020\+vϵ{65: 9r)d!5|EUQ -\j #֜PZۿZ!rL&"OM^UFWƑVw7g9<iz-y \8(UpV,5X -v66V 6ǿE *"x:WǰL>y22;,R;[ݥm s鋊 5Edٖt}maa? Q:vLA l4 eh!0I~Xk٤9Z1zёTQjr'vPg;#quԖ -+V]Ga,2 `)7?$L gd- _ҩPMUP -Ӣ_N;z/(6; OjU;+K[βڌrqd!׫xs uҌizO`GRjZH9%4n)¼j9>Ж_us_k|arm:Mmvc9vOZAO.R!CE'Al#/C\VDH6Rd{n<^ݺ;D1 5HaOrD*1sVj[Lܽ;F!қLy?(60lk4e)d,X+XdM|O0ܦ{C~M@詣H\F*/ssY:7`u>A>Քc4nq9 9#͠?Ie.D%g'*+O]7?ڻkx;$cn۾o*VoB ~0RL%pxRn7$ݿN؃gKܻoɘ6- h[:oc?DAuY /` Pu!osJ|3`RZٰfZ 7uw5e'd - Oݸ45,M23VgQA#P) /3]Kǣd_㷹Oa~Muԫ) h/i]{Y@K&,us`.7xH^&-@+,nQy? #^ŃS9TO(~"QHKwqͰ1h-+x"j(rjb!X 5bp.6=c]~#2W5/{篆/ΟHu-I~UB3} ?S2{f$?rT -%fŭ|`<5Y.4NF*([/mܺtl>#6]X -m~9G'3Lȏi4fT]rK%3r~3YEQ|.+Cv 1S|>yj GZ|ˢ;b[#)4jWʩJ)Mږ?RVT$$x q%<r6i-cN$q?aV5u@t{g _a-x˃j:,QZ/b7u<@nm/^v_ POQ"MurO^iU[,2լ:_S?Y_zUP+:&H1|Gޟ*:|N=ŋB"F=h6ԂZBJK rAO~|G`6b=G0uB/kn#ټV.-@߁@o Me>@ٔB V i~v6]}t_gL|EKapP$?jlڠB9io/;e -endstream -endobj -614 0 obj -<< -/Length1 7204 -/Filter /FlateDecode -/Length 4875 ->> -stream -x9kXUוku}.y\^ jA#H QV1iK'!CmjhjR4k6~Ik-vZ˜~68:1t:c컟k^{`BKKVV>QD -,@ˊ*.ܱ>꟣gYEY[>br~KcE fl-;={6 WR۸=;o+|4 چΚ߇~ `zM%:0p%_ؾ+BuY{C%?8XELdSEcyIa+<4O_{hxZݲrSY$?EV½l)3hA}RxrxA&\ʆ5_K9ʕ073LyrmAPAJ"PsG:tȇEPj`;sz0TH -BmЪ@F" - R=!j( iz :=Eb0#Ыq 83tnI %4V\JMG4P)q/yy>:? =Wegox&~rag2=?0>G=?-S2|j?I?>!?O |\Bk^se'Wƞj+G8#.<qV<\!#:x2~ #(K^ܿ> e&z~ܳTn;>Ї]Ux1"EB;ݸvVa;dlo36nO2nOta&xl#6{yC6mp+uhN]RU[5RM4V[J-2VXх2[qM2~ܐ7ԅwC[~\'cIX؀k׸>\Sdk\XdŻd\UUR2޹v.]Ηtap"3./02333`~^(üy{Ĺsyn.!1'sV`vg1ˁL7Wa&3ݘs\<}nLhLKLb6Lz)<ł)fKz>یٞb -L` -LwxR]$x79pVc'.@{1&c1h%ʏl<܎A´f0ECWȹЙ\O`mV?MV?Z̥҅fKDdLh4X1 ӸVcZ j;5F(;ԉqI0 0@(! -&T"#,!0p()v^"Ll5l]x (kCYI &,TL@+oR8J~8o^r]z\^}߅!4:Lg>z0}ӳ<7a-q{ L6%xF-cpK:lgJ% KM&`= 5wl >J5Qu\MhƸI%Q Gvob>?O~$o-/ a%qу00cdf>n>N _.H+iN,mL쏂vմn|N-V_y2 HX;DžSX_$0 TdX[,K: W+K1%^AX5JkWqD@x(t!qAkX0Wf] γ}2(Y~Qyzv`*".j8Y.2=:kԱJuZF/:w7V iW l,}n # -MeP̡74jP3ȆY,jQf!e EQ/|!_mc {XpeP0QBJBa*c;6?zOrB{=q=i["B#-줦^; ؖp}"5&%o%ŻBc(df ɣڍcm3;5A͙wfIN+4r:Y 6+?'';!W^Ϫ7ok-޷I򟚯иhгLO~K}E df,~od̒[6QbnU IhbAF129Brc̟;¤_dYX|t"FYkEzX3:M1MU1E:]`L7"\Rr$q7F*(1o=Ppxt|y>ݒ_lX*Gw,?S:vm m-; g1`!l)}/dyR`jY{:mfC%Y֑ɂP]$E?YZ8˔K$vX<(_3mO~d7]'F3HJd#R7N^Уo\rlc~:ei!U|E(d kGY ʗQ$@VW^hKZzJ:!Ǩr!=vmƠ4Ҵ2\ilȕ-r);'߬/KKwj`,KnZ Zփ֠]U{ -TӖ*#0IV/"}Qh_BBBBBBΈ2Ffl=rr@ؚ;m''\TX؂חH|W]S]K2ūޟhv鐙:!c .ULlC1>c1iF7QHeDW -1dy`jX>XVr+N7Ӫ]sB吳խs˘V-L[3> ,xa7 ;9gaߗG^yW,c6_~]l>';hmbns̭Q"W]b 'n7u[{Yr ,̾K7>oԱʛjXVT?/_^>e V-]ravN j4F\Mn^IB;{U]̼)/tecJj MSbHRhDx&0d̆hNc:7DLjy鮳1Mbvgj8gl3Hx햻p7h?:5b -([@k@gocKWRA=r6uA-'0wݵA1_:; 3UYޏN\5hݴD\J:(x9B/(g2ѧC^h\ Ń8mXY|E:qUm%ڶn k,?íq%+ -'NQ"\+p3;Ա$%@̲;:@\D&mz;jG!0؄Wտ +mhW3m" :Ӗ %- PPD1 @2~ȠEJbin;aWC4ˡө(yݤզ9;"L=Rk+QX­ ** -}Qip*n=yh~3[>KXPXEXMSn9 s sioVWY) -7ߜvk6ӿPySWNIV1UߐZ+'6 9uSYHR: +)1XM<2XDͬ' pCTyY'_TxBEkE%dllmmPQ&ҋOV} -endstream -endobj -615 0 obj -<< -/Length1 16324 -/Filter /FlateDecode -/Length 11654 ->> -stream -x{y|TEo-w{;4!d# K a¾*/$@D0M%2 b1ЀD@ 9❺A7}>oު:uΩs ![P0lP7?ݳW>F(/ sqEОC1WB;ДY~ LOxhh/xa5l@H_ԩMf]o=&.dPm6{Uv2=PN287a.o׳ CmYÑzhC=oDݬD㜉?_õ2܉sD̂vΟ`hC~}SS< -#W:Q]R~rg^XpN -MEc9y:x=록r j!bX MWH?AS K:~ ګyQ,Z.ٙo+tRwrsD@@i%[|-1ꛠCPJ܆r(܏7,z[h{˃4N@iۧ'P] ^ K)/G|6x:vD%t-VCՠ9P_Z<5dw]_DPQ@3 -`4߿ϭ vGА߿؋{SDZOa>EKnfE݇3.p)'Feq_\[zN-*oi8߫vO_}Ǯs箳LM>HVbcQ؁J$`;bP6dU[mI[FZP#z{UR V{D.hvhgw$і=Fӟ;O+ğpHvRu3A5 -7L}B>ްh3hss·k*zoaHWg+0p]pz~EF!~z~COO\\zя1wcCFϮgB_Eϔ{3fr'}[b#=;zG6}Xl`Ɗoo:K -=h}ewMFPw0z1_Ljlt/1o {2nj:m첊O;?-;ˌlk,pmV#AftK}Ubσm=>RG롕 tv -8QQLAhJ2Zh)kJFK]U|rq_N]fK}Ō.ZhzFx}Λ;TWEi+J紥Ng2:#NKSh1'ɌNBqNdt7J/3ѱt{t44F(=.gpt:ѡat0t p8ioa7aO0ջ@0F{‰ٴGUa=׫|+ͯ'Zݽ&vG3^3<ͫ^oЍѮB׻ \Fs@9ŴSZةf4+.f1ُvL;p`4nLg4 .E0A*v8Lۇv\Ox-V}m٭I>w>H؎Ѷ&2`|Ӌ1S7fh\l&Ә~=f4 -dh$h%2F0hN,d14:ёLة 1j[zX% ; ɨ&5dgUj :jඕ-Ua$*PX̨%FE;08zCHr)p2EqqzfP/x#9vGd ֭8.j#VI 5l%ڦ=YIA_s}s(kQ-s,|f[6zږ A!!E{}-DǡB7۩:DZB@'PLK5LT.99i(媿9gXZ3n"q8sFljy3!}ΖQ4!VZH (_4!Mnm+^;[EN$| 6HzSrE"v9t!f㊎sجhPuJGHX.twtfd GV!n(qqZnAL5fMͰgln7)ӱrkmdv6q+_&x-'~uHV"!#JAm$ <3{li[鲗l8E(E"CĶ&ir弳K3ߥznz7,7޽}j˱XmN(9 Ȭ̎ VIrCaX NkBBfǬ '4pK290w󿜾hb<Ԥ3;ёbu$N`rC􌎙YbZcmIXi0D4->sU٪e#je!;).m9NQ"%Esn@D641yp{buB([LAAǘTbb;Q!nJAqa5dd@YYčk(ٷ_mf~ʾ^Wz/Wt^kܬ1{1#Zr.jzl򿋾S_{ϺU9Ly? sF֒ͻĨL"S.Qs(!J¸HI6դmQF&0O7[uYWnsHfG[6]TzuIofd:>KteNWz 6=7B7#ٝeHf Plͬ˥ˬKWwZ.WHƔa -}Q^TʦTAnpd\PSg hbQ= 1VĶ9l/Oe[sxpIgX)^rfc% pV`^'ze_D(JP%<2q%8W+y zf=[ ZHrL~)9¼zGCFh"tƷ'N)g*_sjk!F`xDY+Z&E gn|i,s|![/a".o`e+4o~wlZ#'rcA\_X)šx+. X[ބޏSP -N!)4EHS9EIѥ)oڜXջYmCl'o @1p̡qǷֲ3qAzھ5=F Cm;Sc|)_hB xY!1hW~ʢATn1;&!K8Ky}7vݼ?b7.ڼy՚2!O"ľ)~x)^2ΝDAܗJ(.z%#B"G12pڨ˔ͭ I8iQZ2ŦwWI|m5Hds݀{x=aK|d n⫩a6m\fO]渘TPZ5.VSC>΄<*Mϗmz^qUvƮ^eXd˖$'|U*nw`s8W9'=?t*n+`Dڈڠ Bl16X|/*"Qs¹Lnn %`4 2٬q`k 1V}xLBDdrQi:䲥Lmv6k1')@[+&J\~}U/VC_Yz+6S-n-ʺ_dwX=laGᯣ>j|ݰUꈐtJR#8k6TXdΠh#+[Hc4̎<=zǀO46(z0];\㹸]]2>`czׂĆ%|23KȬi!MvYRmg{ҳ85$K}4=[u{ZLaJ@1C?/7T)>*ui2 x`[ -O#y,)maBP֡6ސ e0!4&F経!SZ^8ma0(uƅGPzDOpeK..FN<,v>tј՝' ~bv5b/gO8n)>[}xW\f,kwq I#P*X4Ԁ5*TRCr{3ݙ3-Umn9ْåx -JUS.d3|2@b'NqN,ﭨV 4>o)0e@KE$׵$ 㖣WS;͓nW[` -s7ILGC~D: ㍒n>}ebd+JU[]Fߜtb' ۑ<"TV$`X*< Ox>na.9~1t/Cn d`iN!:U0nȒmaS0"ffBӵ[KK~SK\_Å8}dk R22\W;j4?agfQ" 1Ɋ\ {`F%g"pW^xqz i1撒M|~-y_@!v@LUC*zKrP/ 5T'QZQ5ͮ YXh]8k|5g -.:WmhуA;9&s-^ܸ,y>o+~"-]^P'IhW$ůNqHq,HW -i@"Jfkr5.M&%$/+%[>L#~p`p^ -3x0_ku -7mi*!tP]h{}a.:64qVvX35 [4xXCYFuar-O&@&rz)KFNxEH:(.TBQ6KkI.-7ohI ̛|#WVttΌ=vOƲ=2n{rl^+:,ؠI`$DF:Q2v9>/۸\moc &؊zք^}]W?>mr?X&GkobP]+La{,1Iޒ&kcPwWs_[wT̠JWn,[QZN|Y-s_o]ROr~ٳ]`Yס}qcp.sڈd3Q-jdkI;4ҬMbUmJsBO*O۽ϯη?J&kzB:dDJ24/ch=*@YW 8< 㟋8^O_tCpj~Ȋ:yE -QKzL9n+DĜdBA: )Q{9g'E8Q0{?ڶ\5.f~ͳ*@\8!v:eDN@7$z!$D ֬ -B+вZc!QP&)dY,sUpab!)miVL; bHi<fH3%qDUn܀2AslTK_`50vU'@Zg8ADlHKAZ}"HLVɵ?>×p~1@w,ћf3EGJPK"[dd5+Qa"zy5@еjA7N#]p…M *RRT}^h3/,/ ?>8p>wpa`7Al0UX4Z4|!} -=F`Z( -$r.|+8Gk!FxZC,`<~,Z+t%6?ñ?!m_ZRvmII)HrڿNh9x$q :gC|Ź#V|L #+YԠ;&iZp}n^Ybq5 KՋkVX+Kq -;/-Sr;,c0Wķv"7h׫`|__)b]#WȘ/+K0Ӽa&QY1NU:FiE74jxYT峵j/c-5i2w Haܯf} S_`ޚs< gú^}rnO{>ɒ{;vO,uY ##L\| Hb$DH1n|Q(DdUO$|LHn -j<҇Yy>=VHm4i4[?X-F4#2*Vӱl+{6VhydyёjK,dP -X[!ܘ`J0wZ m#*_/d4x C֍<1٠?}O_t8pFa3Gztj&.FQ>'ᨲP$B$RG .4#Ψ#vRzѾZL3EtpЍd0Y0iZ..&`6h73K]c(P~WwQǠS6(ZCņwU͢wX; -~j[l =F[p<ӛޟ_Uѭ-xbyhxv} +!3 ΀byDگ ըp -ஹPC:<5O\dGo}YOѨ_'t%NԮ_(WǭÃ'n\ba$5^0DFG`&h4xQAgtςàoA~vz7xFҮ'L|j$:ySQ괧B'΋sA>ZD -endstream -endobj -616 0 obj -<< -/Type /FontDescriptor -/FontName /GUHWDL+DejaVuSans -/FontFamily (DejaVu Sans) -/Flags 4 -/FontBBox [ 0 -14 472 560 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 560 -/StemV 80 -/StemH 80 -/FontFile2 612 0 R ->> -endobj -617 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /GUHWDL+DejaVuSans -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 317 ] 17 [ 317 ] 20 [ 636 ] 25 [ 636 ] 37 [ 686 698 ] 40 [ 631 ] 42 [ 774 751 294 ] 46 [ 655 ] 53 [ 694 634 ] 68 [ 612 ] 70 [ 549 634 615 ] 74 [ 634 633 277 ] 78 [ 579 ] 80 [ 974 633 611 ] 85 [ 411 520 392 633 591 817 ] ] -/FontDescriptor 616 0 R ->> -endobj -618 0 obj -<< -/Length 744 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -30 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0003> <0020> -<002b> <0048> -<0044> <0061> -<0055> <0072> -<0047> <0064> -<0048> <0065> -<0051> <006e> -<004c> <0069> -<004a> <0067> -<002a> <0047> -<0058> <0075> -<005a> <0077> -<0057> <0074> -<004b> <0068> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0046> <0063> -<0050> <006d> -<004e> <006b> -<0052> <006f> -<0056> <0073> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -619 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /GUHWDL+DejaVuSans -/Encoding /Identity-H -/DescendantFonts [ 617 0 R ] -/ToUnicode 618 0 R ->> -endobj -620 0 obj -<< -/Type /FontDescriptor -/FontName /BNVYMD+Poppins -/FontFamily (Poppins) -/Flags 4 -/FontBBox [ -27 -260 563 736 ] -/ItalicAngle 0 -/Ascent 1049 -/Descent -349 -/CapHeight 736 -/StemV 80 -/StemH 80 -/FontFile2 613 0 R ->> -endobj -621 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /BNVYMD+Poppins -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 266 ] 10 [ 158 453 453 ] 15 [ 197 550 209 ] 19 [ 627 319 574 588 628 627 634 545 630 629 212 ] 36 [ 673 612 771 706 512 503 777 691 245 ] 46 [ 598 431 ] 49 [ 702 785 578 ] 53 [ 607 586 540 674 675 975 ] 68 [ 675 675 606 675 619 328 675 639 245 247 514 245 1029 639 639 675 675 372 521 363 639 560 819 478 562 ] 206 [ 379 379 ] 209 [ 411 ] ] -/FontDescriptor 620 0 R ->> -endobj -622 0 obj -<< -/Length 1248 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -66 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0003> <0020> -<002b> <0048> -<0044> <0061> -<0055> <0072> -<0047> <0064> -<0048> <0065> -<0051> <006e> -<004c> <0069> -<004a> <0067> -<002a> <0047> -<0058> <0075> -<005a> <0077> -<0057> <0074> -<004b> <0068> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0046> <0063> -<0050> <006d> -<004e> <006b> -<0016> <0033> -<0017> <0034> -<0018> <0035> -<001a> <0037> -<0015> <0032> -<0013> <0030> -<0032> <004f> -<0052> <006f> -<0049> <0066> -<004f> <006c> -<0033> <0050> -<0056> <0073> -<0053> <0070> -<0024> <0041> -<0031> <004e> -<005c> <0079> -<0037> <0054> -<0010> <002d> -<0045> <0062> -<0054> <0071> -<000b> <0028> -<000c> <0029> -<000f> <002c> -<001d> <003a> -<0039> <0056> -<001b> <0038> -<0027> <0044> -<0029> <0046> -<00d1> <2022> -<005b> <0078> -<003a> <0057> -<0038> <0055> -<00ce> <201c> -<00cf> <201d> -<004d> <006a> -<002f> <004c> -<000a> <0027> -<001c> <0039> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -623 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /BNVYMD+Poppins -/Encoding /Identity-H -/DescendantFonts [ 621 0 R ] -/ToUnicode 622 0 R ->> -endobj -624 0 obj -<< -/Type /FontDescriptor -/FontName /MQMIVM+DejaVuSansMono -/FontFamily (DejaVu Sans Mono) -/Flags 5 -/FontBBox [ 0 -14 584 759 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 759 -/StemV 80 -/StemH 80 -/FontFile2 614 0 R ->> -endobj -625 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /MQMIVM+DejaVuSansMono -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 16 [ 601 601 ] 29 [ 601 ] 36 [ 601 ] 54 [ 601 601 ] 66 [ 601 ] 68 [ 601 ] 70 [ 601 601 601 601 ] 76 [ 601 ] 78 [ 601 601 601 601 601 601 ] 85 [ 601 601 601 601 601 ] 92 [ 601 ] ] -/FontDescriptor 624 0 R ->> -endobj -626 0 obj -<< -/Length 674 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -25 beginbfchar -<0048> <0065> -<0057> <0074> -<0046> <0063> -<0047> <0064> -<0049> <0066> -<0044> <0061> -<0058> <0075> -<004f> <006c> -<0056> <0073> -<0055> <0072> -<0011> <002e> -<005c> <0079> -<0050> <006d> -<0042> <005f> -<0053> <0070> -<0052> <006f> -<004c> <0069> -<001d> <003a> -<0010> <002d> -<0051> <006e> -<0036> <0053> -<0059> <0076> -<0024> <0041> -<0037> <0054> -<004e> <006b> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -627 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /MQMIVM+DejaVuSansMono -/Encoding /Identity-H -/DescendantFonts [ 625 0 R ] -/ToUnicode 626 0 R ->> -endobj -628 0 obj -<< -/Type /FontDescriptor -/FontName /VZSVIB+DejaVuSansMono -/FontFamily (DejaVu Sans Mono) -/Flags 4 -/FontBBox [ 0 -235 585 699 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 699 -/StemV 80 -/StemH 80 -/FontFile2 615 0 R ->> -endobj -629 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /VZSVIB+DejaVuSansMono -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 601 602 602 602 602 602 602 602 602 602 602 601 602 601 601 601 601 602 602 601 601 602 602 602 602 601 602 602 ] 32 [ 602 ] 36 [ 602 602 602 602 602 602 602 602 602 ] 46 [ 602 602 602 601 602 601 ] 53 [ 602 602 602 602 602 602 ] 60 [ 602 ] 62 [ 602 ] 64 [ 602 ] 66 [ 602 602 602 601 601 601 601 601 602 602 602 602 601 601 602 601 601 602 602 602 601 601 601 602 601 602 601 602 602 602 602 ] ] -/FontDescriptor 628 0 R ->> -endobj -630 0 obj -<< -/Length 1500 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -84 beginbfchar -<0056> <0073> -<005c> <0079> -<0046> <0063> -<0057> <0074> -<004f> <006c> -<0012> <002f> -<0048> <0065> -<0011> <002e> -<0047> <0064> -<001c> <0039> -<0013> <0030> -<0010> <002d> -<004e> <006b> -<0058> <0075> -<0045> <0062> -<0052> <006f> -<0051> <006e> -<0049> <0066> -<0059> <0076> -<0050> <006d> -<0055> <0072> -<004c> <0069> -<0042> <005f> -<0020> <003d> -<0014> <0031> -<0053> <0070> -<0044> <0061> -<005b> <0078> -<0015> <0032> -<0018> <0035> -<0003> <0020> -<0016> <0033> -<0017> <0034> -<004a> <0067> -<0005> <0022> -<004b> <0068> -<001d> <003a> -<0036> <0053> -<0024> <0041> -<0037> <0054> -<0039> <0056> -<000e> <002b> -<0006> <0023> -<0004> <0021> -<0007> <0024> -<000b> <0028> -<004d> <006a> -<005e> <007b> -<003e> <005b> -<000d> <002a> -<0040> <005d> -<000a> <0027> -<0060> <007d> -<000c> <0029> -<001e> <003b> -<005a> <0077> -<0031> <004e> -<0033> <0050> -<001b> <0038> -<002c> <0049> -<0028> <0045> -<002e> <004b> -<000f> <002c> -<0035> <0052> -<0054> <0071> -<0027> <0044> -<0026> <0043> -<002f> <004c> -<002b> <0048> -<003a> <0057> -<002a> <0047> -<0030> <004d> -<0019> <0036> -<0032> <004f> -<003c> <0059> -<001a> <0037> -<005f> <007c> -<0038> <0055> -<0009> <0026> -<0029> <0046> -<005d> <007a> -<0025> <0042> -<0043> <0060> -<0008> <0025> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -631 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /VZSVIB+DejaVuSansMono -/Encoding /Identity-H -/DescendantFonts [ 629 0 R ] -/ToUnicode 630 0 R ->> -endobj -632 0 obj -<< -/GUHWDL 619 0 R -/BNVYMD 623 0 R -/MQMIVM 627 0 R -/VZSVIB 631 0 R ->> -endobj -xref -0 633 -0000000000 65535 f -0000000015 00000 n -0000000235 00000 n -0000000355 00000 n -0000027529 00000 n -0000027662 00000 n -0000030321 00000 n -0000030520 00000 n -0000034117 00000 n -0000034467 00000 n -0000034601 00000 n -0000034737 00000 n -0000034899 00000 n -0000035062 00000 n -0000035218 00000 n -0000035375 00000 n -0000035532 00000 n -0000035692 00000 n -0000035853 00000 n -0000036014 00000 n -0000036165 00000 n -0000036317 00000 n -0000036492 00000 n -0000036668 00000 n -0000036844 00000 n -0000037016 00000 n -0000037189 00000 n -0000037361 00000 n -0000037534 00000 n -0000037707 00000 n -0000042713 00000 n -0000043017 00000 n -0000043267 00000 n -0000043403 00000 n -0000043566 00000 n -0000043723 00000 n -0000043880 00000 n -0000044041 00000 n -0000044202 00000 n -0000044354 00000 n -0000044527 00000 n -0000044700 00000 n -0000044873 00000 n -0000045135 00000 n -0000045395 00000 n -0000050582 00000 n -0000050837 00000 n -0000051092 00000 n -0000051225 00000 n -0000051356 00000 n -0000051487 00000 n -0000051618 00000 n -0000051749 00000 n -0000056758 00000 n -0000057055 00000 n -0000057188 00000 n -0000057319 00000 n -0000057452 00000 n -0000057583 00000 n -0000057714 00000 n -0000057845 00000 n -0000057978 00000 n -0000058111 00000 n -0000058242 00000 n -0000058373 00000 n -0000058504 00000 n -0000058635 00000 n -0000063613 00000 n -0000063882 00000 n -0000064015 00000 n -0000064146 00000 n -0000064277 00000 n -0000064408 00000 n -0000064539 00000 n -0000064735 00000 n -0000064994 00000 n -0000065225 00000 n -0000070848 00000 n -0000071201 00000 n -0000071334 00000 n -0000071465 00000 n -0000071596 00000 n -0000071727 00000 n -0000071858 00000 n -0000071989 00000 n -0000072120 00000 n -0000072251 00000 n -0000072382 00000 n -0000072514 00000 n -0000072646 00000 n -0000072778 00000 n -0000072910 00000 n -0000073042 00000 n -0000073175 00000 n -0000073306 00000 n -0000073437 00000 n -0000073568 00000 n -0000073699 00000 n -0000073928 00000 n -0000079347 00000 n -0000079784 00000 n -0000080022 00000 n -0000080156 00000 n -0000080288 00000 n -0000080420 00000 n -0000080552 00000 n -0000080684 00000 n -0000080816 00000 n -0000080948 00000 n -0000081080 00000 n -0000081212 00000 n -0000081345 00000 n -0000081478 00000 n -0000081611 00000 n -0000081744 00000 n -0000081877 00000 n -0000082010 00000 n -0000082143 00000 n -0000082276 00000 n -0000082409 00000 n -0000082542 00000 n -0000082675 00000 n -0000082808 00000 n -0000082941 00000 n -0000083074 00000 n -0000083207 00000 n -0000083340 00000 n -0000083473 00000 n -0000083605 00000 n -0000088733 00000 n -0000089212 00000 n -0000089345 00000 n -0000089478 00000 n -0000089611 00000 n -0000089744 00000 n -0000089877 00000 n -0000090010 00000 n -0000090143 00000 n -0000090276 00000 n -0000090409 00000 n -0000090542 00000 n -0000090675 00000 n -0000090808 00000 n -0000090941 00000 n -0000091074 00000 n -0000091207 00000 n -0000091340 00000 n -0000091473 00000 n -0000091606 00000 n -0000091739 00000 n -0000091872 00000 n -0000092005 00000 n -0000092138 00000 n -0000092271 00000 n -0000092404 00000 n -0000092537 00000 n -0000092670 00000 n -0000092803 00000 n -0000092936 00000 n -0000093069 00000 n -0000093202 00000 n -0000093335 00000 n -0000093467 00000 n -0000093598 00000 n -0000098570 00000 n -0000099009 00000 n -0000099142 00000 n -0000099275 00000 n -0000099408 00000 n -0000099541 00000 n -0000099674 00000 n -0000099807 00000 n -0000099940 00000 n -0000100073 00000 n -0000100206 00000 n -0000100339 00000 n -0000100472 00000 n -0000100605 00000 n -0000100738 00000 n -0000100871 00000 n -0000101004 00000 n -0000101137 00000 n -0000101270 00000 n -0000101403 00000 n -0000101536 00000 n -0000101669 00000 n -0000101802 00000 n -0000101935 00000 n -0000102068 00000 n -0000102201 00000 n -0000102334 00000 n -0000102467 00000 n -0000102599 00000 n -0000102730 00000 n -0000107838 00000 n -0000108341 00000 n -0000108474 00000 n -0000108607 00000 n -0000108740 00000 n -0000108873 00000 n -0000109006 00000 n -0000109139 00000 n -0000109272 00000 n -0000109405 00000 n -0000109538 00000 n -0000109671 00000 n -0000109804 00000 n -0000109938 00000 n -0000110072 00000 n -0000110206 00000 n -0000110340 00000 n -0000110474 00000 n -0000110608 00000 n -0000110742 00000 n -0000110876 00000 n -0000111010 00000 n -0000111144 00000 n -0000111278 00000 n -0000111412 00000 n -0000111546 00000 n -0000111680 00000 n -0000111814 00000 n -0000111948 00000 n -0000112082 00000 n -0000112216 00000 n -0000112350 00000 n -0000112484 00000 n -0000112618 00000 n -0000112752 00000 n -0000112886 00000 n -0000113019 00000 n -0000113151 00000 n -0000117686 00000 n -0000118189 00000 n -0000118323 00000 n -0000118457 00000 n -0000118591 00000 n -0000118725 00000 n -0000118859 00000 n -0000118993 00000 n -0000119127 00000 n -0000119261 00000 n -0000119395 00000 n -0000119529 00000 n -0000119663 00000 n -0000119797 00000 n -0000119931 00000 n -0000120065 00000 n -0000120199 00000 n -0000120333 00000 n -0000120467 00000 n -0000120601 00000 n -0000120735 00000 n -0000120869 00000 n -0000121003 00000 n -0000121137 00000 n -0000121271 00000 n -0000121405 00000 n -0000121539 00000 n -0000121673 00000 n -0000121807 00000 n -0000121941 00000 n -0000122075 00000 n -0000122209 00000 n -0000122343 00000 n -0000122477 00000 n -0000122611 00000 n -0000122745 00000 n -0000122878 00000 n -0000123010 00000 n -0000127251 00000 n -0000127770 00000 n -0000127904 00000 n -0000128038 00000 n -0000128172 00000 n -0000128306 00000 n -0000128440 00000 n -0000128574 00000 n -0000128708 00000 n -0000128842 00000 n -0000128976 00000 n -0000129110 00000 n -0000129244 00000 n -0000129378 00000 n -0000129512 00000 n -0000129646 00000 n -0000129780 00000 n -0000129914 00000 n -0000130048 00000 n -0000130182 00000 n -0000130316 00000 n -0000130450 00000 n -0000130584 00000 n -0000130718 00000 n -0000130852 00000 n -0000130986 00000 n -0000131120 00000 n -0000131254 00000 n -0000131388 00000 n -0000131522 00000 n -0000131656 00000 n -0000131790 00000 n -0000131924 00000 n -0000132058 00000 n -0000132192 00000 n -0000132326 00000 n -0000132460 00000 n -0000132594 00000 n -0000132727 00000 n -0000132859 00000 n -0000137871 00000 n -0000138390 00000 n -0000138524 00000 n -0000138658 00000 n -0000138792 00000 n -0000138926 00000 n -0000139060 00000 n -0000139194 00000 n -0000139328 00000 n -0000139462 00000 n -0000139596 00000 n -0000139730 00000 n -0000139864 00000 n -0000139998 00000 n -0000140132 00000 n -0000140266 00000 n -0000140400 00000 n -0000140534 00000 n -0000140668 00000 n -0000140802 00000 n -0000140936 00000 n -0000141070 00000 n -0000141204 00000 n -0000141338 00000 n -0000141472 00000 n -0000141606 00000 n -0000141740 00000 n -0000141874 00000 n -0000142008 00000 n -0000142142 00000 n -0000142276 00000 n -0000142410 00000 n -0000142544 00000 n -0000142678 00000 n -0000142812 00000 n -0000142946 00000 n -0000143080 00000 n -0000143214 00000 n -0000143347 00000 n -0000143479 00000 n -0000148519 00000 n -0000149038 00000 n -0000149172 00000 n -0000149306 00000 n -0000149440 00000 n -0000149574 00000 n -0000149708 00000 n -0000149842 00000 n -0000149976 00000 n -0000150110 00000 n -0000150244 00000 n -0000150378 00000 n -0000150512 00000 n -0000150646 00000 n -0000150780 00000 n -0000150914 00000 n -0000151048 00000 n -0000151182 00000 n -0000151316 00000 n -0000151450 00000 n -0000151584 00000 n -0000151718 00000 n -0000151852 00000 n -0000151986 00000 n -0000152120 00000 n -0000152254 00000 n -0000152388 00000 n -0000152522 00000 n -0000152656 00000 n -0000152790 00000 n -0000152924 00000 n -0000153058 00000 n -0000153192 00000 n -0000153326 00000 n -0000153460 00000 n -0000153594 00000 n -0000153728 00000 n -0000153862 00000 n -0000153995 00000 n -0000154127 00000 n -0000159321 00000 n -0000159800 00000 n -0000159934 00000 n -0000160068 00000 n -0000160202 00000 n -0000160336 00000 n -0000160470 00000 n -0000160604 00000 n -0000160738 00000 n -0000160872 00000 n -0000161006 00000 n -0000161140 00000 n -0000161274 00000 n -0000161408 00000 n -0000161542 00000 n -0000161676 00000 n -0000161906 00000 n -0000162041 00000 n -0000162174 00000 n -0000162307 00000 n -0000162440 00000 n -0000162573 00000 n -0000162706 00000 n -0000162839 00000 n -0000162972 00000 n -0000163105 00000 n -0000163239 00000 n -0000163373 00000 n -0000163507 00000 n -0000163641 00000 n -0000163775 00000 n -0000163909 00000 n -0000164043 00000 n -0000164176 00000 n -0000164308 00000 n -0000169178 00000 n -0000169689 00000 n -0000169823 00000 n -0000169957 00000 n -0000170091 00000 n -0000170225 00000 n -0000170359 00000 n -0000170493 00000 n -0000170627 00000 n -0000170761 00000 n -0000170895 00000 n -0000171029 00000 n -0000171163 00000 n -0000171297 00000 n -0000171431 00000 n -0000171565 00000 n -0000171699 00000 n -0000171833 00000 n -0000171967 00000 n -0000172101 00000 n -0000172235 00000 n -0000172369 00000 n -0000172503 00000 n -0000172637 00000 n -0000172771 00000 n -0000172905 00000 n -0000173039 00000 n -0000173173 00000 n -0000173307 00000 n -0000173441 00000 n -0000173575 00000 n -0000173709 00000 n -0000173843 00000 n -0000173977 00000 n -0000174111 00000 n -0000174245 00000 n -0000174379 00000 n -0000174512 00000 n -0000174644 00000 n -0000179360 00000 n -0000179839 00000 n -0000179973 00000 n -0000180107 00000 n -0000180241 00000 n -0000180375 00000 n -0000180509 00000 n -0000180643 00000 n -0000180777 00000 n -0000180911 00000 n -0000181045 00000 n -0000181179 00000 n -0000181313 00000 n -0000181447 00000 n -0000181581 00000 n -0000181715 00000 n -0000181849 00000 n -0000181983 00000 n -0000182117 00000 n -0000182251 00000 n -0000182385 00000 n -0000182519 00000 n -0000182653 00000 n -0000182787 00000 n -0000182921 00000 n -0000183055 00000 n -0000183189 00000 n -0000183323 00000 n -0000183457 00000 n -0000183591 00000 n -0000183725 00000 n -0000183859 00000 n -0000183993 00000 n -0000184126 00000 n -0000184258 00000 n -0000189459 00000 n -0000189938 00000 n -0000190072 00000 n -0000190206 00000 n -0000190340 00000 n -0000190474 00000 n -0000190608 00000 n -0000190742 00000 n -0000190876 00000 n -0000191010 00000 n -0000191144 00000 n -0000191278 00000 n -0000191412 00000 n -0000191547 00000 n -0000191682 00000 n -0000191817 00000 n -0000191952 00000 n -0000192087 00000 n -0000192222 00000 n -0000192357 00000 n -0000192492 00000 n -0000192627 00000 n -0000192762 00000 n -0000192897 00000 n -0000193032 00000 n -0000193167 00000 n -0000193302 00000 n -0000193437 00000 n -0000193572 00000 n -0000193707 00000 n -0000193842 00000 n -0000193977 00000 n -0000194112 00000 n -0000194246 00000 n -0000194379 00000 n -0000199526 00000 n -0000199909 00000 n -0000200044 00000 n -0000200179 00000 n -0000200314 00000 n -0000200449 00000 n -0000200584 00000 n -0000200719 00000 n -0000200854 00000 n -0000200989 00000 n -0000201124 00000 n -0000201257 00000 n -0000201390 00000 n -0000201523 00000 n -0000201656 00000 n -0000201789 00000 n -0000201922 00000 n -0000202055 00000 n -0000202188 00000 n -0000202322 00000 n -0000202456 00000 n -0000202590 00000 n -0000202723 00000 n -0000207709 00000 n -0000208180 00000 n -0000208314 00000 n -0000208448 00000 n -0000208582 00000 n -0000208716 00000 n -0000208850 00000 n -0000208984 00000 n -0000209118 00000 n -0000209252 00000 n -0000209386 00000 n -0000209520 00000 n -0000209654 00000 n -0000209788 00000 n -0000209922 00000 n -0000210057 00000 n -0000210190 00000 n -0000210323 00000 n -0000210456 00000 n -0000210589 00000 n -0000210722 00000 n -0000210855 00000 n -0000210988 00000 n -0000211121 00000 n -0000211255 00000 n -0000211389 00000 n -0000211523 00000 n -0000211657 00000 n -0000211791 00000 n -0000211925 00000 n -0000212059 00000 n -0000212193 00000 n -0000212327 00000 n -0000212460 00000 n -0000215704 00000 n -0000215951 00000 n -0000216085 00000 n -0000216219 00000 n -0000216353 00000 n -0000216487 00000 n -0000216662 00000 n -0000216816 00000 n -0000216931 00000 n -0000217097 00000 n -0000217286 00000 n -0000217415 00000 n -0000217608 00000 n -0000217781 00000 n -0000217965 00000 n -0000218124 00000 n -0000218303 00000 n -0000218480 00000 n -0000218672 00000 n -0000218890 00000 n -0000219102 00000 n -0000219164 00000 n -0000226342 00000 n -0000230584 00000 n -0000235548 00000 n -0000247293 00000 n -0000247525 00000 n -0000247941 00000 n -0000248738 00000 n -0000248888 00000 n -0000249117 00000 n -0000249649 00000 n -0000250951 00000 n -0000251098 00000 n -0000251339 00000 n -0000251712 00000 n -0000252439 00000 n -0000252593 00000 n -0000252835 00000 n -0000253429 00000 n -0000254983 00000 n -0000255137 00000 n -trailer -<< -/Size 633 -/Root 3 0 R -/Info 2 0 R ->> -startxref -255224 -%%EOF diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/rke-1.6-hardening-2.6.md b/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/rke-1.6-hardening-2.6.md deleted file mode 100644 index e12823a88a5..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke-1.6-hardening-2.6/rke-1.6-hardening-2.6.md +++ /dev/null @@ -1,643 +0,0 @@ ---- -title: RKE Hardening Guide with CIS v1.6 Benchmark -weight: 100 -aliases: - - /rancher/v2.6/en/security/hardening-guides/1.6-hardening-2.6/ ---- - -This document provides prescriptive guidance for hardening a production installation of a RKE cluster to be used with Rancher v2.6. It outlines the configurations and controls required to address Kubernetes benchmark controls from the Center for Information Security (CIS). - -> This hardening guide describes how to secure the nodes in your cluster, and it is recommended to follow this guide before installing Kubernetes. - -This hardening guide is intended to be used for RKE clusters and associated with specific versions of the CIS Kubernetes Benchmark, Kubernetes, and Rancher: - -| Rancher Version | CIS Benchmark Version | Kubernetes Version | -| --------------- | --------------------- | ------------------ | -| Rancher v2.6 | Benchmark v1.6 | Kubernetes v1.18 up to v1.23 | - -[Click here to download a PDF version of this document](https://releases.rancher.com/documents/security/2.6/Rancher_v2-6_CIS_v1-6_Hardening_Guide.pdf). - -- [Overview](#overview) -- [Configure Kernel Runtime Parameters](#configure-kernel-runtime-parameters) -- [Configure `etcd` user and group](#configure-etcd-user-and-group) -- [Configure `default` service account](#configure-default-service-account) -- [Configure Network Policy](#configure-network-policy) -- [Reference Hardened RKE `cluster.yml` Configuration](#reference-hardened-rke-cluster-yml-configuration) -- [Reference Hardened RKE Template Configuration](#reference-hardened-rke-template-configuration) -- [Reference Hardened **cloud-config** Configuration](#reference-hardened-cloud-config-configuration) - -### Overview - -This document provides prescriptive guidance for hardening a RKE cluster to be used for installing Rancher v2.6 with Kubernetes v1.18 up to v1.23 or provisioning a RKE cluster with Kubernetes v1.18 up to v1.23 to be used within Rancher v2.6. It outlines the configurations required to address Kubernetes benchmark controls from the Center for Information Security (CIS). - -For more details about evaluating a hardened cluster against the official CIS benchmark, refer to the [CIS 1.6 Benchmark - Self-Assessment Guide - Rancher v2.6]({{}}/rancher/v2.6/en/security/hardening-guides/1.6-benchmark-2.6/). - -#### Known Issues - -- Rancher **exec shell** and **view logs** for pods are **not** functional in a CIS v1.6 hardened setup when only public IP is provided when registering custom nodes. This functionality requires a private IP to be provided when registering the custom nodes. -- When setting the `default_pod_security_policy_template_id:` to `restricted` or `restricted-noroot`, based on the pod security policies (PSP) [provided]({{}}/rancher/v2.6/en/admin-settings/pod-security-policies/) by Rancher, Rancher creates **RoleBindings** and **ClusterRoleBindings** on the default service accounts. The CIS v1.6 check 5.1.5 requires that the default service accounts have no roles or cluster roles bound to it apart from the defaults. In addition the default service accounts should be configured such that it does not provide a service account token and does not have any explicit rights assignments. - -### Configure Kernel Runtime Parameters - -The following `sysctl` configuration is recommended for all nodes type in the cluster. Set the following parameters in `/etc/sysctl.d/90-kubelet.conf`: - -```ini -vm.overcommit_memory=1 -vm.panic_on_oom=0 -kernel.panic=10 -kernel.panic_on_oops=1 -kernel.keys.root_maxbytes=25000000 -``` - -Run `sysctl -p /etc/sysctl.d/90-kubelet.conf` to enable the settings. - -### Configure `etcd` user and group - -A user account and group for the **etcd** service is required to be setup before installing RKE. The **uid** and **gid** for the **etcd** user will be used in the RKE **config.yml** to set the proper permissions for files and directories during installation time. - -#### Create `etcd` user and group - -To create the **etcd** user and group run the following console commands. The commands below use `52034` for **uid** and **gid** are for example purposes. Any valid unused **uid** or **gid** could also be used in lieu of `52034`. - -```bash -groupadd --gid 52034 etcd -useradd --comment "etcd service account" --uid 52034 --gid 52034 etcd --shell /usr/sbin/nologin -``` - -Update the RKE **config.yml** with the **uid** and **gid** of the **etcd** user: - -```yaml -services: - etcd: - gid: 52034 - uid: 52034 -``` - -### Configure `default` Service Account - -#### Set `automountServiceAccountToken` to `false` for `default` service accounts - -Kubernetes provides a default service account which is used by cluster workloads where no specific service account is assigned to the pod. Where access to the Kubernetes API from a pod is required, a specific service account should be created for that pod, and rights granted to that service account. The default service account should be configured such that it does not provide a service account token and does not have any explicit rights assignments. - -For each namespace including **default** and **kube-system** on a standard RKE install, the **default** service account must include this value: - -```yaml -automountServiceAccountToken: false -``` - -Save the following configuration to a file called `account_update.yaml`. - -```yaml -apiVersion: v1 -kind: ServiceAccount -metadata: - name: default -automountServiceAccountToken: false -``` - -Create a bash script file called `account_update.sh`. Be sure to `chmod +x account_update.sh` so the script has execute permissions. - -```bash -#!/bin/bash -e - -for namespace in $(kubectl get namespaces -A -o=jsonpath="{.items[*]['metadata.name']}"); do - kubectl patch serviceaccount default -n ${namespace} -p "$(cat account_update.yaml)" -done -``` - -### Configure Network Policy - -#### Ensure that all Namespaces have Network Policies defined - -Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints. - -Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace. To enforce network policies, a CNI (container network interface) plugin must be enabled. This guide uses [Canal](https://github.com/projectcalico/canal) to provide the policy enforcement. Additional information about CNI providers can be found [here](https://www.suse.com/c/rancher_blog/comparing-kubernetes-cni-providers-flannel-calico-canal-and-weave/). - -Once a CNI provider is enabled on a cluster a default network policy can be applied. For reference purposes a **permissive** example is provided below. If you want to allow all traffic to all pods in a namespace (even if policies are added that cause some pods to be treated as “isolated”), you can create a policy that explicitly allows all traffic in that namespace. Save the following configuration as `default-allow-all.yaml`. Additional [documentation](https://kubernetes.io/docs/concepts/services-networking/network-policies/) about network policies can be found on the Kubernetes site. - -> This `NetworkPolicy` is just an example and is not recommended for production use. - -```yaml ---- -apiVersion: networking.k8s.io/v1 -kind: NetworkPolicy -metadata: - name: default-allow-all -spec: - podSelector: {} - ingress: - - {} - egress: - - {} - policyTypes: - - Ingress - - Egress -``` - -Create a bash script file called `apply_networkPolicy_to_all_ns.sh`. Be sure to `chmod +x apply_networkPolicy_to_all_ns.sh` so the script has execute permissions. - -```bash -#!/bin/bash -e - -for namespace in $(kubectl get namespaces -A -o=jsonpath="{.items[*]['metadata.name']}"); do - kubectl apply -f default-allow-all.yaml -n ${namespace} -done -``` - -Execute this script to apply the `default-allow-all.yaml` configuration with the **permissive** `NetworkPolicy` to all namespaces. - -### Reference Hardened RKE `cluster.yml` Configuration - -The reference `cluster.yml` is used by the RKE CLI that provides the configuration needed to achieve a hardened install of Rancher Kubernetes Engine (RKE). RKE install [documentation]({{}}/rke/latest/en/installation/) is provided with additional details about the configuration items. This reference `cluster.yml` does not include the required **nodes** directive which will vary depending on your environment. Documentation for node configuration in RKE can be found [here]({{}}/rke/latest/en/config-options/nodes/). - -> For a Kubernetes v1.18 cluster, the configuration `spec.volumes: 'ephemeral'` should be removed from the `PodSecurityPolicy`, since it's not supported in this Kubernetes release. - -```yaml -# If you intend to deploy Kubernetes in an air-gapped environment, -# please consult the documentation on how to configure custom RKE images. -# https://rancher.com/docs/rke/latest/en/installation/ . - -# The nodes directive is required and will vary depending on your environment. -# Documentation for node configuration can be found here: -# https://rancher.com/docs/rke/latest/en/config-options/nodes/ -nodes: [] -services: - etcd: - image: "" - extra_args: {} - extra_binds: [] - extra_env: [] - win_extra_args: {} - win_extra_binds: [] - win_extra_env: [] - external_urls: [] - ca_cert: "" - cert: "" - key: "" - path: "" - uid: 52034 - gid: 52034 - snapshot: false - retention: "" - creation: "" - backup_config: null - kube-api: - image: "" - extra_args: {} - extra_binds: [] - extra_env: [] - win_extra_args: {} - win_extra_binds: [] - win_extra_env: [] - service_cluster_ip_range: "" - service_node_port_range: "" - pod_security_policy: true - always_pull_images: false - secrets_encryption_config: - enabled: true - custom_config: null - audit_log: - enabled: true - configuration: null - admission_configuration: null - event_rate_limit: - enabled: true - configuration: null - kube-controller: - image: "" - extra_args: - feature-gates: RotateKubeletServerCertificate=true - tls-cipher-suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 - bind-address: 127.0.0.1 - extra_binds: [] - extra_env: [] - win_extra_args: {} - win_extra_binds: [] - win_extra_env: [] - cluster_cidr: "" - service_cluster_ip_range: "" - scheduler: - image: "" - extra_args: - tls-cipher-suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 - bind-address: 127.0.0.1 - extra_binds: [] - extra_env: [] - win_extra_args: {} - win_extra_binds: [] - win_extra_env: [] - kubelet: - image: "" - extra_args: - feature-gates: RotateKubeletServerCertificate=true - protect-kernel-defaults: true - tls-cipher-suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 - extra_binds: [] - extra_env: [] - win_extra_args: {} - win_extra_binds: [] - win_extra_env: [] - cluster_domain: cluster.local - infra_container_image: "" - cluster_dns_server: "" - fail_swap_on: false - generate_serving_certificate: true - kubeproxy: - image: "" - extra_args: {} - extra_binds: [] - extra_env: [] - win_extra_args: {} - win_extra_binds: [] - win_extra_env: [] -network: - plugin: "" - options: {} - mtu: 0 - node_selector: {} - update_strategy: null -authentication: - strategy: "" - sans: [] - webhook: null -addons: | - # Upstream Kubernetes restricted PSP policy - # https://github.com/kubernetes/website/blob/564baf15c102412522e9c8fc6ef2b5ff5b6e766c/content/en/examples/policy/restricted-psp.yaml - apiVersion: policy/v1beta1 - kind: PodSecurityPolicy - metadata: - name: restricted-noroot - spec: - privileged: false - # Required to prevent escalations to root. - allowPrivilegeEscalation: false - requiredDropCapabilities: - - ALL - # Allow core volume types. - volumes: - - 'configMap' - - 'emptyDir' - - 'projected' - - 'secret' - - 'downwardAPI' - # Assume that ephemeral CSI drivers & persistentVolumes set up by the cluster admin are safe to use. - - 'csi' - - 'persistentVolumeClaim' - - 'ephemeral' - hostNetwork: false - hostIPC: false - hostPID: false - runAsUser: - # Require the container to run without root privileges. - rule: 'MustRunAsNonRoot' - seLinux: - # This policy assumes the nodes are using AppArmor rather than SELinux. - rule: 'RunAsAny' - supplementalGroups: - rule: 'MustRunAs' - ranges: - # Forbid adding the root group. - - min: 1 - max: 65535 - fsGroup: - rule: 'MustRunAs' - ranges: - # Forbid adding the root group. - - min: 1 - max: 65535 - readOnlyRootFilesystem: false - --- - apiVersion: rbac.authorization.k8s.io/v1 - kind: ClusterRole - metadata: - name: psp:restricted-noroot - rules: - - apiGroups: - - extensions - resourceNames: - - restricted-noroot - resources: - - podsecuritypolicies - verbs: - - use - --- - apiVersion: rbac.authorization.k8s.io/v1 - kind: ClusterRoleBinding - metadata: - name: psp:restricted-noroot - roleRef: - apiGroup: rbac.authorization.k8s.io - kind: ClusterRole - name: psp:restricted-noroot - subjects: - - apiGroup: rbac.authorization.k8s.io - kind: Group - name: system:serviceaccounts - - apiGroup: rbac.authorization.k8s.io - kind: Group - name: system:authenticated - --- - apiVersion: networking.k8s.io/v1 - kind: NetworkPolicy - metadata: - name: default-allow-all - spec: - podSelector: {} - ingress: - - {} - egress: - - {} - policyTypes: - - Ingress - - Egress - --- - apiVersion: v1 - kind: ServiceAccount - metadata: - name: default - automountServiceAccountToken: false -addons_include: [] -system_images: - etcd: "" - alpine: "" - nginx_proxy: "" - cert_downloader: "" - kubernetes_services_sidecar: "" - kubedns: "" - dnsmasq: "" - kubedns_sidecar: "" - kubedns_autoscaler: "" - coredns: "" - coredns_autoscaler: "" - nodelocal: "" - kubernetes: "" - flannel: "" - flannel_cni: "" - calico_node: "" - calico_cni: "" - calico_controllers: "" - calico_ctl: "" - calico_flexvol: "" - canal_node: "" - canal_cni: "" - canal_controllers: "" - canal_flannel: "" - canal_flexvol: "" - weave_node: "" - weave_cni: "" - pod_infra_container: "" - ingress: "" - ingress_backend: "" - metrics_server: "" - windows_pod_infra_container: "" -ssh_key_path: "" -ssh_cert_path: "" -ssh_agent_auth: false -authorization: - mode: "" - options: {} -ignore_docker_version: false -kubernetes_version: "" -private_registries: [] -ingress: - provider: "" - options: {} - node_selector: {} - extra_args: {} - dns_policy: "" - extra_envs: [] - extra_volumes: [] - extra_volume_mounts: [] - update_strategy: null - http_port: 0 - https_port: 0 - network_mode: "" -cluster_name: -cloud_provider: - name: "" -prefix_path: "" -win_prefix_path: "" -addon_job_timeout: 0 -bastion_host: - address: "" - port: "" - user: "" - ssh_key: "" - ssh_key_path: "" - ssh_cert: "" - ssh_cert_path: "" -monitoring: - provider: "" - options: {} - node_selector: {} - update_strategy: null - replicas: null -restore: - restore: false - snapshot_name: "" -dns: null -upgrade_strategy: - max_unavailable_worker: "" - max_unavailable_controlplane: "" - drain: null - node_drain_input: null -``` - -### Reference Hardened RKE Template Configuration - -The reference RKE template provides the configuration needed to achieve a hardened install of Kubernetes. RKE templates are used to provision Kubernetes and define Rancher settings. Follow the Rancher [documentation]({{}}/rancher/v2.6/en/installation) for additional installation and RKE template details. - -```yaml -# -# Cluster Config -# -default_pod_security_policy_template_id: restricted-noroot -docker_root_dir: /var/lib/docker -enable_cluster_alerting: false -enable_cluster_monitoring: false -enable_network_policy: true -local_cluster_auth_endpoint: - enabled: true -name: '' -# -# Rancher Config -# -rancher_kubernetes_engine_config: - addon_job_timeout: 45 - authentication: - strategy: x509 - dns: - nodelocal: - ip_address: '' - node_selector: null - update_strategy: {} - enable_cri_dockerd: false - ignore_docker_version: true -# -# # Currently only nginx ingress provider is supported. -# # To disable ingress controller, set `provider: none` -# # To enable ingress on specific nodes, use the node_selector, eg: -# provider: nginx -# node_selector: -# app: ingress -# - ingress: - default_backend: false - default_ingress_class: true - http_port: 0 - https_port: 0 - provider: nginx - kubernetes_version: v1.21.8-rancher1-1 - monitoring: - provider: metrics-server - replicas: 1 -# -# If you are using calico on AWS -# -# network: -# plugin: calico -# calico_network_provider: -# cloud_provider: aws -# -# # To specify flannel interface -# -# network: -# plugin: flannel -# flannel_network_provider: -# iface: eth1 -# -# # To specify flannel interface for canal plugin -# -# network: -# plugin: canal -# canal_network_provider: -# iface: eth1 -# - network: - mtu: 0 - options: - flannel_backend_type: vxlan - plugin: canal - rotate_encryption_key: false -# -# services: -# kube-api: -# service_cluster_ip_range: 10.43.0.0/16 -# kube-controller: -# cluster_cidr: 10.42.0.0/16 -# service_cluster_ip_range: 10.43.0.0/16 -# kubelet: -# cluster_domain: cluster.local -# cluster_dns_server: 10.43.0.10 -# - services: - scheduler: - extra_args: - tls-cipher-suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 - bind-address: 127.0.0.1 - etcd: - backup_config: - enabled: true - interval_hours: 12 - retention: 6 - safe_timestamp: false - timeout: 300 - creation: 12h - extra_args: - election-timeout: 5000 - heartbeat-interval: 500 - retention: 72h - snapshot: false - uid: 52034 - gid: 52034 - kube_api: - always_pull_images: false - audit_log: - enabled: true - event_rate_limit: - enabled: true - pod_security_policy: true - secrets_encryption_config: - enabled: true - service_node_port_range: 30000-32767 - kube-controller: - extra_args: - feature-gates: RotateKubeletServerCertificate=true - tls-cipher-suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 - bind-address: 127.0.0.1 - kubelet: - extra_args: - feature-gates: RotateKubeletServerCertificate=true - protect-kernel-defaults: true - tls-cipher-suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 - fail_swap_on: false - generate_serving_certificate: true - ssh_agent_auth: false - upgrade_strategy: - max_unavailable_controlplane: '1' - max_unavailable_worker: 10% -windows_prefered_cluster: false -``` - -### Reference Hardened **cloud-config** Configuration - -A **cloud-config** configuration file is generally used in cloud infrastructure environments to allow for configuration management of compute instances. The reference config configures SUSE Linux Enterprise Server (SLES), openSUSE Leap, Red Hat Enterprise Linux (RHEL) and Ubuntu operating system level settings needed before installing Kubernetes. - -#### Reference Hardened **cloud-config** for SUSE Linux Enterprise Server 15 (SLES 15) and openSUSE Leap 15 - -```yaml -#cloud-config -system_info: - default_user: - groups: - - docker -write_files: -- path: "/etc/sysctl.d/90-kubelet.conf" - owner: root:root - permissions: '0644' - content: | - vm.overcommit_memory=1 - vm.panic_on_oom=0 - kernel.panic=10 - kernel.panic_on_oops=1 - kernel.keys.root_maxbytes=25000000 -package_update: true -ssh_pwauth: false -runcmd: -# Docker should already be installed in SLES 15 SP3 -- zypper install docker containerd -- systemctl daemon-reload -- systemctl enable docker.service -- systemctl start --no-block docker.service -- sysctl -p /etc/sysctl.d/90-kubelet.conf -- groupadd --gid 52034 etcd -- useradd --comment "etcd service account" --uid 52034 --gid 52034 etcd --shell /usr/sbin/nologin -``` - -#### Reference Hardened **cloud-config** for Red Hat Enterprise Linux 8 (RHEL 8) and Ubuntu 20.04 LTS - -```yaml -#cloud-config -system_info: - default_user: - groups: - - docker -write_files: -- path: "/etc/sysctl.d/90-kubelet.conf" - owner: root:root - permissions: '0644' - content: | - vm.overcommit_memory=1 - vm.panic_on_oom=0 - kernel.panic=10 - kernel.panic_on_oops=1 - kernel.keys.root_maxbytes=25000000 -package_update: true -ssh_pwauth: false -runcmd: -# Install Docker from Rancher's Docker installation scripts - github.com/rancher/install-docker -- curl https://releases.rancher.com/install-docker/20.10.sh | sh -- sysctl -p /etc/sysctl.d/90-kubelet.conf -- groupadd --gid 52034 etcd -- useradd --comment "etcd service account" --uid 52034 --gid 52034 etcd --shell /usr/sbin/nologin -``` diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf b/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf deleted file mode 100644 index a99a551e3d6..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf +++ /dev/null @@ -1,14240 +0,0 @@ -%PDF-1.7 -%🖤 -1 0 obj -<< -/Type /Pages -/Kids [ 6 0 R 8 0 R 38 0 R 76 0 R 114 0 R 152 0 R 186 0 R 222 0 R 258 0 R 294 0 R 306 0 R 313 0 R 317 0 R 321 0 R 325 0 R 329 0 R 333 0 R 338 0 R 342 0 R 346 0 R 351 0 R 358 0 R 398 0 R 423 0 R 462 0 R 486 0 R 490 0 R 492 0 R 495 0 R 497 0 R 500 0 R 502 0 R 504 0 R 507 0 R 509 0 R 512 0 R 514 0 R 517 0 R 519 0 R 522 0 R 524 0 R 527 0 R 529 0 R 533 0 R 535 0 R 537 0 R 542 0 R 544 0 R 547 0 R 549 0 R 551 0 R 554 0 R 556 0 R 559 0 R 561 0 R 564 0 R 566 0 R 569 0 R 571 0 R 574 0 R 576 0 R 579 0 R 581 0 R 584 0 R 586 0 R 589 0 R 591 0 R 594 0 R 596 0 R 599 0 R 601 0 R 603 0 R 606 0 R 608 0 R 611 0 R 613 0 R 616 0 R 618 0 R 621 0 R 623 0 R 626 0 R 628 0 R 631 0 R 633 0 R 636 0 R 638 0 R 641 0 R 643 0 R 645 0 R 649 0 R 651 0 R 653 0 R 656 0 R 659 0 R 662 0 R 665 0 R 668 0 R 670 0 R 673 0 R 675 0 R 679 0 R 681 0 R 684 0 R 686 0 R 689 0 R 691 0 R 694 0 R 696 0 R 698 0 R 701 0 R 704 0 R 708 0 R 713 0 R 717 0 R 720 0 R 724 0 R 728 0 R 732 0 R 736 0 R 740 0 R 744 0 R 748 0 R 751 0 R 755 0 R 759 0 R 763 0 R 765 0 R 769 0 R 773 0 R 775 0 R 777 0 R 802 0 R 813 0 R 817 0 R 821 0 R 825 0 R 828 0 R 836 0 R 853 0 R 855 0 R 857 0 R 859 0 R ] -/Count 142 ->> -endobj -2 0 obj -<< -/Title (RKE2 CIS v1.6 Benchmark - Self-Assessment Guide - Rancher v2.6) -/Creator (pandoc) -/Producer (WeasyPrint 54.3) ->> -endobj -3 0 obj -<< -/Type /Catalog -/Pages 1 0 R -/Outlines 1003 0 R -/Names << -/Dests << -/Names [ (TOC) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (api-server) [ 486 0 R /XYZ 41.740157 784.430079 0 ] (apply-security-context-to-your-pods-and-containers-automated) [ 859 0 R /XYZ 84.259843 324.051496 0 ] (authentication-and-authorization) [ 696 0 R /XYZ 41.740157 784.430079 0 ] (cb1) [ 317 0 R /XYZ 84.259843 529.251496 0 ] (cb1-1) [ 317 0 R /XYZ 101.433071 527.554475 0 ] (cb10) [ 321 0 R /XYZ 84.259843 180.731993 0 ] (cb10-1) [ 321 0 R /XYZ 101.433071 179.034971 0 ] (cb100) [ 556 0 R /XYZ 84.259843 700.370079 0 ] (cb100-1) [ 556 0 R /XYZ 101.433071 698.673057 0 ] (cb103) [ 561 0 R /XYZ 84.259843 643.970079 0 ] (cb103-1) [ 561 0 R /XYZ 101.433071 642.273057 0 ] (cb106) [ 566 0 R /XYZ 84.259843 590.570079 0 ] (cb106-1) [ 566 0 R /XYZ 101.433071 588.873057 0 ] (cb109) [ 571 0 R /XYZ 84.259843 519.320079 0 ] (cb109-1) [ 571 0 R /XYZ 101.433071 517.623057 0 ] (cb112) [ 576 0 R /XYZ 84.259843 459.320079 0 ] (cb112-1) [ 576 0 R /XYZ 101.433071 457.623057 0 ] (cb115) [ 581 0 R /XYZ 84.259843 373.070079 0 ] (cb115-1) [ 581 0 R /XYZ 101.433071 371.373057 0 ] (cb118) [ 586 0 R /XYZ 84.259843 294.320079 0 ] (cb118-1) [ 586 0 R /XYZ 101.433071 292.623057 0 ] (cb121) [ 591 0 R /XYZ 84.259843 219.320079 0 ] (cb121-1) [ 591 0 R /XYZ 101.433071 217.623057 0 ] (cb124) [ 596 0 R /XYZ 84.259843 125.570079 0 ] (cb124-1) [ 596 0 R /XYZ 101.433071 123.873057 0 ] (cb127) [ 603 0 R /XYZ 84.259843 799.370079 0 ] (cb127-1) [ 603 0 R /XYZ 101.433071 797.673057 0 ] (cb13) [ 325 0 R /XYZ 84.259843 547.070079 0 ] (cb13-1) [ 325 0 R /XYZ 101.433071 545.373057 0 ] (cb130) [ 608 0 R /XYZ 84.259843 685.370079 0 ] (cb130-1) [ 608 0 R /XYZ 101.433071 683.673057 0 ] (cb133) [ 613 0 R /XYZ 84.259843 575.570079 0 ] (cb133-1) [ 613 0 R /XYZ 101.433071 573.873057 0 ] (cb136) [ 618 0 R /XYZ 84.259843 485.570079 0 ] (cb136-1) [ 618 0 R /XYZ 101.433071 483.873057 0 ] (cb139) [ 623 0 R /XYZ 84.259843 391.820079 0 ] (cb139-1) [ 623 0 R /XYZ 101.433071 390.123057 0 ] (cb142) [ 628 0 R /XYZ 84.259843 279.320079 0 ] (cb142-1) [ 628 0 R /XYZ 101.433071 277.623057 0 ] (cb145) [ 633 0 R /XYZ 84.259843 185.570079 0 ] (cb145-1) [ 633 0 R /XYZ 101.433071 183.873057 0 ] (cb148) [ 638 0 R /XYZ 84.259843 110.570079 0 ] (cb148-1) [ 638 0 R /XYZ 101.433071 108.873057 0 ] (cb151) [ 645 0 R /XYZ 84.259843 799.370079 0 ] (cb151-1) [ 645 0 R /XYZ 101.433071 797.673057 0 ] (cb154) [ 645 0 R /XYZ 84.259843 332.176036 0 ] (cb154-1) [ 645 0 R /XYZ 101.433071 330.479014 0 ] (cb157) [ 653 0 R /XYZ 84.259843 535.251496 0 ] (cb157-1) [ 653 0 R /XYZ 101.433071 533.554475 0 ] (cb16) [ 325 0 R /XYZ 84.259843 195.929014 0 ] (cb16-1) [ 325 0 R /XYZ 101.433071 194.231993 0 ] (cb160) [ 656 0 R /XYZ 84.259843 463.070079 0 ] (cb160-1) [ 656 0 R /XYZ 101.433071 461.373057 0 ] (cb163) [ 659 0 R /XYZ 84.259843 388.070079 0 ] (cb163-1) [ 659 0 R /XYZ 101.433071 386.373057 0 ] (cb166) [ 662 0 R /XYZ 84.259843 298.070079 0 ] (cb166-1) [ 662 0 R /XYZ 101.433071 296.373057 0 ] (cb169) [ 665 0 R /XYZ 84.259843 219.320079 0 ] (cb169-1) [ 665 0 R /XYZ 101.433071 217.623057 0 ] (cb172) [ 670 0 R /XYZ 84.259843 700.370079 0 ] (cb172-1) [ 670 0 R /XYZ 101.433071 698.673057 0 ] (cb175) [ 675 0 R /XYZ 84.259843 565.251496 0 ] (cb175-1) [ 675 0 R /XYZ 101.433071 563.554475 0 ] (cb178) [ 675 0 R /XYZ 84.259843 158.254475 0 ] (cb178-1) [ 675 0 R /XYZ 101.433071 156.557453 0 ] (cb181) [ 681 0 R /XYZ 84.259843 252.651496 0 ] (cb181-1) [ 681 0 R /XYZ 101.433071 250.954475 0 ] (cb184) [ 686 0 R /XYZ 84.259843 246.470079 0 ] (cb184-1) [ 686 0 R /XYZ 101.433071 244.773057 0 ] (cb187) [ 691 0 R /XYZ 84.259843 466.820079 0 ] (cb187-1) [ 691 0 R /XYZ 101.433071 465.123057 0 ] (cb19) [ 329 0 R /XYZ 84.259843 580.820079 0 ] (cb19-1) [ 329 0 R /XYZ 101.433071 579.123057 0 ] (cb190) [ 698 0 R /XYZ 84.259843 595.251496 0 ] (cb190-1) [ 698 0 R /XYZ 101.433071 593.554475 0 ] (cb193) [ 701 0 R /XYZ 84.259843 529.251496 0 ] (cb193-1) [ 701 0 R /XYZ 101.433071 527.554475 0 ] (cb195) [ 704 0 R /XYZ 84.259843 799.370079 0 ] (cb195-1) [ 704 0 R /XYZ 101.433071 797.673057 0 ] (cb198) [ 704 0 R /XYZ 84.259843 429.479014 0 ] (cb198-1) [ 704 0 R /XYZ 101.433071 427.781993 0 ] (cb201) [ 708 0 R /XYZ 84.259843 799.370079 0 ] (cb201-1) [ 708 0 R /XYZ 101.433071 797.673057 0 ] (cb204) [ 708 0 R /XYZ 84.259843 448.229014 0 ] (cb204-1) [ 708 0 R /XYZ 101.433071 446.531993 0 ] (cb207) [ 708 0 R /XYZ 84.259843 112.087950 0 ] (cb207-1) [ 708 0 R /XYZ 101.433071 110.390928 0 ] (cb208) [ 713 0 R /XYZ 84.259843 658.970079 0 ] (cb208-1) [ 713 0 R /XYZ 101.433071 657.273057 0 ] (cb211) [ 713 0 R /XYZ 84.259843 307.829014 0 ] (cb211-1) [ 713 0 R /XYZ 101.433071 306.131993 0 ] (cb214) [ 717 0 R /XYZ 84.259843 643.970079 0 ] (cb214-1) [ 717 0 R /XYZ 101.433071 642.273057 0 ] (cb217) [ 720 0 R /XYZ 84.259843 490.251496 0 ] (cb217-1) [ 720 0 R /XYZ 101.433071 488.554475 0 ] (cb218) [ 720 0 R /XYZ 84.259843 429.304475 0 ] (cb218-1) [ 720 0 R /XYZ 101.433071 427.607453 0 ] (cb22) [ 329 0 R /XYZ 84.259843 229.679014 0 ] (cb22-1) [ 329 0 R /XYZ 101.433071 227.981993 0 ] (cb221) [ 724 0 R /XYZ 84.259843 305.570079 0 ] (cb221-1) [ 724 0 R /XYZ 101.433071 303.873057 0 ] (cb222) [ 724 0 R /XYZ 84.259843 244.623057 0 ] (cb222-1) [ 724 0 R /XYZ 101.433071 242.926036 0 ] (cb225) [ 728 0 R /XYZ 84.259843 455.570079 0 ] (cb225-1) [ 728 0 R /XYZ 101.433071 453.873057 0 ] (cb226) [ 728 0 R /XYZ 84.259843 394.623057 0 ] (cb226-1) [ 728 0 R /XYZ 101.433071 392.926036 0 ] (cb229) [ 732 0 R /XYZ 84.259843 583.970079 0 ] (cb229-1) [ 732 0 R /XYZ 101.433071 582.273057 0 ] (cb230) [ 732 0 R /XYZ 84.259843 523.023057 0 ] (cb230-1) [ 732 0 R /XYZ 101.433071 521.326036 0 ] (cb233) [ 736 0 R /XYZ 84.259843 384.320079 0 ] (cb233-1) [ 736 0 R /XYZ 101.433071 382.623057 0 ] (cb234) [ 736 0 R /XYZ 84.259843 323.373057 0 ] (cb234-1) [ 736 0 R /XYZ 101.433071 321.676036 0 ] (cb237) [ 740 0 R /XYZ 84.259843 174.320079 0 ] (cb237-1) [ 740 0 R /XYZ 101.433071 172.623057 0 ] (cb238) [ 740 0 R /XYZ 84.259843 113.373057 0 ] (cb238-1) [ 740 0 R /XYZ 101.433071 111.676036 0 ] (cb241) [ 744 0 R /XYZ 84.259843 328.820079 0 ] (cb241-1) [ 744 0 R /XYZ 101.433071 327.123057 0 ] (cb242) [ 744 0 R /XYZ 84.259843 267.873057 0 ] (cb242-1) [ 744 0 R /XYZ 101.433071 266.176036 0 ] (cb245) [ 748 0 R /XYZ 84.259843 133.070079 0 ] (cb245-1) [ 748 0 R /XYZ 101.433071 131.373057 0 ] (cb246) [ 751 0 R /XYZ 84.259843 583.970079 0 ] (cb246-1) [ 751 0 R /XYZ 101.433071 582.273057 0 ] (cb247) [ 751 0 R /XYZ 84.259843 523.023057 0 ] (cb247-1) [ 751 0 R /XYZ 101.433071 521.326036 0 ] (cb25) [ 333 0 R /XYZ 84.259843 622.820079 0 ] (cb25-1) [ 333 0 R /XYZ 101.433071 621.123057 0 ] (cb250) [ 755 0 R /XYZ 84.259843 369.320079 0 ] (cb250-1) [ 755 0 R /XYZ 101.433071 367.623057 0 ] (cb251) [ 755 0 R /XYZ 84.259843 308.373057 0 ] (cb251-1) [ 755 0 R /XYZ 101.433071 306.676036 0 ] (cb254) [ 759 0 R /XYZ 84.259843 159.320079 0 ] (cb254-1) [ 759 0 R /XYZ 101.433071 157.623057 0 ] (cb255) [ 759 0 R /XYZ 84.259843 98.373057 0 ] (cb255-1) [ 759 0 R /XYZ 101.433071 96.676036 0 ] (cb258) [ 765 0 R /XYZ 84.259843 715.370079 0 ] (cb258-1) [ 765 0 R /XYZ 101.433071 713.673057 0 ] (cb259) [ 765 0 R /XYZ 84.259843 654.423057 0 ] (cb259-1) [ 765 0 R /XYZ 101.433071 652.726036 0 ] (cb26) [ 333 0 R /XYZ 84.259843 446.073057 0 ] (cb26-1) [ 333 0 R /XYZ 101.433071 444.376036 0 ] (cb262) [ 769 0 R /XYZ 84.259843 485.570079 0 ] (cb262-1) [ 769 0 R /XYZ 101.433071 483.873057 0 ] (cb263) [ 769 0 R /XYZ 84.259843 424.623057 0 ] (cb263-1) [ 769 0 R /XYZ 101.433071 422.926036 0 ] (cb266) [ 777 0 R /XYZ 84.259843 768.620079 0 ] (cb266-1) [ 777 0 R /XYZ 101.433071 766.923057 0 ] (cb266-10) [ 777 0 R /XYZ 99.933071 596.399864 0 ] (cb266-11) [ 777 0 R /XYZ 99.933071 577.452842 0 ] (cb266-12) [ 777 0 R /XYZ 99.933071 482.717735 0 ] (cb266-13) [ 777 0 R /XYZ 99.933071 463.770714 0 ] (cb266-14) [ 777 0 R /XYZ 99.933071 444.823692 0 ] (cb266-15) [ 777 0 R /XYZ 99.933071 425.876671 0 ] (cb266-16) [ 777 0 R /XYZ 99.933071 406.929649 0 ] (cb266-17) [ 777 0 R /XYZ 99.933071 387.982628 0 ] (cb266-18) [ 777 0 R /XYZ 99.933071 350.088585 0 ] (cb266-19) [ 777 0 R /XYZ 99.933071 331.141563 0 ] (cb266-2) [ 777 0 R /XYZ 99.933071 747.976036 0 ] (cb266-20) [ 777 0 R /XYZ 99.933071 198.512413 0 ] (cb266-21) [ 777 0 R /XYZ 99.933071 179.565391 0 ] (cb266-22) [ 777 0 R /XYZ 99.933071 160.618370 0 ] (cb266-23) [ 777 0 R /XYZ 99.933071 103.777305 0 ] (cb266-24) [ 802 0 R /XYZ 99.933071 799.173057 0 ] (cb266-25) [ 802 0 R /XYZ 99.933071 780.226036 0 ] (cb266-26) [ 802 0 R /XYZ 99.933071 761.279014 0 ] (cb266-27) [ 802 0 R /XYZ 99.933071 742.331993 0 ] (cb266-28) [ 802 0 R /XYZ 99.933071 723.384971 0 ] (cb266-29) [ 802 0 R /XYZ 99.933071 704.437950 0 ] (cb266-3) [ 777 0 R /XYZ 99.933071 729.029014 0 ] (cb266-30) [ 802 0 R /XYZ 99.933071 685.490928 0 ] (cb266-31) [ 802 0 R /XYZ 99.933071 666.543907 0 ] (cb266-4) [ 777 0 R /XYZ 99.933071 710.081993 0 ] (cb266-5) [ 777 0 R /XYZ 99.933071 691.134971 0 ] (cb266-6) [ 777 0 R /XYZ 99.933071 672.187950 0 ] (cb266-7) [ 777 0 R /XYZ 99.933071 653.240928 0 ] (cb266-8) [ 777 0 R /XYZ 99.933071 634.293907 0 ] (cb266-9) [ 777 0 R /XYZ 99.933071 615.346885 0 ] (cb267) [ 802 0 R /XYZ 84.259843 607.293907 0 ] (cb267-1) [ 802 0 R /XYZ 101.433071 605.596885 0 ] (cb27) [ 333 0 R /XYZ 84.259843 239.326036 0 ] (cb27-1) [ 333 0 R /XYZ 101.433071 237.629014 0 ] (cb270) [ 813 0 R /XYZ 84.259843 565.251496 0 ] (cb270-1) [ 813 0 R /XYZ 101.433071 563.554475 0 ] (cb273) [ 813 0 R /XYZ 84.259843 233.057453 0 ] (cb273-1) [ 813 0 R /XYZ 101.433071 231.360432 0 ] (cb276) [ 817 0 R /XYZ 84.259843 607.820079 0 ] (cb276-1) [ 817 0 R /XYZ 101.433071 606.123057 0 ] (cb279) [ 817 0 R /XYZ 84.259843 256.679014 0 ] (cb279-1) [ 817 0 R /XYZ 101.433071 254.981993 0 ] (cb282) [ 821 0 R /XYZ 84.259843 643.970079 0 ] (cb282-1) [ 821 0 R /XYZ 101.433071 642.273057 0 ] (cb285) [ 821 0 R /XYZ 84.259843 258.881993 0 ] (cb285-1) [ 821 0 R /XYZ 101.433071 257.184971 0 ] (cb288) [ 825 0 R /XYZ 84.259843 607.820079 0 ] (cb288-1) [ 825 0 R /XYZ 101.433071 606.123057 0 ] (cb291) [ 828 0 R /XYZ 84.259843 514.251496 0 ] (cb291-1) [ 828 0 R /XYZ 101.433071 512.554475 0 ] (cb294) [ 828 0 R /XYZ 84.259843 174.360432 0 ] (cb294-1) [ 828 0 R /XYZ 101.433071 172.663410 0 ] (cb294-10) [ 836 0 R /XYZ 99.933071 723.384971 0 ] (cb294-11) [ 836 0 R /XYZ 99.933071 704.437950 0 ] (cb294-12) [ 836 0 R /XYZ 99.933071 685.490928 0 ] (cb294-13) [ 836 0 R /XYZ 99.933071 628.649864 0 ] (cb294-14) [ 836 0 R /XYZ 99.933071 609.702842 0 ] (cb294-15) [ 836 0 R /XYZ 99.933071 590.755821 0 ] (cb294-16) [ 836 0 R /XYZ 99.933071 571.808799 0 ] (cb294-17) [ 836 0 R /XYZ 99.933071 552.861778 0 ] (cb294-18) [ 836 0 R /XYZ 99.933071 533.914756 0 ] (cb294-19) [ 836 0 R /XYZ 99.933071 514.967735 0 ] (cb294-2) [ 828 0 R /XYZ 99.933071 153.716389 0 ] (cb294-3) [ 828 0 R /XYZ 99.933071 134.769367 0 ] (cb294-4) [ 828 0 R /XYZ 99.933071 115.822346 0 ] (cb294-5) [ 828 0 R /XYZ 99.933071 96.875324 0 ] (cb294-6) [ 836 0 R /XYZ 99.933071 799.173057 0 ] (cb294-7) [ 836 0 R /XYZ 99.933071 780.226036 0 ] (cb294-8) [ 836 0 R /XYZ 99.933071 761.279014 0 ] (cb294-9) [ 836 0 R /XYZ 99.933071 742.331993 0 ] (cb295) [ 836 0 R /XYZ 84.259843 455.717735 0 ] (cb295-1) [ 836 0 R /XYZ 101.433071 454.020714 0 ] (cb30) [ 338 0 R /XYZ 84.259843 628.970079 0 ] (cb30-1) [ 338 0 R /XYZ 101.433071 627.273057 0 ] (cb33) [ 338 0 R /XYZ 84.259843 315.723057 0 ] (cb33-1) [ 338 0 R /XYZ 101.433071 314.026036 0 ] (cb36) [ 342 0 R /XYZ 84.259843 715.370079 0 ] (cb36-1) [ 342 0 R /XYZ 101.433071 713.673057 0 ] (cb39) [ 342 0 R /XYZ 84.259843 398.176036 0 ] (cb39-1) [ 342 0 R /XYZ 101.433071 396.479014 0 ] (cb4) [ 317 0 R /XYZ 84.259843 197.057453 0 ] (cb4-1) [ 317 0 R /XYZ 101.433071 195.360432 0 ] (cb42) [ 346 0 R /XYZ 84.259843 799.370079 0 ] (cb42-1) [ 346 0 R /XYZ 101.433071 797.673057 0 ] (cb45) [ 346 0 R /XYZ 84.259843 467.176036 0 ] (cb45-1) [ 346 0 R /XYZ 101.433071 465.479014 0 ] (cb48) [ 346 0 R /XYZ 84.259843 134.981993 0 ] (cb48-1) [ 346 0 R /XYZ 101.433071 133.284971 0 ] (cb51) [ 351 0 R /XYZ 84.259843 520.070079 0 ] (cb51-1) [ 351 0 R /XYZ 101.433071 518.373057 0 ] (cb54) [ 351 0 R /XYZ 84.259843 203.073057 0 ] (cb54-1) [ 351 0 R /XYZ 101.433071 201.376036 0 ] (cb54-10) [ 358 0 R /XYZ 99.933071 704.437950 0 ] (cb54-11) [ 358 0 R /XYZ 99.933071 685.490928 0 ] (cb54-12) [ 358 0 R /XYZ 99.933071 666.543907 0 ] (cb54-13) [ 358 0 R /XYZ 99.933071 647.596885 0 ] (cb54-14) [ 358 0 R /XYZ 99.933071 628.649864 0 ] (cb54-15) [ 358 0 R /XYZ 99.933071 609.702842 0 ] (cb54-16) [ 358 0 R /XYZ 99.933071 590.755821 0 ] (cb54-17) [ 358 0 R /XYZ 99.933071 571.808799 0 ] (cb54-18) [ 358 0 R /XYZ 99.933071 552.861778 0 ] (cb54-19) [ 358 0 R /XYZ 99.933071 533.914756 0 ] (cb54-2) [ 351 0 R /XYZ 99.933071 182.429014 0 ] (cb54-20) [ 358 0 R /XYZ 99.933071 514.967735 0 ] (cb54-21) [ 358 0 R /XYZ 99.933071 496.020714 0 ] (cb54-22) [ 358 0 R /XYZ 99.933071 477.073692 0 ] (cb54-23) [ 358 0 R /XYZ 99.933071 458.126671 0 ] (cb54-24) [ 358 0 R /XYZ 99.933071 439.179649 0 ] (cb54-25) [ 358 0 R /XYZ 99.933071 420.232628 0 ] (cb54-26) [ 358 0 R /XYZ 99.933071 401.285606 0 ] (cb54-27) [ 358 0 R /XYZ 99.933071 382.338585 0 ] (cb54-28) [ 358 0 R /XYZ 99.933071 363.391563 0 ] (cb54-29) [ 358 0 R /XYZ 99.933071 344.444542 0 ] (cb54-3) [ 351 0 R /XYZ 99.933071 163.481993 0 ] (cb54-30) [ 358 0 R /XYZ 99.933071 325.497520 0 ] (cb54-31) [ 358 0 R /XYZ 99.933071 306.550499 0 ] (cb54-32) [ 358 0 R /XYZ 99.933071 287.603477 0 ] (cb54-33) [ 358 0 R /XYZ 99.933071 268.656456 0 ] (cb54-34) [ 358 0 R /XYZ 99.933071 249.709434 0 ] (cb54-35) [ 358 0 R /XYZ 99.933071 230.762413 0 ] (cb54-36) [ 358 0 R /XYZ 99.933071 211.815391 0 ] (cb54-37) [ 358 0 R /XYZ 99.933071 192.868370 0 ] (cb54-38) [ 358 0 R /XYZ 99.933071 173.921348 0 ] (cb54-39) [ 358 0 R /XYZ 99.933071 154.974327 0 ] (cb54-4) [ 351 0 R /XYZ 99.933071 125.587950 0 ] (cb54-40) [ 358 0 R /XYZ 99.933071 136.027305 0 ] (cb54-41) [ 358 0 R /XYZ 99.933071 117.080284 0 ] (cb54-42) [ 358 0 R /XYZ 99.933071 98.133262 0 ] (cb54-43) [ 398 0 R /XYZ 99.933071 799.173057 0 ] (cb54-44) [ 398 0 R /XYZ 99.933071 780.226036 0 ] (cb54-45) [ 398 0 R /XYZ 99.933071 761.279014 0 ] (cb54-46) [ 398 0 R /XYZ 99.933071 742.331993 0 ] (cb54-47) [ 398 0 R /XYZ 99.933071 723.384971 0 ] (cb54-48) [ 398 0 R /XYZ 99.933071 704.437950 0 ] (cb54-49) [ 398 0 R /XYZ 99.933071 685.490928 0 ] (cb54-5) [ 358 0 R /XYZ 99.933071 799.173057 0 ] (cb54-50) [ 398 0 R /XYZ 99.933071 666.543907 0 ] (cb54-51) [ 398 0 R /XYZ 99.933071 647.596885 0 ] (cb54-52) [ 398 0 R /XYZ 99.933071 628.649864 0 ] (cb54-53) [ 398 0 R /XYZ 99.933071 590.755821 0 ] (cb54-54) [ 398 0 R /XYZ 99.933071 571.808799 0 ] (cb54-55) [ 398 0 R /XYZ 99.933071 552.861778 0 ] (cb54-56) [ 398 0 R /XYZ 99.933071 533.914756 0 ] (cb54-57) [ 398 0 R /XYZ 99.933071 514.967735 0 ] (cb54-58) [ 398 0 R /XYZ 99.933071 496.020714 0 ] (cb54-59) [ 398 0 R /XYZ 99.933071 477.073692 0 ] (cb54-6) [ 358 0 R /XYZ 99.933071 780.226036 0 ] (cb54-60) [ 398 0 R /XYZ 99.933071 458.126671 0 ] (cb54-61) [ 398 0 R /XYZ 99.933071 439.179649 0 ] (cb54-7) [ 358 0 R /XYZ 99.933071 761.279014 0 ] (cb54-8) [ 358 0 R /XYZ 99.933071 742.331993 0 ] (cb54-9) [ 358 0 R /XYZ 99.933071 723.384971 0 ] (cb55) [ 398 0 R /XYZ 84.259843 379.929649 0 ] (cb55-1) [ 398 0 R /XYZ 101.433071 378.232628 0 ] (cb56) [ 398 0 R /XYZ 84.259843 165.485606 0 ] (cb56-1) [ 398 0 R /XYZ 101.433071 163.788585 0 ] (cb56-10) [ 423 0 R /XYZ 99.933071 666.543907 0 ] (cb56-11) [ 423 0 R /XYZ 99.933071 647.596885 0 ] (cb56-12) [ 423 0 R /XYZ 99.933071 628.649864 0 ] (cb56-13) [ 423 0 R /XYZ 99.933071 609.702842 0 ] (cb56-14) [ 423 0 R /XYZ 99.933071 590.755821 0 ] (cb56-15) [ 423 0 R /XYZ 99.933071 571.808799 0 ] (cb56-16) [ 423 0 R /XYZ 99.933071 552.861778 0 ] (cb56-17) [ 423 0 R /XYZ 99.933071 533.914756 0 ] (cb56-18) [ 423 0 R /XYZ 99.933071 514.967735 0 ] (cb56-19) [ 423 0 R /XYZ 99.933071 496.020714 0 ] (cb56-2) [ 398 0 R /XYZ 99.933071 144.841563 0 ] (cb56-20) [ 423 0 R /XYZ 99.933071 477.073692 0 ] (cb56-21) [ 423 0 R /XYZ 99.933071 458.126671 0 ] (cb56-22) [ 423 0 R /XYZ 99.933071 439.179649 0 ] (cb56-23) [ 423 0 R /XYZ 99.933071 420.232628 0 ] (cb56-24) [ 423 0 R /XYZ 99.933071 401.285606 0 ] (cb56-25) [ 423 0 R /XYZ 99.933071 382.338585 0 ] (cb56-26) [ 423 0 R /XYZ 99.933071 363.391563 0 ] (cb56-27) [ 423 0 R /XYZ 99.933071 344.444542 0 ] (cb56-28) [ 423 0 R /XYZ 99.933071 325.497520 0 ] (cb56-29) [ 423 0 R /XYZ 99.933071 306.550499 0 ] (cb56-3) [ 398 0 R /XYZ 99.933071 125.894542 0 ] (cb56-30) [ 423 0 R /XYZ 99.933071 287.603477 0 ] (cb56-31) [ 423 0 R /XYZ 99.933071 268.656456 0 ] (cb56-32) [ 423 0 R /XYZ 99.933071 249.709434 0 ] (cb56-33) [ 423 0 R /XYZ 99.933071 230.762413 0 ] (cb56-34) [ 423 0 R /XYZ 99.933071 211.815391 0 ] (cb56-35) [ 423 0 R /XYZ 99.933071 192.868370 0 ] (cb56-36) [ 423 0 R /XYZ 99.933071 173.921348 0 ] (cb56-37) [ 423 0 R /XYZ 99.933071 154.974327 0 ] (cb56-38) [ 423 0 R /XYZ 99.933071 136.027305 0 ] (cb56-39) [ 423 0 R /XYZ 99.933071 117.080284 0 ] (cb56-4) [ 423 0 R /XYZ 99.933071 799.173057 0 ] (cb56-40) [ 423 0 R /XYZ 99.933071 98.133262 0 ] (cb56-41) [ 462 0 R /XYZ 99.933071 799.173057 0 ] (cb56-42) [ 462 0 R /XYZ 99.933071 780.226036 0 ] (cb56-43) [ 462 0 R /XYZ 99.933071 761.279014 0 ] (cb56-44) [ 462 0 R /XYZ 99.933071 742.331993 0 ] (cb56-45) [ 462 0 R /XYZ 99.933071 723.384971 0 ] (cb56-46) [ 462 0 R /XYZ 99.933071 704.437950 0 ] (cb56-47) [ 462 0 R /XYZ 99.933071 685.490928 0 ] (cb56-48) [ 462 0 R /XYZ 99.933071 666.543907 0 ] (cb56-49) [ 462 0 R /XYZ 99.933071 647.596885 0 ] (cb56-5) [ 423 0 R /XYZ 99.933071 761.279014 0 ] (cb56-50) [ 462 0 R /XYZ 99.933071 628.649864 0 ] (cb56-51) [ 462 0 R /XYZ 99.933071 609.702842 0 ] (cb56-52) [ 462 0 R /XYZ 99.933071 590.755821 0 ] (cb56-53) [ 462 0 R /XYZ 99.933071 552.861778 0 ] (cb56-54) [ 462 0 R /XYZ 99.933071 533.914756 0 ] (cb56-55) [ 462 0 R /XYZ 99.933071 514.967735 0 ] (cb56-56) [ 462 0 R /XYZ 99.933071 496.020714 0 ] (cb56-57) [ 462 0 R /XYZ 99.933071 477.073692 0 ] (cb56-58) [ 462 0 R /XYZ 99.933071 458.126671 0 ] (cb56-59) [ 462 0 R /XYZ 99.933071 439.179649 0 ] (cb56-6) [ 423 0 R /XYZ 99.933071 742.331993 0 ] (cb56-60) [ 462 0 R /XYZ 99.933071 420.232628 0 ] (cb56-61) [ 462 0 R /XYZ 99.933071 401.285606 0 ] (cb56-7) [ 423 0 R /XYZ 99.933071 723.384971 0 ] (cb56-8) [ 423 0 R /XYZ 99.933071 704.437950 0 ] (cb56-9) [ 423 0 R /XYZ 99.933071 685.490928 0 ] (cb57) [ 462 0 R /XYZ 84.259843 342.035606 0 ] (cb57-1) [ 462 0 R /XYZ 101.433071 340.338585 0 ] (cb60) [ 486 0 R /XYZ 84.259843 565.251496 0 ] (cb60-1) [ 486 0 R /XYZ 101.433071 563.554475 0 ] (cb61) [ 486 0 R /XYZ 84.259843 343.504475 0 ] (cb61-1) [ 486 0 R /XYZ 101.433071 341.807453 0 ] (cb64) [ 492 0 R /XYZ 84.259843 241.820079 0 ] (cb64-1) [ 492 0 R /XYZ 101.433071 240.123057 0 ] (cb67) [ 497 0 R /XYZ 84.259843 178.070079 0 ] (cb67-1) [ 497 0 R /XYZ 101.433071 176.373057 0 ] (cb7) [ 321 0 R /XYZ 84.259843 565.820079 0 ] (cb7-1) [ 321 0 R /XYZ 101.433071 564.123057 0 ] (cb70) [ 504 0 R /XYZ 84.259843 799.370079 0 ] (cb70-1) [ 504 0 R /XYZ 101.433071 797.673057 0 ] (cb73) [ 509 0 R /XYZ 84.259843 670.370079 0 ] (cb73-1) [ 509 0 R /XYZ 101.433071 668.673057 0 ] (cb76) [ 514 0 R /XYZ 84.259843 560.570079 0 ] (cb76-1) [ 514 0 R /XYZ 101.433071 558.873057 0 ] (cb79) [ 519 0 R /XYZ 84.259843 481.820079 0 ] (cb79-1) [ 519 0 R /XYZ 101.433071 480.123057 0 ] (cb82) [ 524 0 R /XYZ 84.259843 406.820079 0 ] (cb82-1) [ 524 0 R /XYZ 101.433071 405.123057 0 ] (cb85) [ 529 0 R /XYZ 84.259843 316.820079 0 ] (cb85-1) [ 529 0 R /XYZ 101.433071 315.123057 0 ] (cb86) [ 529 0 R /XYZ 84.259843 110.073057 0 ] (cb86-1) [ 529 0 R /XYZ 101.433071 108.376036 0 ] (cb89) [ 537 0 R /XYZ 84.259843 772.370079 0 ] (cb89-1) [ 537 0 R /XYZ 101.433071 770.673057 0 ] (cb90) [ 537 0 R /XYZ 84.259843 535.623057 0 ] (cb90-1) [ 537 0 R /XYZ 101.433071 533.926036 0 ] (cb91) [ 537 0 R /XYZ 84.259843 298.876036 0 ] (cb91-1) [ 537 0 R /XYZ 101.433071 297.179014 0 ] (cb94) [ 544 0 R /XYZ 84.259843 200.570079 0 ] (cb94-1) [ 544 0 R /XYZ 101.433071 198.873057 0 ] (cb97) [ 551 0 R /XYZ 84.259843 799.370079 0 ] (cb97-1) [ 551 0 R /XYZ 101.433071 797.673057 0 ] (cis-v1.6-kubernetes-benchmark---rancher-v2.6-rke2-with-kubernetes-v1.21-up-to-v1.23) [ 306 0 R /XYZ 84.259843 784.970079 0 ] (client-certificate-authentication-should-not-be-used-for-users-manual) [ 696 0 R /XYZ 84.259843 684.651496 0 ] (configure-image-provenance-using-imagepolicywebhook-admission-controller-manual) [ 855 0 R /XYZ 84.259843 684.651496 0 ] (consider-external-secret-storage-manual) [ 853 0 R /XYZ 84.259843 568.851496 0 ] (contentsbox) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (controller-manager) [ 653 0 R /XYZ 41.740157 784.430079 0 ] (controls) [ 313 0 R /XYZ 84.259843 570.381496 0 ] (create-administrative-boundaries-between-resources-using-namespaces-manual) [ 859 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-a-minimal-audit-policy-is-created-automated) [ 698 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-a-unique-certificate-authority-is-used-for-etcd-manual) [ 691 0 R /XYZ 84.259843 652.220079 0 ] (ensure-that-all-namespaces-have-network-policies-defined-automated) [ 828 0 R /XYZ 84.259843 318.510432 0 ] (ensure-that-default-service-accounts-are-not-actively-used.-automated) [ 775 0 R /XYZ 84.259843 206.451496 0 ] (ensure-that-encryption-providers-are-appropriately-configured-automated) [ 643 0 R /XYZ 84.259843 220.970079 0 ] (ensure-that-service-account-tokens-are-only-mounted-where-necessary-manual) [ 802 0 R /XYZ 84.259843 449.446885 0 ] (ensure-that-the---anonymous-auth-argument-is-set-to-false-manual) [ 486 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the---audit-log-maxage-argument-is-set-to-30-or-as-appropriate-automated) [ 586 0 R /XYZ 84.259843 464.720079 0 ] (ensure-that-the---audit-log-maxbackup-argument-is-set-to-10-or-as-appropriate-automated) [ 591 0 R /XYZ 84.259843 389.720079 0 ] (ensure-that-the---audit-log-maxsize-argument-is-set-to-100-or-as-appropriate-automated) [ 596 0 R /XYZ 84.259843 295.970079 0 ] (ensure-that-the---audit-log-path-argument-is-set-automated) [ 581 0 R /XYZ 84.259843 558.470079 0 ] (ensure-that-the---authorization-mode-argument-includes-node-automated) [ 519 0 R /XYZ 84.259843 652.220079 0 ] (ensure-that-the---authorization-mode-argument-includes-rbac-automated) [ 524 0 R /XYZ 84.259843 577.220079 0 ] (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated) [ 514 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated-1) [ 724 0 R /XYZ 84.259843 520.970079 0 ] (ensure-that-the---auto-tls-argument-is-not-set-to-true-automated) [ 681 0 R /XYZ 84.259843 408.051496 0 ] (ensure-that-the---basic-auth-file-argument-is-not-set-automated) [ 486 0 R /XYZ 84.259843 528.904475 0 ] (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated) [ 668 0 R /XYZ 84.259843 133.670079 0 ] (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated-1) [ 675 0 R /XYZ 84.259843 313.654475 0 ] (ensure-that-the---cert-file-and---key-file-arguments-are-set-as-appropriate-automated) [ 681 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated) [ 628 0 R /XYZ 84.259843 464.720079 0 ] (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated-1) [ 728 0 R /XYZ 84.259843 670.970079 0 ] (ensure-that-the---client-cert-auth-argument-is-set-to-true-automated) [ 681 0 R /XYZ 84.259843 538.851496 0 ] (ensure-that-the---encryption-provider-config-argument-is-set-as-appropriate-automated) [ 638 0 R /XYZ 84.259843 295.970079 0 ] (ensure-that-the---etcd-cafile-argument-is-set-as-appropriate-automated) [ 633 0 R /XYZ 84.259843 370.970079 0 ] (ensure-that-the---etcd-certfile-and---etcd-keyfile-arguments-are-set-as-appropriate-automated) [ 618 0 R /XYZ 84.259843 670.970079 0 ] (ensure-that-the---event-qps-argument-is-set-to-0-or-a-level-which-ensures-appropriate-event-capture-manual) [ 751 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the---hostname-override-argument-is-not-set-manual) [ 748 0 R /XYZ 84.259843 333.470079 0 ] (ensure-that-the---insecure-bind-address-argument-is-not-set-automated) [ 561 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the---insecure-port-argument-is-set-to-0-automated) [ 566 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the---kubeconfig-kubelet.conf-file-ownership-is-set-to-rootroot-automated) [ 708 0 R /XYZ 84.259843 603.629014 0 ] (ensure-that-the---kubeconfig-kubelet.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 704 0 R /XYZ 84.259843 214.987950 0 ] (ensure-that-the---kubelet-certificate-authority-argument-is-set-as-appropriate-automated) [ 507 0 R /XYZ 84.259843 164.720079 0 ] (ensure-that-the---kubelet-client-certificate-and---kubelet-client-key-arguments-are-set-as-appropriate-automated) [ 502 0 R /XYZ 84.259843 277.220079 0 ] (ensure-that-the---kubelet-https-argument-is-set-to-true-automated) [ 497 0 R /XYZ 84.259843 333.470079 0 ] (ensure-that-the---make-iptables-util-chains-argument-is-set-to-true-automated) [ 744 0 R /XYZ 84.259843 544.220079 0 ] (ensure-that-the---peer-auto-tls-argument-is-not-set-to-true-automated) [ 686 0 R /XYZ 84.259843 416.870079 0 ] (ensure-that-the---peer-cert-file-and---peer-key-file-arguments-are-set-as-appropriate-automated) [ 686 0 R /XYZ 84.259843 708.470079 0 ] (ensure-that-the---peer-client-cert-auth-argument-is-set-to-true-automated) [ 686 0 R /XYZ 84.259843 547.670079 0 ] (ensure-that-the---profiling-argument-is-set-to-false-automated) [ 576 0 R /XYZ 84.259843 614.720079 0 ] (ensure-that-the---profiling-argument-is-set-to-false-automated-1) [ 656 0 R /XYZ 84.259843 633.470079 0 ] (ensure-that-the---profiling-argument-is-set-to-false-automated-2) [ 675 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the---protect-kernel-defaults-argument-is-set-to-true-automated) [ 740 0 R /XYZ 84.259843 389.720079 0 ] (ensure-that-the---read-only-port-argument-is-set-to-0-automated) [ 732 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the---request-timeout-argument-is-set-as-appropriate-automated) [ 601 0 R /XYZ 84.259843 239.720079 0 ] (ensure-that-the---root-ca-file-argument-is-set-as-appropriate-automated) [ 665 0 R /XYZ 84.259843 389.720079 0 ] (ensure-that-the---rotate-certificates-argument-is-not-set-to-false-manual) [ 759 0 R /XYZ 84.259843 389.720079 0 ] (ensure-that-the---secure-port-argument-is-not-set-to-0-automated) [ 571 0 R /XYZ 84.259843 689.720079 0 ] (ensure-that-the---service-account-key-file-argument-is-set-as-appropriate-automated) [ 613 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the---service-account-lookup-argument-is-set-to-true-automated) [ 606 0 R /XYZ 84.259843 164.720079 0 ] (ensure-that-the---service-account-private-key-file-argument-is-set-as-appropriate-automated) [ 662 0 R /XYZ 84.259843 483.470079 0 ] (ensure-that-the---streaming-connection-idle-timeout-argument-is-not-set-to-0-automated) [ 736 0 R /XYZ 84.259843 614.720079 0 ] (ensure-that-the---terminated-pod-gc-threshold-argument-is-set-as-appropriate-automated) [ 653 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated) [ 623 0 R /XYZ 84.259843 577.220079 0 ] (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated-1) [ 755 0 R /XYZ 84.259843 614.720079 0 ] (ensure-that-the---token-auth-file-parameter-is-not-set-automated) [ 492 0 R /XYZ 84.259843 427.220079 0 ] (ensure-that-the---use-service-account-credentials-argument-is-set-to-true-automated) [ 659 0 R /XYZ 84.259843 558.470079 0 ] (ensure-that-the-admin.conf-file-ownership-is-set-to-rootroot-automated) [ 338 0 R /XYZ 84.259843 157.876036 0 ] (ensure-that-the-admin.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 338 0 R /XYZ 84.259843 471.123057 0 ] (ensure-that-the-admission-control-plugin-alwaysadmit-is-not-set-automated) [ 529 0 R /XYZ 84.259843 280.473057 0 ] (ensure-that-the-admission-control-plugin-alwayspullimages-is-set-manual) [ 535 0 R /XYZ 84.259843 202.220079 0 ] (ensure-that-the-admission-control-plugin-eventratelimit-is-set-manual) [ 529 0 R /XYZ 84.259843 502.220079 0 ] (ensure-that-the-admission-control-plugin-namespacelifecycle-is-set-automated) [ 544 0 R /XYZ 84.259843 370.970079 0 ] (ensure-that-the-admission-control-plugin-noderestriction-is-set-automated) [ 554 0 R /XYZ 84.259843 183.470079 0 ] (ensure-that-the-admission-control-plugin-podsecuritypolicy-is-set-automated) [ 549 0 R /XYZ 84.259843 295.970079 0 ] (ensure-that-the-admission-control-plugin-securitycontextdeny-is-set-if-podsecuritypolicy-is-not-used-manual) [ 537 0 R /XYZ 84.259843 736.023057 0 ] (ensure-that-the-admission-control-plugin-serviceaccount-is-set-automated) [ 537 0 R /XYZ 84.259843 499.276036 0 ] (ensure-that-the-anonymous-auth-argument-is-set-to-false-automated) [ 720 0 R /XYZ 84.259843 720.651496 0 ] (ensure-that-the-api-server-only-makes-use-of-strong-cryptographic-ciphers-manual) [ 645 0 R /XYZ 84.259843 547.576036 0 ] (ensure-that-the-api-server-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 317 0 R /XYZ 84.259843 352.457453 0 ] (ensure-that-the-api-server-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 317 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-audit-policy-covers-key-security-concerns-manual) [ 698 0 R /XYZ 84.259843 418.457453 0 ] (ensure-that-the-certificate-authorities-file-permissions-are-set-to-644-or-more-restrictive-manual) [ 708 0 R /XYZ 84.259843 252.487950 0 ] (ensure-that-the-client-certificate-authorities-file-ownership-is-set-to-rootroot-automated) [ 713 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the-cluster-admin-role-is-only-used-where-required-manual) [ 775 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-cni-in-use-supports-network-policies-automated) [ 828 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-container-network-interface-file-ownership-is-set-to-rootroot-manual) [ 333 0 R /XYZ 84.259843 586.473057 0 ] (ensure-that-the-container-network-interface-file-permissions-are-set-to-644-or-more-restrictive-manual) [ 333 0 R /XYZ 84.259843 763.220079 0 ] (ensure-that-the-controller-manager-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 321 0 R /XYZ 84.259843 351.131993 0 ] (ensure-that-the-controller-manager-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 321 0 R /XYZ 84.259843 736.220079 0 ] (ensure-that-the-controller-manager.conf-file-ownership-is-set-to-rootroot-automated) [ 346 0 R /XYZ 84.259843 290.381993 0 ] (ensure-that-the-controller-manager.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 346 0 R /XYZ 84.259843 622.576036 0 ] (ensure-that-the-etcd-data-directory-ownership-is-set-to-etcdetcd-automated) [ 338 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the-etcd-data-directory-permissions-are-set-to-700-or-more-restrictive-automated) [ 333 0 R /XYZ 84.259843 409.726036 0 ] (ensure-that-the-etcd-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 329 0 R /XYZ 84.259843 385.079014 0 ] (ensure-that-the-etcd-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 329 0 R /XYZ 84.259843 736.220079 0 ] (ensure-that-the-kubelet---config-configuration-file-has-permissions-set-to-644-or-more-restrictive-automated) [ 713 0 R /XYZ 84.259843 463.229014 0 ] (ensure-that-the-kubelet---config-configuration-file-ownership-is-set-to-rootroot-automated) [ 717 0 R /XYZ 84.259843 799.370079 0 ] (ensure-that-the-kubelet-only-makes-use-of-strong-cryptographic-ciphers-manual) [ 769 0 R /XYZ 84.259843 745.970079 0 ] (ensure-that-the-kubelet-service-file-ownership-is-set-to-rootroot-automated) [ 701 0 R /XYZ 84.259843 394.260432 0 ] (ensure-that-the-kubelet-service-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 701 0 R /XYZ 84.259843 684.651496 0 ] (ensure-that-the-kubernetes-pki-certificate-file-permissions-are-set-to-644-or-more-restrictive-manual) [ 351 0 R /XYZ 84.259843 362.223057 0 ] (ensure-that-the-kubernetes-pki-directory-and-file-ownership-is-set-to-rootroot-automated) [ 351 0 R /XYZ 84.259843 675.470079 0 ] (ensure-that-the-kubernetes-pki-key-file-permissions-are-set-to-600-manual) [ 398 0 R /XYZ 84.259843 324.635606 0 ] (ensure-that-the-proxy-kubeconfig-file-ownership-is-set-to-rootroot-manual) [ 704 0 R /XYZ 84.259843 584.879014 0 ] (ensure-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) [ 668 0 R /XYZ 84.259843 294.470079 0 ] (ensure-that-the-scheduler-pod-specification-file-ownership-is-set-to-rootroot-automated) [ 325 0 R /XYZ 84.259843 351.329014 0 ] (ensure-that-the-scheduler-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 325 0 R /XYZ 84.259843 702.470079 0 ] (ensure-that-the-scheduler.conf-file-ownership-is-set-to-rootroot-automated) [ 342 0 R /XYZ 84.259843 221.381993 0 ] (ensure-that-the-scheduler.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) [ 342 0 R /XYZ 84.259843 538.576036 0 ] (ensure-that-the-seccomp-profile-is-set-to-dockerdefault-in-your-pod-definitions-manual) [ 859 0 R /XYZ 84.259843 604.851496 0 ] (etcd-node-configuration-files) [ 681 0 R /XYZ 41.740157 784.430079 0 ] (extensible-admission-control) [ 855 0 R /XYZ 41.740157 784.430079 0 ] (general-policies) [ 859 0 R /XYZ 41.740157 784.430079 0 ] (header_bottom_text) [ 6 0 R /XYZ 85.009843 392.718898 0 ] (if-proxy-kubeconfig-file-exists-ensure-permissions-are-set-to-644-or-more-restrictive-manual) [ 701 0 R /XYZ 84.259843 263.460432 0 ] (kubelet) [ 720 0 R /XYZ 41.740157 784.430079 0 ] (logging) [ 698 0 R /XYZ 41.740157 784.430079 0 ] (master-node-configuration-files) [ 317 0 R /XYZ 41.740157 784.430079 0 ] (minimize-access-to-create-pods-manual) [ 775 0 R /XYZ 84.259843 307.251496 0 ] (minimize-access-to-secrets-manual) [ 775 0 R /XYZ 84.259843 523.851496 0 ] (minimize-the-admission-of-containers-wishing-to-share-the-host-ipc-namespace-automated) [ 817 0 R /XYZ 84.259843 763.220079 0 ] (minimize-the-admission-of-containers-wishing-to-share-the-host-network-namespace-automated) [ 817 0 R /XYZ 84.259843 412.079014 0 ] (minimize-the-admission-of-containers-wishing-to-share-the-host-process-id-namespace-automated) [ 813 0 R /XYZ 84.259843 388.457453 0 ] (minimize-the-admission-of-containers-with-added-capabilities-manual) [ 825 0 R /XYZ 84.259843 431.026036 0 ] (minimize-the-admission-of-containers-with-allowprivilegeescalation-automated) [ 821 0 R /XYZ 84.259843 799.370079 0 ] (minimize-the-admission-of-containers-with-capabilities-assigned-manual) [ 825 0 R /XYZ 84.259843 315.226036 0 ] (minimize-the-admission-of-containers-with-the-net_raw-capability-manual) [ 825 0 R /XYZ 84.259843 763.220079 0 ] (minimize-the-admission-of-privileged-containers-automated) [ 813 0 R /XYZ 84.259843 720.651496 0 ] (minimize-the-admission-of-root-containers-automated) [ 821 0 R /XYZ 84.259843 429.281993 0 ] (minimize-wildcard-use-in-roles-and-clusterroles-manual) [ 775 0 R /XYZ 84.259843 423.051496 0 ] (network-policies-and-cni) [ 828 0 R /XYZ 41.740157 784.430079 0 ] (overview) [ 306 0 R /XYZ 84.259843 704.822079 0 ] (pod-security-policies) [ 813 0 R /XYZ 41.740157 784.430079 0 ] (prefer-using-secrets-as-files-over-secrets-as-environment-variables-manual) [ 853 0 R /XYZ 84.259843 684.651496 0 ] (rbac-and-service-accounts) [ 775 0 R /XYZ 41.740157 784.430079 0 ] (scheduler) [ 675 0 R /XYZ 41.740157 784.430079 0 ] (secrets-management) [ 853 0 R /XYZ 41.740157 784.430079 0 ] (testing-controls-methodology) [ 306 0 R /XYZ 84.259843 169.826079 0 ] (the-default-namespace-should-not-be-used-manual) [ 859 0 R /XYZ 84.259843 193.251496 0 ] (the-v1.5.1-guide-skips-5.6-and-goes-from-5.5-to-5.7.-we-are-including-it-here-merely-for-explanation.) [ 857 0 R /XYZ 41.740157 784.430079 0 ] (title-block-header) [ 6 0 R /XYZ 84.259843 502.818898 0 ] (verify-that-the-rotatekubeletservercertificate-argument-is-set-to-true-manual) [ 763 0 R /XYZ 84.259843 187.970079 0 ] (worker-node-configuration-files) [ 701 0 R /XYZ 41.740157 784.430079 0 ] ] ->> ->> ->> -endobj -4 0 obj -<< -/ExtGState << -/a1.0 << -/ca 1 ->> -/A1.0 << -/CA 1 ->> ->> -/XObject << ->> -/Pattern << ->> -/Shading << ->> -/Font 1024 0 R ->> -endobj -5 0 obj -<< -/Filter /FlateDecode -/Length 2633 ->> -stream -x]\W%U 6!, r]8E~:kx9U:RTzY"WZIB͂GC>5X 9 st¯g{_9xNb>UZ%UJUΡ֔ Q3Ւݫ*̰2S KUj5꽪ÌT1̈=W;b:"f.P0R ԩBkb:PRJnLg%wLaKftŴU+E -Ԫ2]- ӉxW:"E"u 73I^$Tb TE*l);Na5[nLaKJը`R-R CvPp.1Zd ifQ VeH=+2DRd P- -#FbعT[c&؂%2(hknMzd,P$pa0(cpX` -bWu5XZ+ -Ea,0pWORl3AcSw5Je,0p(1`U0WBjM MMTAe,0p7enʒ M -c%?Bp<-,c=tI YHHK 2;ӠUƂ Ɔ壺bŌ}YX]*e,.  2ݘ0dpyCf,;-DR][c,. 4j#E8PƂ"wƂJVe,(-cmɞF$LJ -3+R;cAw=l2 ``@ Jk- tHgƂ*d `Uc,@bXPlє j-H }]h}`"cHZ7c,ì2]IUt2j82 - .1 1[U BK̙.$ٌt%؂l*c"4jIL5әx "c *M` 0Xb;3A2`fc,h-y Z-Ic|X c,RɌ8t"=6ԛ /l]&JfwL>GTP3[~~|_N{ߧ'e'ՊyDMv r|z ezvG7 /^~>^="}᫅#\7! ~|bޞWp74(q G\}v>Xŗ6hkx&Cfhg5TX1ɮ{0 -fү[|le?y9ƾ^^m^.z]>fWyn{mzc~.ex(|\Px6&nkk{Dq/}W玂q9.xi6DNswMƲ7~?R?#3Gu*՚_]A}mٳ!JcOgG^$n!rf'I~.ފ5݋b^/e:=="?oB\}vy\ e=cK.q20U-LSP)\vu8l|/m%N6^'ͩ+K8Mߧ.n?ڦ-DŽ' ϥOTm1FL7r.u"ѵa1~[5Y.6f>㉶J٪Gerums옣y+0 t'|hjr;SK狹tK-3o]34mLrX>Iz ڐ :d2d:l*ƴo,ՙS,L}U$}U][wD-Lu3lDVVKvmk2TcK=bq::C>b;.i!_Ukq~'$d LUj&> -endobj -7 0 obj -<< -/Filter /FlateDecode -/Length 3679 ->> -stream -x\[ܶ~_1vx 61 AчNPpпߏHJ3]7vҧ#;7V~Otz1)% L JGB NZ:(pUûvߺ4#ECғZ+s$?d>B:0i5'r}0SRD Sړ Ahu&['1w 5~mJ4ׯn< 8bBUءmwjSc{;;8wh`؁iҦڡCAvnsn=vhg}Ajccj !ls\63{>9-q [BtVQ\~~0[B/P|D\B}n mxɌ(w!#Mއhyp% P(f54AZomhM*L?v.D΂ء6C;\VZ6|.͍!v(e!vۡ]24C;;3v`QGC15BLΛ%n!z [Bʵh\~~0[B/P|D\B}*>I(Ƿ!j]`ivSûe8.H>D#>D#i=xڻFC{hx VCmsؘ͍v(edv!9c#C4ڏ}&\ء;hn QԘ 63{>;of-Do! kע*#x3(y^&N.F BRJ0!ĝaQdt2$N$pHtGCXga ~I tư!m' -w&x,A+CB[8$2dKVIzr$ϩa'qS2) -9Lz&L f28Hx08:`Fm](1zCNTI:k 2VAg1I IO:r:X%CwJKFTHDyݑjO٢t ̕aPYVI5>TSꠊ)I5CFyAjJ@T$pP(dC&8DZ-q: )A)D!'A^|#^2m%~HL{w})GsѴ}æ݂~'7XPcvn[+,HjD(.cZc2 87lNJYP-)#ɵ1-y :Z;(o)瀹78%̭ENK5&_PO'drm}U7O[$dZs[v=v|RK62<wtkXPt.iϊ|2] -vw؋jUnȾpnV1Esy`|LcJDxPlkUp%9M8mٌeىO޽]1-O~Ճ[TD'z6;kX~::fk%|sО95yfb VG9=zd'3 $hzp\|$3d{>{V$?=Lkrb^ ['|-ka$r@~be '>!qzN%?9"͵l<&Yyg1oOpS]>(?-7Kge癝>8gӰQѥߛO"f3-#LkΗ[c uɜXEKÎۏP--<~^g ')J;z{i>om]`91/[Ie_%ŇE.E]Ah~L}$w??Y><֐?ުH'Hyvkk~dowy:X>?SI0~ZpKvЮTNrlV'f7b@d]:곜/@>'*]PFC*$UGu)Ss%UQ5+wpӓjWkTmáZ\{Wg>_\ήK' 6VbH - ni~KS-Ft09cɤ]_S/}d^_wqj05v0db‹15lhK ֱRZǍaڵUKER URі1CxڰX'2jVS[n[U+4k#kgYt\u݈(NYi֩wR;n -b'lOmZMlqtװӼ3P`*hMxcΧ?5I Pm˲سuBM-\w}ݶ -.@-_o+#CBS4W4qT[dsْ Ts8> -endobj -9 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 671.061024 504.679134 638.361024 ] -/BS << -/W 0 ->> -/Dest (cis-v1.6-kubernetes-benchmark---rancher-v2.6-rke2-with-kubernetes-v1.21-up-to-v1.23) ->> -endobj -10 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.750423 648.111024 496.429134 633.111024 ] -/BS << -/W 0 ->> -/Dest (cis-v1.6-kubernetes-benchmark---rancher-v2.6-rke2-with-kubernetes-v1.21-up-to-v1.23) ->> -endobj -11 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 626.361024 504.679134 593.661024 ] -/BS << -/W 0 ->> -/Dest (controls) ->> -endobj -12 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 485.690364 618.411024 496.429134 603.411024 ] -/BS << -/W 0 ->> -/Dest (controls) ->> -endobj -13 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 581.661024 504.679134 548.961024 ] -/BS << -/W 0 ->> -/Dest (master-node-configuration-files) ->> -endobj -14 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 485.521907 573.711024 496.429134 558.711024 ] -/BS << -/W 0 ->> -/Dest (master-node-configuration-files) ->> -endobj -15 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 530.961024 498.679134 507.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -16 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 510.561024 491.179134 495.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -17 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 491.361024 498.679134 467.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -18 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 470.961024 491.179134 455.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -19 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 451.761024 498.679134 428.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -20 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 431.361024 491.179134 416.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -21 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 412.161024 498.679134 388.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -22 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 391.761024 491.179134 376.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -23 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 372.561024 498.679134 349.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -24 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 352.161024 491.179134 337.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -25 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 332.961024 498.679134 309.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -26 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 312.561024 491.179134 297.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -27 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 293.361024 498.679134 269.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -28 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 272.961024 491.179134 257.961024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -29 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 253.761024 498.679134 230.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -30 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 233.361024 491.179134 218.361024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-pod-specification-file-ownership-is-set-to-rootroot-automated) ->> -endobj -31 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 214.161024 498.679134 190.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -32 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 193.761024 491.179134 178.761024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -33 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 174.561024 498.679134 151.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-ownership-is-set-to-rootroot-manual) ->> -endobj -34 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 154.161024 491.179134 139.161024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-container-network-interface-file-ownership-is-set-to-rootroot-manual) ->> -endobj -35 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 134.961024 498.679134 111.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-permissions-are-set-to-700-or-more-restrictive-automated) ->> -endobj -36 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 114.561024 491.179134 99.561024 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-permissions-are-set-to-700-or-more-restrictive-automated) ->> -endobj -37 0 obj -<< -/Filter /FlateDecode -/Length 3697 ->> -stream -x\Y ~_1\.:A@$~0 %ʀ]Gts Vvf rsI1O%oBv? 9=;_?]w"WăO~VGtǻŔhA -(b"r -!^db@ X"x-،P|20$6C&&>%-}41 g LL S! LAF@#b3g,6/&́7B L1y#~ЋX1#~PĠ3#ƐfPA.ML@rc&J61ѻ9#~0͜$!#~0!b3%,FH C⧈B!/6by@ba@l?RmLtg#ƈP0>d#~$-LblďT'G\ƈ͌>1FQld#~H@MD>e#~7$l c$àDOV8(1D&81#ÜDOF1QIF%qdOqs2'8( 6Fl&dXqPj4&#~ l '#~ؘpNF8dLɈ -N:ɈqP#6GOш1qPJF2#6Sшqe0F?,GT<#~d%.0˔cIe Ke2ieV;y=/fp￙5QL*%,blK.E -cLUJ>$724E"\%;D\:4|:rb)M O]Kk1RS]zZ99F$7<ȇ-iC!y|._Lv%Kxyv>4"s>&;D-!WK9aż#mZg_2)(fF`a^M=L ʘc.`H-Lt!8ls&&KH 8ݬ  -<]D9\Sf0H!M-  _)M+Ũe/½.'%B,Eop&&"W:JFo$"zH_!\c0(5(G- i-Ξ BރW 2KKT+stpA@"ha,TdqIg)Y|r) !2:HpP(",70H)q6Bo~H 20:f`4(y -%$G= |Ix9A|ȎdL_” @,.L[\drR171X|_ iiKJγ̆ȱ̩ѠC@q. dv9iwd .q!p>1 ߽qП_TZFbzw? ]y qx/y|ע;?zhdte?=^>)P}"Zz oQT)ԪxL`RT2wU~!.:Ʃ tq&/(m_?~- ؉ ꣝X>={3KY{\'1}C:YL3w+&e{Kd#.c,KV~¼-;t`o=G6٩Wge|Z٦أMm;6-smݱK/v`X|UC⇓W#nroQm<ͺ\|] l~|~W.&;F nhN?%.Oesmw/!X-~̊9=l  }Qnӹo?/t-+6LM̔ª1s [qU,o3O ҡeU%FV=~:0L}뵐i`;OחJaXg]zq&b$U^MǗuc[2}@)ʛK1陦hR!t -y50EA"\ /K6Q-}???R;>x~n\|'ԗJٚUl+@6ok!I7KSΛ_?i45=M Rח{f1O_e/6S& -È -WŲ|)Cs],yY*fivG@b贄4KһM)Ba~7U+O"}SBَˋ0@ - W*nCt:lmܘJ zCrsl"2q7삧Ger7x!<\6kzM}.M*Bw{.ܤZy }q7k'تNԱ dעc+AJ5OT+k1kb-a?VB_溘[(߭Nn*^0;7][ũ1ܫ@b -O6h0) -]$ڪ;fOt0 sHEߴo._J~uǿGq\ǷHH«b҄-m!w1 mGu^+Zvtr 4x ̋m"Tn=R4Cjݑ܏QJShA?b8(;R,ݲc#j mkKX쨺ʦ^ V=F?:brVڛnm)Mq:NMܣ6ѧa3 cVց }ʚTmi-SRStoyd9GVV͖Mx {;%,g7iH˶ú:nnH3SO crg-vYR!ұt'(5D:"搇%>Ǿry^@[}k\ o;&Ɂrjy~4}yKs[mۯ cUt%>KH~qP -endstream -endobj -38 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 37 0 R -/Resources 4 0 R -/Annots [ 39 0 R 40 0 R 41 0 R 42 0 R 43 0 R 44 0 R 45 0 R 46 0 R 47 0 R 48 0 R 49 0 R 50 0 R 51 0 R 52 0 R 53 0 R 54 0 R 55 0 R 56 0 R 57 0 R 58 0 R 59 0 R 60 0 R 61 0 R 62 0 R 63 0 R 64 0 R 65 0 R 66 0 R 67 0 R 68 0 R 69 0 R 70 0 R 71 0 R 72 0 R 73 0 R 74 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -39 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-ownership-is-set-to-etcdetcd-automated) ->> -endobj -40 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-etcd-data-directory-ownership-is-set-to-etcdetcd-automated) ->> -endobj -41 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -42 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -43 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -44 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admin.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -45 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -46 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -47 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -48 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-scheduler.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -49 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -50 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -51 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -52 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-controller-manager.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -53 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-directory-and-file-ownership-is-set-to-rootroot-automated) ->> -endobj -54 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-directory-and-file-ownership-is-set-to-rootroot-automated) ->> -endobj -55 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 473.570079 498.679134 450.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-certificate-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -56 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 453.170079 491.179134 438.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-certificate-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -57 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 433.970079 498.679134 410.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-key-file-permissions-are-set-to-600-manual) ->> -endobj -58 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 413.570079 491.179134 398.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubernetes-pki-key-file-permissions-are-set-to-600-manual) ->> -endobj -59 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 394.370079 504.679134 361.670079 ] -/BS << -/W 0 ->> -/Dest (api-server) ->> -endobj -60 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.910335 386.420079 496.429134 371.420079 ] -/BS << -/W 0 ->> -/Dest (api-server) ->> -endobj -61 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 343.670079 498.679134 320.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---anonymous-auth-argument-is-set-to-false-manual) ->> -endobj -62 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 338.270079 491.179134 323.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---anonymous-auth-argument-is-set-to-false-manual) ->> -endobj -63 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 304.070079 498.679134 280.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---basic-auth-file-argument-is-not-set-automated) ->> -endobj -64 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 298.670079 491.179134 283.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---basic-auth-file-argument-is-not-set-automated) ->> -endobj -65 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 264.470079 498.679134 241.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---token-auth-file-parameter-is-not-set-automated) ->> -endobj -66 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 259.070079 491.179134 244.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---token-auth-file-parameter-is-not-set-automated) ->> -endobj -67 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 224.870079 498.679134 201.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-https-argument-is-set-to-true-automated) ->> -endobj -68 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 219.470079 491.179134 204.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-https-argument-is-set-to-true-automated) ->> -endobj -69 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 185.270079 498.679134 161.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-client-certificate-and---kubelet-client-key-arguments-are-set-as-appropriate-automated) ->> -endobj -70 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 164.870079 491.179134 149.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-client-certificate-and---kubelet-client-key-arguments-are-set-as-appropriate-automated) ->> -endobj -71 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 145.670079 498.679134 122.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-certificate-authority-argument-is-set-as-appropriate-automated) ->> -endobj -72 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 125.270079 491.179134 110.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubelet-certificate-authority-argument-is-set-as-appropriate-automated) ->> -endobj -73 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 106.070079 498.679134 82.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated) ->> -endobj -74 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 85.670079 491.179134 70.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated) ->> -endobj -75 0 obj -<< -/Filter /FlateDecode -/Length 3501 ->> -stream -x\M,dHb ޱsϣZnMtOMv1RT#)ihK?ɕ9iλ,eWώeO>B f Jqsb<~bv,GR >.]& -I͚4H50 Řa uチa(F0n"z\ _a rY&rx mV ]EV#h0,⢰J.PY~'a8d$Ç1K1Rs00!;.Aa!m uX>ꄐ #S60BN$y6s$3{ Ä6k"KD- -. -Ĺ$ Ò]J RaQ CU=ҏ{AQF00d"#2!c3 !2$r@rW(>U`!36Y Pb.#>IzF0|PQ. HuP!*!:Y .X;HR .u٣X>yA#Ҫ cԪwjE|gKJBK -dz*r Qҫ^,"B -0TnhgVW1jOjVGȖ^M1\@na .:W#"AZzBAdp!WzU^8r<ҫ)''HT^EJuiU'TX*;b=2&'W30cJ^mV-C(U̧*&ː$Qk*fܘRoUL0Fo4 eha0_Q2Xz5g̗E5X\̗$,m֔,eoՂ:ܖ^-*H uP'KAjVG)^-TKhuT&*d(U> Yz̩2|ձ-Z)f@k@S_k7|ՃY>/z}Z=XzUՑҫJShUPWWZ#[zU1*Wg1lUL 0fBG<0Vg.K*:!ҫ -XzUաҫ -΅WZ:;YzU%>=&̵oXc,Ir"Ls"{ne$N)`L@k ׂZVhJb 0eO#7u|dFUy]t7?|y)~_}!K'bP6į';|!| QÕ9~[C]K$ZS)ׇ͢O1ԖzIm 16- edQqZ-)h}.s% VaQQLnؘ5偠oRofT ,漠IqĶg)8X㈱5yQx/ƭqcc~ s}V9~9q_c{,?QRy<&5eq~|N՜9%Nw9NO>lDU5P]esY%䴼9.ƲF{TRx?rz2]<0M+P Ŏ5Wgx^nZu[hmqjv4Nw6L݆KBWj,#qa:6hҙݫS!?2z, ۂjExvǶyjNƵ/S î N򆷌\u\/ÚK*Q}1UH̳lFESf{Y w~/]Mݻ#vb Y[jLusMa +goYzW~<1vJb.=0;gs_nbԁ4f<,͵vaWq80#>.6Z{v"վ9V=~-e.!gV)H/ >;}lzn=1ϕ,(jAxJLeJ 0k؛' Jld1x8C [{&C՝v[Ʊ8J~ -:J:rNu줙CLEךv&Qw8ƣΡmɅi:$0|Q=iF_=n}mrj#Z{joZ{۶e7_Q@NJ؋]䌡1}tq EN. -EO N)5X;.()iY Jq[j)v$swZl|vvym>v6x4$ eirQr qU0X꬙˴^se2_ t`7Tq@Box飋˟u:U-;_0ȕ"Ka% -endstream -endobj -76 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 75 0 R -/Resources 4 0 R -/Annots [ 77 0 R 78 0 R 79 0 R 80 0 R 81 0 R 82 0 R 83 0 R 84 0 R 85 0 R 86 0 R 87 0 R 88 0 R 89 0 R 90 0 R 91 0 R 92 0 R 93 0 R 94 0 R 95 0 R 96 0 R 97 0 R 98 0 R 99 0 R 100 0 R 101 0 R 102 0 R 103 0 R 104 0 R 105 0 R 106 0 R 107 0 R 108 0 R 109 0 R 110 0 R 111 0 R 112 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -77 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-node-automated) ->> -endobj -78 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-node-automated) ->> -endobj -79 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-rbac-automated) ->> -endobj -80 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-includes-rbac-automated) ->> -endobj -81 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-eventratelimit-is-set-manual) ->> -endobj -82 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-eventratelimit-is-set-manual) ->> -endobj -83 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwaysadmit-is-not-set-automated) ->> -endobj -84 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwaysadmit-is-not-set-automated) ->> -endobj -85 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwayspullimages-is-set-manual) ->> -endobj -86 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-alwayspullimages-is-set-manual) ->> -endobj -87 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-securitycontextdeny-is-set-if-podsecuritypolicy-is-not-used-manual) ->> -endobj -88 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-securitycontextdeny-is-set-if-podsecuritypolicy-is-not-used-manual) ->> -endobj -89 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-serviceaccount-is-set-automated) ->> -endobj -90 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-serviceaccount-is-set-automated) ->> -endobj -91 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-namespacelifecycle-is-set-automated) ->> -endobj -92 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-namespacelifecycle-is-set-automated) ->> -endobj -93 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 473.570079 498.679134 450.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-podsecuritypolicy-is-set-automated) ->> -endobj -94 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 453.170079 491.179134 438.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-podsecuritypolicy-is-set-automated) ->> -endobj -95 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 433.970079 498.679134 410.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-noderestriction-is-set-automated) ->> -endobj -96 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 413.570079 491.179134 398.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-admission-control-plugin-noderestriction-is-set-automated) ->> -endobj -97 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 394.370079 498.679134 370.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-bind-address-argument-is-not-set-automated) ->> -endobj -98 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 373.970079 491.179134 358.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-bind-address-argument-is-not-set-automated) ->> -endobj -99 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 354.770079 498.679134 331.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-port-argument-is-set-to-0-automated) ->> -endobj -100 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 349.370079 491.179134 334.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---insecure-port-argument-is-set-to-0-automated) ->> -endobj -101 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 315.170079 498.679134 291.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---secure-port-argument-is-not-set-to-0-automated) ->> -endobj -102 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 309.770079 491.179134 294.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---secure-port-argument-is-not-set-to-0-automated) ->> -endobj -103 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 275.570079 498.679134 252.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated) ->> -endobj -104 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 270.170079 491.179134 255.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated) ->> -endobj -105 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 235.970079 498.679134 212.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-path-argument-is-set-automated) ->> -endobj -106 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 230.570079 491.179134 215.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-path-argument-is-set-automated) ->> -endobj -107 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 196.370079 498.679134 172.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxage-argument-is-set-to-30-or-as-appropriate-automated) ->> -endobj -108 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 175.970079 491.179134 160.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxage-argument-is-set-to-30-or-as-appropriate-automated) ->> -endobj -109 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 156.770079 498.679134 133.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxbackup-argument-is-set-to-10-or-as-appropriate-automated) ->> -endobj -110 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 136.370079 491.179134 121.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxbackup-argument-is-set-to-10-or-as-appropriate-automated) ->> -endobj -111 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 117.170079 498.679134 93.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxsize-argument-is-set-to-100-or-as-appropriate-automated) ->> -endobj -112 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 96.770079 491.179134 81.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---audit-log-maxsize-argument-is-set-to-100-or-as-appropriate-automated) ->> -endobj -113 0 obj -<< -/Filter /FlateDecode -/Length 3643 ->> -stream -x\݋6￢qTRIK.p3n1W-mwgϥR}Jpv%ȟD0#x{_8}:1?tNO'!t/CL}!N!Y)8 "ۆy&D`貅=AsˆEEfdbHdv1:0"slb!ICHL&i1{G&: :w 8I"sHId.,2Op1t" A'2cf"3"eP4@&Ef0>^dv;6'HƈR uPN#xm$#,3`!4'-%ɍ3%[i2O`p{z8a) pRMe4;]&-¶6+Fgς>$7nRta&7tq2P/'MAlsi-;թ:(G7tDCԠy㪂]^4a^ځ5}2itMnAanKC.ʥU aEu}_NnȾoUۡfe}  Q.?|{.{+=z } V辆k]"@j[rjƼA׌VR]M >Gd00 L>XT@k S?-tn`+BQl噡!sEp2GQvdhٻ!h- laH-´r{JD0FΖsё%sD9{IɖR`KfID.zæ1y; a'vJbډq;N$)hi'v!N -Rwb';$GN$Q;IrN;$GN$߉,9NE;%GNw'vry;YrĎӾc#yu'vr!Nfɫ;YN2ى,9Nvb'Kɒ`'vIP{DͲ|.uykxXo.\׷^/|9 we>=a0M[;d>i3mHk˧c,SL;7^5pϸفu/{o徴}>};.y~f; -;2C;n=nHWuy|_F9L2Z`cFidK2m#z_x~^>m5ۛm3@a.QY£fo\i-ەZH]S乘|)҂}OWG0`x6Gg||cvzk=ddk?}}̣#=V:&,!\cqjumx9ֆUW]]M`oE~}|Ze7mg.c5llފyiy@8Sxcj~Pw~Y]ϙ딝ޟcC!־]o` kd5<}LuruR8]׹o1P칵qgo5x'ו;cb2;~uW5x8lDԛA)ctL\y}?_VZqDOfoxܿc?ytŸ.Ǖ;j71]_.@ㄝBlŞT2Ƃ~|-(Cnu@mMfmDl>LXJ@Gڀ颯6ʷj"ݎTN]=:Ot+o|gK uڨYLm^>x -ek@; \y/q$~q8aچƭk>6&(oژ^sNfGé!LGB.&?sLȩ q>tA6|E -CR1/_r1ޔCO1 -Qd%ޗoL0gD \ebgHwɒ~1j%.sb;Zu_9-$k*Ѱj$ʧʍ*VH)7/]eMbv]Y 4Su$j\q+i7s RR5WwQBu4S%M%|I 4*)_5~t2Vzc=>-;AZŽ~>e}\Z^t'7ωǧ:^^7-.Ⱥ!j]2bn6~'CPqDzbHhUM ]uL0+-̽{:sҌ/Rɉ~|V,@{I@uhr]!u#ME~Ҧ-ukˬf]ic/@L`L yV~qxmYdP-7ꓦjKxT?.'5x/bϷAN>ʼnQEMtTiFkh·ö́1VxeqZRlcNYk:h4%mђo9޹lcɴBc}wRGJmmj{Vݠ.뷅Kbgusj<-kR9NbRT"%^{e[sȤݻo"<ɅAq[v]z6U? *Q;er$A!'f)^` -endstream -endobj -114 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 113 0 R -/Resources 4 0 R -/Annots [ 115 0 R 116 0 R 117 0 R 118 0 R 119 0 R 120 0 R 121 0 R 122 0 R 123 0 R 124 0 R 125 0 R 126 0 R 127 0 R 128 0 R 129 0 R 130 0 R 131 0 R 132 0 R 133 0 R 134 0 R 135 0 R 136 0 R 137 0 R 138 0 R 139 0 R 140 0 R 141 0 R 142 0 R 143 0 R 144 0 R 145 0 R 146 0 R 147 0 R 148 0 R 149 0 R 150 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -115 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---request-timeout-argument-is-set-as-appropriate-automated) ->> -endobj -116 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---request-timeout-argument-is-set-as-appropriate-automated) ->> -endobj -117 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-lookup-argument-is-set-to-true-automated) ->> -endobj -118 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-lookup-argument-is-set-to-true-automated) ->> -endobj -119 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -120 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -121 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-certfile-and---etcd-keyfile-arguments-are-set-as-appropriate-automated) ->> -endobj -122 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-certfile-and---etcd-keyfile-arguments-are-set-as-appropriate-automated) ->> -endobj -123 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -124 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -125 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -126 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -127 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-cafile-argument-is-set-as-appropriate-automated) ->> -endobj -128 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---etcd-cafile-argument-is-set-as-appropriate-automated) ->> -endobj -129 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---encryption-provider-config-argument-is-set-as-appropriate-automated) ->> -endobj -130 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---encryption-provider-config-argument-is-set-as-appropriate-automated) ->> -endobj -131 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 473.570079 498.679134 450.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-encryption-providers-are-appropriately-configured-automated) ->> -endobj -132 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 453.170079 491.179134 438.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-encryption-providers-are-appropriately-configured-automated) ->> -endobj -133 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 433.970079 498.679134 410.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-only-makes-use-of-strong-cryptographic-ciphers-manual) ->> -endobj -134 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 413.570079 491.179134 398.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-api-server-only-makes-use-of-strong-cryptographic-ciphers-manual) ->> -endobj -135 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 394.370079 504.679134 361.670079 ] -/BS << -/W 0 ->> -/Dest (controller-manager) ->> -endobj -136 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.970394 386.420079 496.429134 371.420079 ] -/BS << -/W 0 ->> -/Dest (controller-manager) ->> -endobj -137 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 343.670079 498.679134 320.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---terminated-pod-gc-threshold-argument-is-set-as-appropriate-automated) ->> -endobj -138 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 323.270079 491.179134 308.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---terminated-pod-gc-threshold-argument-is-set-as-appropriate-automated) ->> -endobj -139 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 304.070079 498.679134 280.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-1) ->> -endobj -140 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 298.670079 491.179134 283.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-1) ->> -endobj -141 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 264.470079 498.679134 241.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---use-service-account-credentials-argument-is-set-to-true-automated) ->> -endobj -142 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 244.070079 491.179134 229.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---use-service-account-credentials-argument-is-set-to-true-automated) ->> -endobj -143 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 224.870079 498.679134 201.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-private-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -144 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 204.470079 491.179134 189.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---service-account-private-key-file-argument-is-set-as-appropriate-automated) ->> -endobj -145 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 185.270079 498.679134 161.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---root-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -146 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 164.870079 491.179134 149.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---root-ca-file-argument-is-set-as-appropriate-automated) ->> -endobj -147 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 145.670079 498.679134 122.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) ->> -endobj -148 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 125.270079 491.179134 110.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-rotatekubeletservercertificate-argument-is-set-to-true-automated) ->> -endobj -149 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 106.070079 498.679134 82.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated) ->> -endobj -150 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.786556 85.670079 491.179134 70.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated) ->> -endobj -151 0 obj -<< -/Filter /FlateDecode -/Length 3770 ->> -stream -x][ݶ~?<!gx-61P !}j'(v8}Pe(QuZ4Zcm;# E1\5Bxtʓɢ;>獊墉`\*jvR@\`.kKyŃ5X}.i Sghܩ3N jEWg@nΜJjowbضW7m?:vqv9NYv_;胊6ցv0z!mh8G(seCvsh8Gv8*:C܁vs;9Ϋ!Oh}PuܴWC1x9Jhq8Qphq2qv({9 -8GH;-y1Y[|gNcl;UޭI\l't/`,o*1sn+qoSౕR=zN_n5Gh7GxVxwzP/6C;\̆=Ԙ. 9N"f# 7FXU188>y pyyh؈8Ԙ;6Ek7-Eɢ)SDW}|'Ѯ=]ݠEDOLK-=%zJXz_-MyN-7VzS^\sG=C8qZQ{oc -Grt4~qx+S]v Z×Y3hݜtujwA%*n7J 9 \tiQ}`#y:Azht(qSDO$N]{ֻAN=%$:'[=%zJ]]B LPk}[0oᢜh5୲)J_؃"C -2nal^Q=x-2{!|ataD80sbk3_4o/wQ!#\vi57/[ǯ_~˟޲qv'`%3{Pro|wp\tLy&q)SE/oŨqpu,DSV:vp}RqO_|2d4&6+Ixe;S=']Cq{y;BO.b -?M0 yC^NkL'8?OAg_c8O!;q>.ſ˗]8 t4AY=EM0;E6.Wr HTmQ#ڴV"}b.6JlJ @#^vm^ƽn\Z=Dx-$Eo\n"v{m1%2C+ﵳ3 ?YӛI8Խ2No#Ƌ8Ip2cZ7 sӛXOQcJ(h7x ׭1x<|fn}o9縵͢oO,u?Yr`pkm\Ik!9rgG; n1\4JvIlxw ǨӔg,5h#cM~F9Đ\?V^"mv{{N!Lu?Jehto;w浨ح壉 ],+ѱq[G\U{,wK^i">":{r.'u\N0] {H>tSLR||L_ّ,%oclqk){Ow`gww>D- uȋ[m>̡agJ SgpEB,ӑaT(}/bCvL%%Lp5i]DBS .)jSӅ.6ሁNs[{'J^q\0%v0 ׍K=SLv 6#Nx/[E쌖>y[ÈaC8Pײ>L^lzZaaiX g0]O2;&SΒftS-3Al>s*Jlm aZp`e,sk%u _lovkM_Q*]1+*+JŲkPzRd~K2JGj]v4*KcaUuu*l(&)h[{إXOY46vIyg?\ -5hEPbi,Lϩ*2ttJ9IڬpO]:8b7[Ax_ ا[+c*(xzeja)~j.`w ڕ:ՓTgDwZn]͝56Nަ p8iuk*I->LpQkNc=l"ϗi3LLOZclp7ۼ^<]Hf-!<6A R u7Fkl؋% -S RPv]V0C;mb6`ϧ4XNds4lH>KmHB>p[ͺj)TSQ&_DL#ҩmafeZ!L]i3uws]Q@BkjDkZөOc餈1T˲B{Nr4GeـS,X 5]SJN._VhZ,:hϒiQ$[٦rˈWgKNHvgZeKfi 2^E3UĵnE%>4G m 5^c8pCxՌA< 6I@ B`m -?asE=l|xU6??SCz&طr -endstream -endobj -152 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 151 0 R -/Resources 4 0 R -/Annots [ 153 0 R 154 0 R 155 0 R 156 0 R 157 0 R 158 0 R 159 0 R 160 0 R 161 0 R 162 0 R 163 0 R 164 0 R 165 0 R 166 0 R 167 0 R 168 0 R 169 0 R 170 0 R 171 0 R 172 0 R 173 0 R 174 0 R 175 0 R 176 0 R 177 0 R 178 0 R 179 0 R 180 0 R 181 0 R 182 0 R 183 0 R 184 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -153 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 790.370079 504.679134 757.670079 ] -/BS << -/W 0 ->> -/Dest (scheduler) ->> -endobj -154 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.518001 782.420079 496.429134 767.420079 ] -/BS << -/W 0 ->> -/Dest (scheduler) ->> -endobj -155 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 739.670079 498.679134 716.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-2) ->> -endobj -156 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 734.270079 491.179134 719.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---profiling-argument-is-set-to-false-automated-2) ->> -endobj -157 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 700.070079 498.679134 676.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated-1) ->> -endobj -158 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 679.670079 491.179134 664.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---bind-address-argument-is-set-to-127.0.0.1-automated-1) ->> -endobj -159 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 660.470079 504.679134 627.770079 ] -/BS << -/W 0 ->> -/Dest (etcd-node-configuration-files) ->> -endobj -160 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.154476 652.520079 496.429134 637.520079 ] -/BS << -/W 0 ->> -/Dest (etcd-node-configuration-files) ->> -endobj -161 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 609.770079 498.679134 586.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---cert-file-and---key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -162 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 589.370079 491.179134 574.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---cert-file-and---key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -163 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 570.170079 498.679134 546.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -164 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 564.770079 491.179134 549.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -165 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 530.570079 498.679134 507.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -166 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 525.170079 491.179134 510.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -167 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 490.970079 498.679134 467.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-cert-file-and---peer-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -168 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 470.570079 491.179134 455.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-cert-file-and---peer-key-file-arguments-are-set-as-appropriate-automated) ->> -endobj -169 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 451.370079 498.679134 427.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -170 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 430.970079 491.179134 415.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-client-cert-auth-argument-is-set-to-true-automated) ->> -endobj -171 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 411.770079 498.679134 388.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -172 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 391.370079 491.179134 376.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---peer-auto-tls-argument-is-not-set-to-true-automated) ->> -endobj -173 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 372.170079 498.679134 348.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-unique-certificate-authority-is-used-for-etcd-manual) ->> -endobj -174 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 366.770079 491.179134 351.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-unique-certificate-authority-is-used-for-etcd-manual) ->> -endobj -175 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 332.570079 504.679134 299.870079 ] -/BS << -/W 0 ->> -/Dest (authentication-and-authorization) ->> -endobj -176 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.482112 324.620079 496.429134 309.620079 ] -/BS << -/W 0 ->> -/Dest (authentication-and-authorization) ->> -endobj -177 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 281.870079 498.679134 258.470079 ] -/BS << -/W 0 ->> -/Dest (client-certificate-authentication-should-not-be-used-for-users-manual) ->> -endobj -178 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 261.470079 491.179134 246.470079 ] -/BS << -/W 0 ->> -/Dest (client-certificate-authentication-should-not-be-used-for-users-manual) ->> -endobj -179 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 242.270079 504.679134 209.570079 ] -/BS << -/W 0 ->> -/Dest (logging) ->> -endobj -180 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.494564 234.320079 496.429134 219.320079 ] -/BS << -/W 0 ->> -/Dest (logging) ->> -endobj -181 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 191.570079 498.679134 168.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-minimal-audit-policy-is-created-automated) ->> -endobj -182 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 186.170079 491.179134 171.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-a-minimal-audit-policy-is-created-automated) ->> -endobj -183 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 151.970079 498.679134 128.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-audit-policy-covers-key-security-concerns-manual) ->> -endobj -184 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 146.570079 491.179134 131.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-audit-policy-covers-key-security-concerns-manual) ->> -endobj -185 0 obj -<< -/Filter /FlateDecode -/Length 3781 ->> -stream -x\ێ}W9} `H$1 AVd#XY]Rk'd35gNץ/5Cڽ/,Idr ?|}ڙ)9/an?Ah'!~8Tq]BH,o +t1ZfmkNt*l:;!&N7,7Yk+Zp҃슐˭q 5nQFbhvpO[>L'w5fUnh~wnk~KrBnouih1gzˏ/d?{sbnzqgNOtݧc(˦aЛ{B7Iq=wz.MxO}:>gjml.>\SrؘA9/74'&S,;a VÀ3GF c3Y$p .4 8; yC;Rǀc٘bٰ MTw0 hT2*U1 ΜQ18*&3dsHaF4J.9JΖlJ"0f%~d2* ) 9q1+]L9!pfKYOLU 0golVpvިL(rJ&%`4S'̨~)rRb A -)GU VI9gV8pfJaM9)C}L*ٛ!gL*]RbI - S1,_ÐaJV$ LJPS>G%~(BH˒sJ0n]P19*}"[cΎ0%hhU 5&*e7V=E)z/|tI MàG=E?SS s{O{S}K1Q{sr#6qײ%:vd %#CL)jL:gQ -$sg`4 8'p&##Lg9лɀ3 pN%Ƃ (F)%p)A\JC9qƙ3i =E3)dڣ&c4\64L,eC˭t?¤R6 =zbby;93q/-1l4U8cS8g S8gF{yqQ8cxyqlB -ggc}8S,ia4Μ#j1ah 8Gp93=i83U%%(dmVF9:eX= e\(3 -fA*,fDQ{v9 !<OKz{=,41#4ko?|oЗv -ݟB#/*>0YW*{Ä"?~� -\Ϭ"}^O?PYUWtPEWyPn2D !BEr%_BE,^"˒*ewبx*;TK߃1ac=>i9E^d.x\z/qW|_~Xui, Y€2{.36KBJ|&VL1@ي@\;?x/f5JX*~:rljzuǕ5&Qضy|gsl hok 9h<@` oǥkBªu߭beo켝o 5wAeֳu[ ڹx^zwC*tleZ:6^r}>XoW__ͦe_s=^?:خ-߇Ŵɵ8q1Z'# j߸UgQkj113lf9f0\ˈZqdnܴԲNIgX^[mjܱ\C_:"w|v\}n3vf0S^r%uf;HǶO;&gv'7U1bEY~XbqƮ7}#;jtc;j϶fIYs<ƞ vV׍i=3r}WEBJ -m} -a~e%җX^R)7@yKe^^#A4 ,gn)a֦°}uAօ_3]_bM[xn rx|´cO;NXRm01gv!;;[:맆ZLmiaɊ_&LSq@y%NA e|,~sfFLO\$.дV`v֗77anCw\oKzVaQ<`Oť NgQP9C$ c4B>b];utVbK"aX8:dZי&TnRj~'/LmVܮ a[ -S $j\qa7ĭqTloJuFģ8í8T_?㴸nve9?8NJ+B/mdztiLTH*+8JqlXNy <ѱ~JY L;1 -]܇Y\N6vؓl4v?iyv|Bv`V_%^qghغ˙9_][-mБئ mwNo7}`HFPۮJ!w -kaEx8b[\>a/vj|y)‰NSM@č8T(̝نf H' -_t(_>ʦl74LV*>/NR5 M(cEϧa{/'5yZ[^o}iABm+R:Q2SeX9jih]4K4#J8vVK-Xs3֒i &UvlݠN$ EKrg)5ߗ2)!T~0RgߣPN$"5ش{- G\O_M=s[6.=g4~cO~\%jl9 2FsI)t -endstream -endobj -186 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 185 0 R -/Resources 4 0 R -/Annots [ 187 0 R 188 0 R 189 0 R 190 0 R 191 0 R 192 0 R 193 0 R 194 0 R 195 0 R 196 0 R 197 0 R 198 0 R 199 0 R 200 0 R 201 0 R 202 0 R 203 0 R 204 0 R 205 0 R 206 0 R 207 0 R 208 0 R 209 0 R 210 0 R 211 0 R 212 0 R 213 0 R 214 0 R 215 0 R 216 0 R 217 0 R 218 0 R 219 0 R 220 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -187 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 790.370079 504.679134 757.670079 ] -/BS << -/W 0 ->> -/Dest (worker-node-configuration-files) ->> -endobj -188 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.214534 782.420079 496.429134 767.420079 ] -/BS << -/W 0 ->> -/Dest (worker-node-configuration-files) ->> -endobj -189 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 739.670079 498.679134 716.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -190 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 719.270079 491.179134 704.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -191 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 700.070079 498.679134 676.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-ownership-is-set-to-rootroot-automated) ->> -endobj -192 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 679.670079 491.179134 664.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-service-file-ownership-is-set-to-rootroot-automated) ->> -endobj -193 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 660.470079 498.679134 637.070079 ] -/BS << -/W 0 ->> -/Dest (if-proxy-kubeconfig-file-exists-ensure-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -194 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 640.070079 491.179134 625.070079 ] -/BS << -/W 0 ->> -/Dest (if-proxy-kubeconfig-file-exists-ensure-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -195 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 620.870079 498.679134 597.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-proxy-kubeconfig-file-ownership-is-set-to-rootroot-manual) ->> -endobj -196 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 600.470079 491.179134 585.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-proxy-kubeconfig-file-ownership-is-set-to-rootroot-manual) ->> -endobj -197 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 581.270079 498.679134 557.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -198 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 560.870079 491.179134 545.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-permissions-are-set-to-644-or-more-restrictive-automated) ->> -endobj -199 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 541.670079 498.679134 518.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -200 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 521.270079 491.179134 506.270079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---kubeconfig-kubelet.conf-file-ownership-is-set-to-rootroot-automated) ->> -endobj -201 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 502.070079 498.679134 478.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-certificate-authorities-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -202 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 481.670079 491.179134 466.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-certificate-authorities-file-permissions-are-set-to-644-or-more-restrictive-manual) ->> -endobj -203 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 462.470079 498.679134 439.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-client-certificate-authorities-file-ownership-is-set-to-rootroot-automated) ->> -endobj -204 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 442.070079 491.179134 427.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-client-certificate-authorities-file-ownership-is-set-to-rootroot-automated) ->> -endobj -205 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 422.870079 498.679134 399.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-has-permissions-set-to-644-or-more-restrictive-automated) ->> -endobj -206 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 402.470079 491.179134 387.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-has-permissions-set-to-644-or-more-restrictive-automated) ->> -endobj -207 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 383.270079 498.679134 359.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-ownership-is-set-to-rootroot-automated) ->> -endobj -208 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 362.870079 491.179134 347.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet---config-configuration-file-ownership-is-set-to-rootroot-automated) ->> -endobj -209 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 343.670079 504.679134 310.970079 ] -/BS << -/W 0 ->> -/Dest (kubelet) ->> -endobj -210 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.214534 335.720079 496.429134 320.720079 ] -/BS << -/W 0 ->> -/Dest (kubelet) ->> -endobj -211 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 292.970079 498.679134 269.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-anonymous-auth-argument-is-set-to-false-automated) ->> -endobj -212 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 272.570079 491.179134 257.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-anonymous-auth-argument-is-set-to-false-automated) ->> -endobj -213 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 253.370079 498.679134 229.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated-1) ->> -endobj -214 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 232.970079 491.179134 217.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---authorization-mode-argument-is-not-set-to-alwaysallow-automated-1) ->> -endobj -215 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 213.770079 498.679134 190.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated-1) ->> -endobj -216 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 193.370079 491.179134 178.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---client-ca-file-argument-is-set-as-appropriate-automated-1) ->> -endobj -217 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 174.170079 498.679134 150.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---read-only-port-argument-is-set-to-0-automated) ->> -endobj -218 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 168.770079 491.179134 153.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---read-only-port-argument-is-set-to-0-automated) ->> -endobj -219 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 134.570079 498.679134 111.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---streaming-connection-idle-timeout-argument-is-not-set-to-0-automated) ->> -endobj -220 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 114.170079 491.179134 99.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---streaming-connection-idle-timeout-argument-is-not-set-to-0-automated) ->> -endobj -221 0 obj -<< -/Filter /FlateDecode -/Length 4009 ->> -stream -x\[$ ~_ρ8,@-0Lpfaվ\>ϲ/}3J%[>I]w׎KLJ9<_~:Y±:Y.ǿsє>1d篒 W _~wX?%KD]$FYa &Ft.d0ɲ⨰ 1hw2Y|O0f$RxL@S -G v+bM"Ƭ/DllN4}ΰ<HyH1^'yxƓ xa@p+uRB`ʺ]^qް:}eCV!DS >>$)7c -:jlISGET0e0 O!a h0Md$Ɖ%0D&)z9arR6sƤ -샜2!$S <)pFTxSV0>lGYVxq$ξO .h6 2sf` i)q,“s&2Ct!ja2g>C?SCQ>C}Е#A4qqDohFr=Y[S@c=9a,S}aL&6*LF g>Cg -y(= -g>CGeeы5]vRܙabvy1E\xxO&DSՇ<E'- .i< <{ēiy'[5}?8Amc"P L1ڤX1Sy*f %b?&B۽ i}>|m f<.n<zog/c-cfoO^+"pC> "sZC]Dy."" vtDP -ˍ$0dw&EȾP|?m"{PD{v GEo߃"|/ܟ6n}ٖ7Pny*8Ac-b>cY-Ox׹py] +&[n$kωeS9똮׈p-A:~+}sK*^+nEB/}ڟeu{ѯSSܮabK㇪cs؋̋/ZkOQQbR:]m.Զucc6}'ryBŪ]k -Î &z1E8{5n bO*&x ݆k9mxyg&a7raW4_~Yج~_ZLv [;⁽V텿XX'v[Aؼ7|yJ }|D>k>ܺ-]J_Ҿ6͇E;Uscycum/g'Ŀ~ -NK)yߜKn[[Zmqk˷gyFREȋZo|{͢;^15s`>Jvc$ Z].#&]07>DAvE[Ummsvbޭ k앹EqZ乭^ȕQrNWr[{Oe^:oQ|dZ7d)1ێĬ -+M46Lf*@ܥze@ 4@Awm-"-TQ i  YAB$dx6teUgby9.,7O?Rٛ/\fUzy)7PWN^qiwKY.W[̟'Unr~Z~5vBwCUӉ*0bΖ%y\>rą~hXakA[?uKkʇ'z@a0t=b2 -'dNr!C*mh+w綜=WJmJA/+Гz7a w ;_$9v]@׷+|/Ć[rqԄ 2> a80#,=;ٌ{9pZ9-xz_^ĞEQZDѬ2&.fN6kfYFVIҍH-WK@$9k4ٺSqpFƵ6۞0p(FejG3q)%vO;θV#.m [>Υ):j~ɫ(m"%1h6:^B}AtU_9htH3 gSmeƲTʗWl*ﭹh)m}=j -endstream -endobj -222 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 221 0 R -/Resources 4 0 R -/Annots [ 223 0 R 224 0 R 225 0 R 226 0 R 227 0 R 228 0 R 229 0 R 230 0 R 231 0 R 232 0 R 233 0 R 234 0 R 235 0 R 236 0 R 237 0 R 238 0 R 239 0 R 240 0 R 241 0 R 242 0 R 243 0 R 244 0 R 245 0 R 246 0 R 247 0 R 248 0 R 249 0 R 250 0 R 251 0 R 252 0 R 253 0 R 254 0 R 255 0 R 256 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -223 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---protect-kernel-defaults-argument-is-set-to-true-automated) ->> -endobj -224 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---protect-kernel-defaults-argument-is-set-to-true-automated) ->> -endobj -225 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---make-iptables-util-chains-argument-is-set-to-true-automated) ->> -endobj -226 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---make-iptables-util-chains-argument-is-set-to-true-automated) ->> -endobj -227 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---hostname-override-argument-is-not-set-manual) ->> -endobj -228 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 705.770079 491.179134 690.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---hostname-override-argument-is-not-set-manual) ->> -endobj -229 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---event-qps-argument-is-set-to-0-or-a-level-which-ensures-appropriate-event-capture-manual) ->> -endobj -230 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---event-qps-argument-is-set-to-0-or-a-level-which-ensures-appropriate-event-capture-manual) ->> -endobj -231 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated-1) ->> -endobj -232 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 611.570079 491.179134 596.570079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---tls-cert-file-and---tls-private-key-file-arguments-are-set-as-appropriate-automated-1) ->> -endobj -233 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---rotate-certificates-argument-is-not-set-to-false-manual) ->> -endobj -234 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the---rotate-certificates-argument-is-not-set-to-false-manual) ->> -endobj -235 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (verify-that-the-rotatekubeletservercertificate-argument-is-set-to-true-manual) ->> -endobj -236 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (verify-that-the-rotatekubeletservercertificate-argument-is-set-to-true-manual) ->> -endobj -237 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-only-makes-use-of-strong-cryptographic-ciphers-manual) ->> -endobj -238 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-kubelet-only-makes-use-of-strong-cryptographic-ciphers-manual) ->> -endobj -239 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 473.570079 504.679134 440.870079 ] -/BS << -/W 0 ->> -/Dest (rbac-and-service-accounts) ->> -endobj -240 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.986019 465.620079 496.429134 450.620079 ] -/BS << -/W 0 ->> -/Dest (rbac-and-service-accounts) ->> -endobj -241 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 422.870079 498.679134 399.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cluster-admin-role-is-only-used-where-required-manual) ->> -endobj -242 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 402.470079 491.179134 387.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cluster-admin-role-is-only-used-where-required-manual) ->> -endobj -243 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 383.270079 498.679134 359.870079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-secrets-manual) ->> -endobj -244 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 377.870079 491.179134 362.870079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-secrets-manual) ->> -endobj -245 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 343.670079 498.679134 320.270079 ] -/BS << -/W 0 ->> -/Dest (minimize-wildcard-use-in-roles-and-clusterroles-manual) ->> -endobj -246 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 338.270079 491.179134 323.270079 ] -/BS << -/W 0 ->> -/Dest (minimize-wildcard-use-in-roles-and-clusterroles-manual) ->> -endobj -247 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 304.070079 498.679134 280.670079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-create-pods-manual) ->> -endobj -248 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 298.670079 491.179134 283.670079 ] -/BS << -/W 0 ->> -/Dest (minimize-access-to-create-pods-manual) ->> -endobj -249 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 264.470079 498.679134 241.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-default-service-accounts-are-not-actively-used.-automated) ->> -endobj -250 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 244.070079 491.179134 229.070079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-default-service-accounts-are-not-actively-used.-automated) ->> -endobj -251 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 224.870079 498.679134 201.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-service-account-tokens-are-only-mounted-where-necessary-manual) ->> -endobj -252 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 204.470079 491.179134 189.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-service-account-tokens-are-only-mounted-where-necessary-manual) ->> -endobj -253 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 185.270079 504.679134 152.570079 ] -/BS << -/W 0 ->> -/Dest (pod-security-policies) ->> -endobj -254 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.454036 177.320079 496.429134 162.320079 ] -/BS << -/W 0 ->> -/Dest (pod-security-policies) ->> -endobj -255 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 134.570079 498.679134 111.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-privileged-containers-automated) ->> -endobj -256 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 129.170079 491.179134 114.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-privileged-containers-automated) ->> -endobj -257 0 obj -<< -/Filter /FlateDecode -/Length 4115 ->> -stream -x]K#Wl4Y,cHb/ aVٵX琿"b7hv,ckUUER-I%<*}pϗӧHKIzzr"^m (}~.# -ZySTZ&2)g=VRΤ:5y5R-%YLLzf}\ڌIo?y>~ѴDCf#e,YTڊ " ۆS:l0|"`Q niP) ЪrbfתR5J^Y ãsNָФF6b0tpJ<5AzYݐI ;<4\@4ʮ+pȿa{] gɡוӐAcxWyjG9GLqWysܷVF/k=b5x *Y`;ayjnNvǃyuݐ m*ϊ8~SyWC!!4vhǃF=<5 XXovBw?9&7!znt!-{!zP|Dw/t=BMtGPeo3mu[)xkg.q̹,,-!;2^@ٗ4Gp=@'mҷl3ޘfxwINlJE &Y V869, QjhrWB8 ,1jy0trJUɼ5pz.rc86ddÃM$1j sSC;.s6ٓykl<~LrqG}2S>z;1I^ zeiSX8,Bƒ@kaZ?}%W =l|_ޑ窰TU@+A7ДU8}~x^Y7} -e7YRB-SAr_,%øۂ*-nTѹ5:uW]pKl@;OE*+3q׹=hfg@EqX&Q:^c|%o -#jӞNKHiT~.g ߷s$[1Y<1,mCƶR{R,mZIo{hĶq]gю\~_@}gt~${m>pYʶH&W|f=([5mej+Ҽuó#N}i׾ )w־6ŶN^[pVGja($q!:Q|YҮ}y8eߗRs=^/_]۠2.uĩ]mޠꇦ3l훹ڏ]P O%&/RY~OwՄk5%yf[EN0n⢭'bJűhw:tg̍3h&-GS3.a#T^ѡ#;'93:TwW5VvZj(mrx%((fg}q׶ - eRaKQ(:;YGlJY:K-yJgJN$Se^[s/Qu&sH7׹Z;,d[?]XnvMj{͌aܙUZV">KۨM~P̖_k+`w`v"KKz^wwdottmA,[0G_է,m2YyD`y"r(Fo0@g_S']:3FBQ|۸VIBt~Z\aXCvn)jk=[\@vX.[C9 Q4vqɅ sWK%őݬBXRzaA.Ӳs(;bg}3du[[oT\D - 8n>zH Ztw?IĝǏȫɻBVf8FrÒy)H۲v0N [B,%W xTRa'jf}[E7>G"Ę'.4/\ z(ܩmu޹4J٧*L[˯,stR!hTL~$X>p`>-)t'e%MrjC07zS.K"raQ<Jp}igbl r`*dقk0e(PC\C3N1,8F H^CTŠxd43*TJVPh~-KHdkP~%n*r5SrUʷKC|3 x>|QJTI]{8 T؀S;d@ڴ\!MzԬ -{KC/,X|w= -SјyA|oTYSc½8nk/ Jmǯ 8ttX21<S5y1\AY u 6u(?vpP^Yņ6aWWk'Zl -8}Q`5e lQRhpK .Z - US*s xW_M$>ťjn`^t* *XÆ,7X&khukl˖؋TW9h u_zl1bȼVS]:'oC뀊';tk3k΢h+*NxtfYgf\Iu}9:b'lOu{ [M,bFŕΞw׋y&hMxcTS֚۟ϊmmi{NrZhv'|2Է˲J`R(j LM6_Vܒz^ruN_ g:pVF6[*^-:2|8;$\0˯(6I]nuj{ffm3S.3ɻ=3q$m(_5dG4so-#ơg%Ͼf&)(\XZ:EmDŽGz!\5?sY.=ߚΟHDť >4A9yl? -endstream -endobj -258 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 257 0 R -/Resources 4 0 R -/Annots [ 259 0 R 260 0 R 261 0 R 262 0 R 263 0 R 264 0 R 265 0 R 266 0 R 267 0 R 268 0 R 269 0 R 270 0 R 271 0 R 272 0 R 273 0 R 274 0 R 275 0 R 276 0 R 277 0 R 278 0 R 279 0 R 280 0 R 281 0 R 282 0 R 283 0 R 284 0 R 285 0 R 286 0 R 287 0 R 288 0 R 289 0 R 290 0 R 291 0 R 292 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -259 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 790.370079 498.679134 766.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-process-id-namespace-automated) ->> -endobj -260 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 769.970079 491.179134 754.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-process-id-namespace-automated) ->> -endobj -261 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 750.770079 498.679134 727.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-ipc-namespace-automated) ->> -endobj -262 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 730.370079 491.179134 715.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-ipc-namespace-automated) ->> -endobj -263 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 711.170079 498.679134 687.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-network-namespace-automated) ->> -endobj -264 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 690.770079 491.179134 675.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-wishing-to-share-the-host-network-namespace-automated) ->> -endobj -265 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 671.570079 498.679134 648.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-allowprivilegeescalation-automated) ->> -endobj -266 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 651.170079 491.179134 636.170079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-allowprivilegeescalation-automated) ->> -endobj -267 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 631.970079 498.679134 608.570079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-root-containers-automated) ->> -endobj -268 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 626.570079 491.179134 611.570079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-root-containers-automated) ->> -endobj -269 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 592.370079 498.679134 568.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-the-net_raw-capability-manual) ->> -endobj -270 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 571.970079 491.179134 556.970079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-the-net_raw-capability-manual) ->> -endobj -271 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 552.770079 498.679134 529.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-added-capabilities-manual) ->> -endobj -272 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 532.370079 491.179134 517.370079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-added-capabilities-manual) ->> -endobj -273 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 513.170079 498.679134 489.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-capabilities-assigned-manual) ->> -endobj -274 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 492.770079 491.179134 477.770079 ] -/BS << -/W 0 ->> -/Dest (minimize-the-admission-of-containers-with-capabilities-assigned-manual) ->> -endobj -275 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 473.570079 504.679134 440.870079 ] -/BS << -/W 0 ->> -/Dest (network-policies-and-cni) ->> -endobj -276 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.970394 465.620079 496.429134 450.620079 ] -/BS << -/W 0 ->> -/Dest (network-policies-and-cni) ->> -endobj -277 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 422.870079 498.679134 399.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cni-in-use-supports-network-policies-automated) ->> -endobj -278 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 417.470079 491.179134 402.470079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-cni-in-use-supports-network-policies-automated) ->> -endobj -279 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 383.270079 498.679134 359.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-all-namespaces-have-network-policies-defined-automated) ->> -endobj -280 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 362.870079 491.179134 347.870079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-all-namespaces-have-network-policies-defined-automated) ->> -endobj -281 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 343.670079 504.679134 310.970079 ] -/BS << -/W 0 ->> -/Dest (secrets-management) ->> -endobj -282 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.962581 335.720079 496.429134 320.720079 ] -/BS << -/W 0 ->> -/Dest (secrets-management) ->> -endobj -283 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 292.970079 498.679134 269.570079 ] -/BS << -/W 0 ->> -/Dest (prefer-using-secrets-as-files-over-secrets-as-environment-variables-manual) ->> -endobj -284 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 272.570079 491.179134 257.570079 ] -/BS << -/W 0 ->> -/Dest (prefer-using-secrets-as-files-over-secrets-as-environment-variables-manual) ->> -endobj -285 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 253.370079 498.679134 229.970079 ] -/BS << -/W 0 ->> -/Dest (consider-external-secret-storage-manual) ->> -endobj -286 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 247.970079 491.179134 232.970079 ] -/BS << -/W 0 ->> -/Dest (consider-external-secret-storage-manual) ->> -endobj -287 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 213.770079 504.679134 181.070079 ] -/BS << -/W 0 ->> -/Dest (extensible-admission-control) ->> -endobj -288 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.506282 205.820079 496.429134 190.820079 ] -/BS << -/W 0 ->> -/Dest (extensible-admission-control) ->> -endobj -289 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 163.070079 498.679134 139.670079 ] -/BS << -/W 0 ->> -/Dest (configure-image-provenance-using-imagepolicywebhook-admission-controller-manual) ->> -endobj -290 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 142.670079 491.179134 127.670079 ] -/BS << -/W 0 ->> -/Dest (configure-image-provenance-using-imagepolicywebhook-admission-controller-manual) ->> -endobj -291 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 123.470079 504.679134 90.770079 ] -/BS << -/W 0 ->> -/Dest (the-v1.5.1-guide-skips-5.6-and-goes-from-5.5-to-5.7.-we-are-including-it-here-merely-for-explanation.) ->> -endobj -292 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 481.202815 100.520079 496.429134 85.520079 ] -/BS << -/W 0 ->> -/Dest (the-v1.5.1-guide-skips-5.6-and-goes-from-5.5-to-5.7.-we-are-including-it-here-merely-for-explanation.) ->> -endobj -293 0 obj -<< -/Filter /FlateDecode -/Length 2240 ->> -stream -xZͫ7_@:7M kxò9a=OI*UOkzg3֯KURIc `I)q2KTݠ~K7D\pi 3S|!80mCD?}5)&N,p wE:)L\3VxLD0M^‹U)pAwhԼqdY C!򺑆v͟ -V!B;; wbqo~p׸`%Q{+yHC;ٖ?ᷟob?&J$v~/t OHZv+ռ$KB$䟒{nz+M_%v 29;6C+>Cf0ŘͿ=h. 8I@Nh[,}8 f!hbSE3>1-xB|O6 :< Kfs)ӽAgOAdmBnx{Y>a1L'4txtCGO| -Lm -'1F.Mx'1%މyL}Yc -KK)ļʕ<-iIwb;1ovQ̷"4\j11Eh3*4osqۇ B sR̆Lo|?~+c'ǿf$țLhl Hj2a懟~sE R¿V犸--:чRQYca7#mV]hæ#u7C%\D0*Ek -Dq{.b4.Et+_<~[F:m@lroQ||{]ߝ,j9d&[%hfGvk-|aLt̶ٖoUv ?,txzUlCnMb_U޿csjS{mM.[SvB_/ tm-m |$>n2 sî3:Q -KTyzn8K6|6d{+9_^\~9xTcUך?%6/)$O *!JC'lX;7QoM-(㎦I/-!lrRE{\9Vtip»+47.\B{Juإ!Tjv+{ougwױ>No[á%8TӡƐèHt&L{4iZStLG0 94??5'XDpBt4|GXpۣ^Pu[j(mն, ly5eiv+)ȣH3rFATCb3t3`4J\)/3Ӣ'WCC$_pXO -endstream -endobj -294 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 293 0 R -/Resources 4 0 R -/Annots [ 295 0 R 296 0 R 297 0 R 298 0 R 299 0 R 300 0 R 301 0 R 302 0 R 303 0 R 304 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -295 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 790.370079 504.679134 757.670079 ] -/BS << -/W 0 ->> -/Dest (general-policies) ->> -endobj -296 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 478.142757 782.420079 496.429134 767.420079 ] -/BS << -/W 0 ->> -/Dest (general-policies) ->> -endobj -297 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 739.670079 498.679134 716.270079 ] -/BS << -/W 0 ->> -/Dest (create-administrative-boundaries-between-resources-using-namespaces-manual) ->> -endobj -298 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 719.270079 491.179134 704.270079 ] -/BS << -/W 0 ->> -/Dest (create-administrative-boundaries-between-resources-using-namespaces-manual) ->> -endobj -299 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 700.070079 498.679134 676.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-seccomp-profile-is-set-to-dockerdefault-in-your-pod-definitions-manual) ->> -endobj -300 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 679.670079 491.179134 664.670079 ] -/BS << -/W 0 ->> -/Dest (ensure-that-the-seccomp-profile-is-set-to-dockerdefault-in-your-pod-definitions-manual) ->> -endobj -301 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 660.470079 498.679134 637.070079 ] -/BS << -/W 0 ->> -/Dest (apply-security-context-to-your-pods-and-containers-automated) ->> -endobj -302 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 655.070079 491.179134 640.070079 ] -/BS << -/W 0 ->> -/Dest (apply-security-context-to-your-pods-and-containers-automated) ->> -endobj -303 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.673228 620.870079 498.679134 597.470079 ] -/BS << -/W 0 ->> -/Dest (the-default-namespace-should-not-be-used-manual) ->> -endobj -304 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 477.090267 615.470079 491.179134 600.470079 ] -/BS << -/W 0 ->> -/Dest (the-default-namespace-should-not-be-used-manual) ->> -endobj -305 0 obj -<< -/Filter /FlateDecode -/Length 4758 ->> -stream -x\ߏ$m~￢ l$'`H6|~׹8?JUŮdEXH}Xe?,.9,)#)\i _@iI%;_/o9RiI9%VXRX!,)V L,EcAGV䠱w.+ 5'KGV.Y-!),kuƨ<(b'lX"&=jk(rY|J+a$ XՀ t >jH@x\]x A а8O#Z4, 7jX@[ol԰PhX@@\kX@\RѰ԰XIRNQF%™* 5,:.d3iXdMҰw8 VѰw]6^u )@k4,]`.a:cj  z9] ߃H[ p?eMK԰ wmT^YlŒ+DE.3kX_Qk Zw+FÂE4,@8,o5]WSrְ wKNdd K jX0^ P "phX&iXƣQyЅӰu xXʚFx]ca5& "pӦ11e *iX_JJQÂX x(T^\p4,HRy'a -P$]9 .(4,@E[@?@%5,H!b?Yx-9U^& R Rհ{%ckX_\Ұjg@, Pk< ]PdkXJ3kX}\T԰;M ʃ. l f](x rv ]q 6y4,(Ӱpa`l<_gcOTBAڧc_B Jlo,vta$go.{c%Z>] /`e~ŽI>]:9GUtb{A!tu1+m _o=f.=HO!͟хa|V>~hx:štפW{tagx/Q $u0štפW<{tagK#%/zta_wk҃+S]{tagX3xOB)ޛkf]]Z`4y>:joӅ%:^K _?Nvo'J-N}tޤ^9Ncu-2ȩeƉ~O.cޛ{z,?NvǥY7;;}tޤ^UNcu.~l-3 OP@w(Y^׿j_.Kc\dw7=~-~Js?1>7h|Bkc8\~gL_֬)luvmL=&r? sι7&/v{pnjEԏ,?!9}Y㰁os62ż:f8@se'n>pg9e\r[k!o1CZe?ݿle B֔_0H+?YJ6.1Փ9Շ5gj6g,yn\#$\qVDy1r:ޭիxXDRpMbtqځ Paqq=2iDMc(~!DR7Gt]"ސ4 U;G_VkqϮ~H%9I}S;4G|OjkJ[|1VHXd5ZqhX omkz[*vMu5y67dsoUNjF˘zn:DAfV܋=)alnHGlsYoUA41c>8o㐱O$?ZOsonټrNqz׏j*;pSqoM0Y VIqͷUv62gl޼=Nm;NzaǺ;0 ->F4 rwru_r\ЃTGftf0zYG=SMF`|5w(NeŃY#P5ev4>?޴AT^X!hd,v#K̐kU !plb8 ;YXA˩mKg=U򫓚6FBҩO -vQL^s€@}\iۤGqji3?Tݼx4[1>h6Yč;o ^BRF&ГDr;9/r*,F+TNe!ůG"6;y$Iu6֧1VLMǬ/2A36QŔ :jcl{u2CXh ʯyR;q1ZرUSt}\x]dn\LbA0ZmvtwDciv륦9G͈H_&+/~o7> -endobj -307 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 740.570079 409.271317 725.570079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://releases.rancher.com/documents/security/2.6/Rancher_RKE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf) ->> ->> -endobj -308 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 311.068925 661.574079 469.171708 646.574079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke2-1.6-hardening-2.6/) ->> ->> -endobj -309 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 646.574079 183.998124 631.574079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke2-1.6-hardening-2.6/) ->> ->> -endobj -310 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 351.653153 220.574079 461.230790 205.574079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://www.cisecurity.org/benchmark/kubernetes/) ->> ->> -endobj -311 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 205.574079 165.615800 190.574079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://www.cisecurity.org/benchmark/kubernetes/) ->> ->> -endobj -312 0 obj -<< -/Filter /FlateDecode -/Length 3687 ->> -stream -x[K$ s˒H@$F8E|rX=6QUX:0|fEARUG*Wk+ϗw'J{%~K:ťrMwBJK?7Mz7DŽstoJ-' VJaY, -Gg&18j* .Y bbAR1XC7y3S4x! g˵f -xDGrᐂk.眪cȒ/AŃ,LX Y(7y%B@4W! <K2O.U"oBp I&#b"d>5Yh0~,p"QՈ(MK%& Y| -BXRȂؒ܊x1X@@$P,5y[X@D%2YX@@[XX@[-XX@[![X@\-, . ,, `.;-, .½XX@@]J9ZX@]-, .q0p#Md[Xtt*YX] -XX]QVula|Z ܍ճ ܍)$ `ennL>ZX1[XGqoV]@HH`2QXX!1 rlaA -Bƍ]ȹYXHTdaA>x-,H@b$.da &9j wKda+G -GjaA"7 2p'" 2p3YF P׀5bŪHa>}idதM rB@@*8ZX+VJ 7J>‚AH,Y(]V-,(PYP2XX<@y>`ȂJ ‚2cЪ6yP,,(Rqg)WK@ [XPdAXXTjDendAma*]BFȂj‚+N[X $Tm9ZXP9;)-,@ 4y0aa#da?8lc %(jaA%ha|SΛ‚! *> Nd yoaA  .Y-,hqψFYΛ‚Ɛ%D1yES3&erfeΛ+*b^wS2Y<.*la8o -3YYMȭ敁"[|d^@L,k6o V ޼6_c| 퓾pYl!,W\aYd(\!kѯhٞ#/ޜPo -Y5FM%7O| -g" 9oѮMlg5U7zct?>Xo}e3Lo~|_\W<>ʔ?o>Ǧ(jkyYZ0U]cϻ[|FߧMnI_zTyru=<)U8eݘsmCOCSS^8\Nd k~˳:[N]yf曮w|C?}yeVs?};hpY;zGo_i颏Q:}^g|kt8: o>N/h!!=^ӊ>6K4}~v{2=\m|/5폲*V}:xs^>;0:s)G9=.ly.>Wf(TBW0V=rO]֚;rE66]N~U>e{9ĠZǼg -&w sxgZK,OǪov<RDHX5SϓC$t|$Cv\f3]#gm//tno;87<ܹi;XI޴e̼b~aؠ]N^n{"CR mFƧ1L?6=Yv]ru%!3kB}ׄk@^=ѫ9'-SuyZuAE9^M#9ڍ~H &5 =Ym yU~ Kw=?>$vx#W59Կ}k|pU%-ɸ?+| =j[+ej|ּ);Wh6{$Eoo?I@p} %{ -endstream -endobj -313 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 312 0 R -/Resources 4 0 R -/Annots [ 314 0 R 315 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -314 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 450.884598 712.370079 494.898026 697.370079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://kubernetes.io/docs/tasks/tools/) ->> ->> -endobj -315 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 297.976884 697.370079 309.064286 682.370079 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://stedolan.github.io/jq/) ->> ->> -endobj -316 0 obj -<< -/Filter /FlateDecode -/Length 4307 ->> -stream -x\K$ ˔DÇI#b`Ɲ]luҫ3رޮ"(=>'59xz{xw ZbwS_'l9 -'Jp)v-xÿuљRka7)DAazIɅ5b) bĎ/Y bpAcA v.+ 1<'/YbdYcA [BRX uD*w -51WT^&71 Vc Y1d %Xfx}N/B=xiXcx] -iX0chXX骼baAX e Kd5,BaAby/D.5,]b=*4,@\ViBwb5p( "pWM b@@(iX3R԰ !ʋAÂD @ʃ,X֦5,Hx4,H dа)ѷ@0dAa¬aA -39U^& RbjX\d8x#ᒆ<Y*`)2!2x ְ.xjXdA4aAvYf$ B#5YÂHa&RAIH~l"Qyְ g'fְ giX۔|3iXP ӰP4&kXHÂb3M/%O7)~[||3iXP(* h*o4^,%F73o"WI.dx]DQ Dd ̒qfuǀke@^VI3 HDfkeLK&lOU9$9 ܂ݏcWmc?~|RwF'Lc]l=@!HƅrFdzF^ωuעO`btdҗҋl d!?, #=#0ˎV"v'yqAϮv4`߭mLmT5q:ăg\2bui{(!hs^heExjnCim( ɒ> lh65ukYYWʺ ņ2JCeGw+qРAϮv4^E~]QWtOK!#ӅW -9-xYwZ<3Z|Y_:d}v.k)h G߽:}3.lsR"Jg_O7o?'ݾ 񁠜ҿ՗W{Fҍ[U q[˴{9o(qQObEyܥX/>K;N[RJFR_[YS+'_ e ʤ}IYM#]3\{H34RTZӤ* itʢކ[Y)mZ44G{h; xњʬCm37f%Тf4*Nj80|6Y?.ۉ^~1.35ޒ;&ͱT(&O'bs(mWͿ!S~c-#d~8qy{ K*}EK;n|zwlZNezP`9`yCVCv.LK?M<\}׶NXwS_B_}>픡Ѷ16ok7>:nsș.延cKs:ri{gc߰fߊUC ?"u xy P4rfFds5,ynZ4b<#' T2ybfZo˟_Z" }^7_D\wglS},W;~F}ٙt@[ -F=;QO7h\Gp1H]6:+̲SCzD0)?mShMNPߛˌb}zŏtAVa)x)4cBw1\ zA: .7MMcyb~ - n =,rnь0PaCÄE{<6.-vfUAlT4.ٔ$iwx.#nckKcOKa3>B'$Q*(1rw~WTW~zþ1,oR,Sfs ut/y^&mrFs>4izn~Ko7g_tUt,6'X.Ʉy4Xc6F_/ -A~ʹW0^lNomgțc:rI2MBz0ے1y(Ev|l VYJ+ӽmI~FtQΞ PBnl,i$=Abj2<dl!1\LC/6zlӯQ[C25B٪l{RnjLj,"oog-7:oםzUrvfr+du,vI-c7N9y$rX.]裑WWqz!__F:V%YFجl|C y-;.t7Ɏ~_qG-y]Dg؉m'Y6tks ^N{I;J S u/ 73-@Cf.ۭQ9;Ku8͓|\ĝK:얊Ya\;y -/}-7K!~x.kӝVGAכake'"{{9vA}\c`BS}۱ ѝwjh#ș1C ݬ6P -S]}puh1ubRGU-SL:+CaxQV+ވjifKfڃʳ˾yw_m0x -gdJZ(^>Xuwyfj;_#0$y.yv=f a{JVExg,Mþj!=OW_R_D׺X7ƭ<g/Aos'x-*O -endstream -endobj -317 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 316 0 R -/Resources 4 0 R -/Annots [ 318 0 R 319 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -318 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 527.554475 101.433071 508.804475 ] -/BS << -/W 0 ->> -/Dest (cb1-1) ->> -endobj -319 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 195.360432 101.433071 176.610432 ] -/BS << -/W 0 ->> -/Dest (cb4-1) ->> -endobj -320 0 obj -<< -/Filter /FlateDecode -/Length 4053 ->> -stream -x\K ϯ bA !a5V^=yZfE~Er-t/39xzwx&Kr2(TOtgs߾8k)%z?I9%V:RX!| -+:% FHyJK bYaeAYbXcA WBRXBUy2Wx.G睉x.yGdbb+&cu/@ƃ,L9iY(UyD/A! +)ñ$ :Ӏ,d 5$ Y ְxkXpRkIw)tBLPӥJ'ZR}~ArPj0/?"enmvz}'J1췯8/ -qR"N,᫯?[HQZ ^V $gqm?t|2nm׋eS#Aֈ1-d&c,* @.*^b'z-4mUQhBV8E>,o ՗N{Zw74vv_Nva>{8|s{WbTfbBR-i]mT W5e,[vc~8kCM&7Uc|«8dlߣ4+YDCe=Ia-3ǡYm ve'ͺi}qOMo]ge{Uεexi}W4M7&qMbuY8$哯]:V*Grc-67B"|-X쁓<WVK6Hg[=M^u> {ϛY>_m9_hc̈+Ykս=ݖauu 8P1kϛ:t8t/^8zUs(zEnnm]_oF]W}7]ew66]2.oE7 Sa7ى {oIǫtxqcraoD9w0p('z8vvG;-8]KVb$x1=Y.1bmq%Ѻ#ua kz?7ֹ:~gkXwjr .E &}quC/m]^v\#yldBL]ۚ@߾ɼG$8s%tz܎^Y3֧cgsٚY顏Rlon )8dH7L>R6v:{]0;E/e"#2|:f'1y |!Y3 ]*^MIIX&7mg^ YM[/H>Z,0_ 69ôwz-q۶;>Ǻ6e,+:׬"'|}հٕtŮzG+&HQ徚j_kQSeVŚja^ggEUEoSZQo{*h/WLr?¹y%9XˇU8cU8S>_g_婕A+4Lo*|^],GUIstgc?JsB!~>tJԃ eH,Ut/S%UJz^qᖇcÁ;yp__Їr -*'P%?nvDI*K0097˹ϧcL?9.Q0 VKcB(#OϧZ, ->X.=m; An-70-&ң;asB )?@a -y - GWS*=yl,[z)6MS -,{R{?O=uoi2Cݻ)f+)U_ChkmC\q6b1!ٛr'%׺Ex{[VGҘ.j˦;Ll5vot5`< -[7Bm]5 L9o ֏&iQJhy-O\+DnO#1dml^.JMfǀ<7ɎD {dM'vAϪs>Myx:`Z:>Ty" մm$TZ O -tP_64c3;5yo%fHەN!j:Z;z'Nry -^HN~ua?h5^wAVo<A.ms5T.yv}O晰lr򫕺O`یizb%=OJyhg˖"QL*ʯKVw)Md/|Q -endstream -endobj -321 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 320 0 R -/Resources 4 0 R -/Annots [ 322 0 R 323 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -322 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 564.123057 101.433071 545.373057 ] -/BS << -/W 0 ->> -/Dest (cb7-1) ->> -endobj -323 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 179.034971 101.433071 160.284971 ] -/BS << -/W 0 ->> -/Dest (cb10-1) ->> -endobj -324 0 obj -<< -/Filter /FlateDecode -/Length 4066 ->> -stream -x\K ϯU "A Aa5V^Ý]l%&b_ׄ2ɹÇ5)X[Zl.MH TbBɤ\LJ]m::SJt?{rJ6(%B0)V$% FH 4`s"*%b1Br֪<bSxLңsdb.%711xCx YBd l5daƋGoUdq9y vː֕Udђ+ބU^yV*MI9m(*oouzx8XAl.B #aKpqp次pJ^WXx4 x, Uyְ;ȂxY{ <Жa-x-Bx-[x.Ĵx ϑ5,\RѰs=SЅ' opR~Қ_ \vD߄s =L&BḓI!i kYk_VH( -1mKUh>WEN[ʱk -:d}r5o1C)SYhDv* jI{w}V ϋZ3Jp_kёGt1-]6J(:./(5N268pL#iU{~I>45ӫﱙo~wֆׄ/z3*/V^J~fm۸mF9y^(A&q~-L:A&c˺dnJCZekbA¡4k7eM]ލq"k։1܈m]>ƞ?MmBbꗓm Ue6c3bڕg3zk[ql}G.e~K,rIcdj}3Ix3ƭ4) -Ui@$indLV5׵VFV1,˲,3u(E:RŊBx ]q|v>NE%>&kYE;hŢmHL =sYsW^I4i%zگ?1fޞ0mR]CSY-}ql{w׽ _eӺ7.˟' $k(N{jș.2޻.q+]>ZQԥKIkkX4|&zHUސP>JE>EPVF>d,[vA.խoGۺNIJEMf -sx/鼕/`ژwCZ1}od;Zwv z hs5zw?4ְ:6Ƴ&aB,_L.\1҆>9w56M&ɴi[g'QmшVẉ_bo15we6"$Cq)pI&8|-ͻc8}Ɩ@OYjO)̈́cMM] DrRH"ʍ)I/I0os%7i>[$0_|/Džew#z- o(ɂv^0>6sd/_Nx.϶MѷtܬRnҺ`#1zQLķR2wYzYn@ V)rݭe̳bm+꼗/%Mh<"?&ky^|_W-hu?<އM/]rFoRĭ.R^Q^uvc_:ac,{gK׶ӽLyMKy$C/qkDL} pb!/m}~iC ^v})Py̒c]E7BrSe|>I5Rf]eX(̶R9\ -s+h =v}>3y)ӭ}Ǯ6A7[3tkEWKt>$ύom]t~O}P\iNPSCk7>)A!~mЌiȕ!qoWZ;t:hTZ(}WhpAX>nRg{-7-;>#?BRZ64ӛ~2)7U5M-W*ȳ|[ 0_I7;y;갦4Nꢔlu؆:l%SNkX9m r!9Cw`d&s}A;fr;No;|#d1&dIOl" -<`a!7o$/0ji'a9NI]1G^tڼ?|=,vp[7$7Fn3O?ȔGЬrxѤZRGPܙ'O { {3ҷIRmRb^.q$!q%MǑ.#.Aq9MXd1 IE~\Fȥ<> -endobj -326 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 545.373057 101.433071 526.623057 ] -/BS << -/W 0 ->> -/Dest (cb13-1) ->> -endobj -327 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 194.231993 101.433071 175.481993 ] -/BS << -/W 0 ->> -/Dest (cb16-1) ->> -endobj -328 0 obj -<< -/Filter /FlateDecode -/Length 3986 ->> -stream -x\Ko$ϯs$$A8Er0rЎW6muWϔF]VKfbc-~?sٙK|Xaw=a  w!A V{ ɂY*pb XB%kX%sH9" #9lF4c?|wݿ {1};,"*{N[4) "w'?7;I!ȃHxvmy\ ^1p A97NuhwH}^\V$pr?e7c7 TB%m[->/뼷Z}^\Vq~^:[/7Dۧl3ܩG\/?k,JZam4 -4[_u>xHu?LݚMU u%DeHi1q̄tQz|r$*X%FJnB'1..lCC݀?|l@_|՟}Da"W1.r.^U@^=\^6ckl JڊQۍ. I9N 4:h}֧?᯴8롫&o_d2oܯQpӪo^VũU_}^v6.: -]=m{_Wj2طs^w܊bm8$#O.{mxUMεTliGE6)Z(cW `zo<}mO<?o[ -]^u> /2N}U|ޞ}aum m̰6muq?u/ni'ѡ̳,uӶ7_WWO7ektm 's ܆:nKy1ښH>0߭iÐy3~P!I9B 㐴Dlpc@>UÂrږvmӕNgm ؝pfJYy7s`YАy,6Wwh#i^o7@]7ynöи#%Lj4Hm}~nCB28=6-& ,`W[{6cL͔fl[7Ol\YG%Iy՘'C4PSN3-k&x<C1܉.Ni.-B} 7,Gg^+&p,ɐ> 7q\Xn޺[ؒ ˿߷ya]u|j?5 -1v+A#.H^5ۺ6Ү[}_o~-#YŖz}Q~; u^|ZqQzI򥣘݉8+%Wε|\rQϗ~ yB34izI¹' ()RdOrG%ܩpLKӽLIIג## gD4| r7f~[Ч(y^?bI+qsi>LsCKj--=ً|X^O%P7;“@Ŋ/U8?UIe}5ۂײf<ۍ)gC./~zyo۫CfYܤ \<DQlVY*H:_̧f]g ݏ5юgHuoMƿ5p W1cdC7(ydKֹlw|g.Uz+O<.w,TE}䇃< -y֬ c,vi'r2% ϶N&8FM`QI~X!gtdY=rFv(!vAv8;>Ivdb$eIqP]!:lo o"Ω*U"Cuz;hU5cCxB:g_vMڈvSHڮN*Ϯk~2MPB;-$OK,e̱-GwO ?BRZ6t[;N{Ԕp4;MdTAo n^Il^I+=aMlK :Vi/;Zz*]<{V7a]?+WB`IÔv)gG51Yt1$ǁ+9wdw|'cs~L 0F*ցNm)> -endobj -330 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 579.123057 101.433071 560.373057 ] -/BS << -/W 0 ->> -/Dest (cb19-1) ->> -endobj -331 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 227.981993 101.433071 209.231993 ] -/BS << -/W 0 ->> -/Dest (cb22-1) ->> -endobj -332 0 obj -<< -/Filter /FlateDecode -/Length 4004 ->> -stream -x\Kϯs3, $A$!99Z:C~bӵ -PHfbGv2ɹOO֤`]T7™,'?'Jp)Nr-tۯNס3DG{Q7)d*PY* QQE2b) -fĎ3䠩`;U 5̠" ;Y`eNQ0NΑtHc Y1l Œ %t}N.Uu5]-).DWVuFKxJfVu:S> &dﭦ#2UV&)&E`K:u_M>嬬V'[O.:؂EbS +.iR2\k 79k(r1``8့# -` c: kXlA -hˈ `vQECBIY,~9f1L|N~@=IYK 4_a`߄ f t4MB?㗝0TLEm샢!Rihr#(t[~Wm}u7uQ :o׵{zg7+Ral-;뼹_~uVm)zۂ;|{ؓ8`d"/y^Xoh5Nv+e|q/G̭D߬!K[NJ n.t / /H>g>oͼ+fa9Ŭq,zrY{"epgk9oe&>[YqV/S&Cl(|#vom_lmpiiG?W:~c64͇-n&k}U{yӷz:ߗeۇֺ]jchrjm6[Z֎mkq^~E+_8nq}:} ]AP,]d% :Ě>ED&8'͸O NR -;ٖdKJgT~rQǯ^]LHJQ<ѯ;ȓ qYe^cO.K"mxk;} ȉ|ORqkZj~Tt=q@Z{Im@c;uoG46c;#r;>h"_O4| {B3e G! >}Q`0,ۍ:  M Ⱦ{twp єOF1sJψiX_}X9aK昳klbh3dy{gφ->!w/װizvZzQf<7꼟zj7ʾ޶LѦQzަSc[~slI*tmQv.t#8&ky WVjɥ/yՅAw ۋ:s Sb3qc{$W\4ua]Q} ۲F״b(wɎӖ@W3[lf%.ٔoe,zㅰg9܊ʙxiߥFC矱|;/yLJ gzfdhR^PJs!o0Hȱ7ǎqNCep0r] ʶBVՅ>z5yRm/볲[NJ5#2zkl|9 egb" G]b@W2,vx.nIʻ]g/F! .'EM3&sY726aģ\外k1Siʳj鞟Py8^]$?S׽X\c4R Oab =V_lgLiUX]&ϳT!_GH EWYCw*uXqewQJ#fW(tGᱝtq"O' 5c/uC,3rn0Bi'vTEZ=v8|Zi8 F]xw2Ύl7;[0O}Z:ɏ&sirTӜAC$ˮ̋F'>qgZ;b.f:^`)ϲG-xͳK@PU/ 7+/"s3v!y[u8SgJ>/MJΔ-".FqtXe;3% N~^B֋Fȥ:ivm("~XfZ;-;{?xy}7c_">Ot Ltq9rgE}N 9siLj5FiZv]'.-nSlպ[ꈳ48Ŕz:2Ynx-AiΒKfECʳc߼g2 L%?>dluN"Ro=<_iDfJ+U6 ay9.yu'S~~0M$7EyY4LV:9wC -9?8S!Ѹ;N~_ h> -endobj -334 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 621.123057 101.433071 602.373057 ] -/BS << -/W 0 ->> -/Dest (cb25-1) ->> -endobj -335 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 444.376036 101.433071 425.626036 ] -/BS << -/W 0 ->> -/Dest (cb26-1) ->> -endobj -336 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 237.629014 101.433071 218.879014 ] -/BS << -/W 0 ->> -/Dest (cb27-1) ->> -endobj -337 0 obj -<< -/Filter /FlateDecode -/Length 3870 ->> -stream -x\K ϯ  "A AkmrXicW@b5d=X,#Yݽh\R,)d+1G!P2.揇9{)%z}I9%V:RX!| -+:% FHyJK bYaeAYbXcA WBRXBUy2Wx.G睉x.yGdbb+&cu/@ƃ,L9iY(UyD/A! +)ñ$ :Ӏ,d 5$ Y ְXaw=a  w!AO V{ Fd YaAqg Rof -Yԛ(-L,)ʃ,H$ԛ@'!/aAQͬa ԛ#,fR 4pi԰7jLgf8zb`U=2^DXHDezj -걁"&,OU9$̜dn{1хfo}{?oIYq0~(Ԡr^:D%9}DTؿȐXdvHfx3/J>/.+Iߔq冐@eֆ ޺{w}^ ˊh,߱) (Vrx{@m?j\ΖI7˟F3|ʽ: 0/߃[?ZK[ ;V>+)N;y:O\ -C.KUslf޿{X_JS=_G:*2ݻGnnOl:\gu.|ž/,<ўggWw*k߼]mW_%RƜ]v݇3_˚>މɲڸ\9Nz.[],=x?BAnr4Qȡ/cԍs>J7RdK{zkcv {V)8?imd-=sA[V٤5OD3X]Nם>_|͗{6vḟmmynn}foݖpm_,WiƦ;nP1 Sfi5Kl+SrJnKɞecyȝεD-#!I4oKd4^<~̹n{E@⫮NFZ~7w+`*lê;NSpEN'^1ip] * 5V=Ƽ[Ƙ ҧ۲w=}/Hcǘ9sHZm?yv7گ\?R8%y,pnW})էRv NI)<)niMOaт=KkieɻOvINz-=N97Wl5H;<]So:}-ԗm˶2l}YlY嫳L׬r :s?K%X`_ DӪ.g{"ȃ{^Rka}( < 7LI;{a EI򒂇$]Da nb}ݒ ͓t@: LiNvˠTl4yDW_"t O⸛$jL"[%Q5 8N.RY_.[no5N*4:xlɮ[]' 5t 9tS~ܐj}&s}A;gr;䝉.owFVr֎Nx:Lï</n8g^_y}{|v[79 N@ވm& 64kq yt[KuL Cw&̈́+ә{"{3rImqm&.2|ĕ4!\SG\̃r 6bAΓtՋY}9>?z -endstream -endobj -338 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 337 0 R -/Resources 4 0 R -/Annots [ 339 0 R 340 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -339 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 627.273057 101.433071 608.523057 ] -/BS << -/W 0 ->> -/Dest (cb30-1) ->> -endobj -340 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 314.026036 101.433071 295.276036 ] -/BS << -/W 0 ->> -/Dest (cb33-1) ->> -endobj -341 0 obj -<< -/Filter /FlateDecode -/Length 3869 ->> -stream -x\K$ ˔DIE"99;6Jb?fg֏xEJ"EQIU#s2[sI2)--6 kp[bBɤ\ǧ;?>L)p؛S -Xd -BTXL5Bb{V\rXP -+C =@ ,k,aKH -HAbN`"5&K4&&jbb!k<.xLIE']\N^%`2twe](xśP2+QNysLޓƳWyQX.BQy%xrCƏNrVv[sUtk"t52K  g -\ 5p%%i8ɂK!ЅsUt5,C^expTxd 5I9 W*x`vjXI!: <`sxgK0p{Tyax  6r`U 0jX_1.gҰ.kX]T^2؃^)h9 E (Cj6=.X s^ f p?eO%jX6cT^16ʾhXT^Â|f iX#RkJ4,( ]R]4ePo4^.%F7H3Po"WԛI=.dx]dQ\Df RqfĀU=2 `/UR +5zh5QY樞 iI=6 /1az4QECBI&Y-}9F3z>/|rR~,s\ -kt,`WfAـ:e -~LQ",C7QU23E`V>>ϫꤶ@E\v+q eQI:&=lѺ+Q %քQx[3B_&7!7iʈg˛ @Bs+idW_"Ѧ FȊ8}\e4ay|^]P,{ΏUSx]gu} [tSj b,2V]M[WsdTQaAw37i*=^ 095溊¡"2OނX˱㲥vWnc90>*r.(b]L1UKRO^n990mLw6w@@ozymj>Û=yśxݽXX9+̦=x͓jʌ<=1-/+K#1&3XgTlm4Od6}DJs[Yy-23婬TOC{׈yvՈqW#/q?oFW_#>U}^Tc.ϰmQd~]JdXz7r'ڳG{6wvHk&y Rޭ٭k`KiX׫L1ś-mI߻z@u5Ł!kT=%9 ܌BRepývy"\G/kS@q&I!/\ޛ[WiIޮ'lòh!g. =BFB$ ~>,L.ryկ#J~uFMn3F~y s3=YfOV:Wb1 mǀM4ÞHAvA7]Įl:;-kҴ׈sJPͺ:OJN e_뤐N9Ӫc+17Gޮv -tPB_[ѵ4U NS֙]io_dIZ˭c;!$uXALӸiˠJ0^J*B -,_,wo\ !7;yk;fieS>;fR bdJSO@ǖlu@XOʙHM ]iCzUuaN;v>W[,]>xZs2Ȏz&P 0Frۭul2-?0|pr26ojoqQG ױuC#Ÿ$+طDt< <چ =;754Am0l8]winpx:bOd^6#`Mb?Ҵ<\#$!q%MGH󠸜FMqYH7Rx5]Li\fm)/BFE^/^rl;@;i Ne^[m |Oro.fyt ,m#QS)n,ˌjsAatW1̫wmez{fwNcv4Z\2+8T-}eVvi<#3-Z~}Q_Zt5_!,o'qɳ\??ٟYðQ+]'0m4TWzBꔞg/ ,dS$#/IoHf9:mO`M -endstream -endobj -342 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 341 0 R -/Resources 4 0 R -/Annots [ 343 0 R 344 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -343 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 713.673057 101.433071 694.923057 ] -/BS << -/W 0 ->> -/Dest (cb36-1) ->> -endobj -344 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 396.479014 101.433071 377.729014 ] -/BS << -/W 0 ->> -/Dest (cb39-1) ->> -endobj -345 0 obj -<< -/Filter /FlateDecode -/Length 3885 ->> -stream -x\K ϯU "Aa=V3ܙ*hi,:Z|M/3K|GְraJEN <@4,@]Ӱv=az&awGOY`5,`'4,`.iX]5èalŸ uٲ u !@%0p,A]Ӱ]԰b?Va=xkXCZaARAS|he(aARb(ABˆb,.װ wY`ADu.yDj%W!hXs0@7C%g p4,@66IT^20$Ұ`l,P "phX6xaAZFڣ N5mFjRh<%Z+aSÂಆ v̦5,łOEaA @ʃ,X$֦5,Hx4,H eа)[- E S԰Hfraְ z Zxљ*/GI LkX7.iX1#ְ WѰd\dAa2]4, ԰ *3Z QKBԙYÂHa&RA)(~PlQyְ g'fְ gӰ)fҰXȂOÂb4Y8xjXP(taRͬaA&J/{-tgtr$I"g6J<./!5NjV8=P؂ZboHC;\|hr#cfo5}s7ֆ$yͫ+sqQ -ȭ6sȰ/ uNh6#~M.a~x]Gc^rSXyY*2V|[7[r|_ZҠtA|uyuq+J(hڟYMy]Blbow msde29=uY8+Puu=~?eZA!x__Z?'1t\ mcR'0M*[ݠ(fW-jgqH-Mn6|{YL8nadOp=ШPDn޾>,z^U8 | t'٧߬^;"Q3yғ[ϗVyS>W,Vn,W#Uَzgm,]si6clWfc2 7vuҬ2s[y&6glF=aRY}xw֧Y}O﯌S6Tjg hg":+Ty6> -rU#r|tz9B| -uݏ.ZYߍ5Us|ʵ Hm{J*,>|aD(K -/ +$󻿂-*?s7׷ͼ_Pz}1,,y<ӳ}on6ORGUthȶdϨ7Q&yŽ[jZ0;+)]SB#~N&-H/jI˔ őP[4f LldY=b+?b}L6fCNt>F6^l=g*޳Z_AO>]?MMlYq}Vrvbz/+dynr'YGbz8ɔ+v8y 6G9HC&]m|}xX!gKyJWU좄dq s1xLNpItCJMW].:uiksJ3PMv*Z˾!I! -kۆflfO&, {)AmN*i~2LxvJ$0k0{-Oݬ[0\wO ?BRZ64ӛ~2)7U5M^*S?J$⛝ULuXqm'uQJfg}QJ{޺klCT6Si Huؒ[]' 5t 9tS~ؐj}H> ǎ39'y[ǝlO59YL?IdqPܼ|E8LONRI^>3/:m^>~vY⸳-\ yd駝dFn3O?ȔGЬq&`o-#(uL Cuu'̈́+ә{"{3r0Tbj2ŵ[SK]qVzN1?͚t%yWE[E-ٜX-{.Z{w*.-e$Ԏn99;Zz:By@͔+l t\>O.OI<ð6|y.6c}ޭXuIOS/^2t~{OA[eRQKқ;F%ΧIj -endstream -endobj -346 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 345 0 R -/Resources 4 0 R -/Annots [ 347 0 R 348 0 R 349 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -347 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb42-1) ->> -endobj -348 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 465.479014 101.433071 446.729014 ] -/BS << -/W 0 ->> -/Dest (cb45-1) ->> -endobj -349 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 133.284971 101.433071 114.534971 ] -/BS << -/W 0 ->> -/Dest (cb48-1) ->> -endobj -350 0 obj -<< -/Filter /FlateDecode -/Length 4178 ->> -stream -x\K ϯs "AAK6U9|zt7!imH^4YHVw;[|Ofgr.)dM -~r2(TOt?˹9kǝ)%z?I9%V:RX!| -+:% FHJK bYaeAYbXcA WBRXBUy2Wx.G睉x.yGdbb+&cu/@ƃ,L9iY(UyD/A! +)ñ$ :Ӏ,d 5$ Y ְXaw=a  w!AO V{ Fd YaAqg Rof -Yԛ(-L,)ʃ,H$ԛ@'!/aAQͬa ԛ#,fR 4pi԰7jLgf8zb`U=2^DXHDezj -걁"&,OU9$̜dn{1ѕf؏ߟ|{ߧ'e!A 7};," -*2i*C(\D(;|N z\{WHq -7.yQx CsW䄴wO󼳎~pg5 GkSYha!4,"26x#&hgy%UAwN&;<)!#7@x?}1_=}[lmH!t|NRr'_rV|)ӸUuFԓRP}L5\IR'5`OUXJP!ncuz6~(Ȁ qH|6Pi ~/+/F+e;Wn۶q<|v&}Ւ][4-fp Lޚr&.fZ^ oٱC*Qfx;~ggǐMր8o'd/2nj&|a+i[3o&j!eتfrG3|TbSil2jo A%#_D0$LɡN|SZLrAo iKfyv.wy3.lXMots1%VXm'y^j1k|nI܎//f9a_m'iɒx-VhqX͎2TqC4>al_C- oꜚEYL*4Z=]i(ΜܿLh Lc6ah'e촣n 5nrDm -8u]o9>;Uȥ_c}!I/s-pJ堻n,EOxTvӺkg[tT"-RvVW=1!VLX2>2Q)gV< -^VQ;` -MYޅ7vG.qw}5?׺>5t_~m]\ʥrF$u8"Ofy?1xMN^Uqᵲi8Ϸ^ϫB /]wQaٖҜ. 8$v_;xUkVѸ\Q\2M;J^e_+G{ɵ! ڣvJ6!TK(7(EB[W|=WU1esd#QBUb׶Ue%+VXyQP^Y2`Xۿ -T]nyVd{If< ~},T~G)(MqLҨC[w y]>dxd1&do{M!@a>Ur֎N%#p2-^N?j$_>g^yu{iv[79ɷ$f"z`]mCǽGw;tA]0t8}7]9L 7{"{3rImqU&.2|ĕ4!\SG\̃r 6bAΓtՋyWcvhԧ&x:e^CCC},|z3\cmtmmI6@4h}dkj)bP5]J C[E-QOliΎ= --ν;GKjܼE đ-Z~}oiO=qy@.n6 aby:.>O$d a&'ϧFϘjݧw+V]҇) f_&)H,_#U=BI/ŒL{ -endstream -endobj -351 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 350 0 R -/Resources 4 0 R -/Annots [ 352 0 R 353 0 R 354 0 R 355 0 R 356 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -352 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 518.373057 101.433071 499.623057 ] -/BS << -/W 0 ->> -/Dest (cb51-1) ->> -endobj -353 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 201.376036 101.433071 182.626036 ] -/BS << -/W 0 ->> -/Dest (cb54-1) ->> -endobj -354 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 182.429014 99.933071 163.679014 ] -/BS << -/W 0 ->> -/Dest (cb54-2) ->> -endobj -355 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 163.481993 99.933071 144.731993 ] -/BS << -/W 0 ->> -/Dest (cb54-3) ->> -endobj -356 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 125.587950 99.933071 106.837950 ] -/BS << -/W 0 ->> -/Dest (cb54-4) ->> -endobj -357 0 obj -<< -/Filter /FlateDecode -/Length 4592 ->> -stream -x]M$9nDR` x а kw10} )̌Țj#w*3H}0$T(]Rs/_Oe7X]Lq9GI+[bA yk18b - ΁ -1bl F V#DM ^0R ^9HxեX<,R}xY$0{YJx P"o K,,^,S ^,Юb O>XJNja6y<_r'[@70I)Yj  'r)Fn,@3<Ȃɷ &s , 9;-. -RL *S`y",$Yk U"dA Kd mkC[X@@\*-, @.TZX@\vZX@]{$)ZX@],, .q0p5Md[Xtt -YX] ->[X]Qꠇ芋x g 3\6H0p7 -n(>ZX1YXEqoF]@dZX^$ ИK,,npM\(5YX P0}&1b]HZX ]8*@ba0F wC"n . 5yZ,E /@)XX0vq ^-,H]/D$g=&P fk4U#w} [ x;$2 \W*!):X ը @yUN0 -m7g n~o?'t(~.໤'̗<_q C[3BuS}LoH]݉:RM-f9'0+7fsL`(|Q0cUf\A#J]j~eM7_jzwU}=VyyDd-CA-[Qo| g~^5}4(4-5(dC24>y^\GHcITkS{>`Q٬R}|\ev5R5y A/C95E;rΡh8^·j<F_-G>+A9>%2:34<}$&w"d 2t6ԏi2vZ lU[tł.j -ofFxbxЧDZ -3bɽX -'bMﮣ7Fd]VbPd4ëOKom8(mf#+Y]IQx/y l%:/|+$&ܬ*Ay*٢ d 6|R*J4S[2qV#PﷲK1 ~x1{Hbzk&m 9Gi󗇵ʮ]<8uWĦILw#}~|᪣Ä~t+-' cݢeU\3Dzu8M.m\lDGW. ձ -{rZEnxx9x`U>*أr*&ߡ*Oe,*"$/}p!׍wک! Eq|cڀ!EE QD7Jyo`C/݈oj>~jT5EPQry%i{Ew$]8{}{M03ׄ0fo`'lQj"'p(vA薘e>uU[]9^uOx)$B6b@j} -C3]X7M&Y_Aj๖[|{/<-ڶAL>:pq \9sӄoM/1︌vxȗiO17N͎ɦ#2 /بG՗bƦǪQGgOEZDo5cxy1{I%|q㶾fF]60hfqݐpԴDpn#Q$u7w`A謻k MqY"/+S^>_S FTvCX0VofKJUΚ[qY(B><UyTg9h}vzٱ:3hE^{=Fmv7MޔyxΚPwfǪ<ڕWcI +iyњkHt|E` (A灓7٪{|ͮ^ۨHҷゾyy*o'YŨjQ{ھ4K'Uv[(=Ԋ(4YyXZb8'2Z:-m<Xm<O:l4Pncnjxn(6ir09Vy&h2x.y7ک&c,T=``vjm[z9uju D>hv-޸5\eŏ<!LbnEz#PZ>x o p޹- [7O+Ygt%Ā.n116/ÕyNlO*i7qjo?_?\ŶZw+>Ysi.OZUYw]Gr9ٱ *_=\_Oz%dxm飻+ l,z]k퍓Qh}i0ծ.DLaKֻG1hJ]IMfy,4T%keKCw Y_oecZE. *?SAp1zI 7;6h] Ex16kK[u%!7,rj:R)M2/ϡ$fh=AbKhQGjYdmis.@[M4Wk2q1G)buig6ezD=Qrw~)cbXSy)I}7o{nAlJ b;:W+VH(˩pX?%%=E2\咇_?ٮ'Lc"&`}TNjC۸XZ`oV3o^$YSE/,Hޢ'ogi EV'?I -endstream -endobj -358 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 357 0 R -/Resources 4 0 R -/Annots [ 359 0 R 360 0 R 361 0 R 362 0 R 363 0 R 364 0 R 365 0 R 366 0 R 367 0 R 368 0 R 369 0 R 370 0 R 371 0 R 372 0 R 373 0 R 374 0 R 375 0 R 376 0 R 377 0 R 378 0 R 379 0 R 380 0 R 381 0 R 382 0 R 383 0 R 384 0 R 385 0 R 386 0 R 387 0 R 388 0 R 389 0 R 390 0 R 391 0 R 392 0 R 393 0 R 394 0 R 395 0 R 396 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -359 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb54-5) ->> -endobj -360 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb54-6) ->> -endobj -361 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb54-7) ->> -endobj -362 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb54-8) ->> -endobj -363 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb54-9) ->> -endobj -364 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb54-10) ->> -endobj -365 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb54-11) ->> -endobj -366 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb54-12) ->> -endobj -367 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb54-13) ->> -endobj -368 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb54-14) ->> -endobj -369 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb54-15) ->> -endobj -370 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb54-16) ->> -endobj -371 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb54-17) ->> -endobj -372 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb54-18) ->> -endobj -373 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb54-19) ->> -endobj -374 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb54-20) ->> -endobj -375 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb54-21) ->> -endobj -376 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb54-22) ->> -endobj -377 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb54-23) ->> -endobj -378 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb54-24) ->> -endobj -379 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb54-25) ->> -endobj -380 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb54-26) ->> -endobj -381 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb54-27) ->> -endobj -382 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb54-28) ->> -endobj -383 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb54-29) ->> -endobj -384 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb54-30) ->> -endobj -385 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb54-31) ->> -endobj -386 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb54-32) ->> -endobj -387 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb54-33) ->> -endobj -388 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb54-34) ->> -endobj -389 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb54-35) ->> -endobj -390 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb54-36) ->> -endobj -391 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb54-37) ->> -endobj -392 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb54-38) ->> -endobj -393 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb54-39) ->> -endobj -394 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb54-40) ->> -endobj -395 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb54-41) ->> -endobj -396 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb54-42) ->> -endobj -397 0 obj -<< -/Filter /FlateDecode -/Length 5075 ->> -stream -x]K$ȳ K"s0`/~>r0KJEap\!B] Ƿ7]ױGi)FVXRX/1:V n1g1|d׬18' ;V5+C -k,a -a1*fr -%@A9]Vy<#ZBdK'ǐgc5,2YRxP K4^, -/AXWRyc5^Ĭ2x&ts/>gaQ, '4AƏNx))Ļɐx8YA .@EpIٱ.‰.c$ \ 5 csV2sА,daxʃ,Yr4, ,I2EܲV޲ABLaq)ְ0as ةatQNawѰD XB6 %k ܅9 0 0hX[Y\JFdX)@>H0py܂6sw7N:vA1j4x=,X 0߃H48%x͘Z-6aڄSyyWZ^lYDEx.3iX_0: l{ D yְ %'fҰ %Ӱ)f԰ ȂOÂl"aqѰ ۄ|ӱK7 Mxf -oF 2CEAMY[`M eְ fҰaMD@|3]L4hX 䛈lx}D|3dI]10^U]20^VQ]30_ɑE2u*֨x04/QCĜd[0sbty}=3&_yxMY)k?O$".cWKi")Bg1!-`.1cb"Cb")ws,.uI֡+3PĬ$Fםu]sYzE 9ґ(EU{+f率Ti^RS#)/#RDZJ L>X=$EGd#S3*O@T_Nr#e(o?n?11?O?CdIpUҬ/ly3n60YɊ IwCR " en ӝЍ=nBxؗ]Ry_KR I~im2 :R`%d<2bШc" d&Uxk3NJ͗v{UcB˖&/jrŻҢw:nɿ^!瘜yO\7ZJmҋnahdYyVZ݃x'䐵[,9Z&ܸ$Nk *l3NX&T}[I B\r~cK%`% -~LFr" ^qLmLdW) ㇎䁒-· d7> FSHAFiVwc=Soڱmp(ϝCxJ@=wۈ`alxJʪg٩0C؛ojk74U #Xn!hLޝHy 0!qh|*Gֺ}6[&m1&Xenqi>JrQd"9qG6yyYu:%G|5,#22w >}U>ΰf1]ad=ݯ]U>#߇Su+HW}Z6xRq_|d3oiN+Ŀn_@~8F?w#W??'G*+ - i3߇;iAi Ya uFgJhi9 H^!nG ML}xdH٨#%DN}!ۥݬ{yyjgSԽ}x=i!-y '}J9T_tIUٯ,ލ3U8aC&}w ʺV ;|uyh) uﳺpc J\] @dՅ}U>Dy3r}ϪW(%DN&`|a 󦼒2u'۫ liAc̳Q;ĒK޿ºj&y5.hʅpf[+ ;|E{d0UE}_-8ncSRLJU>*c- ey|^V]?Khۻ"Fz~ >QƢE׽Jw:/@M{:W UyI6[ !tuÆRߏmonOP+/9P7aF_PCZٲZ6Ы/]٤lA/赬{&چᆒi)֕Qφ2:_'hjTrٝ׼.{.GnVWEk\G|Iv=BnI,JUe:7I"Svɫr\u;]\ -@G0usd$mږcur|{lJ~>WzצJRwXj[{yW}kzAi'TzY,o+Oҷҳu~اYż~#pp}-=HO{2ͯb n./^E%33arr}x2rf}c[XKmJ:]k}aD|+nwC뢾Xp69\5gk;yn ?o~-z]/+6#SG8v}-YL:gD4eA,mJ,^/'PФ-)-1$zQB0"P3OkeZfcO^FCM \h{kv!L\WX=p9G\LRys'1@`GJ q?e㍚_z)$##/j_ʠ|WqCuikvӢY!3y,q Ȁy$BS$FH}ߪMޮ+D ,wo[QZ^.MfYf \v48*n-诉fn7yU>Nʺ8 =nRT.2FIܩ}3i`v4jrZ♘!q/[9t:jkTҨ()u+ӴOL>b}]eIݸ+ eo~`f"Mvr2^@U\9 Syݤq5:䵒fzÚ,QvR/R^@[Q'MxRxǝh:L& $_Bh6l(5yܹ yT7[IvLCuӕExbdvlƄ}vs&.e<SqjWRtLಛ*bnSyHS r^y(H.0B.ixLsӍVb*拹asy%"^EڡSfj1vөT.9T^m;4ۢ95FhF'jj?wʍM.@3[MP5;Nb)o<*]~pUVm3^@~68Ό=L --̵;GIjywmm$ԌjS\DhOYi7m$G/HH#i:OWIܓD&Z[`o`mT;azl[zLЀ9s:T E~%UD&X},IP -endstream -endobj -398 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 397 0 R -/Resources 4 0 R -/Annots [ 399 0 R 400 0 R 401 0 R 402 0 R 403 0 R 404 0 R 405 0 R 406 0 R 407 0 R 408 0 R 409 0 R 410 0 R 411 0 R 412 0 R 413 0 R 414 0 R 415 0 R 416 0 R 417 0 R 418 0 R 419 0 R 420 0 R 421 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -399 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb54-43) ->> -endobj -400 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb54-44) ->> -endobj -401 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb54-45) ->> -endobj -402 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb54-46) ->> -endobj -403 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb54-47) ->> -endobj -404 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb54-48) ->> -endobj -405 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb54-49) ->> -endobj -406 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb54-50) ->> -endobj -407 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb54-51) ->> -endobj -408 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb54-52) ->> -endobj -409 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb54-53) ->> -endobj -410 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb54-54) ->> -endobj -411 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb54-55) ->> -endobj -412 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb54-56) ->> -endobj -413 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb54-57) ->> -endobj -414 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb54-58) ->> -endobj -415 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb54-59) ->> -endobj -416 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb54-60) ->> -endobj -417 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb54-61) ->> -endobj -418 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 378.232628 101.433071 359.482628 ] -/BS << -/W 0 ->> -/Dest (cb55-1) ->> -endobj -419 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 163.788585 101.433071 145.038585 ] -/BS << -/W 0 ->> -/Dest (cb56-1) ->> -endobj -420 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 144.841563 99.933071 126.091563 ] -/BS << -/W 0 ->> -/Dest (cb56-2) ->> -endobj -421 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 125.894542 99.933071 107.144542 ] -/BS << -/W 0 ->> -/Dest (cb56-3) ->> -endobj -422 0 obj -<< -/Filter /FlateDecode -/Length 4555 ->> -stream -x][ ~_1H" @[4hX>lNv'>ǖe3LN̘ԅ,k糀?+O?o(79xNBME?*UbN.⯧ep,&K^ V2X".(`pZ,!#oYbp-b X V9ЖU!F́-U -rɃ ,^ .-KW]JIc"'Exd %&Ēej -duY|UrR ɫ˖8)DI&3 -%y&h0~,pB(b֨<'%&`- , rKĜB  bs& bǩf bW pWݦ)+! C-,H]9YX!KbaA  AlakW r,9B  "p5 6s1,-,R-,ȒA/EW2B gvpR`[Xw.YX1 laAS"W""s l %BDXe&oa<4rI xCa9ىzgi,PjTĄ@yQNFcv oPnw?>WߠwN@Qugŏq'g+K?2~]mOϾn-c+;:{Zf}{N;=\-mc0ӀǢvӚxȘ Ff`Ai6>.B|L3\6y}"?ACV鶁eD=DQ@ ^Uyd]]!^& ,Kk;|wEEM8{]v;1m4*[v{*|Buw}9x5p|p D+9x܇e;ުoZLYGMVAHӬ=u,@OAGm͌ԌdTy Pq?DŽ,ʆ3q}tIdRy}iZ5#˥R sb+{?cm8'W<͋u87UkҮ*~!v5,Y`o-QJk}#xwx8cUq=c=ÔBI{w`x`o7fX ~OQ_8~k&ĺakn}+XńmnR[q>XKD6$*EԨjD0KW;Af7Lք0fo`u5t>ceGCöĬ/{WFۇr?oiLAXƀԺ{ͨ0?GȺ1 f}9s-$y^xsm)|9n 76lCUGEԶۃq[=ZCo} |]v7߸9"Q*SQr=|?X"F}E8j?yq㶾fF] e S4jq]p4GpEM] m㞨)'}ٞ}~ t.Qo)8M&]nhrFݪM9 -ug͵lx?N(g:-&ucU-(&BT-hx{cuGi{4z9lטF`^ycxC2אp0󘝨kC|IJdWabE*/hz޻>~~q`I"Dj.@a>XiP%&zmEŨjQ{ؾg4s@y{#Fi8® -Ҭd:aCpᵑݝŊHl~m2ڌ a: -^yxn(aѓjLhX; r܍vnf<= kHqF-#ƠFsVэj?jWszl(Ra)I?P`|/{MXu㐾u:6]uF1u-smiytaMߡض䱿aH-CW.E23!=tmMC) Ƅ0=if=q4taPv8_9S+Azle5?XaZ_6хO wJJzt%w׹~]%O0|"Q]SbWӗ -[O s~:4"Q̚*A=;`. K(y|2+ -endstream -endobj -423 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 422 0 R -/Resources 4 0 R -/Annots [ 424 0 R 425 0 R 426 0 R 427 0 R 428 0 R 429 0 R 430 0 R 431 0 R 432 0 R 433 0 R 434 0 R 435 0 R 436 0 R 437 0 R 438 0 R 439 0 R 440 0 R 441 0 R 442 0 R 443 0 R 444 0 R 445 0 R 446 0 R 447 0 R 448 0 R 449 0 R 450 0 R 451 0 R 452 0 R 453 0 R 454 0 R 455 0 R 456 0 R 457 0 R 458 0 R 459 0 R 460 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -424 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb56-4) ->> -endobj -425 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb56-5) ->> -endobj -426 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb56-6) ->> -endobj -427 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb56-7) ->> -endobj -428 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb56-8) ->> -endobj -429 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb56-9) ->> -endobj -430 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb56-10) ->> -endobj -431 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb56-11) ->> -endobj -432 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb56-12) ->> -endobj -433 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb56-13) ->> -endobj -434 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb56-14) ->> -endobj -435 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb56-15) ->> -endobj -436 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb56-16) ->> -endobj -437 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb56-17) ->> -endobj -438 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb56-18) ->> -endobj -439 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb56-19) ->> -endobj -440 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb56-20) ->> -endobj -441 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb56-21) ->> -endobj -442 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb56-22) ->> -endobj -443 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb56-23) ->> -endobj -444 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb56-24) ->> -endobj -445 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb56-25) ->> -endobj -446 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb56-26) ->> -endobj -447 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb56-27) ->> -endobj -448 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb56-28) ->> -endobj -449 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb56-29) ->> -endobj -450 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb56-30) ->> -endobj -451 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb56-31) ->> -endobj -452 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb56-32) ->> -endobj -453 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb56-33) ->> -endobj -454 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb56-34) ->> -endobj -455 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb56-35) ->> -endobj -456 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb56-36) ->> -endobj -457 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb56-37) ->> -endobj -458 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb56-38) ->> -endobj -459 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb56-39) ->> -endobj -460 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb56-40) ->> -endobj -461 0 obj -<< -/Filter /FlateDecode -/Length 4707 ->> -stream -x]M$9nDR`laCOm.>12BVgĐ'RPw -WJ͉O~;yRbs'9xNBMEο*UbN~ʄst/br`U| %r V -Xł95+C E,*P8fUs`5Bl!zoghNO/JeBȥAū.$1t"[' ANq€Xqb@,qd@8l^ .B -Ѕ&Pe (BD& h˰ p˾ x>$  5ĥ”%`Ѕg K%.oaw i PRU;LV\,[XX<[Xݘ1dawG 9& `(h ;.X 0߃T" *?çV.,,n(>W]qo.T-,.&*@ba0aFp7fj z A,,9o.xɫR,,.`)ZXY$1ycZXޫ ‚A*5m F|RX<a>W pWM RVB,@A(8ZX -s UB>‚A@Ƀ.֮R-](F r.,,@Dj@mb ])ZX$s2[X%!CZ]ɀkW ‚a* rNoaida/B\-^.-,@ ^] ZXPbAK-{3P 2M Ƀ. 0>lH~l"1yЅ-,(%jY,,(D-,mj-, ⳰4L0PoF~fGJIlaAe"QLtAT &!:Y]be jJo f DDo. 7\ܕ -dx]D\ Ddk+,qszsdf#PeIU07 <_aei^J09d -`D=bϘ|`IkQ rKu Qጪ!|DFu(뢛*m=/a24VxnBPQu[t}h{o:I@zPunw$C׻e]׼ąn{w#w$J~g%řbv1ɤ"1hHՄRTle7 @6y/'o26_O|{1>#8]h >RNY*xX*Mƍ_~N>"j -IT(?tS5ܻӥ&%8 hsU9=ݮCBy=(?:[=R3x˨ -C _[D|pæ?~|`u~5n|# 6 32G㙘w;().|Xe0V>Z~iuk9As m#? K^dcr^wވ4EyK{[t`jb2F}A7 2NrH ]W0v@jޤ&DHw -~gǘu1jJ&zJ#^9<.qU[wuQ=`R;\y-ubo|%yk\Z\!$lɷr<ɺQ[y1K(u}N/ZF(dF+]!ڒ>jٴ"D[lQtݣHd=|"!گat[0 Xꨓ4,iW}ddzUZ{;AC5!: i -ʃj\My9~ ^Vك]t02ږ{I5B.}OwnA-i FwS*cbj=ΐy]wlI! FJ6Af.bX"_Q @=trfH__V{\: j7cӟB u'Gf'48Ш;t Eʑn}XC^䵭/k[̰*|pmdiv;Pؕun?&q=Kcʻt]OOt[)f}LtC~L[ -k/7 CG4!c?B|C1 Fo?U]̗=+,ohsz3-*?lӳ4)y>4Ow샎GQ -L}H zs]Md}[m@D'CɶQAHsnt>zN"}JLߦW@Lw)/A6> u޷`r/W|AE4M.蛙!';8"@*amdu31j$︺@7k냩TWpPtxd7{Wf;"mo8#r쨼] i1Z}>5ZW|WQ߾N Gj/m,]+L~ -b*+tC -zB-7J_hOC";Æ; Ag4l\Xچp/GE-o'Q:60@r&ҭ}3,ԍ6hQO~ߚaq/t)#LHKO zpP=pEr9؞{˘tn_Z y_O[.SPxaλ/=]:m7lݪLgrF<уk2kN4NYU5;T'sCF2Ap-DUuv\␺i. dbjRNߘY 7Ap1]>pZOi.y55,ꗵI^߃{PvJˁ9a94ͧ-zƕs=9ap~Cr9^J:=hb-2连u5d_ v1/'=J 2J\^VӞ%b~Z{wQݨ41=Ev~pi B2k޽wa%`z*Κ -y.;*@~"5O 1>w]y[ħ@ZFi4)U;UZ> = wUΟFMҺK3$j+gNf6#{2Dk0u* G+5ғxj_#ڗn)/'FiXᥙLN.~ˠ"6] -hz@t"%p7)=Ll\F7;yI3=uaQvꮐsٹBFy^؆:uDϵ cK:Y!Oʙhnˆ<{c)L.AN;_fr#dowF|Z&6~MV/Af>8( їܼvݾ'fܧ_O4I&ȉt:G^(#>}Zy<c85q? ACD}8c7hA|zՋ=ڱ͡3ٚVoehLJ\i1k'A\̕rj6jA΍Wy -Ҷ)K<\u-w1AL\1ѺPaq_UNڡS_fj1v\eshY=j;zEQrkЂ7N227ʍiM.@kMnY{L1{ZQ(󨤫ZozD=ٜ;?JX4Kw*hm6۞HbrU!{w.2V"RgY eE'L?/KJA %\咻en\% c"[0>c[L,t_CEe_fME3>EJ,,?} -endstream -endobj -462 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 461 0 R -/Resources 4 0 R -/Annots [ 463 0 R 464 0 R 465 0 R 466 0 R 467 0 R 468 0 R 469 0 R 470 0 R 471 0 R 472 0 R 473 0 R 474 0 R 475 0 R 476 0 R 477 0 R 478 0 R 479 0 R 480 0 R 481 0 R 482 0 R 483 0 R 484 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -463 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb56-41) ->> -endobj -464 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb56-42) ->> -endobj -465 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb56-43) ->> -endobj -466 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb56-44) ->> -endobj -467 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb56-45) ->> -endobj -468 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb56-46) ->> -endobj -469 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb56-47) ->> -endobj -470 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb56-48) ->> -endobj -471 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb56-49) ->> -endobj -472 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb56-50) ->> -endobj -473 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb56-51) ->> -endobj -474 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb56-52) ->> -endobj -475 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb56-53) ->> -endobj -476 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb56-54) ->> -endobj -477 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb56-55) ->> -endobj -478 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb56-56) ->> -endobj -479 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb56-57) ->> -endobj -480 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb56-58) ->> -endobj -481 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb56-59) ->> -endobj -482 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb56-60) ->> -endobj -483 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb56-61) ->> -endobj -484 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 340.338585 101.433071 321.588585 ] -/BS << -/W 0 ->> -/Dest (cb57-1) ->> -endobj -485 0 obj -<< -/Filter /FlateDecode -/Length 4634 ->> -stream -x]KInׯ aAva h}Ȍf&ѭ$`Ȭ;[)Dӗ59ZZl.,e]M%?3!dk9NR6:wqgojM?2%gV˺b49VrKUcAӑ!5 *#PvȪgG brr8oʃ (xIPzxޙT*/x!EI)ŢjƋ%:" 5^,! /9h Y#lA%hpדOP Ǫpt`5,@ 0HK4,]WZWjҰ w]j\KjXTAÂ| kX. Rk~Q@VjgWLM}w0K_>+:ua>W9z}ϫ˚Jv -y]򩣐'm^L"죝^Qޝ):|V2Du28|/`}:Gk,=bmrTڿw?lƎ~30C3qNeE~"Yб@_bc\X1+aVѿ<edNS^&㺮{]S]O9x|?vݽ֩ subֹq?t+%GXn+m<Ə%KDeV[ۛ:{STiEʳ-ӚiI_G擰η꒯ۭviaM׽~XGo,ڄ߮S^>xWZy/]׌7ہ]m3𧯫leuN¹^MYwrwTv]a䁙L-_G|q>0$5}^x~DoJ[m-QQuQ͸t!yKg}X'ټpI0l k2I HaoQ8ń?t7KTwl]ZzP~`<'o74}78b>si'w-ShϮzW'ՕϻO -!޶Xnܜ 2Rf) -dk;HcǮ}TC}5-ݻR}:=BLi/(JƜafzw;a%$+΅%q685 ܐ#rMNXc7kII F^ۮ:ְ|{)<`$"ai}%;tYPgO >٬Fgv  7uyS:+{_Q`FSmcТE SolD1S<$>h>ox} )^p9.xW<@xxEjm;}y܄j6np-=&z?]Mڼ -:yQp;@`-mmɾN_v [Ϧݽq־m3io [yX{ӵF ͖Et -}[Ya (w;;q=~|?cӷi׎[:0yދvaIw_귊r?sRލ{+V ~UſJmuy#V7Յ Tۡ#=e{t2۝(,kZ3: -~rc 9߰2.ePw->oRm| ;[rLqNkJ\Ikc,,lK}[ocYԇ}9xtEKQ{Z|<d+X>o*o痷}$W澏g6 -hg)Y3nc}&/"Jɾ7FE('vi7+8xiI[K}. - K|r;a%>w eŝO2v:1~7=;}ϛ!vӐtn/'4w]&Hh#j2}{؄!5= f~3Ƶ&q8rZabW9k~D%/j~K>iՅ={;`do{sc;b_a+R{ˋko|@ω Zo)6[皲J/NU˯YW,/\k/m?\%ojF=$L4CfՎȍG:\Zhu>agmWj$d{̱L3#Wo[bz(|i$gǻd #ъ&S;$ѥg {J7v {˱!4I!/l/vK7$jo.':Z;G2֮)4PE> -endobj -487 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 563.554475 101.433071 544.804475 ] -/BS << -/W 0 ->> -/Dest (cb60-1) ->> -endobj -488 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 341.807453 101.433071 323.057453 ] -/BS << -/W 0 ->> -/Dest (cb61-1) ->> -endobj -489 0 obj -<< -/Filter /FlateDecode -/Length 4569 ->> -stream -x]Kܸs=H `׻9Z$KTͺўV%C:K|Q/Z%bLӧIB,.&k|;+ip*OO8EJ^+wFt*A%aTΉ+[LS kU6Eǩ`:23 ʬU f,*JK`hF(t>&X]N>XK{"%8-NY+9l&NaF:آc0.I.+:"T.R%d q N)MТPI>0: [tgtX|8x™#ZunFl:XV[Ph[dKMr$6ȱI G:9a} -ӊ##ac`Eeu$qѰ8.0hk8.0`[ p\`@V&qZ< 3%kP.8.0\tkЮs\`*qQp\`Fqi P8+B(9.]wu@@4Xvj'5(#Yo -q;[@N pK8.p]1ml%TLUP%δ[P' xwAp@9.p]eSs:Ir\Pp8.@&tY]2q4腅`V8. ?E8.]w`5С2mΪLR9xWʐ8.mr\Cq 5>ZB$ H(,pE2)r\4l1Zs\4lq<ovx[v|`a "ơイ"ƛr\vǛd$ƛ16Ǜda` Ĵ[pƛ`'NaN}oF f` yK`&Nޅg9.ƛlW<쌁:씁 -윁1;i315@ -촁+N>)*81Lh}s`f#e~O߾E{?fGAB[Wh:o7$08و -8Oe#0'AZa G _AbQ`z[0&NJiV\@%1%V󛏧oo5` }o7|.U9LHkpEaNWp9* ]EbeKQjCFz`&V-JXk+J1P|C^s=b+z;Rd5MFMٯܱ8Cʡmب~2ȽH^!YyuGWWnUs<-Oe~cqNjo4i z'/HN'¬38~iY,?ti-U }ΨwpX!r5]ɖңp-E)>ܗy充H2h(4}KegԽݘնsi0~833YRe}ů-Oʧwnd m;>=odF8>r7J n - 9B_L[g~c'uT!v,{ݏyW"aTr>W|^_?tZHg}FUD9"׻~ruD8s΢8Curk- {5ͭGM{;ޅL^vW<J~=:C>pܙ<*] !EZIǕH׭w 9w|p/Uы;e9JݠXJkcEjW/7s&sGgnCIYi&9ztԭp`áxgzn8C|vݐnE!÷5 "sԙP\F׈ [s8^Uuܯ/L/\{AhBFPO"G8h_\!㊿%Pfⶭx"_no|098ymwD~A3W}~ᮺ~_̪%vϱ߱r0P d08Oɜhe0ۯh]tMxkwn_avN=p_[#z]ox}Ow<=pCbcGSrwƨbXp QQ{v/6zos8d{@_~䙝1{(Uge%0ӕw4&}=*й|>Qt*6*w o}8G9?=)7BqM<0n9T -[7bNGSe>0Ju9\?M31\N 8rď|be -=(iYUV5ԇ4NgW~jW&w%Z>Lg\2fZ^ -5QWS/6C4lKE+#Эd{T>oj:-:EՁT5 ٚ^JY%RZV!F*u%d[=7$mQUOj-v$[å=psjTbJ7SMȦ2!#Nڈ4Rs F't1v%~o* -WyVH3U$*^:+eC KKP1KKEɄϤ[C[HIyHżLRRq5ޚ.|>LdZޮeF0B7}ĥVv>lqN?nN~xyR"+|uj~\rBL{|yЋ6"Ԗ~ºڏkMڶ{ *BʐuV"|J:2Oa_.M9dc{*\el:Ӻ3IW9hҡDM$,[I3E*L΋\7"_It$\`C/hVL軛ד}6ٗګJei%<^jK}9x[ մ i{:9i4..(F4hsG3Eȴt. EVS &?G+2qdK)TI%hBtV*lNx[2rΡݝl!/Զyeޥ=۰%)'4'TȠ H -|Z+-In+fzќ\ai^> -endobj -491 0 obj -<< -/Filter /FlateDecode -/Length 4479 ->> -stream -x]K# Wz^C$1HFcyF0`琿zu7%f]JMփ"?%M9jDFcÏSZ, -+h4EM`*foc8>qn|^1GrOoEN+Xޫ+%, diˊr bI`%(eea!1LQ` 9ZAM3^(=Hxj%,]%pج%,] ^2H$,@|SFtE^V:$aJ' ȋ -d$,+"?+$h@Gl 4*g5xh1QY  ixlh ӧ*"bf d܅f󱟾;|{?w+'eAPZ+n`. 1.A%/B<4zB"Br΢7g .@2:(F}`9fsS !#:T5;t%zwח%Jh$ye!o4~oyh6!dYwye]w[I( ++ -Q#; hh -Dio*̾?N#3p/__~{gZSï멾x~}:8-|Z -`F~f盭L>oʻ|a\S_K, TKgql9b^}]6yIm66Mav l[[շpz2uON=yގvғw9?;fʟ*5Oᖝh*G,, XԤJľwy8 XzX oi{x 8Yϔ|~z܇Sz;pz#'(WN6Z>fF.BܹjmwGz;q`J壭ֹYg7MV-}6Nq|Y<[J hƒ{vͱ[޺z[YnE0zߝzh[i5E 9~ ,3 HKx^ށKsrhm:}i_8"Xں7=zU>[6ZQ:^g&)_\/ K/a%rg9:Uw^?'y⾳Yr]Wa/ou/TBk8{&VK?^ipz=h15'X O$[y!vv[ߕѬ=/d Mߥ c&MxmOZ*w[K~&Zi-\rʅ $0u,e1e;=׶Ͼ=\g1e$}|}uX_kk)+aȍ);KiV9kYj5}6=43~:M|Nv|?N՝8k3n x/(َb(&ߩ#ˡZ.3Ɇ,],2]Wz-mXڶ[mt[jVTǜ<57k+}^eZ0u5Nuo]-|NOuLiOܪq=]z۹SIylke5DMvsښ֨12\kCC3G "X9=<-u_5Wzt*N:Z3Y'>A[=VI 3Hs-#51I^mlmGT11ƴUٗn~ L{\ IŨwS}ńwyG0s1*.Ls)99o s@ -ʗ&zu\ǵ.+qoTnH -T7IKZ~ǘA]ԇ'Wn[^} Jo&8zڧdq]Sݸ:׺pq*xT v,"ium7ei5iK@B5J7\}}x7\C4e8f0+O\!/g7q9z^3km1d$įi S4 jٝaQ>g\[&u~pZ{N}^nzE]Kޤڤn70:W겝et|KHˑDRlo9Ů CWejmZLz]Z[S-Kt\+WTx*W6|[f+L8m5iݚ,R6TӮ՝&rֲo}H@D Ӯ͗gbjD]n SJkn Sw+^[":GkodN t@ оLtӸA -h|o  -ߩ<卡nR|xovRI3=t!Ih;mvn=no5N*17:x,ɦ[]'35t wS~^}`&s}A;gr;n".owFLȥ"/Io_?eG(,Og -endstream -endobj -492 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 491 0 R -/Resources 4 0 R -/Annots [ 493 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -493 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 240.123057 101.433071 221.373057 ] -/BS << -/W 0 ->> -/Dest (cb64-1) ->> -endobj -494 0 obj -<< -/Filter /FlateDecode -/Length 4604 ->> -stream -x]]ܶ}_(P-j4EC{m'(n -$}V$Gh{mi| I3CY+U"=_~Y`O'Oeu"%;>! JPIes"TiY1QŢ:bh؂[5Z8.0[+oT…5[ (PJpwr\`@5k h9.0]cwANV[` ¨h8.]dwэ4hUz cXr\`:  .]w՞E$ wA!` { U `+b8h>V -qߢ>q\pT}F Us\Ss:Ir\P8.J. bwAKxa!# ) @B"w+1x{Xl1Qs\:t[O#XR)8xW*0J&>d@(Xs\)qO:| ; Xlr\Z$"A5A  "I!fpa RL&b7M$7N,<ތ x=;%x3]Ls\7rc{ uy u씁[v@|4YFB$;m Ot>3| "cl$Ώ7psi)Sj -@'4Cpƣv>'R3RIl$_w^XXÿNopxʭ1|wfyAIm=Ҙ3;r+]$:[q|K v?NDW -^]ߢw6y+/oqOEm/r $tȧ\uh=㴅d61Ͽt,pz;|[EL][v8|OڴHm3ʈLo]߻kȧ둀IZl,t;ʺԣG"-J}[|RkyEQaYFz:DgFEkԞֳ;fuYږw?E #u0ѐoG^=h`4 ZV*3-ݷ"As)6Wr+;ԖU롡iԗoi6;gr̨'{YtqBIEY={F.>E^ִVQ{59'ګHhm7ЗX9hK!>}54NJ3(d{ -xf{0P8'~U|!orY/9@imKG1wFߪDw;D"hBq7R1%gz6Jҫ?%P^zE^ǹJ'Ȩ#m,N`D=ٮ`"__|mל_?SY臭X`6/Op/w=S\+װjʟN~HMI7gomy(UT꼑sljW-vLyoiS|.r@ˆ|h67K.*HЂ'M {^nd_z@Vj'*xseL rZh]PilQTLY-1TtőPc&ִR+V񫴹jdj(C:RX222OsWm)Mm.L.6C|LeV)G5O7*숊mM8jrؼvLܝz̟395FmEW}JlIt_0Cjv3O_ND0䡢Kӆ2Ƽa{.P.ݶf -endstream -endobj -495 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 494 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -496 0 obj -<< -/Filter /FlateDecode -/Length 4520 ->> -stream -x]KȍȳA0m`.cQR<$1vv{P)2  ٳ7!/?~:!Xbq1_59$>(p~=/z_cn98}! + ^a11: -+CYcA hˊrb1ȹ߲2pђƂ6sTX@Qyy,J!ʋ4Cdj<8i<,x YYȧdY\^E⠝du%YL0Ve?pND*/gRL[3 lAڄSyyWZlY"Py  LDTawGx]ѰX`hX6XUyy09%  Xr -&IT^`HV`jXYÂ5콆kiʃ,>9 ׀U|`Bw k<11kX65,Q.iXdNÂh1 B6!Sya5kX  Ry"iXz>' ,9 ,H4,@F0d[]@> ȂLQ ِ2cЪ nHpx6jX# Vװ?Haϒ1CECr5,H5,@ $Y jX\*3 5Yg& ARE &Xi)UdLhX6kXX<4,Hr3iXdqiX۔f԰ ȂOÂl iqѰ ۄ# LdoO샬7 #EQyISV&I2iXCfҰi֛-$ͨnw94piаXo"LLꎁ2be`VQ30_Y#+]U0Q m0a}귨!"f(p Bv_Rl۟O~{O/wʯE0&Wp1݌bMCf%!bnBZ&B"yf!9Q {)I6$[',>p3w׹)rDemmdΛ*%4ξ_&o;؜m/xD74º< q]UP`1R2>; M,* - -ǻPjbH,Ow?||r7+oz^WVd㈖<˲(t*/knYfU}7齙[3~k{kUnlonFB;绥ˎg% G#d.U91=s*ЦNQx+3)}Z6SN:}N,$g[JKr6ˮT^NX;?8Cbj$'خul扅}neZn6.|{-ivC簵^jw_:l"7K,)etIs:YIri^fyf9_ieieޢ*b[KQdpkF^KoiK(:OgI_+\d>q52\A|gYec?l؞_y_]CҖNR恝%ٷcu*slיKmv/wPE[3c:fn?\g}vΗO+er/\*ܴcuRodxu#W+吆1Xߊ<|d%3PZOy_}Q$`9׸~93DpJk07esx۹M-OfSz~qqtr1{kbZ[U/u-̤:\c)4ߨf3u=8˜w6ˮɭɴD=Z#ʷEZZg•_xcyt7 \[ʘaW0l [ܢ x$\05rFVKԚ$Y|8"*˷7jS T7s2cc]>|lw49Hu`0/ǸBy!^2{N<.B꾝r5ɨS, -j)?,"גm #g9tW0G[@;v:Oixx}iC~顦 Z{o/nXmm6w,WdMn; Y:X'49KmEEFrjbsovuGѤ<'t`[C05v'4sj´%b?e -vˎnˈH47OtWJ.m~))ePC9"ʟNa<Վzg^&d<2uvT=_9>+ZJdDu9Mwb.8?lɦG`kIuA -m. q~kj[d^E] q뒈f~64$LoH}.R2:V,74*TQ$- e[M#hQUul7t/'tW*)(M:Si*W*uBΓB74MfMzrSHZnnLZ*hLݧxv6<%Y\ٍ/'ڐ_Oܰp1v+9f/*{N& *Ry7Iau"YK%PQ4 Xl.c^_6n-]5v*1*x,ɶZ]% T쉦).MNʦvlg\mP':VN.v;/hMOFvFYGlH.Zip -endstream -endobj -497 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 496 0 R -/Resources 4 0 R -/Annots [ 498 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -498 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 176.373057 101.433071 157.623057 ] -/BS << -/W 0 ->> -/Dest (cb67-1) ->> -endobj -499 0 obj -<< -/Filter /FlateDecode -/Length 4623 ->> -stream -x]ˮ丑W@|_ ( Ë6h{$R!*dUt]dAR!0c -/?]¿1dTOpW( N',aə/ל/?ҐB's'qAP8P-H8C)J\ lH\ l q Cv%.CIG7 I\~Qd曘 6YADEuNS-8 M$ yQo£C17.ft]x^` V+ de3(F alC -܋*1s$1h31^`XR+1lh S􉇨<0fƐo2[:XٝdS|?\~\>j? aLM3Ihn[X0 -i>'b-Al$=XYÿ.S1k9RtDл/?_U/JQT5|7Νdh$ OSݷzhH4а^8%ݻlc5ј!_ --7al2 Vs*jչ10w'&o?`Mo4aVv<N%>|T95y1a8|OK:>a>s ~ʪM)\74e^\BAP23IP fkVr}Z`O 2hmAöWygr󵺑黖yGRFRi:AEj_!mA[mZZB!^q48c岾Ry}yNx̩Aԇ8/4}+Ѡ"⥧їRǦhL6r f0{׽s6TcOkGrql|IQ@ R rN8t9]JM(f;6nul[OV03qf5~4B<*j~qw[8\5h=(t(fb~z}yNcn3vhf]ھKcO Rbvdzf3~=G;6qa=1) t9lH-JZDi֢|lk[ӺqXX,Y.Gu-m_juor[=%? -sڶ\3"/ِjDNk6q9Hkgnㅖn[5^{ ƎY0Eczj6/#r/?"cC$v9x_9QyW&jr[5wۢ+6Q'yNc#TU^Z$oPZSFi, &&1 Tz}yN;@۠4(G{iv$ojpwa׳~m_dQUYOYܢE7GmzK tm"7Cak}5?ifϋTb'Z2hCv9R#Gƃy2M#>ݹQ젒$89ʾnP rǷ~~!|MJ>?0+xꊷvPɞ_F;wg崃YX?K/irsoyΆpG< g'Fĺs:߉q~?_~h|"ٙth|_w tߪ;|\{\:sjj^3b>5{O$; Wm߯Z 0 -t̞g<î?4Xd/;_m߅ (qMo|"0vDsE^ִ{,cw55GޫlxrmiNj{{b=dgOm>"s9yb[ӑEPw7mw.7\;ȼkWD7|?Š_~_jF?]Ɣƍ枚ڍ3\SU*[b%Ը@i˚rb(e1oI*fмAWaӔ?]i7S>E&]F5QYҥXs܏jޢU]=c9Ocxщ\ (,KN1ag|jYK*]O˧6uS- Bz+w=q󙯦8_lp)xڥ%] Vb[Xժ󋰚ΫN/iM`y$]pYJ_DiUjר*̨T B"QhBcV=k$HTӥN.b4W[*TqɚJ/,PV h2#ʖõ(m"Ío 1\\R++Bʭ,^tYdy3DJ3*Zr7x]I\+TyK*fy}騄tkZc+)2&IZ+8SXʕ\"v/+b]`/ršλU{k Ex6j\dUGbLRX [+;ɤveu&[7䞗i/tC]jǍla*|$[CNq*kaBCKZWPK顑j!RWU˅nC&6F[V3@xkj:2meNm9\}ɊU8᷃Ӹ2$_Y8I!Z2,#Nx8eLe+33 Ejg7b'̍ȧv2l .'`ie`>KJU¥Ʋ,_1ǎ?_:RC,N5ׂV'Lls/JEh(*]@M~Ve(R>"i[V7i,p8ԒQyJiIil{mZ_WvT-&SLwR1:#j{M݉ރC((py'(I+9V E`E[Yْo -C mc> -endobj -501 0 obj -<< -/Filter /FlateDecode -/Length 4435 ->> -stream -x]]۸} (@[4 t>8(n -dпCJ$GX7pl͐pxxfH˒>*}_$=ĘA )+%fEZQN>,aəO8ş?~s>!%o;>!JP)msCyA.$` dh -0Rt -f1QPEa)hV%a&I3trAPi;QJEdnptF>&D]N#| KEIG%%-N)I[ H\"RK:6II\àH\6h芺4 Z2 -*ID]$-qxPC%.]$q*gi-6 @i+i$2` -IU#,J$q)qY`0p@l$.'R>Q; Dl@ MQ``5F`` R  I#p[)J\&b" 8*b]@Bk!bK\r$q̀N!L hK: [dK\L:%.  UW Bc- WK:Ry%.䇜*J\i&RЄv`&9XGhr3J\#l1H\lf )؂O₤d @)%qAMC`^f Y&x¼Mf lqHQDlAҔy Nz$F+Nwbf ӂݷ5G/f~);eO#A( In[M3Ie a-u!u#5hqtF"0u9mO1B `E,__Y VX!zdvW*:Y1Cf>%d͇wy0zxΎttc7 /ʅ]MHyU9=StvF%1;ܮ\3N,\ɶE/V뱾[7S7x3\B 1ｿ}U>Xn@* h mP>tH8k,SrZLaFbr?}+r6νAk-e|O;->/~O~1κ e*UMM3Ɨu4]s۩͑Eb{Zt6wֹ;T&#Re|>%m!s -E@eϳIÒU :wDìuŦA'չ;DnoYSGE+ - ĸ -ow/RmY Cak+Zq(JK?ak|єQݡb>b< >|fʏgPo}uۙ2ffnH,̗cJKHYސj/d -:3#ٙx,T4`})swy-[f ̴3tׯwֹ;t~f:DgH!BN"*ig{C(]Eo䝫-2w~۹ݡs;yF[ܑkur?49;BwZWWx7oQn&~g{Cs~1@w:w {/ki6Z75Y^ r{YPz+ugr:{3^mQzܿYfN?8ug~Bd#኷!qk^rrV֟wֹ74}\?箵?w꼌ggYIko~3w++wֹ;t^9دr|e["<~_!B~Ս&|_5tK>A {;Z/br94X/wf3 瑚0.sg{Cgؙ{ޥ6Jgrecn+}i`{|[m/?m/raB2ǍlXօ<;k?|*+G==ޘL$p}m):Uޞt-X1ݺƞ'fS}8QuDJe;ۼKQ-ކXo;Ut6?ڧ0ds9Fo[mZ5ycT֖ўC̼x9B-+2> myMS[|u/Mn ajw_GTVϩ>W3ĕlűA즏Z8PSd}6Qgߴ5g܎ֽ|ņǩ>J]/6ٳ;]f>^vХ_kG-'m/c|/~bÚ0c)R%ڮPlVX[縀<ޮ{5AٹkW,3{FιF~n_^<⑰qqō6x֖{Αusr^vӨMxYc~>F0` sB -v5dӑ .XKޑ9~ 1񈜞Rȷs4mȹvR-_NS}^y߉* -{6ic0[0 i ^m}Ox6\8hur41:7*K.35b>RCcT|Dv0XL|M,TGSAgY8}T-,^BvB7 iYҺzN[W?W{Z-xT-d˭G Bz-νW!)qӑo8_m7HloW(V1[ ;]|S:߅t:͆5 tiR$JjSջF5eF&udj$NAM٨\XD\ ZsmB+{T=MP9^ت1>9qjc"ÍY OZ.] -*вv8.?ajVY=p -פyM R$&;}c<)]:Y/P>n+<621yHռLRe^Q-L֙GS^Um0!F]c/*Z75{-B}ĦAh<6["cxhkp^cI=CKUo섩[633>O|(l>;`iD>]G=򦫬A -lo4?i#}qLudi&}ֱ,m'Km9s1=ڲlٖS p2iզlv(]@M~VRzE/StӎJsWes5lɶq8;K\2 -2k7)k=nP7TjnU&eu;RWvGtO@&塟*zܦ@m\]g{dKRO0YΏoMx"]V]jI]P9*+#MvR1?7槌M}ʔo!& -endstream -endobj -502 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 501 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -503 0 obj -<< -/Filter /FlateDecode -/Length 4760 ->> -stream -x]ɎȑWY@SoЇF4Fi0::TEuJ0?NYUlU"+fݟ?3s2H}UNHz1Oϗ_.jNXbv0opW( N'g0L ⯗?y}5CJhwO";r*AT !N1%I3\ CKUT0* KAۥ* 4I* J+ءR("kvǠ{Igc2It0NK4x]t[\RZ94tl u`%]-]-@WuEy%]KH%T q3 .Z$փ6Ê$ l%Q[UFYBt gCj5Z9bL Q[0[T` KJ$0)J,`b(+рIn Vi茖*KL`5l!\Q[l" -( qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ], qZk)z ,xגVxZu8X޵Z ed$.XLJH €5h%. q8swSF2^e(1B+q  xW'?aMwu4-Fy' xJ\(q8~G58ԒMR8.'q0h Z. *(qƒ`QIK\2P ơSJ₤#MC`]r%.HV!D'd=AD!DuAS-8 &IybI\|3J\0&"zqK rK`&IEd%.MDRn@. >3((Po *{ -9i3YF/Bmh ݧv>3>ɄeAKQٕbۏp׿7NY%ω%bt5Lچ&TM iˍM#MA lF(3"OИ(EKjL0"_Dƽ»Yw]~1yo2F N4hw6p )9oFjw[C1*G) {$ r Er{Cm]~0F]?|?퇗˟e"L_rgc~a?J. ZU$nAX6^ߩ ټ+6TǢG֧P>]jfbP#D?u鯍Ӽ~Ίg"ZĭrE8ρ-c_4S۠7NElNKd4q(I뼅 T?H/B2}W֕+PWvjC0CZ؛뚩_PuoPzIPZMman_p|Ά霻2cC^ 4`Y2!!+r1-&42^``0v cLcט!y!~r|xF:1M9;~o׊~װ\n31@A|Nw(QwIPW͎quvbȷ>' 1KncLm2B ]?-g~Va$<3wbGƋ6G_׾zr;mZAe&_s:TnǗfky |(Ӣ:NF@ Oͱ:ٝ.h1y=҄cy4fd5~nᅼ=+͜öc:(Fc<#ߧcuΆSڎC7s6yñ{H#}TϺ,kwf{f픿;O/9Xthڎٌz͌y;cY,5Yny=-)vKEk)+gBu6^\E:C^i=M7]gifZQ{;B ;vezT$QxǛx鐸)~㽎#Wrj]9>oǐ_wY ѫʨ^A n;v<ߌ\z$/ơ4/(yWwf'ssRķm#`!wg7vh3Kv/_fUn.?뛘_ċ.Ĭ,Qn<:zK9"wn_^2Qy+2 #=oF:Cvzi`kk] |LwnG-+l$;v:gC߉EPlWwk<*P.#ӛ`!s'|n=A -Jk,y8#:Xt(=vϽ;{@#׏|xVlh ;13W`_/Nws:>=߾\+mbB~=s:ķ7Ur֊bЙA9mDs:DzvlfT+K[t}+#}|^G.w -vw{G2*cs:C>Y9m# ;Y%Wcl[`!q'F< g'x|̃uN҃qcARo,oPW99ŝJm~3ݝ.[{:緣n_| WP97 w ̃uNƝG w`|β*`ߪ=ޟ:q>{fo'̳ݧLs:nǪk&kǷ^f'|5>DMs6Djups~ |~/Enk%Fa[ە/,=?N#!:فF~W=Ny$B4@RG=to1߿:>Cߏy;sBwN1br>{3E2f%\S_NS<~]ScgXsXL/?BR>;s -,Ϭ{n'B*Ik -vuO$y 1*hmńW(ҾiuzI\-)a{ҜZMr8U[z#7(-n_u -endstream -endobj -504 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 503 0 R -/Resources 4 0 R -/Annots [ 505 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -505 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb70-1) ->> -endobj -506 0 obj -<< -/Filter /FlateDecode -/Length 4338 ->> -stream -x]Kܸ=H aøE0!?%,IgƑUŢǯl -jIw1|ypR]p -^#^9|tY`C3Oovȋ?S}6]Jhw"ۅr*ATu!.* JI*ADAᆥR $AF)QG5NΣӽ31$t:Igmi%].J:/.)-|qHI:B6IV:bb.I.+:Ғ.ΥH$t*:UNVaFa|tx咨/*#,|!I:!Fa-UőjBDX_P@k!+q"qݒJZ % 7k' ,(PJXpwJ\`AA ֵ ,hRX%$. 𮵰uY޵Z id$.vXLJH B9h%. qh)#qw /qҁ wA!NN V{茕uiŸ0VK\:bD]t@ i@e%.p]g! xW[DjI&) xyp4 :]Q:bwAKFDNE0 %.w -y$.]嬕w!uF#q0m9dSL!Jc%xW$.6%.! LvȂ>RBC'|c'qAP8P/H$])J\ |H\ |A q2.id. 2E d]LDCJ:o@ע.B!PP%.Zໜ.I\7$qAHSE.dN$ ӅNk /%.&bXK%ΌD]N%.4JL) hBO^l; bQ_# b4y%.e$.6z3H\|A'qARiq蔒 ! 0/z3J\zKh=d#^b1LƝ_?}W?Fߝ~RR.~Ο>i& 2~x׹LGH\֓J. _-6f,Siʎ6jx}}Ͷwڮd<~u)taDƜy*n</W,sû0Bew2z6US b3uϠߌu/umsdVͽx`}6CFX2Ĵk\ 4[P=W9Y0mfk;}XXu;O9" Tzݜʳ۝e;ffZWPf~*O|H8n^NzY\jNZil:.xK.9k} q6/Vg w;m̍/_ ygȀe̲/wcv0{=\{E`I'0ӕoL߭߁. -R')_lrPIѮ#v׽woT۹rPy=g^u }=rl;mԍL૕qǙ+e9k5vQ;_3׸9uJ~^(D3gq!;{u;mԍ?һ{~? zSks_#Ho}y={F{zHk6GCI?IyvHk6C\_ 4B {7nQ&~ᐸs~]#6Cƞ'54vFp~ W5_Vo9߽9J)V -L z3^}QozE30~(#pW~l<H5$^[/O9ǜg9kWz6C\YrOGڵkO({ZϼMR(\kO*W;rйWz[/XדV+7ںE;mȸ_F.r[A~w_:/WzǞNáu*=NLd&~ΖGjh'B>ásgK;4uVr߲1tmI].mΒKIzm}[^y_/ASm3oCY,m򱬼nxvCF0KQ7+ ڹ[ l]F˻J{djV7r3дLlǗc-Fͬ|~l9'4َ|>0ZH]mmx~4Ͳ5khsNGvJ4E6xeysrsGk&񌤋<ɕ'RY3k0t֏ݐ$,tA &NHz6y 7kِy=0e}n<7LچӲ'ߗ^&Q>v䇗=u6M:{GeI}geȷ8  -0<"?3:_x&Ջ)MxO"ALԈbCGUBD433ti^ҺrGmFN֕ƕd{WIBpbAKzQz;;g[˶ -X[ńn)TtMlS2j&lKYp^^N8KEi~RQUfSJ])Y8 I~JՄz6j0 Q-J9At9\PKfJ7Wm/.,G6G-bG 7f!bh!~< v++B^4pgYd~*\f?hhG$ynV񴓸W!4VubJ(I=6.c{*yLź3\Ʌ85P~NUkwWmb_CqR2l4gr&6Fv2&lc/.ScdRĽ~=aXg>xxEWxD,8nTe Su",?}2Qa6Lh~ʺǍa|M\5b/%ueP]\Z25ڲqWY/DcphKp}RocϬJ-CKWCv<OR>O|(l>;`iD>MG-򪋬o+^1i~4Gpq]edi*}ڰ,'Km觇5s>(P˲gkӦFK-hr1ʤ?)%PTLY1hVoq{)ԜI=Nt|TlD-ٚ9ZZɚKFAuR+ilynD3k5G|LU3sw=sgDH_;c{5`⭢b v6O$e ё*> -endobj -508 0 obj -<< -/Filter /FlateDecode -/Length 4801 ->> -stream -x]ˎ%q߯k fa2< аS#/>LGUW 73 yxw4KNO)ۯ75EXO9$6N1{ <۟~wu}7ShϤrv)FUJi+b4>'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kS@IgR6YEt4)Dty -!$lYiIa)I[MQbUŠwKJv99'2t*Ŵ'UNVaFaBt峨-*#,lqt ocJl54ZybLt`%0$ - $01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq$. l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kSXdu8*J\FF ɤ$.p]wM 9h%.p]ik (Gxew`%.z-wu'iդSxN>Q'¼E/O:,qbx.3I\ .\Q;ey6/5KK}nOW>Te`}?2]@zfIڢaM)fGm258342Aul{[WݙRTI?;y .u|ePUV>LB,&eAحʴ}8T8{s9eRW^"& -Nr# gI~EbsK2l=y-Ca =Ky1Y.ٲDqzBmI~=p5w}g6uTӓREAt ǵT.-,XǭO,3=*-}l - vB|I5">C4.w,t/"{0g4.5J~s^:u5FXWaz`*o?}l^ʾ>˃!ls`  -K0&M9P!|-X -%-ϣiuU3|5Nt |mr7-y>v1,]~?-n9G{|t ehT8c݋yuluvƮ;D 901x#K.ej#3CVTWLfR]:Kpٜ"ZCj8G; yAN| q8<1岾R~=Ry8cNU>yeW;7UδbS4ڦTv_ј0)y1ϣo'& G<wF֛<7'>4*9&̢GilDPzxE^[h96^HǾVC/iS|Xw~@kIFsD_%?<cnvh6f]ǾƘ lRu|gfcs}ڡ}fOcrK.y84{YGيFlD6˺!V,(xY1&|aE/qșvik=m+ϫgKw<Ri#ʦ>NCM~Q1Ai{xa3Bύ';%͈*zS4/#1p6 s"bC≧wh<2+]WgͰkiC.Ď|?wLvawTFr߰w1!w|#T1X[F$oPZ fObu]^p= :xViҞyaƕ||qn볁amUYOYrw_Myo~O^9;v|B:by4o4y/U^|7|=3ЛIy=}0A{w.y8]Y¿J>?x'˾]*;<*O!K~Ufȟ[_H;yIS[(V*g/,;C,/- [dzJ}Z6چPz a]NW!MkhMtn^w:8)t:]:[wrR):⟎w.CoA妳)wo"Nt{ b'񢘄˥je9]637NyLB-NG̗P~_љND -;W,3識Z&5i]haLM t SkrM'ob4F*Tg͵)6dir9l\,6tP2}v Kۈ?|RWqe6qR/]J+L**| ~+NXI=]iYwfy餄D-u뱕u\#j놺&& -Ӹ U5uoPw;}^ʂfp.;?sql#(fo+a -F1A?JبʘRNNzz'>r+ -C'.0CכE>F50[Wb{E1W -۴aBwN=hh1]Ϯ:ה1nZ.4mYЋ͑ұ |kkH:ľZܦ}I"qGI3,#nxenL$u=PX07nm׹򢫬% l /i^i^#㾘 i&̥a$m'Km ۶rbZY=ۜ>5kV7Lz%畺*[UZF*k%jSXn)-Nb/St_xO{>*=IKyK9@9֩II]Oil[[]W;k놄oR2wHOѩ [ǪRGԊ.W9?^cr֪ͺ -VT}뮜-+Ia{mՊe?lH"IՒӛpQo(_"Kv -endstream -endobj -509 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 508 0 R -/Resources 4 0 R -/Annots [ 510 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -510 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 668.673057 101.433071 649.923057 ] -/BS << -/W 0 ->> -/Dest (cb73-1) ->> -endobj -511 0 obj -<< -/Filter /FlateDecode -/Length 4388 ->> -stream -x]Kϯ|_@C$ $ Z9cOiJjIb4U,v5"g_+Hwt~I -o%M%^ޞ$/.I`jO'şN:kʞ}TdK˨"TRFe^[Ǩ9ܰ4UnP S :07 ye֪7Wĩ3*%R:8"ft -FwN+Bԑyל<)8]98tXE$9|!uZZa1)%,iXF:yFዓ6:bԜOXC`FNH8/Z{bu1vEzQFHq^PđFPQ =F*HbqL`|!\V_L$ /(q1Em hnIFqߒT…5 (E 8׀;9.0 ] wq4k(8 xאxX:s\vFqwbi Ы8t+B 9. 8.  Aqw%pxWv(#l -|:_@ C Lh%X̘[ wU@(G3,s E2X.3p\ UӁw E`9.BqPeuQ Z - $ Iq\2y(9.p]iw%!auq0l1dUH t]Ü+8n -8:p\`q $%tHX8x e:B8.@b-њ R }/9.8.a>VtNA׬.@<ޓ@(V`.%= x% t8.`p\P$Ff|Aq2] hl゠fNr\$ӑLqA 'Rq f`JV_@dr\&:b,q\NqAEKq曞( 2> t"ơエ曚8.LqA4MLqKMqA$b:)2&؉9#q\Kq 7ѳK!7=\޵L8|-7 ^둟ʐf]1^.Hp/g $7͑Eep*J|VpY}j3O1,}sbfe}O< WJYSH҄ -@GtEpơ4yINXTy-9WM9}D>}_Fߝ;)kw -w {:,SuDlzZW;OZ6=23k:Y^CT w?^sV'`RJnKmw]H#oA!\;'˹3ܛ {}ey⣇yVeRxCyhGU/vw6z/n~ep!tqt,dkB{{p(3!C=z˽M{9iY>w~{,wnݘlqĠ}Q̣@ete'?Έ6CN֘q{ωiאBv`=7Ue^@;ovnigCw<9hs8D܅n,H7ъ{$U޿ܺQAaGwH6ɫZf-qt3hs8|^!W}8mwi:^<~{+8\!~3mńz.ѐiw{X~䕝O"10{=\{${2ts{_%bhnrpYż /v@e+loϋ/#A!d__mȝL>H@hC>1hs8{޳Fy ?3Aá=域hf#CDp6CNNI9B;7?[4y={F{zߑ6CNNI #Gp~pEg+dh6Us'=[T-; a'ct}PIr >+@C+Ϛ~T1{6CدY+:s|j}?n|Fgvrq.xBo #tpqͳ6xk )}z~#; q,|ѸO%=۬&._d'F}gn++moy7ymȝ_iî-`Ϳtow7km]&X -Dw rBޠzȹk-Ҷ&)Hw@,Ȩ~{IK(gҸqj 2i)$e'u!-;ujK^{+wIrʺkk<2DM-)܍?S }\u/'7jͤ Bّ0o9!NMӆR2m+l0:瓊$R'¸('qNiObDBp(K]r"{z -9rcGm${>,$s!3Dr91#Skqz),N{a#W\. aڲj+VF6BtU)[\ۦSM7yMxiM/}bi\Un]-4N"d*ĈOk&tf7Cr1cD'\-=KPMcnJ FԧM1"MehpWB O'Ҷrz4q/U~^ C3nA U"M3}PT vG$ilZ+C\ (l\ٶ 1ҥҦٽDR%kYBn]Hⴗua55_*Բ6qj.+璪0*Vhk6b]iZ^>vXM ؗC/1ia:SCGh Вn qV愱zp3=Ii?]aҹ&Hꨆٶ,)شmŤړƅ?wg# I S+-xsNy*uf왒ԡQS Zml{RʲIs(t̲R>,7tŁm%_r*miJiD[MW%S ׫d%#suR-il}nZ;GssTq53̮JM -uHjRhs) ΁C(m)4%7\_?YLAH yM,JnkfyҜ\aei4UqtY6RE.Ovf -endstream -endobj -512 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 511 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -513 0 obj -<< -/Filter /FlateDecode -/Length 4851 ->> -stream -x]ˮ$7rWz-<4<30 hHfTVWrWUG<<`fUwKN/)嗋ZW\O9$6.1{M<Ͽ6%` ]bQyAR -**MYR q{U.'/`3& 3Uf:((%`rAAMu:v i%]^B>I:[|VZysJgSt`-&E+"l1,l-*(-]|NΉ J1uF'kzuQ-A,`H: [I:1%aVY-/UyMG{=ϗ׾Z)wʊ5ת LwT֭4Zo7 -cN>myT~zS?[yzY?lW8^!Fe ]ui6i&V^PSS5_UMÉSM*mH#A6vlmdۚ+&ekz״ %]+Ф1MQf6[PC⨫r>Ԫkz'TLmK;BdYO2iV}է5 ՞N^Lk/[mQM YU`cD? A/N(;N;h % lOA9xJB+G[$dQ?[U}6[[G~'Ts r; -B[l6Z_E:]=kz]4?/kR4YU1anRޗ:Ν-,7<ݦ0F7= S3N-+o'2axg-y΀Oθ-+Nc|z?2y"+m><VunOݥ/ؼcm[.\Ϳi˰AhgK-O|8svmRK%H&iH:!0Vץ#ur (uK>E=UxRO7VyNn*l(t>J;sBnAN^M8P5ϧ3st;ϙZ׾N4ma=%!vh݌;FݹZO*9& ;fTAy}G?&lv^b{cS|X o|7eoѳ}^ysy ؃ۭ|?mw~y=AY-|96wy-MyLg:tegFQ2#Jn GHow,(-cf]< ĨG1Qc6~spTKw<RM6luzi{xa+Bϝ`nˌ*zS4wRy/<x̉mLv6:o7]ӧ{^>;*r߰w2ϳ!7ϼwoFkˌ4QZ z5ݡɜX9]Lx < ).!gԳݍɽKOy:D>G}{|0⽾Y>ߑy篁T{jd czsy3Ake3Vtύ^T=_GJU=a_n?5ԼM}6\ Tؔ J5{woom /PNPJ:RbilNK:݆N;9ATlvEǵQ}좦 B_\(("N] ˅vعqp1 Wrd7m\Eկzyej|k -oTKd _kł9ދjULg֫M6pxQPbB*Vtve0tu Kk"#j,}tr+Q]fQK}KqD N٨905 .tv|S5 e7vJW`sDu+3 - -вr8!%~dt - -ߥdbӡke=#c3Ҷ)t i -9LCgǒ|eE⊒%ZgXF\Bq*òH^IzT`n]ڡscE7YiK ^ӼҼG0ǽ i.}0v“\e_sl9MC,NΘõp Q&M#[My6dzj-I}!iGwviܶuovs8:5Rv_2 sw)mvۺj{epÐ0> -endobj -515 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 558.873057 101.433071 540.123057 ] -/BS << -/W 0 ->> -/Dest (cb76-1) ->> -endobj -516 0 obj -<< -/Filter /FlateDecode -/Length 4351 ->> -stream -x]Mܸ%Y/ C$ Ƴ.qoyTEZǖ`<*U"_)i?٨S|~|{zw*8C栜I>,Br6 um?9gncVq__g -1UJTΩKLIR R$`kp8Zܰ& j-f&+S%5d Й`%3.)ｋKH:_a֒0 <|!OZI_,Z' _(HDʥ,t:Y픋DZI# -䃠kD|q#t G!Fa N>KTp1L9bR>ϧ|?a$CiF~a`!6|h!{l!MN薝D3驞>!_Nyd|DL_M>#D[2lf'@yY߿<5zظx0[w~_^?|sZ&vrf~/wef|ѻy>5 we:0?y%ѥXo/|kt\3^-ټƍK+uy{c^A8d9'2H9>skpvW=KӼNkMӹí{|"1p!IzT{|s{nކ+(g;m97A*Xis84n,fʏ=o>٫C(ь|< -ihrKn<ݝsҤOgo!v{=Wqw? (\5܃~CY܋6GC }ϚrHMgJ:Z}6C7g<=;nrN׮sדj 9mNYmxUW?عNI͚N!uڪk k]F(7{49Bznx/(-0)82VHis8$n䄇m""C=J;|˥gHwG927{&7[ݽn<8+zX:|<Сtɗmf:rlmwӐ;mCc+쳐'd:}{P)u{9W$t6CT86C{䎟W>YsJU:.3yre۟is8]v :nnWSZ۴g~>w~ wOwnݘlq}iΣ@ute?pڻƴl`/ -{ ==vZ<4N!o܅n,/H7т{g㵧7{J6sFł{ xϊkOk:Я~=f-q gy=\[k:={+$\ -υ?+Z6/V38٭;m̍ˏYd2f۷mbv0{=\{lx tw=g_%XaҠoqP6V1W?"CԎ+۹rP ;QAWz7;mԍL૕+sN!tc _vuf+_lo9:3域ifw>O9R7rϒHxh<_kyEo(is8t^C~';'}~ѐ6rϒ>;pOw|N!tg.> ԽPx}_mN{෨~[TOw܉is8$n_9FLjwepX,}VdćW5Y|b-˻?{iu.eE6ȣlq?=1DAMt)r -yߙ @+}}K&9]?<^ _SvZ6vmz|1u=YnsY?|C7n]rw:\s ёw'?d}ؼٳ7mؔ3Cc=ZjܱXM V팛ߞLb?ewQ=-weAwpk]lJ*{?Z9Ѻr5R}o.'f)Wyިh<Nr[vp2ҍ-9$\1yGt~Vۦ3M64yMxi>Ҽ/hUFSJ])Y;k? Ǔ VYM.Xĵ\*I,7jOZ*NuF4-Ǜ1|}:6 !⧓ Bi7qvzz8 /4PsYdyo*\f>MGIجy#r_Y0Ms*f2Q 3ҵfҦyHŽLR7U(B:lC9a<ٞ6}ۮ|I#!M:l[u WA -LA[1i}tٗګ JxC??1 ީj]Ԍ=I44Ԃg-Fi=)%PTLY1hVe(R9$miJmD_W% kSɚKFA[*$> -endobj -518 0 obj -<< -/Filter /FlateDecode -/Length 4836 ->> -stream -x]K$9ׯ3&~?J#8 35 ԋp3mG:#{zFbZ=UGEWo4KNO)始WWR.FH|%O|/.ZW3"SL1*/2TJ[AAP=9K*3n0%p$A`uQۭ* T0CgVCD QY#负:=H:ɢ.BtN!:S'I`JK:[vNI:l.uŤh%]-]-@WuE%]9QS)(?dtZOش3 -3%(ElVIgaÏOxSfmՒcu/1 E QfD$qqr8LK.I,`R\VBX3Z"`wAbauf'q5 $.g%.`[H\`ANe-q: 3kSpXP.%.\ t1ݣk}0XЮu)H\`i%qZ'wVQ42`T'0H\L&%%qk"\栕wG$ 5^ x8$.P&.(lJ\ ,wu4j) $xiXo" -#3Yhř▁[Eq@|i$nL,Sw VJ6P_cn ߢ -CL1-Ny=<v0 Lp{Dͷ@v4XTm, "\,8u6dmэvּ'o<\/m5ky-Ov}֠+\闀gGl×{5Hݶñ Ol:Qǡ~`l -T|c/t-fvv_tGpj]jd(ҝXnx2ϣC4!ih퐧;aba]Pr6޿Alجm#Jm_Δ'<:1WvgK ?S.kny@׋RB3hD_Je<"H^FC0 _ 4A7p-OsnrfE>6z6P$fZ{蕛 -syDZϖЬ̒ay_u4=m:Oy4tN^mlʫc6.-y* ږv VTo~?4S:RaaWk7Ⱦ94;k;|IV/{sYڮ2K_J>?ĭ.5[S]xDzI.[,=GY-[mfRz m:,n3N-Tb'K7ն2gCiۑtOCPGxAmt.(h eϨeQmч&_q-Oxj\ (HiLh\9,^/hb?OslX0a3Q\Rާ_8n>kb_q~Pv݇86Bmt,zOtnlOq֌b {s}v9oe"[05sks׊l^C/?C]%Lb<ͱXm71rO't@Ds7:U70^{Li1*S}\dJ,`aᯡ™Y8[]j^'prwwrTNLg՝>Lc%G0V&_j#E҉;[NY-z|,:/ݖOΰz%ŽcF㰮1y;t. -bOHVA 8ts"tTf&5Afds#\Y6>. qQvQ/yf>Y،;[Σ+!'.n/G&妜}zYŊ¹ y YtYn4AFLnHG%Y|:cX:~\>|ѷ<O-{]t"M֓yul:-|fC?YF/#mmԺ5zD)v;YB.Ry4F}̏v@N9\oFFZHƼ'<R1Q,֛_ٻ(1!y:߯e_=C՛vPcEc¤Lw˓yѭvCḽn 1 )Qn?U -9FN W{Ƽp,[u4nКB6 kulNA.?$r~{(GcI=h8Mw[~o/NR:~`<:NC>Q"Ny84GYGlHw(qvcVO2F)p`@!5>cƣk\kֶ7/G<;;{hosSGZWQXPs ͌䶌7u 4D6GQ,JԵڻF5eF&5eI.Uv̦gFɵtDn)ͷ-UYsnJMٍ=^9lsmUb16狏Bj߹B -=.&NKidYefD -ߤdbӠke=[ c|ik>zIl -9L]gK"qEIKP\ -sle&WҺw|(,.XA\w*+`I[~ vWWFzz}/&:HڨI5d-a}|-{eܳ-Snu1ʤg[x^UQ4LUY+1V’vKiq{)K{QiMZ*z-y[zK&Ax&u=mn]wW =2U=ߤ|fy)U)#:cQ;8џ.9?^cr֪/&> -endobj -520 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 480.123057 101.433071 461.373057 ] -/BS << -/W 0 ->> -/Dest (cb79-1) ->> -endobj -521 0 obj -<< -/Filter /FlateDecode -/Length 4387 ->> -stream -x]MܸG  bd,`$ 񬽋`C~"UMZjcz0VIbjϷ%2*ߞޝ^ߐbPFSTmb6 u<ߜsǜ9XϿ.*r*T*m^h}T(ϧ07C8Cjn`36x|F B,{#b41VW,?wYClY|ghm@ma'@~ĿyPG+.1vx0Y~_^?|so R~qLfԅI4҄L5K,#>gv7vX=>oICzhWR~?#':G a۲VނhN|ƏU}tv{--P嶿{.ϵ B! .-k\,i˜NjGeuPY Zr}_ORWnO~*bkdZP==:os8Mk5ëy7D>wHR, 9eY-zq|o>2>|c%,!0kݖpGލ{Z)qϺȈ?ViO&"79"m\rrsF8#jRP"ZCܶfns4~cAbWna:mPG(rCś5Xy<СWt^ecKoCH%^\Bߎ}C}{hg^7A?ޘh( ďv/|Ms]]@Íy?)|JwYi+y|:٘pػ8nWSZzt?uz_S?Cg3~nWrSWc8S }uOQ*P#]bos8Tx{W|Ub{ -"гꃯGk|aK;vCns4DƕUhnlz<w5AW٫;ܺ^#1npơwW=NVx_w79>oXQּ^2ځ{/$\ -Ÿkܞsro ][Eܘp\Y~ȑ1߶يmyYEYaIq tc}w ٣ Lo0ns4T(Gdq~ܘp͎w,C?hL;޾٘pH]D -ZkQzBߜ1<]}άos4tg??S99F߹1ᐺ~y@͖wm>yΕoC;G=;aq<#z4|Mbm4x&YApzŹp # Uu Gr,gx7}}rf.|Eup.1M }C?&]B"~ߔ*T\mI.CY硜T~N%9!^W̞ Ϟ)ߝp.!)c@ʕrSҎLm:3T9/~Rr0a9rD1ӿdR Y\N Ճ8z1NXĄFqu+LMdܨryǏ|h}}l$5βX"g0sqyz(.&ƫL T SSUq \&j) ΫΰimdyKxm]/}ZT]1r5vD'AEY.TD-]IL7[KŖ*MYsɔ .dCXg}DZJ Զ։΄' 14?|R+Bm'LҲ ]yS U&-3|0 UΌו塱I5`(NiYufy}t[VcWRVeLs5T#kikBa~WrFv7(?]';}{Y0 ;C'.M9ea`^\M&mnƄa I< ǩI#0YmƇL9ϖ{^?yC=@2[6n󑬜~6iUغ Zb?M6[z"45M˅~C& 8V3ȼoLՇm\9zZ 8LMCtҡ%2Kvqi{"m'Kp/ۘvީZY=לkL]]p2i <)UM@2]eXm -cZ-'b)&/=oVJ-yK9@9NO͗L,MJSJWe{h{fA!aLR=}璧DH1i:r5;!TX<'(I;99Lx"+XQOirGDszrʍ!!H.c*<ۭS*GmpѰ3]OR -endstream -endobj -522 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 521 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -523 0 obj -<< -/Filter /FlateDecode -/Length 4804 ->> -stream -x]K$9ׯ3&~?$$@L4"-|LۑȬ잞FL*#۟?G8)~xQS -JEQZ8yCH`71\/oɟ/'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kS@IgR6YEt4)Dty -!$lYiIa)I[MQbUŠwKJv99'2t*Ŵ'UNVaFaBt峨-*#,lqt ocJl54ZybLt`%0$ - $01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq$. l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kSXdu8*J\FF ɤ$.p]wM 9h%.p]ik (Gxew`%.z-wu'iդSxN>Q'¼E/O:,qbx.3I\ 7-r)ϧ~ռC>wʊKƚe)f6<=*O?h 5j_=w]~n -͠#lK,/ϜO3nCXtyb]if-ݿ:%l0j`fSR2 Qw˓y 8A]$ (-7f@7vPi݋Wy?~U\FP$gYX˩ٷ8dҊ|<J̆7<:'8#j3#^mhc}UY5~#pn(oe̬m7%m{Pc/\]e(J>;Yjַv3,h\e#XR{,/,3a5JZ2m8,n#}!W;F?n Om9eDkҮ#;ByуA9P^ϖ>S;MVŞ?-c}r-ybys}ǰ_z)Cz;})e}u.w4Re^:Oq,}Zsv铝&je}8c)MwOql` kZ3W$3y+قF^]VuoF+^{د}?v.B2}ZH4|^DwO#= -Jsw:Ui Pi*0d s0Aح0@P_-E~\yQ(?}{'K)߇){.OYu>؃:D6r/NrZN-t^-FaK3.9*8a]/Tp\Dw,˝ciŭ3FOAfzh" t|{&5Afd:&“y$l| |ӒxrD-b6|`4W{QZTťڸ$ܔOQ)XU8av2ϣ +ݲiSܐ쨕<.O|9T/S9l [46"=f Mؓyulzju ͆p@fz.K:u gT.G'c\wh<Ԥȉ5_W Cg~*c/E<T{̩j@:Ɨa^]~vސV:ʾ`w"J[{6=aҸИ0)GLNy8TǣcUGٮ̆14D9OEU9pod+\;>\[%f*{|MCZ(m;E5C9Hnˈ*zC{}'pH)>̑9<"PAxe>Y=7|8bdGCV#o}g>QQbfSF^_=F{z^:F5Mr%8W=xh}WEm0Gz#=Qiyr.G> m^{_;߫ǣ}hZ9>giG3U;/SŪH;~?8~k6C%WҤ dil(u.;9ˋlw+z.Z -XXn/gz{U'S/B=wع~0Wr3H8NyLi02_[C}Fs&lsł9ފjҋ&\f -[j^i{=] VXu]l\GӻF[ׅ.llkZp oTkG(7Vעjdהm@\'AtoT-a0s -$N.b4F*Tg͵)6d7v`?`sDu-3mUb1%mԾsz\hYMTKT -S證LIyͧWBsם塱z@Ӳ16I t[c+)2&G$c- uMLVq%jbߠw;}^ʂfp.;8fo+a -oeasj%]lT[zeL )tq"SyO2iŽ]~)˜`5{^k@uܨqJW2餘GiÄ1bzZ_qc_]ub)ucPݴ\{2i5ڲЋܱ͑ |ik5@Z \}I"qEI3,#.xdnL$u=PX]07.m׹򢫬% l/i^i^#㾘 i&}06“\e[sl9\'oVes6'OZ(mIyVօdZl[JK]wӞJDG%lRukޒmpulddnRS*uʚ!{g󛔯̝9ϰ!?ewDl,NGkl[h*q,KlyO$uׄᘜ*jv P -VTwr&Nsj;TQ,D2RH̒ӛ華Dg@[m}X -endstream -endobj -524 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 523 0 R -/Resources 4 0 R -/Annots [ 525 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -525 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 405.123057 101.433071 386.373057 ] -/BS << -/W 0 ->> -/Dest (cb82-1) ->> -endobj -526 0 obj -<< -/Filter /FlateDecode -/Length 4482 ->> -stream -x]ˮܸW:h(` F&#YYw!%o;6!JP)msCyAGLIR Z`$ c0RvJ0M -f䂠 -vh!AQ^=Lu:vӒ. {%t8M$l!zDl11XI`A$Aa ElQ^iIR$u :C\r*IM+ТPI>:[rIgt$xZMnVY-l1&-|-*xЂKJ$0)J,`b(+рIn Vi茖*KL`5l!\Q[l" - qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ]4 qZk)z ,xגVxZu8X޵Z fd$.@XLJH.@ԅmJ\@]R 5N kx Do -q;[@X `H\:4j1y xWGTK(qݢ}wQY x%.Q-zjI&) x~p4 п Z. *(q$. d<(x.$q*gn-6 @f+i82` -IU5,J$qnSD `/H\# )/qO -:|we:B$.c=$k #-` "SL6D$qAp1ft-"t:H\ 芵K ^% `t$. H\hӰNtZh` A ez%qzh%QԒTgF "!` u4!q'`a-֑1<܌[2y$.H -㓸 )?d7Y8tJI\txӐhy%.HVa!ny$.H[\Q[4%݂0;I:[L" y%.& -#al29NV\@-3%d~0z*x?|M..Nydk}.=6LS\|u0Ma<͜z4:?|j:QΧФnÞlBg,×,Z߿Zl7M)T~wJ .+vNڑJOΧwBh3ж3RRo5/M 2?0opC98Cu|Ӄ>|c'˭&jpGތ+vM5z(SgȈ?tfP|FUDv9"u\rruD8#*iŽ8Curk-G a#FCZԔZiyksͥ+j4c"v ygárgveօzgi% Wn#_[1}:;>a8+ow֬{Qh(N 1kcGYhzRYz|Z3(&fq?ϫ>u+}2@}<p(ޙ#&n8C|6ݐnE5 "sԉPUӝkD&}B=kR{+q뾪YZK8f=ȻMaW\d/; Ig+@۶Zz{Dnoݼ39ymwD~K,L_+ _]afa63AAkp-{3سlt|Ƽnf{FQRˇ+[ZI3f_UK:)st9b?OhY{imc}h|cJcg!＋s'`(lV#e[k:qPev1)\zftwpd_!sg[{zw׾jiOﭚvq [}AoU_6|rmiŋ[c?dgás?dۦX~fl|Qxg3POv/zM.˗nagá g問r6ZI3][V>YȃS^\ƞ}Ogaw8[qsYVţn}OW]AMYL%x[##>imKG @?_6vgárklJۧf ֦вjʃGk|֌Uzn?Nun8GCdYƶ73Zq_$oޭ+5,޹ִ7k+mW۽"ܓod~<.wgoͫƃ\ߋbI¥/Yٝ`N-__!sg#|{~1x\{VQvXR\1q3]Y1y}>,&uq˓_o* T۹3P=U-o o:;7W-r7?IK@h3:;o3|9{*ҹ|Pt:c4*$w p}F9Z [Đ RgdHßWjy{ypk|jb2̀~|%TϥjUT˙ X/rgLkӉS~4r_寮=c=C>UU~8#=y|ɇ= 6M:3K鱰y#xj:]XaSXO:ѐ?$P5)7O%ALNqNElRҺAM&n]4ó$UJר*̨TBI~J҄ʬzVk$0 Q J8ApMZSsTJ~6eXF4YQ\.>@knJpBC+!B=.,*j,͋ʗ+4"H/T43xB*7͙YBr_Y氬ttTBL5t-T$Uc)uU)OJ.Td7]Ba^,]q*[ʭ 1SO9/lY4~4GW32Z.ts25ڲqWM)VGu3wؗ[[|^ -7qpg3Kw9ܥCKE O,4[03gR>O*l΋07"YGs7˓.)XIL軛ד}2ٗګKei%m L4VCv48IToC*4ǭb*bd -endstream -endobj -527 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 526 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -528 0 obj -<< -/Filter /FlateDecode -/Length 4446 ->> -stream -x]K ϯz FĀd#Xszu7gGN4YH")IXTV|F "wEx]mw78 `F aۤLWI%,p]QxRH"C''<; Dd@ MQ‚` 5F‚` R LI#s,%,M1IXG=J|?|RV4ܚ_ Lv;d˷,KȢA!u4Xx}Jsx{2(eMrtno,k8oW$}^H֮#`#@!<׃}^\GzKj$n!(.A;$=d8~Q(Z4ݫH1ҷA|dtѸw/ͷӫTWk~}[^/5ίo{{*4iΕ^oѷ~ٯzڦz>UObC!a:y8]Kӿ0a^I8YꍄğGCZh2"- =,`.&.6,8vnLT/u ϣYs]@7J`\ĚY^YW9u-M+VsFJnr9$߲c}Jf)+ npwLT:ZfymeQ?:h}꡶?nKsZDuy4kr͗)?*֋Ek[(ίWYIWscRkXiXyY獜sOwAX~`j'Vwga5 _֘pqM>^gipֺk~v͚'$['ZW2նouA׹mqϷ:(,^V:sy_žZ/A谭_/zN8˥]fۚ谎A;mۚK:}F+:3=w՟U~PW{^p sz~ǢìS7k2. ~Uh_Wqs rG\yk\u-}Y5Ć^/u}}=[aBuFͿNGnnf<_0uM^#9f7^N͛pu䑜Wat((jڑ -}\c<0{Ս&ՍOa9xw`|!aXj;wGz`dRz>pu7ky9S4𸈚憝4\({ WR7[NՔ$ YYS#r,a]++3Sjls[dE$H֡"k;"A{WɡZWdmǞ-Z}$}|Wa_'W:\cɫE=^iuA3س3}M/$h1F/Iot7s,⫝7:"J;9~.O1gQ_B|ݵ]S$)ExapZC* \aT m/ k -gh( 0x1U|[9wEpFCMnG-A/^1Q -|oTpܦ9PҦ!j9@mj%fiy됿x94C 5[H:߃|rϞ&>.EeI׭Y|g^}kAR| !_@v|(M&_ |;dX[N|;, d^- 3Um,ҭ cҺ%B*o{qIlv[{HF6[3O,-W&]|nlyMFض;$k0]'hwb}T5a=i$R^:TծQfRڲm}H@\ա îh31VC.vrە\۩Z5UwQ/.)F+Q]n{`7fCbhC~: v+70n#GSCkV-gpȓhj&> f#/4}C4)tfG}騄 u؂:lWmhcI!aHTULɮӂtUjy=kvo4Cq͗5y۸W%6ZcjѮO6`N0[:Ζɤ{9taXgH>$}|Զ066?c9yXv=ے=h5n'J[LZE TCɗnU-yQRh9E4jڍҔ]> -endobj -530 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 315.123057 101.433071 296.373057 ] -/BS << -/W 0 ->> -/Dest (cb85-1) ->> -endobj -531 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 108.376036 101.433071 89.626036 ] -/BS << -/W 0 ->> -/Dest (cb86-1) ->> -endobj -532 0 obj -<< -/Filter /FlateDecode -/Length 4629 ->> -stream -x]M丑ȳ  ؋;@c}X졦zƆQxQH*bfWwkBu""! -?hIO1狚S77V&S0L׷ .y_~sҔB'k'qAP8P-H8S)J\ lH\ l q<)ix.` Sv%.CIG7 I\qכQd֛X 6YכADEuNS-8 M$ yכQXo£C17.ft]x^\` VZ+ de+(F anC -܋*1k$1h3^`ZR+1lh K􉇨<0gƐo2aXhN%>^~9RV~495&o۷\3GeaY !55Hq e1awc -pgg!&fzGl,|n`p@oӿ||_J %|&LZ!O9\s÷N)uj%?MgkoLKa -By@)m61n. ~kܝMS|izAhлqs7۷fݠ^h|vfKaK7iwMܚu鋼0m}ַzj9Qڕ=˽*6eD.5>c>v銽Jn5K"z3V,a*s61!+Fu r.4s%,rP0V뾮|&o9oP%]v%skks#V5[ƪ-9,A -1Q/<`)`~0I0_9N=̗~Fk~Y>ooS._#kή׿~'ǣڤ2KJaa[ᦲ~ucyNf6<{h7-c ^-#*M?]!˭u #{Z<"ٌRxT׸fdP2Hs:h;䄆;hMOKz'D>k6F0\Cj#u,鐚sV/Ҏ+,^Fl}Y6^Ǯy&6ɨW4O{_9*}l[Qkcz<7yN׳>Yka%=9\7GrXb\.vسf= љQ!G1u,QXkRģtHs6Admsit=k\{`}/2t6vAwc*ңʱZ {}q`!Sʱ#ݬ|+ʨv{(u!&AldQ;}"7tȽ;9w՟*v/=7*OJw|Q[ -!w,{ |97ٻq=Ytԩǹt0..R[^{+Qof_yhHe6SRѨ}@yN#Ak{=;3>ݹQ젒$ܼ8?BXӡ=Bѣ^~wVE 33OXD<>rw >t}y<~Gu&j;l ;EC/5::3)G>>"-wWT;s-s:č}+#FCJ>?^mwaWi+A%{~=!s:T!iwVaC~`v,=~": +0pk'7Gx5@[ -m{ow5?,˛7:7˼Qݞ˛pYgrs.]-]A5!6CysZW~Xxc/{9˽2|m\MW|z>}He &&]iQYҥs>j=Q壟!bM?]t)fL65)Mvg &̠8 ׏E$K~=sSZWޚS-6oj:o:ͺ5u=^&JijҺFUeF*u%e$^/U&tfճ^g,XD5]*ELjO*|3AlnUAl]1(}"Í_/bh#~ v++Bʭ^4_>ahY>#P<MRTv*co}eZ@ShiYs*fy{騄tkb7RdLR1/T%[La}*Wr*F&vo7fC`/yjM+wqq=KZ.| X*ibl*cfH2Z+;cc6Ȥ<Lou>1{^H-~~5j5Pdᒇ܏l$%~kBwLd -x1 t`EْoC'Gnϱ9HT/C^*4b%> -endobj -534 0 obj -<< -/Filter /FlateDecode -/Length 4510 ->> -stream -x]MܸG  bd0 q`C~%,Ighݭ**_jI/bL%&5^9|tY`C3Oovȋ?~i}6]Jhw]VB A9AR -*]LIR R`$ c0RvJ0M -f䂠 -vh!A]t/|L&FY@iI:ｋ`KJK:[&RAybU ;IEtEQ[WZ%۹D]N:\碵Ji9`ӊ:( \uYe$-?Ip6(VgUVK:[ $` _ba -^̠.&!LE : -J4`ȧ U:%" -8X [3WHk` -H\`-l1d%.`[Z$.[RIK\`paqm$qJI εN ,H=H\`y#qZ^ ޵޵5El%.;vVG+qwVAb 0p%.V:&*& aZ k EnqH\@]CK\t%f]P:c%.@cAZ"q'iUc8>Q:qa˝>I\TV}F "wEt]mw78 N# -uS)F xd$.@THZqJ\IUZ y$.M,sDl$.f Fb qARI.ơSJ₤#֛$.(qA -M,y qA"␢:؂) &IybI\(q 7ы[17]u $L8zW ^ʘWQ1P^*n(p/U 7Me*Z -|0>-*8r'!kV̮~?/Mȯ0 Lp;dݷLRBxOlDHH Z7ݲyab9 ݟ'D o#so+,m=d2;r+M - @@!3a2黿_x y:3{\)20wxv., ֽ*sn0DWS)`^usYRAt[ULV1NMfˇ3m~!Ev1~݌sUeމ'w90LȐ)e+a)BvG<0}m9T|/J~g;rk"BNY=2u=s=;˷͇074_e XT L%dΜ{vl;-m([#lkcogĝuʍ0e:zOiא@@hnA^\欪f`(!nicc<y=^~2ٞJs[y}szlsPXۊSJӾҬOV:r1YqYpecT۸f,I9ܿl1#R6*2w92 S#켈 XƬ10{=\{E`I'0ӕoLb߭_~]5&m$%׹k-Ts8TnbFW_W&?23yFy>_wgӗJ,?3Ô[HYhHL7W+3r:3WrȽjs8n{޳Gy| v_F:C'?_hf3sDz_9/?;uI; n#wnk靽Zuy/0sEէݾYpHI_$< ;rw9BwZ -O|žw|Eu7; ~#bv}kuʍ=54vFp~ W5_Vo9߽s8n\9l0 A׿=A^hF~Nxy -B/v#t_!=Oi<.xk ;x%,gqmJTw|׾r~:׮_n~ru^F۳v}EZ{boָ2۹rgásҩy^'Wyv9"7HT^+w߸%W|~wis8nbrS4[MfgA+7jy&v;qs4tƝJ.QZ6VƤ~0%uڻƒ%&}y?o}I c+QLmn#8u!x!f=A^v,Ϲ=~yyK^]N܉ovX_Ye|?e+vVezf}z9 +]2bnyޟl~>=o}xo^la]#?CC /K&%ؖ,6lc\861_ -l8ഷ=^G?fG- 9XD6Wp0Wǹ K`U0~J1;J ~8ߟԫ}y(6Xmmn_ 玪 3nyN`'Lpl^qBd6G 6q@ڭST3wLcEΈ p>wڇ~gYs='hNGv@mȗ7(.=yBM懃xFD)iKIC&in S=%0"eґ$ɧ ~]!6Ա}v .eq.ϳgClZ Ǔ (;mΞ:&裲RZj|g7A\:_IGS񔟚E@,?2}3]*]՚]֕ƕTw3'U -~É!jzޫNWS/6C$^5*nULBNĆ=:?7a5N/e] s(;*MUeԕu@ ᷪ4M̪g1crDXnlՑ -TlUS|3AxAvaKRSƁs\ZE^N1?\JqeVqT /Mo$6|,|@J34UHfv<7x$.uH2w*ftTBLtD\!2IUuE]g -+\Ʌ5P~NUkwWmb_CqR2l4gr&6Fv2&lc/.ScdRĽ~9aXg>x3xEWxDC$8nTe Su",?2'Ba6Lh~ʺǍa|Mj^Jʠj5252ϸ+̋5yش=9Ǐpt3kGh Вaq!;ajM̀' -XmQ "{ 7L4M{z=yG}YZJv,K+Ra9mmY6lMrhM8F4jcOJE69i . SEV[ &?V+n{E/S4/ӎJues%lq8;J\2 -2kW)ȖK=nP3ķTjnQ.g uf;R@M:Xc'i=8E]rs']τZt~&l#i[*K%%v6Cbw(n[ITC^*g`ۜΠS#z7i -endstream -endobj -535 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 534 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -536 0 obj -<< -/Filter /FlateDecode -/Length 4427 ->> -stream -x\K$ s^C$1HA;6q;|T$VgvNEQIU 2)"/?~:)jMeP-1LiJ%O'şN?:RGfRNU2+\ -+ C,EcAў 4 S~*%K b²rXgʃ ;gb.MNy?D6XWc K(jY%2IE7*KA;Ee*h+~ -%)y΄)dƳv -M0I1)<Y EAx~4p"Znox8HAL.BXA㒆.# \e -\&Jk0J(7' !TdD /Y wN B L"VsQ,5,MiXBD>j覜*/g)Wl5,@.5e,z K@ ,iX -dRѰhƳAtV A 2Ѱ$Tp5,'5,2A Ty0a懓a$HsTd4,q5,84,mr4,( Ӱ8qa`r4,(YBY4eo4^,%F73o"W2I.dx]DQ Dd39ꎁVu{᭒g`#e*֨xv0>-sH9 !9(~Wwڏ{X^`WSm`"vX@*,B*CD P\XD8b8rv-0e-B:."O(UI[$ -"X&rQDn+:UjΫ83{C:WzΫ˚MKY'<&7yqk# k]BY;+{ w.lsrLx?OϯȘ0t5_q>̛ y? 3y#MgVy-p`/4x]ְv:+Z6:Sooi_U};D4b -fa:K_e|A8Q1 oxMÕZ}zMs˨mGG?}d^7}T-O\ȳ eOcHU81ϻP^LWGz>Ϟ 5}-2)D ; Ea_]&u -ga Y/GdY}Yι,_d~G_2ATb[]=g9~|ݭaiGI*uKGbqY^x?_veB'u,ϦW.3cb~W6MN7Sy3)~}V=7,ɮ-ZeEuxH-n[=3};ulw$G0M[3CegbNyÒ*-]-2u[M,Qš56 Q-yr ]HYr_-vj|lS8׷?Z"}TpqW6B6fOi[2϶J5#phv` n´yC~x=ySg{b:: cȿ+H=N.̐m54ѬOk^nFאؑ ʶm:{%7d??\ֺYVή~a鮑:~9=؟2S.u:o&i$lgJ^Ҹo9IN?=i4@"i|EjI㱝I#%ϏPKS =I#a4M{B٩y4.9i\'b}ywwg7ƥi?SҸ}IHuwiuM4i܋/ҸWӾHiS-B* }~ i]W_]@-{&;~)oxyaÕEx}6)]#}Qn7}5[ᵿ[{"nv:byl}.gvWX{Jf,~mG4ҊJ݅ - -ti5MLtmHomMNlK}tڔ[6@퇥sN/-ܾ>Wl@fw- XAgVw_7buCl>8ںY4I -/m|S}uͩB{U²ѽ̱흍yTp`q`gˠnZ}uޜc|Ij͛={ ʹf]d5) Vݖe>|K[TƆCS5z/҇ `ٽ4]ccԅoKGW]Xa/Zn-ߧ f[śEn^ [ut^'^ [k8e GFmQ{yֵ^<G0푀|\WNzk(z?x,vS)m=& q;C;)$tX8^ {Ԕ4gS/,u3f'$鱣iFY.h;v7:6ڒsdnt&C0 }Z;:r,2^N?s>8~~deCom~ܙc,=>$iؗ :?6YC Q `o%mGP۹uu ̈́e| =68~G_4p#> -endobj -538 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 770.673057 101.433071 751.923057 ] -/BS << -/W 0 ->> -/Dest (cb89-1) ->> -endobj -539 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 533.926036 101.433071 515.176036 ] -/BS << -/W 0 ->> -/Dest (cb90-1) ->> -endobj -540 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 297.179014 101.433071 278.429014 ] -/BS << -/W 0 ->> -/Dest (cb91-1) ->> -endobj -541 0 obj -<< -/Filter /FlateDecode -/Length 4620 ->> -stream -x]]q}_C" ~pgFp9Td*Iwf碧[U$U"O)JTWVSzE$M)G|*ip*?g "$^_wH^_yUVןb1TQ9'B3*.1%N3\ڮUfVȨ"06(V% -fRv(-%!Zr£=Jtbu:43F`S. ｋt8etŚ8-`p[4j'1[`RqdKZV1ĵNK'\4Fr:6 CB#4l%V[b΄ުs6(N`:؂@{"(=Hd^8@ lҖ#FtL†`8 SxHV [[,z.-&Y -Hq1E[qZ2) J9.0 \)9.0`\rqp'8.0`]v5VI ,xdu( 5J ,xHs\VX:Fq(-\ }p\`8 Nj ,xW[9.PGxp`9.N PK8.p]> *&q愈cuIg-jY( Ge8.p]g/Q5 <5*$q\87$꒐)F x9.2IX]d,$P ZB$C H(,E2)r\4l1Zs\4lAq"ovx[v|`a "E d"&k9.cD<3c-,:hF_t O|4SV)E|n!V|JLB;Yɓ@[6/,,?N7 ^|:='`,1|fyG%GiLҙ9ĕ. :[q|K v?_~o?G')];^pb=β>O"FRKY8V~/5Epwx\6^۾cYҾ_Y1iT֚Ju֫~t4 缺k|i0el6}YC7םZi!g#yyS5pڷ߄EM~ZWyE{[Ma?T?U-˜0ܝ?KN6}GOy0 C6thԣG"-J[ꟗ|RkyEQyYFzSގjY3VfS{ZϒHn9gBq9Rîzen0j?Mnm3LKH,ۨʎISUKϽ.uY^}vߪ@" `&q8tH<K+\[#Gzc&V+3)}i+/t%_5CdZq.|Ɠ/_ŋdbQV|"G=x& .s:DģݼH=꽶F(h/<[bo=VS #ĞJ$7D:tHݏWG6yO)mKiߵ,た΍G!s 7 P9l4mFP1*u|qs:dĚ9r@CF4AGAJ[,9<"s:ğ_k%ܡ>r}yNRu/v͜gcf2 5YZ̼bHʧ]tnd,̃yΆ6{3>s̨'{_zqBI,EYQ~| -EFv=P.}n![;>u:ɽ{DMvVVݑs:Ǫ\~0^#<фvġE#p,Y2vo2m]Ƈ ->̯Zwt|07VG<wWoŵϬzkk{ 5x6|o)s 9b1OYGemr` sh@h|}yNЃgqi4n${ˮt &<oX"C}^\V*qjӥ/ˑw 92{+Zs O5u^ z */k:g47Z-=r07ӧ\Cs8BWmgcqZEr ϲPI>`3!v=g#]+fkϊk1e<|{Toauա֤>KD!: w;7n e*&Zܺ;21h_~YֶqshJ[:=4`ӡ j|0#s -}fгj4z?@mn񮂗7j-M -lH"tk$kbm=*HV7a5V"_@sOxദҼe)ԮUfQJ]IYvbD #N-IXdkT1ۅM7jK*|3AZlY٤HS~.>@ik nJxؕ5@ - )lxikY[) -WyVHQ;IU$*u,WʆT -bƟLL5uTT$Uc)VuU)OJ*]Btd^ZnʝTj]K0_ɱ^IXɈRhFN短qvers8n/\eײܺSOwwnCob[ZWPքm.2Z*tXWjeH͸᭫ȼmþrq8p@/LsWR$rҡd-䄩Y03V}Ҧ0\䀄4mn]dU$ =[EO0F?ݽɾ,^TZ/,K+R3a9Jm5T2䴮B 8%ز =-It,Zb(69[#[KMgZӎJDG[ůrǫђpdKYc<]4E>]x+ -2-[|;> -endobj -543 0 obj -<< -/Filter /FlateDecode -/Length 4520 ->> -stream -x]K# Wz^@C$"b`f8:|bRK;hm`vdU5E~$K=|a_&;\RÇR07X\oJC%p > V9{PJt6|,C) -Xz QaE;`h,9:g%A%1ȹ2?g%1l IaY93FAC³aPzx1WT^&b"+C1dG%c5^,Y"dY\N^%⠝2dueYL4V?T^y΄!dƳvMQX,ф Ki<Y?8|YV퍷/@<ȂEbR 40.iR8@e?PebIxcsVo K!*BxY@!#aE%SxKF <b <Hx@.LhXةaݓCtx5,]OhX@]SA@5, ஷ&iX@]Ӱ:l4, ˆ4, K*/ Aaw] u8 E `(Ǩpt`5,@y 0hX )> l.QÂܵ˧`4-<@5,]gְ? : pzDjܵ pyCа0X$ tU^LYÂ,9 $*/ 0$ax0C5,]aAཆkiʃ,>; ׀U|`Bw -k<1hX65, .kXdNÂi()E b1!Syquа  KAJa5,Hx4,H eаP,o<,0> ȂLQ ِ )DcЪƋn p2x6iX VRCkX8]ҰbgIÂT \E!;dB$ Z ,5,.ʌFDhԒP#ufְ S8U԰nJH `BA?(6Q<iXr3kX3dqiXz3iXP dAƧaA1q4Y8xhXPlFH%כY MxL,)ʃ,H$ԛ@'!+aAͬa ԛ-fR 4pi԰7jLgf8c`U20^D/HDek -5궁"3LvU9$̜xnA[ћf؏|B=~oƝc ,w@m1}q`fb !=}XT8oxb!9guQ佀| 8:(F}8fvosU  U%uzsW! -%4ź*Ư\lζWx>nŠܕ6jEqhޠ0h,Ŵ.H, Ƿ?oo-◙~⚞wn|lڞ_-~7P9[jUpVItmr_ \1 -e~}72܁Aw"wy8K~ "ܻgY\NܹhmwGz/2<> r:wy4лޟa>A~g+9g?a},tg.&sިux%ކ -owY╜X "8k}*ʞg5M;#|VdaOª/grWy~5>ylEy9zNZ_g얲oae0c>fJι~c}TEa};;T/87*?BuZ B6=vSېC\3ܖ:tYswy(y|}iVRbJdy;LiyʼnM,i? ]rǮCs$LxsT}^^ũb, Xdn|,B'Q|hj W7} jH}Dlx\C$Cw3=}cioU-2S Zm*}xjSl ncsCȵwd<{wbybnZ/5.m1p;n-=3󕐓]q'!ɖ9,jkz묺9?hW{-Շ!+|Fք-ݹSȲs-ToZ?U6Um5\zk\#u@KPEa{}u;-6ڻ͡RΖ!'jTe`1ymc4NO.m=/Z_aHk>t\Zy10.[P - LmS+D̳7} yUlp߈}@mUF9шu*}b'6ѥX%nʧסvi4/*j˶ I! - S&,fUv'bD]頶G mRk{R5E۴N4G/d@mkmwF<brIi:VPMOҩ)WU5+O*'3LOW&웍Tdž:iRmlJfl6J{ֺilA*Tx R :6_1њ̦M:ٙ P/#zkCew2-0|poB=m_:~]ޝ3 -\YF2ޜߣSmёN ZwN5{miƕu(Ȯ^h&\ VZlǮMӥJ>J 9\=$Ő=KNtą↥K Rޤ'&/DY9tM{y!&+oZ(B^ȱzS7ꋤ1Ne\^}]Cm,/|Ϸ$FO-hq!mTPs67Ti@4SimTesqYRj9E~/54%*-[#^˖|K4ggz˖KfeFWiymb=35[8ky;SN֪#6&& ! -DYl.I?wr IIRr!2w+Fm -P:̙ݡ-q]&.='(?o[l?o -endstream -endobj -544 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 543 0 R -/Resources 4 0 R -/Annots [ 545 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -545 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 198.873057 101.433071 180.123057 ] -/BS << -/W 0 ->> -/Dest (cb94-1) ->> -endobj -546 0 obj -<< -/Filter /FlateDecode -/Length 4598 ->> -stream -x]]ܸ}_Cl$F=N`9Td*I׶/ݪ"yxX,QJ}_JĘO/R'oJ8?UISGw) L!9C_\̣Zr׿UֈCQ%29vQy%p)q*v -0æ8̰ZGFaA* T0C%Ci)Y 9VǤ Щ91tIx]t$s)k%-I:/p8.buqkL [ [2p\@$XO0Z 󘏡V9"5ЩqAV`(V`.%":= x% `tr\lAWC9SN6tSエa A ezqFh%Q՜<όDEv9.@7LL` hOl; 0dV[Ĩt3r\#lRs\lf I$n2q _f &xLMf Yࢰ:)1&؉yآ y监o£gC17.ft]x` ϖK xe3F $aleC܋*1 s$6h31`XRI6l 'CCȄna9GKf6c1^O"eOAR[W:o7 $0<و -8ݲrtzSN(Nru KL0z1IgvWJHwuʸb>8aO_??F>]?tWߩp ^>WSKQ7CiMҙq\~j쏰1οk13_GI2mUdWf9o%o-),qMv75{CU3KOzs\>-/C'GkۅeYWڳjzaQ\ [iÎd /=m~Yj)|6di*Ǩ/Rsd9*=/Q* E<Z6>7cyֲ+5y#dW}t#gzҌ Gii4o典kUvo pʎK 4םZ{ũnޘ͑oPt0pElKWycn=A齲񬛣uPϑmxYOIڱ`ӡiԣG"-JǶ?-˙fR|Zѳj>љQ!G1,kݖ5Ս"u,z8GrSirkΟUgZoExamWvl͂-=9S $R/q]}$9́cGQy+Jvk(缍!s=@oˣQOEXse=It't,yvqZ{tښwd:䭢3#J$+n:lHҦ#Ak[ݙ;#>ݹQ$&pyN_E[}#ޘ}(@y/[\PM19 7P|`ӡtlg{w{\[?y`Jjծ~Nǵ83?3(V|pzCOʧwjf2"GG'Fߐ5{bOQiwرi8_W<3?.s0PRV0Y'(["'OͬV:HdNWnݚN[gCA=>s:8 -oA&g9♏+V`|.2zCrSuڹ3G/֡O # -$6YYytGr0rUK:b3{M;`׈H,rcyΆY2vͯ2m]ƇoQY9"{#a;L[~35ڞ:iʝ\2ʚO2ߙϗ69~5|nbT#5狟vR.qGtF0m5J4*[]7rN\SʼE_ޞY/9<5OwQ&~S-#pY8,J*hH}JㄜZxޟSr59+6VDf~bF^P8?|5b3@KӶ[C2Z(XbժMXMUH:.8/4zY*ebTRWRhƬzjyﰻ0 ٚ.tvaͥR-k*5LiP7V<#h6#ҔK-PZF.bJrqIWHWG[Q64i~j ]K;U*3PB*֎Ir߬e%QcP6TTLL5uTT$Uc)VuU)OJ*]Btd^Znʝ/Tj^K0_i`8C?4uk'#fHL[+;ɸveq:7*J=/u|^e+8ee ]u!#Y<EX jKhUli]ACǵ&|m[vوTAURkuHĺBW+Cjo]-VGm)Ә ] -rpδ!JQNچth&q@ !9aj-̀'U)L>9 nD>4Mg0K.*HЂ'M {^nd_z@Vj*x9Jm5T2䴮\ 8%ز =-I@Q2YdPlsR-GB)mZ_zK:@9-e%##4wږvy2^efol*SL߹"\7EGTlob*m);{p[bI> -endobj -548 0 obj -<< -/Filter /FlateDecode -/Length 4449 ->> -stream -x]K$ s^@C$Y`ƽ8C~>JU];]{EJ*>j>+|_$=ĘO'5𯴘]w֊tѝ rKߜ=fH?YdCPN`%˹!zSX2fA):1Ș("İ]0AĂ: (% "Fi7x(K<I"/x>vZ{#Aă,dcxXoȃ,&+d1Nxȃ,+-\D"/bkQnpZ%|ӊ<(g W.<2BN8bVɫ*%,yƗxȢ +hȸ$a adH@&B )H8`h ,VCy&ȂX Y Y ,Ж-X-%,[RKX`SIX`6zrJI ̵N ,@=HX`y#aZ^ ܵܵ=EdKXtVZ22KX_LJH €5h%, q)#aw /ae(1B@+a  pW'?aMwuD^tƅu -$a"PY p%,FZwIJE$,;  oVp]bwKFDAE IKX0P ҐBC'k'aAP 8@ȃ,H$C)JX dHX dA a2!idbyY.b}@@!&" ǠUZEt E/a~钄!e彛mW1Lv}xPUg #n#TnNxǫ/I$4vZRȢm-<]2ߊ zkĐbxC٥0K_rJrLɓ r )pd$2`gM%>f?\eWmAYF* dsK&ml $%78)oz{>9r[}cT^oW;XsQjf}u -]lߊTU4UO=KrrVoE;k?X*O9ƭg=h89I=1涰ҫ۱`GN%\bzƱޫ";>_tyra՝. |?5xKިp.s'Z ocO`+WT1m˛J+h;{ N68u;y8<{ndMF.vl&<4ڻΥ]B%Ȯ:yme._Oy_ e.oY yuy+6 ҅fy]#~r|_?%=+<@uf-Gs+q\&.~#Lscz(q.G`P]E2f)z> G6p[6ӕyL+76]OX~W$Zr>:dGzE'ai_WgllS۝X b4.Ǥ]}>bSG7TLVչom;jzƪk8%c*gt}jo}}NߌG1W>cD1pW+췛rwDq|d5&#c}3+s.옺V:\mrRXjW;e)!Jx6(Rg0JrNKw9-۵xc}_n-icn;Az r3s_/jd;!͡~X`xbD&*vN6Tt:߉Mt:_̹ۚGp[|F~jרFLԨlf't9 /T`gV' XZT Il7暥Bk{T5E鮞c6 -~e99|*21+C+X\u=NlFK#WXiP5#OyT>k_s%qoC4ޖK|KG%ϠZ7ͨLeR/T9Y7k aU? +9QU!pNv͕_f.kK^o5swd߰Cg7y۸+R-cI'բ]#v -ajmTN`^E&ES s:[g^_:zǍjhatY&H-7M3y^^mId_W@6hoNmx2ՖK?l1ǞE]]Cm,֞mIN_=QFRnZE TCOݪZʌrNkq4%:njǭeK%@sSe%@wRoi+m}o߻F3uA|LUV-¿{g!?ewD~T?5`-߾_(풛wI 1*=/` 6TM[RnS=aNv&Q Tߛhs=wW6m_ -endstream -endobj -549 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 548 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -550 0 obj -<< -/Filter /FlateDecode -/Length 4730 ->> -stream -x]Kqׯ=/, LώW}A2LU3Õ<.F#I -?iI1헛S7X]+ -Gw6 !9ö?s벎!%o'VB A9AR -*.* JI*ADAaZ` $AF)QC5Ncн3z1$t:Igi%].J:-.)-lqHI:B6IaV:bb.I.+:آҒ.H$t*UNVaEa|tx咨-*#,l!H:!Fa^VY-l1&-|-*x%L%C h%01 h$7OA4tFKD`lq%&V-6ZbJ\`H\`AoIi/qL%qI kX.{uF ڵkI+ k-j:K\vVZ22`VK\ &F%qwMT$qwM uax8)#qw /q2 wA!N` V{茕 aܟVK\:bD]t ):?I\%` l[1[2H\`HѷE RL6D$qApFUy3u:$.b-qr!bK\8\f@Iₐ` pEC4%-%.@ D[ J\MD%1ԒQH~PQ,d`JQ[@`~8v A4GH QaQF` qARId @)%qA! .9ߌ$o"m qA":؂) |$>]jfb~W#D?wӼ~ߛg"ZrE8^tXO\fکm]"}yAi29!IEá. 9%X/Р\[=ϱ<,~jsajN_V0֮N)tm}ڰe:ׂ |`!%Yaei87b1CҼxnE2ýe啂hDd.egu_da8ט!~ϿEN]9><#sUgLSο4[|ޢo !@ wu\ulowQghqSA*,6p9#$Ϡg_A:UOKjYyD6w*YF%ssu.ԸϏCNZʹ7B#֢5+4WCjJ#\!u}cCT?.OgiÎ+m}ev>vE52Y$X?(a|yP_i'f_GU! -1s|sf k%c^&溜̞nfiFsRN̳?4YM7-cڎ_ fNىa[~0JjmqZ1h};:~z3WusX=}$Hi>*g]zוuFf픿;Sԧ5s%'\ Me#(jE|doKMۢӲV:D3n!GZbJYk ;[]H=YrH=8G۸v>cf γb0eʷNʂ[[zT $Qxx)~㽎#W^rj]9>_!Blƻ/Q}bd!w?v?U͹H^!Ci9N=%_P -jO1'8hK|rչrnfn=?U=ov7GyKOֹ"n_^뽶2Q_x+2V #=9w:C~zi`k[]|LwmoG-l$ܘ\ˡ =BѣVqTodEo 3=\ |n :;u.`ƒ3u.sw:~K C3}u.r$G+j4B370[y'8 -hNڭL7{g=:CAfG:1r׋7d!4<=<:dĆ&&Gt_=@:C"+|S,k.f}롉#G:CeWnFE'\q_wC{?j}Eww[Gl_!?YjW崝,_dt\ŏn}򎷓u.ă2w*2OֹJOƍyIawA^iķfVw:(͜vw"ө?~>V|p|dˡ`Ag'3Oֹ~w`|β*`ߪK{?u}7N^#JޤOgM:C~Vooe-|yϣ uOu&M^is9~8. -;@۶V7YC~%JD:Cͽ#aW0ފk7?ZI[ۓdFrÿިq~8zp]}7F?\Oٷ~n')H}sZsXM/7?C/FR>s",{5Y̯\|1]AjkCP5UlWUXLoN7ӟ˚Lnm/}T]6F"ud*$^n;&Lf7Ư˙1J Xnn͕ -TUSjJe8F4;d5l{<*61+ .Vכ BiWB Vhv8*廩OXY/'pE3~T / G^EV 4B- `/PI.#6CC1IXuA]3)\ -U6U+P~],UJg^7pw*;_[q(3On,|b~̝TQa5 PŕF_Gq^c]d}69_/߿ɏUn][OƯ'*,,˦jhue]FC4|MĞK h[c؈MѶ#|F2;7aO6߻A{:8UgK7M∋V-"Fqte 3m'e~jr_AF:nm:Ƴh A0ӴG0> -`i"}mXZO/ϱ<#Tڲڳ%ȩK8h1Hc6pmeN(tʲb6Z8JUv];+e];+~UDK@sgjKFAEJͲuߴ;{{sT 52U[|Y;Sn'B*IkߍvuOֻ$y 1*hmÄW(ұiu~U\-)a{ҜZo6Mr8Uti|gYmbd?' -endstream -endobj -551 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 550 0 R -/Resources 4 0 R -/Annots [ 552 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -552 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb97-1) ->> -endobj -553 0 obj -<< -/Filter /FlateDecode -/Length 4426 ->> -stream -x]MܸG  bd0 qz87dYGR^tHDp$. -uI\ĺK6E - -H$.@F%[\E\lA(qH ]N%.CIG7 I\yכQd֛X 6YכAD!EuIS-8 M$ yכQXo"b^oqIҁwz p&2[im@. ?18c@U2P^D (o^#0+]U( -8a}[Tp1N&L Bv_])6/9)+ B__avȾ5o=HI*[禎A[6/;/?L,z(>>o!X-38B(c!T4)7'ub|K,ɸ5`SXKu[?;u.A|t\eo9TnmloVleVF]Q]y~7S:$FS$*Oǀ'I3Ό d(F^ae_ܴaw YXmWqрU5$4dh9 -3i ٲw3K !w92*G7!%R(WtS}?0y棇aȗsm<0C\_gnvVy)}kRX}urmN3t}ytͳ[R>u&/p_áp_Xze虣x?_0u3[8~yN@ -C osg -RYVuԍL૕qɧ+e9k5v9B7=٣wfqxJ~gá#/43x "Sw\ѐ6r?w+v9B7r;y;Fݑ޹ۯfYp輞޽ #=WT}Ho_s8n/i8{u~g!E@+W}oow97rq1f'_s8TnyHyٴ3kE&H|`r*o|}gátf+ugpZⶨzE30jݝ~(#peYh 7y2Np[kH^K/9ǜg9kWzu}\娟Ƶk׮\Q4ly|QUtwp:C_S엷^'Wyv9"7HT^+w߸%W|~[wis4ƍ_TN{ʝf+L3h-ԄN68}uΝJ.QZ6VƤ 3%uڻƒ%>o@&}y?o}I aW7}CY,l9 k|D}OvC}smW훯X{`m\'ۤ.,~욟;ҧj> vͷWΏXSNc[1١Z_z0\"v4z8m5?(61k1 cy0[5wa\Oo,ۇאzppsfM\fq9RP4"fYo-qwʌQS#.K*ǧkWpQw˳L䗸7⷇YhCYwlx P~CA"N.#-sq}Tt:;[WjgPKlS).XC?V2J zq4堉OZ$Z4gQնp,ti^Һrk++]o{N Bz)νWe㑯8_l5HlkUk- {t~Euoj:wf_ʚri\(JJSŻFUeF*ud$.'A*M٨K XD\*$uB-[Tn-]=621yHżLR> -endobj -555 0 obj -<< -/Filter /FlateDecode -/Length 4783 ->> -stream -x]M丑ȳ 6va)F~AdT*9.TW*A1RR);_~:|RS -JEQZ8yCH`71NoN_yL9o?)T*~ Ĝ%UEr -f8cJ0úVaI*J+ءR(tO$SHdQH:kZ)sg%-^;$lq6EI` V:bR.ɂ.+:آҒ.䜨ЩVg|VI:'lZQA -QϢxGҁ') jIa1щ:؂آb(3h"^88lD&%$0)O.F+р~r!G-UŻ 1հa:b؂X [XZ$.[oA …J Ƶ)8 ,(PXpwJ\`AQ ֵ> ,h׺$.]봒wENQ[` J\V(qb 0p$.V&wMRN5K栕wGk28q&H\L%z]P=tJ\&D˟0VN9H\:aD]tD <J\$q8~Šj$.]mRK:6YI\äH\m -uyR9% ?"$(P*n(p/V((/HDdkeJm?60>-8D)R#3wb^I6O_`=_~B 1B6 Jy&mC YCF܍ԠeӍR66Li[ՋPAclm;ϻۊ3xxozE#o%iF" p#=?>q83l xO_~h}x=Jj8J_|v/];|{M)K:%muSE?=8t-˒Nv5LVvmGZ翥 Eֱb~~ScZn~?Si絕vۃgX_i.??jmklVڗCPb<4(Nyh[-BN6>iCɮ:wMַnaTacXo4A2-C^p; -VL{.CTZʙaԕ~fBFe׬x;)?M_{ni?Pf|;=5!硎HY}|`ϒw^<ֲGI9'>mK=FPz!$FXBShRiU78. -d?}@xEi!!GC7z2m~ /F7+v<~>}PҵY<~q=tTӹ,v[ /k9IzbenkG*1ĿO^;>fNgNq060ܔOQ,L:KG$f<6lT{3Efh56{?oo!]oaiT>g˜Zfw)njA=Fў>yu5|f0ǰы2EVGPw.G~G;q wm!,28"{͎Hus%dln!`gC3hĎyCbHKz'Dk6fadiTGy:${GUyv6mu^!o{A.;Q2r<rþ;x{lTH nO#]́͞?t4i)={c7&[JGԳݍGcy7a__E(xV_yL|Om#XC꾿ziex5~LqQ~kQٞ$F3p<* _JT@d`C _=#(+yoD3t3! -J/y8":PzI/{ {t\~0ӡp߷,Oh]mkXI#.7cf smpy7=:8ɸW{-Il/|0ϳ-vT{_z~?C|r;Ͽ츂XD{,!"+|S(k͸g}Lʻ@G^Ÿ zyYɫ>S|\A%}t`C}g崝(Xݿ,*?x;xG|7D˥Grj98ub6Lrr9g=C>E{,4kјoAC&a=0/g>M^SlʰCu\εmyn".)?{fCwlm 1ںJA4iCZ:7Y|NסӥJ򆪟[*"Eﱠ3%e:~ fT'S/D/r!>(&Q fSSZ?cnq+VLW^4*4S&:3koUU{1114D6{ Q&J0ڻX2r k$.'AE; fӳQga@r-]$[JmbKz\{ҡnSxAVhFz#֏kqcÍ/',1n#~;(+Bm:^P?ajVONTᛔ|ЮA^1Яz%47xI\8=-.c,/Hn=.cyDRɤr,s qK4/'wC=o^Ǎjla|%奃bzy^iÄ1bzZ_qc_]ub)ucPݴ\{2i5ڲ;Ћܱ͑ |ik_zSC -9L]g|fE⊒%ZgXF\Bq*ݲH^IzT`n]ڮs}EWYiK ^ӼҼG0㾘 i&}06“\e[sl9NC,mNNݵp Q&M=ےJ]* E Tc),j'b)ϼ=։Jؤr׼% {TO|$ݤUۭ뮫5uCBLU7)G)U)#:7`v:ZcKU -q%]rw.I?5a8&g^-E`EWKٲt_C涯L)-e]F -uDo9J~J96O?h -endstream -endobj -556 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 555 0 R -/Resources 4 0 R -/Annots [ 557 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -557 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 698.673057 101.433071 679.923057 ] -/BS << -/W 0 ->> -/Dest (cb100-1) ->> -endobj -558 0 obj -<< -/Filter /FlateDecode -/Length 4384 ->> -stream -x]MܸG  bd0CxE0!?j,K-uόA[U$U"_UQ>*}_$=ĘǃS7xwԊt?d CH|88u )ywYEv1UJi+B0 *\bJ -f@UfPNR 2& -3,mU fIR \TZmu0DY#<:K:I.@t>vZҥ{#Ғ-dctXo-&+l1$"l-+-\D.Ab:ࢵJi=8`ӊ:( \uYe$-?Ip6(VgUVK:[ $` _ba -^̠!&!LE  -J4`ȧ U:%" -8X [3WHk` -H\`-l1d%.`[Z$.[RIK\`paqm$qJI εN ,H=H\`y#qZ^ ޵޵5El%.;VG+qwVAb 0p%.V&*&0`Z k.A]㔑@?J'+q=tJ\D O`A%.p]1|. :Džy^Iޅ8.3J\Q-<jI\8 oVKJ1J\%#q"Dԅ@8Tޅ{OxrJ\:bq tœF:(t]1’THxnv&J\DFiH!x |R!u~ ((K -$q!%.Xc$. d4o1=-lA(qlH<1ft-"t:H\ pZRCĤ?pI& B-* 2t Ȗ.tZK\ lA4(qA4YWC#DWK:R9όDC%.4A u4!q''N$?H6:bI\f Fbf )؂O₤d @)%qA! 0/s%.HV!D'd}7`C"` $[pM$ y(q 䛈% .w]3I:."S/qo"r{u񙬌9⊁:Vq@{ᭂf@9G `&2UU( qi/Qy!gƐ/2aZsbvi}_?wJY҄ -$ Cqc$-FԌԠi- ?,z/~:}^4B_Y VHm=d2;r+ -@8Cf>%a2ᇿ_z yx3MazΝށE~^Xe+Wva۸ھ"{ڨ%VvM5خݷs|oOu 6n?o #9)EEʯv[94\gKRs nnk_2XgoDvt Mk SPGSe[fcW:!j[-/"!gI9$Ӎlh#s_skQ-=W~&v yy}3^&PÂ9$qIEVQPcs8Ӎu#~NWG=5Y՞;5c:dҼ>ޱs_mX6b/~<.Xzp83u0|t} 8 -(u(j7.!Ij+̯άP4hjZ FS$ZA:{Cu4JM(oL捯qf, w.Έq\muvĕpWcEf̻4mOUef*# y9fB.l}?0y棻)+[etTP :b SW֖xq }l)0muvriN۸B%Zu}PhʼnՐM#z͍EP749i^lR -:C#b+O8sܳ{%ݪwYqzk&BLY=m[6.Gci7ևư,Wg,3P꽌MTBtwddоLroKͣ@uteG;[FVgw\ G1>2ZkP=㆞UU~d/m]nuM+y yrc!VB;gwYdt] Yv|6v_a1{[7k0ֶ{gמ|'eu_+''5XgwCE;IڊQm^o>WcI%gO5nsh1#Yr|Wv^D,cތmuv. -KwLL<ƾk>*:Tcroˬ=APVV1Ѯ#˷wTrcݡr/(|Yu }5 -γ u%*jaFXgoIg'^:CJL"om;mKs¨u7C)s>>pAz'4 xk c>9{~o;4n5)Gx4.=k7yEwIgokߙ[xWn;tnV:ү._Ge2" /XgoL+e7x#]kAտo/5͍uv֕oTN{/1ul&~Gjh'ZC:Cs!zVh(-be+cz`sytd[ԁX-?濾cԣ4M;m<)Q -yܑ?udYb#=^֟3G'OTf9B 'Jp#s睦~*ryz",7?ƶc; tq,b~־pWoҏP~e^*;Q-L֙{3s(;5a6Lh~ʺǍa|Mj^Jʠjе>dbSke=.^cǦ9ӡ-ؼ-X -rp6|dM(m.Z2"x8d'LͲ$ćsFCt,oƫ`E[~&OfF<=ɾ̀,^\Z/,K+R;a9m=T۲l䴩B p2ilզlv(*]@M~Ve(R1E{Qjdk8C:JX2 -2kW)Mso{dA"Sժ7-sT[JquDǶ"5`=D!7)ru.~& @֪H -ô\-)ayќ:[7EzrҸ1oN9[>69 -endstream -endobj -559 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 558 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -560 0 obj -<< -/Filter /FlateDecode -/Length 4776 ->> -stream -x]K#9rW|9 h؇U]5f}#TJ]ָ j)#2S>+_$=Řo'5/X]d/xw֊tѝe SH~?O~?kG͔7ڝUdCPNP%ʹ)㼠zBST02UA):I3Ș("̰ݪ0A: (%`"Fi7yttFO>&D]N#鬝| KEIG%%-N)I[ I\pTV}F !? [6y ry&m-a#BjFjFݦs&bY#-UX*hwp[-9unPǬ#xFowN?X#&?zO`>#g׈gwSAђ}7%-/l4un2i̯[{]WKbbwχ;̺辩E^ԙ|uisi6/F,bkp6?ok ;lr+}n˞>\CpWq;6i -0 eϐme!lRc F>=Z{N%[7 RK w^/68O.2J}4Oy -,0vs*u悧0,--}vL?@q667f?Ž~2j2fivK6y'-*_纾k^`^w)s?eh[H)Ɓƀ;yoGNhd\8N*]S/uh$qs˟zɰZ&],Ӧ: \J36T8S.uE_ ?.P{Fn,x;kVNʟnԒvfY>u9?س'Zvd /!}y2'=pb rqR7uTjTsR)kx\{];Ud=۠o%*ͳ -Bj+`Rw÷CiK36a -Ja;o6F/6_sPAgz{+C r8_Ȍ(<ҔAa8ꔟHt<)?s+}.y#_^UNC:גyy3?vP,:!DA?F>y5E]=Y|tod5G1/6MǾ ۑ_!.."ζb YyjRc:Ƞdn"XCjG; '4[[mFZB!^msYZ.{!]H=ِ>Q]T2𥟽Ǐ;Ww^̴l}_)|Zd -*[hV|y0ӡr?܋FO.z1g4:9FF Wzyɡ7ya4et7J "8Po~ȣ_U_#[y!Z+-\}֙(EcďTD~Ny:Gp,v*p,1]g*wfhGܩvh9+7F4.bRtl`gCߏيFVmu9̌җ:|-<":PzIoPriG?u4:3*o&gg=޶VzkmkI7_~1TT;c,-iw0ZY'*ﵗsf~ay>f9?O&!VTJ6CGu>Z8iÿPq4Y>1.|%g]j*"ŧɯyh%oy=D>,˯8r'YDtb.U-t=,.`01uZ>KGJk8+LR%F Bz+֫I/bi8WS0*lR2k: -UW]*h> -vojzuքn8]һpEEf;RqD A Yݨij0 QMJ:At9\PSŖ5o4X;^]SVO7G-b>!nFx9F~rAHW(W mWnGҤ|bYd|+?SRfASܮZ%<7xIW!4.Bl_:*!=nM]{l%Tc늺*f -+SbkbW7;]NʼjM+wPG\)Zn"dFK%MlTvN )4q,.rP&q/3>[?G^?H3^y)ų7ܺb(Oa6PGMcK -7kjU#RWU ]Nl*t]ϸe|4=_8>{Ϸ.Vo.c]ͥCKˈP\vfLd_Iz\Wwх|i.܊. B`_+M+{^_=ɾVj^ZJxK>m=T˲ܳ5iS1Ic˶$p}TdJt*Zb(6%[(R1Ei׏JD׏ߤrǫђZTKYc(|JEuo{A"SղMʇ#].*ywDv?5`?ը_ 풻lwII_c"kU Pۊr&PAWe$#ȿ m> 뎧S -endstream -endobj -561 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 560 0 R -/Resources 4 0 R -/Annots [ 562 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -562 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 642.273057 101.433071 623.523057 ] -/BS << -/W 0 ->> -/Dest (cb103-1) ->> -endobj -563 0 obj -<< -/Filter /FlateDecode -/Length 4418 ->> -stream -x]Kܸ=H !aE0!?CRÃvXTUR7Y[)BΗw')7 $yaUt%G;?-x7LmYVۛ"#|^ZF0*k:F%ȩipb -nցQa+TE"N7TQ) ?Id4SV84tZ CtIYp(*" 9/p:_4Z'2_tRqhEda -N)aM0I3: _kt8x3ZuF,|/|/;0D%&t0t7 h90RAGFKc a:b"q\`4|A / lK@ tK2* r.ܔ0 8.0\@)r\`qb{ XX9.0]Cq\`一0* kxHs\^X:qwuqwG`u^`  -.]m渀@f]P:m8.@eB#-wUDc4JE5rظx0i{~_^?~{$Rx]Vop}S:Uf=Klrbe?sXM+;Է\vO)~^fujHzkf>z{A5$֯:~u)l></QLmo@"7ծ(2욬GPog]@cu}Jèwa| S{!7ׇhCiE$pvÝ6G1fU7^qӖd_ YA*Mt6lFɩw BJ{O9rw[Pmi]r{9W[ϴMH-U{ ¹\Gl;IBUM)gs8~zgE=_f3_ -?P>gtɗufg6z/p!tqѴYqwPؗ'ft=^VB.i\sҴ }y(Nj7 !V;mNzBQyGJW2[.#+/{}M)sgƧpػuԖ?6ԺiϜ<ár#k wSb-d.=(E@fռaΪrv6۵y xpܸ Y^ܑn2wINfNj7{F<' -K]{ ?+2_{r6ɫ"uկq۬%p:mO{;\sLckŨq{Xp<Xk\ӶbBEupܸ+;DcM/flb﹋0Ӎ;&O{/JƤS -;ܖBeP _ޟE4Nϕ6GC͎(|^c> -Rw|pHDZϙ|&}VpXܳFwfϸpLp| u}HOw ~#'$~Ƿ:m;w?5wGzW:myyg?9R7rOi8yh h, -' |܉c|EN|ᐸs~] 29*7s,_qǽNá/|ѸO%=[g~M\W o?{ eBSw=NM5@&-ı㤙eOy9KzOu=ISYw} uzBxaR%%\W~;g6א|rKjO N &~OARb9lkw:iôu`,~w'IOqݕTA?ҮĈ'QHEvz%rKI6݂HBf/zbFKtRQv ŒGb]Z!ekpSlv)XSGJӹ*,Meori\J~ܺZiEjs!T]N[&tf7ve -Cr1cD[n͖T1|uB݄lhQV&]24 C z\!m^+4MEdK~̲UJH H}Q=IE+[NtUl '-C`'s-V+؊}q6,zgel4'|*ֲDzFX)TqAGkaǏuqr49mJ{涙:e^ț]㸖-t։di)N;ga6PSCUB-k3J׺k{. -ma#Ze e֊%yjԀ}=4p^ᠽ35$*q֐-m8lNg7 ۓOS&9h҈thjmβ*"HM{VL=i8{x=G]IZH[i$-Kp覇%s:ȃP4cϔ$Zh# l,`ۓRMNE d}ɍfY+l+STmK۶WJ#ڶWܢl7G-ξ^%K.kjIes9ڞˠꈫfvQr;WJW* #*mMIy9t'8ٸ,ms{dJO3;#V\x"n+ay(KJsr:d5ErTakp0ȣREjtd?, -endstream -endobj -564 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 563 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -565 0 obj -<< -/Filter /FlateDecode -/Length 4795 ->> -stream -x]M$qׯM` /0=5^+$#QYw[/L*N)~|QS -_rq:?)fob]'7諙rF߿)T*~ Ĝ%UEr -f8cJ0úVaI*J+ءR(tO$SHdQH:kZ)sg%-^;$lq6EI` V:bR.ɂ.+:آҒ.䜨ЩVg|VI:'lZQA -QϢx៤OxSfmՒcu/1 E QfD$qqr8LK.I,`R\VBX3Z"`wAbauf'q5 $.g%.`[H\`ANe-q: 3kSpXP.%.\ t1ݣk}0XЮu)H\`i%qZ'wVQ42`T'0H\L&%%qk"\栕wG$ 5^ x8$.P&.(lJ\ ,wu4j) $xiXo" -#3Yhř▁[Eq@|i$nL,Sw VJ6P_cn ߢ -CL1-dr /}yM)4!40}k42HZ4n .ldw~YY -CT:(Z -zʭӧ tbޥo|Dt맟.#)i|:7z 3"_r_t5;e% LWm i^oYtji]W˫Yt˧7g-O6k~5:NcIy ]ui:i&V^権){Ś.W"hJ[~`1R}ix®֖ 6kbjvBݶeSui`t}G^X>5k״^Wm{mSxS?+Pq6V~sv6OA5j/UD-ۥ|7\-'XZѭm9?C=;ޱCPQߛyn-b5:-}.6JVŞ`=/AnGTM0nluSK}u+>7ωy,0vyOq,}]d+@ql6>7ڸn?qOq<ն9E ijvZK|t|r\7N-غ3׬Jo[~[B_c6~dw-@>УfwSB`o U*SyVbڶ*EeյE_yQ(׿~ۥr+{V">{8!',8NOd|m6r'lӥw>Dxi-|\d0㒃ǩl4vCSEA Fɹk -@gHг ~Rgot >$+Ƈ_wP˙?՝ ,95m[☵y4Ԑ-ni -J%l)=$y -gTxNnlHtW>3k2ȗ&wC:.AΒsT>go{~ǂZ渡p[ٽO=."ZB6>yu5*;e$)=w^#XoF/X<~ny$<ֶ [2O?^Fes%dlz.!5;j*M-6#-h\BC?,-͐H=鐚9U ⼗/}(ݱc@{C:uܷ͞ZΗ\L6ɨ =V4&LD{_l ^6zrky>wgu-?7+;q9F =yc^rM;nz-vޛ3[Մ5x i?jſAn唝sE-j9z*G8=pm|fcu7wC{H-Fƨ?Vg|=>Ycs}ڡ}_樯ڠELg9дe#( ?Ho7lQ.cdz@kYNuQgLH@Ƶmm[s?GKw'<Ri#ʦOCMQ1AiGDaƎ{`nˈ*zjyGoF>y:$Dȉu v6:o7ޕ vDߖʨwtݏyoտU-#7q[ӈFupf's4i詊t= :Jyii0J'jp%l`1֡< *k..GԳݍģI=Υ'<"A<:싴 -q{#s篁T{j3e ݷsy {2ܙv;1s~rlO2ɗ*y:TĢG(zt4>*;; Af|_t<5?rrn>;σ`ǒWD'<J'7S 6~l_t(܏-˓$9ZiW?t҈ k53ۅYGo}@֎;hc{g=S'oVes϶ OZ(mIyVVG2UeXm -K-Ib.+iGu6iZd[9co)[,Y๛ʶuu^Y3\7$Tl~]3v"T_ѩ$GtƖ߆S)p.풇lwI 19kU+ oPc+-+Iu=iNmv<˲I.Cf)Mc4Qi,X&zYm -endstream -endobj -566 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 565 0 R -/Resources 4 0 R -/Annots [ 567 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -567 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 588.873057 101.433071 570.123057 ] -/BS << -/W 0 ->> -/Dest (cb106-1) ->> -endobj -568 0 obj -<< -/Filter /FlateDecode -/Length 4402 ->> -stream -x]Kܸ=H 0]"搿j!bkr\$Ё8(k \ w(CK,(qkM x _x _2p\@D|AqLHq1*sZfu:9.bqR"s\)\n@ -DЈ9/9.@ R _ r\t(I Cc,t$83p\ȉ*r\f&4ض`&9Kp3p\|Rs\l J(Ha2q & .x3p\xCdD DeQd_>}OfG!@R+4QѷVb!c:@[r_w^L<㯇˛r^|<$*+0|4K :1Q'vWJ$:zq-/1&moޟ˫׀ћwNJkV/ȍQ>K3w槪Wveۙ+y1Q窮12[U{QGvv{4YM^RZ:yuÛ) -{ ZQ ]Spp0̬XYu|1U2kڷq/ ӦiLes?mX5&C2Ͷgbd@O r )R-w!ÄrKP)>!nq8 o;pU~Ac.Aj0vGQ[fנc@vF}J-wa| S{Qg/װҔl۱o w Ɠ6=|M4v v z7?xO);<ݑoA!÷%EkVhF6v텧g\El;0"gs8ގUuخς o?`WO n?|ȸo~5ҕcfɉ5>L<Ed"lM=Y_kVC?~vLb˴s3_4`Q]x?5S4jJi8EA-t 5f#p1sMC 8ӵ3$R")r %1RkgE&H|hP}Y*ֲww}Bx|W:t;c>"]far8s+mFhzgimO5$/wK1Qګgmڷ(Xm8 -7l niG>sHKHpFHѧ=f^[3d]_±1zlx-KqL3|Yk%akU"ߔWJOﮰIrҺwk<  ^N~3a{ȏEU~8a$5']JMuώIui \uj(lu^"PR˴aaڬuqs20T$R'B$*qOi'YbĄ1u8 CY"E4V0͇̍I6~HDfzaFKtRQv Œgb]š!ikpSlv)XSGJѹ*,Eiore\J9\ZiEjsR!T]N[&Tf7vR -Ct1cDn͖%U1|uB݄Rl(QM&N.@krBC z&\!m^+4MEdKGhYJ_ib@QTKՋYBj宰q%״Mq) fRA2ԥ&ҦٽDRڵײ.:=Y=t.YXM#~Pڌҏk5UsY=TAUѶB[˰]LS22+7Y,%]:Cⴹ`MLl/R>OmUt #ҩ:lu w$Alړ6cRE>r HBEJˍ%i!<^jS7=-}9xk LL rjӨMNZ6P(e䢹(t̲>,pǁ-%_b*-iJ)D֊[MDK@w'kKFZ"d4vmmPuTV3Hl&K? -u+RtԤSP ShK=%'P^o+.> T -endstream -endobj -569 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 568 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -570 0 obj -<< -/Filter /FlateDecode -/Length 4837 ->> -stream -x]Ks+|?I# b`v{wbvURkƳ6nUQ$X(*|_rzJ)ஷ.?^¿buQ7V.N^8M .yu:)`TN1ŨP)mSA&,`θ* T0UEm 3LNR }TZmu0D9g~ - 錞B&FY;ג.O!$->+-'D]N:䓵Ji=y`ӊ:x)DAg`KP>:2I6$x!jIa1щ:؂آb(4/I`b\6N"K 'hd?Vi茖*]j๢$. l ,֩%.[tpaqm -N kX.=J\`#qZkV8)` ,qq:Y xj%.p]:A`e2)) x$$.p]18k< ]㕑w3Ae(1B3V6%xΘ[M: quy=.-zy!d 04gv_B/Zwd󼹭^wz1ou`W;ƞF^? BPDL&h{a74Xa90 ͆S$VBʭԺX1ڷKf>"<.7˟=]R.|Ƨ7'_0}"w~NawE KYjvSmZl4mֈo?w1utn·u6uuX}o.{\Y79,s:G!Fe9 4kk3\Ay6T f;jO?Py>u}BA!eh,%k>kpHiYEdx<"Ǒh:BCk L"#if3خ91m "(Ǽ>6*M <VwȟXNCޢk%i]a3:y8t < qޫmv1MXyuLڲڂ՜bmilj XŘT)3-kmZsN1wȗ9w[|.:|jiobS՛u:n+cq->U`2͑١zߕ>!ngTVu8l,R]Η$rZ: -s(}s`رC8ј_PHP΄,=cZ[&_g{m+bO[ڿ`؞ `ybxo\',l^N۱JYWfX0a.Oq,}Z|k&5q8Ps?(qMF7gDx_axI6֜9IB ԊF/gƶm0n|CԶl{R3>:e5/Tn#glأ,X<^}Ð7{p'bHSx\.J lʟa!™Y`ZCȏ˥y\D\.=!Yu'S;) :@П(u>؃:ڑ}6r/Xh?JH:ݼW>B煸;iּ]dq!8Ʃl4Cs1@Xu۠NFf:4TZ}Ԑ)Vw\Y5>>q acoiy\A6<mn͌zoz?䫺q+ng-;'\%㾴Ň4_>E=TxG9V*;(h}G#5F{cnH_uƬ}~\>>gtmeIum@" yulQ7f#2 6uy$m:hv?@\g .H=a/~4\Cj4/G<t̩j@VDƗa(1!M/e_ZǡMM;챢1aR&ڻ[1҈QZmpavcVO2FVpг@!51~*Zm]H=ѐ 6l44ڴOkwLEVbo;#Tر -涌7<,xwh<;#9z}m{2Ď9:.=#ݿyDZ#gcC4Q ںkCٓ91s&m)sywvd4iEaƙ|qÕn볁{ȇ?:rlw5hʯsy N|2áN,zE_qzgU@2+\CX-W.'P[#zxHqK^h(QϾl辤op]Tcļw&{U$wV"o_s ֧Q$ަrU6{zy}0_S7u=Ul-Շy,$7N՟+=@Cd<`ƖVMv -z {w*&[buqMoDm]λNiMdy$]PϢޫ]kTYfTnR_Sqm"Rhlz6jvY*\Kk:At|R5מt:^#de׵>ocÍoL1n#~(+Bm:^\ݎLIyWBNXI=]iYwfy餄D-u뱕u\#j놺&& -Ӹ U5uoP~^W}+Cg.m5le[(&ZIf^v@ -]i6v? Rv'fKVӻy䥯EotǍjla|&4N/Tas&4~6{MBMі?ކ^l>aϗ6VpuOWV$(iҡue/-[I䕴' -Ku FХ:קY^tV$-;++{_^?{C6jog.m #i#> -endobj -572 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 517.623057 101.433071 498.873057 ] -/BS << -/W 0 ->> -/Dest (cb109-1) ->> -endobj -573 0 obj -<< -/Filter /FlateDecode -/Length 4380 ->> -stream -x]KܸQ|$AlFrrڻ9$RUj{ t -DHD.J:'pm9. bugjҖ_/OxUG%FUfs}&Os@ C+P+TYW{Ӕ^&?I^`cSUuY`ab;7:oKagial.<<Ӭ{[HC>*>;mP|"d"0UO>_g@)HiX{9b:ފ+[j>aPdUA :"lqAgW]Vgs8]+!fzϦT><@ɵ=훱#*Pr>KRq!E+Tv z,yXN2 -B +QMK! בgs8$ĈጯUы9GiP7* -kryյ\P͇* -3B$SjIſ kXڧIէnŷ^(;m9{c>d _߃-4;3;mF3y+?=;yݐoA!÷%E{Vh&6v텧;L57"Y[9bǪ:gA t? ~4ï8Ts9?j|Vȸo~5޼9>L"{6Cd浭i7~~,bv.:63AA뇞P]x?5Ka+ޞ*kis4k iǞ 7 1`g=-QFeu~(Õ/ZI3foc֬-s9J7[޼㷞w|CQy=t߀{UG{pH݉IHH-=߆is8vƢ^}j_U+vz^t>4kDPQෛdm9M8rD:ׄ3E>%*o/b7/ cxjX"Ty+%rUcTcU7ӻ:ISZ7yM|BLKL_o{W yg\U凓ERxt:nI]Jl!K$Uc)VuE(,OZ(,ʏ -M`7s-bWR*X-VбQ+N&X7c Y< έ ǹq=i洱:3*g[G^?yc>@mǵ,l .uON?tzfS 5U?Uڌҏk]5r&RUE[ \XjeWK Ժ;mL:z/{qpfs%RҹKte:S\V7g 7 뛔OS]&ݫˆtiflu OQ%Al:cRM黛ד}rڋKBx nyYsN%T2U3%șZh% ٔ7,[4w. YVr'7b8KL1KKֵR -ֵViS+ђ)秓sKFj"9ɲiy۞Ǡ7Gr6w=mgif"TgQa>r5)o9!钛mϟgII}'T cWۆ P}EtZ+o%H3=4Ӝ\a)a\4Tq8[RE76 -endstream -endobj -574 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 573 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -575 0 obj -<< -/Filter /FlateDecode -/Length 4842 ->> -stream -x][8~_H|HhJ#xXpgfW,خ8tΙ3F0TR?Uv*JR]o?^~)z?%ꢨſZ8yCI`71\/oɟ/'41gI3|tmUfΘ$̰.jUeav -f죠 -vh!9kS@IgR6YEt4)Dty -!$lYiIa)I[MQbUŠwKJv99'2t*Ŵ'UNVaFaBt峨-*#,lq+Ɣjhv[eŘDlK `lQ1H4/I`b\6N"K 'hd?Vi茖*]j0sElI\` lA -Y ,-XЭSYK\`N qL%q (e ,8ׂ;%. ]L(qZk] -XuZI\"-`d%.p]Uw1 8 +III\&)'q 9h%.p]swWF5 h -r8[@Cg(l2K$.]9 tA '#z\I%.]8*+q> H\SK:6YI\äH\6i芺< Z2 O*ID]$-qxRC%.],qA*oQ[l2 VV'e4FXҁwY%)qA$0I8! -6c dB>Q&\{ DlqI\z6' - -$.@D0e[\E\8؂HQ0ٔsDCJ`Aע.A1 XK\Ԕ0%.O.I\3Nₘa pES2%-%.@ $[ J\L*3( ࡱDWK:h$.H.L*J\i&RЄZl{ bQ[wdh$.H e$.6i%. - ⓸ 0Q,qh:$.:aiLdOZoF -!-0oIXo$]-&; rL z%h`&IEd$.֛lLV&Zq&q@z=|eVQ3P _Z#0+]U( p¼ķ3SFfL 辭9z2l_>^/NY n[6`QiEژYDlYpxȍPտbpO)a!/m}q&GھhVG^I/B{ze#$~R$kklLolEPN<-~f T "€46E}[% tbާo|t/7}|+\+MOw|"]W[]򵎰=M{mRϧu9$6[oK^Ȗ:J]K^=Cڌ|uv}7@++h鎕[sY>_9BrbޅK{:<B]!WM*+'ݛLf{SAT0|b)X˩S'C"-s#pҎCh J )CnH,tBp FgF1А7QKlQ@,yOCMk2vCy=^ƣӸ?Q /1q#Zw\fY~2á\8Hnˈ*zÆG}'ƞhHw"G>l8rb5;GsGd;lڇkϵWp=y?z)qu?h|A[w wh6{2'1iѩ;={g7+M楹 wlQ=xW +хgvm(.!GԳݍģ9Ky8DމGw[Q~YjłOm{z9^MkGkH^Qz;EGYu9gi~/(0jDzMyCGSҷ6چPt 튺aWDZ^ n46JotL:]Nם ~j2PzczeZ~ D_-)WEL w b*w$\V fqcJ'|A5l>@j"[ވ7W,3識Z&iUh1&:3koUU{4u]f::͆֜.֎gQJo E5,3*7)ۀ6Nv_Z`6=5z,LH5 ]tKiTlRϚkwS:mj/nH?F戲ZLCVl \ۈ/> -} -+вr8.5 S譕LIyͳWBsם塱z@Ӳ16I t[c+)2&G$c- uMLVq%jbߠw;}^ʂfp.;8fo+a -oűQLO.6y^v@ -]ilmT߱|LU -V[y䥯Fowc} ǍjlaܓobM*lӆ c:qc_]ub)ucPݴ\{2i5ڲЋ-ܱ{qZ \%_YݥC ˈ ^(.Y[2+i]O;>b,KuY^tV$-;++{_=>{C$mޤ\FFxԖ˰l>ǖG=ʲlC eԳ- *aʭEK@9֩ŒII]Oil[[]5uCBLU7)_;sa'BJU᨝[t*qs"%]<']kpLZ5l3UqPΖؤu=iNmvJ˲I.C"g)M7Qi}!e+h}Ry -endstream -endobj -576 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 575 0 R -/Resources 4 0 R -/Annots [ 577 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -577 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 457.623057 101.433071 438.873057 ] -/BS << -/W 0 ->> -/Dest (cb112-1) ->> -endobj -578 0 obj -<< -/Filter /FlateDecode -/Length 4395 ->> -stream -x]KW輀|_@I#ĀZ{87|l5bW)nxU,v5cѢ:JP/!Dxzp[SI -$/.$0^hw.䏇|wϥ:j}TdK˨"TRFe^[Ǩx9ܰ4-UnP S :07 ye7Wĩ3*%R:8"ft -BwN+Bԑyל<)8]98tXE$9|!,uZZa1)%,iXZ*yFዓ6:bԜOXC`ZNH8/Z{bu1vEzQZHq^PđFPQ =F*HbqL`|!\V_L$ /Hq1Em hnIFqߒT…5 (E 8׀;9.0 ]4wq4k(8 xאxX:s\vFqwi P8t+B 9. 8. XhjGznRs\@]Mq\d.(|r\:m8.@fB#,wUDǴiP!: ,xWTBy8nQB99.]tT } =wAOJGq"nB!PeuQ Z2IXd,$P x{w5ޕ4kCe4U!5ӁwB s:>r\$Ё8(k \ w(CK,(qkM x _x _2p\@D|AqLHq1*sZfu:9.bqR"s\)\n@ -DЈ9/9.@ R _ r\t(I Cc,t$83p\ȉ*r\f&4ض`&9Kp3p\|Rs\l J(Ha2q & .x3p\xC=dD DeQd_>|ﾛfB0&Wh:-o7$C8xMr-ΓnItqs8j)ŧ2J@Ns7|D%GmҘ;r+%]$:{q-/1&m˿WwNJ -?Pk/|flv2ALUYM[di23_]7}]\)m+t?/6EN&J>L%W`ytSseJ ^d}Zù= .G yMi{c6C|2҃>|Gnb49v6{CGތ+[jQΧjq]zkYAdZ-%sc6Cr\ruD&F$ŭA!z\YF5{v5>aS6У&J[ko5Q+ϴ]YAݡrcrve6zgi%WMBۯ"qfoH41n8+owƀ(J\^ᲆ)܃{Em-TjɯV B$nfS/| i^[ -Aݡxcޘ7 wwg_|βvC| --y4-2;B3sKn/<=FDܤgErkErfo뱪۵Y9]=ȻMk$f.rc6CCmWρ2}]ƛWY2\PDvk|fw߼;")ۮX_adfuŵLP mvײ/x{v4ŀ1/xwjM(kFI=.|iJ1{fgo󔶙s yʋ*`އ6+6C^.(KaFaƷ2Vho_7b]z6Vl|aС>N;wY3sd#lv̍uofXrk43\n7xVe><Сgtu;g67Z[;C }np?dߦwf_qf|[A}=h;ʼnj:_Ʃ,_rN{6Cb+Ĺnֻ031eyw {ףé0܏kYBn=Y:< YXM#~Pڌҏk5UsY=TAUѶB[˰]LS2ԕb dZ7>_pIGep>.Cՙ%,q.Zҍ!.Lq0V.LloR>OmUt #ҥ:luMO$Alڋ6cRM?w7'- I c+-x.es1][KegJSF -h# lN`ۛR]4w. YVr'7b8KLQ%mZ)hZq)hɔȶpdMYb\k]TS,[ޛ.{cTq52.RM7? -QtԤSP:ShKn>%'P^o+.> -endobj -580 0 obj -<< -/Filter /FlateDecode -/Length 4763 ->> -stream -x]KHn,kx}XPݽ R<v6܅L`/PH -??hIO1zEM)%V3~jEar:访0)$g^p.fJ,S!('XJ[q^`y=a)I,ڲĠĂdLXbX -nY bIbA \XZAmyDY#<%ѓ$H -UőjB"DXYP@k!!+aE %xKJ{ ,b* ,FOX@.\)IX`)ab ,P:o$,]KKX`֢ȃ,p` JX@]UFFXuz +QIX@]IX@]0aZ k ]㔑2 w!N V+a  pW',œZM:&/a4 ZIBe%,p]g?aE58ஶX%pW$,p] NäHXm -+ҤR8.`HXUxRH"G'8T$,]嬕w!yF#a0m9`uRH!JTHx./%,`#a4>)[TfL)6߿`/_~wʏFK+L`n[c(Edo*݆e‚/+Y!* ȄƓ8K' - <"B26^A} -`H1N|tq\~?ۿgx/A)A4RnZ7̟ʶz_r}'[-/v,|nm[Y}I;Բ֕2G͏qOΗx#zo)iUmm֬bbLTLQpNgB[ܶx17V{]lH،Ht?Oy6EfCcdb$3 mʲt8|jm=˖d!:OtTv^aI-f7Xu<]Oy:<4Oytr^O|zhYX)ʷ-d&{^zyqY=e|`RK meQ|:3FI==p4硦Ō=dgPs2,0_ 7G \c1ʡ[wVucߞtx.|++xux6{/Eqmg/kZ]t`:Owb1/w<ے<~yrDAtIX@fɤ}hyckӶo?m'hg Z6LdG"ukoh^[giO]qט8< X4, s۠CNi;@.>UNy!K / 7p[x5l6>}\mIOV [>wŠ1[Ns['4~Γx]Cnln Gf~S7߂ok(a:{ -tCúvOy:Oux~Ϸ%oXg~^]J;r ^=[Lo+#Ӡr#ӎWX?)dgt_>N^B6G_v.ZÿYL-{0,vvQsqJn庾[՜㷶Ecwq}U/YУI~]WJ߰?o>^ slU"$ՎȥL+ˡr /74M=p=)j0(T,V*cpe Szmq:1T8iïz,Z7Yt:+[_wjZK-fWV~Ub)k6/GՌ{U&GS.&LԎ!3qj[fv)%Wh+fJ!5w,Q-G&]q˕MJl R_5*%k:U]#*h~weUo*z:ݙ53vAvT~rihרJPR])Y BNv?4Y#9cq$R)'nҚ -TlUS|U 9l&jk;1%6׋ BiװBz=vVrT_5Ģ*LB. RyMեMusJ龢IZN]:곽tTByZjlETC*1HUXuJf+XU5"79]NμvW|ɡZ\kQ 6tFծu`Fn0eVt!XI&.y3>i|嵒:nTE SuEW2$FD!i u:xC]ǍZuՀAuDtؑMu]mw@ Zڦ--3B".26mKkW\-*o]I浪.0/mQ[f -+}äNJA臧W}ٗ -SZO|חuͱ]MC-=[65ZhAG;jlՖ -miY(*\ -L~VԒGE-S4zM*UߔvˊW%[ ׻shSd%@}JVڶoZ]Vk7 jVmJ>̝ΰ!*?ywD"f,Ԥ56m-y@.ys.I?{9&V%Mt5U\-)qHoS=`Nmv{y^NbYz#1d~7j$/< ^ -endstream -endobj -581 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 580 0 R -/Resources 4 0 R -/Annots [ 582 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -582 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 371.373057 101.433071 352.623057 ] -/BS << -/W 0 ->> -/Dest (cb115-1) ->> -endobj -583 0 obj -<< -/Filter /FlateDecode -/Length 4538 ->> -stream -x]MܸG  bd,`$ {E0!?j*QgƖx0VIbjϷEC)x:?|8}-UőjB蹢DX[@ka!+q"qݒJZ % 3k' ,(PJXpwJ\`AA ֵ ,hRX%$. )` ,qq:Z k -xH\VC/q25Q5C k2xא(Gxdw`%.x-wu'iՠc8h>QPBE-$qb8.3J\0 xW[ԒMR8.'q0h8`|tE]TQ- 0 -*ID]$-qxPC%.] IUZ d^GR^tpDp$. -uI\zH6E - -p$.G0$ [El(qlHϧ`=oHYp -$4֣0 -iޓ'l-NAl$8'*b:7fyF&Gm=d2;r+- @@%3%&dwz?#`QʹKt-~$]nk7J&Ke)I]ɧvkg(|@9=OkSXSM<|mД2~ߨ9vm^/8z3N(e߾,OK+]5Bɐbx_Vf_ꩅ☾)B-m,Q|dB#3рUµ :7F\˙$^45hkmDEEvAZZQGv}?r|z~Nw-@pY6iogtC[ Űfo;6ȫ= 4/TbT4y2t}yj'ƃ׶oZVw莍me[Iaz)/Px.S/22/; f|ΙKo<7:{ot%gDySͽ_ A-gmuU<& -5u 20oq1Qؾv'9iFҚoXya'"㫀 t7[Q(m-|qы}eisgȱؤOhgMjoE3{W5qu? pIy y;CEv#/PהBsm[W DaJ޺yg!3ymwD~37L~UZ(Dan?In~ٙhe/x{64G=/l/Ј2^^3Kjpe _+i쫽x{@gҳcl38g핵ʎ=},ػؙpyN.hgZV#e_Ht9w|CFt+2[DdiPw'ʓ߻lte9293ѐvֽ|ggwwo=w,cK5=Gޫlxrmiŋ[c?dgás?dۧX~fl|@lw9 -Ov/zMs]/@gyx;-Lq\o:4g~j>7vfͮ q妬pŭՑAnΣUoUocw9*wjتĽc]oPpjm -߂#۵>okv*x3MDޱ3 -ߍmWog.&Hj1;ڝWZXsϭ5+>nWڮx{Eؓod+rw9>Qּڍ2^K.}/5nnBfĽos4duˏ"<`w|ega찤bfbn]}(`s8T}'dqw|zgá {%;z+R\>(:Ivи>wq?-3aȇxH)se2^ Wm]^D~U:W8D2LB?n.s!76uKիi:|xKdiw,k<KsN>~QpVM3xNq&{46eʒ.M獜kDb)T]+fSc8DCLC(\S>=1`:Y8}T,%a=sÐڔ jj֕ƕ]ɖO!U\ˍ!rzW8WS/6C8H<\qWbB*vYlأm,ӬKZXs^>p[JEi>Ujר*̨T BI~JфƬzj0 QMJ:ApMRsTj~6eXG4#YQ|\}n*2ܘ!VǓ Bj7srz\hYUՌYE.5,=P<MRjIU$.uHMaN˪KP1KG%Ϥ[S[HY1yHżLR [e/‡q`VMfQuoƄa Y<(.mǹI#8Lou>ۖ{^yC9L2UTn]HOB|2znÄb紮09ԕAur됉MіՌ"|hj:2Omy\ppqyH>"qC:dXF\Bqnfff@Ԫo -./yE, \`/xM軻ד}2ٗګKei%>(-.]/'> -endstream -endobj -584 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 583 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -585 0 obj -<< -/Filter /FlateDecode -/Length 4553 ->> -stream -x][ ~ׯsl¹A -Eh}`v@҇~R+]r.#9+Ys"))%o;YdCPN`%˹)zSX2eA):1Ș("İݲ0AĂ: (% "Fi7y(K<'I"/xN>vZ{#Aă,dcxXoȃ,&+d1Nxȃ,+-\D"/b[QnrZ%lӊ<(L@\yYe$,?p6(Vë*%,y/!E/AVĸ$a adHD&B &)H8`h ,VCy&ȂX Y Y ,Ж`-X-%,[RKX`SIX`6zraJI ̵N ,@=HX`y#aZ^ ܵܵ5EdKXtVZ22`V'ء25Q5.@ kJX@]0swSF2^Qb489,X 3V46%8NpšZM:&/ayi-0-Rv1s4o[XTKyw;"rM4;B{W,tλ׮jU=J"cϼ&Zeq˗h]8ujq)Go-Zz]wt~O4-F@hD7X_[+jnoY*'?~7)RRp2o<D;&oBJŽ1o[:gq]{WGFݟhjnĤ$ -{`Oo:gc5Ygad6Cevsg -o^>n:g7b_cK:g7]æ]}yYf6b1G3f).7Rox*X7yÇS 47㩃u \LsXb :I>`c&ВXu8C #~~y]):&ՍOa9Y@ ,rhjo+tL* #:0~[ ghf1>y9S4Xqz۩KlNd ȋ)< cPo\iGYuW # -VCu$lx٦wayeĵŊSU˶.eƠ,Y](a+ah%Ő#/9tp*S?cu*{VyqP7tzEr|`.yy ly-T9?r n wukG-Rm>DD~`Tve9[ͧ`WZhzYjT7CzXf+ko>xKەLWNJI`oƗs}n0f*AӞ{USm9w*8h9>/:c|,rcjR=WG!-.4ۈYz3ڮe]ݼ/[6gGeSlmx6X˃I3)XnCaju.lүy6Su>sV8iÇҟ=M0Yt:WjjԎ7Oy>N& -o6boƲ^&Y[5ݖ:PGMu0 t/'tk'ghצvj4;ՒmB͓@6MfO"rHXLV*jMƦxv>Z95l\uk1CX\5hv9n/bUf9 QyfR|kl䥒FoC4^vP/PAn[P x R xދȾ6hoԧx2[m>懧uv l r-nFW+)Uڢ(\*LTj#B):QnD7Ίߔvkђm9ѩ^ŒQvR/i+m7-< GWs¿笝j'B*U(o8jME!?(%w?'LD֪wdHCS7jICOP9?&Q *Yz#LPZ9oI/Qr -endstream -endobj -586 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 585 0 R -/Resources 4 0 R -/Annots [ 587 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -587 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 292.623057 101.433071 273.873057 ] -/BS << -/W 0 ->> -/Dest (cb118-1) ->> -endobj -588 0 obj -<< -/Filter /FlateDecode -/Length 4632 ->> -stream -x]]8}_HQHXb< Y"-<9NNũ$wfsӝ*SˎWEC)x>ᢆ)|jEap:g CH}'g.m )y_f!T *rn8/p)I*ZܠdLTnX -ڮU nIR \TZmupDY#< -K:I.@t>vZҥ{#Ғ/dctXo/&+|1($"|/+-\D.AbkQnpZ%iEZ*AgW.:2ŸO8bZɭ*%/u/1E/QZАyI@ɐD&ځ"ELL`%0 Sx* X_y /+M$q5 $.X--X-%.[RK\`ApSI\`6zr$qZp$.`]뼑v-E/qZJZ KQ_` J\@]UhFFz Ĩ$. 𮉊$. D]5 ]㔑@?J'+q{茕 a?MwuD4-Jy' xwAQpH\ڢt]mw78 A#۠+ҠR8.hH\^xPL" i @ƃB*q{OxrJ\:bq thBF:(t]QÒTHxn6%.! L>ҐBC'c'qAP8P/HC)J\ |H\ |A q"!iD. "E dCLD1CJ:o@ע.B!ЀXK\%.9\n@Iₐ 芆hK: _dK\H:%.  QWXE-Hqf r(q F`JQ_@~`I\:bI\(qA(#qǛA₤ "> C%.CIG7 I\vǛQdƛ 6YǛAD!DuAS-8 M$ yǛQo"boqIҁwz p&"[il@. >188c@}8e譂8g@y$NM,g ЭB8mh '>E>3| ͂1ǜn$͏ϟ^ƙ In[GEa!|&;-NnItuc9f$oCz=i Ѥ8ƂGH,3[隐d(5[R?z10]\k|ח_[BoGGQ&g~ -bpҶF y*o@K[EQZ6PT9o|N}/E(Bc[HtN =4ѷF\S꜎ZҬFK~I|]4׼(̣ѶWL־nB-̮Aj{CADҘEc2S.k]6ClNă02kMls̨۪崑WW^]i5lyAFzWι]w_e]"rȝqN鐻;nsըb"y`ҲZ4J}At=/cN -q@?@nِk:hbqziE9XmO^ƜB-х]zxMA,jtnQϦ6GK;mNȃx{ -(^ꋞ51ܗydИS"Ş IEgs:ǫ=H{9mKԬ?ӝQ*ٔdrG9*b#[ozcT@LN!Ěo9r@]F4CGqσ αdt(=??S A#Ƚu;mNRӄYmJ3S:ƅ1ᘙlo.3jOaڊJ |D'\HƲth;fT-G8YF(80?~GB6gC(=~?O~Cle1a^ m6}6C~y7vgZ\ub3r3zgs:Dxﯟ쎨6_[is:Ǖ[r&񵒛ޫ*7 -^#ݿ!9*sřmmcC7t|EEy [FWzזS˷ )lcҋKU>6g^ڏr iKG wzߪ_9*7 >27l1jm -oA#{|֌*x[&"X is:D|'޽aъ=ARߩaq#H_tTskN?ܝ6}1ZQ{Լ:1yl'tnϘc50>v#2y۫I׼oRTt:=nXPSM;`@궝0;0VhᶻєYrɻ &L8 E$gplRҺAM?SܺӸr5ȎN,aZ^ zr`#_]q !sX[ńn-TtPGjYX]EY&>_pZJ_DiޗdUJר*̩TBE~JքʬzVkyw0 QMJ:A|MZSi*%?2CZl,I߬([~.>@knJ|AC+!B=.,*j,C/4"{CoT43CSTm>Of/ }eJ@SӲ!TQ 3ԵRVdLRq/T%XWUqR>+P'pY*_OW*^N5b_Cq7|yبgrYlT1Ha42Kk4}972}2vs:[呗ilvvǍla*.ļ';Nq޹kaBCgsZWPqc_lfb/)ueP]\2dbSke%vM)@u3wطC[.y0:;wW%rҹK 3ilf$?I-?\쀅:YuW gL4-~y'}iYZJ_^XV“v(w.em gnshAQ&ٔR-NZ:J"9ⓟJWR -5%xBtV*mηx5Z5ra:5dd[W))mMs.fG̭R>M3!*숎Ik5p'ziwȦKٟ?Yϒ~&T@֪ ^H -˴lxI0=4ӜZNS$Q= yҸŶ1o1u]8 -endstream -endobj -589 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 588 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -590 0 obj -<< -/Filter /FlateDecode -/Length 4360 ->> -stream -x]K#Wl4 X$ k# !?_nZ-F f"bWUDRw)-=?MQyCwLpQm .χ}u9Zs~,r*X,m^h}X(L1g1|$K1('/ YVq 1l4$ > -,!Z<xƫg -),"x&Z -7/O H<Y!KQ"ċB;Y%J"蠍ND^OyV{sZ<❶A¯NxSղw;H"`%$)% l% lr% lʊbt %pڀgNCOABg sEdq$,pAKN%XpK:  8.8 K$,p\RsSЅG P`%,p]G)HXΡȃ,0` ʙ$, 3:JX@]`A؊)i k& k#Bȋ ->$, k+aw- a E w!^N V{𬓰)D5Oi2) WE=1]U}$YoⲢEp.+ -y.>eO I2|Zm\7(*4-(5K1mA|$KQwo{,뷇FbkÏbޢqDK ڮPi_:yϼwկ&U4X1OKt.{.okY0ׂ.tG;gMJae:X?}G^!ׯR᪥pz% E\Y/XBjR%X_QdaOUoѤ_ǩrUN}Ji;\-i}cc x~ϊ֠QhFS~ \1ƻh=go<޸9` p%n;ps1YBT;^kq_"oq4nkh}VylEiz8zNR_gl_tVpy%\bzƱ>"-ҏq,_/W+Ѵ߅aޑk5_֘pqZx^{Zu;l15;X Ot:{i]upֹ3K;4m.b%gkƫk>sɪu.r36(4Yr eQs_0ӻY%ayYe1"\aH.t 'fnk}EoқR9-KR]k'/ *;,nCSl;O=ǰܡ}> LV8rڧdqnl۩>}uI EA,8a0Er.%| iM_lB5>W_AJˆ|<p+{֖M\ZxXX6F\lw,3GeJyVI*gYpe'E mɛ48Lj+W5s~ѬY*C.jOӺ:frn3gm6LU =j;ynSU>T-c3ul4D@# ٯ}TKC="-C('Ùr:ILJ)kH|#Seㅞ|YXbn,ɤXe+ >32QߏBfTȴJ;_/=?{ hzRl,3ҵ+yM79g|xRn -MΒHc>`xlu*s*B'6Gՙak["[SE*v\ڵ TnT_[Nt_:4a1X5>3r"jHN by4V*VwU]n.5 ӰOѮ>]y۩N3Cg烏Bk߱Bjz# 6r^:5*f{ -ߨ<剡fR|jf7al䥒FzhC vP/ОAn[P x R VM6`x*d6ToVho6`N0\[:ɤ{:t(a:oy+$Ќˣh -:zǭnha.c$H;}f Z`Mm}ǭzw݁4 AMDu8m3]kܠA<]KW'Ǜ:|h -tp:|7!\CG\ra-doTӸ%1^ i_Σfǡ+bh؍dƛ> -endobj -592 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 217.623057 101.433071 198.873057 ] -/BS << -/W 0 ->> -/Dest (cb121-1) ->> -endobj -593 0 obj -<< -/Filter /FlateDecode -/Length 4598 ->> -stream -x]]ܸ}_Cl$F=N`9Td*I׶/ݪ"yxX,QJ}_JĘO/R'oJ8?UISGw) L!9C_\̣Zr׿UֈCQ%29vQy%p)q*v -0æ8̰ZGFaA* T0C%Ci)Y 9VǤ Щ91tIx]t$s)k%-I:/p8.buqkL [ [2p\@$XO0Z 󘏡V9"5ЩqAV`(V`.%":= x% `tr\lAWC9SN6tSエa A ezqFh%Q՜<όDEv9.@7LL` hOl; 0dV[Ĩt3r\#lRs\lf I$n2q _f &xLMf Yࢰ:)1&؉yآ y监o£gC17.ft]x` ϖK xe3F $aleC܋*1 s$6h31`XRI6l 'CCȄna9GKf6c1^O"eOAR[W:o7 $0<و -8ݲrtzSN(Nru KL0z1IgvWJHwuʸb>8aO_??F>]?tWߩp ^>WSKQ7CiMҙq\~j쏰1οk13_GI2mUdWf9o%o-),qMv75{CU3KOzs\>-/C'GkۅeYWڳjzaQ\ [iÎd /=m~Yj)|6di*Ǩ/Rsd9*=/Q* E<Z6>7cyֲ+5y#dW}t#gzҌ Gii4o典kUvo pʎK 4םZ{ũnޘ͑oPt0pElKWycn=A齲񬛣uPϑmxYOIڱ`ӡiԣG"-JǶ?-˙fR|Zѳj>љQ!G1,kݖ5Ս"u,z8GrSirkΟUgZoExamWvl͂-=9S $R/q]}$9́cGQy+Jvk(缍!s=@oˣQOEXse=It't,yvqZ{tښwd:䭢3#J$+n:lHҦ#Ak[ݙ;#>ݹQ$&pyN_E[}#ޘ}(@y/[\PM19 7P|`ӡtlg{w{\[?y`Jjծ~Nǵ83?3(V|pzCOʧwjf2"GG'Fߐ5{bOQiwرi8_W<3?.s0PRV0Y'(["'OͬV:HdNWnݚN[gCA=>s:8 -oA&g9♏+V`|.2zCrSuڹ3G/֡O # -$6YYytGr0rUK:b3{M;`׈H,rcyΆY2vͯ2m]ƇoQY9"{#a;L[~35ڞ:iʝ\2ʚO2ߙϗ69~5|nbT#5狟vR.qGtF0m5J4*[]7rN\SʼE_ޞY/9<5OwQ&~S-#pY8,J*hH}JㄜZxޟSr59+6VDf~bF^P8?|5b3@KӶ[C2Z(XbժMXMUH:.8/4zY*ebTRWRhƬzjyﰻ0 ٚ.tvaͥR-k*5LiP7V<#h6#ҔK-PZF.bJrqIWHWG[Q64i~j ]K;U*3PB*֎Ir߬e%QcP6TTLL5uTT$Uc)VuU)OJ*]Btd^Znʝ/Tj^K0_i`8C?4uk'#fHL[+;ɸveq:7*J=/u|^e+8ee ]u!#Y<EX jKhUli]ACǵ&|m[vوTAURkuHĺBW+Cjo]-VGm)Ә ] -rpδ!JQNچth&q@ !9aj-̀'U)L>9 nD>4Mg0K.*HЂ'M {^nd_z@Vj*x9Jm5T2䴮\ 8%ز =-I@Q2YdPlsR-GB)mZ_zK:@9-e%##4wږvy2^efol*SL߹"\7EGTlob*m);{p[bI L -endstream -endobj -594 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 593 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -595 0 obj -<< -/Filter /FlateDecode -/Length 4598 ->> -stream -x]KɭWh`:~,$AIp0] – 3&Ycu=-v%;XjE>uZ%}VJR/?~<)z⢰og\!Dqٛ/'_N?}L9)X,~ 0Ŝ%w͊%p$ uQkV&j' > -, 6J<Fi?(=H<"/xN!:S' JK<YvNI<2B6$VC*%,D' /! E AVD$aqr8 LK.I(`R\VBX3Z wAB!yf'a5 $,g%,@[onZ uJ ,b* ,צ$,\Rs-S rXHX`֥ aZk-z<8Yk8.VAdRR8IIX&"8a Z pxLA]㕑w3A8Qb6x9,X 3V 6%xšZM: a< ZtYEx.3IXQ-"jKXw4 &"/O*$a“J@'8`<).{ wV‚Uiȃ,6 ׀e+i$2@ -Ux]b w)lJX"LNȂ!)$,YO ^‚@,Y\t I‚h 5F‚h R LY#wY)JX$RvN‚1hU3y <%,MZRS¢?Q$aO; b,X* M 3x ɖ.xZKX dA6(aA2 UfP B%STg& `R<bKX&YwdLY27ތdYIXU(M0RdPo'a%՛I‚lMxº6P%,x(" iº&:IYLvL @^HToFq3Iw pzT+df3; -[-E➁R$n@LT)`j%n(/1w ߢ -p"M2cY8dFy=-:}U)k? Bi_a s{dӷʿ"!| R GoCpQ ȔnE1C1s|w"GdhY֡*~ߡ+Iֻ5SSBG@.M<. -E'66B},e- P%y~o7NF)Jեicmuﱌ[{\׶/}l]<$JWαC7wA\?7Kw*"_ c]>?xEiUaʴJ7)׎М -yUynޓ*OWײj[` OEg܋O槈<('L+C7*, XY3r>{ϳ?V:k6׎"#е -2}Zw[[HjF>鲟ю6Xtmn4,۱ֿո'wq+Xyy~(5~ -]m~܊TU҃XRᦧtz#YƊ|+QPrHoE}C}G(_2amx?_hf+3Dzˣ`9??Hʣn?} FGԑk}So_$ -{H5>OsQ,P\+Zgy^+x_-KT3?}o?SV?ټ"VΟYx[;Ϛyr~y?RXU -L '{otE:}꡵?K<~pCǂ{>Owy2L -K_rrߊ`c">_tyre՝! |?5ykި֘q.s'Z o}`O`WR1m˛J+h;Gmwty0ޥn\gٚM(4<ڻͥ_B谬6|>K\!sZ=9Vi|}Em{5xN{,yVy?.|XjyTJ0;V\K!ue%bV [vG34٥gk[=k_iMM -1L\ڞ.uN1%ELY:gV@*=\,E^9yɁlC5Y+R ʙg_zkҳK*oqfضT׶etPe5(>|`+g$LkWdC~2soi }ټX97,OWkB3"Ke -cmt!?PyOOq>ϸ Z"*n!5>081G Irw6j˲rw4Ϲ̳ͩsZ띯fӪxYްt#Õ,a(l`zwyDNGo$P7xblt]p,oIMx\Da\]*G%Ս>LvRFR^` wJ'F>}:+ qs7ּ]2Xq!Sڽ׺qJ#+Xw_e%Ub~cB"|Z7D䤆 *8l4:w*!Oy]w):L}\䥒8=tq-S,חNJhO[w-Les@ǒu2AXOJNTMn}wyR,h;ȡc 'nqM'wyR[S գݸ# -<`jTo""S szCeg@R0n'qܨc#}-X:H kľl8h78n k7쭥;!#F[CmΤoROig6$::Kv<$[IoUO;n -Kb,K;xnY>tY&H-;oB?>UVQ;w L2,/{̱lwheڳ=Kcnq}QVx~Sh@4h}d -[SKq{N1*][%\q[ْ hs$ݩnv}owg6 7 #3Uj=v>U)#:@v:Zc׫07dEv}OwI 19kUE/` 6T][VS=4`N]oJ,=M~T/F&>g~F,Om -endstream -endobj -596 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 595 0 R -/Resources 4 0 R -/Annots [ 597 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -597 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 123.873057 101.433071 105.123057 ] -/BS << -/W 0 ->> -/Dest (cb124-1) ->> -endobj -598 0 obj -<< -/Filter /FlateDecode -/Length 4611 ->> -stream -x]Mܸs bd,`$ E0!?Hf=OJbI-ʫ7#w"o%z{肽~Ht!-to.^֑W5蔴ן%у ˨"TBjFeིQ99cT0zZar*a -* mkUKé`3*)`TB:"ъI;8ttJ.DYNz7JN tXit9-i` -^s:[z'2[`pBr1.B'kvAk,YfyF`6:bPNNڇVfZr: [ >GAC%p$L0c` hx@ h[qh [ f.-: -(qְEq 5"J 48. \)8.`\@rqjp'9.`]m@v  F - xWkdu8h4.:`eP! xWa8.0]X05,.]ewQe6B,,)q ,xWF?fNwe8Hg-zyE ,xJs\`q8~GUXԜ+UX.q0H R."qƒ`VIr\2P x=r\jq -kôe4A(0 -t]!|w$P8 -V`EB>V[ Xl1p\z: -Z) -8.@D0D]]؂H01xCr:A׬.@'=ޛXr\09.)\f@' >L s: [ds\H:)9. -  UCc-tFuf 7PL4&8.Ŷ,6auE[qA*-7!%fZoz -8. )L4DT˴ D-QD[,BV[4Efނ;q:[T4Dz3p\0MDlJ g]Lq\7rk{ i،ZV6e VoZ#IeplnJ)ش"3+NO4E|Ȉiaݗ5G-7M|{?3eG"@KW*b-o 2vKtRQ48'ْQpwuaa) ayZk^7$g `*c}oց5$&X X!$p(JyWE߽`6VLr(b7^_|W?_[,K= -728n[s_s\*^^۴i7me[Y^^_uj;. -Vn\a@_^O+,1a[:g+ٍ_9@(dks*kONfX* Ǿ[]RFTc@Y9(Litf% -#$+@Lh}ΛSgXNGw͌٘q,q{fmmoE%:'A]5<{̣d瞏D~9 jָ}D9"망-+ ۟-s6oŴrl}&g%70^(*x/uoPy<+º}w$-~uouNă4 wxqsuNθ1 }Cs>ezIǷfVO:.=26tʷG݊o?yn8޾s6}{pG>xϼg,wTnh~n{3G/Cmy(ܤgi:C~~/<.2= ~4n]=qh n9|~rxKLm[Waz{أuΆؙ{:"CϿw"wc#. 㭸v3d5ij= ;5~7|̍H~Й$ػZs:\̬P }h@}uNЃGՄҴ1]n*EQHm.YĔqbDFM fѓQKLdJ1 [nn͖TUcjJGԧ=o:\]<"ܨcV⧋Li[B =*Ԥ"JwOY6GIOTa41!b s$"^v:i|-KKz_0KKO[J[HIټDRI+Q]=V@ -U\iiZ)?IyO)mUe|F^_y]Ǖ(l -.ԓzC8mݛe2XZf4?kSJ칤, * -mC"VJj3vGb d;6aO:_N>Q*a:]]4TtޮM*6CrX-[IOR>oPt.r@ˆtT7Kβ*HІ' {^dg@j/'*-x}My*mi2t rԨYPidQLdYig\-wxŁ%_b*R:QqJKd)}:QKX202Gk%umJ.TC\LEfW%{TDpϘGmJ_c -wsv&tu',IΟ3a8x0 x M=[ բ`/`C*;4^>0$Q9ihǬ!]"H?4i -endstream -endobj -599 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 598 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -600 0 obj -<< -/Filter /FlateDecode -/Length 4420 ->> -stream -x]Mܸ֒!@1`$Ev۳`C~%CRnUEREի"[- ./NOV__brЫ_Y+{;xöߝ=ϦmϿO*T*IPYyoTNwb -fXφ*38+`U^Ra%zAF)QC3Am0NݹMu:퍤#gmsIǰF%-V3+I[t#%` $-]-@WuE9%],"t*e;Ӻ&:x&yAg`S6:bIIG'|ݤHK: [,` &_b`NxPxI}ѰD&Pǁ&Ď'L% 3Z"RŲ4lax-Y2$. -I2"qnYE-qoYi'qpaK\@\@)J\@\wJ\@ ]d@I\@]b$.`.j:K\vHp##qfJgBP0x0xxQ; I\]c)rwUF6N(1Bui#Ÿ`N$.]0}.vc(wڹ(q"P ;DT#qjBt]mw7X N# -uS1 ,xd$.@T:HZqJ\QUHUG -F5mF)t]1Ò8n -8&H\;dF; \T!uñ+,(K,q.R x[ -H$.@FE[\E\0lA(q YocUILKy";pt~g!tg.^ 4B2CqEۢučk\<ܾVYp|\D޴3׊LAkMW';xQ`:zjZsMs\t&9&DZ~lQc5k~2XCվL#͑I-)6. -mmNX:3KhQba_Oqq|wr?z\2O|b8ߐGr4^bei>>}[9Z_eGؑ<^?yٌ5CG=_s;11j9%e\d>G3w=ılGm?cN/g+$s}9BIN7Ƒ3 ,o/-Z67XUdF:eC9A4+CጵGn*ć[zSn_OJq:e GG?sUHXKrS8kg3fK+n)]Fl"mK$Uc*uE(,OV8]ljidN7p*v;[/3󋽥Yx !*ѮV@ -U\igo-߲mXL/>&#f^_y׿N|1|F0['60,,n 7_:Բ6qcZ]Ub%uaP]1lĦ@hjF^^fXOCʝi(ݹ>[;8 UG5$&q֐-"Fq؜0V&f&@')Cv*(9h҈tHU5̶MgYߋR`jچY'{vOd= I c+-KBxC7=,1 ;o5G%ɩQS mV e@Q2eEmrc<,}8JUK;Ҷ2(dKT ީZAvr-IY<7OϝWC\LUf%{|g3ۉJ~wDj֞ aU9phyvu,wII{&LGD8]لG(ⶢi*?jWإ@4CMrfbS)%!=+-.UI?rx -endstream -endobj -601 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 600 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -602 0 obj -<< -/Filter /FlateDecode -/Length 4762 ->> -stream -x]KƑׯ| ֋0X fzi|0|TM it1"/ H}UFHz1Oח/\¿`TZQN>,aəo.:j돬";r*AT !N1%I3\ CKUT0* KAۥ* 4I* J+ءR("kvǠ{Igc2It0NK4x]t[\RZ94tl u`%]-]-@WuEy%]KH%T q3 .Z$փ6Ê$ l%Q[UFYBt gCj5Z9bL Q[0[T` KJ$0)J,`b(+рIn Vi茖*KL`5l!\Q[l" -( qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ], qZk)z ,xגVxZu8X޵Z ed$.XLJH €5h%. q8swSF2^e(1B+q  xW'?aMwu4-Fy' xJ\(q8~G58ԒMR8.'q0h Z. *(qƒ`QIK\2P )*8$!/{Z̮~|LY%kK$L7j#l0k?l { -R5QG g僞 {bPfAc--՘$xaDnmX{wc$B8vpG+=hGMwV8ml`kh٣6&YP#(ea^BѬoyrvÏب뻟/}z˷p[F!rMtwoU& 55Vũ4ɷ56}qͺv*nvccקPޣ? To?bsjVd6DNVojrR?t:;_ݽX/ZsCX>>811aU9 ՠ ?!n$p2c8P41[Yab][f(hD;8X$(fĆV -N4F_c|-rq|:crv83z/ }[Y٬0 -8)S9 1nF;^Ou> qƸ]3>,g~VYn0RH;hLKz"ֶ Y1嶾Rzj9UuP?߼giŎ+m}ev>vE52۴+eݍ/9*˭8|(Ӣ:N٭f\s݉H4^M^;e_X̞nfiBױ^Lأ?4.'skSP{)1lɗs2Nk4F|3{8=Vl8n;lo_|@{H#}TϺ]_ffG)mw~oQ62Q1):/9Xthڎٌz͌y;1Xjv- -^mH1|nC43>d/ZkWLYi=K~Z/sƋ+,Qs:d:N6&vmfxaψ*]ر nmQ嚾ͯ f8cuNĝH+: -t^yvs}C^n]•Yyjd2W@`!mǎgmQ՜K8ԣQe]YdxWcN -qЖms:dmvxE+,Íх]g}xBڸʲMvx\zvy2zZۡ4Վ_鐷fό&fH*w:Cvzi`kk] xLwnG-+lr nܜXĢ{(w6Aʮ跁rϗ;3w.P~وn1ީsƒwDt{ρu s|#ߗs:nǖ$>Z)rҌ {=sYoΙEϱ iڵor=:gC[؉dT=\,#4?Xt}z!>7D\+mbB~D%=s:x/7U|ŬϾЙA9mDs:DvvlV`!.VL-Ğ^G.'Evwų#~}4C~P<+m!YVIǕkx;XtH܉O//`ӡ`ܘGSːїpY-OrS;1OwNO料{hzb9a1\=G8hz,Mk%qu_J)"XkSL'N4ʽLhA]w$ 󠘅GU" e|z_ҺAMSixh\>r5~)\Ȏu,Q류^ z `#_LVamڲZqWjn)TMwUl(ۣ3e|ۡ&4ӹ%|[KD),7Gר"QH].Y&< F Yͬ_n˜D\E,7LR*֪)|5B2lIQ6=@kܘC \\^+MEUK򽩷OXYƯoTኔg@_Sj'6x>H!i4Z.Bl;^:*9~E([tpV|m.Z2ME0Uff2 NгN徚&C[uTltgAlۃamif`}2BEJˉ,㡟cR[GegKSF -hvbZm*N)ffGQ2eŐmS<,GqB)v];+e];+~QDK@sgjKFAEJͲe4;{ksT 52U[|Y;:]&B*숎ipԤ5oQ{p;M&]rw2K'mOUAo+&AMSoӋjItJsjm=$Q9 UW[z#7(-/dYdJk -endstream -endobj -603 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 602 0 R -/Resources 4 0 R -/Annots [ 604 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -604 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb127-1) ->> -endobj -605 0 obj -<< -/Filter /FlateDecode -/Length 4327 ->> -stream -x]KܸsQ|$Al0]"搿HRK3hl{0VIɯ*go4St|8}<.8}A9|tY`C3Oovȋ?ӿut)yןlb VP9ׅ`T^wbJ -f@3(E'`UKU&hT0C'VCD QD::Ad `$t޻(si"%` $-[%`J[ F' [(`JKd;"KЩRg\VI:;lZQ$ l%Q[UFYBt gCVY-l1&-|-*xA]%L%C h;%01uh$בOA4tFKD`lq%&F Nvbf nA뚣+ņ_>}{?wʏFЗ&Wp0ٷFI9TS'R3RMl$_w^~XOopz8qRp< -#D[26NJE¿{{PG+=zGb;po޾?JOJ7:v؍N3Y_t$i;^i=?3;:f,Sڢiʎu[^A2k+]?[_m׬jzK}7߿LNd̙׮v_%e5ix?ЌSE3HVgR{'@aSݨ#0Su z;lHHϝuP"N"QFaD!a4DXAmX7l:9*W7ḟ1h!ϖ5c}uIg}%1 KY=~a[䙏YfsnKU,Yv.k?l¾5^\C_K)oB߾:CF<->g!kK5u{g eFz(op_oΖR:9:;_y=g%ϭܳ߉<9e2Xwݲw=;-ߏXkch ϒ8<MBe2z6US b3gANK[:J-V}dVjw0:CFX2Ĵk\ z`/ -{ sVU`(!nicc<igu߱LgVud]̾9WfX\m50ֶԮҴ4?IA-KܻYpC.b;׾V[;F<|~oƒKZkܞbF%:CƗ/ˏ*2`KݘWp.oQ6XR tww/K¤IJs2Yh]lי[޻7 -*\Py=g^u> -RYVjuԍLܸx -BYZuЍ}{(ᝯkܜ}%^(|z'~:CFN*;^A]㝛Gx;л׽a犪^ݾYhH9gGzoo_s8E@ -OzbĻqFۢučs\w}~=;{kɛvFp~ W5_Vo9߽s4?)V -L z3^mQ?<èuwC)S>^^wPvGns8޸8Go!zy/s,_w9r~:׮_n~ru^Fxj;>Ip=1b랹Uwp:Cλҩ엷^'WuE; q#D+]vt;WzǞ:C믕Ӟ$ -o≟ԃVHMdS[Wpܙ{dM\l^2'/ޥ/#Y}) R6˛?ߟ%Y.\?\j6ؑmʺ=u8^Dz05: <{ ˞2w{rю riGL;>\ 1KY=h۾d?5'z4jYty8x _;lC]`!ߣӑ=ʸf X><>&Kl<#"t:qps>Sn8 9X˔a#߱sPsvt<9rSMm2t^Xpw㹙=kmci1O;|/&;{ltϹʒ.S畚>RT~K~7v0Ox*uf6&Ջ)Mxo"AL|CGUB331ti^ҺlF*֕ƕTOI'U -9É!jzޫNFWS/6C$^5*nULBNĆ=:oj::ͦ5M5ڹQ(UeԕuBΓ 74M̪gF1crDXnlՙ -TlUSfJuمސ_|Dq*y\pc !Ǔ Bi׸B=.*ItOp"T43OAST~G;j'ɾYAr_YZY6\:Y>^X 3u&R6dLR1/T%XWUq2>+P#p&vʏqUWɼfpw&;8*.|^Fsq~,'ibjk'cfH>⭕qIrԇ9cI -㙗>e_':_^N1q*[ʭ1d͒q8i0!FMc+ -j75{)+BƐMі"F&2OC[:Zbxwpζ|fM(m!Z2"x8d'LͲ$uħsFCt,o^"H-? 'M{v'h/ګKkDz,֘c8oږegk\49eت?)%PTLYm1X K(R9EGYEnx5[5rΡN5UJ-izmϬ -3U[l'B*U~IklnP~bȶKns}dKRO0YZMx"m+XS=r.6P9_o> -endobj -607 0 obj -<< -/Filter /FlateDecode -/Length 4832 ->> -stream -x]M8r{4Cu.f} J$CT̮nL3 A(}UNR]_rQS -JEQZ8yCןI`71\.o.yL9?)T*~ Ĝ%UEr -f8cJ0úVaI*J+ءR(tO$SHdQH:kZ)sg%-^;$lq6EI` V:bR.ɂ.+:آҒ.䜨ЩVg|VI:'lZQA -QϢxGҁ') jIa1щ:؂آb(3h"^88lD&%$0)O.F+р~r!G-UŻ 1հa:b؂X [XZ$.[oA …J Ƶ)8 ,(PXpwJ\`AQ ֵ> ,h׺$.]봒wENQ[` J\V(qb 0p$.V&wMRN5K栕wGk28q&H\L%z]P=tJ\&D˟0VN9H\:aD]tD <J\$q8~Šj$.]mRK:6YI\äH\m -uyR9% ?"$(P*n(p/V((/HDdkeJm?60>-8D)R#3wbH6㯗߿`.Wv X;<0 Jy&mC YCF܍ԠeӍR6_6Li[ՋPAclm; -?+17^/fhAC,n X7pʼnƞFoO.`y8\6A_< \RvkQW:Ȗ1njҟx="Ƽ +#Y)\]I,}.|ߋӒfPsoK}n-$/zۧͦ{0{JQ?uEH=^eͦѪf&;YC>zj>tɍTwEAulZlX MuOq 8նޗ:]im^Fb}YR7l`cAv_gO'4eJGM:_q=v?ݾ_ |ή8YoZ3Q1[dT0C̄ }ʓylPDygcƸ54칸5` r)=tJWy&xɹ$mIO`k#Nt _nHGũ_|:cX:~Z>YYCm@ AE;IPvjuvxZC[:y=(2ݰEVGP3VUY$ֶ:ܮ*es%dlz.!5;j*-6#-yq8<1岾Rc<R>Q2eWv hoHۤ(pR"q୑5\WJIsw3z҂CwZVPe{4GՄ5x ijȭr~o mM2N7iD\Y;noױ̄q=AY̸7cs}ڡ}f>A;_r2ӡi[V4dDf#׶q?)be̢\2F_Mz+9i3mdOB鼱>Kw'<Ri#ʦOCM~Q1Ai^{xa3Bύ`nˈ*z(D_=$sxdC⁧xdXWΚanӆZ9d6ugwGeT@'<r}gCeDu~(-ldάt1M:z<rviUG|vq%jpŻl`>qXۿ.Ī,Qv7GKOy6DtiW[ -(뫕W~Gf@f7|e2S)d课z.!u_=B~bv3>r<? ~2!wOHgy[Óy { R([͸g}Lʻ@GE*\Kk:Az-6RJ=k=MPu +}H#le׵ΙmcÍ_/XbFvQH;W(_DžIut)MajVJMTᛔ|ѮANWM$.uŞuaNJHOR[IY1y<"Fknkb?+PU#P]巕TU4ovqhű4{[ UZ67 VFծWƄ0Bw}+:[;ѫ>ɤKYV:3XMoភ/1:nTc Ӹu%+#-;ӪM&4~{MBMі/`ϗ6Ue:ۗ++W/:2KVa$@JZדs#v,/J+X_=O/PgI7,2/ۚc!ujeY6lsr讅[]p2iٖWlUi](]@MaV8Oѥ=N|T&-[W-y[zK&Ax&u=mn]w]mgz6I=2ww/HOѩ [5RG .풻lwI 19kU`ل7(U(,gJl} lu۾)6gMv)TZrz.*>)?uO -endstream -endobj -608 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 607 0 R -/Resources 4 0 R -/Annots [ 609 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -609 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 683.673057 101.433071 664.923057 ] -/BS << -/W 0 ->> -/Dest (cb130-1) ->> -endobj -610 0 obj -<< -/Filter /FlateDecode -/Length 4388 ->> -stream -x]Kϯ|_@C$ $ Z9cOiJjIb4U,v5"g_+Hwt~I -o%M%^ޞ$/.I`jO'şN:kʞ}TdK˨"TRFe^[Ǩ9ܰ4UnP S :07 ye֪7Wĩ3*%R:8"ft -FwN+Bԑyל<)8]98tXE$9|!uZZa1)%,iXF:yFዓ6:bԜOXC`FNH8/Z{bu1vEzQFHq^PđFPQ =F*HbqL`|!\V_L$ /(q1Em hnIFqߒT…5 (E 8׀;9.0 ] wq4k(8 xאxX:s\vFqwbi Ы8t+B 9. 8.  Aqw%pxWv(#l -|:_@ C Lh%X̘[ wU@(G3,s E2X.3p\ UӁw E`9.BqPeuQ Z - $ Iq\2y(9.p]iw%!auq0l1dUH t]Ü+8n -8:p\`q $%tHX8x e:B8.@b-њ R }/9.8.a>VtNA׬.@<ޓ@(V`.%= x% t8.`p\P$Ff|Aq2] hl゠fNr\$ӑLqA 'Rq f`JV_@dr\&:b,q\NqAEKq曞( 2> t"ơエ曚8.LqA4MLqKMqA$b:)2&؉9#q\Kq 7ѳK!7=\޵L8|-7 ^둟ʐf]1^.Hp/g $7͑Eep*J|VpY}j3O1,}sbfe}O< WJYSH҄ -@GtEpơ4yINXTy-9WM9}D>}_Fߝ;)kw -w {:,SuDlzZW;OZ6=23k:Y^CT w?^sV'`RJnKmw]H#oA!\;'˹3ܛ {}ey⣇yVeRxCyhGU/vw6z/n~ep!tqt,dkB{{p(3!C=z˽M{9iY>w~{,wnݘlqĠ}Q̣@ete'?Έ6CN֘q{ωiאBv`=7Ue^@;ovnigCw<9hs8D܅n,H7ъ{$U޿ܺQAaGwH6ɫZf-qt3hs8|^!W}8mwi:^<~{+8\!~3mńz.ѐiw{X~䕝O"10{=\{${2ts{_%bhnrpYż /v@e+loϋ/#A!d__mȝL>H@hC>1hs8{޳Fy ?3Aá=域hf#CDp6CNNI9B;7?[4y={F{zߑ6CNNI #Gp~pEg+dh6Us'=[T-; a'ct}PIr >+@C+Ϛ~T1{6CدY+:s|j}?n|Fgvrq.xBo #tpqͳ6xk )}z~#; q,|ѸO%=۬&._d'F}gn++moy7ymȝ_iî-`Ϳtow7km]&X -Dw rBޠzȹk-Ҷ&)Hw@,Ȩ~{IK(gҸqj 2i)$e'u!-;ujK^{+wIrʺkk<2DM-)܍?S }\u/'7jͤ Bّ0o9!NMӆR2m+l0:瓊$R'¸('qNiObDBp(K]r"{z -9rcGm${>,$s!3Dr91#Skqz),N{a#W\. aڲj+VF6BtU)[\ۦSM7yMxiM/}bi\Un]-4N"d*ĈOk&tf7Cr1cD'\-=KPMcnJ FԧM1"MehpWB O'Ҷrz4q/U~^ C3nA U"M3}PT vG$ilZ+C\ (l\ٶ 1ҥҦٽDR%kYBn]Hⴗua55_*Բ6qj.+璪0*Vhk6b]iZ^>vXM ؗC/1ia:SCGh Вn qV愱zp3=Ii?]aҹ&Hꨆٶ,)شmŤړƅ?wg# I S+-xsNy*uf왒ԡQS Zml{RʲIs(t̲R>,7tŁm%_r*miJiD[MW%S ׫d%#suR-il}nZ;GssTq53̮JM -uHjRhs) ΁C(m)4%7\_?YLAH yM,JnkfyҜ\aei4UqtY6REӯлv -endstream -endobj -611 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 610 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -612 0 obj -<< -/Filter /FlateDecode -/Length 4803 ->> -stream -x]ˮ丑W@|?F/ xi@a0Uecp@{}D2D۷iwv"Wh/9=cpۏ.j^ῒbuQ?/V.N^G8M 7\䯗?u}5ShgR9;*CTO1U>:㶪3\N^R gLT fXݪ20Q;I3tQPi;QJ5N)Ӄ3z -),"t:Ig^K<|tk甤-Φ(l*Q[LVEb;Y%t%Q[TPZe;u:bO*IM+00H! -:[Yot8t ocJl54ZybLt`%0$ - $01N.'Ivr%LʓJ4`\Q4tFKD`l.HL`5lq$. l ,֩%.[tpaqm -N kX.{uF ڵ. ,x:$.p]kSXdu8*J\FF ɤ$.p]wM 9h%.p]ik (Gxew`%.z-wu'iդSxN>Q'¼E/O:,qbx.3I\ \@.}dãX~?\RƧsa>/-%-<^EW|)+.,tGeݐF]Fa̢SOZ^:U￦[>Y>kyYtր+qRFH{u ]ui:i&V^PSS5]UMÉSM*m?wڂ`@S^֦ >b흯7%m~r*k5,\ g\~^ʺ-׵/bQKV<Nuu]]r-+=[,M˟g-]K+^-Q DX+"˧{[ZTp,ZaiӟKA hؖvm.>efymt)(I({Fy/sϖ>ouL.k[{ ƐvL- Q(뢧tu^/is~R2ZfK1 &̺ev+fGmsS?Ky|/}vkb-_q~Pv݇86Bmt{Oq8cOaZd؃ |>:BmNٲ O;o} qw[yw`%>8k &D1| \;5+G9[猞tu"t*R'@ewOyՋL}:حiVU8|ضjnxˢczq 9P=@`ӫpr\gó fk7ݐ<.O|9~>[Fmg{zNE=SFcԝ$f}:F[c5ϰxi= -$.y$<`Mu#x9@j\g .H=鐚ȉ5yAO"{9,-ՐH=ِ1Q2eW;7UδbS4&ƄIh'<*#?m\Us# Uן{Nu,л2N7iD/^_YA>6u2ϳ){YGيFj GHo7,(.cdM< Ĩ{q=oϘ6F$Zm.ItH7pڈ馏h>eTLFZC^XPsc^mQY]owȽ>z+*7Yx.!ϘXgͰkiCvy} bGtxadC;xG٨bmA0CݺF4JkA;4=39]Lsy n#MJ70߱Fi\ǻ>\.>Oyz(B:rlw-h2sq3@zv~ڱ6yve>vg|8<>rwdgCVo~P~G ?,'SENL^'vU$w`Y_&sqIP$Io}9)n{odzyՙd'ŖתAyISR*ó0gګujsy=9rS_B/!n!j~ř=?8j6lK('r* - [ n46J &eCKgNrO-r#82bIS/:QVEL s;b._U+vH@qcJ'|퇓VWkk( =j"[N+VLW^t}r)JrO ULBŪb=Gm]λNiMdy$]PNٮE5,3*7)ۀ6NvߨZ`6=5:t -$N.b4F*Tg͵)t˾l([t^LknFx`qG!\|ZVn'ҥ05NzTᛔ|ѮANkWM$.uŞuaNJHOR[IY1y<"Fknkb?+PU#P]וTU4ovqhű8=Uׁ0_QLO.#*|ZeL )tq"H'.eXoܑ`5$=/};|ѥ:nTc Ӹu%+H:)!6m8F]SO+:n k׳N5n }C&6 F[3@xz92?wl=_8:AV7l_H\QҾC ˈ ^(.Y[2+i]O;>b̍Ku/*+`I[~ vWWFyzq_LuQ{rikIR[.97R'oVes6'OZ(mIyVօdZl[JK]ӞJDG%lRukޒmpulddnRS*uʚ!{go⿷̝9ϰ!No,NGkl6B8 .y8v0VEM' -E`E_铳e%6:ͩP)Y6eP~y͒ӛcy/ -endstream -endobj -613 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 612 0 R -/Resources 4 0 R -/Annots [ 614 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -614 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 573.873057 101.433071 555.123057 ] -/BS << -/W 0 ->> -/Dest (cb133-1) ->> -endobj -615 0 obj -<< -/Filter /FlateDecode -/Length 4396 ->> -stream -x]Kܸ=H 0E0!?CRxlkӪbQ%WEJjϷ -R"/NORx+o(19ԯYIª=KㅏV{w~:a[oNڨ1:ן{iUJ*èkS#֓ r*AZF!R8PzF$PZJVG$ьNYi%\::#'e9g#bT$/dtg$/:x<|h|/I6"VNK+l0Fr:6 ÈB'94|qFV_Bt k|hitiEkO9H8 -8 8 -8! -p4xHV _,9 /q8.0h2---ɨ8.0[q\`@pSr\`&8rqp'9.0`]cv qRKV_` ¨`8. Qs\@] #qzU`E$A!y1h8. 𮶸.rwjҎE$ wA!O {  U`+BtX ->Vhqfܢr.r\`T } Us\` Rs:Qr\`,PH8.@|J. -CwAKDa!y ) @B"w#+18$=9.@^-3 -+zӁwMa@ @9.pDq\ࢄ)sǖ/!,V_HE41p\5|1Zs\5|Aq2ovz_v~@"`2":Ъi<{Ŋ̥D/Rq܀N>  D9/H9.@ R _ r\t,I 1DSs:i8.DJ9.0LL hOl[ 0dV_% Bi8.h9.6|s\%|AqAN48tRr\U|Si8.Fb)3nqi9._,RV_4Ef܂0;q:_t$ si8.@&2zvI g 68xo"k=3^Ҍ3+k[% E욁9h71 ]5@XRIv@тOá3o-HM=N*y\P8͇3B$SIſ kګ߾x(9yPo碻s>jdAރU4|ҦNJpZA>ávz7?xO1;:QoA!÷fDsQhF6v텧g\El@"Yt[9bo:l'AsƟ=ۏ&vՓf)}6CC2n䛟e&r%~80=59"M=ҽl?^jiOq+Ef嵳p;C=~ki֔ŵGqJ(9j6r.&<3{θigvżqZO++rڜج*wd6gYG@:i{g+6Cuڪk k{ѾfNcz;77r?(ݍy82x$NѐH9x_Xd>PFSz]9>ŗH2sdᐹq[53ܚt{Ga,cKvT5n,&_/7[[5x&p|r> ͱy - -sNá/OXЮ\Ӹ4ilPPZ9:3rO+p之{%U2kgry9ngCq7چZ73gg /=޹wcZbŵ#Oĥ/e*cdVv{kgs8Tnd.{NLZ칚7YUڣ9fsV71;9"7B7wwh]=Aٛ{F łg:=VdfmWkE_YKt v苕'jw縙֊Q {y.E~3kńz.bᐹqbWv> lM/flb﹋0Ӎ;&{/JƤ7;mʍU/Տw#J/Nwa/votoVFs&g$ 6CƺꝯA3n>?9:_(L3Azѐ6rϒHv is8|HÎo(9:o硻_`DՋGppHI?K@#>6N!4v@2O |܉c|EN|ᐸs~]!owk%|gE&H|hP}Y*Ѳq3is8} oЙ3tP3yQl;!Gimڻ(X8 -,7lpqG~0s#65䐢O$XV鋟OׯYւ ǩ[Rxc 2!^0'\[{%9Ryz2u*뮿C]硞7o 5W~;g6אn|rÞIj7O N &>MARb9lGw(i´au`,~w'IO$qMTA?nĈ NqeT.Xdpq^X!ǏTnlmdoYd.d}n'ftj)NW/iG x+e!R[VX 7FhBٜ5eT4zt\V;o /'̥O4ʭeƩX6,BjBg}ki70d Q)s9Ft9l)_JjsWW*M( Ȇ6>m1ތiǩإ}-C^N1?gJfB[AVTiz C3^T+U"M3|PT G$ilZ+C\ (l\ٶTLDtiiFcv/T!Xq>+[NtUl &-C`'s-V+Ԋ}q6,zgel4'|*ֲDzFX)TqѧAGkaǏuqr49mJ{ݶ:e^':7Wq- [­qSvJ2lXZf48uTe%\RUE -mmF t2MˬK"ܾzh4&m˗A{98 UgjH>7U(!Zҍ!Jq؜0V&n&@')M+L:WsФT0VeU4ET{8qzzv.<P{>raIZMK1tomRiƞ)IN5AFX',4B,+5r WV%_ږmFmETox%[2%-}:YK\202Z)Ւ&˖s=7AW3SY.3v6TVGTۑ"PFsLNpBipOY.r$gBw2FzEV4U=;fQt_0Cbu3.eDЧÖ2].\}, ?, -endstream -endobj -616 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 615 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -617 0 obj -<< -/Filter /FlateDecode -/Length 4878 ->> -stream -x]Ks+|?I# b`v{wlNURkfNj6nUQ,~X(*|_rzJ)ஷ/?]¿buQ7V.N^G8M .yu:)`bQyAR -** MYR q[U.'/`3& 3nUf:((%`rA 錞B&FY;ג.O!$->+-:2I6$VC*%-D'` :_b`AxIq d'\X<D&Ʌ%JCgDVV+`Nk` H\`-l1J\`hnZ uJ ,f* ,צ$.\@)K\`)qbG ,X`$.]RwJ޵9El%.;NV'+qZad$.@NaXLJJ5I9 xDL.NV5MfnH\ƙ q2 wA!^` V+q -  ʭdX1ӷKf>b:/7˟=]R4}ޖOL.-o{KQvӕ_ k~N3˧^uǼB?Or[!^Z>RO] kkZZvǚ\}sݻ5h&lG4b\Ŝ(fEZ>Gh{;6-6.Jn9cx̋}plht#T7uu -M%C/Oy4pb~ZXbhYEň#hDN}+y.!ͫC/44$.wsZiֶ-Ӣ ,r -o=)_Wߟ("͈?]m#jAX^ks걒fc_r]Zx1"˧o'n[:m.m꘽Ir[te[Z5e;vޖ?nyD -ѱ Y(-6eJҧq)w_͒V#N)Y\؏~(6.6dJMۥ>s.{3uoc-Wly|wq]f_v:Hl80Fwv1wx,iY[JlXٵY# ֆ1kw0BW]pf2[is0Fl-qvt77~xbϞFm~&h=ź몮y\C+XOt$m'ٛݔǐB[W` e*niAv^'prwrT"g՝>L٣%PD嘿xh/k{D-gnl}:y -煸;cּ]2q!D<ƩϬ7s"O)EA\"`b۽ }YL&Jh!Bt%5oQ'<Ȧ@C|6bv͸z&8| 7)j^]&v݋9l{}vkAffXصe%13t!P8DųpnkdGgΪ{7'ץFnHG%\|`ðtv|;/53ZAy[lo˗v7>ydA]7;C 6v闳縩{ /lk[p/2zD2;YB.Ry4b8͍cmrY_ -Q#dC=T5 C>o<2 cǀt6בƏA|)|UellAe "~{7~ -WhDZ#QrF4JsA[w wh6{2'fcNӤ3'={g7+M6K^40߱ziǻ1\.>XL`հoCYwYRzu-zר&̨ܤlZ? E~j0U .tv-SJ=kt{ :`cDu-'h[_pc6Sۈ/> -} -+вr8.f*|/5H[TUf塱<]it _:)!=nK<21y<"Fknkbƕ\}Jmz* ݷr84|z\+q\*͍b~tQm1a7 ŝFN]>ȤvR9c'wyq[ƭ+1b U؆ hui}ECǍa|zvՉԍAur>dbӠke|n {q#Z \}J"qEI3,#.xdnL$w+,.XA\fyUVZ 44~~_LuQ{>sikIR[.9<XoP+˲g[ӇF-cIS϶$RWeJD2UeXm -K$z)KW=IKEK@9֩ŒII]Oil[[]g+k놄oR^3v> -endobj -619 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 483.873057 101.433071 465.123057 ] -/BS << -/W 0 ->> -/Dest (cb136-1) ->> -endobj -620 0 obj -<< -/Filter /FlateDecode -/Length 4386 ->> -stream -x]MܸG  bd,`$ 񬽋`C~"UMZjcz0VIbjϷ%2*ߞޝ^ߐbPFSTmb6 u<ߜsǜ9XϿ.*r*T*m^h}T(ϧ07C8Cjn`36x|F B,{#b41VW,?wYClY|ghm@ma'@~ĿyPG+.1vx0Y~_^?|so R~qLfԅI4҄L5K,#>gv7vX=>oICzhWR~?#':G a۲VނhN|ƏU}tv{--P嶿{.ϵ B! .-k\,i˜NjGeuPY Zr}_ORWnO~*bkdZP==:os8Mk5ëy7D>wHR, 9eY-zq|o>2>|c%,!0kݖpGލ{Z)qϺȈ?ViO&"79"m\rrsF8#jRP"ZCܶfns4~cAbWna:mPG(rCś5Xy<СWt^ecKoCH%^\Bߎ}C}{hg^7A?ޘh( ďv/|Ms]]@Íy?)|JwYi+y|:٘pػ8nWSZzt?uz_S?Cg3~nWrSWc8S }uOQ*P#]bos8Tx{W|Ub{ -"гꃯGk|aK;vCns4DƕUhnlz<w5AW٫;ܺ^#1npơwW=NVx_w79>oXQּ^2ځ{/$\ -Ÿkܞsro ][Eܘp\Y~ȑ1߶يmyYEYaIq tc}w ٣ Lo0ns4T(Gdq~ܘp͎w,C?hL;޾٘pH]D -ZkQzBߜ1<]}άos4tg??S99F߹1ᐺ~y@͖wm>yΕoC;G=;aq<#z4|Mbm4x&YApzŹp # Uu Gr,gx7}}rf.|Eup.1M }C?&]B"~ߔ*T\mI.CY硜T~N%9!^W̞ Ϟ)ߝp.!)c@ʕrSҎLm:3T9/~Rr0a9rD1ӿdR Y\N Ճ8z1NXĄFqu+LMdܨryǏ|h}}l$5βX"g0sqyz(.&ƫL T SSUq \&j) ΫΰimdyKxm]/}ZT]1r5vD'AEY.TD-]IL7[KŖ*MYsɔ .dCXg}DZJ Զ։΄' 14?|R+Bm'LҲ ]yS U&-3|0 UΌו塱I5`(NiYufy}t[VcWRVeLs5T#kikBa~WrFv7(?]';}{Y0 ;C'.M9ea`^\M&mnƄa I< ǩI#0YmƇL9ϖ{^?yC=@2[6n󑬜~6iUغ Zb?M6[z"45M˅~C& 8V3ȼoLՇm\9zZ 8LMCtҡ%2Kvqi{"m'Kp/ۘvީZY=לkL]]p2i <)UM@2]eXm -cZ-'b)&/=oVJ-yK9@9NO͗L,MJSJWe{h{fA!aLR=}璧DH1i:r5;!TX<'(I;99Lx"+XQOirGDszrʍ!!H.c*<ۭS*Gmp唻% -endstream -endobj -621 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 620 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -622 0 obj -<< -/Filter /FlateDecode -/Length 4825 ->> -stream -x]K丑ȳ~ x;@c}0|10ރD2Dv6܅LE~(*|_rzJ)ஷ.?_¿RbuQ?7V.N^'"8M ח .yuۺ)`bQyR -,+ CYbA q[V.'/ 3& 1nYbĂ:((% r B&FY;/O!$,>+-'D^O<䓵Ji=yyQ0R@|y[e$,?8mLIfUVK<YNA_B A̠pIqd'\P<&Ʌ%JgVAVC+ Nk -HX`-d1JX`"a:xX.TX MIX`p,aZ`%,@]냑vKA ܵN+ pZy,aq:Y pj%,p]L##a:ɤ$,p]wMDyq8+#agp l r:Y ރghl2HK$,]9 tA yy-<@e%,]g?! "?VI1P^*n(`/U H2qaLmE>60>-w) 3Cv)6/_G/UvFPJ;W&ٷmEk =T6G/+Y!* X Z.x{J` E.ukeYxLIy{Y)&! -yƄ~í, -{ mLdbPDvL&p)3+,P,bܪo]>}d#_t>_Roy[>I~g.,M ]_xP睶R~-^ƢZFO/SOk9|BMnLo|}wNWVK!6%*_⧿{|=SWc5a5<1~?YhWf]'2wt F-.`nmN) Qu*Kw˓ur? u׭,5YC-xv==\Гyf 4 7牟l9Kr9f9n֝nku͹\-pF/ѻ l^ Zŋ8&)_ƈ {XiXyy睜s-E+dt9r#y:_hZ=_a",0781"]oZf펷bGd\Ŵ=o>wV3 ;m#^Γu;s'{vhvr1’MX{&9%Oe].ٽdK&ac)M,ց0FYƳq.#:zC_6'g6J&0߱x.[(}z{K<Tg)5'%{zWSKUKS5vKm󝍞(qLuۢ%p}-=.cX,Cm'X:E lQ˸1qAϵr>>3<{a Yh̖CA|ee, `uF=x -Mo}q!ZwYk f51;KAGC_>c,T~rK6pgf_!ft <ʗ;\̯JY6悢][v?K{ZM}D#QgG>dm8`ΙvcUʳUWr77Uib[iGo6YLDَ{,)A9NqƊ1oO\I͛Oyա7L}9QS^L q]%v;Kzepv<9/v͓BBnm\!IuST$2ßh<|:jf'lyRNmBH'y;d0Cx>3k5.D -33*{I6 '`3=k6tZfPA[s:OrzCVS ;31<6c[ҝm(Q!t5ΎkmՅQܡ˞$ۥ6cyZ H|PkI -Z%1-OQ!=WGs'<b%zd;[T PK2ưrv|;ϣqhokkŃ8YIm)r <Y׬m{ƒcm# M#Yr>ѱuS1>sbop Cg=Km}5O qO=W<5co2 st}{+1x{tLO|#㠯zf#ӎW\ј0ad?vγye>/_6 e<%uڭﶂ-xsYNW5ycQRxnLJGPmGk`!2^ޱ̓ w<{=8RegcIUr\ n;"~ɷ7ǧ{LUR:3O>0sַw1ƓuΛxB;yyqCvCV }tVmyr/[3fw?2g}}٩7EyOoK^'wq}U/YУIzMWʑ?OL{i6}ɭ#0v4/e>;Ԏ,Gꑏǿ))G6L7w-+#j>ϴK1:)&;]fBם_DPr-[t([_wjJ-W*Yz`1-X\Eg79gUԋN~;@vvC&UEPSKZ?k?`K7(P}_ѻלlyܱ@D͠dB.WB47x`xbD%*]'W^ͦЉMt:_˚yD]Э/"\5,*7%A\@]w6`gVw\TɵrHXni7KV*j]ݦxvc#6G_d:l!.1nC~(+ljIuԘ05+HP|Ѯ_Nhn6ZI8I^K|K'%'mVT2FG cM a%'*d\eEr6Ujݷv;94|,镭M.JF2~tQ- P/\gkCkdRĽ]z)aXo,f@3/}+/8nTC ӰuE摌^E:I_Qm0q ;Y^Wohq׮WWkIT7.'CF6uL3x/M󥭃S*.pp:|eM⊊3".xd.JLrHIS=),.XA\J+`E[~vwWBzz}CDmި/Fx2Ֆ˰l1ǖ#uv ,{%9}j­.2jՖw*mi  .@SZUTj)#Nb):\Ӟ[)sMYjF-ٖyαN-L-ڍzI[i۾ݺml zfz5)*{ܙ ;RSvGt/Fv:ZcR)`?]b%9?19kUd^jYCzLP9*§YMviHRқD?Ўj{ -endstream -endobj -623 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 622 0 R -/Resources 4 0 R -/Annots [ 624 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -624 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 390.123057 101.433071 371.373057 ] -/BS << -/W 0 ->> -/Dest (cb139-1) ->> -endobj -625 0 obj -<< -/Filter /FlateDecode -/Length 4538 ->> -stream -x]MܸG  bd,`$ {E0!?j*QgƖx0VIbjϷEC)x:?|8}-UőjB蹢DX[@ka!+q"qݒJZ % 3k' ,(PJXpwJ\`AA ֵ ,hRX%$. )` ,qq:Z k -xH\VC/q25Q5C k2xא(Gxdw`%.x-wu'iՠc8h>QPBE-$qb8.3J\0 xW[ԒMR8.'q0h8`|tE]TQ- 0 -*ID]$-qxPC%.] IUZ d^GR^tpDp$. -uI\zH6E - -p$.G0$ [El(qlHϧ`=oHYp -$4֣0 -iޓ'l-NAl$8'*b:7fyF&Gm=d2;r+- @@%3%&dwz?#`QʹKt-~$]nk7J&Ke)I]ɧvkg(|@9=OkSXSM<|mД2~ߨ9vm^/8z3N(e߾,OK+]5Bɐbx_Vf_ꩅ☾)B-m,Q|dB#3рUµ :7F\˙$^45hkmDEEvAZZQGv}?r|z~Nw-@pY6iogtC[ Űfo;6ȫ= 4/TbT4y2t}yj'ƃ׶oZVw莍me[Iaz)/Px.S/22/; f|ΙKo<7:{ot%gDySͽ_ A-gmuU<& -5u 20oq1Qؾv'9iFҚoXya'"㫀 t7[Q(m-|qы}eisgȱؤOhgMjoE3{W5qu? pIy y;CEv#/PהBsm[W DaJ޺yg!3ymwD~37L~UZ(Dan?In~ٙhe/x{64G=/l/Ј2^^3Kjpe _+i쫽x{@gҳcl38g핵ʎ=},ػؙpyN.hgZV#e_Ht9w|CFt+2[DdiPw'ʓ߻lte9293ѐvֽ|ggwwo=w,cK5=Gޫlxrmiŋ[c?dgás?dۧX~fl|@lw9 -Ov/zMs]/@gyx;-Lq\o:4g~j>7vfͮ q妬pŭՑAnΣUoUocw9*wjتĽc]oPpjm -߂#۵>okv*x3MDޱ3 -ߍmWog.&Hj1;ڝWZXsϭ5+>nWڮx{Eؓod+rw9>Qּڍ2^K.}/5nnBfĽos4duˏ"<`w|ega찤bfbn]}(`s8T}'dqw|zgá {%;z+R\>(:Ivи>wq?-3aȇxH)se2^ Wm]^D~U:W8D2LB?n.s!76uKիi:|xKdiw,k<KsN>~QpVM3xNq&{46eʒ.M獜kDb)T]+fSc8DCLC(\S>=1`:Y8}T,%a=sÐڔ jj֕ƕ]ɖO!U\ˍ!rzW8WS/6C8H<\qWbB*vYlأm,ӬKZXs^>p[JEi>Ujר*̨T BI~JфƬzj0 QMJ:ApMRsTj~6eXG4#YQ|\}n*2ܘ!VǓ Bj7srz\hYUՌYE.5,=P<MRjIU$.uHMaN˪KP1KG%Ϥ[S[HY1yHżLR [e/‡q`VMfQuoƄa Y<(.mǹI#8Lou>ۖ{^yC9L2UTn]HOB|2znÄb紮09ԕAur됉MіՌ"|hj:2Omy\ppqyH>"qC:dXF\Bqnfff@Ԫo -./yE, \`/xM軻ד}2ٗګKei%>(-5M_d -endstream -endobj -626 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 625 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -627 0 obj -<< -/Filter /FlateDecode -/Length 4531 ->> -stream -x]Kϯ(ÇI#b@HFH9+6_]ӳZ+#Zvd?Vg8c -ΗO?¿\bq7V&# lBr& .Ovײ>)%o;UdCPNP%ʹ)㼠zBST02UA):I3Ș("̰ݪ0A: (%`"Fi7y8K:'I.@tN>vZҥ{#Ғ-dctXo-&+l1Nt]Q啖tN.E"QS1ĭ(7htZOش3 -䃠3+DlqVIga Gҁ' 1 -jI`1DlK `Q&qa˓>I\X 'F+jI\8LX&]Q&bwAKF“`Q&IK\2P }GL8w~?|-/_}u_Ev5ׁ"z튮]sJ[/6kvZ/{6 'sWVu<Ś/cu4*E-(߫$ŋkĆ\<:oĜX2_eD:H_Fyu'I\x0agoxJ&Ƌl闛W=̓u'i| _`-fGAWHMdSyá`y%zvh(]ŘK6kګc}ISνk_p?XM}_d}!~+i}Y o.z#/e~3} KNS˝*m+t]Pgr]-nm:C }C=,Ole¦&,Ple{>>~m[H~ێ*}ce#36>~+2> mg~]Eɕ&v_s3.Bicoxeވܖ6]!Xl2+y3(Zw[k0K>^{y:TyKK9=+>xXaQn(Kr١9PC۵unonoo]SWk՞g{jWiaڈ!_NtR9F \a [mh2~1BN߫)sEfՍOa90[@.rxjovL#<YgxO@>Wy9S4qfԥa4vN]Dy1Y1Lo "(m 2%>eu<ۯaϤƘ*ͷ )pge\C[q~B[m65l)gpol4[$h o C0YŌŘ⑦\ zu=<&Άfl9mhxLV#Y5~=1uJ7]gPΖ߷/șkrekyuTԭlp#qŏ#ξn`-<fΛē\w<R>?rBGͧYBMG>R<R}RU+Hݱ00]caSm|:[ݽ]>`m9A)8s|]t:25,,rz50s֫C}9m< ,>mZlΛ -l>3K{Jml ߗżfiH|ԫ̓|%/gkg3>l'|zq҆W?{x> 5|%]NggPZrNkᢔ)'hb'iLiԋ.~:$bE=ݫ 6Li]y*/#@NNp}WYoj!O;o,Q뭘{&]|.{lހk e{MjP bCx6.lײ& ù'p[>R> 6UkTԤlBm$?Wi`60j|,HʥZN]NbҚk#ZثnJ2<&EQ\InkܘrC\\(CMUKX]Ye|"!?SkRfBS*گMxn6I7!B/;K0;KG%gmee?Ot9F50[q%Lj}Uئ 44~˺35{-p]#`ϗv*\e:ۗ$h_ҡ%3T(.nLxzơ|b#vevlr/"x16LziZ#^LuQ{>16“6_e[sl~V'oPks϶ OZb Z)ƛR-nZF*k-j/ժ[rb.aG9э7eݺhɶȍpwldd~ݤK*ޛyuC|LU6%ϙ;sNTXIkl1UD8l]gdKRO;a8&V'E&'WKJ}:ͩPʠ7eT!rM{A' -endstream -endobj -628 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 627 0 R -/Resources 4 0 R -/Annots [ 629 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -629 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 277.623057 101.433071 258.873057 ] -/BS << -/W 0 ->> -/Dest (cb142-1) ->> -endobj -630 0 obj -<< -/Filter /FlateDecode -/Length 4620 ->> -stream -x]]q}_C" ~pgFp9Td*Iwf碧[U$U"O)JTWVSzE$M)G|*ip*?g "$^_wH^_yUVןb1TQ9'B3*.1%N3\ڮUfVȨ"06(V% -fRv(-%!Zr£=Jtbu:43F`S. ｋt8etŚ8-`p[4j'1[`RqdKZV1ĵNK'\4Fr:6 CB#4l%V[b΄ުs6(N`:؂@{"(=Hd^8@ lҖ#FtL†`8 SxHV [[,z.-&Y -Hq1E[qZ2) J9.0 \)9.0`\rqp'8.0`]v5VI ,xdu( 5J ,xHs\VX:Fq(-\ }p\`8 Nj ,xW[9.PGxp`9.N PK8.p]> *&q愈cuIg-jY( Ge8.p]g/Q5 <5*$q\87$꒐)F x9.2IX]d,$P ZB$C H(,E2)r\4l1Zs\4lAq"ovx[v|`a "E d"&k9.cD<3c-,:hF_t O|4SV)E|n!V|JLB;Yɓ@[6/,,?N7 ^|:='`,1|fyG%GiLҙ9ĕ. :[q|K v?_~o?G')];^pb=β>O"FRKY8V~/5Epwx\6^۾cYҾ_Y1iT֚Ju֫~t4 缺k|i0el6}YC7םZi!g#yyS5pڷ߄EM~ZWyE{[Ma?T?U-˜0ܝ?KN6}GOy0 C6thԣG"-J[ꟗ|RkyEQyYFzSގjY3VfS{ZϒHn9gBq9Rîzen0j?Mnm3LKH,ۨʎISUKϽ.uY^}vߪ@" `&q8tH<K+\[#Gzc&V+3)}i+/t%_5CdZq.|Ɠ/_ŋdbQV|"G=x& .s:DģݼH=꽶F(h/<[bo=VS #ĞJ$7D:tHݏWG6yO)mKiߵ,た΍G!s 7 P9l4mFP1*u|qs:dĚ9r@CF4AGAJ[,9<"s:ğ_k%ܡ>r}yNRu/v͜gcf2 5YZ̼bHʧ]tnd,̃yΆ6{3>s̨'{_zqBI,EYQ~| -EFv=P.}n![;>u:ɽ{DMvVVݑs:Ǫ\~0^#<фvġE#p,Y2vo2m]Ƈ ->̯Zwt|07VG<wWoŵϬzkk{ 5x6|o)s 9b1OYGemr` sh@h|}yNЃgqi4n${ˮt &<oX"C}^\V*qjӥ/ˑw 92{+Zs O5u^ z */k:g47Z-=r07ӧ\Cs8BWmgcqZEr ϲPI>`3!v=g#]+fkϊk1e<|{Toauա֤>KD!: w;7n e*&Zܺ;21h_~YֶqshJ[:=4`ӡ j|0#s -}fгj4z?@mn񮂗7j-M -lH"tk$kbm=*HV7a5V"_@sOxദҼe)ԮUfQJ]IYvbD #N-IXdkT1ۅM7jK*|3AZlY٤HS~.>@ik nJxؕ5@ - )lxikY[) -WyVHQ;IU$*u,WʆT -bƟLL5uTT$Uc)VuU)OJ*]Btd^ZnʝTj]K0_ɱ^IXɈRhFN短qvers8n/\eײܺSOwwnCob[ZWPքm.2Z*tXWjeH͸᭫ȼmþrq8p@/LsWR$rҡd-䄩Y03V}Ҧ0\䀄4mn]dU$ =[EO0F?ݽɾ,^TZ/,K+R3a9Jm5T2䴮B 8%ز =-It,Zb(69[#[KMgZӎJDG[ůrǫђpdKYc<]4E>]x+ -2-[|;lɲ -endstream -endobj -631 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 630 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -632 0 obj -<< -/Filter /FlateDecode -/Length 4489 ->> -stream -x][ ~ׯsl¹E -Eh}p Nqv粻J>qe'>%gf9#9Fc -Ηw'5/]dxw֊tѝ1!$g??o|RFoEv1VKi+B0 ,L1%1\ CkVX+B KA5+A 4I, K+ȡR"("kvҽ3z1$x:gi%^.J<,.)-dqHI[T3cI&!5Gkf7c?x No;eO#Aȭ $,C1}p`fb !=}X8m~1荺^@  E11|s"d\_hY֦MW7yqYQ͡duH8e'J]]^P`G & -Eƿ}JMRɒF1髿_!~Avt穝 uy qqnzF+/SvY2l~Aw˂$ Ox`0m$㺹޴ׯNx=7\~f(qڵc]>> Li,2]ˁ\Lq1o1W:)zf}t&ʜM,3IT+E|K (.[4X~V=LE!(u^BK^kY@Oq KfjvRvz}sͦمW0mEJ&VXJGjוm\,p3pq("MzܰJwVpVv.Iݭ>oC;Kw KJd\_c}Rd -ȅgWrO^8[w{MY\46M|[.xս -x`+9X"8k}*ʞ'5/M#xY%>uVYGj|]N}J's֗8}،:T+2W;=\auä2$3!tԼ=E]F~2!>Y>fnN?i͛IE&7Etsvq'5 -W{ӚqXV`v_n,$COI&{_Tl{NokX|ۘF~B3yvu>jlaՂC~gj(.vza\:N7=H+MƧ=\r栺< -&J+[[.b#\[mϝl&m/l4z^Wz'\Yeێ*Nq_UvǿbZ{Eo| is5s<箓)^0etUDCt.(tY]Z5. G-nbCKLQa\+)CߒJvR-mw`|09ow41w`d_|#0<6gz?Ě>EmN]{-K29`À<l4R>T6񍋛fou55W&ث<o?q𾶚~@A|f^bj>/ʳ6I>\e2[O|B= dr饪c[7v!-[0z)#)tIF67X k2^ z")qӕpFTm@۶[ǫdmUGtknȆ v ++m7n%GQC,koP*'TMϨmW&웕p[l/9ђ̦M٨:b F3xkE|9q/N9 o{xa~p>m^)qܨbG2x̿Rm:YkqܘuW KK]TWnOtMT5vq;B5еi{erGpOl nH\q%uE?(.&LL6&U,?KEFm> -endobj -634 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 183.873057 101.433071 165.123057 ] -/BS << -/W 0 ->> -/Dest (cb145-1) ->> -endobj -635 0 obj -<< -/Filter /FlateDecode -/Length 4598 ->> -stream -x]]ܸ}_Cl$F=N`9Td*I׶/ݪ"yxX,QJ}_JĘO/R'oJ8?UISGw) L!9C_\̣Zr׿UֈCQ%29vQy%p)q*v -0æ8̰ZGFaA* T0C%Ci)Y 9VǤ Щ91tIx]t$s)k%-I:/p8.buqkL [ [2p\@$XO0Z 󘏡V9"5ЩqAV`(V`.%":= x% `tr\lAWC9SN6tSエa A ezqFh%Q՜<όDEv9.@7LL` hOl; 0dV[Ĩt3r\#lRs\lf I$n2q _f &xLMf Yࢰ:)1&؉yآ y监o£gC17.ft]x` ϖK xe3F $aleC܋*1 s$6h31`XRI6l 'CCȄna9GKf6c1^O"eOAR[W:o7 $0<و -8ݲrtzSN(Nru KL0z1IgvWJHwuʸb>8aO_??F>]?tWߩp ^>WSKQ7CiMҙq\~j쏰1οk13_GI2mUdWf9o%o-),qMv75{CU3KOzs\>-/C'GkۅeYWڳjzaQ\ [iÎd /=m~Yj)|6di*Ǩ/Rsd9*=/Q* E<Z6>7cyֲ+5y#dW}t#gzҌ Gii4o典kUvo pʎK 4םZ{ũnޘ͑oPt0pElKWycn=A齲񬛣uPϑmxYOIڱ`ӡiԣG"-JǶ?-˙fR|Zѳj>љQ!G1,kݖ5Ս"u,z8GrSirkΟUgZoExamWvl͂-=9S $R/q]}$9́cGQy+Jvk(缍!s=@oˣQOEXse=It't,yvqZ{tښwd:䭢3#J$+n:lHҦ#Ak[ݙ;#>ݹQ$&pyN_E[}#ޘ}(@y/[\PM19 7P|`ӡtlg{w{\[?y`Jjծ~Nǵ83?3(V|pzCOʧwjf2"GG'Fߐ5{bOQiwرi8_W<3?.s0PRV0Y'(["'OͬV:HdNWnݚN[gCA=>s:8 -oA&g9♏+V`|.2zCrSuڹ3G/֡O # -$6YYytGr0rUK:b3{M;`׈H,rcyΆY2vͯ2m]ƇoQY9"{#a;L[~35ڞ:iʝ\2ʚO2ߙϗ69~5|nbT#5狟vR.qGtF0m5J4*[]7rN\SʼE_ޞY/9<5OwQ&~S-#pY8,J*hH}JㄜZxޟSr59+6VDf~bF^P8?|5b3@KӶ[C2Z(XbժMXMUH:.8/4zY*ebTRWRhƬzjyﰻ0 ٚ.tvaͥR-k*5LiP7V<#h6#ҔK-PZF.bJrqIWHWG[Q64i~j ]K;U*3PB*֎Ir߬e%QcP6TTLL5uTT$Uc)VuU)OJ*]Btd^Znʝ/Tj^K0_i`8C?4uk'#fHL[+;ɸveq:7*J=/u|^e+8ee ]u!#Y<EX jKhUli]ACǵ&|m[vوTAURkuHĺBW+Cjo]-VGm)Ә ] -rpδ!JQNچth&q@ !9aj-̀'U)L>9 nD>4Mg0K.*HЂ'M {^nd_z@Vj*x9Jm5T2䴮\ 8%ز =-I@Q2YdPlsR-GB)mZ_zK:@9-e%##4wږvy2^efol*SL߹"\7EGTlob*m);{p[bI> -endobj -637 0 obj -<< -/Filter /FlateDecode -/Length 4603 ->> -stream -x]Kϯs(@I#b@HFHk#XsGvm-V3]EŪ=}VBHz1OOjN_i1(oY+ -Gw!lBr& -.y?wϼ>!%o;>!J`)msCy)$ dh -Rt b1Q`Ea)hf%a&1trA`i9QJAEdnPxF>&D^O#| KEG%%,N)Y rRT2XõȀE5=gWr~Gy8 މ;7?[?ek>f]#=S}HO`+9g?/a^pz0տzE,+x-K>gWr_b1Dpny4tWOqY;>hF{Pq e :l<޸0GnmY^|>s嬞ߊw`cgWJ4dwaw[F%ܻ̆ϝh]zǞ>gW>bږ5ŗ;X3Oa=ԄN68u:y8<{ndM[\gꚴQ\Pj:vN ɇeyme._/y_`p2Ǎ,օu>mU`cj ϻ9Om+/m)LcQSmfCj\:5#[̨j׼3kC6 -3 &-W*`!&O`Լ}֔L=sT\)lvYyqpBjOVƜg]v)mټ B*6vs0ϓvյ_-Yy]]95M٪]=ḋ>nsh2o<\yĹmdhx8F=sV:5PZgQz~]|Nh_!9,[XG*E7Ws؃}:Wc!:ז?z`Y -!,a#/n8PVĞtoklEuOXN~K+IK])yO'[N'fޡ|V:Lϫ\O"!۷S۽@p7NlHró^&=c#bqRsÚ1˹֬V)N1ĸyL(ո=-5~o%nZrVyqߔX2'jsW˥ú?|OsFSא,t([7zoGeiDz?,ES#ڎ_ʡ -SR(Ar&NoUt++lqIMZg-K6=^ՠ'rb87Q27bx>`xbD&*vN6T :߉Mt:͖5-rm,Riԡvj4˄Jj˶ I ]N U&,fUˇX ZT Il7J*jM=o$l.l)ob>l};'獊*21+C+X\5=NlFKS!wpJG:GpL*ޯMo6\IꐤMe!4Q 3Mc3*ST cN9CXOJNTUܮ]3隫:n53wd߰C[qoqW6ZzN6E~3F:s!WomTv'"9cGz:+Dc7i:#H`,$/6h~'ۺj -zwՁ Aur:ddLh4v["kxir)OROlg6$r%:Kv% ߤ>O|)l`iDG=+̂5A -l4i#}{}O"ڠQ9M,ST[.{yXmINwZ(mjMf7hڈnU-eQRh9E~54%:*~6[#^˖lK7gz˖KFyFV4wg6 ͭZޅg!?ewDԤ5|QC(VȶKn%'NXUAܕEx#]gݒtsj;Ts> -endobj -639 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 108.873057 101.433071 90.123057 ] -/BS << -/W 0 ->> -/Dest (cb148-1) ->> -endobj -640 0 obj -<< -/Filter /FlateDecode -/Length 4595 ->> -stream -x]ˮܸWzQ|YH ddq}m "CI|*I-OƍmUQ"U}p/.bpFߘbq0_U -rzs} .:\#j*i*҃ èTBjFe2QY9CT08RV9AN3H)Ϩ<^PN2ǨR ` ҊI3X4tJXN:#i$ xNG!9-F N[H{,lV V[w9آ:ytyV[=X]Nx:%`ւI9`S:(tuN+L`uh8-OgF[ -9-J9bu1E8QFy@AG=3wLRqo0qA -@ՅA9.0]В <չ@? 8.]awauE{q0l1 gu -LB9xW8.8mr\`](q + !8g9.A@dž' 0,V[p)آ)xC.l|@"`" ЪΪ;5Iqs4`* <= !K $q\lPSF]1^]2^V]3 #0U(` 8aZ},0gzO2`Xsdz#ٴ>O0^7JYH8cj1 T@wx-2vKX ( ٢QRrY-0QHu2mX6B;300z݋?} \zw¼KM.0L]Ztl.4?E]avX|3%tf/il9 A\DhUY>&)!W1qvVN)&c"AʌˏU7VBfd>Ʈ/=ǪtчR~vî˥:dЍs$ouX甐Ami3p\c注ψfPњ51sTl ڝyNmز '0^oS.#sETN7_C%[cjw,$2Sw)=:%tFPʁ.:ulX:Dfǹkf{x *[uRVM󼭐e溺po._,܏RFapȠڗtH}~ r\AMBFЪ9t="oڶ 1Ȓ|Y FߎԾpӾ<;rdįh17 5FZls>kԞ[Uc'>6Xt9lH-JZDIZ߫d93*ʭQnYFzxSY #n!GZ=bHkY kkHWzڗtH=Xk8E۸&ގ*~^Q+t6zB(weV\ҢTuHނ]$v9SkGYyKҨiVVP]A^{e]uT:VGyTo տgҁ򛢛FtN xŗ쎈:}w:~S A=ȽyΆB[whU~W;zcjfk}3pZy_{@56IVj-wfs:\VT=/G>?y;;_O[W~cOV^*sؾuWF Edg!}O;Zv# ĩ-s:=^aWC{Wrk 㙼= TVׯ{W;g崝( 7d4\ɏu;:>i8W>*ev9J}ߘZ սVwr+'Oͬtbɜzu:)|XO9zqj^5"_Mڀ~$Hv9b}ZwY8y y;CCًAv/3O/^o+{h~or>aՕ.vB;ɨҠc߄kܑ M2u[^7r/~ȩEܞ)n1mX?" #LQU:(K71:Q8,)a=Uڔ brEOe&eHFbFV gq{z>cN[ -,RJhBQUWĊ=2Ua6n:YuJ\՝{ խRQu2]ԤC(#z0oE*ЙY_Z7f$BJLj/l4{Td )gdcR7SpV Z.1M -ajb/ -^4>{2LF -y29Tf/:ĵ$WV%˘KzS[H&.$"IeXeF]G -K퓹d+b;M{ -&[6sS-ve)ۛ˭0F8BߧJX<ە*a1 PąFFq֮gd܌x2NsJjw=/y/Ҽ_q%2[̭ q==`}8 yTBE%IhR_S. -23ZhJVbZV̎MCNQ -.S*G1iҡ%UeA]( -Clafd]Inh?]c]AFC]tTٺ$ϢJXu$J軇GlM# J3gS-'x09zq( B,]=24kAԗlsSWJI4M. IKt&;gK2g[eH[ԽԽbWiciޒى2:wRIl]7-N: *♊ͬRv..U#җ0QtZkBq;TGZ.9z$5;Z8 mE8VTE={ق`O` -ͭX,E|bh¸y>n-UܘH>,OLW~@ -endstream -endobj -641 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 640 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -642 0 obj -<< -/Filter /FlateDecode -/Length 4399 ->> -stream -x]Ms(~ 8Er0rmfsϣ$%R̮5[U,H>*Ւ>+}_$ŘIu)KLzwxw֊Btѝ?d ]H~:!/tNRFﳊlb VP9ׅ`T^whbJ -n@7(E'UKU&hTpC'VCDQD::Nd `$t޻(si"% $/[%J_ z' _(JKd;"KЩRg\VI:;lZQAAK8'ΆjjI1D|K `<|QKe^8Q2$HQbSG!XLr$JCgDVG^b a:bI\` |A /lK@tK*i ,X.TX0$.\@)I\`)qb ,X:o$.]KK\`RXcguxj$. .^`31* k" kB 栕ơ R5dJQb689/ X 3VT%8Nœ[u:&/qu=.[rO8.wAQp|j$.p]m%xW$.p] NH$.@|tE]TQ- ;$.td)x.{wVUGkô4N0*t]Bwsؔ,0Q8! 6H] -K\)AA@YP Xwɦ(qA0#qA0)}/%.u1I\z *b]@Bk.bK\r$q܀N!L hK: _dK\L:%.  UW Bc-t:3J\w9U+M0/ 0>y$.M,sD|$.f Fb qARI.ơSJ₤#֛$.(qA -M,y qA"␢:) &IybI\(q 7ы[17]u $L8zW ^ʘWQ1P^*n(p/U 7Me*Z -|0>-*8r#!kV̮~?/Mȯ0 Lp;dͷor`$=d'BjNj閝Dwm=}BNX%Uu&/֣M& RѤޞыa2/&o?|Nqxwn|e`g6:5W1X؏rz{۱^|)zQ}h&>vhٲw3K/ou~ǷS6$FS$>SkD:3vYX¤ q)S<8~^*r0}m9羔s0 4ҭ*3^/WʖC/ﾏ@,N+kOV ]'|,3MZ3; CP^ANR]k٪}}# Զ줢ɩu9 -*V)ZnQ9[7#\yzf -:[2HXx-t9:83g%ɭvf>Yq|5!,Q\K]v{׳þr0ևư,ϳ~ēfY elb3gANK_"J-VȬl{kڨqPi6p=']C݂(칚7YU|nC|6[q]:yry=e: ^7.#k1v_aq3٬~-8m{퓲;0(҃~=wpC.b;+. 4vjyތ% >ָ?+ɳŌJ;gs8d^0?E,?ΫȀEZnNa^?P6XR t=v VԶ|\*Ѯ#Ǿ{~\A+3yFy>/TU`JM9R72_ȍL>LJ,{N!6=٣wdL[A}%pD+ ^t}HO,w9@_pE䝛wGz}w{+>uw5N!u#'}B3޹;mН(h{uĻqD97r_S̮}h{k^h6Z \k2 -r;{is8n\9l0 A׿A^W4 R~?|pApqϓq ZC^z9?K\R_-S[ e]ȳs8/<\ܺDQ. e)uOK}]ن_wu]}iݬ%T~X=i>zlS{T<\+òo AMQ}_ӊe2 -=#>{>oc끣ü14sh#)WfEn坹Ogf߾ޫ9z{7~)mrX_g#_l%3|d:TZN&,w>Cm[-G#shțE6>n72?3˔B-2/h.ȀՌ=[0XJc7o/݀#5'0ۂYn*19ޟo|l';6}RnR7i1Oųo|:#<6o+%]N+ӓ>RT~B%v0A'GS~C))u!u43ifҼu,b[W>WZ]17%&U -É!,^sUGq~Px+!l/*lbmP57]盰λN/eM`yMx9v.}%һFUeN*ud$.'A*U٨囿XD\*$ksuB-i*=\iPIѺ²ڐ戲T:*2ܘrBP5P@ -jxi|gf[gpUB*YNr_YZY]:Y_:*|&ZDʺC*e1늺*Vr%NĮBi"n~:Ur2]}'.uu~A0_>\Iبɘ9RhFONƏmIrԇ9cIΏᙗ>e-Q-L։G SVu0!FMc+ -j755sՈԕAurk}ĦBhz]^fXM á-il~@ -98Mg[H>*q-f^) Slf$?I?\쀥60˫.R`xŤI黧׳}tٗګKkò,֘cLC.枭IN-(f6pTd@Q2UdP|Y閾QPs&R;Q񋲹jdk8Ckj%k.UJ-izmϬ-3U-J̝f!*)Ԥ5 ރC(?,Pd%7\?Y~& GG֪eH -VUylؤ:@j4C-oqMzR1?7'/- tMOM -endstream -endobj -643 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 642 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -644 0 obj -<< -/Filter /FlateDecode -/Length 4804 ->> -stream -x]Ko$I3|I VXi!/Y;<YrIAgx~$pZ nxHALCXA㒄&! LE -& -J0`ȧ U<% -8X Y+WAHk -HX`-d1d%,@[HX`oIi/aBL%aI ȅ)% ,0;%,], aZ獄k)z ,pגVpZy,aq:Z k -pHXY`^dbTpDEp&A+aw$ 5N kx `(Gpp`%,X dHX: kh5阼#OIh\XO8.wQ`j$,p]m%pW$,p] NäHX6iyiR)F pd$,T0I!wޓx"="h$,@\N)$pWḭ*nS`pBl$,'B>'<; Dd@ MQ‚` 5F‚` B LI#s,%,M1IXG>J[T3cA&, Btr^|gyh%ω%bp5duHS UXXXD8b8tmR`k2y\4vtY).tWX%iůcH~'y?xMm}=rHu:_՜eلj_kPeGψǛp뢉 K@(.LUurax̰lX`i.xFz\׌N``fv(zhS֦/j#ě7rL,>8#C1D U>}樍e >YKOS}KfYm֫`YFװ5>`y3ak?V3X7MKC6#k[pEbm{*R>{VqG -p`j}ŽзǨgl6SX[ūSk9+ョ3dg%;SH"[o^i-v?k5J4{)Mpm0Ҫ囇3j>>}ejذKZm㥰Њ1]Z홣)KX5؟/>i>MbϾ}"$u]m˲&V>!+pٜg>֨q~KYCs;? m9)uHOj^wLj޼y+9)QȭR%x(Z4u-??/USh#f@/gfqF}!w _ܶ5ol>~ SvO3ԬbmYGf^l|+2> m\Z8vL:yؙɲ>8^+ی%s̏dC2uqGfr[Uj_ziGW<Σ*6j:XCijz]|?mg:jnW\ʪONyC]qԡ,~#K]0vYSwv#@jDӣc0 -jVM{!Aj0P&5WmE١fb%98sdMtǹn8wGlNyD]^9WqߘܵƎЍC6iUVRٕk{_u\ݐZњnoLfA=y ߻Sx.vVgֶWQV4?=/gg`Z!eEyKxXRe[]KM:wdfIVxZOܰbN[Z -{,cZYc\ezYڑceq3*}]6>E=2Yʴc=V4O{7aeww=DfCw1>UmBAFb5U7.E9Ⱥ͇IP\WUS*Uڡ|5Gx6vD}Y!{_Ԯ Å~=Y\&H%#cL1{6"«B藺ԾVuf~}㏭Ty< >=yDSAƷT&GS:o#j>IfbZ[MJÔ%TدSfѸ:j5~+Z DzKѫI20N<& -D5boƲ^.Y[5ݖ:PGo|'6GakY<".֮/"ߛV5 TjTWK 6Ovߨ4a25~LՐK@]r5f*RWMU]n66 p0+Y5$> -endobj -646 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb151-1) ->> -endobj -647 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 330.479014 101.433071 311.729014 ] -/BS << -/W 0 ->> -/Dest (cb154-1) ->> -endobj -648 0 obj -<< -/Filter /FlateDecode -/Length 4571 ->> -stream -x]Kܸs=H `׻9Z$KTͺўV%C:K|Q/Z%bLӧIB,.&k|;+ip*OO8EJ^+wFt*A%aTΉ+[LS kU6Eǩ`:23 ʬU f,*JK`hF(t>&X]N>XK{"%8-NY+9l&NaF:آc0.I.+:"T.R%d q N)MТPI>0: [tgtX|8x™#ZunFl:XV[Ph[dKMr$6ȱI G:9a} -ӊ##ac`Eeu$qѰ8.0hk8.0`[ p\`@V&qZ< 3%kP.8.0\tkЮs\`*qQp\`Fqi P8+B(9.]wu@@4Xvj'5(#Yo -q;[@N pK8.p]1ml%TLUP%δ[P' xwAp@9.p]eSs:Ir\Pp8.@&tY]2q4腅`V8. ?E8.]w`5С2mΪLR9xWʐ8.mr\Cq 5>ZB$ H(,pE2)r\4l1Zs\4lq<ovx[v|`a "ơイ"ƛr\vǛd$ƛ16Ǜda` Ĵ[pƛ`'NaN}oF f` yK`&Nޅg9.ƛlW<쌁:씁 -윁1;i315@ -촁+N>)*81Lh}s`f#e~O߾E{?fGAB[Wh:o7$08و -8Oe#0'AZa G _AbQ`z[0&NJiV\@%1%V󛏧oo5` }o7|.U9LHkpEaNWp9* ]EbeKQjCFz`&V-JXk+J1P|C^s=b+z;Rd5MFMٯܱ8Cʡmب~2ȽH^!YyuGWWnUs<-Oe~cqNjo4i z'/HN'¬38~iY,?ti-U }ΨwpX!r5]ɖңp-E)>ܗy充H2h(4}KegԽݘնsi0~833YRe}ů-Oʧwnd m;>=odF8>r7J n - 9B_L[g~c'uT!v,{ݏyW"aTr>W|^_?tZHg}FUD9"׻~ruD8s΢8Curk- {5ͭGM{;ޅL^vW<J~=:C>pܙ<*] !EZIǕH׭w 9w|p/Uы;e9JݠXJkcEjW/7s&sGgnCIYi&9ztԭp`áxgzn8C|vݐnE!÷5 "sԙP\F׈ [s8^Uuܯ/L/\{AhBFPO"G8h_\!㊿%Pfⶭx"_no|098ymwD~A3W}~ᮺ~_̪%vϱ߱r0P d08Oɜhe0ۯh]tMxkwn_avN=p_[#z]ox}Ow<=pCbcGSrwƨbXp QQ{v/6zos8d{@_~䙝1{(Uge%0ӕw4&}=*й|>Qt*6*w o}8G9?=)7BqM<0n9T -[7bNGSe>0Ju9\?M31\N 8rď|be -=(iYUV5ԇ4NgW~jW&w%Z>Lg\2fZ^ -5QWS/6C4lKE+#Эd{T>oj:-:EՁT5 ٚ^JY%RZV!F*u%d[=7$mQUOj-v$[å=psjTbJ7SMȦ2!#Nڈ4Rs F't1v%~o* -WyVH3U$*^:+eC KKP1KKEɄϤ[C[HIyHżLRRq5ޚ.|>LdZޮeF0B7}ĥVv>lqN?nN~xyR"+|uj~\rBL{|yЋ6"Ԗ~ºڏkMڶ{ *BʐuV"|J:2Oa_.M9dc{*\el:Ӻ3IW9hҡDM$,[I3E*L΋\7"_It$\`C/hVL軛ד}6ٗګJei%<^jK}9x[ մ i{:9i4..(F4hsG3Eȴt. EVS &?G+2qdK)TI%hBtV*lNx[2rΡݝl!/Զyeޥ=۰%)'4'TȠ H -|Z+-In+fzќ\ai^> -endobj -650 0 obj -<< -/Filter /FlateDecode -/Length 3465 ->> -stream -xM:/`.*~ F6#{rp{87j~t$flG3RWjTnxpٙK?|}YTbq0_7Lp% J&S?gu8:nM)ѻ坨L)٠ -T֑ -CTT\b) -fĞOU fpAS >+ 3SU>9T0ÕykU  &ӣ\|Qu :#21 Nc Y1l :M`KpV4]-ɪ:s"M`GEa +:bu %3) &d"3I3 -%PTl d#xi:p"PY^f7Yr.:؂#l)j 2%>%ųpQb8%0K0K8@A%pH@0f-TXcy؂ `gX@-[4p˶8޲uQc0j, rd•s X@.{X@.5KwX.j:X:r40K& byU? +l50e $ K"7 8 @Hj,@Γ4f<uOӠqDuçq =[q1E">0 zuH]X] Ac8$ ߌp]UW-9k,.5 -AU i,E EcAwm X]H{Tl5 VHV wk:pT4DpW¦ƂDh{1))EXhp4$ ATl XB%k,H -H4 #0!V SX\5CjMNй %6NcR&ck,K `t5[0U4 쑙k:[dk,@ s -5dʌVc"4֒jMV֙YcAh$UXi&H` 0#,6Quk,r3k,x57e4 [i,(6I5Yg -Y7Sm(ͤ0l HQTlATy &a :i[|a%FYofH3DFn dYo&u dt.2ӨXo" ̲ꎁzbe`^DXWH2GuaJgm "&w-wH9EL Fv)vo|?gi4#4};\>E$S`H01uĈTX7H?ٟ~XX_Ov(>aް8rumU>#Dۈ2T .oਲ਼=v8x0a^?yoa~{X _ǚ_2lC'v Zs=8iQ]׻0]K9VZ^S?}S?ͫ,m>S.*OXnqy0kwnurPbyۮ..J6or9zNQwS٥N'OnsoEOǓ\yg&PXmע:w|8f:҂'̴3q~cϔ|>θ/rsV;M۷H9!Wr*ܝw^C -#3 Dzn_oswz%'}D3#}}My\49sl'Z^k= k;u\:w祗)8\ӭ9|f%ff8N盵g{ܝ^5-yzk1 ҽ3<1FP -oso6gwmҙ\LXr桽:&/R!o9<j+~zGb/uƹGMcW(ё\ܩ$_$LOi[S2 ) G$ݥSMwiK#ElNA?y$hXG1Jv])B)ԏ>ԫVB4)u<"DNrָY,tɆL aoDz^ؑThuj{[.l]e}ii-}P$T]oJZ qRD"|akӌla~ܣ0WGVrSͭ6Rʽj=MNu"h&yH0G,ՏKqcm7Dx!aR:tVP]ongKS]Yer7="4gܑู܏Idn6Fyla^v.Rٱ~R t[c eFUxmѮlv.}u6:M[<Lϻ)y -C$'OK3//ʼvޞ{6ZօxdlQ,ڪ6m]r/78km{-A]ӎp3ŖR8ja:!y?4#)C:쇊8p-[)9uPk89fǦlR`Ɔٍ'- {=<ɱ67(m&<]Ja\C{9PkG-S8}t^m.Ɠr-NZEdZj[+j/StcOqTZ'qTIYiF-QKΩ_%[.Yk7)Tekݐ3S۫cαj'B+U_yQjs`ca:ONwIx& a"> -endobj -652 0 obj -<< -/Filter /FlateDecode -/Length 4664 ->> -stream -x]Kϯ|?ÇI#b@AX9+v]푽^fb"eQ9U -F)1{R 6 ywcV ޒ;rJ:6NPR! -hX!y뷪3|AR omTf8۪ -̰xI3L IP ;Z(Q1[D]$+S1y+*%m$]-x%l.'IaN:bsr. Aa ЕElQIW -%{/ -t:YTiIg -uQ褘-Q"`KpJ:[<$x"0Z-ntX-|l-:E06% >K,`sQ>%'р-AXN謑i|1rElqK\,lA -; -8ЭH\^(qL-q ( 8ׁ;%.p ] $q|8FK\!-`GLvx3:I\FV9k y XJ Y⬕ Y؂ADD.DT.K\Bz ^tѪ@ע.Cg)yH\K 茗 ؂"q"-"sIg` l BgDdʌZXKՒkZgf BE 0LS:C q?Xlb#` ^ₜ--79&7ED|ơZb2֛K\qI,qAqM,q[\fx:؂&IEbH,q 7ы[֛I.ft]DQ`VZkoHdegw 47`n 4U 4ȗH2Gq*Fxo8a}[TpH3sF 辯9F2w%ٴ?/^c=ӻNY#li-'8Cĵ ΈLWbniAq-Ux911,X*gĚsjf^XKV+q= (wGKt4zT5#r1 RI(+]` 䠮Let2o]",=M}{uTs#o.s:WIJ&&BbZ=. 4Kq9^iS!2R!긐C(QU.EyC Yц:ȸ߸_ H#39b2^#8r^/ecBN, -N{dnҪ.e yU<+QZs!K3TE`ݫMhuQl7;[# Mt4l=nP =Zw\_e%ϯޟO߿EozwZ'5 ֆ6ԝC'iۿnu~S_m8d#`lse2omQe͗T&S픖,o&y0 9-[G QW+><;gY@dYl<ᵲZ0Lt e%+qx4͟0,oT&Rg$Oo/ی1I WɋT~[Ntt2.ٖvMm޳#kvі?.cL х_Q{PQ3n/jVW't׶;iiޱF2j쮯,*3e֖8|$3l_5-kwO oi彝720zάv24}M//.GKf༱.]Ub]_f[zL2>P}v3'fmf vyU4G,9_XxJb`(IgwǔKC^TdTFWV~h\LW,[7ll0Oٗ5 -c W+,QBU*: [Z,BA ﾺz%b׬kBy%ʬݎI`c!41p249t~O2 -m>?:ʄ"-2B" kTkzr.R_|x9MeEɞU@] n#]^zU)h 2IzD5.կ*>.ۑÔ[jVF^d5Ce&\+?U{Q;ӄEAylU)2a=pKWsGb]swX/zY%NL?a,i_N[Go?~Nfe~{U'1~8DF ]Ofc s'fXk3Fֶ^Q,sKߐX2[/KEMvmwh鰜h<R{|s};myxfz,|zsyi!Ԇb#!lj>%ʻk_ϧVoQ[͞ WFHEَ -i'\A}zs#۫<a`C/|鯠3<\ sJK'.'1\Z=z i.}0v“as\ ^cc g Z(mNxdzl-YR1Ő=xt'+qm3^\s#e% > -endobj -654 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 533.554475 101.433071 514.804475 ] -/BS << -/W 0 ->> -/Dest (cb157-1) ->> -endobj -655 0 obj -<< -/Filter /FlateDecode -/Length 4595 ->> -stream -x]K$9ׯ3&~_ VXiawz}pjVL+#;>;Yc -O_~)89"opW(LN'{0Lח ./?u}5SJhwGVB A9AR -* MLIR V`$ c0RvJ0M -f䂠 -vh!A^=Lu:vӒ.M{%t8M$l!zDl11XI`A$Aa ElQ^iIR$u :Cr*IM+0$-^$`H: [?Q&¸E/O$qb8.3J\0 xW[ԒMR8.'q0i`~tE]TQ- 0 O*ID]$-qxRC%.]LIUZ [Tp3cF& Bt_-I6o{ۿ/?;eG#@ȩ IpC|4XvWb6f.ll& ]'^T}gZCVu:r4WijuBr6}o.zQ^ ^B|o\Oݏ&t -=n&~7=F>.mCyq$ ;`wPf Oy4 b%~ďb9CJ:&IDAO&ћu~"w#TⅲjvJIo =<zX&?쐧gb>Q.(r6H)pY۾m]ux!}syA&S;P.; -`*k/wjm!-v1"y8D}'j0 _f4Рyxg4rf~tI߰TFV\y鯜kw}?6o.タs,ei| -\k6+t돒acd'yl:{{<'|ìj!(1\VGzf~[2NO|<"aXC.DMv+L*˰4IZ.BB>oU7;?%I?\DQr]Wo7fb8%4|s mp_9>-0^Dx|o97u jT#]U;TbDgYOyXRw)U9w#J喴u䛵=_G'Ɗ0#-Oz@c?Gq+bCGH DQ'<>o2lۭe9ޱ/gZ|tty(~qS!{Dm- lLj>B`東?qT@zġc>fe \{rKfγm#4ӸyǭP7xUsK[:f]R!n"lKݖپ6VFe|!3ŽQ{.ás(@C(73b|4o/mQ4Ɖ!vt6Fئ7 6h1m^<ڎcώ=Ah#\GChS~Q+UcW܉J**J OoL+͓y7{ 1S9sꂾ?hyx<8-#3BX~>Ai5O(p(ދv|c{m]<͔T47h(L7bOxS_Td 39dC獸'C_Bdn/cG'<o_~.>Lύ^ٙdCǏ?̃zdA+h8iѽ T_aΥAwؽ©bf+ǫ5@X(_na)_@G PIKrn+w z}9_~3\1|;rSPWC1K75#m(i.>kO*'mWOeߤ+/*KNΞ 9k7+~-0XEOjf-*)Mr᷐ &jpjYsCE SSZ7c{+dÑ*l~?\ DNbn"7.WGH}V`xSn+T]uMlأ͟|VӝKZ:w .֎Q.E5lgTRWRVP z¯T)̪oᜅjT n)UO*|3A{/WStcDq-ʪUpc6§ ڈ_..] - -zʭ^4UE0gpU̓?hV *^wR/uHMKP1JHϤ[S[I.!*yźJT셪U(NWS2;Znʝ/8Tk~laFK%MlTZeRhF/Y\FkecdҌt%Os:_y}䥯Ao ]_^9FU0[W~&oԈ' EXM'4~Һ:5{I+텮a'6Fۮg܁i|oڄ=_8~_ZE\ƦmJvE⊓)Z2]F\ⲫ05Vf2 Jj׳Իr]EFm:jl_tVtI/t_iZ#~_LeR{0V“6_esl~t C,ۍ=[64ZhA4lKWJEL. SEVK &d+ݒ[^ -5hҿ=zNtW&-[f-ΡN5ZJ[dۺi]wm]3[dZ6I*{ؙ ;RwGtlDM:Xc7=8%n<']wLd -cN6t[UNΖؤ:@j46CKe$b_߷·Kj$LzO -endstream -endobj -656 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 655 0 R -/Resources 4 0 R -/Annots [ 657 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -657 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 461.373057 101.433071 442.623057 ] -/BS << -/W 0 ->> -/Dest (cb160-1) ->> -endobj -658 0 obj -<< -/Filter /FlateDecode -/Length 4656 ->> -stream -x]ˎ%߯kC x0Ew[ d@¿#3#U]uތ#<< 2YJ)@o?ݴ^_I(ohʛUpcV|d9S 6NPyb>`>* K*A&A`hVa$0GAe40VkQC4x Q!eE]D+S!FeBIlYIa7DZr)J[\pZtXx' [$`HωHeti+ӒM'0I! -: [Yﴕt~$x»0Z-ntXIt6DAyIlI"DIbD6{E!G6Y#ӰSBL8 [@`%'q"qݒF%m 3R (P8pwJ\@Qu>X hQ -8#%. s)` ,qQ9uFG ad%.@*0H\(6i6b -uQa : k= ]뵕l@Q-F]P=tI\”EX"qO`+eRxI>Q0neeBx.&*'q>xJ\at]cw7x eH\M 芺tNI-Y 0 +$.*H\2Vq=K\;'qAjB#`KV5a -cL!ڠ%xW%.]6%.6I\`+qAHrAₐ5tD]PD e:B$.@`IhaVha B l}-%.$.>`=J`UkQ3QIa*6`- x0:C [0T$.TEd. lA-q"]茑 Y؂hPdVAK\kIZґuf QP*J\a&RЄ^l{ bQ[' RL[ތd [I\uP&K\Nk IXoZכI4֛X 6(qA&:؂) &Ib3I\Cfa֛-(nw}3I:." q.Dd+5Gg23;1[܋*{k$qfbekiJm E2`>b:oo-ڇ2=d_CG\9?嵏'kuTݜzZڧY6]e]R-`yKj͋<Ϻnown RzFeqյ/vtfc0Ӯ_> Y^6alOog\ay>dxl ?@|^hj_5FUX1ѵJ7P 21Qy-áy{~ӷ#a)xΐx-!$ PjVH|?zЊU˩e rfcį}T/۴m5"C:!ZCq(xu5䭗.~S;~Y_-E/BǴ*oƁFߌ 8o[ x6 _hHDZb/}65ZwfN;c| S\p9ޒL9h\Ϭޭ^4ڸEi-g&)^\ůAKwmѲW@ct^p<68}]KDbbC^'WWqą V ffl֜xq]ReyMP^hhu'_*Z|Ag# ^ZCs'zvhZ/b%5 >iG$-YwmKNL{hKoޗ Smk>_]SZyTMvkOuLg4\G+׈Jq.wHS>u?_q,ѱmzku⫱݃jڵq15P'i& vy>_]ng_WLJm9 n'6ّҞzϧ}S;;6~'h! eOe.1}mC|R~grZW}of_%o+I3j1_ ,Xi> %S}5},.Π~hK>bг@RqyŲ8o. ,7m.iNݜCY;sw﫲wǷ+b-hzpbA`?m ﬽ϛ-۞:m1ej} W=`_Ϋm\!GhA+]>f-áQ L$ݠ[]0|"Ȇt!A:@?ڷ5aӨ -jX[P`<r)á6s(-@+Q4ފ(r[>iu>/݂==>F)4trS,Wp<Gەx~qoM LJz-ϣ!4Ĕ_ -a@+;ET`敘FVqmxbCIFMzѼ>r_đayqG;(y'KyH-G -xXuFc^h(4$},%_NhVѓ[7ixIUi[bۗEG˻f(_'i9ُ^3)cjPrqNvU;4^pSsգA|ʓܶ|9z8۱%[E(pԩpĬQ+6AS(CR+w~aҎL:Sm;9ˋjwk~/ʱtx1t7Go{u'[/Y'ALY8խ,2,k=h+=^k6~ȕ7M B f+kef1>)7_f -i^ i{=8=VRMB6GיkZ<>P[KE)!UkuܤlBM~kфl=0U QKk:AtͥSJ=kt/ȞC0F_b>sZ7v#|a棐wоBo&NKcЬ2~K#?QoRfPi_Jxl6I<4!bO;0;$-gme~i:o,mp?F^/{kGyqB>aO6O kUuOH\q>CKvȈP\nLXIs=OcW8kt]G}Ҋ! B`7^+ {_=>gC,mޤϣ5d+ayW=rs-C1:HS6'cTeJD2]eXm -s$z)K=^iNcMZ.x-Zr-#co)[,Ys7)ʶuӲ:އfP7$Tl~U3YDHO15+{M!>#RK^xdKROƚ_ѓMx"+_ؓe-6e:P3JelKEi%j#?˛q}R~  -endstream -endobj -659 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 658 0 R -/Resources 4 0 R -/Annots [ 660 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -660 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 386.373057 101.433071 367.623057 ] -/BS << -/W 0 ->> -/Dest (cb163-1) ->> -endobj -661 0 obj -<< -/Filter /FlateDecode -/Length 4595 ->> -stream -x]ˎ$Wڀh>/€mX+`piil- &_#itea2W/ KdTJ9>}UJEQFST{b6m.ϗus*`;VS1ŨPi*F냠 -F9K*#Yګ"̠dmT f8UfhHR }TFcu0D9+WNRYEL9"o$]V!$txC%l! El):IawKJ蠍ND]N:9-Qt# -%hElN[I` Gҁ') vIaDlAK `l1H$1*ʖ$)J$)+I4`Wrxi58 [< -+`$q $.pXr8--8-l$.p[&H\@0SK\.r,q:p%.p`]烕v q:2Z:3I\@]gtFV)i k& k#QƠ֣ ޵^[ k b4x9- X 0Cg(LY%xɘ1 R& quY ^V&,qbrx.3I\WQkfjI56k ؂HQ0JHc Vu :%.b#qR*aK\W.I\33$qA̰CELE*YD ҅ -%.H6a%i^g& š&Xi)ElMH\Ŷ,6uy %$qAJj+q(qAְYaq贖 % 0.y$.Nc%0n ތd-!-0nIXo$]-69^o& f`^Hތvxg0"2 MD^x}D|&+8cAsegAF7 `&V)V4Z6_ceiޢ -CĜ"72cX܍dؿ~{L׿We%5!0}4,&l1 (1W0ˀ6 ]VT6 -Ԋ=t2+˳yrm>Nl}q7K4,R=BumOb`b cOfzc]);;8hAxayNASd  xDi\<ѴJwib٧ &G˯_>^_eQMU^r_u-&7ʊ5Ǫ C:zڔmF~|k[ԖnGMȷHk{6;ՏOOs/v}w++`X" 1y.˧`s@1#(2ɯ!!u]LOU|P0 W*7d(] -,);d98<<FAOC:Yh깕~ݑv^ir|$C<;暓3xG ML+rT+9rzQKn M[! pq<G -=z`CyՋϯhW{%-81m[q}qⴙw#Ht#3-i7 hHtw"'x;+c@ڢx_a.zy8pocm4ngV6y6~A/m\EQZ,g&)^įAkorw2á8b8vo {'<"nz{ I\xaЖ3;/ΣK~uV9kR -F:nsđd.z}<:Oƞ7wiҍXd'q[nKVe/'S)kl*mLm)L۰slגG}N^焥E^ W[^~(-=Nofw~ZzL&+ź◍ZZ)n{bjZΣ&{OT=jê͞^pzmg _ׇڮͥGvt=ڲ.#Q_#lB(eQ=|mè/Y9k7ҧ>qmm)B; fV#G*K}- -},.ͩ~jK>񳾎6\UN.ySks[\H?m~m?;fNpz[70bǁh{6fؖ?%,ͱhOb ɟIQ\}{`Gdǭ2o ^͡/֗o'˼ƽۘ2;l81:Ua0ǫ -+1,4]FSt -s@xͯ}o*fU҃\Z\D\;|VB=N_MOY!"܁o8}so[*9; V kzOz/b|os>eMSOֵ]P\ޫ6<¼siK_6X{}8[ؠXH!X_l 5)c Jpd0gќ9z2ϣ>k`ܻ׹2i*C&QL5ͷ5vJ﷛ϛ3nefOzߓylgXlcv8|cmKs(lzþg۸eC4ඳ7?Oy84c>ts5IsJ)m+|A.&kAzbo;jMo`Em|-V0aǨ=P9Hw(o%v|6i#ۇ3h#G﷈9{;l&yy.ϣ 8$ng >[!u=?)z|~]&M1u\Mrm?^j6Gׄ(Nwj[+BݲKbV:2X뺰\\Ӵt{2m[e:/ro+t{V'}]>m^ڰ.g٩:$e,~ MY}I;2LqYk>-\.jJ1`^Xb9QZqb/|8 bqeI6MկǍy^/oeHDuT,3[b>=)WB7pHsQxWl~/SuClc0ufƩ;OTgQgAw27ԷC z/t+Й]?StDO1]-=UYs0e@ݥxA4=k&1]upcw§ ډ/> - -f^4* &*|2:Lq5*k'Y$#.c/I[I'MyLRl&ؤ74yډid׃[Jt,ÇvZ&Ƌ=ԾrZ:ڬ\scJNE⊓)ZSF\̅r0Vf2 J~q]F:\tVLIb.\i^#^MmS{>0v“\es\P/Mc g Zb$M#[MJVdzj$z)bH1{Ͻҝ^ \nzzg8:=RX2 0R)]umN͠aH.5cgɳىR;b85+2S/9?&t"t4}q P]rr&Р9*_T2&QTs&Z>?V'q -endstream -endobj -662 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 661 0 R -/Resources 4 0 R -/Annots [ 663 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -663 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 296.373057 101.433071 277.623057 ] -/BS << -/W 0 ->> -/Dest (cb166-1) ->> -endobj -664 0 obj -<< -/Filter /FlateDecode -/Length 4352 ->> -stream -x]K$ׯ|D,tX`mX0={gl-|dVTUv54z2`Av۝-r/39Ǔ5-߉R2J|A!Tاx~>\:m[ǝ)%zrJUʺMJ`h*<]̠YS >+ 3%.UfHS W8)*ga֪:bWtMӣ\|Qu : D+&YlbcŽj:B!'MaK:s -.Ea ЕUl:MWᒉT]/u޲t6Ê$Ťj\U.(t`5.@ ИHK4.`+ʚ[KԸ.cT]1.ʺh\]qwAYpAD0xDjMuX 5.CqqUuؒ -y `U 4.~m9i^{M/0>Lu֟qxsHMHےu~\yKoNn y^U)x9`Z-~ޯy`~{n 6{rNwaSM}s2[F~vxŎIm]{e|sd9x<슼Lt<X}>#H)4҈ӬeLi{Kr}z#y=p(bdMLӽ(|!Y^|eH{^4ciXCϱAɛOG>:lEAQ^~^mg?&-_寯 -Wmю`C"b39;ɯ8+n܃uw ?WN{f%~t#t.!cus+ٻvBgJ.&\r橽6'~2b޻?N :o~4r.ן='M}[[Gۖde1.3eK;g ]l6aO/Ccڸ=m}cX}af1ݖ'iY.ōM)X\q9(},>>e;1厡v:OW7H.\Îl!s5&wMEK>-}}T?\qby)s9뜄'a[\pqV)9_:Qے6[i,qgE"f̫jiu ~jcnxKއ+?2-"]?7N8ҏ 9㦷Z8pnr[l\oˇ]tᓙ3س2IqmXV12kCo$c_»[hs&g:8XU~ôǧPXjS~K-L)2 W;,܍ݦU3vwjSxͪ;9˜;~MRv"hI O}=N9qkfNCKX/Go8s9cϣk']1x,ɾ$I6Q$ZxeEMuZ -!P/Iw߈΃l!;@7Ծq}񁲝mc+1$w ciMxk\Մ~FpNn߮7$FEf,:xwY}&ge<4)W`H֨kxk<׼Li.=]{U^ͭ"}7QDrI7r\~mnۿ'chy hނic65H&܀-ܞȵs|f\^jorrN'WȈ!AVqaOr74)bqpG,mM6MKrn5iܪɝ]d[PoZ:VݥXFo[rv6a}ɧp4HsxW삝|)SwC>8unV֧i:o N6ϪTnmM5zea2t)}Bϓ"z:)¯lk0]?͚܍srSDO'JTUK0e@=xE4&܊吪ϵnC'4ܠ7 ng;2)7Wai6,'/T]*S_8ꐒ!Dfo4cg<(\J\Jy!^{l#\6Si Iu؊]G] 5t;7a'ʶwwq({Є}LBOˣ,7484A쭤 v$ޅ3|CbOd~܌<689K6UxyG[C0Г4FjA4jk;&tE lS)՚[ꈳs!ig;Yezz3%{.Ykw).m-ڞa0$Ԏj|QUٝDhW=qy\.@M.ߋ9Fpɕt\:O.OIP69_ PWjŪCzAstzXYc Io?Ptq|Rr#Y -endstream -endobj -665 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 664 0 R -/Resources 4 0 R -/Annots [ 666 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -666 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 217.623057 101.433071 198.873057 ] -/BS << -/W 0 ->> -/Dest (cb169-1) ->> -endobj -667 0 obj -<< -/Filter /FlateDecode -/Length 4405 ->> -stream -x]Kϯ|_@C$ $#Xk#Xs&Y]=ӳZ-9Zf""m_Ȩr t;?iƿ!bP+79$~W.tKN1gr/o)FUJ'W1ZU0 -MYR Za% kJ0Q4n0FC -f죠2v!YAg - Q!eE]D+S!FeBIlYIa7DZr)J[\pZtXNt ]It)ZgW>9%1NaFaBt-i+l!I:w1%a2vFybm$Q[0[t `KeK %J ؔ$+ -9J<ഁ-ueY؂8[,9 ؖ t68-i$.p \%.p`\I\@RsSt8J\@Rw-qwCNQ[` ʙ$. 3:J\@]L#+qFUA`Eٔ޵I޵.@E9$. hk+qw- q?Z/+q=tI\”EX"q 'i2) xj%.]%xج%.] ^A)]Q)I\%+q L" cJ\pY9 xWQ[\ VV` -I#,Z,qA)qAE`0P! -D*$.YCOk/qAxP-I*$.8k%. dѷ<-> ؂HQ0JHcUIJt-t&J\#)b#qR*aK\W%\f@gHₘa pE*YD ҅ -%.H6aXK%L$ -`` u4!qƧ,X`e-Γ)ٲL[e%. ⓸ J,qh:%.&aiI˲LdOمތd-!-0oIXo$]-69L z%z3]L4H\ 7Jk{ Leř ▁[Eq@|I4XY Bimh ߢ -CL42cZFq엟N<aCjB|i`3#6hC )F܍4iӭ WfCV(Gkp ץwfyA5Gi\9ĕfNV{8_b1L֟߼;}Ww7~mʻ]]k&G`24?N:kY:7~\|^Moa_>Ot 4k -ޞe{qJy^O:ڣ߼:TF&PQ LBX|_~j5Qz긷1avK#|Dz;]n]`9\{{ڹ>""pe^sHy'V;FYM~4v=>܏}yP{# UدڹYT`ufplTxsg!F =i[s2am4=Y9t@k&e %[hݗphgM#mH/zkPڙp(ދ,9կ9#7PIcUɖmp_݈A%Z x t ڙp輱g(~{T Hfx?:=crg!| T -([s4T=qپ#9 $s8$'cqN!&˻ZXxyo>~JC89nGA|x=_,㯖w'JjX/s9q_{rځ4 FlC95h! eeǤ NS12S4vn7-\A3k瀹#}luXGK=kK}(w橿݃T\q~Egqo<hZ_˜Nh7%nZyنou3l,9XJRmIhS8qCV;w=ÖWPPoީ=yjN~8%s9r%W1Ǎ)(xBYu,9_ڻ$e]b>F`t9mx==JI윷นb}*\=[\ 8Ybc9P -K)l&8=eC7d6qj^6`!rۺYx^ʿ[j(ߟp e!)cS΁+cФ:tfls9<}K5=Bi1Ŕ00'Y8UqNQ$T!.neiPe˔ף}Ə֔f+GH"̵̃bAťZI\B3Ňj3@i{=Mq ZYu]lcB6y65l8 /'T'QZEEPeהm@ ׺M̦gVZ\ IL7HŖ*|7Cݥ\l,ϯasDq..k6:1ؕr䣐wоB +xҘjWajVY9?Ro<C R~+)s塱I=`(L LBB-u뱙u\+$c.6 uM\(OJ.TžAi&v6UZY0 šq6⦜tl/]mqj.xspu|fE$.Z,#.xdnH^Ib?p.vˆr麎EW -!`23w<)UvGLgQκ:Hmܝz0єQ&> -endobj -669 0 obj -<< -/Filter /FlateDecode -/Length 4531 ->> -stream -x]Kϯ|_C$1 $ i%VJbU|ɏ_=lsDFcûVk+)E#~?MQyCw,pQm []Oes*`?UTL1j/2T8A彊 QhbΒ -fH3('/`YUq[U6T0dѰXE D -:U@Ig -),"t&ZI -7.O`H:[!ҒKQӢŢwKJ蠍ND]N:9-Qt3 -%hElN[I` Gҁ') vIaDlK `l1H$1*ʖ$)J$)+I4`Wrxi58 [< -+`$q $.pXr8--8-l$.p[&H\@0SK\.r,q:p%.p`]烕v q:2Z:3I\@]gtFV)i k& k#\ -sI\@]swVZAE wA!^` V{謓)D5O`+eRxI>Qqaޢ !K\pTN}& -J\SK:YK\2$.SF.+SwAKVxaDE  @J# w޳s&=d%.@\0*m FXҁwYe)qA,I[ B"c C'µ j<(K$qk]ND [D [2H\@e[\E\lA(qLL$qA1 Vu :%.\k)0%.+$. f؂"q\J3At3Fda A MXe-q<4֒jIGיIDAq(q V`JQ[@`|x%.M,sDlq$.Hr3I\lJ\lz3J\5lA'qAAq,qh:%.&aiIK^o& Xob'7`G"` ,[p֛`'I`$qAכIXo"7]$Lz ^+$hPo 4*{k$qfbek -ⶁ" 'LOU"|fȌiAۚ'sMct%~UvƼ f7J+Lۖ[oF܍4yӍ+,MlA0SZFzT0+D[mE<^FkZyኑB"6*N4hg4z ߽8]p aLN|??b^=[ޡњּ[15= ?{=fy?/MbzhErq,+ž+iBuOvM:=frn[ -4-M 74o;n(Eq~.M K3,[4yvh6TRiԣ'[ {3\WEn9$kش6-``zej}{: -gXݥ?SєoܦVs3TMRo~mMO -ֿi]۰jYfin0+3EaF| T -3V":+)6Os-U.[茅φQ:uM47WVi0ck1vR~&_{nn?PfG>oc">G_oZyQ/~p@ -mn9%Eq?R;XYqo9,OaQ'>#[J#$K| <cjGTčěfGɼ0)?3,wI`H? -=\1ֆp6KSʹaY#Vh`Z䚶|bZe4V êCP1euYzuS0DBCv]qV{;'edMX*0!ͪ=Frӭ.ah>4l4Frd6V%4w!3 ^̈́3i^_uC:7^}^Y>VVH:EX V!,׽I둪#FefeƵ|r}d;D`ߎicΣm\ htcJ>;4>Uo( -G4j2baH[y_ n=zo -Ϙfo=k}rsii!·b-IcyqCob+*2+.̐oHxCswh27{=Hאx,!3kzi_yd\8w<*^?[e Ybƫ^XC╽Ƚ^|6<_s!3|`{CO>vYs4KF͂ųhYIo#<݃ -%nCvStk|ao{;n]|]XMNk -"7ǒ3fuD(q` E9򱐗nLr'>@̢+]=(ϐ᭐<_/}"v|V=i|u>LˉWy擕SډJ"s}eQӷSZ;6ԯP?rĩ)\됔s xlUMڑCgJg!["eЎseߝ&&]֋.~<H){Pne U^t^cnp~_񡜤k"W*V̭b~FRn -> {4WAB=TŖ=|\Yۘf05p N֭EEx_en0*7)ۀP'Ap_Z4a0~5>x -$jrM'Nb4F*Tg͵).dfi7 sDq) X4n'ڈO> -} -+Fm;^4UUGU&e) 5HWs4CczPi216̎hHHϤR[H.1Wy,Ŧj47(?.Nߦ׭`VnƝ87|w;` -cj%]luvA )tq"~LOaua bH=~u,ɏ[6n]GO/2Jb*lfZhMi}EC|M=^SƠiG}8m5n#|Xb d>tlÞ.]mȧhWp16\wH\qҡ%;dX(. -sla&ru=OP8kt]G͎EWYiŐ!/ƂɌ=7OPgK7(m ci#Ұ]<']2քP䜎_)Ee-6i lug_V5&QTW9:z*jx{;l' -endstream -endobj -670 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 669 0 R -/Resources 4 0 R -/Annots [ 671 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -671 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 698.673057 101.433071 679.923057 ] -/BS << -/W 0 ->> -/Dest (cb172-1) ->> -endobj -672 0 obj -<< -/Filter /FlateDecode -/Length 2760 ->> -stream -xK\ S:R^@E5`4d'( 8]3G3C_wD#Q? _Ur}(D8vkK0i [RBi)|y]q}sZ.d*Pj)UXUJy*F}T&O34*-,3baT0[* vp$ru0T%::N!cҳrmDB.ʉ=] 9T=–Ԉ=]-UZ<]-\l+%bvU]lL隄ԪkQ-Q)TE1WEEؒ)5W[Pt[/ON$):5t X,Ga !;(<RbUGX[R@l)hnClI=uuEz,[Pcl* Uxn{,Vpa&y,WjV•sX .{X =+ZwE<(+=Awx,Pp(z,aX_ VXn ܍G+{P<(;ݘ(z,Pp7j (!7wX( YK<$p?gOVk Zw-f9pcAwqPǂcpF eI]<$pqCXwcηuu-PcAwp -H08cAwq7ܥ$ {\l= VEӁXaO vlz,z,QpXVJXArXPd:آE= MZXP"l=[2x,@D#vwq-=d6U%ecUOcvu:. Jр= -c,\X3cXPlVX(Ԉ1lA.t j-=XefX$)YY=TBE&4AJW[ XK$?H6:"I=-ݬ j-cA#؂cA,LXCG䱠qEccABٷMcASؒ:؂9LB :y [bS-g77ѻW^LEd=| -3_Y- g{e@`/Nk9{i3YXɽ6 >0v^QeCY=döPD#nc}~ߔ#@k++lذ 7%#8-aS-mqfFḳ'Ka}X6ڷaH~XM!uE\ q$lpÊ۝(.|D1]޼۾˫p7o(/Uo_!zȏzvS74]o{.Uo]^tu=twuvnTccҜ;x|fysw8FDȏ}G?oHaq1Ծxx?b""1bGZ!gxy﷼Ƕo OFo_ bk.O#VKd-ޏZ7IdKXܾfZ -GͿۭ/b^٭:b&<> w+RB))%17h G%!Zf~SClߜ G)SS!Zwv8~TB0= -inv{21uy -n,r>'nVOk{W}vv,F!MX䈮#|Akbjބ;zsDͭwJQΦ4e1lCZegqkdM|^71 ~Rqj -JV,q/SL*l." g:\Y$< Yw..e:_\ɩonj˔-Һy !`*n4\$vU}̋ΧU\Ɗ] {Gwu?^l_ SivsE8 xbi:d_Lsy'ueۏ()6|y忨 -mz's<ҠEl=ד̾(oplEusuSqǸZgs`5yv98׍,̤g׻Y׮OtHlvTHeAA1putѬO՝2b)e鴮ʘĴJ~koDK2sOG%#k!YSql=O: 32,="}޹j~;u^V.e% ՜/s<xKO֑AE7 qU߬H7Tn$bO,ӃB^ާ? -endstream -endobj -673 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 672 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -674 0 obj -<< -/Filter /FlateDecode -/Length 4400 ->> -stream -x][9n~_ V, 2>y{]yGUIbU/̌{iw E)Ɲ-O!gJ9dMZEcOgg)j* !\t?KYߝg[ǝ5y, -&mTX,ŠcRX V1b&OGVTKX/ -@@م#B i,j -Yἵ*X&AIygR ^`R&ƫ&#u/B般ƃ,Jx ʃ,2dNUxʃ,6Yj0"W%#hb jʃ,| |,6' AqII_BEC_FCf uyA%RҐ 8B\YB% ,(aASа m ֢aAܒNÂ%뒆 1J"  T5,԰ tY 1y `7PIn g5, n X  pn5,aҰb|)VbI #EnஏkX@]O>iXC1f]@Hհ<4,@c#-Ѱ w]ES|he\IÂuӧqWZ6.aA"P "pY4,DTaAHWaA"oCaq򪱵 "p5,@6IT^60$aX$.{հ wm AÂܵGAPk*>dXx]0km$.M Rf/@@,kX -sҰ U R> قY*P& XjѰ {װ {ȂAd:d\AdLD䘰V5^d+๬aAdXKװo8]ҰbHÂ\! \E"S<2s l 眆Cd_LVDh%jGיEÂBpa+M ʃ, 0?؎`&9*HyY4,(x5,mz3kXP-dAƧaApa`(q5mHg_O7UK^ֺTㇾ.uSA~úTY]ehGm:>Gm:!qޟ~:|W2D :O3ￜ~??OhZD A|"ğ|@yxr0/9 CoZz~wz\z0HСv}eEİʯ\Q]faڍ2M4e[lkb< iEMUS}Ne-$> 4s?I6c;M]é_αkFm.kzz3M_x){ow]}X;bEʺBG> c|"@#}Tv^g;}arL-Nmh8ohЉ:/kH5oxёek>:..!o)|K(.OG\҃_wIaMVhgK; |~]OLJ;a|_^JפS+֥o!9h6-S߻>0Zilަ,y'c'i>߅ |uw[=SB4V17$}R)B](./q7IR N_Bj7.7PC*nue K!ߏ{#{>l zecZ?.ϻǭ)N ng2L5L@ m,1"Q_*dBtY"z;œZ@~͂~^:q8mfռn7)i߳2qFJiw޶|o\e1lfC˶LslZlyŶ  +Q,ju> ,#QǴ&Bs϶|wobonȻ[1^X^~wgwWHokֵ``R.Fײ=;{db3+|ODhG6҇|w6mj }iS>@t}\V<=]~ケ={(/TgGMd^P_/w}y_qveǶߎ^7?[y#z{=nV9ݼnr}G?MvXy'cG7SN?9&pVB?&|wsLXO1;&{5~^(g엎"j&w$q+XLX I Ίw.XAGM. եIK91b:o/'t' Muz;hAU5cBh̓Bg*lo0/fK7$j/.'Z3G2֮)4PE6d~-cmv !ͱtXac7=I A.vˤU4~@ETF0)~ͼoVIꐦGyr9r*tG顱 ULs1H ؒݰAfX) &9S~ڐqj䄹$Onj;~1ѐw+l/-ў̦_z'v3A&yS#wo/[?ir˩9EgBJOӸ̏-qہ~`,#O:x:5˴1'fwީVF3]c6*eV[ D)uڦ(\f;mLiF\T-SL_(g%r=l)(JsstvdQhIT%Cm=ڞ0h -ffjgx("{4j߶;|5|ho%%` J3]:OK0͎?O` TժU<(COvB6e">p[ux"BiZo -endstream -endobj -675 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 674 0 R -/Resources 4 0 R -/Annots [ 676 0 R 677 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -676 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 563.554475 101.433071 544.804475 ] -/BS << -/W 0 ->> -/Dest (cb175-1) ->> -endobj -677 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 156.557453 101.433071 137.807453 ] -/BS << -/W 0 ->> -/Dest (cb178-1) ->> -endobj -678 0 obj -<< -/Filter /FlateDecode -/Length 3228 ->> -stream -x՛K )H{1A C"搯?JfHSE)uM8{ppԜ|px.ǿfQ'9xNBMET@*1 n⏧;s_'5 _߫咳CU 9J2T)8|Ϫ%] 96_aƹTmLqItĎ jR⢭ -P7A1kX?u聸!Gj_c xfo7:{!{.POZ?;y'9Mכ.ʿu;z xw[eLw޴7ɑmIu7<;͋3Ys|Wnv8LC蠎$hgسHzV[hxh/^{;w.{-u%Ī~bl[Qo՞a?!Pϫye"2T'{V-r9RϬyWHz|VvЙK^i0i?xQ**k[戥K۱xeZphZS2mz]͵nuj9ue㝶úTlZ?K[NiG[o e̫~׾l}OvПA3\MSZ 7>xNH禞C v8ߨ8ޥz~h9l?.*;u'A_9Obf)Vv{[Z.\ǒ$o7e4Z_Z5>}+Dˉڱ!DޅMG]Hj6C8hpT|ROB! ]s4y4lt^N薎GSo,Fe4UTZ>!]NoM3&Y}WaiĽ\m dZ>S*jm#?LN![hf}zZ#^t\2M^N1|%~> -endobj -680 0 obj -<< -/Filter /FlateDecode -/Length 4362 ->> -stream -x\K$ ˒HÇI# b`vۻ QUzT13"(#;[~'39|yp&ZbsQYN&s8%J)N?mw]8뭰L)٠ -X֑ -CTX 1BbGV\rX -+C *' brr8oʃ sD(=j'x xh( Y`]YAxL(YlN6s&[ְ>!daw} z G `(cl  z:Y ރI4f< p?ŧV5,]1}*qoeb,.iXϬa0 z p":_!hXs0 oY+Ɩ5,]װQ $QyccjXEÂܵHÂܵGA^5mFjRh`ȂLQ ɅYÂ"cЪƋVy<4,H BӰk)K@ kX -dhXPdGfdAa2]Ӱ {ȂlPÂ3VjX$T:3kX9I5,` Ty0aGA,~2GA -aA^YÂ!^ئ7Bd|VÂ2֛5,_z3kXPb%ⷅ7!K@ -0 MƋְ(ͬa 7ѫ[Y֛I.dx]dQ\`V[[oHtfgVw ,7 [؋h= 5i1Q5@XYuݧy*bfN2`d}1ѕbؿv5o>_ N -l~BNcL $%ŷqcCYKI\Ql(6'('8flCQN] hxs%U񋂲1m6^|Q~7 E"Ü+y$_w7WNZWgka#>i9m5z~>Ɏއ4RVfs5t -]F*F+N=.:ϭ}>.'>sr…>w;n]hҳYM}-+OU:J)WiQI*CSxoNдnzmlioS'?CjkHmyф_%Zh #o0;<&M|eE\ŏ^8mBEu;InAvfhx,]VKC[cMA'Jת{[u!m-|6lesW}\ۺg~{M=^MOX.c7i2:jsE;zM7%ӹzvf_a+7z>&Q.[ڎmWd^CY؄-ݦ^U7/n"t1mWZ=*F?#Zx83"]a GbUMGk9񲖽lztz\mm# y~HȲx"ᱝ&Hxl%?EQu["ec7tYWJ3E!znꜽn>ڈߎ[@ "İ{ȯ!{Ś0:8˓: ^j[[| 7ߖ_N~\5} ,}G;V\q H\pS/~0chuy|tLǀ0lna)mG&䎌j] ;ߚU\틺?*/|$f#X;>GmR{Wk-~cquQMt~ FǦe_YŜ׀ʗDNthl!v.8%TVv=".nx՝ڜC1^NM\ un$oG{{iniAji~r2$Cj㺫UGi`˞U^m2if_~CP&yv?8.w8ꝍ7ۀIZtL@"6:~9dOg;`O``0оCnᐶVx]lד\v<<]]c]򋵴1=_ŧ[}'پ%߶FV OlJ rq-*Jdo=X[%[PMJHBmi\MomNMwvvrgYfA;{OΆc?x[l6#7AX1Dz||<:4{kCԜ˕7J?5{s0[w`22y8iy.Wk5l~dX% -vcf}-Zu<8 n;v|ͮ=ux)kI92ɓz-;oU@I@mהUe L[r}jݎk[.5Yb^YoNhB۴ۿESήra#BcΑ<ϐYުΖصsU|f=>0vөT/J h=IpZbщG@;FtE lS)՚ZꈳsA0JWbg%J-lzfsNctvdVhqݩ> -endobj -682 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 250.954475 101.433071 232.204475 ] -/BS << -/W 0 ->> -/Dest (cb181-1) ->> -endobj -683 0 obj -<< -/Filter /FlateDecode -/Length 4573 ->> -stream -x]Mܸs{1A0C=wxsϣZJTIzVI*Y"!<>>¿1`TOpg( N'c0Lkys2>!%o;>!JP)msCyAKLIR Z`$ c0RvJ0M -f䂠 -vh!AQ^=Lu:vӒ. {%t8M$l!zDl11XI`A$Aa ElQ^iIR$u :C\r*IM+УH>:[rIgt$x[MVY-l1&-h|-*xЃKJ$0)J,`b(+рIn Vi茖*KL`5l!\Q[l" -H qŐm hnI%-qߒ^ …J Ƶѓ (% ,8ׂ;%. ]t qZk)z ,xגVxZu8X޵Z nd$.@XLJH!@ԅ}J\@]p 5N kx Do -q;[@`X P`H\:a4j1y xWG4Kqߢ}w1PY x%.Q-FjI&) x~p4 0 Z. *(q$. d<(x.$q*gn-6 @n+i82` -IU-,J$qaSD `/H\# )/qO -:|8ve:B$.c=$k #-p-%. 1I\GE13| ݂טcNf7]~ sqi8cjn`ָ|z4Zɓi6RIl$0'sa:cįqnY|cg4X!8h& _hwOde21^"&ί?NF7=L~:ӱZ@eN(4e9}93S˴4}Xh /,ȺbsQzzE^\?ϯ_~z t8FS$Ǿ,OK o|תWVˠ/vYJ9,Mm%≵o@9nq9hlJïrro 1˭L) -s8x\Ȧ63:elfz҄f4}8ogVqߗmz{kvW\ړ2NgWr}k8s8+vԬ&}78ص)1dmyoSms}.^͖_ht9pg<[0RQ(V,g -%r|XѲ*|RV̨[Q5_Z|'DZKrnUw9R–Zenz?Mnm53BK/l.ʎҢʱso Kw9x_tH3*/t%_5ͬ9Wι]lt_މQeӌ1Ng!ww<>*v--W~(-E4ԸusR{#ry}r\+QfcViNjq!3Yes\J|x'\V$Cl.{ds8]fT=/G>?YFc~`~._s4wɭ3?ޱXL]Cl_!vߏy;[tS|}1wog!뽿~޲Qm 'v:q4r&k%7UU  ؠzLwC|sS'^CmGd`:j|Ժ_yoQc܃фvu9> BƎ%Pf㶭x Da~}qD}{@=:FZFʼ36oәpH70s_""}k`^\V*O~jҥt;: }o6Y;#"/k{k^ ~*/>g4mXٙp\C9z!+6Px3۝y—M^6BrY@nw9:;~Q^yƞ4޵gS}ӌ\G}KӞ{E#j+8[oQ8H~B+0jm<õ.8?g|M+//_p/ǹAJ龼b֗. ri,5oʝ 7rZeMrb :ϏD~Qp\ڦt^EzܯN8h7={lnt#EeIceFqO5մ3ʛ换.)?t!.jGSf)JtpjYK*{!)3­+?+W-C$2 Bz-W=Nqӑ8_lp.xڹ9U Zfb;ժ󳰚ΫN/iM`͹'|8ᴶ>Ҽf)ԮQUfQJ]IYj; F Y.fa,@.t$JsBM笩l uk &i[{>lUd1+ C ď'n - -вr8/4?8Ydy*\fhGIr߬e%qCR h -sZV]:Y^_:*!}&ݚBʪC*e늺*Vr%bN7]Brq-|Z.|> XN2|2& )FGq魕7O?N&N0g3 ?yYy>:e7ܺ,H;y"݆ 1ڟ:i]ACǍa|Msv5{I+B7! -]-#|hj:2Omyrq8p/qyH>"qC:dXFBqNfff@Ԫo -yEx, \`xI軻ד}2ٗګKei%> -endobj -685 0 obj -<< -/Filter /FlateDecode -/Length 4204 ->> -stream -x\I$ ZH-@C$ b`y679磺Tg=62M"TUlßL\RɚjMegg)v%f>BH&)O?:M);>ZXL)YVX,b6)y -+:! 'g%A%Ƃ}VXbJ.YbHcA W8),g!֪<bWxMң\|Qy < D+&YdbcŽj|s//ׯ1_>cewEHv$sTnskk9/׼fv4BvK9uYRuR>~!M<|q˵cեձ$Fz#A!S`)G.(E1m\tٴޕzHetvn#n_~_-.vmzn*G2KuI:bY|][jh'n=^{Q8/@ W*$ECiVN޻+.SAoxuoO@f|С;W>VJ:ϭm0[f -+f(Vo~no/=e|8;!^fJH,Lp\-dG.}.ވ,#a~G_v+M~ȸV%m>\^/ZW>Fؓi?{,_zkKNuP\-_|bY4ڵ@ZOO|eD\TWcgX -`2%qfwvb]79ݷ#iJ;Hr9ߒ׎1vYdpIv\Wٞ^3auLm_1:ii-ec~j}?z_5ط3}y in雯3Á<-6hrpk{M}~ZfE7lXe}5_Z#]].U'?:f -XV&濗K5&~P6]EUGFl"ro&jً]e,4󄦕:/H?B~o/؆[~p~oGq ŏCn5qfgO܋;ni| _oi/s y>l ϫ?tV`z#p?vDfL9_HLo0M)d_pȳțcЏIJڔ1ޒN}0l?\M$G |q!i' F6Z bk*VɒI!?V){̲LǾea_# 2ˣH߮Un%]^jlq*u>ҁrv9ĭmmj9lKq}?Tq|գfܪ}gXO{Xx;{&{ XGdё tn`ыL)tAg"nExs{b6WM)Koοd^28p4?S4O -ZVx-c_2Z\}=hw癵\䦕To`m ;S=ژ!s$#}Iz@Ue o{V^|{noߜ:o_JF[I޾'L4r\5hY2e[A.cH"sVMފ -^c2zkB/dE G4 w.؉{dOM'ouAϪs[Y&s/'tg*Mv0 U:[nvRHBܶ jٕ#Q/WZ9t9ָ[*RyT-MC!w+˴ǚ,]ɲEmm7~GbhG~>qRJ -!eO SAM -S{ -TAzᨻ7F'27;y;ꐦGiR>;eVIe=&T5ud36! swy}E7;v9v|ɩ[˔]xdq:do{M!@a>Wr1rL2-^N?jlsE׉_Ѯqێcm& Q784쭤:w&Du fxh'2j N65&n6^!<5;):B:䧊a;i6E)0x4tQLEfniYɣ jN}}`B퀧SCsB)kwhz3H-hu3DͣRNV@4hdK:j)bP5ͳUyJܕv[R (sɬ\Si }h{AC82S;{̝kNVR~!$UIws%i'sO0lrmE]g0}T^XuH呂;T?U7 -&QMToIz|(Y "@V[(hɗ -endstream -endobj -686 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 685 0 R -/Resources 4 0 R -/Annots [ 687 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -687 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 244.773057 101.433071 226.023057 ] -/BS << -/W 0 ->> -/Dest (cb184-1) ->> -endobj -688 0 obj -<< -/Filter /FlateDecode -/Length 4639 ->> -stream -x]ˮ丑W@|?<77PUY]m n¿CI$CTH{KJ)B`HJ7 -ED)x{x"EpI>]A8|t__.ۥ_.uUVb1TQ9'B3*.1%N3\nUfVȨ"06(U% -fRv(-%!Zr£=Jtbu:43F`S. ｋt8etŚ8-`p[4Z'1[`RqdKZV1ĭNK'\4Fr:6 ÈB'4l%V[b΄Ѫ6(N`:؂@{"(#Hd^8@ lҖ#FtL†`8 SxHV [[,F.-&Y -(q1E[qZ2) J9.0 \)9.0`\rqp'8.0`]v5VI ,xdu( 5J ,xHs\^X:Fq(-\ cp\`8 Nj ,xW[9.PGxp`9.N p0p\*1cl%TLUP-Ό[P' xp\q8^j xWxjNU:I xqp -oBI@%!S8.hIs\/,d $qXHġx.{w3ޕa-&j @aˌiBj0Jt])Cw,Б(k |"9.IBy}qA8P-6X XdR hb h؂D")D.DDLr\| 1Y]N BXq\E8.)qAHC"5"sN` l BQDD1xh%Ԝ<όDE9.0LL` hOl; 0dV[Ĩt3r\#lRs\lf I؂$a2q `\f &x̸Mf Y:؂)1&؉yآ y监o"gS17.ft]D`ȖK xe3f $)  -l@|ML,gpP*ɦ $pœ})*8E& 9Z1SlΏ˯^ӯLYSNn[GG+1 d! |N6"f-.Il$_wn,M7(Za - GL_ *oh֣I: RU߾s*TLvw?^~`/!Fۅ{ٗfF`.Yoϟ*7d6Kq)^י>Zuܲmbb\uf{}:_ﾽ:9*tƪmoj58eF]M9B noKK9*>W6sB^"s |Ot\puo 7,OVXSvC`s:CN9sLK - 'y{#_>+n\k|DF[KT4$a9x/yB7\yQl9oAۆ -o72ޞ$m9㼇r]5,Ǩv_#+4Ԝ>[vPIbaO=Vlq!GdY?gAm2+sѡ"x2&,ŪnuZHg}!VQ,8;,Yf&\l:z?}6euڮ-_\c;~[vmɸcԍ9#[~:mmoH/-uLF'l@4~4Z"Ar˨9`);sZH68mӱ:q|aGO]_v8صmbd/緱y4ndƟ%c~>Q^\H9̝GI(Ez?3̀ -%2ǥ(>FzcuΌ7 KSGZϒmm[n=l:C\ci=ڦ:.{۠gu,=}/t& -K3#˦oF$G#zj.D\zx'R#W^J2j9oc+El.WxuvKs:C{Чը"#y`u;h|Awuw 6YbNP`!ǩuFłLxiiE9xޓYn.|Ɠدċ$ :]C'ٍgQ:Cxt~3^{3QG1[m3#ĞJ$O6#uz39Y =~{b_>o젒$nCXӡuC>ozgVu| s6d;[\xmhvֈ&蘞D9 y:r{tF4Xt(\sρu k|G<>/s:ǖ ;Ym_q=ΙIf/Yzdy@OdEz:C۝;p$rm9狓wJ AH/+4XlOG3o?G'1a~_]Gq;|O ob<4F\uO_ӎxgg7Nw/͆g?rE{#Tף:gCe<+†w,=~ O=XtH#3G^<<\`ӡt0n,-h ͳez[3'<|3f}7NgouN;9/ wO3 N>Q~|?  ءz*q[uڹS^=ڿ7x(/ 9bcZw3^#<фvġ"s:~8tWjOě_e&ۺAdQY7s:D>Dgvaމ<;L'ڝg6#ɵkxg{A9j/ٿG`2leKr5k`>oc:;rA4Prs7#c{:uN;1xƊ槓˓KܻyY/g'~hِ[J=p/?yy={]_;?A9AxaEfM{Cpӵ=blnYm"8syT$WT-rbۥ.ʂc/D^fīR+d|?LieG4U/X2bܕsHS]ܬO2h?ӱ8|o]0Ww˹=1Waӕ?]ʐV> -RWo}ye(USsZZjYWeOdg)?^T"fyM9.;MrZFlAn,\6e=U`@AqB.<1ojW&wZ^RL+'fV^ -QeWS/6ChivVXIn+tMmG5j&ӦSKYHw oVW,*ebTRWJYc0 Z.rva-GsB-[TZҠnbmxF6" yQn2F)k=PZF.p1v#~v++УBC[Q64i~#o,zS -Wy e+ -lm$*^7:keC+KKP1KKEɔϤ[K[IIyHżLRnx5Z25rΡ]l%k,Զȶso{%a!EUsO3cge"Roʎ*m);{pjI:mO#vLx"WC,kՒd/`C&;dYS> -endobj -690 0 obj -<< -/Filter /FlateDecode -/Length 4953 ->> -stream -x]Ɏ$9rWyBHA CCztI͗Ȫb*f\̍=]SJ9wzߵrq:ￒ)fobpɓ^w3~!SL1*/2TJ[AAP=sT0GgVaK*I* 뢶[U&j'`> -*`6J:Fi?8=H:ɢ.BtN!:S'I`JK:[vNI:l.uŤh%]-ɂ.+:آҒ.䜨ЩVg|VI:'lZQF -QϢxGҁ') PjIa1щ:؂Ɨآb(=h"^88lD&%$0)O.F+р~r!G-UŻ 1հš:b؂X [XZ$.[oA …J Ƶ)8 ,(PXpwJ\`AQ ֵ> ,h׺$.]봒wENQ[` J\V(q Ъp$.V&wMRN5Cw-H#7xxe$.p]L@?J/+q{茕Ma3?O&rwuB< ^tY@e%.]g?aD5x%xW$.] ^a$.6i芺< Z2`T8HZJ\޳r{DlH\:t[O#XSH:haIU*f xM B$I Q $7!+0K\%`NS9I\ lH\ lA q")kD.Dɦ *邙R]& Z̥N/q~pIv [U$.P4%\i؂ [Di-qA2Ѡ$2#4psID&i)ElMH\ɶL61uz'qAJIₔ`QF`Q€` "> -ơSJ€I\~I$qA -ML~mf ;:؂) &Ib @$q 7ыKQ\. ft]DA\`V+degW cl U ȗH2q*Z -xm8a^}KTp3S}sdv'ټ>?sRV4!B70}kܾc,S1w4pYf#0ѿVJ"7fBf\#+%O959"&E˶2z$[m$fze#ObZ ԋ> {5w66gejjPGA Cu43 V#" Hcr2]%31?z_oR.4z| cX}]7ӊ4n][jO3{>mmZ/{;e=e=S?OVz*x-˷``·oPy9tF+ۡLͮ fV[ۛw G[624i^81c?Bw9z >ǞjM5vtn廌AN!C%~Ư}\}h ]~?kS\ a6`vv`9x+?q͆=ft wR*KR(Px*R6slm*~ rk8?[4z2n=㕙zz\Cn}cYpH601Ry9D[ynM+xxr#m"*q<.y-cZ"(w]fw:Ma3;NFaQg̞ */y5THrDeѐxYʳhrNFnk Rb-.C_jJKO-ϱŝӝi}~]9d&yRorLS٥Gm-R/wu }]uD^Xmq/;qwZ, t>!G8BRsX .KgK]vi [ޖ,mm9;K+¡tPCutuY[PuBd2qrg#NՂ8rA-3{FUi}_s[tuՎsV1u~v^_ed^^/yצw [}cvNr] s#Vä2*eaDg8[yQ($Kj{Vam'?\ Ǡ>K'@1/ -G^lvRO#}zR[r]^uM&cW]2e!:Ʀˇu@'Cdi=nG:՟PiPГ)tZ78P}.hoc7[B_F6ۙ+#>v.k cw -f}C9٧ -pKǗ zm]rM7PҲIDA;T4D{6x\FwpFQZ}2β阹Ay1ϋ"B8nٍ6G2 uu#bC=dgdm .;[t6PQq؀wŮI};ۺ;ϣw[q= -gHy{p0m6X<⻺-4rTEGҎD]/y9$GzO!-:.2-6*9R77>زJ]y5Th~? ~h6 sێ l=}!:o&] \BzUmטyզ(m`#!I(ik`ޓ]6gG.y9Gm5`tY+-<%7'6V:y36=A.c'\J[](NJjM23^r8=/7Wx ㏛!tyUM, -G@Xyj‹y^ M$.<V4dDf-ǶՇ㇚/ CՃ4c<0YY,{<-.~~^}1!dqmeM֦0CK =]j3'@uƫsy^'/~woFWq[iD4yװYu24i| ry5 Ǥkx&P{Gcfq +g 7O eUYaϖ7.?/oF=.y؋Ovھ8殇CHz%MwtHo; e̫0z9M`Ya 518v{9^ʫ.GCWQ`P4J}>Oiw!oo=l[(o孨*' 6DO0|%eMljyWӳ%o&y^+Zq2np'=I|U,3TU))?hE׻fw9UbAAotjҋ޷&\f -n^i{=X[ń~+T.6ڣu u5Mk"k#j(}ZTQMfQI}MĵvD AբYѻ2ga@r-]&[JbKz\=MP9^=È#֯k1=WZ%>nbFvQH;W(_DžIut)ET7t*7 3U&%)_k^ &^;Cc'y@2wftRBz"ݖyl%e.cyDRC ˈ ^(.Y[2+i'o -Ku FХ:ׇY^t`I[~ vWWF{}s/&HڨI߸IR[.9> -endobj -692 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 465.123057 101.433071 446.373057 ] -/BS << -/W 0 ->> -/Dest (cb187-1) ->> -endobj -693 0 obj -<< -/Filter /FlateDecode -/Length 4260 ->> -stream -x]Ks|_@C$""99;6Q-%Rvv0;*>JǏg4St~pxRCp -Q08|tY`3OɟO):?I\%` l[1[2H\`H޷<-> OQ0yЪΛ!е qA4`*`-5D z @Cv$.i $؂"q!xN8ӅNk -%.&bDSK:Ry%.*J\a&RЄ蟼v`&9XGhr3J\#l1H\lf )O₤d @)%qAMC`\f Y&x¸Mf lqpQDlӔq Nz$07ch8cja`ָ}AĜI*[ɓAS-/;/?,om>aT|Bs%m=d2;r+ @@%3%d݇~|0ztoo//)L<-w $ro,2 )mt%]ͧ[`鵛t^6znɘ&.m>6m7<{s9F>L:IaEf7/K0 -LLgyZedGƮK|׭ zp9Cdcɯ FX \ l÷-5:ѲH:3(G>:"9"+*q1ܙhʵ9b4TbУJ[kxZӁ"<#;qȣrڕU.d0(r-#q_!qG< gG=8{d;҂|8a;uPfk[6Y"+G5Cm2,=n}m9R-PF1; Ŵ#&=]E̝yƍx?P=܊BoklD(G[;M~֤Hs8^UM/a.= ~4!b/Pו@Ku[2"]󗉣&r[w9";9a۽2'Bk~m w -z;>w>ȝyex_{v4GkOr4 4׭z>\Ÿtk^}#`gұ.<СtQeck߆Vkk;Cs8ُC9{!;VPx7w9 -k:_3GVwY~~pww9: |/+pg%]Ի,b1Շn:t峌;ĝy^nqڹf k}/.6qG@;Y[eێ帷X=K?Ֆ7F# 3P-lVPbJmq{WF]WTM]Ǩ=̵o9;޾gg!u)@c +ڭ^Cqt.q=͉jz{}O4e#k̿#Vb^G6cᬶNڗhd)oLpC[U~លS m+]v:y08tstdVm&@rx9^EWxL(|Jgɛ?e0M.=p P/y -D22+D%wO!/5m -_~Dzc9S.Le(pwS̞ {XtǓOAZI|mTt:=6>_򱦚_ŔN:ѐ?˻(\4)1aUSGU"]V#3 Oi]9+3shN+w-J$)!rzW}&qӕ8_lHvXM/Pb.26mSMВaq %05fff@Jjgwu FKtԦY^twLWfF=^ɾ,^\Zo,K+R;^es9_ZeسiC4eزM lVi(*]@M~Ve(R>E[^xE\nd8C;RV_2 -2sW)ȖuӼ2۞mP37Tln.g\t)U#:9`&9UBK" ܜzd%)^c kUM Pm+UΖxK5j4ѡU{chr ː͚6;1,(-꾾Ye* -endstream -endobj -694 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 693 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -695 0 obj -<< -/Filter /FlateDecode -/Length 3206 ->> -stream -x[ˮWڀh>/"@D@E4lri3)6Y,Vټ"WZ]&Ku9s|=]V~3]%|$j:D>$"s!;A\%ʣB -3Ԑ5(P# L5Bϕ!zOePċHd!&c -YRrJȁɺ+d]r2tA3t*JT]b*tN']]ʠ/>0YO.&Be2j{E]n)y& ef2D&T"Хܩ #%"a2DN5Q;,CPt3Z X@lIX h x Y .Y -c r . R. %%1.H`[0.H[=0.H[0.H \$0njE$P.\3.Hd\@ʸ uS.qA&iqA& qwS“T] .x7_xa`V0.ؚg\ ؼ0.nX:`b\ ݘ1rwcqw¸?f]PHt2.zYL ИHKdnXHL\h0.0}T]8[XمR: Bd.1.;qA!vϸ w7dp0.悇RYwƸ wAKqVaʪ# c瑇2.(],qAʠKjq$:L3d]kg\Pl2.(U@A,82.(M\0.(CʊC93.@eQt* Xzc\P#tI12. e`\n ܅ Sd\&s0.`?2YU55Be\P8,ŁqR!K dA]* 3Y.H Ӆ,-Bd Zleϸ+405}fc\Ф8M LSRtM0.f;3.Mls , Zl Z.GMoVCd| /Ndqȼg\C~3 -ĥ7ゞ<⑸~2.]2R*.H:[p`'&+%va\Kfc\4MdH~n`&&"3- P~-{oϸ鎳X[鑁b|uD &vS,O <}}A -lǎ~A=D^[ |ܐ 4=\=Zld`lKA=zılnC^;j z1#1vwpΫ΂]ՠkЫefGLƲ&HbYӠC>|o΁Gt.k_sgsɶSdf5v5VfP Ue#Q-CG4evt]!>Ը5C \VٝC]^]-0^#w\M aكu|2v3_ *lFl q{Ae)xρ O9zufۥʼnuzy~˿WNN {S^"Mn8K_W/GߪO}T.&O[ݠKRAEFovݭmpedz1F'Fim!onF{=m/Ygc}uƐ~S -fl,kdh]P}#<%~r/mC-~zl$=lz떍Q=ROᗕY'aDtk6K,=Bvm7ܵ=#l/nۋ{]-*캼mtiF]5{XyY7ﰠ5[=&c$وo69irY8$}n6hp3鱜{C3gT$9{> -endobj -697 0 obj -<< -/Filter /FlateDecode -/Length 3917 ->> -stream -x\K\ ϯu+HmQ)hENP\pG͑3ù/pzDAQGJGgEJ<Bgߒsq)\R,xw~w?m1r ;a1RK`5| +%lrpbk b‘YbpbA  -1KkVX#T V#DM ^H.Crm^(\8`9jK%fo S-/CMd+%B;U&kR&k׼K[\mɃGar1xdɃ,|xY?8jxk&O%caY Y|-BXRȂؒ܊x1X@@$P, 5y[X@D%2YX@@[XX@[-XX@[![X@\-, . ,, `.;-, .ܽXX@@]J9ZX@]-, .q0p-Md[Xtt*YX] -XX]Q`؊z g  B+>H0p7&Lݘ|c?dka=x,,@g."- wCC3|hBm‚ g 7Zv!faA"P "j w!R[N`&9&Pb jݬ -Y6eY,,h 㳰$M0PߌlaR‚FMl meY,,h YRY45oIo,^,-goV f`<,qp75 "3&2[ko ?Uv<1ބjx`/U1 Wp>}GTP3kI6#{UnT;7ǟuxM?)?bI0Վ `{6+ӣ.5_E',btjrͭMQOj&|wf; rJNwLuMz ct Q P)k.l/nh!KYZ]a/5VZZZdk;F=]tMXl*"'yŧ+΄yoBg.H4L& UԾ$eڄiB&Zڱ{_q%Sj9|iiu+s,O g:t7}u_=%ĦgyPNŻiG9|HU>;Q9Zq~'7{}l6]Vdqc3|=jL!?^ȇ*F!~췾c\*FRWV_Zާ=~O(oׯ捱??HU܏EnۈLKa?o:$z gL{Y%8K9m4;I73!{:mmOK^K!O\v-ZQRJC15m uA7aOIJdr1溟.OOo\Ng[3d Rs[֍ՙVEܲ6{g|) I]CL>sCO}ݱ&;j$OE9`7|p16&6FE)P~F-huY%J_M;ct-O\gk5gO)3/\nzAO\#<2~;MMƭ7 !(-\7޶ZDRC> -SƤq/ qm4/y ZRX0[].rYɵA{wsq$X0G#3ؑliF>F5xߨ;'xMKy2ᾣ^{M5<nҒc1Iށ;GA#y\1@Gl\o9:M9Q'YNmJqZmtzIܨ^jVg&YIwAJN'+ g-Jdd̴J\5f<(SO%[{k[s~0nˢ,98hz/-ްؓ{[5z9ֽzn$d+hYtV9zZ1ױgik;Ngg?lwJD*PUX@x84~#E+rOVx<"OySK;vL,7֯t3'VC,ڙr\ȶDͶzC9sZʏ|ޏՅ(/3n}3x> ]xe㬵a+p~ZېO仃 yB>WlI]D᷏+H~rӘOR%y`9\eޅ,oWG[)OQkWWɁ"kW-r!O7P"NѵZQ7O K;*1v4RBIM\d]3sժ gbij^ `zKsʬUW64DYNu*ޠTV+xd%Z&^O"g׵ -i"~'e/ZP\s.=CETA!4)yf ⛓W:li pYuB)fBF}Y{jlGU*S҆xR<0n†~&VjB`ENӔv%g,eiyb&A^n~6$1"G?L`E^0z[':6ɬ{:|a.Rr)Ȼ: -+%s~Eغ#H&PIoz6Y"a 3ǨWs} AjbZ:T8M7RIOZ̧ -"8yhHuh%B:UCt(ےl'd^g$cJ#H+BUA -L;m;y ^yxP'OꝦΉ uM^9ԟ ]}=IrZmTQjUHzPݠ#PL lϸZ*3Xԟ^ĤW%_Օ~Gě(is.kv~՜d5hYT^5iЮ#4x WfWtUY1oYO? uN@͡P Y aU> -endobj -699 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 593.554475 101.433071 574.804475 ] -/BS << -/W 0 ->> -/Dest (cb190-1) ->> -endobj -700 0 obj -<< -/Filter /FlateDecode -/Length 4143 ->> -stream -x\KϯsE $A8!>9&`@!?_}HcK^vb=*r۞ ?/,lM%E>_ޝޟȤ@\T7Ml I%'ߟ>L)p؛S -Xd -BTX,1BbGV\rX -+C #@ ,k,aKH -䰎HAbN`"5&K4&&jbb!k<,xLIE'Y\N^%⠝2dweY(xśP2+QNsLޓƳWy()& KPTd huݞx8XA_C! A".iR2\k 79k(r1``8' x,BF< kXdA ,h ; P׀UbŪ!x]aAJ԰ &!a41))E b!Php4,HBd<‰5,@am/Y wN J PbQ}wQ YP)jX$30kXB~ Zxљ*/g)A*`/e2^rIe R, Lv5,(5,@ dYP jX].3KBIYÂHa;M ʃ, `l fY|` rv Y9 L,4,(#Ұ،c OobmQI%DQyESQ&IE -kXPbfְe#,ͤwC2i<.*Өa.De 3eǙVȀVI=3 Ce*c&,OU;$̜dac4W-c?~NoWOڏF LڮNPkD92ݑ=`=ZT4-:X-\tk[IzV2O,`G#0f"qy~Ev4^N16* iMY΁.bT-zvvkkZ=h6ygruiI4d>t n|h>4Q55oY+e݇CG>L}(>ԩccMϑDAAٍvy56zt9>'|QK',Y|s=1 {Zy% ?)%'6soY&"n"S7\oərlu}_j57}/9UY ٘O -P{Þ߿:A9*-ls.HnHr}~?O ݗD@P,; ~$q~ʜrDSqqCp2:<H!-NtULk b\N\/My]Rf]oevi[|ЛVu/>2Oh+8;-~~CVE긼[,KzyiY]YFe~[״uBK+mP2kX'MTM5_ˋ+e]i\7ks2-+V?D/ߧ=;qy+ޒ;&T(&nEb2v Ƨ=|ɣ-U]ֿi.=/U9_mn@m@V [6nxVjy;!s.16tI!AgW#u7k,)()ko~!cR]N~Zs͵[/#ëZ^ q|AR+NS|ýh.{wIƫfrt=4[v^Ӄ>?>Gca~PI&wy.QRwn-&o6X-EnnMZ!J"+Ua)>! ?EbRFww0S6Σc׾o>bo/*P䑔Ώ4}mejuulÝ z>\~6w޺?$>HLVN;'4yq^n&o'[ՆM(DZ?M62)\ۯ`Hz K\xuGŒzm\qj}Jj4OԿ[įm>5i9j>iy*s<A!7yڡc?-|-{vI~M"=Ӆazbybo|՜iY5)ߟb}"֧IN^rlئ)Lm3ʶ+=fVgHILkĖ"aO?ɻBX!3DYGcuA]N=I>Z?ANJ.Hк3\LO1-+DHՓ+Y޷_b%&3c@ێG(l'b8in7yNomr"^N*UІjui~tjh-AI!Mk jC3Yم#qoWZ;t9BTZ(}WhN)Fȷ[k֔'qrQ: \o&iN4ePSnBh6 2é9烓/Ң&KKwulݐL&ʏ${Dt< <چ =;754Am0t8]w]gpxi2jK'7wCM*\e}<a{JVpFy1 w+.i - [_XoDRsO/Eo%os6G(y -endstream -endobj -701 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 700 0 R -/Resources 4 0 R -/Annots [ 702 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -702 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 527.554475 101.433071 508.804475 ] -/BS << -/W 0 ->> -/Dest (cb193-1) ->> -endobj -703 0 obj -<< -/Filter /FlateDecode -/Length 4059 ->> -stream -x\Kos_@C$1 $ j#rj_3[]RD;Aq_=vfɹÇ=~S8Zd-1{!dR ..m{tl8NXM)QPX,^a`Rr!*h XƂ!sV\rX -+C sV.YXÖ%aʃ ³D(=j; ׀ciBwb5p( "pWܦ1 e A4,MI)jX OEaA" KANakS|$Ys$Y2hX[M E R԰Hfraְ | Zxљ*/g)+ 2^pIe R,8*k< YdkXHZ o{&g/?]O>w͒G[*2i>Y[Tf/]^\<Γ~VLigNgq-y#qNqoΥqN/E19hͲպ "],-"\0Ζ:[}YZTe㊉Ӿ,}gl)9u1/6$^Sܞ{A\-]Z\3e< X}ڸکSQ1T۟Av-~zDwLw߅} -l"=_1b5/>goüe4E#2u Du:c6Ka#Wuל}tƷOEnvב^`e*ʘd3N`&戸͒_Koy[!{,f)W`77y5fikKD6XNz)M5 brtLoD.Ͻ5J:kzg/M}d퓁>B.^/b/_Nx a^jفHXoLhtrAo*|ӕP%]K~ƭ}|bМfU. iJw&\ך,-95p`vy$b6;C)Gy-g۶.ʶGz.oZ[՗<-of.j˦gc_^@ fؓ V#:BbH},=h"dʾ%KGD"AхZ7y5#< -=='JdU좄dq s1xl=MpNiAvr[MW].:;mkҴ{JWvu*Z˾!I! -+jC36]EWbnĽ]i頶Sʣki S+^=ۓ3B}ܒ%P{MywF<bpIiVH!q;9ӰAM -G1;Щ<ݤ֡q5&[%Q5 XN.RY_6^@P'MTxR8&z+#/{|]{nt:ZOF'dGЬq&ѝ#ܙ'묟4.O;-@cf8ҷq -rp|ĕ4.\vSG\̃r 6bAΓtՋ7on8- qD4¿眝Ϯj?Ku8j;> -endobj -705 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb195-1) ->> -endobj -706 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 427.781993 101.433071 409.031993 ] -/BS << -/W 0 ->> -/Dest (cb198-1) ->> -endobj -707 0 obj -<< -/Filter /FlateDecode -/Length 4164 ->> -stream -x\KϯE$A8!99Z*C~b7S;3Zً$Zjbc ?_[lM%E>>>Ȥ@W[l.*{p[bǏBɤ\LJ.}u綏=:SJt6 ,&((YB0)VK,EcA9+A .9h,e!d9@ ,k,aKH -䰎HAbN`"5&K4&&jbb!k<,xLIE'Y\N^%⠝2dueY(xśP2+QN('g MpI1)<Y" K4,>嬜V'ۓ/@<ȂEB)jd4 p).5pΜ5pNk0J0KpY jLNkIÂ[ KCaHaϲ@ Lv5,5,@ dY jX]FIxhPc<3kX9 5,1A Ty0aGa$HsTd5,I5,8r6%L,4,(#Ұ،|ӱ8of 'Hs[||3iXP(* h*ʹ&!:iY\a Jof f DDI-wC2i<."Өa.o"r{Lgf8Z1 @ooUK셷Jj̀#E2Gj -%l@_c| Ki.QECIYp,}9F3H>o|?pU %rD\vLk1 ;΍EDHehkMD#-n"E(S,6GUҧvyqIqS)eUkJ!eL hyo6}NlyqY nk&`B^k,926$׈)%,>/󼳎e}rwsR~A[+F^\9"J@%/&Q%$%$h勓ƿ}{@N|/ta7z?=}{xg>-C\ !ʢ"%l2eIXitvgeȻ!+1EH+-qK߈w4Y/b^A~xv,Zo::M}Xu^:|=LK@(hY}[g qA7ҴX5dQf j -a~ܴ̀e2lu hwkXe ;qOkh<':C; acJ Euv K/Y}^iJE-CV5_#^qytͣ珢ݸ5l(cS` M5/_.AxB\ΘE*Io[ӑIs/<8J,[<2WZ~h`/@>ffipa,%ny=Y4NGhf ^*Ƚ9ySk+/Y^8KVz_\2>M\ /Y2pYev FbȷuymvvɎ?&[r[.(M%5R%,#Ak vOĻ_x]7a$NuL␖7T2m -J8{wsKt3զ״E;luQ CϽQF)xn"WE7"8xK|L"7ւKũU4ʴW^?E8=>YV]gf&׭{9z;(ŘVkiۭ)Řz{X7݅qc_;I.ȓʓԪK^)j6v\,9@/^ -p@2VN>y+d]]! qH},=Xk`9o .Hк'L\,+D,'cW"^.JMfǀ<WD DdM+vAϪ.Myx:`Z>Ty$ մ$TZ O -tP_S?<طs3$JkN:Z;z> -endobj -709 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb201-1) ->> -endobj -710 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 446.531993 101.433071 427.781993 ] -/BS << -/W 0 ->> -/Dest (cb204-1) ->> -endobj -711 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 110.390928 101.433071 91.640928 ] -/BS << -/W 0 ->> -/Dest (cb207-1) ->> -endobj -712 0 obj -<< -/Filter /FlateDecode -/Length 4039 ->> -stream -x\Kϯ|"` bA a5lryj% X,~qGW19\r---6 xt$B}N;??>M)ɻx(9ۨ -XǤ3Xb) bL 1pXg#Pva*gG brr8oʃ (xIPzxޙskLxŤ"k<,X"djlpK<7pG5, '4,U. $djX`0hX)gheaA:b\ƕs -RѰ wᨂ d kX.SkTf5y DQBlJ9VŮrIAgYc)_Î,':Olr!Y(cl2~00:bX\u^a NwU}g[ǜF< 6-㕫%*{xT?o ->>lnlSnm׹َzqa~r"`ldɅ<ϳqK5x[–vڬj +]_߾Rl`pOn鐢"˳փTC>GYkc> i017>yg4Y95/4n!x]:y;.ֹ86kXڴ Ɵɤf,ȼ}}~k2K-w5Viu5UVfv443L[}"߱bJZ- cTP{Q]u5ܞt?8s5 k 4R0~ig.^h,R~jwSP5-`6Tv;Kgԏ씂txmiϘe}5SH׬[jiAw沆oΖL`lkL5d(7 ._SNmB;Q'rt_k,oUhV7l]dҳMzFMzTڼԣ{OSksE_\Si>vU>/[_i"E ҮZó c,79|vk n}5_ J?ck;Xf]/_NxͲj%Ifu>_eݰ?ԇ1s1CKOvvlrC'A3VGw|<6.e,._2^vHW+- T2UJmӌ~{^3V[@}jLЛFe|Lf+Yk_ClkmCZwˋXV /ojN\:(/\o[Wޭ'o@Oe\!#_sv!#rǃL -gIbhXzɰNlyKT[?m5?n8(,N+DLnO*Y^fUdq Hs1x삝qOt䕠4]Yuni;OLΩ*U^,mC5ziatjl-P't:(W MΟvM^Y z)AmWG}roţki SNS=wVLgo0Zn-GwOH$!fuXac3q;AThrBETA僣nRrw\IlvVI3=u!Mh;mv֗c6Ie=&T-ud36!0 nʏ3m,cwSǙ;y۬ǝlOcs>IdqP ֎N 8d=~9,n·46:~Y-| yd$Ih~l& h5t?4쭥:w&ơÉz&+ә{ {3z⤤,y5p1/^UNP;wL j<˴>',uvxXa:{9hЂ6NTj8OJ9F#&SݚZcAetw+1λvmezzgscuv$+4T-Ce$ԎnqY0j?Kux\>,_Yf9%`ɷNd\>'*I3a; `/ExfLC/ӻ.i -zCKn),|X;RuWTӦD% -endstream -endobj -713 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 712 0 R -/Resources 4 0 R -/Annots [ 714 0 R 715 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -714 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 657.273057 101.433071 638.523057 ] -/BS << -/W 0 ->> -/Dest (cb208-1) ->> -endobj -715 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 306.131993 101.433071 287.381993 ] -/BS << -/W 0 ->> -/Dest (cb211-1) ->> -endobj -716 0 obj -<< -/Filter /FlateDecode -/Length 3488 ->> -stream -x[K ϯsE 0| K6U9|z wg%9X4YYdu/=~^+B/NO8\4L^TS*r! ]]O_>t(y*aK> -'6T1CL*-j#f rʀ!DKB1T0X2F$ -0lMxK0zt\*5TS,KY(.`ՓI[:`.%`K(-]TCWULUvSW%[]-M6uQX ]c5uK"tȹc,]:`[ , -rK  NBNrfBNR'YDX$ EsMp 8 X\ ,A -݊dqoSA-.`0.$0(T-.`p.;-.`.{SA,%Y\]x=M-.;:xg m,.:aB)`d "n}@AB?h`0X\T= rTj w`L]uaqcʎRD.[\bq8! "xҁw)ToqA"o!͑뚺|-- /`S,.;<Ex$$=X @mki$0z -[:Z\6-.HYX\Yp q5dqA:|.9\G LH XʵX\p,H,.@F*!6` 2E dT rL`UK+tm -t-.YB1Y\Zlz @N% : rl \ - l BGdqA l --.@F- S[:Zg $&4X@`}؎A2 Gf` >X\z3[\P= 㳸4M4T*7X\}fGط֛*:`AT} NB vt XB jJZo fDFo 7y\ލdL@֪=7fghYꍈ摁"Ze|F2 eI*cE>&7>GT 3K֛~?l;7}zvRϒȝ rmWf }ˣRp|/o79Ӯo{[y7ǐ} y}~~A G8%>iscSu6V|/t]-?\+na;7#b>G˜SǧuϿBbe\=E>(iFZ͠%#v}.ҾqMȱ98yǓMÑS8u2ynR5Vl:ޟ8}o~ay9O=̙=lm[u|~݇e6c2߇uo_}s}Ǹq}1ex{+nF -e֟|j& M%ӣ>}M < =vɚp)No|OY =]JJ&Ju3͸$oa'b^߯1U)vJԿͤm EzBv5F6([tϏPt_Xc>L(}{2oRdc#;h!YtG>v;nfuK_73N0>ogxYO(D -c %&=ѯPX.ew =._pEQk\X澶kȚZpuz\|d]uc9GE0#1øBf4S4JoS[}\!դ-=^ݝz\}/%"gEj'O9fx"Žf*گ.\uozFd 9wZj8X6qk6þ)035帇xJ7|*yNXa3KGt~g{hc}丽\?Ep"ͅ9Y{71c?}@1"XW?gw]vQdW[b<ӽ} ߍ>q{RMl3ѭX;Neq_tYp(k9xWLae)>KS8e{ې|Nx9aZ>R}խi-ǂX'Ct9W-X̡_VMoIFlJѪ̮[~Beސ]C//{szXkorB)fu\cwU˸C\)ͥ -[iQERed0$7hUe<.梜ϮB`Wd<OIjQLX)gp*8\ 8تя-ǸSw> ˬuk[''| -endstream -endobj -717 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 716 0 R -/Resources 4 0 R -/Annots [ 718 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -718 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 642.273057 101.433071 623.523057 ] -/BS << -/W 0 ->> -/Dest (cb214-1) ->> -endobj -719 0 obj -<< -/Filter /FlateDecode -/Length 4874 ->> -stream -x]K$mׯMŃ=/$ COG}3螑հf=UIƃ 2%"/O_NfI_-yJK%pTKrGY_cn)%:,K) -Xz’ QaE`h,9:ĠƂ\VXbxJYbdIcA [BRX@QyylX"5Ki<c Yd X KDFA9iY|FAx 8h( Y`]YAx/d"W39#ϙx.U< -s%PTd 8! G'O9+ػV\"Y0YL% \J Gʔ5p,`P,Io,xj@ d 5$`u1Hb5pטT4,]^65, .kXDNÂi))E b1!Syqsа  KAJa5,Hx4,H dаR,o5=,05? ȂHQ ْ )DcЪƋn p2x6iX-Xȥ װpaϒ@Xk< YdkXH 3FÂb3MG/9oo"SfҰd QTdAT&!:iY\! Jof f DDn d7] Ȥ񀻈Lx@V 7$g:3sƙ X[-j=I4,sTw im` ܢ053'd[sbJu: O}zU)?l0v =D\tG^ĺkQ #:Xؗ-Y]tѝEJ "F"/'$ HwFٝ$$ϑjjGGL&@%aYwa{T@ TT[,.m%v1!Pֲ;w|t>^r^q5!'Sʉ]*n2KM UL]rozԝ -,^|Te}uo$Q?O}ԇ`oWz}7?)ͧ*w{ȧB&CF+>Z -}'xJ=]B Q qğm?|>Ϙϧ1@`cc'cB6L?t3N07X ]n{Zy^c{& sҡ|t>.5}C~G,ד(cS^fU8WYq*Ϙ7xeqf;6֍emBlg9=GT]t:[r$wM3pMs/|nsc<œ_o.M1ilvTm/KcZ,Ʈv5_-=ߌC75[8P ?D/5?g&"ym7t-X*xёC8f dC,RuUx> ys:8&%{YT.=toK: W;,q1c:\9cj],.G~>ȑTӸliRJx͈Bݔ))eXO);F`wcDS(.ڈGī;'7LAnxcL}=wa8a:a'2~Ʀ4׾Z;l"m[~^ݝGc~qW†bNw^5'z^z+*:vtb=WY8iG`o؃ufoi _4#]$ -3nž^[eN\XcqXZb~i2j<-ޭvxo[V %>XYb%ּ'i]#˂eKr&=pm-z''2Y羏B5v> -\{S=Xo̽:Ğ1oއ߲Ee@mzٺxPc7 -ʼnFg -mqywo"kQ د6´t>6n7k>GtxiDYYoml2(Siz}zS?`Wⶃ_c,8dgR ȺH?e0،\@Ԧܱ;˻ ֑~gLiS˕Bj{rM_lg2OeD~>ЏǸ:f؎A뚑kuޝuݎnY˜/1ᯰ%w|R2] Ø+ۯk8&kV+=CYcuޝގ8t//*kQ!nWr}_{{V)=4<ݳ7,cpmgCZbM}q;J|9S~aJfYtk+bώO\/3imywv'.G=3!_53alc7,qrjTd]W~7˱cʺǶ&۵"G Bs>XYӊ#t_o)_ݖ߈E݉z}޽Gx:b7֢FcHhc Kfv2,Z )4h(L\0etH:=} ~n׵rspsb&\|W6k -rC~r&niU_ts{>˟؎I8Zc|VC;95\Mq|"t$XU^?'K)gr0J4⵿v'GgsZ,0_N^-f&:iS9ufx}lU=_Yo2J |VK'[haׯKwM%g&ħI!!35-8v;w%}XL{;ַ.pЫeXdz!_Z;Ṿ7md:/=! -2Aeg]FÑhDwcá8Ct:+uIL-nRT׮3PePC/9&<)$M&sŬ+1wCQr -rR˵˜4JYtOQ<.;mo>b|%ױ\,:W -Ir6^&5*fm -aPyKä4;a䭒$=!M,+eS6+A)Ϡ;JmBeJAjǖl 2CXJI4]t7aˆ< UE+=v'9|4fCѮNԅd6;dgj7;)@a'TrցNwdڊ{9T9S[ZF^?(~D -uܙn`,W2A2ANn#Oͳl0q^Ӭn&v \I S:f e|{}}p]*<1OKY4'.:tpɉxQtXd1 e'C,?ɩܗxa?ɣʦ;BAllQ~{}7chIc5#yF[^AtZAڨYSM}pb2V8ZJ#?KM9+CAJ> -endobj -721 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 488.554475 101.433071 469.804475 ] -/BS << -/W 0 ->> -/Dest (cb217-1) ->> -endobj -722 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 427.607453 101.433071 408.857453 ] -/BS << -/W 0 ->> -/Dest (cb218-1) ->> -endobj -723 0 obj -<< -/Filter /FlateDecode -/Length 4751 ->> -stream -x]K$mׯM:-, ‡ Ff$++%iT%&HF>Z_~/9cpϗ_.j^_i9(U+sH3l\b&M?~uӶ%` ]bQyR -,+Ă>:1\N^bA gLX bXݳ20Q;1tQ`i9QJA5O%@AMy<ijv i%^^B>I<Y|VZysJAgSx`ȃ,&E+"d1Nx ȃ,*(-]|NΉ J1yF'kzM+QX,A, H< Y~$pۘ୆*%,D' _B AxB$aqq8 LK.I(`R^\VBX3Z wAB!p@%e$,>V%^0KkQ‚݂P%,@-$8% xIX3dHXP$\iȂ$[di-aA2٠$TAIXZxNQ$,H.,*JX7A y0!aևm/a(sDdIXr3IXd1HXۤz3JXdA'aAVa4Y8xJIXuBiK7*ԛ(6P%,x(" iʂPo$^,&; rTo& fDF/n $7]$L8@VGg23Qř▁"ZEq@|F7 &*]U0 aºķ!"fH'}9F3{ٺ??\~{_._UvڏFPZ;Wpٷ[M 1MK6G/Y!* ިUQSN ); E!<9"'E˲y$Yde:hFze>.kBm|cj̛%'|ȶO%(nP .%TL7v@iml6 ؠxtARW?!Faϗ_Pʫ|n{=F}Wy.ϯM־Fi cj={7i̍l[i*zvq: vT5R(YN6{˷_Ts>2Uwbu [*޶̴ xu6F[ܷj{Wc1sv~na2#ߗ<ɤ6yp(evɹuϳ6`XVLlUl+UjަdIuemw7OhTy9m;GslUUacVPwle& ^-nz)-oǪqx1י¾cOdgB ^TH N\`\/J{7V?];=K yS|ܵT+H£dKDC0<ӳs,rL]2A)}GyY|_þz[ aKes] ~Uac]7./dY]~YrCtڤ"P^BkL_ rmiWsxGm5 bFMW:f96[Wcϯ:n YEߧ2۱Wmu}; -^YMeW6\b:LT,)~n^ѝ–fz@sT9Ȇ~ڏ,FM)&;æ{rq.v[5^6zd3(.pk5z$c^KE[c,k`cG}tvN[?bv=q[?c"]?l:sd_y6vrtO tUpOzv.Ys9Z۹F .㊡,#Ǒ%J9ڭa-y~Y{)z}\s02/vm6|_hίzk ۪ jk#YņvpagqGС>2MsC)[nWXhdwvŋZ$bRBp+h +"ܝ0Eez xi;lA{s$ImA,$C)z'gDI%؀K '<ZG|و;(Ĭ2rc;m߹QQ]% (trȮRo-Nu.Wdz 4i{.B//hc;IxiڭbnOt2[y;HH9zŝQ]$1xNJNPCw=le> fCVz>`ͺ#0SCW~i>>6 :F֣~v/w%ku>ObAe ufo)A0;%7ݦ>G~z6F[4sMIJ7cռ${&m~{g$FzUH/KhτrGN{|^ͨi1=em{ u?퍔x~{, jX{`{R}g庌vK%,ޢy nRmtQY=KoU_G ev]젶,M%Z`}u*dc~&^vٹq%c9/4 4A:v 8:>$kM75y4. bNomMdyD]0"^׆j5,*wo-Nvߩ6bv>[5zuJL͐\o[;thT蚛(i>ƮFz0wց[_kݘvAq;GX|3=NlNNjˠR~k6x_w*!O]7)zy8ovVI:8IіKmK'%'6T2FG cK: c%'&dMuCr^ɂf:vrr+M`]>.Ff2~j Q=ڍqPܼSyH~N&E受bKyIiFu0[7d5$^܈m8h58n k7쭥;!#nF[@MZ̷m'i,I~:8LgGH!qDMGH|P l#&$w|),XAv|F+g 44o~{}WCvhWN'Fx2Ֆð=1ǖ CC},|$gH-(ѭ6|RhI[pj>bl2ڭq{N1|U=_kK㶈׳% 9Se%@ w6~nE+; 7 #3Uߵ|w>NԪƻ$T -%]>']gr,Z5aYW0c[V)MЀ9*o/{eF*AXJz:*-v e -endstream -endobj -724 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 723 0 R -/Resources 4 0 R -/Annots [ 725 0 R 726 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -725 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 303.873057 101.433071 285.123057 ] -/BS << -/W 0 ->> -/Dest (cb221-1) ->> -endobj -726 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 242.926036 101.433071 224.176036 ] -/BS << -/W 0 ->> -/Dest (cb222-1) ->> -endobj -727 0 obj -<< -/Filter /FlateDecode -/Length 4359 ->> -stream -x]K$ szP/ !@d1HF8C~>*vw:tzPResDFcO'X=7l4EMɟd*foc8?q.|NX1grEN+Xޫ+!, diϊr bI`%(gea!1LQ` 9ZAM3^(=H"?WI1Ѐ^*nh`/U 4H2qaLm E>F;LXv-s) 3܂5([~;<=씵&Wp1ٷ,"${Qa6!m6 ;?d,,jc%xFt )XXC׹+rDNet4;$:HIGp>,b@|zN:\րiZ+ -yu//%)b1"`dN -\N&Y_X -:˖s"Y;S߼=!,U)7qٱAa폧//ۧӷֈ#_}a;Gq>2߼V^賕zݟy?S-cú<.w:czm{+f iiooN}6ϲB]k(ݱcU>Ƣ C!0n\icLojʾԡl|7r`Mue̙M>Xьpd5Ra-Si2BG:'[ bgI0!g=^PY'ˋz+Dhۆng"I1zf7ac+5աVqu;!w;As,u7US{Zy8kԲ>LEMV@9:f#5Xf>{yY ?e+kҷx4YY=?N;7%26Ѽ~i4&.?z6>uT$K|luykYX\=vJ?~.޷U^E0deҋ)7_?ec꧍CÏ-McS=.O,khai~[yEE/Ѿ]ǵ.]CsddfA.zYY[4-]*e?T]T]u[Cn{->U4O6+2.7u/:L$kzAy.mJmvO F/30TmY mRilcZKuCOdvz2֧XWS}G;M=.68xsq2oWs%]Ǽ"kǛA -Y}4݅[ &^~q{MJZbC!9|{Ԟձ6~AzZrSg6:5 -cUe]B2yMױ:z TH%₪_/YyiLsP:MNK 6 ڋhRL ŗd(-kFPS.i)Ye:cDeLL&؈]d5uZcʘgt^a.z[yBtGM"meWqȷ|l-N}/d>5Tw/u΃ Ow׭-|Lhu/\>}ÎđYIb({[6IiO h6aC66&.{Yw˪cq=Z!:3sn/wY_ɏ)5[p-:bv7s1]vT>yl{Ko42vWf Id:>wY= xy|߱:g&~>:z~)Lz:gw2'"KS^z:fv.ߦMoHڑiSgJrOTQuI|UrqPT&Ǔzq3]ɶA~>kfDP2G"X6Uޖt^qm4\߷j|Vȕo/ D fOke*s)tQ|h28hpTK6NOD'ꩻA1|wLW].:3M+k4u[HZSMVwʝ[>!I ]N ݚ&LfO, z I,W[}b/F4?D瓮.aȗN>em0> -endobj -729 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 453.873057 101.433071 435.123057 ] -/BS << -/W 0 ->> -/Dest (cb225-1) ->> -endobj -730 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 392.926036 101.433071 374.176036 ] -/BS << -/W 0 ->> -/Dest (cb226-1) ->> -endobj -731 0 obj -<< -/Filter /FlateDecode -/Length 4799 ->> -stream -x]KHׯ5Ҙ|?,1HG:Ai`q"vgS|DFF|U+SJ9w}ᢦ_rq:)fob^/.XW3~!SL1*/2XJ[A`=a9K,3nˊ%p$ uQ-+C XCgVCDQY#$SHdHh%,p]1ik P&. dJX'qoI%,],TV|& VT#ajZwJE%,9LX&`"/O*$aX'$"/N0$-axRC%,],Y‚UZ pW9="d$,@\Vi2@ -U3,J,aAҲ)aAD0I8! -6c dB>&\{ DdqIXz6' , ,$,@D0e[L EdA(alJ9 ǠU̔"Z%t F7a) ^Dᒄ<$,U$,R4%\iȂ [Di-aA2Ѡ$dAIX$T-<3IX\(TnLH) `B%^$?H6EaOVů>]twٿRVtwwO/k*DH J]Giy]?CltKsY8r3:*z-.oO]4ӽ,Gzb.{+{(!SoO;s}3Th"fUWQpf,^o!zV۷UppQUFm'Xn䦝2PTs$G{r1RwДѮtP$]̑U:ҦB)ꢙr]PEFuK1-{n7fnMCݦ׮b=jë́g>ǦlTWu|NRr7rwtgFwM礛6?xY*K'n32[ց=Ҽɨ9S+Iuf^ux/4t'Y%CwP\G‘ 궴QkeDJϴnse{[Ҥf~mg\s %$Ӝw:dq0Jg&E{ -ְCSBuĞVF:m_=+> a %2QUƒ3zWcd; ,ͰtCy8+8kUY"~|Z'wڗf[q{ {e,>ŋ~e @su&1 -6{YEts/jm?>7vZ*vh{|#}z{mk،ӱ坫h㹮:Bڔ2_S[Y$Me.B_Cq!5MK|HXLtޓ6 =Cd -+ E&mZӞ@.S^d{<{͑覿}Amަ-7m 3m~{ɳxS3W3+cLPN+:Ҥ i{ nGmc IIYl}ݩYg+:.feҿ&y㾜 -9v1ȯz[ dkwD_UoqO~GУWho|Z![N;LWd: 7M^. -8thpTKV1nkh:;. bNoeMdyD]Э]S_E*ٚj5,*wo%>Ov_ִdv>5:l&fH˭@]r5g*RiTMCa6u ;N#Gm_d:&ϵJn̆x`qGX|3=NNNjˠTl4:w*!O]7):m\N7;y$Nu(ԥc6S(OKw-Les@ǒu2AXOJNTMt7Ⱦ5\-+qHoS=4`n{b3 e?lH"UKAo>/P{=X -endstream -endobj -732 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 731 0 R -/Resources 4 0 R -/Annots [ 733 0 R 734 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -733 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 582.273057 101.433071 563.523057 ] -/BS << -/W 0 ->> -/Dest (cb229-1) ->> -endobj -734 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 521.326036 101.433071 502.576036 ] -/BS << -/W 0 ->> -/Dest (cb230-1) ->> -endobj -735 0 obj -<< -/Filter /FlateDecode -/Length 4812 ->> -stream -x]K$ȳ Ah؇s ۅ (PDٳ7eK%E:_~:|2K -jEePZ-1OLiI%/'7]/}{vK)p /)d*`VKJ.D! FHJJ bsYae)Yd%1l IaY93FAC³aPzx.1WT^&_b"+K1dG%c5^,Y"dY\N^%⠝2dueYL4VT^䔏xc[ sTdk"d1)jZ4 p)-Ti _(SPPJ^WB$ 97%PԐ[B\Y|! ,(aőװm ֢aܒ)V%c 1s$ < T4,\԰tI!: <`Sx'k4, Xmp[4, .iXY]`Qr6peCp%,*/-Aaw]qpבPQ. $djX<5,@cCXaAڂOibs͘>WqoX4,],T^Â|f VTaAZZw+FÂE4,9,Xk`*,aAX$*/-0$ax1C5,],EÂ5{ "pY|v n48 x]cRѰ wy԰ &&a\; b5,ŀOAÂd@,Y(Kְ 9Ӱ 9ȂADK\ "E dK.DA/%'٤aAJ`) Z2^ᒆV*}XywYS ~Ś -S~3_xN=c&죕Yh$Z&bC*!+fqiGqd9%t& &z_ -+[.?t}wOϧz7iO q>FO VyNgէ+`~ke~q_-~]7swQ3jXccKU[WP)Lh6'gxB_&˔ộ̥y/WkOM`2呇3?{V6:F7)Hf JR7Yį3UMJc6e+k&p+ɨc^_WpuR!.N>VYXp -,42f7Y! /uM>Y/fNĊ|` -!B_>XY_^jZNYǿW|w3ciDݫ$ڽ֏I{C`gwͫ~}IKԶOdlxnW,pĆ%-u3|8-VXqҕ-K/=>0.W?OBqe=۾rL_ r-xWs@V[#o(g.rvk_WYiޘoz';FZ!W5ۗr+W5wû($G$4cl܆wcLp6F\`UܞN|۩<d59KqL(;J.-Y2VίdelhVՒGvTlm뭎ybL{umNn<oy*cZJf\nBM(ﺖnX^'!LzUGVĻ?7uf]5¿[~e訍kĈmvpr߲?lmp5V0N*{WTSڪXvE}ڣvbhʣ4{瑩w/Ty5BAE70 k~A>3_<>]ZL㵈=4U J|Vd=]ǯ#c5?+\Da# ;mGG<[o4 |/yi\?M6ݔ#I5ۯ-sOz8g@;iʒCiuچ: W;,q10:~ڸq^& j1AP3WԫFR#Qvx·1ďؔm|g1n3b -};c7Wmc~NTWI-qlUhX3z\,xi+.1o`6<[fډ cw=zŊvwWcyynջ;M<9yyE;|n⵭.G>+kV1Lqww:RuK - |Q9M !aGIAm h 9٩[5j?XBGm|e uFsk{ . ^~/{V۬4DwOG?N}湵g!۾cA32/"4u/~!6?6#n{?L^o;Cʰ~/y>mXFeo_sMӫF~·8`G-[' -dT N28N\q{qN3WW/dx ->Vd^St%s'N;a.;xJnCD{_Du=VYxn>>?U3e!'ۦVe%?R{7 _òS\lZXR}G )dqW"P582DRigWhC -cSʣji S+^]a/>b|'>& q%SHJ0„fzEͰAgopF7+TNe_,u$ f'$鱣iFY.RY/PJy^klG*Tx R> -endobj -737 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 382.623057 101.433071 363.873057 ] -/BS << -/W 0 ->> -/Dest (cb233-1) ->> -endobj -738 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 321.676036 101.433071 302.926036 ] -/BS << -/W 0 ->> -/Dest (cb234-1) ->> -endobj -739 0 obj -<< -/Filter /FlateDecode -/Length 4837 ->> -stream -x]K-7ޟ_qH1~?$ "@Db1sr&Hn?է{ސ9]G*wG]%P'Z%bLw)X] ©䣻~&z?%-z.\QW-RZ>f5"cT * rNgT^ bJ -f`ݪ̰):N3֑QEalPfJ0Ce9PF$PZJVCF3:Ǡ{N1t*hNg*8]{9-.IlqZ`51p:[7thNbt]t.A'c[NhtJ lVIiK8#53Ӂ' 12UmQeu1EQVȼqAؤ-G:a 蘄 p4֧ -:8"089&0 -X\V[L [Pc`@ tkeRs\`@0Sr\`&zqJ5N H=p\`yq=kX1` qQ k X.*Cq"t QZ ,xWV֠w-pXs\d.(lr\61p\*1kl%TLUP#ά[P' xp\q8^j xWxjNU:I xqp -oBI@%!S8.hIs\/,d $qXHġx.{w3ޕa-&j @eˬiBj0Jt])Cw,Б(k |"9.IBykqA8P-6X XdR hb h؂D")Dlz[6?"`2瑏aT9"5ЩqAV+ KEq^p[T8.+Q#2t - .tJq\5lA4qAYC#Ps:+s9.֋*r\eLL` hONH~l"au8qA:a`3盁$a "> "ơイ"Mm9.f |)n9 $ [BV[4%f݂o8-:Y 9ߌ @9 vx%0"2&"[. ^ʘ3HPoe $*{s$vf"5[RIv@ ',Ot>3| "9(fv-cOp׿S־R"2 }+ܾc$-禎i@u- n?,tF^^@dLTZH3oshr@mCEc:1F 4Rhd>߳zr2pY) -h*qNz1Igo -D$/?\@ՊeϾ_)8Jw__H0_(t OϺ\7^thK'rt9ƵuL\xWӰkD7 MؾEߵeoST˿^?|uՇ5K6V6Z{sU>dS 6Lk"CX~@Rخ87SBt&vLSy UC\8S -f<,ghH'L`D30yΣY=T6ؐED~+igBS>mm56ȥFz0,R!isUemfY^A3h;Wfs`P&ݚ[gBma#$Ґ!#^WmWt5)2Vf۶NC>ETλROO5߯rw8Y;vP8>봐x[~á`A*a=͈LyaW-{3wQvá ff9sg/Y;b{ޘ&|?]a|hF׬19/9f(We{Oɪ^ "+Ϥn&+:*{wמ?iϵ\,-3cVg--n&Ki}l^z$:|á`{@ޫPoJ9*H:"&/If{pnn x7:{~n̼kKBGBy8ޏfo6>bݽ/=!z\]oĔӮ7}*:ｱꍰd{z'< -b)MYPPvŊ+|ޓ1YJ {v{*y5U;M c_gN=u AʛvaV&}[xĻveNYwě'<:uWϙT ʯ=9Ww{b 1䗭K"#[/oj2JbWoH+,9$oSQ-\ʺܐ\oΖ6FV~ƚYsdJ?OSv >S)96˾uBϜ|"l63T:|0zYYe?dO؟G˽cx߻egĽmX3v\;kC[.V>:/y<0hd<bצ~U1i롭{94穻O\a6_tFM9 թ~\w(Y&ų Jq!/aB|_-  -H0M~8źw-bFh}uD)o}0iiEׯ;^Güu=(8sT$ -u9v4UM-xA -,nՖ)7VàjHZ-4?M ;^d)E4:/7H鯦*=Ho g -ro*}JC¯ފ=tgEijS`NrwT=m]X{Q䢖Lm_,f%Nˈ+,eo˪Wd7oi. rɌ|ԮMZ|b)gv-3Bj+w/|x^nfG be$PXfʧQCMC:']Э4iܚjebTRJ }iz2kdEl/Z9FtjkT⨚SMnd3?@ֈ4Z\Hp7.nįnpt zThH]ːEOXM.T43OlT>s\N QcP6dTtTLLt $c-Vu])OJ*t7ĮCu%vTyEzC;wRq3A.|ފc8C?NXFgD8 ) "nS99~/itN QnyP+|boE.~\sJL=Y+8Շ&ˆ%?*q _Q]bo%UgPյTʐqwi{ s3ri͡mV.ЙᒯI\åCk5 (.IiX23v҇>oT aD4CgM7Y R!ahiec'{5ٷڻJei'<^jʥ__vc-1B-C֞AX# Q"Z-hV6G2dlZrǑc!;iGg7eshQ8qwrdddR;J&m}7o{%a!~DrTsδj_ewDq2UhSZރClF]:O$mTg PciM4Z-mAsr;TMylːSwLzcA* vڀYm,V -endstream -endobj -740 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 739 0 R -/Resources 4 0 R -/Annots [ 741 0 R 742 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -741 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 172.623057 101.433071 153.873057 ] -/BS << -/W 0 ->> -/Dest (cb237-1) ->> -endobj -742 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 111.676036 101.433071 92.926036 ] -/BS << -/W 0 ->> -/Dest (cb238-1) ->> -endobj -743 0 obj -<< -/Filter /FlateDecode -/Length 4534 ->> -stream -x\Ks+|_@C$1HF8C~D$U5kc`vZU|?Kj٫eS%E~x1S -jEUP-1,iJ%ş/_:RGVRNEU2+\* C,ES^`4 粢0S~*0%K -fvXg!;Eg霝b.MNy?D6XMWcȚ`K(j[%2IE7K;EeteU[L4V?T]:gFY;`ӫ:(LRLhBQu%x4-M>嬬Vǫo5]-%Ru1ŤQVļqKiH#D.R &%iU'\ TlD /Y`wN` B L"VpQ[)j\&r!Ҹ 颛r] MDbqRSƢ׸?qq̀Β, M!2t ָ.tj\lA4qAvh4.$\93k\)N*j\e&RЄ>l paU[| rv| [q|L[i\PL8Lָ41qtq%77qSmϛIB% DQuASQ-8 MҸͬq 7ѫ)ͤ 4xiԸ8o"3]ęՌj{[%5g`@|FR0'լU(Qxv0gd* {fN<ȂeAcw=6wN1 4ug4yO}wAd1ՈWL79 @pW5`ƄEpELsg:?q/q}qQv'wc]K^W,@`ZX_XS|C|qa7~~i}&"sNß_,_~_X\m6ikF^ѯRH] @f0B_vKOc MG|4s2x!tΛl9 Cy37a \zO~{ɶvWnqч~vGt:W4QxA0b-2/-dd7*HbCX*sC:Zi]7e>u r݂*ڠ wۄYaG1pD׹-pv.i:F:ot齲5ﾄ3iVr3n6Ȕ<ԸnJܽIm'9l{+?u,&g)=:oU_#966ka5#~y3[ߋC=Aٗ)^gs_ [^֒OFN]5T\7'0̫g@i[Sٽ)D.Q8hίGl~jx".8~דu^q,{^p۝Le)~shMgW/bh=W͡ARd}eMVD;M>#G Γu:D:WhRq1~)2d=?m]V35kٌ0zL#Z -#453ekC|/e+\v⭛)ZuǓYë#12.'sgi -6;1~{[kߴh__z=3=K}e帒*#jNl ??o/:;=;K[YrgɁcmW<ڹwGjُ/:a6R<-r1sqp8ێf ^[..v558e-Rp|YON4֢\-F;m.e-t0u_n-7AƬcLցhfYl?mV~T-}q !,:;(m!0e} ߟw~8>voۯ3os)mo]oo~smYtnde?1,;Sqs(b\:yGVb'=BZiб\UO>|C~xƋ r]blumy7](}'SGJwe/dEG?)@NwD)cTd=d&kS Rz`rTLAlx+@.w)w%w,Tָ_quGOK`rw;YJ14~nDk$iJkdfE=~u9].G>~<{ 9F9.(;ϲŻ#ϣ;<|9湍n3w ڶD'< K:sX51~n4mIltf8nt7tVVLsNJ5݋yf8r)!6! ,;7BB#bG˯讋CMb[Yt otgU/jM5:e^U4}Bϓ"]5M̮Ưoz)E-L^*y~2sw"Pǵ56Y턷 ډ/!) -Ћv8!M -KLKyKRq5:k'IyC,QV˦1+hS)ϤKweBJ3IZl;꺘)sfС;C_΢p!;86nooW` ouc['CLFgB8 ) *na}Lqo/us>8NyGoZ2W煮nosqg:[έ+U_؄}#ACl(>k Vv]+aP]^x&o/@SfloC7Ҭ….%_EcK (.EeX2);gINą#mV6duB`//ddeeeb'brl+ڻYJX Ozח}~D[C-/֞AX#ՅĨQm)ddNF2dlK:z)bHrV+GK@A9љQǒYEYKiM}*AÐ8"S3]Wk֎ - TQMJkc0Q9Ο$-"{tLI_N EyMՊQ2(AsԷdMGE~7;4]ѿNJ/Axe -endstream -endobj -744 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 743 0 R -/Resources 4 0 R -/Annots [ 745 0 R 746 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -745 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 327.123057 101.433071 308.373057 ] -/BS << -/W 0 ->> -/Dest (cb241-1) ->> -endobj -746 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 266.176036 101.433071 247.426036 ] -/BS << -/W 0 ->> -/Dest (cb242-1) ->> -endobj -747 0 obj -<< -/Filter /FlateDecode -/Length 4792 ->> -stream -x]M$qׯM#{0`^XXi Ƭ~d&HfdeVTZM+#I>`fU;")<]o?]~)8ꢨwpW(LN',a -ə_/oſ^~諙RF럿d)T *rn -8/p)I*ڪ̠dLTfX -nU fIR \TZmu0DY#贛<K:'I.@tN>vZҥ{#Ғ-dctXo-&+l1$"l-+-钝\D.Ab[QnrZ%鴞iEV&Ag`W.:2—O8bVɫ*%-u/1E/QVДyIDɐD&ډ"ELL`%0MSx* X[y -+`M$q5$.X--X-%.[RK\`A0SI\`6zr$qZp$.`]뼑v-E/qZJZ'V qw 8+QI\@]I\@]D]5 ynqH\@]CK\L%F]P:c%.@cAX"q'iդc8𮎘>Q&0º(O$qQY x%.OFZҁwIJE$.&@I+@WԥI%.p]В^xRL" i @ƓB*q½' ):?I\%` l[1[2H\`JѷE RL6D$qApFUy3u:$.&b-qr)bK\r$q̀N!, hK: [dK\H:%.  ,+ ࡑKb%gF ")` S:m'q$HsDl$.t3J\#l1H\l|3H\lA'qAR~aq蔒 |ӐX9ߌ$o"m>AD!DuAS-8 &IybI\faMD@f .$x7JLVƜqFq@z|eVA3P ߜ#0e*Z -x60>-*8M&, Btr^o_|oNYJiB|e`!ָ}1+FԍԠe- ]Vl:j#/y/F6&*b&nuMҵ}в}x}$[lmZS.Z;R^=qv@ƒU!r'b_)d -?7?ˠc( (i ޸(5Z 6aZoֲ |답ɇ{vYFNy6!6qo0cB6cmzaB_"3]KFbu oӭAtYzߞt袻v m0˟@G3j@/ #װ:v-//y/ȨV.jYȧh2"jy:G: -5,z|3+Lא¼:;햾#J}(Z!_Em8tJ)Ly8B:O1b Opd`k魷?1&i{ŏ,a*XǰǾmF7?e.Ny6pkZ\R_B1WYAطSBIq%jlpm%ukJy-٦rY_CG1:O܃-4G - m1 N,FaZc=3YyGy!\QD8T_ʨHh;bL?&7#dtȼs Ѷ !yf%ϖ6UA^=ۼZ 1//FzsγޏI8 py2_<+k|c nOtNy:ġwF~a މǺ|/R~ܷd͇OѲKN"q:ObHjhޮR#>sefP6p5_ ؗ*{紙&u<*)?;} r,c(6ycs.hBbϨ#vOy6y6߻bvx`-ġ.wQvӡ {dyc#?v^F1d-)t(:x#?pP]o5kByN+˕x^zԢ^6#,+׋-_Yxޜt:ػO_e\,3cZg--n&>k^ZFcٝu `@k{oJ9;K۸9w ,n̸kc{oL!\CXnDfS}hVvߥ^<^.zn[j@y̾{[6י½cOdCA,8D!+v -N:Oԃr+o+څ[9oGڕ9fNxdgC?7w6>\?f"Sylx{G{lT~1ȹ*Ocql]2uVO&~o4{ WVrBد!#[9uyW絢uȗ+(YRsنbG= -R(o,ut倫etYvy y>:=ݡ^lQS~үr 8\ˌ~_}vCQxˈud7KV-6gd6HcbK >ybg!6rٙ/k6}[$iT}߻])~B m\اu,_1u<7<6W֬۬žRaUjƙ>#<.Yk޽`-7n~aϜP>coϰԢ&,34Q2ˊmײV .:sK9 W7uކy=X{NcY6N/iuU6uClۿ;n^q?(-NK?߫+\phWa隽[>4"Bxayv;L~R)b8t!,qDY,q.6{E&k{^R=窇sst|VWR{It/3# ۚ_Ӷƥߨ>_?gkoI6 ||YZۙ=+\T|:]+UfmyHB񢲤2Ss+ YxvLOA/5H/8"^tKD=?gQHġn0$Z>"sѸz7jj![;V^Mzd+Lq aox`x(V1 -뮋 U{t>8 f::ͦ5M=n(*J˵:F5eF&udj$nAM&٬C,ga@V.rv-6Sj#MP <ֈZ6ȩ:nFxFPuPB -kx K*\f)45Hc+PU#]+qӵTkwb߸+6:m2W86vF5o;cnH;~-Z;*}Ivӥ9cA:1#/}?}Ꙗ7iܺsO E<) -۲aBCX^U44?n kU'ZR7M˅!]-wGxF2K[o|j -vpv|eM*.Z2".xdn HIl?񩰹/vˆ|iMWY V!aҼӴG0 -FMKۍei#B-֞mAN_=(^m)xTeNhtb6ZrQb.ig 7eshɶq8~wlddnR%mmu^mP7TjnS]3v"RO&{=8fvulwI 1*'dBjICfwllːS'lzcK"Aik%XB)_x -endstream -endobj -748 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 747 0 R -/Resources 4 0 R -/Annots [ 749 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -749 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 131.373057 101.433071 112.623057 ] -/BS << -/W 0 ->> -/Dest (cb245-1) ->> -endobj -750 0 obj -<< -/Filter /FlateDecode -/Length 4803 ->> -stream -x]KȍȳsX`mx`;@cCuN } Ń(*kƓ.TgH(}UJR]o?\~)z⢰oW\!Dqٛo._uL9o_S V`y?h|XAOb b۲"p9y11I`%a]vD$GF)As<gR6YEt4)Dxy -!$dYi!)YMQbU"ċ@;Y%J"v99'2x*Ŵ'UO6Ê$( d gYUFY#Ɣjhu[eŘDdK`dQ1H4.I`b\6NK -'`d?Vi*]jrEdIX` dA ,Y ,Z$,[oA J ĵ)8 , %,\ 씰tܣk}0Xu)HX`i%aZ"%,:NV'+aZed$,N ale2)) p$$,p]D^k< ynHXƙ a e(1B@+a  ">2$(@o *{ -K9i1Y m'E`>3EdƲp{1ٝbt O씵 .PbMm`WSi!Dm:$DCH Xn$$\1m/z)2$&522\ :?CGB"DozOWYr~E!+{B( )%=Y'z 邤èոd-Dڤ.7}z߯S!GJWF>=4gri.E E嗮}83L.S  t:ObOCl[_}K?EyY0;hu6ReN1YajѨǣ"##mhdi]6:Ogqcg-`A1¤سӾ661YqZ^ڗͳ *^+dxy:L(qmϢw[o -tK|@I[#}z{.R]VdZG4{ѕ-c;W,/s]+?Bڔrnl ,g ̻ mGvמtuY¸aƠ6,E(V17cY:w_|^YGղhOhg<Gk}$Ev$e->x׬v'Znw*yGOJc=!ϓ@]W50fNAr+'n\mTUseM]Ǝt48[#ʶK2Z%f7fC]b܆vQ(V(L-k215Uai6!EP;|Ѯ7F'6;y$Nu(ԥc6S(OKw-Les@ǒu2AXOJNTMt7Ⱦۂ<}z; rɱϸC]fx+ͭdu2Fuo7:c!@ar[u,2.7g7iΨ呗e_.v(Ǎha:.ܓщ$N8oľl8(5t?n k7쭤;!#nF[@pmC7kRipW$p:*7Ka-$tՓO #n7heB`/xNNBA臗ׇ罊 - jN}>0v\e9Po˲g{3-(QShNpjbl2Z8Z=?sM{>+]Jؔvђ(c$ݩn-nʆ aDjT#kG> -endobj -752 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 582.273057 101.433071 563.523057 ] -/BS << -/W 0 ->> -/Dest (cb246-1) ->> -endobj -753 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 521.326036 101.433071 502.576036 ] -/BS << -/W 0 ->> -/Dest (cb247-1) ->> -endobj -754 0 obj -<< -/Filter /FlateDecode -/Length 4851 ->> -stream -x][不~_Qх<,dYCk$X 0([m\= ҍ*PeLvʹHO/fJO-Ij )sTKv?KY_]cn*%:,S) -Xz” QaE;ah,9ڳĠƂ\VXbxJYbdIcA [BRX@Qyyl"5Si<律c Yd X KDFA9iY|FAx 8h( Y`]YAxOd"W39=ϙ0xNU< -s%PTd 8! NrVձw{ ŹD*`5p5MK&*4pO)k(r(%+aXXՀ(jH-d!xʃ,Aа{kXkѰnaޒQF9 S*x`vjXpa)G  +Ӱ wJaA"n&@o50]W&Srְ wKN“@&հ`<ġD.aAཆkaʃ,>; ׀U|dBw k<1hXljX\ְN1TRbCȧaA2 @ʃ,HS%kXdiXdAȠa"XDjzY`.j~@@)" RǠUݔZelҰ %[ KMNa~pI% R,p M!2x ְ.xjXdA4aAvYf4`F. Uk<2gf 2ʼnCE &4*&4,p4,@diʃ,>9;N79CgM7@D|'5,gf䛎4,_r5,( DmͤaA!<Ȃ(~ LB txB9 @^Ȝo&u -IwF p|oHtf3;[؋*{9i1Y`Yu'Ea kfN< D=b_t vyU)k-Z_ \tDIyA -s ,pfcJV¢62?2%^s:! FFx>] 1AVuH+to$V6$!y*=דuA4{C_@*֩FQѾ_˦hc[;ݰ.uҺNm=~~?O_0jX X1>sUƖ~ *ȄfT5U6s\Fdl̥y-Wk/Mc>(<~:,m6JK3^,:F7)HQYw LˬU-0ԙaZgKH4[+ š*5݀lwkla՚ -6gCHgH}{7/cpW% '|8kc,]ߵְ3lDR,R~/0Y]-mOZvIiaS]UJ]:!sv#8#sٺBpzm-J<+J6:SE_q.le"su{:Z.*=su>>7!~a?nB"lRS$O>2gB^؛9}ݫ"_sRB(l["yR.K^gJ쥚ߓ6~ӵgvgE8ش[l1ˑs;-$JY^lE-q.t/B>qN|1˸1qAߓÌlk/MJ[=*2悗m~j/.yCnO}.t1 ;Tlsfck9'AgU[sZuU$PqB9&-<ݷ6xmWI[k5zϧXE^G]Zց'|ƌK\pW+ejQgjίh<֎>FfcM>a灖~>/a‘noY.zFΒ_X#G ^ -y-a_Y0~9\p1,uƧҙL!-Qd:H,S(TƁ[ ]4|м~͑|x1 kś?ڵ?ue B3#گ%'x䑼єs~`VPa‡|6xdwRrXbԿ.aۭvNjdz8l:f3<փɠ?0QV :띄%>_7u>%χRi#Rz)_hkֻsEߏS]%%7C鮲WŖb-h뷾wߛy ?2=+K9u>NmI94bN 4_}˼oݝOZ~sQtiΎug.Tl[><.z!OGGjuDJ#h;UVz˱#*w:Mvѭu>w淵{4 }9<pYiZYnD?wsx=|f罜N=4xg!;BruGpr!6X/7ZvmʰmO)瓶ekl(bc٢>;Khtl:!=cg-i8d׉LӾ6vk*WܞEe[u8{㘊(~p6YQTu{Vi]9I`ev\ld:#8#>xT\f{t|դ)mjd;m[\%˨8+>hD7SL/9f~7E nO^g[ 8k,$~!Ž\qmmD宥k9rW٘qwjlT4;յ.< jݝ} a7?_b}/2W8~5H*W~K6l:[mwjK-25v3~SqNO[hbף`kv;yd&.?Mol?h7 eʶ$Jg8ٜEZ5~Vb+DԌvOћ.d~ugr(!6A ,;A { &W=uAKY1Kb: [Jv4/*Z>!I!. -;Ӛ&LfY. z)E-L^*i~2Lxv<XB A8`kݸvC;%$tXaB3=INfˠ/fKk*B2I}JQ4 XJPM۬(> -endobj -756 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 367.623057 101.433071 348.873057 ] -/BS << -/W 0 ->> -/Dest (cb250-1) ->> -endobj -757 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 306.676036 101.433071 287.926036 ] -/BS << -/W 0 ->> -/Dest (cb251-1) ->> -endobj -758 0 obj -<< -/Filter /FlateDecode -/Length 4867 ->> -stream -x]K$qׯM|d  ]3-5|D2zfteǏl}VNHz1OˏNj NRbsQ?;VcذL.y:l/YEv 1UJi+[B0 *bJ -f@3(E'`U{U&hT0C'VCD QD:Ad `$ti޻(si"%` $-[%`J[ F' [(`JKd"KЩ^g[\VI:lZQIAK8%ΆjjI`1DlK `.6XzJy-٦2'2?\dž<r8_Vh;GBm1!#Faz=Wo`C1kP7~+=yG-2y6d>g@:v!DvmOlƨ:~&>XUۚ/Z1u\ÒاҜJww8m1<2vaGjfK&~9Ni7N0aZsuxu O5cg.\b֘?y2+kWs/TUyi-k`[(U8Ƕ.gq^z6NZ7n'| /{N[/_%bRnVum=l.xm8xnӌ1o|-!Iu` C25i΁Ől e{,Y'j/*ަ4%iJR!H0^ $zű -"zLѪ}7^8Xi@U>Q(_&h I%2S8e~7;`gv.=(һErR;欧b+MCm<!|NneuFk6;+)^_GlӽNu6ٜ6MqLfeTsL{blT!Va7?|9NsO6`%j!9{QYmtl}R'S/UOW|z<*I'Z,P9 Z1St~|4V6]s[Smt2ˌJ]Z>!I]N;՚&Lf׳Y˧a؀D\j$>Sjj#?LP o"eǭ8g \pcv [ 'npr z\hY]ːWdOXMT43OC*:F'ymvvw!i4Q cJ(I#!cy:ylź3\Ʌu(oNחS3]ow}w.}u>ܵeoKhgw@ -Cϊߕ{K;@9Sd% v(il7mn CLըv%?Y;k)!j_%;8N5`-!LE!C%׹?gIZXZt[o P -T;pr[zlР9?S^\*I~rNo$(-C57)H -endstream -endobj -759 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 758 0 R -/Resources 4 0 R -/Annots [ 760 0 R 761 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -760 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 157.623057 101.433071 138.873057 ] -/BS << -/W 0 ->> -/Dest (cb254-1) ->> -endobj -761 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 96.676036 101.433071 77.926036 ] -/BS << -/W 0 ->> -/Dest (cb255-1) ->> -endobj -762 0 obj -<< -/Filter /FlateDecode -/Length 4921 ->> -stream -x]]q}_VG 0dY"y0wF0`R"YJ-͌noHDl}UFHz1O.j -N_):( -䣻6L!9C^򟿺Ϻ)%o";r*ATM!.1%I3\ C[UT0* KAۭ* 4I* J+ءR("kvG{Igc2It0NK4y]t[\RZ94tl u`%]-]-@WuEy%]KH%T q3M.Z$֓6Ì l%Q[UFYBt gCl5yv[esŘ@`%0% - 2/I`B(HD;Q(iD&| -X3Z"`#/1հ0sEl$.CV %E %|KJ{ ,f* ,FOXP.$.\ t1݃k7XЮ%.]KZI\@]kQSXduxj$. .:^`e21* k" k\ 栕$ 5N kx h -qr8[@Cghl2K$.p]9 tL^'Ҥz\I{$.p]8*+q> H\SK:6II\äH\6i芺4 Z2 O*ID]$-qxRC%.]$q*ga-6 @i+i2` -IU#,J$qf)qY`0pBl$.'B>Q'; Dl@ MQ``5F`` B LI#Dɦ$.#CJ:o@ע.B!W%.@.5ELz @S$.i $؂"q\ "sIa l BDDez%q<4rIt#(qA$?PQLd`JQ[@`|r$.@di-֑1nF b-F ͜o -$.HO9L4R$o2QdMx¼M|3H\8( hJ¼'!;I:[L" 9ߌ @^\9 rx%0"2&"[)W ^ʘ3((Po *k -s$qf"^\5[R+q@ц'DCȄiA[ыٝb؟x ?&$ Cq#~9sT6}J6!n).KnD8f>;\pJ ~_MFjr&[F_~/?J@wg29bk ˺,e9MNSḩ_R̶ JQUL1qv;|.% !71qu6NsWCm]DЍ+ǿ ro4d,a~'_Z}yOܮ[6e4"wzkoٵMcXoZ3ïd fh,2&v*; uyF/ׁ{1*u:M޼rXn;n0M]bܼ貼~__[}a0d:O8ރ=hECnּ *lauyq6>g2&X\dẑ/ C46 ^=375&[{㼨Ƿ0͓:1!sz{RV 6 kaHv:@:φ<8k;H1M)wDdfL~)scc\ަ[_|;i_{ӡqt m0_߁aTw `țQ 17הh~{qFmg&ٶZ)Htsu#đ" )IQ0+a\}}^am#< 1GK'<*Lj[I̝pM#?zcҝWr2{ūa!x K;qmFl.?YcyJ!Ny6A\8F53`ٯHh! )!rTZZepm%uked1?WpxdCA-4G - m1 A,FaZc=3Y} pgdCAWnlXsnJ<8k_%n>}U}*:č'<F=x#>Wv*<1hsbZ9m=!vӡ`yEET -<1F -ee>QqgSCFg9 :φB~K_#=s3x͖Pct(;9Gޘ&yVv-#{" o̯V7>goNy:Tջ%=򹚋yrQlerMD<xyKh ,:|γ1 }yI1Gz?1xI4_xW[8ǿY*˸3s2ׂڸ#t}ˍlXԋEޭ{B 0ﳯ;뭞LF>wӡ g!+V -NܷXq/JGwf?UlQJ<;wU/׳lNy:ėR>Z+g&[HC2?olƇc?:wc&o|rGAUy:?ѻcߊ')#Y^ -yo-6QK丒=;ߟ\쥰@ -Ϻ5KE|GնX/fK,PyU{`6o7y6wϳqےzun|d9WXd,OюfzobRz(ow7Rm ގy?b]l)|dG4{v,}Iu3K-=+mFgyțo@^EV_e]Vvi#yfmc}]U.%oG4?TA|1&劁z_jN;oKW o\tzQ`MKlqM*d]rc/4sYF~ʱ;Lhǥ${Rܜ$|Vv|_Ǎjlaܓ'M&4hue]EC0^]ub%ucPݴ\z2i5ڲq[ ٱ{>pwV_cIݥCKUo섩[23u}P|.vˆ|hMWY -V!aie`ק}1ڛKۅei#> -endobj -764 0 obj -<< -/Filter /FlateDecode -/Length 4865 ->> -stream -x]K丑ȳc а=Tew0j) IGfxӅ"/R2U"!<]o?\~!8즰opW( N'Laə/u )y_2b V`97`X^bJ b@֬1(E' VkV&hXC'VCDQD<Id `$xi޻(si"% $,[% JY f' Y]QA啖x.E"S15(7hxZiEvg W.<2BN8bvɻ*%,y/!E/AvАqI@ɐ&ځ"E LL`%0 Sp* XYy ,+ M$a5$,X-A[$,[RIKX`p!qm$aBkX.{uF صkI+ k-j<8XܵZ md$,C/ate01* k" kL a5dPDo q;Yރghl0pK$,p]`= tL^'Ҡf\طA{$,p]*+a>HXRK<6IIXPAm -+ҠR8.`HX+<$ya"i ƃ*a¼' )ǛQ7ы) .$p77JLfqF1cUL(`/Us -c$1i1YF/f `VJL(/1Za˜})*u1A&l wb^nc/0׿W%SV4ߒ/5p'G0ll:Y8%ݲ00.\dHepfh/B^:_I>Gp38xod>߳zW5]VѼ_Qȣ‡ﺾ8~=\]OIسk ,☍W0  ˯j}zoõoɍ6:Mpzn4x]ƑF7zQO׷~DlI۷{Ɯ%>gyӦdN&^3MUTթMOA<gJ):vRښPus׎ɜ\؛|rnaBdllB+<,<yt'D%bM&{pTB SnuM^803}Cܷ oQFv;.fp!UE5U2EFJbr U,dMk`&jDƹRJÿ@Ny%;/ [OtZ.fF!L*xLf‰ڮ8b:n!f22e||v2*ϽJwM2;Ƒؘ_=Ue!e2+7.boڜ1SEE6E^ v1?(:b'|ē)vqo͵e4ot`t4#W-)!?"SJ/;k1ƳsYl~q_w#t?tG?UwX4MՋP\&xv:϶7ް9耱6넵2Ms$2(Z{ӤBcb =G LL/>O^LfLM_"4uΜ$v~׫ŵ#֝%RK]jڦS6Jy+-^TZ[=E=ј l^aJ9eq<]G j҂VY淵I>q}m-1YmmҼ-cey] -V}qN2vg+NE#LB֕ʐvCݐuIoBh%ȞJiWNy:.HFЦ.*B#y栕afC_~akxn>y=ӶdӮ}nO -,sZЀ_bPqЀ&W|"՘M3j;KoRʕmi- FS$:suNk=%yrL]"9#\j7i%XXpeOy:-<_Hoc#{rj?e<xO̞58,xƲ?}OF!H:OEo$aTV=++krxW_z/T/0Mp-0dqKWV7`SݛuMA>bq[p3ӽz:'|׏(~Qj0!D^5FƩ+"ȳUU?#g.ĪS9ϓu:a~=~Sicpu Iv|_p4d@ O׌ʒKdF%?RJ|t>ft v3,hb<^r4/3}ӥjm CZnPejVg3l9pX krDߣ;& -\ԈAe{!Y[ňnMTN6T6u|4[Z{%]kSuvj4˄Jjɶ I .U&,fUgXZT E,7JV*|mZð=l}^*21+C+X\U=NFKxYiQ3 MM)wf#'}Cf@SetQ 3mfT6eR/T9Y7k au~VrBNvMg.k[թ֙L]k}wNmu>ҹe:_bhIΪk'lTv3F:{!)MML_/L>[{^Hю4l%gOApض #b:jC0^]u`%uCPݸ2ike3v,6Gk xkЍ͇)WpÇy+kwh7aq-0ufbf䝴_ -b7̍ȷYtQ"p- 杦<o$; S7;ej> -endobj -766 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 713.673057 101.433071 694.923057 ] -/BS << -/W 0 ->> -/Dest (cb258-1) ->> -endobj -767 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 652.726036 101.433071 633.976036 ] -/BS << -/W 0 ->> -/Dest (cb259-1) ->> -endobj -768 0 obj -<< -/Filter /FlateDecode -/Length 4841 ->> -stream -x]K$mׯMŃ  ؆vF1k`?FƃzuV-aSd< G223ڞ ~/]r.)YR0WKl.*pl9bOK*xvKY?~sm{vK)pf_RNU2+\ -+C,EcAё 4 S*%K b²rXgʃ ;g]b.MNyD6XWc K(jY%2IE7*KA;Ee*h+~ %)y΄%dƳv M0I1)<Y EAx~4p"Znox8HAL.BXA 㒆.# \ e -\Jk0JX(7\ !TdD ^/Y wN B ,"VsQ,5,-iXBD>j薜*/g)Wl5,@.d,z K@ ,iX -dRѰhƳAtV A 2Ѱ$Tp5,5,2A Ty0a懓a$HsTd4,q5,84,mr4,( Ӱpa`r4,(YBY4eo4^,%F73o"W2I.dx]DQ\ Dd39ꎁVu{᭒g`#e*֨x>-sH9 !9,[o_|ԝc ҄ -Lw@m1|V 3eTP06X(;w>~H -AYTF90ݴ~] A9/VuH;utwu(`>2#|\yw~u]Vж_U{wQ~C@/̩gׄ}; nj^(T ؅\OVyG8Ύ(%t& \Tb1.-BΟ~:_O_Owﾳg'rF ̥]#!j{<їy.VfW/{v[L{}z賐C#䴡ڡQqq+o/1V9^xOikT5ǬFUzL3|[a|2>ڕ71vo`C#haF7.'Yt?ӿ yl=#YC;0aۥYkYx:c7@oeF++|^jg>V-M*/oexcI8ZHQ5bk zqsUڹn[b3 U-As2uQʏA|M~f}DI0h9S5l~K$W0JRS#"p%JUϗi4٧^X. D1_]ib{jcnAh}啰ikۄQqt_r2k=H+ݿ[Z͊b:emLm#z9ԵeGcDn߷o-]2=mt&pWgq-{w՛u_nıDZ_ $FhD\k;{mj1SO ->>wM[^tǯ݅ck{R(|Yq_ۺ!#-kq_(HjGW?BԖ`)N?Xܤ+-tk]^]>,Fͬ;Fݫ3//;mýJz–JްaiƍuH[>RJ:en6ٙ{޾a>YK&i]mlf . ^j-M+3x>w\ϿL++fM.TR[B&׾DyEԽ:Ğߌ@|q=lO,׊e^lې.ֈAFKo/[c3xm]A4 Sgo[cu>89c3rY8mۏN>VYxnhwGỤ̾~ٶ_ˈ~Ǹ:f؎ArӾ:κnGw,a~',`T',`"_b#(P}}OgvѤujEgho({:joG{[{9kQ!nWr}_{{V)=~SYcu>U1~mhRZbM}60g~>&ETWOf˶aJjYtk+bώ1ȹN\;fwٙJÛ{ -u9]ť&q\mSe>}/75ٮ?vp^`gwb/+~нRHonK`oĢ;Qoϻw,"|·ͷZԈCU^ A^L?>~u>eZs;)]7h(L\0etH:=mãrspsf.>*ũ+cr3Zyg;cb{0'>xJ#ݷ:mQw/\~Y ~ls5Vr?mlexF}߿wSk;\g>GiYxa*>z%MT-.Zt}Ѻk*9~1N$)d2W3";^ 5-e_҇Ŵ q~paB DHc7յ̠y!TK 1O -rRߙ4a2_s7$J/.'\k-JTUKe:vv($>M^-_smw ^Np1t ;+L'^;L{Ԕ4;WSX&GΫ A*I@4`)ͲB]6aR_ ؆*T&txlvX 3u DӅ@w)ېa,`Fg -sI;Ir3AL?w:6ړsd3A&yJum߿Ey鏧 2C':qgZd|~~̇wX6H$<ˆn Ï;'fu3AJb:d7LY/4n/;-@s3zЍTe> -endobj -770 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 483.873057 101.433071 465.123057 ] -/BS << -/W 0 ->> -/Dest (cb262-1) ->> -endobj -771 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 422.926036 101.433071 404.176036 ] -/BS << -/W 0 ->> -/Dest (cb263-1) ->> -endobj -772 0 obj -<< -/Filter /FlateDecode -/Length 3605 ->> -stream -x\ˮWڀi>/$A8!^YHcFp@"S=M+۸I4ͰjTˀ*Wk+ -{[jl -5ޅSqZ| T\iK>>߮?mp^T\x6T *bvDΆ*KlR .RU`ʖ -fPPUtj0#@ -fP;BO 2&=[\-6SW %Z\.8Xr\-n>X:--jt-d -lf*l->`Zr*kZ.zv\S.f2uQX\ ]-s3u.ҁ'8Zew'cc!S[ [|`9%b)Z$bM*UbmJI Ǝr+$"a S BعF[Pₔ`KdqAbqAݒo% 3 j& (Pj$pnwZ\@M f x7Qx7%4uR6`Up-.V\[\@X=Y\@XL]q؃F%XG )f f4dq:sa `+j0x7T,k.̸o1.,.`.Ujq8F <ؼ E. 蚺|W0+@ -GjqA½7 2xsJd'=-.@\:Vҁw/ iqA."G r%JCgC-.(e:B,.@`ZjaKa B }l\` "E d6" -gcUKtm*tX\P -9`qr)W-.; ,.4؂bq\ At a A j2$ґ}GTp(E6l Bt?rY-]v>Wo|?夬6!6 ͈.?i*˰Mp=fVz7qy\l1ɺV$i2 uRG"IOʿ}s4W+Χ̇DKo>ӫΛ{_I'}qݖQ3VI~׶b/d[>Cu]}1&u /x?_/ǵ^]ӯaCs?yuݛ-8t;}`*PӾ@r]*~JMo_fYG_@Nc߶u>o]W}>sƵgx -6䜽B׃m^D;]U෫AWSƻHci#U.&+Lv5Jwyq7f{8^Wp Z[hع.|>.P~FkgY0m~v;n!;p#Fcm^ -oV募aG߇< rHқ({͋CٝZ=Ssc[XE_q;͸m3X1ɨTgX<6/ EvGJԫ"ؾ[AWϵjF«yNgWz!<'CWx񋬜eKyKwmMQT<švWmEZ?z.+ Gos-is*'wHg;*WШbƎkx@P/_E+o}j Rh8NXp^ugw'5ػӘt/ћk|yq:V(fgWϾۡA<ռ)wGޤOo'Q(3lPĂ(,nX bÕ||b9@}9U4nZLe~ }=WbEq!B_>!N|yo?t -smgŎ3x֩L!}F`;}}HNPtlxGذcn|gǚ89_1&^b) .ʡbޭrg&/o鷥嵟Q>Ky|-#BjEy?/jj qTnj7TTyJB[LM -k [穓z-Sޏ(u~_}Karoulek~ K񐗻rՅ(39ZJ;' -}2x`Qk}VrABUX\!4r2s=~ Stb"\^qNھfbׯmtܯFso&ۑry`C9\ X.Ӕ TeVi}݊@_k_nt ӁQ'Wx¤'^T~92+T?S0%Ѐ=KsٛC$-σuȚ@eUJ7 c6R5eJ^Z7OHjVX(J- 7<O;ylU;~8|2V?<%'z$,| W{lh}f͛ip K-a9[FH(%I[y\4؞--l -endstream -endobj -773 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 772 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -774 0 obj -<< -/Filter /FlateDecode -/Length 4008 ->> -stream -x\K AH !aܶwxsGuIbU{=c3"YE)-~8)L)5':>Ig|r<:KDWSL}Nl^Ԛ?2%gV˺b49VrCUcAӞ5 *P#PvaϪPgG jrz8oʃ"(xI0zxޙT*/x!EI)ŢjƋ%:" 5^.!/9h ]x5,]5pj5,] Qq(4,@~3uU^5aA 4,:TÂEz$஍!hXP<װu x[%QkfXwUÂ崩aALE(hP{ R!SsNjCɧq԰ [" KAʤa -kSC-d]d]P2hXT[]@> JQ )HÂcKޔ Vy<5,ș RӰk)S K@ iX+tAhXTdGetAa*]ӰxjP VjX $L:hXP(.5,@` Ty0aQ,~2GAIÂR}v/F Lc}l> XMrAe!t-Z4 X{㚎`it.-tԓ ?XtCqʎ$fT9մfk_"Ku9((g= /n|K/wTXXbٯ|wgAv_y! _5`w{ɹ_M5_v9g<|O`+8|?8L#|ȀN8/B.V|?h?=jЃ.iDO9wML\dCM7 -xzʏos`r~EON,kBf6OnƂ6$=zv٠~ih4kr~=im6Ň&t?kbfMݾšnmfĞmҢFZ0Ogj@þxoطsТ[l]#x{I;BcfqE7&Y*m7=-m8i9݆͎+\#m(vs93 -{nwچat8mUjgTMl˝7c>G~3[y?WmTzXt_hE9Mv[視WMgDnAMEGZsZI`MF6]~Ӵd^Ύ7a|w+qZ{pyp͆Ɔ܇KLuD>gYkO4q#}^y#r]3YDzH d};e_@,)^z^yhWmw_=;~XGvo=*#VLG{5a~^Q*#oX\lv֭ _1ߝo>Ho-:!suiWe*ltבzՆe;{rgb&zou܂Hz&_2?;4o\H޼0/_#Ϗ};E|ώ}߼F2OtWjc÷Q2%vǺ.2s쨀DoghnDn)b5;,\gw /ġcO]ō꽱/v7}Zl\#Kz<7m -blsE%=$=ﳛ}$ew?c]ܟqځw NOmX#-1*re{E!w9ks Ά -v6xX?O֗;T"n]E!_!kl  Y(zjKhai9y頱 V*.r'i{c6H/.&DǪܳwҨhP|vq]&r1#/4YǑghvolZֱ߱]8#}ncH#!1!E\{dЦbw -\ -jMr}\3;^8ːZ^`yM~Vqie m$?AzRDxmJ.d._gEbc i.-"LnO[2JL]gg$eg'.XA{M׆$ե霘.볘k݆-Q#нn]o-.9&<)$cG|c{ӄ|1k ٙX#ѐ]N!Z3TntPIT߮"bWAXsm#H1#xqb$1v/q1B1{8<틣R(+%v%$ʏ+3PΒGv>Jr3ȡhW|'Zb-]N&ۑfg8(LF:Љҿ 2ۡ9|gpyϿt[ǽh2Kaʍd~IL'DO'ٕ)7:x:5ô>9'h+ ș1K ZH2O[:miO.@6Z]F\T+QSLoQ0bvnxZ -ҝ, --ɳd}ߴgۣMEҬL<-$ -&vԻ5vG\Ob#Qr=[R%S%w˞W͎_F}!POV}Hzkj7ͷMqyȯ \~O.Py -endstream -endobj -775 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 774 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -776 0 obj -<< -/Filter /FlateDecode -/Length 5464 ->> -stream -x][q~_V楊`# Ƀ9u[(bwΈd%Յٳ,)| WJ,JO|6%!fv1O-~ߜg7_%S,c<8(YxŜ,m"ؠX\Rfe%- lQɲ|XgF wJ!ӃRvY͋ȳiy!e!I#X- [")jy^\^ˋšw +ycΉH3)m3mӗ  8s?˿~B_NBOp2sQ$jgL$ke틽H(eqޞ3}4O}j禓 rSSc}ʧ(N`2aIbg$E;ܞ4O3ə!IփQQ-8Z=Uj~ $7e6 o}2^|6/;YMgRY-l}4#l0= ?gBt-D_ک~lSR+>)NLuGlyA.+_=6:@>9 ϲ/{Ǭy)-K̺83kn3_76wxM_}IX_W}8&:Z*woC C|AWKwOŸ.$g1ne`Ps>N[N&|{COtYV|-}s Ɩᡱ:ع1VZMm T3.[K5.<׸#ݲױ%}/;2rnY~rJvzuY||ni?U,om`dtMkMV}$3LQvAv]}"yNX};瘔FQsi[WB-=T y`ֽrjPQrqSIUrLӭS4*kfD@yi@Pk6~=@;6Kʱ4 yZo*lZvX$Dsjܲ߻Ѭl<^[{͉8>gHchComI&u&}ލX\c{7tC'z 6 3ə$WGGѵx)I[Z궖yѯٔ}-6}`}t D}4#DQ٠}kŚ' 7Խ%ʅH.yPN9p&nyP{G|5:͠܂YqI4{1r[ۻܰ`xWcq}J9۟|^lvxsuO(a8.ll XRh^,cp|I(ܞ}43Yuy/&RkrܦUPL73y'F\vŭg -rFSj}$#QՉ+ERS -v]4Or˙vr|lp -X^W{ь-3ݛg*KN'@=SukKoߦm[ - -/r Noy#rÕ) F;5:ElhԚzߵpCge C +u1ytr&<\0qsYhAJק;<#^1qK9-l[ۺCꡝ:7tTM}Xi|}>;VAƷ\Ao:<+Cf&Ppn'\Ȅ]rwȽ9{wCe_z?xz8NlA\(w`woKyC`vv:3v5,[f0ZnC-!dVC7ƶ`)>Fbʊ(P --;W8&[oD&9ď/Ԯ sbe: Tf8o%^Nh֯STTԻ40k*O%P'%rR3S0loFMVrML Q-rJ外k:RJ3iz~feuj+i(lܐ>C,ֱ6Ibh~⨔+ O&ޚ,/s׿054փ -\SyHɪ47"s&/;MuHKq.tl_6n-]{ltY.7lתCeRW¦X& 47'sE'ש*cbswN;XGw*FKQlNOS#sƚę1œ<{IfkE'vsdƽz*j.x+ߒk-/{?u\3-\Erˣ3Yɞi5?'4Iwk SI[6>l]]3|#j|tlf}}R|f -xmY%*$Eg\r !J4gl@Ԯ -ٹ>4f<9f5V=hC[1ٶѼGaqY -5M/&T__vZLwZo枯F<5fӂ6i& p(MiF'EQifJ5Ɖ0MR8M1inGv"6eIUkW[qۙd%ZJsI?mۦeۓ=7A3#aLLƛ#sGVVjW#6͟K/_p7)`G8#&\r76J2Oږ0yo|T>~)M'F}:@ 0W37cWQ.1䓱X5\T@A~/B(s0 -endstream -endobj -777 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 776 0 R -/Resources 4 0 R -/Annots [ 778 0 R 779 0 R 780 0 R 781 0 R 782 0 R 783 0 R 784 0 R 785 0 R 786 0 R 787 0 R 788 0 R 789 0 R 790 0 R 791 0 R 792 0 R 793 0 R 794 0 R 795 0 R 796 0 R 797 0 R 798 0 R 799 0 R 800 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -778 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 766.923057 101.433071 748.173057 ] -/BS << -/W 0 ->> -/Dest (cb266-1) ->> -endobj -779 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 747.976036 99.933071 729.226036 ] -/BS << -/W 0 ->> -/Dest (cb266-2) ->> -endobj -780 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 729.029014 99.933071 710.279014 ] -/BS << -/W 0 ->> -/Dest (cb266-3) ->> -endobj -781 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 710.081993 99.933071 691.331993 ] -/BS << -/W 0 ->> -/Dest (cb266-4) ->> -endobj -782 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 691.134971 99.933071 672.384971 ] -/BS << -/W 0 ->> -/Dest (cb266-5) ->> -endobj -783 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 672.187950 99.933071 653.437950 ] -/BS << -/W 0 ->> -/Dest (cb266-6) ->> -endobj -784 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 653.240928 99.933071 634.490928 ] -/BS << -/W 0 ->> -/Dest (cb266-7) ->> -endobj -785 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.293907 99.933071 615.543907 ] -/BS << -/W 0 ->> -/Dest (cb266-8) ->> -endobj -786 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 615.346885 99.933071 596.596885 ] -/BS << -/W 0 ->> -/Dest (cb266-9) ->> -endobj -787 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 596.399864 99.933071 577.649864 ] -/BS << -/W 0 ->> -/Dest (cb266-10) ->> -endobj -788 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 577.452842 99.933071 558.702842 ] -/BS << -/W 0 ->> -/Dest (cb266-11) ->> -endobj -789 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 482.717735 99.933071 463.967735 ] -/BS << -/W 0 ->> -/Dest (cb266-12) ->> -endobj -790 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 463.770714 99.933071 445.020714 ] -/BS << -/W 0 ->> -/Dest (cb266-13) ->> -endobj -791 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 444.823692 99.933071 426.073692 ] -/BS << -/W 0 ->> -/Dest (cb266-14) ->> -endobj -792 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 425.876671 99.933071 407.126671 ] -/BS << -/W 0 ->> -/Dest (cb266-15) ->> -endobj -793 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 406.929649 99.933071 388.179649 ] -/BS << -/W 0 ->> -/Dest (cb266-16) ->> -endobj -794 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 387.982628 99.933071 369.232628 ] -/BS << -/W 0 ->> -/Dest (cb266-17) ->> -endobj -795 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 350.088585 99.933071 331.338585 ] -/BS << -/W 0 ->> -/Dest (cb266-18) ->> -endobj -796 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 331.141563 99.933071 312.391563 ] -/BS << -/W 0 ->> -/Dest (cb266-19) ->> -endobj -797 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 198.512413 99.933071 179.762413 ] -/BS << -/W 0 ->> -/Dest (cb266-20) ->> -endobj -798 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 179.565391 99.933071 160.815391 ] -/BS << -/W 0 ->> -/Dest (cb266-21) ->> -endobj -799 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 160.618370 99.933071 141.868370 ] -/BS << -/W 0 ->> -/Dest (cb266-22) ->> -endobj -800 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 103.777305 99.933071 85.027305 ] -/BS << -/W 0 ->> -/Dest (cb266-23) ->> -endobj -801 0 obj -<< -/Filter /FlateDecode -/Length 3653 ->> -stream -x\ˮ +`zXE@0I#d#YY؊=:'~[]x%]ۃU8b-#ۀOd%Y[.VH򢡦&1\\͟}pK)=TK.9: -vTKQJa-CDVeZSXU ZU# -0BGD@H $=yTj.CrtK4xx:<t"\K‰K,=]TGWU\P*/ZQZI-BXɮ; -HeEʹgFL<KY\`= X('%b΋( ‹) Rə=UI5{<#&`QIpuuU<.,hq3Da l+ t+T  -&y\`\.I<.`P.\z\\wz\ ]lquYSA,%y\]@x=]=.;. -{\ ]=..Q%Bx7 3B {\ ݨ/rwR@Qb`z\x]d 0x\P= ZBsuu w- -Eb  ,Dqw#R{:n<.P.$ -ຮ.TK@qBLG -BqA"W x%AꀅKy tضΞFPSx:.qAZ eq.ȂRsNJ!suiz\ e:`, ^*qA1z\# eRo<[ SL*qAքz Vt).%]].d r8x\Zj)K<. x\+`x\P`Aq2]BD`A6qAUf" QKԞNqAXq *M0ЄX+?(6Q:`a JVn JH՛JJi48tDPPoFqAeBٷ՛*HQ\ iξ';y,5%7H3Po"w՛=.j3y:.2q.Po"j{jF~+U=1 P"GE|Fr eI*c"+N8>GT 3K?|>O 7IY p~d ZD R06)} Dd-nn Ć9 YLyQ),'|!F1 5 @=>uw2}6"PPP5Q͚\Ǻ|5zA_EW*U^Xn/ Վ2,-?Yx‘>as6{Hej$#;l;_^W:Z1y-o/C]e L+Ew^hbV%ŽHpgg7=,.MT;ۼ&5/k>Kע=ا%F.O`fd+P[4wy -,qc,SQ ^d(6m7 -6eK6v 3k sB$2*f/xGS*V0Ľk];brgmٻ.Μk :zkoN -zq{G w ps7ysIn(=Ø -&=t]\ls?{ͼ>\ |sfE=Ot2Z[=z Py/7ӖwL^ʊrW-p<s4oXXt]"Ms5Jr=Aߵ–gXo`\czr:Mr6^m(RYÌ/[}=#&ʾqgg. yLv5_.\xͶStKgKX3vn<"exqs39̞3`Um9lL&;ikNJ/6_z)ܞq}}s]>4O6}ϳS==VڛEC sɝspQC7W"Bщ>st#T"|7sUu2VkμL ? -*MK}n[v^fNuil?R~< GSCIHB,-]X\ھ/A ->s2t.D -?-66*.] mG,2 ǒUH^DB,w9kf}BO;BLZlwOKUP45en;$k!M .}!gӅi[ۘ%<0-_J\fmfH]ڥZNtpRZ]?uHnm4+{2fe:nxGvl_xq[ך7Jx: ȕi+HBB_4f*l&7c3Uht՘f4Sg,$Bgg{BN{#޺[l'L6sm:yš{]5t@`!O;}*R]C:w>W<ثow&XeRѾΖ]1P?; -endstream -endobj -802 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 801 0 R -/Resources 4 0 R -/Annots [ 803 0 R 804 0 R 805 0 R 806 0 R 807 0 R 808 0 R 809 0 R 810 0 R 811 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -803 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb266-24) ->> -endobj -804 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb266-25) ->> -endobj -805 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb266-26) ->> -endobj -806 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb266-27) ->> -endobj -807 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb266-28) ->> -endobj -808 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb266-29) ->> -endobj -809 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb266-30) ->> -endobj -810 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb266-31) ->> -endobj -811 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 605.596885 101.433071 586.846885 ] -/BS << -/W 0 ->> -/Dest (cb267-1) ->> -endobj -812 0 obj -<< -/Filter /FlateDecode -/Length 4594 ->> -stream -x]K$ s+DÇI# b`flM.=OE.R"?R2-~A'3K|<}8|z kYS^, 4^&̬ -x69L[Gdlӫx֓ Ź*`5p5% \Jc \3g \.S  ǒ4s%pԐdaxʃ,A4а{kX kѰnҰoR԰p!հq}a”끝x.=iX>DazQLVz*5,:OkX]O6iX]Ӱj`Q؊q9[ e BK>5,` X.Xawa  w!AO V{װDÂܥ4P.QÂܥSyP X4,]*aA>x4,]KX pyCа` o,LWcK.`iX(lld`HaXD.{Ѱ wm^ÂܵGAk*>dXx]Kaܵ6 "pW¦1 e A4,MI)jX)ʋAÂdA,Y8HM%kXdiXdAʠa2Sٷz<,0|@2 )DǠU p2x4,H B1iXpz F% xY* 쐙k<,H5,@ AddqʌVDh%jVΙYÂHa'M ʃ, ?r&9*丙5,84,my3iXP,dAƧaAHa`+ t$?Xt$aS1!L(Ⱆ>LM(&ԩccMώ8d쬝C^tYo?;g?s(qW<)bmٟ}vOuR >;=rPhJ!BT>ORZw˱ϥJ su>>e -}Ly]Qtw^W[[Vame˼mw}wH>o.kaˆwloj?'\{|r|˯,_ZK?z OprZ#> wv|oi̓_~r2HDg,W_ЗM3/33JDg,faJ{xߕ2~kqYy{hf*oֱhrVL28o;ٷ~F /_LvJ;x (hW%X'wI`ɷ[m#nU/ɇ.or?LPǡA{Z;^Dcg 8Oc6v)zyṍ<)ϊy6kӅ57]i26n#Su[?78ty`)= xm>Oy_^;SW4Fs>uLٹH<.rjVDxUz޵k"w_n&8q۶'Pnʝ}~!NG+#'\ WY bOÔoCE?i=Oz;$@\nid- 1g^lpdgH^$N;|jR?vsQ8:>btBBmOAi^Yt^hLhov?UvBh2$io[1@ -[^W1ُX$Q$ky]d?N$>劉s.JBk ;}>\%IjG$zw>?AoM'~*W a؜Yj^{yoV TRI}Q$yc -|G/˷x]˦I`uҳ<]Hn8q9eK?;Nꍅ:WVo2ӔD](l}NRI:fV@wB}}~nt<%&_E3M2Wgu-k'Ԯ1̗nᏓE2nͮ,?Obܨ"+9Į%^j%l+YM{Aen[߉_Ǡ !2 Lo9}}>v)򔦶0X)6e$\̞ͅa?<-} gIu KZn2HъX_ -!8@˷Z~ycT)76rx_Cn-w 1faC%u|?[c#OGH>)y>~ZV]P^E|BkKא|T+m fmOjlE^LOtY776o -G.M 8nH7ܰ]RÐ?@n%St'U1qvןT}zRvMtv -s֎zwvd;Ϲi^\>+hueN?,sO -__ChkmCoxdxٛrJdMUtгYCwcΗʨǝlO5,$,gf>}8( їJnI^>'"á9@'y3ߜyh5~~#c8lG ױuE#5I6bwxA<چf =;75v{kIAsgb:Ȯ#?i&\!6Z̏ݛϗ-NJ#&.2!8 +i:B:즎4a'y -)uS!~xyF <0'5τ0M$g]0m4T݊UЀT_m]H/M^,/MR⪄Ro -endstream -endobj -813 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 812 0 R -/Resources 4 0 R -/Annots [ 814 0 R 815 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -814 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 563.554475 101.433071 544.804475 ] -/BS << -/W 0 ->> -/Dest (cb270-1) ->> -endobj -815 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 231.360432 101.433071 212.610432 ] -/BS << -/W 0 ->> -/Dest (cb273-1) ->> -endobj -816 0 obj -<< -/Filter /FlateDecode -/Length 4418 ->> -stream -x\KϯIV>HqBr0rX-*C~b7];3ZYrvgbclşvJ)w'3EoX]wl ?)fb8?gs9:ӿuM9g4 -+e,), -+ CYcA !5`J8Zڳ2pѲƂ6 a&4SHei<)Dj<|x Y|6Vy-x)E 2*IE⠝du%YL0Ve|N*/gRL{3~h`?j*/g1jXԔ' 4,Yְ fWѰKє"sg! l gAD$ FKB3$p4*&4,fkX6ܞaN ߕ3];elpIWT9Lt_,)v!+mE~cY9O3|]O\{9zW踎eEvlS"Ӡt\g1plmciSd)})[(nl}ˋ:[EM&^`iڋeionã?a=X$K qcK.[}Ubgԥƾt~y28$wxppZ]y6PNkxP_l~ʷEo_6%ݶ׿Jm/dVHAЬ$˨Iy}8xeտY`ҳg+i;tǑGyKRanCpMMW{ҦQ -.hm> Q|I"3̯}b[ggݔr"cCPwΧ.3ĘDhPjeguYS|ǡ\c4WN:kfWd߇kNw!l{M=:ĮUD6'g<8DSzNe*n6-aqސ&0%CObF8/T`8mF` eܦC&h̚RHO͑/ጛb6Y:]ejt].Gr .=Zq-< h4eTqZ}fֵJ +r#h# bEl`ހJ'W(%u&y鳦=͑8siqN}AnErϦӒ{fǜ+ʭV@:T;>ZB+nTo WZ{hحձo/YUؓ(5ӬjL*$ӐEOn:dQjGsǪ|n/Ӎy/,ߖ$a4ܛ_2-ԜqJ+L/qo}H}4۱4U 5^}u: inJGoIGl| r[ -l=?D^[όp"_D;t7$ݐȿSwC"3 ʃ+u>5uylM|X'MsMx^@1l7t݃q,U w_2l,FT^r 2?By̒k9u>Wt$pv|)!moa3yB -Y]@2f$h Ogls;%yLٷqok4v.Q}_8 ɍY!C7qK[〃u>m&{ Si^u=8Vs'k0 Fx[z,nS4TyOmjJAܨlmI!~ijӌla=31UCV.r -[Zmb+z\5EN)^=Q^8uMs6& vvޑN>*} -DmdtjLUUpJ QyͤMw"k%P5 X.cQ_6n+4*1WxɶY]# U4 -:7S~Z7`sN ;Frl3nM`X6ޒSj>(trѧBI^UXv'Vϧ9N2Q~Ԟ2'>[_04p [Wq%wdya%6dzY_ xͽ^KچqG:Ȯ4h_ >n`ϗT'7yF -pp:|ĕK:솊a;iy -!K> -endobj -818 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 606.123057 101.433071 587.373057 ] -/BS << -/W 0 ->> -/Dest (cb276-1) ->> -endobj -819 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 254.981993 101.433071 236.231993 ] -/BS << -/W 0 ->> -/Dest (cb279-1) ->> -endobj -820 0 obj -<< -/Filter /FlateDecode -/Length 4393 ->> -stream -x\[,m~_1TfUnI`!" yZVd?cMץ93=sڰv "gڞ ٚK|~L -jMeΖ8`K|2_۹~su{vl8Ga7)DAazIɅ5xR4Y bpAcA v.+ 1<'1\ -!),K:"A;gPzxΚ+*/gxޛ1BV,3i<>'!Tdq9y vː֕UdHVoB*G9=Q0!{OZ`^aGabRxD -EAi<Y4p"[nOjYK _C! Av\0d8@eo8sPb8%+p,IO @,Y8M%kXdiXdAȠa"S,oxY`.! "E d&f R8A/:ZelҰ %6pVLƦװo$\ҰbgYÂT pE&;DB Z ,5,.Ixh%j$̬aAh$T԰'M ʃ, >r&9*丙5,8r6弙4,(YiXP( 5,GaAM`_y3kXP<Ἁ#orL,!ʃ,oI8o4^,%F9of f༉^M d9o&5] Ȥ񀻈Lyv'oHtfgV3 jʀVIWHjbd5[Ӓ6 /1a%4"!g$Y-}?sfJK~<ǿ>f? `;K 2u<Itk[EOu1RbZv1p˹_صАYgjb,VG];,>ibWT)5+;B}/ң}[N.mARh{O'Wv^wo[Zϟ~:ݿwPçϧ?󕕿M녎\+!iK[K](?~[in1oqYƉvu>ȆyCױ^8ˬCQ[始Le:Um!\QAE+j_䡂ގvzqy8?X3#T_͇E<#Ʊ?ǁ/AX\SqڗcśrtMRuҏFMRŢ-S^묙l5}4=KNCOǚstic~\tܞ5\>Mխ&ɸmlGY[7 vWϰ=mc,c,B[3GгOjnVu[iut"."wkgMY$뿒>?ɏ OjgM೩M3{SwaI 䐊LslfZOɡy :\'3*L|e1G_C~o|},JGZt ;Q3Sz=JJc߿>ߓ@N!\wZ6ZP/=Kuw'6.{R8Q!fM+{ S 8뻨22yS71sq=sqM6dAf -LmX_캼^GLk z׻@w׋QbǛ whXck0_zڵv5jx1)||cf(Ϫ6K`}DՐ.n&s 7*>l7b|rvȂFUykb[|6+,OcLWӷ|@<ؐ.%>g;]b#\A žc6;maz]a ]/sd3ZqnGfQ@$mM SwͰ2.5GG:$=[W"g -؂ty /ֱ=45čt}stOU85Z]6o9,X`l&+gv|rݤ>2[tv~2tFi*qo GK5_GR]ˮ鶮 5t7Jt*Kv-__8y4MάW O;TokA?~-h/#+O{h-躾't7ՂT zRwS-)cLXykA`7ӖZ`ws[R5;^ :#\ZZŏׂ=7?Z "׿t-HSZ>g;'-ւ)?\ "_R zB+S-)L ewԗׂy-)]N /U *֛Rpſ`-h=}w\p-`/BοZU-h=Ƣ[-Y2y]7MXM:gZyE?7$r*IYzMu.\{Yz|5̌svzОa?bo 8kUZgO@t*۞/ D^vY\deS_D]䷓+dQ -CrI},9)ۖZ.GIrB{Z7^/Sk7[/+DvOG\.vQ$e܉c@ێGǻdi"=Y\뗥9]YuvZ֥i9o_Ooo*UӆjEh~tjh-p_'zR_Q??B͐+Bz=B_[ѵ4Q^m -N{|\ךd7nG|=v -IiVPh74n'g2)7Uak6|\~_"t OMJ 1$7;y;갦ie봊l&no5N*4:xɶ[]' 5tԄt)Cзj>Y> ǎo39:.owF|d1&dGۍ& 0F*֎Nv96q_O:U7|pۭ˞m:wul]gO&BnFf":`mmCǝGwZڎsgb:Ȯ~LA|h2_6a_n}{8IMȋ8TypiHIe7u<(n ːl%uZfGl/ ܹҔc0q%?gIZd a{JVFϘjo׻R1(scM$GEy7K,Yss -9ӗ -endstream -endobj -821 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 820 0 R -/Resources 4 0 R -/Annots [ 822 0 R 823 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -822 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 642.273057 101.433071 623.523057 ] -/BS << -/W 0 ->> -/Dest (cb282-1) ->> -endobj -823 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 257.184971 101.433071 238.434971 ] -/BS << -/W 0 ->> -/Dest (cb285-1) ->> -endobj -824 0 obj -<< -/Filter /FlateDecode -/Length 3985 ->> -stream -x\K$ szP/ !@ĈX$#ٶF0`琿*=XU5$^N>QGRUj3 -9SJ͉/?]bw_'ǫMt5x!\t_K_]]5y?* -&mTT*낢cRTLVM1*5`EQ]8*`HS1+*gykUX&IygR ^Ӆ`R&&#`:M%:"逅Bɚ.KH:`%M:U`wU,6Yj0"UW%hb j:LoUEJYy`I6VU,1Xh:D ez"xI _cQva^8lzH`PXj(рPY`tiD,DJ,%TҸ x`A BOA%xtK: K.`Z 7DP.\j\ܩqAbg X75.@%i\ո!NU,p` &4. np6k\@]l#qVKxKxgU `и>b -Zhpj6D=q:3i*ŸVƕ4.]W|aqeƥT5.]qA>x5.]5xj5.] QqH4.@|3uU]5qA04._O0tJߌͧZߣO'mKhukv 5x5nm]ڎc:ڍ{O9~yG4٘'y v~hEm}nkly׆hm(ׯǎ[JXޯul,ۏswVwI+.vW;k8:ލ2_"򃔂T[5w&$B=#~o(l~a}:0qӇxS_oEMۑ: -G/^^ ܊p+}3fE/!HTܔp-Ԗ QOoх7\@m.:Mήwܲ[9>~;ͷsp>㏭wNAؖtDVj1z5o&FVgy,:W~sDa |Sz}_ytDPy}=v xg{r}7xz˦+uzY]uHxZc0=b`- /8no/}Ͽ1bZ,`ɣ?EokOS'Ϗ,>fŎ]GIV3\p8tͭy)E_B?[\>nQlwN%ͼu{"Þ6l1gm~NK%\{ڦb\]QTs\ -_]}S٪y.6qGd)dKMl?._4"EL,̕vqzlr+3c6| `dG^V3gobV1_ %!ɶubƳЊi4?,v(}RհS:q Bs?kbNX5~vH4N.j[+gn rPM}* ^9\k[vA:.qeIQwSakoT}p4]0$iipW[a.Yi/WҞIwIɄ<ϷϘ&ynz3 LB;@`%ӕv3έ,9qirxge h ċFxN]qm2-.?\Z!z~A]6_~5޻⸷-֝XF2lyD;s'AKj78kZE죥 V -㲡axGx;Xq&26+`oaL~c{….҅K\qҡ%/nąb`CA?ɥ<i_feCf! BvLNZwx>z;4vK'O铔Ήt. 2/g ؼB ^I+݅Q!- Aiv@12;d<0~0KqQgN?HKG*ӈQJ:~GěR Pj9sɢȒ{Ji Cvch{Ӡ$Ԯ߇Iji#o Pؒ88.y=OΧ$D0͎ej3mժSzYCh!Ѽ\*?8-ml7c -endstream -endobj -825 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 824 0 R -/Resources 4 0 R -/Annots [ 826 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -826 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 606.123057 101.433071 587.373057 ] -/BS << -/W 0 ->> -/Dest (cb288-1) ->> -endobj -827 0 obj -<< -/Filter /FlateDecode -/Length 4662 ->> -stream -x\K$9nDJXx 0 kwaTGD2 =5ՕAAQ'M?ԒɻJɕS6X98,V1R׬1JXc%fUK`1BM`9BAL2-^ .KB!W]9cȒ/AŃ,LR,^,ɛ<+%B; duɃ,>`*TUE\"oBp I&MEȒ}&$daX!Kl!\Y! XX@Y"eXe_ed0jas iatRK[X]"4ylaQ|phavE ܍Ƃ#$ `ݘ|c?ތdka{"YX\DXbaAi R g 7Zv!jaA" p)NhaAIm!VoaA"nH\@`a7; -,罅5/5 *yH 5,T, !Ƀ,$@'!KlaAYMaMDfI@4,f*wf p|{o*lh)fzVd8Y3_̢͑Df)٬X3xl -.էDag]d[0sft٥>~>}MN -nNJtB" dAdz `#U-Z۞lP}qmoȶP_,drJn%wJ\jjO16*ǚ: ^::tjh{^hekEzfmCe(ɚ>tE$mh#j2 z6$ bCGrʳn%6MԹ9Ԏׯx;5|}u3_9_x/+^:;t7}u3{Oȉg);Iqw-iv{ܳs?zL\ポ -*x7o -{}l>_\֔e/j -Ck![| -9M*LlwZ[Jb賝O-ҾӗNvKVvҾ {t~q?~1xoߠ%qR3}߈ڏ.4WɿݐCrКO:] ez&TyXHYԈ6j}jya㥰NOh[UЛŠQ˵*~1q~~㔧mDc7hko6Y߄G=X//E?usin|@A˩s\֠?_I[Nnxv\Z8\6Mvyി06ꝏ]S_6Ëm0@ϛ~my_|C;WZs.ckЇl{aA~6^\F!hËW~7=ZdY} 5C7|낙˞,ZDA#e TIOp*nY@ (}>+bE޻x>$Ռ@iȫjH䟿ԏo?>K?Ƒvs⚝z[a o9؝hrZDvw.˾]s5'|c6|}(u8ڄ8v3"oc4.T{kEF48Z۪RջIIpYF2FEN\_کTc6:3㾑w"={S[*0! AEgAo"3vbʠ4[s%#H =\mя=˭!Kև&䅘]o,]DJ/=C;rMGsiL -9Z[S ziD%i˜òzkxk\l3P}yKm(#9?w`A{R3×%omUm Ē"#˯m@㍨#> EʖJb 'w`VE+[R%K tpJU 8LA{*wR S`s{g? qؒ=l )u@êrjXL%VUTZŮ֤U,*T)߱'OK`{wS)U}ӮEa_-"EQ4nmXǭs_\hUj;':.b,w梷 -㼯,^nZ>|=vɭ(mഏQ0Ens[VN뿭XLM-S~ͭ^k }:Ovd_pՑ~Orv0 -MyņnVb.1hOS( !P+i,2asg)laviiw̴|]{!oo\_:W:{t -_b8yR*p Cʼg(q? g[EoDZ8y S]_45ԇ(߁/A}>f\>dq>DM(7̩GJ n/fN5㴋!Gg a#ɞ3\`l_ie[61$k﷧J: F45iYɃM-RWi "9G,}V6_7;hzLV/[m_~`[ԩGlo[rKܟc6-77",/R_Vt)SZ}#ݛz'u);ol/HiA}mzm'qrO|#KvZd= +qXFi2Q>Όfjc'o/Dᚬ.ld}G8ڮ%.3s@^gLJ@~!k_]˓8D_UmcYiH}3f>T."NE:c h}E9ˮ.Dģ] lNJf5?EN2o^Lї.>ܓ0b7zWvsu4§nz+qYI-U4}:^@ETE!0)}żo^I+=aKl+2lvR9h=4.*[vxaX +u \ &9 S~ۑijcsOcI;Vr;u%C1b6>O2яnN`I0[:+d։zsR`;SзoW8|<9@8uG^O2}Wo+u,Ll*˼g/N h=AtZbх* r&ŀ |K)oݺZڊR1ŤutZwe(1(\l9bI1hy=<[R]i{^S<#S?;cNVӪ#A pPk0R{絗!-,<>'_ϳ΄pLKз"Q3n՛KzЄB{}m{eTQVMd5ˮ~ -endstream -endobj -828 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 827 0 R -/Resources 4 0 R -/Annots [ 829 0 R 830 0 R 831 0 R 832 0 R 833 0 R 834 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -829 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 512.554475 101.433071 493.804475 ] -/BS << -/W 0 ->> -/Dest (cb291-1) ->> -endobj -830 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 172.663410 101.433071 153.913410 ] -/BS << -/W 0 ->> -/Dest (cb294-1) ->> -endobj -831 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 153.716389 99.933071 134.966389 ] -/BS << -/W 0 ->> -/Dest (cb294-2) ->> -endobj -832 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 134.769367 99.933071 116.019367 ] -/BS << -/W 0 ->> -/Dest (cb294-3) ->> -endobj -833 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 115.822346 99.933071 97.072346 ] -/BS << -/W 0 ->> -/Dest (cb294-4) ->> -endobj -834 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 96.875324 99.933071 78.125324 ] -/BS << -/W 0 ->> -/Dest (cb294-5) ->> -endobj -835 0 obj -<< -/Filter /FlateDecode -/Length 4156 ->> -stream -x\Ko$ sJ"C$"dArXڻ<fsJEwg<ԃȏ盀_+O'xZ.&XJNja6y<_r'[6I)Yj  'r)Fn,@3<Ȃͷ &s , 9;-. -RL *S`y",$Yk U"dA Kd kkC[X@@\*-, @.LZX@\vZX@]{$)ZX@],, .q0p=Md[Xtt -YX] ->[X]Q`؊x g 3B>H0p7 -`Enn-,`n,,87. Dt`-,@/E%p7T?çV.,,n(>W]ив )U @EpY,,;Dhaw!R[W pWæ)+! C-,H]9YX)KbaA  AlakW r,9B  #p5 6s1,-,R-,ȒPA/EW2B gvR-,;M,, WWȕȂ$d`aA٠%T[XZx,NNSE &4&&,,h-A2Af}fzȂ‚48x[XPCA֛‚J&J/o|Ͽ餬?qZEbv4HHF)ċs.B|B"#s"Cb9 V㼨-`Hat#h`7zuwQ% %絅i+ÎIB5~e!Ey1ztl*\NQ_5iЊjF]yOy=~9ȍ|??b7ṿ<r}Ȃ赚CrwD5$3ZF -)0=^Jp˻i?_oǨf`d޴#>ZTАכF+k_+D_,H4AiLiOc}ޞcTM<>ȳדàuPo&ik{AܮAsf.УPZi槮#PJDK h賳(}#N2%t~0_]t VqՓ~f=9ʱ>oUc)v -m4m ܡmȄ+ƾz`(R^!Zʳ\MJǐd\YC?R4 [ޢu;|VBl%.AmRlGi^ Qѿ!WJAd=|HQJa,ie#ho7ZVtxkXѣX -qhj:&g"v#",W<_O:1_vJocz"Ըqzͨ>f3ƚTrXup<=HP v;g{WCf, k=Te{zmepF5yxƅ ⤃?mAd_Z}^5\GMti#MO~!N"VIS7M`7FH@7ڡqiCeq}黅a)_ρ3`ӯt}==;vFZ" VadGh ۜgL7ϟg۬z-Y㤷IdۢGDI}ٌC4=ϡ>㱤I_.} *uzfWz?=!:$ @5Ie Ҽt©Lrl-]R$p5M ,i9쯦[ws~E7Z-" v}6Op -Cؒ(]|@`9""6˵ <:i.p9eAbjpiGKِ/aKS.;yfr5sD} z+?vFIl}ؑM=!uaR69}JH}5fbni'=T^[^'䧓Ńd%}CkiuK?>fgKi-MO_&6–.d}8RPX;qǶˀK]r ?eKt 9r'b]ui!vGՅa[ۘE?aZ>TM*PMHjJk7>AƷҡ]. {nMNު,]k"bT ڤL>Iw/ IZLo$0n'Bu.o TH*Lw7זeN^+i:li p^ -9w7+]c+꠲kOAǚuBXOʑn!K7yS0qr4s!vy7_$ Y"@a!/04vtǧɬ{4H Qз+6N|uw[W1wdNFn3#CYJc~2t ;e@tcA3rxŞ|,rImq&.,W'V3@o.DΗCI %/sd{JOƙ|O`}0TB[^xh99j:deRQ4-9g1> -endobj -837 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb294-6) ->> -endobj -838 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb294-7) ->> -endobj -839 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb294-8) ->> -endobj -840 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb294-9) ->> -endobj -841 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb294-10) ->> -endobj -842 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb294-11) ->> -endobj -843 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb294-12) ->> -endobj -844 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb294-13) ->> -endobj -845 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb294-14) ->> -endobj -846 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb294-15) ->> -endobj -847 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb294-16) ->> -endobj -848 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb294-17) ->> -endobj -849 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb294-18) ->> -endobj -850 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb294-19) ->> -endobj -851 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 454.020714 101.433071 435.270714 ] -/BS << -/W 0 ->> -/Dest (cb295-1) ->> -endobj -852 0 obj -<< -/Filter /FlateDecode -/Length 3347 ->> -stream -x[K$ 賁%z >9v<6QUXݜٙ]9xvvKE~Tpyrp|px$ơ㷤s\\ --t *K>_OsSկ:&k-ǐο(,&Wj)>dRrĔ VSlbAT8=@ n5Y,1VU!q tj# b -rɃ e(=[\-6W %Z<" ,^s9T-C|x -daeBɃ,xDh -Y`]A}x\j5|-}ryKM2y(,R./BS3y% 'Z o)XYb,l B!/قx\0 E@ Vr\Z(ks\ -Y0[r[p|/ CB -&Pc (BTD& h˰ p˾ x>d  1ĥ”%`Ѕ K)G K\%Ƀ,0` B% K  7`U0[X[qVoawclawcA0yƄ)X0p7rPǛpt`-,@/E%$nhO\-[XbL^s@B.,,H]* w`CD$n Dj y pyC \0]לoZXhaHb! # wޛiɃ,Tk>dx]}id஄M rB@@,8ZX+VJ 7R>‚AH,YH]V-,(PY2XX@?`ȂL ‚2cЪ6yP,,(Bq{)WK@ [XPdXXPjDfndAma2]BFȂl‚+v[X$Tm>ZXP9;I-,` 4y0aaG6l~6AJlaAQ‚Z!Kئ7Cd|4‚*-,_~ZXc-᷍7!KBb f-0 Mː%6,ja 7ћGU<.dx]dDfk=7g6ʎ'Л[#E*晁<4Yl yl'}Da1d[0Xj/?~{?IH⤀ivlX'(CY Wd7dL|Kx9)2@ {=ұC^;j+f6 ؑސSZupȫE^3*jiciR_8Dֲe?D 1p\k,,^"WG=_uM&Xl*"w$y`C|!MG4e$6Tmʆ*jߒS^upm(64kkKWx|`A;sl|zSuW9_|kE,^^|,|!_~g~'H/ೱcu/ry~w˟=oNP 3981MCEOۭаϛUľg cw!o߄oI>bxio O4يwk> 9(ue$)nn&g瘛w_fO]No)ސZ.KU6^6dVfGx少Gdfs'uηz]vA AcvڐW;z%#DiLCc6<_X~i}749į e‰ڃ?{ӳx;ewٔ|ڛe;zO#j?тt7:۽\0i7@]v]i4V޿C/UN6=hjF͹ < Ə9jFFÐxkAz{oiTjچ(ԩNJ4|MFx$K2We7x9!N +|ꗽ,jCUpAw4*ID4J]iZ_z=5v*)ziC< GrV7aC?+5!0"iyə`9(sOE;\6*Kl|KӯcE~F5". -`[':ɗvr2+^N?zb{ -r_[g^_:O[d=d NQ -9U7 kq> -endobj -854 0 obj -<< -/Filter /FlateDecode -/Length 3190 ->> -stream -x[M$ׯh%E =l`|)bj >EV#^|2_(P()T變UӇw%yl%7Gt^K JKwkoN>>ѵcH_ߚHŕZOD A(%WJLrpbkL5RѨ5DPCcDTh (jP#L5BK!zOePīJ$\3rmQY,d". )0Ys9TLKj>0Y.)z&.*0Y.StaFd*A}`&.Je 2_K}E\"Bp )T BddA$>2@/'ZIFn,ARt3 X@je,ksZ0-9ͭ0 x43&]KeE2.]Pqt* lUߪqpg\ `\Y(8W p/ +)GqwEg\]*k.X-B΍qAb 3jd\A0S3x7$.ĸ\p]*kηZ$.h)2.,|PYqpd*qA(ʠe\5iqAEbd\P"tAk7]@ ](tAȸLjSe\PRz Ve]-k*¸u\E3.;K@ Ȃ2.( T`*r5"3g]d3.@ Y j.X̞qfh%aj&Soʸjv*2.@` 2`\vb\XPt jܬ j.GM[oCd| dqȼg\Bz3*ĥ7+&M,H6ɶ, Bʠ F&؉2tMmY z=,tL3`̖=7g\XmY鎁&̭t{1[gAFP+˚U|L8nQeCYu!,XsbLد?}{?wl;e|#Y1ڱaߟ`,L`M |nx9-0``{=X _C^K/-e_OX,`Ez4ˎVPg=.ljZr acZR0Y! p7#6ͱ]K0G DZP`C2kqb\vc>T֊1s/C>Њ#k2 6܇Cg -> tvz65{yKZn? ²>l%^w|~ oUxjgK /K9 ȗ{ Y}~4೩S{K_lK?G_;;C_}z>3֞jא ?ίx={k>ڳ&Tg˭W⭉~?ch7et\k?ӺzuFe^{4ݴ5܆r&Svf,?Ms}[ғ;n1_t{[0ݞoњ݂>x_v\`'&Ge7',MnG1Fi-m}D9=>eCr^cns[醴f-kw.^x~]L?[e!zd/=\rio7vcW5luQzdvoq4UI{'b˛[p4A!4)n2i1UGwp7^ʯEv_OwCH[RP~8YN\]vizЇ.lg܎~SKf/a`uuvopfד(TuisK. ܕ~9' I2{>MB2;[ē9<{۩dCmB] -烟L_pԮOtyCta^6e8?^NJQ; ֫1YjMD KmWW!_FިIGr2Jh떟LW: O˒;fĈ~ymc7IJCG$Nx[i`eZf\ᳫ!tGal<u6 -\+&+_3PrX=z'w^Wv@d;]|mb{\F&fc 8)Lxu{vCrq/_N4%f^yQ <`83 iY O8Y6uox _|Ob%`0+ 8׍Aˤ;+D淎͜o;fĎftpvudNJY9Cqy7k]lSk#C!rv+Ss]֋R`Yo֊5>D<ʹGz]1CqT|sШKؓИnV]: Qء>Q ;6j,]?ͲR+SLiaĴJ~(kodK2s%+@u=Ƕl{^S<3S?K%&v2+ݑP4LDپekE]|큨% S_}_p}ZTտKkv > l_lDRѾ(VZCϼm ?O- -endstream -endobj -855 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 854 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -856 0 obj -<< -/Filter /FlateDecode -/Length 2995 ->> -stream -x[ˮWڀiU|A Ā/,F,9|̹$/hmbba7\=>_\d]_+VT[5x-.k3@+-Œ ~<˷_\s'\k-ǐ?o"Wj)>Q!\)1e"a1HE> -VA Q%ȳAX2-" -z=A*BrFL˵FeP"\4dSe2.d dHOe%"LVKuUT]|ɚԪ*5|-Y}rx& %P" - E}jT]d]&O$)h%0Y.12g 3t%3 -@9%-*#XiX a4[r[a< >@#%ifL ("ʠ4e\ UV- tU2BMϸ@R2.P.\1.p;H^XWR +Z3ϸ@"ʠ qI¸@|a\]Qd\Yu̸bqwcʸ@` ¸@1al#FqŁ<e\( ИHK$nhXHL\-3.HP1}T\(8[XمB% xYVȸ w`f2n3.H] q$ T֜o2.H]Rd\U -&Hqy䡌 2x{c\>0.]H{ H @%1d`2a&z_ ޵eqA.ʸ -:dqAZ)qAn2|TʉqA(ʠe\5iqAEbd\P"tAk7@ (tAȸLjSe\PR~ Ve]-k*¸uX\E3.;K@ Ȃ2.( T`)r5"3g]d3.@ Y j.X̞qVh%aj&Soʸjv*2.@` 2`\vb\6Pt jݬ j.GMoCd| dqȼg\B~3*ĥ7+&MlH6ɶ, Bʠ F&؉2tMmY ~==,L3Dfě -3.zVzdX -=3 _#Ce*cE>O>GTPfbl Ev?Pm?Wo^/1HivlwCy+2X@ӽ.5?۩. ,~0<~mX7|{^{mAoH~f;8YwtSes$]M0.b߯mLkT -5\"Aފo΁[l.Ksgas^he}:+2} c3l^WOɇ&|˨o "P><C@gW:̾M"f]/˞3Amk,+OuˈC=5^5>1h}ZB@kS\R ~7uu{`Oi^߼|_|.mv,swֽL:2} 90k?C:e~{l>.mU(ꦴ@ l*oߛNl_ym6"˂=lǤ3u*ۣ*0Z:'Ě]Mc!]q3v_SqU>|ANޟE!/+̤^# Ҋ̲"/Madc~wPw#9k6 G}:϶Għ{h?-ӗ4Ɛ%oB7ѮYDgW{@!ԅ{G>oO R8&% eop0^Rǥmiv1)㲍%˘hocql{ĝ9<6z+lQC$ mA]獿 At7]`<2n,t~)x'z8ӛ֍~`(z1!:@<_޴b2|5{;z#B1SeԪ-?U.u`;Kxg8 u"GrirOVPv\";L=;UlAKYXllσuY husRϮBDb't1قc?Gyl3r}WM8 Wg -g尸{N8p3iw|o¦~L8p*RhdodlŽ]~l\H+\:_^O u<qp ^W2{~$lwpF]h¡κ{Xc\Z~{!]4mqNeۃG"kf.{QЍs -pPS&sI.MdUFFQ\:lSk'S!RX+ʔ\fצ;bXڰv҇(P90tP@+:f uvTHkڱS}twlXNeqV*#O:+ÈiT+Ȗd$@iu2Gg͑KV){[} C"yf~ޖj~}N38VӑP;X5I9Cު-ZOsY{t8%q_,M?5OixE(zb؎ZCQ,U?Kz^ 'v Tek5f -endstream -endobj -857 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 856 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -858 0 obj -<< -/Filter /FlateDecode -/Length 4328 ->> -stream -x\K$ 賁~ >9̶=6QUXU5r`vJJ(#*wy_JӇ5%Y=6%$rMDŔ|5eӏ_ǝi-{οLLؤX)ŧ3Xbk b}< -Ĉ&1UaUbqj5p-,pZAl+׌+ивq97 p*hXϪa0 z pDjuY pyCҰ` ߌ0]׌mjX%aH!9 "հ wޛkSd஍H{Td kX!\Pֲ8|:dW}q?ݟr߽=AmX!}8?}>k]ůUAKn7y&yK}<vh|gl kB}h(C%I}㾙q*ETkuЦOIqu^?K&H*J;4ig?ȴ/>u9BuG;^q:\VkȫYM1X0Cc-cNOqrB5}8N_3wKɱ$x"})&sS܄=c]望On>=ml@uUn@ʐWq/SkYчBg>q:usϹQ,o( (PdӊBY O^5c~+1v[: <ƴԵ?Ѵ(}4 -y{.mQC,ikcC;01418c&'cqUnv-»8%dXxSq>-택L^NY7M'-fx4~+8 -S=|=dS:7^&fp\IyϹ+MG#~n0Iv浴ùlZooX5;tN+䝽>w \?~^zyxcwۊbJm]+0Zlz7nM00Wqv1ݴo=?:8,Z[ԙnѵ8_o!Y|ӄѯW-#uէɼ&_ZV=aC#_6[}_xe6ֺװ ؾ?O\0MyWd>`-*s| \]\\O:^1GBl+ĺ_8+`?l`pV?T@[{pƶնk}u'bWs ұZ*{U9:PV땪&^TtFϞB2ެ Փ8UOus-W=9hE߉p|Gn#M#|Gˠng#v93(dBd| - ]vVnP7tv'b#;!KZ"'W+u}==P鯕~5* -=uG>[,gNۚݮ[aSnn (}1ncs=s}=zx+ZQ㐑ZٯU= zaëlOB']{|$mjU]{#u&馮^Ws&Z3E Qϸ5v}꠿ŞS'p⁕;~Aye4wo1$ZXazM$2C=X#(>/'-yO|kپop1><ޖ-k8lSOt8OAPT+LO3Vs]|ҞKcK~Dco{Dh2 sc_NΕcA2K;ƢiG\/wzdz9'^ ݟ6z.Z` -wfw$q+[SMX[y2L_hFw8o|t$Z1$8zy.O]Ή8b {JeP]o-ڠ&96$}RH#6sŮ3 !ѯq?t9ة2zykcOQ:.".".#6Lk[rBrwXa$1 W;eRKeU5FOl TA%.gkNB9[%Iz5 Xf_.WʰY/Wҟ@wP4@jǖ 2Ag`$ZMr!O9pU;O04Ɲ -؟dWg0N`n \ILSzf eő|̀4/zxBC.:ya-:C:ыѐ)&lSdrz?ʭ4h4a rhU.Hlȁ<^ș=ERˆ:O9L vީ1VF3]cqӐ6*u޶vHrȴͤ(\f6F,,S^ocWUKet2C_#ȖH42WggϑKV݃gq;7G۳XF䙙y[:(QzO:_ځ@] >ښ30$ҫJ\=9lqF]]0 1mWYuI)O\bF>@Io{幩T]ڔP -endstream -endobj -859 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 858 0 R -/Resources 4 0 R -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -860 0 obj -<< -/Title (RKE2 CIS v1.6 Benchmark - Self-Assessment Guide - Rancher v2.6) -/Dest [ 6 0 R /XYZ 85.009843 502.818898 0 ] -/Count 142 -/First 861 0 R -/Last 998 0 R -/Parent 1003 0 R ->> -endobj -861 0 obj -<< -/Title (CIS v1.6 Kubernetes Benchmark - Rancher v2.6 RKE2 with Kubernetes v1.21 up to v1.23) -/Dest [ 306 0 R /XYZ 84.259843 784.970079 0 ] -/Count 2 -/First 862 0 R -/Last 863 0 R -/Parent 860 0 R -/Next 864 0 R ->> -endobj -862 0 obj -<< -/Title (Overview) -/Dest [ 306 0 R /XYZ 84.259843 704.822079 0 ] -/Count 0 -/Parent 861 0 R -/Next 863 0 R ->> -endobj -863 0 obj -<< -/Title (Testing controls methodology) -/Dest [ 306 0 R /XYZ 84.259843 169.826079 0 ] -/Count 0 -/Prev 862 0 R -/Parent 861 0 R ->> -endobj -864 0 obj -<< -/Title (Controls) -/Dest [ 313 0 R /XYZ 84.259843 570.381496 0 ] -/Count 0 -/Prev 861 0 R -/Parent 860 0 R -/Next 865 0 R ->> -endobj -865 0 obj -<< -/Title (1.1 Master Node Configuration Files) -/Dest [ 317 0 R /XYZ 41.740157 784.430079 0 ] -/Count 21 -/Prev 864 0 R -/First 866 0 R -/Last 886 0 R -/Parent 860 0 R -/Next 887 0 R ->> -endobj -866 0 obj -<< -/Title (1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 317 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 865 0 R -/Next 867 0 R ->> -endobj -867 0 obj -<< -/Title (1.1.2 Ensure that the API server pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 317 0 R /XYZ 84.259843 352.457453 0 ] -/Count 0 -/Prev 866 0 R -/Parent 865 0 R -/Next 868 0 R ->> -endobj -868 0 obj -<< -/Title (1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 321 0 R /XYZ 84.259843 736.220079 0 ] -/Count 0 -/Prev 867 0 R -/Parent 865 0 R -/Next 869 0 R ->> -endobj -869 0 obj -<< -/Title (1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 321 0 R /XYZ 84.259843 351.131993 0 ] -/Count 0 -/Prev 868 0 R -/Parent 865 0 R -/Next 870 0 R ->> -endobj -870 0 obj -<< -/Title (1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 702.470079 0 ] -/Count 0 -/Prev 869 0 R -/Parent 865 0 R -/Next 871 0 R ->> -endobj -871 0 obj -<< -/Title (1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 325 0 R /XYZ 84.259843 351.329014 0 ] -/Count 0 -/Prev 870 0 R -/Parent 865 0 R -/Next 872 0 R ->> -endobj -872 0 obj -<< -/Title (1.1.7 Ensure that the etcd pod specification file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 329 0 R /XYZ 84.259843 736.220079 0 ] -/Count 0 -/Prev 871 0 R -/Parent 865 0 R -/Next 873 0 R ->> -endobj -873 0 obj -<< -/Title (1.1.8 Ensure that the etcd pod specification file ownership is set to root:root \(Automated\)) -/Dest [ 329 0 R /XYZ 84.259843 385.079014 0 ] -/Count 0 -/Prev 872 0 R -/Parent 865 0 R -/Next 874 0 R ->> -endobj -874 0 obj -<< -/Title (1.1.9 Ensure that the Container Network Interface file permissions are set to 644 or more restrictive \(Manual\)) -/Dest [ 333 0 R /XYZ 84.259843 763.220079 0 ] -/Count 0 -/Prev 873 0 R -/Parent 865 0 R -/Next 875 0 R ->> -endobj -875 0 obj -<< -/Title (1.1.10 Ensure that the Container Network Interface file ownership is set to root:root \(Manual\)) -/Dest [ 333 0 R /XYZ 84.259843 586.473057 0 ] -/Count 0 -/Prev 874 0 R -/Parent 865 0 R -/Next 876 0 R ->> -endobj -876 0 obj -<< -/Title (1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive \(Automated\)) -/Dest [ 333 0 R /XYZ 84.259843 409.726036 0 ] -/Count 0 -/Prev 875 0 R -/Parent 865 0 R -/Next 877 0 R ->> -endobj -877 0 obj -<< -/Title (1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd \(Automated\)) -/Dest [ 338 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 876 0 R -/Parent 865 0 R -/Next 878 0 R ->> -endobj -878 0 obj -<< -/Title (1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 338 0 R /XYZ 84.259843 471.123057 0 ] -/Count 0 -/Prev 877 0 R -/Parent 865 0 R -/Next 879 0 R ->> -endobj -879 0 obj -<< -/Title (1.1.14 Ensure that the admin.conf file ownership is set to root:root \(Automated\)) -/Dest [ 338 0 R /XYZ 84.259843 157.876036 0 ] -/Count 0 -/Prev 878 0 R -/Parent 865 0 R -/Next 880 0 R ->> -endobj -880 0 obj -<< -/Title (1.1.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 342 0 R /XYZ 84.259843 538.576036 0 ] -/Count 0 -/Prev 879 0 R -/Parent 865 0 R -/Next 881 0 R ->> -endobj -881 0 obj -<< -/Title (1.1.16 Ensure that the scheduler.conf file ownership is set to root:root \(Automated\)) -/Dest [ 342 0 R /XYZ 84.259843 221.381993 0 ] -/Count 0 -/Prev 880 0 R -/Parent 865 0 R -/Next 882 0 R ->> -endobj -882 0 obj -<< -/Title (1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 346 0 R /XYZ 84.259843 622.576036 0 ] -/Count 0 -/Prev 881 0 R -/Parent 865 0 R -/Next 883 0 R ->> -endobj -883 0 obj -<< -/Title (1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root \(Automated\)) -/Dest [ 346 0 R /XYZ 84.259843 290.381993 0 ] -/Count 0 -/Prev 882 0 R -/Parent 865 0 R -/Next 884 0 R ->> -endobj -884 0 obj -<< -/Title (1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root \(Automated\)) -/Dest [ 351 0 R /XYZ 84.259843 675.470079 0 ] -/Count 0 -/Prev 883 0 R -/Parent 865 0 R -/Next 885 0 R ->> -endobj -885 0 obj -<< -/Title (1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive \(Manual\)) -/Dest [ 351 0 R /XYZ 84.259843 362.223057 0 ] -/Count 0 -/Prev 884 0 R -/Parent 865 0 R -/Next 886 0 R ->> -endobj -886 0 obj -<< -/Title (1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 \(Manual\)) -/Dest [ 398 0 R /XYZ 84.259843 324.635606 0 ] -/Count 0 -/Prev 885 0 R -/Parent 865 0 R ->> -endobj -887 0 obj -<< -/Title (1.2 API Server) -/Dest [ 486 0 R /XYZ 41.740157 784.430079 0 ] -/Count 35 -/Prev 865 0 R -/First 888 0 R -/Last 922 0 R -/Parent 860 0 R -/Next 923 0 R ->> -endobj -888 0 obj -<< -/Title (1.2.1 Ensure that the --anonymous-auth argument is set to false \(Manual\)) -/Dest [ 486 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 887 0 R -/Next 889 0 R ->> -endobj -889 0 obj -<< -/Title (1.2.2 Ensure that the --basic-auth-file argument is not set \(Automated\)) -/Dest [ 486 0 R /XYZ 84.259843 528.904475 0 ] -/Count 0 -/Prev 888 0 R -/Parent 887 0 R -/Next 890 0 R ->> -endobj -890 0 obj -<< -/Title (1.2.3 Ensure that the --token-auth-file parameter is not set \(Automated\)) -/Dest [ 492 0 R /XYZ 84.259843 427.220079 0 ] -/Count 0 -/Prev 889 0 R -/Parent 887 0 R -/Next 891 0 R ->> -endobj -891 0 obj -<< -/Title (1.2.4 Ensure that the --kubelet-https argument is set to true \(Automated\)) -/Dest [ 497 0 R /XYZ 84.259843 333.470079 0 ] -/Count 0 -/Prev 890 0 R -/Parent 887 0 R -/Next 892 0 R ->> -endobj -892 0 obj -<< -/Title (1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate \(Automated\)) -/Dest [ 502 0 R /XYZ 84.259843 277.220079 0 ] -/Count 0 -/Prev 891 0 R -/Parent 887 0 R -/Next 893 0 R ->> -endobj -893 0 obj -<< -/Title (1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate \(Automated\)) -/Dest [ 507 0 R /XYZ 84.259843 164.720079 0 ] -/Count 0 -/Prev 892 0 R -/Parent 887 0 R -/Next 894 0 R ->> -endobj -894 0 obj -<< -/Title (1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow \(Automated\)) -/Dest [ 514 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 893 0 R -/Parent 887 0 R -/Next 895 0 R ->> -endobj -895 0 obj -<< -/Title (1.2.8 Ensure that the --authorization-mode argument includes Node \(Automated\)) -/Dest [ 519 0 R /XYZ 84.259843 652.220079 0 ] -/Count 0 -/Prev 894 0 R -/Parent 887 0 R -/Next 896 0 R ->> -endobj -896 0 obj -<< -/Title (1.2.9 Ensure that the --authorization-mode argument includes RBAC \(Automated\)) -/Dest [ 524 0 R /XYZ 84.259843 577.220079 0 ] -/Count 0 -/Prev 895 0 R -/Parent 887 0 R -/Next 897 0 R ->> -endobj -897 0 obj -<< -/Title (1.2.10 Ensure that the admission control plugin EventRateLimit is set \(Manual\)) -/Dest [ 529 0 R /XYZ 84.259843 502.220079 0 ] -/Count 0 -/Prev 896 0 R -/Parent 887 0 R -/Next 898 0 R ->> -endobj -898 0 obj -<< -/Title (1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set \(Automated\)) -/Dest [ 529 0 R /XYZ 84.259843 280.473057 0 ] -/Count 0 -/Prev 897 0 R -/Parent 887 0 R -/Next 899 0 R ->> -endobj -899 0 obj -<< -/Title (1.2.12 Ensure that the admission control plugin AlwaysPullImages is set \(Manual\)) -/Dest [ 535 0 R /XYZ 84.259843 202.220079 0 ] -/Count 0 -/Prev 898 0 R -/Parent 887 0 R -/Next 900 0 R ->> -endobj -900 0 obj -<< -/Title (1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used \(Manual\)) -/Dest [ 537 0 R /XYZ 84.259843 736.023057 0 ] -/Count 0 -/Prev 899 0 R -/Parent 887 0 R -/Next 901 0 R ->> -endobj -901 0 obj -<< -/Title (1.2.14 Ensure that the admission control plugin ServiceAccount is set \(Automated\)) -/Dest [ 537 0 R /XYZ 84.259843 499.276036 0 ] -/Count 0 -/Prev 900 0 R -/Parent 887 0 R -/Next 902 0 R ->> -endobj -902 0 obj -<< -/Title (1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set \(Automated\)) -/Dest [ 544 0 R /XYZ 84.259843 370.970079 0 ] -/Count 0 -/Prev 901 0 R -/Parent 887 0 R -/Next 903 0 R ->> -endobj -903 0 obj -<< -/Title (1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set \(Automated\)) -/Dest [ 549 0 R /XYZ 84.259843 295.970079 0 ] -/Count 0 -/Prev 902 0 R -/Parent 887 0 R -/Next 904 0 R ->> -endobj -904 0 obj -<< -/Title (1.2.17 Ensure that the admission control plugin NodeRestriction is set \(Automated\)) -/Dest [ 554 0 R /XYZ 84.259843 183.470079 0 ] -/Count 0 -/Prev 903 0 R -/Parent 887 0 R -/Next 905 0 R ->> -endobj -905 0 obj -<< -/Title (1.2.18 Ensure that the --insecure-bind-address argument is not set \(Automated\)) -/Dest [ 561 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 904 0 R -/Parent 887 0 R -/Next 906 0 R ->> -endobj -906 0 obj -<< -/Title (1.2.19 Ensure that the --insecure-port argument is set to 0 \(Automated\)) -/Dest [ 566 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 905 0 R -/Parent 887 0 R -/Next 907 0 R ->> -endobj -907 0 obj -<< -/Title (1.2.20 Ensure that the --secure-port argument is not set to 0 \(Automated\)) -/Dest [ 571 0 R /XYZ 84.259843 689.720079 0 ] -/Count 0 -/Prev 906 0 R -/Parent 887 0 R -/Next 908 0 R ->> -endobj -908 0 obj -<< -/Title (1.2.21 Ensure that the --profiling argument is set to false \(Automated\)) -/Dest [ 576 0 R /XYZ 84.259843 614.720079 0 ] -/Count 0 -/Prev 907 0 R -/Parent 887 0 R -/Next 909 0 R ->> -endobj -909 0 obj -<< -/Title (1.2.22 Ensure that the --audit-log-path argument is set \(Automated\)) -/Dest [ 581 0 R /XYZ 84.259843 558.470079 0 ] -/Count 0 -/Prev 908 0 R -/Parent 887 0 R -/Next 910 0 R ->> -endobj -910 0 obj -<< -/Title (1.2.23 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate \(Automated\)) -/Dest [ 586 0 R /XYZ 84.259843 464.720079 0 ] -/Count 0 -/Prev 909 0 R -/Parent 887 0 R -/Next 911 0 R ->> -endobj -911 0 obj -<< -/Title (1.2.24 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate \(Automated\)) -/Dest [ 591 0 R /XYZ 84.259843 389.720079 0 ] -/Count 0 -/Prev 910 0 R -/Parent 887 0 R -/Next 912 0 R ->> -endobj -912 0 obj -<< -/Title (1.2.25 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate \(Automated\)) -/Dest [ 596 0 R /XYZ 84.259843 295.970079 0 ] -/Count 0 -/Prev 911 0 R -/Parent 887 0 R -/Next 913 0 R ->> -endobj -913 0 obj -<< -/Title (1.2.26 Ensure that the --request-timeout argument is set as appropriate \(Automated\)) -/Dest [ 601 0 R /XYZ 84.259843 239.720079 0 ] -/Count 0 -/Prev 912 0 R -/Parent 887 0 R -/Next 914 0 R ->> -endobj -914 0 obj -<< -/Title (1.2.27 Ensure that the --service-account-lookup argument is set to true \(Automated\)) -/Dest [ 606 0 R /XYZ 84.259843 164.720079 0 ] -/Count 0 -/Prev 913 0 R -/Parent 887 0 R -/Next 915 0 R ->> -endobj -915 0 obj -<< -/Title (1.2.28 Ensure that the --service-account-key-file argument is set as appropriate \(Automated\)) -/Dest [ 613 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 914 0 R -/Parent 887 0 R -/Next 916 0 R ->> -endobj -916 0 obj -<< -/Title (1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate \(Automated\)) -/Dest [ 618 0 R /XYZ 84.259843 670.970079 0 ] -/Count 0 -/Prev 915 0 R -/Parent 887 0 R -/Next 917 0 R ->> -endobj -917 0 obj -<< -/Title (1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate \(Automated\)) -/Dest [ 623 0 R /XYZ 84.259843 577.220079 0 ] -/Count 0 -/Prev 916 0 R -/Parent 887 0 R -/Next 918 0 R ->> -endobj -918 0 obj -<< -/Title (1.2.31 Ensure that the --client-ca-file argument is set as appropriate \(Automated\)) -/Dest [ 628 0 R /XYZ 84.259843 464.720079 0 ] -/Count 0 -/Prev 917 0 R -/Parent 887 0 R -/Next 919 0 R ->> -endobj -919 0 obj -<< -/Title (1.2.32 Ensure that the --etcd-cafile argument is set as appropriate \(Automated\)) -/Dest [ 633 0 R /XYZ 84.259843 370.970079 0 ] -/Count 0 -/Prev 918 0 R -/Parent 887 0 R -/Next 920 0 R ->> -endobj -920 0 obj -<< -/Title (1.2.33 Ensure that the --encryption-provider-config argument is set as appropriate \(Automated\)) -/Dest [ 638 0 R /XYZ 84.259843 295.970079 0 ] -/Count 0 -/Prev 919 0 R -/Parent 887 0 R -/Next 921 0 R ->> -endobj -921 0 obj -<< -/Title (1.2.34 Ensure that encryption providers are appropriately configured \(Automated\)) -/Dest [ 643 0 R /XYZ 84.259843 220.970079 0 ] -/Count 0 -/Prev 920 0 R -/Parent 887 0 R -/Next 922 0 R ->> -endobj -922 0 obj -<< -/Title (1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers \(Manual\)) -/Dest [ 645 0 R /XYZ 84.259843 547.576036 0 ] -/Count 0 -/Prev 921 0 R -/Parent 887 0 R ->> -endobj -923 0 obj -<< -/Title (1.3 Controller Manager) -/Dest [ 653 0 R /XYZ 41.740157 784.430079 0 ] -/Count 7 -/Prev 887 0 R -/First 924 0 R -/Last 930 0 R -/Parent 860 0 R -/Next 931 0 R ->> -endobj -924 0 obj -<< -/Title (1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate \(Automated\)) -/Dest [ 653 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 923 0 R -/Next 925 0 R ->> -endobj -925 0 obj -<< -/Title (1.3.2 Ensure that the --profiling argument is set to false \(Automated\)) -/Dest [ 656 0 R /XYZ 84.259843 633.470079 0 ] -/Count 0 -/Prev 924 0 R -/Parent 923 0 R -/Next 926 0 R ->> -endobj -926 0 obj -<< -/Title (1.3.3 Ensure that the --use-service-account-credentials argument is set to true \(Automated\)) -/Dest [ 659 0 R /XYZ 84.259843 558.470079 0 ] -/Count 0 -/Prev 925 0 R -/Parent 923 0 R -/Next 927 0 R ->> -endobj -927 0 obj -<< -/Title (1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate \(Automated\)) -/Dest [ 662 0 R /XYZ 84.259843 483.470079 0 ] -/Count 0 -/Prev 926 0 R -/Parent 923 0 R -/Next 928 0 R ->> -endobj -928 0 obj -<< -/Title (1.3.5 Ensure that the --root-ca-file argument is set as appropriate \(Automated\)) -/Dest [ 665 0 R /XYZ 84.259843 389.720079 0 ] -/Count 0 -/Prev 927 0 R -/Parent 923 0 R -/Next 929 0 R ->> -endobj -929 0 obj -<< -/Title (1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true \(Automated\)) -/Dest [ 668 0 R /XYZ 84.259843 294.470079 0 ] -/Count 0 -/Prev 928 0 R -/Parent 923 0 R -/Next 930 0 R ->> -endobj -930 0 obj -<< -/Title (1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1 \(Automated\)) -/Dest [ 668 0 R /XYZ 84.259843 133.670079 0 ] -/Count 0 -/Prev 929 0 R -/Parent 923 0 R ->> -endobj -931 0 obj -<< -/Title (1.4 Scheduler) -/Dest [ 675 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 923 0 R -/First 932 0 R -/Last 933 0 R -/Parent 860 0 R -/Next 934 0 R ->> -endobj -932 0 obj -<< -/Title (1.4.1 Ensure that the --profiling argument is set to false \(Automated\)) -/Dest [ 675 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 931 0 R -/Next 933 0 R ->> -endobj -933 0 obj -<< -/Title (1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1 \(Automated\)) -/Dest [ 675 0 R /XYZ 84.259843 313.654475 0 ] -/Count 0 -/Prev 932 0 R -/Parent 931 0 R ->> -endobj -934 0 obj -<< -/Title (2 Etcd Node Configuration Files) -/Dest [ 681 0 R /XYZ 41.740157 784.430079 0 ] -/Count 7 -/Prev 931 0 R -/First 935 0 R -/Last 941 0 R -/Parent 860 0 R -/Next 942 0 R ->> -endobj -935 0 obj -<< -/Title (2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate \(Automated\)) -/Dest [ 681 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 934 0 R -/Next 936 0 R ->> -endobj -936 0 obj -<< -/Title (2.2 Ensure that the --client-cert-auth argument is set to true \(Automated\)) -/Dest [ 681 0 R /XYZ 84.259843 538.851496 0 ] -/Count 0 -/Prev 935 0 R -/Parent 934 0 R -/Next 937 0 R ->> -endobj -937 0 obj -<< -/Title (2.3 Ensure that the --auto-tls argument is not set to true \(Automated\)) -/Dest [ 681 0 R /XYZ 84.259843 408.051496 0 ] -/Count 0 -/Prev 936 0 R -/Parent 934 0 R -/Next 938 0 R ->> -endobj -938 0 obj -<< -/Title (2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate \(Automated\)) -/Dest [ 686 0 R /XYZ 84.259843 708.470079 0 ] -/Count 0 -/Prev 937 0 R -/Parent 934 0 R -/Next 939 0 R ->> -endobj -939 0 obj -<< -/Title (2.5 Ensure that the --peer-client-cert-auth argument is set to true \(Automated\)) -/Dest [ 686 0 R /XYZ 84.259843 547.670079 0 ] -/Count 0 -/Prev 938 0 R -/Parent 934 0 R -/Next 940 0 R ->> -endobj -940 0 obj -<< -/Title (2.6 Ensure that the --peer-auto-tls argument is not set to true \(Automated\)) -/Dest [ 686 0 R /XYZ 84.259843 416.870079 0 ] -/Count 0 -/Prev 939 0 R -/Parent 934 0 R -/Next 941 0 R ->> -endobj -941 0 obj -<< -/Title (2.7 Ensure that a unique Certificate Authority is used for etcd \(Manual\)) -/Dest [ 691 0 R /XYZ 84.259843 652.220079 0 ] -/Count 0 -/Prev 940 0 R -/Parent 934 0 R ->> -endobj -942 0 obj -<< -/Title (3.1 Authentication and Authorization) -/Dest [ 696 0 R /XYZ 41.740157 784.430079 0 ] -/Count 1 -/Prev 934 0 R -/First 943 0 R -/Last 943 0 R -/Parent 860 0 R -/Next 944 0 R ->> -endobj -943 0 obj -<< -/Title (3.1.1 Client certificate authentication should not be used for users \(Manual\)) -/Dest [ 696 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 942 0 R ->> -endobj -944 0 obj -<< -/Title (3.2 Logging) -/Dest [ 698 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 942 0 R -/First 945 0 R -/Last 946 0 R -/Parent 860 0 R -/Next 947 0 R ->> -endobj -945 0 obj -<< -/Title (3.2.1 Ensure that a minimal audit policy is created \(Automated\)) -/Dest [ 698 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 944 0 R -/Next 946 0 R ->> -endobj -946 0 obj -<< -/Title (3.2.2 Ensure that the audit policy covers key security concerns \(Manual\)) -/Dest [ 698 0 R /XYZ 84.259843 418.457453 0 ] -/Count 0 -/Prev 945 0 R -/Parent 944 0 R ->> -endobj -947 0 obj -<< -/Title (4.1 Worker Node Configuration Files) -/Dest [ 701 0 R /XYZ 41.740157 784.430079 0 ] -/Count 10 -/Prev 944 0 R -/First 948 0 R -/Last 957 0 R -/Parent 860 0 R -/Next 958 0 R ->> -endobj -948 0 obj -<< -/Title (4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 701 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 947 0 R -/Next 949 0 R ->> -endobj -949 0 obj -<< -/Title (4.1.2 Ensure that the kubelet service file ownership is set to root:root \(Automated\)) -/Dest [ 701 0 R /XYZ 84.259843 394.260432 0 ] -/Count 0 -/Prev 948 0 R -/Parent 947 0 R -/Next 950 0 R ->> -endobj -950 0 obj -<< -/Title (4.1.3 If proxy kubeconfig file exists ensure permissions are set to 644 or more restrictive \(Manual\)) -/Dest [ 701 0 R /XYZ 84.259843 263.460432 0 ] -/Count 0 -/Prev 949 0 R -/Parent 947 0 R -/Next 951 0 R ->> -endobj -951 0 obj -<< -/Title (4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root \(Manual\)) -/Dest [ 704 0 R /XYZ 84.259843 584.879014 0 ] -/Count 0 -/Prev 950 0 R -/Parent 947 0 R -/Next 952 0 R ->> -endobj -952 0 obj -<< -/Title (4.1.5 Ensure that the --kubeconfig kubelet.conf file permissions are set to 644 or more restrictive \(Automated\)) -/Dest [ 704 0 R /XYZ 84.259843 214.987950 0 ] -/Count 0 -/Prev 951 0 R -/Parent 947 0 R -/Next 953 0 R ->> -endobj -953 0 obj -<< -/Title (4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root \(Automated\)) -/Dest [ 708 0 R /XYZ 84.259843 603.629014 0 ] -/Count 0 -/Prev 952 0 R -/Parent 947 0 R -/Next 954 0 R ->> -endobj -954 0 obj -<< -/Title (4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive \(Manual\)) -/Dest [ 708 0 R /XYZ 84.259843 252.487950 0 ] -/Count 0 -/Prev 953 0 R -/Parent 947 0 R -/Next 955 0 R ->> -endobj -955 0 obj -<< -/Title (4.1.8 Ensure that the client certificate authorities file ownership is set to root:root \(Automated\)) -/Dest [ 713 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 954 0 R -/Parent 947 0 R -/Next 956 0 R ->> -endobj -956 0 obj -<< -/Title (4.1.9 Ensure that the kubelet --config configuration file has permissions set to 644 or more restrictive \(Automated\)) -/Dest [ 713 0 R /XYZ 84.259843 463.229014 0 ] -/Count 0 -/Prev 955 0 R -/Parent 947 0 R -/Next 957 0 R ->> -endobj -957 0 obj -<< -/Title (4.1.10 Ensure that the kubelet --config configuration file ownership is set to root:root \(Automated\)) -/Dest [ 717 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 956 0 R -/Parent 947 0 R ->> -endobj -958 0 obj -<< -/Title (4.2 Kubelet) -/Dest [ 720 0 R /XYZ 41.740157 784.430079 0 ] -/Count 13 -/Prev 947 0 R -/First 959 0 R -/Last 971 0 R -/Parent 860 0 R -/Next 972 0 R ->> -endobj -959 0 obj -<< -/Title (4.2.1 Ensure that the anonymous-auth argument is set to false \(Automated\)) -/Dest [ 720 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 958 0 R -/Next 960 0 R ->> -endobj -960 0 obj -<< -/Title (4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow \(Automated\)) -/Dest [ 724 0 R /XYZ 84.259843 520.970079 0 ] -/Count 0 -/Prev 959 0 R -/Parent 958 0 R -/Next 961 0 R ->> -endobj -961 0 obj -<< -/Title (4.2.3 Ensure that the --client-ca-file argument is set as appropriate \(Automated\)) -/Dest [ 728 0 R /XYZ 84.259843 670.970079 0 ] -/Count 0 -/Prev 960 0 R -/Parent 958 0 R -/Next 962 0 R ->> -endobj -962 0 obj -<< -/Title (4.2.4 Ensure that the --read-only-port argument is set to 0 \(Automated\)) -/Dest [ 732 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 961 0 R -/Parent 958 0 R -/Next 963 0 R ->> -endobj -963 0 obj -<< -/Title (4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0 \(Automated\)) -/Dest [ 736 0 R /XYZ 84.259843 614.720079 0 ] -/Count 0 -/Prev 962 0 R -/Parent 958 0 R -/Next 964 0 R ->> -endobj -964 0 obj -<< -/Title (4.2.6 Ensure that the --protect-kernel-defaults argument is set to true \(Automated\)) -/Dest [ 740 0 R /XYZ 84.259843 389.720079 0 ] -/Count 0 -/Prev 963 0 R -/Parent 958 0 R -/Next 965 0 R ->> -endobj -965 0 obj -<< -/Title (4.2.7 Ensure that the --make-iptables-util-chains argument is set to true \(Automated\)) -/Dest [ 744 0 R /XYZ 84.259843 544.220079 0 ] -/Count 0 -/Prev 964 0 R -/Parent 958 0 R -/Next 966 0 R ->> -endobj -966 0 obj -<< -/Title (4.2.8 Ensure that the --hostname-override argument is not set \(Manual\)) -/Dest [ 748 0 R /XYZ 84.259843 333.470079 0 ] -/Count 0 -/Prev 965 0 R -/Parent 958 0 R -/Next 967 0 R ->> -endobj -967 0 obj -<< -/Title (4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture \(Manual\)) -/Dest [ 751 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 966 0 R -/Parent 958 0 R -/Next 968 0 R ->> -endobj -968 0 obj -<< -/Title (4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate \(Automated\)) -/Dest [ 755 0 R /XYZ 84.259843 614.720079 0 ] -/Count 0 -/Prev 967 0 R -/Parent 958 0 R -/Next 969 0 R ->> -endobj -969 0 obj -<< -/Title (4.2.11 Ensure that the --rotate-certificates argument is not set to false \(Manual\)) -/Dest [ 759 0 R /XYZ 84.259843 389.720079 0 ] -/Count 0 -/Prev 968 0 R -/Parent 958 0 R -/Next 970 0 R ->> -endobj -970 0 obj -<< -/Title (4.2.12 Verify that the RotateKubeletServerCertificate argument is set to true \(Manual\)) -/Dest [ 763 0 R /XYZ 84.259843 187.970079 0 ] -/Count 0 -/Prev 969 0 R -/Parent 958 0 R -/Next 971 0 R ->> -endobj -971 0 obj -<< -/Title (4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers \(Manual\)) -/Dest [ 769 0 R /XYZ 84.259843 745.970079 0 ] -/Count 0 -/Prev 970 0 R -/Parent 958 0 R ->> -endobj -972 0 obj -<< -/Title (5.1 RBAC and Service Accounts) -/Dest [ 775 0 R /XYZ 41.740157 784.430079 0 ] -/Count 6 -/Prev 958 0 R -/First 973 0 R -/Last 978 0 R -/Parent 860 0 R -/Next 979 0 R ->> -endobj -973 0 obj -<< -/Title (5.1.1 Ensure that the cluster-admin role is only used where required \(Manual\)) -/Dest [ 775 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 972 0 R -/Next 974 0 R ->> -endobj -974 0 obj -<< -/Title (5.1.2 Minimize access to secrets \(Manual\)) -/Dest [ 775 0 R /XYZ 84.259843 523.851496 0 ] -/Count 0 -/Prev 973 0 R -/Parent 972 0 R -/Next 975 0 R ->> -endobj -975 0 obj -<< -/Title (5.1.3 Minimize wildcard use in Roles and ClusterRoles \(Manual\)) -/Dest [ 775 0 R /XYZ 84.259843 423.051496 0 ] -/Count 0 -/Prev 974 0 R -/Parent 972 0 R -/Next 976 0 R ->> -endobj -976 0 obj -<< -/Title (5.1.4 Minimize access to create pods \(Manual\)) -/Dest [ 775 0 R /XYZ 84.259843 307.251496 0 ] -/Count 0 -/Prev 975 0 R -/Parent 972 0 R -/Next 977 0 R ->> -endobj -977 0 obj -<< -/Title (5.1.5 Ensure that default service accounts are not actively used. \(Automated\)) -/Dest [ 775 0 R /XYZ 84.259843 206.451496 0 ] -/Count 0 -/Prev 976 0 R -/Parent 972 0 R -/Next 978 0 R ->> -endobj -978 0 obj -<< -/Title (5.1.6 Ensure that Service Account Tokens are only mounted where necessary \(Manual\)) -/Dest [ 802 0 R /XYZ 84.259843 449.446885 0 ] -/Count 0 -/Prev 977 0 R -/Parent 972 0 R ->> -endobj -979 0 obj -<< -/Title (5.2 Pod Security Policies) -/Dest [ 813 0 R /XYZ 41.740157 784.430079 0 ] -/Count 9 -/Prev 972 0 R -/First 980 0 R -/Last 988 0 R -/Parent 860 0 R -/Next 989 0 R ->> -endobj -980 0 obj -<< -/Title (5.2.1 Minimize the admission of privileged containers \(Automated\)) -/Dest [ 813 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 979 0 R -/Next 981 0 R ->> -endobj -981 0 obj -<< -/Title (5.2.2 Minimize the admission of containers wishing to share the host process ID namespace \(Automated\)) -/Dest [ 813 0 R /XYZ 84.259843 388.457453 0 ] -/Count 0 -/Prev 980 0 R -/Parent 979 0 R -/Next 982 0 R ->> -endobj -982 0 obj -<< -/Title (5.2.3 Minimize the admission of containers wishing to share the host IPC namespace \(Automated\)) -/Dest [ 817 0 R /XYZ 84.259843 763.220079 0 ] -/Count 0 -/Prev 981 0 R -/Parent 979 0 R -/Next 983 0 R ->> -endobj -983 0 obj -<< -/Title (5.2.4 Minimize the admission of containers wishing to share the host network namespace \(Automated\)) -/Dest [ 817 0 R /XYZ 84.259843 412.079014 0 ] -/Count 0 -/Prev 982 0 R -/Parent 979 0 R -/Next 984 0 R ->> -endobj -984 0 obj -<< -/Title (5.2.5 Minimize the admission of containers with allowPrivilegeEscalation \(Automated\)) -/Dest [ 821 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Prev 983 0 R -/Parent 979 0 R -/Next 985 0 R ->> -endobj -985 0 obj -<< -/Title (5.2.6 Minimize the admission of root containers \(Automated\)) -/Dest [ 821 0 R /XYZ 84.259843 429.281993 0 ] -/Count 0 -/Prev 984 0 R -/Parent 979 0 R -/Next 986 0 R ->> -endobj -986 0 obj -<< -/Title (5.2.7 Minimize the admission of containers with the NET_RAW capability \(Manual\)) -/Dest [ 825 0 R /XYZ 84.259843 763.220079 0 ] -/Count 0 -/Prev 985 0 R -/Parent 979 0 R -/Next 987 0 R ->> -endobj -987 0 obj -<< -/Title (5.2.8 Minimize the admission of containers with added capabilities \(Manual\)) -/Dest [ 825 0 R /XYZ 84.259843 431.026036 0 ] -/Count 0 -/Prev 986 0 R -/Parent 979 0 R -/Next 988 0 R ->> -endobj -988 0 obj -<< -/Title (5.2.9 Minimize the admission of containers with capabilities assigned \(Manual\)) -/Dest [ 825 0 R /XYZ 84.259843 315.226036 0 ] -/Count 0 -/Prev 987 0 R -/Parent 979 0 R ->> -endobj -989 0 obj -<< -/Title (5.3 Network Policies and CNI) -/Dest [ 828 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 979 0 R -/First 990 0 R -/Last 991 0 R -/Parent 860 0 R -/Next 992 0 R ->> -endobj -990 0 obj -<< -/Title (5.3.1 Ensure that the CNI in use supports Network Policies \(Automated\)) -/Dest [ 828 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 989 0 R -/Next 991 0 R ->> -endobj -991 0 obj -<< -/Title (5.3.2 Ensure that all Namespaces have Network Policies defined \(Automated\)) -/Dest [ 828 0 R /XYZ 84.259843 318.510432 0 ] -/Count 0 -/Prev 990 0 R -/Parent 989 0 R ->> -endobj -992 0 obj -<< -/Title (5.4 Secrets Management) -/Dest [ 853 0 R /XYZ 41.740157 784.430079 0 ] -/Count 2 -/Prev 989 0 R -/First 993 0 R -/Last 994 0 R -/Parent 860 0 R -/Next 995 0 R ->> -endobj -993 0 obj -<< -/Title (5.4.1 Prefer using secrets as files over secrets as environment variables \(Manual\)) -/Dest [ 853 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 992 0 R -/Next 994 0 R ->> -endobj -994 0 obj -<< -/Title (5.4.2 Consider external secret storage \(Manual\)) -/Dest [ 853 0 R /XYZ 84.259843 568.851496 0 ] -/Count 0 -/Prev 993 0 R -/Parent 992 0 R ->> -endobj -995 0 obj -<< -/Title (5.5 Extensible Admission Control) -/Dest [ 855 0 R /XYZ 41.740157 784.430079 0 ] -/Count 1 -/Prev 992 0 R -/First 996 0 R -/Last 996 0 R -/Parent 860 0 R -/Next 997 0 R ->> -endobj -996 0 obj -<< -/Title (5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller \(Manual\)) -/Dest [ 855 0 R /XYZ 84.259843 684.651496 0 ] -/Count 0 -/Parent 995 0 R ->> -endobj -997 0 obj -<< -/Title (5.6 The v1.5.1 guide skips 5.6 and goes from 5.5 to 5.7. We are including it here merely for explanation.) -/Dest [ 857 0 R /XYZ 41.740157 784.430079 0 ] -/Count 0 -/Prev 995 0 R -/Parent 860 0 R -/Next 998 0 R ->> -endobj -998 0 obj -<< -/Title (5.7 General Policies) -/Dest [ 859 0 R /XYZ 41.740157 784.430079 0 ] -/Count 4 -/Prev 997 0 R -/First 999 0 R -/Last 1002 0 R -/Parent 860 0 R ->> -endobj -999 0 obj -<< -/Title (5.7.1 Create administrative boundaries between resources using namespaces \(Manual\)) -/Dest [ 859 0 R /XYZ 84.259843 720.651496 0 ] -/Count 0 -/Parent 998 0 R -/Next 1000 0 R ->> -endobj -1000 0 obj -<< -/Title (5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions \(Manual\)) -/Dest [ 859 0 R /XYZ 84.259843 604.851496 0 ] -/Count 0 -/Prev 999 0 R -/Parent 998 0 R -/Next 1001 0 R ->> -endobj -1001 0 obj -<< -/Title (5.7.3 Apply Security Context to Your Pods and Containers \(Automated\)) -/Dest [ 859 0 R /XYZ 84.259843 324.051496 0 ] -/Count 0 -/Prev 1000 0 R -/Parent 998 0 R -/Next 1002 0 R ->> -endobj -1002 0 obj -<< -/Title (5.7.4 The default namespace should not be used \(Manual\)) -/Dest [ 859 0 R /XYZ 84.259843 193.251496 0 ] -/Count 0 -/Prev 1001 0 R -/Parent 998 0 R ->> -endobj -1003 0 obj -<< -/Count 143 -/First 860 0 R -/Last 860 0 R ->> -endobj -1004 0 obj -<< -/Length1 41480 -/Filter /FlateDecode -/Length 7852 ->> -stream -x| xUԭ^tg![gO4M -(@A"F&!&,*DDĀ"""θ=pЙ :I;Uof{{osV})`Byynk37#B vnʿe|'״Q{ξr@Cݿt #C~ -2>=s/.`Ծ}2|ExaV@;hZ\6sμk pZsfayቑԶͼoI/x^2(/in.)S^@Ē9 %.p?J.('~)s_vL7x93R_`#N/ShT~eMmdn_ b󛫴l=q8gLѲ -p3Qj0~=P_]O,X -D=m;ӮrV -ŐQCPqTbGk̓` t~s׵v(@vKp 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0m V@~VH|M5=7LJPKW/_C&0nQ0C!,(E~>\C#vFL ~ -&YH:xҨ&߭oMMm%f?)&7&LROɟm1séo$j-{ڦM"F4yxv<0anjA/WKo3oVM¿x1 zxJ x..Ur~1 ϩLxy=gřY:~'*~ƏC?pKC{ߥ.ӧn⩛o#IQ*J_x9#Qx T|sSo_W**a_VUC*tb˪$ѢbCY2iϓ>?I?O}*T{Uܣb/_㮝IbWltI/SqϺplg2q.P[TMlV)>DxOD&n*aMS1;>zT*ja2gIf*%#*]_UqM||x(Vj7buT*Ԫ$\ğbSPqRq*?YTDťK"IKTߎmȂ U\p/82X\*&T,Y3Q T4 aeۆSUS)*Nd/$ !UH;O<89p͍o[TwCSfUq Q1:GEQ7W#q7~8>x.q ׻0wpqpRq p.Ɯlq` ̼*2UƊVV,;fbIONsIԔ$:S09*1Ɋ*&qg E{c"(`0FEF -S1&FGE!*hKE'\vl"HEUE**4LQF%)xzQ%2|?M ,8kOҾ:z^X uvU~Է.IYDZQ6=hd q>6Y:'RtB*YnopXhfC9/1 [>.Z<5 *7+J^ol",'fv;Vi؀ i8|+pŋ %Tއzk^Fc?qZNjPI;Omr6%.ĶY4I l FBM@X5&m\̖VhRk/4Z #sMhmbA< f+(F h) -5@)fýTݰa=J: |Rxao4(.h߶u_Q:'dc!Ž|6&<: D(|k#?62UP:2i`~2@ 4@ 4@ 4@ 4@ 4@ 4@ 4@ 4@ 4@?Vuu[<0(bJI.1s 8Neyxd|6mTU{VpᒣHoIIUqHSi oQ85)x¤nrۑ"h1'Mg1XS9EvR(Qhu#6ݾQ*1 gjzȱO[>td/WwLU?G6=@qҡ_RH\;S洠-&:hY4;Ѣh7>df$_bҷ#aڡ=F^9:{6Ʀ`l -Va,2X fSf)E$oJlKM+Ul5_f7bF'Xb  UԊ߮giaݗJ!cmĹN\: NC"bأBEDT3D8:v2΁:. O<0g~p ݕ$:-MBcl3O=22zbоZ}QZUO#-VXiNŦd')_nۭ<&6F1s Xcb%RH?`lxWwy6YӅ -⻟TAZvx>Ln;bF$4;׆ Ã̊5d:wNef:?rR;y7LE1ތ!)h_/ccq)e)+bbUq+kSR.tM5 [WS[-[,vwY\Uq?{3!|sw׶ g -BsܹN*IZn2_"YyZxgmk"=\(0GD$sZMxtR K]b aCϐHהZJROiyRH.G{ JvwlQvƯPm.@+L OqS8ոlo#w}|sLm'=L | N>,~<~@p%#q E&(b>S)W)z^yͭS1Ebv%X`ƕRx"&\oj~wMË7KZ0b؄-;SWRwՒ{:\wIWr"IqǏHը:uUCk-}RHLrN%eOnmyeu/K䩖TktwwhjLjl7-.1eeumUK{3Ĺlh c0:0{a$FI!iU-KMkHN)&YZ$KcJuLJyo}o._;coO~YO;5uߨ8{OOH8=1Iu7Ѵ|9ʿͤB Z*dLkZCq.),}1h@E.-*8bVS˧VU/j:m[^PnмnI}a/ꊅVwmG~`@fvYUB(&;KHf53{= _{; -l9W|߰xEܡq=xT2|K \arșqt?i/7`ڋ/_|yxPߊh~6+x%_ŗu|Wh֟9za/)YI^% $e(yF()O}p;|,%%r -䕰Uc5ŃUr=Գ|n6ܤ|ji/U~]T>w})D#ŀD IS[\xP9c4tÑetsϻx*_/ǺZTs/dR:qU -#Ǥ+PMzZizJ2+ؘZ2]5F4P|aJh[R c{]W%s)*{=fhLˤOIq-%=5{bFWit^j(EhԔL26G[&N4 Uי[Z -Q)VQj<{$iұNybTH&.vƻds |yA#4ܭ8%+q؄)=8 <|Wْ{Lqb,]{~j iϳ䣛=ϥl(e)W$3wH3VAayu/ g:2Y1PK`>̂P 0t AEi4 h(|0R(KSm(Gۺ*[3:,FZ]sw@;-̥4q8yB}aP_m>PK̥Lug8// {?\gJ9QDq0z]/*,? NZj;j7'r[ۮB4G$=uk-3/Ai&nm:sE1῱<#v%&{,l$Y8lJ(vH#9K&lSҭRМl9&;fG6x+ֺ"a9Ԭ4_i7Y7u^FȺPD"ZDCĵ9Ct?JO߱v[/̅i gA¹T̘OAT9l-)KcJfLمs RV%P;wS:p_8F.(;mS7kfUJbwTHN6% -!|!YO y}K^*džRL/5?/ rm`Hۊ/ (>Z6+O>N7X=t{qUW:X=5ъ -endstream -endobj -1005 0 obj -<< -/Length1 7456 -/Filter /FlateDecode -/Length 4548 ->> -stream -xY{|SU?4iB_i<ӄPmn6iiKGҖݦj-!ˆ2ЁQE( ̌: -MBws~{~"Z4nuBKA -pQN)'+#-a#7t{rnjd"y#x|; %:e0^myk=n} qƎw0}w}Oxt;d,QDOwe] 6|)[a=3z֟Mw9<M"8A w5 -k(94\Bi]0CYƎBAxTB_ZѢ З_I -~N99ͯL>k@-G2t :HuG -# -~HEkPG,TCld咍ȄΣ5SsQl05!#@ -d#ОSȆB*yסZ^}EX4 f! ?Έ"? Ek:+ c PlHJ&$xja@;8q~#IE 4B h[_/+0PZZFa#K;ۨ@NT6a!? UA}GNW;$zMbv| O#`>Mn0+-St2̻p|+ q"TAG&~ AW1RfI5E}D>  ^ ~8+!KCrBjCzB 9!ܟmr%"6LB -fɻpw"2X"$bOo[]O΅cǏwHw~z{jH*=BF*6:BED)-ޞ^!8fh qs珏s[8CC"YHȐx|0ˢ!Ů]+ì䩂,mcU3UN4zAL%S*V̒}T~.^]}Cz2Y䱞<(7>?x]JwAqtV-Je9-V[Ay1(>>}]Ùn *ᡂUG*6N% -hVRӳkw~Rb A5H78~7OT C՛M7 lGpYxܫ.2f&BE$rDwH*^x!_0z\-?}OQг`1wQB`tR,OOk5kZJC756IriVQjMuաAa,gZwsՔm)JI ",BaT gt#4u66V 6*9yɡC,l"|a8}JbK|:ޚ]ֶmaUCSRZZ*X_$;XUԙg+k>P?+a7`24&N&UFKd W*SزY屶 $aT35Lo/G2-gWסqkXk]J -[Qm pc;@-F -Axzg$LKϐS -3>Z=tIjxQ^iU,AGnzVgW#n]]qP+|HS\x|$ (jo:ec7Ŵ -Qa^3%D\mݛi v[e=f[<yju]{h[2䌱ˀ8H҄.N~5A!I0d]٨d+y !R*E2?s2OZ_6:?ykst`^1|[>)cWb_ޢ&o {\>vZ}v+ͫUd"T^2W^dek:I#o:)ג@Npp=\i5 x}zՔӍ8#:m~cp3eeDـ,whߥKd)I;ݳu^e*!̂߆H15_?R8%xt򭅜h/~_(56|d3|3os F!^HjAjvL /`Q`MAw1&O)+nj5ڛvv5d'FD -'ivrO:Vjd7 @0"B$P;) /3Kͣ ~"b>Vso|ބ^ZicCX%;wi6C+~CŘ s^YIJIoܩužR/ gI t9I<9Y Z^I4n328ub>`6PEΧ)--%QcWQ]@ϖDzTd\B3fdঝ7nwďsWD_¼>K8LnYϛ씨dxrOZi{(8-] m@t,5 Gj X1M9%kɠ'2|HbK@y/dY0 g՝bX&3t.hbbq) :me~mmd1|~p/ uf!9 -a]__A*H"XG촗'`{24c\iSCtlnѫSy:&5&)^'pm(2oCg1`E+)o-6:\>p)|aa]o]4d&r醊-^8tQ}!]J}2SБhҏF-k)n0 ]Ғ# -`wLsC J"4Ք35sJ`śͥ&E.]H*io-/+ Z Ee1k 3y4kV?w um, -W59]wם(p7s`,aooĸ4%V/-!>;$HeCas2?EP9/Fu2agßYecӹ.$ڭ *qX?SrJNikddVLF|׸I -?R2wd$h2YL DA|<&m<>܂h ͷ\p:? sHl יꬼw Q Ig2 CO̊EE1Yx9q$!IA;~:< ͂_^̣O5:f`-.5YƊSשJ2,5۱h|4UXJLtj]&%rtRY#u's1Ms<;z.WLx'Ϛ8y%in~bJs ʹ#ɾ@Hs2.!P5f3̴\6ϖt8{N&_-S%UX I)W%0ij~4!mub84lZh\c@ yn:Sq!~`Z[f =q^Xky}߃WS+3^ -ΘLMsAkW'k8" -+#YX| o< ,A6%(Q{f{)"g#r. X:(<6nHpcXIDb϶'[ =Y/LGVDJW?K`Wv<sq( ǽ1(zYL=u؈?- >z#` -/ÁwhxB]w!Zcu4PjAher@Oԥ> -stream -x} xEh-]=wIn{/&5 pŰ#DDd $@N"$"@p"F" h\@G_P P1$wouf{{]]]]uUIBQPH߫א;xWAm|잽<ɞ6p_{ ۛC }==ο/ЮʠۥOknCM/S|B9qz{"C -'LI\FbBbWyم/ oĂ*5<Ϝbýxi%&Ap;EOn=(3B)(AC?=ZAk@+E3KϠ0_ӏP!L*D$چSs<#5, +y׋1TؒBT Ǧ"H5P plcxypLЅCntًsPYho&|/wgN핷نgm"O$f9R_kJ gV=BoGihRGFku(*YY=ю~ <: KE>J[ШD @"D @"D @"D @"D @"D @"D @"D @"D @"D d=K)j5pF繠YB;5VG3( Ah oQ h<M-y֯ -I`o$+Cw ?<Ц-~D99ä86WҠZ)_i?g7n3۞yPy0wP =gbJ}*&'u^l/G|88P6Q %!5~e"e4y)Pkx2(cn)165N:(m؊sq')`3z,F@6cHO(΄u u 2ubxS5JR!o-݉ec^(%5fDl(T?rNkf^kMk8jo@CoÜz?z//ϥ]NOYoӷ8=7;5͗؛}l:ݷҽo^}ca{uuNwsM_t';8M_J}ynӶ29Vb}ӭENp9N7qqmtnIQk:xe]"] 5y9N<[7AVKCjNWvt%21TOW+i3]U?鏜>|xC K8}'8]"N>d 9}Ȁ*ZqCP5< -Clhm$/2"Yh4M&mCRPzUBE>Hs4LPCЁq?I9^MH.;N8ZVYDq;< o~D?be |  BaLGh)`ǀ {4S^Rvb Xd ; xmA3_`N.% / U `7GcRw0rhNr φv8mydCY zoR*˥a ~x=!G?J2LžÑuE0`#F0`#F0`#F0`#F0`#?\ݒ}!Q%Jr _Ȇ6) -TdrHv*=*+=V@2) +J\ -Ο_ƿ ;s"r,,zĿ'WCIh(CFj?U^ح33*#I x.lSW-j%ٳ?g;~KrQJIu -8EIr?@dڱ m! G?*9S߃Tֹ%A2ȼr4 wIY?ϲ?O:K֎]F&BNF+klb-{\10~JR''5vOLlG?r%6iɓΙ'c~p -N!Rc.\ |c> /3q ^Χ}f6lcKMScXb6o3NR}ʘ6saet 8IjS} )]@B©_TW+IkUׅ^OC}._KLמrm a%4]RYr#D-HMhhJ3s}SOOXrTi0Ͼqjf -'];ttTy` @:;B~P -Pj "jR1LhجXY.0S] ?յ;,b4pIBA{>oӧuUuK2~ -IJŠ -žұUlW˪D hCD*J0"5kۅn0cӰ?O~'ׯSi~kw{~}:n׫עj# KbJN!UxxJ -{E5f-KXoyPXy*&O~2 - ^Vh%^!U.VxVJ35=HU9w -a'YNj2:6ʻY2n&zlԖ#.qVpsIpYA!(EaaZӱf~K G~`P|(\V퐶  9U{-ثp Nn ^}ev ov7]SQN(^_]##F%mZLPO+/ 椟-ZXB8*)]J iYf9$۠3IgECIcBѣGҒ"}.&=p']H .^U7s|>xoǧQ> -lًbv yb6jߦbmHnk1-Uw4l7& zS6 QǟN\:SNKu_f2mx=.xm7_}Arh6F%G%6ȣpA#ҶxaGp(H?_X^;gM*,,ms}K -^?\ 萾:L(-D=c45bj]kvKhmJdBj=gpl 0f䐭wCo _i2#B '5; FBW&t>#{8T~@Uѧ)L'D 0l7w]2cJ ,HJRl~TzLުDtEACp6LB6M-&%ՙkL4Vͺ zΑ@]Kd@Φ\f(:d"*҉Yot]+%fP -D'J4]ÙuP3LLS)LKz{z^60GF\T{&6#>jĦ4q+>էV;C^2\O$EJ,Si/JR9{igAUk9։x-P'kyG3j x Z ~ -;?ͷ\[rv i%eמk{x~^hhn(A )+rPLdójuV\N2`oýq?y(.&ri~MzI;A )J! c!)mću_# ŨF#'j)mh(XL*(+"-XlGn,O -$}/) =?ο ?|AվG]]6~ς Œxo')ўף;a)$o3/=jHG5c a3qUGP4G˘x78oll\\l|;3=ԓX.%ڮx/iD;)97{Ҥx;e>uo4>bB00;OoU0gX xB% -JnJIn~;fC\X"Q7絺oONUW԰R~zJ )NY YY,~~azn¨ѾE EE"@\bXizlbo<ٴټٲ5akVV@\ẓ#ExErz),└pR.IG|;q#K7W~KiC\؏s6N zGL ޟ{s^i~ryl=BV9|n~SWf6VWv,;x ~m=ܳQhA(0I"2q4 -J% 2S;"" {$jI%dh41R4~7>ROOKUGK/O'x8p膐\R<-ON_ʀdzIڵLܔ -=SaeA(1Cs9CU&_ 1)"x |ٿ$ -vyfbvf׃3ά;렧 MF|}7yUeDi$=$FK^V]Z)֜BZΚ #]Jgirkaݭ}i/3pAa`uv)\pN'Ju6End.2ϢM*̻7.#ān>pτ|Wx6Hm8]{ -$V_ {d+B-n/JT -ɨ~D:3hQ Q( i\FB$鐐GAܒf4MM!p 35qծ{ -C5-7{m ߉M>ZvAnn 'lh{pƘ^#*c,v#d_ RʥEdEJ H7x5fΞ=s9s,=uҝx9.z˺u[^\Erzl.wL2@V^XAǢd=j9wHADJ ruyMq kL\XO܈b h2.Vy&4{|+F톽$u㟦sg|>X;D1J8{W c=;KBa"x%E+ol y -Z:{hSm?bxɎ w3fϦ{ɰ7b -78ztI|#@az5bF6smAboWdDpX%tOD[G,yL}ò.+XufXYyo' -zl^gh;+.%C'+ogجZ*ЉSA,6+7M½tZU^O_?#H!6_ZpI0tɻt^}e?:eGhFwbȕbVi6HJQ>9]HZ :Ab =.Ar>,e%[lX[7 @xq{6٨Al>VK|浪qwT]4s; -Qs >jŽMT޴|+7+GQF("!:>lhĂz;,],zÖܵ>-mgw7H–cpREUOtzm[ֺExI)/Xvm{" - -YCH7&-O+kҍ<1xwm6k6'C.c]ml\Zy0R/DhEK*#hk`sF DBq(MR_Vblg'`:(j,Q}|q{rx֓ vC,@l)R^IQr!wA'x]/siOUXXD p;KJ]n(c5eںOH=S^|c)oӘbԨ0[uvǯ>ը@PT 9QhpԪmrO^Mc5r5oެҹsKAAz79s^Z%q`Հ۰ 6AIF%"t %܈3gtGĘmDe󷆚uV4cgBII BL7v&v1!Ҍڄ4ikb@\qV%B&Q&)CS9DC'd@0WYQ`\?6h9 g8 zCe RQ((T'?G!9|Evc^Tj (N\e,> ,fb5e&L/1^5yTZ6xtivg YNUylo!a@5њd6Y4K5Zb1j[֒Rh].ΖZ?eyeGۣ11UVͪ[L,SǤjbdi-⇍᥵g~8p\ع_5EMdӺwJO Ϻ!U[;cYi,j?mH|ynbC0-kewz&h`(WQDYnd UW -'^Lw)>Dmv#wɣቊ@SɄt;yV=ѫXl(^^D8H$D*;%Ycövox"sussux":<qןu$#ŶϊKJXMR`x5 qe^GF'o?7i`0W|njn()$2ta<xs/zGu'R2j[T)uY4KJS{^"> ?By%ZW -V.oi>؃'|W[Ck@Lٛoُޏ(#:qW#Ğܺ_ ,Mml:ѧe>  Ⱦӣ=+(fM=dܜbrK4f ܑtaJ'6swko~1CHmiyIcY ]j6ARf&j^dy 'KERu ZAʥrRA$oJoBKG9'M>пFoяrg !4Cj=>Ϲ -ڟI;suX;/@n6Öl`ef ٠-hՉ!} E;6ISG/ooZyg8(;OpQ X6pXb󩀔e=m8M֩#a20Ճ-欹\6v͔3,k'~ROS@ -c1ye-[VUzx/-Uj-['G,Gl $coON^pm =^XVժט[*JuZXwDʫ+G50' =+DqcMq˖@O_ҐbףGv=1;YkIV;baUi0XoPN@FNwj t -o$&qqilBYqwq7h;w(S+P=5UW,be6v mH7rz4e]Ol6v/4Bq*!WS+hǍM`ww&?çg*+^7ךPJ.ABTZp=!4P\@ݩJ6zMZ6:b{}Š}2\{ދX˲_-jhiڢ!ʒf.CpdK͒k+b'H(;֗ -,-AIխC>$ݬ"nV a&!U?|CC 1CTtg(:aie,Q$ l:Z1f듢@S7F+I;Ɖr 3k.nFKqyqW5E~Ԡj&Udu@nz6 --u#R_o4WO/Zj/>xbZuQAʶ=1*1B -PfPD;_v -1tx+"ٽ A֩%Q 衘DK<`t=L5g8l臢$IscF<]~~J&~7+ 5|Y>~S}_6>n}~Ys&c{E)ݸ~`y-ws 2>~K{|!7(iNyʹJ?n2l\][U_M,7L )Bo麜w]c#%/T \j(~  -nK-O{:tl -_ o4i4[ nh%}'÷t"{pt %V৤a Bdx7-cZ_ٮ_ojh8G!'&-0gL -JWa@q&P P -΀EZzQ@ x@ @ħ=CaTk'y8= s4} _`hYiѲ3'eτrb (gϘM(( 3 -eCcfJ|lj~__2->EMȟ(-K -Or7!˩&%# Bjl9++AmPp e_xY -endstream -endobj -1007 0 obj -<< -/Length1 17024 -/Filter /FlateDecode -/Length 12118 ->> -stream -x|yxTŶo {!I$B&4aKKo`'ۧPF] ^+K%@v.'{XF' -Nh:Q5 msPZ -u@~"EP< -{!6H(ahV޹u FphOsWokț$ -`)ּx *}w;}X o\[wΰB!R_O~G/'w80; vwr89|>5>~ -&6+InOwK>DVcQ؎*j$`bPVdE m}V7ۋh% {=JR@Z]12F[WR?N;Bo(eccejzKx} ZI}Bџ)^+h3hsݝ;W+"~)~7kF̥_1GoKKF/2v F?*觟Od^N?^I?Fԍ^`TCF?PyFgܓ\g={+62z+黌bFOn7 `8o3z ;fG GzFG?V ooMo#^zC&pE߀2z=PDB[kcV*{0ʞt'"Hw[K/&//&ӿ2.Vѝϛŝy3}N;}yFZXδƯ+}t#֧ tOӌn#)/-aM6QODY-z0"cBѵŒ'e]'?W1t!t9K}%%&#gc1a. 2]`.(.A'yMsNgݢ3NgiS]4F"8E0:IN' Ett4X=.ьbpt:gtCmtq8AGD:)ȦZ')g|h}M̳Zu yMb޾Ǡ5ëkЉ[}"=hF'n怀sh״@hVMb4s !vH3h:ܘh\N4j)NY&v>B;6\GS(ɭI>w>I7#&0oް<ۗv0Qq&Ǩ;6Yt4f u.FF1 N# gɨzp0{G6hO63 Bm -[zW *G2z>!-EꜲ@EtnFP? X 7$0nB7ғ̀NBovb+gD׃BSI&gPT'dp!<#s\,x**'NFs9Irكʥx0YVpRa2AWϩ&@cqGpn/%3:Ko7 4mh<Ah!̈́j`K7 -_ =27@ i cDP1>t#y%Z,6qx/n{dFc"ZLw -Sb/R4F:.G=FyWuX[۫PUvYmOMlL47FMSii)^2d0O56_YVZeuZYKBд7C-e'WR.8 -N\鼂@C1>-֡@eL%/hNIC)Wͩ8B=ԒaQlj}=1Ъᴆ~–Q4!A@$APhNC1[>!3,a쒕ဆNZ6I&iї̿PgZ83-Cw|a[B+0<~NX4qTc:w<+31 jR9}?u"7~z\FR\щqQH{tħ;o6mO;"`&%ծGvǨIn f5v-g̀suιIr0Ɯ'.'`/Cϝ7h쒺uŝ;.Y_{kGc <ķ$99:;dZr(scŇ_ ^wG9wN}|,뾩3!a4;I 3dfiQ^A'aQ6(i8Ua(u!;L4P%TV{W ;qΕ>'\ -ő -alG^:&cP \[ 䆸*i -Ņ m5YggeeNk8<͓驧^6ʾSu?g)c*f /} _>ל+SNaDi ׬M `W0*ܤ4hM Bװ_ -+=bJȩS]fn$bYxŚM][\]ukdº55|_pC3;MhWX `CmDdY3<^zͬǥˬGwwx^h7 $X_'QcB-TRaU *I -7 z]Qj& ((pq3 S(^f WHb1۟g9xbY `EDиZ%k_{¢ZIܙ_q;|θ'dkP0BEZbYQpg1A0kz@"K:kPpUu"%731 |>JA)8!ELR%EsQ.%4Ws\9W媹h(JC$ua5[qbf& ޣ_ :lhNׁKK7n*-?Beu N3}p6NfO5/ anɇSQF+R)QNH. -)lku[LoWS}xFX2n"A(# H$yfJ[* 2.Gv6acky/`q6SH煑3PvVy J^B̢-ǽh)cM555'q^+ܔ{iW1cym]zQ?7Үv+Q -JǰPDmxt1^ BE3͠\993!EЧz2wDSe͜l۾tucg-GgX@cN=;R/U_"1ploxM0,k/QjCT/Wa\ B~?7rk֠_NOs7H#U K#S[Kh?E+%Ѩ/N#*eKyH*zc\.pa5c\|+JPZ(fm^ΑֆѝfկKOxoy5lĮ}~=WfaPc+՘J7”MBeXB8Y¡1^nhWvڬAT9n'!rḠBMZ[.2/؃mkn]nzaoľ-~/x9:/DKa6-P/\JW<IEbdAs)-m1q I]J~!QZ3ŦQֈI<$2D@NL*]ɕV : p;L:=2LTfmָ,Tr@2w ۆsZ 8z$JW&7п PM8Ɉ }~AyEO@JlSG0},RUZJ1}xLBD -ӣteMus zc.6kޘAC*^]&Ə=?5[|kny`|r⊍Oo 3XE+)n丷OhW8 ̕ -Zn@iRj'w6'p'|#\8.8G5x@ͨ ' _)WEx\O} A%Rn=4IȤi!MvS@ngYn%4@ۂ9s\G>-Vﾍぷo/SV30o4 8rDJ*ui28 6% Ѿy9IoI6>Jr/_> -гu{C붋6ݝz҅gykZ+aQ4sG0Qu<"].exbIŌYM{S8S ۫jj5(HiJ[@"JAUE NXZ$FC$aC,O&B]Y..SVBYDM b')IWO'BP̥  @ Y[Q-,|;,yFbkp1pX:}MͰ.Y)W?n$EbS0- I&SJTLʄ" -6UT%IHQ%j ,64݆T&:s`'u(N];x<9\V,i4gIborBl!$l my_D+*'J7dILFTKm11@лtC%zW*.&cp\ %x5[ sD(ĕf[ͪB$ZKa Dja1˹B˿/{nF6 s3bJ빭[vlñR9>F hy+8bJ^*P+4O -JTh ITBtfS]Q$Yr, fN(m>/ sh9oih;?=0xŴq ,͛*"of&n`2_֭`z $DuŸUoL+Oջbl҂_G/ -KUKD(>2'$&ĥ&|'uiXnLWEUF2/ 戣=pxBW: -M,=9c7/]|vVU͒ /wޣi<δhWr}6XxlxJ}l.PXO63y'B8[ eF?6̙]`n'7̟޽GY_۽[NrJ۴t#1(JIYj2 ISynR768& lu6|)u 貯xTU*'ք BaE2`/2x*U >)(%:ߣK5s+sp{q%CcgTH쪎%cECO`1QIyLҍf -J7]}a$ǒB:Z%ÕѺBLea}\X{\ŴdCdy͇{O^:x(>4P+.5ek@䡀$}!>jx(#=0:I,tRPw++|~ ? wL]w 8v'2q^Bb#$ū>F)O';+Κ>p9S_=͖|[]%ydmJ(h*H*y}Pe$]^0V_*g,Xޏ<?:<T*6k^/J df@'c!Ik{3tLx.>@O[`i5ۅ<_BJ6*.I$ ´'Z(גnǒawsx?BV< Adx#OK[cad62o|dS"tF3fR -Y\WÌMo:I{7 pv -?l -f< -KG&:24htYzkӈBx* -&oR[y*K6穾ԘTwj\5դZ -vT;ë#B&`O[+;Cyt4VFf]:XXR.m>tmxl܌#'{ǒGM_ᎃZ.#ǣ-R0|x) pR}Nte*S}j4HRD~4pHk8“mm*kH@|zZxݓO+^UggjcQU:g7]3B;~b?Gld`tQ/Pj./,g!#|_2Ѭ!}yT-=!МG֔եYWHmR[ͿH'O̥vu+Р>KVXu%VU0} b|<]1uudJy9#2:FQ3cD-")BǕVBt$H!( -!`5%jmR୕R!;~,,)vىw^ʥ ,I_7&&:h H208 f tXwsz,r,B;(TxmD%8EIYJ>AE0)KSI bܝv#g+hώViݍdr9ħV}K_[Lv0+Җ"h'.˓=x_|ѓewRtep8_$4@ >LBhTqqĢP[Hm?-$hAsON)Tx i=EGq_=#xt|b__=MU,^t@ G !$Dw%DQB"LH[b=] I(]1ģxܑċGd!Yb#g(= }]~aRcAflqnq\|BQ}I '<.ƨ1jI{^b:FCfd]&RWN[[Ive~`?p)knWI$_ DA0A@>RաS1?USe -8 H"qc[hGgˏe$cE݄.Xa:G8&ձCM-|w Z,'N6?9c pjEվFG qYV{l 1!!w7-h|?6e7 }b0Ŀ6T҅(W U֢〼\*s1>{ѴPN(KrE+=Mn]IS^";@[v@3|&^"hH_C){m^N;hU %6S5e GtD`>KREz1po-kW~=:}.J7ea,?ާ= -endstream -endobj -1008 0 obj -<< -/Type /FontDescriptor -/FontName /EMBABY+DejaVuSans -/FontFamily (DejaVu Sans) -/Flags 4 -/FontBBox [ 0 -14 557 560 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 560 -/StemV 80 -/StemH 80 -/FontFile2 1004 0 R ->> -endobj -1009 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /EMBABY+DejaVuSans -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 317 ] 16 [ 360 317 ] 20 [ 636 636 ] 25 [ 636 ] 36 [ 684 686 698 ] 40 [ 631 ] 42 [ 774 ] 44 [ 294 ] 46 [ 655 ] 53 [ 694 634 ] 68 [ 612 ] 70 [ 549 634 615 352 ] 75 [ 633 277 ] 78 [ 579 277 974 633 611 ] 85 [ 411 520 392 633 591 ] ] -/FontDescriptor 1008 0 R ->> -endobj -1010 0 obj -<< -/Length 772 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -32 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0015> <0032> -<0003> <0020> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0048> <0065> -<0051> <006e> -<0046> <0063> -<004b> <0068> -<0050> <006d> -<0044> <0061> -<0055> <0072> -<004e> <006b> -<0010> <002d> -<004f> <006c> -<0049> <0066> -<0024> <0041> -<0056> <0073> -<0057> <0074> -<002a> <0047> -<0058> <0075> -<004c> <0069> -<0047> <0064> -<0052> <006f> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1011 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /EMBABY+DejaVuSans -/Encoding /Identity-H -/DescendantFonts [ 1009 0 R ] -/ToUnicode 1010 0 R ->> -endobj -1012 0 obj -<< -/Type /FontDescriptor -/FontName /JFIGPQ+Poppins -/FontFamily (Poppins) -/Flags 4 -/FontBBox [ -27 -132 753 704 ] -/ItalicAngle 0 -/Ascent 1049 -/Descent -349 -/CapHeight 704 -/StemV 80 -/StemH 80 -/FontFile2 1005 0 R ->> -endobj -1013 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /JFIGPQ+Poppins -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 266 ] 5 [ 291 ] 11 [ 453 453 485 682 197 550 209 475 627 319 574 588 628 627 634 545 630 629 212 ] 32 [ 722 ] 36 [ 673 612 771 706 512 503 777 691 245 ] 46 [ 598 431 860 702 785 578 787 607 586 540 674 675 975 ] 60 [ 583 540 422 ] 64 [ 422 ] 66 [ 732 256 675 675 606 675 619 328 675 639 245 247 514 245 1029 639 639 675 675 372 521 363 639 560 819 478 562 454 ] 95 [ 290 ] ] -/FontDescriptor 1012 0 R ->> -endobj -1014 0 obj -<< -/Length 1402 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -77 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0015> <0032> -<0003> <0020> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0048> <0065> -<0051> <006e> -<0046> <0063> -<004b> <0068> -<0050> <006d> -<0044> <0061> -<0055> <0072> -<004e> <006b> -<0010> <002d> -<004f> <006c> -<0049> <0066> -<0024> <0041> -<0056> <0073> -<0057> <0074> -<002a> <0047> -<0058> <0075> -<004c> <0069> -<0047> <0064> -<0016> <0033> -<0045> <0062> -<005a> <0077> -<0053> <0070> -<0052> <006f> -<0030> <004d> -<0031> <004e> -<004a> <0067> -<0029> <0046> -<0033> <0050> -<0017> <0034> -<001c> <0039> -<0018> <0035> -<0013> <0030> -<001b> <0038> -<005d> <007a> -<002f> <004c> -<003a> <0057> -<001a> <0037> -<005c> <0079> -<005b> <0078> -<0037> <0054> -<0027> <0044> -<0032> <004f> -<000f> <002c> -<001d> <003a> -<002b> <0048> -<0039> <0056> -<000e> <002b> -<003c> <0059> -<000b> <0028> -<000c> <0029> -<004d> <006a> -<0054> <0071> -<0012> <002f> -<005f> <007c> -<000d> <002a> -<0020> <003d> -<0042> <005f> -<0043> <0060> -<0005> <0022> -<003e> <005b> -<0040> <005d> -<0038> <0055> -<003d> <005a> -<0034> <0051> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1015 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /JFIGPQ+Poppins -/Encoding /Identity-H -/DescendantFonts [ 1013 0 R ] -/ToUnicode 1014 0 R ->> -endobj -1016 0 obj -<< -/Type /FontDescriptor -/FontName /AHJHWI+DejaVuSans -/FontFamily (DejaVu Sans) -/Flags 4 -/FontBBox [ -9 -92 733 729 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 729 -/StemV 80 -/StemH 80 -/FontFile2 1006 0 R ->> -endobj -1017 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /AHJHWI+DejaVuSans -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 348 ] 11 [ 457 457 ] 16 [ 415 379 365 695 695 695 695 695 695 695 695 695 695 399 ] 36 [ 773 762 733 830 683 ] 44 [ 372 ] 46 [ 774 637 995 836 ] 51 [ 732 ] 53 [ 770 720 682 ] 57 [ 773 1103 ] 60 [ 724 ] 66 [ 500 ] 68 [ 674 715 592 715 678 435 715 711 342 ] 78 [ 665 342 1041 711 687 715 715 493 595 478 711 651 923 645 651 582 ] 5038 [ 741 ] ] -/FontDescriptor 1016 0 R ->> -endobj -1018 0 obj -<< -/Length 1182 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -61 beginbfchar -<0014> <0031> -<0016> <0033> -<0017> <0034> -<0018> <0035> -<0019> <0036> -<001a> <0037> -<0011> <002e> -<0003> <0020> -<0028> <0045> -<0051> <006e> -<0056> <0073> -<0058> <0075> -<0055> <0072> -<0048> <0065> -<0057> <0074> -<004b> <0068> -<0044> <0061> -<0024> <0041> -<0033> <0050> -<002c> <0049> -<0059> <0076> -<0053> <0070> -<0052> <006f> -<0047> <0064> -<0046> <0063> -<004c> <0069> -<13ae> <00660069> -<004f> <006c> -<0050> <006d> -<000b> <0028> -<000c> <0029> -<0015> <0032> -<005a> <0077> -<001d> <003a> -<004a> <0067> -<001b> <0038> -<001c> <0039> -<0026> <0043> -<0031> <004e> -<004e> <006b> -<0049> <0066> -<0030> <004d> -<0013> <0030> -<005c> <0079> -<0010> <002d> -<002e> <004b> -<0045> <0062> -<005d> <007a> -<0035> <0052> -<0025> <0042> -<002f> <004c> -<0036> <0053> -<005b> <0078> -<0027> <0044> -<0054> <0071> -<0039> <0056> -<0037> <0054> -<0042> <005f> -<003a> <0057> -<0012> <002f> -<003c> <0059> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1019 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /AHJHWI+DejaVuSans -/Encoding /Identity-H -/DescendantFonts [ 1017 0 R ] -/ToUnicode 1018 0 R ->> -endobj -1020 0 obj -<< -/Type /FontDescriptor -/FontName /LJVNMQ+DejaVuSansMono -/FontFamily (DejaVu Sans Mono) -/Flags 4 -/FontBBox [ 0 -14 602 728 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 728 -/StemV 80 -/StemH 80 -/FontFile2 1007 0 R ->> -endobj -1021 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /LJVNMQ+DejaVuSansMono -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 601 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 602 ] 36 [ 601 602 602 602 602 602 602 602 602 ] 46 [ 602 602 602 601 602 602 ] 53 [ 602 602 602 602 602 602 602 602 602 602 602 602 ] 66 [ 601 ] 68 [ 601 601 601 601 601 602 602 602 601 602 602 601 601 602 601 601 602 601 601 601 601 602 602 602 602 602 602 602 602 ] ] -/FontDescriptor 1020 0 R ->> -endobj -1022 0 obj -<< -/Length 1570 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -89 beginbfchar -<0031> <004e> -<0052> <006f> -<0057> <0074> -<0003> <0020> -<0024> <0041> -<0053> <0070> -<004f> <006c> -<004c> <0069> -<0046> <0063> -<0044> <0061> -<0045> <0062> -<0048> <0065> -<0058> <0075> -<0050> <006d> -<0047> <0064> -<0056> <0073> -<0055> <0072> -<0010> <002d> -<0008> <0025> -<0012> <002f> -<0059> <0076> -<0051> <006e> -<004b> <0068> -<004e> <006b> -<0015> <0032> -<004a> <0067> -<0049> <0066> -<0011> <002e> -<005c> <0079> -<000a> <0027> -<0019> <0036> -<0017> <0034> -<001e> <003b> -<0038> <0055> -<001d> <003a> -<002a> <0047> -<0054> <0071> -<001f> <003c> -<0021> <003e> -<001a> <0037> -<0013> <0030> -<0042> <005f> -<0006> <0023> -<0004> <0021> -<0037> <0054> -<005a> <0077> -<0007> <0024> -<0014> <0031> -<0020> <003d> -<005b> <0078> -<000b> <0028> -<000d> <002a> -<000c> <0029> -<0005> <0022> -<002b> <0048> -<0036> <0053> -<0028> <0045> -<0035> <0052> -<002c> <0049> -<0033> <0050> -<003e> <005b> -<005e> <007b> -<0060> <007d> -<0040> <005d> -<0030> <004d> -<0032> <004f> -<0029> <0046> -<002f> <004c> -<003f> <005c> -<005f> <007c> -<0009> <0026> -<0018> <0035> -<001b> <0038> -<0022> <003f> -<0016> <0033> -<005d> <007a> -<000f> <002c> -<0025> <0042> -<0026> <0043> -<004d> <006a> -<001c> <0039> -<003b> <0058> -<0027> <0044> -<0039> <0056> -<003d> <005a> -<002e> <004b> -<003c> <0059> -<000e> <002b> -<003a> <0057> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -1023 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /LJVNMQ+DejaVuSansMono -/Encoding /Identity-H -/DescendantFonts [ 1021 0 R ] -/ToUnicode 1022 0 R ->> -endobj -1024 0 obj -<< -/EMBABY 1011 0 R -/JFIGPQ 1015 0 R -/AHJHWI 1019 0 R -/LJVNMQ 1023 0 R ->> -endobj -xref -0 1025 -0000000000 65535 f -0000000015 00000 n -0000001200 00000 n -0000001339 00000 n -0000037576 00000 n -0000037710 00000 n -0000040416 00000 n -0000040615 00000 n -0000044367 00000 n -0000044773 00000 n -0000044982 00000 n -0000045193 00000 n -0000045328 00000 n -0000045464 00000 n -0000045622 00000 n -0000045781 00000 n -0000046014 00000 n -0000046248 00000 n -0000046463 00000 n -0000046679 00000 n -0000046920 00000 n -0000047162 00000 n -0000047385 00000 n -0000047609 00000 n -0000047841 00000 n -0000048074 00000 n -0000048288 00000 n -0000048503 00000 n -0000048730 00000 n -0000048958 00000 n -0000049167 00000 n -0000049377 00000 n -0000049606 00000 n -0000049836 00000 n -0000050047 00000 n -0000050259 00000 n -0000050478 00000 n -0000050697 00000 n -0000054468 00000 n -0000054933 00000 n -0000055134 00000 n -0000055336 00000 n -0000055551 00000 n -0000055767 00000 n -0000055964 00000 n -0000056162 00000 n -0000056381 00000 n -0000056601 00000 n -0000056802 00000 n -0000057004 00000 n -0000057232 00000 n -0000057461 00000 n -0000057671 00000 n -0000057882 00000 n -0000058097 00000 n -0000058313 00000 n -0000058541 00000 n -0000058770 00000 n -0000058970 00000 n -0000059171 00000 n -0000059308 00000 n -0000059446 00000 n -0000059637 00000 n -0000059829 00000 n -0000060019 00000 n -0000060210 00000 n -0000060401 00000 n -0000060593 00000 n -0000060785 00000 n -0000060978 00000 n -0000061217 00000 n -0000061457 00000 n -0000061672 00000 n -0000061888 00000 n -0000062095 00000 n -0000062302 00000 n -0000065877 00000 n -0000066355 00000 n -0000066551 00000 n -0000066748 00000 n -0000066944 00000 n -0000067141 00000 n -0000067337 00000 n -0000067534 00000 n -0000067734 00000 n -0000067935 00000 n -0000068133 00000 n -0000068332 00000 n -0000068566 00000 n -0000068801 00000 n -0000069000 00000 n -0000069200 00000 n -0000069403 00000 n -0000069607 00000 n -0000069809 00000 n -0000070012 00000 n -0000070212 00000 n -0000070413 00000 n -0000070609 00000 n -0000070806 00000 n -0000070995 00000 n -0000071186 00000 n -0000071378 00000 n -0000071571 00000 n -0000071761 00000 n -0000071952 00000 n -0000072138 00000 n -0000072325 00000 n -0000072537 00000 n -0000072750 00000 n -0000072965 00000 n -0000073181 00000 n -0000073394 00000 n -0000073607 00000 n -0000077325 00000 n -0000077828 00000 n -0000078030 00000 n -0000078233 00000 n -0000078435 00000 n -0000078638 00000 n -0000078849 00000 n -0000079061 00000 n -0000079282 00000 n -0000079504 00000 n -0000079733 00000 n -0000079963 00000 n -0000080164 00000 n -0000080366 00000 n -0000080564 00000 n -0000080763 00000 n -0000080976 00000 n -0000081190 00000 n -0000081389 00000 n -0000081589 00000 n -0000081797 00000 n -0000082006 00000 n -0000082152 00000 n -0000082299 00000 n -0000082513 00000 n -0000082728 00000 n -0000082920 00000 n -0000083113 00000 n -0000083324 00000 n -0000083536 00000 n -0000083755 00000 n -0000083975 00000 n -0000084174 00000 n -0000084374 00000 n -0000084582 00000 n -0000084791 00000 n -0000084987 00000 n -0000085183 00000 n -0000089028 00000 n -0000089499 00000 n -0000089636 00000 n -0000089774 00000 n -0000089966 00000 n -0000090159 00000 n -0000090358 00000 n -0000090558 00000 n -0000090715 00000 n -0000090873 00000 n -0000091086 00000 n -0000091300 00000 n -0000091496 00000 n -0000091693 00000 n -0000091885 00000 n -0000092078 00000 n -0000092301 00000 n -0000092525 00000 n -0000092726 00000 n -0000092928 00000 n -0000093125 00000 n -0000093323 00000 n -0000093517 00000 n -0000093712 00000 n -0000093872 00000 n -0000094033 00000 n -0000094230 00000 n -0000094428 00000 n -0000094563 00000 n -0000094699 00000 n -0000094882 00000 n -0000095066 00000 n -0000095258 00000 n -0000095451 00000 n -0000099307 00000 n -0000099794 00000 n -0000099953 00000 n -0000100113 00000 n -0000100334 00000 n -0000100556 00000 n -0000100759 00000 n -0000100963 00000 n -0000101183 00000 n -0000101404 00000 n -0000101605 00000 n -0000101807 00000 n -0000102038 00000 n -0000102270 00000 n -0000102483 00000 n -0000102697 00000 n -0000102923 00000 n -0000103150 00000 n -0000103368 00000 n -0000103587 00000 n -0000103823 00000 n -0000104060 00000 n -0000104278 00000 n -0000104497 00000 n -0000104632 00000 n -0000104768 00000 n -0000104961 00000 n -0000105155 00000 n -0000105366 00000 n -0000105578 00000 n -0000105781 00000 n -0000105985 00000 n -0000106176 00000 n -0000106368 00000 n -0000106582 00000 n -0000106796 00000 n -0000110880 00000 n -0000111367 00000 n -0000111570 00000 n -0000111774 00000 n -0000111979 00000 n -0000112185 00000 n -0000112375 00000 n -0000112566 00000 n -0000112800 00000 n -0000113035 00000 n -0000113266 00000 n -0000113498 00000 n -0000113699 00000 n -0000113901 00000 n -0000114106 00000 n -0000114312 00000 n -0000114517 00000 n -0000114723 00000 n -0000114876 00000 n -0000115030 00000 n -0000115227 00000 n -0000115425 00000 n -0000115586 00000 n -0000115748 00000 n -0000115930 00000 n -0000116113 00000 n -0000116278 00000 n -0000116444 00000 n -0000116641 00000 n -0000116839 00000 n -0000117041 00000 n -0000117244 00000 n -0000117393 00000 n -0000117543 00000 n -0000117728 00000 n -0000117914 00000 n -0000122104 00000 n -0000122591 00000 n -0000122812 00000 n -0000123034 00000 n -0000123248 00000 n -0000123463 00000 n -0000123681 00000 n -0000123900 00000 n -0000124104 00000 n -0000124309 00000 n -0000124488 00000 n -0000124668 00000 n -0000124867 00000 n -0000125067 00000 n -0000125262 00000 n -0000125458 00000 n -0000125656 00000 n -0000125855 00000 n -0000126007 00000 n -0000126160 00000 n -0000126350 00000 n -0000126541 00000 n -0000126735 00000 n -0000126930 00000 n -0000127076 00000 n -0000127223 00000 n -0000127425 00000 n -0000127628 00000 n -0000127795 00000 n -0000127963 00000 n -0000128119 00000 n -0000128276 00000 n -0000128483 00000 n -0000128691 00000 n -0000128919 00000 n -0000129148 00000 n -0000131463 00000 n -0000131758 00000 n -0000131902 00000 n -0000132047 00000 n -0000132249 00000 n -0000132452 00000 n -0000132666 00000 n -0000132881 00000 n -0000133069 00000 n -0000133258 00000 n -0000133433 00000 n -0000133609 00000 n -0000138442 00000 n -0000138697 00000 n -0000138958 00000 n -0000139226 00000 n -0000139493 00000 n -0000139700 00000 n -0000139906 00000 n -0000143668 00000 n -0000143899 00000 n -0000144097 00000 n -0000144286 00000 n -0000148668 00000 n -0000148899 00000 n -0000149033 00000 n -0000149167 00000 n -0000153295 00000 n -0000153526 00000 n -0000153660 00000 n -0000153795 00000 n -0000157936 00000 n -0000158167 00000 n -0000158302 00000 n -0000158437 00000 n -0000162498 00000 n -0000162729 00000 n -0000162864 00000 n -0000162999 00000 n -0000167078 00000 n -0000167317 00000 n -0000167452 00000 n -0000167587 00000 n -0000167722 00000 n -0000171667 00000 n -0000171898 00000 n -0000172033 00000 n -0000172168 00000 n -0000176112 00000 n -0000176343 00000 n -0000176478 00000 n -0000176613 00000 n -0000180573 00000 n -0000180812 00000 n -0000180947 00000 n -0000181082 00000 n -0000181217 00000 n -0000185470 00000 n -0000185725 00000 n -0000185860 00000 n -0000185995 00000 n -0000186128 00000 n -0000186261 00000 n -0000186394 00000 n -0000191061 00000 n -0000191580 00000 n -0000191713 00000 n -0000191846 00000 n -0000191979 00000 n -0000192112 00000 n -0000192245 00000 n -0000192379 00000 n -0000192513 00000 n -0000192647 00000 n -0000192781 00000 n -0000192915 00000 n -0000193049 00000 n -0000193183 00000 n -0000193317 00000 n -0000193451 00000 n -0000193585 00000 n -0000193719 00000 n -0000193853 00000 n -0000193987 00000 n -0000194121 00000 n -0000194255 00000 n -0000194389 00000 n -0000194523 00000 n -0000194657 00000 n -0000194791 00000 n -0000194925 00000 n -0000195059 00000 n -0000195193 00000 n -0000195327 00000 n -0000195461 00000 n -0000195595 00000 n -0000195729 00000 n -0000195863 00000 n -0000195997 00000 n -0000196131 00000 n -0000196265 00000 n -0000196399 00000 n -0000196532 00000 n -0000196664 00000 n -0000201814 00000 n -0000202213 00000 n -0000202347 00000 n -0000202481 00000 n -0000202615 00000 n -0000202749 00000 n -0000202883 00000 n -0000203017 00000 n -0000203151 00000 n -0000203285 00000 n -0000203419 00000 n -0000203553 00000 n -0000203687 00000 n -0000203821 00000 n -0000203955 00000 n -0000204089 00000 n -0000204223 00000 n -0000204357 00000 n -0000204491 00000 n -0000204625 00000 n -0000204759 00000 n -0000204894 00000 n -0000205029 00000 n -0000205162 00000 n -0000205295 00000 n -0000209925 00000 n -0000210436 00000 n -0000210569 00000 n -0000210702 00000 n -0000210835 00000 n -0000210968 00000 n -0000211101 00000 n -0000211234 00000 n -0000211368 00000 n -0000211502 00000 n -0000211636 00000 n -0000211770 00000 n -0000211904 00000 n -0000212038 00000 n -0000212172 00000 n -0000212306 00000 n -0000212440 00000 n -0000212574 00000 n -0000212708 00000 n -0000212842 00000 n -0000212976 00000 n -0000213110 00000 n -0000213244 00000 n -0000213378 00000 n -0000213512 00000 n -0000213646 00000 n -0000213780 00000 n -0000213914 00000 n -0000214048 00000 n -0000214182 00000 n -0000214316 00000 n -0000214450 00000 n -0000214584 00000 n -0000214718 00000 n -0000214852 00000 n -0000214986 00000 n -0000215120 00000 n -0000215253 00000 n -0000215385 00000 n -0000220167 00000 n -0000220558 00000 n -0000220692 00000 n -0000220826 00000 n -0000220960 00000 n -0000221094 00000 n -0000221228 00000 n -0000221362 00000 n -0000221496 00000 n -0000221630 00000 n -0000221764 00000 n -0000221898 00000 n -0000222032 00000 n -0000222166 00000 n -0000222300 00000 n -0000222434 00000 n -0000222568 00000 n -0000222702 00000 n -0000222836 00000 n -0000222970 00000 n -0000223104 00000 n -0000223238 00000 n -0000223372 00000 n -0000223507 00000 n -0000228216 00000 n -0000228447 00000 n -0000228582 00000 n -0000228717 00000 n -0000233361 00000 n -0000233564 00000 n -0000238118 00000 n -0000238341 00000 n -0000238476 00000 n -0000243155 00000 n -0000243358 00000 n -0000247953 00000 n -0000248176 00000 n -0000248311 00000 n -0000253009 00000 n -0000253212 00000 n -0000257722 00000 n -0000257925 00000 n -0000262760 00000 n -0000262983 00000 n -0000263118 00000 n -0000267531 00000 n -0000267734 00000 n -0000272610 00000 n -0000272833 00000 n -0000272968 00000 n -0000277431 00000 n -0000277634 00000 n -0000282560 00000 n -0000282783 00000 n -0000282918 00000 n -0000287344 00000 n -0000287547 00000 n -0000292458 00000 n -0000292681 00000 n -0000292816 00000 n -0000297278 00000 n -0000297481 00000 n -0000302360 00000 n -0000302583 00000 n -0000302718 00000 n -0000307275 00000 n -0000307478 00000 n -0000311999 00000 n -0000312230 00000 n -0000312365 00000 n -0000312499 00000 n -0000317203 00000 n -0000317406 00000 n -0000321991 00000 n -0000322194 00000 n -0000326696 00000 n -0000326935 00000 n -0000327070 00000 n -0000327205 00000 n -0000327340 00000 n -0000332035 00000 n -0000332238 00000 n -0000336833 00000 n -0000337056 00000 n -0000337191 00000 n -0000341864 00000 n -0000342067 00000 n -0000346591 00000 n -0000346794 00000 n -0000351599 00000 n -0000351822 00000 n -0000351957 00000 n -0000356458 00000 n -0000356661 00000 n -0000361519 00000 n -0000361742 00000 n -0000361878 00000 n -0000366337 00000 n -0000366540 00000 n -0000371391 00000 n -0000371614 00000 n -0000371750 00000 n -0000376243 00000 n -0000376446 00000 n -0000381316 00000 n -0000381539 00000 n -0000381675 00000 n -0000386152 00000 n -0000386355 00000 n -0000391267 00000 n -0000391490 00000 n -0000391626 00000 n -0000396081 00000 n -0000396284 00000 n -0000401201 00000 n -0000401424 00000 n -0000401560 00000 n -0000406030 00000 n -0000406233 00000 n -0000411071 00000 n -0000411294 00000 n -0000411430 00000 n -0000416043 00000 n -0000416246 00000 n -0000420874 00000 n -0000421097 00000 n -0000421233 00000 n -0000425940 00000 n -0000426143 00000 n -0000430578 00000 n -0000430801 00000 n -0000430937 00000 n -0000435610 00000 n -0000435813 00000 n -0000440486 00000 n -0000440709 00000 n -0000440845 00000 n -0000445531 00000 n -0000445734 00000 n -0000450229 00000 n -0000450432 00000 n -0000455269 00000 n -0000455492 00000 n -0000455628 00000 n -0000460030 00000 n -0000460233 00000 n -0000465140 00000 n -0000465363 00000 n -0000465499 00000 n -0000469962 00000 n -0000470165 00000 n -0000475043 00000 n -0000475266 00000 n -0000475402 00000 n -0000479873 00000 n -0000480076 00000 n -0000485029 00000 n -0000485252 00000 n -0000485388 00000 n -0000489849 00000 n -0000490052 00000 n -0000494952 00000 n -0000495175 00000 n -0000495311 00000 n -0000499924 00000 n -0000500127 00000 n -0000504733 00000 n -0000504956 00000 n -0000505092 00000 n -0000509787 00000 n -0000509990 00000 n -0000514554 00000 n -0000514777 00000 n -0000514913 00000 n -0000519586 00000 n -0000519789 00000 n -0000524467 00000 n -0000524690 00000 n -0000524825 00000 n -0000529495 00000 n -0000529698 00000 n -0000534172 00000 n -0000534375 00000 n -0000539254 00000 n -0000539485 00000 n -0000539621 00000 n -0000539757 00000 n -0000544403 00000 n -0000544606 00000 n -0000548146 00000 n -0000548349 00000 n -0000553088 00000 n -0000553311 00000 n -0000553447 00000 n -0000558117 00000 n -0000558340 00000 n -0000558476 00000 n -0000563207 00000 n -0000563430 00000 n -0000563566 00000 n -0000568236 00000 n -0000568459 00000 n -0000568595 00000 n -0000573022 00000 n -0000573245 00000 n -0000573381 00000 n -0000577861 00000 n -0000578064 00000 n -0000582670 00000 n -0000582893 00000 n -0000583029 00000 n -0000585864 00000 n -0000586067 00000 n -0000590542 00000 n -0000590773 00000 n -0000590909 00000 n -0000591045 00000 n -0000594348 00000 n -0000594551 00000 n -0000598988 00000 n -0000599211 00000 n -0000599347 00000 n -0000603995 00000 n -0000604198 00000 n -0000608477 00000 n -0000608700 00000 n -0000608836 00000 n -0000613550 00000 n -0000613753 00000 n -0000618781 00000 n -0000619004 00000 n -0000619140 00000 n -0000623475 00000 n -0000623678 00000 n -0000626959 00000 n -0000627162 00000 n -0000631154 00000 n -0000631377 00000 n -0000631513 00000 n -0000635731 00000 n -0000635954 00000 n -0000636090 00000 n -0000640224 00000 n -0000640455 00000 n -0000640591 00000 n -0000640727 00000 n -0000644966 00000 n -0000645205 00000 n -0000645341 00000 n -0000645477 00000 n -0000645612 00000 n -0000649726 00000 n -0000649957 00000 n -0000650093 00000 n -0000650229 00000 n -0000653792 00000 n -0000654015 00000 n -0000654151 00000 n -0000659100 00000 n -0000659331 00000 n -0000659467 00000 n -0000659603 00000 n -0000664429 00000 n -0000664660 00000 n -0000664796 00000 n -0000664932 00000 n -0000669366 00000 n -0000669597 00000 n -0000669733 00000 n -0000669869 00000 n -0000674743 00000 n -0000674974 00000 n -0000675110 00000 n -0000675246 00000 n -0000680133 00000 n -0000680364 00000 n -0000680500 00000 n -0000680636 00000 n -0000685548 00000 n -0000685779 00000 n -0000685915 00000 n -0000686050 00000 n -0000690659 00000 n -0000690890 00000 n -0000691026 00000 n -0000691162 00000 n -0000696029 00000 n -0000696252 00000 n -0000696388 00000 n -0000701266 00000 n -0000701497 00000 n -0000701633 00000 n -0000701769 00000 n -0000706695 00000 n -0000706926 00000 n -0000707062 00000 n -0000707198 00000 n -0000712140 00000 n -0000712371 00000 n -0000712507 00000 n -0000712641 00000 n -0000717637 00000 n -0000717840 00000 n -0000722780 00000 n -0000723011 00000 n -0000723147 00000 n -0000723283 00000 n -0000728199 00000 n -0000728430 00000 n -0000728566 00000 n -0000728702 00000 n -0000732382 00000 n -0000732585 00000 n -0000736668 00000 n -0000736871 00000 n -0000742410 00000 n -0000742809 00000 n -0000742945 00000 n -0000743079 00000 n -0000743213 00000 n -0000743347 00000 n -0000743481 00000 n -0000743615 00000 n -0000743749 00000 n -0000743883 00000 n -0000744017 00000 n -0000744152 00000 n -0000744287 00000 n -0000744422 00000 n -0000744557 00000 n -0000744692 00000 n -0000744827 00000 n -0000744962 00000 n -0000745097 00000 n -0000745232 00000 n -0000745367 00000 n -0000745502 00000 n -0000745637 00000 n -0000745772 00000 n -0000745906 00000 n -0000749634 00000 n -0000749921 00000 n -0000750056 00000 n -0000750191 00000 n -0000750326 00000 n -0000750461 00000 n -0000750596 00000 n -0000750731 00000 n -0000750866 00000 n -0000751001 00000 n -0000751137 00000 n -0000755806 00000 n -0000756037 00000 n -0000756173 00000 n -0000756309 00000 n -0000760802 00000 n -0000761033 00000 n -0000761169 00000 n -0000761305 00000 n -0000765773 00000 n -0000766004 00000 n -0000766140 00000 n -0000766276 00000 n -0000770336 00000 n -0000770559 00000 n -0000770695 00000 n -0000775432 00000 n -0000775695 00000 n -0000775831 00000 n -0000775967 00000 n -0000776101 00000 n -0000776235 00000 n -0000776368 00000 n -0000776500 00000 n -0000780731 00000 n -0000781066 00000 n -0000781200 00000 n -0000781334 00000 n -0000781468 00000 n -0000781602 00000 n -0000781737 00000 n -0000781872 00000 n -0000782007 00000 n -0000782142 00000 n -0000782277 00000 n -0000782412 00000 n -0000782547 00000 n -0000782682 00000 n -0000782817 00000 n -0000782952 00000 n -0000783088 00000 n -0000786510 00000 n -0000786713 00000 n -0000789978 00000 n -0000790181 00000 n -0000793251 00000 n -0000793454 00000 n -0000797857 00000 n -0000798060 00000 n -0000798256 00000 n -0000798486 00000 n -0000798612 00000 n -0000798758 00000 n -0000798898 00000 n -0000799095 00000 n -0000799329 00000 n -0000799560 00000 n -0000799816 00000 n -0000800055 00000 n -0000800302 00000 n -0000800532 00000 n -0000800774 00000 n -0000800999 00000 n -0000801243 00000 n -0000801471 00000 n -0000801706 00000 n -0000801924 00000 n -0000802155 00000 n -0000802369 00000 n -0000802604 00000 n -0000802822 00000 n -0000803066 00000 n -0000803293 00000 n -0000803525 00000 n -0000803769 00000 n -0000803971 00000 n -0000804147 00000 n -0000804339 00000 n -0000804544 00000 n -0000804750 00000 n -0000804957 00000 n -0000805211 00000 n -0000805441 00000 n -0000805664 00000 n -0000805875 00000 n -0000806086 00000 n -0000806298 00000 n -0000806514 00000 n -0000806728 00000 n -0000806978 00000 n -0000807193 00000 n -0000807412 00000 n -0000807630 00000 n -0000807846 00000 n -0000808058 00000 n -0000808263 00000 n -0000808470 00000 n -0000808675 00000 n -0000808876 00000 n -0000809103 00000 n -0000809333 00000 n -0000809562 00000 n -0000809779 00000 n -0000809996 00000 n -0000810222 00000 n -0000810458 00000 n -0000810702 00000 n -0000810918 00000 n -0000811131 00000 n -0000811359 00000 n -0000811573 00000 n -0000811782 00000 n -0000811965 00000 n -0000812179 00000 n -0000812383 00000 n -0000812608 00000 n -0000812841 00000 n -0000813054 00000 n -0000813276 00000 n -0000813473 00000 n -0000813647 00000 n -0000813837 00000 n -0000814034 00000 n -0000814226 00000 n -0000814437 00000 n -0000814645 00000 n -0000814849 00000 n -0000815084 00000 n -0000815297 00000 n -0000815506 00000 n -0000815698 00000 n -0000815895 00000 n -0000816078 00000 n -0000816250 00000 n -0000816433 00000 n -0000816625 00000 n -0000816822 00000 n -0000817043 00000 n -0000817261 00000 n -0000817495 00000 n -0000817711 00000 n -0000817956 00000 n -0000818184 00000 n -0000818424 00000 n -0000818657 00000 n -0000818907 00000 n -0000819127 00000 n -0000819300 00000 n -0000819493 00000 n -0000819716 00000 n -0000819931 00000 n -0000820136 00000 n -0000820364 00000 n -0000820581 00000 n -0000820800 00000 n -0000821004 00000 n -0000821252 00000 n -0000821496 00000 n -0000821712 00000 n -0000821932 00000 n -0000822138 00000 n -0000822328 00000 n -0000822525 00000 n -0000822700 00000 n -0000822896 00000 n -0000823075 00000 n -0000823286 00000 n -0000823488 00000 n -0000823674 00000 n -0000823859 00000 n -0000824094 00000 n -0000824322 00000 n -0000824554 00000 n -0000824772 00000 n -0000824965 00000 n -0000825178 00000 n -0000825387 00000 n -0000825585 00000 n -0000825774 00000 n -0000825964 00000 n -0000826158 00000 n -0000826341 00000 n -0000826543 00000 n -0000826710 00000 n -0000826903 00000 n -0000827096 00000 n -0000827333 00000 n -0000827501 00000 n -0000827704 00000 n -0000827935 00000 n -0000828140 00000 n -0000828317 00000 n -0000828381 00000 n -0000836324 00000 n -0000840962 00000 n -0000852820 00000 n -0000865030 00000 n -0000865264 00000 n -0000865690 00000 n -0000866516 00000 n -0000866669 00000 n -0000866900 00000 n -0000867468 00000 n -0000868925 00000 n -0000869075 00000 n -0000869310 00000 n -0000869849 00000 n -0000871086 00000 n -0000871239 00000 n -0000871482 00000 n -0000872077 00000 n -0000873702 00000 n -0000873859 00000 n -trailer -<< -/Size 1025 -/Root 3 0 R -/Info 2 0 R ->> -startxref -873951 -%%EOF diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/rke2-1.6-benchmark-2.6.md b/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/rke2-1.6-benchmark-2.6.md deleted file mode 100644 index f50043d7cbc..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-benchmark-2.6/rke2-1.6-benchmark-2.6.md +++ /dev/null @@ -1,3326 +0,0 @@ ---- -title: RKE2 CIS v1.6 Benchmark - Self-Assessment Guide - Rancher v2.6 -weight: 101 ---- - -### CIS v1.6 Kubernetes Benchmark - Rancher v2.6 RKE2 with Kubernetes v1.21 up to v1.23 - -[Click here to download a PDF version of this document](https://releases.rancher.com/documents/security/2.6/Rancher_RKE2_v2-6_CIS_v1-6_Benchmark_Assessment.pdf). - -#### Overview - -This document is a companion to the [Rancher v2.6 RKE2 security hardening guide]({{}}/rancher/v2.6/en/security/hardening-guides/rke2-1.6-hardening-2.6/). The hardening guide provides prescriptive guidance for hardening a production installation of Rancher with RKE2 provisioned clusters, and this benchmark guide is meant to help you evaluate the level of security of the hardened cluster against each control in the benchmark. - -This guide corresponds to specific versions of the hardening guide, Rancher, CIS Benchmark and Kubernetes: - -| Hardening Guide Version | Rancher Version | CIS Benchmark Version | Kubernetes Version | -| ----------------------- | --------------- | --------------------- | ------------------- | -| Hardening Guide CIS v1.6 Benchmark | Rancher v2.6.5+ | CIS v1.6 | Kubernetes v1.21 up to v1.23 | - -Because Rancher and RKE2 install Kubernetes services as containers, many of the control verification checks in the CIS Kubernetes Benchmark do not apply and will have a result of `Not Applicable`. This guide will walk through the various controls and provide updated example commands to audit compliance in Rancher created clusters. - -This document is to be used by Rancher operators, security teams, auditors and decision makers. - -For more detail about each audit, including rationales and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). - -#### Testing controls methodology - -RKE2 launches control plane components as static pods, managed by the kubelet, and uses containerd as the container runtime. Configuration is defined by arguments passed to the container at the time of initialization or via configuration file. - -Where control audits differ from the original CIS benchmark, the audit commands specific to Rancher are provided for testing. When performing the tests, you will need access to the command line on the hosts of all RKE2 nodes. The commands also make use of the [kubectl](https://kubernetes.io/docs/tasks/tools/) (with a valid configuration file) and [jq](https://stedolan.github.io/jq/) tools, which are required in the testing and evaluation of test results. - -> NOTE: Only `automated` tests (previously called `scored`) are covered in this guide. - -### Controls - ---- -## 1.1 Master Node Configuration Files -### 1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the -master node. -For example, chmod 644 /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml - -**Audit:** - -```bash -stat -c %a /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml; then stat -c %U:%G /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml; fi' -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml; then stat -c %a /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml; fi' -``` - -**Expected Result**: - -```console -'644' is equal to '644' -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml; then stat -c %U:%G /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml; fi' -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml; then stat -c %a /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml; fi' -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml; then stat -c %U:%G /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml; fi' -``` - -**Expected Result**: - -```console -'root:root' is present -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.7 Ensure that the etcd pod specification file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml; then stat -c %a /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml; fi' -``` - -**Expected Result**: - -```console -'644' is equal to '644' -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.8 Ensure that the etcd pod specification file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml; then stat -c %U:%G /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml; fi' -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.9 Ensure that the Container Network Interface file permissions are set to 644 or more restrictive (Manual) - - -**Result:** warn - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 - -**Audit:** - -```bash -stat -c %a -``` - -### 1.1.10 Ensure that the Container Network Interface file ownership is set to root:root (Manual) - - -**Result:** warn - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root - -**Audit:** - -```bash -stat -c %U:%G -``` - -### 1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -On the etcd server node, get the etcd data directory, passed as an argument --data-dir, -from the below command: -ps -ef | grep etcd -Run the below command (based on the etcd data directory found above). For example, -chmod 700 /var/lib/etcd - -**Audit:** - -```bash -stat -c %a /var/lib/rancher/rke2/server/db/etcd -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -700 -``` - -### 1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd (Automated) - - -**Result:** pass - -**Remediation:** -On the etcd server node, get the etcd data directory, passed as an argument --data-dir, -from the below command: -ps -ef | grep etcd -Run the below command (based on the etcd data directory found above). -For example, chown etcd:etcd /var/lib/etcd - -**Audit:** - -```bash -stat -c %U:%G /var/lib/rancher/rke2/server/db/etcd -``` - -**Expected Result**: - -```console -'etcd:etcd' is present -``` - -**Returned Value**: - -```console -etcd:etcd -``` - -### 1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 /etc/kubernetes/admin.conf - -**Audit:** - -```bash -stat -c %a /var/lib/rancher/rke2/server/cred/admin.kubeconfig -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.14 Ensure that the admin.conf file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root /etc/kubernetes/admin.conf - -**Audit:** - -```bash -stat -c %U:%G /var/lib/rancher/rke2/server/cred/admin.kubeconfig -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 scheduler - -**Audit:** - -```bash -stat -c %a /var/lib/rancher/rke2/server/cred/scheduler.kubeconfig -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.16 Ensure that the scheduler.conf file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root scheduler - -**Audit:** - -```bash -stat -c %U:%G /var/lib/rancher/rke2/server/cred/scheduler.kubeconfig -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod 644 controllermanager - -**Audit:** - -```bash -stat -c %a /var/lib/rancher/rke2/server/cred/controller.kubeconfig -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -644 -``` - -### 1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown root:root controllermanager - -**Audit:** - -```bash -stat -c %U:%G /var/lib/rancher/rke2/server/cred/controller.kubeconfig -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chown -R root:root /etc/kubernetes/pki/ - -**Audit:** - -```bash -stat -c %U:%G /var/lib/rancher/rke2/server/tls -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive (Manual) - - -**Result:** warn - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod -R 644 /var/lib/rancher/rke2/server/tls/*.crt - -**Audit Script:** `check_files_permissions.sh` - -```bash -#!/usr/bin/env bash - -# This script is used to ensure the file permissions are set to 644 or -# more restrictive for all files in a given directory or a wildcard -# selection of files -# -# inputs: -# $1 = /full/path/to/directory or /path/to/fileswithpattern -# ex: !(*key).pem -# -# $2 (optional) = permission (ex: 600) -# -# outputs: -# true/false - -# Turn on "extended glob" for use of '!' in wildcard -shopt -s extglob - -# Turn off history to avoid surprises when using '!' -set -H - -USER_INPUT=$1 - -if [[ "${USER_INPUT}" == "" ]]; then - echo "false" - exit -fi - - -if [[ -d ${USER_INPUT} ]]; then - PATTERN="${USER_INPUT}/*" -else - PATTERN="${USER_INPUT}" -fi - -PERMISSION="" -if [[ "$2" != "" ]]; then - PERMISSION=$2 -fi - -FILES_PERMISSIONS=$(stat -c %n\ %a ${PATTERN}) - -while read -r fileInfo; do - p=$(echo ${fileInfo} | cut -d' ' -f2) - - if [[ "${PERMISSION}" != "" ]]; then - if [[ "$p" != "${PERMISSION}" ]]; then - echo "false" - exit - fi - else - if [[ "$p" != "644" && "$p" != "640" && "$p" != "600" ]]; then - echo "false" - exit - fi - fi -done <<< "${FILES_PERMISSIONS}" - - -echo "true" -exit - -``` - -**Audit Execution:** - -```bash -./check_files_permissions.sh /var/lib/rancher/rke2/server/tls/*.crt -``` - -### 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the master node. -For example, -chmod -R 600 /etc/kubernetes/pki/*.key - -**Audit Script:** `check_files_permissions.sh` - -```bash -#!/usr/bin/env bash - -# This script is used to ensure the file permissions are set to 644 or -# more restrictive for all files in a given directory or a wildcard -# selection of files -# -# inputs: -# $1 = /full/path/to/directory or /path/to/fileswithpattern -# ex: !(*key).pem -# -# $2 (optional) = permission (ex: 600) -# -# outputs: -# true/false - -# Turn on "extended glob" for use of '!' in wildcard -shopt -s extglob - -# Turn off history to avoid surprises when using '!' -set -H - -USER_INPUT=$1 - -if [[ "${USER_INPUT}" == "" ]]; then - echo "false" - exit -fi - - -if [[ -d ${USER_INPUT} ]]; then - PATTERN="${USER_INPUT}/*" -else - PATTERN="${USER_INPUT}" -fi - -PERMISSION="" -if [[ "$2" != "" ]]; then - PERMISSION=$2 -fi - -FILES_PERMISSIONS=$(stat -c %n\ %a ${PATTERN}) - -while read -r fileInfo; do - p=$(echo ${fileInfo} | cut -d' ' -f2) - - if [[ "${PERMISSION}" != "" ]]; then - if [[ "$p" != "${PERMISSION}" ]]; then - echo "false" - exit - fi - else - if [[ "$p" != "644" && "$p" != "640" && "$p" != "600" ]]; then - echo "false" - exit - fi - fi -done <<< "${FILES_PERMISSIONS}" - - -echo "true" -exit - -``` - -**Audit Execution:** - -```bash -./check_files_permissions.sh /var/lib/rancher/rke2/server/tls/*.key -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -**Returned Value**: - -```console -true -``` - -## 1.2 API Server -### 1.2.1 Ensure that the --anonymous-auth argument is set to false (Manual) - - -**Result:** warn - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---anonymous-auth=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -### 1.2.2 Ensure that the --basic-auth-file argument is not set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and configure alternate mechanisms for authentication. Then, -edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and remove the `--basic-auth-file=` parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--basic-auth-file' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.3 Ensure that the --token-auth-file parameter is not set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and configure alternate mechanisms for authentication. Then, -edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and remove the `--token-auth-file=` parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--token-auth-file' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.4 Ensure that the --kubelet-https argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and remove the --kubelet-https parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--kubelet-https' is not present OR '--kubelet-https' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection between the -apiserver and kubelets. Then, edit API server pod specification file -/var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml on the master node and set the -kubelet client certificate and key parameters as below. ---kubelet-client-certificate= ---kubelet-client-key= - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--kubelet-client-certificate' is present AND '--kubelet-client-key' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and setup the TLS connection between -the apiserver and kubelets. Then, edit the API server pod specification file -/var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml on the master node and set the -`--kubelet-certificate-authority` parameter to the path to the cert file for the certificate authority. -`--kubelet-certificate-authority=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--kubelet-certificate-authority' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --authorization-mode parameter to values other than AlwaysAllow. -One such example could be as below. ---authorization-mode=RBAC - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'Node,RBAC' not have 'AlwaysAllow' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.8 Ensure that the --authorization-mode argument includes Node (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --authorization-mode parameter to a value that includes Node. ---authorization-mode=Node,RBAC - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'Node,RBAC' has 'Node' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.9 Ensure that the --authorization-mode argument includes RBAC (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --authorization-mode parameter to a value that includes RBAC, -for example: ---authorization-mode=Node,RBAC - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'Node,RBAC' has 'RBAC' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.10 Ensure that the admission control plugin EventRateLimit is set (Manual) - - -**Result:** warn - -**Remediation:** -Follow the Kubernetes documentation and set the desired limits in a configuration file. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -and set the below parameters. ---enable-admission-plugins=...,EventRateLimit,... ---admission-control-config-file= - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -### 1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and either remove the --enable-admission-plugins parameter, or set it to a -value that does not include AlwaysAdmit. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NodeRestriction,PodSecurityPolicy' not have 'AlwaysAdmit' OR '--enable-admission-plugins' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.12 Ensure that the admission control plugin AlwaysPullImages is set (Manual) - - -**Result:** warn - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to include -AlwaysPullImages. ---enable-admission-plugins=...,AlwaysPullImages,... - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -### 1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Manual) - - -**Result:** warn - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to include -SecurityContextDeny, unless PodSecurityPolicy is already in place. ---enable-admission-plugins=...,SecurityContextDeny,... - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -### 1.2.14 Ensure that the admission control plugin ServiceAccount is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and create ServiceAccount objects as per your environment. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and ensure that the --disable-admission-plugins parameter is set to a -value that does not include ServiceAccount. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--disable-admission-plugins' is not present OR '--disable-admission-plugins' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --disable-admission-plugins parameter to -ensure it does not include NamespaceLifecycle. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--disable-admission-plugins' is not present OR '--disable-admission-plugins' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and create Pod Security Policy objects as per your environment. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to a -value that includes PodSecurityPolicy: ---enable-admission-plugins=...,PodSecurityPolicy,... -Then restart the API Server. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NodeRestriction,PodSecurityPolicy' has 'PodSecurityPolicy' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.17 Ensure that the admission control plugin NodeRestriction is set (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --enable-admission-plugins parameter to a -value that includes NodeRestriction. ---enable-admission-plugins=...,NodeRestriction,... - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'NodeRestriction,PodSecurityPolicy' has 'NodeRestriction' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.18 Ensure that the --insecure-bind-address argument is not set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and remove the --insecure-bind-address parameter. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--insecure-bind-address' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.19 Ensure that the --insecure-port argument is set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---insecure-port=0 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'0' is equal to '0' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.20 Ensure that the --secure-port argument is not set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and either remove the --secure-port parameter or -set it to a different (non-zero) desired port. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -6443 is greater than 0 OR '--secure-port' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.21 Ensure that the --profiling argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---profiling=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.22 Ensure that the --audit-log-path argument is set (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --audit-log-path parameter to a suitable path and -file where you would like audit logs to be written, for example: ---audit-log-path=/var/log/apiserver/audit.log - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--audit-log-path' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.23 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --audit-log-maxage parameter to 30 or as an appropriate number of days: ---audit-log-maxage=30 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -30 is greater or equal to 30 -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.24 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --audit-log-maxbackup parameter to 10 or to an appropriate -value. ---audit-log-maxbackup=10 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -10 is greater or equal to 10 -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.25 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --audit-log-maxsize parameter to an appropriate size in MB. -For example, to set it as 100 MB: ---audit-log-maxsize=100 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -100 is greater or equal to 100 -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.26 Ensure that the --request-timeout argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -and set the below parameter as appropriate and if needed. -For example, ---request-timeout=300s - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--request-timeout' is not present OR '--request-timeout' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.27 Ensure that the --service-account-lookup argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---service-account-lookup=true -Alternatively, you can delete the --service-account-lookup parameter from this file so -that the default takes effect. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--service-account-lookup' is not present OR '--service-account-lookup' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.28 Ensure that the --service-account-key-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --service-account-key-file parameter -to the public key file for service accounts: -`--service-account-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--service-account-key-file' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the etcd certificate and key file parameters. -`--etcd-certfile=` -`--etcd-keyfile=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--etcd-certfile' is present AND '--etcd-keyfile' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection on the apiserver. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the TLS certificate and private key file parameters. -`--tls-cert-file=` -`--tls-private-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--tls-cert-file' is present AND '--tls-private-key-file' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.31 Ensure that the --client-ca-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection on the apiserver. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the client certificate authority file. -`--client-ca-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--client-ca-file' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.32 Ensure that the --etcd-cafile argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the etcd certificate authority file parameter. -`--etcd-cafile=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--etcd-cafile' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.33 Ensure that the --encryption-provider-config argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and configure a EncryptionConfig file. -Then, edit the API server pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml -on the master node and set the --encryption-provider-config parameter to the path of that file: --encryption-provider-config= - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--encryption-provider-config' is present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.2.34 Ensure that encryption providers are appropriately configured (Automated) - - -**Result:** pass - -**Remediation:** -Follow the Kubernetes documentation and configure a EncryptionConfig file. -In this file, choose aescbc, kms or secretbox as the encryption provider. - -**Audit:** - -```bash -/bin/sh -c 'if grep aescbc /var/lib/rancher/rke2/server/cred/encryption-config.json; then echo 0; fi' -``` - -**Expected Result**: - -```console -'0' is present -``` - -**Returned Value**: - -```console -{"kind":"EncryptionConfiguration","apiVersion":"apiserver.config.k8s.io/v1","resources":[{"resources":["secrets"],"providers":[{"aescbc":{"keys":[{"name":"aescbckey","secret":"ZP3yNnlCjzcKMBXfmNBmpGbiY+oXne+WP6EM42lZIbE="}]}},{"identity":{}}]}]} 0 -``` - -### 1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual) - - -**Result:** pass - -**Remediation:** -Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml -on the master node and set the below parameter. ---tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM -_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM -_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM -_SHA384 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep -``` - -**Expected Result**: - -```console -'--tls-cipher-suites' is not present -``` - -**Returned Value**: - -```console -root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -## 1.3 Controller Manager -### 1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node and set the --terminated-pod-gc-threshold to an appropriate threshold, -for example: ---terminated-pod-gc-threshold=10 - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'--terminated-pod-gc-threshold' is present -``` - -**Returned Value**: - -```console -root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.3.2 Ensure that the --profiling argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node and set the below parameter. ---profiling=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.3.3 Ensure that the --use-service-account-credentials argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node to set the below parameter. ---use-service-account-credentials=true - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'true' is not equal to 'false' -``` - -**Returned Value**: - -```console -root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node and set the --service-account-private-key-file parameter -to the private key file for service accounts. -`--service-account-private-key-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'--service-account-private-key-file' is present -``` - -**Returned Value**: - -```console -root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.3.5 Ensure that the --root-ca-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node and set the --root-ca-file parameter to the certificate bundle file`. -`--root-ca-file=` - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'--root-ca-file' is present -``` - -**Returned Value**: - -```console -root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -### 1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true. ---feature-gates=RotateKubeletServerCertificate=true - -### 1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Controller Manager pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml -on the master node and ensure the correct value for the --bind-address parameter - -**Audit:** - -```bash -/bin/ps -ef | grep kube-controller-manager | grep -v grep -``` - -**Expected Result**: - -```console -'127.0.0.1' is equal to '127.0.0.1' OR '--bind-address' is not present -``` - -**Returned Value**: - -```console -root 5522 5416 3 14:58 ? 00:00:16 kube-controller-manager --flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins --terminated-pod-gc-threshold=1000 --permit-port-sharing=true --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/rke2/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/rke2/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/rke2/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/rke2/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/rke2/server/tls/service.key --use-service-account-credentials=true -``` - -## 1.4 Scheduler -### 1.4.1 Ensure that the --profiling argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Scheduler pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml file -on the master node and set the below parameter. ---profiling=false - -**Audit:** - -```bash -/bin/ps -ef | grep kube-scheduler | grep -v grep -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -root 5533 5414 0 14:58 ? 00:00:02 kube-scheduler --permit-port-sharing=true --address=127.0.0.1 --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-scheduler --kubeconfig=/var/lib/rancher/rke2/server/cred/scheduler.kubeconfig --port=10251 --profiling=false --secure-port=10259 -``` - -### 1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1 (Automated) - - -**Result:** pass - -**Remediation:** -Edit the Scheduler pod specification file /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml -on the master node and ensure the correct value for the --bind-address parameter - -**Audit:** - -```bash -/bin/ps -ef | grep kube-scheduler | grep -v grep -``` - -**Expected Result**: - -```console -'127.0.0.1' is equal to '127.0.0.1' OR '--bind-address' is not present -``` - -**Returned Value**: - -```console -root 5533 5414 0 14:58 ? 00:00:02 kube-scheduler --permit-port-sharing=true --address=127.0.0.1 --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/rke2/server/tls/kube-scheduler --kubeconfig=/var/lib/rancher/rke2/server/cred/scheduler.kubeconfig --port=10251 --profiling=false --secure-port=10259 -``` - -## 2 Etcd Node Configuration Files -### 2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Follow the etcd service documentation and configure TLS encryption. -Then, edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml -on the master node and set the below parameters. -`--cert-file=` -`--key-file=` - -### 2.2 Ensure that the --client-cert-auth argument is set to true (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Edit the etcd pod specification file /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml on the master -node and set the below parameter. ---client-cert-auth="true" - -### 2.3 Ensure that the --auto-tls argument is not set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the etcd pod specification file /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml on the master -node and either remove the --auto-tls parameter or set it to false. - --auto-tls=false - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--auto-tls' is not present OR '--auto-tls' is not present -``` - -**Returned Value**: - -```console -etcd 5059 5033 0 14:58 ? 00:00:00 /pause etcd 5121 5033 3 14:58 ? 00:00:18 etcd --config-file=/var/lib/rancher/rke2/server/db/etcd/config root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 16473 16413 0 15:07 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke2-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Follow the etcd service documentation and configure peer TLS encryption as appropriate -for your etcd cluster. -Then, edit the etcd pod specification file /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml on the -master node and set the below parameters. -`--peer-client-file=` -`--peer-key-file=` - -### 2.5 Ensure that the --peer-client-cert-auth argument is set to true (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Edit the etcd pod specification file /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml on the master -node and set the below parameter. ---peer-client-cert-auth=true - -### 2.6 Ensure that the --peer-auto-tls argument is not set to true (Automated) - - -**Result:** pass - -**Remediation:** -Edit the etcd pod specification file /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml on the master -node and either remove the --peer-auto-tls parameter or set it to false. ---peer-auto-tls=false - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--peer-auto-tls' is not present OR '--peer-auto-tls' is not present -``` - -**Returned Value**: - -```console -etcd 5059 5033 0 14:58 ? 00:00:00 /pause etcd 5121 5033 3 14:58 ? 00:00:18 etcd --config-file=/var/lib/rancher/rke2/server/db/etcd/config root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 16473 16413 6 15:07 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke2-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -### 2.7 Ensure that a unique Certificate Authority is used for etcd (Manual) - - -**Result:** pass - -**Remediation:** -[Manual test] -Follow the etcd documentation and create a dedicated certificate authority setup for the -etcd service. -Then, edit the etcd pod specification file /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml on the -master node and set the below parameter. -`--trusted-ca-file=` - -**Audit:** - -```bash -/bin/ps -ef | /bin/grep etcd | /bin/grep -v grep -``` - -**Expected Result**: - -```console -'--trusted-ca-file' is not present -``` - -**Returned Value**: - -```console -etcd 5059 5033 0 14:58 ? 00:00:00 /pause etcd 5121 5033 3 14:58 ? 00:00:18 etcd --config-file=/var/lib/rancher/rke2/server/db/etcd/config root 5275 5222 15 14:58 ? 00:01:26 kube-apiserver --audit-policy-file=/etc/rancher/rke2/audit-policy.yaml --audit-log-path=/var/lib/rancher/rke2/server/logs/audit.log --audit-log-maxage=30 --audit-log-maxbackup=10 --audit-log-maxsize=100 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,rke2 --authorization-mode=Node,RBAC --bind-address=0.0.0.0 --cert-dir=/var/lib/rancher/rke2/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/rke2/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction,PodSecurityPolicy --encryption-provider-config=/var/lib/rancher/rke2/server/cred/encryption-config.json --etcd-cafile=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --etcd-certfile=/var/lib/rancher/rke2/server/tls/etcd/client.crt --etcd-keyfile=/var/lib/rancher/rke2/server/tls/etcd/client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/rke2/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/rke2/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/rke2/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/rke2/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/rke2/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/rke2/server/tls/serving-kube-apiserver.key root 16473 16413 3 15:07 ? 00:00:00 kube-bench run --targets etcd --scored --nosummary --noremediations --v=5 --config-dir=/etc/kube-bench/cfg --benchmark rke2-cis-1.6-hardened --json --log_dir /tmp/results/logs --outputfile /tmp/results/etcd.json -``` - -## 3.1 Authentication and Authorization -### 3.1.1 Client certificate authentication should not be used for users (Manual) - - -**Result:** warn - -**Remediation:** -Alternative mechanisms provided by Kubernetes such as the use of OIDC should be -implemented in place of client certificates. - -## 3.2 Logging -### 3.2.1 Ensure that a minimal audit policy is created (Automated) - - -**Result:** pass - -**Remediation:** -Create an audit policy file for your cluster. - -**Audit:** - -```bash -/bin/ps -ef | grep kube-apiserver | grep -v grep | grep -o audit-policy-file -``` - -**Expected Result**: - -```console -'audit-policy-file' is equal to 'audit-policy-file' -``` - -**Returned Value**: - -```console -audit-policy-file -``` - -### 3.2.2 Ensure that the audit policy covers key security concerns (Manual) - - -**Result:** warn - -**Remediation:** -Consider modification of the audit policy in use on the cluster to include these items, at a -minimum. - -## 4.1 Worker Node Configuration Files -### 4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chmod 644 /etc/systemd/system/kubelet.service.d/10-kubeadm.conf - -**Audit:** - -```bash -/bin/sh -c 'if test -e /etc/systemd/system/kubelet.service.d/10-kubeadm.conf; then stat -c permissions=%a /etc/systemd/system/kubelet.service.d/10-kubeadm.conf; fi' -``` - -**Expected Result**: - -```console -'permissions' is not present -``` - -### 4.1.2 Ensure that the kubelet service file ownership is set to root:root (Automated) - - -**Result:** Not Applicable - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chown root:root /etc/systemd/system/kubelet.service.d/10-kubeadm.conf - -### 4.1.3 If proxy kubeconfig file exists ensure permissions are set to 644 or more restrictive (Manual) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chmod 644 /var/lib/rancher/rke2/agent/kubeproxy.kubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /node/var/lib/rancher/rke2/agent/kubeproxy.kubeconfig; then stat -c %a /node/var/lib/rancher/rke2/agent/kubeproxy.kubeconfig; fi' -``` - -**Expected Result**: - -```console -'permissions' is present OR '/var/lib/rancher/rke2/agent/kubeproxy.kubeconfig' is not present -``` - -**Returned Value**: - -```console -644 -``` - -### 4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root (Manual) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, chown root:root /var/lib/rancher/rke2/agent/kubeproxy.kubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/kubeproxy.kubeconfig; then stat -c %U:%G /var/lib/rancher/rke2/agent/kubeproxy.kubeconfig; fi' -``` - -**Expected Result**: - -```console -'root:root' is not present OR '/var/lib/rancher/rke2/agent/kubeproxy.kubeconfig' is not present -``` - -**Returned Value**: - -```console -root:root -``` - -### 4.1.5 Ensure that the --kubeconfig kubelet.conf file permissions are set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chmod 644 /var/lib/rancher/rke2/agent/kubelet.kubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/kubelet.kubeconfig; then stat -c permissions=%a /var/lib/rancher/rke2/agent/kubelet.kubeconfig; fi' -``` - -**Expected Result**: - -```console -'644' is equal to '644' -``` - -**Returned Value**: - -```console -permissions=644 -``` - -### 4.1.6 Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the below command (based on the file location on your system) on the each worker node. -For example, -chown root:root /var/lib/rancher/rke2/agent/kubelet.kubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/kubelet.kubeconfig; then stat -c %U:%G /var/lib/rancher/rke2/agent/kubelet.kubeconfig; fi' -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual) - - -**Result:** warn - -**Remediation:** -Run the following command to modify the file permissions of the -`--client-ca-file chmod 644 ` - -**Audit:** - -```bash -stat -c %a /var/lib/rancher/rke2/server/tls/server-ca.crt -``` - -### 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the following command to modify the ownership of the --client-ca-file. -`chown root:roset: trueot ` - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/client-ca.crt; then stat -c %U:%G /var/lib/rancher/rke2/agent/client-ca.crt; fi' -``` - -**Expected Result**: - -```console -'root:root' is equal to 'root:root' -``` - -**Returned Value**: - -```console -root:root -``` - -### 4.1.9 Ensure that the kubelet --config configuration file has permissions set to 644 or more restrictive (Automated) - - -**Result:** pass - -**Remediation:** -Run the following command (using the config file location identified in the Audit step) -chmod 644 /var/lib/rancher/rke2/agent/kubelet.kubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/kubelet.kubeconfig; then stat -c permissions=%a /var/lib/rancher/rke2/agent/kubelet.kubeconfig; fi' -``` - -**Expected Result**: - -```console -'644' is equal to '644' -``` - -**Returned Value**: - -```console -permissions=644 -``` - -### 4.1.10 Ensure that the kubelet --config configuration file ownership is set to root:root (Automated) - - -**Result:** pass - -**Remediation:** -Run the following command (using the config file location identified in the Audit step) -chown root:root /var/lib/rancher/rke2/agent/kubelet.kubeconfig - -**Audit:** - -```bash -/bin/sh -c 'if test -e /var/lib/rancher/rke2/agent/kubelet.kubeconfig; then stat -c %U:%G /var/lib/rancher/rke2/agent/kubelet.kubeconfig; fi' -``` - -**Expected Result**: - -```console -'root:root' is present -``` - -**Returned Value**: - -```console -root:root -``` - -## 4.2 Kubelet -### 4.2.1 Ensure that the anonymous-auth argument is set to false (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set authentication: anonymous: enabled to -false. -If using executable arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---anonymous-auth=false -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'false' is equal to 'false' -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set authorization: mode to Webhook. If -using executable arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_AUTHZ_ARGS variable. ---authorization-mode=Webhook -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'' is not present -``` - -**Returned Value**: - -```console -apiVersion: v1 clusters: - cluster: server: https://127.0.0.1:6443 certificate-authority: /var/lib/rancher/rke2/agent/server-ca.crt name: local contexts: - context: cluster: local namespace: default user: user name: Default current-context: Default kind: Config preferences: {} users: - name: user user: client-certificate: /var/lib/rancher/rke2/agent/client-kubelet.crt client-key: /var/lib/rancher/rke2/agent/client-kubelet.key -``` - -### 4.2.3 Ensure that the --client-ca-file argument is set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set authentication: x509: clientCAFile to -the location of the client CA file. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_AUTHZ_ARGS variable. -`--client-ca-file=` -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'' is not present -``` - -**Returned Value**: - -```console -apiVersion: v1 clusters: - cluster: server: https://127.0.0.1:6443 certificate-authority: /var/lib/rancher/rke2/agent/server-ca.crt name: local contexts: - context: cluster: local namespace: default user: user name: Default current-context: Default kind: Config preferences: {} users: - name: user user: client-certificate: /var/lib/rancher/rke2/agent/client-kubelet.crt client-key: /var/lib/rancher/rke2/agent/client-kubelet.key -``` - -### 4.2.4 Ensure that the --read-only-port argument is set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set readOnlyPort to 0. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---read-only-port=0 -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'0' is equal to '0' AND '--read-only-port' is present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set streamingConnectionIdleTimeout to a -value other than 0. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---streaming-connection-idle-timeout=5m -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'--streaming-connection-idle-timeout' is not present OR '--streaming-connection-idle-timeout' is present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.6 Ensure that the --protect-kernel-defaults argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set protectKernelDefaults: true. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. ---protect-kernel-defaults=true -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'' is not present -``` - -**Returned Value**: - -```console -apiVersion: v1 clusters: - cluster: server: https://127.0.0.1:6443 certificate-authority: /var/lib/rancher/rke2/agent/server-ca.crt name: local contexts: - context: cluster: local namespace: default user: user name: Default current-context: Default kind: Config preferences: {} users: - name: user user: client-certificate: /var/lib/rancher/rke2/agent/client-kubelet.crt client-key: /var/lib/rancher/rke2/agent/client-kubelet.key -``` - -### 4.2.7 Ensure that the --make-iptables-util-chains argument is set to true (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set makeIPTablesUtilChains: true. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -remove the --make-iptables-util-chains argument from the -KUBELET_SYSTEM_PODS_ARGS variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'--make-iptables-util-chains' is not present OR '--make-iptables-util-chains' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.8 Ensure that the --hostname-override argument is not set (Manual) - - -**Result:** warn - -**Remediation:** -Edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf -on each worker node and remove the --hostname-override argument from the -KUBELET_SYSTEM_PODS_ARGS variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -### 4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture (Manual) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set eventRecordQPS: to an appropriate level. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'--event-qps' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set tlsCertFile to the location -of the certificate file to use to identify this Kubelet, and tlsPrivateKeyFile -to the location of the corresponding private key file. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the below parameters in KUBELET_CERTIFICATE_ARGS variable. -`--tls-cert-file=` -`--tls-private-key-file=` -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'--tls-cert-file' is present AND '--tls-private-key-file' is present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.11 Ensure that the --rotate-certificates argument is not set to false (Manual) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to add the line rotateCertificates: true or -remove it altogether to use the default value. -If using command line arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS -variable. -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'--rotate-certificates' is not present OR '--rotate-certificates' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.12 Verify that the RotateKubeletServerCertificate argument is set to true (Manual) - - -**Result:** pass - -**Remediation:** -Edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf -on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable. ---feature-gates=RotateKubeletServerCertificate=true -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'RotateKubeletServerCertificate' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -### 4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual) - - -**Result:** pass - -**Remediation:** -If using a Kubelet config file, edit the file to set TLSCipherSuites: to -TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 -or to a subset of these values. -If using executable arguments, edit the kubelet service file -/etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and -set the --tls-cipher-suites parameter as follows, or to a subset of these values. ---tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 -Based on your system, restart the kubelet service. For example: -systemctl daemon-reload -systemctl restart kubelet.service - -**Audit:** - -```bash -/bin/ps -fC kubelet -``` - -**Audit Config:** - -```bash -/bin/cat /var/lib/rancher/rke2/agent/kubelet.kubeconfig -``` - -**Expected Result**: - -```console -'--tls-cipher-suites' is not present -``` - -**Returned Value**: - -```console -UID PID PPID C STIME TTY TIME CMD root 4785 4751 3 14:58 ? 00:00:21 kubelet --volume-plugin-dir=/var/lib/kubelet/volumeplugins --file-check-frequency=5s --sync-frequency=30s --address=0.0.0.0 --alsologtostderr=false --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/rke2/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override= --kubeconfig=/var/lib/rancher/rke2/agent/kubelet.kubeconfig --log-file-max-size=50 --log-file=/var/lib/rancher/rke2/agent/logs/kubelet.log --logtostderr=false --node-labels=cattle.io/os=linux,rke.cattle.io/machine=7c32844c-359f-45f7-88c5-a7173d27690a --pod-manifest-path=/var/lib/rancher/rke2/agent/pod-manifests --protect-kernel-defaults=true --read-only-port=0 --resolv-conf=/run/systemd/resolve/resolv.conf --serialize-image-pulls=false --stderrthreshold=FATAL --tls-cert-file=/var/lib/rancher/rke2/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/rke2/agent/serving-kubelet.key -``` - -## 5.1 RBAC and Service Accounts -### 5.1.1 Ensure that the cluster-admin role is only used where required (Manual) - - -**Result:** warn - -**Remediation:** -Identify all clusterrolebindings to the cluster-admin role. Check if they are used and -if they need this role or if they could use a role with fewer privileges. -Where possible, first bind users to a lower privileged role and then remove the -clusterrolebinding to the cluster-admin role : -kubectl delete clusterrolebinding [name] - -### 5.1.2 Minimize access to secrets (Manual) - - -**Result:** warn - -**Remediation:** -Where possible, remove get, list and watch access to secret objects in the cluster. - -### 5.1.3 Minimize wildcard use in Roles and ClusterRoles (Manual) - - -**Result:** warn - -**Remediation:** -Where possible replace any use of wildcards in clusterroles and roles with specific -objects or actions. - -### 5.1.4 Minimize access to create pods (Manual) - - -**Result:** warn - -**Remediation:** -Where possible, remove create access to pod objects in the cluster. - -### 5.1.5 Ensure that default service accounts are not actively used. (Automated) - - -**Result:** pass - -**Remediation:** -Create explicit service accounts wherever a Kubernetes workload requires specific access -to the Kubernetes API server. -Modify the configuration of each default service account to include this value -automountServiceAccountToken: false - -**Audit Script:** `check_for_default_sa.sh` - -```bash -#!/bin/bash - -set -eE - -handle_error() { - echo "false" -} - -trap 'handle_error' ERR - -count_sa=$(kubectl get serviceaccounts --all-namespaces -o json | jq -r '.items[] | select(.metadata.name=="default") | select((.automountServiceAccountToken == null) or (.automountServiceAccountToken == true))' | jq .metadata.namespace | wc -l) -if [[ ${count_sa} -gt 0 ]]; then - echo "false" - exit -fi - -for ns in $(kubectl get ns --no-headers -o custom-columns=":metadata.name") -do - for result in $(kubectl get clusterrolebinding,rolebinding -n $ns -o json | jq -r '.items[] | select((.subjects[].kind=="ServiceAccount" and .subjects[].name=="default") or (.subjects[].kind=="Group" and .subjects[].name=="system:serviceaccounts"))' | jq -r '"\(.roleRef.kind),\(.roleRef.name)"') - do - read kind name <<<$(IFS=","; echo $result) - resource_count=$(kubectl get $kind $name -n $ns -o json | jq -r '.rules[] | select(.resources[] != "podsecuritypolicies")' | wc -l) - if [[ ${resource_count} -gt 0 ]]; then - echo "false" - exit - fi - done -done - - -echo "true" -``` - -**Audit Execution:** - -```bash -./check_for_default_sa.sh -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -### 5.1.6 Ensure that Service Account Tokens are only mounted where necessary (Manual) - - -**Result:** warn - -**Remediation:** -Modify the definition of pods and service accounts which do not need to mount service -account tokens to disable it. - -## 5.2 Pod Security Policies -### 5.2.1 Minimize the admission of privileged containers (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that -the .spec.privileged field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp global-restricted-psp -o json | jq -r '.spec.runAsUser.rule' -``` - -**Expected Result**: - -```console -'MustRunAsNonRoot' is equal to 'MustRunAsNonRoot' -``` - -**Returned Value**: - -```console -MustRunAsNonRoot -``` - -### 5.2.2 Minimize the admission of containers wishing to share the host process ID namespace (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.hostPID field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.hostPID == null) or (.spec.hostPID == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.3 Minimize the admission of containers wishing to share the host IPC namespace (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.hostIPC field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.hostIPC == null) or (.spec.hostIPC == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.4 Minimize the admission of containers wishing to share the host network namespace (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.hostNetwork field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.hostNetwork == null) or (.spec.hostNetwork == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.5 Minimize the admission of containers with allowPrivilegeEscalation (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.allowPrivilegeEscalation field is omitted or set to false. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.allowPrivilegeEscalation == null) or (.spec.allowPrivilegeEscalation == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.6 Minimize the admission of root containers (Automated) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.runAsUser.rule is set to either MustRunAsNonRoot or MustRunAs with the range of -UIDs not including 0. - -**Audit:** - -```bash -kubectl get psp -o json | jq .items[] | jq -r 'select((.spec.allowPrivilegeEscalation == null) or (.spec.allowPrivilegeEscalation == false))' | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.2.7 Minimize the admission of containers with the NET_RAW capability (Manual) - - -**Result:** pass - -**Remediation:** -Create a PSP as described in the Kubernetes documentation, ensuring that the -.spec.requiredDropCapabilities is set to include either NET_RAW or ALL. - -**Audit:** - -```bash -kubectl get psp global-restricted-psp -o json | jq -r .spec.requiredDropCapabilities[] -``` - -**Expected Result**: - -```console -'ALL' is equal to 'ALL' -``` - -**Returned Value**: - -```console -ALL -``` - -### 5.2.8 Minimize the admission of containers with added capabilities (Manual) - - -**Result:** warn - -**Remediation:** -Ensure that allowedCapabilities is not present in PSPs for the cluster unless -it is set to an empty array. - -### 5.2.9 Minimize the admission of containers with capabilities assigned (Manual) - - -**Result:** warn - -**Remediation:** -Review the use of capabilites in applications runnning on your cluster. Where a namespace -contains applicaions which do not require any Linux capabities to operate consider adding -a PSP which forbids the admission of containers which do not drop all capabilities. - -## 5.3 Network Policies and CNI -### 5.3.1 Ensure that the CNI in use supports Network Policies (Automated) - - -**Result:** pass - -**Remediation:** -If the CNI plugin in use does not support network policies, consideration should be given to -making use of a different plugin, or finding an alternate mechanism for restricting traffic -in the Kubernetes cluster. - -**Audit:** - -```bash -kubectl get pods -n kube-system -l k8s-app=canal -o json | jq .items[] | jq .metadata.name | wc -l | xargs -I {} echo '--count={}' -``` - -**Expected Result**: - -```console -1 is greater than 0 -``` - -**Returned Value**: - -```console ---count=1 -``` - -### 5.3.2 Ensure that all Namespaces have Network Policies defined (Automated) - - -**Result:** pass - -**Remediation:** -Follow the documentation and create NetworkPolicy objects as you need them. - -**Audit Script:** `check_for_rke2_network_policies.sh` - -```bash -#!/bin/bash - -set -eE - -handle_error() { - echo "false" -} - -trap 'handle_error' ERR - -for namespace in kube-system kube-public default; do - policy_count=$(/var/lib/rancher/rke2/bin/kubectl get networkpolicy -n ${namespace} -o json | jq -r '.items | length') - if [ ${policy_count} -eq 0 ]; then - echo "false" - exit - fi -done - -echo "true" - -``` - -**Audit Execution:** - -```bash -./check_for_rke2_network_policies.sh -``` - -**Expected Result**: - -```console -'true' is equal to 'true' -``` - -**Returned Value**: - -```console -true -``` - -## 5.4 Secrets Management -### 5.4.1 Prefer using secrets as files over secrets as environment variables (Manual) - - -**Result:** warn - -**Remediation:** -if possible, rewrite application code to read secrets from mounted secret files, rather than -from environment variables. - -### 5.4.2 Consider external secret storage (Manual) - - -**Result:** warn - -**Remediation:** -Refer to the secrets management options offered by your cloud provider or a third-party -secrets management solution. - -## 5.5 Extensible Admission Control -### 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller (Manual) - - -**Result:** warn - -**Remediation:** -Follow the Kubernetes documentation and setup image provenance. - -## 5.6 The v1.5.1 guide skips 5.6 and goes from 5.5 to 5.7. We are including it here merely for explanation. -## 5.7 General Policies -### 5.7.1 Create administrative boundaries between resources using namespaces (Manual) - - -**Result:** warn - -**Remediation:** -Follow the documentation and create namespaces for objects in your deployment as you need -them. - -### 5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions (Manual) - - -**Result:** warn - -**Remediation:** -Seccomp is an alpha feature currently. By default, all alpha features are disabled. So, you -would need to enable alpha features in the apiserver by passing "--feature- -gates=AllAlpha=true" argument. -Edit the /etc/kubernetes/apiserver file on the master node and set the KUBE_API_ARGS -parameter to "--feature-gates=AllAlpha=true" -KUBE_API_ARGS="--feature-gates=AllAlpha=true" -Based on your system, restart the kube-apiserver service. For example: -systemctl restart kube-apiserver.service -Use annotations to enable the docker/default seccomp profile in your pod definitions. An -example is as below: -apiVersion: v1 -kind: Pod -metadata: - name: trustworthy-pod - annotations: - seccomp.security.alpha.kubernetes.io/pod: docker/default -spec: - containers: - - name: trustworthy-container - image: sotrustworthy:latest - -### 5.7.3 Apply Security Context to Your Pods and Containers (Automated) - - -**Result:** warn - -**Remediation:** -Follow the Kubernetes documentation and apply security contexts to your pods. For a -suggested list of security contexts, you may refer to the CIS Security Benchmark for Docker -Containers. - -### 5.7.4 The default namespace should not be used (Manual) - - -**Result:** warn - -**Remediation:** -Ensure that namespaces are created to allow for appropriate segregation of Kubernetes -resources and that all new resources are created in a specific namespace. - diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf b/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf deleted file mode 100644 index 35251edd3d0..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/Rancher_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf +++ /dev/null @@ -1,4149 +0,0 @@ -%PDF-1.7 -%🖤 -1 0 obj -<< -/Type /Pages -/Kids [ 6 0 R 8 0 R 26 0 R 39 0 R 41 0 R 49 0 R 56 0 R 59 0 R 72 0 R 81 0 R 85 0 R 125 0 R 165 0 R 205 0 R 245 0 R ] -/Count 15 ->> -endobj -2 0 obj -<< -/Title (RKE2 Hardening Guide with CIS v1.6 Benchmark) -/Creator (pandoc) -/Producer (WeasyPrint 54.3) ->> -endobj -3 0 obj -<< -/Type /Catalog -/Pages 1 0 R -/Outlines 277 0 R -/Names << -/Dests << -/Names [ (TOC) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (api-server-audit-configuration) [ 59 0 R /XYZ 84.259843 315.158799 0 ] (cb1) [ 41 0 R /XYZ 84.259843 617.450787 0 ] (cb1-1) [ 41 0 R /XYZ 101.433071 615.753766 0 ] (cb1-2) [ 41 0 R /XYZ 99.933071 596.806744 0 ] (cb1-3) [ 41 0 R /XYZ 99.933071 577.859723 0 ] (cb1-4) [ 41 0 R /XYZ 99.933071 558.912701 0 ] (cb1-5) [ 41 0 R /XYZ 99.933071 539.965680 0 ] (cb1-6) [ 41 0 R /XYZ 99.933071 521.018658 0 ] (cb2) [ 49 0 R /XYZ 84.259843 687.872079 0 ] (cb2-1) [ 49 0 R /XYZ 101.433071 686.175057 0 ] (cb2-2) [ 49 0 R /XYZ 99.933071 667.228036 0 ] (cb2-3) [ 49 0 R /XYZ 99.933071 648.281014 0 ] (cb2-4) [ 49 0 R /XYZ 99.933071 629.333993 0 ] (cb3) [ 49 0 R /XYZ 84.259843 389.087993 0 ] (cb3-1) [ 49 0 R /XYZ 101.433071 387.390971 0 ] (cb4) [ 56 0 R /XYZ 84.259843 110.200913 0 ] (cb4-1) [ 56 0 R /XYZ 101.433071 108.503892 0 ] (cb5) [ 59 0 R /XYZ 84.259843 692.870079 0 ] (cb5-1) [ 59 0 R /XYZ 101.433071 691.173057 0 ] (cb5-2) [ 59 0 R /XYZ 99.933071 672.226036 0 ] (cb5-3) [ 59 0 R /XYZ 99.933071 653.279014 0 ] (cb5-4) [ 59 0 R /XYZ 99.933071 634.331993 0 ] (cb5-5) [ 59 0 R /XYZ 99.933071 615.384971 0 ] (cb6) [ 59 0 R /XYZ 84.259843 533.634971 0 ] (cb6-1) [ 59 0 R /XYZ 101.433071 531.937950 0 ] (cb6-2) [ 59 0 R /XYZ 99.933071 512.990928 0 ] (cb6-3) [ 59 0 R /XYZ 99.933071 494.043907 0 ] (cb6-4) [ 59 0 R /XYZ 99.933071 456.149864 0 ] (cb6-5) [ 59 0 R /XYZ 99.933071 437.202842 0 ] (cb6-6) [ 59 0 R /XYZ 99.933071 399.308799 0 ] (cb7) [ 72 0 R /XYZ 84.259843 799.370079 0 ] (cb7-1) [ 72 0 R /XYZ 101.433071 797.673057 0 ] (cb7-2) [ 72 0 R /XYZ 99.933071 778.726036 0 ] (cb7-3) [ 72 0 R /XYZ 99.933071 759.779014 0 ] (cb7-4) [ 72 0 R /XYZ 99.933071 740.831993 0 ] (cb7-5) [ 72 0 R /XYZ 99.933071 721.884971 0 ] (cb7-6) [ 72 0 R /XYZ 99.933071 702.937950 0 ] (cb9) [ 81 0 R /XYZ 84.259843 126.824079 0 ] (cb9-1) [ 81 0 R /XYZ 101.433071 125.127057 0 ] (cb9-10) [ 85 0 R /XYZ 99.933071 666.543907 0 ] (cb9-100) [ 165 0 R /XYZ 99.933071 401.285606 0 ] (cb9-101) [ 165 0 R /XYZ 99.933071 382.338585 0 ] (cb9-102) [ 165 0 R /XYZ 99.933071 363.391563 0 ] (cb9-103) [ 165 0 R /XYZ 99.933071 344.444542 0 ] (cb9-104) [ 165 0 R /XYZ 99.933071 325.497520 0 ] (cb9-105) [ 165 0 R /XYZ 99.933071 306.550499 0 ] (cb9-106) [ 165 0 R /XYZ 99.933071 287.603477 0 ] (cb9-107) [ 165 0 R /XYZ 99.933071 268.656456 0 ] (cb9-108) [ 165 0 R /XYZ 99.933071 249.709434 0 ] (cb9-109) [ 165 0 R /XYZ 99.933071 230.762413 0 ] (cb9-11) [ 85 0 R /XYZ 99.933071 647.596885 0 ] (cb9-110) [ 165 0 R /XYZ 99.933071 211.815391 0 ] (cb9-111) [ 165 0 R /XYZ 99.933071 192.868370 0 ] (cb9-112) [ 165 0 R /XYZ 99.933071 173.921348 0 ] (cb9-113) [ 165 0 R /XYZ 99.933071 154.974327 0 ] (cb9-114) [ 165 0 R /XYZ 99.933071 136.027305 0 ] (cb9-115) [ 165 0 R /XYZ 99.933071 117.080284 0 ] (cb9-116) [ 165 0 R /XYZ 99.933071 98.133262 0 ] (cb9-117) [ 205 0 R /XYZ 99.933071 799.173057 0 ] (cb9-118) [ 205 0 R /XYZ 99.933071 780.226036 0 ] (cb9-119) [ 205 0 R /XYZ 99.933071 761.279014 0 ] (cb9-12) [ 85 0 R /XYZ 99.933071 628.649864 0 ] (cb9-120) [ 205 0 R /XYZ 99.933071 742.331993 0 ] (cb9-121) [ 205 0 R /XYZ 99.933071 723.384971 0 ] (cb9-122) [ 205 0 R /XYZ 99.933071 704.437950 0 ] (cb9-123) [ 205 0 R /XYZ 99.933071 685.490928 0 ] (cb9-124) [ 205 0 R /XYZ 99.933071 666.543907 0 ] (cb9-125) [ 205 0 R /XYZ 99.933071 647.596885 0 ] (cb9-126) [ 205 0 R /XYZ 99.933071 628.649864 0 ] (cb9-127) [ 205 0 R /XYZ 99.933071 609.702842 0 ] (cb9-128) [ 205 0 R /XYZ 99.933071 590.755821 0 ] (cb9-129) [ 205 0 R /XYZ 99.933071 571.808799 0 ] (cb9-13) [ 85 0 R /XYZ 99.933071 609.702842 0 ] (cb9-130) [ 205 0 R /XYZ 99.933071 552.861778 0 ] (cb9-131) [ 205 0 R /XYZ 99.933071 533.914756 0 ] (cb9-132) [ 205 0 R /XYZ 99.933071 514.967735 0 ] (cb9-133) [ 205 0 R /XYZ 99.933071 496.020714 0 ] (cb9-134) [ 205 0 R /XYZ 99.933071 477.073692 0 ] (cb9-135) [ 205 0 R /XYZ 99.933071 458.126671 0 ] (cb9-136) [ 205 0 R /XYZ 99.933071 439.179649 0 ] (cb9-137) [ 205 0 R /XYZ 99.933071 420.232628 0 ] (cb9-138) [ 205 0 R /XYZ 99.933071 401.285606 0 ] (cb9-139) [ 205 0 R /XYZ 99.933071 382.338585 0 ] (cb9-14) [ 85 0 R /XYZ 99.933071 590.755821 0 ] (cb9-140) [ 205 0 R /XYZ 99.933071 363.391563 0 ] (cb9-141) [ 205 0 R /XYZ 99.933071 344.444542 0 ] (cb9-142) [ 205 0 R /XYZ 99.933071 325.497520 0 ] (cb9-143) [ 205 0 R /XYZ 99.933071 306.550499 0 ] (cb9-144) [ 205 0 R /XYZ 99.933071 287.603477 0 ] (cb9-145) [ 205 0 R /XYZ 99.933071 268.656456 0 ] (cb9-146) [ 205 0 R /XYZ 99.933071 249.709434 0 ] (cb9-147) [ 205 0 R /XYZ 99.933071 230.762413 0 ] (cb9-148) [ 205 0 R /XYZ 99.933071 211.815391 0 ] (cb9-149) [ 205 0 R /XYZ 99.933071 192.868370 0 ] (cb9-15) [ 85 0 R /XYZ 99.933071 571.808799 0 ] (cb9-150) [ 205 0 R /XYZ 99.933071 173.921348 0 ] (cb9-151) [ 205 0 R /XYZ 99.933071 154.974327 0 ] (cb9-152) [ 205 0 R /XYZ 99.933071 136.027305 0 ] (cb9-153) [ 205 0 R /XYZ 99.933071 117.080284 0 ] (cb9-154) [ 205 0 R /XYZ 99.933071 98.133262 0 ] (cb9-155) [ 245 0 R /XYZ 99.933071 799.173057 0 ] (cb9-156) [ 245 0 R /XYZ 99.933071 780.226036 0 ] (cb9-157) [ 245 0 R /XYZ 99.933071 761.279014 0 ] (cb9-158) [ 245 0 R /XYZ 99.933071 742.331993 0 ] (cb9-159) [ 245 0 R /XYZ 99.933071 723.384971 0 ] (cb9-16) [ 85 0 R /XYZ 99.933071 552.861778 0 ] (cb9-160) [ 245 0 R /XYZ 99.933071 704.437950 0 ] (cb9-161) [ 245 0 R /XYZ 99.933071 685.490928 0 ] (cb9-162) [ 245 0 R /XYZ 99.933071 666.543907 0 ] (cb9-163) [ 245 0 R /XYZ 99.933071 647.596885 0 ] (cb9-164) [ 245 0 R /XYZ 99.933071 628.649864 0 ] (cb9-165) [ 245 0 R /XYZ 99.933071 609.702842 0 ] (cb9-17) [ 85 0 R /XYZ 99.933071 533.914756 0 ] (cb9-18) [ 85 0 R /XYZ 99.933071 514.967735 0 ] (cb9-19) [ 85 0 R /XYZ 99.933071 496.020714 0 ] (cb9-2) [ 81 0 R /XYZ 99.933071 106.180036 0 ] (cb9-20) [ 85 0 R /XYZ 99.933071 477.073692 0 ] (cb9-21) [ 85 0 R /XYZ 99.933071 458.126671 0 ] (cb9-22) [ 85 0 R /XYZ 99.933071 439.179649 0 ] (cb9-23) [ 85 0 R /XYZ 99.933071 420.232628 0 ] (cb9-24) [ 85 0 R /XYZ 99.933071 401.285606 0 ] (cb9-25) [ 85 0 R /XYZ 99.933071 382.338585 0 ] (cb9-26) [ 85 0 R /XYZ 99.933071 363.391563 0 ] (cb9-27) [ 85 0 R /XYZ 99.933071 344.444542 0 ] (cb9-28) [ 85 0 R /XYZ 99.933071 325.497520 0 ] (cb9-29) [ 85 0 R /XYZ 99.933071 306.550499 0 ] (cb9-3) [ 85 0 R /XYZ 99.933071 799.173057 0 ] (cb9-30) [ 85 0 R /XYZ 99.933071 287.603477 0 ] (cb9-31) [ 85 0 R /XYZ 99.933071 268.656456 0 ] (cb9-32) [ 85 0 R /XYZ 99.933071 249.709434 0 ] (cb9-33) [ 85 0 R /XYZ 99.933071 230.762413 0 ] (cb9-34) [ 85 0 R /XYZ 99.933071 211.815391 0 ] (cb9-35) [ 85 0 R /XYZ 99.933071 192.868370 0 ] (cb9-36) [ 85 0 R /XYZ 99.933071 173.921348 0 ] (cb9-37) [ 85 0 R /XYZ 99.933071 154.974327 0 ] (cb9-38) [ 85 0 R /XYZ 99.933071 136.027305 0 ] (cb9-39) [ 85 0 R /XYZ 99.933071 117.080284 0 ] (cb9-4) [ 85 0 R /XYZ 99.933071 780.226036 0 ] (cb9-40) [ 85 0 R /XYZ 99.933071 98.133262 0 ] (cb9-41) [ 125 0 R /XYZ 99.933071 799.173057 0 ] (cb9-42) [ 125 0 R /XYZ 99.933071 780.226036 0 ] (cb9-43) [ 125 0 R /XYZ 99.933071 761.279014 0 ] (cb9-44) [ 125 0 R /XYZ 99.933071 742.331993 0 ] (cb9-45) [ 125 0 R /XYZ 99.933071 723.384971 0 ] (cb9-46) [ 125 0 R /XYZ 99.933071 704.437950 0 ] (cb9-47) [ 125 0 R /XYZ 99.933071 685.490928 0 ] (cb9-48) [ 125 0 R /XYZ 99.933071 666.543907 0 ] (cb9-49) [ 125 0 R /XYZ 99.933071 647.596885 0 ] (cb9-5) [ 85 0 R /XYZ 99.933071 761.279014 0 ] (cb9-50) [ 125 0 R /XYZ 99.933071 628.649864 0 ] (cb9-51) [ 125 0 R /XYZ 99.933071 609.702842 0 ] (cb9-52) [ 125 0 R /XYZ 99.933071 590.755821 0 ] (cb9-53) [ 125 0 R /XYZ 99.933071 571.808799 0 ] (cb9-54) [ 125 0 R /XYZ 99.933071 552.861778 0 ] (cb9-55) [ 125 0 R /XYZ 99.933071 533.914756 0 ] (cb9-56) [ 125 0 R /XYZ 99.933071 514.967735 0 ] (cb9-57) [ 125 0 R /XYZ 99.933071 496.020714 0 ] (cb9-58) [ 125 0 R /XYZ 99.933071 477.073692 0 ] (cb9-59) [ 125 0 R /XYZ 99.933071 458.126671 0 ] (cb9-6) [ 85 0 R /XYZ 99.933071 742.331993 0 ] (cb9-60) [ 125 0 R /XYZ 99.933071 439.179649 0 ] (cb9-61) [ 125 0 R /XYZ 99.933071 420.232628 0 ] (cb9-62) [ 125 0 R /XYZ 99.933071 401.285606 0 ] (cb9-63) [ 125 0 R /XYZ 99.933071 382.338585 0 ] (cb9-64) [ 125 0 R /XYZ 99.933071 363.391563 0 ] (cb9-65) [ 125 0 R /XYZ 99.933071 344.444542 0 ] (cb9-66) [ 125 0 R /XYZ 99.933071 325.497520 0 ] (cb9-67) [ 125 0 R /XYZ 99.933071 306.550499 0 ] (cb9-68) [ 125 0 R /XYZ 99.933071 287.603477 0 ] (cb9-69) [ 125 0 R /XYZ 99.933071 268.656456 0 ] (cb9-7) [ 85 0 R /XYZ 99.933071 723.384971 0 ] (cb9-70) [ 125 0 R /XYZ 99.933071 249.709434 0 ] (cb9-71) [ 125 0 R /XYZ 99.933071 230.762413 0 ] (cb9-72) [ 125 0 R /XYZ 99.933071 211.815391 0 ] (cb9-73) [ 125 0 R /XYZ 99.933071 192.868370 0 ] (cb9-74) [ 125 0 R /XYZ 99.933071 173.921348 0 ] (cb9-75) [ 125 0 R /XYZ 99.933071 154.974327 0 ] (cb9-76) [ 125 0 R /XYZ 99.933071 136.027305 0 ] (cb9-77) [ 125 0 R /XYZ 99.933071 117.080284 0 ] (cb9-78) [ 125 0 R /XYZ 99.933071 98.133262 0 ] (cb9-79) [ 165 0 R /XYZ 99.933071 799.173057 0 ] (cb9-8) [ 85 0 R /XYZ 99.933071 704.437950 0 ] (cb9-80) [ 165 0 R /XYZ 99.933071 780.226036 0 ] (cb9-81) [ 165 0 R /XYZ 99.933071 761.279014 0 ] (cb9-82) [ 165 0 R /XYZ 99.933071 742.331993 0 ] (cb9-83) [ 165 0 R /XYZ 99.933071 723.384971 0 ] (cb9-84) [ 165 0 R /XYZ 99.933071 704.437950 0 ] (cb9-85) [ 165 0 R /XYZ 99.933071 685.490928 0 ] (cb9-86) [ 165 0 R /XYZ 99.933071 666.543907 0 ] (cb9-87) [ 165 0 R /XYZ 99.933071 647.596885 0 ] (cb9-88) [ 165 0 R /XYZ 99.933071 628.649864 0 ] (cb9-89) [ 165 0 R /XYZ 99.933071 609.702842 0 ] (cb9-9) [ 85 0 R /XYZ 99.933071 685.490928 0 ] (cb9-90) [ 165 0 R /XYZ 99.933071 590.755821 0 ] (cb9-91) [ 165 0 R /XYZ 99.933071 571.808799 0 ] (cb9-92) [ 165 0 R /XYZ 99.933071 552.861778 0 ] (cb9-93) [ 165 0 R /XYZ 99.933071 533.914756 0 ] (cb9-94) [ 165 0 R /XYZ 99.933071 514.967735 0 ] (cb9-95) [ 165 0 R /XYZ 99.933071 496.020714 0 ] (cb9-96) [ 165 0 R /XYZ 99.933071 477.073692 0 ] (cb9-97) [ 165 0 R /XYZ 99.933071 458.126671 0 ] (cb9-98) [ 165 0 R /XYZ 99.933071 439.179649 0 ] (cb9-99) [ 165 0 R /XYZ 99.933071 420.232628 0 ] (conclusion) [ 245 0 R /XYZ 84.259843 575.052842 0 ] (configure-default-service-account) [ 56 0 R /XYZ 84.259843 388.198913 0 ] (contentsbox) [ 8 0 R /XYZ 77.509843 756.850394 0 ] (control-1.1.12) [ 72 0 R /XYZ 84.259843 368.389950 0 ] (control-5.1.5) [ 72 0 R /XYZ 84.259843 164.143950 0 ] (control-5.3.2) [ 81 0 R /XYZ 84.259843 520.622079 0 ] (create-the-etcd-user) [ 49 0 R /XYZ 84.259843 500.585993 0 ] (ensure-etcd-is-configured-properly) [ 41 0 R /XYZ 84.259843 480.020658 0 ] (ensure-protect-kernel-defaults-is-set) [ 39 0 R /XYZ 84.259843 289.233496 0 ] (header_bottom_text) [ 6 0 R /XYZ 85.009843 422.718898 0 ] (host-level-requirements) [ 39 0 R /XYZ 84.259843 369.381496 0 ] (known-issues) [ 72 0 R /XYZ 84.259843 463.537950 0 ] (kubernetes-runtime-requirements) [ 49 0 R /XYZ 84.259843 352.740971 0 ] (networkpolicies) [ 56 0 R /XYZ 84.259843 663.033496 0 ] (overview) [ 26 0 R /XYZ 84.259843 283.881496 0 ] (podsecuritypolicies) [ 49 0 R /XYZ 84.259843 257.592971 0 ] (reference-hardened-rke2-template-configuration) [ 81 0 R /XYZ 84.259843 228.224079 0 ] (set-kernel-parameters) [ 49 0 R /XYZ 84.259843 799.370079 0 ] (setting-up-hosts) [ 41 0 R /XYZ 84.259843 237.872658 0 ] (title-block-header) [ 6 0 R /XYZ 84.259843 502.818898 0 ] ] ->> ->> ->> -endobj -4 0 obj -<< -/ExtGState << -/a1.0 << -/ca 1 ->> -/A1.0 << -/CA 1 ->> ->> -/XObject << ->> -/Pattern << ->> -/Shading << ->> -/Font 298 0 R ->> -endobj -5 0 obj -<< -/Filter /FlateDecode -/Length 2585 ->> -stream -x[+tmvUW /BBrk0X"?oR4zhȈQW>ꢤ0jH؛Fu8QX\.–,QlI& 8^LN$+61e[b,Nu3lpBc@,%x ^bmK1R -〉B$όqrXs `Ktc,0ֱ[ uiX`ୋfpa0k5;cJ\; q/Zʑ] 5Wa,pp -`3cR 1XՀ} WBU ܍UXAc,pp7&<nL ܍3c6JF.x8[X{10$pW9ӠU2cAwb-qrn1Asn ܅2Ƃ𨑱 jLjlX] !(Ku-H Rd,RA+I C 2  2+Ɍ {Xkñ%gjR0+f:pW4Ƃ vXKXXVJf,MCGu9 @,-^uh*cAbd,( d`,@D"lvD Y͝| t9Zkia,(\2 -=\b,Щ3[pT B̙Na lDЩ2[ 2Xefa,F.f:gVƂ9P&HIu`,d;1 A4`%g,5t2 -[D͞oƂ&cAzXC'Xд"ߌXsXLo"#Yfa,h[B-9`MЉ2l Z=߬3o"W盅^LL"2͌( Ddr{xSA|ƕgЛ[镁Vs$zi3YLo VT"&\o+P3kp,9V5{Oد?~ {?:nKsOs&r~ZO[?5(!?v ǥŦh>6ʫr~|W'J_Bޡ'H?~_+?~3|l7 ǑI-%>aUrVSʯg3^m g!|-N5أyNl׶jǷ0]ם&GV^oZ'TTڦ -xv6z?]|@-qLC"uܥMo ޝ% ׿8s&j)cǥYv.=a}+; 'أ띗b8\ <~W( -'Vf_HA3}yM$r{f[ڧѬ"[qLhQܟ^e^޸4uաuWGj ӣP8G{1./4}:ݖԍe[ /' kϥOToFWcv͇6ڔQs.u"ˉ_ڱSZ:6zm#ˉֻJYm2emus옣¶3"6ދs_־ ?NiBzж~/K86U8C#4<$YzVi O.ϓ:f@ti)sUHY{؝tM^0Cj^sMqGؘ]( in;3ͣduiyiSiwCx9?_ Kez5&\ -K0titˍ1{9r:\[|!#&=u^_'?7R2i'[Ļ'OpM}k]u ӏǸWsY`5uTv58έնI^ d~,}-x8 c=yV?ul%Jrzw6`[ݙ7>ȜnKa}hK][]A۝=/>^yo&qt}Jv|.R;8}{a5C/Ξ gZ]aߣf -iԇn(&. !=aS5r.ZԜe5gƸGr7m܄'([WnYH7}pz|?˝Y,=U`k> -endobj -7 0 obj -<< -/Filter /FlateDecode -/Length 3356 ->> -stream -xOo$)lc'r 1`F1 ݁F X琯bOj]z Ep5󵥿JR֜ry<}:sb{G?.st9uٞM.9d?B̨?Hݰ.N7YzXbq0ڳ-tN[_~ Jg(mΩ~_O߼/)jbnq.s)EJ/{:UA}. -X(a'J{aQQ{ Ξp-}^DX dĭNQ vjnș-ۍf ![ ĸ*|p@_uZD2J|nuQ;uZDΔ !|Q1щD轫("-OJ&щ!݉Dt"jݒuDY(N_EQ? Z -&%#\+PT)ݻx^D= ^KJC@Ct(Djĺ`LC>dCu1ds:"*}pz@UQaHCD -L~Лch'&щ;_ -DIDt":}#Du;ND_m.QV_EQEԇ iu(WXC$,-HD pDJ|< V`]":X(Ԉu;5s1"gJϷl7-|H҇ bȬgw@7tFFU%+B>؁}pD!Sz_(qE1Dt"z@ע(D>)=ND'o7#t'щkmtU! -@1XBE4 iu(W0r!v u8ሔx{@t " -5bNM0{ș-ۍf at1dʹ |pz@4DQqHsD -#r|Q1b4щD蝯Eh"::НND'MIGu" vuE(`]":•r?:s@Ct(Dj`Թ(gJϷh!I0!Sረ |ѬU: i(T`чpD3BoQY'&щ;_ -DEEңDt"F(>;Bw":FE}e]荾~htI}+1Q.WC$,MA}KwLp>/?D4`" -5`NM09SzelC>4`XC(o |=+oiU}X>҇h5Q;ǷtC|Q1"Dt":= zkQDT\>)=ND'o7#t'щmtKe]}EhIo*WO10#\(HX Wҝs@Ct(DǺ` 1LC>DCu1d>ҝ\Q}(atQ;[!Sz_(qEEpb":@T\>)=ND'o7#t'щmtCWQ%aWQoM!rqS W!;8ህpWG]"Zr0n&Xpș-ۍf ú2YyKnIyKw*E |(҇h5Q;ǷtC|Q1"Dt":= zkQDT\>)=ND'o7#t'щ6NZŧdiIѝCtvyx??`Mӷ/:qvKа|_1d}=aV^<[cyܬgyX*w)X/V~y~!/љ%] =<зQ돷?@V$_Oy*˷ỿs.Cm0w6&~wDWX?{q|ٯ?Uhk䇽0j kMr5Jֶ>'r+cqiӱ$z[!oOڵus")Iuz.X=G1: Oqݳ{r2蹴﯏ݟ|r.Ğ}m =cxGrmu=g>Oulm$^w:ֹPm̑A :Үl.?Ѷ 6՟&wJss=]LUj3T2fJpaSEb>ۺenׇ֖_+ѧS,d.52MwѹJdf*nY#?Rܛsv ^"pZiGnR>"[vi6e-/?4`[іmMIfIzS6R}P[`E;=ʵUU&b9*L"W,W7~Vހp,Ok+õ{Nbo:΂`SDav͵:5Z[nH>)R} s6@f5z ˭"]Nj؝ʽT[זyn -u_zmѮ4u(@7 ^Nu9ґ -CC]. TM[u]3>r+RL:A\esceQI* IOR}uNa-?}DѴFP8cBvƎ* ,Yrsʹ;nSu oe[­\~iAXvv DnM -,4ɍ>;u2mŽ~;m˜ѭ^{eybQߧ|[3}p}n2dfge.vl@t}mᲱ;u O쭤3Ϣ9 >txbȼ^uxU/;tY9KUU-K:=HX)]B[&Y$驯hsYi[/Hps`1*ڣ4n^jڻjXU~L9~ ^P{or Zqc·" MABѧ Lz)l=.jrSf:+=]I޶ݒ9s {ɢh jiAnܐ;S÷Cɻ{QSRXÖ~ah6{痵nwJJ4PGUs(p{>8oDvЋvo6h=~ j7mQ(:<OJ\_*Ƶ_7j֏Gq~ -endstream -endobj -8 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 7 0 R -/Resources 4 0 R -/Annots [ 9 0 R 10 0 R 11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R 17 0 R 18 0 R 19 0 R 20 0 R 21 0 R 22 0 R 23 0 R 24 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -9 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 671.061024 504.679134 638.361024 ] -/BS << -/W 0 ->> -/Dest (overview) ->> -endobj -10 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 489.361263 663.111024 496.429134 648.111024 ] -/BS << -/W 0 ->> -/Dest (overview) ->> -endobj -11 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 626.361024 504.679134 593.661024 ] -/BS << -/W 0 ->> -/Dest (host-level-requirements) ->> -endobj -12 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.881526 618.411024 496.429134 603.411024 ] -/BS << -/W 0 ->> -/Dest (host-level-requirements) ->> -endobj -13 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 581.661024 504.679134 548.961024 ] -/BS << -/W 0 ->> -/Dest (setting-up-hosts) ->> -endobj -14 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.893245 573.711024 496.429134 558.711024 ] -/BS << -/W 0 ->> -/Dest (setting-up-hosts) ->> -endobj -15 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 536.961024 504.679134 504.261024 ] -/BS << -/W 0 ->> -/Dest (kubernetes-runtime-requirements) ->> -endobj -16 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.809749 529.011024 496.429134 514.011024 ] -/BS << -/W 0 ->> -/Dest (kubernetes-runtime-requirements) ->> -endobj -17 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 492.261024 504.679134 459.561024 ] -/BS << -/W 0 ->> -/Dest (api-server-audit-configuration) ->> -endobj -18 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.857357 484.311024 496.429134 469.311024 ] -/BS << -/W 0 ->> -/Dest (api-server-audit-configuration) ->> -endobj -19 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 447.561024 504.679134 414.861024 ] -/BS << -/W 0 ->> -/Dest (known-issues) ->> -endobj -20 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 488.869808 439.611024 496.429134 424.611024 ] -/BS << -/W 0 ->> -/Dest (known-issues) ->> -endobj -21 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 402.861024 504.679134 370.161024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke2-template-configuration) ->> -endobj -22 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 485.053890 394.911024 496.429134 379.911024 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke2-template-configuration) ->> -endobj -23 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 76.423228 358.161024 504.679134 325.461024 ] -/BS << -/W 0 ->> -/Dest (conclusion) ->> -endobj -24 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 485.053890 350.211024 496.429134 335.211024 ] -/BS << -/W 0 ->> -/Dest (conclusion) ->> -endobj -25 0 obj -<< -/Filter /FlateDecode -/Length 4642 ->> -stream -x][$7~_1H|D -B!v'9,RC>m]3sf7D@Ξ*wn\")z賙RFd)X ,rn -8/`bJ j@5(E'V[V&hXPC'VCDQD<&{gc2It0NK4y]x]\RZ94xЅl Cy`%^.I/BdWyEy%^KH%T q3M.Z$֓CnZ t%]UFYBx gCj5yu[esŘ@" ]T`M$ 0!L I `(RP4QVD> -UőjBX"DX]0@k!+aE %xKJ{ ,j* ,FOX@.R)IX`)ab ,P:o$,]KKX`N]'V aw< W&&*&` yap8 ]㔑2X w!N. V+aMe?aM&wuDD^tDžu /O$ab8.3JX pW[MR8.'aa($,6iyiR)F pd$,.<$yaB"i ƓB*ab{OxrJXP3JXOT&RAOnh~ly: F(aA(#ar3A‚ *> S.%,IG$,f Y~-n $.%ȃ.(nI7NCH‚}7(3ob7x\u $񀻨L@Vg233' -밷G -؋*g -{$j^<5 -Vⱁ &̧O# ˂Pݷ;=}^~QN[ƺ$ %є׮՜~=y[ӳu4"LԱΜבQG:PG3a+脢sMGGsz6#+ARR9S:kT7㯱,9n_ Ix;BɅ4Rk:v\}nC.\`|ra1K ~y+F[F v'Yfd}IY4X.ӳ;ޢ39i(J:J"a~=(-ˁGVEםxްGvLă%%@' E2^J̿!^rްGv<^ax1?>YX,Pb =|g">;?-:s3>س$[{da {םxްGvL!^KρO&!^rްGv<^ ߇x /׵{}0ߟנ\_ =|g"m/O/gѢW/g\KlPo.X5S*jy˿n|J+2eiS~7C ׹}i6L=}7j6|\r99-߫}a+ 5|OZr3kC?ڏ97|UcY6ŮV޲j.)9Ə8stfM)7݆8ǯcvUv]Y׬C.9y~=` -Ri\y?ދQkbqX.ymsIr,K g}1a!k,y>aκd}]c= s&¯}QhYɽ8 5i" ³yeUk]cΣ{v8¢kZ=U>[=˽uoF}f7| {C#.Qhڇɱ9111l?'ZsrX:U2ܵ6w͏yͯnZ:rYG$tߊjM-QWCO -h&]?nˎߟ>ҥ(VN.(9_Rʝ<厶CG{)3Z/[݇c\m68ՊGMPsS=U -[ܴ +NӖ4"i~Ɋpxj򝉱vzAZ+G5qkdK\=q?)^iL㹞Џvmo#<އiS݉#Sa_O ϓ4㰲3BK~q#j9C,@[y7j[UtxgcϮWv~FZ[k_>C+W=![蟿O?/gF2y-_f{:Sy\|F\,E_j-Nyϡsl8RZ8?A̡n`9ZmU2{0erK򾔝Jr] 5qvfz 5UQiԦ}Cev m9in]v{,wܓ;bg[wxpN||t '>>Ʃ'z|78H^:zǐ.ݘL_>rc` -lAB2iz7=ZbZp[|y .Q>NaNC:@DeIW׬ٹO-5ODO(!9>tӣ2UԋNH H4w3qy,D.'KMjyُ/]-?BhUyb;ޒj 9?/NvMԀ@c~Mݖtla|'6չ4 k r´vM*zWi)Ց- $.'FUф`6>Z~TL5Ku@q4"ڨoM]66 ;l([_d#Pc?!/NЛІ|= v+ljmztjUXt5jF"o -W}ˉG'qoCWi -!Q 3cCej1u˺FVӰUU"]K@zTjy5v^99䡦or/ec59~tQm1bW F\WkC/2iǽ;mXg^xxŤ?blj_Q -Lցwx'9?۲aDC ;Y>lh1 ߮:ב!n\Nt݇lZmgb+dM߰K[4M$ .cپ%H\}K \(.لk6O\' -bȗo\t+_piGP/*2A{^9 d-~l{=狺x,֞mEN_(~2I҆IF4UiMb:bqZMѩqO;Dǣ7cܺjɶt:GZ2 -4nT#mmq۞2U6*{ɥQéYg>kly|C(?4Pds|=ݨ|&UAtDI|[RI9@80=*ON UyA7'Xo -endstream -endobj -26 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 25 0 R -/Resources 4 0 R -/Annots [ 27 0 R 28 0 R 29 0 R 30 0 R 31 0 R 32 0 R 33 0 R 34 0 R 35 0 R 36 0 R 37 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -27 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 445.281496 409.271317 430.281496 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://releases.rancher.com/documents/security/2.6/Rancher_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf) ->> ->> -endobj -28 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 418.281496 162.214732 403.281496 ] -/BS << -/W 0 ->> -/Dest (overview) ->> -endobj -29 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 403.281496 251.801646 388.281496 ] -/BS << -/W 0 ->> -/Dest (host-level-requirements) ->> -endobj -30 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 388.281496 203.586314 373.281496 ] -/BS << -/W 0 ->> -/Dest (setting-up-hosts) ->> -endobj -31 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 373.281496 309.303355 358.281496 ] -/BS << -/W 0 ->> -/Dest (kubernetes-runtime-requirements) ->> -endobj -32 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 358.281496 284.198131 343.281496 ] -/BS << -/W 0 ->> -/Dest (api-server-audit-configuration) ->> -endobj -33 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 343.281496 187.304576 328.281496 ] -/BS << -/W 0 ->> -/Dest (known-issues) ->> -endobj -34 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 328.281496 407.493297 313.281496 ] -/BS << -/W 0 ->> -/Dest (reference-hardened-rke2-template-configuration) ->> -endobj -35 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 107.173228 313.281496 174.285045 298.281496 ] -/BS << -/W 0 ->> -/Dest (conclusion) ->> -endobj -36 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 293.575760 152.481496 483.355790 137.481496 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke2-1.6-benchmark-2.6/) ->> ->> -endobj -37 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 84.259843 137.481496 285.368241 122.481496 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke2-1.6-benchmark-2.6/) ->> ->> -endobj -38 0 obj -<< -/Filter /FlateDecode -/Length 4975 ->> -stream -x]]m}_1$d`AcFpe΃{ݜ;wKpu`C rp||ɻ<,-6 ~J:ťrMBJK .uo~qO8GZ!QXLR|2X ,`J)ؚłp#@ n5Y,1VU!q td5K`1BK`9BAL2-^ .+-˅C -s!Kj>XYR`0b2dLAX YY" ^,j >XF.lxzE\D|Lv%LdI#kJnSx XAB!/ق 'da@,ql@rP ` 8b^ , cR7nCy:zeh=fP7@7|AՌJS/ߓȞ4sMA((<ñ#F9!G3#oԸ9f|-}hAIiֻ"ePtSHVRtu1-W0ϑ7ȶwy3HªJc/ߚ4'ZۼYv]z#pBFWEO+[ ?S;yLkOk[ vyG煖qVi/}aUEJ/h9.kZ9 6E}CD K -b-*I-QxQ18r3xvNB~ㆴ.u}i MVyUӢT ~Zf?ZUv:nﻴ+&!5W7"KTͩi]^ouWx2[wź6Y~~ lJ!Ƕ-ٴzyR1׶}k[z/\4@ #׼WxV,{KGH+yy|3`b^9C`zޠ@o^M0.wc?M$&Dz{^V_T[ew@ )7p˴ݭ\vC)(6EXo,ĖuWq//}?Rޕ=RR]´ +Mcq>ո`3@'p p kЃ{nwj3`d<zR bACh̭dC>K':gkk5Hnj ~kw I%%d"SSKr0s஗OѺh}Uy Q+yys1ChIT+XQ"?>0֡QeD=JGUW^j|IKvy|.g/:[81+SJ p*,։yŎJrW'i ˜͌SRoJ^Nn4*S#e-=u]=rwZOZ4ުn3j0rcn=;ո8x&=nNԺe=}UsBny ;d/}"$M{=}ׇ7İUf֨;byy7Hm]vZd|{u||vR <͙COw&RR=<*{֊ sH\9bا轧,5 \yF?¡!:wtt'!e'ȏUP;q3خ~ #Zw)8 ގz9h^ȽcnA7^oR2k?+uScL-'M%?{Z^c2t $}3LP7vzưFwƪY73]DQUYقXVFo֮|E-a6S"lJ2z􎻙?֎ N} ^oߏ[vꦮ-vqƌ)[Y&~q]Y1,zG<5UOȰIòЙx:,uC}{DvJk(I}].^O>+NQ|&شI-I|jZH8~WNq7IT!~t?ynm}j!OҊsA[Q\`l> tx1m}3 swKAO`[&ZJC9ǎS]klŧ|q!!v"W3>d;7ef,t'~c:6s{d)p? ;@o1 ݣ?֍-s\ qn?'x7Tːzcpʖ<鱛ޝ YΎɁ"#ѫ&9r'k{$ѵ2o2=iiO}1>TnFJ6a't9|aWVdvGѮvr2ۭa2ZٵuOQS7hu{e?nrnW7@8/TibO4Ը\IE -[$*Ҡ -,fl9[%izÖVKuE:Ʈh/;ZmJe^ZO@jǖ @XJM] /3,i;y`&a oqwe l'>$G?ݜL`I0n$o&""(KPgL5~uq<q`놬#,ım1IuMFQ5~{o4uqn 4/;-Df%aw1u &J\ɣjH\I:BK5amԓ ՋMA2Pi\ zN[V &}'my ߼~WsB>/:&x6˼1r7ޣ̭1S \hU: ;m3i.E6F,]vjYV\M-SLPbVɇ2nx#[%eϖ#-ރʳ%uqnݣY- yf~vKo¿k js|5yLio|fUs> -endobj -40 0 obj -<< -/Filter /FlateDecode -/Length 4845 ->> -stream -x\K$ɑȳ`B0Ahaeviv@CujZb^tؿE[DZ9h0=>7st*V2O_?$ ?%$rMǯLe)-owncXZ?~dťR\2X ,Ji)%l_pY, -dA&1(j*ĈT|d5'1|K`y9|pAGiPzx/L^ϗ`b\r!kK9UG%5-^,9Y(b2d9:YB-f*dwUY\v⵸VL^R/y%~IhQ0R./@R3y%E,^,8bՈ]/A -<[2dq%[Z, ,Y j\RP ԶP)тB oAt%Q zB\Yb# b,h`aA%P m baAܒk‚%糅 1k& " ,,촰 t‚ԍ) "`7RDn$,, ni }p7zW,, .(XX.la|e : #  -W`! p7PQ3. $dZX-,`K@ZbaAψik$ய0k/иsn$.haA>+j w}Jm>4gaA"oHowp]j wK‹@W8`8d.faAiɃ, ׀5bw-p׹,,]^6-,ȅ ZXd‚\iid rs!3yyu8 A*daV-,(,,( e ȂL R%ecЪapm*xXXP --XpdaϓAX[<Yd[XL<-, *3; B-93©T@JY>\l' PDc KLdaAjaA%`a|baAsd 9gaAf \oV Zt7QqbzXX$(& ijFPo,^,-g7H3Po"7*כ.dx]d\Dfk -3Y掁&斁b*极rdn@LT5XV6p_ct 'Ekf-| aAG1+c/X|/֝2 EF:qs=+M~xx@cJӕөYZ#[m[r+ -:!Ս7Ԡ6j'ů*M  \:{ QKFgY&&e?+?6Gv895?\&H[@RW3n0j'^qO&>" hR?,N"%/G 7uXQlE=-Cm=mKtl |7 CL,!̇#תּU -,#(p[Otv'i\;^q)[Šܦ) -F4A|r5._ zOrȬ|t^HTa>:? џς.2 -|q<$ChxA)Z{{a6D6;6l6ಔn?<Ͽ>}9p SKǕqtuϽ?ߒҭ@ۑpFs}C+iZQɑl[TV9qWAiB_su7iעrm/J~>y7)Nso\if.tD67G?Y=R~TpDOb-nw:;lG6]e{uۋҔ閿>W鉇WyC箷 q6Q-ɜҖPl;G1k*?tl)ۑg^^zl]+48$;vǼ/F,tK*ՕfUTq"(-D{nX4ZBgݧbq *݇ntr1ߝ=8qu{8ۻqpK[CKKDǡlL \my![Hqͪpb1sOuν"˳c'r5o5ح]WzUy^9<8%a;?:<q1!~G^;p(=ΧB:vh;6iv\q0d3Wq29N)N;Ug 9gDH7\Npu[e8J` pʨQ z~㑀{77 W ~܏\a.%5Ww uJ[ּ :}^"L5A1ҸA~ԇ;H /K5,|̼@=ࡼnp!ʭǽzz%y[t+Юxyߨ>"㩜vf7 yKHi}x>ֵPF-7q2f"nq/UL5DJ9;0m0.U/BcJciQND$@H^R.tzѬ&jFhX/M)$ JFIk8.E1skLino@&qUպםAO\?u -n[]f҆IP]"]_"S_aSFjG|R;%qy*Pmr/ne>"_I ɟ -ÍD۵>E>O2S]+vXdw>_r]OQ*aa(+oWɋs\}hWǟXWw_|vo\\L끿}Eycq&-cZ\sSqn!$DV=$/4N%<x"3s@m瀳]2?2tHZ*U]h~2]=֡xvR\"qQܒ3[@l}M F$N!uXᒸ&F5 W7eRwU!4oPgOؼ $"oyYTf[.~'^1vuF{zhlCU*SD<[^7 aD~wp yʙF&7&^{NreXLc\B< U&d~LgLS0$O}] 2k=vXS6G_??s):@0uC+DZ>H: -q"R?ɾζIa!(M`~ \MLSf iőȼ6s>_F9L#""e8Wt.RPqťM6bCIY~Ҧ=.w7dCs,+ln -FPCWn͙m s[Wq|aKEuw=(;YbI -endstream -endobj -41 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 40 0 R -/Resources 4 0 R -/Annots [ 42 0 R 43 0 R 44 0 R 45 0 R 46 0 R 47 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -42 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 615.753766 101.433071 597.003766 ] -/BS << -/W 0 ->> -/Dest (cb1-1) ->> -endobj -43 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 596.806744 99.933071 578.056744 ] -/BS << -/W 0 ->> -/Dest (cb1-2) ->> -endobj -44 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 577.859723 99.933071 559.109723 ] -/BS << -/W 0 ->> -/Dest (cb1-3) ->> -endobj -45 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 558.912701 99.933071 540.162701 ] -/BS << -/W 0 ->> -/Dest (cb1-4) ->> -endobj -46 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 539.965680 99.933071 521.215680 ] -/BS << -/W 0 ->> -/Dest (cb1-5) ->> -endobj -47 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 521.018658 99.933071 502.268658 ] -/BS << -/W 0 ->> -/Dest (cb1-6) ->> -endobj -48 0 obj -<< -/Filter /FlateDecode -/Length 4733 ->> -stream -x\Y$I ~_QH H\ Z1Bbz|Ùfz5ݕv,{6W&\R'`\T7JK%p >-_Kcn)%:,K) -Xz’ QaE`h,9:ĠƂ\VXbxJYbdIcA [BRX@QyylX"5Ki<c Yd X KDFA9iY|FAx 8h( Y]YAx/d"W39#ϙx.Uvs%PTd 8! G'O9+[ sTd5p5Z4 p)-Ti _(SPPJ^WB$ 97%PԐ[Bع*BxY@!#aE%SxKF <b <Hx@.\hXةab' 9;N79CgM7@D|5,gf䛎4,|3kXPAOٷG7 K@ [`MƋҰfְaMDjI srp7 "2&"[-7ސgV+p%iԚr &2ժU0QxVd*̜xۂݏc6W{Z)?)rb>{:pt϶ ?[ٍa2L]m&F`a-uij\'㙃To7LT`ϮY9T&}>G 8Qb^ -}rxN_~_w ^N1BOĄNP5.Coiտf}Or~N,#( 'aa۵'Rp?|ivxk8%΋1l'aU'ÀOw(5-Nhc! EzehoK%}o￙ 0f)6ü e ٦}NNc(6Xl6J1R3XkW5#X},#mEi!kRdzi#yR73cvl46ls `[:?鄎npVsy;/8D!y-IKߴ뵾mVSKq  ' Sd5U|U7D>:xGP/SU下JH3l@zIyd*MUp0!(ym1}?&>몓qi}p@(+`X/,_/Qnte3]In**4BF9DeމSBy-iZȃ>om)o09Z|`54j;eS$FicK7E=8n\(q{[ވ+c\=x%Rk+̸3ߍ} -3cϷqvB>ͭ޶Iu r\pZ2ߚz 1=$/ h.#PbgQ{W #P thy>po]#X{}ZnkIm˷m -&nEޯ!z}තCE5 (*B{0%.X+?9i5ݬ]g:-vW5^}ܼCFF|RVX^;0]MzmN'=$1E[[9_d28NJ^{!}Iԥ9sx 9sNusܞZXy9nP=29@+6/RO]!NCh>h g]ۥ{^7ci9A ocn7]Z@Y=~W~SYwon256g~Zv_mUq#8h8=L9V/ƕNU[Ou^QqHe)tEM&[HyxnI{I>sܕܩi{s6TgO;JY$ˆRcoF)vD%ViC]# >5Rs=TKjI'^ة? /7mUkQZ5iezQޔ+u('F/ždK[ϛuhs$7g|%#[z,؀՗6ɌiB>z\>o\o0n4Bxhi'^Ŷns+mk}Û<(;մ捡anڶև:Y. ^1' H^##py/dzlq#[}SpϐIj7S_㷔o ^wh;r.!;y|>; hKOB5~U-`OJiok:sD:-g~}3O![dWzo)~ .~D^Wc}ligSI~=q92ѬMwSꫤ1uN2n/Ǚ!}N {~9skЂ6G5nARm&ŀ LS)n]-uYR1Ť]j:H %ixhoDK~@As3%Bl;87mY, qFfv wԯaZZհy~K j;_x!(2}n=Ս^3Y~J{,.+>C տ^XVu&4ĿVSEXAooKMes -endstream -endobj -49 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 48 0 R -/Resources 4 0 R -/Annots [ 50 0 R 51 0 R 52 0 R 53 0 R 54 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -50 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 686.175057 101.433071 667.425057 ] -/BS << -/W 0 ->> -/Dest (cb2-1) ->> -endobj -51 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 667.228036 99.933071 648.478036 ] -/BS << -/W 0 ->> -/Dest (cb2-2) ->> -endobj -52 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 648.281014 99.933071 629.531014 ] -/BS << -/W 0 ->> -/Dest (cb2-3) ->> -endobj -53 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 629.333993 99.933071 610.583993 ] -/BS << -/W 0 ->> -/Dest (cb2-4) ->> -endobj -54 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 387.390971 101.433071 368.640971 ] -/BS << -/W 0 ->> -/Dest (cb3-1) ->> -endobj -55 0 obj -<< -/Filter /FlateDecode -/Length 5084 ->> -stream -x]KHnxlcc , Çܮ]z}GI]vRd R;2%"/O_NfI:b8X?o -gk(-3|ZR . Lr98ǞRJt6Y䗔S2Aa -+%%Šv% FH蚕 4 SU K4İ%$e A w -φ%BQ9\\Qy <~l,1Ɛ5APxKd4d!ƋGoTdq9y vːޕUd1XWJ&Ry9;.79CgM7@d|N5,gfԛ4,@\r5,(ޠDmͤaA!<Ȃ(q LB txB @^m d7.dx]dQDf3jzVe`ح30_ԦDe5 -5j&l'٢p=3'Ȃ d??9f P"ܟOȈ]o5Y:6s;6$ά.:ґ^lt[xv"/E_A'3bWQJrt^W4IզѲ0`[5nu}fbQO:_\I4z1x UL=xCy[IN=7@V7-68P4rt^W_}P Gc0vtT\T4!m 'ӄPm:}0Kntq=mՋt}+( q+Xdu(H%X\pt.ޚ4(4:]XQhJ寑$ҶSBXԻ54]YPSscͯs/Qq]ք]xsQ9_%✊D evKe&b Cᶠ71?|>}?c1 j>F 96g^[^6~ghcg1unsY.e8z?~{k"9i+׮i:\;s~.m4;mܯipmcꑤԉt宓06>O6#nٗXD]b?7=6s/6|EY,#0הl*\B]|L;UAAϿ~CSaV ^5bLd1`l>09Gjm[=bRe՛n^^Fl{uwu/)5y"P&~s/Q5DZhB^Qz2b}}YOa`E,+66tfmqYExCk^*euտÿ\fo.Y߫5CI> - j(6_&+us2yT l$vEm620Yϕ pLǞp!kp~~7Vo0Vw2ʿ JzQ ETyDrqr7|Y* -ڞ׬O]W5>GU 2D>Oƭ(mQ!H0׹qX>_[G-pО2b8z.Z,TYMVd3nIA,za'8MvT+znrIEmҽA=Y~}K6|O Vk=\! *unAFP!};]gN87NH fE.Pܠs?;w~4sYBܡhEO|=EإDfUWj(>"X~^G -wލĽc\ђ}4=͊,5z,zz;Ln1WEȞC? Qz 8o1ܛ"6~ MLNG)]&7}Ok._ļz#IJAv/70qׁHU &C8qY T BKѨuk!:t+.!忺b[ⷔ6#bB" -ߚ_qPD2N)vVGwϚi~q.NE{et:՛&2'ɭ}hyz;&7qۼFCૣݼƯѨAr)LwjxkϏwϵ^Y˒VnzWzG|ڎnZU߻``t{l% Ť9۝T>in(P|;4sqSl⎺KBči =-H.)x;;<=v;NS#w-n'qŻ)\ĭ4ZO9 X ?;c2Vqe5f^WI2=syr˽,0W޲m~w=̯pI(ٝi}E˸U7մCCnD?|gYmynm:Ǝc}~S.;oGuRC5y(GJYR'v9~̮(u<7\Ϧ_n zٯI:wS8[I|5y!w/w4SK4}>;h$~zW \MrCDŽ+bNGgV1#ֶc>l/Į2Td#-쫩}+ٰwUI|0s}63I>j'[ m; -hVrv_OVHRDi;d&M;?\7.PlH?}xŮ jx~mdږb[X!bfdz؝őߏb%*3?_NHrl?axlpM4bN^Ǻ4Duv+eL}U>z]g J:3c6aݑ+uBqBTjrZ(}nWhvjW1~ɑ-Pmnx9jɯѡc $ы6r6_:*f" *B2,5⌫E86yTdž:i WT;R_6eTM:6+P]s]gLALZl̷ڦoۡe4M*~|ߒ8}KyRKlR.T4āH#wmV֫C{y OLV.Zy:ȱFS7ꫤ cj<8=ǟoP;[C4Hܧ\*mXn .@3ΘLqVղ^qVZNѩ*MAZ%^eK%@AsWgȖKfF>W4]w۳ Ğ>-\*LmTY6 -b&ar&ʢ}F{ȕ`7 -F>S0g:!cmĥ"̯NKIg_ -endstream -endobj -56 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 55 0 R -/Resources 4 0 R -/Annots [ 57 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -57 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 108.503892 101.433071 89.753892 ] -/BS << -/W 0 ->> -/Dest (cb4-1) ->> -endobj -58 0 obj -<< -/Filter /FlateDecode -/Length 5358 ->> -stream -x]IƱׯrA@~=FˀH2Q$ 4=\勈d2\5|eW"R1VkWz,.J?79$ .r_˱~srZs_MTL1j/4e4i&U)GYj>mSY6EMlhHj&(4 >Zl#Yx YB6mm&Z9"oB>Im^|Fj"-r)Jm^lNjB:YhK֕66R[vD$eӶj|rNKm(tb< -J -Qh%h6❶R/?Rp»ୖig6^$(_BAxb\0ƨ([@&(QP(F'^QQ ڬi)HH x!x^\& / asŒm "aܒF%m 6R  %,p\씰tQu>X `Q -8#%, s)@GLrp%, .JX*alJZڤIڈ Etpz<k+aw- a E w!^N V{Y'a&Sik2Ÿ@+eRxIPؖැ2!d dUi ڀ@RpW%,]$, -Y $R9 aAmHĶp%, E.' /Z /H$,@FA-"^)JX$S)IX}@=Jmb[BH -HXZJ%8x钄`m$,U$,@(R"3 xA-a2]#aA٠&TAKXZHs$,HMPi)6bKX& 8OdL^6ތd ^IXuP&KXGdPoZ~f ;z%7G"$MY[`M$aA$a ԛ%f >6.2 a.Po"j{ ܘL⊁zVq@{f\#`e -* 4m0aZ}!"fmZ._?!^˧ߔRXC^2 @ZXl4yٍD0Fd<3Ly6Zł\}|qDsdJONlzsَ7b}|[p5~p@c釟._?/9?| @QhNu,}c}gZμe~g{Džt/ßWY,’7̷3<-ίnWY.}?CC۪FQWќ#I`("Ka1kt!y#^ÚCEe˹TMw6ۥG2sP׿~?wjyF*6i5G\G',me7k8+Wڞ=ǮIa04+ژݹ[}qW|XcynW';NNT}BvM(b)5xfw-~DŽ^37f:>y -9k.RMwRN֢\F,6rѤMzx̯.wd._fmO]~eaL?6tc6? >? ~Np!7V hd)"Fړ*5۬('RQܘVsBTJuf3`)79:+FlѬ:WjmlsK>ZXcZ>w|E)9-'Vqjȗcv! -#ŔbV׋oը! fyEۉύrԁDNzNT{CM,O -N'd ~**`΄0籇cBF]^+.+ӑ:~J}Pˊꮑ o~v?^>o~%ȝ+ڧaȋ) h}fvڀ2;H^~xCrgdQ)L5Ϭu/*펢b>>2RuXߥj޴):\Z@Fe*5\"/(LyyCWRhB/w>}zbey?9o?CpҊ~O8o Z{o.}wcW]T}lqٹ`a&𛳬?6qr{:mmfqc9M;lF y)@/oF#Yv /›z"QR*{+9;7M^"i[v $#N^񼏓=rSI} -Dq /)]!oi` -p`ZeFFG3dؐJҬ ~ qHph|Oi1L Fఴ!~KݬdH=}̒8<(ƻ54eDxMD<"ʹ1W>@YT9QXX+d49*RĤa+fp;\i;<FDɁbFҽߎqB4Xޓs}n.Yl${`'|98.ʑѕtӐuYι@Q E0#ʁ[: p! /=& -@'j\]xB9,ʓcȃE*6NJy@Jl71n:_ "Dod))%z 0ə -l'%Sve e“I0)2o,>܍Ҩ-_X͛5P΍r%j;V敮8^VMpU%)rB&4^5o}[;515 ScA<T)jT^|tYPo}itouץR'Zn2zk_F뾭R_>ڷC}d:eSV݋Hbƀ><}[Uv۾ b+q4sF⽺r7g?IJj6y?JyǨ~ -d}eQ^3#3gi|2ƴs7̟a_pnʭh3Ƃ? 1,Wme0[o ٯ Ә2F`Fީ`rB ЬSxp1 tW~AOKЇi!`CөYUۘ Y]g7cvڈ6aGV){-+ImאRn!̧?F6[QMnA񼏻bOi>ng].mJ6\j[~`VTɳJ ۛVdtΎ?*sk3 ;xÊlWWc2)E=< K!U)n6z}Gdbu, -,4f d$y!7~Id=L-i1z䪶?O43C.Z{kqO/|70CLX%^tx瓩`bk(&3tմp@)HW,|2LGһt-o#&=UBiz"Y %<|i }mԹG],5Eu*] LFgS5= E ~eAk|DLՐ˵@]~li*^Un[ʻz4/|zUun扝rQ;Vh_Mo$aFNKTEL Qy? 5U f#/4CC$`(x[1wBֻIlAD6c1H5XMFfiX9uedLeA|^3ovrh2cӸ#sm+Vlޤtj>f3P/\dRĽ]~)a:o9i cdA?\]=rt| |۰uA#ţUbshiN6Z糟u45u$.ÁlZm%Ŗ|nz.]}8\b|\zHS⊻Χ*a .Iq90wlA7igiT{ CQԕVb؍dƛ?ӯvr2Rۃ1Lu2,/[qW%r﹖t-.F;Ti@4]imXy -*IRl9E}҄GM_F-ќc:{\2 0nT=]mM{h{:#g󛞯¿xԫ)&Cn])`oJҰuF]u(rNGÿAOf0LU<,kan{^tJo^iKEiĿ%jhqtRp -endstream -endobj -59 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 58 0 R -/Resources 4 0 R -/Annots [ 60 0 R 61 0 R 62 0 R 63 0 R 64 0 R 65 0 R 66 0 R 67 0 R 68 0 R 69 0 R 70 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -60 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 691.173057 101.433071 672.423057 ] -/BS << -/W 0 ->> -/Dest (cb5-1) ->> -endobj -61 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 672.226036 99.933071 653.476036 ] -/BS << -/W 0 ->> -/Dest (cb5-2) ->> -endobj -62 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 653.279014 99.933071 634.529014 ] -/BS << -/W 0 ->> -/Dest (cb5-3) ->> -endobj -63 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 634.331993 99.933071 615.581993 ] -/BS << -/W 0 ->> -/Dest (cb5-4) ->> -endobj -64 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 615.384971 99.933071 596.634971 ] -/BS << -/W 0 ->> -/Dest (cb5-5) ->> -endobj -65 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 531.937950 101.433071 513.187950 ] -/BS << -/W 0 ->> -/Dest (cb6-1) ->> -endobj -66 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 512.990928 99.933071 494.240928 ] -/BS << -/W 0 ->> -/Dest (cb6-2) ->> -endobj -67 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 494.043907 99.933071 475.293907 ] -/BS << -/W 0 ->> -/Dest (cb6-3) ->> -endobj -68 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 456.149864 99.933071 437.399864 ] -/BS << -/W 0 ->> -/Dest (cb6-4) ->> -endobj -69 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 437.202842 99.933071 418.452842 ] -/BS << -/W 0 ->> -/Dest (cb6-5) ->> -endobj -70 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 399.308799 99.933071 380.558799 ] -/BS << -/W 0 ->> -/Dest (cb6-6) ->> -endobj -71 0 obj -<< -/Filter /FlateDecode -/Length 4732 ->> -stream -x\Y$m~_Q66,ذ-cm4!z詝`XA#`f+gWٙ$`2ȏGeZBΔRsNj59ZF.{,e]M%^?3!dk9]_.p)\WqWojM_?1%gV˺b49VrXƂ1{VTKX/ -@@م{V>;X՘ykUD+<MғΤR}Uy< L.:WMJ)G%V4^,YY(d )XY|Ae⡝ -duYlN`b-D*gK.4, ஏ-rw}^zIX5B@a3i*Ÿ@+JMD+8>Wивq)U "p*hXϢa0 z "pDjuZ "pyC԰` ߌ0]WhX%aH!9 "հ wޫ kc$%=*5,@^Vi$z Zx]ksհ w9ljX2|Ѱd^ÂTԜZdp5,Ry2iXPCཆC  #0!VsQ,5,R4,1V5^d+๬aAdLkX7.iX1saAaB)sItsNÂ! A /2հ$TrY4,( MPi)UdLhXb;jX&YB$ J\n J,z `\of ,4,6N5,gԛ4,_rY4,Dm ͬaA%<Ȃ*~ LB tx JԔ, @^m 7. -dx]dI\Df33Y,jz#b2^D ,k$i1QYv VtVmX/1Ä$[T 3K曬p Bv?k5,2lϗo|Zlq0@ .+per -te$_2u B"#E,C2侨*$]we y)Qn*SwE2}Q üb?S~uB%$ -3k[ ͇ |o qȍDЭ/~m?<_o~ưct^?~L?]?uy<89-{yXïO&# <{R>ٯO㺧;ܛ}mnu&x?1M"shL$#A}Nuȗˑn7ن Yul6J{I@v~_+pQtro9\. -ͩމ÷kO9NFՖAywTcDV=>*Oتm8 T)n?J>5OGҍǴsbVɡd>E,+O\D,)},~fʍْEX J4c9c6¢1#2i*of4JպY(~_pbۚU;{ZrH3+[gH$v%c+3RNG&0YEyG:S2:Q1 )[lyOW}-}x8Fҁ?oS_#3~#FK..M2 -sm[!"Kۻ[ne[M5czkL)<)å~4 gJѰ(݄$!B%Œ^[14|vk%O?QI73e33)]ƃ{??ח#A$׺1nޯK)n'"ry7Kݿ\: ?mY6A+~׿]~vny+?/BA/[a`O4{f CcziH?>hϗ0mQ_|q漑nKoSZ>-? 92 D/KNjُgNT5{n[u"&xهswfãxlˌfO">+}3}Z9DBّgeTuS* yGwW~D~=aqhn^1% Kak*;||ݣrV*Ip^Nسד7AJUn%zǏ#2:}r.VT(.cvQE,<rĵ)(Y@FlW>"p]^CIA l=LQV`8 iG:VЀ! qN3r8㼚<-juنxE?N?pv%MPyrz6#v$` _g33C|w5X)+֥&*{WcV<4f廟9&c?;SFwA m.I?-iLou-|OBr00@̮Cm |73}ՑgFםT8^{% G°8=Sro*wqwgtbqsbpXWTD]Ν dwL[IIm,G\PzOaQ}4{ -r(,~Ȅ`{a~Y*=vТlXc$/gn6v@Pw1O8Z;<wP7df~F}DB}";ϴBգԏM[x#-zEGhtof5SKjosFM8_qMdsdŢt*wMIE)?Q/HAWڑȋ>~TEJ'F.~\,˅2.s-rzvqz ( %i͏c?w2Uhol+DLwRLWiӐ_ \O_xObE4qnT]Z)T?,vH}Q c]ĉA B:qBciaN85?NquSH:I9uh~L=xv]_~$|ɯ ɜγE؍#.'.%fet\Xa0=I bI.vˢ2T4~Kݠ"N*#O4)~u]M7'y$IOuHӀ -u3ᎎU3Sc;P:c'iu63R-r#/9thf ssEN;_$9ww+l~o-ё̦_&  F_yxD'*r2-.0C\Ȥ[8dØ_xsN[wd;N8F= _dW8aq~W.h<.`#DP7O.A3gv{ -vpY/|K⊇Oz1rQ\ l'&d'y"˰x¬\z]!H ֝<_^?ܻixS'Oꋤc<e_Θ|1wih,X. -jY(7Am:ń ~myȔvER9ŢEj:SJTX^wD-Eiyݝ]#g.YZ'0h{~m6h Vfj״x7K|G}2V5+CK[R}Q"q}P6¯F=g7ӪUo} -P: cn_cמ&m͝yTo lހZ'NsTN -endstream -endobj -72 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 71 0 R -/Resources 4 0 R -/Annots [ 73 0 R 74 0 R 75 0 R 76 0 R 77 0 R 78 0 R 79 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -73 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 797.673057 101.433071 778.923057 ] -/BS << -/W 0 ->> -/Dest (cb7-1) ->> -endobj -74 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 778.726036 99.933071 759.976036 ] -/BS << -/W 0 ->> -/Dest (cb7-2) ->> -endobj -75 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 759.779014 99.933071 741.029014 ] -/BS << -/W 0 ->> -/Dest (cb7-3) ->> -endobj -76 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 740.831993 99.933071 722.081993 ] -/BS << -/W 0 ->> -/Dest (cb7-4) ->> -endobj -77 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 721.884971 99.933071 703.134971 ] -/BS << -/W 0 ->> -/Dest (cb7-5) ->> -endobj -78 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 702.937950 99.933071 684.187950 ] -/BS << -/W 0 ->> -/Dest (cb7-6) ->> -endobj -79 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 155.548661 618.187950 248.939042 603.187950 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (https://kubernetes.io/docs/tasks/debug-application-cluster/audit/) ->> ->> -endobj -80 0 obj -<< -/Filter /FlateDecode -/Length 4663 ->> -stream -x\I _ܮF$ r%(C~>V[F#[&kaȏdb/]r.)d R8[Ci ӒJp)Now)??>R;f_RNU2+\ -+K,EcAё 4 S*%K b²rXgʃ ;g]b.MNyD6XWc K(jY%2IE7*KA;Ee*h+~ %)y΄%dƳv MQؤ,ф Ki<Y5p"⭎o5^,%Ry!ŤAr4,(YRY4oI7N/BWHÂ#כY7ѫGͤwC2i<.2Өa.Po"j{ \qfzbzd`VI=30_C2GaLkcE>FLXOU9$̜xnAG1+_~:}O￪'e{\XexLfљcIOUB)}XTXHbrحȐeHfh3/JQ}>G|Y6Yh 3N|?/ߟ;>G00 ~ v{˯u~fv\cpH{!2B2ig\ڽ%67f_?֑ZO7~77C7dyV6v[([Ē=2iX7^/v^W!\'5h[l\RB'ue*ja˰M49_y~E{@G._6jYJC܍^>cr|5RJz3'EםN -v7 U!Z8필kj/]]]6Ȏwݔ]{{!en֕8IB̿ ^HO&#=PicU& ET~u=@,<$!=k_ -*5${~/ ePJwKG(k͝b+n 8" uTG !.߸{1z76s;3~~&r3J 0S:PWf< EĽ-@^n0G~c)h5#7Hdo<>g+w63-~b ٜRE!e{Es;6}z/zӰø$X㲼2שE:g`z߷ep 4湨:.{wj.Ҏ -d^,di F)|ȚeN=[v{K b)]pKX"4E?>iCJ^\7JyiݕLmuxU šC믾u_M6wcٰN~gWC;w!epfVUmL>5>K4Ǵx+G\z#"YMfsyFHkP=t"5Ycc|vXyhg.@xK=۠9S@>?QY–<]߼!|ڮ;"F;9eqF)K>rhF^j+>oBPuU㸴> yy5_֟G3n(~M [~1-b쏯_@J5I%+B[Kz^y gVDBn 1\Vek`dž[kcr>_,E +'ƦnL\b==38}h/uK)[N׻Mlc㏯m!3T4Ru} y$+=H]mI[3fsW-xA[_702H 1El<ٮr[dWz|'z olǺYP)A$?s*fqcJ]2(G-_Lu5~.pлkndC#EubɼzFOd~l^! -8$v8;%[o1FL7Ɏ'*z˱!4I!]N -kӇ&l]s1^3$Jo.']-JU]Ke:?=zvol 1%akݸr -4$;3ݜL`I0T[:ɴ{9|a8 ^ddC':.^3- YF24X~̟ -6H$<ۆn #sYv4n&v \I S2S3Hd^73`/+L~/K \3$Ő3KNtąb2%ۈ)'gInąH#O0+ -)r`rҲGD:}P$u,tq{9bXN =?3ͅQAͳ[kiI{p1b2֭8ZJ#ԟܕ w%=lɏ(HsNsufdVhQT-}=ڞ2h -gfjfphI)~AkS 8&|Īɑ_ JV,9t{ș yo"> -endobj -82 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 101.433071 125.127057 101.433071 106.377057 ] -/BS << -/W 0 ->> -/Dest (cb9-1) ->> -endobj -83 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 106.180036 99.933071 87.430036 ] -/BS << -/W 0 ->> -/Dest (cb9-2) ->> -endobj -84 0 obj -<< -/Filter /FlateDecode -/Length 4874 ->> -stream -x]ߏ8n~X(Q> `,!䡷oAoST0f$Y-}9b~m~sis:Hq\:LD4%R$}MP\Z EgB03=E@0y7Zl)4i>gH$Q'ȉomM_.#nӗ˧?X+"se]]/yO@n`K,-/OӲ}3b1<%~Kil{h1[%".D&) KeQdKZ٫JiEhj_C-;m we9v(ro&s+{UJ]{ώt'@!\iFȖ}FHF#}J2ɠ; Pc"1!=LZV{PNd)ԠyZvd24\DFS^.y>BA4{D-{A_XQTa $D\$EzrJEvrek`N 7Η̗\vǘd d'B&7Α;Me@c?)-x2irA!; O>}efU<.@zםz,˷jm?UNǦ>dcB($۶:z*bjE"O[ Tc>2SY'tg<ϲNe]sZ܅dӅl>M4,߆q8wuܕiXcVwP̴:+Ϲlb/ykX@h*xP4NVvX{Y'y&Y9pZ{ҒsvS͊􃁝ɛkY @C ʜǡ`sjQQVa1JN߻j#.>kё7lyelI#9 %f N<ح4crL1gMVEԁpHgL<#۩Bv#euy5*:m}f/js罘F o9YŐ`Y"X2S޸$@#o1s{9U@I(95md{e4mzn/FOZGc>4:]^s4p8:&rFG;Mߍ-!k2"!/ g[EѧEdV=i ̷wy9,4vc21^VeAV$6˚~Udw,;J hPB6"}^~:YM>EK\l<$r3Fλ_8>\lkDW!'AG;21YۉhgۃdFҫͮEIRb=p֡)dD$1pP˱"H(SѤKw(/˿;/G9g壍.y5y鹛ն[FV^/°t~Wx~Lذ@/9et=|P4.R #%ex3!t\wlUk)T 46>(s9 j?!KƉy }*+J21z ƒnq{iiB~i"Kxa:XC9dً,}~意U{{Ola?~ʎnJHNv ʜf08מּX}g3moqņN6c wXNSê']iu6# 1XdYӎ$JsûϷg(ܚM)ɤI_^oZnjҗ{t*{/#G7ʂr/{{j;]>oL%Nggt~SVwk]ф4,˹69MDk)~m^- tI{_'crN)EX. AmKWWuI,rGӈ|brW⿷+DHFڒw UlXuqs!YޯaKfU˺4T:ײ.u|D|~M}Sr|.JRQC- N -jİT1WGVr -R+gR[~Vevu[+$_5%9M~6׋lݐ.!)Ì6T뉾e\ -]LRQyͥ jF^6RO uXk{iCE)5ۋU ҭԮ:z*U=K25kd> +{Jv394W~[g=CE=zgrl֓S8!MVo: l&z,ڪuY1Lam"Iǹi#ois>8s'΃>b̟_Pٽ6p [~$oɃdƜJlݦ#:`&Sˆ mwk $5anÎ:]˄U+@km3طK_N^㙫VyyHvUJC::A\ⲻa5[)ߤ5Ͻ)d3aҦ E_1SӲGQ~W9 Sۃ Ne\^1Oo;Pw}Ϸ gshG;jBSM@4[iTuw,gR)fUZ#*qSV#^| Bi~:;ldVhnTKJޛ{ sdjg)!H߹ɬfRgՠ<K)yo9F`˗$4ǻe{lg7G'ð6|gUUORvGz_(:3ͬawiIRE@/Ao6Jii'GS" -endstream -endobj -85 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 84 0 R -/Resources 4 0 R -/Annots [ 86 0 R 87 0 R 88 0 R 89 0 R 90 0 R 91 0 R 92 0 R 93 0 R 94 0 R 95 0 R 96 0 R 97 0 R 98 0 R 99 0 R 100 0 R 101 0 R 102 0 R 103 0 R 104 0 R 105 0 R 106 0 R 107 0 R 108 0 R 109 0 R 110 0 R 111 0 R 112 0 R 113 0 R 114 0 R 115 0 R 116 0 R 117 0 R 118 0 R 119 0 R 120 0 R 121 0 R 122 0 R 123 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -86 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-3) ->> -endobj -87 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-4) ->> -endobj -88 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-5) ->> -endobj -89 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-6) ->> -endobj -90 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-7) ->> -endobj -91 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-8) ->> -endobj -92 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-9) ->> -endobj -93 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-10) ->> -endobj -94 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-11) ->> -endobj -95 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-12) ->> -endobj -96 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-13) ->> -endobj -97 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-14) ->> -endobj -98 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-15) ->> -endobj -99 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-16) ->> -endobj -100 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-17) ->> -endobj -101 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-18) ->> -endobj -102 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-19) ->> -endobj -103 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-20) ->> -endobj -104 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-21) ->> -endobj -105 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-22) ->> -endobj -106 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-23) ->> -endobj -107 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-24) ->> -endobj -108 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-25) ->> -endobj -109 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-26) ->> -endobj -110 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-27) ->> -endobj -111 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-28) ->> -endobj -112 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-29) ->> -endobj -113 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-30) ->> -endobj -114 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-31) ->> -endobj -115 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-32) ->> -endobj -116 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-33) ->> -endobj -117 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-34) ->> -endobj -118 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-35) ->> -endobj -119 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-36) ->> -endobj -120 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-37) ->> -endobj -121 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-38) ->> -endobj -122 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-39) ->> -endobj -123 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-40) ->> -endobj -124 0 obj -<< -/Filter /FlateDecode -/Length 4375 ->> -stream -x][ ~_1J" Ph^APAN9 Mɲ㝙1)ڴ(~"iY_*\)5'>p]`b,9; 59.W9_:?2])9\.9{1X,`$-jd|Pk58b - ΁.YjbAP%Gޛ<() .ӓŋRc5y#r)s`K)Ix ]`H`0ltDAX2Y ]"z]0Ƀ.>`*9U|8)DcL< -FJE蒼T]|x]8!K15w`ĘABɂxS\0 F@ r\X(Ku3Y08N5[8@>䡋ptaxɃ.T ,, .2Fe_eRIlar1%`Ѕg K%.oaw i @GG ܥ೅ ܅E `Uq,,Xqoawclawc` ܍[fnn-,`n,,@qoF]@tZXHd.",@b3|hBBF~^v!jaw1Q| 3j@0S[9 -,罅5䛑-,_jY,,o"3R|3[XPB]4UoI7N/AX‚7ћ%f6]@&Ed,,MDVn̢g1++[͒bf|5G2PeIf*eE<p>%1g7Ys3T{~6Uw'NXH07Mc:ȓPU"YX<TILŘnKLwu)e+> xC\9TT}34Ņ4HhE5*v!z^4|Szc6gtn?~?~~ths/ڊ2r3/d<:g~^=~DС8gbam"wauo5U m[$hj4 ?=}ec`XD<5I]r( &*"?lpQ6H]Jq ӓMUtX$7Tx2J=chVO: g{b²op~L^ |ʉ0n;&$lُ)DoZzO+3t<`1XOt -]S[f&{j>w}]_U]:xRE'nٍu;wwz /}"9n>־33½Sn}Qf?F!]"2?]!Dg]T:;-((aC-tQﷆ9JX~l߼|eb߼zktl(XUݒuC>ʲ6g@N~Pw 9b.>5eu h}XxġCB~Cz_@]JOzr8ጶ-_&%֘%Fom2`EUg-.[?ɹch[ ճu< ~1gɺ{7 p] V=L,LKz/vFݸeI\2ͳbN -??80n;f}:u[1vоKNIFT3E;HWUSprꖨѬ>sZb]q;%COmaѰ)tst?ҴU0i -mk-V@Yap"9m coA򺁤>L28뇃oz:bO;K׃AOHV+ <>nIc''iQyib.kG:~O6Lᒬw=uw|* '|Y&Yӓ(D?\n&.mk9]`6o_,&UdmjhPv d^ NX=t`5D,m qoW[;r0۝&R*hm=?2u* Ggj>.I-l\{7rЕ׃dX Hy;y\ZW5M'NU>CJGE7;yI#=ua]J+oW{-C \z -Rđ6t4%8Oul"UMAz`#fxFbhƃƋօ>wv?(C{~cJgSi:L>дKs޹h=Ashq2xQnED4hb[;.f/SǞ*eJhm3^@2<ߝ[X4Jw*-.k8ϊ92\ ̪`jSU#ykXL2Eۏ/)CX7l\2ǻeޮ{\V7ZcVz1O'[L0n}`ufUw\YSE?=Ao/}0> -endobj -126 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-41) ->> -endobj -127 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-42) ->> -endobj -128 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-43) ->> -endobj -129 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-44) ->> -endobj -130 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-45) ->> -endobj -131 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-46) ->> -endobj -132 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-47) ->> -endobj -133 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-48) ->> -endobj -134 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-49) ->> -endobj -135 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-50) ->> -endobj -136 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-51) ->> -endobj -137 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-52) ->> -endobj -138 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-53) ->> -endobj -139 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-54) ->> -endobj -140 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-55) ->> -endobj -141 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-56) ->> -endobj -142 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-57) ->> -endobj -143 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-58) ->> -endobj -144 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-59) ->> -endobj -145 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-60) ->> -endobj -146 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-61) ->> -endobj -147 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-62) ->> -endobj -148 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-63) ->> -endobj -149 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-64) ->> -endobj -150 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-65) ->> -endobj -151 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-66) ->> -endobj -152 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-67) ->> -endobj -153 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-68) ->> -endobj -154 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-69) ->> -endobj -155 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-70) ->> -endobj -156 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-71) ->> -endobj -157 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-72) ->> -endobj -158 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-73) ->> -endobj -159 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-74) ->> -endobj -160 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-75) ->> -endobj -161 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-76) ->> -endobj -162 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-77) ->> -endobj -163 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-78) ->> -endobj -164 0 obj -<< -/Filter /FlateDecode -/Length 4434 ->> -stream -x]ߏ ~b DDP!h6EZ=(}lIǒe-\{3&%O$%k 2;sIϏ?~>Yſbbr2'!P26}_~u纎;{SJ.$,&rJ6(uB0)VtXƂ!kV\rX -+C U O5p%$,pZA,3y炉31_T^%LLxCx YBNx)'! E*H%;EeȂѕUd:WȄU^支y2xΙI*%Ť%ų>YCH_Xdxi@@, Uy -kX@D3iX@@[hѰlӰl]԰jX@@\ʑ5, @.RѰ԰0au)Davs԰jX]"TyX!IIŒЪ8`հ>[ְ>a -PyIGfnkX]>jXb?Va{`=_M0ALpevf"$!",I7S1rn_ZdH,2;83ӓq_D -:o%+>y0cgSe5BNGU?`D/vىѵޞ?t??}~|kF~7~Xw -h<'S8V宎|CL7 ''毾p(qʹ|aϗO:]O?,'g:X0o^ik֮U13* -qن_U<A"I[Gu0Ƽ^UjkZUبZÎlX`_ Vn`(I">LEڒ轑h'@9F^6ޛt&-i9cBEɚT/[^2]sɞh gYv cu3BxzKۛhЌȮkqOwqT+!{ޱWz?VE=1^k, 88MÞXè5XL7v]斧dkZiYlh~s-bΈδ6XQ#bA^[`tj$z2{eczݜϷT0V8*lk^,l'nOrPe>O9LG+{WREuZ;LdrL.߲:Q N+fcw~죨p{=nrt4n8 -pxRܳQßnzL^Ju: A%vw^t.U6 &Z_n@ -Էo{n.f5V0 -{$ܭ -$(#oڴ ع1zu,}ݯ~۱ηm -sv9AwrIq^NX(;_2(4J.ԉ9Jsfٵ(o5mt$+ -UΫOQ 9MLj&peHp4xmb\La*^`㨔dcLe7 -|)-nq!1cNQֹt:Qirwkރbqu,Oٮ\ms}lovc3s`զ@r讋:nN,t8?Ԥf=>uzFmNŐsFwF, Rrbt䷿oץ# ?]|./$i)\Nb|rS?e\ -b&s9phϕL/u/Ͳ|jOq:5M'8m%AoF,8!0raM;5n( Jϓ~:9X> -endobj -166 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-79) ->> -endobj -167 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-80) ->> -endobj -168 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-81) ->> -endobj -169 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-82) ->> -endobj -170 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-83) ->> -endobj -171 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-84) ->> -endobj -172 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-85) ->> -endobj -173 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-86) ->> -endobj -174 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-87) ->> -endobj -175 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-88) ->> -endobj -176 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-89) ->> -endobj -177 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-90) ->> -endobj -178 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-91) ->> -endobj -179 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-92) ->> -endobj -180 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-93) ->> -endobj -181 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-94) ->> -endobj -182 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-95) ->> -endobj -183 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-96) ->> -endobj -184 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-97) ->> -endobj -185 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-98) ->> -endobj -186 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-99) ->> -endobj -187 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-100) ->> -endobj -188 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-101) ->> -endobj -189 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-102) ->> -endobj -190 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-103) ->> -endobj -191 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-104) ->> -endobj -192 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-105) ->> -endobj -193 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-106) ->> -endobj -194 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-107) ->> -endobj -195 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-108) ->> -endobj -196 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-109) ->> -endobj -197 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-110) ->> -endobj -198 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-111) ->> -endobj -199 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-112) ->> -endobj -200 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-113) ->> -endobj -201 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-114) ->> -endobj -202 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-115) ->> -endobj -203 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-116) ->> -endobj -204 0 obj -<< -/Filter /FlateDecode -/Length 4341 ->> -stream -x]Q$m~_NDJF$.! A`.9XR`H%IJ?'H-/?~9yWǿ%RYg%PqX6cu>]9te1"d*X>JɕS6X98b b‘1JXc%ڳ*Ĉ%łb!zo ghBr-^ .KB!W]9cȒ/AŃ,LR,^,ɛ<+%btY|Ur -ɫy)E\"oBp I&%b"d>UYh0~,p"Q15w`dɃ,P1C_ da@,ql@r,, -DK! bMs-`yȒ8[H@0\NnMIy'ri޴.ﲾ0:.}ݜ]FW6W˭QQ"Sٴlʏ ovQ,âGdè.o=q-}dz4N];6@ۧ22c}2+qYlL9DgJ|2HeO2Γ}`RSJw^Y6/K[0MxreeqT>D[7`ܪS"5tk8b4n&Qv;0jK^:1N=gUud(GW_ 2GSSC彙{C3Jyߚs%f9FA_HK8H}}W}Y|݃MRշXc ~>;sd6Vv$)/ ksWURi!3X0kvlqTJ:9{nfxm\n 􌰾+XPp=wqTtI_ GE䡩>Z'rE>bxk>Q(Уvjm%?~CU!.͟M3&FUj2yUm.7J uf08jХK?? -GGQ058*H -EjRA `[ժʺp@__=28]lu7oo,kˡce^~ -laT+K;=ZoB,瘢,:\ ?:2Mݦx[pĿtnRC68M -㏝B-)hEe9 c78fi'Guky<4`e#H$H9s}usRbq35TrYEᢻ(Es!']K~pJM *CH.Bhnq<)dBy+:z0yQJgлǼLzlXc'M9EJVScjJL3>QβE(,|ĢG/'2y}OnϷ kvՇO`=L`݉n/ "IfXd48V|tW`]TC7QeO﫲!]+uL> Z{H^??_ 1rv "-/mѽpzmkKߋ%]eS/l |^r*姥u)ġ yX)\IA򺛢N/*Y) G.ۜKFדnsa;Nxۆ*n[RrSj_cjwS"v{ADd{•[Qdq=!mD?\n%m_k9]q 6Ao_N,m&U7(mj} TZvpדAz9|;5t Q!qoW[;r2]ϖJo%kF~e5u>m+烏xj_oY5t|`#teԎzJhVHἝ,~Z \t,Sy/IFwzN;5Z.8^A^A#vClSqK:Y!OʑJNݔ_oȫjb9 yWr:Kx] 7xKVӗv}v*@a%0vtҥ?dV}9鴄H)jV)&c6}ǣh;ސH[$Ypo61+965kq<yW`o-CGй#1c8c7he3=ZݬrHpT8oh 8ҦkHIq8\݈9^ϣ*H5 i5̎n.&Hi<Oahz(C{~cJgSi9̷=вEsuh=Ikj7TY]h7mhK)_aYXQ*=XG:Z郘F][=ox=[ќzw~msI1hyݩF_oݢy ^kfni]߹ X2d'CH˟30u2Lsf j+ˍ[zninVg+wEKE5:'{ieL,?w -r -endstream -endobj -205 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 204 0 R -/Resources 4 0 R -/Annots [ 206 0 R 207 0 R 208 0 R 209 0 R 210 0 R 211 0 R 212 0 R 213 0 R 214 0 R 215 0 R 216 0 R 217 0 R 218 0 R 219 0 R 220 0 R 221 0 R 222 0 R 223 0 R 224 0 R 225 0 R 226 0 R 227 0 R 228 0 R 229 0 R 230 0 R 231 0 R 232 0 R 233 0 R 234 0 R 235 0 R 236 0 R 237 0 R 238 0 R 239 0 R 240 0 R 241 0 R 242 0 R 243 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -206 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-117) ->> -endobj -207 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-118) ->> -endobj -208 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-119) ->> -endobj -209 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-120) ->> -endobj -210 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-121) ->> -endobj -211 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-122) ->> -endobj -212 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-123) ->> -endobj -213 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-124) ->> -endobj -214 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-125) ->> -endobj -215 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-126) ->> -endobj -216 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-127) ->> -endobj -217 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 590.755821 99.933071 572.005821 ] -/BS << -/W 0 ->> -/Dest (cb9-128) ->> -endobj -218 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 571.808799 99.933071 553.058799 ] -/BS << -/W 0 ->> -/Dest (cb9-129) ->> -endobj -219 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 552.861778 99.933071 534.111778 ] -/BS << -/W 0 ->> -/Dest (cb9-130) ->> -endobj -220 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 533.914756 99.933071 515.164756 ] -/BS << -/W 0 ->> -/Dest (cb9-131) ->> -endobj -221 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 514.967735 99.933071 496.217735 ] -/BS << -/W 0 ->> -/Dest (cb9-132) ->> -endobj -222 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 496.020714 99.933071 477.270714 ] -/BS << -/W 0 ->> -/Dest (cb9-133) ->> -endobj -223 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 477.073692 99.933071 458.323692 ] -/BS << -/W 0 ->> -/Dest (cb9-134) ->> -endobj -224 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 458.126671 99.933071 439.376671 ] -/BS << -/W 0 ->> -/Dest (cb9-135) ->> -endobj -225 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 439.179649 99.933071 420.429649 ] -/BS << -/W 0 ->> -/Dest (cb9-136) ->> -endobj -226 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 420.232628 99.933071 401.482628 ] -/BS << -/W 0 ->> -/Dest (cb9-137) ->> -endobj -227 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 401.285606 99.933071 382.535606 ] -/BS << -/W 0 ->> -/Dest (cb9-138) ->> -endobj -228 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 382.338585 99.933071 363.588585 ] -/BS << -/W 0 ->> -/Dest (cb9-139) ->> -endobj -229 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 363.391563 99.933071 344.641563 ] -/BS << -/W 0 ->> -/Dest (cb9-140) ->> -endobj -230 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 344.444542 99.933071 325.694542 ] -/BS << -/W 0 ->> -/Dest (cb9-141) ->> -endobj -231 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 325.497520 99.933071 306.747520 ] -/BS << -/W 0 ->> -/Dest (cb9-142) ->> -endobj -232 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 306.550499 99.933071 287.800499 ] -/BS << -/W 0 ->> -/Dest (cb9-143) ->> -endobj -233 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 287.603477 99.933071 268.853477 ] -/BS << -/W 0 ->> -/Dest (cb9-144) ->> -endobj -234 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 268.656456 99.933071 249.906456 ] -/BS << -/W 0 ->> -/Dest (cb9-145) ->> -endobj -235 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 249.709434 99.933071 230.959434 ] -/BS << -/W 0 ->> -/Dest (cb9-146) ->> -endobj -236 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 230.762413 99.933071 212.012413 ] -/BS << -/W 0 ->> -/Dest (cb9-147) ->> -endobj -237 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 211.815391 99.933071 193.065391 ] -/BS << -/W 0 ->> -/Dest (cb9-148) ->> -endobj -238 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 192.868370 99.933071 174.118370 ] -/BS << -/W 0 ->> -/Dest (cb9-149) ->> -endobj -239 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 173.921348 99.933071 155.171348 ] -/BS << -/W 0 ->> -/Dest (cb9-150) ->> -endobj -240 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 154.974327 99.933071 136.224327 ] -/BS << -/W 0 ->> -/Dest (cb9-151) ->> -endobj -241 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 136.027305 99.933071 117.277305 ] -/BS << -/W 0 ->> -/Dest (cb9-152) ->> -endobj -242 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 117.080284 99.933071 98.330284 ] -/BS << -/W 0 ->> -/Dest (cb9-153) ->> -endobj -243 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 98.133262 99.933071 79.383262 ] -/BS << -/W 0 ->> -/Dest (cb9-154) ->> -endobj -244 0 obj -<< -/Filter /FlateDecode -/Length 3716 ->> -stream -x\ۊ$}gR70 2`è+af >QUyZȸȪ&|_J9Ӊ\KϞ$k*^ ]1t~CFBΧT-,]lTlaA>x5XXS[<,,] H,,ȂL +U‚1hJ\,[+z N% x^,, T,,VJ@fnJp=d]dEX^sfD|N=`=ӻO,I !* rp!EB!}T\؊s"Cb#YV&E|@B$ | I1 N^]/ޜF mn.PnϾ_kLn|/YQu Oot)joύ]HB4:Kۯn/c2\dc}^ܔ>`yp$ps|K3~fp.EUD iH33>e -1ChU/NGQXֿHC;AUjo6HTK$MڛEk 3 gB(Y2r[f1j ?qlyt3G7EŽ^HDViSd@j70Jer:,q׈ТzEYϫq.Eebh&9jSw67S/QX^WJ!0˝}^YP'5"IS"Z"!*UP2}}^Ȗۑt0E~ٛr7hk}[,DbkχlƓ,s#U -5:U[S*|ۭ{ncm5>Enu9eon9Sn@ _Y/=Q _Wcx}֢xfO$t}ծZwg+TwānCRx -\LT`k3] 9p1z#`c,{SYlVUU|% -.Wo(!c}0vas~Pz.4M9àr^SCfںlכ\m׵m4O+PBNdkh/# [(|᳕ǍV6*"XqW۠CXU[{w=o+MSv=e[α[32yC6isϟ'qɼo|wa[ut&Y6bֱmk[MCQjkqtuڶ6ӺK60-G_KCwcVw\5,cMVmjmzY>4ƌ]|De15{QSttEop TߟRTgazճOfquMksf -O>j&Skx? [^bf.͗:bFod}ߟW›96&M0Ŕfi]!>%?&7[C\ -YP\Մ&s=Ă}X KW&锖d$|W)INY)Xh* (?V;)#J +~'MRKqi!.Ay ӮF ή[rt}5Ķ[7}C5Ɇub_uFw0*uQbj28ptIL1^inVkmb}V"w/'LGI'PM:'jֲD d?6?YM[9v3Hn-vKުi~2\KWALK֗ʦ!n_h2M"^NQz$)fuXALiN.4ePsiBh6>}P;Ug⥻>A8$WLOuҀ-q.owF,M2zܧO6`A0[vtWd֎{9xZ1Pbo7GO/I_}b6p1/exliH\iӱ+aꈋyP\N!NLuyz_fS5]Li^fmY)0INC_lM"@;q)M2/CC},b{3Bc}tmkIvhh}dJ[eR9Š8k:VJUU[x=[ٝX=,-ͽ;UFKne?wm2dFfJ[jA!cjYrx́)@%%`kay~2}?>hL0f^:-#6c[%sI/SOGˬ5֤Ky̳?1o -endstream -endobj -245 0 obj -<< -/Type /Page -/Parent 1 0 R -/MediaBox [ 0 0 595.275591 841.889764 ] -/Contents 244 0 R -/Resources 4 0 R -/Annots [ 246 0 R 247 0 R 248 0 R 249 0 R 250 0 R 251 0 R 252 0 R 253 0 R 254 0 R 255 0 R 256 0 R 257 0 R ] -/TrimBox [ 0 0 595.275591 841.889764 ] -/BleedBox [ 0 0 595.275591 841.889764 ] ->> -endobj -246 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 799.173057 99.933071 780.423057 ] -/BS << -/W 0 ->> -/Dest (cb9-155) ->> -endobj -247 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 780.226036 99.933071 761.476036 ] -/BS << -/W 0 ->> -/Dest (cb9-156) ->> -endobj -248 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 761.279014 99.933071 742.529014 ] -/BS << -/W 0 ->> -/Dest (cb9-157) ->> -endobj -249 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 742.331993 99.933071 723.581993 ] -/BS << -/W 0 ->> -/Dest (cb9-158) ->> -endobj -250 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 723.384971 99.933071 704.634971 ] -/BS << -/W 0 ->> -/Dest (cb9-159) ->> -endobj -251 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 704.437950 99.933071 685.687950 ] -/BS << -/W 0 ->> -/Dest (cb9-160) ->> -endobj -252 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 685.490928 99.933071 666.740928 ] -/BS << -/W 0 ->> -/Dest (cb9-161) ->> -endobj -253 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 666.543907 99.933071 647.793907 ] -/BS << -/W 0 ->> -/Dest (cb9-162) ->> -endobj -254 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 647.596885 99.933071 628.846885 ] -/BS << -/W 0 ->> -/Dest (cb9-163) ->> -endobj -255 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 628.649864 99.933071 609.899864 ] -/BS << -/W 0 ->> -/Dest (cb9-164) ->> -endobj -256 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 99.933071 609.702842 99.933071 590.952842 ] -/BS << -/W 0 ->> -/Dest (cb9-165) ->> -endobj -257 0 obj -<< -/Type /Annot -/Subtype /Link -/Rect [ 468.550614 515.652842 489.260575 500.652842 ] -/BS << -/W 0 ->> -/A << -/Type /Action -/S /URI -/URI (file:///doc_tools/%7B%7B%3Cbaseurl%3E%7D%7D/rancher/v2.6/en/security/hardening-guides/rke2-1.6-benchmark-2.6/) ->> ->> -endobj -258 0 obj -<< -/Title (RKE2 Hardening Guide with CIS v1.6 Benchmark) -/Dest [ 6 0 R /XYZ 85.009843 502.818898 0 ] -/Count 18 -/First 259 0 R -/Last 276 0 R -/Parent 277 0 R ->> -endobj -259 0 obj -<< -/Title (Overview) -/Dest [ 26 0 R /XYZ 84.259843 283.881496 0 ] -/Count 0 -/Parent 258 0 R -/Next 260 0 R ->> -endobj -260 0 obj -<< -/Title (Host-level requirements) -/Dest [ 39 0 R /XYZ 84.259843 369.381496 0 ] -/Count 2 -/Prev 259 0 R -/First 261 0 R -/Last 262 0 R -/Parent 258 0 R -/Next 263 0 R ->> -endobj -261 0 obj -<< -/Title (Ensure protect-kernel-defaults is set) -/Dest [ 39 0 R /XYZ 84.259843 289.233496 0 ] -/Count 0 -/Parent 260 0 R -/Next 262 0 R ->> -endobj -262 0 obj -<< -/Title (Ensure etcd is configured properly) -/Dest [ 41 0 R /XYZ 84.259843 480.020658 0 ] -/Count 0 -/Prev 261 0 R -/Parent 260 0 R ->> -endobj -263 0 obj -<< -/Title (Setting up hosts) -/Dest [ 41 0 R /XYZ 84.259843 237.872658 0 ] -/Count 2 -/Prev 260 0 R -/First 264 0 R -/Last 265 0 R -/Parent 258 0 R -/Next 266 0 R ->> -endobj -264 0 obj -<< -/Title (Set kernel parameters) -/Dest [ 49 0 R /XYZ 84.259843 799.370079 0 ] -/Count 0 -/Parent 263 0 R -/Next 265 0 R ->> -endobj -265 0 obj -<< -/Title (Create the etcd user) -/Dest [ 49 0 R /XYZ 84.259843 500.585993 0 ] -/Count 0 -/Prev 264 0 R -/Parent 263 0 R ->> -endobj -266 0 obj -<< -/Title (Kubernetes runtime requirements) -/Dest [ 49 0 R /XYZ 84.259843 352.740971 0 ] -/Count 3 -/Prev 263 0 R -/First 267 0 R -/Last 269 0 R -/Parent 258 0 R -/Next 270 0 R ->> -endobj -267 0 obj -<< -/Title (PodSecurityPolicies) -/Dest [ 49 0 R /XYZ 84.259843 257.592971 0 ] -/Count 0 -/Parent 266 0 R -/Next 268 0 R ->> -endobj -268 0 obj -<< -/Title (NetworkPolicies) -/Dest [ 56 0 R /XYZ 84.259843 663.033496 0 ] -/Count 0 -/Prev 267 0 R -/Parent 266 0 R -/Next 269 0 R ->> -endobj -269 0 obj -<< -/Title (Configure default service account) -/Dest [ 56 0 R /XYZ 84.259843 388.198913 0 ] -/Count 0 -/Prev 268 0 R -/Parent 266 0 R ->> -endobj -270 0 obj -<< -/Title (API Server audit configuration) -/Dest [ 59 0 R /XYZ 84.259843 315.158799 0 ] -/Count 0 -/Prev 266 0 R -/Parent 258 0 R -/Next 271 0 R ->> -endobj -271 0 obj -<< -/Title (Known issues) -/Dest [ 72 0 R /XYZ 84.259843 463.537950 0 ] -/Count 3 -/Prev 270 0 R -/First 272 0 R -/Last 274 0 R -/Parent 258 0 R -/Next 275 0 R ->> -endobj -272 0 obj -<< -/Title (Control 1.1.12) -/Dest [ 72 0 R /XYZ 84.259843 368.389950 0 ] -/Count 0 -/Parent 271 0 R -/Next 273 0 R ->> -endobj -273 0 obj -<< -/Title (Control 5.1.5) -/Dest [ 72 0 R /XYZ 84.259843 164.143950 0 ] -/Count 0 -/Prev 272 0 R -/Parent 271 0 R -/Next 274 0 R ->> -endobj -274 0 obj -<< -/Title (Control 5.3.2) -/Dest [ 81 0 R /XYZ 84.259843 520.622079 0 ] -/Count 0 -/Prev 273 0 R -/Parent 271 0 R ->> -endobj -275 0 obj -<< -/Title (Reference Hardened RKE2 Template Configuration) -/Dest [ 81 0 R /XYZ 84.259843 228.224079 0 ] -/Count 0 -/Prev 271 0 R -/Parent 258 0 R -/Next 276 0 R ->> -endobj -276 0 obj -<< -/Title (Conclusion) -/Dest [ 245 0 R /XYZ 84.259843 575.052842 0 ] -/Count 0 -/Prev 275 0 R -/Parent 258 0 R ->> -endobj -277 0 obj -<< -/Count 19 -/First 258 0 R -/Last 258 0 R ->> -endobj -278 0 obj -<< -/Length1 10956 -/Filter /FlateDecode -/Length 7306 ->> -stream -xz \UU{}.^qyP PQ|%H0S|$Ȕ Ќd:Q?jeӔ59!| f}~^kZC(!3$dff߿nʾ털,aؾ/q^}s3 ۵Ss!#((6{N3'>;-0@L]T`*xV[񏚞 Xuan=Qg{l[/_ey*rS}-sw$wj )]W3n໧ ^ תm? f |W|_6_VC36+_WZ~? ,hOᲀOlRt>!.^/. Cy;x_jxl(OP8 wI~+pLp - . s(8|h2?|/&;[z^ &^+fط::D -{$`]6N31v|jAUհY3 ϚaC+_wnd([&}Nn<-`|})d{rWa*"QR.Xi\nO -Xn',P&ҥqK’<(vR,HcfXh/`^+V - -x4f iM3 ӗ4l'`)rBN+&770^8y\:d;`,=`FdQ}FⓑF ~0<ć0* 2a{Y~o+{F[@p`_~ 0 -Hp;X;$y?| #Opy3B>z};{x|^.Al1.vy/% R@/#6pAX+" y(`A3(G @p `C+jMR?`Bh?, "@g9$|(8{Aղpy+?\5 -Cb:A60{jǞYZ`nrG -r$BG$%g&&G*T:titP#y JsRTB`'w -`|s c# $A4D2ԑ/qw(i)cl VLEN#uG" FӋYyY$VD\pVR"~`؇\S<ZAplR+{d.gQ%M[gI 9"=0+!kVu\@!j*UR#H9)# ՘yDWB%R> !t#~81"d2kd?9@@5Y4~My^Kf?s0a[]K#oɿя$c tZ'얗ȵr.R]b= }}m`\Jі0y@CA$ HrD~r9FtEb n#j$VßБ& F˅}Ė&/ě-Z0vA&dW5.柡#j뤒aaT:Lc{A`+s)uO}{X , XF;Gg?8ޞ Rtq-5: h}Ixbi1_TÝ(İ,xY Y4/x9)\sy=dOu2B&SȀё.9%%)QreLph>{K叜l _S{ƃf]]B~MV_]![v\{#"Q~2)7&T>x .r|4lnk\W2ඣ]98'ge]mP6NNH<vⰓH'ZHx?]c*;uwЁYS.n|!uE{ѣ/<y_w,+gEt -xZPb^wd 2lO*+aV81zl‘6T \TmIԄYkGުfUKY:Q4oF&]m]jSt׬dswryvQK:\@yJ_JUz뚞@`TIlAaA S)ɔY%VSpuy7W f^[!^i9[~OH\'~atFC*UQF퐫$VEPW uL$JЅ[J8CMvާ';ٞv7X'2گuy!n'A - *zeM(#RR@%'jknkŻpݚಆ'[e[)!f/;|>ꊊVY{.Ǝ[lZH #9}_}W|&nR^wi"܌YXG>xL{~}kWA鳈HUTbQ-,f'yk.+kgj;wb2YeUyU/s*Ɋ:ѻtVU$z-tMV-]q@ƽΨ?+CY&WǦl!k9*sȠz9u]r/]Sd]pK-unȑiشVg䵺{>} H_??ޓsP4Ov*AOC{*J}XAY_R6J-kdl U H* e]7sC`dMMRMz`RtPUv('r&Nr3\E],bh]wI3t>_W6˛uah_$vGZTMzMj$<}O.5bcS=^)6TUm`iYJ~Ï>h^+Uͩ@` y=FB 0AUVltA 5Ât$"(Gh\njikiF/E kR-*9/8/Kh5<":&ٿgDG'JJȮ^ħ}bkgh3> HY`j~X`Cw/\֣6GP|@\~1@o&/ f捃vש˗O|[&$޽|S@ -TLS53y3~;T0[=M2Jvl"m:BHd$Y%y,АۏնWyߩ;/շ:6ǤH#THbiE;[DDjd7]|lC|]qɦ.~:|IuZH̀>xe<+`ӔY%FyUMʋ̦zyfD 1џOS%*ɷ&]}n UD)FԑGl֍ m~}l˯./LrG6}_"'x-:bU9˪fPzfFj{<খDm1~ QYQQj0YTGWW[OG5yŎ8c s0wӻ- K|/lSm[/WH9MYrK?oӼy]w0RÉUZ '7Hc[Co 6GFtZm4ؑiT.ӕ)e2CTSf.-YKm57bU;d㾽U joE|Gӧ~}7)"IE cwz%#B+lĕ4B٣od(6ՔhmTx0o*_$F GV 6cPS9يЗbxglg3p}\d/wTP}s3&H1{DFJՅp߫Nv{u[6M}t66 2 22IX!˯lhlX3.<*Pn,7H@ Lf BO`)D/.-eqjnq/+5@e`V3rƴ]?~4G ]&{?_pPJnrۡcGrFU-߾/ThʷG6s^&VڨT(cYMKW6V=6nH3TYwVTkk*Gm{ޭZe'?5hpٍpe:TOjTsmV8n3?^žD6{'N=wǎc}SopI9D&?c:m1e\-uBt-4(N}euS_%ID{}lt"al&+ee-cY-Sԉ=MiIN%$Ӂ0PJP2I&åL>Lv+x:&JYJ)3`4Osd-R<,W*Ѧդnb[aozҡ=Y5z]oӇoZlS Jh< - %dߺq2862Od:E'2(:Up&F dQ1 z(  G[wq65S3W\zݖ^@v*UU3aH6 gymx= Z,emaFC#kﳓLdŨ`/AJnt`$p#KGTjJ0ga)tYbbtfudz,i4#e)cنqƩ$泙/3噺B}q<̧RxLZ[&/֕Sƥ -4oD6эY&=sݯڴü즵J{˺JU5xS:=MmxO:ih$@xW_^K_z ufO5P6S LR:%QhfgK:2r/)"dKfid:GN%qX&LIXN0H sI>%IoN -/!br1ph|,q/̚rkliΥ;P*8ߛqfd>BLE\ [6"WȉX -1/F)w9q|Ξ=%Od l)NB}T74#[x1뜎 R&"oyR}b5կ6(Z}恘(1DI/\9<eM!ga a> -%Y(MJ! -LؐyUѾiгu/K{HdKČ4z%qYٱ_kymg髓?ӥ'3<ZqUw۱tg8EQT]EQSU<xz̈>vA/lcm/H62UwG=b?1M]7 o諰b ;װKݰK؇bkpDa2º:6Yxb!d%04j4j{tH];7w -Y;wv!Y1en bjna bhdŴ"O?[0`Ϭ\"^_1;wtpS4-w6Y1w~!B+(t7{}]TDFS-GCRݯ6Y/(.4eV]n8nԭ=:T> -stream -xYyxSG'K`6A֓d|ɲ%%ƒmd|'8` ɲ&!H&ad6$L/Ir !096ds~'ۄdo=uwuWկ=90lUf w+]nׄvv'K[/@ް'WZ{n9@l=vˁ?dnd|>bXKK>tn : ۇ}O#Ѝϫ<=*u -?ZWl."H{i^~q~—1QlʀBypZ$y厉+MΈ=g@8-y2b_ ֖pr `cEI#hEL^k%+VDe襃+Q5}VLB6h\yy(Zx5,P [N΂ O!nU۰C!8 [?zH -PN o=OA9|bx 8yt) ;w6 K9m4 i߆S."DcbC:ِEAvs8!8c1u{Ccx>ܬaYD%p- -=$MpCxl+RaqLiP.j  zǾe~J|"p>#st3!:<㾕~)l]݇3kx +ĻFrx31M1{b^J/n)}^zRl,O%;({WXglOONgŠmE&Six,# 5pב -T"Ͷ9ql GVsAD\^. rթPgS_)@R%iY™ꚅ38>23YoHF'%PYv{?Y]DqN="|ȢQ-R+D%WUz^y;{Ib;} ~xm%T9F8OwvDlxUR:M/j"jTPYap 9Q%DE!z=z񈤎J#釸b,&JIիSSU)R|AR5ƾo>?fؒm-.}ţc#NHmVsk=M }D=O}.@<KЏ0wq QRRVlm&uǮ[VxWK9t>=DDL.VL / $?Xe#o+q:]?yVGKk@c薭#9^>.f~;ϯm+t;]nR`ԛL'ZG-WOx^v:(Wz CeO!r\!~Rn -yJzp(^0Vw>kW&Ԑ' V.)v癚**||:ه1F wK 1IWjUsL#\_GC!wP&'YuVOU9~K)pxv]eMΊL+̌E&ߘ)JrQK(Qyb^_@aon1u:_޹) u\5C!*T:%BC Fi=hɼ*kY_^^py <_kȯ'6Kz}ļ!tiqlee -&:#^c,n&ĄyaTRys𺁛3B m5^S]qq|n+t}f6;O2f),o_r%AN4XDȟk7\꼸zt{dpaJ?k(5 -2~ו !Ryrx*\`kњs.ZzywC$urxVָ.ae^_8)/5:} SIVp|Ú=nPiÍZ-^v gC]fjTU<<'Z3gg{wq}~m]Me*O&ٱDD ?EuEiO!YX#R"7Oǝu -hD?EK.|.mXl6ovp2#ƕV -bb^¥'f~(*ш|%ٚ: sACθ4;ˠmGRb~IW@Cpe-qK]MpOf0:\V-j f*hEZܙzD"{rOK^}7L}}Fx 5a ͑y2td¿~,Ŭ 3 F<ߢR)X26}jiLqXʗ]Q"¢Gd ܗ_}*M,8tT,SVׯ+yDʟ[֥H*FxkʴLca .@f$>u7 4"}hObJvcbȩ9Z6:gڷwgY٘ϷZ(- ddJ́  e\r^^EmZ=yqg wrZ{fx v:.]ճnj8iҙiWD,f=b\wt -R[`ޕf - -\ld.* -}?WW -zJ+׮eԪ@UnMb>..e{ntI&v>]n}_'_QzQ]=G)>?}ƷM8}2}daY -H -`ڡ0i![,+=XWT}H tFqF lƺUJC8c16eڝ"fhL =y3ۂsGo&Wg;wC(**2Τd:䜍eX?OΤ˸.GWPe6,] ۋYDOG~8uo̤iJ -endstream -endobj -280 0 obj -<< -/Length1 15596 -/Filter /FlateDecode -/Length 11081 ->> -stream -x{y|TEoUNoNglt@ط -00!` Jd # b :Hܑa8 -IN>7uo]Ns9SPBw{Ġǧ}ӳWo!v+l:dxG.zlSl>w=r _R[B1qW*T !aiΘ7͹3&/ZHTH&l[f]6־LBڕΜ60GzL.r%6#O3'>`VLIINUH$T\Egxb-w -sLžaax8<KA<-rӱae Ae|˪tR_"h`9h -'cw>ŹT,كG!kXN`Y,'9rK#*,7G: Ayŵ€n}=G1S 8JDQ/ V#H"I?29:L$ -m1WI2I!3Aao*qׯp7GǧE3ή'C,}{h%/G_%^RZWK=zO/hi<߫qM__IΌ{Xbci)j>u#I9ܯ&uPc$N;v[zȁo=|4ĖLqL]Pը+=Q`ásh^ Mnq?V7J9xLq}|n_K~ZT?7T79|W]m94"koߖ__).+/E|ÿFȗn?#b9|O>v˟p Ç9|,W{Ѐ\89p8C> 9UgJ|9Z orxNn9pk!c.8j8ߎVKɯWpjzȯpCMxiR!(Zaqx/r9*{n|k?="i%<䰋óvFU3:v!P\a[+ʡ#r9'qn=y\-m}'o[Op،Gq2z&v 6OB *9`9+r89r#_pXaw+U~VzVXa9dE^b%?[`1i9¡' ;@-MR~ZFo{ؠG-=-E[_KWc+b,WKB;nBЕC֐!S;Fʝ@6!stJ; TNqAJ-ݶ;^[.kqhwA+КC2$e_/heD 6!>.E_ q);سC hm4(!)xzC;E.SeP/N|;=`f6րBPw!:JXʖtD` -*I+d -718,(2@S؁¢??BZr(t3qBѲՒx3t=ݤ kT7h6)ϖƓe%Yw}/i]O/" w{:l -KHqbxdÐ"{㶅q|LDi)\!e$2)SI2.& -![*M -Ҝ?a;9aHLA6L,(0eb'oMfi_7@'Q3,L}Y!o ly##}C4u#;tZ@m.$"z&JHn_܎oq͎'(i9noʉ_(Q<*{hmnv4tPgz}9n4O02כgRȐgBemk-6¶v>G[t>OBt'S3T7+YJ -9ZVDm.\vO(ۺ* Dˬ^ĬDʭ㬨8jk'kU7گ~Ùq8=XrPYYvXIIəaaGRRf 6xv)*;8 ?dB:Ԕ3S9Vogɵןolj_Wsxb$%wR]aBE픕1KLHˬvAsN:oϡCѡ'tٙ)'O=C3YyHZ&mٗwgMJ~V H+`ĻKt*`I_|gTWQ"ckq<5Ip *H Bfj}jӎxb4>pJS"oK, N% ;s%ҲG冟E?C?^KExē7>,ұ_W勒TR!UJST5UK5iO٧GQzQrT=5Տ{3`4QLT'jM_#j<O #Xxhs؝XO4eu:$󀢍%%7lﾻv]:4l;4flVkt=]E@/GN'I~THB^ -xŌCXd z54_CeF4HYMoVKKP-jRMı&ېh)ow<R*H#vQIC{tz`wJ0@:<9IÞ3HvVOB}I"( -]^lZrg޲z g1cj]ع$}yŐxcM:X&p.f#I7­vT(%q+˕J mB "Iv/$ĺLm_d|p85a _Ayבa-;7g7cSv8m׍o>M~ɿTf򍿯ܽ|ޢ[ ː͟ 1ľU*J ^R=cBAkc -DE.r?Yvݨ_Q;ǥ';<D?-VNZ!wjlD[a,!,$U+} ^*44'rc֑FL -@h -FbަA^O.h"u/ٺuͺ僇}"p?? ZB7tcl=wyq?`7%"y d›RDBZU[fkMC6L Aagy -τ-O$?fa_ozիV,[NV 9ދ>a$A| P8,X,K&A'>LA'V$4U14T+Ík -iߎN8:a[F$f&E2n`x2B#0a3m:=un~f ^َn!GCl'T7< -;[uF ˎh?2%r B^Wʡ224B:*i.1 #ib x@O5 --uk,O<3vנ#Oן,x_f6.ie6g 56,~RaZO*l -THtT4'$0|@=hz,=)>%A>}6THGҞU^En-SVȓ6OjSBNeSGCV;qD9 4`fGԻ3 -)KE2vd2K4 -,hǦ5?uF[ݜmϤ8F1?>"AdE}䍊ZHVh:ăR͈93㥡y_Oc&`ē'6+ t̬8lxCl<ݼ[IDqZD -*w4!O p]/c%-pOp9s}lhZJXo -[iFБtRFLе;3\SD#ek -tʨ1 0[E*" -I `BAS] -ƦS2JtG 7%61e:670Td(#q$"{F%j;oTQlt-P``"(C/>JU:9An"*F06,Ibl-WpVz~(:TD@>q.Ӊۄk'[7Io@Ou\Kf5Uؠ]n ',%ݙn0mhKV`&:l(^Y\\o؄ڏF/+A#h?lj=-j]x% %Žz]טD5eH#I`D e_>c#Hޤ߾i9֢-?¿Q&*C1ߚt>I|E"n&L֛%fR@.9:t%-&Kc'L&VZb0=HF'`1ViS_;CnPw.lT8{͵`7I=;y?a~ݚ x.-¬f7֫bc+QK+%T+wT($EX;Ԝ(fgŲ;&c AqhLLE]%*N_Pz<3KNH"y6ЄcY,z{fesy\Y'zKעL ~V,|$."'8pU*g*WF~͢SE< of,^7#lI$j^ёGޙ賅*Bў\bMQD"LESBҤ-g,e#G=o_={VrY7d7>K׮]"ͅM3?-Knn''@mȉBP:8S1 4e>A@Ԉi<{=M:b/`3s|u>\SC(,䒿'Fntfݓٌ6j*ڄi* KGf1&-Y%w pg&1&BvX꬏acdǜڂOj+ڙ|$K&˅L)W:,#:(i*=}p-rIzkG;Sn۶G?9{KwȇY"WdUUZSq8}^Ā߯k D{_g|}zvn[_TTRRTα~n8|f>|Szq#?I^bڨP4QZR,n -SHh=[}ॏPe1׮~-TL*h:1ѸVڼhMfWPy94Zzr wCz %PkvjjZJ*ubb.-4],{;bw"/%:jymKS˚R\ 3h}oT %aRoX ZM tEcDbwn7vz23`LMeW^rSxr}m~nyj-9g~ěj:ߵ_[9aͥ*h1IPwQMV_:,O!&WHbvhaF#voKP{~hMImm=ij*6bܤ`=? ?B!z)r\a5 4SEHr=՝$fO5ͧ%[[+MjJ-+|Ya>Of12zFk^o} -k'fMR$R>8e6%/\J`xa^O/=M*=ʟm6t vҟy9GyTidaI8y*$,\~LRK6rAUDa -Ӵ0.kfU"{JdHr~he:fIY2xT^,S6P~OPVs|LsoU(ĢƓ0 XNB0(&Qi٪߿"-v???t!hg p$$&JQݖ8:aWæ R;Gh6`eĀc :nj$d;]/D?'MJӔ45MK3i漰:IE ᆳO޳K;6K7>+?ʍp>὏vzXW 8Xg'x >F4! ;R}aC"~^(|JˆE!h&JK ĂA,uʨc K^~G⢢ YdJSW:!Npi60;jx7ƙu CpdT3TXLU]Q>XBο%&zg'vjwđ8H#i4Þ?}w %CPPs1:<8|@Dk䎕$&efN#nYxt-]A fAk5f61v~xkFKM K^:[- ?^\)[vah >&+uz",?a5`~ے -܁I'j,cu|᡽{aٲ[L.$Ʋ%'M v Ybdq\(Cπ{*KH/xb+d&bAMdcLa(E{|UՒ"/2cMX/4Ȗ yR<"R[O ܓگ%ŽXj6IXKcX$DKr)J4ZHmÒ6J5QkoaYrfh]-~Ziye:ӥYl4#l[D!z;Nκ]h}6%WULZ%-Qo-0p͉w7t`?*p)o bT&Pf/bUA" KQ0ԏ=&YGݚ<|]ሳ`S8r翎 O/u:>BJݭJ1H]C M,Q`@ |mP ޢmh4Zc}Y8C%u*5DL33Yrx<6;=bX!b5'-D95g?kP`u0l+E%5 XiדؙМ$kst.V'^f 9w35c{p\>H3?}B4i+^Vd?36+>Sc⁘kLnz]bVa$FCEtmﮣr+MHi~a,KAbvq ?{fc~SZ U,.{ [FmMQvT6>Ifc}QaevG$9HDMI|= [e_tD&GuwdȒ.V.M -H tWwdJLs1 gouڱ)*b?m,(rW|wapY*#M2a7Q$[:#4X{KeN<@dy"3LnMbG Ft)xG{EX&dDl?2d.nqdZ4> -stream -x9iXU׵kuA@"z55AAFQD!Jժ1|mHK jM Dۦ~41|g65px뜋tz}{53tao"QoܢsgzKWRiF(7=sK*ZR{}%&E#S/[Tي۩cͦvϩyߛ{mkZSW4 `kak*]RO.v57w5Y{c˚ʹC ^8TULdlBseSMl$K -ͭ-ǯ -ugH8)UlZm)hAy.š //J4V<4O$GJ =41G+ ,>CHvm-OkeWgM`]QD}%eTUZMT;b5i0(l Pӧ--|Ź\<Ó~^5 'uxŽ;26d>7~Cq2XyO>uG|h׏q|wݧq6q}|W9 -_3 wXp{~Mnm[|[5nC}U¸ŏ__c7SjqL| Om2m767265شMllrl Zj= qӜjkihbkd +d\U+p2>~\—̅C_e~\*ciZĀK>\\l]Xld\/Åո@2;yv-{ t";݅EvǍ38ÏmXX`2L33N3`~^(üyĩsyn.N!⦸1'scvg1ˁL7Wc&3ݘxFq2uMƴTO A!Љ)jA2S,2^$I'q _LIL n>*|1D8F:xldcLDŽc42Fѐ(?F:0"#PΆN p;i -Zx  .BCg.:rN~ ChZ j\-]h MF`A=k5F6ȡ8Qp%A8%rA0QCL鋌phdz>õXc'>xE0E$R%edqAVBg{`2eZuhzh!*wa| Bț -|+p307z2˄,ޠ2ӳ<·` Q{OL "pp XϔX%J8n2B dK)T+ΊjB3F 8\v8-U 6889|_0Zx_ -aB%QуEPH#pAsH2tV>B7(N~w 3=W6өi+{%!j;8]M)+wrh<,\"hf&'ym^&tWINw+4D. -\p:\dz2 uRgaI&t GC2(Xy Vy: ,eT -,Cdh5,z1 i\ RPU!R޸B~O|mi\+{/eīJ&0AH>P b&a[^xy%/=1V0Zl#DltmV(T^%˟ o%IR*n!`@(kB:D+XXt"Rpsped'q7+c,YO7UU}?|0vQ{CqDh Lw9PG"$-V[7M-gQm wZLRsx[RV]R+4$9u[H87#N|)5!!';> -%$JN+4R8MH\A| ?{fum%;:.Nm˵MW6/z>o'˿gβ33fWrYf5爫Rx_ k <`V.PdZsTq3^Q=yE&2ihɪl|3 ,&l P*b(Jck iPDI2LA#94&)O+>!HI,fҲ3b2<ލB͵vngY_qw]L"͛#Iq$),e;J)S<.ᯭXؾWsVoU7t]vU0.Xӎc]s3ɿ EnLjoa09:]hk`[e\)'\ٚw=GyfJ&rsE߽ǫ1ps%'8гRRT`N7)U;cN+wD4V)(7sכ6֎"eHROP3!` rl{1͈6 eռzVWnn^,qhefn2eˡCV]]/ qFɱ=&[=tQ*H ͮI i -kepxt|y!ߑ_lNz"rQF\T{i.}Ll &Fz%GADsqkʒʚچ3촐"FPG$擯CCA0 W#jrɐcTHŜ_0SL.^{B -F.cg䷪+cWrm26/Az]ۣtKjeTa}/ڀYNxlhI/wbhy aN;,HtX(ԆI4{pODoU6K;?Т͗ --8% ׵^t(MMa׿/B@GAhkby=xCF Ll&{LpAbbs&o+4U8V^rLЪ]wBeͭsLF1٭Z d|aXZ!.͛n<>aaG#ᾗyY!faYrџgY!'/;hmbs{ml?F.Ct~w:ClVWO0u궩;86(UVoʿ^>c nU-]ravN 'a!ق&7h*n^X7m0_Ɏ ٘:szBcبXq!*R>!VL#BQ0b:A#2^G7>I:CLG̹#6o'/E($/@<,^H&Ɇdc)ٜjOw;S]ɑQ1ɞ$o|vs1(P&Q y/UU\j> -endobj -283 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /FEVNJS+DejaVuSans -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 317 ] 17 [ 317 ] 20 [ 636 636 ] 25 [ 636 ] 37 [ 686 698 ] 40 [ 631 ] 42 [ 774 751 294 ] 46 [ 655 ] 53 [ 694 634 ] 68 [ 612 ] 70 [ 549 634 615 ] 74 [ 634 633 277 ] 78 [ 579 ] 80 [ 974 633 611 ] 85 [ 411 520 392 633 591 817 ] ] -/FontDescriptor 282 0 R ->> -endobj -284 0 obj -<< -/Length 758 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -31 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0015> <0032> -<0003> <0020> -<002b> <0048> -<0044> <0061> -<0055> <0072> -<0047> <0064> -<0048> <0065> -<0051> <006e> -<004c> <0069> -<004a> <0067> -<002a> <0047> -<0058> <0075> -<005a> <0077> -<0057> <0074> -<004b> <0068> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0046> <0063> -<0050> <006d> -<004e> <006b> -<0052> <006f> -<0056> <0073> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -285 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /FEVNJS+DejaVuSans -/Encoding /Identity-H -/DescendantFonts [ 283 0 R ] -/ToUnicode 284 0 R ->> -endobj -286 0 obj -<< -/Type /FontDescriptor -/FontName /MIHDNY+Poppins -/FontFamily (Poppins) -/Flags 4 -/FontBBox [ -27 -170 413 547 ] -/ItalicAngle 0 -/Ascent 1049 -/Descent -349 -/CapHeight 547 -/StemV 80 -/StemH 80 -/FontFile2 279 0 R ->> -endobj -287 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /MIHDNY+Poppins -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 266 ] 5 [ 291 ] 10 [ 158 453 453 ] 14 [ 682 197 550 209 475 627 319 574 588 628 627 634 545 630 629 212 ] 36 [ 673 612 771 706 512 503 777 691 245 ] 46 [ 598 431 ] 49 [ 702 785 578 ] 53 [ 607 586 540 ] 57 [ 675 975 ] 60 [ 583 ] 68 [ 675 675 606 675 619 328 675 639 245 247 514 245 1029 639 639 675 675 372 521 363 639 560 819 478 562 454 ] 209 [ 411 ] ] -/FontDescriptor 286 0 R ->> -endobj -288 0 obj -<< -/Length 1276 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -68 beginbfchar -<0035> <0052> -<002e> <004b> -<0028> <0045> -<0015> <0032> -<0003> <0020> -<002b> <0048> -<0044> <0061> -<0055> <0072> -<0047> <0064> -<0048> <0065> -<0051> <006e> -<004c> <0069> -<004a> <0067> -<002a> <0047> -<0058> <0075> -<005a> <0077> -<0057> <0074> -<004b> <0068> -<0026> <0043> -<002c> <0049> -<0036> <0053> -<0059> <0076> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0025> <0042> -<0046> <0063> -<0050> <006d> -<004e> <006b> -<0016> <0033> -<0017> <0034> -<0018> <0035> -<001b> <0038> -<001c> <0039> -<0013> <0030> -<0032> <004f> -<0052> <006f> -<0056> <0073> -<0010> <002d> -<004f> <006c> -<0054> <0071> -<0053> <0070> -<0045> <0062> -<0024> <0041> -<0033> <0050> -<0049> <0066> -<0037> <0054> -<005c> <0079> -<000b> <0028> -<000c> <0029> -<000f> <002c> -<001d> <003a> -<0039> <0056> -<000e> <002b> -<0027> <0044> -<0029> <0046> -<0005> <0022> -<004d> <006a> -<00d1> <2022> -<005b> <0078> -<003c> <0059> -<000a> <0027> -<0012> <002f> -<003a> <0057> -<002f> <004c> -<0031> <004e> -<001a> <0037> -<005d> <007a> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -289 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /MIHDNY+Poppins -/Encoding /Identity-H -/DescendantFonts [ 287 0 R ] -/ToUnicode 288 0 R ->> -endobj -290 0 obj -<< -/Type /FontDescriptor -/FontName /BKSMOQ+DejaVuSansMono -/FontFamily (DejaVu Sans Mono) -/Flags 4 -/FontBBox [ 0 -14 502 728 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 728 -/StemV 80 -/StemH 80 -/FontFile2 280 0 R ->> -endobj -291 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /BKSMOQ+DejaVuSansMono -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 3 [ 602 602 602 602 602 602 ] 10 [ 602 602 602 602 601 ] 16 [ 601 601 601 601 601 601 602 ] 24 [ 601 601 ] 27 [ 602 601 602 602 602 602 602 ] 36 [ 602 602 602 602 602 602 602 602 602 ] 46 [ 602 602 602 601 602 601 ] 53 [ 602 601 602 601 602 602 ] 62 [ 602 ] 64 [ 602 ] 66 [ 602 ] 68 [ 601 601 601 601 601 601 602 602 601 602 601 601 602 601 601 601 602 601 601 601 601 602 601 601 601 ] 94 [ 602 ] 96 [ 602 ] ] -/FontDescriptor 290 0 R ->> -endobj -292 0 obj -<< -/Length 1416 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -78 beginbfchar -<0033> <0050> -<0052> <006f> -<0047> <0064> -<0036> <0053> -<0048> <0065> -<0046> <0063> -<0058> <0075> -<0055> <0072> -<004c> <0069> -<0057> <0074> -<005c> <0079> -<004f> <006c> -<0056> <0073> -<0031> <004e> -<005a> <0077> -<004e> <006b> -<0053> <0070> -<0049> <0066> -<0010> <002d> -<0014> <0031> -<0011> <002e> -<0019> <0036> -<0018> <0035> -<0051> <006e> -<0044> <0061> -<001d> <003a> -<0003> <0020> -<0026> <0043> -<004a> <0067> -<0050> <006d> -<004b> <0068> -<005b> <0078> -<0012> <002f> -<001c> <0039> -<0013> <0030> -<0045> <0062> -<0059> <0076> -<0042> <005f> -<0020> <003d> -<0038> <0055> -<0005> <0022> -<0030> <004d> -<0024> <0041> -<0037> <0054> -<0039> <0056> -<000e> <002b> -<0006> <0023> -<0004> <0021> -<0007> <0024> -<000b> <0028> -<004d> <006a> -<005e> <007b> -<003e> <005b> -<000d> <002a> -<0040> <005d> -<000a> <0027> -<0060> <007d> -<000c> <0029> -<001e> <003b> -<0015> <0032> -<001b> <0038> -<001f> <003c> -<0021> <003e> -<0028> <0045> -<0054> <0071> -<0016> <0033> -<002f> <004c> -<0035> <0052> -<002a> <0047> -<0025> <0042> -<0027> <0044> -<0032> <004f> -<0008> <0025> -<002b> <0048> -<003a> <0057> -<0029> <0046> -<002e> <004b> -<002c> <0049> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -293 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /BKSMOQ+DejaVuSansMono -/Encoding /Identity-H -/DescendantFonts [ 291 0 R ] -/ToUnicode 292 0 R ->> -endobj -294 0 obj -<< -/Type /FontDescriptor -/FontName /CBTLAY+DejaVuSansMono -/FontFamily (DejaVu Sans Mono) -/Flags 5 -/FontBBox [ 0 -207 558 728 ] -/ItalicAngle 0 -/Ascent 928 -/Descent -235 -/CapHeight 728 -/StemV 80 -/StemH 80 -/FontFile2 281 0 R ->> -endobj -295 0 obj -<< -/Type /Font -/Subtype /CIDFontType2 -/BaseFont /CBTLAY+DejaVuSansMono -/CIDSystemInfo << -/Registry (Adobe) -/Ordering (Identity) -/Supplement 0 ->> -/W [ 16 [ 601 ] 36 [ 601 ] 49 [ 601 ] 51 [ 601 ] 54 [ 601 601 ] 68 [ 601 ] 70 [ 601 601 601 601 ] 76 [ 601 ] 78 [ 601 601 601 601 601 601 ] 85 [ 601 601 601 601 601 601 ] 92 [ 601 ] ] -/FontDescriptor 294 0 R ->> -endobj -296 0 obj -<< -/Length 674 ->> -stream -/CIDInit /ProcSet findresource begin -12 dict begin -begincmap -/CIDSystemInfo -<< /Registry (Adobe) -/Ordering (UCS) -/Supplement 0 ->> def -/CMapName /Adobe-Identity-UCS def -/CMapType 2 def -1 begincodespacerange -<0000> -endcodespacerange -25 beginbfchar -<0053> <0070> -<0055> <0072> -<0052> <006f> -<0057> <0074> -<0048> <0065> -<0046> <0063> -<0010> <002d> -<004e> <006b> -<0051> <006e> -<004f> <006c> -<0047> <0064> -<0049> <0066> -<0044> <0061> -<0058> <0075> -<0056> <0073> -<0033> <0050> -<0036> <0053> -<004c> <0069> -<005c> <0079> -<0031> <004e> -<005a> <0077> -<0050> <006d> -<0059> <0076> -<0024> <0041> -<0037> <0054> -endbfchar -endcmap -CMapName currentdict /CMap defineresource pop -end -end -endstream -endobj -297 0 obj -<< -/Type /Font -/Subtype /Type0 -/BaseFont /CBTLAY+DejaVuSansMono -/Encoding /Identity-H -/DescendantFonts [ 295 0 R ] -/ToUnicode 296 0 R ->> -endobj -298 0 obj -<< -/FEVNJS 285 0 R -/MIHDNY 289 0 R -/BKSMOQ 293 0 R -/CBTLAY 297 0 R ->> -endobj -xref -0 299 -0000000000 65535 f -0000000015 00000 n -0000000176 00000 n -0000000297 00000 n -0000011596 00000 n -0000011729 00000 n -0000014387 00000 n -0000014586 00000 n -0000018015 00000 n -0000018337 00000 n -0000018471 00000 n -0000018607 00000 n -0000018757 00000 n -0000018908 00000 n -0000019051 00000 n -0000019195 00000 n -0000019353 00000 n -0000019512 00000 n -0000019669 00000 n -0000019827 00000 n -0000019966 00000 n -0000020106 00000 n -0000020279 00000 n -0000020453 00000 n -0000020590 00000 n -0000020728 00000 n -0000025444 00000 n -0000025734 00000 n -0000025989 00000 n -0000026125 00000 n -0000026276 00000 n -0000026420 00000 n -0000026579 00000 n -0000026737 00000 n -0000026877 00000 n -0000027051 00000 n -0000027189 00000 n -0000027456 00000 n -0000027722 00000 n -0000032771 00000 n -0000032972 00000 n -0000037891 00000 n -0000038146 00000 n -0000038279 00000 n -0000038410 00000 n -0000038541 00000 n -0000038672 00000 n -0000038803 00000 n -0000038934 00000 n -0000043741 00000 n -0000043989 00000 n -0000044122 00000 n -0000044253 00000 n -0000044384 00000 n -0000044515 00000 n -0000044648 00000 n -0000049806 00000 n -0000050026 00000 n -0000050158 00000 n -0000055590 00000 n -0000055880 00000 n -0000056013 00000 n -0000056144 00000 n -0000056275 00000 n -0000056406 00000 n -0000056537 00000 n -0000056670 00000 n -0000056801 00000 n -0000056932 00000 n -0000057063 00000 n -0000057194 00000 n -0000057325 00000 n -0000062131 00000 n -0000062393 00000 n -0000062526 00000 n -0000062657 00000 n -0000062788 00000 n -0000062919 00000 n -0000063050 00000 n -0000063181 00000 n -0000063404 00000 n -0000068141 00000 n -0000068368 00000 n -0000068501 00000 n -0000068631 00000 n -0000073579 00000 n -0000074082 00000 n -0000074213 00000 n -0000074344 00000 n -0000074475 00000 n -0000074606 00000 n -0000074737 00000 n -0000074868 00000 n -0000074999 00000 n -0000075131 00000 n -0000075263 00000 n -0000075395 00000 n -0000075527 00000 n -0000075659 00000 n -0000075791 00000 n -0000075923 00000 n -0000076056 00000 n -0000076189 00000 n -0000076322 00000 n -0000076455 00000 n -0000076588 00000 n -0000076721 00000 n -0000076854 00000 n -0000076987 00000 n -0000077120 00000 n -0000077253 00000 n -0000077386 00000 n -0000077519 00000 n -0000077652 00000 n -0000077785 00000 n -0000077918 00000 n -0000078051 00000 n -0000078184 00000 n -0000078317 00000 n -0000078450 00000 n -0000078583 00000 n -0000078716 00000 n -0000078849 00000 n -0000078981 00000 n -0000079112 00000 n -0000083562 00000 n -0000084081 00000 n -0000084214 00000 n -0000084347 00000 n -0000084480 00000 n -0000084613 00000 n -0000084746 00000 n -0000084879 00000 n -0000085012 00000 n -0000085145 00000 n -0000085278 00000 n -0000085411 00000 n -0000085544 00000 n -0000085677 00000 n -0000085810 00000 n -0000085943 00000 n -0000086076 00000 n -0000086209 00000 n -0000086342 00000 n -0000086475 00000 n -0000086608 00000 n -0000086741 00000 n -0000086874 00000 n -0000087007 00000 n -0000087140 00000 n -0000087273 00000 n -0000087406 00000 n -0000087539 00000 n -0000087672 00000 n -0000087805 00000 n -0000087938 00000 n -0000088071 00000 n -0000088204 00000 n -0000088337 00000 n -0000088470 00000 n -0000088603 00000 n -0000088736 00000 n -0000088869 00000 n -0000089001 00000 n -0000089132 00000 n -0000093641 00000 n -0000094160 00000 n -0000094293 00000 n -0000094426 00000 n -0000094559 00000 n -0000094692 00000 n -0000094825 00000 n -0000094958 00000 n -0000095091 00000 n -0000095224 00000 n -0000095357 00000 n -0000095490 00000 n -0000095623 00000 n -0000095756 00000 n -0000095889 00000 n -0000096022 00000 n -0000096155 00000 n -0000096288 00000 n -0000096421 00000 n -0000096554 00000 n -0000096687 00000 n -0000096820 00000 n -0000096953 00000 n -0000097087 00000 n -0000097221 00000 n -0000097355 00000 n -0000097489 00000 n -0000097623 00000 n -0000097757 00000 n -0000097891 00000 n -0000098025 00000 n -0000098159 00000 n -0000098293 00000 n -0000098427 00000 n -0000098561 00000 n -0000098695 00000 n -0000098829 00000 n -0000098963 00000 n -0000099096 00000 n -0000099228 00000 n -0000103644 00000 n -0000104163 00000 n -0000104297 00000 n -0000104431 00000 n -0000104565 00000 n -0000104699 00000 n -0000104833 00000 n -0000104967 00000 n -0000105101 00000 n -0000105235 00000 n -0000105369 00000 n -0000105503 00000 n -0000105637 00000 n -0000105771 00000 n -0000105905 00000 n -0000106039 00000 n -0000106173 00000 n -0000106307 00000 n -0000106441 00000 n -0000106575 00000 n -0000106709 00000 n -0000106843 00000 n -0000106977 00000 n -0000107111 00000 n -0000107245 00000 n -0000107379 00000 n -0000107513 00000 n -0000107647 00000 n -0000107781 00000 n -0000107915 00000 n -0000108049 00000 n -0000108183 00000 n -0000108317 00000 n -0000108451 00000 n -0000108585 00000 n -0000108719 00000 n -0000108853 00000 n -0000108987 00000 n -0000109120 00000 n -0000109252 00000 n -0000113043 00000 n -0000113354 00000 n -0000113488 00000 n -0000113622 00000 n -0000113756 00000 n -0000113890 00000 n -0000114024 00000 n -0000114158 00000 n -0000114292 00000 n -0000114426 00000 n -0000114560 00000 n -0000114694 00000 n -0000114828 00000 n -0000115096 00000 n -0000115272 00000 n -0000115397 00000 n -0000115580 00000 n -0000115734 00000 n -0000115885 00000 n -0000116061 00000 n -0000116199 00000 n -0000116336 00000 n -0000116527 00000 n -0000116663 00000 n -0000116809 00000 n -0000116959 00000 n -0000117120 00000 n -0000117292 00000 n -0000117423 00000 n -0000117567 00000 n -0000117697 00000 n -0000117874 00000 n -0000118002 00000 n -0000118064 00000 n -0000125460 00000 n -0000129765 00000 n -0000140937 00000 n -0000146172 00000 n -0000146404 00000 n -0000146824 00000 n -0000147635 00000 n -0000147785 00000 n -0000148014 00000 n -0000148559 00000 n -0000149889 00000 n -0000150036 00000 n -0000150277 00000 n -0000150882 00000 n -0000152352 00000 n -0000152506 00000 n -0000152748 00000 n -0000153121 00000 n -0000153848 00000 n -0000154002 00000 n -trailer -<< -/Size 299 -/Root 3 0 R -/Info 2 0 R ->> -startxref -154089 -%%EOF diff --git a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/rke2-1.6-hardening-2.6.md b/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/rke2-1.6-hardening-2.6.md deleted file mode 100644 index 8ce1fe8f70e..00000000000 --- a/versioned_docs/version-2.6/security/hardening-guides/rke2-1.6-hardening-2.6/rke2-1.6-hardening-2.6.md +++ /dev/null @@ -1,403 +0,0 @@ ---- -title: RKE2 Hardening Guide with CIS v1.6 Benchmark -weight: 100 ---- - -This document provides prescriptive guidance for hardening a production installation of a RKE2 cluster to be provisioned with Rancher v2.6.5. It outlines the configurations and controls required to address Kubernetes benchmark controls from the Center for Information Security (CIS). - -> This hardening guide describes how to secure the nodes in your cluster, and it is recommended to follow this guide before installing Kubernetes. - -This hardening guide is intended to be used for RKE2 clusters and associated with specific versions of the CIS Kubernetes Benchmark, Kubernetes, and Rancher: - -| Rancher Version | CIS Benchmark Version | Kubernetes Version | -| --------------- | --------------------- | ------------------ | -| Rancher v2.6.5+ | Benchmark v1.6 | Kubernetes v1.21 up to v1.23 | - -[Click here to download a PDF version of this document](https://releases.rancher.com/documents/security/2.6/Rancher_RKE2_v2-6_CIS_v1-6_Hardening_Guide.pdf). - -- [Overview](#overview) -- [Host-level requirements](#host-level-requirements) -- [Setting up hosts](#setting-up-hosts) -- [Kubernetes runtime requirements](#kubernetes-runtime-requirements) -- [API Server audit configuration](#api-server-audit-configuration) -- [Known issues](#known-issues) -- [Reference Hardened RKE2 Template Configuration](#reference-hardened-rke2-template-configuration) -- [Conclusion](#conclusion) - -### Overview - -This document provides prescriptive guidance for hardening a RKE2 cluster to be provisioned through Rancher v2.6.5+ with Kubernetes v1.21 up to v1.23. It outlines the configurations required to address Kubernetes benchmark controls from the Center for Information Security (CIS). - -For more details about evaluating a hardened RKE2 cluster against the official CIS benchmark, refer to the [RKE2 - CIS 1.6 Benchmark - Self-Assessment Guide - Rancher v2.6]({{}}/rancher/v2.6/en/security/hardening-guides/rke2-1.6-benchmark-2.6/). - -RKE2 is designed to be "hardened by default" and pass the majority of the Kubernetes CIS controls without modification. There are a few notable exceptions to this that require manual intervention to fully pass the CIS Benchmark: - -1. RKE2 will not modify the host operating system. Therefore, you, the operator, must make a few host-level modifications. -2. Certain CIS policy controls for `PodSecurityPolicies` and `NetworkPolicies` will restrict the functionality of the cluster. You must opt into having RKE2 configuring these out of the box. - -To help ensure these above requirements are met, RKE2 can be started with the `profile` flag set to `cis-1.6`. This flag generally does two things: - -1. Checks that host-level requirements have been met. If they haven't, RKE2 will exit with a fatal error describing the unmet requirements. -2. Configures runtime pod security policies and network policies that allow the cluster to pass associated controls. - -> The profile's flag only valid values are `cis-1.5` or `cis-1.6`. It accepts a string value to allow for other profiles in the future. - -The following section outlines the specific actions that are taken when the `profile` flag is set to `cis-1.6`. - -### Host-level requirements - -There are two areas of host-level requirements: kernel parameters and etcd process/directory configuration. These are outlined in this section. - -#### Ensure `protect-kernel-defaults` is set - -This is a kubelet flag that will cause the kubelet to exit if the required kernel parameters are unset or are set to values that are different from the kubelet's defaults. - -When the `profile` flag is set, RKE2 will set the flag to `true`. - -> `protect-kernel-defaults` is exposed as a configuration flag for RKE2. If you have set `profile` to "cis-1.x" and `protect-kernel-defaults` to `false` explicitly, RKE2 will exit with an error. - -RKE2 will also check the same kernel parameters that the kubelet does and exit with an error following the same rules as the kubelet. This is done as a convenience to help the operator more quickly and easily identify what kernel parameters are violating the kubelet defaults. - -Both `protect-kernel-defaults` and `profile` flags can be set in RKE2 template configuration file. - -```yaml -spec: - rkeConfig: - machineSelectorConfig: - - config: - profile: cis-1.6 - protect-kernel-defaults: true -``` - -#### Ensure etcd is configured properly - -The CIS Benchmark requires that the etcd data directory be owned by the `etcd` user and group. This implicitly requires the etcd process to be ran as the host-level `etcd` user. To achieve this, RKE2 takes several steps when started with a valid "cis-1.x" profile: - -1. Check that the `etcd` user and group exists on the host. If they don't, exit with an error. -2. Create etcd's data directory with `etcd` as the user and group owner. -3. Ensure the etcd process is ran as the `etcd` user and group by setting the etcd static pod's `SecurityContext` appropriately. - -### Setting up hosts - -This section gives you the commands necessary to configure your host to meet the above requirements. - -#### Set kernel parameters - -The following `sysctl` configuration is recommended for all nodes type in the cluster. Set the following parameters in `/etc/sysctl.d/90-kubelet.conf`: - -```ini -vm.panic_on_oom=0 -vm.overcommit_memory=1 -kernel.panic=10 -kernel.panic_on_oops=1 -``` - -Run `sudo sysctl -p /etc/sysctl.d/90-kubelet.conf` to enable the settings. - -Please perform this step only on fresh installations, before actually deploying RKE2 through Rancher. - -#### Create the etcd user - -On some Linux distributions, the `useradd` command will not create a group. The `-U` flag is included below to account for that. This flag tells `useradd` to create a group with the same name as the user. - -```bash -sudo useradd -r -c "etcd user" -s /sbin/nologin -M etcd -U -``` - -### Kubernetes runtime requirements - -The runtime requirements to pass the CIS Benchmark are centered around pod security and network policies. These are outlined in this section. - -#### `PodSecurityPolicies` - -RKE2 always runs with the `PodSecurityPolicy` admission controller turned on. However, when it is **not** started with a valid "cis-1.x" profile, RKE2 will put an unrestricted policy in place that allows Kubernetes to run as though the `PodSecurityPolicy` admission controller was not enabled. - -When ran with a valid "cis-1.x" profile, RKE2 will put a much more restrictive set of policies in place. These policies meet the requirements outlined in section 5.2 of the CIS Benchmark. - -> The Kubernetes control plane components and critical additions such as CNI, DNS, and Ingress are ran as pods in the `kube-system` namespace. Therefore, this namespace will have a policy that is less restrictive so that these components can run properly. - -#### `NetworkPolicies` - -When ran with a valid "cis-1.x" profile, RKE2 will put `NetworkPolicies` in place that passes the CIS Benchmark for Kubernetes' built-in namespaces. These namespaces are: `kube-system`, `kube-public`, `kube-node-lease`, and `default`. - -The `NetworkPolicy` used will only allow pods within the same namespace to talk to each other. The notable exception to this is that it allows DNS requests to be resolved. - -> Operators must manage network policies as normal for additional namespaces that are created. - -#### Configure `default` service account - -**Set `automountServiceAccountToken` to `false` for `default` service accounts** - -Kubernetes provides a `default` service account which is used by cluster workloads where no specific service account is assigned to the pod. Where access to the Kubernetes API from a pod is required, a specific service account should be created for that pod, and rights granted to that service account. The `default` service account should be configured such that it does not provide a service account token and does not have any explicit rights assignments. - -For each namespace including `default` and `kube-system` on a standard RKE2 install, the `default` service account must include this value: - -```yaml -automountServiceAccountToken: false -``` - -For namespaces created by the cluster operator, the following script and configuration file can be used to configure the `default` service account. - -The configuration bellow must be saved to a file called `account_update.yaml`. - -```yaml -apiVersion: v1 -kind: ServiceAccount -metadata: - name: default -automountServiceAccountToken: false -``` - -Create a bash script file called `account_update.sh`. Be sure to `sudo chmod +x account_update.sh` so the script has execute permissions. - -```bash -#!/bin/bash -e - -for namespace in $(kubectl get namespaces -A -o=jsonpath="{.items[*]['metadata.name']}"); do - echo -n "Patching namespace $namespace - " - kubectl patch serviceaccount default -n ${namespace} -p "$(cat account_update.yaml)" -done -``` - -Execute this script to apply the `account_update.yaml` configuration to `default` service account in all namespaces. - -### API Server audit configuration - -CIS requirements 1.2.22 to 1.2.25 are related to configuring audit logs for the API Server. When RKE2 is started with the `profile` flag set to `cis-1.6`, it will automatically configure hardened `--audit-log-` parameters in the API Server to pass those CIS checks. - -RKE2's default audit policy is configured to not log requests in the API Server. This is done to allow cluster operators flexibility to customize an audit policy that suits their auditing requirements and needs, as these are specific to each users' environment and policies. - -A default audit policy is created by RKE2 when started with the `profile` flag set to `cis-1.6`. The policy is defined in `/etc/rancher/rke2/audit-policy.yaml`. - -```yaml -apiVersion: audit.k8s.io/v1 -kind: Policy -metadata: - creationTimestamp: null -rules: -- level: None -``` - -To start logging requests to the API Server, at least `level` parameter must be modified, for example, to `Metadata`. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/). - -After adapting the audit policy, RKE2 must be restarted to load the new configuration. - -```shell -sudo systemctl restart rke2-server.service -``` - -API Server audit logs will be written to `/var/lib/rancher/rke2/server/logs/audit.log`. - -### Known issues - -The following are controls that RKE2 currently does not pass. Each gap will be explained and whether it can be passed through manual operator intervention or if it will be addressed in a future release. - -#### Control 1.1.12 -Ensure that the etcd data directory ownership is set to `etcd:etcd`. - -**Rationale** -etcd is a highly-available key-value store used by Kubernetes deployments for persistent storage of all of its REST API objects. This data directory should be protected from any unauthorized reads or writes. It should be owned by `etcd:etcd`. - -**Remediation** -This can be remediated by creating an `etcd` user and group as described above. - -#### Control 5.1.5 -Ensure that default service accounts are not actively used - -**Rationale** Kubernetes provides a `default` service account which is used by cluster workloads where no specific service account is assigned to the pod. - -Where access to the Kubernetes API from a pod is required, a specific service account should be created for that pod, and rights granted to that service account. - -The `default` service account should be configured such that it does not provide a service account token and does not have any explicit rights assignments. - -This can be remediated by updating the `automountServiceAccountToken` field to `false` for the `default` service account in each namespace. - -**Remediation** -You can manually update this field on service accounts in your cluster to pass the control as described above. - -#### Control 5.3.2 -Ensure that all Namespaces have Network Policies defined - -**Rationale** -Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints. - -Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace. - -**Remediation** -This can be remediated by setting `profile: "cis-1.6"` in RKE2 template configuration file. An example can be found below. - -### Reference Hardened RKE2 Template Configuration - -The reference template configuration is used in Rancher to create a hardened RKE2 custom cluster. This reference does not include other required **cluster configuration** directives which will vary depending on your environment. - -```yaml -apiVersion: provisioning.cattle.io/v1 -kind: Cluster -metadata: - name: - annotations: - {} -# key: string - labels: - {} -# key: string - namespace: fleet-default -spec: - defaultPodSecurityPolicyTemplateName: '' - kubernetesVersion: - localClusterAuthEndpoint: - caCerts: '' - enabled: false - fqdn: '' - rkeConfig: - chartValues: - rke2-canal: - {} - etcd: - disableSnapshots: false - s3: -# bucket: string -# cloudCredentialName: string -# endpoint: string -# endpointCA: string -# folder: string -# region: string -# skipSSLVerify: boolean - snapshotRetention: 5 - snapshotScheduleCron: 0 */5 * * * - machineGlobalConfig: - cni: canal - machinePools: -# - cloudCredentialSecretName: string -# controlPlaneRole: boolean -# displayName: string -# drainBeforeDelete: boolean -# etcdRole: boolean -# labels: -# key: string -# machineConfigRef: -# apiVersion: string -# fieldPath: string -# kind: string -# name: string -# namespace: string -# resourceVersion: string -# uid: string -# machineDeploymentAnnotations: -# key: string -# machineDeploymentLabels: -# key: string -# machineOS: string -# maxUnhealthy: string -# name: string -# nodeStartupTimeout: string -# paused: boolean -# quantity: int -# rollingUpdate: -# maxSurge: string -# maxUnavailable: string -# taints: -# - effect: string -# key: string -# timeAdded: string -# value: string -# unhealthyNodeTimeout: string -# unhealthyRange: string -# workerRole: boolean - machineSelectorConfig: - - config: - profile: cis-1.6 - protect-kernel-defaults: true -# - config: -# -# machineLabelSelector: -# matchExpressions: -# - key: string -# operator: string -# values: -# - string -# matchLabels: -# key: string - registries: - configs: - {} - #authConfigSecretName: string -# caBundle: string -# insecureSkipVerify: boolean -# tlsSecretName: string - mirrors: - {} - #endpoint: -# - string -# rewrite: -# key: string - upgradeStrategy: - controlPlaneConcurrency: 10% - controlPlaneDrainOptions: -# deleteEmptyDirData: boolean -# disableEviction: boolean -# enabled: boolean -# force: boolean -# gracePeriod: int -# ignoreDaemonSets: boolean -# ignoreErrors: boolean -# postDrainHooks: -# - annotation: string -# preDrainHooks: -# - annotation: string -# skipWaitForDeleteTimeoutSeconds: int -# timeout: int - workerConcurrency: 10% - workerDrainOptions: -# deleteEmptyDirData: boolean -# disableEviction: boolean -# enabled: boolean -# force: boolean -# gracePeriod: int -# ignoreDaemonSets: boolean -# ignoreErrors: boolean -# postDrainHooks: -# - annotation: string -# preDrainHooks: -# - annotation: string -# skipWaitForDeleteTimeoutSeconds: int -# timeout: int -# additionalManifest: string -# etcdSnapshotCreate: -# generation: int -# etcdSnapshotRestore: -# generation: int -# name: string -# restoreRKEConfig: string -# infrastructureRef: -# apiVersion: string -# fieldPath: string -# kind: string -# name: string -# namespace: string -# resourceVersion: string -# uid: string -# provisionGeneration: int -# rotateCertificates: -# generation: int -# services: -# - string -# rotateEncryptionKeys: -# generation: int - machineSelectorConfig: - - config: {} -# agentEnvVars: -# - name: string -# value: string -# cloudCredentialSecretName: string -# clusterAPIConfig: -# clusterName: string -# defaultClusterRoleForProjectMembers: string -# enableNetworkPolicy: boolean -# redeploySystemAgentGeneration: int -__clone: true -``` - -### Conclusion - -If you have followed this guide, your RKE2 custom cluster provisioned by Rancher will be configured to pass the CIS Kubernetes Benchmark. You can review our RKE2 CIS Benchmark Self-Assessment Guide [v1.6]({{}}/rancher/v2.6/en/security/hardening-guides/rke2-1.6-benchmark-2.6/) to understand how we verified each of the benchmarks and how you can do the same on your cluster. diff --git a/versioned_docs/version-2.6/security/security-scan/security-scan.md b/versioned_docs/version-2.6/security/security-scan/security-scan.md deleted file mode 100644 index c5a3cdb21d4..00000000000 --- a/versioned_docs/version-2.6/security/security-scan/security-scan.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Security Scans -weight: 299 ---- - -The documentation about CIS security scans has moved [here.]({{}}/rancher/v2.6/en/cis-scans) diff --git a/versioned_docs/version-2.6/security/security.md b/versioned_docs/version-2.6/security/security.md deleted file mode 100644 index c745f356c7c..00000000000 --- a/versioned_docs/version-2.6/security/security.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: Security -weight: 20 -aliases: - - /rancher/v2.x/en/security/ ---- - - - - - - - -
-

Security policy

-

Rancher Labs supports responsible disclosure, and endeavours to resolve all issues in a reasonable time frame.

-		 -

Reporting process

-

Please submit possible security issues by emailing security-rancher@suse.com .

-		 -

Announcements

-

Subscribe to the Rancher announcements forum for release updates.

-
- -Security is at the heart of all Rancher features. From integrating with all the popular authentication tools and services, to an enterprise grade [RBAC capability]({{}}/rancher/v2.6/en/admin-settings/rbac), Rancher makes your Kubernetes clusters even more secure. - -On this page, we provide security related documentation along with resources to help you secure your Rancher installation and your downstream Kubernetes clusters: - -- [NeuVector Integration with Rancher](#neuvector-integration-with-rancher) -- [Running a CIS security scan on a Kubernetes cluster](#running-a-cis-security-scan-on-a-kubernetes-cluster) -- [SELinux RPM](#selinux-rpm) -- [Guide to hardening Rancher installations](#rancher-hardening-guide) -- [The CIS Benchmark and self-assessment](#the-cis-benchmark-and-self-assessment) -- [Third-party penetration test reports](#third-party-penetration-test-reports) -- [Rancher Security Advisories and CVEs](#rancher-security-advisories-and-cves) -- [Kubernetes Security Best Practices](#kubernetes-security-best-practices) - -### NeuVector Integration with Rancher - -_New in v2.6.5_ - -NeuVector is an open-source, container-focused security application that is now integrated into Rancher. NeuVector provides production security, DevOps vulnerability protection, and a container firewall, et al. Please see the [Rancher docs]({{}}/rancher/v2.6/en/neuvector-integration) and the [NeuVector docs](https://open-docs.neuvector.com/) for more information. - -### Running a CIS Security Scan on a Kubernetes Cluster - -Rancher leverages [kube-bench](https://github.com/aquasecurity/kube-bench) to run a security scan to check whether Kubernetes is deployed according to security best practices as defined in the [CIS](https://www.cisecurity.org/cis-benchmarks/) (Center for Internet Security) Kubernetes Benchmark. - -The CIS Kubernetes Benchmark is a reference document that can be used to establish a secure configuration baseline for Kubernetes. - -The Center for Internet Security (CIS) is a 501(c\)(3) non-profit organization, formed in October 2000, with a mission to "identify, develop, validate, promote, and sustain best practice solutions for cyber defense and build and lead communities to enable an environment of trust in cyberspace". - -CIS Benchmarks are best practices for the secure configuration of a target system. CIS Benchmarks are developed through the generous volunteer efforts of subject matter experts, technology vendors, public and private community members, and the CIS Benchmark Development team. - -The Benchmark provides recommendations of two types: Automated and Manual. We run tests related to only Automated recommendations. - -When Rancher runs a CIS security scan on a cluster, it generates a report showing the results of each test, including a summary with the number of passed, skipped and failed tests. The report also includes remediation steps for any failed tests. - -For details, refer to the section on [security scans]({{}}/rancher/v2.6/en/cis-scans). - -### SELinux RPM - -[Security-Enhanced Linux (SELinux)](https://en.wikipedia.org/wiki/Security-Enhanced_Linux) is a security enhancement to Linux. After being historically used by government agencies, SELinux is now industry standard and is enabled by default on CentOS 7 and 8. - -We provide two RPMs (Red Hat packages) that enable Rancher products to function properly on SELinux-enforcing hosts: `rancher-selinux` and `rke2-selinux`. For details, see [this page]({{}}/rancher/v2.6/en/security/selinux). - -### Rancher Hardening Guide - -The Rancher Hardening Guide is based on controls and best practices found in the CIS Kubernetes Benchmark from the Center for Internet Security. - -The hardening guides provide prescriptive guidance for hardening a production installation of Rancher. See Rancher's guides for [Self Assessment of the CIS Kubernetes Benchmark](#the-cis-benchmark-and-self-sssessment) for the full list of security controls. - -> The hardening guides describe how to secure the nodes in your cluster, and it is recommended to follow a hardening guide before installing Kubernetes. - -Each version of the hardening guide is intended to be used with specific versions of the CIS Kubernetes Benchmark, Kubernetes, and Rancher. - -### The CIS Benchmark and Self-Assessment - -The benchmark self-assessment is a companion to the Rancher security hardening guide. While the hardening guide shows you how to harden the cluster, the benchmark guide is meant to help you evaluate the level of security of the hardened cluster. - -Because Rancher and RKE install Kubernetes services as Docker containers, many of the control verification checks in the CIS Kubernetes Benchmark don't apply. This guide will walk through the various controls and provide updated example commands to audit compliance in Rancher created clusters. The original benchmark documents can be downloaded from the [CIS website](https://www.cisecurity.org/benchmark/kubernetes/). - -Each version of Rancher's self-assessment guide corresponds to specific versions of the hardening guide, Rancher, Kubernetes, and the CIS Benchmark. - -### Third-party Penetration Test Reports - -Rancher periodically hires third parties to perform security audits and penetration tests of the Rancher 2.x software stack. The environments under test follow the Rancher provided hardening guides at the time of the testing. Results are posted when the third party has also verified fixes classified MEDIUM or above. - -Results: - -- [Cure53 Pen Test - July 2019](https://releases.rancher.com/documents/security/pen-tests/2019/RAN-01-cure53-report.final.pdf) -- [Untamed Theory Pen Test - March 2019](https://releases.rancher.com/documents/security/pen-tests/2019/UntamedTheory-Rancher_SecurityAssessment-20190712_v5.pdf) - -### Rancher Security Advisories and CVEs - -Rancher is committed to informing the community of security issues in our products. For the list of CVEs (Common Vulnerabilities and Exposures) for issues we have resolved, refer to [this page.](./cve) - -### Kubernetes Security Best Practices - -For recommendations on securing your Kubernetes cluster, refer to the [Kubernetes Security Best Practices](./best-practices) guide. diff --git a/versioned_docs/version-2.6/security/selinux/selinux.md b/versioned_docs/version-2.6/security/selinux/selinux.md deleted file mode 100644 index f2fa310b3ed..00000000000 --- a/versioned_docs/version-2.6/security/selinux/selinux.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: SELinux RPM -weight: 4 ---- - -[Security-Enhanced Linux (SELinux)](https://en.wikipedia.org/wiki/Security-Enhanced_Linux) is a security enhancement to Linux. - -Developed by Red Hat, it is an implementation of mandatory access controls (MAC) on Linux. Mandatory access controls allow an administrator of a system to define how applications and users can access different resources such as files, devices, networks and inter-process communication. SELinux also enhances security by making an OS restrictive by default. - -After being historically used by government agencies, SELinux is now industry standard and is enabled by default on CentOS 7 and 8. To check whether SELinux is enabled and enforcing on your system, use `getenforce`: - -``` -# getenforce -Enforcing -``` - -We provide two RPMs (Red Hat packages) that enable Rancher products to function properly on SELinux-enforcing hosts: `rancher-selinux` and `rke2-selinux`. - -- [rancher-selinux](#rancher-selinux) -- [rke2-selinux](#rke2-selinux) -- [Installing the rancher-selinux RPM](#installing-the-rancher-selinux-rpm) -- [Configuring the Logging Application to Work with SELinux](#configuring-the-logging-application-to-work-with-selinux) - -# rancher-selinux - -To allow Rancher to work with SELinux, some functionality has to be manually enabled for the SELinux nodes. To help with that, Rancher provides a SELinux RPM. - -The `rancher-selinux` RPM only contains policies for the [rancher-logging application.](https://github.com/rancher/charts/tree/dev-v2.5/charts/rancher-logging) - -The `rancher-selinux` GitHub repository is [here.](https://github.com/rancher/rancher-selinux) - -# rke2-selinux - -rke2-selinux provides policies for RKE2. It is installed automatically when the RKE2 installer script detects that it is running on an RPM-based distro. - -The `rke2-selinux` GitHub repository is [here.](https://github.com/rancher/rke2-selinux) - -For more information about installing RKE2 on SELinux-enabled hosts, see the [RKE2 documentation.](https://docs.rke2.io/install/methods/#rpm) - -# Installing the rancher-selinux RPM - -> **Requirements:** The rancher-selinux RPM was tested with CentOS 7 and 8. - -### 1. Set up the yum repo - -Set up the yum repo to install `rancher-selinux` directly on all hosts in the cluster. - -In order to use the RPM repository, on a CentOS 7 or RHEL 7 system, run the following bash snippet: - -``` -# cat << EOF > /etc/yum.repos.d/rancher.repo -[rancher] -name=Rancher -baseurl=https://rpm.rancher.io/rancher/production/centos/7/noarch -enabled=1 -gpgcheck=1 -gpgkey=https://rpm.rancher.io/public.key -EOF -``` - -In order to use the RPM repository, on a CentOS 8 or RHEL 8 system, run the following bash snippet: - -``` -# cat << EOF > /etc/yum.repos.d/rancher.repo -[rancher] -name=Rancher -baseurl=https://rpm.rancher.io/rancher/production/centos/8/noarch -enabled=1 -gpgcheck=1 -gpgkey=https://rpm.rancher.io/public.key -EOF -``` -### 2. Installing the RPM - -Install the RPM: - -``` -yum -y install rancher-selinux -``` - -# Configuring the Logging Application to Work with SELinux - -> **Requirements:** Logging v2 was tested with SELinux on RHEL/CentOS 7 and 8. - -Applications do not automatically work once the `rancher-selinux` RPM is installed on the host. They need to be configured to run in an allowed SELinux container domain provided by the RPM. - -To configure the `rancher-logging` chart to be SELinux aware, change `global.seLinux.enabled` to true in the `values.yaml` when installing the chart. diff --git a/versioned_docs/version-2.6/system-tools/system-tools.md b/versioned_docs/version-2.6/system-tools/system-tools.md deleted file mode 100644 index 58a4391cf5b..00000000000 --- a/versioned_docs/version-2.6/system-tools/system-tools.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: System Tools -weight: 22 ---- - -System Tools is a tool to perform operational tasks on [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) clusters or [installations of Rancher on an RKE cluster.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) The tasks include: - -* Collect logging and system metrics from nodes. -* Remove Kubernetes resources created by Rancher. - -The following commands are available: - -| Command | Description -|---|--- -| [logs](#logs) | Collect Kubernetes cluster component logs from nodes. -| [stats](#stats) | Stream system metrics from nodes. -| [remove](#remove) | Remove Kubernetes resources created by Rancher. - -# Download System Tools - -You can download the latest version of System Tools from the [GitHub releases page](https://github.com/rancher/system-tools/releases/latest). Download the version of `system-tools` for the OS that you are using to interact with the cluster. - -Operating System | Filename ------------------|----- -MacOS | `system-tools_darwin-amd64` -Linux | `system-tools_linux-amd64` -Windows | `system-tools_windows-amd64.exe` - -After you download the tools, complete the following actions: - -1. Rename the file to `system-tools`. - -1. Give the file executable permissions by running the following command: - - > **Using Windows?** - The file is already an executable, you can skip this step. - - ``` - chmod +x system-tools - ``` - -# Logs - -The logs subcommand will collect log files of core Kubernetes cluster components from nodes in [Rancher-launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) or nodes on an [RKE Kubernetes cluster that Rancher is installed on.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/). See [Troubleshooting]({{}}//rancher/v2.6/en/troubleshooting/) for a list of core Kubernetes cluster components. - -System Tools will use the provided kubeconfig file to deploy a DaemonSet, that will copy all the logfiles from the core Kubernetes cluster components and add them to a single tar file (`cluster-logs.tar` by default). If you only want to collect logging from a single node, you can specify the node by using `--node NODENAME` or `-n NODENAME`. - -### Usage - -``` -./system-tools_darwin-amd64 logs --kubeconfig -``` - -The following are the options for the logs command: - -| Option | Description -| ------------------------------------------------------ | ------------------------------------------------------ -| `--kubeconfig , -c ` | The cluster's kubeconfig file. -| `--output , -o cluster-logs.tar` | Name of the created tarball containing the logs. If no output filename is defined, the options defaults to `cluster-logs.tar`. -| `--node , -n node1` | Specify the nodes to collect the logs from. If no node is specified, logs from all nodes in the cluster will be collected. - -# Stats - -The stats subcommand will display system metrics from nodes in [Rancher-launched Kubernetes clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) or nodes in an [RKE Kubernetes cluster that Rancher is installed on.]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/). - -System Tools will deploy a DaemonSet, and run a predefined command based on `sar` (System Activity Report) to show system metrics. - -### Usage - -``` -./system-tools_darwin-amd64 stats --kubeconfig -``` - -The following are the options for the stats command: - -| Option | Description -| ------------------------------------------------------ | ------------------------------ -| `--kubeconfig , -c ` | The cluster's kubeconfig file. -| `--node , -n node1` | Specify the nodes to display the system metrics from. If no node is specified, logs from all nodes in the cluster will be displayed. -| `--stats-command value, -s value` | The command to run to display the system metrics. If no command is defined, the options defaults to `/usr/bin/sar -u -r -F 1 1`. - -# Remove - ->**Warning:** This command will remove data from your etcd nodes. Make sure you have created a [backup of etcd]({{}}/rancher/v2.6/en/backups/back-up-rancher) before executing the command. - -When you install Rancher on a Kubernetes cluster, it will create Kubernetes resources to run and to store configuration data. If you want to remove Rancher from your cluster, you can use the `remove` subcommand to remove the Kubernetes resources. When you use the `remove` subcommand, the following resources will be removed: - -- The Rancher deployment namespace (`cattle-system` by default). -- Any `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` that Rancher applied the `cattle.io/creator:norman` label to. Rancher applies this label to any resource that it creates. -- Labels, annotations, and finalizers. -- Rancher Deployment. -- Machines, clusters, projects, and user custom resource deployments (CRDs). -- All resources create under the `management.cattle.io` API Group. -- All CRDs created by Rancher v2.x. - ->**Using 2.0.8 or Earlier?** -> ->These versions of Rancher do not automatically delete the `serviceAccount`, `clusterRole`, and `clusterRoleBindings` resources after the job runs. You'll have to delete them yourself. - -### Usage - -When you run the command below, all the resources listed [above](#remove) will be removed from the cluster. - ->**Warning:** This command will remove data from your etcd nodes. Make sure you have created a [backup of etcd]({{}}/rancher/v2.6/en/backups/back-up-rancher) before executing the command. - -``` -./system-tools remove --kubeconfig --namespace -``` - -The following are the options for the `remove` command: - -| Option | Description -| ---------------------------------------------- | ------------ -| `--kubeconfig , -c ` | The cluster's kubeconfig file -| `--namespace , -n cattle-system` | Rancher 2.x deployment namespace (``). If no namespace is defined, the options defaults to `cattle-system`. -| `--force` | Skips the interactive removal confirmation and removes the Rancher deployment without prompt. diff --git a/versioned_docs/version-2.6/troubleshooting/dns/dns.md b/versioned_docs/version-2.6/troubleshooting/dns/dns.md deleted file mode 100644 index a1292df3e32..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/dns/dns.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -title: DNS -weight: 103 ---- - -The commands/steps listed on this page can be used to check name resolution issues in your cluster. - -Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. - -Before running the DNS checks, check the [default DNS provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/options/#default-dns-provider) for your cluster and make sure that [the overlay network is functioning correctly]({{}}/rancher/v2.6/en/troubleshooting/networking/#check-if-overlay-network-is-functioning-correctly) as this can also be the reason why DNS resolution (partly) fails. - -### Check if DNS pods are running - -``` -kubectl -n kube-system get pods -l k8s-app=kube-dns -``` - -Example output when using CoreDNS: -``` -NAME READY STATUS RESTARTS AGE -coredns-799dffd9c4-6jhlz 1/1 Running 0 76m -``` - -Example output when using kube-dns: -``` -NAME READY STATUS RESTARTS AGE -kube-dns-5fd74c7488-h6f7n 3/3 Running 0 4m13s -``` - -### Check if the DNS service is present with the correct cluster-ip - -``` -kubectl -n kube-system get svc -l k8s-app=kube-dns -``` - -``` -NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE -service/kube-dns ClusterIP 10.43.0.10 53/UDP,53/TCP 4m13s -``` - -### Check if domain names are resolving - -Check if internal cluster names are resolving (in this example, `kubernetes.default`), the IP shown after `Server:` should be the same as the `CLUSTER-IP` from the `kube-dns` service. - -``` -kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup kubernetes.default -``` - -Example output: -``` -Server: 10.43.0.10 -Address 1: 10.43.0.10 kube-dns.kube-system.svc.cluster.local - -Name: kubernetes.default -Address 1: 10.43.0.1 kubernetes.default.svc.cluster.local -pod "busybox" deleted -``` - -Check if external names are resolving (in this example, `www.google.com`) - -``` -kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup www.google.com -``` - -Example output: -``` -Server: 10.43.0.10 -Address 1: 10.43.0.10 kube-dns.kube-system.svc.cluster.local - -Name: www.google.com -Address 1: 2a00:1450:4009:80b::2004 lhr35s04-in-x04.1e100.net -Address 2: 216.58.211.100 ams15s32-in-f4.1e100.net -pod "busybox" deleted -``` - -If you want to check resolving of domain names on all of the hosts, execute the following steps: - -1. Save the following file as `ds-dnstest.yml` - - ``` - apiVersion: apps/v1 - kind: DaemonSet - metadata: - name: dnstest - spec: - selector: - matchLabels: - name: dnstest - template: - metadata: - labels: - name: dnstest - spec: - tolerations: - - operator: Exists - containers: - - image: busybox:1.28 - imagePullPolicy: Always - name: alpine - command: ["sh", "-c", "tail -f /dev/null"] - terminationMessagePath: /dev/termination-log - ``` - -2. Launch it using `kubectl create -f ds-dnstest.yml` -3. Wait until `kubectl rollout status ds/dnstest -w` returns: `daemon set "dnstest" successfully rolled out`. -4. Configure the environment variable `DOMAIN` to a fully qualified domain name (FQDN) that the host should be able to resolve (`www.google.com` is used as an example) and run the following command to let each container on every host resolve the configured domain name (it's a single line command). - - ``` - export DOMAIN=www.google.com; echo "=> Start DNS resolve test"; kubectl get pods -l name=dnstest --no-headers -o custom-columns=NAME:.metadata.name,HOSTIP:.status.hostIP | while read pod host; do kubectl exec $pod -- /bin/sh -c "nslookup $DOMAIN > /dev/null 2>&1"; RC=$?; if [ $RC -ne 0 ]; then echo $host cannot resolve $DOMAIN; fi; done; echo "=> End DNS resolve test" - ``` - -5. When this command has finished running, the output indicating everything is correct is: - - ``` - => Start DNS resolve test - => End DNS resolve test - ``` - -If you see error in the output, that means that the mentioned host(s) is/are not able to resolve the given FQDN. - -Example error output of a situation where host with IP 209.97.182.150 had the UDP ports blocked. - -``` -=> Start DNS resolve test -command terminated with exit code 1 -209.97.182.150 cannot resolve www.google.com -=> End DNS resolve test -``` - -Cleanup the alpine DaemonSet by running `kubectl delete ds/dnstest`. - -### CoreDNS specific - -#### Check CoreDNS logging - -``` -kubectl -n kube-system logs -l k8s-app=kube-dns -``` - -#### Check configuration - -CoreDNS configuration is stored in the configmap `coredns` in the `kube-system` namespace. - -``` -kubectl -n kube-system get configmap coredns -o go-template={{.data.Corefile}} -``` - -#### Check upstream nameservers in resolv.conf - -By default, the configured nameservers on the host (in `/etc/resolv.conf`) will be used as upstream nameservers for CoreDNS. You can check this file on the host or run the following Pod with `dnsPolicy` set to `Default`, which will inherit the `/etc/resolv.conf` from the host it is running on. - -``` -kubectl run -i --restart=Never --rm test-${RANDOM} --image=ubuntu --overrides='{"kind":"Pod", "apiVersion":"v1", "spec": {"dnsPolicy":"Default"}}' -- sh -c 'cat /etc/resolv.conf' -``` - -#### Enable query logging - -Enabling query logging can be done by enabling the [log plugin](https://coredns.io/plugins/log/) in the Corefile configuration in the configmap `coredns`. You can do so by using `kubectl -n kube-system edit configmap coredns` or use the command below to replace the configuration in place: - -``` -kubectl get configmap -n kube-system coredns -o json | sed -e 's_loadbalance_log\\n loadbalance_g' | kubectl apply -f - -``` - -All queries will now be logged and can be checked using the command in [Check CoreDNS logging](#check-coredns-logging). - -### kube-dns specific - -#### Check upstream nameservers in kubedns container - -By default, the configured nameservers on the host (in `/etc/resolv.conf`) will be used as upstream nameservers for kube-dns. Sometimes the host will run a local caching DNS nameserver, which means the address in `/etc/resolv.conf` will point to an address in the loopback range (`127.0.0.0/8`) which will be unreachable by the container. In case of Ubuntu 18.04, this is done by `systemd-resolved`. We detect if `systemd-resolved` is running, and will automatically use the `/etc/resolv.conf` file with the correct upstream nameservers (which is located at `/run/systemd/resolve/resolv.conf`). - -Use the following command to check the upstream nameservers used by the kubedns container: - -``` -kubectl -n kube-system get pods -l k8s-app=kube-dns --no-headers -o custom-columns=NAME:.metadata.name,HOSTIP:.status.hostIP | while read pod host; do echo "Pod ${pod} on host ${host}"; kubectl -n kube-system exec $pod -c kubedns cat /etc/resolv.conf; done -``` - -Example output: -``` -Pod kube-dns-667c7cb9dd-z4dsf on host x.x.x.x -nameserver 1.1.1.1 -nameserver 8.8.4.4 -``` - -If the output shows an address in the loopback range (`127.0.0.0/8`), you can correct this in two ways: - -* Make sure the correct nameservers are listed in `/etc/resolv.conf` on your nodes in the cluster, please consult your operating system documentation on how to do this. Make sure you execute this before provisioning a cluster, or reboot the nodes after making the modification. -* Configure the `kubelet` to use a different file for resolving names, by using `extra_args` as shown below (where `/run/resolvconf/resolv.conf` is the file with the correct nameservers): - -``` -services: - kubelet: - extra_args: - resolv-conf: "/run/resolvconf/resolv.conf" -``` - -> **Note:** As the `kubelet` is running inside a container, the path for files located in `/etc` and `/usr` are in `/host/etc` and `/host/usr` inside the `kubelet` container. - -See [Editing Cluster as YAML]({{}}/rancher/v2.6/en/cluster-admin/editing-clusters/#editing-clusters-with-yaml) how to apply this change. When the provisioning of the cluster has finished, you have to remove the kube-dns pod to activate the new setting in the pod: - -``` -kubectl delete pods -n kube-system -l k8s-app=kube-dns -pod "kube-dns-5fd74c7488-6pwsf" deleted -``` - -Try to resolve name again using [Check if domain names are resolving](#check-if-domain-names-are-resolving). - -If you want to check the kube-dns configuration in your cluster (for example, to check if there are different upstream nameservers configured), you can run the following command to list the kube-dns configuration: - -``` -kubectl -n kube-system get configmap kube-dns -o go-template='{{range $key, $value := .data}}{{ $key }}{{":"}}{{ $value }}{{"\n"}}{{end}}' -``` - -Example output: -``` -upstreamNameservers:["1.1.1.1"] -``` diff --git a/versioned_docs/version-2.6/troubleshooting/expired-webhook-certificates/expired-webhook-certificates.md b/versioned_docs/version-2.6/troubleshooting/expired-webhook-certificates/expired-webhook-certificates.md deleted file mode 100644 index 59a7bfbcc1f..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/expired-webhook-certificates/expired-webhook-certificates.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Rotation of Expired Webhook Certificates -weight: 120 ---- - -For Rancher versions that have `rancher-webhook` installed, these certificates will expire after one year. It will be necessary for you to rotate your webhook certificate when this occurs. - -Rancher will advise the community once there is a permanent solution in place for this known issue. Currently, there are two methods to work around this issue: - -##### 1. Users with cluster access, run the following commands: -``` -kubectl delete secret -n cattle-system cattle-webhook-tls -kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io --ignore-not-found=true rancher.cattle.io -kubectl delete pod -n cattle-system -l app=rancher-webhook -``` - -##### 2. Users with no cluster access via `kubectl`: - -1. Delete the `cattle-webhook-tls` secret in the `cattle-system` namespace in the local cluster. - -2. Delete the `rancher.cattle.io` mutating webhook - -3. Delete the `rancher-webhook` pod in the `cattle-system` namespace in the local cluster. - -**Note:** The webhook certificate expiration issue is not specific to `cattle-webhook-tls` as listed in the examples. You will fill in your expired certificate secret accordingly. diff --git a/versioned_docs/version-2.6/troubleshooting/imported-clusters/imported-clusters.md b/versioned_docs/version-2.6/troubleshooting/imported-clusters/imported-clusters.md deleted file mode 100644 index 18d0a0bd062..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/imported-clusters/imported-clusters.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Registered clusters -weight: 105 ---- - -The commands/steps listed on this page can be used to check clusters that you are registering or that are registered in Rancher. - -Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kubeconfig_from_imported_cluster.yml`) - -### Rancher agents - -Communication to the cluster (Kubernetes API via cattle-cluster-agent) and communication to the nodes is done through Rancher agents. - -If the cattle-cluster-agent cannot connect to the configured `server-url`, the cluster will remain in **Pending** state, showing `Waiting for full cluster configuration`. - -#### cattle-node-agent - -> Note: cattle-node-agents are only present in clusters created in Rancher with RKE. - -Check if the cattle-node-agent pods are present on each node, have status **Running** and don't have a high count of Restarts: - -``` -kubectl -n cattle-system get pods -l app=cattle-agent -o wide -``` - -Example output: - -``` -NAME READY STATUS RESTARTS AGE IP NODE -cattle-node-agent-4gc2p 1/1 Running 0 2h x.x.x.x worker-1 -cattle-node-agent-8cxkk 1/1 Running 0 2h x.x.x.x etcd-1 -cattle-node-agent-kzrlg 1/1 Running 0 2h x.x.x.x etcd-0 -cattle-node-agent-nclz9 1/1 Running 0 2h x.x.x.x controlplane-0 -cattle-node-agent-pwxp7 1/1 Running 0 2h x.x.x.x worker-0 -cattle-node-agent-t5484 1/1 Running 0 2h x.x.x.x controlplane-1 -cattle-node-agent-t8mtz 1/1 Running 0 2h x.x.x.x etcd-2 -``` - -Check logging of a specific cattle-node-agent pod or all cattle-node-agent pods: - -``` -kubectl -n cattle-system logs -l app=cattle-agent -``` - -#### cattle-cluster-agent - -Check if the cattle-cluster-agent pod is present in the cluster, has status **Running** and doesn't have a high count of Restarts: - -``` -kubectl -n cattle-system get pods -l app=cattle-cluster-agent -o wide -``` - -Example output: - -``` -NAME READY STATUS RESTARTS AGE IP NODE -cattle-cluster-agent-54d7c6c54d-ht9h4 1/1 Running 0 2h x.x.x.x worker-1 -``` - -Check logging of cattle-cluster-agent pod: - -``` -kubectl -n cattle-system logs -l app=cattle-cluster-agent -``` diff --git a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/controlplane/controlplane.md b/versioned_docs/version-2.6/troubleshooting/kubernetes-components/controlplane/controlplane.md deleted file mode 100644 index e27339cb8b5..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/controlplane/controlplane.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Troubleshooting Controlplane Nodes -weight: 2 ---- - -This section applies to nodes with the `controlplane` role. - -# Check if the Controlplane Containers are Running - -There are three specific containers launched on nodes with the `controlplane` role: - -* `kube-apiserver` -* `kube-controller-manager` -* `kube-scheduler` - -The containers should have status **Up**. The duration shown after **Up** is the time the container has been running. - -``` -docker ps -a -f=name='kube-apiserver|kube-controller-manager|kube-scheduler' -``` - -Example output: -``` -CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -26c7159abbcc rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kube-apiserver -f3d287ca4549 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kube-scheduler -bdf3898b8063 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kube-controller-manager -``` - -# Controlplane Container Logging - -> **Note:** If you added multiple nodes with the `controlplane` role, both `kube-controller-manager` and `kube-scheduler` use a leader election process to determine the leader. Only the current leader will log the performed actions. See [Kubernetes leader election]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-resources/#kubernetes-leader-election) how to retrieve the current leader. - -The logging of the containers can contain information on what the problem could be. - -``` -docker logs kube-apiserver -docker logs kube-controller-manager -docker logs kube-scheduler -``` - -# RKE2 Server Logging - -If Rancher provisions an RKE2 cluster that can't communicate with Rancher, you can run this command on a server node in the downstream cluster to get the RKE2 server logs: - -``` -journalctl -u rke2-server -f -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/etcd/etcd.md b/versioned_docs/version-2.6/troubleshooting/kubernetes-components/etcd/etcd.md deleted file mode 100644 index f83d241a08a..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/etcd/etcd.md +++ /dev/null @@ -1,365 +0,0 @@ ---- -title: Troubleshooting etcd Nodes -weight: 1 ---- - -This section contains commands and tips for troubleshooting nodes with the `etcd` role. - -This page covers the following topics: - -- [Checking if the etcd Container is Running](#checking-if-the-etcd-container-is-running) -- [etcd Container Logging](#etcd-container-logging) -- [etcd Cluster and Connectivity Checks](#etcd-cluster-and-connectivity-checks) - - [Check etcd Members on all Nodes](#check-etcd-members-on-all-nodes) - - [Check Endpoint Status](#check-endpoint-status) - - [Check Endpoint Health](#check-endpoint-health) - - [Check Connectivity on Port TCP/2379](#check-connectivity-on-port-tcp-2379) - - [Check Connectivity on Port TCP/2380](#check-connectivity-on-port-tcp-2380) -- [etcd Alarms](#etcd-alarms) -- [etcd Space Errors](#etcd-space-errors) -- [Log Level](#log-level) -- [etcd Content](#etcd-content) - - [Watch Streaming Events](#watch-streaming-events) - - [Query etcd Directly](#query-etcd-directly) -- [Replacing Unhealthy etcd Nodes](#replacing-unhealthy-etcd-nodes) - -# Checking if the etcd Container is Running - -The container for etcd should have status **Up**. The duration shown after **Up** is the time the container has been running. - -``` -docker ps -a -f=name=etcd$ -``` - -Example output: -``` -CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -605a124503b9 rancher/coreos-etcd:v3.2.18 "/usr/local/bin/et..." 2 hours ago Up 2 hours etcd -``` - -# etcd Container Logging - -The logging of the container can contain information on what the problem could be. - -``` -docker logs etcd -``` -| Log | Explanation | -|-----|------------------| -| `health check for peer xxx could not connect: dial tcp IP:2380: getsockopt: connection refused` | A connection to the address shown on port 2380 cannot be established. Check if the etcd container is running on the host with the address shown. | -| `xxx is starting a new election at term x` | The etcd cluster has lost its quorum and is trying to establish a new leader. This can happen when the majority of the nodes running etcd go down/unreachable. | -| `connection error: desc = "transport: Error while dialing dial tcp 0.0.0.0:2379: i/o timeout"; Reconnecting to {0.0.0.0:2379 0 }` | The host firewall is preventing network communication. | -| `rafthttp: request cluster ID mismatch` | The node with the etcd instance logging `rafthttp: request cluster ID mismatch` is trying to join a cluster that has already been formed with another peer. The node should be removed from the cluster, and re-added. | -| `rafthttp: failed to find member` | The cluster state (`/var/lib/etcd`) contains wrong information to join the cluster. The node should be removed from the cluster, the state directory should be cleaned and the node should be re-added. - -# etcd Cluster and Connectivity Checks - -The address where etcd is listening depends on the address configuration of the host etcd is running on. If an internal address is configured for the host etcd is running on, the endpoint for `etcdctl` needs to be specified explicitly. If any of the commands respond with `Error: context deadline exceeded`, the etcd instance is unhealthy (either quorum is lost or the instance is not correctly joined in the cluster) - -### Check etcd Members on all Nodes - -Output should contain all the nodes with the `etcd` role and the output should be identical on all nodes. - -Command: -``` -docker exec etcd etcdctl member list -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list" -``` - -Example output: -``` -xxx, started, etcd-xxx, https://IP:2380, https://IP:2379,https://IP:4001 -xxx, started, etcd-xxx, https://IP:2380, https://IP:2379,https://IP:4001 -xxx, started, etcd-xxx, https://IP:2380, https://IP:2379,https://IP:4001 -``` - -### Check Endpoint Status - -The values for `RAFT TERM` should be equal and `RAFT INDEX` should be not be too far apart from each other. - -Command: -``` -docker exec -e ETCDCTL_ENDPOINTS=$(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") etcd etcdctl endpoint status --write-out table -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd etcdctl endpoint status --endpoints=$(docker exec etcd /bin/sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") --write-out table -``` - -Example output: -``` -+-----------------+------------------+---------+---------+-----------+-----------+------------+ -| ENDPOINT | ID | VERSION | DB SIZE | IS LEADER | RAFT TERM | RAFT INDEX | -+-----------------+------------------+---------+---------+-----------+-----------+------------+ -| https://IP:2379 | 333ef673fc4add56 | 3.2.18 | 24 MB | false | 72 | 66887 | -| https://IP:2379 | 5feed52d940ce4cf | 3.2.18 | 24 MB | true | 72 | 66887 | -| https://IP:2379 | db6b3bdb559a848d | 3.2.18 | 25 MB | false | 72 | 66887 | -+-----------------+------------------+---------+---------+-----------+-----------+------------+ -``` - -### Check Endpoint Health - -Command: -``` -docker exec -e ETCDCTL_ENDPOINTS=$(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") etcd etcdctl endpoint health -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd etcdctl endpoint health --endpoints=$(docker exec etcd /bin/sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") -``` - -Example output: -``` -https://IP:2379 is healthy: successfully committed proposal: took = 2.113189ms -https://IP:2379 is healthy: successfully committed proposal: took = 2.649963ms -https://IP:2379 is healthy: successfully committed proposal: took = 2.451201ms -``` - -### Check Connectivity on Port TCP/2379 - -Command: -``` -for endpoint in $(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f5"); do - echo "Validating connection to ${endpoint}/health" - docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl -s -w "\n" --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) "${endpoint}/health" -done -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -for endpoint in $(docker exec etcd /bin/sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list | cut -d, -f5"); do - echo "Validating connection to ${endpoint}/health"; - docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl -s -w "\n" --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) "${endpoint}/health" -done -``` - -Example output: -``` -Validating connection to https://IP:2379/health -{"health": "true"} -Validating connection to https://IP:2379/health -{"health": "true"} -Validating connection to https://IP:2379/health -{"health": "true"} -``` - -### Check Connectivity on Port TCP/2380 - -Command: -``` -for endpoint in $(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f4"); do - echo "Validating connection to ${endpoint}/version"; - docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl --http1.1 -s -w "\n" --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) "${endpoint}/version" -done -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -for endpoint in $(docker exec etcd /bin/sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list | cut -d, -f4"); do - echo "Validating connection to ${endpoint}/version"; - docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl --http1.1 -s -w "\n" --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) "${endpoint}/version" -done -``` - -Example output: -``` -Validating connection to https://IP:2380/version -{"etcdserver":"3.2.18","etcdcluster":"3.2.0"} -Validating connection to https://IP:2380/version -{"etcdserver":"3.2.18","etcdcluster":"3.2.0"} -Validating connection to https://IP:2380/version -{"etcdserver":"3.2.18","etcdcluster":"3.2.0"} -``` - -# etcd Alarms - -etcd will trigger alarms, for instance when it runs out of space. - -Command: -``` -docker exec etcd etcdctl alarm list -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT alarm list" -``` - -Example output when NOSPACE alarm is triggered: -``` -memberID:x alarm:NOSPACE -memberID:x alarm:NOSPACE -memberID:x alarm:NOSPACE -``` - -# etcd Space Errors - -Related error messages are `etcdserver: mvcc: database space exceeded` or `applying raft message exceeded backend quota`. Alarm `NOSPACE` will be triggered. - -Resolutions: - -- [Compact the Keyspace](#compact-the-keyspace) -- [Defrag All etcd Members](#defrag-all-etcd-members) -- [Check Endpoint Status](#check-endpoint-status) -- [Disarm Alarm](#disarm-alarm) - -### Compact the Keyspace - -Command: -``` -rev=$(docker exec etcd etcdctl endpoint status --write-out json | egrep -o '"revision":[0-9]*' | egrep -o '[0-9]*') -docker exec etcd etcdctl compact "$rev" -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -rev=$(docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT endpoint status --write-out json | egrep -o '\"revision\":[0-9]*' | egrep -o '[0-9]*'") -docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT compact \"$rev\"" -``` - -Example output: -``` -compacted revision xxx -``` - -### Defrag All etcd Members - -Command: -``` -docker exec -e ETCDCTL_ENDPOINTS=$(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") etcd etcdctl defrag -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd sh -c "etcdctl defrag --endpoints=$(docker exec etcd /bin/sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','")" -``` - -Example output: -``` -Finished defragmenting etcd member[https://IP:2379] -Finished defragmenting etcd member[https://IP:2379] -Finished defragmenting etcd member[https://IP:2379] -``` - -### Check Endpoint Status - -Command: -``` -docker exec -e ETCDCTL_ENDPOINTS=$(docker exec etcd /bin/sh -c "etcdctl member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") etcd etcdctl endpoint status --write-out table -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd sh -c "etcdctl endpoint status --endpoints=$(docker exec etcd /bin/sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT member list | cut -d, -f5 | sed -e 's/ //g' | paste -sd ','") --write-out table" -``` - -Example output: -``` -+-----------------+------------------+---------+---------+-----------+-----------+------------+ -| ENDPOINT | ID | VERSION | DB SIZE | IS LEADER | RAFT TERM | RAFT INDEX | -+-----------------+------------------+---------+---------+-----------+-----------+------------+ -| https://IP:2379 | e973e4419737125 | 3.2.18 | 553 kB | false | 32 | 2449410 | -| https://IP:2379 | 4a509c997b26c206 | 3.2.18 | 553 kB | false | 32 | 2449410 | -| https://IP:2379 | b217e736575e9dd3 | 3.2.18 | 553 kB | true | 32 | 2449410 | -+-----------------+------------------+---------+---------+-----------+-----------+------------+ -``` - -### Disarm Alarm - -After verifying that the DB size went down after compaction and defragmenting, the alarm needs to be disarmed for etcd to allow writes again. - -Command: -``` -docker exec etcd etcdctl alarm list -docker exec etcd etcdctl alarm disarm -docker exec etcd etcdctl alarm list -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT alarm list" -docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT alarm disarm" -docker exec etcd sh -c "etcdctl --endpoints=\$ETCDCTL_ENDPOINT alarm list" -``` - -Example output: -``` -docker exec etcd etcdctl alarm list -memberID:x alarm:NOSPACE -memberID:x alarm:NOSPACE -memberID:x alarm:NOSPACE -docker exec etcd etcdctl alarm disarm -docker exec etcd etcdctl alarm list -``` - -# Log Level - -The log level of etcd can be changed dynamically via the API. You can configure debug logging using the commands below. - -Command: -``` -docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl -s -XPUT -d '{"Level":"DEBUG"}' --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) $(docker exec etcd printenv ETCDCTL_ENDPOINTS)/config/local/log -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl -s -XPUT -d '{"Level":"DEBUG"}' --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) $(docker exec etcd printenv ETCDCTL_ENDPOINT)/config/local/log -``` - -To reset the log level back to the default (`INFO`), you can use the following command. - -Command: -``` -docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl -s -XPUT -d '{"Level":"INFO"}' --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) $(docker exec etcd printenv ETCDCTL_ENDPOINTS)/config/local/log -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker run --net=host -v $(docker inspect kubelet --format '{{ range .Mounts }}{{ if eq .Destination "/etc/kubernetes" }}{{ .Source }}{{ end }}{{ end }}')/ssl:/etc/kubernetes/ssl:ro appropriate/curl -s -XPUT -d '{"Level":"INFO"}' --cacert $(docker exec etcd printenv ETCDCTL_CACERT) --cert $(docker exec etcd printenv ETCDCTL_CERT) --key $(docker exec etcd printenv ETCDCTL_KEY) $(docker exec etcd printenv ETCDCTL_ENDPOINT)/config/local/log -``` - -# etcd Content - -If you want to investigate the contents of your etcd, you can either watch streaming events or you can query etcd directly, see below for examples. - -### Watch Streaming Events - -Command: -``` -docker exec etcd etcdctl watch --prefix /registry -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd etcdctl --endpoints=\$ETCDCTL_ENDPOINT watch --prefix /registry -``` - -If you only want to see the affected keys (and not the binary data), you can append `| grep -a ^/registry` to the command to filter for keys only. - -### Query etcd Directly - -Command: -``` -docker exec etcd etcdctl get /registry --prefix=true --keys-only -``` - -Command when using etcd version lower than 3.3.x (Kubernetes 1.13.x and lower) and `--internal-address` was specified when adding the node: -``` -docker exec etcd etcdctl --endpoints=\$ETCDCTL_ENDPOINT get /registry --prefix=true --keys-only -``` - -You can process the data to get a summary of count per key, using the command below: - -``` -docker exec etcd etcdctl get /registry --prefix=true --keys-only | grep -v ^$ | awk -F'/' '{ if ($3 ~ /cattle.io/) {h[$3"/"$4]++} else { h[$3]++ }} END { for(k in h) print h[k], k }' | sort -nr -``` - -# Replacing Unhealthy etcd Nodes - -When a node in your etcd cluster becomes unhealthy, the recommended approach is to fix or remove the failed or unhealthy node before adding a new etcd node to the cluster. diff --git a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/kubernetes-components.md b/versioned_docs/version-2.6/troubleshooting/kubernetes-components/kubernetes-components.md deleted file mode 100644 index 0b6fd969dbc..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/kubernetes-components.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Kubernetes Components -weight: 100 ---- - -The commands and steps listed in this section apply to the core Kubernetes components on [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) clusters. - -This section includes troubleshooting tips in the following categories: - -- [Troubleshooting etcd Nodes]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-components/etcd) -- [Troubleshooting Controlplane Nodes]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-components/controlplane) -- [Troubleshooting nginx-proxy Nodes]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-components/nginx-proxy) -- [Troubleshooting Worker Nodes and Generic Components]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-components/worker-and-generic) - -# Kubernetes Component Diagram - -![Cluster diagram]({{}}/img/rancher/clusterdiagram.svg)
-Lines show the traffic flow between components. Colors are used purely for visual aid \ No newline at end of file diff --git a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/nginx-proxy/nginx-proxy.md b/versioned_docs/version-2.6/troubleshooting/kubernetes-components/nginx-proxy/nginx-proxy.md deleted file mode 100644 index 70505e96280..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/nginx-proxy/nginx-proxy.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Troubleshooting nginx-proxy -weight: 3 ---- - -The `nginx-proxy` container is deployed on every node that does not have the `controlplane` role. It provides access to all the nodes with the `controlplane` role by dynamically generating the NGINX configuration based on available nodes with the `controlplane` role. - -# Check if the Container is Running - -The container is called `nginx-proxy` and should have status `Up`. The duration shown after `Up` is the time the container has been running. - -``` -docker ps -a -f=name=nginx-proxy -``` - -Example output: - -``` -docker ps -a -f=name=nginx-proxy -CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -c3e933687c0e rancher/rke-tools:v0.1.15 "nginx-proxy CP_HO..." 3 hours ago Up 3 hours nginx-proxy -``` - -# Check Generated NGINX Configuration - -The generated configuration should include the IP addresses of the nodes with the `controlplane` role. The configuration can be checked using the following command: - -``` -docker exec nginx-proxy cat /etc/nginx/nginx.conf -``` - -Example output: -``` -error_log stderr notice; - -worker_processes auto; -events { - multi_accept on; - use epoll; - worker_connections 1024; -} - -stream { - upstream kube_apiserver { - - server ip_of_controlplane_node1:6443; - - server ip_of_controlplane_node2:6443; - - } - - server { - listen 6443; - proxy_pass kube_apiserver; - proxy_timeout 30; - proxy_connect_timeout 2s; - - } - -} -``` - -# nginx-proxy Container Logging - -The logging of the containers can contain information on what the problem could be. - -``` -docker logs nginx-proxy -``` \ No newline at end of file diff --git a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/worker-and-generic/worker-and-generic.md b/versioned_docs/version-2.6/troubleshooting/kubernetes-components/worker-and-generic/worker-and-generic.md deleted file mode 100644 index 28ee4499bb4..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/kubernetes-components/worker-and-generic/worker-and-generic.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Troubleshooting Worker Nodes and Generic Components -weight: 4 ---- - -This section applies to every node as it includes components that run on nodes with any role. - -# Check if the Containers are Running - -There are two specific containers launched on nodes with the `worker` role: - -* kubelet -* kube-proxy - -The containers should have status `Up`. The duration shown after `Up` is the time the container has been running. - -``` -docker ps -a -f=name='kubelet|kube-proxy' -``` - -Example output: -``` -CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -158d0dcc33a5 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kube-proxy -a30717ecfb55 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kubelet -``` - -# Container Logging - -The logging of the containers can contain information on what the problem could be. - -``` -docker logs kubelet -docker logs kube-proxy -``` diff --git a/versioned_docs/version-2.6/troubleshooting/kubernetes-resources/kubernetes-resources.md b/versioned_docs/version-2.6/troubleshooting/kubernetes-resources/kubernetes-resources.md deleted file mode 100644 index 450f02f85df..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/kubernetes-resources/kubernetes-resources.md +++ /dev/null @@ -1,271 +0,0 @@ ---- -title: Kubernetes resources -weight: 101 ---- - -The commands/steps listed on this page can be used to check the most important Kubernetes resources and apply to [Rancher Launched Kubernetes]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/) clusters. - -Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. - -- [Nodes](#nodes) - - [Get nodes](#get-nodes) - - [Get node conditions](#get-node-conditions) -- [Kubernetes leader election](#kubernetes-leader-election) - - [Kubernetes controller manager leader](#kubernetes-controller-manager-leader) - - [Kubernetes scheduler leader](#kubernetes-scheduler-leader) -- [Ingress controller](#ingress-controller) - - [Pod details](#pod-details) - - [Pod container logs](#pod-container-logs) - - [Namespace events](#namespace-events) - - [Debug logging](#debug-logging) - - [Check configuration](#check-configuration) -- [Rancher agents](#rancher-agents) - - [cattle-node-agent](#cattle-node-agent) - - [cattle-cluster-agent](#cattle-cluster-agent) -- [Jobs and pods](#jobs-and-pods) - - [Check that pods or jobs have status Running/Completed](#check-that-pods-or-jobs-have-status-running-completed) - - [Describe pod](#describe-pod) - - [Pod container logs](#pod-container-logs) - - [Describe job](#describe-job) - - [Logs from the containers of pods of the job](#logs-from-the-containers-of-pods-of-the-job) - - [Evicted pods](#evicted-pods) - - [Job does not complete](#job-does-not-complete) - -# Nodes - -### Get nodes - -Run the command below and check the following: - -- All nodes in your cluster should be listed, make sure there is not one missing. -- All nodes should have the **Ready** status (if not in **Ready** state, check the `kubelet` container logs on that node using `docker logs kubelet`) -- Check if all nodes report the correct version. -- Check if OS/Kernel/Docker values are shown as expected (possibly you can relate issues due to upgraded OS/Kernel/Docker) - - -``` -kubectl get nodes -o wide -``` - -Example output: - -``` -NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME -controlplane-0 Ready controlplane 31m v1.13.5 138.68.188.91 Ubuntu 18.04.2 LTS 4.15.0-47-generic docker://18.9.5 -etcd-0 Ready etcd 31m v1.13.5 138.68.180.33 Ubuntu 18.04.2 LTS 4.15.0-47-generic docker://18.9.5 -worker-0 Ready worker 30m v1.13.5 139.59.179.88 Ubuntu 18.04.2 LTS 4.15.0-47-generic docker://18.9.5 -``` - -### Get node conditions - -Run the command below to list nodes with [Node Conditions](https://kubernetes.io/docs/concepts/architecture/nodes/#condition) - -``` -kubectl get nodes -o go-template='{{range .items}}{{$node := .}}{{range .status.conditions}}{{$node.metadata.name}}{{": "}}{{.type}}{{":"}}{{.status}}{{"\n"}}{{end}}{{end}}' -``` - -Run the command below to list nodes with [Node Conditions](https://kubernetes.io/docs/concepts/architecture/nodes/#condition) that are active that could prevent normal operation. - -``` -kubectl get nodes -o go-template='{{range .items}}{{$node := .}}{{range .status.conditions}}{{if ne .type "Ready"}}{{if eq .status "True"}}{{$node.metadata.name}}{{": "}}{{.type}}{{":"}}{{.status}}{{"\n"}}{{end}}{{else}}{{if ne .status "True"}}{{$node.metadata.name}}{{": "}}{{.type}}{{": "}}{{.status}}{{"\n"}}{{end}}{{end}}{{end}}{{end}}' -``` - -Example output: - -``` -worker-0: DiskPressure:True -``` - -# Kubernetes leader election - -### Kubernetes Controller Manager leader - -The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `kube-controller-manager` endpoint (in this example, `controlplane-0`). - -``` -kubectl -n kube-system get endpoints kube-controller-manager -o jsonpath='{.metadata.annotations.control-plane\.alpha\.kubernetes\.io/leader}' -{"holderIdentity":"controlplane-0_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","leaseDurationSeconds":15,"acquireTime":"2018-12-27T08:59:45Z","renewTime":"2018-12-27T09:44:57Z","leaderTransitions":0}> -``` - -### Kubernetes Scheduler leader - -The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `kube-scheduler` endpoint (in this example, `controlplane-0`). - -``` -kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.annotations.control-plane\.alpha\.kubernetes\.io/leader}' -{"holderIdentity":"controlplane-0_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","leaseDurationSeconds":15,"acquireTime":"2018-12-27T08:59:45Z","renewTime":"2018-12-27T09:44:57Z","leaderTransitions":0}> -``` - -# Ingress Controller - -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. - -Check if the pods are running on all nodes: - -``` -kubectl -n ingress-nginx get pods -o wide -``` - -Example output: - -``` -kubectl -n ingress-nginx get pods -o wide -NAME READY STATUS RESTARTS AGE IP NODE -default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 -``` - -If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. - -### Pod details - -``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx -``` - -### Pod container logs - -``` -kubectl -n ingress-nginx logs -l app=ingress-nginx -``` - -### Namespace events - -``` -kubectl -n ingress-nginx get events -``` - -### Debug logging - -To enable debug logging: - -``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' -``` - -### Check configuration - -Retrieve generated configuration in each pod: - -``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done -``` - -# Rancher agents - -Communication to the cluster (Kubernetes API via `cattle-cluster-agent`) and communication to the nodes (cluster provisioning via `cattle-node-agent`) is done through Rancher agents. - -#### cattle-node-agent - -Check if the cattle-node-agent pods are present on each node, have status **Running** and don't have a high count of Restarts: - -``` -kubectl -n cattle-system get pods -l app=cattle-agent -o wide -``` - -Example output: - -``` -NAME READY STATUS RESTARTS AGE IP NODE -cattle-node-agent-4gc2p 1/1 Running 0 2h x.x.x.x worker-1 -cattle-node-agent-8cxkk 1/1 Running 0 2h x.x.x.x etcd-1 -cattle-node-agent-kzrlg 1/1 Running 0 2h x.x.x.x etcd-0 -cattle-node-agent-nclz9 1/1 Running 0 2h x.x.x.x controlplane-0 -cattle-node-agent-pwxp7 1/1 Running 0 2h x.x.x.x worker-0 -cattle-node-agent-t5484 1/1 Running 0 2h x.x.x.x controlplane-1 -cattle-node-agent-t8mtz 1/1 Running 0 2h x.x.x.x etcd-2 -``` - -Check logging of a specific cattle-node-agent pod or all cattle-node-agent pods: - -``` -kubectl -n cattle-system logs -l app=cattle-agent -``` - -#### cattle-cluster-agent - -Check if the cattle-cluster-agent pod is present in the cluster, has status **Running** and doesn't have a high count of Restarts: - -``` -kubectl -n cattle-system get pods -l app=cattle-cluster-agent -o wide -``` - -Example output: - -``` -NAME READY STATUS RESTARTS AGE IP NODE -cattle-cluster-agent-54d7c6c54d-ht9h4 1/1 Running 0 2h x.x.x.x worker-1 -``` - -Check logging of cattle-cluster-agent pod: - -``` -kubectl -n cattle-system logs -l app=cattle-cluster-agent -``` - -# Jobs and Pods - -### Check that pods or jobs have status **Running**/**Completed** - -To check, run the command: - -``` -kubectl get pods --all-namespaces -``` - -If a pod is not in **Running** state, you can dig into the root cause by running: - -### Describe pod - -``` -kubectl describe pod POD_NAME -n NAMESPACE -``` - -### Pod container logs - -``` -kubectl logs POD_NAME -n NAMESPACE -``` - -If a job is not in **Completed** state, you can dig into the root cause by running: - -### Describe job - -``` -kubectl describe job JOB_NAME -n NAMESPACE -``` - -### Logs from the containers of pods of the job - -``` -kubectl logs -l job-name=JOB_NAME -n NAMESPACE -``` - -### Evicted pods - -Pods can be evicted based on [eviction signals](https://kubernetes.io/docs/tasks/administer-cluster/out-of-resource/#eviction-policy). - -Retrieve a list of evicted pods (podname and namespace): - -``` -kubectl get pods --all-namespaces -o go-template='{{range .items}}{{if eq .status.phase "Failed"}}{{if eq .status.reason "Evicted"}}{{.metadata.name}}{{" "}}{{.metadata.namespace}}{{"\n"}}{{end}}{{end}}{{end}}' -``` - -To delete all evicted pods: - -``` -kubectl get pods --all-namespaces -o go-template='{{range .items}}{{if eq .status.phase "Failed"}}{{if eq .status.reason "Evicted"}}{{.metadata.name}}{{" "}}{{.metadata.namespace}}{{"\n"}}{{end}}{{end}}{{end}}' | while read epod enamespace; do kubectl -n $enamespace delete pod $epod; done -``` - -Retrieve a list of evicted pods, scheduled node and the reason: - -``` -kubectl get pods --all-namespaces -o go-template='{{range .items}}{{if eq .status.phase "Failed"}}{{if eq .status.reason "Evicted"}}{{.metadata.name}}{{" "}}{{.metadata.namespace}}{{"\n"}}{{end}}{{end}}{{end}}' | while read epod enamespace; do kubectl -n $enamespace get pod $epod -o=custom-columns=NAME:.metadata.name,NODE:.spec.nodeName,MSG:.status.message; done -``` - -### Job does not complete - -If you have enabled Istio, and you are having issues with a Job you deployed not completing, you will need to add an annotation to your pod using [these steps.]({{}}/rancher/v2.6/en/istio/setup/enable-istio-in-namespace) - -Since Istio Sidecars run indefinitely, a Job cannot be considered complete even after its task has completed. This is a temporary workaround and will disable Istio for any traffic to/from the annotated Pod. Keep in mind this may not allow you to continue to use a Job for integration testing, as the Job will not have access to the service mesh. \ No newline at end of file diff --git a/versioned_docs/version-2.6/troubleshooting/logging/logging.md b/versioned_docs/version-2.6/troubleshooting/logging/logging.md deleted file mode 100644 index 13a7a752bac..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/logging/logging.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Logging -weight: 110 ---- - -The following log levels are used in Rancher: - -| Name | Description | -|---------|-------------| -| `info` | Logs informational messages. This is the default log level. | -| `debug` | Logs more detailed messages that can be used to debug. | -| `trace` | Logs very detailed messages on internal functions. This is very verbose and can contain sensitive information. | - -### How to configure a log level - -* Kubernetes install - * Configure debug log level -``` -$ KUBECONFIG=./kube_config_cluster.yml -$ kubectl -n cattle-system get pods -l app=rancher --no-headers -o custom-columns=name:.metadata.name | while read rancherpod; do kubectl -n cattle-system exec $rancherpod -c rancher -- loglevel --set debug; done -OK -OK -OK -$ kubectl -n cattle-system logs -l app=rancher -c rancher -``` - - * Configure info log level -``` -$ KUBECONFIG=./kube_config_cluster.yml -$ kubectl -n cattle-system get pods -l app=rancher --no-headers -o custom-columns=name:.metadata.name | while read rancherpod; do kubectl -n cattle-system exec $rancherpod -c rancher -- loglevel --set info; done -OK -OK -OK -``` - -* Docker Install - * Configure debug log level -``` -$ docker exec -ti loglevel --set debug -OK -$ docker logs -f -``` - - * Configure info log level -``` -$ docker exec -ti loglevel --set info -OK -``` diff --git a/versioned_docs/version-2.6/troubleshooting/networking/networking.md b/versioned_docs/version-2.6/troubleshooting/networking/networking.md deleted file mode 100644 index a184369afe3..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/networking/networking.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: Networking -weight: 102 ---- - -The commands/steps listed on this page can be used to check networking related issues in your cluster. - -Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. - -### Double check if all the required ports are opened in your (host) firewall - -Double check if all the [required ports]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. -### Check if overlay network is functioning correctly - -The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod. - -To test the overlay network, you can launch the following `DaemonSet` definition. This will run a `swiss-army-knife` container on every host (image was developed by Rancher engineers and can be found here: https://github.com/rancherlabs/swiss-army-knife), which we will use to run a `ping` test between containers on all hosts. - -> **Note:** This container [does not support ARM nodes](https://github.com/leodotcloud/swiss-army-knife/issues/18), such as a Raspberry Pi. This will be seen in the pod logs as `exec user process caused: exec format error`. - -1. Save the following file as `overlaytest.yml` - - ``` - apiVersion: apps/v1 - kind: DaemonSet - metadata: - name: overlaytest - spec: - selector: - matchLabels: - name: overlaytest - template: - metadata: - labels: - name: overlaytest - spec: - tolerations: - - operator: Exists - containers: - - image: rancherlabs/swiss-army-knife - imagePullPolicy: Always - name: overlaytest - command: ["sh", "-c", "tail -f /dev/null"] - terminationMessagePath: /dev/termination-log - - ``` - -2. Launch it using `kubectl create -f overlaytest.yml` -3. Wait until `kubectl rollout status ds/overlaytest -w` returns: `daemon set "overlaytest" successfully rolled out`. -4. Run the following script, from the same location. It will have each `overlaytest` container on every host ping each other: - ``` - #!/bin/bash - echo "=> Start network overlay test" - kubectl get pods -l name=overlaytest -o jsonpath='{range .items[*]}{@.metadata.name}{" "}{@.spec.nodeName}{"\n"}{end}' | - while read spod shost - do kubectl get pods -l name=overlaytest -o jsonpath='{range .items[*]}{@.status.podIP}{" "}{@.spec.nodeName}{"\n"}{end}' | - while read tip thost - do kubectl --request-timeout='10s' exec $spod -c overlaytest -- /bin/sh -c "ping -c2 $tip > /dev/null 2>&1" - RC=$? - if [ $RC -ne 0 ] - then echo FAIL: $spod on $shost cannot reach pod IP $tip on $thost - else echo $shost can reach $thost - fi - done - done - echo "=> End network overlay test" - ``` - -5. When this command has finished running, it will output the state of each route: - - ``` - => Start network overlay test - Error from server (NotFound): pods "wk2" not found - FAIL: overlaytest-5bglp on wk2 cannot reach pod IP 10.42.7.3 on wk2 - Error from server (NotFound): pods "wk2" not found - FAIL: overlaytest-5bglp on wk2 cannot reach pod IP 10.42.0.5 on cp1 - Error from server (NotFound): pods "wk2" not found - FAIL: overlaytest-5bglp on wk2 cannot reach pod IP 10.42.2.12 on wk1 - command terminated with exit code 1 - FAIL: overlaytest-v4qkl on cp1 cannot reach pod IP 10.42.7.3 on wk2 - cp1 can reach cp1 - cp1 can reach wk1 - command terminated with exit code 1 - FAIL: overlaytest-xpxwp on wk1 cannot reach pod IP 10.42.7.3 on wk2 - wk1 can reach cp1 - wk1 can reach wk1 - => End network overlay test - ``` - If you see error in the output, there is some issue with the route between the pods on the two hosts. In the above output the node `wk2` has no connectivity over the overlay network. This could be because the [required ports]({{}}/rancher/v2.6/en/cluster-provisioning/node-requirements/#networking-requirements) for overlay networking are not opened for `wk2`. -6. You can now clean up the DaemonSet by running `kubectl delete ds/overlaytest`. - - -### Check if MTU is correctly configured on hosts and on peering/tunnel appliances/devices - -When the MTU is incorrectly configured (either on hosts running Rancher, nodes in created/imported clusters or on appliances/devices in between), error messages will be logged in Rancher and in the agents, similar to: - -* `websocket: bad handshake` -* `Failed to connect to proxy` -* `read tcp: i/o timeout` - -See [Google Cloud VPN: MTU Considerations](https://cloud.google.com/vpn/docs/concepts/mtu-considerations#gateway_mtu_vs_system_mtu) for an example how to configure MTU correctly when using Google Cloud VPN between Rancher and cluster nodes. - -### Resolved issues - -#### Overlay network broken when using Canal/Flannel due to missing node annotations - -| | | -|------------|------------| -| GitHub issue | [#13644](https://github.com/rancher/rancher/issues/13644) | -| Resolved in | v2.1.2 | - -To check if your cluster is affected, the following command will list nodes that are broken (this command requires `jq` to be installed): - -``` -kubectl get nodes -o json | jq '.items[].metadata | select(.annotations["flannel.alpha.coreos.com/public-ip"] == null or .annotations["flannel.alpha.coreos.com/kube-subnet-manager"] == null or .annotations["flannel.alpha.coreos.com/backend-type"] == null or .annotations["flannel.alpha.coreos.com/backend-data"] == null) | .name' -``` - -If there is no output, the cluster is not affected. diff --git a/versioned_docs/version-2.6/troubleshooting/rancherha/rancherha.md b/versioned_docs/version-2.6/troubleshooting/rancherha/rancherha.md deleted file mode 100644 index d724c778cdb..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/rancherha/rancherha.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Rancher HA -weight: 104 ---- - -The commands/steps listed on this page can be used to check your Rancher Kubernetes Installation. - -Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`). - -### Check Rancher pods - -Rancher pods are deployed as a Deployment in the `cattle-system` namespace. - -Check if the pods are running on all nodes: - -``` -kubectl -n cattle-system get pods -l app=rancher -o wide -``` - -Example output: - -``` -NAME READY STATUS RESTARTS AGE IP NODE -rancher-7dbd7875f7-n6t5t 1/1 Running 0 8m x.x.x.x x.x.x.x -rancher-7dbd7875f7-qbj5k 1/1 Running 0 8m x.x.x.x x.x.x.x -rancher-7dbd7875f7-qw7wb 1/1 Running 0 8m x.x.x.x x.x.x.x -``` - -If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. - -#### Pod details - -``` -kubectl -n cattle-system describe pods -l app=rancher -``` - -#### Pod container logs - -``` -kubectl -n cattle-system logs -l app=rancher -``` - -#### Namespace events - -``` -kubectl -n cattle-system get events -``` - -### Check ingress - -Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to). - -``` -kubectl -n cattle-system get ingress -``` - -Example output: - -``` -NAME HOSTS ADDRESS PORTS AGE -rancher rancher.yourdomain.com x.x.x.x,x.x.x.x,x.x.x.x 80, 443 2m -``` - -### Check ingress controller logs - -When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher: - -``` -kubectl -n ingress-nginx logs -l app=ingress-nginx -``` - -### Leader election - -The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`). - -``` -kubectl -n kube-system get configmap cattle-controllers -o jsonpath='{.metadata.annotations.control-plane\.alpha\.kubernetes\.io/leader}' -{"holderIdentity":"rancher-7dbd7875f7-qbj5k","leaseDurationSeconds":45,"acquireTime":"2019-04-04T11:53:12Z","renewTime":"2019-04-04T12:24:08Z","leaderTransitions":0} -``` - diff --git a/versioned_docs/version-2.6/troubleshooting/troubleshooting.md b/versioned_docs/version-2.6/troubleshooting/troubleshooting.md deleted file mode 100644 index 47448e25c17..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/troubleshooting.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Troubleshooting -weight: 26 ---- - -This section contains information to help you troubleshoot issues when using Rancher. - -- [Kubernetes components]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-components/) - - If you need help troubleshooting core Kubernetes cluster components like: - * `etcd` - * `kube-apiserver` - * `kube-controller-manager` - * `kube-scheduler` - * `kubelet` - * `kube-proxy` - * `nginx-proxy` - -- [Kubernetes resources]({{}}/rancher/v2.6/en/troubleshooting/kubernetes-resources/) - - Options for troubleshooting Kubernetes resources like Nodes, Ingress Controller and Rancher Agents are described in this section. - -- [Networking]({{}}/rancher/v2.6/en/troubleshooting/networking/) - - Steps to troubleshoot networking issues can be found here. - -- [DNS]({{}}/rancher/v2.6/en/troubleshooting/dns/) - - When you experience name resolution issues in your cluster. - -- [Troubleshooting Rancher installed on Kubernetes]({{}}/rancher/v2.6/en/troubleshooting/rancherha/) - - If you experience issues with your [Rancher server installed on Kubernetes]({{}}/rancher/v2.6/en/installation/install-rancher-on-k8s/) - -- [Logging]({{}}/rancher/v2.6/en/troubleshooting/logging/) - - Read more about what log levels can be configured and how to configure a log level. - -- [User ID Tracking in Audit Logs]({{}}/rancher/v2.6/en/troubleshooting/userid-tracking-in-audit-logs/) - - Read more about how a Rancher Admin can trace an event from the Rancher audit logs and into the Kubernetes audit logs using the external Identity Provider username. - -- [Expired Webhook Certificates]({{}}/rancher/v2.6/en/troubleshooting/expired-webhook-certificates/) - - Read more about how to rotate a Rancher webhook certificate secret after it expires on an annual basis. diff --git a/versioned_docs/version-2.6/troubleshooting/userid-tracking-in-audit-logs/userid-tracking-in-audit-logs.md b/versioned_docs/version-2.6/troubleshooting/userid-tracking-in-audit-logs/userid-tracking-in-audit-logs.md deleted file mode 100644 index e6150b18bf8..00000000000 --- a/versioned_docs/version-2.6/troubleshooting/userid-tracking-in-audit-logs/userid-tracking-in-audit-logs.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: User ID Tracking in Audit Logs -weight: 110 ---- - -The following audit logs are used in Rancher to track events occuring on the local and downstream clusters: - -* [Kubernetes Audit Logs]({{}}/rke/latest/en/config-options/audit-log/) -* [Rancher API Audit Logs]({{}}/rancher/v2.6/en/installation/resources/advanced/api-audit-log/) - -Audit logs in Rancher v2.6 have been enhanced to include the external Identity Provider name (common name of the user in the external Auth provider) in both the Rancher and downstream Kubernetes audit logs. - -Before v2.6, a Rancher Admin could not trace an event from the Rancher audit logs and into the Kubernetes audit logs without knowing the mapping of the external Identity Provider username to the userId (`u-xXXX`) used in Rancher. -To know this mapping, the cluster admins needed to have access to Rancher API, UI, and the local management cluster. - -Now with this feature, a downstream cluster admin should be able to look at the Kubernetes audit logs and know which specific external Identity Provider (IDP) user performed an action without needing to view anything in Rancher. -If the audit logs are shipped off of the cluster, a user of the logging system should be able to identify the user in the external Identity Provider system. -A Rancher Admin should now be able to view Rancher audit logs and follow through to the Kubernetes audit log by using the external Identity Provider username. - -### Feature Description - -- When Kubernetes Audit logs are enabled on the downstream cluster, in each event that is logged, the external Identity Provider's username is now logged for each request, at the "metadata" level. -- When Rancher API Audit logs are enabled on the Rancher installation, the external Identity Provider's username is also logged now at the `auditLog.level=1` for each request that hits the Rancher API server, including the login requests. diff --git a/versioned_docs/version-2.6/user-settings/api-keys/api-keys.md b/versioned_docs/version-2.6/user-settings/api-keys/api-keys.md deleted file mode 100644 index 7f39b336b55..00000000000 --- a/versioned_docs/version-2.6/user-settings/api-keys/api-keys.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: API Keys -weight: 7005 ---- - -## API Keys and User Authentication - -If you want to access your Rancher clusters, projects, or other objects using external applications, you can do so using the Rancher API. However, before your application can access the API, you must provide the app with a key used to authenticate with Rancher. You can obtain a key using the Rancher UI. - -An API key is also required for using Rancher CLI. - -API Keys are composed of four components: - -- **Endpoint:** This is the IP address and path that other applications use to send requests to the Rancher API. -- **Access Key:** The token's username. -- **Secret Key:** The token's password. For applications that prompt you for two different strings for API authentication, you usually enter the two keys together. -- **Bearer Token:** The token username and password concatenated together. Use this string for applications that prompt you for one authentication string. - ->Note: Users may opt to enable [token hashing]({{}}/rancher/v2.6/en/api/api-tokens). - -## Creating an API Key - -1. Select **User Avatar > Account & API Keys** from upper right corner. - -2. Click **Create API Key**. - -3. **Optional:** Enter a description for the API key and select an expiration period or a scope. We recommend setting an expiration date. - - The API key won't be valid after expiration. Shorter expiration periods are more secure. - - Expiration period will be bound by `v3/settings/auth-token-max-ttl-minutes`. If it exceeds the max-ttl, API key will be created with max-ttl as the expiration period. - - A scope will limit the API key so that it will only work against the Kubernetes API of the specified cluster. If the cluster is configured with an Authorized Cluster Endpoint, you will be able to use a scoped token directly against the cluster's API without proxying through the Rancher server. See [Authorized Cluster Endpoints]({{}}/rancher/v2.6/en/overview/architecture/#4-authorized-cluster-endpoint) for more information. - -4. Click **Create**. - - **Step Result:** Your API Key is created. Your API **Endpoint**, **Access Key**, **Secret Key**, and **Bearer Token** are displayed. - - Use the **Bearer Token** to authenticate with Rancher CLI. - -5. Copy the information displayed to a secure location. This information is only displayed once, so if you lose your key, you'll have to make a new one. - -## What's Next? - -- Enter your API key information into the application that will send requests to the Rancher API. -- Learn more about the Rancher endpoints and parameters by selecting **View in API** for an object in the Rancher UI. -- API keys are used for API calls and [Rancher CLI]({{}}/rancher/v2.6/en/cli). - -## Deleting API Keys - -If you need to revoke an API key, delete it. You should delete API keys: - -- That may have been compromised. -- That have expired. - -To delete an API, select the stale key and click **Delete**. diff --git a/versioned_docs/version-2.6/user-settings/cloud-credentials/cloud-credentials.md b/versioned_docs/version-2.6/user-settings/cloud-credentials/cloud-credentials.md deleted file mode 100644 index f3022599613..00000000000 --- a/versioned_docs/version-2.6/user-settings/cloud-credentials/cloud-credentials.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Managing Cloud Credentials -weight: 7011 ---- - -When you create a cluster [hosted by an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools), [node templates]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) are used to provision the cluster nodes. These templates use Docker Machine configuration options to define an operating system image and settings/parameters for the node. - -Node templates can use cloud credentials to access the credential information required to provision nodes in the infrastructure providers. The same cloud credential can be used by multiple node templates. By using a cloud credential, you do not have to re-enter access keys for the same cloud provider. Cloud credentials are stored as Kubernetes secrets. - -Cloud credentials are only used by node templates if there are fields marked as `password`. The default `active` node drivers have their account access fields marked as `password`, but there may be some `inactive` node drivers, which are not using them yet. These node drivers will not use cloud credentials. - -You can create cloud credentials in two contexts: - -- [During creation of a node template]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for a cluster. -- In the **User Settings** - -All cloud credentials are bound to the user profile of who created it. They **cannot** be shared across users. - -## Creating a Cloud Credential from User Settings - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Click **Create**. -1. Click a cloud credential type. The values of this dropdown is based on the `active` [node drivers]({{}}/rancher/v2.6/en/admin-settings/drivers/node-drivers/) in Rancher. -1. Enter a name for the cloud credential. -1. Based on the selected cloud credential type, enter the required values to authenticate with the infrastructure provider. -1. Click **Create**. - -**Result:** The cloud credential is created and can immediately be used to [create node templates]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates). - -## Updating a Cloud Credential - -When access credentials are changed or compromised, updating a cloud credential allows you to rotate those credentials while keeping the same node template. - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. Choose the cloud credential you want to edit and click the **⋮ > Edit Config**. -1. Update the credential information and click **Save**. - -**Result:** The cloud credential is updated with the new access credentials. All existing node templates using this cloud credential will automatically use the updated information whenever [new nodes are added]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/). - -## Deleting a Cloud Credential - -In order to delete cloud credentials, there must not be any node template associated with it. If you are unable to delete the cloud credential, [delete any node templates]({{}}/rancher/v2.6/en/user-settings/node-templates/#deleting-a-node-template) that are still associated to that cloud credential. - -1. Click **☰ > Cluster Management**. -1. Click **Cloud Credentials**. -1. You can either individually delete a cloud credential or bulk delete. - - - To individually delete one, choose the cloud credential you want to edit and click the **⋮ > Delete**. - - To bulk delete cloud credentials, select one or more cloud credentials from the list. Click **Delete**. -1. Confirm that you want to delete these cloud credentials. diff --git a/versioned_docs/version-2.6/user-settings/node-templates/node-templates.md b/versioned_docs/version-2.6/user-settings/node-templates/node-templates.md deleted file mode 100644 index d3b712815e6..00000000000 --- a/versioned_docs/version-2.6/user-settings/node-templates/node-templates.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Managing Node Templates -weight: 7010 ---- - -When you provision a cluster [hosted by an infrastructure provider]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools), [node templates]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) are used to provision the cluster nodes. These templates use Docker Machine configuration options to define an operating system image and settings/parameters for the node. You can create node templates in two contexts: - -- While [provisioning a node pool cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools). -- At any time, from your [user settings](#creating-a-node-template-from-user-settings). - -When you create a node template, it is bound to your user profile. Node templates cannot be shared among users. You can delete stale node templates that you no longer user from your user settings. - -## Creating a Node Template - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Click **Add Template**. -1. Select one of the cloud providers available. Then follow the instructions on screen to configure the template. - -**Result:** The template is configured. You can use the template later when you [provision a node pool cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools). - -## Updating a Node Template - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Choose the node template that you want to edit and click the **⋮ > Edit**. - - > **Note:** The default `active` [node drivers]({{}}/rancher/v2.6/en/admin-settings/drivers/node-drivers/) and any node driver, that has fields marked as `password`, are required to use [cloud credentials]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#cloud-credentials). - -1. Edit the required information and click **Save**. - -**Result:** The node template is updated. All node pools using this node template will automatically use the updated information when new nodes are added. - -## Cloning Node Templates - -When creating new node templates from your user settings, you can clone an existing template and quickly update its settings rather than creating a new one from scratch. Cloning templates saves you the hassle of re-entering access keys for the cloud provider. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Find the template you want to clone. Then select **⋮ > Clone**. -1. Complete the rest of the form. - -**Result:** The template is cloned and configured. You can use the template later when you [provision a node pool cluster]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools). - -## Deleting a Node Template - -When you no longer use a node template, you can delete it from your user settings. - -1. Click **☰ > Cluster Management**. -1. Click **RKE1 Configuration > Node Templates**. -1. Select one or more template from the list. Then click **Delete**. Confirm the delete when prompted. diff --git a/versioned_docs/version-2.6/user-settings/preferences/preferences.md b/versioned_docs/version-2.6/user-settings/preferences/preferences.md deleted file mode 100644 index fc2fe8c1f2b..00000000000 --- a/versioned_docs/version-2.6/user-settings/preferences/preferences.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: User Preferences -weight: 7012 ---- - -Each user can choose preferences to personalize their Rancher experience. To change preference settings, open the **User Settings** menu and then select **Preferences**. - -## Theme - -Choose your background color for the Rancher UI. If you choose **Auto**, the background color changes from light to dark at 6 PM, and then changes back at 6 AM. - -## My Account - -This section displays the **Name** (your display name) and **Username** (your login) used for your session. To change your login's current password, click the **Change Password** button. - -## Table Row per Page - -On pages that display system objects like clusters or deployments in a table, you can set the number of objects that display on the page before you must paginate. The default setting is `50`. diff --git a/versioned_docs/version-2.6/user-settings/user-settings.md b/versioned_docs/version-2.6/user-settings/user-settings.md deleted file mode 100644 index 3781c633859..00000000000 --- a/versioned_docs/version-2.6/user-settings/user-settings.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: User Settings -weight: 23 ---- - -Within Rancher, each user has a number of settings associated with their login: personal preferences, API keys, etc. You can configure these settings by choosing from the **User Settings** menu. You can open this menu by clicking your avatar, located within the main menu. - -![User Settings Menu]({{}}/img/rancher/user-settings.png) - -The available user settings are: - -- [API & Keys]({{}}/rancher/v2.6/en/user-settings/api-keys/): If you want to interact with Rancher programmatically, you need an API key. Follow the directions in this section to obtain a key. -- [Cloud Credentials]({{}}/rancher/v2.6/en/user-settings/cloud-credentials/): Manage cloud credentials [used by node templates]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) to [provision nodes for clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters). -- [Node Templates]({{}}/rancher/v2.6/en/user-settings/node-templates): Manage templates [used by Rancher to provision nodes for clusters]({{}}/rancher/v2.6/en/cluster-provisioning/rke-clusters). -- [Preferences]({{}}/rancher/v2.6/en/user-settings/preferences): Sets superficial preferences for the Rancher UI. -- Log Out: Ends your user session. diff --git a/versioned_docs/version-2.6/virtualization-admin/virtualization-admin.md b/versioned_docs/version-2.6/virtualization-admin/virtualization-admin.md deleted file mode 100644 index 19c517f7c3d..00000000000 --- a/versioned_docs/version-2.6/virtualization-admin/virtualization-admin.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Harvester Integration -weight: 10 ---- - -##### _Tech Preview_ - -New in Rancher v2.6.1, [Harvester v0.3.0](https://docs.harvesterhci.io/v0.3/) is an open-source hyper-converged infrastructure (HCI) software built on Kubernetes. Harvester installs on bare metal server clusters and provides integrated virtualization and distributed storage capabilities. Although Harvester operates using Kubernetes, it does not require users to know Kubernetes concepts, making it a more user-friendly application. - -### Feature Flag - -The Harvester feature flag is used to manage access to the Virtualization Management (VM) page in Rancher where users can navigate directly to Harvester clusters and access the Harvester UI. The Harvester feature flag is enabled by default. Click [here]({{}}/rancher/v2.6/en/installation/resources/feature-flags/) for more information on feature flags in Rancher. - -To navigate to the Harvester cluster, click **☰ > Virtualization Management**. From Harvester Clusters page, click one of the clusters listed to go to the single Harvester cluster view. - -* If the Harvester feature flag is enabled, Harvester clusters will be filtered out from any pages or apps (such as Fleet and the multi-cluster app) that list Kubernetes clusters. - -* If the Harvester feature flag is disabled, and a Harvester cluster is imported, the Harvester cluster will be shown in the Rancher cluster list in the Cluster Management page. Harvester clusters will only be shown on the cluster list when the feature flag is off. - -* With the Harvester integration, Harvester clusters can now be imported into Rancher as a cluster type `Harvester`. - -* Users may import a Harvester cluster only on the Virtualization Management page. Importing a cluster on the Cluster Management page is not supported, and a warning will advise you to return to the VM page to do so. - -### Harvester Node Driver - -The [Harvester node driver](https://docs.harvesterhci.io/v0.3/rancher/node-driver/) is marked as `tech preview` on RKE and RKE2 options in Rancher. This will be the case both on the Create page and once the driver is already enabled. The node driver is available whether or not the Harvester feature flag is enabled. Note that the node driver is off by default. Users may create RKE or RKE2 clusters on Harvester only from the Cluster Management page. - -Harvester allows `.ISO` images to be uploaded and displayed through the Harvester UI, but this is not supported in the Rancher UI. This is because `.ISO` images usually require additional setup that interferes with a clean deployment (without requiring user intervention), and they are not typically used in cloud environments. - -Click [here]({{}}/rancher/v2.6/en/admin-settings/drivers/#node-drivers) for more information on node drivers in Rancher. - -### Limitations - -* Harvester v0.3.0 doesn't support air gap environment installation. -* Harvester v0.3.0 doesn't support upgrade from v0.2.0 nor upgrade to future v1.0.0. \ No newline at end of file diff --git a/versioned_sidebars/version-2.6-sidebars.json b/versioned_sidebars/version-2.6-sidebars.json deleted file mode 100644 index caea0c03ba6..00000000000 --- a/versioned_sidebars/version-2.6-sidebars.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "tutorialSidebar": [ - { - "type": "autogenerated", - "dirName": "." - } - ] -}