Skip to content

Conversation

@HuyPhanNguyen
Copy link
Contributor

Add Octopus.Action.Kubernetes.VerboseOutput variable to log CLI tool output at Info level for Kubernetes steps

OctopusDeploy/Issues#9786


Setting the Octopus variable `Octopus.Action.Kubernetes.OutputKubeConfig` to `True` for any deployment or runbook using a Kubernetes target will cause the generated kube config file to be printed into the logs (with passwords masked). This can be used to verify the configuration file used to connect to the Kubernetes cluster.

Setting the Octopus variable `Octopus.Action.Kubernetes.VerboseOutput` to `True` will cause successful output from Kubernetes CLI tools (`kubectl`, `helm`, `aws`, `az`, `gcloud`, etc.) to be logged at the Info level instead of Verbose. This is useful when debugging deployments to see the full output of these tools without needing to enable verbose logging for the entire deployment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could mention the default logging level if this flag is not set or false? For example, do we only log errors if VerboseOutput is False?


`Octopus.Action.Kubernetes.VerboseOutput`

Set to `True` to log successful output from Kubernetes CLI tools (`kubectl`, `helm`, `aws`, `az`, `gcloud`, etc.) at the Info level instead of Verbose. This is useful when debugging deployments to see the full output of these tools without needing to enable verbose logging for the entire deployment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could mention the default logging level if this flag is not set or false? For example, do we only log errors if VerboseOutput is False?

@steve-fenton-octopus
Copy link
Contributor

@HuyPhanNguyen I've fixed the Markdown Lint errors. It would be useful to explain what logging level is set if the flag isn't passed, or is False.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants