From 8e0d13bcfcf50a1dadca5d919a5d074dda4ed255 Mon Sep 17 00:00:00 2001 From: Ellen Date: Fri, 8 Nov 2024 20:37:27 +1000 Subject: [PATCH] Fixing formatting issues --- src/pages/docs/kubernetes/steps/helm.md | 4 ++++ src/pages/docs/kubernetes/steps/kubernetes-ingress.md | 2 ++ src/pages/docs/kubernetes/steps/kubernetes-resources.md | 2 ++ src/pages/docs/kubernetes/steps/kubernetes-service.md | 2 ++ src/pages/docs/kubernetes/steps/kustomize.mdx | 2 ++ src/pages/docs/kubernetes/steps/yaml.md | 4 ++++ 6 files changed, 16 insertions(+) diff --git a/src/pages/docs/kubernetes/steps/helm.md b/src/pages/docs/kubernetes/steps/helm.md index 0cc243c91..cfd212d5a 100644 --- a/src/pages/docs/kubernetes/steps/helm.md +++ b/src/pages/docs/kubernetes/steps/helm.md @@ -192,9 +192,13 @@ To ensure a smooth deployment experience, we recommend setting a larger Octopus :::div{.hint} **Step updates** + **2024.1:** + - `Upgrade a Helm Chart` was renamed to `Deploy a Helm chart`. - Support was added for Helm charts stored in Git repositories. You can learn more in [this blog post](https://octopus.com/blog/git-resources-in-deployments). + **2023.3.4127** + - Support was added for Helm repositories stored in OCI-based registries. ::: \ No newline at end of file diff --git a/src/pages/docs/kubernetes/steps/kubernetes-ingress.md b/src/pages/docs/kubernetes/steps/kubernetes-ingress.md index 2313b9b09..55598b833 100644 --- a/src/pages/docs/kubernetes/steps/kubernetes-ingress.md +++ b/src/pages/docs/kubernetes/steps/kubernetes-ingress.md @@ -79,6 +79,8 @@ When there are no matching ingress rules, traffic can be sent to the service con :::div{.hint} **Step updates** + **2024.1:** + - `Deploy Kubernetes ingress resource` was renamed to `Configure and apply a Kubernetes Ingress`. ::: \ No newline at end of file diff --git a/src/pages/docs/kubernetes/steps/kubernetes-resources.md b/src/pages/docs/kubernetes/steps/kubernetes-resources.md index eb64d1ce1..12425be08 100644 --- a/src/pages/docs/kubernetes/steps/kubernetes-resources.md +++ b/src/pages/docs/kubernetes/steps/kubernetes-resources.md @@ -1053,6 +1053,8 @@ For example, to change the name assigned to the ConfigMap resource to include th :::div{.hint} **Step updates** + **2024.1:** + - `Deploy Kubernetes containers` was renamed to `Configure and apply Kubernetes resources`. ::: \ No newline at end of file diff --git a/src/pages/docs/kubernetes/steps/kubernetes-service.md b/src/pages/docs/kubernetes/steps/kubernetes-service.md index 76e4a4176..69e7cdc2c 100644 --- a/src/pages/docs/kubernetes/steps/kubernetes-service.md +++ b/src/pages/docs/kubernetes/steps/kubernetes-service.md @@ -79,6 +79,8 @@ There are some advanced use cases where creating a Service resource without sele :::div{.hint} **Step updates** + **2024.1:** + - `Deploy Kubernetes service resource` was renamed to `Configure and apply a Kubernetes Service`. ::: \ No newline at end of file diff --git a/src/pages/docs/kubernetes/steps/kustomize.mdx b/src/pages/docs/kubernetes/steps/kustomize.mdx index 429b352e7..d8c236c4c 100644 --- a/src/pages/docs/kubernetes/steps/kustomize.mdx +++ b/src/pages/docs/kubernetes/steps/kustomize.mdx @@ -91,7 +91,9 @@ The "`#{Octopus.Action.Package[nginx].PackageVersion}`" Octostache expression wi :::div{.hint} **Step updates** + **2024.1:** + - `Kustomize` was renamed to `Deploy with Kustomize`. - If you store your project configuration in a Git repository using the [Configuration as code feature](/docs/projects/version-control), you can source your Kustomize files from the same Git repository as your deployment process by selecting Project as the Git repository source. When creating a Release, the commit hash used for your deployment process will also be used to source the Kustomize files. You can learn more in [this blog post](https://octopus.com/blog/git-resources-in-deployments). ::: \ No newline at end of file diff --git a/src/pages/docs/kubernetes/steps/yaml.md b/src/pages/docs/kubernetes/steps/yaml.md index 0381f904b..23929a496 100644 --- a/src/pages/docs/kubernetes/steps/yaml.md +++ b/src/pages/docs/kubernetes/steps/yaml.md @@ -113,9 +113,13 @@ There are a few different ways to take advantage of this feature: :::div{.hint} **Step updates** + **2024.1:** + - `Deploy Raw Kubernetes YAML` was renamed to `Deploy Kubernetes YAML`. - If you store your project configuration in a Git repository using the [Configuration as code feature](/docs/projects/version-control), you can source your YAML from the same Git repository as your deployment process by selecting Project as the Git repository source. When creating a Release, the commit hash used for your deployment process will also be used to source the YAML files. You can learn more in [this blog post](https://octopus.com/blog/git-resources-in-deployments). + **2023.3:** + - Sourcing from Git Repositories was added. You can learn more in [this blog post](https://octopus.com/blog/manifests-from-git). ::: \ No newline at end of file