AWS prescriptive-guidance documentation change
Summary
Reformatted Flux capabilities from table to bullet points and updated image path
Security assessment
The change involves formatting improvements without altering security content. The 'Security and RBAC' section remains unchanged and no vulnerabilities are addressed. Image path update has no security implications.
Diff
diff --git a/prescriptive-guidance/latest/eks-gitops-tools/flux.md b/prescriptive-guidance/latest/eks-gitops-tools/flux.md index 0d937f809..efa1eeab6 100644 --- a//prescriptive-guidance/latest/eks-gitops-tools/flux.md +++ b//prescriptive-guidance/latest/eks-gitops-tools/flux.md @@ -15,20 +15,38 @@ Flux is another tool for Kubernetes that implements GitOps principles in a uniqu -Area | Tool capabilities ----|--- -Git as the single source of truth | Flux uses Git repositories as the definitive source for defining the desired state of the system. All configuration for applications and infrastructure is stored in Git. -Declarative configuration | Flux works with declarative descriptions of the desired state of your cluster. These descriptions are typically Kubernetes manifests, Helm charts, or Kustomize overlays. -Automated aynchronization | Flux continuously monitors the Git repository for changes. When it detects changes, it automatically applies them to the cluster. -Kubernetes-native | Flux is built as a set of Kubernetes controllers and custom resources. It uses the extension mechanisms in Kubernetes to provide GitOps capabilities. -Pull-based deployment model | Unlike traditional push-based CI/CD systems, Flux uses a pull-based model. The cluster pulls the desired state from Git instead of using an external system to push changes. -Continuous reconciliation | Flux constantly compares the actual state of the cluster with the desired state in Git. It automatically corrects any drift that's detected between these states. -Multi-tenancy | Flux supports multi-tenancy through its concepts of _Kustomizations_ and _HelmReleases_. Different teams can manage their own parts of the configuration independently. -Progressive delivery | Flux supports advanced deployment strategies, such as canary releases and A/B testing, through its Flagger component. -Helm integration | Flux includes native support for Helm, so you can easily manage Helm releases through GitOps. -Image update automation | Flux can automatically update container images in Git when new versions are available in the container registry. -Kustomize support | You can use the native support provided by Flux for Kustomize to customize and patch Kubernetes manifests. -Security and RBAC | Flux integrates with Kubernetes RBAC for access control. It supports secrets management through various backends. -Observability | Flux provides status information and metrics about reconciliation and operations. It integrates with monitoring tools for enhanced observability. -Event-driven architecture | Flux uses an event-driven approach to implement reconciliations and updates. -Extensibility | The tool is designed to be extensible, so you can add custom controllers and resources. -Cross-cluster synchronization | Flux supports the management of multiple clusters from a single set of repositories. -Dependency management | It allows for defining dependencies between different parts of your system and ensures the correct order of operations. -Webhook receivers | You can configure Flux to receive webhooks from Git providers or other systems to start immediate reconciliation. + * **Git as the single source of truth** : Flux uses Git repositories as the definitive source for defining the desired state of the system. All configuration for applications and infrastructure is stored in Git. + + * **Declarative configuration** : Flux works with declarative descriptions of the desired state of your cluster. These descriptions are typically Kubernetes manifests, Helm charts, or Kustomize overlays. + + * **Automated aynchronization** : Flux continuously monitors the Git repository for changes. When it detects changes, it automatically applies them to the cluster. + + * **Kubernetes-native** : Flux is built as a set of Kubernetes controllers and custom resources. It uses the extension mechanisms in Kubernetes to provide GitOps capabilities. + + * **Pull-based deployment model** : Unlike traditional push-based CI/CD systems, Flux uses a pull-based model. The cluster pulls the desired state from Git instead of using an external system to push changes. + + * **Continuous reconciliation** : Flux constantly compares the actual state of the cluster with the desired state in Git. It automatically corrects any drift that's detected between these states. + + * **Multi-tenancy** : Flux supports multi-tenancy through its concepts of _Kustomizations_ and _HelmReleases_. Different teams can manage their own parts of the configuration independently. + + * **Progressive delivery** : Flux supports advanced deployment strategies, such as canary releases and A/B testing, through its Flagger component. + + * **Helm integration** : Flux includes native support for Helm, so you can easily manage Helm releases through GitOps. + + * **Image update automation** : Flux can automatically update container images in Git when new versions are available in the container registry. + + * **Kustomize support** : You can use the native support provided by Flux for Kustomize to customize and patch Kubernetes manifests. + + * **Security and RBAC** : Flux integrates with Kubernetes RBAC for access control. It supports secrets management through various backends. + + * **Observability** : Flux provides status information and metrics about reconciliation and operations. It integrates with monitoring tools for enhanced observability. + + * **Event-driven architecture** : Flux uses an event-driven approach to implement reconciliations and updates. + + * **Extensibility** : The tool is designed to be extensible, so you can add custom controllers and resources. + + * **Cross-cluster synchronization** : Flux supports the management of multiple clusters from a single set of repositories. + + * **Dependency management** : It allows for defining dependencies between different parts of your system and ensures the correct order of operations. + + * **Webhook receivers** : You can configure Flux to receive webhooks from Git providers or other systems to start immediate reconciliation. + + + @@ -46 +64 @@ The following diagram illustrates a GitOps-driven CD workflow that uses Flux wit - +