Merge pull request #7321 from stolostron/swope-release-notes

https://issues.redhat.com/browse/ACM-16247--removing what's new and adding notes for when we update

clusters/release_notes/mce_whats_new.adoc

@@ -5,7 +5,7 @@ Learn about new features for creating, importing, managing, and destroying Kuber
 
 For full support information, see the link:https://access.redhat.com/articles/7086906[{mce-short} Support matrix]. For lifecycle information, see link:https://access.redhat.com/support/policy/updates/openshift[{ocp} Life Cycle policy].
 
-*Important:* Cluster management now supports all providers that are certified through the Cloud Native Computing Foundation (CNCF) Kubernetes Conformance Program. Choose a vendor that is recognized by CNFC for your hybrid cloud multicluster management.
+*Important:* Cluster management supports all providers that are certified through the Cloud Native Computing Foundation (CNCF) Kubernetes Conformance Program. Choose a vendor that is recognized by CNFC for your hybrid cloud multicluster management.
 
 See the following information about using CNFC providers:
 
@@ -29,14 +29,4 @@ If you are using {mce-short} 2.6 and earlier, the hosted control planes document
 [#cluster-management-new]
 == Cluster management
 
-Learn about new features and enhancements for Cluster lifecycle with {mce-short}.
-
-- You can now set a duration to choose when the `kubeconfig` bootstrap in the klusterlet manifest expires. To learn more, see xref:../cluster_lifecycle/import_agent.adoc#cluster-import-agent[Importing a cluster].
-
-- You can now import all cluster resources and continue using them after moving a managed cluster that was installed by the {ai} from one hub cluster to another hub cluster. To learn more, see xref:../cluster_lifecycle/import_ocp.adoc#import-ocp-cluster-resources[Importing cluster resources].
-
-- You can now connect to {ocm} with Service Account credentials. To learn more, see xref:../credentials/credential_ocm.adoc#creating-a-credential-for-openshift-cluster-manager[Creating a credential for Red Hat {ocm}].
-
-- You can now specify the CA bundle when importing a managed cluster. To learn more, see xref:../cluster_lifecycle/adv_config_cluster.adoc#custom-server-url-ca[Customizing the server URL and CA bundle of the hub cluster API server when importing a managed cluster (Technology Preview)].
-
-- You can now manually configure a hub cluster `KubeAPIServer` verification strategy. To learn more, see xref:../cluster_lifecycle/adv_config_cluster.adoc#config-hub-kube-api-server[Configuring the hub cluster `KubeAPIServer` verification strategy]
+Learn about new features and enhancements for Cluster lifecycle with {mce-short}.

release_notes/acm_whats_new.adoc

@@ -3,7 +3,7 @@
 
 {acm} provides visibility of your entire Kubernetes domain with built-in governance, cluster lifecycle management, and application lifecycle management, along with observability. 
 
-*Important:* {acm-short} now supports all providers that are certified through the Cloud Native Computing Foundation (CNCF) Kubernetes Conformance Program. Choose a vendor that is recognized by CNFC for your hybrid cloud multicluster management.
+*Important:* {acm-short} supports all providers that are certified through the Cloud Native Computing Foundation (CNCF) Kubernetes Conformance Program. Choose a vendor that is recognized by CNFC for your hybrid cloud multicluster management.
 
 See the following information about using CNFC providers:
 
@@ -29,109 +29,52 @@ Learn specific details about new features for components within {acm-short}:
 Some features and components are identified and released as link:https://access.redhat.com/support/offerings/techpreview[Technology Preview].
 
 Access the link:https://access.redhat.com/articles/7086905[{acm-short} Support matrix] to learn about hub cluster and managed cluster requirements and support for each component. For lifecycle information, see link:https://access.redhat.com/support/policy/updates/openshift[{ocp} Life Cycle policy].
+//links to be updated for 2.13--leave comment so it is known that these are out of date. TY --bcs 12/24
 
 [#install-acm-whats-new]
 == Installation
 
-* You can enable the `SiteConfig` component from the `MultiClusterHub` custom resource that is deployed on your cluster. By default, the `SiteConfig` component is disabled. Learn more at link:../install/adv_config_install.adoc#advanced-config-hub[MultiClusterHub advanced configuration]. Learn more about {sco} at link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/multicluster_engine_operator_with_red_hat_advanced_cluster_management/siteconfig-intro[SiteConfig]. 
-
-* Now when the `MultiClusterHub` resource prepares to install the {mce-short}, it implements `CatalogSource` priority as criteria. The {acm-short} `MultiClusterHub` resource seeks the `CatalogSource` that contains the desired {mce-short} version that is compatible with the current {acm-short} version. Learn more in the _Catalog source priority_ section in link:../install/install_disconnected.adoc#install-on-disconnected-networks[Install in disconnected network environments].
-
 [#console-whats-new]
 == Console
 
 Learn about what is new in the {acm-short} integrated console.
-
-* Command line interface (CLI) downloads are now available in the console, which are available from the `acm-cli` container image and are specified with the operating system and architecture. See link:../console/console.adoc#command-line-tools[Command line tools] to access command line interface (CLI) downloads, such as the `PolicyGenerator` and `policytools`.
-
-* View more information about your cluster when you enable the _Fleet view_ switch. Many summary cards are redesigned, such as _Cluster_ and _Application types_ cards. Additionally, many new summary cards are available, such as _Cluster recommendations_, _Nodes_. See the numerous changes to summary cards in the product console.
-
-* You can now export data in a CSV file by using selecting the *Export* button. See link:../console/console_access.adoc#accessing-your-console[Accessing your console].
-
-* You can now view virtual machine resources from the console and your search results. Configure actions for the virtual machine resources. See link:../console/enable_vm_actions.adoc#enable-vm-actions[Enabling virtual machine actions (Technology Preview)].
+//View more about the console at -- need the main intro link here- bcs 12/24
 
 [#cluster-whats-new]
 == Clusters
 
-*Important:* Cluster lifecycle components and features are within the {mce-short}, which is a software operator that enhances cluster fleet management. Release notes for {mce-short}-specific features are found in at link:../clusters/release_notes/mce_release_notes.adoc#mce-release-notes[Release notes for Cluster lifecycle with {mce-short}].
-
-* You can now enable and use {sco} as a template-driven cluster provisioning solution, which allows you to provision clusters with all available installation methods. Learn more about {sco} at link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/multicluster_engine_operator_with_red_hat_advanced_cluster_management/siteconfig-intro[SiteConfig].
-
 View other Cluster lifecycle tasks and support information at link:../clusters/about/cluster_mce_overview.adoc#cluster_mce_overview[Cluster lifecycle with {mce-short} overview].
 
 [#global-hub-whats-new]
 == multicluster global hub 
 
-* You can now enable the `local-cluster` on your managed hub clusters by importing your managed hub cluster in hosted mode. See link:../global_hub/global_hub_import_hub_hosted.adoc#global-hub-importing-in-hosted-mode[Importing a managed hub cluster in the hosted mode (Technology Preview)]. 
-
 * For other {global-hub} topics, see link:../global_hub/global_hub_overview.adoc#multicluster-global-hub[multicluster global hub]. 
 
 [#application-whats-new]
 == Applications
 
-* You can now use the {acm-short} `GitOpsCluster` to register a non-{ocp-short} cluster to a {gitops} cluster, giving you more ways to deploy your application. For more information, see: link:../gitops/gitops_registering.adoc#register-non-ocp[Registering non-{ocp-short} clusters to {gitops}].
-
 For other Application topics, see link:../applications/app_management_overview.adoc#managing-applications[Managing applications].
 
 [#observability-whats-new]
 == Observability
 
-* For more environment stability with default settings, the default CPU request is increased to `500m` and memory request is increased to `1024Mi` for the `thanos-compact` pod. See link:../observability/obs_config.adoc#observability-pod-capacity-requests[Observability pod capacity requests] for more details.
-
-* To create and mount secrets to your `alertmanager` pods for access to arbitrary content, you can add the contents to your `MultiClusterObservability` resource. See link:../observability/observability_alerts.adoc#mount-secrets-alertmanager[Mounting secrets within the Alertmanager pods].
-
-* Grafana is updated to version 11.1.5. See link:../observability/design_grafana.adoc#using-grafana-dashboards[Using Grafana dashboards].
-
-* You can now use the _Advanced search_ option from the console by selecting the *Advanced search* drop-down button. Specify your query and receive results that match the exact strings that you enter and range-based search parameters. See link:../console/search_console.adoc#search-customization[Search customization and configurations].
-
 See link:../observability/observe_environments_intro.adoc#observing-environments-intro[Observability service introduction].
 
 [#governance-whats-new]
 == Governance
 
-* To configure a cluster based on the available node roles, you can now use the `getNodesWithExactRoles` function to receive a list of nodes, and use the `hasNodesWithExactRoles` function to receive confirmation about clusters that contain nodes with only the roles that you specified. See link:../governance/template_functions.adoc#template-functions[Template functions] for more details.
-
-* You can now define additional health checks and customize status messages for your resource kinds by configuring your `ArgoCD` resource. See link:../gitops/gitops_manage_policy_def.adoc#config-gitops-healthcheck[Configuring policy health checks in {gitops}] for more information.
-
-* To add more clarity for compliance messages in your configuration policies, you can now customize compliance messages by using the `spec.customMessage` fields. See the link:../governance/config_policy_ctrl.adoc#configuration-policy-yaml-table[Kubernetes configuration policy controller].
-
-* You can use the `.PolicyMetadata` hub cluster template variable now to access the metadata of a root policy. See the link:../governance/template_support_intro.adoc#template-comparison-table[Comparison of hub cluster and managed cluster templates].
-
-* You can now use the `hubTemplateOptions.serviceAccountName` field to specify a service account to expand and control access for all hub cluster template lookups. See the link:../governance/template_support_intro.adoc#template-comparison-table[Comparison of hub cluster and managed cluster templates].
-
-* To specify `containerArguments` in the {gate}, provide a list of argument names and values to pass to the container. See the link:../governance/gatekeeper_operator/config_gk_operator.adoc#gatekeeper-custom-resource[Gatekeeper custom resource sample].
-
-* The default value for `spec.evaluationInterval.compliant` and `spec.evaluationInterval.noncompliant` is `watch`, so now you can use Kubernetes API watches instead of polling the Kubernetes API server. See link:../governance/config_policy_ctrl.adoc#configuration-policy-yaml-table[Configuration policy YAML table] for more information.
-
-* With the new command-line tools, you can download the `PolicyGenerator` to generate policies with Kustomize from Kubernetes manifests. You can also use `policytools` with a `template-resolver` subcommand to resolve templates locally. See link:../governance/policy_generator.adoc#policy-generator[Policy Generator] to learn more about the policy generator. See link:../governance/manage_policies.adoc#policy-cli-commands[Policy command line interface] for more details about `policytools`.
-
-* As you directly apply {acm-short} policies and Gatekeeper constraints on your managed clusters, you can now view the deployment of the policies in the _Discovered policies_ tab from the console. See link:../governance/pol_deploy_ext_tools.adoc#policy-deploy-ext-tools[Policy deployment with external tools].
-
 See link:../governance/grc_intro.adoc#governance[Governance] to learn more about the dashboard and the policy framework.
 
 [#dr4hub-whats-new]
 == Backup and restore
 
-* You now have a scenario where you can run a disaster recovery test. By simulating a disaster, you can practice the following actions: restoring hub cluster data on a new hub cluster, verifying that data is recovered, and returning to the initial hub cluster by using the primary hub cluster as a the active hub cluster. See link:../business_continuity/backup_restore/backup_return_hub.adoc#return-initial-hub[Returning to the initial hub cluster after a restore].
-
-* You can now use an existing hub cluster as a restore hub cluster by tagging user-created resources on the restore hub cluster with the `velero.io/backup-name: backupName` label. See link:../business_continuity/backup_restore/use_existing_hub_cluster.adoc#using-existing-hub[Constraints for using an existing hub cluster as a restore hub cluster] and link:../business_continuity/backup_restore/tag_resources.adoc#tagging-resources[Tagging resources]. 
-
-* You can now customize the OADP version by setting an annotation on your `MultiClusterHub` resource. See link:../business_continuity/backup_restore/backup_install.adoc#installing-custom-oadp[Installing a custom OADP version].
-
-* You can now temporarily pause the `BackupSchedule` resource instead of deleting it. By using the `BackupSchedule` `paused` property on the backup hub cluster, you can avoid a backup collision. See link:../business_continuity/backup_restore/backup_schedule.adoc#prevent-backup-collision[Preventing backup collisions].
-
-* You can now keep the primary hub cluster active during a restore operation. See link:../business_continuity/backup_restore/backup_active_restore.adoc#keep-hub-active-restore[Keeping the primary hub cluster active during a restore process].
-
-* With {acm-short} restore resources, you can set more `velero.io.restore` `spec` options. See link:../business_continuity/backup_restore/backup_restore.adoc#more-restore-samples[Using other restore samples].
-
 To learn about disaster recovery solutions for your hub cluster, see link:../business_continuity/backup_restore/backup_install.adoc#backup-intro[Backup and restore].
 
 [#mce-acm-integration]
 == {mce-short} with {acm-short} integration
 
 If you later installed {acm-short} after using stand-alone {mce-short}, you get access to all {acm-short} features. 
-
-* You can enable the `SiteConfig` component from the `MultiClusterHub` custom resource that is deployed on your cluster. Learn more at link:../install/adv_config_install.adoc#advanced-config-hub[MultiClusterHub advanced configuration]. Learn more about {sco} at link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/multicluster_engine_operator_with_red_hat_advanced_cluster_management/siteconfig-intro[SiteConfig].
+// Learn more about the MCE and ACM integration at -- Intro link needed here
 
 [#whats-new-learn-more]
 == Learn more about this release
@@ -144,4 +87,4 @@ If you later installed {acm-short} after using stand-alone {mce-short}, you get
 
 * See support information and more in the {acm-short} link:../troubleshooting/troubleshooting_intro.adoc#troubleshooting[Troubleshooting] guide.
 
-* Access the open source _Open Cluster Management_ repository for interaction, growth, and contributions from the open community. To get involved, see link:https://open-cluster-management.io/[open-cluster-management.io]. Visit the link:https://github.com/open-cluster-management-io[GitHub repository] for more information.
+* Access the open source _Open Cluster Management_ repository for interaction, growth, and contributions from the open community. To get involved, see link:https://open-cluster-management.io/[open-cluster-management.io]. Visit the link:https://github.com/open-cluster-management-io[GitHub repository] for more information.