GA changes to docs for Agent #2390
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
NickJosevski
commented
Jul 29, 2024
| @@ -44,6 +44,14 @@ If the Agent install command fails with a timeout error, it could be that: | |||
| - (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?
NickJosevski
commented
Jul 29, 2024
| ### 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:
rain-on
reviewed
Jul 29, 2024
|
|
||
| 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.
__
Suggested change
| 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. |
rain-on
reviewed
Jul 29, 2024
|
|
||
| ## Frequently Asked Questions {#FAQ} | ||
|
|
||
| ### Can the agent work with Octopus running in an HA Cluster setup? |
There was a problem hiding this comment.
Suggested change
| ### Can the agent work with Octopus running in an HA Cluster setup? | |
| ### Can the agent work with Octopus running in a HA Cluster setup? |
rain-on
reviewed
Jul 29, 2024
|
|
||
|
|
||
| ### 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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).