diff --git a/_docs/whats-new/whats-new.md b/_docs/whats-new/whats-new.md index dd42b7de..010e2d11 100644 --- a/_docs/whats-new/whats-new.md +++ b/_docs/whats-new/whats-new.md @@ -7,9 +7,332 @@ redirect_from: toc: true --- -We launched the Codefresh platform in February this year. Built on Argo, the world’s most popular and fastest-growing open source software delivery, Codefresh unlocks the full enterprise potential of Argo Workflows, Argo CD, Argo Events, and Argo Rollouts, providing a control-plane for managing them at scale. +Built on Argo, the world’s most popular and fastest-growing open source software delivery, Codefresh unlocks the full enterprise potential of Argo Workflows, Argo CD, Argo Events, and Argo Rollouts, providing a control-plane for managing them at scale. + + + +## October 2022 + +### Features & enhancements +{::nomarkdown} +
+{:/} + +#### Kubernetes version runtime support +We now support Kubernetes server versions 1.21 and higher. + +{::nomarkdown} +
+{:/} + +#### Request Routing Service for runtimes +We have changed the routing mechanism for hybrid runtimes. URL requests and webhooks are now routed through a new internal routing service instead of through the ingress controller. + +The change is effective from runtime version 0.0.543 and higher. If you already have runtimes installed, this change does not require any action from you, both to upgrade to the new runtime version or retain existing runtimes. Older runtimes continue to use the ingress controller for routing purposes. + +See [Hybrid runtime architecture]({{site.baseurl}}/docs/getting-started/architecture/#hybrid-runtime-architecture) and [Request Routing Service]({{site.baseurl}}/docs/getting-started/architecture/#request-routing-service). + +{::nomarkdown} +
+{:/} + +#### More Git providers for runtimes +Codefresh runtimes now support GitHub Enterprise, GitLab, and Bitbucket as Git providers, apart from GitHub, which is the default. + +When installing the first hybrid or hosted runtime for your account, you can define the Git provider of choice. Because Codefresh creates a configuration repository that is shared with subsequent runtimes in the same account, you cannot change the Git provider for a different runtime in the same account. + +Each Git provider requires runtime tokens with specific scopes and has specific installation requirements. Once installed, you can authorize access to the Git provider through OAuth or a personal access token. + +Note that GitLab cloud is not supported for hosted runtimes. + +See [Git provider and repo flags]({{site.baseurl}}/docs/runtime/installation/#git-provider-and-repo-flags). + +{::nomarkdown} +
+{:/} + +### Turn off notifications for runtimes +Codefresh alerts you to runtimes that are insecure or have invalid or expired Git personal access tokens. You can turn off these notifications selectively for runtimes for which these alerts are less critical, such as non-production runtimes. + +The option is user-specific, and applies only to runtimes in the user's account. + + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png" + url="/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png" + alt="Turn off notifications for selected runtime" + caption="Turn off notifications for selected runtime" + max-width="80%" +%} + +Runtimes with disabled notifications are prefixed with an icon as in the picture below. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png" + url="/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png" + alt="Runtime with disabled notifications" + caption="Runtime with disabled notifications" + max-width="80%" +%} + +{::nomarkdown} +
+{:/} + +#### Rollout Player for deployments +Managing ongoing rollouts during a deployment is now simple with the Rollout Player. Clicking the rollout name in Timeline > Updated Services, displays both the visualization of the steps in the rollout and the Rollout Player. With the Rollout Player you can control individual steps in an ongoing rollout and even promote the rollout to a release. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct-22-rollout-player.png" + url="/images/whats-new/rel-notes-oct-22-rollout-player.png" + alt="Rollout Player" + caption="Rollout Player" + max-width="40%" +%} + + +The Rollput Player allows you to: +* Resume an indefinitley paused step +* Forward a step by skipping its execution +* Promote the rollout to deployment by skipping remaining pause, analysis + +{::nomarkdown} +
+{:/} + +#### Context menu for application resources +We have enhanced the functionality for application resources in the Current State tab with the context menu for resources. The options available differ according to the type of resource. + + + +**On-demand sync for individual application resources** +Sync is a context menu option available for all resources that track sync status. You can sync individual resources as needed or when out-of-sync without synchronizing or refreshing the application. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct-22-sync-context-menu.png" + url="/images/whats-new/rel-notes-oct-22-sync-context-menu.png" + alt="Sync option in resource context menu" + caption="Sync option in resource context menu" + max-width="50%" +%} + +**Rollout resource actions** +The context menu for `rollout` resource types have actions to control the rollout. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct22-rollout-context-menu.png" + url="/images/whats-new/rel-notes-oct22-rollout-context-menu.png" + alt="Context menu options for Rollout resource" + caption="Context menu options for Rollout resource" + max-width="50%" +%} + +{::nomarkdown} +
+{:/} + +#### Other enhancements + +**Git Sources as Application Type filter** +The list of filters for Application Type in the Applications dashboard includes the Git Source filter. Filtering by Git Source shows `Git Source Apps` which are applications created by Codefresh that store definitions of Argo Project resources. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct22-app-type-git-source.png" + url="/images/whats-new/rel-notes-oct22-app-type-git-source.png" + alt="Git Source as Application Type filter" + caption="Git Source as Application Type filter" + max-width="40%" +%} + + +**Manifests for Analysis Runs** +Analysis Run now shows the manifest in addition to the run results. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-oct22-analysis-run-manifest.png" + url="/images/whats-new/rel-notes-oct22-analysis-run-manifest.png" + alt="Manifest for Analysis Run" + caption="Manifest for Analysis Run" + max-width="40%" +%} + +{::nomarkdown} +
+{:/} + +### Bug fixes + +{::nomarkdown} +
+{:/} + +**Runtimes** + +* 500: Internal Server Error when adding cluster command to hosted runtime. +* Commit SHA link in Activity Log goes to the Home page instead of to the Commit URL for the Git provider. +* Ingress controller errors for cluster even when `skip-ingress` flag is defined. +* Retry mechanism requests cause delay in Git integration checks. +* For hosted runtimes, Git Source is not displayed though the Connect to Git provider step is marked as complete. +* No option to log out on selecting invalid authentication mode. +* Removing a managed cluster does not display any indication in Codefresh UI. +* Up-to-date runtimes display upgrade indication. + + +{::nomarkdown} +
+{:/} + +**Applications** +* Applications deleted in Git displayed as errors, or as Missing in Codefresh. +* Tagging/untagging favorite application breaks relationship to parent application. +* Application definitions validation for cluster URL that does not exist shows wrong entity type. +* Incorrect number of replicas for previous image in Applications dashboard. +* Mismatch between information reported for cluster and namespace in Applications dashboard and Images. +* Source link in Timeline tab redirects to incorrect branch. +* Missing Health indication for Argo Rollouts in Codefresh UI. + +{::nomarkdown} +
+{:/} + +**Delivery Pipelines and workflows** +* 100% CPU consumption for workflows with more than 20 nodes. +* Discard Changes button enabled when there are no changes. + + +## September 2022 + + + +### Features & enhancements +{::nomarkdown} +
+{:/} + +#### Enriched application header +Every application includes a header that highlights key information and links to key aspects of the application. For example, you can see both the current sync state and the result of the previous sync operation, with links to pull-out panels including additional details. + + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-sep22-app-header.png" + url="/images/whats-new/rel-notes-sep22-app-header.png" + alt="Application header for selected appplication" + caption="Application header for selected appplication" + max-width="80%" +%} + +#### Refresh and hard refresh to manage applications +Just as you can manually synchronize applications directly in Codefresh, you can now perform Refresh and Hard Refresh for applications. +In the Applications dashboard, both options are available in the context menu of each application. On selecting an application, you can see them on the top-right next to the Synchronize button. + + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png" + url="/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png" + alt="Refresh/Hard refresh options for selected application" + caption="Refresh/Hard refresh options for selected application" + max-width="80%" +%} + + + +#### Click resume indefinitely paused rollouts +Argo Rollouts allows you to pause a rollout indefinitely and resume it manually instead of automatically after a fixed duration. Manually resuming a rollout is generally done through the CLI. +Codefresh provides you the option of resuming an indefinitely paused rollout directly from the Applications dashboard in Codefresh, with a single click. + +In the Timelines tab of the selected application, an ongoing rollout that is indefinitely paused displays the pause button. Resuming the rollout is as simple as clicking the pause button. + + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-sep22-resume-pause.png" + url="/images/whats-new/rel-notes-sep22-resume-pause.png" + alt="Resume indefinitley paused rollout" + caption="Resume indefinitley paused rollout" + max-width="60%" +%} + +#### Custom path for application resources +When creating applications, in addition to changing the name of the manifest, you can now also define the path for the manifest within the Git Source. Use the front slash (/) to add subfolders to the path. The resource is created in the Git Source you select, according to the path you defined. + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-sep22-app-yaml-location.png" + url="/images/whats-new/rel-notes-sep22-app-yaml-location.png" + alt="Define location for application YAML" + caption="Define location for application YAML" + max-width="60%" +%} + + + +#### Events tab for applications +In the previous month's release, we added the Events panel displaying successful and events for the application. +For more visibility and easier access, the same Events tab is now displayed with the Current State, Timeline, Services, and Configuration tabs for the selected application. + + +{% include + image.html + lightbox="true" + file="/images/whats-new/rel-notes-sep22-events-tab.png" + url="/images/whats-new/rel-notes-sep22-events-tab.png" + alt="Events tab for application" + caption="Events tab for application" + max-width="60%" +%} + + +### Bug fixes + +{::nomarkdown} +
+{:/} + +**Runtimes** +* Incorrect status for Hosted runtime when app-proxy is unreachable. +* Git provider not registered for hosted runtimes with Git Sources defined in the shared configuration repo. +* Authentication failure between platform and app proxy. +* Adding cluster to a runtime shows an error even when the cluster is added to the runtime. +* Duplicate dates in Activity Log notifications. +* Argo CD fails to connect to K8s 1.24 clusters. +* After uninstalling a runtime, argo-rollouts and rollout-reporter files remain for managed cluster remain in shared configuration repo. +* Deleted managed cluster shows as Unknown. + +{::nomarkdown} +
+{:/} + +**Applications** +* Health status does not change to progressing when previously degraded. +* Wrong git source reference +* Git Source applications in the Applications dashboard not reflected in the Runtimes > Git Source tab. +* Switching from YAML to form view after changing fields does not update validations. +* App details drawer crashes when application does not have resources. +* Missing namespace for resources. +* Full Screen does not work in Safari. +* Recreating an application with the same name as that of a deleted application displays incorrect data for rollouts in the Timeline tab. +* In the Timeline tab, data for a new release with long sync duration is assigned to the previous release. -This month's release is all about quality and usability. ## August 2022 @@ -142,6 +465,8 @@ max-width="60%" * Test Connection option disabled when integration name is not defined. + + ## July 2022 ### Features & enhancements @@ -446,7 +771,7 @@ By the very nature of its design, the Tree View allows progressive discovery. Vi **Resource filters** -The filters in the List view are available also in the Tree view. These global filters help narrow the scope of the resources displayed, by kind, health status, and sync state. The filters set in either the List or Tree views are retained when navigating between them. +The filters in the List view are available also in the Tree view. These global filters help narrow the scope of the resources displayed, by kind, health status, and sync state. The filters set in either the List or Tree vies are retained when navigating between them. **Resource search and find** @@ -473,7 +798,7 @@ For details, see [Current State Tree view]({{site.baseurl}}/docs/deployment/appl In addition to installing Argo Rollouts in your cluster, visualize Argo Rollout history and progress directly in the Applications (deployment) dashboard. Visualize rollouts from multiple clusters and runtimes in a single centralized location through the Deployment tab. **Rollout progress** -Ongoing rollouts show the progress of the rollout in real time. Completed rollouts show the switch to the new version according to the deployment strategy. +Ongoing rollouts show the progress of the rollout in the real time. Completed rollouts show the switch to the new version according to the deployment strategy. {% include image.html @@ -604,7 +929,7 @@ For details, see [Runtime installation flags]({{site.baseurl}}/docs/runtime/inst #### Internal and external ingress hosts Codefresh runtimes support defining two ingress hosts, an internal and an external ingress host, for private and public networks. Previously, runtimes supported a single ingress host for both the app-proxy and webhook ingress resources. Internal and external ingress separation allows you to expose the Codefresh app-proxy service only within your private network, while keeping the webhook ingress unchanged. -* New runtime installations: The `--internal-ingress-host` flag lets you define an ingress host for communication with the app-proxy. For details, see [Runtime installation flags]({{site.baseurl}}/docs/runtime/installation/#runtime-installation-flags). +* New runtime installations: The `--internal-ingress-host` flag lets you can define an ingress host for communication with the app-proxy. For details, see [Runtime installation flags]({{site.baseurl}}/docs/runtime/installation/#runtime-installation-flags). * Existing runtimes: To add an internal ingress host, you need to commit changes to the installation repository by modifying `app-proxy ingress` and `.yaml`. For details, see _Internal ingress host configuration (optional)_ in [Post-installation configuration]({{site.baseurl}}/docs/runtime/installation#post-installation-configuration). diff --git a/images/whats-new/rel-notes-oct-22-rollout-player.png b/images/whats-new/rel-notes-oct-22-rollout-player.png new file mode 100644 index 00000000..1e01193c Binary files /dev/null and b/images/whats-new/rel-notes-oct-22-rollout-player.png differ diff --git a/images/whats-new/rel-notes-oct-22-sync-context-menu.png b/images/whats-new/rel-notes-oct-22-sync-context-menu.png new file mode 100644 index 00000000..bb1422bd Binary files /dev/null and b/images/whats-new/rel-notes-oct-22-sync-context-menu.png differ diff --git a/images/whats-new/rel-notes-oct22-analysis-run-manifest.png b/images/whats-new/rel-notes-oct22-analysis-run-manifest.png new file mode 100644 index 00000000..5305fb84 Binary files /dev/null and b/images/whats-new/rel-notes-oct22-analysis-run-manifest.png differ diff --git a/images/whats-new/rel-notes-oct22-app-type-git-source.png b/images/whats-new/rel-notes-oct22-app-type-git-source.png new file mode 100644 index 00000000..76e68fb2 Binary files /dev/null and b/images/whats-new/rel-notes-oct22-app-type-git-source.png differ diff --git a/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png b/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png new file mode 100644 index 00000000..c443db56 Binary files /dev/null and b/images/whats-new/rel-notes-oct22-dimiss-notifications-indication.png differ diff --git a/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png b/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png new file mode 100644 index 00000000..7d303e1d Binary files /dev/null and b/images/whats-new/rel-notes-oct22-dismiss-runtime-notifications.png differ diff --git a/images/whats-new/rel-notes-oct22-rollout-context-menu.png b/images/whats-new/rel-notes-oct22-rollout-context-menu.png new file mode 100644 index 00000000..d7a34f01 Binary files /dev/null and b/images/whats-new/rel-notes-oct22-rollout-context-menu.png differ diff --git a/images/whats-new/rel-notes-sep22-app-header.png b/images/whats-new/rel-notes-sep22-app-header.png new file mode 100644 index 00000000..87f2aab7 Binary files /dev/null and b/images/whats-new/rel-notes-sep22-app-header.png differ diff --git a/images/whats-new/rel-notes-sep22-app-yaml-location.png b/images/whats-new/rel-notes-sep22-app-yaml-location.png new file mode 100644 index 00000000..7d2b07c5 Binary files /dev/null and b/images/whats-new/rel-notes-sep22-app-yaml-location.png differ diff --git a/images/whats-new/rel-notes-sep22-card-view.png b/images/whats-new/rel-notes-sep22-card-view.png new file mode 100644 index 00000000..91feb877 Binary files /dev/null and b/images/whats-new/rel-notes-sep22-card-view.png differ diff --git a/images/whats-new/rel-notes-sep22-events-tab.png b/images/whats-new/rel-notes-sep22-events-tab.png new file mode 100644 index 00000000..d6500463 Binary files /dev/null and b/images/whats-new/rel-notes-sep22-events-tab.png differ diff --git a/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png b/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png new file mode 100644 index 00000000..235d9987 Binary files /dev/null and b/images/whats-new/rel-notes-sep22-refresh-hardrefresh.png differ diff --git a/images/whats-new/rel-notes-sep22-resume-pause.png b/images/whats-new/rel-notes-sep22-resume-pause.png new file mode 100644 index 00000000..b5439bab Binary files /dev/null and b/images/whats-new/rel-notes-sep22-resume-pause.png differ