Conversation
might be elsewhere
src/pages/docs/infrastructure/deployment-targets/kubernetes/kubernetes-agent/troubleshooting.md
Outdated
Show resolved
Hide resolved
…bernetes-agent/troubleshooting.md Co-authored-by: Mark Coafield <[email protected]>
remove this to put in other page
| - (if using the NFS storage solution) The NFS CSI driver has not been installed | ||
| - (if using a custom Storage Class) the Storage Class name doesn't match | ||
|
|
||
| #### 404 error when setting up the NFS Pod. |
There was a problem hiding this comment.
@APErebus The 404 error when setting up the NFS pod should also just a troubleshooting node
did you mean to put it here under Installation Issues?
| ### When trying to install the Kubernetes Agent on an existing cluster, I get an 401: Unauthorized error. | ||
|
|
||
| ``` | ||
| Error: GET "https://registry-1.docker.io/v2/octopusdeploy/kubernetes-agent/tags/list": |
There was a problem hiding this comment.
this is based on this exchange:
|
|
||
| Check if your version of help is up to date. In versions the error message you might be experiencing is [not shown]([url](https://github.com/helm/helm/blob/1ec0aacb8865d5b1f7ef1cb884bbf9b12579ecef/pkg/action/install.go#L753-L769)). | ||
|
|
||
| Once you version of help is up to date, run `helm repo update` and try again. |
There was a problem hiding this comment.
__
| Once you version of help is up to date, run `helm repo update` and try again. | |
| Once your version of help is up to date, run `helm repo update` and try again. |
|
|
||
| ## Frequently Asked Questions {#FAQ} | ||
|
|
||
| ### Can the agent work with Octopus running in an HA Cluster setup? |
There was a problem hiding this comment.
| ### Can the agent work with Octopus running in an HA Cluster setup? | |
| ### Can the agent work with Octopus running in a HA Cluster setup? |
|
|
||
|
|
||
| ### Can a proxy be specified when setting up the Kubernetes agent? | ||
| Yes! Proxy servers for the polling connection that takes place between the agent and Octopus Server. These can be supplied for setup via the `.pollingProxy.*` helm values. |
There was a problem hiding this comment.
the second sentence feels incomplete - update to be:
Yes! Proxy servers for the polling connection that takes place between the agent and Octopus Server are supported - their configuration can be set via the .pollingProxy.* helm values.
| If that doesn't help, please [get in touch](https://octopus.com/support). | ||
|
|
||
| ### I'm having strange behavior relating to ingress in a HA configuration. | ||
| Carefully look and see that there is a `serverCommsAddress` property for backwards compatibility, and a `serverCommsAddresses` the latter supporting an array input, mistyping these can happen. This has presented itself as a variety of errors depending on the broader configuration, e.g. you may see "it failed to allocate the public ip" if using load balancers. |
There was a problem hiding this comment.
'Carefully look and see ...' felt odd to me - potential reword?
"Carefully check that both the 'serverCommsAddress' and 'ServerCommsAddress' properties exist. The latter supports an array input - errors in these fields may result in erroneous HA behaviour.
|
@NickJosevski this PR has been inactive for over 6 months. Do you want to persist with this change? If so, there's a merge conflict to resolve. |
4 participants
I took the questions and answers from communit slack to create this FAQ at the end of the trouble shooting page.
I opt'd for keeping the question part vague similar to how customers asked it in slack, so more people consider that a specific issue may be what they're experiencing.
The slack messages will slowly be less accessible to us, as there's a rolling window of what we can see (maybe 90 days of history in community slack).