Replicate backup job to other namespaces

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, go, kubernetes
Domain
devops, infrastructure

Research direction

No file or test is identified in the issue. Start by reviewing the repository's Kubernetes backup example and configuration, then compare every kube-system reference with the production namespace. Done means documenting which namespace-related values must change and confirming the instructions work for production.

Written by the indexing model from the issue text.

Description

Hello,
Congratulations on a fantastic job.

I was able to successfully execute following the example.

Now I'm trying to backup a "production" namespace, but I'm having problems, I believe I must have replaced "kube-system" with "production".

Could you tell me which kinds I need to change from "kube-system" to "production"?

Dominant language
Go
Stars
6
Forks
1
Avg merge
1d 21h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.