I have spun up Octopus Deploy in a pod in AKS.
I have two workers which are not in AKS and are in the on-prem network.
During one of my deployments, Worker is trying to get an artifact from the Octopus Server and fails.
I realised that the worker is trying to access Octopus Server with a URL which is the pod’s URL within AKS, while we have an internal domain for accessing Octopus Server.
I am wondering if we can change a configuration in the Worker or Octopus Server so that they see each other.
Octopus web request (GET: http://octopusdeploy-web-7d54877985-dc6gq:8080/api/projects/all) failed & will be retried in 30 seconds:
The remote name could not be resolved: 'octopusdeploy-web-7d54877985-dc6gq'
Octopus web request (GET: http://octopusdeploy-web-7d54877985-dc6gq:8080/api/projects/all) failed & will be retried in 60 seconds:
The remote name could not be resolved: 'octopusdeploy-web-7d54877985-dc6gq'
Octopus web request (GET: http://octopusdeploy-web-7d54877985-dc6gq:8080/api/projects/all) failed & will be retried in 120 seconds:
The remote name could not be resolved: 'octopusdeploy-web-7d54877985-dc6gq'
Octopus web request (GET: http://octopusdeploy-web-7d54877985-dc6gq:8080/api/projects/all) failed & the maximum number of retries has been exceeded:
The remote name could not be resolved: 'octopusdeploy-web-7d54877985-dc6gq'
The action Deploy on a Worker failed
Sorry if I misunderstood, but I thought you were making manual API calls. What is the process you are doing above that is resulting in the error? Please provide as much detail as possible.
I was using an old version of Chain Deployment step template and it was using $OctopusParameters['Octopus.Web.BaseUrl'] in it’s code which is not correct.
I updated to the latest version which they have fixed it.