# addons Published articles for addons. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sail Operator 1.0.0 released: manage Istio with an operator DevFeed: [Sail Operator 1.0.0 released: manage Istio with an operator]() Original publisher: [Read original article]() Author: Francisco Herrera - Red Hat Published: 2025-04-03T00:00:00Z Content type: release Language: en Sources: [Istio Blog]() Topics: [istio](), [control-plane](), [Deployment](), [Kubernetes]() Tags: [addons](), [cni](), [control-plane](), [deployment](), [incluster](), [istio](), [istiooperator](), [kubernetes](), [mesh](), [microservices](), [operator](), [sail](), [services](), [upgrade](), [upgrades](), [ztunnel]() ### AI overview This release announces Sail Operator 1.0.0 reaching general availability as a community project for managing Istio in Kubernetes clusters. It describes automated installation, maintenance, upgrades, dedicated custom resources for Istio components and revisions, support for multiple Istio versions and multicluster deployment models, and alpha support for ambient mode. ### Source excerpt The Sail Operator is a community project launched by Red Hat to build a modern operator for Istio. First announced in August 2024, we are pleased to announce Sail Operator is now GA with a clear mission: to simplify and streamline Istio management in your cluster. Simplified deployment & management The Sail Operator is engineered to cut down the complexity of installing and running Istio. It automates manual tasks, ensuring a consistent, reliable, and uncomplicated experience from initial installation to ongoing maintenance and upgrades of Istio versions in your cluster. The Sail Operator APIs are built around Istio's Helm chart APIs, which means that all the Istio configurations are available through the Sail Operator CRD's values. We encourage users to go through our documentation to learn more about this new way to manage your Istio environment. The main resources that are part of the Sail Operator are: Istio: manages an Istio control plane. IstioRevision: represents a revision of the control plane. IstioRevisionTag: represents a stable revision tag, which functions as an alias for an Istio control plane revision. IstioCNI: manages Istio's CNI node agent. ZTunnel: manage the ambient mode ztunnel DaemonSet (Alpha feature). If you are migrating from the since-removed Istio in-cluster operator, you can check this section in our documentation where we explain the equivalence of resources, or you can also try our resource converter to easily convert your IstioOperator resource to an Istio resource. Main features and support Each component of the Istio control plane is managed independently by the Sail Operator through dedicated Kubernetes Custom Resources (CRs). The Sail Operator provides separate CRDs for components such as Istio, IstioCNI, and ZTunnel, allowing you to configure, manage, and upgrade them individually. Additionally, there are CRDs for IstioRevision and IstioRevisionTag to manage Istio control plane revisions. Support for multiple Istio versions. Curre ## Reworking our Addon Integrations DevFeed: [Reworking our Addon Integrations]() Original publisher: [Read original article]() Author: John Howard (Google) Published: 2020-06-04T00:00:00Z Content type: release Language: en Sources: [Istio Blog]() Topics: [istio](), [telemetry](), [Deployment](), [Grafana](), [Prometheus]() Tags: [addons](), [deployment](), [grafana](), [integrations](), [istio](), [mesh](), [microservices](), [prometheus](), [releases](), [services](), [telemetry]() ### AI overview Istio 1.6 introduces a new approach for integrating telemetry addons such as Grafana, Prometheus, Zipkin, Jaeger, and Kiali. The changes reduce configuration, improve compatibility with upstream installations, publish Grafana dashboards, enable Prometheus scraping through standard annotations, and remove bundled addon installations from Istio tooling over subsequent releases. ### Source excerpt Starting with Istio 1.6, we are introducing a new method for integration with telemetry addons, such as Grafana, Prometheus, Zipkin, Jaeger, and Kiali. In previous releases, these addons were bundled as part of the Istio installation. This allowed users to quickly get started with Istio without any complicated configurations to install and integrate these addons. However, it came with some issues: The Istio addon installations were not as up to date or feature rich as upstream installation methods. Users were left missing out on some of the great features provided by these applications, such as: Persistent storage Features like Alertmanager for Prometheus Advanced security settings Integration with existing deployments that were using these features was more challenging than it should be. Changes In order to address these gaps, we have made a number of changes: Added a new Integrations documentation section to explain which applications Istio can integrate with, how to use them, and best practices. Reduced the amount of configuration required to set up telemetry addons Grafana dashboards are now published to grafana.com. Prometheus can now scrape all Istio pods using standard prometheus.io annotations. This allows most Prometheus deployments to work with Istio without any special configuration. Removed the bundled addon installations from istioctl and the operator. Istio does not install components that are not delivered by the Istio project. As a result, Istio will stop shipping installation artifacts related to addons. However, Istio will guarantee version compatibility where necessary. It is the user's responsibility to install these components by using the official Integrations documentation and artifacts provided by the respective projects. For demos, users can deploy simple YAML files from the samples/addons/ directory. We hope these changes allow users to make the most of these addons so as to fully experience what Istio can offer. Timeline Istio 1.6: The new