# Instaclustr for Apache Kafka® and Apache Kafka® Connect 2.8.2, 3.0.2, and 3.1.2 are now generally available [Blog](/blog/)>[Technology](/blog/category/technical/)>Instaclustr for Apache Kafka® and Apache Kafka® Connect 2.8.2, 3.0.2, and 3.1.2 are now generally available Instaclustr for Apache Kafka® and Apache Kafka® Connect 2.8.2, 3.0.2, and 3.1.2 are now generally available =========================================================================================================== October 12, 2022 | By [ Varun Ghai](https://www.instaclustr.com/blog/author/varun-ghai/) [ ](https://x.com/intent/tweet?text=Instaclustr%20for%20Apache%20Kafka%C2%AE%20and%20Apache%20Kafka%C2%AE%20Connect%202.8.2,%203.0.2,%20and%203.1.2%20are%20now%20generally%20available&url=https://www.instaclustr.com/blog/instaclustr-for-apache-kafka-and-apache-kafka-connect-2-8-2-3-0-2-and-3-1-2-are-now-generally-available/) [ ](https://www.linkedin.com/shareArticle?mini=true&url=https://www.instaclustr.com/blog/instaclustr-for-apache-kafka-and-apache-kafka-connect-2-8-2-3-0-2-and-3-1-2-are-now-generally-available/&title=&summary=Instaclustr%20for%20Apache%20Kafka%C2%AE%20and%20Apache%20Kafka%C2%AE%20Connect%202.8.2,%203.0.2,%20and%203.1.2%20are%20now%20generally%20available&source=) Instaclustr is pleased to announce the immediate general availability of Instaclustr for Apache Kafka® and Apache Kafka® Connect 2.8.2, 3.0.2, and 3.1.2 on our managed platform. These versions of Apache Kafka include the fix for [CVE-2022-34917](https://nvd.nist.gov/vuln/detail/CVE-2022-34917) (which we previously provided advice on in [this blog post](https://www.instaclustr.com/blog/security-advisory-cve-2022-34917-apache-kafka/)) along with other bug fixes. While Kafka Connect is not impacted by the CVE, these new versions do include several bug fixes, and customers are recommended to upgrade. Upgrading from one bugfix release to the next (i.e. from [2.8.1](https://archive.apache.org/dist/kafka/2.8.1/RELEASE_NOTES.html) to [2.8.2](https://archive.apache.org/dist/kafka/2.8.2/RELEASE_NOTES.html), or from [3.0.0](https://archive.apache.org/dist/kafka/3.0.0/RELEASE_NOTES.html) to [3.0.2](https://archive.apache.org/dist/kafka/3.0.2/RELEASE_NOTES.html), or from [3.1.1](https://archive.apache.org/dist/kafka/3.1.1/RELEASE_NOTES.html) to [3.1.2](https://archive.apache.org/dist/kafka/3.1.2/RELEASE_NOTES.html)) should not cause compatibility issues since the newer versions do not introduce any breaking changes. As communicated recently as part of the operating system patching notification to all customers, customers on Kafka and Kafka Connect versions 2.8.1, 3.0.2, and 3.1.2 will be upgraded to the respective new bugfix versions during the upcoming operating system upgrades. Customers on Kafka and Kafka Connect versions lower than 2.8.1 have been individually notified of the need to upgrade to receive the fix for this CVE, and we recommend getting in touch with us via our [support website](https://support.instaclustr.com/hc/en-us/requests/new) to schedule upgrades as soon as possible. Our recommendation is based on the results from our internal investigations which identified that older versions of Kafka are also likely susceptible to the same issues as listed in the CVE. With the release of these new Kafka and Kafka Connect versions, we have now marked the superseded Kafka and Kafka Connect versions 2.8.1, 3.0.0, and 3.1.1 as being in the [lifecycle state](https://www.instaclustr.com/support/documentation/useful-information/lifecycle-policy/) of Closed. For new customers this means they will not have the option of provisioning new clusters of these Closed versions. They are recommended to use one of the generally available versions. For existing customers who are running clusters on any of the Closed versions, they will continue to have access to that Closed version to allow them time to undertake testing, client upgrades etc. and prepare to upgrade to one of the generally available versions. If you require any further clarification or assistance, please feel free to reach out to us via our [support website](https://support.instaclustr.com/hc/en-us/requests/new). ### About the author **[Varun Ghai](https://www.instaclustr.com/blog/author/varun-ghai/)** | Product Manager With a keen focus on product management, Varun brings a wealth of experience and expertise to the team, driving innovation and excellence in the company's Apache Kafka offering. ![mail icon]()#### Get the latest articles for open sourceIn your inbox Sign up now ### Related content [ Zero Downtime Migration to Instaclustr Yes, we can migrate existing Cassandra clusters to Instaclustr without any downtime. Here's what to expect from the process... ](https://www.instaclustr.com/blog/zero-downtime-migration-to-instaclustr/) [ Workflow Comparison: Uber Cadence vs Netflix Conductor When choosing what’s right for your company’s opensource workflow needs it is important to know the difference and similarities ... ](https://www.instaclustr.com/blog/workflow-comparison-uber-cadence-vs-netflix-conductor/) [ Will Your Cassandra Database Project Succeed?: The New Stack Open source Apache Cassandra® continues to stand out as an enterprise-proven solution for organizations seeking high availability... ](https://www.instaclustr.com/blog/will-your-cassandra-database-project-succeed-the-new-stack/) ×Sign upto ourNewsletter -----------------------