Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add supportbundle information to antctl documentation #812

Conversation

antoninbas
Copy link
Contributor

We add information on par with what we have for the other antctl
commands.

Fixes #765

Some formatting issues are fixed in the documentation:

  • broken relative links
  • an empty line is required before code blocks or the markdown
    documentation does not render properly on the netlify website

We also include some very minor code changes for antctl:

  • the directory where support bundles are collected is created later,
    to avoid creating a directory in case of an early error (e.g. invalid
    kubeconfig)
  • the timestamp suffix for the default directory name now uses a more
    UNIX filepath-friendly format. We also do not generate the default
    directory name when registering the --dir flag, as it causes the
    help output to change every time the command is invoked.

@antrea-bot
Copy link
Collaborator

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

  • /test-e2e: to trigger e2e tests.
  • /skip-e2e: to skip e2e tests.
  • /test-conformance: to trigger conformance tests.
  • /skip-conformance: to skip conformance tests.
  • /test-networkpolicy: to trigger networkpolicy tests.
  • /skip-networkpolicy: to skip networkpolicy tests.
  • /test-windows-conformance: to trigger windows conformance tests.
  • /skip-windows-conformance: to skip windows conformance tests.
  • /test-all: to trigger all tests.
  • /skip-all: to skip all tests.

These commands can only be run by members of the vmware-tanzu organization.

Copy link
Contributor

@jianjuns jianjuns left a comment

Choose a reason for hiding this comment

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

Just a NIT.

docs/antctl.md Outdated Show resolved Hide resolved
including logs, so please review the contents of the directory before sharing
it on Github and ensure that you do not share anything sensitive.**

The `antctl supportbundle` command can also be run inside a Controller or Agent
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you want to mention we are able to collect bundles of only matched Nodes?

BTW, I suggested to review the current command design: provide a flag to collect controller bundle only; command with a matching expression should not include controller bundle.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree with your points. I'm aware of the --controller-only flag. It seems that matching on Node name still collects cluster info & controller bundle.

I'm happy to update this document in the future when changes are made to the command. For now, I'd rather not include information that may become stale soon if the command is still evolving.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good to me.

docs/antctl.md Outdated Show resolved Hide resolved
We add information on par with what we have for the other antctl
commands.

Fixes antrea-io#765

Some formatting issues are fixed in the documentation:
 * broken relative links
 * an empty line is required before code blocks or the markdown
   documentation does not render properly on the netlify website

We also include some very minor code changes for antctl:
 * the directory where support bundles are collected is created later,
   to avoid creating a directory in case of an early error (e.g. invalid
   kubeconfig)
 * the timestamp suffix for the default directory name now uses a more
   UNIX filepath-friendly format. We also do not generate the default
   directory name when registering the `--dir` flag, as it causes the
   help output to change every time the command is invoked.
@antoninbas antoninbas force-pushed the add-supportbundle-information-to-antctl-documentation branch from e888c9b to 5a533a0 Compare June 10, 2020 00:45
@antoninbas
Copy link
Contributor Author

/test-all

@antoninbas
Copy link
Contributor Author

/test-conformance

@antoninbas
Copy link
Contributor Author

/test-windows-conformance

@antoninbas antoninbas merged commit 07d2484 into antrea-io:master Jun 10, 2020
@antoninbas antoninbas deleted the add-supportbundle-information-to-antctl-documentation branch June 10, 2020 20:23
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.

antctl documentation is missing information about support-bundle
5 participants