Giter Club home page Giter Club logo

cluster-backup-operator's Introduction

Welcome to the Stolostron Project

Getting started with Red Hat Advanced Cluster Management for Kubernetes? Ready to manage your fleet of OpenShift and Kubernetes clusters? You're in the right place! The Stolostron project houses the projects built into Red Hat Advanced Cluster Management for Kubernetes. This repo contains tools, integrations, and suggestions to jumpstart your multicluster and multicloud presence!

Looking for Development Preview Content?

If you're looking to try out our Development Preview content - you're in the right place! Visit our Development Preview Section to discover, install, use, and provide feedback for our new features and capabilities. Your feedback is most welcome and will help us shape the future of these features!

Getting Started Resources

Day 0

Description Link
Sizing Documentation TBD
Results from 1k SNO Scale Testing TBD
Results from 2k SNO Scale Testing TBD

Day 1

GITOPS is short for Openshift-Gitops. Pipeline is short for Openshift-Pipelines. AAP is Ansible Automation Platform.

Description Link Technology
Bare metal Zero Touch Provisioning https://github.com/jparrill/ztp-the-hard-way ACM, GITOPS
OpenShift 4 Azure IPI installation https://github.com/stolostron/ocp4-azure-ipi AAP
ACM managed service Deployment https://github.com/stolostron/acm-aap-aas-operations AAP, ACM, GITOPS
Openshift-Pipeline ACM Pipelines https://github.com/stolostron/openshift-pipelines Pipeline

Day 2

Description Link
A comprehensive collection of managing your fleet using RHACM Policies https://github.com/stolostron/policy-collection
Collection of Kustomize bases https://github.com/redhat-cop/gitops-catalog
Operate First https://github.com/operate-first/apps
cm cli https://github.com/stolostron/cm-cli
RHACM Ansible collection project https://github.com/stolostron/ansible-collection.core
RHACM: How to configure an ApplicationSet to deploy Policies? https://access.redhat.com/solutions/6553071
RHACM: Can Policies also be applied via Gitops when using ArgoCD? https://access.redhat.com/solutions/6435991
RHACM: What is the Polling Interval in ArgoCD-Applications compared to RHACM-Applications? https://access.redhat.com/solutions/6390571

Reference:

https://www.redhat.com/en/blog/how-does-red-hat-support-day-2-operations

cluster-backup-operator's People

Contributors

birsanv avatar jnpacker avatar o-farag avatar openshift-ci[bot] avatar sahare avatar sdminonne avatar tesshuflower avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

cluster-backup-operator's Issues

when run the restore hub cluster backup showing error

when run the restore cluster backup showing this error
[[email protected] ~]# oc describe Restore.cluster.open-cluster-management.io -n open-cluster-management-backup
Name: restore-acm
Namespace: open-cluster-management-backup
Labels:
Annotations:
API Version: cluster.open-cluster-management.io/v1beta1
Kind: Restore
Metadata:
Creation Timestamp: 2022-10-06T14:22:08Z
Generation: 4
Managed Fields:
API Version: cluster.open-cluster-management.io/v1beta1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:cleanupBeforeRestore:
f:veleroCredentialsBackupName:
f:veleroManagedClustersBackupName:
f:veleroResourcesBackupName:
Manager: kubectl-client-side-apply
Operation: Update
Time: 2022-10-06T14:22:08Z
API Version: cluster.open-cluster-management.io/v1beta1
Fields Type: FieldsV1
fieldsV1:
f:status:
.:
f:lastMessage:
f:phase:
Manager: manager
Operation: Update
Subresource: status
Time: 2022-10-06T14:22:08Z
Resource Version: 5398419
UID: 2891e9f8-b207-4323-b574-656c3f1174ad
Spec:
Cleanup Before Restore: CleanupAll
Velero Credentials Backup Name: acm-credentials-cluster-schedule-20221006140010
Velero Managed Clusters Backup Name: acm-managed-clusters-schedule-20221006140010
Velero Resources Backup Name: acm-resources-schedule-20221006140010
Status:
Last Message: This resource is ignored because BackupSchedule resource open-cluster-management-backup is currently active, before creating another resource verify that any active resources are removed.
Phase: FinishedWithErrors
Events:

Name: restore-acm-passive-activate
Namespace: open-cluster-management-backup
Labels:
Annotations:
API Version: cluster.open-cluster-management.io/v1beta1
Kind: Restore
Metadata:
Creation Timestamp: 2022-10-07T05:23:10Z
Generation: 1
Managed Fields:
API Version: cluster.open-cluster-management.io/v1beta1
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:cleanupBeforeRestore:
f:veleroCredentialsBackupName:
f:veleroManagedClustersBackupName:
f:veleroResourcesBackupName:
Manager: kubectl-client-side-apply
Operation: Update
Time: 2022-10-07T05:23:10Z
API Version: cluster.open-cluster-management.io/v1beta1
Fields Type: FieldsV1
fieldsV1:
f:status:
.:
f:lastMessage:
f:phase:
Manager: manager
Operation: Update
Subresource: status
Time: 2022-10-07T05:23:10Z
Resource Version: 7986795
UID: c3283e4b-27ff-45a8-973a-86e0034659f5
Spec:
Cleanup Before Restore: CleanupRestored
Velero Credentials Backup Name: skip
Velero Managed Clusters Backup Name: acm-managed-clusters-schedule-20221006140010
Velero Resources Backup Name: skip
Status:
Last Message: This resource is ignored because BackupSchedule resource open-cluster-management-backup is currently active, before creating another resource verify that any active resources are removed.
Phase: FinishedWithErrors
Events:
[[email protected] ~]#

Managed cluster namespaces should be label to say `cluster backup operator managed cluster` and `accepted or not`

In order to have restore operator working properly we need to add a lable or an annotations (better a label) saying something like this:

backup.cluster.open-cluster-manegement.io/accepted=true or backup.cluster.open-cluster-manegement.io/accepted=false.
In this way we'll accomplish two goals

  1. Understand which managed cluster namespace comes from a backup
  2. Understand which managed cluster namespace was accepted previously (already talked about this in a chat)

To be honest I don't care too much about the way accomplish this, but we need to solve both and this is the first idea I got (open for discussion)

Incorrect command in README

Changed
Run os get schedules -A | grep acm to view the list of backup scheduled.
to
Run oc get schedules -A | grep acm to view the list of backup scheduled.

Also an issue in the documentation in section 1.22.2.3

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.