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

Documentation and scripts should use full name ie. backups.velero.io #8461

Open
kaovilai opened this issue Nov 26, 2024 · 1 comment
Open

Comments

@kaovilai
Copy link
Member

What steps did you take and what happened:

Per best practices: https://kubernetes.io/docs/reference/kubectl/conventions/#using-kubectl-in-reusable-scripts

We should be using full name when referring to velero api objects.

To name a few of the conflicting APIs existing today

backups.velero.io
backups.postgresql.k8s.enterprisedb.io
backups.infinispan.org
backups.postgresql.cnpg.io
backups.data-protection.isf.ibm.com
backups.redis.databases.cloud.ibm.com
backups.netbackup.veritas.com

The following information will help us better understand what's going on:

If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help

If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)

  • kubectl logs deployment/velero -n velero
  • velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
  • velero backup logs <backupname>
  • velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
  • velero restore logs <restorename>

Anything else you would like to add:

Environment:

  • Velero version (use velero version):
  • Velero features (use velero client config get features):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • 👍 for "I would like to see this bug fixed as soon as possible"
  • 👎 for "There are more important bugs to focus on right now"
@kaovilai
Copy link
Member Author

From community meeting we'll add to troubleshooting sections if there isn't already a note on conflicting short name.

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

No branches or pull requests

1 participant