diff --git a/src/pages/docs/deployments/kubernetes/deploy-container/index.md b/src/pages/docs/deployments/kubernetes/deploy-container/index.md index 93e55bcae1..181399b2e9 100644 --- a/src/pages/docs/deployments/kubernetes/deploy-container/index.md +++ b/src/pages/docs/deployments/kubernetes/deploy-container/index.md @@ -1,7 +1,7 @@ --- layout: src/layouts/Default.astro pubDate: 2023-01-01 -modDate: 2024-04-23 +modDate: 2024-06-25 title: Configure and apply Kubernetes resources description: Configure and apply Kubernetes resources. navOrder: 10 @@ -597,7 +597,7 @@ The [command and arguments](https://oc.to/KubernetesCommand) that are executed w This section has two fields: `Command` and `Command arguments`. Each plays a slightly different role relating to how Docker images define the command that is used to launch the container. -Docker images can define an [ENTRYPOINT](https://oc.to/DockerEntrypoint), a [CMD](https://oc.to/Docker/), or both. +Docker images can define an [ENTRYPOINT](https://oc.to/DockerEntrypoint), a [CMD](https://docs.docker.com/reference/dockerfile/#cmd), or both. When both are defined, the CMD value is passed to the ENTRYPOINT. So if CMD is set to `["hello", "world"]` and ENTRYPOINT is set to `["print"]`, the resulting command would be `print hello world`. @@ -677,7 +677,7 @@ The [command and arguments](https://oc.to/KubernetesCommand) that are executed w This section has two fields: `Command` and `Command arguments`. Each plays a slightly different role relating to how Docker images define the command that is used to launch the container. -Docker images can define an [ENTRYPOINT](https://oc.to/DockerEntrypoint), a [CMD](https://oc.to/Docker/), or both. +Docker images can define an [ENTRYPOINT](https://oc.to/DockerEntrypoint), a [CMD](https://docs.docker.com/reference/dockerfile/#cmd), or both. When both are defined, the CMD value is passed to the ENTRYPOINT. So if CMD is set to `["hello", "world"]` and ENTRYPOINT is set to `["print"]`, the resulting command would be `print hello world`. diff --git a/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template.mdx b/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template.mdx index 8ef5bfbba7..8318ed1147 100644 --- a/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template.mdx +++ b/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template.mdx @@ -1,73 +1,9 @@ +--- +layout: src/layouts/Redirect.astro +title: Redirect +redirect: https://octopus.com/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template-with-dsc +pubDate: 2024-06-25 +navSearch: false +navSitemap: false +navMenu: false --- -layout: src/layouts/Default.astro -pubDate: 2023-01-01 -modDate: 2023-01-01 -title: Installing the Tentacle VM extension via an ARM template -description: How to install the Tentacle VM extension using an Azure Resource Manager (ARM) template -navOrder: 6 ---- -import AzureVMExtensionDeprecated from 'src/shared-content/deprecated-items/azure-vm-extension-deprecated.include.md'; - - - -An Azure Resource Manager (ARM) template is a JSON file that defines a set of Azure resources that can be automatically read and provisioned by Azure. - -Using an ARM template, you can deploy the Tentacle VM extension at the same time you create the virtual machine, or update the resource group to apply the extension later. - -:::div{.hint} -A [fully functioning example](https://azure.microsoft.com/en-gb/resources/templates/octopus-deploy-tentacle-windows/) can be found in the [Azure Quickstart Templates](https://azure.microsoft.com/en-gb/resources/templates/) library. -::: - -Create your ARM template as normal, and add a `resources` element under your `Microsoft.Compute/virtualMachine` resource: - -```json -"resources": [ - { - "type": "extensions", - "name": "[concat(parameters('vmName'),'/OctopusDeployWindowsTentacle')]", - "apiVersion": "2015-05-01-preview", - "location": "[resourceGroup().location]", - "dependsOn": [ - "[concat('Microsoft.Compute/virtualMachines/', parameters('vmName'))]" - ], - "properties": { - "publisher": "OctopusDeploy.Tentacle", - "type": "OctopusDeployWindowsTentacle", - "typeHandlerVersion": "2.0", - "autoUpgradeMinorVersion": "true", - "forceUpdateTag": "1.0", - "settings": { - "OctopusServerUrl": "http://localhost:81", - "Environments": [ - "Development", - "Staging" - ], - "Roles": [ - "App Server", - "Web Server" - ], - "CommunicationMode": "Listen", - "Port": 10933, - "PublicHostNameConfiguration": "PublicIP" - }, - "protectedSettings": { - "ApiKey": "API-ABCDEF1234567890ABCDEF12345" - } - } - } -] -``` - -## Properties - -* `publisher`: (string) Must be `OctopusDeploy.Tentacle`. -* `type`: (string) Must be `OctopusDeployWindowsTentacle`. -* `typeHandlerVersion`: (string): The major and minor version of the extension to apply. You can find what versions are available [via the Azure CLI](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-cli). -* `autoUpgradeMinorVersion`: (string) Indicates whether the extension version should be automatically updated to a newer minor version. Accepts the values `true` or `false`. -* `forceUpdateTag`: (string) Any user defined value that can be modified to force the extension to re-run, even if none of the `settings` or `protectedSettings` have changed. - -Please refer to the [configuration structure](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/configuration-structure) for details regarding the format of the `settings` and `protectedSettings` elements. - -:::div{.hint} -If you need more the ability to customize more of the installation, you might want to consider using the [Azure Desired State Configuration (DSC) extension](https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-overview) in conjunction with the [OctopusDSC](https://www.powershellgallery.com/packages/OctopusDSC) resource. -::: diff --git a/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-portal.mdx b/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-portal.mdx index 03f7448f22..e4d96d94b6 100644 --- a/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-portal.mdx +++ b/src/pages/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-portal.mdx @@ -1,7 +1,7 @@ --- layout: src/layouts/Default.astro pubDate: 2023-01-01 -modDate: 2023-01-01 +modDate: 2023-06-25 title: Installing the Tentacle VM extension via the Azure Portal description: How to install a Tentacle using the Azure VM Extension via the new Azure Portal navOrder: 2 @@ -61,5 +61,5 @@ After entering the extension settings, click **OK**, and the extension will be i After a few minutes, the machine should appear in the environments tab of your Octopus Server. If it doesn't, please read the [Diagnosing issues](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/diagnosing-issues) section. :::div{.hint} -If you need the ability to customize more of the installation, the [CLI](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-cli/), [PowerShell](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-powershell/) and [ARM Template](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-an-arm-template) methods expose more options than the Azure Portal. For even more customization, you might want to consider using the [Azure Desired State Configuration (DSC) extension](https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-overview) in conjunction with the [OctopusDSC](https://www.powershellgallery.com/packages/OctopusDSC) resource. +If you need the ability to customize more of the installation, the [CLI](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-the-azure-cli/) and [PowerShell](/docs/infrastructure/deployment-targets/tentacle/windows/azure-virtual-machines/via-powershell/) methods expose more options than the Azure Portal. For even more customization, you might want to consider using the [Azure Desired State Configuration (DSC) extension](https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-overview) in conjunction with the [OctopusDSC](https://www.powershellgallery.com/packages/OctopusDSC) resource. :::