docs(blog): added blog post explaining operatorless istio changes

General MR

Summary

This MR adds a blog post explaining the incoming istio changes for Big Bang 3.0.

Linked Issue

Closes #2561 (closed)

Upgrade Notices

N/A

blog/bb-3-0-operatorless-istio-migration.md

 # Big Bang 3.0 - Operatorless Istio Migration
 
-It has been nearly two years since the Big Bang 2.0 release, and the project has grown significantly in that time. The Big Bang engineering team is proud of the product that we have built alongside our growing community. Your support and feedback have been essential in shaping the platform your missions rely on.
+It has been nearly two years since the Big Bang 2.0 release, and the project has
+grown significantly in that time. The Big Bang engineering team is proud of the
+product that we have built alongside our growing community. Your support and
+feedback have been essential in shaping the platform your missions rely on.
 
-In line with our mission-first principles, we want to share updates on the direction of Big Bang and what it means for you as Big Bang operators.
+In line with our mission-first principles, we want to share updates on the
+direction of Big Bang and what it means for you as Big Bang operators.
 
 ## Istio Operator Deprecation
 
-In August 2024, the Istio project [announced](https://istio.io/latest/blog/2024/in-cluster-operator-deprecation-announcement/) the deprecation of the Istio Operator in Istio 1.24. The Istio Operator was created to address many of the problems with Helm 2. Helm 3 resolved many of those issues. Additionally, the Istio project's data showed that less than 10% of installations used the operator, with most relying on istioctl for initial deployment and upgrades.
-Big Bang uses a declarative approach to application deployments. With 3.0, we've included a declarative approach for installing Istio into Kubernetes clusters without the operator or istioctl.
+In August 2024, the Istio project
+[announced](https://istio.io/latest/blog/2024/in-cluster-operator-deprecation-announcement/)
+the deprecation of the Istio Operator in Istio 1.24. The Istio Operator was
+created to address many of the problems with Helm 2. Helm 3 resolved many of
+those issues. Additionally, the Istio project's data showed that less than 10%
+of installations used the operator, with most relying on istioctl for initial
+deployment and upgrades. Big Bang uses a declarative approach to application
+deployments. With 3.0, we've included a declarative approach for installing
+Istio into Kubernetes clusters without the operator or istioctl.
 
 Istio 1.23 has a
 [generous EOL timeline](https://istio.io/latest/docs/releases/supported-releases/#support-status-of-istio-releases),
@@ -58,8 +69,8 @@ Here are some key architectural changes you should be aware of:
 ✅ **Simplified Deployment with Iterable Helm Releases**
 
 - We are developing an iterable `istioGateway` package to ease deployment.
-- Users can still deploy custom `Gateway` resources manually, but our new package
-  will reduce friction.
+- Users can still deploy custom `Gateway` resources manually, but our new
+  package will reduce friction.
 - More details on this feature will be shared in the coming weeks.
 
 🔍 **Exploring Kubernetes-native Gateway API**
@@ -107,5 +118,7 @@ deployment.**
 
 As always, we want to thank our community for their continued support. We build
 Big Bang for you, and our mission is to simplify and enable yours. If you have
-any feedback or concerns, please share them in our community Slack, on
-Mattermost, or by making an issue in repo1.
+any feedback or concerns, please share them in
+[our community Slack](https://bigbanguniver-ft39451.slack.com/archives/C051A2BPS0K),
+on Mattermost, or by
+[making an issue](https://repo1.dso.mil/big-bang/bigbang/-/issues/new) in repo1.